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.
RHi,
I flashed latest cm-rom and lateyt gapps. Everything went OK, but when I try to install google play service, I get error-code 505. It doesn't matter which gapps I use, it's always the same problem.... Could someone help, please? THX!!!
Check the CM12.1 thread. People mention which gapps work more consistently.
blueberry.sky said:
Check the CM12.1 thread. People mention which gapps work more consistently.
Click to expand...
Click to collapse
Which thread exactly? Sorry, if this is a dumb question, but I´m too blind to find
DocRobbe said:
Which thread exactly? Sorry, if this is a dumb question, but I´m too blind to find
Click to expand...
Click to collapse
I was able to get CM 12.1 to run on my Fire using TKGapps.
I used the pico universal DPI
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
DocRobbe said:
Which thread exactly? Sorry, if this is a dumb question, but I´m too blind to find
Click to expand...
Click to collapse
http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416
neozen21 said:
I was able to get CM 12.1 to run on my Fire using TKGapps.
I used the pico universal DPI
http://forum.xda-developers.com/android/software/tk-gapps-t3116347
Click to expand...
Click to collapse
I tried these, but they don´t work, too.
It is always the same problem that I can´t install Google Play Games, which I need for my favorite game.
I performed a factory reset, installed the CM-ROM and the Gapps-zip, but it doesn´t work...
Try these gapps http://rootjunkysdl.com/getdownload...gen/CM12/open_gapps-arm-5.1-pico-20151120.zip They were reported to work.
DocRobbe said:
I tried these, but they don´t work, too.
It is always the same problem that I can´t install Google Play Games, which I need for my favorite game.
I performed a factory reset, installed the CM-ROM and the Gapps-zip, but it doesn´t work...
Click to expand...
Click to collapse
I was able to successfully install it by sideloading with ADB
I tried attaching the file, but it's too big, so.. just get it with the APK Downloader extension in Chrome...
neozen21 said:
I was able to successfully install it by sideloading with ADB
I tried attaching the file, but it's too big, so.. just get it with the APK Downloader extension in Chrome...
Click to expand...
Click to collapse
Thanks alot, I will try it tomorrow...
DocRobbe said:
I tried these, but they don´t work, too.
It is always the same problem that I can´t install Google Play Games, which I need for my favorite game.
I performed a factory reset, installed the CM-ROM and the Gapps-zip, but it doesn´t work...
Click to expand...
Click to collapse
If your problem is only with G play games then see this message http://forum.xda-developers.com/showpost.php?p=64232246&postcount=535
If you are seeing "play services have stopped" that's a different problem and you need an earlier gapps version, see http://forum.xda-developers.com/showpost.php?p=64149284&postcount=7
I had this error and clearing cache and data didn't work. I installed the Play Games app using ADB from a laptop and it worked first time though. Was a bit odd because I only used ADB to get a more detailed install error but instead it worked. I'm happy with that
Hi guys,
I finally got it with your help. I downloaded the apk-file from apk.mirror, copied it to my sd-card and simply installed it by choosing the .apk from the filemanager and ... it worked!!!
Thanks a lot to all of you... you really rock!
just opengapps pico. wipe cache and dalivk. install gapps then the rom then superuser if need. it works. someone has tested
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.
Hi everyone!
I have a rooted Z3C and it is a fantastic phone, I love it. The problem is that I bought a television sport service that includes the possibility to watch games on your phone, it's called Bein Sport. This app is able to detect root and refuse to play any videos so the service I bought becomes kind of useless
The worst part is that I don't want to mess around, just want to watch games on my phone and use the service for what it was thought. Si I thought i'd give a shout here, has anyone been able to bypass that annoying feature? I don't even understand why they don't like rooted phone
thanks!
McGuigew said:
Hi everyone!
I have a rooted Z3C and it is a fantastic phone, I love it. The problem is that I bought a television sport service that includes the possibility to watch games on your phone, it's called Bein Sport. This app is able to detect root and refuse to play any videos so the service I bought becomes kind of useless
The worst part is that I don't want to mess around, just want to watch games on my phone and use the service for what it was thought. Si I thought i'd give a shout here, has anyone been able to bypass that annoying feature? I don't even understand why they don't like rooted phone
thanks!
Click to expand...
Click to collapse
There is an Xposed module for masking root on your phone, not sure if it will work or not. There is another Xposed app that offers help as well.
Installing Xposed can sometimes be tricky, make sure you find the right arm zip or you could be facing bootloops.
The place to start if you want to go down that road is here
Didgesteve said:
There is an Xposed module for masking root on your phone, not sure if it will work or not. There is another Xposed app that offers help as well.
Installing Xposed can sometimes be tricky, make sure you find the right arm zip or you could be facing bootloops.
The place to start if you want to go down that road is here
Click to expand...
Click to collapse
Hey Steve, thanks for answering. I am willing to try your solution so I read the page you showed me to install Xposed. I downloaded the last version of the ARM (note arm64, or x86), should I boot into recovery and flash it now? I reaaally don't want to mess up and have to reinstall it all! Is the Z3C part of the phones that have problems with Xposed? cheers!
McGuigew said:
Hey Steve, thanks for answering. I am willing to try your solution so I read the page you showed me to install Xposed. I downloaded the last version of the ARM (note arm64, or x86), should I boot into recovery and flash it now? I reaaally don't want to mess up and have to reinstall it all! Is the Z3C part of the phones that have problems with Xposed? cheers!
Click to expand...
Click to collapse
I use Xposed, it's very popular and works fine on the Z3c. I think the emphasis is to read about it before you do it, as many people rush in, go to downloads, install the one with the latest build number and then come crying to the forum about bootloops.
The fact that you have read ahead on the page before you did anything assures me that you won't mess it up :good:
If it reassures you, I am using xposed-v80-sdk22-arm.zip on a 5.1.1. build. But there are more recent versions out now, although I don't know what the advantages of using those are. Perhaps later versions cover the use of MM. Can anybody enlighten me on that?
Edit: Once you have flashed the installer in recovery, restart the phone and then install XposedInstaller_3.0_alpha4.apk
With that installed and running you can find the modules and install them.
Each install or change of settings requires a restart.
Didgesteve said:
I use Xposed, it's very popular and works fine on the Z3c. I think the emphasis is to read about it before you do it, as many people rush in, go to downloads, install the one with the latest build number and then come crying to the forum about bootloops.
The fact that you have read ahead on the page before you did anything assures me that you won't mess it up :good:
If it reassures you, I am using xposed-v80-sdk22-arm.zip on a 5.1.1. build. But there are more recent versions out now, although I don't know what the advantages of using those are. Perhaps later versions cover the use of MM. Can anybody enlighten me on that?
Edit: Once you have flashed the installer in recovery, restart the phone and then install XposedInstaller_3.0_alpha4.apk
With that installed and running you can find the modules and install them.
Each install or change of settings requires a restart.
Click to expand...
Click to collapse
Thanks! I'm gonna procede and give you a heads up! cheers
I am unable to flash the xposed.zip in recovery (Philz). It says "failed to set up expected mounts for install". I have tried on internal SD, external SD and even USB... any idea?
McGuigew said:
I am unable to flash the xposed.zip in recovery (Philz). It says "failed to set up expected mounts for install". I have tried on internal SD, external SD and even USB... any idea?
Click to expand...
Click to collapse
Check you have root, install SuperSU and make sure it's up to date
Didgesteve said:
Check you have root, install SuperSU and make sure it's up to date
Click to expand...
Click to collapse
Yep, installed, up do date, and some apps even use my root without any issues
If anyone comes here, here is what happened to me: I tried to install Xposed to try this trick but my phone would'nt falsh because it couldn't mount /system. I assumed that it was a problem with partitions. I tried deleting root manually but the app always found root even when I wasn't rooted anymore (beware, this app is pretty smart). I ended up having to go back to stock which sucks because the battery is really bad in comparison, but anyway I can watch football! Cheers
i don't know what i did ,this tablet was working fine for 2 years with RR custom rom i used root junky tools to root and install RR custom rom,pico gaps, xposedframework ,and android custom boot animation from 5.0,1 , it was working one second and then all of a sudden the google app , gmail ,and youtube all say
" "app name" relies on google play services which is not supported by your device ,contact manufacturer "
how do i fix this and how did it happen? funny thing is that the play store still works and apps can update but i can't use any google apps
all i did was log into a secondary account and then try and install the google app which was already installed on the primary account , the google app stopped working then it worked and then it stopped again and now none of the google apps will work on either account,how do i fix this?
google play services version is 11.9.75(230-182402865)
i tried uninstalling the google app from the secondary account and then tried using gmail and youtube on the secondary account and it does not work, then tried on the primary account and it does not work , then i tried uninstalling the google app from the primary account
and rebooting , and it still does not work
how can i fix this without having to reflash everything?
how do i stop this from happening again?
and i have 2 other tablets i set ap the same way only on those i used flash fire because they were on 5.1.1 i think
do i now have to worry about it happening to those tablets too?
should i not ever update or install any google apps from the play store again?
update: ok this is really strange , i booted one of my other tablets i set up the same way only it was flashed with flash fire from 5.1.1 instead of 5.0.1 and TWRP
(i have 3 5th gen fire 7's running RR custom rom, root, with xposed , 2 were on 5.1.1 and flashed with flash fire and one was on 5.0.1 and flashed with TWRP , all with root junky tools)
i first went to gmail and then to youtube both worked fine , then i went to the play store and i updated an app , not an app that uses play services though,
then i noticed a notification pop up that said something about google play services not being supported on the device , so i went to launch gmail again and then it was doing the same thing as it was on the other tablet , then i launched youtube , and same thing
then like a minute later after closing the apps and trying them again , they worked fine
i really would like to to know what is going on here
next i will try the 3rd tablet, , that one was the last one i set up and has the least apps on it
just to be clear here the play store works just fine , i can update ,install and uninstall apps through it
and my account is visible in the playstore and my accounts show up in the tablet
just cant get any google apps like gmail ,youtube , google plus and the google app working
gdroid666 said:
i tried uninstalling the google app from the secondary account and then tried using gmail and youtube on the secondary account and it does not work, then tried on the primary account and it does not work , then i tried uninstalling the google app from the primary account
and rebooting , and it still does not work
how can i fix this without having to reflash everything?
how do i stop this from happening again?
and i have 2 other tablets i set ap the same way only on those i used flash fire because they were on 5.1.1 i think
do i now have to worry about it happening to those tablets too?
should i not ever update or install any google apps from the play store again?
update: ok this is really strange , i booted one of my other tablets i set up the same way only it was flashed with flash fire from 5.1.1 instead of 5.0.1 and TWRP
(i have 3 5th gen fire 7's running RR custom rom, root, with xposed , 2 were on 5.1.1 and flashed with flash fire and one was on 5.0.1 and flashed with TWRP , all with root junky tools)
i first went to gmail and then to youtube both worked fine , then i went to the play store and i updated an app , not an app that uses play services though,
then i noticed a notification pop up that said something about google play services not being supported on the device , so i went to launch gmail again and then it was doing the same thing as it was on the other tablet , then i launched youtube , and same thing
then like a minute later after closing the apps and trying them again , they worked fine
i really would like to to know what is going on here
next i will try the 3rd tablet, , that one was the last one i set up and has the least apps on it
just to be clear here the play store works just fine , i can update ,install and uninstall apps through it
and my account is visible in the playstore and my accounts show up in the tablet
just cant get any google apps like gmail ,youtube , google plus and the google app working
Click to expand...
Click to collapse
Google (any many 3rd party) apps rely on Google Play Services for core/shared functionality. Play Services/Framework is supposed to seemlessly auto-update in the background and usually does. Believe you saw that happen on your 2nd tablet. For whatever reason the framework appears borked on the 1st device.
As previously advised fixing Google Play Services issues is difficult/unreliable without a fresh install. Given you can boot twrp on the device having this issue I suggest the following:
- boot into TWRP and backup the current (nonworking) environment
- dirty flash RR, SuperSU and a suitable OpenGApps package
- verify everything is working correctly
- proceed to a 'clean' flash if the trouble persists
Dirty flashing will preserve existing apps/data/settings and is obviously less disruptive. Effectively the way a FireOS OTA update works. However, it doesn't always work and can create additional problems.
Davey126 said:
Google (any many 3rd party) apps rely on Google Play Services for core/shared functionality. Play Services/Framework is supposed to seemlessly auto-update in the background and usually does. Believe you saw that happen on your 2nd tablet. For whatever reason the framework appears borked on the 1st device.
As previously advised fixing Google Play Services issues is difficult/unreliable without a fresh install. Given you can boot twrp on the device having this issue I suggest the following:
- boot into TWRP and backup the current (nonworking) environment
- dirty flash RR, SuperSU and a suitable OpenGApps package
- verify everything is working correctly
- proceed to a 'clean' flash if the trouble persists
Dirty flashing will preserve existing apps/data/settings and is obviously less disruptive. Effectively the way a FireOS OTA update works. However, it doesn't always work and can create additional problems.
Click to expand...
Click to collapse
ok thanks so what kind of additional problems? nothing serious like bricking right?
i do not know the difference between clean and dirty flash so how would i go about that from TWRP
i don't even remember how to get TWRP , i assume i need to get the tablet into fastboot ,i also forgot how i do that
and i may have uninstalled the clockwork mod driver from my PC not sure if i need those or not
is there a guide you can link me to on how to get the tablet into tethered TWRP and which option i need to select from it , i think i have the files i used for the initial flash somewhere i should be able to find those, the RR rom, gapps ,
super SU
also where would the backup go exactly? to an SD card? would you happen to know how much space i would need , if it goes to internal then how do i get the backup to Sd?
also what about xposed framework would that remain intact after a "dirty flash"
should i also add the xposed framework to the zip at the time of dirty flash if not or would i have to do after?
i can not remember too much about how i set this thing up and this is probably the only time i have ever used TWRP , the other 2 tablets i used FF
also could i just a dirty flash from FF? , guess i should use TWRP since i can note make a backup with FF right?
EDIT: i really have no clue what i am doing here ,what are the chances that when google play services updates in the background next time it will just fix itself? should i wait a few weeks and see if it corrects itself 1st?
gdroid666 said:
EDIT: i really have no clue what i am doing here ,what are the chances that when google play services updates in the background next time it will just fix itself? should i wait a few weeks and see if it corrects itself 1st?
Click to expand...
Click to collapse
Try updating Google Play Services from here. It usually doesn't work but worth a shot given your level of familiarity with managing your custom build.
Davey126 said:
Try updating Google Play Services from here. It usually doesn't work but worth a shot given your level of familiarity with managing your custom build.
Click to expand...
Click to collapse
yeah i tried it a few times ,rebooted and tried again and it is snot working
it is weird because on gmail i can click outside the message box that says no google play services and then i see my gmail account and it says getting your messages , and syncing but it just hangs forever and with youtube i get notifications for new videos for channels i am subbed to, when i click on the notification and open youtube from there the video plays but there is no video just audio and the no google play services message is there and everything is greyed out but i can hear the sound from the video
gdroid666 said:
yeah i tried it a few times ,rebooted and tried again and it is snot working
it is weird because on gmail i can click outside the message box that says no google play services and then i see my gmail account and it says getting your messages , and syncing but it just hangs forever and with youtube i get notifications for new videos for channels i am subbed to, when i click on the notification and open youtube from there the video plays but there is no video just audio and the no google play services message is there and everything is greyed out but i can hear the sound from the video
Click to expand...
Click to collapse
Yep - not unexpected from a borked Play Services is install. You're probably gonna have to bit the bullet and perform a fresh install. At that time it may be wise to consider a shift to a different ROM. Nothing wrong with RR but it isn't being updated which could eventually lead to further issues.
Davey126 said:
Yep - not unexpected from a borked Play Services is install. You're probably gonna have to bit the bullet and perform a fresh install. At that time it may be wise to consider a shift to a different ROM. Nothing wrong with RR but it isn't being updated which could eventually lead to further issues.
Click to expand...
Click to collapse
well the rom is working on the other 2 tablets it acted up for a minute then worked again on one of them
i am wondering if that issue could be because i had the internal memory maxed out?
it was almost 100% full then i started moving some apps to the sd card , maybe it tried to update and ran out of memory or something and got only partially updated?
gdroid666 said:
well the rom is working on the other 2 tablets it acted up for a minute then worked again on one of them
i am wondering if that issue could be because i had the internal memory maxed out?
it was almost 100% full then i started moving some apps to the sd card , maybe it tried to update and ran out of memory or something and got only partially updated?
Click to expand...
Click to collapse
Possibly. Trying to perform forensics w/o supporting data is a bit of a fools errand. What happened to your device is neither common nor rare. I would focus on remediation which likely means an uncomfortable rebuild (due to unfamiliarity with procedures). You are fortunate to have TWRP access which removes most of the risk. Unless it self-resolves (unlikely) you're going to have to get your hands dirty one way or the other.
Davey126 said:
Possibly. Trying to perform forensics w/o supporting data is a bit of a fools errand. What happened to your device is neither common nor rare. I would focus on remediation which likely means an uncomfortable rebuild (due to unfamiliarity with procedures). You are fortunate to have TWRP access which removes most of the risk. Unless it self-resolves (unlikely) you're going to have to get your hands dirty one way or the other.
Click to expand...
Click to collapse
so what would the risk be if i were to try and side load the .APK's for the play services to try and fix it that way?
which .apk's would i need and in what order would i need to install them , is it worth a shot to try and manually install them from .apk and see hat happens?
if not and i need to do twrp route then would i install the xposed framework zip at the same time
can i flash the rom , gapps, super su , xposed, and custom boot animation zips or would i need to reboot 1st , which order would be best to line them up in TWRP to flash
also what do i do for dirty flash, ? just not wipe anything like dalvik cache? what do i wipe and not wipe?
ok i have booted into TWRP and i made a backup of everything including cache
now how would i go about dirty flashing
i just want to know what to do about xposed , will it remain in tact if i dirty flash the rom , gapps and super SU ?
or do i need to add the xposed zip when i do the dirty flash? would i need to also side load the xposed installer .apk after too again?
in what order do i need to add the zips to the install list? and what do i need to wipe and not wipe and what order?
gdroid666 said:
ok i have booted into TWRP and i made a backup of everything including cache
now how would i go about dirty flashing
i just want to know what to do about xposed , will it remain in tact if i dirty flash the rom , gapps and super SU ?
or do i need to add the xposed zip when i do the dirty flash? would i need to also side load the xposed installer .apk after too again?
in what order do i need to add the zips to the install list? and what do i need to wipe and not wipe and what order?
Click to expand...
Click to collapse
As a precaution you should copy (not move) the TWRP folder to off-line storage. If the folder is located in the external SD card that's reasonably safe. Take a deep breath and proceed as follows:
- verify you have all of the required zips located somewhere on the device or external SD card
- boot into TWRP
- wipe the system partition ONLY
- install the following zips in the order listed (individually or as a group; doesn't matter):
--> RR ROM
--> GApps package (suggest arm/5.1/nano; nothing larger than mini)
--> SuperSU 2.76 or 2.82 SR5 (avoid versions between 2.76 and 2.82)
--> Xposed Framework v89
Once all the of installations are complete accept the offer to wipe cache/dalvik and then reboot system.
Davey126 said:
As a precaution you should copy (not move) the TWRP folder to off-line storage. If the folder is located in the external SD card that's reasonably safe. Take a deep breath and proceed as follows:
- verify you have all of the required zips located somewhere on the device or external SD card
- boot into TWRP
- wipe the system partition ONLY
- install the following zips in the order listed (individually or as a group; doesn't matter):
--> RR ROM
--> GApps package (suggest arm/5.1/nano; nothing larger than mini)
--> SuperSU 2.76 or 2.82 SR5 (avoid versions between 2.76 and 2.82)
--> Xposed Framework v89
Once all the of installations are complete accept the offer to wipe cache/dalvik and then reboot system.
Click to expand...
Click to collapse
ok i am back again , i still have not done the dirty flash yet because i have been busy
i will probably try it soon with the original files i used to flash the rom and xposed with
but first i would like to get your input on this theory i have
ok i am thinking that because i have 3 5th gen fire 7 tablets all rooted and running custom roms ,and only one is having a problem , and that the one with the problem is the one with TWRP /unlocked bootloader
that this may be the cause of the problem
https://www.xda-developers.com/google-blocks-gapps-uncertified-devices-custom-rom-whitelist/
i have the same pico gapps flashed on all 3 devices but only one device has the unlocked bootloader
and that is the broken device , and the message that i get says " [app name] relies on google play services which is not supported by your device.please contact the device manufacturer"
i went into the play store under settings it did indeed say that the device is uncertified
i then installed an app to get my GFS device ID ,and converted the hexadecimal number into a decimal number and successfully submitted it to the whitelist site google/android/uncertified
it still did not fix the problem , then i cleared data and cache of the play store in settings/apps/play store
and tried again and nothing still , then i checked in play store settings and saw it no longer says incertified but it the field is gone completely now it does not say uncertified but it does not say certified either
then i went back to settings /apps/ google play store and removed updates and reverted back to factory play store and checked settings again there is still no field where the uncertified used to be and it is still not working
and now i don't know how to get the play store to update to latest version aside from sideloading it
i am not sure what to do next but what do you think about my tablet being broken because google now blocking gapps on uncertified devices as being the cause for this issue ,seems really strange to me that only the one tablet with the unlocked bootloader is being affected
but why did the whitelist also not work then ,i am really confused now and i am not seeing any other posts here about similar issues
gdroid666 said:
ok i am back again , i still have not done the dirty flash yet because i have been busy
i will probably try it soon with the original files i used to flash the rom and xposed with
but first i would like to get your input on this theory i have
ok i am thinking that because i have 3 5th gen fire 7 tablets all rooted and running custom roms ,and only one is having a problem , and that the one with the problem is the one with TWRP /unlocked bootloader
that this may be the cause of the problem
https://www.xda-developers.com/google-blocks-gapps-uncertified-devices-custom-rom-whitelist/
i have the same pico gapps flashed on all 3 devices but only one device has the unlocked bootloader
and that is the broken device , and the message that i get says " [app name] relies on google play services which is not supported by your device.please contact the device manufacturer"
i went into the play store under settings it did indeed say that the device is uncertified
i then installed an app to get my GFS device ID ,and converted the hexadecimal number into a decimal number and successfully submitted it to the whitelist site google/android/uncertified
it still did not fix the problem , then i cleared data and cache of the play store in settings/apps/play store
and tried again and nothing still , then i checked in play store settings and saw it no longer says incertified but it the field is gone completely now it does not say uncertified but it does not say certified either
then i went back to settings /apps/ google play store and removed updates and reverted back to factory play store and checked settings again there is still no field where the uncertified used to be and it is still not working
and now i don't know how to get the play store to update to latest version aside from sideloading it
i am not sure what to do next but what do you think about my tablet being broken because google now blocking gapps on uncertified devices as being the cause for this issue ,seems really strange to me that only the one tablet with the unlocked bootloader is being affected
but why did the whitelist also not work then ,i am really confused now and i am not seeing any other posts here about similar issues
Click to expand...
Click to collapse
Your non-functioning tablet does NOT have an "unlocked bootloader". It has a coding oversight that allows a custom recovery (TWRP) to be booted from fastboot. In all other respects it is identical to the other two from a capability/signature perspective.
The policy change/enforcement you reference is not the cause as Google only starting blocking access a couple weeks ago. Nor will it likely impact this device based on my interpretation of the criteria Google applies.
What to do next? Reload as previously outlined. I also recommend (rather strongly) that you consider migrating to a supported ROM. At present that's either Fire Nexus or Lineage.
ok i finally got around to doing this
after the flash everything looked good, but i am still getting no play services , can't open youtube or gmail still
i get play services not supported by this device
gdroid666 said:
ok i finally got around to doing this
after the flash everything looked good, but i am still getting no play services , can't open youtube or gmail still
i get play services not supported by this device
Click to expand...
Click to collapse
Sorry to hear that. Best move on to second recommendation from previous post.
Davey126 said:
Sorry to hear that. Best move on to second recommendation from previous post.
Click to expand...
Click to collapse
from what i have been reading trying to find a fix that probably will not work either
looks like a lot of people having this issue even with real android devices with factory roms including samsung phones on N and lenovo tablets
this OS is really turning into a complete dumpster fire, Google should have provided a fix but i feel that they are deliberately causing these issues to kill devices to drive sales or for some other nefarious purpose
either that or they are just totally incompetent
i have not seen a single person who posted that they have this issue get a resolution to it
how is this acceptable how have they not been sued for this yet?
i understand that this is a hacked Amazon device but this issue seems to persist across legit devices with factory roms as well and there is no official solution what are people to do if they bought an expensive Samsung device and have this unsolvable issue?
just toss it in the bin and buy a new one i guess
i can;t beleive there is no solution that is as simple as installing some .apk's
gdroid666 said:
from what i have been reading trying to find a fix that probably will not work either
looks like a slot of people having this issue even with real android devices with factory rom including samsung phone on N and lenovo tabets
this OS is really turning into a complete dumpster fire, Google should have provided a fix but i feel that they are deliberately causing these issues to kill devices to drive sales or for some other nefarious purpose
either that or they are just totally incompetent
i have not seen a single person who posted that they have this issue get a resolution to it
how is this acceptable how have they not been sues for this yet?
i understand that this is a hacked Amazon device but this issue seems to persist across legit devices with factory roms as well and there is no official solution what are people to do if they bought an expensive Samsung device and have this unsolvable issue?
just toss it in the bin and buy a new one i guess
Click to expand...
Click to collapse
Sorry, don't subscribe to that line of thought. Google Play Services issues are largely self inflicted and almost always resolvable. Move to a supported ROM and the problem will likely go away. If you dumpster it in favor of something different stay away from current gen Amazon gizmos. With exception to the HD 10 none are rootable. Good luck.
Davey126 said:
Sorry, don't subscribe to that line of thought. Google Play Services issues are largely self inflicted and almost always resolvable. Move to a supported ROM and the problem will likely go away. If you dumpster it in favor of something different stay away from current gen Amazon gizmos. With exception to the HD 10 none are rootable. Good luck.
Click to expand...
Click to collapse
Yes i will try a new rom i guess which one is the most like the one i have now ?
and do you happen to know if any of them will support casting from the quick settings shade?
I actually did just buy the fire HD 10 on prime day for that very reason
but besides root what exactly can be done with it?
I mean no there are no custom roms or TWRP yet right
is anyone working on TWRP or a custom rom?
I kinda think i might want to leave it on fire OS to try out the always listening Alexa and Alexa show capabilities
Is it like the fire 7 where i can already remove lock screen ads install play store and change the launcher to nova without root even?
What does root allow on the HD 10 that is useful right now?
Would it possible to install xposed and youtube adaway on it with fire OS?
I have not opened it yet so do all current FW's support root still?
does the FW that added the Alexa show capabilities to fire OS still support root?
gdroid666 said:
Yes i will try a new rom i guess which one is the most like the one i have now ?
and do you happen to know if any of them will support casting from the quick settings shade?
I actually did just buy the fire HD 10 on prime day for that very reason
but besides root what exactly can be done with it?
I mean no there are no custom roms or TWRP yet right
is anyone working on TWRP or a custom rom?
I kinda think i might want to leave it on fire OS to try out the always listening Alexa and Alexa show capabilities
Is it like the fire 7 where i can already remove lock screen ads install play store and change the launcher to nova without root even?
What does root allow on the HD 10 that is useful right now?
Would it possible to install xposed and youtube adaway on it with fire OS?
I have not opened it yet so do all current FW's support root still?
does the FW that added the Alexa show capabilities to fire OS still support root?
Click to expand...
Click to collapse
- I would go with Fire Nexus + Xposed and a few select modules for maximum flexibility if seeking to mimic the RR UX
- head here for the latest developments on HD 10 platform
- nothing wrong with curated FireOS + xposed once rooted. I ran with that config for quite some time with no regrets