I was looking at my apps in the Market and under the section where is says which of your devices the app is compatible with I noticed it listed a phone that's not mine. It's an unlocked Samsung phone on T-Mobile. I use Verizon and all Motorola devices. Thinking someone got into my account I changed my password but that device is still on there. Is there any way to disconnect that device from my account and remove it from the listing?
Maybe you are using a Samsung ported rom?
Sent from my toaster.
Well, all of my devices just use the standard rom that comes from Google / Verizon. However I use BlueStacks too. I saw that listed as just "Phone", at least I assume that's what it is. Unless it's my old Droid X. Maybe BlueStacks has something to do with it. It is true that there are no unrecognized purchases on my account.
Edit: Since that's probably the solution. I'll mark this as Resolved.
I saw a new release, Fire OS 5.6.1.0. I didn't update yet. I wonder what this has in store for us, except a more hardened and hard-to-root firmware!
Someone who updated check out the changes and tell us here!
Be careful with this Update, probably has something to do with certified Google devices, the rule says: every device with a firmware build from march 18 and forward should be certified to be able to use Google apps.
So probably this Update wont be able to use Google apps.
---------- Post added at 09:51 AM ---------- Previous post was at 09:50 AM ----------
Be careful with this Update, probably has something to do with certified Google devices, the rule says: every device with a firmware build from march 18 and forward should be certified to be able to use Google apps.
So probably this Update wont be able to use Google apps.
The update isn't available on the U.S. site, but it's up on the Japanese page for the 2017 HD 10. For other Fire tablets, go to the U.S. update page and change the domain name in the URL from .com to .co.jp.
Update: 5.6.1.0 continues to be rootable from scratch (i.e., after an adb sideload). The bootloader files have different hashes, though.
Note: There's no need to adb sideload an update to test whether it's rootable. Just inject su:
-- Extract system.new.dat from the update .bin
-- Convert system.new.dat to system.img using one of the MTK tools
-- Mount system.img in Ubuntu and inject the su binary and other su files
-- Flash the rooted system.img and the 5.6.1.0 boot.img (from the update .bin) in FlashFire
As others have reported, 5.6.1.0 has a build date of 03/22/2018. W.r.t. certification, I read somewhere that devices with already signed-in Google users might be grandfathered? In any case, the lack of clarity regarding certification is one more reason to be armed with a 5.6.0.1 FlashFire backup.
donalberto17 said:
Be careful with this Update, probably has something to do with certified Google devices, the rule says: every device with a firmware build from march 18 and forward should be certified to be able to use Google apps.
So probably this Update wont be able to use Google apps.
---------- Post added at 09:51 AM ---------- Previous post was at 09:50 AM ----------
Be careful with this Update, probably has something to do with certified Google devices, the rule says: every device with a firmware build from march 18 and forward should be certified to be able to use Google apps.
So probably this Update wont be able to use Google apps.
Click to expand...
Click to collapse
Build date appears to be 22nd March, so likely no Google Play Services functionality will be available from this point..
For those who don't want the update yet, make sure you use something like NoRoot Firewall to block OTA updates. Fire devices have a tendency to update at odd hours without user consent, Windows 10-style.
I'll see what happens when my mom's HD 8 updates.
Anyway, I have blocked the updates on router. If someone update an HD 8, please try Kingo Root or Offline Rooting by retyre.
lakitu47 said:
For those who don't want the update yet, make sure you use something like NoRoot Firewall to block OTA updates. Fire devices have a tendency to update at odd hours without user consent, Windows 10-style.
I'll see what happens when my mom's HD 8 updates, since she doesn't care about rooting/mods/tweaks/etc.
Click to expand...
Click to collapse
Can you point which processes must be blocked? I have four, but it still managed to update to 5.6.0.1 recently.
xvitehx said:
Can you point which processes must be blocked? I have four, but it still managed to update to 5.6.0.1 recently.
Click to expand...
Click to collapse
Happened to me too, even after blocking ALL Amazon apps. That, I think just works for someone, and doesn't for someone. That's why I moved to blocking them in router.
Wow, this looks like a major update! After a long time they moved 50.5.X.X to 50.6.X.X. That makes me think, it is almost sure that this is not downgrade-able.
EDIT: They also moved to 5.3.6.2 from 5.3.6.1.
Supersonic27543 said:
Happened to me too, even after blocking ALL Amazon apps. That, I think just works for someone, and doesn't for someone. That's why I moved to blocking them in router.
Click to expand...
Click to collapse
I blocked all Amazon apps, turned on the "start on boot" feature, and my device hasn't checked for updates since 3/26.
Anyone with the update notice any major differences? Is there any reason to update if I am satisfied with my current rooted set up?
Someone with gapps (no root) updated to this version?
Are gapps still working?
The new gapps build date control is triggered only when accessing for the first time with Google account or even with a device already set up?
Fire HD8 7th gen - got auto updated to 5.6.1.0 today in India. Dont see any difference, all Google apps are working just fine. Not rooted, obviously
Change log.. good stuff
5.6.1.0 No loss of Google functionality
Just got pushed to 5.6.1.0, Fire 8 (2017) and Alexa is now available hands-free, which is the first thing the tablet notified me of after the update. I'm not rooted and I lost absolutely no Google functionality.
I updated Fire to 5.6.1.0 from Japanese Fire user.
Hello! I am a Japanese Fire user.
I updated my Fire to 5.6.1.0.
After that, I used Google, the Google Play Store, etc., but there is no problem.
However, I think that it is better to stop updating by looking at this reply.
I used Google translation, so I think that it is wrong sentence.
As per post#3..... does this mean that the FireHD 8 is now rootable if updated to 5.6.1.0 or just the HD 10's?
fire1951 said:
As per post#3..... does this mean that the FireHD 8 is now rootable if updated to 5.6.1.0 or just the HD 10's?
Click to expand...
Click to collapse
Nope, I think just the HD 10s. Nobody tested though, it may work really.
Just got the 5.6.1.0 update on my Fire HD 8 this morning in the US. All my google apps are working correctly, no issues at all.
Google Play seems to work
donalberto17 said:
Be careful with this Update, probably has something to do with certified Google devices, the rule says: every device with a firmware build from march 18 and forward should be certified to be able to use Google apps.
So probably this Update wont be able to use Google apps.
---------- Post added at 09:51 AM ---------- Previous post was at 09:50 AM ----------
Be careful with this Update, probably has something to do with certified Google devices, the rule says: every device with a firmware build from march 18 and forward should be certified to be able to use Google apps.
So probably this Update wont be able to use Google apps.
Click to expand...
Click to collapse
Just updated to Fire OS 5.6.1.0, it actually auto-updated while I wasn't looking. I have google apps side-loaded, no root. Google Play seems to work, apps are updating. YouTube plays videos, and Maps, Movies & TV and Chrome work too. Haven't tried anything else yet.
Fire HD 8 btw
If any of you have read the recent headlines on XDA about how to enable RCS on the Google messages app, I recently did that as I'm on Cricket Wireless, (Unlocked Moto Z3 Play 64gb) which originally didn't support the chat features or RCS in the messages app, however after I followed the steps, it worked like a charm, however to my (pleasant) surprise, I looked in the Google dialer apps Settings today, and found the "Call Screening" option was now available... I thought it might be just a side effect of enabling RCS, so I had a few ppl call me, and to my surprise, Call Screening now FULLY works!
pretty cool
I don't see that option on mine ..
@bdizzle1686 please tell us how did you enable this feature ? Give us steps.
ajaikumarnadar said:
@bdizzle1686 please tell us how did you enable this feature ? Give us steps.
Click to expand...
Click to collapse
Actually, I didn't do any steps.. installed normal Google dialer from play store (beta version) , and it just works. Appeared in setting of phone app, chose voice, watched demo, and it works on every incoming call. Works on my new Moto G7 as well..
(Dropped and shattered the screen on my Z3 play for the THIRD TIME in 6 months)
The only thing that I've done that may have contributed to this working, is I've installed a few Google Pixel related apk's, (modded Pixel launcher, Pixel launcher Icons, all Pixel wallpaper ports, Pixel camera, Pixel Visual Core, Device Configuration - android.autoinstalls.config.google.nexus) etc.
As I stated before, this has now worked fully for me on both my Unlocked Moto Z³ Play, and my Unlocked Moto G7, both NOT rooted, NO magisk, NO unlocked bootloader, On cricket wireless as my carrier.. I'm thinking the Device Configuration apk (android.autoinstalls.config.google.nexus) is what may have helped in activating this on the Google Dialer BETA version..
Thanks.. ?
But this config APK didn't help in this pixel call screening...
Maybe it's somewhat restricted to US.
ajaikumarnadar said:
Thanks.. ?
But this config APK didn't help in this pixel call screening...
Maybe it's somewhat restricted to US.
Click to expand...
Click to collapse
Yeah, that's definitely possible, as I live just about a half an hour drive north of Detroit, Michigan...
As you can see, like I originally said, I don't really think I did any specific steps to enable this, Google just started rolling the feature out to certain specific non-pixel devices...
Call screening just suddenly appeared and started working one day, on both my Z³ Play, and my G⁷...
What are the safest ways to backup my Maxx and then unlock, and if possible, root it? As in the title, I have an (old!):
droid maxx
Motorola X8
Android 4.4
Kernel 3.4.42-ge1d6506-0006-g9ddacc8... (Wed Apr 30 2014)
Build "
Build SU2-3.3
Unfortunately, it is (most likely) not a developer version, just a plain old Verizon customer version (bought I think in 2014).
It only took a system update once a long time ago when my SO accidentally updated it (many years ago). Since then, it keeps annoying me for system updates now, but I keep rejecting them and disabled the play store ( Google Play Store vers 10.8.33-all [0] [PR] 205773289) and as many things as I could, hoping I can root this sucker at some point. I just install apks directly whenever I need something.
If it is not unlockable/unrootable, are there any other options for playing with it through adb on the computer, etc...? Are there any options for permanently disabling the pesky update notifications so I never accidentally hit them, or even better, getting rid of whatever the update was? I'm a long time lurker on this forum but always got too busy to play with it before. I am currently using it as my primary phone as I'm trying to save money by not buying a new one. I love the battery life on this thing, even with regular use for 5 or 6 years.
Thank you all so much.
1: Back up ALL data.
2: Install Sunshine from theroot.ninja.
3: Enjoy twrp.
Sunshine requires you to pay $25 USD dollars.
Hey everyone, haven't been on the forums for a long time, anyway i bought a Fire 10 2019 and i went through the process of installing google play store on the device. The Play Store icon shows up, but when i press login nothing happens. I have used the Toolbox V12.0 to try it. The google icon won't open at all but the play store will open, and like i said, it will not let me login. I remember reading a review on amazon.ca and the person who wrote it said the Canadian version of the tablet was like wearing handcuffs compared to the American version. When i ran the toolbox the first few apk's failed. Any suggestions?
You can use a VPN app.
Another Candian here. I've got an HD 10 and the Play Store works without a problem.
The biggest issue with the Canadian Fire vs American is that various built-in services do not function, such as Alexa. (You can use it to control other Alexa-enabled devices, but the assistant portion does not work while it works fine in the US) I ended up installing Google Assistant to fill the role you'd think Alexa would take on an Amazon product.
PonyFlare said:
Another Candian here. I've got an HD 10 and the Play Store works without a problem.
The biggest issue with the Canadian Fire vs American is that various built-in services do not function, such as Alexa. (You can use it to control other Alexa-enabled devices, but the assistant portion does not work while it works fine in the US) I ended up installing Google Assistant to fill the role you'd think Alexa would take on an Amazon product.
Click to expand...
Click to collapse
Sorry i took so long to reply. I did end up getting it to work. Is the Canadian version really as bad compared to the American version as the person who left the review says it is?