[Q] How do I do a system reset? Does it remove root? - X 2014 Q&A, Help & Troubleshooting

Recently I had some problems with my phone (how you can see in the hid content) and I was instructed to do a system reset as the only way to solve it.
I'm kind of layman, so... can someone help me? Tks.
My device is the Moto X 2014 (XT1097). It is rooted but I didn't install any custom ROM.
Copied and pasted from my post on Reddit:
I uninstalled some apps trough the Titanium Backup (Downloads Manager, Downloads, E-mail, Google Chrome and Talkback). Luckily I had a backup of it, I restored it and restarted the phone. After it, every time I open the gallery or the Play Store the warning "android.process.media has stopped" pops up... actually, it pops up all the time, I barely can use my phone. Can someone help me?
My device is the Moto X 2014 (XT1097). It is rooted but I didn't install any custom ROM.
EDIT: I've just disabled the "auto-sync" option and the warning has stopped but I really want to find a solution that lets me auto-sync my apps. Please, help.
EDIT²: Ok. The warning is back.

If system files are missing or damaged, a factory reset won't help. You would need to reflash the system image. Otherwise, a factory reset could fix it if data things are messed up.

Related

[help] Dialer/phone force closes

Rooted (stock) VZW moto x
A couple days ago my phone app started force closing immediately upon opening it every time. It doesn't work at all now. I am rooted, but I rooted weeks ago and this just started yesterday or the day before. I haven't messed with anything. The only thing that I have done is download apps from the play store... None of which 'should' mess with the phone app.
I have since downloaded an alternative dialer app which works, but I'd rather use stock. I tried rebooting, tried clearing the app's cache and data (in system settings - apps) and no luck.
Any help would be great. Either finding/fixing the issue or a way to reinstall the stock phone app? I am rooted and I believe write protection is off, which I had to do to install busybox. Thanks!
__
What version are you on. 4.2.2 or 4.4
There is a couple things i would try i have had to do it with other phone specially my old S3
1. restore from a backup when i the dialer was not FC
2. try reinstalling the dialer from the APK located here device/system/prvi-app/dialer.apk
3. pull the dialer.apk out of the correct stock ROM or recover img and replace the one located in the above folder and install it.
but to be honest option one is normally the best way to go and the fastest.
Thanks. I'm on 4.4. I'm going to try option 2 when i get home. I'm not exactly sure how to restore a backup on this phone yet being that i dont really have a recovery.
Edit: option 2 installed ok, but still force closes
let me get you the .apk from the restore img give me about a hour to download it and get you a link
also do you know how to use titanium backup if so i would install it and back up all user apps and data because you might have to do a factory reset. but if you backup with TB you and restore everything right back to ware you was

[Q] com.android.phone crashing

In advance: I may be a idiot.
I received my LG L90 D410hn yesterday and was happily fooling around. Summing up, all I'd done was:
instaling LG OTA update
successfuly rooting it (towel)
installing greenify pro/donation edition
installing Classic Messaging
Installing Google Launcher (sideloading apk)
Greenifying the bloatware described all along this thread
Eveything was running smooth and crisp, but the dialer design really got to my nerves. So I decided to try to install my LG Optimus 2X custom rom's dialer (The ROM) because that is NEAT.
I backed up my original Phone apk and other related apps with ES File Explorer just in case and uploaded the apks to my Dropbox.
Then I proceeded to uninstall the Phone app. The try was rewarded with a "unsuccesful" message, but the app was seemed gone from the system apps list. So I tried to install the dialer from the Custom rom... no success. I decided to give up, restored the back up and everything was OK.
I went to bed and even dreamed about this marvelous phone, just to wake up to a... Well:
"com.android.phone crashed" messages
no access to any of my SMS apps - stock or Classic Messaging. It just closes with no warning or error message
No data connection. Actually, my SIM wasn't recognized at all after a while
I took my SIM card and put it back in my old phone and, until I rebooted for the second time, the card was problematic, but now it's ok.
How can I clean this mess? I tried to clean the Phone cache to no success, then proceeded to a factory reset with the same outcome
(I have no MicroSD card on the L90)
Follow this Guide and reflash stock rom. :good:
http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479
marioho said:
In advance: I may be a idiot.
I received my LG L90 D410hn yesterday and was happily fooling around. Summing up, all I'd done was:
instaling LG OTA update
successfuly rooting it (towel)
installing greenify pro/donation edition
installing Classic Messaging
Installing Google Launcher (sideloading apk)
Greenifying the bloatware described all along this thread
Eveything was running smooth and crisp, but the dialer design really got to my nerves. So I decided to try to install my LG Optimus 2X custom rom's dialer (The ROM) because that is NEAT.
I backed up my original Phone apk and other related apps with ES File Explorer just in case and uploaded the apks to my Dropbox.
Then I proceeded to uninstall the Phone app. The try was rewarded with a "unsuccesful" message, but the app was seemed gone from the system apps list. So I tried to install the dialer from the Custom rom... no success. I decided to give up, restored the back up and everything was OK.
I went to bed and even dreamed about this marvelous phone, just to wake up to a... Well:
"com.android.phone crashed" messages
no access to any of my SMS apps - stock or Classic Messaging. It just closes with no warning or error message
No data connection. Actually, my SIM wasn't recognized at all after a while
I took my SIM card and put it back in my old phone and, until I rebooted for the second time, the card was problematic, but now it's ok.
How can I clean this mess? I tried to clean the Phone cache to no success, then proceeded to a factory reset with the same outcome
(I have no MicroSD card on the L90)
Click to expand...
Click to collapse
When you place your original dialer back into its original place, make sure the permissions are r-w-rr, and then reboot. If that doesn't work, I'm sure someone else can help you out. There's a fix for this besides reflashing the KDZ.
Ilxaot said:
When you place your original dialer back into its original place, make sure the permissions are r-w-rr, and then reboot. If that doesn't work, I'm sure someone else can help you out. There's a fix for this besides reflashing the KDZ.
Click to expand...
Click to collapse
Thank you, guys! I ended up reflashing KDZ. It was a breeze though, so no hard feelings.
I did, indeed, read about the permission settings, but couldn't find a good guide at the time so I let it slip.
Reflash KDZ didnt fix it for me
I have an almost identical problem after attempting to install the google dialer. I reflashed the phone but it still had all the previously loaded apps still in it including the dialer and services. Any ideas what to do next? The dialer and services have the correct permissions. I noted in another post that the version on these is 0.

Voice Search Broken, says "Can't reach google at the moment."

Hi All,
Running stock but rooted (with Xposed modules) 4.4.4 on Verizon Moto X with an unlocked bootloader. (Flashed this stock ROM: http://forum.xda-developers.com/showthread.php?t=2829123 )
Any time I try to do any activity with voice I get the error, "Can't reach google at the moment."
I get this error if I click the mic in google now and by clicking the voice text mic on the keyboard. Also, Touchless Controls doesn't respond.
After searching around forums I've tried some suggestions that worked with similar problems on other phones, but to no avail. I've tried:
- clearing data and cache of google search app and force stopping (lost my google now launcher set up in the process)
- removing my google account from the phone, rebooting to recovery, clearing cache and dalvik, rebooting and adding my account back
Thanks for any suggestions.
hi, had the same issue with one of the modules in xposed, ended up wipping the device and started fresh, installed xposed and gravity box, no other modules, all is good now.
ericizzy1 said:
hi, had the same issue with one of the modules in xposed, ended up wipping the device and started fresh, installed xposed and gravity box, no other modules, all is good now.
Click to expand...
Click to collapse
Hmm, interesting...
I'm thinking it's not a specific Xposed module... I just tried uninstalling xposed framework altogether and then wiping cache and dalvik for good measure. No luck.
But out of curiousity, these are the modules I have installed: GravityBox, Exchange Bypass For Xposed, SingalIconsAOSP, Unicon. Besides GravityBox, did you have any of these installed when you had the issue?
I hope this doesn't come down to just wiping, which it most likely will.
My droid maxx has had the same problem since the update to 4,4,4 I have tried everything including a fdr ( through twrp ). Nothing has worked ! Moto has offered me a new phone but I don't want a new one as mine is unlocked and rooted ( otherwise stock ). I think I'm going to unroot it, put back in the stock recovery and try a fdr through that...POS !!!
This may not help at all....but maybe worth a shot. If you try and it doesn't help, post back here and let everyone know so nobody else tries it.
You might have some luck by erasing baseband cache with fastboot:
fastboot erase modemst1
fastboot erase modemst2
You might have to re-activate afterwards. It is the only suggestion that might be relevant that you haven't tried already...
Good Luck....that would be a frustrating issue... :good:
Unfortunately I gave up and just wiped and did another clean flash and its working again. It was very frustrating not having touch less controls or voice to text...
Thanks for the help though anyway.
leffer said:
Unfortunately I gave up and just wiped and did another clean flash and its working again. It was very frustrating not having touch less controls or voice to text...
Thanks for the help though anyway.
Click to expand...
Click to collapse
I agree touch less control wasn't something I cared about when I got the phone. But after getting used to it its hard to go without.
When you say you wiped and flashed. Can you elaborate. I tried fxzing ( saving data ), 2 FDR's everything .. Did you unroot then use HOM ? I will try anything at this point . Thanks in advance
tombaldwin6 said:
I agree touch less control wasn't something I cared about when I got the phone. But after getting used to it its hard to go without.
When you say you wiped and flashed. Can you elaborate. I tried fxzing ( saving data ), 2 FDR's everything .. Did you unroot then use HOM ? I will try anything at this point . Thanks in advance
Click to expand...
Click to collapse
My bootloader is unlocked so I was able to simply factory reset and reflash the stock 4.4.4 ROM from the thread I linked to in the OP...
leffer said:
My bootloader is unlocked so I was able to simply factory reset and reflash the stock 4.4.4 ROM from the thread I linked to in the OP...
Click to expand...
Click to collapse
I will try both methods and post back. Thanks for you help !
So I took both suggestions tried them 1st. I tried erasing the the baseband cache's via fastboot. No luck. 2nd I reflashed the current 4.4.4 stock rom via HOM, Full FXZ ( no data saved). !st off what a pain in the ass it is to reset up these phones from scratch. I setup my Google account but I didn't let Google reinstall all my previous apps and there data. I then went into settings and arranged things how I like them. Cleared off my home screens, put a few of the apps where I wanted them. I then went into the play store and allowed all apps ( preloaded ) to update. I then went back into settings and went to touchless control. To my surprise it worked ! I then went about loading all my apps.The usual 1's everyone has ie: Elixir2, FX filemanager,Poweramp, MX Player,Chromecast Panasonic tv remote 2, Google Wallet, UE Miniboom and Few other nondescript. Then I checked touchless control again and It was still working. Then I decided to install twrp and its recovery via fastboot ( 2.6.31 ) let it root the phone for me. Here's where it gets dicey.. It was late and I had had it with this friggin phone. I went and loaded all my apps that required root,Superuser pro, Dsploit, Busybox pro,Android terminal emulator, Wakelock(full) all the usual's. Then I went through and disabled all of the bloat. Rebooted and switched the phone to ART The following morning I went to show a friend how I had fixed my phone and It no longer worked ?
So I FXZ'd again not saving any data. Reinstalled twrp , rooted . Then 1 by 1 I reloaded every single app back into the phone and checked google now between every single install. Also this time I didn't let any of the bloatware update. I planned on disabling it anyways so why bother. I didn't install any apps that require root except twrp, busybox, Dsploit and #mirrorenabler . Also it's currently back on Dalvic. So as my phone sits now touchless control and all of its functions are working again. It's obviously a rouge app or ART Runtime that did this and I will narrow it down in the next few days and report back.

[Q] Xposed causes WiFi to stop working...

So I decided I should to a factory reset on my Moto X today to clean it up and make it run better. Anyway I downloaded Towel Pie Root, rooted the phone, and backed up my apps with TB. My phone hadn't been rooted up to this point. Anyway I did the app backup and pulled my /sdcard/ contents to my laptop with adb and did the factory reset. Afterwards I got everything updated, restored the apps I wanted with TB(after rerooting with TPR), and got the phone set back up like I wanted. I also decided I'd give Xposed a try being that rooting was fairly simple with TPR. I downloaded Xposed 2.6.1, installed the framework and did a soft reboot. After doing that I can't connect to WiFi anymore; I just get a "Failed to Connect to Network" toast notification when I try. A Hard Reboot fixes the issue until I reinstall Xposed then WiFi breaks again.
Any ideas on why this is happening or how to fix it? I know I read in the TPR thread that people were using Xposed with TRP like I'm trying to.
Sent from my MacBook Pro using Chrome
Phone: Moto X(XT1053) running Stock 4.4.3

Help, Bricked after using Kingroot

The first few times I used Kingroot to achieve temp root, it worked great and then just went back to unrooted after a while. One time after rooting, it was spammed with error messages that the play store and other apps were crashing. I rebooted the phone and it seemed to fix it. The errors were gone and so was root. I tried kingroot again and I had the same problem. I did the same reboot and then deleted the kingroot app. I thought everything was fixed then until I plugged my phone in to charge. It shut down even though it was around 75%. I didnt know what i was doing so I put it in recovery mode and choose factory. I thought this would do a factory reset but now when my phone powers up all my apps and stuff is there. Please advise how to completely rid my device of kingroot. Thanks in advance
Update: When I started in factory mode, there was a testing app called commserver or something like that running. I saw in other forums to reboot to remove that and i did and it worked. Still would like advice on removing kingroot completely.
Jefff0101 said:
The first few times I used Kingroot to achieve temp root, it worked great and then just went back to unrooted after a while. One time after rooting, it was spammed with error messages that the play store and other apps were crashing. I rebooted the phone and it seemed to fix it. The errors were gone and so was root. I tried kingroot again and I had the same problem. I did the same reboot and then deleted the kingroot app. I thought everything was fixed then until I plugged my phone in to charge. It shut down even though it was around 75%. I didnt know what i was doing so I put it in recovery mode and choose factory. I thought this would do a factory reset but now when my phone powers up all my apps and stuff is there. Please advise how to completely rid my device of kingroot. Thanks in advance
Update: When I started in factory mode, there was a testing app called commserver or something like that running. I saw in other forums to reboot to remove that and i did and it worked. Still would like advice on removing kingroot completely.
Click to expand...
Click to collapse
To remove Kingroot completely, you need to reflash the system partition. You can do this by plugging your phone into a computer, installing the Verizon Upgrade Assistant, and using the "repair your phone" option. Doing this will wipe your phone, so backup any data first.
TheSt33v said:
To remove Kingroot completely, you need to reflash the system partition. You can do this by plugging your phone into a computer, installing the Verizon Upgrade Assistant, and using the "repair your phone" option. Doing this will wipe your phone, so backup any data first.
Click to expand...
Click to collapse
Thanks, I'm kinda a noob so could you walk through the steps like you were talking to a baby? Like do I put my phone in recovery mode and then download the version thing on the computer? How do you suggest backing up my phone? Sorry for the bother, I'm new to this stuff. Thanks again
Sure:
1. Boot your phone normally. Backup whatever data you want to preserve. Make sure that whatever backups you make are stored in a place that is outside of your phone.
The best way to backup your phone depends on what you want to backup. If you're worried about losing contacts, don't be. I'm pretty sure Google backs those up automatically. You can make sure by going to https://www.google.com/contacts/. If you see contacts there, you're good. If you're worried about losing pictures, plug your phone into a computer and use a file browser to copy the folder called DCIM to your computer. If you want to try backing up your texts, there's an app on the play store called Super Backup that might help. Just make sure that you transfer whatever backup file it makes to a cloud drive or your computer.
2. Plug your phone into a computer running Windows (I'm not sure if it what I'm about to describe works on a Mac or not, but I know that it does not work on Linux). You should get a pop-up that says something like "do you want to install the verizon upgrade assistant?" Install it. If you don't see the pop-up, install this instead: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481. This is the Motorola Device Manager, and it's basically the same thing.
3. If you're using the Verizon tool, select "repair device" and follow the instructions. If you're using the Motorola tool, look for something that says "repair phone" or something like that, and follow those instructions.
4. The tool will wipe your phone, along with all of that nasty Kingroot stuff that tries to make modifications to /system despite the fact that /system is write-protected until you unlock with Sunshine (which is why it messed up your phone).
5. If you decide you want it, download Sunshine from here: http://theroot.ninja/download.html.
6. Go into your phone's security settings and allow installation of apps from unknown sources.
7. Click on the Sunshine apk that you downloaded to your phone to install it.
8. Open the Sunshine app and follow the instructions. If, when your phone reboots, you see a bootloader unlocked warning message instead of the black and white Motorola M symbol that usually appears, it was successful. If it was unsuccessful, keep trying. It should get it after a few tries.

Categories

Resources