Related
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.
What's the point of rooting an active if you can't do anything with it. Now you can't even get the new at&t update. Someone explain what the reason is please besides the thrill of pointless tinkering.
psideburns said:
What's the point of rooting an active if you can't do anything with it. Now you can't even get the new at&t update. Someone explain what the reason is please besides the thrill of pointless tinkering.
Click to expand...
Click to collapse
I do lots of stuff with my rooted S4A. Wanam Xposed, Pie Controls, frozen ATT bloat and Avast Firewall to name a few things. It even text messages and makes phone calls!
New update=yawn. 4.3 isn't a big deal (unless you want a Gear).
psideburns said:
What's the point of rooting an active if you can't do anything with it. Now you can't even get the new at&t update. Someone explain what the reason is please besides the thrill of pointless tinkering.
Click to expand...
Click to collapse
It depends on what you're trying to accomplish. I personally have root so I can fully utilize Titanium Backup to backup my entire phone, block ads, use Folder Mount to force files to be saved to my external SD card, install Cerberus as a system app to utilize more of its features, and install Xposed Framework and Xposed Modules to endlessly customize my phone and add additional functionality to it. It's up to you whether or not you think rooting is worth it. With that said you can always update to the official AT&T 4.3 firmware using the Odin files found in this thread.
Good points for your purposes granted. But I loved to change roms on my gs2 until I found cm, then I stuck with that one as my fav. I'm just frustrated that it is not that easy or even possible anymore, at least with this phone that I like and plan on keeping for a while.
psideburns said:
Good points for your purposes granted. But I loved to change roms on my gs2 until I found cm, then I stuck with that one as my fav. I'm just frustrated that it is not that easy or even possible anymore, at least with this phone that I like and plan on keeping for a while.
Click to expand...
Click to collapse
Have you looked at SafeStrap?
Devo7v said:
It depends on what you're trying to accomplish. I personally have root so I can fully utilize Titanium Backup to backup my entire phone, block ads, use Folder Mount to force files to be saved to my external SD card, install Cerberus as a system app to utilize more of its features, and install Xposed Framework and Xposed Modules to endlessly customize my phone and add additional functionality to it. It's up to you whether or not you think rooting is worth it. With that said you can always update to the official AT&T 4.3 firmware using the Odin files found in this thread.
Click to expand...
Click to collapse
Hey Devo, you run xposed framework on the stock rom with no issues? I had some problems with it on my sgh-i537 and some of the modules wouldn't work at all. If I tried to install the hypderive device tools(shutdown) menu, when I use the shutdown button my phone locks up and just shuts off, no menu ever appears. I really like alot of the hyperdrive functions, I'd love to be able to add the hyperdrive tweaks too, but never had any luck there either.
As concern me I will sell my s4 active No Roms No updates :'(
Sent from my GT-I9295 using xda app-developers app
monkeyhouse said:
Hey Devo, you run xposed framework on the stock rom with no issues? I had some problems with it on my sgh-i537 and some of the modules wouldn't work at all. If I tried to install the hypderive device tools(shutdown) menu, when I use the shutdown button my phone locks up and just shuts off, no menu ever appears. I really like alot of the hyperdrive functions, I'd love to be able to add the hyperdrive tweaks too, but never had any luck there either.
Click to expand...
Click to collapse
Yeah, I run Xposed on my stock ROM. The only issue I ever had was a few days ago when I updated XPrivacy and the phone refused to boot. I had to flash the Xposed disabler with SafeStrap. I run the GPE ROM in slot 1 so I can't speak to the way Hyperdrive works. Sorry I can't be more helpful.
Devo7v said:
Yeah, I run Xposed on my stock ROM. The only issue I ever had was a few days ago when I updated XPrivacy and the phone refused to boot. I had to flash the Xposed disabler with SafeStrap. I run the GPE ROM in slot 1 so I can't speak to the way Hyperdrive works. Sorry I can't be more helpful.
Click to expand...
Click to collapse
Ok, I see. so whatever is in your slots can affect your stock rom as well? I also ran GPE in another slot for a while and I liked it, but with the aroma installer and the hyperdrive tweaks, it really is something I'd like to stick with. I wish I understood more about what is shared and what isn't between roms in slots and the deal with the locked bootloader. We're a long way from Windows Toto, lol. Then again, I do networking, not programming so much.
So, do you run the advanced power menu module on your stock ROM? I really like the HyperDrive version, I think it's called HyperDrive Device Menu or something.
I want to say I installed wanam and xposed from apk files, no flashing. Maybe I need to start there. Thanks again.
monkeyhouse said:
Ok, I see. so whatever is in your slots can affect your stock rom as well? I also ran GPE in another slot for a while and I liked it, but with the aroma installer and the hyperdrive tweaks, it really is something I'd like to stick with. I wish I understood more about what is shared and what isn't between roms in slots and the deal with the locked bootloader. We're a long way from Windows Toto, lol. Then again, I do networking, not programming so much.
So, do you run the advanced power menu module on your stock ROM? I really like the HyperDrive version, I think it's called HyperDrive Device Menu or something.
I want to say I installed wanam and xposed from apk files, no flashing. Maybe I need to start there. Thanks again.
Click to expand...
Click to collapse
I don't think that the Rom slots impact each other unless you are running low on space.
I don't have am advanced power menu and I'm not sure what the Hyperdrive one looks like. That said Wanam had a couple of options that extend the power menu that are worth a try.
Everything I've installed has been by directly installing an apk. Except for dark dialer, dark contacts, and call recording.
Devo7v said:
I don't think that the Rom slots impact each other unless you are running low on space.
I don't have am advanced power menu and I'm not sure what the Hyperdrive one looks like. That said Wanam had a couple of options that extend the power menu that are worth a try.
Everything I've installed has been by directly installing an apk. Except for dark dialer, dark contacts, and call recording.
Click to expand...
Click to collapse
thanks for the info man. I will try the wanam menu and see, think I tried it once, but still had the issue with the button locking up. One thing for sure, installing these other ROM's gives me plenty of ideas of how to change my stock ROM! BTW, I love D.C. saw the FW's at the National Harbor last year, good time. There's an Amtrak that runs direct from here and you can drink on the train!
Devo7v said:
Yeah, I run Xposed on my stock ROM. The only issue I ever had was a few days ago when I updated XPrivacy and the phone refused to boot. I had to flash the Xposed disabler with SafeStrap. I run the GPE ROM in slot 1 so I can't speak to the way Hyperdrive works. Sorry I can't be more helpful.
Click to expand...
Click to collapse
Hey Devo, how do you un-flash something? I flashed a accuweather transparent widget that doesn't work and I think it might have stopped my air gesture from working, just working back from things I have changed recently and that is one of them.
monkeyhouse said:
Hey Devo, how do you un-flash something? I flashed a accuweather transparent widget that doesn't work and I think it might have stopped my air gesture from working, just working back from things I have changed recently and that is one of them.
Click to expand...
Click to collapse
You need to open up the zip file and look inside the folders to see what files are flashed and where they ate flashed. This will tell you what files were changed our added then you can manually remove them. I would also ask the creator to post a zip that removes the necessary files to return to stock. It should be easy enough.
Devo7v said:
You need to open up the zip file and look inside the folders to see what files are flashed and where they ate flashed. This will tell you what files were changed our added then you can manually remove them. I would also ask the creator to post a zip that removes the necessary files to return to stock. It should be easy enough.
Click to expand...
Click to collapse
thanks man, I know that wasn't your issue and I really appreciate your response.
psideburns said:
What's the point of rooting an active if you can't do anything with it. Now you can't even get the new at&t update. Someone explain what the reason is please besides the thrill of pointless tinkering.
Click to expand...
Click to collapse
Quite a few apps don't work without root access. Plus it is necessary to be able to use tethering without a separate plan. Battery doctor, quickboot, app quarantine, and titanium backup are just a few on mine.
Been a long time Venom user but recently decided to try Insertcoin due to unimpressive battery and overall phone slowdowns (none necessarily related to Venom).
I have noticed in the Kontrol, there are tweaks such as DPI, remove NFC logo, etc. They all request root access as they should, and when the restart is forced the settings absolutely refuse to save. I've tried a fresh install with both superuser and superSU, neither seems to make a difference.
What am I missing here?
---
Edit - side issue, the front camera has not worked for months either, with any rom. It doesn't even show up as selectable in apps. Physical damage?
Thanks
nonameguy321 said:
Been a long time Venom user but recently decided to try Insertcoin due to unimpressive battery and overall phone slowdowns (none necessarily related to Venom).
I have noticed in the Kontrol, there are tweaks such as DPI, remove NFC logo, etc. They all request root access as they should, and when the restart is forced the settings absolutely refuse to save. I've tried a fresh install with both superuser and superSU, neither seems to make a difference.
What am I missing here?
---
Edit - side issue, the front camera has not worked for months either, with any rom. It doesn't even show up as selectable in apps. Physical damage?
Thanks
Click to expand...
Click to collapse
Ensure you have the latest custom recovery and SuperSU; then perform a full wipe then re-install the rom. If that didn't work you might have to re-flash your stock firmware then flash your custom recovery and SuperSU.
385
majmoz said:
Ensure you have the latest custom recovery and SuperSU; then perform a full wipe then re-install the rom. If that didn't work you might have to re-flash your stock firmware then flash your custom recovery and SuperSU.
Click to expand...
Click to collapse
Everything is indeed up to date.
Why do you think going back to stock would help with the issue(s) I described?
nonameguy321 said:
Everything is indeed up to date.
Why do you think going back to stock would help with the issue(s) I described?
Click to expand...
Click to collapse
Oftentimes that is the only way to clear out residual data. The other thing you could try is to go back to other rom and see if it is corrected.
majmoz said:
Ensure you have the latest custom recovery and SuperSU; then perform a full wipe then re-install the rom. If that didn't work you might have to re-flash your stock firmware then flash your custom recovery and SuperSU.
Click to expand...
Click to collapse
majmoz said:
Oftentimes that is the only way to clear out residual data. The other thing you could try is to go back to other rom and see if it is corrected.
Click to expand...
Click to collapse
Maybe I should have left out the part of the front facing camera not working.. or created that as a separate topic.
The one that I'm really having issue with is the Insertcoin Konfig settings not actually applying themselves.. tweaks on other ROMs worked without a problem..
I was able to install Chinese ZTE Axon Elite (A2015) Marshmallow rom to my international version of Axon Elite (A2016). Wifi, mobile data network and calling works. All Google apps are working too, Chinese rom has google services installed but those are needed to be activated by allowing them run in a background. Only Chinese and English languages available, but system is working in your local language after installing More Locale 2 from Google Play.
This ROM is not rooted, so you need to install Super User in TWRP right after installing this ROM.
Changes:
Added modem files (modem.b00-modem.b22, modem.mdt) from international B06 NON-HLOS.bin.
Minor build.prop changes (e.g. changed English as default language).
Removed stock recovery.
Added Google Play, Google Contact sync, Google Calendar sync, Google Gmail, Google Exchange sync, Google Phone, More Locale 2.
Removed all possible Chinese ZTE bloatware (over 200MB). I had to leave Mi-Assistant so that it can be used for allowing apps running in a background (example Google Play, Super SU).
[*]Added stock Marshmallow boot animation and removed boot sound.
Features:
Latest Google Security patch
MiFavor UI 4.0 with new themes and fonts
Applications Avatar (I have no idea what it is)
Toolbox - including compass, noise test, ruler, protractor, level meter, paintings
Calendar, shows weather for five next days
New Desktop backup and recovery capabilities
Long screenshots
More system Sleep functions
Smoother UI animations
SMS two-finger zoom
New power limits
Enhanced ZTE lock screen
...and some more which might not be useful in other countries than China (please check more details from: http://www.myzte.cn/thread-270646-1-1.html)
Working:
Wifi, mobile network, mobile data, bluetooth.
Fingerprint scanning.
Google Play services + other Google apps are working too (like Calendar, Contacts sync), but must be activated in Mi-Assistant Auto-start manager and allowing permissions in apps. Please see attached images for example.
Bugs and limitations:
NFC doesn't work.
Only Chinese and English languages, but it is possible to use More Locale 2 app (included in ROM) to change locale settings. Then apps (and part of the system) are working on your defined language. On my opinion it works just like in B06. More Locale requires Root access and executing ADB command (app shows the needed command) to change locale.
Download (B15M beta, updated 09.09.2016):
Mega https://mega.nz/#!cRAXTbqQ!UYTEzWb4AH5yZbcI4fK_09QBM5TYgvCCMMl1uTijetE
Based on the tip from @martas.vavra, I removed stock Chinese recovery so TWRP is not deleted after installing this rom.
Working Super user can be downloaded here https://cloud.tapatalk.com/s/57550023717f4/SuperSU_V2.62-3.zip. Thanks again @martas.vavra.
Quick steps:
(optional) Backup all apps by using ZTE own backup/restore app. It's then possible to restore apps after rom installation.
Install TWRP+root by using the method by @acer73: http://forum.xda-developers.com/zte-axon/development/zte-axon-elite-a2016-twrp-root-t3237760
Copy ZTE_Axon_Elite_A2016_unofficial_B15M_09092016 to SD card.
Boot to TWRP recovery.
Do full backup in TWRP.
Do factory reset in TWRP.
Install ZTE_Axon_Elite_A2016_unofficial_B15M_09092016 from SD card in TWRP. NOTE! Status bar is not progressing at all when installation is ongoing! Don't panic. Just wait, it will complete.
Install Super User .zip again.
Reboot. Please be patient, first boot will take minutes to complete.
After first boot is complete, start Mi-Assistant and enable apps (Google Play, Google Contacts, SuperSU... etc) in Auto-run Manager.
Enable app permissions for Calendar, Contacts, Phone, SMS, Storage in Settings -> Apps, App permissions.
Reboot.
(optional) Restore apps by using ZTE own backup/restore app. ZTE has removed Backup/restore app but here's download link for backup/restore app from B12M: https://mega.nz/#!hZQ2HTbb!IvTJu17kjibXGSJBsRUutz0wwPZL0XlruDVAyExqsC8
Note to users: I'm not responsible if you brick your phone, so please be careful!
Thank you for your efforts! Great to hear that there are only minor bugs. :fingers-crossed:
Leaves me thinking about why ZTE does not provide this update by themselves if there are only few things needed to be adjusted in order to make this work...
There is a CM 13 for chinese Axon http://www.myzte.cn/thread-263527-1-1.html It should work
martas.vavra said:
There is a CM 13 for chinese Axon http://www.myzte.cn/thread-263527-1-1.html It should work
Click to expand...
Click to collapse
I am afraid it does not work, as @brainmaster already tried booting it - without success.
Please refer to his post here:
http://forum.xda-developers.com/showpost.php?p=66497035&postcount=5
This is great! Thanks a lot
GalaxyFan88 said:
I am afraid it does not work, as @brainmaster already tried booting it - without success.
Please refer to his post here:
http://forum.xda-developers.com/showpost.php?p=66497035&postcount=5
Click to expand...
Click to collapse
But maybe it will work using the same method the opener of the thread used! (aka replacing the radio). I don't know though...
Dapalm said:
This is great! Thanks a lot
But maybe it will work using the same method the opener of the thread used! (aka replacing the radio). I don't know though...
Click to expand...
Click to collapse
You can read here. Its not just about the radio partition.
Like already mentioned, when trying to add PIN lock, settings will force close. I also compared international B05 and Chinese marshmallow rom files and noticed differences on fingerprint modules and apps, so I believe we are out of luck here.
suunnittelija said:
Like already mentioned, when trying to add PIN lock, settings will force close. I also compared international B05 and Chinese marshmallow rom files and noticed differences on fingerprint modules and apps, so I believe we are out of luck here.
Click to expand...
Click to collapse
I think that copying that files, modules and apps would be possible, from one to another, won't you? I have no idea of how to doing it, but maybe it is easy for someone experimented in rom's modding.
@suunnittelija how about the batttery life?
Mononitoto said:
how about the batttery life?
Click to expand...
Click to collapse
Unfortunately I don't know, because I was testing this rom just half day. On that time I didn't notice battery drain. I returned back to B06 because my phone has to be password protected and I just can't live anymore without fingerprint scanner.
suunnittelija said:
Unfortunately I don't know, because I was testing this rom just half day. On that time I didn't notice battery drain. I returned back to B06 because my phone has to be password protected and I just can't live anymore without fingerprint scanner.
Click to expand...
Click to collapse
What would be necessary to do, to port fingerprint scanner etc to this rom?
Mononitoto said:
What would be necessary to do, to port fingerprint scanner etc to this rom?
Click to expand...
Click to collapse
Probably it's nothing to do with fingerprint scanner. I checked logcat file and settings will force close before that. Settings will force close right after trying to enable PIN code lock.
Code:
FATAL EXCEPTION: AsyncTask #3
Process: com.android.settings, PID: 8191
java.lang.RuntimeException: An error occurred while executing doInBackground()
at android.os.AsyncTask$3.done(AsyncTask.java:309)
at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:354)
at java.util.concurrent.FutureTask.setException(FutureTask.java:223)
at java.util.concurrent.FutureTask.run(FutureTask.java:242)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:234)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
at java.lang.Thread.run(Thread.java:818)
Caused by: java.lang.NullPointerException: Attempt to read from field 'int com.android.server.LockSettingsStorage$CredentialHash.version' on a null object reference
With cyanogenmod there has been similar issues with some devices and error has been caused by wrong baseband (https://forum.cyanogenmod.org/topic/118507-cant-enable-screen-lock/?page=3), which means that users have not been updating the baseband before updating the latest version of cyanogenmod. This might be the same issue, I used lollipop baseband to get this work.
I created new version based on latest Chinese B10M (previous was B09M):
https://mega.nz/#!1QgxVbza!9S0ugYNp3QmJvPxzNvcb2XB_YCsHygf3NPdohVisSg4
I don't know what kind of changes they have done for this version, but in our A2016 it has the same issues than previous version (security settings force closing etc.).
suunnittelija said:
I created new version based on latest Chinese B10M (previous was B09M):
https://mega.nz/#!1QgxVbza!9S0ugYNp3QmJvPxzNvcb2XB_YCsHygf3NPdohVisSg4
I don't know what kind of changes they have done for this version, but in our A2016 it has the same issues than previous version (security settings force closing etc.).
Click to expand...
Click to collapse
Continue your great work !
How to restore 5.0.1 ?
kacsa105 said:
How to restore 5.0.1 ?
Click to expand...
Click to collapse
Easiest and the best way is to take full twrp backup first before installing this rom. Then it can be restored in twrp and phone is restored to the state it was before.
If backup is not made, then stock B05 update.zip needs to be installed in recovery (in stock or twrp).
@kacsa105 pointed out that adb root method doesn't work anymore with B10M. I didn't notice it because I installed recovery + supe su in right after I installed B10M in twrp.
If you are now in stock Chinese recovery, then follow these steps to restore stock B05 in stock (Chinese) recovery:
1. download B05 from:
http://download.ztedevice.com/UpLoadFiles/product/643/6549/soft/2016042111364202.zip. Unzip it and find update.zip
2. place update.zip to phone internal SD card
3. shut down your phone
4. reboot to recovery: Press and hold Volume up button then Press and hold Power button. When ZTE logo appears, stop pressing Power button but continue pressing Volume up until it goes to recovery.
5. It should be now in stock Chinese recovery. You need to use volume up/down buttons and move it to the selection where is written something on Chinese but with letters SD (which means your internal SD card). Press Power button to select it.
6. Use vol down to navigate until you see update.zip and choose it with power button. If I remember correctly, you need to confirm Yes (it should be in English if I remember it correctly).
7. After it has been updated, recovery asks something again in Chinese. Don't change the selection, just use power button to select what it proposes, and system will boot.
Just wait until your phone boots back to system. If it keeps crashing, just power it down and reboot again to recovery. Recovery should be in English now. Then clear cache and dalvik (or was it factory reset?) and boot to system again.
Google play crashed, when download big data games. Solution pls
Are known any major issues with this ROM? Tired of Mi-sh*t, I'm thinking about install TWRP, make a backup and later this or CM. Is worth it?
hik4ru said:
Are known any major issues with this ROM? Tired of Mi-sh*t, I'm thinking about install TWRP, make a backup and later this or CM. Is worth it?
Click to expand...
Click to collapse
I'm not using this rom because PIN lock screen and fingerprint doesn't work (CM has these issues too). Then it has some China specific in the settings. Be careful when installing this B10 rom, you need to install twrp recovery + root again in recovery right after flashing this rom. Otherwise you will loose root and recovery is replaced by stock Chinese.
On my opinion this is not worth of flashing, you don't even notice major differences. In some devices Marshmallow has improved performance and battery life, but I didn't notice any difference. I'm using stock B06 (5.0.2) with xposed (+some modules installed) and I'm happy with it.
Of course this rom is fun to try if you want to test how Marshmallow will look in our device.
suunnittelija said:
I'm not using this rom because PIN lock screen and fingerprint doesn't work (CM has these issues too). Then it has some China specific in the settings. Be careful when installing this B10 rom, you need to install twrp recovery + root again in recovery right after flashing this rom. Otherwise you will loose root and recovery is replaced by stock Chinese.
On my opinion this is not worth of flashing, you don't even notice major differences. In some devices Marshmallow has improved performance and battery life, but I didn't notice any difference. I'm using stock B06 (5.0.2) with xposed (+some modules installed) and I'm happy with it.
Of course this rom is fun to try if you want to test how Marshmallow will look in our device.
Click to expand...
Click to collapse
How to flash recovery in recovery? I have tried to flash it via ADB, but there was stock recovery after reboot. And when I flash supersu zip the system won't boot.
Odesláno z mého ZTE A2016 pomocí Tapatalk
suunnittelija said:
I'm not using this rom because PIN lock screen and fingerprint doesn't work (CM has these issues too). Then it has some China specific in the settings. Be careful when installing this B10 rom, you need to install twrp recovery + root again in recovery right after flashing this rom. Otherwise you will loose root and recovery is replaced by stock Chinese.
On my opinion this is not worth of flashing, you don't even notice major differences. In some devices Marshmallow has improved performance and battery life, but I didn't notice any difference. I'm using stock B06 (5.0.2) with xposed (+some modules installed) and I'm happy with it.
Of course this rom is fun to try if you want to test how Marshmallow will look in our device.
Click to expand...
Click to collapse
What modules are you using with Xposed?
Enviado desde mi ZTE A2016 mediante Tapatalk
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