Just flashed cm-13.0-20151114-UNOFFICIAL-titan.zip on my XT1068 and that boots OK, I can also call and data seems to work.
If I install open_gapps-arm-6.0-pico-20151118.zip after reboot there's only the message "Unfortunately, Setup Wizard has stopped" and I can't continue...
Any clues?
flash slim zero gapps
https://www.androidfilehost.com/?fid=24269982086998389
daywalk3r666 said:
flash slim zero gapps
https://www.androidfilehost.com/?fid=24269982086998389
Click to expand...
Click to collapse
First updated to 20151117 which didn't change anything
Then
Factory reset
Install 20151117
Install Slim Zero GApps
Which resulted in the original message
Code:
Unfortunately, Setup Wizard has stopped
and now alternated with message
Code:
Unfortunately, Google Play Services has stopped
showing very briefly (could've been there before as well
spiloss said:
First updated to 20151117 which didn't change anything
Then
Factory reset
Install 20151117
Install Slim Zero GApps
Which resulted in the original message
Code:
Unfortunately, Setup Wizard has stopped
and now alternated with message
Code:
Unfortunately, Google Play Services has stopped
showing very briefly (could've been there before as well
Click to expand...
Click to collapse
After
* Factory reset
* Install 20151117
the FC of Setup Wizard just comes back. Anything else I need to do to remove GApps when flashing?
spiloss said:
Just flashed cm-13.0-20151114-UNOFFICIAL-titan.zip on my XT1068 and that boots OK, I can also call and data seems to work.
If I install open_gapps-arm-6.0-pico-20151118.zip after reboot there's only the message "Unfortunately, Setup Wizard has stopped" and I can't continue...
Any clues?
Click to expand...
Click to collapse
Why did you make a new thread instead of asking in the main CM13 unofficial thread?
Ragarianok said:
Why did you make a new thread instead of asking in the main CM13 unofficial thread?
Click to expand...
Click to collapse
Sorry for the n00bness! Will close and add the Q to the unofficial thread!
[FIX] Setup Wizard Stopped Working
1. After Flashing gapps go lock the screen
2.Unlock screen and drag setting from above it selt
3. You will get notification "Unfortuantlley stopped" click ok in while of gap slide down (repeat it till you find apps)
4. open apps and click on three dot menu and click show system apps
5.go to last scroll down you will find Setup Wizard with Cm Logo and with CM Logo
6. Select with one without CM Logo and give permissions
7. Done Enjoy!!!!!
HostZero said:
1. After Flashing gapps go lock the screen
2.Unlock screen and drag setting from above it selt
3. You will get notification "Unfortuantlley stopped" click ok in while of gap slide down (repeat it till you find apps)
4. open apps and click on three dot menu and click show system apps
5.go to last scroll down you will find Setup Wizard with Cm Logo and with CM Logo
6. Select with one without CM Logo and give permissions
7. Done Enjoy!!!!!
Click to expand...
Click to collapse
When I try to give the permissions, android says "Screen overlay detected- To change this permission setting you first have to turn off the screen overlay from Settings > Apps".
Can't continue...
Yesterday just got the same issue.
Wipe dalvik, cache, system ( but dont touch internal storage)
Install - choose CM zip, add another package - add OpenGapps Pico - flash - reboot. Voila.
Be sure to skip cache/dalvik wipe and just reboot
Hi everyone,
I am looking for a solution to recover my Samsung Galaxy S7 (SM-G930FD) from a bootloop, without TWRP. I have read through many posts to find a solution, but not have worked for me. Please read the full details before offering a solution.
- I rooted my phone, successfully, using CF Auto Root (via Odin). It was working fine for several days
- I installed Hide My Root from the Google Play Store, which did not work
- I installed XposedInstaller_3.0-alpha4.apk
- I installed TWRP Manager from the Google Play Store
- I installed BusyBox from the Google Play Store
- I downloaded xposed*.zip (xposed-v86-sdk23-arm64.zip) and xposed-uninstaller*.zip (xposed-uninstaller-20150831-arm64.zip)
- I installed TWRP. I did a lot at once, so some steps are a little fuzzy right now.
- I booted into recovery mode (TWRP) and completed a backup for the data, to the SD card.
- In recovery mode, I then selected BOTH zip files for install. Once that completed, the phone restarted and stuck at the Samsung logo.
- I booted into download mode and tried CF Auto Root again, with no success.
- I booted into recovery mode, but TWRP does not seem to appear. It goes to the default Android Recovery with the following options:
> Reboot system now (did not help)
> Reboot to bootloader (did not help)
> Apply update from ADB ("Update from external storage is disabled")
> Apply update from SD card ("Update from external storage is disabled")
> Wipe data/factory reset (did not help)
> Wipe cache partition (did not help)
> Mount /system (did not appear to do anything)
> View recovery logs (lists various logs)
> Power off (turns off phone)
Specifications:
- Samsung Galaxy S7 (SM-G930FD)
- Dual Sim
- International
- Exynos 8890 Octa-Core
- Android 6.0 (Marshmallow)
If you need any additional information that will help you determine a solution, I will attempt to provide to you what I can. I am only looking for possible solutions from the point in which I am at now, not what I did wrong or the correct way to go about doing it. It's a little too late for that now, isn't it?
Thank-you in advanced,
Brandon
SOLUTION
A friend of mine suggested using Smart Switch, which failed, but I was able to come up with a solution from that. Here are the steps I took to bring my phone back to life.
1) Download Samsung Smart Switch and run it
2) From the top right, select "MORE," followed by "Emergency software recovery and initialization
3) Fill in the required information, including the model number and serial number of your device, followed by the OK button
4) Attempt to complete the process vis Smart Switch first
Note: Keep your phone in a cool place, since the screen does stay on the entire time.
If this fails AFTER the download completed (it did for me):
5) Locate the files that were downloaded. On Windows this will be on your system drive under "Users\*user*\AppData\Local\Temp\tmp****", where tmp**** contains random characters. The easiest way to find the name is to sort by date created or modified and look for a large file with a similar name. Now locate the folder starting with the same name. Within this folder there should be 5 files. Copy them all to an alternate location. You will only need the AP file, but you may wish to use the others.
6) Disconnect the phone from your computer
7) Uninstall Smart Switch, Kies, and the Samsung Drivers (if installed)
8) Download the latest version of Odin
9) Restart your computer and reboot the phone into Download mode (Vol Down + Power + Home) => Vol Up on prompt
10) Reinstall Samsung Drivers
11) Run Odin and click the AP button and locate the file you saved, starting with "AP_"
12) Plug in your phone, click Start, and wait for the process to complete.
I hope this helps anyone else looking for a solution, as I have not found this anywhere else online. :good:
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
How did you install Magisk?
When I open Magisk Manager v5.6.4, I get a "Magisk is not installed" and I only have the settings option.
No "install" options.
I have the same tablet. don't know of any twrp that can work with it, therefore leaving me with Magisk Manager only.
Id' be glad to get some help
Thanks,
SOLVED: You must have a functioning network interface in order for the "install" button to appear and you need internet connection to "install the v16 zip".
Magisk is OpenSource though, right? so probably it can be changed to allow offline installation as well.
Rooteed
Well Crap...I just got my Nice, New, Sparkleing Tab Active2 and cant root it yet. I have the New US version SM-T397U Unlocked model. cant find a Stock firmware on Sammobile as of yet...any ideas?
EDIT: Neeeevermind... I did a lil hacking and cracking (for about 26min, lol) to find the files I needed for the SM-T397U. If anyone is looking for em let me know and I'll shoot em' your way. Guessing I'm the first person to root a T397U, hope more will follow. I havent even had this thing 6 hours yet. Thanks for the write up and all those that contributed to the tools and info!
I followed every steps till the end and everything went smoothly. But once I rebooted the tablet, I got the red label on the top left corner: "custom binary blocked by OEM lock". The tablet won't boot properly anymore "OEM unlock" was enabled in the Developers options, I double checked to be sure before flashing.
Edit:
Actually, the "custom binary blocked by OEM lock" appears as soon as I modify the system partition (I wanted to modify the Generic.kl in the keylayout folder on the system partition). If you do not touch anything, everything is fine.
[X-POST from here ]
Worked perfectly, Thank you very much!
WARNING: THIS WILL WIPE EVERYTHING ON YOUR TABLET.
Backup all of your important files before you flash the patched boot.img using odin.
I tried to backup my app data using samsung switch and it worked, but didn't restore most of my device settings and all of my app data.
(Good thing I kept backups for my important apps that had in app backup functionality - like Nova launcher and Squid)
Keep in mind that you probably won't be able to get OTA updates after you perform these steps, it doesn't matter though since this tablet isn't going to be updated that frequently (The 8.0 update is going to come at the end of 2018, source)
Hello.
I tried this but when i using the magisk manager i have an error meassage and the following log:
- Copying image to cache
- Device platform: armeabi-v7a
- Existing zip found
1038+1 records in
1038+1 records out
1063528 bytes transferred in 0.022 secs (48342181 bytes/sec)
- Unpacking boot image
MagiskBoot v18.1(18100) (by topjohnwu)
- Boot Image Modification Tool
mmap failed with 12: Out of memory
! Unable to unpack boot image
! Installation failed
Can you help what i did wrong?
Thank you
oem unlock does not appear
SOLUTION FOUND
how do you oem unlock
I have wasted hours on this, waited weeks, tried the date trick with a legit setup, but the oem unlock never appears, running oldest version of firmware 7.1.1 feb 2018, what gives?
Tried reinstalling firmware via odin, successful flash but no factory reset. Suspect this made no difference. Got the security fail on PIT error, needed a new version of odin and selecting individual AP etc. files fixed this.
apparently you need a samsung or google account
So trying a samsung account... no dice
Now trying adding a sim card as well... success
OK after months of waiting and trying things, this just worked!
Update- I lost the date trick, have to wait 7 days after step 7 on auto date, just appears in developer options no need to press manual update.
https://forum.xda-developers.com/galaxy-s8+/how-to/guide-how-to-skip-rmm-prenormal-install-t3749468
- try downloading UK rom which was released before december '17 (october)
See if it lets the below process work again?
0/ install sim card (was not even the original carrier one in my case although my phone is not carrier locked)
1/ factory reset
2/ on reboot skip all accounts, do not enter a name do not turn on wifi, accept minimal amounts of things
3/ set date to 1/4/19 - turn off automatic date
4/ turn off automatic software updates
5/ enable developer options and turn off auto update system
6/ turn on wifi (date changes)
6b/ change date back
7/ Install samsung account (I went to samsung cloud) (date not changed but software update now triggered despite not touching manual update)
8/ (for interest look at manually check for software updates - it already says 1/4/19 last checked)
9/ reboot
10/ (date is now changed back to today again without my permission)
11/ (it pops up asking to install an update, despite auto updates turned off. - LATER)
12/ (last checked software date is now today (because I left wifi on I think through a reboot) this is 4/5/19 over 1 month later)
13/ go to developer options for the 27868745# time
OEM UNLOCK APPEARED HOLY ****
It is between Bluetooth HCI snoop log and Running services on the dev page, top of the developer options
Since the RMM prenormal thing triggered I had to do this again, so the above instructions do work.
If you stuff up the date just factory reset and start again. Reflash not required
I used a brand new throwaway samsung account for this but thats possibly up to you.
RMM state prenormal
OK now that I've jumped through hoops, installed TWRP
I go to reboot and it's locked recovery again - repeat above OEM unlock reappearing act steps fixes RMM=prenormal. Now it's official again.
Apparently you need to install an RMM patch as well which is not mentioned in this thread.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
So, odin -> ap -> TWRP download
quickly press power-up-home when it resets!!!
recovery is not seandroid enforcing appears and TWRP starts.
1. back up all partitions to microsd!
2. install
a TWRP -> magisk
b TWRP -> RMM disabler - this writes to /system defeating the purpose of magisk???
wipe cache/dalvik reboot
on boot:
"Verification failed"
"Unable to restart your device the integrity verification has failed.... erase all your data"
Well recovery boots this time not an RMM error thats nice... oh it runs a few commands and automatically restarts again.
"Verification failed..."
I guess that is a boot loop then, thanks TWRP for not stopping at a menu ffs.
Reflash TWRP with odin, now it halts at TWRP menu.
https://forum.xda-developers.com/ga...t/how-to-recover-verification-failed-t3775722
Apparently I should put in download mode and cancel - Result = fail & TWRP bootloop -> reinstall TWRP
unmountable /data partition - yep thats me - could try format to exfat - ext4 - Result = Verification failed ffs
---------- Post added at 01:52 PM ---------- Previous post was at 01:00 PM ----------
Take 3
"Looks like you didnt flash encryption breaker." no-verity-no-encrypt_ashyx.zip or no-verity-opt-encrypt-6.0 zip well duh of course but which one for t395
https://www.androidinfotech.com/no-verity-opt-encrypt-versions/
seems a few up to 6.0
BTW if you don't press reset and instead try and reboot into recovery you don't have to reflash TWRP
Verification FAIL.
https://forum.xda-developers.com/galaxy-note-8/how-to/guide-how-to-root-device-encryption-t3742493
Take 4 - try reinstating boot.img with no mods.
Try flashing stock AP -> twrp -> DMM fix -> magisk in quick succession & booting tablet
Verification Failed! Reset
Goes to recovery - less errors on TWRP (no mount errors like before) but verification failed again.
Because TWRP is installed I don't get the erasing screen as described by OP....? TWRP does something very quickly I think it says formatting cache, it is doing a standard factory reset. Trying manual factory reset with TWRP does not work.
So I think I need TWRP to prevent DMM tripping and install magisk but I need stock recovery to avoid the verification failing constantly.
Or a new version of TWRP that supports encryption? 3230+ I have 3230...?
Try Stock RO system - twrp - dm verity - magisk
Verification failed. Reset - no dmm error thats nice. TWRP did some extra stuff.
Verification failed again.
#&%^&^#%$#[email protected]#%[email protected]#%#$%
Option 556
Install dmverity patch using stock recovery.
Gives error can't find /misc partition - pretty sure these are TWRP zips only.
Magisk website says install TWRP so I can't see how to avoid TWRP and this annoying verification fail. Maybe try an older version of magisk???
Verification bootloop FIX:?
I tried booting stock, it says something like data corrupt on start, looks the same as the verification failed but with the different message. I let it erase/factory reset with stock recovery.
DMM preload did not trigger on this!
As soon as it succeeded I installed TWRP in case DMM triggers.
Now with fixed data partition (presumably) retry TWRP
1. no verity patch (6.0)
2. magisk
cannot install DMM as it alters system partition...?
No cache wipe.
Lets see what happens...... Black screen but this time
'encryption failed' reset. Press reset.... TWRP does a factory reset
'encryption failed'
LOL now I have an encryption failed bootloop.
Reinstall stock and use stock factory reset again - boot to recovery straight away, wipe data & cache
Now install TWRP (not booted once yet)
Install verity patch 6.0
install magisk 19.1
Boot system for the first time. - got a bootloop? no just taking it's sweet time. Fingers crossed!
Android is starting... WELCOME
HOLY **** IT WORKED
DMM patch not installed and it hasn't tripped DMM yet (the old 7 day wait issue)
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
2/ flash stock AP - do NOT boot system yet
3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the first time
So I have not installed RMM patch (system untouched) but I did install the no encryption/dm verity patch.
It actually boots now.... will update if further problems
Interestingly OEM unlock has disappeared, so RMM must be prenormal so it will probably die on reboot. Argh. But everything is restoring OK for now. See what happens...
Magisk app auto installed and passes safetynet. Preserve force enctyption and AVB 2.0/dm-verity unchecked.
Annoyingly despite backing up all my messages to samsung they are not restoring past 20 april. Not the end of the world.
Skype keeps stopping.
Reboot and YES only officially released binaries are allowed to be flashed boot loop.
So lets do this again!
SUMMARY:
1/ ensure DMM is official and not preload, OEM unlocked etc with above post steps
8skip 2/ flash stock AP - do NOT boot system yet
8skip 3/ stock recovery - wipe data and cache
4/ download odin mode - install twrp-3.2.3.0-gtactive2lte-7.1.2.tar
5/ twrp - install no-verity-opt-encrypt-6.0.zip
6/ twrp - install magisk 19.1
7/ Boot system for the second time
Pretty sure I already tried this so it won't work. &^%#@&^$#$#%#$%@##%@
Oh great it has managed to install the update and now the date fix doesn't work. &^#%&^#$#@$%@#$
After waiting 7 days
1/ Use stock recovery factory reset, then immediately hold down-home-power download mode
2/ Odin TWRP, then immediately hold up-home-power to enter TWRP
2a/ TWRP swipe to allow modifications (for RMM patch)
3/ TWRP install RMM patch
4/ TWRP install no verity patch
5/ TWRP install latest Magisk
NB Magisk seems to install itself as an app - its just there.
...Safetynet pass despite RMM editing /system phew
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Driss35 said:
Hello,
With the last version of Magisk, we no longer have the setting to choose the output format as odin compatible tar.
How can we deal with this, please ?
Regards,
Click to expand...
Click to collapse
You don't have to choose any file type. Magisk scans files automatically.
Also, if your file type is ".lz4", you have to change it to ".img". Unless, you can't continue.
@Drnms thanks for this thread. But, some places have to be updated because of new Magisk versions.
Did App data remain after rooting
Drnms said:
First up - Let me say that the complete credit to the method goes to two members here as in the thread https://forum.xda-developers.com/galaxy-tab/help/galaxy-tab-active-2-forum-question-t3712591
BUT BUT BUT what the two experts have missed out is on explaining a clear step by step guide for a complete noob like me . So this is an attempt to explain every step. My tab had root in less than 10 mins .
why i needed the root ?
16gb is not enough for the tab so i wanted to apps and data to be moved to the sd card .
Here are the steps
On the Pc
1. Download the stock firmware (must be the same as in your tab) from samfirmware or any other source.
2. Extract the firmware and the extract archive called AP... . Once extracted you will have a boot.img file in it.
On the TAB
3. Activate developer options by clicking the software version 5 times.
4. In the developer options check OEM unlock and USB debugging
5. Download Magisk Manager v16 from xda and install on the TAB.
Connect the tab to the pc
6. Copy the boot.img file from pc to the tab.
7. Run Magisk Manager and in settings choose the output format as odin compatible tar,
8. Click the INSTALL button in the MAGISK manager and choose 'patch boot image file'
9. After a few minutes a dark screen will appear will read all ok boot image patched...now copy that patched_boot.img.tar file from the tab to the PC and rename it as boot.img.tar
On the Tab
10. Recheck under developer options if check OEM UNLOCK and USB DEBUGG
11. DELETE the GOOGLE account (crucial)
12. Switch of the tab
13. Go to download mode by holding vol down, menu and power together , once asked press vol up to go to the download mode.
14. Connect tab to PC.
On the PC
15. Download ODIN and once downloaded right click and run as administrator.
16. Choose AP and select the previously patched boot.img.tar file.
17. Click START
On the TAB
18. It will run the download and restart , restart will say "VERIFICATION FAILED and aask to RESET and erase .
19. CLICK RESET
20. wait for reset saying ERASING and let the tab restart.
NOW the next step is the most crucial one and it is where i got stuck as none of the members who have rooted their device mention it. I did all of the above procedures repeatedly and failed to get root until i realized there was one FINAL CRUCIAL STEP before enjoying the root.
LAST STEP
ON THE TAB
After the TAB restarts , fill in the initial details (google , samsung account, wifi etc) and before you do anything else INSTALL THE MAGISK MANAGER V16 app you downloaded from XDA .......thats it ....you have root access now . ENJOY!
Click to expand...
Click to collapse
Hi Dmms,
Please confirm if the data remained (i.e. was not erased) after the rooting?
Thanks in advance.
Hi, in case it is still relevant:
- Tab does a factory reset when booting first time after the boot img is flashed, data on the device is lost. Data on the SD card is not affected
- In my case, flashing boot.img with Odin didn't work. Odin said success, but no root. Heimdall worked fine, tab was rooted at first attempt
Does this guide also work for Android 9 ?
Edit: So it works with Android 9 also but I had to unpack the boot.img with 7zip ZS according to this post https://forum.xda-developers.com/t/samsung-a40-how-to-root.3929496/post-79902328
and re-pack it with normal 7zip according to these steps:
Do you have the boot.img.lz4 file to boot.img unpacked?
You have renamed the magisk_patched.img to boot.img?
You used the normal 7zip to package into a .tar file? Not the 7zZs?
You used the normal Odin 3.14?
Hello, did you manage to remove the "format as internal" lock?
Hi guys,
Trying to root this tablet, when I load the patched magisk file in Odin and perform the download. The tablet restarts and loads like normal but the tablet isn't rooted.
Any ideas?
alguma fortma?
I recently got this phone and first thing i tried to do is install new ROM, but everytime i boot into it i get Google Services Framework crash, android.process.media crash, and probably some other ones as well i couldn't see because of overlapping error messages.
I didn't do a "dirty install" - everything except internal storage was wiped, then fresh rom install, gapp install and cache wipe then reboot.
When i don't install gapps, i can boot into system but still android.process.media keeps crashing, and random applications i can open usually crash as well.
Did anyone encounter similiar problem?
I suspect you need to format not just wipe before you flash.
If flashing a custom rom other than miui -
download a new updated package of open gapps with the right android version for rom arm64bit package. I usually go micro.
Flash directly after rom before rebooting. A miui rom has gapps built in obviously so no need to flash
Sounds like you encounter strange issues because data was not wiped.
Try the LOS installation instructions step by step with any ROM you are going to use. Works for me.
Good luck!
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