Related
Hey Guys,
I have an original (2013) Moto X 1060 (Verizon) that I rooted using this method. http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602 It's been working great with no problems until today when my phone decided to update my google wallet app to the new android pay. Whenever I try to add a card to android pay I'm getting the error "Android Pay Cannot be used...... Google is unable to verify that your device or the software running on it is android compatible."
Googling has led me t believe that this is an error related to the app detecting root. I tried both of these methods, but neither has worked. http://bit.ly/1LnwzAZ http://bit.ly/1LnwEog . I've tried each separately with rebooting in between as well as trying them together all to no avail.
Other than following the guide above the only root-related things I have modified on the phone are the removal of some verizon apps via titanium backup and adding the following xposed module: "NoSafeVolumeWarning".
One thing that I noted was when I uncheck "Enable Superuser" inside of SuperSu 2.46 it displays a message saying "Uninstall Failed !" It still displays the "Superuser is disabled and hidden" underneath the box and if i enable it again and disable it it does not pop up with the uninstall failed message. Does this have something to do with write protection?
Any help would be greatly appreciated!
Thanks,
Adam
johnnyboy239 said:
Hey Guys,
I have an original (2013) Moto X 1060 (Verizon) that I rooted using this method. http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602 It's been working great with no problems until today when my phone decided to update my google wallet app to the new android pay. Whenever I try to add a card to android pay I'm getting the error "Android Pay Cannot be used...... Google is unable to verify that your device or the software running on it is android compatible."
Click to expand...
Click to collapse
Having the exact same issue. Just upgraded to 5.1 today, xposed Rootcloak as well as No Device Check installed. Also tried Disable SU. Still get the same issue.
Same. I tried uninstalling SU, Hide My Root, and Rootcloak...nothing has worked. Found out today that the app updated when I went to buy something at Walgreen's. How ****ing embarrassing is that?
So I have not yet found a solution to this and am still hoping someone has one. In the mean time, you can install this app http://www.apk4fun.com/share/7185/ (doesn't need to be from this site, it's just an old version of google wallet, and the one I used), go into settings>apps>google play services>manage data clear all data, and reboot. I just tried it at cub foods and it worked fine, but of course you do have to go into the app first, and I had to disconnect it from the app store with titanium backup so it wouldn't update to android pay again.
Was able to get Amex card working after uninstalling Xposed. However, I think I'm going to pass on Android Pay until they allow pin codes on the app, not the phone.
Same problem, few apps frozen with TiBu and xposed installed. Any other work around? s
johnnyboy239 said:
So I have not yet found a solution to this and am still hoping someone has one. In the mean time, you can install this app http://www.apk4fun.com/share/7185/ (doesn't need to be from this site, it's just an old version of google wallet, and the one I used), go into settings>apps>google play services>manage data clear all data, and reboot. I just tried it at cub foods and it worked fine, but of course you do have to go into the app first, and I had to disconnect it from the app store with titanium backup so it wouldn't update to android pay again.
Click to expand...
Click to collapse
check to see if your phone allows pin codes to be deactivated at times. I have mine set to not be used at home work and if I am carrying the phone. It is quite useful feature in settings Lockscreen but I am on COS 12.1 OnePlus basically CM
I haven't tried it yet, but I think they only way we'll get this working on root is to install it on stock unrooted, back it up with TiB or Helium, root and then reinstall/restore.
Lots of fail here as well. All the tricks you all listed + some others. It seems there is a lack of consistency for those that resolved. Some just say disabling root, uninstall busybox, uninstall xposed, rootcloak, device checker for play services, etc.
Nothing yet has worked for me. Luckily I backed up Wallet just before taking the update, so I may go back until the community has a solution.
Ezekial said:
Lots of fail here as well. All the tricks you all listed + some others. It seems there is a lack of consistency for those that resolved. Some just say disabling root, uninstall busybox, uninstall xposed, rootcloak, device checker for play services, etc.
Nothing yet has worked for me. Luckily I backed up Wallet just before taking the update, so I may go back until the community has a solution.
Click to expand...
Click to collapse
I'm in the same boat. Couldn't get AP to work. Just loaded up the previous version of Wallet. Now have two wallet apps, but whatever. Both appear to be working.
Has anyone tried to get Android Pay working by re-locking the bootloader and temp unrooting on a Nexus device (say, a tablet), then getting AP up and running, and then checking to see if it was usable on your other device(s)??....I was curious if Android Pay would work on ALL of your devices once it was set up properly. Working with lock, unlocking, rooting, etc. is much easier on a Nexus than it would be to work on a Moto, or similar.
Does this make any sense?
KenNashua said:
Was able to get Amex card working after uninstalling Xposed. However, I think I'm going to pass on Android Pay until they allow pin codes on the app, not the phone.
Click to expand...
Click to collapse
Tried AP for the first time at Panera today and failed...seems even with Root Cloak on AP and Google Play Service as well as No Device Check, it still fails.
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
same thing happened to me just now.
not sure what to do, not sure if i have to reinstall everything again
fmkilo said:
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
Click to expand...
Click to collapse
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
JokersWild0075 said:
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
Click to expand...
Click to collapse
Listen up folks. Do not and i repeat do not update any of samsungs apks. Until we can find out whats going on. It seems that samsung is now pushing updates thru their apks to check and get rid of SU. They are getting sneaky. So for now do not update any samsungs apk, not even thru google. Also do not update SU, this is another way to lose root. We are working on it. Please do not ask if we found anything, if a fix is found we will post our findings.
If you need shealth, iris scanner, samsung pay, android pay, or any other samsung apk, then you need to stay on stock firmware and not use root.
Also if anyone is having issue with files or odin not flashing, make sure you are not on the new PI4 stock ROM, if you are then odin will fail everytime and at this moment there is no way to root or down grade to the older firmware.
Otherwise Try to redownload all files as it seem that afh is/was having alot of issues with uploads and downloads. This not something that we can fix as we dont host or own that site.
Can you guys break down the steps to regain root without reinstalling the OS? Mine also lost root on v2.
It looks like my S-Health was automatically updated to the latest version, which has been reported to be a root of the cause.
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
elite-fusion said:
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
Click to expand...
Click to collapse
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
galaxyuser88 said:
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
Click to expand...
Click to collapse
I am currently logged into the Samsung account and have been for about 2 days now with no ill affects so far, downloaded a couple themes is all...that is with all the Sammy stuff froze and functional root.
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
I need advice with GPay to be working after Bootloader unlock.
I have new MI9, like long user of Mi series (last Mi Note2) I unlocked Bootloader, uploaded TWRP (the only one that worked was TWRP 3.3.0-0423 for Mi9 by wzsx150 - big fight with TWRP ...) and uploaded MIUI xiaomi.eu_multi_MI9_9.5.1_v10-9.zip.
Everything works fine for me, only Google Pay is a problem. Anytime I try to add an card in app, I got message that phone is either rooted or modified and cant proceed due to safety reasons.
I checked all forums and nothing works or I do something wrong. I tried this:
1) delete in DATA / DATA / com.google.android.gms - the folder will appear again after successful deletion
2) Magisk manager install - App is working correctly, GPay has been added to Magisk Hide and all Google Play Services folders, but still GPay not working
3) follow guide on https://forum.xda-developers.com/Mi-9/how-to/xiaomi-mi-9-firmware-twrp-recovery-root-t3922158 and install PrebuiltGmsCore.apk and then Google pay Patchfix. I stopped , because PrebuiltGmsCore.apk cant be installed
I do test with SafetyNet Test and it does not detect any problems.
I tried several times to delete Google Pay data as described on some forum. This does not help also.
Does anyone know how to get out of it? I don't want to go back to stock ROM and lock the bootloader ...
Thanks for any advice
Did you 'clear data' for all the Google Play/Pay/Framework services apps after you installed and configured the Magisk GPay module & MagiskHide settings and rebooted ?
Yes, I try many combinations. Like install GPay and Magisk then, reverse, delete data of GPay and install Magisk etc..
Odesláno z mého Mi Note 2 pomocí Tapatalk
I have the same problem. Please someone help!
Install Magisk and add Google Pay and/or Google Services in Magisk Hide list??
All done
Odesláno z mého Mi Note 2 pomocí Tapatalk
Hi
Any update for this issue ?
I've also tried to solve this problem in every conceivable way, failing miserably at it. It seems that you may or may not get GPay to work after deleting the gms folder, but the problem always reoccur after a while. It seems impossible to get GPay to work permanently with an unlocked bootloader on the Mi 9. Sad but true.
MrDeacon said:
I've also tried to solve this problem in every conceivable way, failing miserably at it. It seems that you may or may not get GPay to work after deleting the gms folder, but the problem always reoccur after a while. It seems impossible to get GPay to work permanently with an unlocked bootloader on the Mi 9. Sad but true.
Click to expand...
Click to collapse
I set up google pay on my girlfriends phone 2 weeks ago and it's still working fine. You must be doing something very wrong.
i opened my bootloader and cant get google pay to work. I am using the PFAEUXM stock rom
Just for the fun of it, I took the steps that Xiaomi demands in order to await bootloader unlock. There is no lack of warnings to make you understand that there may be a risk that sensible things like GPay will stop working.
I didn’t unlock.
I apologize if this is a noob question. I haven't rooted since Pixel 2, so it has been close to 6 years and I am not very aware anymore about Magisk. I can probably find videos regarding how to install Magisk and root, but my question was with its use of LSposed and Pixelfy Google photos.
The Pixel 5 and older have free photo storage, and I assume this module spoofs the type of phone and makes it think it is a Pixel and gives free photo storage.
I have a phone I am not using but it is not rooted yet and something I am considering.
I have been also checking various threads and there is mixed feedback on this particular module.
Does anyone use the Pixelfy free photo storage ? It looks like it needs to be used with Magisk and LSposed to get it to work ? Some threads it looks like it works, others have been commenting that it is bricking and causing problems. If it is unreliable or bricking, then I'll just see if I can buy and older pixel but thought I'd ask here first. Thanks.
mikeprius said:
I apologize if this is a noob question. I haven't rooted since Pixel 2, so it has been close to 6 years and I am not very aware anymore about Magisk. I can probably find videos regarding how to install Magisk and root, but my question was with its use of LSposed and Pixelfy Google photos.
The Pixel 5 and older have free photo storage, and I assume this module spoofs the type of phone and makes it think it is a Pixel and gives free photo storage.
I have a phone I am not using but it is not rooted yet and something I am considering.
I have been also checking various threads and there is mixed feedback on this particular module.
Does anyone use the Pixelfy free photo storage ? It looks like it needs to be used with Magisk and LSposed to get it to work ? Some threads it looks like it works, others have been commenting that it is bricking and causing problems. If it is unreliable or bricking, then I'll just see if I can buy and older pixel but thought I'd ask here first. Thanks.
Click to expand...
Click to collapse
If you mean this LSPosed module, then yes, I use it on 3 of my devices and it works perfectly.
And yes, it requires to be rooted with Magisk and to have LSPosed framework installed.
Lord Sithek said:
If you mean this LSPosed module, then yes, I use it on 3 of my devices and it works perfectly.
And yes, it requires to be rooted with Magisk and to have LSPosed framework installed.
Click to expand...
Click to collapse
Hi yes I believe this is it. So in order to have unlimited Google photo uploads, I need to first root, have magisk, download lsposed, then download this module separately?
I have a pixel 6a. Has there been any issues with Google halting or finding out about the spoof and blocking it?
mikeprius said:
Hi yes I believe this is it. So in order to have unlimited Google photo uploads, I need to first root, have magisk, download lsposed, then download this module separately?
I have a pixel 6a. Has there been any issues with Google halting or finding out about the spoof and blocking it?
Click to expand...
Click to collapse
Yes...there is actually two methods Pixelify goes about this; they either spoof the Pixel 5 (which is the latest Pixel Google will allow unlimited uploads but at "Storage Saver" lowered quality on the photos and videos) or the original Pixel(1) [which is the original and only Google Pixel left that Google allows unlimited uploads in original quality]. So you would need to decide which method you are willing to try and do...
But yes, you'd have to unlock the bootloader (which wipes the device), root with Magisk, install the LSPosed Magisk module, then run that Unlimited Google Photo app (or Baltiapps Pixelify GPhotos as it's officially named) which will then install the LSPosed module "separately".
I've already spoken a bit on this, so I will just quote what I said before (things to consider and risks involved) as well as you can click on the quote to go to the post/thread and see how the discussion developed there;
simplepinoi177 said:
I wouldn't make this claim with such certainty. Spoofing a Pixel phone is definitely against Google's Terms and Conditions. Doing this for years may have worked out since Google was offering it from Pixel 2-5 in Storage Saver capacity, but it's been 2 years since the Pixel 5 was released, and as time goes on, it's less realistic that Pixel's before 6 would still be in use, yet there would be all these accounts still backing up using the unlimited storage feature. ESPECIALLY if (like me, to be guilty of) there are many who are spoofing the Pixel 1 to get it unlimited WITH original quality -- being the first Pixel is 7 years old; highly unrealistic that so many people should still be using the phone to be taking photos and videos off of.
My point is that, no one using this "trick" should completely rely on it and expect Google to "play along" indefinitely about it. Like I've been saying, at best, Google will just plug in the loophole and close the feature down; at worst, they remove any photo or video that were taken under a particular Pixel model when your google account shows it being connected to another device altogether and/or they suspend a google account outright using the exploit -- this is highly unlikely, but is still in the realm of possibility and is as I said worst case.
I, myself, back my photos and videos from my Pixel 7 Pro using this spoofing trick, but I will also back all my media up (when my device is full) on a physical medium just in case.
Click to expand...
Click to collapse
P.S. Also, since you are out of practice in rooting, there is an excellent tool that streamlines most anything to do outside of stock experience on the Pixels (bootloader unlocking, rooting, flashing and/or updating Full Factory images or OTAs [to either both or inactive slots], flashing custom ROMs, other recovery checks and protocols, advanced apk install or apk/app disabling [system, stock], it might even be able to flash custom kernels but I can't be too sure) which would be able to accomplish what your aims are pretty much with a single click (outside of clicking where your factory images are and what not)....
simplepinoi177 said:
Yes...there is actually two methods Pixelify goes about this; they either spoof the Pixel 5 (which is the latest Pixel Google will allow unlimited uploads but at "Storage Saver" lowered quality on the photos and videos) or the original Pixel(1) [which is the original and only Google Pixel left that Google allows unlimited uploads in original quality]. So you would need to decide which method you are willing to try and do...
But yes, you'd have to unlock the bootloader (which wipes the device), root with Magisk, install the LSPosed Magisk module, then run that Unlimited Google Photo app (or Baltiapps Pixelify GPhotos as it's officially named) which will then install the LSPosed module "separately".
I've already spoken a bit on this, so I will just quote what I said before (things to consider and risks involved) as well as you can click on the quote to go to the post/thread and see how the discussion developed there;
P.S. Also, since you are out of practice in rooting, there is an excellent tool that streamlines most anything to do outside of stock experience on the Pixels (bootloader unlocking, rooting, flashing and/or updating Full Factory images or OTAs [to either both or inactive slots], flashing custom ROMs, other recovery checks and protocols, advanced apk install or apk/app disabling [system, stock], it might even be able to flash custom kernels but I can't be too sure) which would be able to accomplish what your aims are pretty much with a single click (outside of clicking where your factory images are and what not)....
Click to expand...
Click to collapse
Thank you for the information. So before the way I used to root was I would use adb then type fastboot img then the TWRP file.
Then reboot and now I have custom recovery TWRP. This is of course after I have unlocked the bootloader which wiped.
I assume this is still the case where oem unlock is checked in developer options then sdb fastboot flashing unlock?
I briefly used magisk by topjohnwu but it was new back then and I sort of didn't keep up with it.
If there is a program or different method is it possible to point me to it? I honestly can remember what to do after booting TWRP.
Regarding the spoofing, the standard upload of the pixel 5 is fine for me and you mentioned some good points regarding Google potentially catching on. At the time banking apps didn't care if you were rooted but I think they do not work anymore if you are.
Also I thought I read somewhere, lets say I just flash a custom rom instead and don't use the pixel OS, will this be automatically for this module without having to do anything extra? It reminds me of when all custom roms had free Hotspot tethering built in so you didn't need to do anything extra.
I also don't mind flashing a custom rom and using it as a dedicated backup device either. Just exploring options
Thanks for the starter info. I just realized how long it has been and I don't recognize anything anymore.
mikeprius said:
Thank you for the information. So before the way I used to root was I would use adb then type fastboot img then the TWRP file.
Then reboot and now I have custom recovery TWRP. This is of course after I have unlocked the bootloader which wiped.
I assume this is still the case where oem unlock is checked in developer options then sdb fastboot flashing unlock?
I briefly used magisk by topjohnwu but it was new back then and I sort of didn't keep up with it.
If there is a program or different method is it possible to point me to it? I honestly can remember what to do after booting TWRP.
Regarding the spoofing, the standard upload of the pixel 5 is fine for me and you mentioned some good points regarding Google potentially catching on. At the time banking apps didn't care if you were rooted but I think they do not work anymore if you are.
Also I thought I read somewhere, lets say I just flash a custom rom instead and don't use the pixel OS, will this be automatically for this module without having to do anything extra? It reminds me of when all custom roms had free Hotspot tethering built in so you didn't need to do anything extra.
I also don't mind flashing a custom rom and using it as a dedicated backup device either. Just exploring options
Thanks for the starter info. I just realized how long it has been and I don't recognize anything anymore.
Click to expand...
Click to collapse
I also had a Pixel 2 XL (taimen) for 3 years -- upgraded to the Pixel 5 -- so I am familiar with the method you are familiar with.
Unfortunately, that is no longer how it works. It sucks, but TWRP could never catch up after Android 10 -- it would take so long for them to develop that once they finally got TWRP to work with Android 10, Android 11 was released and became the new established version; then once they finally got it compatible with Android 11, Android 12 released and the same thing. So, as I understand it, TWRP does work in a limited capacity for Android 12, but it will not work for Android 13 (yet); and it seems if history repeats itself, it might not get there by the time Android 14 releases...
So still using magisk, but you can't "install" magisk from a .zip like you could with TWRP.
It's not that much more complicated than flashing Full Factory images or temp booting from a recovery image -- you simply extract the init_boot.img from the Full Factory image, "run it through" the Magisk app and get it patched that way, then flash the patched image the same way you flash the recovery partition (from the TWRP image) to permanently install/flash the custom recovery.
But, if you are still wary about going about all of this and/or if you are out of practice and unsure, please consider badabing2003's PixelFlasher. It basically does all of that stuff, but puts a GUI and automates it all for you -- as well as doing certain checks and protocols to make sure things aren't done wrong or buggy/incompatibly. It's as close to "one-click" as anyone's gonna get for the Pixels...
PixelFlasher will guide you to downloading the Full Factory image (or OTA if you wish that way), Magisk, the right platform-tools version (the least buggy version), i believe it can unlock the bootloader (but I could be wrong), and root or Full Factory update for you.
Hope this helps!
Lord Sithek said:
If you mean this LSPosed module, then yes, I use it on 3 of my devices and it works perfectly.
And yes, it requires to be rooted with Magisk and to have LSPosed framework installed.
Click to expand...
Click to collapse
Please, after installing how can be used?
Thanks!
amplatfus said:
Please, after installing how can be used?
Thanks!
Click to expand...
Click to collapse
after installing the module, the module actually installs an app (which can be found in the app drawer) under "Pixelify GPhotos". Running the app should give you all the settings and options you need to get it to work/"be used" -- it even has a button to force-close Google Photos to reset it to detect the spoofing. Just be sure you have all modules enabled (LSPosed[within Magisk], Pixelify GPhotos[within LSPosed]).
I've assisted a bunch of users/members where they had to play around with the configurations a bunch to finally get it to work for them; for whatever reason, one configuration works for one user but not the other -- my configuration did not work for some of them and they had to enable certain settings to get it to work for them (even though we are using the same device).
simplepinoi177 said:
after installing the module, the module actually installs an app (which can be found in the app drawer) under "Pixelify GPhotos". Running the app should give you all the settings and options you need to get it to work/"be used" -- it even has a button to force-close Google Photos to reset it to detect the spoofing. Just be sure you have all modules enabled (LSPosed[within Magisk], Pixelify GPhotos[within LSPosed]).
I've assisted a bunch of users/members where they had to play around with the configurations a bunch to finally get it to work for them; for whatever reason, one configuration works for one user but not the other -- my configuration did not work for some of them and they had to enable certain settings to get it to work for them (even though we are using the same device).
Click to expand...
Click to collapse
Hi thank you for all your help. I currently have the pixel 6a now and will get the 7a but probably keep the 6a as a dev device. Once I unlock the bootloader, I will try the pixel flasher and go from there. Good to know about TWRP but if there is a newer and better way I am all about experimenting with that as well. I may give it a run over the summer.
Once I download pixel flasher and install magisk, so I go to gitgub and download lsposed then install pixelfy as a module separately?
Unlock bootloader -> pixel flasher->magisk->Lsposed-> Pixelfy?
Thanks and salamat po
mikeprius said:
Hi thank you for all your help. I currently have the pixel 6a now and will get the 7a but probably keep the 6a as a dev device. Once I unlock the bootloader, I will try the pixel flasher and go from there. Good to know about TWRP but if there is a newer and better way I am all about experimenting with that as well. I may give it a run over the summer.
Once I download pixel flasher and install magisk, so I go to gitgub and download lsposed then install pixelfy as a module separately?
Unlock bootloader -> pixel flasher->magisk->Lsposed-> Pixelfy?
Thanks and salamat po
Click to expand...
Click to collapse
Once [you] download pixel flasher and install magisk,...go to [github] and download LSPosed (zygisk version), then install Pixelify GPhotos (Baltiapps version, not original kingsman44) LSPosed module as a module separately (in LSPosed).
It will then install a companion app which you can set the settings and options....
But yes, "Unlock bootloader -> pixel flasher->magisk->Lsposed-> Pixelfy?" looks right; just keep in mind that unlocking bootloader wipes device, and use Pixelify Baltiapps and not kingsman44's.
Glad to help!