Related
This is CyanogenMod 12.1 (Lollipop (5.1.1 – LMY49F)) for ASUS’s Transformer Pad (TF701T – Macallan).
This thread is for device specific shakeout and bug fixing.
This is not a production build.
Please always supply a system log (logcat) and a kernel log (kmsg) when reporting an issue.
Please read through the entire blog post:
http://droidbasement.com/db-blog/?p=3765
Please take note of the 'Known Issues'.
Download: http://get.cm/?device=tf701t
Note:
SELinux is in Enforcing mode.
First one to answer!
At least! CM 12.1 for our beloved TF701!
And yesterday we got TWRP recovery after more than a year thinking that it was impossible.
New life for the best Asus Android Transformer. Thank you, pershoot.
Thanks so much for this. I'm very excited to get my 701 up to date.
I'm working on a clean installation (12.1-20150601)
Got to the screen where I select the apps to reinstall from a previous installation. After selecting the apps to reinstall the CANCEL/DONE buttons were difficult to select. It seemed to "take" after tapping around the "Done" button a bunch of times.
I have the new TWRP installed (in case that makes any difference).
david31262 said:
Thanks so much for this. I'm very excited to get my 701 up to date.
I'm working on a clean installation (12.1-20150601)
Got to the screen where I select the apps to reinstall from a previous installation. After selecting the apps to reinstall the CANCEL/DONE buttons were difficult to select. It seemed to "take" after tapping around the "Done" button a bunch of times.
I have the new TWRP installed (in case that makes any difference).
Click to expand...
Click to collapse
I noticed the same behaviour on one of my older BlissPop builds. It went away on my newest build. Something to keep track of now that I'm not the only person that was experiencing it.
david31262 said:
Thanks so much for this. I'm very excited to get my 701 up to date.
I'm working on a clean installation (12.1-20150601)
Got to the screen where I select the apps to reinstall from a previous installation. After selecting the apps to reinstall the CANCEL/DONE buttons were difficult to select. It seemed to "take" after tapping around the "Done" button a bunch of times.
I have the new TWRP installed (in case that makes any difference).
Click to expand...
Click to collapse
this is only shown in Play? Try dynamic dpi gapps build from banks (check droidbasement link) and see if that sorts it out.
pershoot said:
this is only shown in Play? Try dynamic dpi gapps build from banks (check droidbasement link) and see if that sorts it out.
Click to expand...
Click to collapse
I believe that is the file I'm running. I loaded:
BaNkS-dynamic-gapps-L-5-27-15.zip
Except for that one minor problem during initial startup & configuration (which only occurred on that one screen). You're load has been working great.
THANKS !!!!!
Been running for two days as a dirty flash update from your cm12.0. Simply works except for occasional slowdowns opening apps and with the apps drawer. This is also true on cm12.1 for my d2att do I don't know if it is a trebuchet issue or not. Either way excellent work as ever.
Matthew
Please snap a log the next time it happens. Thanks.
Calendar App trouble connecting to google account
When I tried to open the calendar, it asked me to log in to connect to my calendar.
When I put in the same google account I'd set-up the device with it said that the account already exists on the device.
Checking the account, the Calendar was not visible as a service that was syncing.
The calendar was blank, and trying to add a new event reported that I need to add an account first.
I went to the play store and downloaded the google calendar app. That opened fine and connected to my existing calendar. Returning to the Cyanogen calendar then connected and showed my events.
I'm getting a force close on the new Google Photos app. The app seems to be working fine on my other devices running CM12.1. (pershoot I'll send you a log shortly)
Also, every time I open the Play Store it seems like I have 15-20 apps that need to be updated. It feels like my updates are not sticking through a reboot, and I have to re-update some apps after a boot. Is anyone else seeing similar issues?
Try updating gapps (linked on DB) and update your 12.1 build (06/18).
Hmm, this is odd. The latest banks Gapps (6/17) got rid of the Play Store.
edit: Tried reinstalling the PA Gapps for 5.1, still don't have my Play Store back.
no issues with Play here and no issues with Google Photos as well.
on 6/18 12.1 (DB) and 6/17 Banks.
ariadnejro said:
First one to answer!
At least! CM 12.1 for our beloved TF701!
And yesterday we got TWRP recovery after more than a year thinking that it was impossible.
New life for the best Asus Android Transformer. Thank you, pershoot.
Click to expand...
Click to collapse
Could you send me the link to the TWRP Recovery page please?
mvd96 said:
Could you send me the link to the TWRP Recovery page please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3121989
Bad Dirty Flash of 6/20 & GApps 6-21-15
Hmmm,
Just dirty-flashed your 6/20 and BaNkS-dynamic-gapps-L-6-21-15. Am looking at a mostly blank home screen. The notification pull downs are there, and the 3 navigation buttons on the bottom, and nothing else. And, now a message "Couldn't add widget". I've tried to redownload and flash, but no change.
Suppose next step is either an earlier gapps, or reflash with full reset.
david31262 said:
Hmmm,
Just dirty-flashed your 6/20 and BaNkS-dynamic-gapps-L-6-21-15. Am looking at a mostly blank home screen. The notification pull downs are there, and the 3 navigation buttons on the bottom, and nothing else. And, now a message "Couldn't add widget". I've tried to redownload and flash, but no change.
Suppose next step is either an earlier gapps, or reflash with full reset.
Click to expand...
Click to collapse
no issues with 6/21 12.1 (DB) and 6/21 banks flashing over 6/18 12.1 (DB) and 6/17 Banks. Using CM Recovery to flash.
Got it back with a Full Wipe
pershoot said:
no issues with 6/21 12.1 (DB) and 6/21 banks flashing over 6/18 12.1 (DB) and 6/17 Banks. Using CM Recovery to flash.
Click to expand...
Click to collapse
Thanks for checking
I tried flashing over with these versions, but it didn't come back.
Ended up doing a full wipe and loaded these versions (still running TWRP).
Not sure what happened, but it's working fine now (maybe a TWRP problem).
Thanks.
Better than CM12
I would like to just give an update to how smooth lollipop 511 is running! I'm voice typing this and I did a full wipe from CM 12 then install CM 12.1 and selection of the options to restore from Google all of my apps and after about a half an hour all is just funky great! I have CWM 6. 0. 5. 1 installed. It seems a bit zippier but miracast or screen mirroring still does not function. Great job Pershoot!!!!!
Oh, one thing that it did not do was the stock browser did not sync my bookmarks.
K94U said:
I would like to just give an update to how smooth lollipop 511 is running! I'm voice typing this and I did a full wipe from CM 12 then install CM 12.1 and selection of the options to restore from Google all of my apps and after about a half an hour all is just funky great! I have CWM 6. 0. 5. 1 installed. It seems a bit zippier but miracast or screen mirroring still does not function. Great job Pershoot!!!!!
Oh, one thing that it did not do was the stock browser did not sync my bookmarks.
Click to expand...
Click to collapse
Try this for screen casting:
http://forum.xda-developers.com/nexus-7/general/guide-how-to-enable-chromecast-t2941155
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,
After a clean flash I restored my user apps through Titanium backup v8.0.0.
The Play Store doesn't detect my installed apps: https://framapic.org/2B4BI8G6r2xU/KpoiIpq9ondr.png
I installed a new app from the Play Store and I can see it: https://framapic.org/9Kl35z8Hznx2/DBxvbshb27PB.png
I guess it's a TiBu issue. Do you know how I can fix it?
I already tried to clear app data of Google Play Store and Google framework and remove my Gmail account.
With or without Gapps, it's the same issue.
Thanks.
Google Play Store v7.5.08.M-all [0] [PR] 146162341
Primokorn said:
Hi,
After a clean flash I restored my user apps through Titanium backup v8.0.0.
The Play Store doesn't detect my installed apps: https://framapic.org/2B4BI8G6r2xU/KpoiIpq9ondr.png
I installed a new app from the Play Store and I can see it: https://framapic.org/9Kl35z8Hznx2/DBxvbshb27PB.png
I guess it's a TiBu issue. Do you know how I can fix it?
I already tried to clear app data of Google Play Store and Google framework and remove my Gmail account.
With or without Gapps, it's the same issue.
Thanks.
Google Play Store v7.5.08.M-all [0] [PR] 146162341
Click to expand...
Click to collapse
I had that issue too but i found a way arround i restored all the apps using my google account once all the apps were installed i used tt to restore data+apps again and it worked.
Arrowblue said:
I had that issue too but i found a way arround i restored all the apps using my google account once all the apps were installed i used tt to restore data+apps again and it worked.
Click to expand...
Click to collapse
I don't back up my apps to Google servers. I'll try with the previous version of TiBu.
EDIT: after restorting the previous version of TiBu, I can update my apps again from Google Play.
There's definitively something wrong with v8.0.0.
EDIT2: it was a coincidence. Same issue after a new clean flash with TB 7.6.1. Don't know what I have to do to fix this damned problem!
EDIT3: Solved. I flashed a new ROM with Gapps package and done several tests. I'm back on unofficial RR ROM with microG and everything works... Do not ask me what is the final solution...
Primokorn said:
EDIT3: Solved. I flashed a new ROM with Gapps package and done several tests. I'm back on unofficial RR ROM with microG and everything works... Do not ask me what is the final solution...
Click to expand...
Click to collapse
Strange to see this, as I just clean flashed yesterday and didn't have any issues with TiBu/Market. I'm on 8.0 too. The only thing that I can't see for some reason is the Menu button that should normally be in the upper right next to the paper w/ check on it. I have hardware buttons instead of NavBar (right now), so it is probably linked to that. Trying to get a new feel for the new phone and coming from the Shamu, it's taking me some time.
Something to look at though: take a peep under the Hide tags in my signature and check out the Android_ID link. After a clean flash, the very first thing I do is install Terminal and run that command to restore my AID.
Glad you got it sorted though. I am finding that this device is riddled with all sorts of gremlins.
Woody said:
Strange to see this, as I just clean flashed yesterday and didn't have any issues with TiBu/Market. I'm on 8.0 too. The only thing that I can't see for some reason is the Menu button that should normally be in the upper right next to the paper w/ check on it. I have hardware buttons instead of NavBar (right now), so it is probably linked to that. Trying to get a new feel for the new phone and coming from the Shamu, it's taking me some time.
Something to look at though: take a peep under the Hide tags in my signature and check out the Android_ID link. After a clean flash, the very first thing I do is install Terminal and run that command to restore my AID.
Glad you got it sorted though. I am finding that this device is riddled with all sorts of gremlins.
Click to expand...
Click to collapse
Yes, very strange. During my various tests I flashed OpenGapps pico package and I saw a blank line while setting up my Gmail account. This blank line (probably a bug) is near a storage icon and it was disabled...
A few days ago I also flashed an OpenGapps package (several microG users - and maybe Gapps users - had FCs with the Play Store so I wanted to test with a Gapps package). I don't remember but maybe I disabled the option at this moment.
So during this clean flash I enabled it. idk if it's related to this mess but I think that's the only thing that can explain that my problem is solved (TiBu v8.0.0).
As for your Menu button, I don't see which button you are talking about. I also use the hw buttons and I have never needed a Menu button.
Coming from the Nexus 5 I spent a lot of time reading the 3/3T forums. Filesystems, encryption, OnePlus specifications (WiFi modules, custom ROM/nandroid backups based on OOS firmwares for instance),... and everything is not fully clear lol. I have all my data backed up on Nextcloud so I can test again and again. It seems to be pretty hard to really brick this device. We just have to be careful while flashing files (a confusion between 3 and 3T could be easy, not all threads are unified, or clicking on the wrong link).
I'm used to installing custom ROMs without restoring the Android ID for more than a year. I doubt this could be related to my problem but I'll give it a try so it happens again, thanks.
27 devices gained access to my account during the last month lol
Good luck with your 3T, an awesome device despite all those headaches
Primokorn said:
Yes, very strange. During my various tests I flashed OpenGapps pico package and I saw a blank line while setting up my Gmail account. This blank line (probably a bug) is near a storage icon and it was disabled...
A few days ago I also flashed an OpenGapps package (several microG users - and maybe Gapps users - had FCs with the Play Store so I wanted to test with a Gapps package). I don't remember but maybe I disabled the option at this moment.
So during this clean flash I enabled it. idk if it's related to this mess but I think that's the only thing that can explain that my problem is solved (TiBu v8.0.0).
As for your Menu button, I don't see which button you are talking about. I also use the hw buttons and I have never needed a Menu button.
Coming from the Nexus 5 I spent a lot of time reading the 3/3T forums. Filesystems, encryption, OnePlus specifications (WiFi modules, custom ROM/nandroid backups based on OOS firmwares for instance),... and everything is not fully clear lol. I have all my data backed up on Nextcloud so I can test again and again. It seems to be pretty hard to really brick this device. We just have to be careful while flashing files (a confusion between 3 and 3T could be easy, not all threads are unified, or clicking on the wrong link).
I'm used to installing custom ROMs without restoring the Android ID for more than a year. I doubt this could be related to my problem but I'll give it a try so it happens again, thanks.
27 devices gained access to my account during the last month lol
Good luck with your 3T, an awesome device despite all those headaches
Click to expand...
Click to collapse
indeed A hell of device i chose 3t over S7.Mean while i just flashed cleaned Marshmallow Stock based rom and didnt restored any apps from google account ,Just installed tt and restore apps+data it seems to work for me no broken links to playstore every thing works fine the only thing i noticed is tt backup seems to take more time to restore apps+data that is all.
Arrowblue said:
indeed A hell of device i chose 3t over S7.Mean while i just flashed cleaned Marshmallow Stock based rom and didnt restored any apps from google account ,Just installed tt and restore apps+data it seems to work for me no broken links to playstore every thing works fine the only thing i noticed is tt backup seems to take more time to restore apps+data that is all.
Click to expand...
Click to collapse
Yeah but I don't want to do that for each clean flash
At the end I have this issue each time I clean flash.
Restoring the Android ID doesn't help.
I just wait a moment, clear app data, reboot then the Play Store detects my apps... and I use an addon.d script for dirty flash.
Hi there, i'm quite confused and desperate. I was on Computerfreaks stock rom for a while untill i decided i needed to change the flavor of my device a little bit and installed RR 6.0.
Sadly it came with a lot of bugs, one day it logged me out of my whatsapp account every hour and i had to do all the first-time setup again, so i grew tired of it and installed the flashable stock 6.0 rom zip.
Everything was good, but then when i tried to install whatsapp google play would tell me that it couldn't install, error code 504. It had nothing to do with the avaliable storage obviously so then i did the whole google account removal/ erasing cache, uninstalling, rebooting, etc. Nothing, the mistake keep going. I downloaded the apk directly, and when i tried to install it, it wouldn't pass the setup and just display "app cannot be installed" only gaving me the option to accept it.
This is when i realized it had to be a bigger problem, so i switched roms ro RR 7.1.2, i could install the app.....however it simply crashed at launch, and wouldn't even allow me to complete the initial setup. I've changed the DPI, governors, tried with beta versions and older versions of the app, and nothing. I've tried with AOSP extended, Kang, and the roms mentioned above without success.
It's funny thought, every other app works wonderfully, it just this annoying thing that i actually need to use, that refuses to install.
In twrp i've wiped everything. System, Data, internal storage, dalvik, cache.
I've tried using another google account.
I just don't know what else to do.
Fun fact, i've also tried to see if this was the app's fault and just for the lolz i've installed it on my tablet.....it worked at the first installation like a charm.
BoredDude said:
i decided i needed to change the flavor of my device a little bit and installed RR 6.0.
Sadly it came with a lot of bugs,
one day it logged me out of my whatsapp account every hour and i had to do all the first-time setup again,
so i grew tired of it and installed the flashable stock 6.0 rom zip.
Click to expand...
Click to collapse
I'm sorry you are having issues, but it has nothing to do with the ROMs you have used. How are you restoring data when you flash the new ROMs, if you are restoring data? Are you using Titanium Backup?
My wife and I are on RR 6.x and we both have and use What's App. Nothing is wrong with it. It doesn't log us out "every hour" -- never logs us out.
RR 6.x doesn't have "a lot of bugs" -- in fact it's rock stable and that's why I've stuck with it instead of going to Nougat ROMs. And because of xposed modules, which I am loathe to give up just yet.
Considering LOTS of people use What's App on all the ROMs you mentioned -- including my personal experience with two XT1225 on RR 6.X -- it's not the ROMs at fault in any way.
I know it's not the ROMs fault, I've ruled that out since I've changed 5 times of rom and it keeps failing. Yet I don't know what I should do to solve this problem. I'm not restoring any data, I've done a full clean install everytime, no xposed, even no root sometimes.
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