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.
Hi,
I am new to this forum and do not know much of the technical terms. So here is my problem as best as I could say...
I have a unlocked Samsung S4 purchased last Sept (Philippines/SE Asia version, I think). The phone worked fine until the latest upgrade to Kitkat 3 weeks ago.
A week after the upgrade, the phone started rebooting itself. After checking this forum, it looked like a battery problem. On checking, it did have a swollen battery. At the same time, the S4 stopped working as a phone - meaning I could browse, use apps, but could not make calls.
First changed the battery with an original from Samsung, hoping everything would sort out. Unfortunately, it did not. The phone still kept restarting and the network signal showed as not available. So I went to my provider and got a new SIM card and changed it.
Unfortunately, that has also not solved my problem.
Now, my phone keeps rebooting itself. If I connect it to the charger, then the phone starts successfully. At times, it behaves well, but suddenly/randomly, if I touch an app (any app, no pattern) it will reboot again. Once it starts rebooting, it keeps doing that in the screen which has the samsung music comes - it would turn off again and keep restarting until that screen reaches again. Only if I connect to the charger would it start. Again, there is signal at times and there is no signal most of the times. My area has good network signal, so that should not be the problem.
I tried clearing the cache and clear all data/apps, but still no luck. Also, my battery still has / holds charge - so that is not the problem.
Could somebody please help me!!! Please let me know if you need any other details regarding this.
TIA.
Baseband version: I9505XXUFNBE
1. Sig & log in Sammobile.com
2. Download ur firmware: HERE
3. Unzip it
4. Phone in DOWNLOAD MODE
5. Flash the firmware through ODIN like the pic attached
It has nothing to do with your battery...but yes a swollen battery can be dangerous. Follow the steps told by @Joku1981 and don't upgrade to kitkat. Wait for a stable release from samsung.
Hi,
I have already upgraded to kitkat, so cannot downgrade now.. . I had the request to upgrade to kitkat by the phone (Samsung).
As mentioned by Joku1981, I downloaded the Philippines firmware and did as mentioned. However, the phone was still randomly shutting down on opening some apps (esp Gallery, Playstore, Chrome) and failed to reboot.
I also tried to download the pit file and flash it again as mentioned in http://forum.xda-developers.com/showthread.php?t=2265477. Still no lock.
I tried with UK's version of firmware, still same problem.
The phone can be restarted only if connected to the usb cable.
The "No Signal" issue seems to have been solved, but the rebooting randomly seems to be a real pain now.
After my latest flash, while i was in the third screen setting up the phone for language/accessibility --> "wi-fi setup" --> "Accept Samsung t&c's", the phone shut down again...
Is there any counter to identify the number of times the phone is flashed? Would it cause any problem?
Thanks
Also No Service now!
Also noticed that after the last 2 restarts, the network signal shows full strength. However the default lock screen shows "No Service" (see picture). When I try to call when the phoneis in this status, the phone gets stuck in the dial screen and has to be rebooted...
akpreets said:
Also noticed that after the last 2 restarts, the network signal shows full strength. However the default lock screen shows "No Service" (see picture). When I try to call when the phoneis in this status, the phone gets stuck in the dial screen and has to be rebooted...
Click to expand...
Click to collapse
Though you flashed, do a factory reset one more time to be on the safe side - make sure the phone is 100% charged, and given your case do NOT touch the phone until the reset has completed.
One more thing to try - from experience some batteries are bigger than others and you said your previous one became swollen. This may cause the power pins to become too compressed causing the new battery to lose contact. This manifests on the phone as rebooting at the slightest of movement/flexing, try this:
1. Remove the battery
2. GENTLY pull out slightly the power pins on the phone - don't pull too hard.
3. Put the battery back, put a piece of cardboard or something at the bottom of the battery to make sure there's good contact
Let us know of the results
Nothing seemed to work but only got worse. The phone could not stay on even for a few hours. Finally gave it to the Samsung Service centre yesterday. They sad it might take upto 3 weeks if there was a motherboard change needed.
Fingers crossed...:crying:
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.
so, guys, this is the second time this happens to me !!
suddenly my phone turns off and then restarts and after it finishes the restart and I enter the passwords and lock the device the device acts normal for seconds and then gets frozen then the notification light turns blue then green then the phone boots again !! and on and on !! I tried the following:
the safe mood !!
switching it to airplane mod !!
taking the SD card off also the sim card off!!
connecting it to the charger!
connecting it to the PC!
turning it off and wait a while then turning it on again!
nothing helped I was able to fix it through the PC companion but I lost everything apps, images, videos WhatsApp data etc
anyone has any idea what happened?
I'm running stock Android 8, up to date with the security patches, also those 2 events happened after the last update! I'm thinking that it may be related to them but I'm not sure!
any words of wisdom?
Hi - I had the exact same problem last week and had to fix (re-install) via PC companion. I was thinking it was due to something I did, but with couple of others reporting maybe it was due to the Feb update
Zewarxx said:
so, guys, this is the second time this happens to me !!
suddenly my phone turns off and then restarts and after it finishes the restart and I enter the passwords and lock the device the device acts normal for seconds and then gets frozen then the notification light turns blue then green then the phone boots again !! and on and on !! I tried the following:
the safe mood !!
switching it to airplane mod !!
taking the SD card off also the sim card off!!
connecting it to the charger!
connecting it to the PC!
turning it off and wait a while then turning it on again!
nothing helped I was able to fix it through the PC companion but I lost everything apps, images, videos WhatsApp data etc
anyone has any idea what happened?
I'm running stock Android 8, up to date with the security patches, also those 2 events happened after the last update! I'm thinking that it may be related to them but I'm not sure!
any words of wisdom?
Click to expand...
Click to collapse
I had that problem before with no help also i post it on sony support
https://forum.xda-developers.com/xz-premium/help/help-phone-restarting-t3754120
https://talk.sonymobile.com/t5/Xperia-XZ-Premium/Help-Phone-Keep-Restarting/td-p/1303354/page/3
Hi,
I was going through it and found this link https://www.technipages.com/why-does-android-randomly-restart
Mine happened when I tried to install a tempered glass protector using LOCA. The LOCA install didn't go well and that's when it started restarting randomly. I am not sure if the LOCA jammed the power button or water/ alcohol got inside. In fact I had a tough time trying to do a PC companion since the USB port was also messed up. After several tries - the USB opened up was recognized.
Hey everyone, I've run into quite an issue.
My phone was in the charger working very well, I went away for only a few minutes and when I was back it was totally unresponsive.
I've tried to do a forced reboot, double click the screen, try to boot into recovery and fastboot. But so far no luck. Even upon inserting it to my PC and look at device manager, it doesn't show anything, not even when unplugging it and plugging it in again. Also have tried different adapters and so on.
I'm quite unsure what could cause this happening out of nowhere.
Could it perhaps be the bettery giving up? If any of you are able to come with suggestions before going out and getting a new phone, I'd be very greatfuld.
I'm running pixen-os 10.0. So far never experienced any issues, and been running it a long time.