Database Develop

[Guide] Suggested Install Guide for I9300 Omni 4.4 Nightlies

After following the Omni 4.4 Nightlies thread, I thought it would help some people (noobs like me) to have some guidance about how to install Omni in your device and making it easier to get what's needed to make it work. Still, this is not an "official guide", just the procedure I use to flash every day's nightly and I'm open to suggestions and corrections. Also, the resourses quoted here are not my work, just links to the work of the amazing devs in Xda and out there in the Android development world.
Hope it helps. Don't forget to hit "Thanks" in case it was.
Important: be wise and don't go for anything you are not sure about. I can't be held responsible for the results, remember that you are flashing a Custom (Beta stage) ROM, and even when not likely, things can go wrong. If you are unsure about anything, just ask and/or search the forum and the net for other's experience and knowledge, that's the way to go (and learn).
Suggested procedure (updated to November the 30th 2013)
Be sure to check the official thread for lastest news and guidance here.
DOWNLOADS
1) THE RIGHT RECOVERY - Your device must be rooted and running CWM Recovery 6.0.3.2+ or latest TWRP. Latest Philz Recovery is reported to be working too if you prefer. If aren't on CWM/Philz's or not on the right version, you can find a guide to get it and install it here. The safe way to go is to follow any of the procedures listed there. There are also many threads in XDA offering the flashable zip, but if you go down that way, be sure you choose the right version.
2) GET OMNI - Download the latest Omni 4.4 for I9300 Nightly here
3) GET GAPPS - Download the 4.4 Gapps of your choice:
PA Gapps (recommended by XpLoDWilD)
Spec Gapps
Banks Gapps
Any other 4.4 Gapps of your choice (must be 4.4, earlier versions won't work or give you some mean headaches)
4) CUSTOM KERNEL (optional) - If you want to use a custom kernel, download one that you know it's compatible. If you don't know what this means or you are not 100% sure about what you are doing, it would be safer to skip this step. You can explore Xda I9300 forum for info about Custom Kernels if you like.
5) UPDATE SUPERSU - Download the latest Supersu here. Get the Zip to be flashed via CWM. At the moment, the latest can be found here.
INSTALLING
1) If you had to install CWM or Philz, make sure it's done and working.
2) WIPING - Get into recovery. Be sure you make a nandroid backup in case things go wrong. Then, it's time for some wiping. The safer way to go is a Full Wipe, and that means Wiping Data, Cache, and Dalvik. Beware this will result in loosing some user data if you don't got a backup of them (I'd recommend moving anything you want to keep into SD, since Titanium is never a neat choice when flashing a new ROM, you'd probably get your beautiful clean new install dirty if you go that way). Back to wiping, I usually format /system too, just in case.
3) FLASH OMNI - Find and flash the downloaded Omni Build.
4) FLASH GAPPS.
5) FLASH CUSTOM KERNEL (optional) - if you've chosen to do so (should be done before flashing SuperSu Update).
6) FLASH SUPERSU UPDATE.
7) (Optional) Wipe Cache and Dalvik once more. I'm not sure if this is required, just found out it solved some FCs sometimes and since then I do it allways.
8) Reboot.
Post-Installing (Absolutely Optional, but maybe useful)
1) Once you've booted and are past the Gapps Google login and stuff, you might want to install Xposed Framework, in case you use Greenify Pro or just want to access some more customization moduldes. If that's what you want, get the latest 4.4 compatible XPosed Installer APK here and run it. There you need to install the framework and if no errors arise, voilá, you got it. It's reported that you need to set RW privileges to let this happen, if that's the case, you need any root explorer (ES or any other) to do it. And if you aren't able to do so, or still got trouble, you can install BusyBox Installer from the PlayStore, and duh, install it. Or you can just take the advice found here to get that done. Then you'll be able to get /system RW privleges and install Xposed Framework. After doing it, you'll need to reboot, thought.
2) Installing GravityBox or any other Xposed module you want. Gravity is a nice collection of customization options that has been updated recently to support Kitkat. If any others become compatible too, or you want to try any available module to see if it works with 4.4 too, assume the risks and go ahead. Yet, many will become compatible soon, perhaps it would be wiser to wait for that to happen. Back to Gravity, you just need to get it here (make sure to get the last version), install it, enable the Module at Xposed Installer, and reboot.
And that's it. Course you can do plenty of other stuff to your lovely Omni 4.4 Build, but that's up to you. Hope this was of some help and I'm open to any feedback to update the guide and make it better. And in case you spot any mistakes, please let me know. I'm not a dev, just a noob trying to make other noob's life easier.
Enjoy!

Very good guide
Inviato dal mio GT-I9300 utilizzando Tapatalk

Nicely done. Enough info for those who're new to omnirom (like me).
Sent from my GT-I9300 using Tapatalk

Question on Gravitybox. I've installed the Xposed installed, Gravitybox 2.7.6 and ticked on the module, the problem is when Gravitybox opens, it says that Gravitybox System Framework is not responding. What do you think I should do?
fermasia said:
After following the Omni 4.4 Nightlies thread, I thought it would help some people (noobs like me) to have some guidance about how to install Omni in your device and making it easier to get what's needed to make it work. Still, this is not an "official guide", just the procedure I use to flash every day's nightly and I'm open to suggestions and corrections. Also, the resourses quoted here are not my work, just links to the work of the amazing devs in Xda and out there in the Android development world.
Hope it helps. Don't forget to hit "Thanks" in case it was.
Important: be wise and don't go for anything you are not sure about. I can't be held responsible for the results, remember that you are flashing a Custom (Alpha stage) ROM, and even when not likely, things can go wrong. If you are unsure about anything, just ask and/or search the forum and the net for other's experience and knowledge, that's the way to go (and learn).
Suggested procedure (updated to November the 27th 2013)
Be sure to check the official thread for lastest news and guidance here.
DOWNLOADS
1) THE RIGHT RECOVERY - Your device must be rooted and running CWM Recovery 6.0+. Latest Philz Recovery is reported to be working too if you prefer. If aren't on CWM/Philz's or not on the right version, you can find a guide to get it and install it here. The safe way to go is to follow any of the procedures listed there. There are also many threads in XDA offering the flashable zip, but if you go down that way, be sure you choose the right version.
2) GET OMNI - Download the latest Omni 4.4 for I9300 Nightly here
3) GET GAPPS - Download the 4.4 Gapps of your choice:
PA Gapps (recommended by the op)
Spec Gapps
Banks Gapps
Any other 4.4 Gapps of your choice (must be 4.4, earlier versions will likely give you some headaches)
4) CUSTOM KERNEL (optional) - If you want to use a custom kernel, download one that you know it's compatible. If you don't know what this means or you are not 100% sure about what you are doing, it would be safer to skip this step. You can explore Xda I9300 forum for info about Custom Kernels if you like.
5) UPDATE SUPERSU - Download the latest Supersu here. Get the Zip to be flashed via CWM. At the moment, the latest can be found here.
INSTALLING
1) If you had to install CWM or Philz, make sure it's done and working.
2) WIPING - Get into recovery. Now it's time for wiping. The safer way to go is a Full Wipe, and that means Wiping Data, Cache, and Dalvik. Beware this will result in loosing some user data if you don't got a backup of them (I'd recommend moving anything you want to keep into SD, since Titanium is never a neat choice when flashing a new ROM, you'd probably get your beautiful clean new install dirty if you go that way. Back to wiping, I usually format /system too, just in case. Be sure you make a nandroid backup in case things go wrong.
3) FLASH OMNI - Find and flash the downloaded Omni Build.
4) FLASH GAPPS.
5) FLASH CUSTOM KERNEL (optional) - if you've chosen to do so (should be done before flashing SuperSu Update).
6) FLASH SUPERSU UPDATE.
7) (Optional) Wipe Cache and Dalvik once more. I'm not sure if this is required, just found out it solved some FCs sometimes and since then I do it allways.
8) Reboot.
Post-Installing (Absolutely Optional, but maybe useful)
1) Once you've booted and are past the Gapps Google login and stuff, you might want to install Xposed Framework, in case you use Greenify Pro or just want to access some more customization moduldes. If that's what you want, get the latest 4.4 compatible XPosed Installer APK here and run it. There you need to install the framework and if no errors arise, voilá, you got it. It's reported that you need to set RW privileges to let this happen, if that's the case, you need any root explorer (ES or any other) to do it. And if you aren't able to do so, or still got trouble, you can install BusyBox Installer from the PlayStore, and duh, install it. Or you can just take the advice found here to get that done. Then you'll be able to get /system RW privleges and install Xposed Framework. After doing it, you'll need to reboot, thought.
2) Installing GravityBox or any other Xposed module you want. Gravity is a nice collection of customization options that has been updated recently to support Kitkat. If any others become compatible too, or you want to try any available module to see if it works with 4.4 too, assume the risks and go ahead. Yet, many will become compatible soon, perhaps it would be wiser to wait for that to happen. Back to Gravity, you just need to get it at the PlayStore, install it, enable the Module at Xposed Installer, and reboot.
And that's it. Course you can do plenty of other stuff to your lovely Omni 4.4 Build, but that's up to you. Hope this was of some help and I'm open to any feedback to update the guide and make it better. And in case you spot any mistakes, please let me know. I'm not a dev, just a noob trying to make other noob's life easier.
Enjoy!
Click to expand...
Click to collapse

carlallanvela said:
Question on Gravitybox. I've installed the Xposed installed, Gravitybox 2.7.6 and ticked on the module, the problem is when Gravitybox opens, it says that Gravitybox System Framework is not responding. What do you think I should do?
Click to expand...
Click to collapse
Should I assume you: got an i9300, installed following the procedure, did all the wipes, are on the latest (27th) nightly, got the right Xposed Framework installed successfully with no errors, rebooted, installed gravity last version (2.7.6), enabled the gravity module, rebooted again? If so, and can't live without Gravity till next nightly, I'm not sure what else to suggest but reinstall from scratch and try again.

I got it. Looks like I used Xposed Firmware not Installer. Got it working.
fermasia said:
Should I assume you: got an i9300, installed following the procedure, did all the wipes, are on the latest (27th) nightly, got the right Xposed Framework installed successfully with no errors, rebooted, installed gravity last version (2.7.6), enabled the gravity module, rebooted again? If so, and can't live without Gravity till next nightly, I'm not sure what else to suggest but reinstall from scratch and try again.
Click to expand...
Click to collapse

carlallanvela said:
I got it. Looks like I used Xposed Firmware not Installer. Got it working.
Click to expand...
Click to collapse
Cheers :good:

fermasia said:
Cheers :good:
Click to expand...
Click to collapse
This is brilliant. Maybe add the list of known bugs and as they are fixed, you can cross them out, Would definately keep the main thread cleaner. Well done :good:

cornelha said:
This is brilliant. Maybe add the list of known bugs and as they are fixed, you can cross them out, Would definately keep the main thread cleaner. Well done :good:
Click to expand...
Click to collapse
Would be very interesting, but I guess it would be a bit tricky to keep up with known issues and resolution, unless there's somewhere I can check for that information. I guess that would be in the better hands of the devs that are after bugs and solutions on a daily basis. But still, if there's any way I can help keep track and inform about that, I'd be happy to help.

fermasia said:
Would be very interesting, but I guess it would be a bit tricky to keep up with known issues and resolution, unless there's somewhere I can check for that information. I guess that would be in the better hands of the devs that are after bugs and solutions on a daily basis. But still, if there's any way I can help keep track and inform about that, I'd be happy to help.
Click to expand...
Click to collapse
It's all over the Omni Thread. The devs are way too busy building the rom and sorting out bugs. The most common ones relate to Google Services battery drain. Camera issues and root.

cornelha said:
It's all over the Omni Thread. The devs are way too busy building the rom and sorting out bugs. The most common ones relate to Google Services battery drain. Camera issues and root.
Click to expand...
Click to collapse
I'll try to build a list of those, but I believe it wouldn't be serious to post it if not very precise and up-to-date. Think it's a great idea, but again, not having access to de development roadmap, is a big drawback, and I wouldn't want to go around pushing confusing info.

Problems with Root
After I flashed the 15Dec Build, suddenly I found I'm having problems with Root.
I'm flashing SuperSU 1.75 and RootChecker won't finish.
Xposed Framework won't install, etc.
I've trued the RW trick mentioned above but never get a response to 'su'.
Root worked fine prior to this build.
Any easy fix?

harrybarracuda said:
After I flashed the 15Dec Build, suddenly I found I'm having problems with Root.
I'm flashing SuperSU 1.75 and RootChecker won't finish.
Xposed Framework won't install, etc.
I've trued the RW trick mentioned above but never get a response to 'su'.
Root worked fine prior to this build.
Any easy fix?
Click to expand...
Click to collapse
You've got the wrong SuperSU version. See that the guide redirects you to Chainfire's SuperSU Xda thread, and there you'll find the latest recovery flash version is 1.86 and that's the one you want to grab. If not, download it from the Store, then update binaries by recovery, and there you are. For sure, if you want to try to do this procedure the dirty way, see if it works, if not, you should reinstall Omni with full wipes and use the new supersu version. Let me know if you got it solved or we will try to help you out with your problem.

Pokemon GO 0.37+ : which ROM ?

Hello there,
stupid question but Pokemon Go doesn't work with latest version (0.37). It says OS is incompatible (and ROM has been de-rooted, this was verified). I think it's due to Safeynet check that doesn't pass. I will check this tonight !
Using an old AMCHA version (Android 4.4.4), Pokemon Go works great with 0.35... but for now. When this version will be desactived, there will be no way to play anymore.
Is there a ROM, official or custom, working with Pokemon Go 0.37 and future versions ?
Thanks for your help !

seconding this!
i am on N4EliteLite_v15-Final-Note5Edition_i9305_AROMA and the game worked perfectly until the update
i already tried RootCloack with Xposed -- not working
i cannot try magisk method because it requires android 5.0 and i have not found a 5.0 rom with working gps for i9305.
any ideas?
thanks in advance!

Yep, I saw Magisk method but I didn't noticed it was only for Android 5.0+. So I will have to flash a new ROM if I want Pokemon GO + root !
Is there an official Samsung release (or an optimised ROM based on it) that works will v0.37 ?
@Girugamesh : it seems that Ressurection Remix is the best one to choose !

thanks for telling.
unfortunaly i am stuck with magisk manager root toggle turning it self off again
i flashed ressurection remix and followed the guide on androidpolice
i even tried flashing "unSU Script zip"
let me hear if you have any luck with your i9305

I will try to flash new ROM this week-end. I will tell you if I find something.
For your issue, check if all the folders associated with SuperSU are deleted : /system/xbin/su, /data/su.img, /sbin/su etc. There is probably something remaining from previous root.

i finaly made it. the real pain was to get rid of a corrupted supersu installation (es file explorer was not allowed to remove su.bin)
i did supersu unroot, deleted the files you said, also used unSu script.zip BUT since i dont need root, i just started pokemon and it works.
to clarify i am on ressurection remix android6.0 with a i9305
thanks for your help

Great news !
For my wife's phone, I will give a try on the latest official ROM (4.4.4 - I9035XXUFPB1). If it doesn't work, I will go on RRM + full unroot. More news this week-end

hoeni said:
How?
I didn't find a Superuser app, but I deleted everything su related from /system
Flashed magisk, Flashed phh Superuser, installed magisk and phh app, but the toggle keeps reverting to root. Maybe you could provide me with the steps you took
Click to expand...
Click to collapse
I thought that I'd post my solution here. I'm running CM13 right now and I can run the lastest version of Pokemon go.
1. Install Supersu from the play store and select the option full unroot.
2. Flash Magisk and phh's SuperUser.
3. Install the Magisk manager apk and install phh's SuperUser from the play store.
4. Now when you want to play PoGo open the Magisk manager and disable root. Simple as that.

JD. A said:
I thought that I'd post my solution here. I'm running CM13 right now and I can run the lastest version of Pokemon go.
1. Install Supersu from the play store and select the option full unroot.
2. Flash Magisk and phh's SuperUser.
3. Install the Magisk manager apk and install phh's SuperUser from the play store.
4. Now when you want to play PoGo open the Magisk manager and disable root. Simple as that.
Click to expand...
Click to collapse
Yep, I followed the steps provided by the dev of magisk. Seems like that thread gets so overrun by "doesn't work" that individual questions get forgotten haha
I can't think of anything I did wrong, I'm trying to get it to work on an s3 lte and a note 3.
On my main, s7 edge, it works perfectly. But only because I found a rom featuring magisk and phh root in aroma.
I'm reflash the rom right now to start over. Maybe it'll work now.
Edit:
phh's root didn't work.
the modified SU app did however
Edit 2:
Nah
Magisk is working, yes, but PoGo wont let me enter and SafetyNet wont let me pass either.
Ugh getting sick of this.

Tested with official I9305XXUFOB2 and without any root / busybox, everything is OK with Pokemon GO 0.37.1. No need to go further for my part

Lwysiwyg said:
Tested with official I9305XXUFOB2 and without any root / busybox, everything is OK with Pokemon GO 0.37.1. No need to go further for my part
Click to expand...
Click to collapse
damn, it could have been so easy.. good job mate :good:
i will remember this.
EDIT: install stock , unroot with supersu , even pokemon go v0.41.4 works now

Girugamesh said:
damn, it could have been so easy.. good job mate :good:
i will remember this.
EDIT: install stock , unroot with supersu , even pokemon go v0.41.4 works now
Click to expand...
Click to collapse
Hey man, can you help me step by step what you did to unroot and get POGO running on resurrection remix

Bootloop after rooting CrDroid

I Installed the latest 2.1 crDroid today, the ROM is smooth and almost everything works perfectly fine. So I decided to install the substratum theme engine, and it failed and because it couldn't get the root privileges. Then I came to know that the ROM itself is not rooted and tried to flash super su 2.4.6. zip in order to root it.. but instead it gave me bootloop... can anyone confirm if they faced the same?
Thanks in advance

Kalp3sh S1NGH said:
I Installed the latest 2.1 crDroid today, the ROM is smooth and almost everything works perfectly fine. So I decided to install the substratum theme engine, and it failed and because it couldn't get the root privileges. Then I came to know that the ROM itself is not rooted and tried to flash super su 2.4.6. zip in order to root it.. but instead it gave me bootloop... can anyone confirm if they faced the same?
Thanks in advance
Click to expand...
Click to collapse
Try installing this..

Ashish Banka said:
Try installing this..
Click to expand...
Click to collapse
I flashed the latest zip. Thanks anyway

Flash ROM gapps and root files together and check

Kalp3sh S1NGH said:
I flashed the latest zip. Thanks anyway
Click to expand...
Click to collapse
hello frnds. I have installed RR rom (5-02-17 built) by Rishab Rao every thing is working good. but i m facing network reception issue specially on jio network. although its working fine fine but there is a flactuation in network every time. 1.. 2.. 3.. but never 4 ( full network). Anyone facing this issue..??

Samsung S5 Plus Magisk above v12 boot loop stuck on boot logo

Hi all when flashing any version above v12 on to my phone it gets stuck at the boot logo I am using Lineageos latest version of typing this but if I use v12 its fine but dont pass the CTS and stuff
I have tried to fully uninstall the magisk and reinstall it on the newer version and nothing can anyone help please

I have also fully reinstalled the ROM with formatting everything and it still don't boot

Your bootloader must be unlocked to flash LOS on the S5, right? I have the same setup as you and running no issues at all. Are you flashing the zip after flashing the ROM?

ldeveraux said:
Your bootloader must be unlocked to flash LOS on the S5, right? I have the same setup as you and running no issues at all. Are you flashing the zip after flashing the ROM?
Click to expand...
Click to collapse
The Samsung galaxy S5 plus (g901F) is different from Samsung galaxy S5 (g900) si magisk work on second one but on the first one magisk v13 never worked and it's confirmed at the lineage OS side. I'm on this case too so I confirm the issue.

Jet45 said:
The Samsung galaxy S5 plus (g901F) is different from Samsung galaxy S5 (g900) si magisk work on second one but on thé first one magisk v13 never worked and it's confirmed at the lineage OS side. I'm on this case too so I confirm the issue.
Click to expand...
Click to collapse
So glad someone eles has the same problem and I'm not on my own it just seems weird how the v12 works it don't pass but all loads fine. Let hope they find why and fix it.

Flash your stock bootloader then try flashing magisk

I'm using the stock bootload not changed my bootloader
If it was the bootloader why foes v12 work fine?

No request to have any information about this ?
What do the devs need (other than time of course) to try a troubleshooting ?
How to get this logs/boot image and logs ?

Managed to get it working, but did a clean install and lost it, first time I got it working I was at 19-07-2017 build with magisk manager 5.1.1 and magisk 12, with magisk folder mount and magisk ext SD access modules installed, then upgraded to 26-07-2017 build through official update from settings, and after installation I rebooted the phone into recovery and installed magisk 13.3 (as you know when updating we lose magisk root) and it worked.
Then did a clean install of 26-07 build (thinking it will work) but nope.

Recycool said:
Managed to get it working, but did a clean install and lost it, first time I got it working I was at 19-07-2017 build with magisk manager 5.1.1 and magisk 12, with magisk folder mount and magisk ext SD access modules installed, then upgraded to 26-07-2017 build through official update from settings, and after installation I rebooted the phone into recovery and installed magisk 13.3 (as you know when updating we lose magisk root) and it worked.
Then did a clean install of 26-07 build (thinking it will work) but nope.
Click to expand...
Click to collapse
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?

Jet45 said:
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Click to expand...
Click to collapse
I tried to do that again but I couldn't. As said:
In was on 19-07-2017 build with magisk 12 sdk and magisk manager 5.1.1 app, had magisk folder mount 0.8.5 and SD card access module, then on 26.07.2017 I received the weekly update, after update I rebooted the phone into recovery and instead of magisk 12 sdk I installed magisk 13.3 (for testing) and it worked. I tried doing that again but didn't worked so I don't know what to say lol.

Recycool said:
I tried to do that again but I couldn't. As said:
In was on 19-07-2017 build with magisk 12 sdk and magisk manager 5.1.1 app, had magisk folder mount 0.8.5 and SD card access module, then on 26.07.2017 I received the weekly update, after update I rebooted the phone into recovery and instead of magisk 12 sdk I installed magisk 13.3 (for testing) and it worked. I tried doing that again but didn't worked so I don't know what to say lol.
Click to expand...
Click to collapse
So I'll try to reproduce it at my side with that you've said, it may be a walktrough . Two brains to work on it may succeed

Jet45 said:
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Click to expand...
Click to collapse
I posted a logging of the problem on the main support thread, let's see what happens
https://forum.xda-developers.com/ap...sal-systemless-t3432382/page1765#post73249492

cross the fingers (I hope that you say like that in English)

Fingers crossed they sort it. Would love yo be able to use magisk again

Does anyone here have this issue on a stock ROM or is it just Lineage OS? From the log that was posted in the main support thread it looks like the Magisk installation was successful, but the system hangs on this one line before it can fully boot. I'm not qualified to read more than that out of the log though...
There's been some code added to GitHub in the last few days. Have anyone tried the latest unofficial snapshot? There was a new one built yesterday: https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901

Hi we got anymore news on this I have tried the latest beta one and it still gets stuck at booting.

It seems there is nothing to expect from nor magisk team neither lineage team. Nobody seem want to work on this really specific problem.

Need help with Rom that doesn't add Root and will run Gapps

Hi all,
I have recently tried running RR and loved ridding my Mix of Miui but had issues with root being recognized by my work email even with magisk hide. It would not allow me to run Maas360 because of that.
I then tried Pixel Experience which wasn't rooted (I think) but NFC wasn't working so that wasn't going to work.
I then tried AICP 13.1 which I think wasn't rooted and all things like NFC we're working but when I tried to install the linked Gapps (and a couple different ones) it would load and when I went into Google to set up the account it would hang at looking for details and then almost all Google apps one at a time would show as stopping.
Can anyone recommend a Rom that will give me the pixel experience that will include the Gapps and that isn't rooted.
I appreciate any help in advance.
Thanks

imapfsr said:
Hi all,
I have recently tried running RR and loved ridding my Mix of Miui but had issues with root being recognized by my work email even with magisk hide. It would not allow me to run Maas360 because of that.
I then tried Pixel Experience which wasn't rooted (I think) but NFC wasn't working so that wasn't going to work.
I then tried AICP 13.1 which I think wasn't rooted and all things like NFC we're working but when I tried to install the linked Gapps (and a couple different ones) it would load and when I went into Google to set up the account it would hang at looking for details and then almost all Google apps one at a time would show as stopping.
Can anyone recommend a Rom that will give me the pixel experience that will include the Gapps and that isn't rooted.
I appreciate any help in advance.
Thanks
Click to expand...
Click to collapse
You really need a thorough wipe when coming from miui ROMs as some files from gapps can remain and cause problems, did you try dm-verity instead of magisk, no root but stops device becoming encrypted.

james1089 said:
You really need a thorough wipe when coming from miui ROMs as some files from gapps can remain and cause problems, did you try dm-verity instead of magisk, no root but stops device becoming encrypted.
Click to expand...
Click to collapse
Thanks for the help!

james1089 said:
You really need a thorough wipe when coming from miui ROMs as some files from gapps can remain and cause problems, did you try dm-verity instead of magisk, no root but stops device becoming encrypted.
Click to expand...
Click to collapse
Thanks for your help!