The latest update issued from Samsung for the T Mobile variant of the note 9 has slipped in an Android “Coronavirus Tracker” without Consent.
I just found this in my phone! See attachment.
Anyone with a tutorial for downgrading the OS?
It only works is you have a covid 19 app on your phone. No reason to downgrade
Sent from my SM-G988U using Tapatalk
This is not a tracker. It is only the framework for Google services to work with an app provided by governed agencies. If you do not opt in to the contact tracing , the files that are on your phone do nothing.
Sent from my SM-N960U using Tapatalk
Thanks for clarifying guys. I still want to be able to go back to an earlier firmware to this recent release. Is there a way to successfully accomplish this without root? I am attempting the ODIN method, but constantly being met with "FAILED". Any insight would be greatly appreciated. Thanks in advance.
michel5891 said:
Thanks for clarifying guys. I still want to be able to go back to an earlier firmware to this recent release. Is there a way to successfully accomplish this without root? I am attempting the ODIN method, but constantly being met with "FAILED". Any insight would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
Seems like that Samsung may have disabled the ability to revert back to Pie with their latest OS update.
You can only downgrade to an earlier firmware if it is the same bootloader version. For example, if you are on Android 10 with the June security patch (probably bootloader 3) you would be able to downgrade to the May firmware. I'm not sure if you can go back to March or April unless it's the same bootloader version.
Sent from my SM-N975U using Tapatalk
iceepyon said:
Seems like that Samsung may have disabled the ability to revert back to Pie with their latest OS update.
Click to expand...
Click to collapse
Yes, it does seem that way. However, I did a complete reset after backing up, did a search for the covid19 thing and it doesn't show up. So, I guess all is well for now.
Being unable to downgrade to previous OS releases is quite curious.
Look at the firmware version... For instance, my baseband version is N975FXXS4CTD1. The 5th number from the right is the bootloader version, in my case 4. If the bootloader version you are trying to flash is LOWER than the one you have it WON'T allow you to flash the firmware, you will get an error and fail. Higher number is a later bootloader and will flash but no love to get back to the older firmware...
Hope this helps a little...
I got rid of the Covid-19 thing from my Note 9 by uninstalling updates to Google Play Services. I can't remember the exact process, as this well several weeks ago, but it shouldn't be hard to find.
Also, proceed with caution. Removing Play Services updates may cause various Google apps to dysfunction.
I didn't even realize this was installed onto the phones.
Thank you for the heads-up.
I believe it is regional as I haven't encountered this on my Australian Note 9 or Note 10+ both running OneUI2.1...
michel5891 said:
The latest update issued from Samsung for the T Mobile variant of the note 9 has slipped in an Android “Coronavirus Tracker” without Consent.
I just found this in my phone! See attachment.
Anyone with a tutorial for downgrading the OS?
Click to expand...
Click to collapse
This worked for me!
Easy STEPS to TURN OFF COVID-19 Exposure Notifications on Android
Wise2TheLies said:
I got rid of the Covid-19 thing from my Note 9 by uninstalling updates to Google Play Services. I can't remember the exact process, as this well several weeks ago, but it shouldn't be hard to find.
Also, proceed with caution. Removing Play Services updates may cause various Google apps to dysfunction.
Click to expand...
Click to collapse
Correct. The only way to get rid of it is to delete Google Play Services. That's how they snuck it in. On Android Pie it's simple. Just debloat via ADB using pm list packages prompt and voila! it's gone. On Android 10 it works the same EXCEPT none of the google apps, firefox, instacart, or anything like that will WORK. So you can de-google all you want - they've baked it into everything. It's something I'm struggling with now since I was forced to upgrade.
Articul8Madness said:
Correct. The only way to get rid of it is to delete Google Play Services. That's how they snuck it in. On Android Pie it's simple. Just debloat via ADB using pm list packages prompt and voila! it's gone. On Android 10 it works the same EXCEPT none of the google apps, firefox, instacart, or anything like that will WORK. So you can de-google all you want - they've baked it into everything. It's something I'm struggling with now since I was forced to upgrade.
Click to expand...
Click to collapse
You don't need to delete the Google Play Services.
The actually Service is called "exposurenotification", and there are a couple of this service entries inside the Google Play Services App.
The last Version I could find was around Jun/Jul 2020, which had none of these entries.
I was able to "kick" the services with a Service Disabler APP, but the modified Settings Entry remained.
Perhaps it could be worth to dig deeper into this, but it is a bit over the level of my understanding.
Spoiler: com.google.android.gms.nearby.exposurenotification
XML:
<permission android:name="com.google.android.gms.nearby.exposurenotification.EXPOSURE_CALLBACK" android:protectionLevel="signature" />
<uses-permission android:name="com.google.android.gms.nearby.exposurenotification.EXPOSURE_CALLBACK" />
<activity android:enabled="true" android:excludeFromRecents="true" android:exported="false" android:name="com.google.android.gms.nearby.exposurenotification.settings.SettingsCheckerActivity" android:process="com.google.android.gms.ui" android:taskAffinity="" android:theme="@style/ExposureNotificationDialogStyle" chimera:autoEnabled="true">
<intent-filter>
<action android:name="com.google.android.gms.nearby.exposurenotification.settings.CHECK_SETTINGS" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
<service android:enabled="@bool/platformIsAtLeastL" android:exported="false" android:name="com.google.android.gms.nearby.exposurenotification.service.ExposureNotificationInternalService" android:process="@string/common_persistent_process" chimera:autoEnabled="@bool/platformIsAtLeastL" />
<service android:exported="true" android:name="com.google.android.gms.nearby.exposurenotification.WakeUpService" android:permission="com.google.android.gms.nearby.exposurenotification.EXPOSURE_CALLBACK" />
...
Related
Android 4.4.3 Force Update Procedure found :
Disable Google Services Framework and Restart the Phone...now clear cache and Enable the framework and check for the Update.....!!
It's been known for a while.
Also, don't do it... http://www.androidpolice.com/2013/1...to-never-clear-google-service-framework-data/
Sent from my Nexus 4 using Tapatalk
Force it but after you will have many problems to resync the phone whit playstore!
I have always forced it this way and have never had any problems with anything afterwards. I just have to accepts G Play terms and conditions after I do it. It might be something Google engineers don't want us doing. I think this process generates a new ID for the phone, which Google might not want.
It doesn't make a difference in getting ota. It is a wasted effort.
raul6 said:
It doesn't make a difference in getting ota. It is a wasted effort.
Click to expand...
Click to collapse
You're wrong, it does. I have always gotten my OTA doing this.
I was also wrong though. I just noticed that my Facebook messenger notifications aren't getting through. So don't do this people, flash the factory images without -w flag instead.
TheNikkoMan said:
You're wrong, it does. I have always gotten my OTA doing this.
I was also wrong though. I just noticed that my Facebook messenger notifications aren't getting through. So don't do this people, flash the factory images without -w flag instead.
Click to expand...
Click to collapse
The syncing problem will resolve itself in a matter of hours. There is no permanent damage done.
Is it really that serious to get the update from OTA with zips and images and roms floating all over the place. We make too much of an incremental update as well..Just my opinion
Just tried it didn't work. Not too fussed about the effects as it only lasts for a few hours.
playya said:
Is it really that serious to get the update from OTA with zips and images and roms floating all over the place. We make too much of an incremental update as well..Just my opinion
Click to expand...
Click to collapse
I did it because the micro USB port is broken, I'm unrooted and have stock recovery (bad situation).
Also, it does work. You just have to repeat the process until it works, it never works the first time.
Anyone managed to get Android Pay working?
I keep getting an error message when trying to add a card.
I'm rooted on 5.1 with latest play services etc.
Tried rootcloak and disabling supersu but neither worked.
acetkbez said:
Anyone managed to get Android Pay working?
I keep getting an error message when trying to add a card.
I'm rooted on 5.1 with latest play services etc.
Tried rootcloak and disabling supersu but neither worked.
Click to expand...
Click to collapse
1. Flash a stock (unmodified build.prop), unrooted rom.
2. Install Android Pay and the latest Google Play Services (version 8.x-230, not the one from google play store)
3. Add all credit cards you want to use in Android Pay
3. Flash your rooted rom (don't wipe data, but wiping cache is okay).
4. Use it.
You will not be able to add additional cards while on a rooted rom, but you will be able to use Android Pay. If you need to add more cards, you need to go back to the stock rom.
Android Pay no longer works on modified system images. There is no way to bypass this, currently.
TheSt33v said:
1. Flash a stock (unmodified build.prop), unrooted rom.
2. Install Android Pay and the latest Google Play Services (version 8.x-230, not the one from google play store)
3. Add all credit cards you want to use in Android Pay
3. Flash your rooted rom (don't wipe data, but wiping cache is okay).
4. Use it.
You will not be able to add additional cards while on a rooted rom, but you will be able to use Android Pay. If you need to add more cards, you need to go back to the stock rom.
Click to expand...
Click to collapse
I'm on the 5.1 OTA but I still can't add my card.
GreaterLesser said:
I'm on the 5.1 OTA but I still can't add my card.
Click to expand...
Click to collapse
What error message do you get? Are you sure you've installed the correct google play services? It's not the one you get from the google play store. You have to find it elsewhere. The version that I'm using is 8.1.15 (2250156-230).
TheSt33v said:
What error message do you get? Are you sure you've installed the correct google play services? It's not the one you get from the google play store. You have to find it elsewhere. The version that I'm using is 8.1.15 (2250156-230).
Click to expand...
Click to collapse
Should I use the latest one from here then? http://www.apkmirror.com/apk/google-inc/google-play-services/
GreaterLesser said:
Should I use the latest one from here then? http://www.apkmirror.com/apk/google-inc/google-play-services/
Click to expand...
Click to collapse
Use the one that matches the number I provided in my previous post exactly (it ends in 230, and it's listed under September 14th ). The last three numbers correspond to different types of phones (android version, screen form factors, etc.). 230 is the code for our Turbos on 5.1.
TheSt33v said:
Use the one that matches the number I provided in my previous post exactly (it ends in 230, and it's listed under September 14th ). The last three numbers correspond to different types of phones (android version, screen form factors, etc.). 230 is the code for our Turbos on 5.1.
Click to expand...
Click to collapse
Strange - That's what I did. I'll try wipe the app's data and start over. Thanks
EDIT: I figured it out. I forgot I had changed my phone's resolution to 1080p and dpi down to 480 (which fits GP Services 8.x-238 but not confirmed to work with 8.x-230 in Android Pay) to save on battery when gaming. So it was the custom DPI that was messing with play services. Changed res back to 1440p and DPI back to 640 and rebooted. It works fine now. Thanks
GreaterLesser said:
Strange - That's what I did. I'll try wipe the app's data and start over. Thanks
EDIT: I figured it out. I forgot I had changed my phone's resolution to 1080p and dpi down to 480 (which fits GP Services 8.x-238 but not confirmed to work with 8.x-230 in Android Pay) to save on battery when gaming. So it was the custom DPI that was messing with play services. Changed res back to 1440p and DPI back to 640 and rebooted. It works fine now. Thanks
Click to expand...
Click to collapse
Yep, that'll do it.
TheSt33v said:
Yep, that'll do it.
Click to expand...
Click to collapse
Similar instructions for 4.4.4 rooted turbos? And does anyone know if a TiBu restore for AP brings back cards?
Sent from my Electric Boogalocked Turbo
rayjr13 said:
Similar instructions for 4.4.4 rooted turbos? And does anyone know if a TiBu restore for AP brings back cards?
Sent from my Electric Boogalocked Turbo
Click to expand...
Click to collapse
Theoretically, yes, except you'll want the version of google play services that ends in 030 since you're not on lollipop. Not sure about TiBu, but it should work.
030, exactly. that what I was anticipating Now to find a stock mofo kk img lol
---------- Post added at 09:31 PM ---------- Previous post was at 08:49 PM ----------
I'm surprised I'm struggling so much to find a stock unrooted system image for mofo. Downloading the firmware files but not sure I know which is which from Rootjunky's website and if it 21.21.15 like I believe it to be can i flash with mofo onto that firmware? I've only flashed using 21.44.15
Argh, noticed that I couldn't get Android Pay working today as well. Sad to see that it requires a reflash, but such is life. Thanks for all the info!
-Collin-
CollinFX45 said:
Argh, noticed that I couldn't get Android Pay working today as well. Sad to see that ito requires a reflash, but such is life. Thanks for all the info!
-Collin-
Click to expand...
Click to collapse
Well there are supported mofo flashable images for lollipop but not for KK yet. This would allow system flash only. And then reflash back to your current modo system. Waiting for a stock KK image w/o root. Still can't understand how/why this hadn't been available since the start of mofo
Sent from my Electric Boogalocked Turbo
Android Pay no longer works with any rooted image. There is no working method to use it yet. Older methods have been broken by Google.
Also, if you want a stock KK image, simply flash the sparsechunks from the stock KK firmware with fastboot. The one on rootjunky's website should work fine, and fastboot won't allow you to flash an image that is not correct for your phone, unlike mofo.
Those rootjunky images aren't the OTA system 21.44 are they? What did Google fix? Guess old Google wallet it is for now.
Sent from my SCH-I605
rayjr13 said:
Those rootjunky images aren't the OTA system 21.44 are they? What did Google fix? Guess old Google wallet it is for now.
Sent from my SCH-I605
Click to expand...
Click to collapse
I don't remember which version it is, but if rootjunky posted it, it's an image that is compatible with mofo. I'm pretty sure he directs you to that image in his video tutorial on how to use mofo. If I understand correctly, Google updated their Safetynet api (which is responsible for Android Pay security enforcement, among other things). In the past, it only did a check when you added a card, which is why you could get around it by adding cards with a stock rom and switching to a modified rom later. Now it checks every time you try to pay for something.
acetkbez said:
Anyone managed to get Android Pay working?
I keep getting an error message when trying to add a card.
I'm rooted on 5.1 with latest play services etc.
Tried rootcloak and disabling supersu but neither worked.
Click to expand...
Click to collapse
Won't work on rooted devices, cloaked, or otherwise.
Tapped out from my Motorola Droid Turbo, featuring Android 5.1. Please pardon my brevity.
I have BK Disabler. What should I disable to prevent updates coming to my phone. It's working great right now, & if it ain't broke, don't try to fix it! Also, bxActions is awesome, so I don't want to risk an update breaking it.
Thanks.
I just searched for update in system, saw 3 or more and disabled, all so disabled there services.
Sent from my SM-N950U using XDA-Developers Legacy app
block the 3 update services as well disable auto update under developer options?
Software Update - con.sec.android.soagent
System Update - com.samsung.sdm
System Update - com.samsung.sdm.sdmviewer
Like my screen name says: Thanks to XDA! You all are legit awesome.
Will this work
How can I disable the update right out of the box. As I require root.
Tinythejuggalo said:
How can I disable the update right out of the box. As I require root.
Click to expand...
Click to collapse
Pull your sim card and disable wifi then set up and root.
Right on thanks man. I’m about to buy a unlocked one from bestbuy. And won’t have a SIM card right away (as I’m going to get one from metro pcs) I just definitely wanted to stop the update. So I can root. A lot of the apps I run require root.
Tinythejuggalo said:
Right on thanks man. I’m about to buy a unlocked one from bestbuy. And won’t have a SIM card right away (as I’m going to get one from metro pcs) I just definitely wanted to stop the update. So I can root. A lot of the apps I run require root.
Click to expand...
Click to collapse
You can boot strait into download mode and if you are on BL1 or 2 you can proceed strait to root. When in download mode you can check you bootloader revision in the RP SWREV line. It will start with either B1, B2 or B3, those are your revision numbers. It's probably better to inspect the phone before you root it but this is what I did with a new Verizon one the other day. I have two unlocked and one Verizon here.
jellyhead said:
block the 3 update services as well disable auto update under developer options?
Software Update - con.sec.android.soagent
System Update - com.samsung.sdm
System Update - com.samsung.sdm.sdmviewer
Click to expand...
Click to collapse
Finally decided to stop risking updating and losing root. took more effort than i thought to find those apps, good thing tibu has a search option. Hope I didn't accidentally wreck my phone.
Hello.
Does anyone know the actual contents of this OTA update that was released today 11/29/17? After the horrible time Samsung and Android gave me after the Note7 fiasco I have become very untrusting of them. The first Note8 OTA update left me with little options relating to rollback and such things.
I would like to know what is exactly in this update. The page I found is vague. The information they leave for the average consumer is always vague.
If no one knows, can anyone lead me to where I can find more information about this particular update?
So that leaves me at this point. If I install this update will it limit my options as for Odin, custom firmware, etc?
So all that Samsung tells me can be found here: http://doc.samsungmobile.com/SM-N950U1/ATT/doc.html
Thank you in advance for any and all assistance. It is always appreciated.
Have not seen any issue's so far on this OTA.
Head over to sammobile dot com, to read more.
In short:
"In addition to the November security patch, the update brings improved performance in the Calendar, Gallery, Voice Recorder, and Reminder apps, a new secure Wi-Fi function, and a fix for an unexplained Samsung DeX error. The firmware version is N950FXXU1BQK6, and at upwards of 840 MB, is among the biggest OTA updates that don’t bring a major Android version upgrade that we have seen"
Safe? It will, at least temporarily, block any attempt at root. If you're running a Substratum theme, it's best to uninstall it before running the update, based on the experience of those who got the October update. Do not reinstall apps that were backed up while running the theme.
Thank you. I am going to Sammobile right now to read more about it.
douger1957 said:
Safe? It will, at least temporarily, block any attempt at root. If you're running a Substratum theme, it's best to uninstall it before running the update, based on the experience of those who got the October update. Do not reinstall apps that were backed up while running the theme.
Click to expand...
Click to collapse
Is it designed to block rooting?
Can you still do the WiFi hotspot trick. Where you try to sing into a hotspot with wrong password then turn on hotspot and quickly turn off WiFi. Can't live without that.
ConcernedCustomer said:
Is it designed to block rooting?
Click to expand...
Click to collapse
The method for rooting Snapdragon phones won't work with updated firmware.
ConcernedCustomer said:
Is it designed to block rooting?
Click to expand...
Click to collapse
Yes it blocks current SamFail method. The U2 bootloader also cannot be downgraded once installed.
sefrcoko said:
Yes it blocks current SamFail method. The U2 bootloader also cannot be downgraded once installed.
Click to expand...
Click to collapse
Thank you for explaining. I was wondering if I would be able to rollback to original stock firmware after updating.
How can I get rid of this update and block all future OTAs?
This update is just sitting somewhere in my phone waiting for me to hit that button. What do I do, boot into factory tech mode and clear the cache or something?
douger1957 said:
The method for rooting Snapdragon phones won't work with updated firmware.
Click to expand...
Click to collapse
How can I get rid of this update and block all future OTAs?
This update is just sitting somewhere in my phone waiting for me to hit that button. What do I do, boot into factory tech mode and clear the cache or something?
pospower said:
Can you still do the WiFi hotspot trick. Where you try to sing into a hotspot with wrong password then turn on hotspot and quickly turn off WiFi. Can't live without that.
Click to expand...
Click to collapse
What this about? First time I'm hearing about this. Is it like getting free internet or something? If the instructions are anywhere on this website would you be so kind as to post the link here.
ConcernedCustomer said:
Thank you for explaining. I was wondering if I would be able to rollback to original stock firmware after updating.
How can I get rid of this update and block all future OTAs?
This update is just sitting somewhere in my phone waiting for me to hit that button. What do I do, boot into factory tech mode and clear the cache or something?
Click to expand...
Click to collapse
Not 100% sure to be honest, but you can maybe try disabling security updates in settings/security menu or maybe disabling/freezing "software update" through an app like TitaniumBackup.
Check the SamFail thread for more info:
https://forum.xda-developers.com/showthread.php?p=74074361
I have the unlocked Note from Samsung on Verizon's network. Currently, tethering works straight out the box. Can anyone confirm that this update does not break this? Thanks
I probably wont update until Oreo...
BlueFox721 said:
I probably wont update until Oreo...
Click to expand...
Click to collapse
That's what I'm trying to hold out for. I have not as of yet experienced any glitches or problems of any kind so I don't see why an update is justified. Just give us Oreo!!! It should've been pre-built into the Note8.
sefrcoko said:
Not 100% sure to be honest, but you can maybe try disabling security updates in settings/security menu or maybe disabling/freezing "software update" through an app like TitaniumBackup.
Check the SamFail thread for more info:
https://forum.xda-developers.com/showthread.php?p=74074361
Click to expand...
Click to collapse
Thank you very much. I'm looking into it for more information now....
Took the update. So far so good. OpenVPN and MS RDP working fine as usual. I was a bit worried as I've read reports of updates screwing up WiFi. I've recently tried these apps on three new Samsung devices and had disconnect issues with all. Oddly, one was a dex using Ethernet - maybe this will fix that, I'll test it. Btw the other devices were a Chromebook pro and a galaxy tab a.
It took me a long time but I have finally gotten things settled down and working adequately on my new 405QA with Android 9, root w/Magisk, etc. I read here <https://www.theandroidsoul.com/lg-v40-update/> and elsewhere there may be an Android 10 coming. While for some that may be great news, for me it isn't. I need to rest and recover from the migration from my old Samsung Note 3 with 4.4.2!
So the question is: how do I 100% avoid any new Android OS updates from being (a) downloaded and (b) installed? In developer options, I have turned OFF "automatic system updates". But I fear this is not enough.
On my old Samsung, rooted with SuperSu, this alone seemed to prevent OS updates. But somehow I wonder if using Magisk and all will make preventing updates a bit different. What is the best way to handle this?
Thanks!
So, what you have done already is enough. Also, for a number of carriers you only get OTA if you are with the original firmware so if you cross-flashed your phone to unlocked US kdz, it is unlikely you would get any OTA updates even if you didn't disable in developer options. Any further options, you'd need to be rooted (which you are), disable/freeze both 'Software Update' apps and 'Fota Update' app. Titanium Backup is the best to freeze these.
Android# said:
So, what you have done already is enough. Also, for a number of carriers you only get OTA if you are with the original firmware so if you cross-flashed your phone to unlocked US kdz, it is unlikely you would get any OTA updates even if you didn't disable in developer options. Any further options, you'd need to be rooted (which you are), disable/freeze both 'Software Update' apps and 'Fota Update' app. Titanium Backup is the best to freeze these.
Click to expand...
Click to collapse
Thanks. Have not cross-flashed but I have used Magisk debloat to deal with fota and software updater. I feel better/safer now. Cheers