Okey dokey, my phone is making my brain hurt. three days ago, my phone was going haywire. I was rooted with UNL3ASH3D 1.4 and RedNinja theme, working well. All of a sudden everything Force Closes. I was getting so many FC's I could put the FCC out of business. When I would unlock my screen, my launcher wouldn't load and the only thing I could do is get Advanced Task Killer to open from the Status Bar. Everything kept popping up Force Closing, Android system, google framework, Moto services. So I decided to FXZ back to stock. While it was on step 14/15 I decided to let it run its course and I stepped outside. Windows decides to restart itself in the middle of re-programming and drained my battery dead so I couldn't fix it. Last night I went and bought the battery dock + extra battery from the VZW store. Charged up the battery all the way, popped that baby in my Bionic and FXZ'd my way to glory. Or I thought so at least. My phone gets done, reboots, and even loads up my old wallpaper so it had to have some kind of connection or something. You know, you can see the wallpaper from the lock screen. Ok remember, my phone is fully back to Factory Settings now. I unlock the screen and what happens? FC FC FC FC FC FC. Everything starts Force Closing again. So someone tell me, would I be right in assuming this is a problem with the phone? Do you guys think I would be able to turn it in and file a warranty claim? Am I just the devil himself to all Android phones? I don't know. I'm starting to think that maybe I should buy a prepaid Net10 phone with a graphics processor from the 80s.
lemonoid said:
Okey dokey, my phone is making my brain hurt. three days ago, my phone was going haywire. I was rooted with UNL3ASH3D 1.4 and RedNinja theme, working well. All of a sudden everything Force Closes. I was getting so many FC's I could put the FCC out of business. When I would unlock my screen, my launcher wouldn't load and the only thing I could do is get Advanced Task Killer to open from the Status Bar. Everything kept popping up Force Closing, Android system, google framework, Moto services. So I decided to FXZ back to stock. While it was on step 14/15 I decided to let it run its course and I stepped outside. Windows decides to restart itself in the middle of re-programming and drained my battery dead so I couldn't fix it. Last night I went and bought the battery dock + extra battery from the VZW store. Charged up the battery all the way, popped that baby in my Bionic and FXZ'd my way to glory. Or I thought so at least. My phone gets done, reboots, and even loads up my old wallpaper so it had to have some kind of connection or something. You know, you can see the wallpaper from the lock screen. Ok remember, my phone is fully back to Factory Settings now. I unlock the screen and what happens? FC FC FC FC FC FC. Everything starts Force Closing again. So someone tell me, would I be right in assuming this is a problem with the phone? Do you guys think I would be able to turn it in and file a warranty claim? Am I just the devil himself to all Android phones? I don't know. I'm starting to think that maybe I should buy a prepaid Net10 phone with a graphics processor from the 80s.
Click to expand...
Click to collapse
after the FXZ did you do a factory reset or did you just reboot?
Just reboot. That's what I've always done, I've FXZ'd it three times. I don't even know how to do a factory reset after I FXZ it.
lemonoid said:
Okey dokey, my phone is making my brain hurt. three days ago, my phone was going haywire. I was rooted with UNL3ASH3D 1.4 and RedNinja theme, working well. All of a sudden everything Force Closes. I was getting so many FC's I could put the FCC out of business. When I would unlock my screen, my launcher wouldn't load and the only thing I could do is get Advanced Task Killer to open from the Status Bar. Everything kept popping up Force Closing, Android system, google framework, Moto services. So I decided to FXZ back to stock. While it was on step 14/15 I decided to let it run its course and I stepped outside. Windows decides to restart itself in the middle of re-programming and drained my battery dead so I couldn't fix it. Last night I went and bought the battery dock + extra battery from the VZW store. Charged up the battery all the way, popped that baby in my Bionic and FXZ'd my way to glory. Or I thought so at least. My phone gets done, reboots, and even loads up my old wallpaper so it had to have some kind of connection or something. You know, you can see the wallpaper from the lock screen. Ok remember, my phone is fully back to Factory Settings now. I unlock the screen and what happens? FC FC FC FC FC FC. Everything starts Force Closing again. So someone tell me, would I be right in assuming this is a problem with the phone? Do you guys think I would be able to turn it in and file a warranty claim? Am I just the devil himself to all Android phones? I don't know. I'm starting to think that maybe I should buy a prepaid Net10 phone with a graphics processor from the 80s.
Click to expand...
Click to collapse
I would probably do the FXZ one more time and if the problem persists, then I think you know it's a hardware issue - warranty at that point.
Good luck and let us know how it turns out.
lemonoid said:
Just reboot. That's what I've always done, I've FXZ'd it three times. I don't even know how to do a factory reset after I FXZ it.
Click to expand...
Click to collapse
Do a fxz and then boot into recovery and do a factory reset. Then report back! good luck!
Fyi a fxz doesn't wipe data like previous sbfs from Droid x and other moto phones
Sent from my DROID BIONIC using XDA Premium App
^^^Everything they said.
Also, stop using Advanced Task Killer.
mistawolfe said:
Also, stop using Advanced Task Killer.
Click to expand...
Click to collapse
Yeah, task killers are the devil for root users.
Yeah I usually have ATK disabled, but last time I did my Titanium Restore I forgot that it was in one of my profiles, I was doing some mods/tweaks to some apps and that was in my tweaker profile. But anyways on to the issue at hand, I did go into recovery and do a factory reset and it fixed it. I didn't FXZ again, I figured if a factory reset should do the trick, and it did since I had already FXZd.
lemonoid said:
Yeah I usually have ATK disabled, but last time I did my Titanium Restore I forgot that it was in one of my profiles, I was doing some mods/tweaks to some apps and that was in my tweaker profile. But anyways on to the issue at hand, I did go into recovery and do a factory reset and it fixed it. I didn't FXZ again, I figured if a factory reset should do the trick, and it did since I had already FXZd.
Click to expand...
Click to collapse
I would just uninstall it and never use it again. ATK that is...
Sent from my DROID BIONIC using xda premium
I would just like to commend you for not immediately going to Verizon for a warranty replacement. It is people who replace before researching the cause of their problems that cause us to be presented with these phones with locked bootloaders. So, again, kudos on asking questions and figuring it out without replacing the phone. If only everyone would follow suit.
Sent from my DROID BIONIC using xda premium
I can't stand not being able to fix something that is broken, especially when i broke it and even more so when its an Android device. People who take the easy way out just show me that they don't like to learn. ever since my Eris i have been trying to fit in time to learning more about Android, programming and software development. Warranty replacement would void my commitment to learning. So thanks for the kudos bro. Just wish that more people got enjoyment from learning.
Sent from my DROID BIONIC using xda premium
lemonoid said:
I can't stand not being able to fix something that is broken, especially when i broke it and even more so when its an Android device. People who take the easy way out just show me that they don't like to learn. ever since my Eris i have been trying to fit in time to learning more about Android, programming and software development. Warranty replacement would void my commitment to learning. So thanks for the kudos bro. Just wish that more people got enjoyment from learning.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
THIS... omfg this is exactly how I feel. :-D
Related
However ironic the title may be, I updated my fiance's non-rooted N1 to the official release froyo and from the very beginning, it will work for a few seconds, then it will just freeze for a few minutes. I have patiently gone through and stopped almost every process, and nothing will fix it. It still just freezes constantly and usually requires a battery pull to get it to work at all. I told her she could try a factory reset, but she would rather just go back to 2.1-update1. I'm going to try renaming 22607-ERD79-update-nexusone-stock-signed.zip (or PASSIMG_Passion_Google_WWE_1.01.1700.1_ERD79_release_signed.zip) to update.zip and reflashing it in the stock bootloader on her phone, but I feel like that won't work because it is a previous version and not really an update. Does anyone have any advice on how to just bring her back, or perhaps how to fix her freezing problems on froyo?
Thanks
Try a fresh flash with no apps installed and see how its doing.... if it doesn't freeze then its a app probably ...
I'd like to try that, but she doesn't want to do a fresh install. I'd imagine that if an app didn't freeze 2.1, it wouldn't freeze 2.2. Besides, 2.2 freezes even after killing all applications and services.
I guess I'm really looking for advice on getting it back to 2.1 without rooting her phone.
dnoggle said:
I'd like to try that, but she doesn't want to do a fresh install. I'd imagine that if an app didn't freeze 2.1, it wouldn't freeze 2.2. Besides, 2.2 freezes even after killing all applications and services.
I guess I'm really looking for advice on getting it back to 2.1 without rooting her phone.
Click to expand...
Click to collapse
Just do a factory reset in settings and security ... no reflash. Just cause a app didn't freeze 2?1 doesn't mean it wont freeze 2.2. And even if the apps currently not running or closed, it'll still wack ya phone. I had a freeze every hour yesterday with my chosen apps installed, flashed 3 different times to no avail. Now I factory reset with only 4 definitely needed apps installed and haven't gotten a freeze yet. So my conclusion is 2.2 doesn't like something I've installed so I'm adding a few apps every hour to fins the cause.
Since I factory reset with my few apps. I haven't had a freeze yet all night and morning long..
I'm having the same issue too. Not sure what is going on with FRF91, but my phone keeps freezing and I need to pull the battery to get it to respond again. I agree it very well could be an application, but installing every application one by one and testing would be a pain. Is there a better way to figure out what is causing the phone to lock up? Any time of log on the phone that would be helpful?
Papa_I said:
I'm having the same issue too. Not sure what is going on with FRF91, but my phone keeps freezing and I need to pull the battery to get it to respond again. I agree it very well could be an application, but installing every application one by one and testing would be a pain. Is there a better way to figure out what is causing the phone to lock up? Any time of log on the phone that would be helpful?
Click to expand...
Click to collapse
Have you tried a factory reset? That might fix it... let us know what you find. I've noticed a couple of freezes as well, but I'm not able to factory reset it just yet because I'm out of town and don't want my phone down for even half an hour.
I have to pull battery a couple of times a day.
I'm having the same issue on 2.2. I have done 2 factory resets. Nothing. N1 call center said slowly reinstall all apps to see if an app may be doing it. No luck.
Is anyone having issues with the screen still being responsive while on a call? My screen will go black but you cant still hit keys when you have up against your face.
I'm betting that you do not have a custom recovery and nandroid backup, or you wouldn't be asking.
I highly doubt that the phone will let you push the old firmware on top of the new one if you don't have a hacked recovery and a test-signed zip. But I don't know - you could try it...
Here is what I would do:
1. Install a custom recovery (like Amon-Ra 1.7.0.1), either by unlocking the bootloader, or by following the directions in the dev forum for doing this without unlocking if you have the fear. If you already a custom recovery, don't worry about this step.
2. Now boot into recovery and make a nand backup!
3. Now go ahead and try this one of two ways - either delete one application at a time until you figure out which one is killing you, OR do a factory reset and then re-add one application or a small number at a time until you figure out what is crashing you.
If it were me, with my 100 applications, I'd probably add 5 or 10 at a time. Once you get crashes after one group, try removing those applications one at a time until the crashes stop. The last removed app when the crashes stop should be the answer.
Of course, since you'll have to have adb running to get a nandroid, you could also just take a logcat of the running, crashing phone and see what app is killing it there.
I did a factory reset today and will report back letting everyone know if that has fixed the issue. Everyone else that is experiencing the freezing issue, did you have Beautiful Widgets installed?
I have that installed, is that whats cousing it?
Beautiful Widgets was killing my N1, too. Freezes, sluggishness, etc. I uninstalled and wiped my cache via stock recovery. No problems since.
I'm on stock FRF91 BTW.
Sent from my Nexus One using XDA App
It appears that's the root of my issue. I would uninstall the application and clear the cache and see if that helps. Report back with your findings.
Sent from my Nexus One using XDA App
Is there a way to reset the phone, much like the Clear Storage command on WinMo, that will restore the ROM back to how it was on day 1? The phone worked fine for the first 3 weeks I had it. Then I rooted it, deleted the bloat, installed OCLF and SGS Tools and some other mods about 2 weeks ago. Had my first of 3 unexplained shutdowns since then. One day this week the phone went berserk. Everything started causing lockups and crashes. Phone calls, incoming and outgoing, would lock the screen to where I had to pull the battery. Programs started force closing for no reason. Over the period of 3 hours the phone was almost unusable. I started uninstalling recent programs thinking one might be the culprit. The phone settled down for a few days, then last night it started acting up again. Screen freezes where I can't do anything, but I can bring up the Home screen with the left hard key. Still have to pull the battery, though.
I want to go back to how the phone was before I did anything to it, but I don;t want to do an Odin or flash a stock ROM. This was easy on WinMo, you just ran Clear Storage and you were back to the day it was new.
only way to completely reset everything and fix it is odin back to stock. its real easy http://forum.xda-developers.com/showthread.php?t=731989
Or once back to stock: *2767*3855#
Xstop said:
Or once back to stock: *2767*3855#
Click to expand...
Click to collapse
Could you explain this? I am on a stock ROM, just rooted.
Miami_Son said:
Could you explain this? I am on a stock ROM, just rooted.
Click to expand...
Click to collapse
It well just delete all memory but will not remove root or restore the bloatware
Sent from my SGH-I897 using XDA App
We do not have the feature you're looking for in our Captivates. Looks like you might have to bite the bullet and flash.
norcal einstein said:
We do not have the feature you're looking for in our Captivates.
Click to expand...
Click to collapse
I gotta tell you, I'm finding this same answer to a lot of what's missing from Android, but was present in WinMo.
My first day with the Droid bionic... it's my first non-Samsung Android phone, so I'm not sure what to think.
In the midst of trying to figure it out and get it all setup (rooted, Titanium Backup restore, apps only), and my data drops out. Apparently for good.
I had solid 4G data when I first opened up the phone this afternoon. I ran some speed tests and switched to WiFi. I left the house a bit later and realized I couldn't open a webpage. I noticed the WiFi was still on, so I shut it off, but the cellular data never came back.
Tried putting it in airplane mode and back, rebooted (several times), tried the data toggle on the power control widget, I even forced the phone into CDMA only mode (and back).
I'm stumped. Has anyone else seen this? Is there any kind of possibility that restoring apps or rooting could have anything to do with it? I have not seen this problem over many a ROM on the Vibrant, and then the Droid Charge. I even loaded a GB ROM on the Charge and restored all my apps without issue.
Any help would be appreciated. I'd really not like to have to wipe the phone and start over.
I had something similar happen although I'm not rooted yet. For 3 days I was golden. Then I installed switchpro widget to see how the 3G/4G toggle worked with the Bionic and it made my mobile connectivity wonky. I uninstalled it. It still is wonky today.
LTE is there then goes away a reboot corrects it until it goes away. 3G is exactly the same. Turn on WIFI and the LTE disappears. It's supposed to stay up just turn white like it did for 3 days prior to installing then uninstalling switchpro. It could just be coincidence with the switchpro thing idk. I'm not all that knowledgeable with APN's, but after some research somehow I believe mine got mixed up via switchpro. Getting a new Bionic tomorrow.
Well, no data at all. If I'm outof wifi area, I have no data access. Only phone calls and text.
Sent from my Android using Tapatalk
Flapjack said:
Well, no data at all. If I'm outof wifi area, I have no data access. Only phone calls and text.
Sent from my Android using Tapatalk
Click to expand...
Click to collapse
I'd get another one then. Or if you don't want to do that get a different brand
I think I'll just try a hard reset. I'm sure it was something I did with Titanium backup... I'll just have to figure out what.
Or you could try a factory reset to see if that solves it
EDIT: I see you thought of that 1st
Something similar happened to me. The only way I could fix it was by restarting the phone until the data crashed again. I solved this problem (or I think I did, still testing it) by removing all my widgets. I have a strong suspicion it was a widget doing this (specifically the AIX weather widget, but I am not sure yet).
So, I suggest that you remove all of your widgets and restart your phone and see what happens.
The hard reset did the trick. I think maybe it was me restoring the [SMS/.../APN] setting (can't remember the middle setting) in TB. I didn't do it this time and all seems well. It was green, so I thought 'why not'.
I'll see how it goes from here on out.
I'm thinking its got to be something related to wifi. every time I disconnect from wifi I can't connect to data unless I reset my phone.
Sent from my DROID BIONIC using XDA App
Flapjack said:
The hard reset did the trick. I think maybe it was me restoring the [SMS/.../APN] setting (can't remember the middle setting) in TB. I didn't do it this time and all seems well. It was green, so I thought 'why not'.
I'll see how it goes from here on out.
Click to expand...
Click to collapse
Glad to hear that. Factory reset did not fix it for me. Will have a new tomorrow
I am also having this problem. If Motorola still used vanilla android this wouldn't be an issue. I hate when manufacturers feel it necessary to fix something that isn't broke. I am sad to see how many people are experiencing this problem because if it was isolated to my phone and a few others then a warranty replacement would do the trick. I now feel like I wasted 380 on phone and accessories. I placed a call to Verizon tech support and their as clueless as usual. I hope an update is released soon that fixes this issue (or a custom rom). I remain hopeful that we start seeing good things on our Motorola devices now that google owns moto.
NOTE: I wish people would start reading through existing threads before starting new ones. I started a thread to this effect back on day 3. Several others have started threads to this effect as well. I think there are now 4 or 5 on this very same subject.
Sent from my DROID BIONIC using xda premium
hey everyone!
my phone went a little crazy by randomly shutting off while using cm10 so I decided to restore to a stock non-root nandroid I made around 8 months ago. Everything went well up until the point I rebooted: I unwittingly had set up a text lockscreen password that I had since then forgotten (who remembers passwords from 8 months ago?!). So I went in CWM, did a factory data reset and rebooted. I turned off the screen and turned it back on to BAM! the lockscreen again... And the fracked up thing is that there isnt even a "forgot password" gmail confirmation option thing at the bottom so I'm completely locked out of my phone! Is there anything I can do other than buy that $4 screen lock bypass exploitation app??
Any help would be greatly appreciated!
h2whoa said:
hey everyone!
my phone went a little crazy by randomly shutting off while using cm10 so I decided to restore to a stock non-root nandroid I made around 8 months ago. Everything went well up until the point I rebooted: I unwittingly had set up a text lockscreen password that I had since then forgotten (who remembers passwords from 8 months ago?!). So I went in CWM, did a factory data reset and rebooted. I turned off the screen and turned it back on to BAM! the lockscreen again... And the fracked up thing is that there isnt even a "forgot password" gmail confirmation option thing at the bottom so I'm completely locked out of my phone! Is there anything I can do other than buy that $4 screen lock bypass exploitation app??
Any help would be greatly appreciated!
Click to expand...
Click to collapse
Maybe try another factory reset (sucks I know) and this time after boot go into security settings and turn off the screen lock before your screen turns off. If you just try and change the password you'll be prompted for the old one first. That being said, I haven't used stock in so long I can't promise this will work either.
Those random reboots you got with CM10 were common with older versions and the other variants such as Pacman, Slimbean, etc, but the latest one I haven't had that happen and I've been using it a week. I only say this because stock is just makes this phone crawl IMO.
ArtfulDodger said:
Maybe try another factory reset (sucks I know) and this time after boot go into security settings and turn off the screen lock before your screen turns off. If you just try and change the password you'll be prompted for the old one first. That being said, I haven't used stock in so long I can't promise this will work either.
Those random reboots you got with CM10 were common with older versions and the other variants such as Pacman, Slimbean, etc, but the latest one I haven't had that happen and I've been using it a week. I only say this because stock is just makes this phone crawl IMO.
Click to expand...
Click to collapse
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.
h2whoa said:
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.
Click to expand...
Click to collapse
If you're rooted you can remove gesture.key using adb shell but I forget where exactly it is. Google it
Sent from my Nexus 7 using xda app-developers app
h2whoa said:
Haha, thanks, not an absolute fix but at least it works. Kinda strange since I read that CWM factory resets wipes out everything including lockscreen passes... And my phone wasn't rebooting, it would just shut off randomly, battery would drain at horrifying speeds (from 99% to 0 after a 7 minute phone call) (I also had the latest ver). I was thinking that I could maybe restore stock rom and send it back to samsung or provider since its still under warranty
EDIT: I'm gonna try Samsung Remote Screen Unlock and see if that works. Plus I just checked my battery: It's as swollen as Rosie O'donnell at Mandarin, which explains the crappy battery life.
Click to expand...
Click to collapse
Hate to hear that and you're not the only one to mention swollen batteries around here lately either. Good luck to you!
theAPANT said:
If you're rooted you can remove gesture.key using adb shell but I forget where exactly it is. Google it
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
yeah... can't root, need this phone to be as stock as can be if I'm to get it replaced (or at least the battery). Btw, Is there a way to possibly remove CWM in case they check recovery?
PS: Totally irrelevant but I keep reading about a CM10.1 rom for this phone; I've searched far and wide but I can't seem to find it! Could anybody point me in the right direction?
h2whoa said:
yeah... can't root, need this phone to be as stock as can be if I'm to get it replaced (or at least the battery). Btw, Is there a way to possibly remove CWM in case they check recovery?
PS: Totally irrelevant but I keep reading about a CM10.1 rom for this phone; I've searched far and wide but I can't seem to find it! Could anybody point me in the right direction?
Click to expand...
Click to collapse
Yes the easiest way to get rid of cwm is to flash the stock file. Go to http://forum.xda-developers.com/wiki/Samsung_Galaxy_Exhibit_4G there are, i believe two methods, one using Odin the other flashing something in recovery. Just read. As for cm10.1 camcory is working on it so is smartguy. Even i compiled it but it doesn't boot all the way. Check insomniaforums.org that is probably where it will be posted
Sent from my Nexus 7 using xda app-developers app
CM10.1 boots fine and runs smooth but not yet ready for release. There is a few broken items in it I believe if I recall but cannot restore it due to limited battery till I get home to verify what was wrong. Be patient and when ready public will know about it.
Sent from my SGH-T679 using xda premium
afwolfpacked said:
CM10.1 boots fine and runs smooth but not yet ready for release. There is a few broken items in it I believe if I recall but cannot restore it due to limited battery till I get home to verify what was wrong. Be patient and when ready public will know about it.
Sent from my SGH-T679 using xda premium
Click to expand...
Click to collapse
Bluetooth and camera dont work. I'm saying my own personal build doesn't boot yet but I'm trying some stuff. Right now I'm working on aokp 4.1.2 to get that fixed all the way, mainly because i like aokp and I'm stuck on 4.2.2
Sent from my Nexus 7 using xda app-developers app
Anybody else having these problems? 2nd day to have it and it would freeze up and bootloop. At one point it was off for 2-3 hours and I couldn't get to fastboot. Finally I got it to factory reset twice and its doing fine for now. Unfortunately I'm on shift for 24 hours or I'd make Verizon give me a new one.
Sent from my XT1254 using XDA Free mobile app
Aarongauntt said:
Anybody else having these problems? 2nd day to have it and it would freeze up and bootloop. At one point it was off for 2-3 hours and I couldn't get to fastboot. Finally I got it to factory reset twice and its doing fine for now. Unfortunately I'm on shift for 24 hours or I'd make Verizon give me a new one.
Sent from my XT1254 using XDA Free mobile app
Click to expand...
Click to collapse
Could it be some app that you installed? Haven't had any problems myself with it.
Have you switched from dalvik to art?
I've had zero issues with bootloops so far.
Haven't switched to art and I doubt any nonroot app would cause bootloops. Who knows.
Sent from my XT1254 using XDA Free mobile app
No issues so far here
none here
Had one this morning. Phone froze during a phone call, and then got stuck at the boot screen before the animation. Rebooted it by holding the volume and power button and it's worked since.
No problems here, have played games for several hours straight with no issues and have been playing with it all day.
Mine was solid for about 4 hours and its starting back up again. Maybe I have a lemon.
Sent from my XT1254 using XDA Free mobile app
sounds like a defective unit or something.
i'd do a wipe, dont install any apps, see if it works fine or not. if it does, probably an app issiue. if you are getting problems even after the reset, its the phone.
Same issue here. Kept randomly rebooting, but only occasionally. Did a few factory resets, installing only essential apps each time thinking it was one of my apps that didn't play nice with Turbo (even though they played just fine with my Razr Maxx and Galaxy S5) to no avail. Last night, did a factory reset, didn't install any apps (nor did I update any of the pre-installed ones) and this morning, endless bootloop. I can't get it to stop. I'm really starting to hate this startup sound. LOL!
My phone locks up occasionally. Always restarts itself. I'm not sure what has been causing my phone to lock up but I haven't been able to pinpoint an action that is specifically creating the issue.
Sent from my XT1254
So I couldn't figure out a way to just power it down (all the usual button combinations just kept rebooting it, which then continued the bootloop) so I just figured I'd let it bootloop until the battery ran out. After about 3 hours of bootlooping, it just finally booted. I didn't touch anything. Weird. Maybe it's like a 4 year old temper tantrum, just let them get it out of their system and all will be better in a couple hours. Hahaha!
I have a phone that it's going this as well. I can get into recovery and reset but that didn't work. If I try to wipe cache the phone reboots and freezes which seems abnormal. I never had a phone reboot after wiping cache. I loaded the phone into fastboot and using RSD Lite I flashed the original software into the phone to no help. I did notice though that in the fastboot option that my baseband is blank. Might just be a bad device.? Does anyone know where I can find stock firmware 21.44 (that has the VoLTE option)?
I've had 4 turbos, latest one with almost no apps, and been waiting on Motorola for near 3 weeks for another device... Just about to sell the next turbo they send out... I've also had the same issues plus WiFi drops BT drops freezing lagging, and lately unable to receive voice calls and voice mail
polish23 said:
I've had 4 turbos, latest one with almost no apps, and been waiting on Motorola for near 3 weeks for another device... Just about to sell the next turbo they send out... I've also had the same issues plus WiFi drops BT drops freezing lagging, and lately unable to receive voice calls and voice mail
Click to expand...
Click to collapse
With four turbos there seems to be more of a user error than system. you either disabled a needed apk, installed an apk that doesn't play nice, or you took an ota and havent completed an FDR. Its recommended and has been posted on here multiple times throughout this site/forum that always, always do a FDR with an update.
the_rooter said:
With four turbos there seems to be more of a user error than system. you either disabled a needed apk, installed an apk that doesn't play nice, or you took an ota and havent completed an FDR. Its recommended and has been posted on here multiple times throughout this site/forum that always, always do a FDR with an update.
Click to expand...
Click to collapse
I'm not running any additional apks at this point and haven't since the second replacement device. Apparently, I just have good luck with this phone, that I now despise, and wish I could get rid of. I followed all the disable guides for what was safe, and I'm not sure what an FDR is, but if you tell me I'll give it a shot. Last replacement came updated as well. At this point this current model doesn't even receive phone calls, because it just doesn't work correctly.
polish23 said:
I'm not running any additional apks at this point and haven't since the second replacement device. Apparently, I just have good luck with this phone, that I now despise, and wish I could get rid of. I followed all the disable guides for what was safe, and I'm not sure what an FDR is, but if you tell me I'll give it a shot. Last replacement came updated as well. At this point this current model doesn't even receive phone calls, because it just doesn't work correctly.
Click to expand...
Click to collapse
Factory Data Reset.
the_rooter said:
With four turbos there seems to be more of a user error than system. you either disabled a needed apk, installed an apk that doesn't play nice, or you took an ota and havent completed an FDR. Its recommended and has been posted on here multiple times throughout this site/forum that always, always do a FDR with an update.
Click to expand...
Click to collapse
the_rooter said:
Factory Data Reset.
Click to expand...
Click to collapse
OK, so I have done that with each of the devices. Unfortunately, I just have horrible issues/luck with this phone.