what I found is upon menu boot up the android robot falls and reports "No Command" and flashes "Error". Then when selecting wipe cache partition, the robot falls and reports "Error" then automatically reboots. its MF3 ...
also it losing signal sometimes....this phone is brand new out of the box..... all what i did rooted it with AR.apk for few days and then unrooted it with SUsuper unroot option. so i tried to do wipe after that, and found out my issue ....i did four time factory reset but i still feel the phone laggy, especially when i open the browser sometimes take a minute to load the page or gives me "page cannot display" so i have to refresh the page every time...
BTW i have a good signal 4G LTE and have no issue with my other phone HTC one
salwansk said:
what I found is upon menu boot up the android robot falls and reports "No Command" and flashes "Error". Then when selecting wipe cache partition, the robot falls and reports "Error" then automatically reboots. its MF3 ...
also it losing signal sometimes....this phone is brand new out of the box..... all what i did rooted it with AR.apk for few days and then unrooted it with SUsuper unroot option. so i tried to do wipe after that, and found out my issue ....i did four time factory reset but i still feel the phone laggy, especially when i open the browser sometimes take a minute to load the page or gives me "page cannot display" so i have to refresh the page every time...
BTW i have a good signal 4G LTE and have no issue with my other phone HTC one
Click to expand...
Click to collapse
Did you ever resolve this?
Related
Hi,
I am running CM 4.0.4 and it has been working great. For the past week or so i have been experiencing connection dropping. Every now and again, increasingly, i have been getting connection errors.
I am using the market, browsing and downloading some apps or on the web, then all of a sudden, it says connection error. I have tried using the browser and other apps that use the internet, and they time out. I then tried calling a number, it showed the usual grey dialling image, then after a few seconds it goes red and days call ended. it never gets to green.
The really odd thing is that i have full signal and the 3g logo is shown. Also the 3g up arrow flashes white but the down arrow stays grey.
has anyone else been having this problem? is it a software thing that can be fixed by wiping or is it a hardware problem and i need to contact T-Mobile? Also, if i do wipe, is it safe to restore from backup or could the error be in the backup too?
Chris
Is noone having these issues?
reflash the radio, if that doesn't help, make a back up, wipe, reflash rom, and see if that fixed it, if not, wipe, flash another rom entirely, and see, if that doesn't unroot your phone, then see if it does it with stock, if it is still happening with stock call t-mobile
Help!
I upgraded to froyo via Kies then all hell broke loose.
On first reboot after installation..a "new user menu" comes up asking for the user's preferences, once that pops up I start getting the following force close loops one after the other, force close one...another pops up:
The application logs provider
Gmail something
Media something
And keeps going on and on.
Decided to do a factory reset, since everything is backed up by google, did 3br clicked on factory reset...phone gets into "Downloading, do not turn off targett!!!" screen....I let it sit there for 30 minutes, no action. So disconnected the battery.
Booted normally, same issue as above.
Then decided 3br, and the "downloading" screen immediately came up after reboot without giving me the options of recovery mode.
So now, my phone boots into two forms only, and gets stuck there:
1. force close loop on user data entry page
2. with 3br, phone gets stuck on "Downloading' screen.
Any solutions for a non-developer like me?
FYI, running ryanZa one-lick lagfix. So phone is rooted.
Help...really need my phone back
Its easy!!! go to app manager and clear data!
Did you undo lagfix before updating ??.
jje
I've never seen this issue before, and now I've run into it twice since updating to Kit Kat, rooting, and setting up my VZ Moto X.
Honestly, I don't have much info to share. I had just gotten done setting up my phone. Froze some VZ apps (this might be it, maybe) though nothing crazy..Navigator for one, then rebooted. No problems.
Did some more updating, installed Delayed Lock and GSAM Battery monitor (which is broken in 4.4 for now, I know) and rebooted again. One final time before I planned to do a full backup of all apps using Titanium.
It boots up fine, boot animations (both Moto globe and VZ logo) and then goes black. Now it's sitting on my desk, screen flashing every 15 seconds or so. The time is accurate and updating. Battery icon comes and goes, but it's not dead. Network shows no bars. It's basically just the status bar and the bottom nav icons. Adb isn't recognized, though it does show up under fastboot.
The worst part is that this happened to me last night. I was at the Pats game. Battery was running low and I was trying to record the last play of the game. Battery ran out and the phone shut down. I tried to start it back up and it died on me again. After getting home and charging it to full, it did what I described above.
I really hope it's not time to do a full reset via fastboot as that's what I had to do this morning. Any ideas? I tried clearing cache via fastboot too. No luck. Anyone ever see this before?
******EDIT******
I've discovered what causes this issue, for me at least. It is the combination of "improper" shutdown methods in use by some apps (Titanium Backup, Quick Reboot, SafeStrap, and others I'm sure) and the use of Delayed Lock. Basically, Delayed Lock takes control of certain system files in order to disable the pin/password/pattern lock. If the system shuts down correctly, it hands control back to system. If the phone doesn't hand over control (the phone cuts out without proper notification due to the battery dying or caused by the way an app handles rebooting), the phone hangs up on the next boot. I made a video and uploaded it here.
http://youtu.be/CRtmUAv3PLk
Also of note, rebooting using the Advanced Power Menu option within Gravitybox (the Xposed Framework module) works just fine. All of the options except for "Soft Reboot".
See more in the Delayed Lock support thread (starting at post 654):
http://forum.xda-developers.com/showthread.php?t=955092&page=66
mercado79 said:
I've never seen this issue before, and now I've run into it twice since updating to Kit Kat, rooting, and setting up my VZ Moto X.
Honestly, I don't have much info to share. I had just gotten done setting up my phone. Froze some VZ apps (this might be it, maybe) though nothing crazy..Navigator for one, then rebooted. No problems.
Did some more updating, installed Delayed Lock and GSAM Battery monitor (which is broken in 4.4 for now, I know) and rebooted again. One final time before I planned to do a full backup of all apps using Titanium.
It boots up fine, boot animations (both Moto globe and VZ logo) and then goes black. Now it's sitting on my desk, screen flashing every 15 seconds or so. The time is accurate and updating. Battery icon comes and goes, but it's not dead. Network shows no bars. It's basically just the status bar and the bottom nav icons. Adb isn't recognized, though it does show up under fastboot.
The worst part is that this happened to me last night. I was at the Pats game. Battery was running low and I was trying to record the last play of the game. Battery ran out and the phone shut down. I tried to start it back up and it died on me again. After getting home and charging it to full, it did what I described above.
I really hope it's not time to do a full reset via fastboot as that's what I had to do this morning. Any ideas? I tried clearing cache via fastboot too. No luck. Anyone ever see this before?
Click to expand...
Click to collapse
Bad system file, you may want to rsdlite and yes userdata needs to be erased. Moto is finicky, I've never had any other device soft brick on me, never. 3 times now with the moto 2 after flashing a ROM, 1 from restoring a nandroid
Sent on my Moto X
flashallthetime said:
Bad system file, you may want to rsdlite and yes userdata needs to be erased. Moto is finicky, I've never had any other device soft brick on me, never. 3 times now with the moto 2 after flashing a ROM, 1 from restoring a nandroid
Sent on my Moto X
Click to expand...
Click to collapse
i figured you'd say that. i'm just trying to figure out how to stop this from happening again. so unbelievably inconvenient.
Added some more info to the OP about what turned out to be the cause.
Noticed my Moto x was feeling kind if laggy all day so I went to wipe the cache. After about 15 minutes of sitting there with "wiping cache" on the screen with the little bars animating I finally reset it with the power button. I've never had it take this long before.
Now if I go back in and try it again it doesn't even say "wiping cache" it just had the Android guy and the little animated bars, and it never progresses.
Any ideas? Phone is still kind of laggy.
This is one of the weirdest problems I've had. I'll try to be very specific. I'm running Android 6.0 on a Moto G 2014. I was just using my phone, on YouTube, when it decides to randomly reboot. Ok, just an error. Then I noticed that my phone's lockscreen never shows up anymore, and I can't pull down the quick settings. I thought it was just an error from the unexpected reboot it had, so I do a full reboot. No change. Okay, maybe clearing cache and dalvik will solve this. Cleared, reboot, Android is Upgrading, and no change. Okay, now I'm worried. So I restore a system backup from a month ago, reboot, and no change. I also tried uninstalling xposed framework, and no change. Now I don't know what else there is to do before factory resetting, because I really don't want to do that. By the way, here's all of the problems I've noticed since that reboot:
Can't pull down notifications.
Lockscreen will not show up at all.
Home button does not work at all, pressing it does nothing. I have to press back if I want to get to the homescreen.
"Developer options are not available for this user" error screen, even though I'm the only user
adb won't respond (probably for the reason above)
I get no notifications at all
I can't receive calls
Any tips or steps I should take to find this problem? Any help is appreciated.
Solved
Restoring System, Data, and Boot from early June took the problem away. But it bothers me that I'll never know what the problem was.