[Q] Phone hangs or repeatedly reboots - Galaxy Grand Prime Q&A, Help & Troubleshooting

I've had the phone (G530f) for 4 months, and it repeatedly hangs or reboots. It's been back to the Nakhon Sawan centre four times (the last time for a week), and returns in just the same state. Works fine on Wifi, but put a SIM in (tried 3 different ones), and the trouble starts within 30 minutes. I've re-installed Android - no difference. Samsung don't seem competent to fix it. Any suggestions, please. I'm reaching the stage where I'm about to throw it out, but I can't afford another. :crying:

mikegbr2 said:
I've had the phone (G530f) for 4 months, and it repeatedly hangs or reboots. It's been back to the Nakhon Sawan centre four times (the last time for a week), and returns in just the same state. Works fine on Wifi, but put a SIM in (tried 3 different ones), and the trouble starts within 30 minutes. I've re-installed Android - no difference. Samsung don't seem competent to fix it. Any suggestions, please. I'm reaching the stage where I'm about to throw it out, but I can't afford another. :crying:
Click to expand...
Click to collapse
Are you rooted? After using Mohan's rooting method, I get occasional 'could not detect SIM card' errors that force a reboot

zomgitsanoob said:
Are you rooted? After using Mohan's rooting method, I get occasional 'could not detect SIM card' errors that force a reboot
Click to expand...
Click to collapse
No, just the normal Android. If fact, I've reinstalled it with the original (Thai) version, but that made no difference.
Sorry about the delay in replying.

Related

Temperamental...

My G1 has recently started playing up. The problems first started with cyanogen 4.1.9999 - it would loose signal, but a reboot sorted this out and it may only happen once every two or three days if that. It was an unstable ROM, no biggy.
But then one day, after rebooting, it got stuck at the android screen then just turned itself off. This repeated several times before it just wouldn't turn on. I left it for a while and tried again later, it turns on, boots but no signal. Rebooting did nothing.
I reflashed (without wiping) cyanogen 4.1.999. and everything seems okay. But then the phone started crashing and rebooting rather a lot, and rather unpredictably. So I wiped, flashed the ADP rom and then cyanogen 4.2.1 rom. This process was a massive brainache - plugging in the usb cable managed to crash the phone within 2-5 min guaranteed, it automatically rebooted.
So here I am. Cyanogen 4.2.1 - after a complete sdcard format, wipe, ext3 repair and flash. The problems still persist! But it's temperamental, a lot of the time I loose signal still, it often reboots itself and hates anything plugged in the usb when it's turned on - making charging the thing awkward.
I used the log collector app to get these logs
http://nopaste.info/17b5351296.html
http://nopaste.info/2e98b9d044.html
At some point during those logs, the signal is lost. The log collector doesn't seem to retrieve a very long backlist, these were taken minutes apart but don't overlap, so I haven't caught a crash. I'm not sure if there are better ways to view logs/debug?
But it's all very temperamental. Occasionally it boots up and life is fine. But more often than not it will loose signal and reboot itself somewhere along the line.
Has anyone come across anything like this before? When it looses reception if I manually try an connect to a network it will say
"This SIM does not allow a connection to that network"
Click to expand...
Click to collapse
I've read that could perhaps be a problem with the sim... but the sim wouldn't cause reboots would it?
Any advise would be great. I bought the G1 off ebay just under a year ago, so no warranty.

[Q] IceColdInsomnia - 7.0 AOKP SIM card reboot issue

I can't remember the exact error message but my phone will randomly restart and produce a SIM card error, prompting me to restart again. Things go back to normal after the 2nd reboot - this tends to happen every day.
I've searched all IceColdInsomnia - 7.0 AOKP forums and these Q & A forums as well to no avail :-( Anybody have experience with this issue?
Thanks in advance,
Rob
DrumRobC said:
I can't remember the exact error message but my phone will randomly restart and produce a SIM card error, prompting me to restart again. Things go back to normal after the 2nd reboot - this tends to happen every day.
I've searched all IceColdInsomnia - 7.0 AOKP forums and these Q & A forums as well to no avail :-( Anybody have experience with this issue?
Thanks in advance,
Rob
Click to expand...
Click to collapse
I've seen this error before. It happens totally randomly. I've even gotten it with no reboot, all that happened was my launcher force closed. I would press OK to restart the phone and same thing - it would reboot fine. Then I just started pressing the back button to remove the error box instead of rebooting. I would be connected to the network so my SIM was fine.
I'm guessing something is triggering a faulty error message. Every time I had it there didn't appear to be an error but the dialog box appears anyway. I've since switched ROMs but if you can get a logcat when it happens (search XDA on how to do that) and pass it along to blackwing182 he might be able to figure it out.
It reminds me of when you suddenly kill the power on your PC and Windows tells you "Windows was shut down unexpectedly, now I need to spend 35 minutes checking for errors!" even though everything is fine

[Q] Nexus 4 -- Only working while plugged in...?!

Yeah... I'm not great at titling... Anywho...
I've come across a problem, of which I'll attempt to go through everything I did that leads to the point, which is; my Nexus 4 doesn't turn on without being plugged into, either the wall or any PC.
So my phone crashes, solemnly (probably because I have Cyanogen on my phone), but lately (lately is in this past week), it's been crashing 3-4 times a day. Then, a few days ago, I was on it and it crashed again, this time, it wouldn't turn on -- my brother was (and probably still is) under the impression that I bricked it -- I would still be thinking the same but seeing as the phone turns on whilst being plugged in I'm wondering if the battery is shot, the hardware is shot, they're both shot or something more undesirable is happening.
I'm not blaming the app for this, however, the frequent crashing did start to happen more violently after I installed and used "Google Camera" for no less than 5 minutes -- at which time, I uninstalled the app and went to the Default Camera App, only for it to also crash the phone, thereafter, the phone just started to crash no matter what I did.
The phone also chooses when to shut itself off; sometimes if I unplug it, it'll turn off immediately, other times I've noticed it'll actually stay on for awhile (the longest its gone so far is 5-10 minutes). I was playing around with wallpaper when I decided to see if I might be able to use the camera, to my dissatisfaction, the phone crashed -- I noticed this when I looked back at the screen.
So now, for the last 18 (give or take 4 hrs) hours, I've been using the phone 'normally' whilst plugged in.
JJBerryere said:
Yeah... I'm not great at titling... Anywho...
I've come across a problem, of which I'll attempt to go through everything I did that leads to the point, which is; my Nexus 4 doesn't turn on without being plugged into, either the wall or any PC.
So my phone crashes, solemnly (probably because I have Cyanogen on my phone), but lately (lately is in this past week), it's been crashing 3-4 times a day. Then, a few days ago, I was on it and it crashed again, this time, it wouldn't turn on -- my brother was (and probably still is) under the impression that I bricked it -- I would still be thinking the same but seeing as the phone turns on whilst being plugged in I'm wondering if the battery is shot, the hardware is shot, they're both shot or something more undesirable is happening.
I'm not blaming the app for this, however, the frequent crashing did start to happen more violently after I installed and used "Google Camera" for no less than 5 minutes -- at which time, I uninstalled the app and went to the Default Camera App, only for it to also crash the phone, thereafter, the phone just started to crash no matter what I did.
The phone also chooses when to shut itself off; sometimes if I unplug it, it'll turn off immediately, other times I've noticed it'll actually stay on for awhile (the longest its gone so far is 5-10 minutes). I was playing around with wallpaper when I decided to see if I might be able to use the camera, to my dissatisfaction, the phone crashed -- I noticed this when I looked back at the screen.
So now, for the last 18 (give or take 4 hrs) hours, I've been using the phone 'normally' whilst plugged in.
Click to expand...
Click to collapse
Have you tried to make a clean install and not restoring anything to check if that helps? If that doesn't help I would try flashing a factory image.
theminikiller said:
Have you tried to make a clean install and not restoring anything to check if that helps? If that doesn't help I would try flashing a factory image.
Click to expand...
Click to collapse
Yes I have tried to make a clean install, with a different OS as well, CyanogenMOD's take on Lollipop 5.1. The phone still turns itself off though.
What is "Flashing a factory image" mean?
JJBerryere said:
Yes I have tried to make a clean install, with a different OS as well, CyanogenMOD's take on Lollipop 5.1. The phone still turns itself off though.
What is "Flashing a factory image" mean?
Click to expand...
Click to collapse
You download the full stock ROM from Google, and use fastboot to flash it. Here is a guide on how to do it. http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
JJBerryere said:
Yes I have tried to make a clean install, with a different OS as well, CyanogenMOD's take on Lollipop 5.1. The phone still turns itself off though.
What is "Flashing a factory image" mean?
Click to expand...
Click to collapse
If you want a 100% clean flash, just download the factory image and flash it by executing the flash-all.bat (you are using windows I guess) script. It might be necessary to reboot into the bootloader first.
cheers
greg17477 said:
If you want a 100% clean flash, just download the factory image and flash it by executing the flash-all.bat (you are using windows I guess) script. It might be necessary to reboot into the bootloader first.
cheers
Click to expand...
Click to collapse
Tried this, didn't work.
My phone has basically been flashing red for awhile now and it doesn't turn on at all.
Your battery is dead, same happened with me 3 months ago.....
I took it to service centre, they just changed the battery (ask them specifically otherwise they will wipe data too, internal included)
Overall it cost me INR 1200 i.e approx $20
anupampb said:
Your battery is dead, same happened with me 3 months ago.....
I took it to service centre, they just changed the battery (ask them specifically otherwise they will wipe data too, internal included)
Overall it cost me INR 1200 i.e approx $20
Click to expand...
Click to collapse
Yeah, so I figured.
My father and I just replaced the battery with a Tablet's battery. Although probably not seen as proper. If it works, why fight about it? Haha.
Thanks.
JJBerryere said:
Yeah, so I figured.
My father and I just replaced the battery with a Tablet's battery. Although probably not seen as proper. If it works, why fight about it? Haha.
Thanks.
Click to expand...
Click to collapse
Your farther does not really worry enough for your health
https://en.wikipedia.org/wiki/Lithium-ion_battery#Safety

Galaxy Note 4 constant freezing & restarting!

Hi there,
So my galaxy note 4 is having some serious problems for the last couple of days and it's really starting to bother me. I've tried doing everything I can find online so far but to no avail I've had no luck at all. Basically, my phone constantly keeps freezing and restarting. It will crash for quite a period of time then restart itself, crash and restart. It probably crashes and freezes about 80-90 times a day? More if I'm trying to use it of course (It also resets itself when not using it).
I've tried everything, bought a replacement (genuine) battery and not fixed it. Got to the point where I seen online about doing a factory reset so I backed everything up to my computer, started the factory reset and when I was going through the setup of logging into google and samsung account, it continues to crash and freeze all over again. (It crashed & restarted whilst retrieving my apps from google, thus I had to reinstall my apps again manually after I finally got it setup again).
To make matters worse, I cancelled the insurance cover last month and only a few days ago this started happening. I've not dropped the phone or damaged it in anyway, screen is completely perfect too. It just constantly crashes and restarts on it's own. Get a phone call and it crashes, using google maps, crash. It's beyond unusable now. I still have 4 months left of the contract before I'm due an upgrade and I really don't think it will last me that long.
Can someone PLEASE help? Suggestions would be so helpful!!!
Thank you!
P.S Phone isn't rooted, only using Nova Launcher prime.
Sounds like your battery is on its way out. Have you tried a new battery?
Already mentioned in post above
tiguy99 said:
Sounds like your battery is on its way out. Have you tried a new battery?
Click to expand...
Click to collapse
QCube said:
I've tried everything, bought a replacement (genuine) battery and not fixed it.
Click to expand...
Click to collapse
Earlier in the week I had an error I've not seen before. Phone restarted and went to black screen sort of looking at a recovery screen with android logo and in the centre of the screen was the message
"Kernal Panic" with some information on the top. This only has happened the one time and hasn't happened since. Took the battery out and restarted again...
Try hardreset or flash via odin
Krprem said:
Try hardreset or flash via odin
Click to expand...
Click to collapse
How do I go about doing either of these....
Still happening and it's driving me insane, It won't last me until the end of my contract (January)
Its rebooting 80-90 times in ONE day? Good god! Have the phone turned off then. Unnecessary pressure is being put on the phone mate!
Factory Reset isn't going to solve it anyway, its for tiny problems. Your system is somehow messed up badly.
Do what the above member said. Flash a stock ROM via Odin. But before that you need to completely wipe the phone. To completely wipe you need a custom recovery like TWRP. So flash it now, root the phone, then reboot into TWRP and use the Advanced Wipe section to wipe everything (external SD not needed), then reboot the phone in Download mode, and flash the latest stock ROM via Odin.
You are now part of a large group of us having the same issues. Several things have been tried. One thought is that the motherboard is faulty. Replacing it would be expensive. Download the app "wake lock" and set it to partial_wake_lock. Don't ask me why it works, but it does. Apparently the phone goes nuts when the screen tries to go off, the partial lock keeps it from crashing. That makes the phone usable, hopefully a permanent solution will become available. ;( The only time it goes nutty again is if the battery runs down and when I restart, the app is not running. Going back to the back and setting it to partial has allowed me to play games, etc for extended periods of time and no problems. It shouldn't be that way, and I really suspect the marshmallow update and then security update screwed it up, it was fine before that.
QCube said:
Hi there,
So my galaxy note 4 is having some serious problems for the last couple of days and it's really starting to bother me. I've tried doing everything I can find online so far but to no avail I've had no luck at all. Basically, my phone constantly keeps freezing and restarting. It will crash for quite a period of time then restart itself, crash and restart. It probably crashes and freezes about 80-90 times a day? More if I'm trying to use it of course (It also resets itself when not using it).
I've tried everything, bought a replacement (genuine) battery and not fixed it. Got to the point where I seen online about doing a factory reset so I backed everything up to my computer, started the factory reset and when I was going through the setup of logging into google and samsung account, it continues to crash and freeze all over again. (It crashed & restarted whilst retrieving my apps from google, thus I had to reinstall my apps again manually after I finally got it setup again).
To make matters worse, I cancelled the insurance cover last month and only a few days ago this started happening. I've not dropped the phone or damaged it in anyway, screen is completely perfect too. It just constantly crashes and restarts on it's own. Get a phone call and it crashes, using google maps, crash. It's beyond unusable now. I still have 4 months left of the contract before I'm due an upgrade and I really don't think it will last me that long.
Can someone PLEASE help? Suggestions would be so helpful!!!
Thank you!
P.S Phone isn't rooted, only using Nova Launcher prime.
Click to expand...
Click to collapse
Which version is your note 4? verizon? att? tmobile? sprint? etc united states variant? other country? This helps find out if others that are having the same problem are on the same setup as you and more importantly tells me if I'm likely to have a problem with mine getting ready to come. :laugh:
ithehappy said:
Its rebooting 80-90 times in ONE day? Good god! Have the phone turned off then. Unnecessary pressure is being put on the phone mate!
Factory Reset isn't going to solve it anyway, its for tiny problems. Your system is somehow messed up badly.
Do what the above member said. Flash a stock ROM via Odin. But before that you need to completely wipe the phone. To completely wipe you need a custom recovery like TWRP. So flash it now, root the phone, then reboot into TWRP and use the Advanced Wipe section to wipe everything (external SD not needed), then reboot the phone in Download mode, and flash the latest stock ROM via Odin.
Click to expand...
Click to collapse
80-90 times in one day is probably being generous. I've not actually counted how many times it restarts but If I need to use my phone I can guarantee it will be restarting a couple of times. Driving using navigation *Crashes* Inbound phone call *Crashes* get text message *crashes* all followed by the phone restarting. Practically unusable.
phonepie said:
Which version is your note 4? verizon? att? tmobile? sprint? etc united states variant? other country? This helps find out if others that are having the same problem are on the same setup as you and more importantly tells me if I'm likely to have a problem with mine getting ready to come. :laugh:
Click to expand...
Click to collapse
Vodafone UK - Samsung Galaxy Note 4 / SM-N910F running Android 6.0.1
grizzylemon said:
You are now part of a large group of us having the same issues. Several things have been tried. One thought is that the motherboard is faulty. Replacing it would be expensive. Download the app "wake lock" and set it to partial_wake_lock. Don't ask me why it works, but it does. Apparently the phone goes nuts when the screen tries to go off, the partial lock keeps it from crashing. That makes the phone usable, hopefully a permanent solution will become available. ;( The only time it goes nutty again is if the battery runs down and when I restart, the app is not running. Going back to the back and setting it to partial has allowed me to play games, etc for extended periods of time and no problems. It shouldn't be that way, and I really suspect the marshmallow update and then security update screwed it up, it was fine before that.
Click to expand...
Click to collapse
I'm gonna give this a go and hopefully it'll help! Thanks for the advice. Funnily enough, for a couple of months the phone has been prevented from the screen going off. I get a text or a notification and the screen would stay on until I hit the power button to turn it back off. Get a text in the middle of the night and I'd wake up to a boiling hot phone the next day, almost too hot to even keep in the hands. This literally frustrated me beyond belief and had to get a new battery and all sorts of complications. Also you mention the android update which made me think, I NEVER had this issue before I installed the security update for 6.0.1 - I put my money on something really stupid that's sincerely knackered my phone for certain!
While upgrading a phone, especially for major upgrades like from LP to MM, OTA method should always be avoided. You MUST do a clean flash of the ROM, otherwise you are bound to have problems. 80% of time people complain because they didn't flash the ROM cleanly, so whatever you want to do now, do it, but if it doesn't solve it (very likely it won't), then kindly flash the ROM via Odin after a full wipe. And if even that doesn't solve it then its hardware.
QCube said:
80-90 times in one day is probably being generous. I've not actually counted how many times it restarts but If I need to use my phone I can guarantee it will be restarting a couple of times. Driving using navigation *Crashes* Inbound phone call *Crashes* get text message *crashes* all followed by the phone restarting. Practically unusable.
Vodafone UK - Samsung Galaxy Note 4 / SM-N910F running Android 6.0.1
I'm gonna give this a go and hopefully it'll help! Thanks for the advice. Funnily enough, for a couple of months the phone has been prevented from the screen going off. I get a text or a notification and the screen would stay on until I hit the power button to turn it back off. Get a text in the middle of the night and I'd wake up to a boiling hot phone the next day, almost too hot to even keep in the hands. This literally frustrated me beyond belief and had to get a new battery and all sorts of complications. Also you mention the android update which made me think, I NEVER had this issue before I installed the security update for 6.0.1 - I put my money on something really stupid that's sincerely knackered my phone for certain!
Click to expand...
Click to collapse
Thanks for letting me know your version. Hopefully it wont affect mine since mine is US Verizon. But out of curiosity have you checked for even the slightest sticky button? I've had phones where a button started to get tacky and would cause it to keep the screen on or go on and off like what you're saying. May not even feel like a sticky button. Do they all click very responsive? or do any feel like they have a dull thud experience?
phonepie said:
Thanks for letting me know your version. Hopefully it wont affect mine since mine is US Verizon. But out of curiosity have you checked for even the slightest sticky button? I've had phones where a button started to get tacky and would cause it to keep the screen on or go on and off like what you're saying. May not even feel like a sticky button. Do they all click very responsive? or do any feel like they have a dull thud experience?
Click to expand...
Click to collapse
The volume rocker and power button feel really loose but this isn't really something new. Something I have noticed is when I take the cover off the back, the battery barely stays in itself. If holding screen upwards and battery cover off then It doesn't hold the battery which made me possibly think that perhaps the battery does not situate properly and doesn't deliver enough power (or too much) but this was just one of my theories into why the hell my phone is acting this way.
Edit:
Forgot to add I'm running the security patch 01/08/2016
QCube said:
The volume rocker and power button feel really loose but this isn't really something new. Something I have noticed is when I take the cover off the back, the battery barely stays in itself. If holding screen upwards and battery cover off then It doesn't hold the battery which made me possibly think that perhaps the battery does not situate properly and doesn't deliver enough power (or too much) but this was just one of my theories into why the hell my phone is acting this way.
Edit:
Forgot to add I'm running the security patch 01/08/2016
Click to expand...
Click to collapse
Are you able to wedge a folded small piece of paper between the bottom edge of the battery and the phone to make the battery fit tighter? I mean it's not good to have a loose battery. But I can't see how that would cause the screen to stay on. If anything I would think it would cause the phone to shut off or reboot.
QCube said:
80-90 times in one day is probably being generous. I've not actually counted how many times it restarts but If I need to use my phone I can guarantee it will be restarting a couple of times. Driving using navigation *Crashes* Inbound phone call *Crashes* get text message *crashes* all followed by the phone restarting. Practically unusable.
Vodafone UK - Samsung Galaxy Note 4 / SM-N910F running Android 6.0.1
I'm gonna give this a go and hopefully it'll help! Thanks for the advice. Funnily enough, for a couple of months the phone has been prevented from the screen going off. I get a text or a notification and the screen would stay on until I hit the power button to turn it back off. Get a text in the middle of the night and I'd wake up to a boiling hot phone the next day, almost too hot to even keep in the hands. This literally frustrated me beyond belief and had to get a new battery and all sorts of complications. Also you mention the android update which made me think, I NEVER had this issue before I installed the security update for 6.0.1 - I put my money on something really stupid that's sincerely knackered my phone for certain!
Click to expand...
Click to collapse
Let me know how it goes. There are other threads about same issue. Most of us have tried reflashing, wiping everything, custom roms, going back to stock, trying to downgrade, taking out the sim card, taking out the sd card, not having both in at same time, brand new battery, I think even putting the battery in the freezer momentarily, etc. etc. Nobody seems to have had any real luck with it, except those who were under warranty and got a new phone, or are capable and wiling to exchange some hardware. I just find it odd that it happened all of a sudden after updates and recently to many people.. Still, I keep coming here hoping someone will have great news. Mine started with marshmallow, but definitely got worse with the security update.
grizzylemon said:
Let me know how it goes. There are other threads about same issue. Most of us have tried reflashing, wiping everything, custom roms, going back to stock, trying to downgrade, taking out the sim card, taking out the sd card, not having both in at same time, brand new battery, I think even putting the battery in the freezer momentarily, etc. etc. Nobody seems to have had any real luck with it, except those who were under warranty and got a new phone, or are capable and wiling to exchange some hardware. I just find it odd that it happened all of a sudden after updates and recently to many people.. Still, I keep coming here hoping someone will have great news. Mine started with marshmallow, but definitely got worse with the security update.
Click to expand...
Click to collapse
why don't you reflash you device with supported PIT file and stock F.W ?
QCube said:
Hi there,
So my galaxy note 4 is having some serious problems for the last couple of days and it's really starting to bother me. I've tried doing everything I can find online so far but to no avail I've had no luck at all. Basically, my phone constantly keeps freezing and restarting. It will crash for quite a period of time then restart itself, crash and restart. It probably crashes and freezes about 80-90 times a day? More if I'm trying to use it of course (It also resets itself when not using it).
I've tried everything, bought a replacement (genuine) battery and not fixed it. Got to the point where I seen online about doing a factory reset so I backed everything up to my computer, started the factory reset and when I was going through the setup of logging into google and samsung account, it continues to crash and freeze all over again. (It crashed & restarted whilst retrieving my apps from google, thus I had to reinstall my apps again manually after I finally got it setup again).
To make matters worse, I cancelled the insurance cover last month and only a few days ago this started happening. I've not dropped the phone or damaged it in anyway, screen is completely perfect too. It just constantly crashes and restarts on it's own. Get a phone call and it crashes, using google maps, crash. It's beyond unusable now. I still have 4 months left of the contract before I'm due an upgrade and I really don't think it will last me that long.
Can someone PLEASE help? Suggestions would be so helpful!!!
Thank you!
P.S Phone isn't rooted, only using Nova Launcher prime.
Click to expand...
Click to collapse
Aside from the previously proposed wake lock solution, members in the T-Mobile Note 4 threads have experienced limited success with a downgrade to LP from MM.
From my reading, these issues seem to be common across all Snapdragon models, not to say it Exynos is excluded (I don't frequent Exynos threads).
​
himuslg123 said:
why don't you reflash you device with supported PIT file and stock F.W ?
Click to expand...
Click to collapse
I tried that and it didn't work for me. The only surefire solution is a replacement device, but even then there's no guarantee the device won't start acting up in the future.
pls help stuck in download mode
this is the issue I'm getting...I did a complete data wipe using twrp...now stuck on this screen...cant even push files...device not recognized in adb or fastboot mode....
what to do...??
imgur(dot)com/a/gKPaL
Well a new motherboard was the only thing that fixed it for me, replaced under the 2 year warranty but I had to wait a while for parts. What is interesting is that the phone is much faster, the battery life much better than when it was new. Also it now barely gets warm using google maps - before it got quite hot. It would be very interesting to find out what percentage of Note 4's have been going down with is problem - mine was a fairly early one - was Samsung rushing to beat Apple two years ago and a bad batch of parts used? I don't know -we need some answers on what is the problem to be sure.
Just a personal experience and thus advice, please don't keep flashing bunch of stuffs every other day. The more your eMMC gets used more chance of your phone getting messed up. This is how my Note 3 died, kept flashing this and that, and did the same on Note 4 too, but have now stopped. I don't know whether there's an endurance rating on these eMMCs used or not but this is what I think, I could be wrong, please quote me in that case.
hathertonwood said:
Well a new motherboard was the only thing that fixed it for me, replaced under the 2 year warranty but I had to wait a while for parts. What is interesting is that the phone is much faster, the battery life much better than when it was new. Also it now barely gets warm using google maps - before it got quite hot. It would be very interesting to find out what percentage of Note 4's have been going down with is problem - mine was a fairly early one - was Samsung rushing to beat Apple two years ago and a bad batch of parts used? I don't know -we need some answers on what is the problem to be sure.
Click to expand...
Click to collapse
Wow, that sounds promising. I'm sending mine for replacement, and although I'm not getting a new MB installed, hopefully the incoming unit will be similar in performance to yours.
ithehappy said:
Just a personal experience and thus advice, please don't keep flashing bunch of stuffs every other day. The more your eMMC gets used more chance of your phone getting messed up. This is how my Note 3 died, kept flashing this and that, and did the same on Note 4 too, but have now stopped. I don't know whether there's an endurance rating on these eMMCs used or not but this is what I think, I could be wrong, please quote me in that case.
Click to expand...
Click to collapse
Your reasoning sounds plausible, but my phone suffered similar issues and I only flashed my unit 2-3 times in the 14 months I had it.

Moto Z Force - Restart Loop

I'm having this issue on my 2 week old Moto Z Force.
I actually noticed a similar issue on a display model in Verizon but chalked it up to just that.. a display model in Verizon and I carried on with my purchase.
I've had a few experiences where it randomly reboots and then it's good to go again. Seems to happen more frequently when the phone is in high use, so I suspected an issue with RAM being full? The restart seems to take place at the same part of the startup animation every time.
TODAY - phone was in pocket while I was on a call for work and I felt it vibrate on a consistent interval. When off the phone, I looked at the phone and it is in a restart loop. The only thing I can do at this point is hold the Volume Down key to get into BIOs (through the rebooting loop) and then I have the following uptions:
1) Start
2) Restart Boot loader
3) Recovery Mode
4) Power Off
5) Factory Mode
6) Barcodes
7) BP Tools
8) QCOM
9) Bootloader Logs
If I sit in this menu inactive for awhile it will timeout and just shut the phone off until I turn it back on and then the loop resumes. I'm beginning to think I need to go with option 5 here... any help is appreciated...
No new apps were recently installed. I barely used my phone the morning when getting to work besides charging it to 90+/- % on my way in.
First I buy a hand grenade of a phone, forced to return, and now I buy a phone that is actually showing me a big issue (it is getting hot too). I'm going to let it sit off before trying a Factory Mode. :crying:
Video of the cycle here: https://www.dropbox.com/s/v7dc6erfydj87ib/Skys Phone.MOV?dl=0
Better ask in a Moto Z Force subforum.
SteveHG said:
Better ask in a Moto Z Force subforum.
Click to expand...
Click to collapse
Thanks Steve. Any suggestion on where would be best? I would have thought the Q&A would be accurate...
I have had this phone for just over two month and have not had any similar issues. I assume that you've already tried options 1, 2, and and 4. Have you also gone into recovery to see if you can clear the cache?
I would personally return it as broken, but I save everything important to my SD, just in case this kind of thing happens.
I had this very same issue. I did a hardware replacement with Verizon and the new phone works great.
broprah said:
I had this very same issue. I did a hardware replacement with Verizon and the new phone works great.
Click to expand...
Click to collapse
Awesome! Glad to hear that it worked out for you. Fingers crossed they don't give me a refurbished model (again, mine was 2 weeks old) and that I have the same luck as you.
rmonjay said:
I have had this phone for just over two month and have not had any similar issues. I assume that you've already tried options 1, 2, and and 4. Have you also gone into recovery to see if you can clear the cache?
I would personally return it as broken, but I save everything important to my SD, just in case this kind of thing happens.
Click to expand...
Click to collapse
I have tried all of the options at this point and none of those work. I can't even get into recovery. Every option does the same thing... reboots, reboots, reboots, etc.
New phone should be here tomorrow. I've got the good old run around on this one though and I'm not happy about it with Verizon and Best Buy. Best Buy's return policy is 14 days and I ran into issues on day 16, no exceptions according to them and off to Verizon I go where I had to purchase a temporary flip phone for the week my phone has been out of commission.
I'm in need of a new SD card before I put anything on there, it has been flaky. The only thing I care about on my phone is the media (photos, videos, and music), all of which are on Google. The crap thing is that now I need to spend another X hours putting all my apps, passwords, etc. on it to my liking. Just did this when moving to the Note 7, then Moto Z Force, and now again with the replacement. Starting to get annoyed.
Update - when switching to the replacement device I found the issue followed to the new phone... Meaning the issue was with the SD card or the SIM card. Found it was an issue with the SD card after switching between the two phones and experimenting. Unreal. Who would have thought?!
I will be formatting the card and keeping this thread posted on if that resolves it or if it's time for a new card (as I mentioned above).
I am very hopeful with your post. My phone has been going crazy with the rebooting mode for two days now. I brought it into Verizon yesterday but all of a sudden (of course) it started working. Now today its gone back to rebooting, over and over and over again. 2nd day in a row I am going to waste my lunch hour and run to Verizon. This time I will ask them about a new SIM card. BTW... I just got a new (refurbished) less then a week ago.
TBabbs said:
I am very hopeful with your post. My phone has been going crazy with the rebooting mode for two days now. I brought it into Verizon yesterday but all of a sudden (of course) it started working. Now today its gone back to rebooting, over and over and over again. 2nd day in a row I am going to waste my lunch hour and run to Verizon. This time I will ask them about a new SIM card. BTW... I just got a new (refurbished) less then a week ago.
Click to expand...
Click to collapse
I just fixed my Moto Z Play by removing the SD card... for the second time... -_- I've had a previous issue where my phone rebooted as part of an update and it stopped seeing my previous SD card. After checking the SD card in various other systems, I found the SD card was completely shot. After some digging online, there is apparently an issue with the new Moto Z's that if your SD card isn't fast enough (somewhere around 85-90+ Mb/s)m, the Moto Z will slowly start to eat your SD card until it fails and causes issues for your phone. In this case, my second SD card failure was that my phone went into infinite booting loops until I removed the card. -_-
This card lasted longer, mainly I think due to the fact that it was larger and faster then my previous one, but it looks like I will need to get a new fast card.
Anyways, I hope this helps you or anyone else who comes across this thread.
About 2-3 weeks ago, the same thing started to happen to me, after that, phone started to act crazy...
-Bluetooth connection was working but glitching,
-Overheat (bottom of the phone) then started reboot in loop (until at start I'm able to turn off wifi). Did everything your supposed to do, clear cache, forget network, deleted my latest app, reboot, reboot in safe mode, remove sd/sim tray... the issues we're still there...
-After a few days of repeating all those steps (or don't know what I did), I finally got rid of the oveheat reboot loop when the wifi is on. But can only see and connect to 2,4g network, no 5g (doesn't see any) and no Bluetooth (turns on, but doesn't see anything), every other device in house works and connect like they should.
-the setting app, and the phone app started to be slow (freezes for a few seconds before the system ask you if you wanna wait or close the app, I choose wait and the app unfreeze)
-Ive tried the rsa (repair system assistant) from verizon without any fix
-finally decide to go for the factory reset. It fixed the freezing issues, works like a charm, but still no 5g wifi nor Bluetooth...
Is there a driver update possible for this ? Or because of overheat it might have damage the device...
I have the phone since September, never had any issues, went through all update, force droid edition xt1650-02, build ncl25.86-11.5, nougat 7.0 (wish verizon would update to 7.1.1 anytime soon), since its gsm unlocked, I'm using it on a Canadian network (Fido)
thanks for this thread. It was able to help me diagnose my wifes phone. The SD card she has been using since her DROID CHARGE (2011!!!) finally bit the dust in this phone. I swapped it out for a new Sandisk micro sdxc uhs-I up to 80 MB/s card class 10 and it booted. funny thing was she was not even storing pictures on the card.
Motorola Droid Z Force restarting (Bootloop)
My motorola z force has started to boot loop restarting again and again ... i have tried following
full formatting from recovery twice, phone starts well but when i turn on my wifi it keep restarting ..
if i turn my wifi off, the phone works good but as soon as i turn on my wifi boot loop starts again and again.......
i guess i need to flash the firmware but dont know how to flash new firmware ....
XDA very big name .. i need help....
alidanwer said:
My motorola z force has started to boot loop restarting again and again ... i have tried following
full formatting from recovery twice, phone starts well but when i turn on my wifi it keep restarting ..
if i turn my wifi off, the phone works good but as soon as i turn on my wifi boot loop starts again and again.......
i guess i need to flash the firmware but dont know how to flash new firmware ....
XDA very big name .. i need help....
Click to expand...
Click to collapse
I've had bootloops happen a couple of times for different triggers, and I still run the phone stock since release date with no updates ever taken. This has worked to correct the issue for me a couple of times. Give it a try:
Let your phone get down below 5% battery life, then plug into the turbo charger. Then fool around with whatever triggers the reboots.
Eventually the phone will not restart because the phone's battery needs to charge a little. When phone charges beyond 10% try to turn the phone back on, and see if boot loop persists. If it persists drain below the 5% battery life and try again. Usually, when I have fooled around with this scenario two or three times the bootloop has corrected itself.
Hope this works for you. Good luck.
Thanku, I will definitle give it a try .... and i am updated to nougat all updates till date installed...
Still restarts.... its been a month... without solution..
alidanwer said:
Still restarts.... its been a month... without solution..
Click to expand...
Click to collapse
A couple of weeks ago, the restart loop happened to me again, and my usual tinkering while connecting and disconnecting Turbo Charger wouldn't work. So I did some research on "stuck power button" or "power button not working".
I did the following:
I blew with my mouth over the power button (kind of like puting your lips in position to whistle)
I also gently tried to clasp the power button using a pair of tweezers, but couldn't. Instead I just kind of lifted/tugged-on the power button from the top and bottom.
I feel like I didn't really do anything, but the phone has been working for over a week now. Maybe pure luck.
Its weird, this made me think it is a hardware issue, but somehow the phone reacts as if it were software related.
Give it a try. Hope you have some luck.

Categories

Resources