Hello my contacts app wont sync and opening phone app it instinct crashes.
Currently:
My phone is rooted with magisk 17.1. , boot loader open and has twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger installed
What happened:
the latest update for android 9.05 was out on OTA and so I updated. But the update did not go through well and then when i restart the phone, it would loop and keep sending my into recovery how every many times i say to boot into systems in recovery.
To stop to looping, I had to ADB install most up to date Stock OOS ROM (9.0.4). Things where working fine and then I updated. (did not try phone and contacts app then)
Also, when i try to install magisk version higher than 17.1 the phone would recovery loop again and the only way to stop it was to flash to stock ROM using Twrp. So i installed Magisk 17.1 right now
So at the moment, everything works but BUT the Contacts app which cant sync to Google and Instinct crashing Phone App on open.
What I have tried:
Flash stock ROM using TWRP and no update
unroot completely using magisk manager then Flash Stock ROM ( then tried to update. Update worked. phone app still crash and contacts app dont sync)
Delete all Cache/Dalvik cache
Please please please help me.
Thanks
Related
So I have installed the 6.0 CWRecovery in my Note 3 (hlr) in order to install the newest CWM12(7.8), I managed to install the CWRecovery touch 6.0 using the app known as Flashfy, it worked fine and so I managed to install CM mod 12 (I have some problem with the stock Music app, which crashes all the time). I saw a new update (8.1) and I wanted to update it again, but the boot does not load the recovery mod and thus, it just keep on a recovery boot loop. The only way to get out of such loop is to load the download mode, and then it boots the CW12. I have tried reinstalling the recovery mode using the flashfy and rom manager, but it does not work at all, even when using the said programs to flash the ROM itself. What should I do? Thanks!
Leminur said:
So I have installed the 6.0 CWRecovery in my Note 3 (hlr) in order to install the newest CWM12(7.8), I managed to install the CWRecovery touch 6.0 using the app known as Flashfy, it worked fine and so I managed to install CM mod 12 (I have some problem with the stock Music app, which crashes all the time). I saw a new update (8.1) and I wanted to update it again, but the boot does not load the recovery mod and thus, it just keep on a recovery boot loop. The only way to get out of such loop is to load the download mode, and then it boots the CW12. I have tried reinstalling the recovery mode using the flashfy and rom manager, but it does not work at all, even when using the said programs to flash the ROM itself. What should I do? Thanks!
Click to expand...
Click to collapse
Try downloading the TWRP...tar file for your phone (http://teamw.in/project/twrp2 - click top right for your phone) and flash it using Odin - it will give you TWRP Recovery.
Also go to Chainfire's site and get SuperSU.zip (http://download.chainfire.eu/695/SuperSU/UPDATE-SuperSU-v2.45.zip) so you can flash it in Recovery.
I flash the ROM, then GApps (I use PA version) then SuperSU in one flash session, then I Restore my Data partition from my nandroid backup and always good to go after that.
http://forum.xda-developers.com/showthread.php?t=3060970
Sent from my SM-N900 using XDA Free mobile app
Hi All,
I use SM-A510FD Galaxy A5 2016 as my daily Driver.
I rooted my phone and installed Xposed in it. Then i uninstalled some Stock Apps like Opera Max and all. After few days of usage(2 days to be particular), I am seeing that some of my apps crash suddenly and that the following error popps up: Unfortunately Phone has Stopped, Unfortunately ES File Explorer Has Stopped.
After I click OK it pops up again.
So in a wonderfully foolish step I uninstalled the Phone App and now the phone will not reboot.
I uninstalled Xposed but nothing helped. Finally after lots of research on XDA and otherwise I flashed The Stock Firmware for my Phone SM-A510FD.
It rebooted just as fine but now the same problem is there and is not resolved. Moreover if i Open some app like Play Books while i am getting the error, the popup of the error stops until i open the Phone app again. I opened my phone in Safe MOde and saw that the same problem is also there which means it is not caused by some third party apps. PLease help
deepray said:
Hi All,
I use SM-A510FD Galaxy A5 2016 as my daily Driver.
I rooted my phone and installed Xposed in it. Then i uninstalled some Stock Apps like Opera Max and all. After few days of usage(2 days to be particular), I am seeing that some of my apps crash suddenly and that the following error popps up: Unfortunately Phone has Stopped, Unfortunately ES File Explorer Has Stopped.
After I click OK it pops up again.
So in a wonderfully foolish step I uninstalled the Phone App and now the phone will not reboot.
I uninstalled Xposed but nothing helped. Finally after lots of research on XDA and otherwise I flashed The Stock Firmware for my Phone SM-A510FD.
It rebooted just as fine but now the same problem is there and is not resolved. Moreover if i Open some app like Play Books while i am getting the error, the popup of the error stops until i open the Phone app again. I opened my phone in Safe MOde and saw that the same problem is also there which means it is not caused by some third party apps. PLease help
Click to expand...
Click to collapse
from my point of view you only need to wipe to factory settings, flashing stock firmware doesn't wipe user data.. just try these scenarios based on your recovery type
If you're on TWRP
1. boot to recovery and just go to WIPE > Advanced Wipe, select all EXCEPT internal & external storage then wipe it
2. reboot to download mode
3. flash stock firmware
if you're on stock recovery
1. boot to recovery
2. wipe to factory format
3. reboot to system, if it does not boot go back to download mode & reflash stock firmware
Twiq said:
from my point of view you only need to wipe to factory settings, flashing stock firmware doesn't wipe user data.. just try these scenarios based on your recovery type
If you're on TWRP
1. boot to recovery and just go to WIPE > Advanced Wipe, select all EXCEPT internal & external storage then wipe it
2. reboot to download mode
3. flash stock firmware
if you're on stock recovery
1. boot to recovery
2. wipe to factory format
3. reboot to system, if it does not boot go back to download mode & reflash stock firmware
Click to expand...
Click to collapse
Thanks for the help sir. But as mentioned i have already wiped the cache and dalvik plus i had also flashed the stock ROM. But the problem did not go away as it is not related to it.
Actually while giving some app access to storage or camera, i had to switch off screen overlays for all apps including the phone app. But the Phone app needs to have this as it requires this to ask for SIM 1/2. So after i gave the Phone app the screen overlay it is workinh just as fine.
Anyway thanks a lot.
I downloaded and installed the unofficial xposed by abforce for my zte axon 7 lineage os 7.1.2 and i started having problems like its would spam my screen with bank app, facebook, snapchat, TWRP, xposed installer et literally ever app would notify me that it had stopped. So i decided to remove it via the xposed installer, i used the correct uninstalller (arm64) but after reboot im not stuck in a continuous boot. It's juts keeps on booting. Last time i had this problem with a continious boot i re-installed gapps and that worked. But in this case, it is not working. I re-installed magisk as well but it's still just booting. I can boot into twrp recovery and stuff.. It's been booting for around 30mins now and it still won't boot. I have a backup of my system when i first got lineage OS with no gapps though.
Wipe system and install rom zip and gapps. install magisk too if you want
WesTD said:
Wipe system and install rom zip and gapps. install magisk too if you want
Click to expand...
Click to collapse
Will i not lose all my data? I have around like 20GB of data.
WesTD said:
Wipe system and install rom zip and gapps. install magisk too if you want
Click to expand...
Click to collapse
Dw, saved my life, thanks so much
Okay well now Im having problems with all my apps just crashing on me every now and then. It seems to happen for every app even the ones I had never experienced crashes on. Why would this be happening. ?
SugnaB said:
Okay well now Im having problems with all my apps just crashing on me every now and then. It seems to happen for every app even the ones I had never experienced crashes on. Why would this be happening. ?
Click to expand...
Click to collapse
Dunno, just wipe system and do that again. if you can wipe data too, then do so
Hello. I rooted my phone using this guide en.miui .com /thread-415853-1-1.html
Everything works good, but then I tried to move an app to system with Link2SD but it said "write error no space left on device" and system space was 100%. I moved some system apps to user apps to make space (Mi Cloud, Mail, Calendar) but the problem persisted so I decided to leave it alone and not do anything. I then proceed to unroot by uninstalling with Magisk Manager, reboot and it got stuck on Mi Logo. I even left it for several hours but nothing happened.
I found out that if I enter fastboot and then TWRP, I can flash Magisk again, reboot, and it is not stuck on MI Logo anymore, the system boots perfectly and all my files and apps are there same as before. But how can I unroot without getting stuck on MI Logo? Is there a problem with Magisk or something? What else can I try?
I'm thinking my best choice is to flash the Mi ROM again using TWRP, is that correct? Any help would be appreciated, I'm still learning about this.
Currently I have MIUI Global 8.5.5.0 Stable (MADMIED) and I just downloaded the zip file of that rom.
Ok I worked it out. I'm going to post my solution in case someone else has the same problem.
Since I was able to boot system normally if I flashed Magisk again, I did that, made a backup of my whatsapp chats and saved a backup of my files in MI Account.
Then I reboot TWRP recovery, wipe all (factory reset) and flash my ROM MIUI Global 8.5.5.0 Stable (MADMIED). Phone started, root was gone, restored my backup.
Then I reboot again TWRP, flash Magisk and Phh SU and everything else in the guide linked above. Installed Link2SD, deleted some system apps (Youtube, Google Play Movies and Music and some others), and then I was able to move the app I wanted to system.
Rebooted phone to system. Then uninstalled Magisk from Magisk Manager, reboot phone, and everything worked ok!
Thanks, im planning on flashing twrp and magisk, so this could become handy ?
Try flashing these, worked like a charm for me.
https ://android file host. com /?fid=889964283620756562
https ://android file host. com /?fid=745425885120731943
just remove the spaces and you are ready to go!
Found a better Solution!
If you are stuck on the MI logo after the unroot that's because of the verity check of the ROM. So if u could boot into the custom recovery(TWRP) then just simply flash the lazy flasher zip file and then you are good to go, the ROM will normally boot with all of your files and apps.
I'm a total noob at rooting. I tried rooting my Xiaomi Redmi Note 7 today and everything was going surprisingly well until I decided to reboot my device.
My device is now stuck at fastboot, this may have been caused because I updated Magisk.
I can access TWRP but don't know what to do with it. I don't care about my data, I just want my device to work again.
Could anyone suggest any solutions? Thank you in advance!
Did you try rebooting it fron twrp?. twrp >reboot>reboot into system.
Anon-cross said:
Did you try rebooting it fron twrp?. twrp >reboot>reboot into system.
Click to expand...
Click to collapse
Yeap, didn't work.
I just flashed the stock ROM using MiFlash and it worked fine.
Half a hour later, I messed up again and stuck at fastboot for a second time, so I flashed the stock ROM once again and it works like a charm now.
My second failure made me realize what the problem was (well, kind of).
So, the first time I got a bootloop, I thought that it was due to the fact that I had updated Magisk (I read some similar issues online, that's why I thought so).
But that's not the case because the second time, I installed the latest version of Magisk and the same thing happened.
So, the only action that could have caused the bootloop, which was performed both the first and the second time, is the removal of a system app using System App Remover.
I clearly removed something that I wasn't supposed to. It was one of those system apps but don't know exactly which one cause I removed all of them in bulk and then tried to reboot:
GetApps (com.xiaomi.mipicks)
Games (com.xiaomi.glgm)
Mi Credit (com.xiaomi.payment)
Thanks for helping, I hope my answer helps someone else.
My only problem now, is that I'm unable to install updates to the stock MIUI ROM, but that's fine, rooting the device was worth it anyway.
I faced the same problem today
Install twrp ,root and install system app remover
delete some apps i did not need it
when i reboot the phone stuck at fastboot
I reboot to twrp and do a factory reset, format data didnt help
Return again to recovery and unroot
The phone boot to system
I dont understand why this happened because i
remove the same apps before with xiaomi adb fasboot tools didnt face any problem
Aures Batna said:
I faced the same problem today
Install twrp ,root and install system app remover
delete some apps i did not need it
when i reboot the phone stuck at fastboot
I reboot to twrp and do a factory reset, format data didnt help
Return again to recovery and unroot
The phone boot to system
I dont understand why this happened because i
remove the same apps before with xiaomi adb fasboot tools didnt face any problem
Click to expand...
Click to collapse
Sounds strange.
I thought it was the removal of specific apps, but could it be the System Apps Remover that causes the issue?
I wonder if using Titanium would make any difference but I'm not willing to risk it for a third time, I'm good now.
Test orangefox, maybe the older magisk 19.4 and the magisk module debloater.