Hello all,
I have a Moto Z Force Droid (XT1650-02). It's running on Android version 8.0.0, and build number OCLS27.76-69-6. It was acquired from Verizon. It is not rooted (sadly), and the bootloader is locked. It has 32GB of internal storage, however, I added an SDCard(64GB) to increase that storage space.
I'm having some problem(s) with my SDCard, or more so its usage as adopted storage. I've had the phone with the storage for quite a while and everything has been fine. However, 3-4 days ago was when the issues started. One night, my phone was acting really laggy. Which I just chalked up to tech being tech. I let it sit for a bit, tried rebooting it, etc. Well, as time progresses it seems to me that Facebook Messenger is what's slowing it down. So, I try uninstalling it. Of course, this isn't working and android just keeps giving me a helpful little notification that the app is uninstalling (for much longer than it *should* take). I figured I'd reboot into safe mode and try uninstalling it from there. The phone powers off and reboots fine. However, when I tried to unlock the screen, the entire phone froze and crashed after a minute or two. Once it reboots, it gets stuck in the bootloader (or, more specifically, where it says "DROID" and there are little shiny spots moving around the letters). So I used the power button to force the device off and try rebooting again. Again, boots up fine but it freezes at unlock and the cycle starts again.
Around 2 days ago I took it to a Verizon store. Originally I was just told I was going to have to factory reset (which I didn't want to because all the pictures I have and such would be lost. Apps are backed up by Google though). They told me to take out the SDCard, to help save what I could. Then, I got the bright idea to try booting without the card. This time the phone booted fine and unlocked like it should (the only problem now is that I had no internal storage and all the apps that were on the SDCard aren't loading since no SDCard).
When I leave the phone on and install the SDCard, I can browse the internal storage again. However, I can't see any of the files when I try transferring them to PC over USB. As well, after a while of using the phone, or even letting it idle, it will eventually crash and go back to the above botting and not-unlocking scenarios.
Based on how/when the problem started, and the logcats I've grabbed as the phone was crashing, I have reason to believe it has something to do with Facebook Messenger not being removed correctly. [Logcats in the comment below.]
Any help would be greatly appreciated. As well, please tell me if there's anything that needs clarification. (Sorry for the wall of text. I just don't know what else to do at the moment.)
Logcats:
View attachment First.txt
View attachment Second.txt
View attachment Third.txt
So. Bit of an update.
Turns out it's not actually just getting locked in the bootloader. It seems it's been doing a soft reboot.
I've been running "adb logcat" whilst trying different things, until the phone crashes. That's how I got the previous logcats. However, upon "rebooting" the adb logcat continues to run. I can provide a logcat for those, should anybod want it.
WeButterTheBread said:
Hello all,
I have a Moto Z Force Droid (XT1650-02). It's running on Android version 8.0.0, and build number OCLS27.76-69-6. It was acquired from Verizon. It is not rooted (sadly), and the bootloader is locked. It has 32GB of internal storage, however, I added an SDCard(64GB) to increase that storage space.
I'm having some problem(s) with my SDCard, or more so its usage as adopted storage. I've had the phone with the storage for quite a while and everything has been fine. However, 3-4 days ago was when the issues started. One night, my phone was acting really laggy. Which I just chalked up to tech being tech. I let it sit for a bit, tried rebooting it, etc. Well, as time progresses it seems to me that Facebook Messenger is what's slowing it down. So, I try uninstalling it. Of course, this isn't working and android just keeps giving me a helpful little notification that the app is uninstalling (for much longer than it *should* take). I figured I'd reboot into safe mode and try uninstalling it from there. The phone powers off and reboots fine. However, when I tried to unlock the screen, the entire phone froze and crashed after a minute or two. Once it reboots, it gets stuck in the bootloader (or, more specifically, where it says "DROID" and there are little shiny spots moving around the letters). So I used the power button to force the device off and try rebooting again. Again, boots up fine but it freezes at unlock and the cycle starts again.
Around 2 days ago I took it to a Verizon store. Originally I was just told I was going to have to factory reset (which I didn't want to because all the pictures I have and such would be lost. Apps are backed up by Google though). They told me to take out the SDCard, to help save what I could. Then, I got the bright idea to try booting without the card. This time the phone booted fine and unlocked like it should (the only problem now is that I had no internal storage and all the apps that were on the SDCard aren't loading since no SDCard).
When I leave the phone on and install the SDCard, I can browse the internal storage again. However, I can't see any of the files when I try transferring them to PC over USB. As well, after a while of using the phone, or even letting it idle, it will eventually crash and go back to the above botting and not-unlocking scenarios.
Based on how/when the problem started, and the logcats I've grabbed as the phone was crashing, I have reason to believe it has something to do with Facebook Messenger not being removed correctly. [Logcats in the comment below.]
Any help would be greatly appreciated. As well, please tell me if there's anything that needs clarification. (Sorry for the wall of text. I just don't know what else to do at the moment.)
Logcats:
View attachment 4613124
View attachment 4613125
View attachment 4613126
Click to expand...
Click to collapse
Related
I know I know, I am very late to the party.
But anyway, I finally installed the ICS update a few hours ago.... and my phone won't stop rebooting now.
Its not a boot loop, because it does get into Sense UI and I can use it, but eventually after a few minutes, it will reboot all on it's own with no warning. I assume its loading my (rather large) list of apps from the SD card since I have never seen it reboot until it finally wakes up, realizes a SD card is indeed mounted, and starts populating my app list. I never saw that process finish from the few times I bothered to watch it.
I tried removing the SD card and now its no longer rebooting, so unless taking out the battery did something, I assume its likely the SD card.
Is there any way to tell what is causing it without reformatting my phone? I REALLY don't want to wipe out everything.
After some testing, I have found two issues with the update:
1. It seems that it is not any one specific app, but the NUMBER of apps on my SD-card causing the reboot. I have somewhere around 200-250 apps installed on it. So far I can put about 80 or so of them in .androud_secure and it will work fine, I do not know exactly what the braking point it, but I know that having around 140 apps causes it to reboot every 5 minutes, regardless of which apps are on there.
2. I can't load my text messages anymore. Any contact who I have had a long history of texting with, it just gets stuck saying "loading". I can still receieve messages, but since I can't actually open the message list anymore, I can't reply!
I would really like to avoid doing a factory reset if possible, is there anything I can do about this?
I was consideing just doing a SMS-backup and then flashing a custom rom, but I like the 3D feature and it seems like there is not a SINGLE custom rom out there that supports 3D, and many don't support 4G either.
Please, does anyone have any advice?
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
GTMoraes said:
Hi.
My Galaxy S3 is frequently getting into hotboot looping state for no apparent reason. The only way to get it out of this state is to wipe the phone or restore a backup of the "data" folder only.
After that, it might work for a week, but it might not work for a day (not work = start to hotboot loop).
It happens when after the phone screen is locked, it doesn't wake up anymore. It doesn't answers to any calls (like if it's off) or notifications. Just dies.
Forcing a reboot (by holding the power button) or removing the battery ables me to reboot it, but enter in hotboot looping state. I can make it go thru the whole booting state and I see the homescreen (And that's weird because I'm supposed to see the lockscreen first). Some widgets animation works but the device doesn't answer to touch (two softbuttons vibrates when touched, they do vibrate but don't render anything on Android) and then hotboots. Keeps doing this forever. Booting into safemode USED to work, but it doesn't work anymore, I don't know why.
After wiping the device or restoring the Data backup, device turns on as expected (restoring data takes it back to working state exactly like it was before the backup, even the same lockscreen pattern). I've tried to leave a terminal running logcat to catch the error, but it doesn't write in realtime, so when the bug breaks out, the logfile is empty.
I even thought it could be the S3 memory issue with firmware, but I'm using the "fixed" kernels. Also, it is recoverable, and not permanently dead.
I suspect of some rogue app, but I have too many apps to just go through installing one by one (and waiting even weeks to install the other one). Is there any way I can get a postmortem logfile or make logcat write in realtime?
Thanks
Click to expand...
Click to collapse
Try flashing another ROM for S3 and doing a full wipe.
TenKoX said:
Try flashing another ROM for S3 and doing a full wipe.
Click to expand...
Click to collapse
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
GTMoraes said:
Thanks for the reply.
I already did. It started to happen out of nowhere while I used the Android Revolution HD ROM, then after a few wipes and reinstalls with the same problem, I gave a shot to WanamLite ROM. Exactly same problem. Both are based on the original 4.1.2 Android.
I'm pretty sure it is being caused by some rogue app, because the only thing in common between those ROMs is that I "batch-install" all my apps back from Google Play.
So far, I'm suspecting about Vine (it's the last install that I remember since it started to have this issue) and I have already uninstalled it, but it might have been caused by some app update that broke hell to my phone.
If there were some kind of "black box" that I could retrieve after a crash, it could be the solution
Click to expand...
Click to collapse
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
TenKoX said:
If you wipe data, your apps disappear, so I think this is not the problem.
Do another full wipe and DON'T restore your data. Just download again from Google Play and see if the problem appear again.
Click to expand...
Click to collapse
Thanks for the reply.
I started doing this the first time, but it still crashes it. And as I was wasting too much time with this, the backup option came as a option to not have to click to download over 200 apps one by one. Also, it once happened during a long holiday, and I was in a friend's ranch with no decent internet connection for downloading. All my apps were gone and I was stuck with a default phone for five days.
The backup is exactly the point where I finish downloading all the apps and they're installed. There are no cracked programs or adapted (e.g. Nexus camera). Every single app is obtainable from Play Store, so it's pretty fresh
Funny (actually sad) thing is that it's a system-wide error that a wipe solves it. If I don't wipe data and reinstall the same ROM (which under normal condition is no big deal), it doesn't get past from boot screen.
The worst is it happens instantly. It's working now, but then it crashes. Bam, gone. Few hours ago I was texting my gf and I left the phone for a while, waiting for her answer. After some time I knew something was off, picked up the phone and it was pretty warm (first signal), with the LED blinking some Facebook notification. Tried to wake up but it is in coma. I force a restart and it hotboot loops like I described on first post
It -only- happens when screen is locked. I disabled the screen lock for now to see if it's a workaround, but I'm not holding my breath
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
WildfireDEV said:
It could be a hardware malfunction if it can carry through all the roms you flashed and even when you tried a fresh install without your apps it still happened.
Click to expand...
Click to collapse
That's pretty much discarded. Wiping data instantly solves it. It did indeed run for 5 days with no external app without a single problem.
But also it ran over one week with external apps without a problem. I've executed some memory integrity tests and they all reported a-OK.
I'm kinda ruling out the "rogue-app" issue. I thought that recovering "data" from NAND backup was the /sdcard/android/data. But it's deeper than that. Now I don't even have a lead.
Phone already crashed today, without Vine and lockscreen, so that's not the problem. I really need to get some logs out of him. Just need to know how. Only if it could write a realtime log, so I could pull through ADB.
My last resort will be a fresh-fresh android installation, default S3 i9300 ROM, with only essential apps. Already have it triggered for the next crash.
If it goes rogue even this way, I'm running triangleaway and returning it (will be a profit too, the silver border is stripping).
This time around, I'm trying running it without a external sdcard (several files were being corrupted in it, don't know if it's due to force restart by removing battery, or some real issue on the card)
It's a problem within the Facebook social app or Youtube.
I've managed to run the phone flawlessly for weeks without signing in on Facebook, suspecting it might be it.
Today I logged in on Youtube app accidentally, and had to login on Facebook app to retrieve some info. Three hours later, phone went mad again.
I don't know which app caused it, but I think there's some relation to Facebook due to a greater ~involvement~ (couldn't find a proper word.. forgot it) with Android.
I've changed ROMs, launchers, system versions.. but not Kernel. I'll try another kernel and report on Boeffla main thread to see if there's some known bug
Greetings reader. I'm new to the forum but have been viewing threads every now and then, so after having read plenty of times that people should search before posting. I have searched and didn't find what I was looking for, so that's why you can read this now ;p.
4 days ago when I was trying to browse the web in college I wasn't able to connect to the wifi network or even open the wifi settings, so I reset my phone only to find the problem persisting. As if something locked me out of the wifi settings.
I'm perfectly able to access any of the other settings, so I think it's kinda weird.
Shortly after I realised I couldn't get to the wifi anymore my phone started to reboot itself automatically. Ever since that first reboot it just keeps rebooting at the same pace over and over again until I either power it off or until the battery dies.
The phone also get's unusually hot now. Not like, super hot, but definitely hotter than any other time I can remember.
I also get error messages since the problems started saying: 'Process system is not responding'. I then get the option to either force close it or wait. Neither seem to do much if anything at all other than taking away the error message. Sounds kinda critical if you'd ask me.
But so after all these symptoms started to appear I figured I'd just do a factory reset and be done with it, but every time I go into the factory reset settings, I put in my lock screen pattern and then at the last step (pressing the Erase all data button) it just does nothing.
I can touch the button and it does give the animation that it is being pressed, but it just doesn't do anything.
The phone doesn't freeze though, I can still navigate after pressing the button only to see it reboot again shortly after.
After that I tried to flash the rom, but for some reason my PC refuses to show my phone's internal memory in my pcor any sign of my phone's connection at all.
I haven't tried it on any other pc yet, so it might just be my pc, though I doubt it is since it was perfectly able to recognize it shortly before all this started.
The device hasn't endured any shocks lately or expsure to water or whatever, so I think that's ruled out as well.
I am running the stock rom, 2.3 Gingerbread I believe, and the warranty is already way over date (I think. I'll have to check that).
Any suggestions as on how to determine what could be causing this, or how to fix it? Because I really don't want to buy a new phone xD.
Macowski said:
Greetings reader. I'm new to the forum but have been viewing threads every now and then, so after having read plenty of times that people should search before posting. I have searched and didn't find what I was looking for, so that's why you can read this now ;p.
4 days ago when I was trying to browse the web in college I wasn't able to connect to the wifi network or even open the wifi settings, so I reset my phone only to find the problem persisting. As if something locked me out of the wifi settings.
I'm perfectly able to access any of the other settings, so I think it's kinda weird.
Shortly after I realised I couldn't get to the wifi anymore my phone started to reboot itself automatically. Ever since that first reboot it just keeps rebooting at the same pace over and over again until I either power it off or until the battery dies.
The phone also get's unusually hot now. Not like, super hot, but definitely hotter than any other time I can remember.
I also get error messages since the problems started saying: 'Process system is not responding'. I then get the option to either force close it or wait. Neither seem to do much if anything at all other than taking away the error message. Sounds kinda critical if you'd ask me.
But so after all these symptoms started to appear I figured I'd just do a factory reset and be done with it, but every time I go into the factory reset settings, I put in my lock screen pattern and then at the last step (pressing the Erase all data button) it just does nothing.
I can touch the button and it does give the animation that it is being pressed, but it just doesn't do anything.
The phone doesn't freeze though, I can still navigate after pressing the button only to see it reboot again shortly after.
After that I tried to flash the rom, but for some reason my PC refuses to show my phone's internal memory in my pcor any sign of my phone's connection at all.
I haven't tried it on any other pc yet, so it might just be my pc, though I doubt it is since it was perfectly able to recognize it shortly before all this started.
The device hasn't endured any shocks lately or expsure to water or whatever, so I think that's ruled out as well.
I am running the stock rom, 2.3 Gingerbread I believe, and the warranty is already way over date (I think. I'll have to check that).
Any suggestions as on how to determine what could be causing this, or how to fix it? Because I really don't want to buy a new phone xD.
Click to expand...
Click to collapse
Since you've not modified your Sola in any way.
Give this official method a try.
http://xperiafirmware.com/component/content/article/2-uncategorised/29-sony-update-service
Hi,
Something strange happened with my z5c E5823 running stock 7.1.1. Here is the riddle
I got a message the other day, saying space on internal memory is decreasing and the option to transfer stuff to SD card. Since there were almost no pictures and music on the phone, I keep them on SD card, there was the option to transfer about 2GB of Apps. I choose that (big mistake when I think of it now) .
I continued using the phone while the transfer was in progress and @ some point , the phone crashed. That never happened before. Screen froze and stayed like that for around 10 min, completely inactive, and the phone restarted itself alone. After this it all seemed fine until I tried to start the Camera app. It just gave me black screen and some seconds later the message - Camera has stopped/ Restart app.
The front camera and flashlight don't work either.
Another weather app - AcuWeather didn't want to start too, but after reinstalling it it was alright.
There is no such option for the camera app and clearing data and restarting didn't help.
Decided I will do a Factory reset for the first time since I use the device and tried a manual back up of all the info to the SD card. Contacts , personal info and settings backed up successfully , but the process hanged up at 50% when transferring apps. It crashed and stooped. Tried it 2 times !
Since back up wasn't possible I proceeded with the factory reset and after that the phone successfully restored my personal data, without the apps , but the camera didn't work. I did a Software repair with xperia companion with the same result.
Another bug appeared. When I pull down the full notification bar, and want to edit/rearrange the icons/shortcuts and press the little pencil next to the settings(gear) icon, the phone freezes for a few seconds and than the screen turns black. The phone is unusable at that point, thought it works, and receives calls which i can not answer. I only can restart it, because the power button gets me to the window for power off and restart.
Than I read some camera sensors might get disconnected from the board so I opened the phone , but it was alright inside. nothing changed.
Now I got an open phone and no answer or clue whatsoever of how to proceed.
Any ideas are very welcome!
I there a way to reset the phone to an earlier version of android?
Thanks inadvance!
Hi,
My phone restarts randomly and when it comes back, the sd card isn't read. When I go to storage it shows corrupted, and says that it needs to be setup. When I restart the phone myself the sd card works as if nothing happened. I've purchased a new sd just in case, and they're both doing the same thing. Both have no read errors on my pc. When the phone restarts itself, it's a quick restart, shows the samsung logo then back to home screen.
I haven't installed any new apps, but I did do an OTA upgrade to N950U1UEU5CRK1 version. It started happening soon after
Random restart and loss of data
I myself am having the same issue. After the random restart I find that some of my apps will not work properly as if saved data is now missing. I have found that restarting the device again after random restart is a quick fix until it happens again. It was happening on a daily basis multiple times per day, but now I haven't noticed as much eitehr that or I am not paying close attention.
Kowboi said:
I myself am having the same issue. After the random restart I find that some of my apps will not work properly as if saved data is now missing. I have found that restarting the device again after random restart is a quick fix until it happens again. It was happening on a daily basis multiple times per day, but now I haven't noticed as much eitehr that or I am not paying close attention.
Click to expand...
Click to collapse
Hmm was it after you updated your firmware also?
Anybody have any ideas?
Hi , do you seller on swappa as linkz? I’m interested in buying any MacBooks you get in if you would like to deal direct on PayPal let me know . My email is [email protected]