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
Related
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
I've tried searching, but didn't seem to get anything on this one.
I've been trying to install the OTA Update to 4.3 for a minute, now... Currently, I've got the update downloaded, but it won't continue b/c it's saying the battery is too low. The thing is, the battery is at 100%. It is also plugged into a charger... Tried it with and without.
Here's info on my phone:
MJ5
Rooted via Kingo
Xposed Installer installed (very few modules installed - nothing hardcore)
RootCloak [1.4] installed in order to hide root status from the OTA update service
I have a bit of bloat uninstalled by Titanium Backup... But, that was all AT&T stuff like Navigator - I left the OTA service in place. I froze some Samsung bloat, but didn't uninstall it.
Any ideas on why I'm getting this error?
You have to be unrooted. At least that what I hear . When I got the update I did a factory reset and downloaded the update and installed with no issues.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Blargh. I unrooted via Kingo, rebooted and I am still getting the same low battery error.
I really don't want to have to do a factory reset...... Are there any other options?
Ah, great. Now Kingo won't re-root the phone. Looks like factory reset is what I'll be spending my evening doing.
Great. Did a factory reset, and went to update. It failed; said the installation was interrupted.
I tried two more times... Same results. This is getting pretty frustrating...
Pscheoverdrive said:
Great. Did a factory reset, and went to update. It failed; said the installation was interrupted.
I tried two more times... Same results. This is getting pretty frustrating...
Click to expand...
Click to collapse
Unfortunately nothing will work except restoring back to stock. I had to do that for the last 2 updates we've received. I just did it to get the last update and I am staying stock until Kitkat arrives then will look for a root solution. I know, it sucks.
Follow this thread:
http://forum.xda-developers.com/showthread.php?t=2559715
Pscheoverdrive said:
Blargh. I unrooted via Kingo, rebooted and I am still getting the same low battery error.
I really don't want to have to do a factory reset...... Are there any other options?
Click to expand...
Click to collapse
If you didn't uninstall the Xposed modules the uninstall Xposed that could be your issue right there. Try uninstalling everything root then try again.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Well, at this point, I have done a factory reset several times. No root, nothing installed.
Knox keeps giving me a notification that it's blocking a process... I can download the update and start the install process. Once the phone reboots and the AT&T splash screen comes up, the progress bar will start and get to about 20%, then the phone will restart, then boot normally. Once booted, it will go to the Update page and then say that the installation was interrupted.
What... the... heck... I thought a factory reset restored the phone to like how it was from the factory? I notice my keyboard is the old version, too. When I bought the phone, I had the updated keyboard with punctuation for long-key presses.
Any insights?
Pscheoverdrive said:
Well, at this point, I have done a factory reset several times. No root, nothing installed.
Knox keeps giving me a notification that it's blocking a process... I can download the update and start the install process. Once the phone reboots and the AT&T splash screen comes up, the progress bar will start and get to about 20%, then the phone will restart, then boot normally. Once booted, it will go to the Update page and then say that the installation was interrupted.
What... the... heck... I thought a factory reset restored the phone to like how it was from the factory? I notice my keyboard is the old version, too. When I bought the phone, I had the updated keyboard with punctuation for long-key presses.
Any insights?
Click to expand...
Click to collapse
Factory reset just wipes your data and cache. It will not reinstall the system files. When you rooted you directly modified some of your system files via root access. Simple solution however. Follow these steps as mentioned before by theorioles33 using Odin and Heimdall. Takes about 10 mins (maybe 30 if its ur first time) Follow every step to the T and when ur back to stock try the OTA. Good Luck!
My brother has an LG G2 (verizon), I rooted his phone for him because he's not much of an android enthusiast himself. He wanted to get rid of some bloatware on stock rom so he downloaded a root unintaller, and in the process of it, he uninstalled something he wasn't supposed to. I don't know exactly what process/apk it was, but it was a system file. Now almost every system app force closes, (phone,mms,contacts,settings). I tried a factory reset, and the problem remains. He is still rooted, and I know the best workaround would be to flash a new rom (custom or stock, i dont really care), but that's where the problem comes in. I am trying to install this:http://forum.xda-developers.com/showthread.php?t=2715496 AutoRec to get a custom recovery, so I can flash a new rom, but because settings instantly force close, I cant enable to install from unknown sources. I tried to adb push the apk, but after about an hour of trying, adb doesn't recognize the device. I tried both a wired, and wireless adb attempt (idk if its even possible to adb push an apk via wireless, but I tried, and it says my device is unauthorized, so didn't work. Is there any workaround to my problem? I downloaded an app that enables usb debugging, but adb still doesn't recognize, even after i installed the driver. Been at this for hours with no luck, would be great if one of you knew a way to fix this dilemma.
FuzionRain said:
My brother has an LG G2 (verizon), I rooted his phone for him because he's not much of an android enthusiast himself. He wanted to get rid of some bloatware on stock rom so he downloaded a root unintaller, and in the process of it, he uninstalled something he wasn't supposed to. I don't know exactly what process/apk it was, but it was a system file. Now almost every system app force closes, (phone,mms,contacts,settings). I tried a factory reset, and the problem remains. He is still rooted, and I know the best workaround would be to flash a new rom (custom or stock, i dont really care), but that's where the problem comes in. I am trying to install this:http://forum.xda-developers.com/showthread.php?t=2715496 AutoRec to get a custom recovery, so I can flash a new rom, but because settings instantly force close, I cant enable to install from unknown sources. I tried to adb push the apk, but after about an hour of trying, adb doesn't recognize the device. I tried both a wired, and wireless adb attempt (idk if its even possible to adb push an apk via wireless, but I tried, and it says my device is unauthorized, so didn't work. Is there any workaround to my problem? I downloaded an app that enables usb debugging, but adb still doesn't recognize, even after i installed the driver. Been at this for hours with no luck, would be great if one of you knew a way to fix this dilemma.
Click to expand...
Click to collapse
Just return it to stock using the guide on the main page. You can disable apps via App Manager without having root. If he does root it again, tell him to rename files to .bak instead of deleting them...
I successfully installed Android M, and things were mostly okay. Titanium Backup won't load. It force closes, and having a problem with Dolphin Browser flashing a handful of times and then erroring out...unable to use. Other than that, everything seemed to be working perfectly. However, I needed to be able to restore my app settings, and I know Titanium Backup needs root. So, I thought maybe that's why it was force closing. So, I decided the easiest way to root would probably be using the Nexus Toolkit. I used that, which seemed to go normally, but the phone won't boot now. It just goes black. ADB seems to be able to communicate with it in this black screen state (via Nexus Toolkit, for example), but I can't get anywhere. I tried re-flashing the boot and bootloader, but it didn't help. I am seeking the wisdom of the elders.
YOu are going to have to start all over. SO factory reset. to clear out everything and get a fresh M load.
The toolkit is for Android L. So it overwrote things that Android M needed.
Once you have a fresh install. Go here http://www.androidauthority.com/android-m-root-613760/ and root.
all you need to do os flash a m kernel(despair kernel) and the latest SuperSU, and youll have root. flashing the latest supersu with a m kernel will not work.
Thank you for the feedback. I am mostly in business. I can't get BusyBox to install, though. The app runs fine, but actually installing it from within the app does not work...says it was not successful. I have tried the other location, which didn't work also. Any thoughts? Thanks much; greatly appreciate the assist.
mystik1 said:
Thank you for the feedback. I am mostly in business. I can't get BusyBox to install, though. The app runs fine, but actually installing it from within the app does not work...says it was not successful. I have tried the other location, which didn't work also. Any thoughts? Thanks much; greatly appreciate the assist.
Click to expand...
Click to collapse
I'll do some more research and get back to you on this one. Not exactly sure how busybox is running on the new file structure.
[HELP] unrooted phone without uninstalling xPosed
Hi, I have a Wiko Highway that I want to send to warranty.
So i had my phone rooted, and unrooted it and then factory reseted it, but i forgot to uninstall xPosed and its modules.
Now i started to install some apps so i dont send the phone empty, and when installing snapchat it wont let me login (as it block's rooted phones)
So, by some way snapchat "thinks" i'm still rooted, i'm afraid the provider can tell that :/
Is there anyway to prevent this?
Thanks
Assuming you don't have a backup...
If it's a kitkat or older phone then reroot and uninstall using the xposed app.
If it's lollipop+ then, first off shame for not making a backup since you need a custom recovery to install lollipop version, use the uninstaller from the main download thread.
If it's kitkat or older and you can't root and the app claims xposed is active then when you boot the phone repeatedly press your power button til the phone vibrates a bunch and that should at least disable xposed.
As for sending it in for warrenty if they were going to reject it then they'd look at a tamper flag and there's a precious few devices that you can reset that on. Cross your fingers basically.
Hi, thanks for the reply
I tried rerooting and i'm not being able to :s
As for rebooting with xposed disabled it didnt make the app work
And how could i reset that flag?
Thanks again for the reply