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.
Related
There is a way to get Marshmallow on the HTC ONE Sprint M7, it's called VanirAOSP ROM. This is a great in most ways, and it's now my daily driver, but be very careful, I almost bricked my phone a few times in setting things up. Here are some tips from what I learned.
Installation instructions (learned from this video, other sources, and hard work):
1) Unlock bootloader.
2) Install custom recovery like TRWP. If you have an old version of TWRP, upgrade it using TRWP Manager or Flashify.
3) Download latest nightly ROM from http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/m7spr/.
4) Download gapps. Biker57 suggests gapps from http://www.emccann.net/dho/5-Gapps/ as it's supposed to cause fewer force closes. I believe 60arm-DHO-GAPPs.zip is the correct file name.
5) Download SuperSU. Biker57 likes SuperSU v2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125.
6) Copy all 3 downloads (in .zip format) to the phone (internal storage, like the TWRP folder)
7) Enter bootloader (volume down and power button), then select bootloader.
8) Backup the current ROM, just in case things go bad like they did for me.
9) From TWRP, enter advanced wipe and select system, data, cache, and dalvik cache. Do not select internal storage as you will lose your current backup and other zips if you do (there is an exception to this, as I did it, but I nearly bricked my phone). Now slide to wipe.
10) Go to install, and first select the ROM's zip. Then choose add more zips and select the gapps zip you downloaded. Next select SuperSU. Now slide to install.
11) Be patient during install.
12) Wipe dalvik cache.
13) Reboot to system (aka phone).
14) Enable Developer Options (if you want), by going to Settings->About and hitting Build Number many times until it's enabled.
Known issues and workarounds:
-Camera app force closes after taking a picture - the picture saves, so just reload Camera app. I've also had good luck using Z Camera then viewing the preview before hitting back to reenter the camera app.
-Stock dialer FCs randomly - Install another dialer app, like True Phone.
-Facebook and Facebook Messenger force closes - use mobile website, which actually isn't too bad, or try the instructions listed here.
-Flashlight turns off after 3 seconds - use the cameras flash instead.
Known issues with no good workarounds:
-FM Radio doesn't work.
-Bluetooth audio doesn't work for phone calls most of the time.
-Switching the battery mode causes the brightness to change randomly - don't ever switch away from balanced mode
Other stuff
-You can find more about the updates made to Vanir ROM here.
-It's risky to play around with the radio, but if you want to try it they are listed here.
-Intersted in supporting Varin, you can donate here.
Please let me know if I missed anything. And feel free to copy freely if it helps others.
***disclaimer - follow at your own risk. I'm not responsible for what might happen to your phone. This is only a cheat sheet, and it's for reference purposes only.***
First off, good tutorial. :good:
Vanir is a great ROM but this Sprint ROM still has a lot of bugs in it. I've used the first Vanir Marshmallow ROM to the most recent and a plethora of bugs have been squashed. But this ROM is still not DD ready, the camera , torch, gapps, browser and settings are broken. I am not saying this ROM is bad, just that its not fully ready yet. Depending on the dev, this rom should be DD ready in 2-3 weeks, they've been releasing more often now. Thank the developer if you know him but if you're the developer, thank you.
We should try to get the dev to see if they can put up a Vanir thread with change logs and the whole shebang.
I'm glad this thread was started and the OP was done well. I've been using this ROM for a while and thought I'd pass along my thoughts and what works for me.
This rom has become my daily driver after learning how to fix a couple of issues. After the latest update of 2/18 the biggest issues of not having a cellular/data connection has been corrected. The only issues that remain for me at least are the camera and Facebook issues. Although the camera does force close it does so for me at least after the picture is taken and saved so it's all good for me. The Facebook issues are corrected by deleting a file in both the Facebook and Messenger file.
The following method works for me without boot loops or any other issues and hopefully will work for you too. I flash these all at the same time loaded in the order listed and don't forget to make a backup before you start just in case.
1 - Flash the 2/18 nightly just like you would any rom http://www.emccann.net/nuclearmistak...ghtlies/m7spr/
2 - flash the gapps found here http://www.emccann.net/dho/5-Gapps/ and select the 60arm file near the bottom.
3 - flash Super SU 2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125 There are new versions, but the 2.64 has continued to work for me.
4 - Reboot
As I said earlier this works for me and I've used this method with their roms successfully a number of times. Good Luck !!
Thank the developer if you know him but if you're the developer, thank you.
Click to expand...
Click to collapse
I'm not the developer, and I don't know the developer. But I would thank him or her if I could. I'm just interested in running Marshmallow on the M7. I will update the original post as I learn more so I can hopefully help others.
anotherfakeusername said:
I'm not the developer, and I don't know the developer. But I would thank him or her if I could. I'm just interested in running Marshmallow on the M7. I will update the original post as I learn more so I can hopefully help others.
Click to expand...
Click to collapse
If you need help with thread stuff I can help, we should start a new thread completely and give it more of a ROM thread look with known bugs, work a rounds and honest opinions on it.
biker57 said:
3 - flash Super SU 2.64 found here http://forum.xda-developers.com/showpost.php?p=64161125
Click to expand...
Click to collapse
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
anotherfakeusername said:
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
Click to expand...
Click to collapse
I'm not the developer either... Just a happy ROM user
There have been some issues with certain SU not working correctly with 6.0. You can try that but I would advise you to try a proven SU version.
is Snapchat also broken
Sent from my HTC One using Tapatalk
SuperSU 2.65 through TWRP 3.0.0-0
anotherfakeusername said:
Since my device is already rooted, would I be best off to install Super SU from the Play Store, then allow the app to upgrade through TWRP?
Click to expand...
Click to collapse
I didn't install it from the Play Store, I just flashed this version (2.65) through TWRP 3.0.0-0 and it's working as expected :good:
Hello,
Flashing SuperSU through recovery is a better way, atleast for Marshmallow ROMs now. I'm using latest beta version (SuperSU v2.67) without any issues. It can be found in official SuperSU thread here.
As of camera issues, you can use 3rd party camera apps like Camera FV-5, ProShot or etc. Of course they cost few bucks but worth it. Issue doesn't solve totally in this ROM but app doesn't force close, instead freezes for few sec and then works again.
This ROM is my DD and faced no major issues so far. What I'm mostly missing is fast charge feature in kernel otherwise normally it takes plenty of hours to fully charge.
Kindly note; you have to flash gapps provided by the ROM developer. Other gapps like open gapps will endup with FC.
Thanks...
Best Regards
CRACING said:
Kindly note; you have to flash gapps provided by the ROM developer. Other gapps like open gapps will endup with FC.
Click to expand...
Click to collapse
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
anotherfakeusername said:
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
Click to expand...
Click to collapse
Their list of gapps is rather long......which one did you use and did you flash it with the rom
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
anotherfakeusername said:
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
Click to expand...
Click to collapse
Correct, they have to be flashed with the rom as I mentioned in post 3.
anotherfakeusername said:
I flashed the gapps provided by the ROM developer, but the Gmail app is force closing due to "unknown issue with Google Play services.".
Then I tried using USB OTG to read my sd card reader in TWRP, but TWRP won't mount it. The issue started right after I booted the ROM the first time; I know because I installed the ROM from my sd card using USB OTG.
I still want this to be my daily driver, because the software is so much faster that 4.3, but I'm not convinced yet.
Click to expand...
Click to collapse
As of error "Unknown issue with Google Play service", go to Settings -> Apps -> Google Play service -> click 3 dot button in the corner -> Uninstall updates. This should solve the problem.
As of OTG, I didn't tested it but usb connection from TWRP to pc for file transfor works fine.
Btw; You are right, ROM is indeed fast.
biker57 said:
Their list of gapps is rather long......which one did you use and did you flash it with the rom
Click to expand...
Click to collapse
Use 60arm-DHO-GAPPs.zip
anotherfakeusername said:
You guys are right. I had to flash Super SU through TWRP (which was a challenge at first without using the sc card and OTG cable).
Click to expand...
Click to collapse
Even if you install supersu from playstore, it ask to reboots to recovery to install supersu. But before you accept to reboot, you'll have to enable root access to apps in developer options. Otherwise supersu cannot reboot or go into recovery.
Anyhow, instead of going through all these, I simply flash supersu zip from recovery.
CRACING said:
As of error "Unknown issue with Google Play service", go to Settings -> Apps -> Google Play service -> click 3 dot button in the corner -> Uninstall updates. This should solve the problem.
Click to expand...
Click to collapse
Android won't let me uninstall the Google Play service update. I get blocked when trying. It claims the app is an active device administrator, but it's not listed when I click manage device administrator.
anotherfakeusername said:
Android won't let me uninstall the Google Play service update. I get blocked when trying. It claims the app is an active device administrator, but it's not listed when I click manage device administrator.
Click to expand...
Click to collapse
Deselect Android Device Manager. Later when you uninstall the update, reselect Android Device Manager.
Deselect Android Device Manager. Later when you uninstall the update, reselect Android Device Manager.
Click to expand...
Click to collapse
That worked to fix my calendar syncing issues! Thanks!
Is not updating Google Play service going to cause other problems?
anotherfakeusername said:
That worked to fix my calendar syncing issues! Thanks!
Is not updating Google Play service going to cause other problems?
Click to expand...
Click to collapse
No such problems noticed here. I use Google calendar but Android calendar also works fine.
May be you should try rebooting or wait for some time and try resync.
CRACING said:
No such problems noticed here. I use Google calendar but Android calendar also works fine.
May be you should try rebooting or wait for some time and try resync.
Click to expand...
Click to collapse
The problem isn't using Google calendar, the problem is syncing Google calendar. I tried waiting, rebooting, re-adding my account, and everything else, but that didn't help.
Only downgrading Google Play services worked, and then Google calendar synced right away.
Thanks for the suggestions. Hopefully as they update the ROM it'll get resolved more fully.
I'm right now I'm at a point where I hate stock and these custom roms are great, but hate being held back by the Play store no longer allowing me to download/update Netflix which is used often.
Previously I had installed
KatKiss - Nougatella #023,
SuperSU
Gapps - Stock
I suppose I could have just installed netflix through the apk but I figured that would only be a temp solution.
So my first steps were to wipe and go back to stock.
I then proceeded to add CWM recovery back (Also tried with TWRP)
I wiped
I then ran an uninstall SuperSU zip (which may or may not have been needed but seemed safer to try.
I installed KatKiss
Then Magisk
Then Gapps - Stock
This will cause lots of crashing right from the start of the setup wizard... the the app/stopped don't ever stop. A lot of google related stuff as soon as I conect to Wifi.
I started over.
This time I installed Gapps - Mini instead.
No longer crashes the set up wizard. Everything seems stable.
At this point I have access to the tablet through KatKiss.
When I run Magisk Manager, the safetynet check never finished. Just spins.
If I hide the PlayStore from root and try to find Netflix it won't be there.
However, if I now install Gapps-Stock through recovery at this point... I can then go back to the Play Store and find Netflix. It will be there.
However, I still can't pass SecureNet check. It just spins.
I first thought to myself... Thats ok. I don't need it, Netflix was really the issue I needed addressing and I have that.
So I started putting apps back on my tablet to find... apps were crashing more. Facebook for example will never work. Just crashes on startup.
So something just isn't right and I don't really know what I'm doing. In the past I always just followed easy to follow guides.
Note: I believe I have better luck with KatKiss build #021. 023 gave me more issues with this process so I had 021 on hand.
You really should go with the gapps version recommended by the dev of your rom and that would be pico gapps in this case. If you flash a different gapps package you're on your own for trouble shooting fc'ing apps and system UI and such...
I have no idea if this rom works with Magisk and would be tickled to find out, but I don;t have the time for it right now. On other devices there were problems when the rom was pre-rooted or for some the build-in busybox did not work and they had to flash a different version. There could also be a problem if the boot image has been modded for SuperSU and idk if it has been on this rom.
Try this first:
If you flashed any other than pico gapps version you really should format /data before reflashing the rom. That done:
format /system, wipe /cache and Dalvik, then flash the rom and pico gapps, then flash unsu by osmosis followed by the Magisk flash. Then install Magisk Manager and try to pass Safetynet with both Busybox enabled and disabled.
Let me know how it goes
https://forum.xda-developers.com/showpost.php?p=63615067
Edit: couldn't help myself - had to try it :cyclops:
So I tried a quick and dirty switch from SuperSU rooted Katshmallow v33 to the same rom with Magisk. No reflash, just wiped cache and Dalvik, flashed unsu and then Magisk. Root works fine but it does not pass Safetynet check, Netflix app does not show in Playstore, device is uncertified in Play.
The failed check says: CTS profile mismatch and I believe that is the problem with the Busybox version that comes with Magisk. Read something somewhere about replacing it with a different one which solved the problem for some folks...
I'll dig some more later....
Thanks for the info. I didn't realize the importance of using Gapps-Pico in this case. I just figured they were recommending a light-weight Gapps opposed to a larger one... So I always went with "stock" and never had an issue.
I'll keep that in mind for debugging future issues.
I'm not sure how important formatting /system was... I always left that one alone, but I was formatting /data /cache and Dalvik
That CTS profile stuff all seems beyond my knowledge at the moment. I guess let me know what you find when you do.
Thanks again
No issues? I thought you had "lots of crashing".. ??
So you want me to do all the leg work, yes? Sorry man, it's you who wants Netflix :silly:
I dirty flashed the rom, ran unsu, then flashed Magisk and osmosis' Busybox but Safetynet check still fails for me...
Don't have time to do a clean install just now, but that would be the next step...
I like Magisk as systemless root and I got it working for my purposes.
As for Netflix - I don't use it much on the tablet and I just squirreled away the 4.16.1 version. Just in case I accidentally update it to the newer ones....
Sorry if that was unclear. I meant I never had any issues using Gapp Stock before this whole Rooted/Netflix thing came up last week. Now it is what it is.
And yeah, I didn't mean for it to be like I was asking anything of you. I'm not. You just seemed like the type who would be tinkering with this kind of stuff. If not, no worries.
Information/guidance is what I'm after. Not leg work.
I'm sure I just need to be patient really. Since a lot of people use Netflix I'm sure this will get a lot more attention in the near future.
Thanks again.
What I did:
- Wipe all (clean install).
- Flash latest Official MoKee ROM (Nougat).
- Flash latest GApps.
- Flash latest Magisk.
- Reboot.
After finished the Wizard Setup and before doing anything, my phone got very laggy, open menu, open Settings, etc.
Then I clean install again like the steps above, but this time using SuperSU, and everything normal, so I stick with SuperSU for now.
My questions, what is the cause of the lags? Is it known bug in Magisk, the ROM itself (not compatible), or GApps? I also heard ResurrectionRemix had the same problem after installing Magisk, so many people revert back to SuperSU.
Thanks,
I have Resurrectionremix and Magisk 14.3
No any lag on my phone.
Tapatalk - Xiaomi Mi6
You need to list what modules you're using.
BIGWORM said:
You need to list what modules you're using.
Click to expand...
Click to collapse
I only flash the ROM, GApps and Magisk without any additional flashable ZIPs.
Honestly that doesn't sound like Magisk. I've ran Magisk on literally probably 20 ROMs between Angler and Pixel XL and never Magisk caused lag... Did u try a different rom? Just curious, or maybe it's some incompatibility with that specific rom and magisk
yung40oz84 said:
Honestly that doesn't sound like Magisk. I've ran Magisk on literally probably 20 ROMs between Angler and Pixel XL and never Magisk caused lag... Did u try a different rom? Just curious, or maybe it's some incompatibility with that specific rom and magisk
Click to expand...
Click to collapse
I tried several ROMs that based on LOS and all same, maybe it's caused by LOS base that used in those ROMs. And since you say so, probably it's not an issue in Magisk, but the ROM itself.
I'll try Magisk again later when some ROM's builds available for my device.
-
I think my questions has been answered (it's appear not issue in Magisk side) and this thread can be closed.
irfanfadilah said:
I tried several ROMs that based on LOS and all same, maybe it's caused by LOS base that used in those ROMs. And since you say so, probably it's not an issue in Magisk, but the ROM itself.
I'll try Magisk again later when some ROM's builds available for my device.
-
I think my questions has been answered (it's appear not issue in Magisk side) and this thread can be closed.
Click to expand...
Click to collapse
Ya I was gonna say cause I use all AOSP and CAF based
I had this issue with Lineage 14.1 and AEX before.
Now I don't have this issue anymore.
What I do is:
- Wipe everything
- Install ROM
- Install GApps
- Reboot and finish Setup Wizard (then I install some or all apps that I use)
- Reboot to TWRP and flash Magisk.
The first time I reboot after flashing Magisk it's still a little slower than normal. Then I reboot one more time and never faced this anymore.
Now I do this everytime I make a clean install and everytime it works.
Danilo-Sanchez said:
I had this issue with Lineage 14.1 and AEX before.
Now I don't have this issue anymore.
What I do is:
- Wipe everything
- Install ROM
- Install GApps
- Reboot and finish Setup Wizard (then I install some or all apps that I use)
- Reboot to TWRP and flash Magisk.
The first time I reboot after flashing Magisk it's still a little slower than normal. Then I reboot one more time and never faced this anymore.
Now I do this everytime I make a clean install and everytime it works.
Click to expand...
Click to collapse
So don't flash Magisk along with the ROM?
Instead finish Wizard Setup first and back to TWRP to flash Magisk. I'll try this if the issue still persist. Many Thanks
irfanfadilah said:
So don't flash Magisk along with the ROM?
Instead finish Wizard Setup first and back to TWRP to flash Magisk. I'll try this if the issue still persist. Many Thanks
Click to expand...
Click to collapse
Yes.
Try it and let me know if this also fix the problem for you.
Yes, Magisk is the thing that's causing lag and stutter. My Nexus 5X is also barely responding to any commands if I flash Magisk right after a ROM clean installation. If you flash only the ROM, then you can finish setting up the device without much stutter or hiccups in performance.
If, after a clean installation (or after installing Magisk - didn't try this though) you use the phone without Magisk for a bit, maybe install some apps, etc, you'll see that everything is nice and smooth.
Now, you can check the smoothness without Magisk and with Magisk installed like this:
- Without Magisk: Update 'Google App' to the latest version then try to open the side panel from the latest Pixel Launcher. You'll see that opening/closing it is nice and smooth, and scrolling up and down is also smooth.
- With Magisk installed (without using any modules): The moment the phone turns on, at first, things might seem OK. First wait for the phone to settle down after the reboot for a few minutes. Then try opening the side panel. You'll see some stutter while dragging that panel to the right, maybe not huge, but it's there. Scrolling up and down is also stuttery. At first I thought it was because of the latest version of Google App, or the new cards design, or even the images in there, but that wasn't the issue. Then I thought maybe the launcher was somehow influencing Google App's performance, but that wasn't either the issue.
AND it was like I completely forgot about SuperSU and didn't even think of trying it in order to see how things were.
I even rebased my ROM in the hope that I'd find the culprit, and still nothing. Nothing weird appeared in any logs, which was so annoying. And a few hours ago, after finishing up cleaning up my sources (for other reasons), I compiled a fresh new build, and it crossed my mind to try SuperSU, just for the hell of it, and BOOM ! No more lag and stutter. The phone is snappy and responsive again.
I'll try to contact the dude behind Magisk and see what he has to say, or leave a comment in his thread.
The thing is, those with more recent phones, like the Pixels or any other phones than are more powerful than mine, might not notice what I described above, but there should be some stutter there, no matter how small, maybe in other scenarios as well.
The thing is, Magisk kinda slowly took the place of Xposed, at least that's what it looks like to me, and I personally don't like that but that's how things are, I suppose. All those modules or at least one of them WILL cause issues sooner or later, just like on Xposed.
But in the end, yes, it's Magisk what's destroying your phone's performance and nothing else. So if you're not really in the need to have your phone pass SafetyNet, and want to have your phone snappy and lag-free, use SuperSU, at least until things get better on Magisk.
dragos281993 said:
Yes, Magisk is the thing that's causing lag and stutter. My Nexus 5X is also barely responding to any commands if I flash Magisk right after a ROM clean installation. If you flash only the ROM, then you can finish setting up the device without much stutter or hiccups in performance.
If, after a clean installation (or after installing Magisk - didn't try this though) you use the phone without Magisk for a bit, maybe install some apps, etc, you'll see that everything is nice and smooth.
Now, you can check the smoothness without Magisk and with Magisk installed like this:
- Without Magisk: Update 'Google App' to the latest version then try to open the side panel from the latest Pixel Launcher. You'll see that opening/closing it is nice and smooth, and scrolling up and down is also smooth.
- With Magisk installed (without using any modules): The moment the phone turns on, at first, things might seem OK. First wait for the phone to settle down after the reboot for a few minutes. Then try opening the side panel. You'll see some stutter while dragging that panel to the right, maybe not huge, but it's there. Scrolling up and down is also stuttery. At first I thought it was because of the latest version of Google App, or the new cards design, or even the images in there, but that wasn't the issue. Then I thought maybe the launcher was somehow influencing Google App's performance, but that wasn't either the issue.
AND it was like I completely forgot about SuperSU and didn't even think of trying it in order to see how things were.
I even rebased my ROM in the hope that I'd find the culprit, and still nothing. Nothing weird appeared in any logs, which was so annoying. And a few hours ago, after finishing up cleaning up my sources (for other reasons), I compiled a fresh new build, and it crossed my mind to try SuperSU, just for the hell of it, and BOOM ! No more lag and stutter. The phone is snappy and responsive again.
I'll try to contact the dude behind Magisk and see what he has to say, or leave a comment in his thread.
The thing is, those with more recent phones, like the Pixels or any other phones than are more powerful than mine, might not notice what I described above, but there should be some stutter there, no matter how small, maybe in other scenarios as well.
The thing is, Magisk kinda slowly took the place of Xposed, at least that's what it looks like to me, and I personally don't like that but that's how things are, I suppose. All those modules or at least one of them WILL cause issues sooner or later, just like on Xposed.
But in the end, yes, it's Magisk what's destroying your phone's performance and nothing else. So if you're not really in the need to have your phone pass SafetyNet, and want to have your phone snappy and lag-free, use SuperSU, at least until things get better on Magisk.
Click to expand...
Click to collapse
I'm glad I'm not the only one experienced this issue, that's mean it's not entirely user fault. Maybe you're right, on more high-spec phones they won't really notice the lags/stutters.
Looking forward to the news/updates regarding this issue.
irfanfadilah said:
So don't flash Magisk along with the ROM?
Instead finish Wizard Setup first and back to TWRP to flash Magisk. I'll try this if the issue still persist. Many Thanks
Click to expand...
Click to collapse
I don't mean to necrobump, but did it work? I have an LG G4 (H815) and suffered the same issue. Like you, I only flashed magisk right after flashing the ROM (LG nougat).
Thanks
Camandros said:
I don't mean to necrobump, but did it work? I have an LG G4 (H815) and suffered the same issue. Like you, I only flashed magisk right after flashing the ROM (LG nougat).
Thanks
Click to expand...
Click to collapse
I haven't got the chance to try it.
Currently I'm using SuperSU to root my device.
I tried installing magisk on my currently in use ROM, i.e., a long time after flashing it, and although it got less laggy, there still was a heavy lag impact in some applications. Maybe it has less impact on lineage or on lighter ROMs? I'm using official LG nougat.
I'm using Mi 6 in Xiaomi.eu rom
YES, magisk causing laggy.
Same here
Mi5, tested on MIUI 9 and 10
Without Magisk everything was great and after flashing Magisk, the phone got laggy!
I have the same problem with my LG G6
interesting, first I thought that emmc will be broken. because the problem is the same (lag). but after i replace emmc, all back is fine. I just think emmc is broken because it is often flashing rom.
ChessPiece said:
What I did:
- Wipe all (clean install).
- Flash latest Official MoKee ROM (Nougat).
- Flash latest GApps.
- Flash latest Magisk.
- Reboot.
After finished the Wizard Setup and before doing anything, my phone got very laggy, open menu, open Settings, etc.
Then I clean install again like the steps above, but this time using SuperSU, and everything normal, so I stick with SuperSU for now.
My questions, what is the cause of the lags? Is it known bug in Magisk, the ROM itself (not compatible), or GApps? I also heard ResurrectionRemix had the same problem after installing Magisk, so many people revert back to SuperSU.
Thanks,
Click to expand...
Click to collapse
what magisk version 16.0 or beta? magisk can't make the phone lag but kernel or something in ROM may interrupt try to change kernel or flash the lastest Gapps
Has anyone has success in installing this on Android 5.0 samsung S4 ? I followed the instructions and the manager just says not installed.
Unless you provide more details and installation logs it's gonna be hard to help...
Didgeridoohan said:
Unless you provide more details and installation logs it's gonna be hard to help...
Click to expand...
Click to collapse
What details would you like to know? I flash it and then later restart but the manager was not there so I tried to install it from saving the apk file that I downloaded. But it just said it was not installed and later I found out I lost root from trying to flash Xposed on my phone.
I am very new to this and tried to follow the tutorials and videos but its not working cause I thought using Magisk I can install the seamless Xposed.
Those recovery/installation logs would be a good start.
You're muddling up the details a bit...
Was the Manager not installed or did it report that Magisk wasn't installed? And you lost root? But you said you couldn't install Magisk... Are you already rooted? That might cause issues.
Being nice and clear and detailed (what is being flashed, version numbers, what's already done, what works, what doesn't work, with logs, etc) in your descriptions would help.
Didgeridoohan said:
Those recovery/installation logs would be a good start.
You're muddling up the details a bit...
Was the Manager not installed or did it report that Magisk wasn't installed? And you lost root? But you said you couldn't install Magisk... Are you already rooted? That might cause issues.
Being nice and clear and detailed (what is being flashed, version numbers, what's already done, what works, what doesn't work, with logs, etc) in your descriptions would help.
Click to expand...
Click to collapse
I hope this is clearly for you!
1. I flash the file with TWRP with success
2. The phone got stuck on samsung logo
3. Root was removed.
4.I had to re flash stock and it is working again.
5. How do I get the logs of Magisk if my phone keeps looping?
I wanted to use Magisk to see if Xposed would work but it looks like i can't even get Magisk to work on my samsung i9500 with original rom. This same thing happens with Xposed where everything goes smoothly with flashing it in recovery and then a boot loop on the logo. Others on this forum have been complaining about this too and perhaps the developer might have not considered odexed rom like samsung for these wonderful apps to work?
I am going back to Kitkat where i don't have these issues and I can use Xposed.
Hello,
first off, sorry. I was stupid and didn't read into it before installing (or trying to install) Xposed to my Samsung S8. Yes, i've read now that it doesn't work with the official ROM, but now it's a bit to late.
So. After rooting my S8 today (using TWRP) i wanted to install Xposed. I downloaded an installer from this site because.. umm, i had a brain fart. For some reason my brain took that site as the official website, so i downloaded it from a 3rd Party site instead of the actual website.
I installed the apk and granted root access. After that i clicked on install and Xposed installed successfully. After that it obviously asked me to reboot my device, which i did. But now i am stuck on the Samsung screen of the boot progress. I know i could technically just wipe the phone (again) and start anew, but i'd like to avoid that if possible. I can access TWRP, but if i try to access the system files in the file browser, it shows "0MB" and i can't access them.
I tried downloading an uninstaller linked in this thread, but i don't know which one i should download.
Sorry again for me being so stupid and not reading into it and downloading from some weird 3rd Party site.
Thanks in advance for the help!
EDIT: And yea, of course i didn't create a backup before installing Xposed. So if there is no way to properly uninstall it, i gotta wipe everything once again
Emilia-Chan said:
Hello, first off, sorry. I was stupid and didn't read into it before installing (or trying to install) Xposed to my Samsung S8.......
Click to expand...
Click to collapse
I don't have this device but, I believe that you should be able to flash (via TWRP) the Framework Uninstaller located on the following Official XPosed link. Just select the correct ARCH (ARM, ARM64, etc...) for your device.
http://dl-xda.xposed.info/framework/uninstaller/
If necessary, you can always try to obtain some additional member guidance and support from the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3582142
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
In the link provided by @lbuprophen use the arm64 zip uninstaller (latest version) to uninstall exposed.
Just curious how long did you let it try to boot for,mine took 10-15 minutes for it to do it's thing and boot up.
Sent from my Samsung Galaxy S8 using XDA Labs
Ibuprophen said:
I don't have this device but, I believe that you should be able to flash (via TWRP) the Framework Uninstaller located on the following Official XPosed link. Just select the correct ARCH (ARM, ARM64, etc...) for your device.
Click to expand...
Click to collapse
I tried that before, unfortunately without success. It also may be noteworthy that my brain turned off and downloaded the XPosed installer off some 3rd Party site. I know. Stupid. But it happened.
spawnlives said:
In the link provided by @lbuprophen use the arm64 zip uninstaller (latest version) to uninstall exposed.
Just curious how long did you let it try to boot for,mine took 10-15 minutes for it to do it's thing and boot up.
Click to expand...
Click to collapse
I waited over an hour for my phone to boot, before and after flashing the uninstaller. I also tried wiping it and even completely formatting the data, everything without any success. It kept on not passing the Samsung screen and eventually bootlooping.
I fixed the issue by just flashing the stock rom with odin and then reinstalling TWRP and rooting my device again. Will stay away from XPosed with this phone for now.
Thanks for the advice anyways!
Emilia-Chan said:
.... I fixed the issue by just flashing the stock rom with odin and then reinstalling TWRP and rooting my device again. Will stay away from XPosed with this phone for now. Thanks for the advice anyways!
Click to expand...
Click to collapse
You did what I would have probably done myself in this situation by starting from scratch.
I just wanted to let you know that I believe that I had saw somewhere (within the dedicated area of the forum for your device) that individuals were successful with Magisk XPosed.
Though I do understand if you want to stay away from XPosed until your ready again and I'm happy to see that your at least up and running again.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
I got the same even just after the installation of the apk for Systemless Xposed on an Xperia (XposedInstaller_3.1.5-Magisk.apk) found here: https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
I made a reboot as I like to isolate the issues while they happen. That was it: bootloop..