Hello, the purpose of this guide is to show how to retain functionality after doing a factory reset on every ROM.
The problem is that the preinstalled gapps may not be working (login not possible), even after enabling and setting autostart in MiAssistant. Therefore some guides (e.g. this newest one) recommend flashing a working ROM, setting up GApps and afterwards flashing a new ROM without any wipe.
But those who simply want to factory reset can be helped with this guide. This also may make the intermediate step of GApps installaion unnecessary.
microG replaces Google Play Services, Framework and LocationProvider, ALL other GApps are working as expected afterwards.
In TWRP backup your current installation (important if any bootloop occurs)
Factory Reset, Reboot, do basic setup (device name, etc) and select language in MoreLocale if needed
Download, Flash and Wipe Cache + Dalvik Afterwards:
Magisk ONLY if you have a unpatched boot.img meaning no previous supersu installation (to obtain root while passing safety net)
-if the installation of Magisk failed please perform another Factory Reset before continuing (otherwise NanoDroid won't install correctly)-
OTHERWISE SuperSU and Xposed Framework (link for Android 6, SDK23)
NanoDroid fdroid (fdroid plus modified play store)
NanoDroid microG (migroG plus removes unneccessary Google stuff)
NanoDroid patcher to allow signature spoofing not working on odexed roms, we solve that with (Magisk-)Xposed-FakeGapps
Reboot, launch fdroid, let it update its repository and install FakeGapps, XposedInstaller (+ if installed, in Magisk XposedFramework)
In Xposed download XposedGmsCoreUnifiedNlp and enable all installed Modules
In Mi Assistant enable all apps to auto start
Restart, then login into Google to see if that works, otherwise check if Xposed modules are enabled and working, restart and try again, if still not working try disabling and reenabling the concerned app (e.g. Play Store)
Furthermore a selftest can be done in microG settings and you can check if Nlp is working in a Maps App of your choice
Unnecessary Apps CAN be frozen (recommended with AirFrozen) or uninstalled (only if 100% sure and backuped)
Q&A:
Contacts Sync is not working / crashing: Try reinstalling the Google Sync Adapters with the flashable zip from here, set the additional permissions in App Settings
Whatever I do google just wont let me purchase anything.
When I try direct carrier billing it tells me that my account is risky.
When I try to use my credit card it tells me the card's been declined.
How do I know my account or phone has been blocked by google play?
It's because I went as far as using my laptop and creating a google account on it and then registering my credit card on the google play account via chrome and it worked!
I linked the new account that's has been linked to my credit card to my phones playstore and it still wouldn't allow me to buy in app purchases.
Is there anyway to reset my phone so google can let me make in apps again? Would a factory reset work?
I
blitzball said:
Whatever I do google just wont let me purchase anything.
When I try direct carrier billing it tells me that my account is risky.
When I try to use my credit card it tells me the card's been declined.
How do I know my account or phone has been blocked by google play?
It's because I went as far as using my laptop and creating a google account on it and then registering my credit card on the google play account via chrome and it worked!
I linked the new account that's has been linked to my credit card to my phones playstore and it still wouldn't allow me to buy in app purchases.
Is there anyway to reset my phone so google can let me make in apps again? Would a factory reset work?
Click to expand...
Click to collapse
Is this really a phone issue or issue with your Google account - have you eg tried from another Android phone with the same Google acc?
If you think it is phone issue, you didn't specify firmware you are running
- if stock, its full build name (to see also are you on MM, N or O)
- or some custom ROM
Is it rooted and how
- old, no more updated/supported SuperSU
- or Magisk
If Magisk, which version and does SafetyNet passes (all green)?
Btw, in Playstore, does it pass Play Protect, and in its Settings (last item) is Device Certified?
zgfg said:
I
Is this really a phone issue or issue with your Google account - have you eg tried from another Android phone with the same Google acc?
If you think it is phone issue, you didn't specify firmware you are running
- if stock, its full build name (to see also are you on MM, N or O)
- or some custom ROM
Is it rooted and how
- old, no more updated/supported SuperSU
- or Magisk
If Magisk, which version and does SafetyNet passes (all green)?
Btw, in Playstore, does it pass Play Protect, and in its Settings (last item) is Device Certified?
Click to expand...
Click to collapse
Both the phone and the account tbh. I tried said account on my laptop and it ran into the same error my phone had ran into - which is the inability to link any sort of credit card to it.
Even tried removing all my accounts, wiping playstore and all of the other google related apps of their data, and then making a fresh new account. It worked for maybe ten or fifteen minutes which was weird and then the account started having the error the previous accounts did.
Emui 5.0.1
Android 7.0
Build is an L19B393
It's rooted
Supersu
Yep it passes play protect and it's certified.
blitzball said:
Both the phone and the account tbh. I tried said account on my laptop and it ran into the same error my phone had ran into - which is the inability to link any sort of credit card to it.
Even tried removing all my accounts, wiping playstore and all of the other google related apps of their data, and then making a fresh new account. It worked for maybe ten or fifteen minutes which was weird and then the account started having the error the previous accounts did.
Emui 5.0.1
Android 7.0
Build is an L19B393
It's rooted
Supersu
Yep it passes play protect and it's certified.
Click to expand...
Click to collapse
Even if Play Protect passing, it automatically sends info about your (rooted) configuration to Google, so better disable it.
What about SafetyNet?
There are dedicated and more detailed checkers but you can also find it in some Root checkers like
https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker
With SuperSU you might need SuHide to pass SafetyNet, but that's why Magisk is better, it knows how to hide root and to pass SafetyNet
zgfg said:
Even if Play Protect passing, it automatically sends info about your (rooted) configuration to Google, so better disable it.
What about SafetyNet?
There are dedicated and more detailed checkers but you can also find it in some Root checkers like
https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker
With SuperSU you might need SuHide to pass SafetyNet, but that's why Magisk is better, it knows how to hide root and to pass SafetyNet
Click to expand...
Click to collapse
Yeah my phone fails at the SafetyNet check. Is there a guide on how to go from Supersu to Magisk?
blitzball said:
Yeah my phone fails at the SafetyNet check. Is there a guide on how to go from Supersu to Magisk?
Click to expand...
Click to collapse
You can Google but installation of Magisk for Huawei is specific (at least for Oreo, maybe also for Nougat).
First you need to get rid of SuperSU:
- Use its Uninstall/Remove root option and then reboot
- It should clean the Boot and System partitions from SuperSU changes
- If you made root changes in Data partition, you will need Factory Reset from Recovery
It will be safer that you also flash the clean7stock Boot partition:
- Download FullOTA update.zip from Firmware Finder, corresponding to your current firmware
- Unzip, open update.app in Huawei Update Extractor (PC app) and extract Boot.img
- Flash Boot.img in Fastboot or TWRP
(Ideally, you should reinstall stock firmware if you have had issues when installing SuperSU and left some mess in System from that time)
Second, about the installation of Magisk you can read this post (more info about Magisk in that thread):
https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
In short, you need to:
- Install latest Magisk Manager v6.01 (find it eg from the XDA Magisk thread above) and open it
- It will ask to install Magisk v17.1, decline and then check-in Preserve Force Encryption option
- Then click to install Magisk but instead of Direct Install take the option to patch Boot partition
- Navigate to the stock boot.img file (instructions above how to get it)
- Patched Boot will be saved to Downloads on Internal mem
- Flash that patched Boot, reboot, open Magisk Manager and let it complete the Magisk v17.1 installation
- Reboot, open Magisk Manager and trigger SafetyNet checking, allow it to install the needful
zgfg said:
You can Google but installation of Magisk for Huawei is specific (at least for Oreo, maybe also for Nougat).
First you need to get rid of SuperSU:
- Use its Uninstall/Remove root option and then reboot
- It should clean the Boot and System partitions from SuperSU changes
- If you made root changes in Data partition, you will need Factory Reset from Recovery
It will be safer that you also flash the clean7stock Boot partition:
- Download FullOTA update.zip from Firmware Finder, corresponding to your current firmware
- Unzip, open update.app in Huawei Update Extractor (PC app) and extract Boot.img
- Flash Boot.img in Fastboot or TWRP
(Ideally, you should reinstall stock firmware if you have had issues when installing SuperSU and left some mess in System from that time)
Second, about the installation of Magisk you can read this post (more info about Magisk in that thread):
https://forum.xda-developers.com/showpost.php?p=77560239&postcount=27389
In short, you need to:
- Install latest Magisk Manager v6.01 (find it eg from the XDA Magisk thread above) and open it
- It will ask to install Magisk v17.1, decline and then check-in Preserve Force Encryption option
- Then click to install Magisk but instead of Direct Install take the option to patch Boot partition
- Navigate to the stock boot.img file (instructions above how to get it)
- Patched Boot will be saved to Downloads on Internal mem
- Flash that patched Boot, reboot, open Magisk Manager and let it complete the Magisk v17.1 installation
- Reboot, open Magisk Manager and trigger SafetyNet checking, allow it to install the needful
Click to expand...
Click to collapse
I have a TWRP backup of the stock boot.img. Would that work? It's in a .win format though and there are two files not sure how to convert them into .img.
Here's the exact names of the files:
boot.emmc.win
boot.emmc.win.md5
blitzball said:
I have a TWRP backup of the stock boot.img. Would that work? It's in a .win format though and there are two files not sure how to convert them into .img.
Here's the exact names of the files:
boot.emmc.win
boot.emmc.win.md5
Click to expand...
Click to collapse
TWRP backup that can be restored through TWRP (Restore option in TWRP)
zgfg said:
TWRP backup that can be restored through TWRP (Restore option in TWRP)
Click to expand...
Click to collapse
Thanks man. I'll go ahead and install magisk
zgfg said:
TWRP backup that can be restored through TWRP (Restore option in TWRP)
Click to expand...
Click to collapse
Dude so I installed it with no problems but I still can't pass safety net
blitzball said:
Dude so I installed it with no problems but I still can't pass safety net
Click to expand...
Click to collapse
As I wrote above, restore-reinstall + Factory reset complete stock firmware to get rid of SuperSU
With clean stock SafetyNet passes.
If it doesn't pass, you don't have clean and don't wastw time installing Magisk - first you must have clean basis
zgfg said:
As I wrote above, restore-reinstall + Factory reset complete stock firmware to get rid of SuperSU
With clean stock SafetyNet passes.
If it doesn't pass, you don't have clean and don't wastw time installing Magisk - first you must have clean basis
Click to expand...
Click to collapse
It's working now dude. I passed the safetynet! I still have one issue though... Even though I passed it, Netflix is still not available on my google playstore.
blitzball said:
It's working now dude. I passed the safetynet! I still have one issue though... Even though I passed it, Netflix is still not available on my google playstore.
Click to expand...
Click to collapse
Don't know, not using NetFlix. Make sure that PlayProtect and Device Certified pass in Playstore
zgfg said:
Don't know, not using NetFlix. Make sure that PlayProtect and Device Certified pass in Playstore
Click to expand...
Click to collapse
I have Netflix now. It's weird though cause only after maybe ten or twenty minutes did it show up in my store. Still can't buy anything though google still detects my phone for some reason. Thanks anyways.
Running Resurrection Remix on a Oneplus One. Starting today the KBC banking app (com.kbc.mobile.android.phone.kbc) started blocking rooted phones.
Using Magisk v19.0 - Magisk Manager v7.1.1
Tried everything I could find:
Hid the banking app
Hid the magisk manager
Enabled magisk core only
Disabled android debugging
And rebooted in between steps, deleted app and reinstalled, SafetyNet passes everything... yet this KBC banking app still detects root.
Any suggestions what I could try next?
You can try this :
https://forum.xda-developers.com/showpost.php?p=77331765&postcount=99
Or mabye this will help :
https://forum.xda-developers.com/apps/magisk/banks-app-detects-root-update-v18-0-t3877412/page5
downgrade your Google play services
Sent from my Pixel 2 XL using Tapatalk
It's likely something with your ROM. I tested on my OnePlus 3T, ArrowOS (Android Pie), and all that was needed for the app not to detect root was to add it to the Hide list and repackage the Manager.
tomzorz88 said:
Any suggestions what I could try next?
Click to expand...
Click to collapse
As of 09/04 KBC also stopped working for me. (Magisk 18.1)
After a lot of trial and error, here's what helped for me:
1) Remove KBC Mobile
2) Remove Magisk Manager and Magisk by flashing the uninstaller
3) Reboot to recovery
4) Flash Magisk 19.0 beta and reboot
5) Install latest Magisk Manager
6) Magisk Hide Google Play
7) Install KBC Mobile but do not run it!
8) Magisk Hide KBC Mobile
9) Repack Magisk Manager
10) Reboot
Fully working again.
Good luck!
Gamm86 said:
As of 09/04 KBC also stopped working for me. (Magisk 18.1)
After a lot of trial and error, here's what helped for me:
1) Remove KBC Mobile
2) Remove Magisk Manager and Magisk by flashing the uninstaller
3) Reboot to recovery
4) Flash Magisk 19.0 beta and reboot
5) Install latest Magisk Manager
6) Magisk Hide Google Play
7) Install KBC Mobile but do not run it!
8) Magisk Hide KBC Mobile
9) Repack Magisk Manager
10) Reboot
Fully working again.
Good luck!
Click to expand...
Click to collapse
Sadly didn't work for me.
I'm guessing you use another ROM than Resurrection Remix?
tomzorz88 said:
Sadly didn't work for me.
I'm guessing you use another ROM than Resurrection Remix?
Click to expand...
Click to collapse
OnePlus 3 - HavocOs v2.4
Gamm86 said:
As of 09/04 KBC also stopped working for me. (Magisk 18.1)
After a lot of trial and error, here's what helped for me:
1) Remove KBC Mobile
2) Remove Magisk Manager and Magisk by flashing the uninstaller
3) Reboot to recovery
4) Flash Magisk 19.0 beta and reboot
5) Install latest Magisk Manager
6) Magisk Hide Google Play
7) Install KBC Mobile but do not run it!
8) Magisk Hide KBC Mobile
9) Repack Magisk Manager
10) Reboot
Fully working again.
Good luck!
Click to expand...
Click to collapse
I just ran through this procedure and can confirm KBC Mobile works again. Thanks @Gamm86 and @Didgeridoohan!
A bit of context: KBC locked their app today April 24th, I had called a few weeks back to complain my phone was still marked as rooted (they do periodic checks it seems, and their database isn't refreshed daily), while it was not (at least not the way it used to be :angel: ).
@tomzorz88 Using a LOS 15.1 (Android 8.1.0) build here. CtsProfile checks out for you? If not check https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228.
I just ran through this procedure from 6) and can confirm KBC Mobile works again on custom ROM.
Thank you @Gamm86 and @Didgeridoohan
.:B:. said:
@tomzorz88 Using a LOS 15.1 (Android 8.1.0) build here. CtsProfile checks out for you? If not check https://forum.xda-developers.com/apps/magisk/module-magiskhide-props-config-t3789228.
Click to expand...
Click to collapse
@.:B:. The CtsProfile and every safety test did check out fine, but never got the KBC to work again.
Just now did a clean install of ArrowOS v9 , without Magisk, and all banking apps including KBC are working like a charm again. If I need Magisk again in the future I'll try aforementioned steps again, but currently no need.
Thanks anyway @Gamm86 and everyone else!
NONE OF THESE ARE MY WORK, THANK THE DEVELOPERS
YOU NEED ASHYX TWRP - https://forum.xda-developers.com/ga...overy-twrp-3-1-0-1-samsung-galaxy-j3-t3573607
BEFORE STARTING - Some apps like Pokemon Go detect BusyBox apps, Xposed Installer and the Magisk Manager. Enable the general Magisk Hide as well Magisk Hide for the specific app in Magisk Manager. Activate in Magisk Manager 'Repackage Magisk Manager with random package name.'
Then you have to try renaming the package name of the Xposed Installer apk with APK Editor or something else.
STEP 1 - Download the Magisk 18.0 zip and move to External SD Card - http://www.mediafire.com/file/4rmzov...%29.zip/file.
STEP 2 - Install the Xposed Installer app but DO NOT INSTALL IT FROM THE APP, YOU WILL GET SOFT BRICKED - https://forum.xda-developers.com/showthread.php?t=3034811
STEP 3 - Download the generic Samsung Xposed zip and uninstaller by wanam and move to External SD Card - https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960.
STEP 4 - Uninstall Xposed completely if you had it already.
STEP 5 - Unroot in SuperSU. MAKE SURE YOU SELECT 'RESTORE STOCK BOOT IMAGE' OR YOU WILL HAVE TO REFLASH THE BOOT IMAGE FROM ODIN.
STEP 6 - Reboot to TWRP and flash the Magisk zip. Reboot to system and wait a while, make sure everything is working properly.
STEP 7 - Reboot to TWRP and flash the generic Samsung Xposed zip.
STEP 8 - Reboot to system and and wait a while, make sure everything is working properly. Enable in the Xposed Installer 'No Device Check' or download it - https://forum.xda-developers.com/xposed/modules/xposed-device-check-t3199705.
STEP 9 - Install BusyBox and then delete any BusyBox app.
Now you should pass SafetyNet.
Update New vendor <testing> coming soon
===================================
Download latest pixel A only 10 link: https://mirrors.lolinet.com/firmware/gsi/
File Name: Pixel-Aonly-10-20190612-ErfanGSI.img.7z ---extract first
Mokee's TWRP https://pan.baidu.com/s/1HgjIWw2WPdnNEdpMN2GCTw#list/path=/
TWRP-20190117-3.2.3.0-4-clover.img
Latest Clover Firmware
https://xiaomifirmwareupdater.com/?...3owHAYMSc0RWndHIcbfKu9_nIGXpmTc#weekly#oxygen
---------------------------------------------------------------------------
https://mega.nz/#F!sfAQyKiY!iXgTnAdp4pbNav-2zjomng
Vendor.zip
bl_pie_vendor-cam-n-logofix.zip
lagfix-for-a_and_ab.zip
Permissiver_v4.zip
FixZygote_v2.zip
Google Play services
Google Play store
play store - https://is.gd/m3mJBL
play services - https://is.gd/Eh8x0d
(arm64-v8a + armeabi-v7a android 9+ Nodpi)
----------------------------------------------------------------
Step guide
1. Clean All
2. Flash latest Clover firmware (and also twrp for pie fw)
3. Flash vendor.zip
4. Flash android Q gsi image
5. Flash lagfix-for-a_and_ab.zip
6. Flash Permissiver_v4.zip
7. Flash FixZygote_v2.zip
8. Flash Magisk 19.4.zp
9. Reboot
10. Forced close ,back to TWRP ,flash bl_pie_vendor-cam-n-logofix.zip
11. Setup android
12.install google play services , and google ply store
13. setup fingerprint
14. use any file manager with root and edit /vendor/build.prop file
-add this line at the end
persist.vendor.camera.HAL3.enabled=1
reboot. camera 2 api is now enabled.
******Note Bootloop at LOGO ---forced close and flash with bl_pie_vendor-cam-n-logofix.zip
not support exFAT
support F2FS
Thanks
Where can I find Google Play services and Google Play store ?
z1022 said:
Thanks
Where can I find Google Play services and Google Play store ?
Click to expand...
Click to collapse
https://mega.nz/#F!sfAQyKiY!iXgTnAdp4pbNav-2zjomng
Thanks
But is there any gcam working?
could not get past bootlop using latest gsi
Yanghbr said:
could not get past bootlop using latest gsi
Click to expand...
Click to collapse
Forced close ,back to TWRP ,flash bl_pie_vendor-cam-n-logofix.zip again