Please help! I have something real funky going on. Anytime I flash a new ROM in latest 2.4.3.0 twrp, it says I lost root and asks to restore. But I really don't, even if I click do not fix, I have supersu when I boot. But then a notification pops up on first boot saying play services error! And the google play store doesnt get installed.. Doesnt matter what gapps i use, gplay never gets installed. So luckily I have a TiBu update zip that I made of all my apps, so I go back into twrp, flash it, reboot, go into es file explorer to install play store, but it keeps force closing, so I reboot and that fixes the problem. So it gets worse, once I update all my apps thru gplay, like update supersu, once I reboot, I lose all the updates and have to redo them! And supersu will ask for su access to the same apps over and over again each time I reboot. I have no idea what's going on, can anyone help?
IDL about that but twrp will not restore data from any of my backups even when the archive shows 2+GB backed up, fails to restore
Sent from my Nexus 4 @1.67 GHz on Stock 4.2.2
Your issue with losing root so to speak may come from superuser. Go to setting in the su app and go to settings, reinstall and download supersu from play store
I had the same thibg haooen a out loosing root access and that fixed it
As for your errors and force closes...what kernal are you running?
sent from my 1920 overclocked note 2 running jedi xp11
Related
I tried installing the 4.2.2 OTA update on my unlocked and rooted Nexus 7 (no mods or anything). I have CWM 5.8. The update failed, so I rebooted and everything seemed normal (I am still on 4.2.1). Then, I went to the Play Store and tried to install some new app updates. As soon as I clicked the "Update" button, Play Store force closed, and continues to do so no matter how many times I clear cache/data from both Google Play Store and Play Store Services. I flashed the /system from a Nandroid backup of 4.2.1 but the problem still persists. I also tried reinstalling the Play Store apk but to no avail.
Any ideas?
Save your data on pc, cloud, etc. and flash factory image, if you want to stay stock. There is also a 4.2.2 stock-ish ROM in the development section, it's deodexed, and rooted, so you don't have to do that manually. To flash factory image, I recommend using one of those toolkits from the development section.
mkoch820 said:
Save your data on pc, cloud, etc. and flash factory image, if you want to stay stock. There is also a 4.2.2 stock-ish ROM in the development section, it's deodexed, and rooted, so you don't have to do that manually. To flash factory image, I recommend using one of those toolkits from the development section.
Click to expand...
Click to collapse
I was going to try flashing the factory image, so I downloaded the .tgz file, but the Android Toolkit app kept giving me an error, saying that the device was offline. My Nexus 7 connects fine to my Windows 7 PC, but it doesn't seem to connect in ADB mode and I have no clue why. USB debugging is enabled, but I cannot get it to connect in ADB mode.
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.
As soon as the root finished installing and the device booted up, some apps where uninstalled while the google apps kept force closing. I try to open the play store but it closes before any information pops up. Do I just need to install new Gapps? I am lost and a complete noob.
Edit: I installed the latest version of Gapps and that solved the force closing issue but now every time I try and download an app, I get the "Unfortunately Google Play Store has stopped working" issue.
Edit 2: The errors are not limited to Gapps. I'm also getting "android.media.process has stopped" and "Unfortunately Contact Storage has stopped".
crazydaftunk said:
As soon as the root finished installing and the device booted up, some apps where uninstalled while the google apps kept force closing. I try to open the play store but it closes before any information pops up. Do I just need to install new Gapps? I am lost and a complete noob.
Edit: I installed the latest version of Gapps and that solved the force closing issue but now every time I try and download an app, I get the "Unfortunately Google Play Store has stopped working" issue.
Edit 2: The errors are not limited to Gapps. I'm also getting "android.media.process has stopped" and "Unfortunately Contact Storage has stopped".
Click to expand...
Click to collapse
I would suggest wiping the Dalvik/Art and caches in recovery. Rooting I prefer to flash custom recovery and flashing SuperSU manually
Sent from my SCH-R220
mattzeller said:
I would suggest wiping the Dalvik/Art and caches in recovery. Rooting I prefer to flash custom recovery and flashing SuperSU manually
Sent from my SCH-R220
Click to expand...
Click to collapse
I used the option on SuperSU to unroot and delete the app. I think it got rid of the root and the recovery. Would I have to root my phone again, install a recovery, and then wipe the dalvik/art caches?
I can update the apps already installed but can't install new ones. Apk's install just fine.
crazydaftunk said:
I used the option on SuperSU to unroot and delete the app. I think it got rid of the root and the recovery. Would I have to root my phone again, install a recovery, and then wipe the dalvik/art caches?
I can update the apps already installed but can't install new ones. Apk's install just fine.
Click to expand...
Click to collapse
Unrooting shouldn't touch your recovery
Sent from my SCH-R220
crazydaftunk said:
As soon as the root finished installing and the device booted up, some apps where uninstalled while the google apps kept force closing. I try to open the play store but it closes before any information pops up. Do I just need to install new Gapps? I am lost and a complete noob.
Edit: I installed the latest version of Gapps and that solved the force closing issue but now every time I try and download an app, I get the "Unfortunately Google Play Store has stopped working" issue.
Edit 2: The errors are not limited to Gapps. I'm also getting "android.media.process has stopped" and "Unfortunately Contact Storage has stopped".
Click to expand...
Click to collapse
That happens after rooting with CF auto root. You need to boot into recovery to fix the problem by wiping cache and restore to factory default.
Hello guys.
Today I did it successfully the root of my Oneplus 5 with magisk. But I have a problem. Even with root hide I can't install netflix. Google Play show me not certified. I allready wipeout everthink remove the root install the stock remove, I allways use the stock rom I still no certified in google.
Someone can help me?
pmsfcruz said:
Hello guys.
Today I did it successfully the root of my Oneplus 5 with magisk. But I have a problem. Even with root hide I can't install netflix. Google Play show me not certified. I allready wipeout everthink remove the root install the stock remove, I allways use the stock rom I still no certified in google.
Someone can help me?
Click to expand...
Click to collapse
I think its shows not certified because you unlocked the bootloader.
Thx for aswer. Yes I allready try to lock back but the phone dont boot again.
pmsfcruz said:
Thx for aswer. Yes I allready try to lock back but the phone dont boot again.
Click to expand...
Click to collapse
Do a data factory reset in recovery and then reboot.
gee2012 said:
Do a data factory reset in recovery and then reboot.
Click to expand...
Click to collapse
Well, that's a bit... drastic, isn't it?
I have my op5 rooted with magisk (latest beta version) and i can download netflix and google play doesn't say "uncertified".
If you got magisk hide working (i.e. safety net check inside magisk manager is all green), just go to settings -> apps -> google play and clear its data!
You shouldn't see "uncertified" anymore in google play and you should be able to download netflix (I am).
Ok. I allready do that many times. So I lock first and then do data factory or after reset i lock bootloader? Sorry my question but I allready try everthink.
You don't need to relock the bootloader in order for Magisk hide to work, in fact it's a very bad idea to relock the bootloader with a custom recovery installed. What you need to do first is wipe everything and start from scratch.
Once you have the latest OOS 4.5.5 and everything working properly, download the latest stable twrp from here and download the latest beta of Magisk from here (version c4377ed) and put it in a folder on your phone from where you usually flash files via TWRP.
Boot into bootloader and flash TWRP then boot into TWRP, from there wipe Dalvik and cache, then flash Magisk and wipe Dalvik and cache one more time then reboot into system. Once you booted up, open Magisk manager and hit the safetyNet check, if you get green checkmarks, you're done. If not, go into settings and see if Magisk hide is activated, if it isn't check it and then do the safetyNet check again. If Magisk hide is activated, then deactivate and reactivate it again and then go back and do the safetyNet check again, and it should be good to go.
I did all those things I told you and as you can see from the pictures I have Netflix working no problem.
HueleSnaiL said:
You don't need to relock the bootloader in order for Magisk hide to work, in fact it's a very bad idea to relock the bootloader with a custom recovery installed. What you need to do first is wipe everything and start from scratch.
Once you have the latest OOS 4.5.5 and everything working properly, download the latest stable twrp from here and download the latest beta of Magisk from here (version c4377ed) and put it in a folder on your phone from where you usually flash files via TWRP.
Boot into bootloader and flash TWRP then boot into TWRP, from there wipe Dalvik and cache, then flash Magisk and wipe Dalvik and cache one more time then reboot into system. Once you booted up, open Magisk manager and hit the safetyNet check, if you get green checkmarks, you're done. If not, go into settings and see if Magisk hide is activated, if it isn't check it and then do the safetyNet check again. If Magisk hide is activated, then deactivate and reactivate it again and then go back and do the safetyNet check again, and it should be good to go.
I did all those things I told you and as you can see from the pictures I have Netflix working no problem.
Click to expand...
Click to collapse
Thank you very much for this post, was very helpful throughout the whole process. :good:
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.