Database Users

Oral B Bluetooth Issues

I just bought one of the Oral B 8000 toothbrushes and apparently there is an issue in Android 7.0 which won't allow the toothbrush to pair over bluetooth with the phone app. I was curious if anyone else had come across this issue and gotten it resolved. The issue is known to Oral B but right now the only fix is to upgrade to Android 7.1 and I would like to stay on stock firmware because it's nice and stable. I am rooted and bootloader unlocked so if absolutely necessary I can change roms but I was hoping someone might know of a fix. Was also curious if the latest phone update might have fixed it even though it didn't change the Android version number.

pwnerman said:
I just bought one of the Oral B 8000 toothbrushes and apparently there is an issue in Android 7.0 which won't allow the toothbrush to pair over bluetooth with the phone app. I was curious if anyone else had come across this issue and gotten it resolved. The issue is known to Oral B but right now the only fix is to upgrade to Android 7.1 and I would like to stay on stock firmware because it's nice and stable. I am rooted and bootloader unlocked so if absolutely necessary I can change roms but I was hoping someone might know of a fix. Was also curious if the latest phone update might have fixed it even though it didn't change the Android version number.
Click to expand...
Click to collapse
an Android controlled toothbrush? is it april 1st? How does that work?

blue"tooth" LOL
You listen to music via vibration of your teeth.

railfan-eric said:
an Android controlled toothbrush? is it april 1st? How does that work?
Click to expand...
Click to collapse
it syncs with bluetooth and your phone camera to see what stops you are missing and over brushing. even without all that functionality and just as a dumb toothbrush it really is worth it

Same problem with LG G5 with 7.0. Did you find any solution?

Oral-B not starting on rooted devices
Hi,
Has anyone managed to use the Oral-B app on a rooted android? I am on Oreo with Xposed, and despite adding the app to Rootcloak config, it will detect the root.
I've read on the app comments that uninstalling supersu makes the app work, so it may be that Rootcloak default config is missing some keywords/commands?

jbd7 said:
Hi,
Has anyone managed to use the Oral-B app on a rooted android? I am on Oreo with Xposed, and despite adding the app to Rootcloak config, it will detect the root.
I've read on the app comments that uninstalling supersu makes the app work, so it may be that Rootcloak default config is missing some keywords/commands?
Click to expand...
Click to collapse
hi. did you find a solution? rootcloack didnt help me...

Ugo10 said:
hi. did you find a solution? rootcloack didnt help me...
Click to expand...
Click to collapse
Yes, it's working for me now. I have actually two solutions.
- I moved from superSU to Magisk. I still don't pass SafetyNet as I'm using gravity box. Now I'm with Oral-B app 6.0.1 and it starts and works correctly.
- at some point, while still with superSU, I downgraded the app with an apk of a previous version found online. The v5.2.3 doesn't seem to have SafetyNet implemented and it has the same features anyway. Remember to disable "auto update" in Google play to remain on that version.

jbd7 said:
Yes, it's working for me now. I have actually two solutions.
- I moved from superSU to Magisk. I still don't pass SafetyNet as I'm using gravity box. Now I'm with Oral-B app 6.0.1 and it starts and works correctly.
- at some point, while still with superSU, I downgraded the app with an apk of a previous version found online. The v5.2.3 doesn't seem to have SafetyNet implemented and it has the same features anyway. Remember to disable "auto update" in Google play to remain on that version.
Click to expand...
Click to collapse
it's perfect! thx!

Device is altered

I didn't unlock my bootloader and I'm not rooted. My bootloader is locked. But Google Pay seems to think my device is modified. I did install Android 10 on my TMobile variant but it was working fine when I had the Android 9 open beta. Disney + and Netflix aren't in the app store so Google Play thinks I'm altered too. Help?

bigmikey307 said:
I didn't unlock my bootloader and I'm not rooted. My bootloader is locked. But Google Pay seems to think my device is modified. I did install Android 10 on my TMobile variant but it was working fine when I had the Android 9 open beta. Disney + and Netflix aren't in the app store so Google Play thinks I'm altered too. Help?
Click to expand...
Click to collapse
Seems to be working just like everyone else's T-Mobile Android 10 OP6T. This is a known issues on our devices.

bigmikey307 said:
I didn't unlock my bootloader and I'm not rooted. My bootloader is locked. But Google Pay seems to think my device is modified. I did install Android 10 on my TMobile variant but it was working fine when I had the Android 9 open beta. Disney + and Netflix aren't in the app store so Google Play thinks I'm altered too. Help?
Click to expand...
Click to collapse
It's a bug, you're going to have to wait until it's patched, no ETA from OnePlus yet.
Sent from my ONEPLUS A6013 using Tapatalk

I converted my T-Mobile phone using the MSM tool (no root) a while ago and never had trouble with Google Pay. It stopped working only after the latest update (Android 10.0). I hope OP will fix this in their next update.

Yeah, we all do. I have not been able to get around it. Tried the magisk module "setprops" but that didin't work. Anyone find a way around it yet?

Scott said:
Yeah, we all do. I have not been able to get around it. Tried the magisk module "setprops" but that didin't work. Anyone find a way around it yet?
Click to expand...
Click to collapse
You mean magiskhide props ?...
Ans set 6T pie fingerprint?...

cultofluna said:
You mean magiskhide props ?...
Ans set 6T pie fingerprint?...
Click to expand...
Click to collapse
The latest magiskhide props module has a valid 6T A10 fingerprint, I'm using it and my device is certified.

Open Beta 2 T-Mobile

Has anyone tried to flash the new Beta update to the OnePlus 6T TMobile version? Does it still give the same error "Build Version does not match Hardware version"?

bigmikey307 said:
Has anyone tried to flash the new Beta update to the OnePlus 6T TMobile version? Does it still give the same error "Build Version does not match Hardware version"?
Click to expand...
Click to collapse
I just downloaded and installed the open beta 2 and it's great! I'm going to give it a week and "test the engine and tires." I still have my Pie firmware, just in case.
NOTE: I installed using the local update method. I was rooted also with pie.

Main OP question was if you flash android 10 via zip and tried flashing beta on top to see if it works like it did on android 9. Please let me know if anyone tried this as well. Thank you in advance.

bigmikey307 said:
Has anyone tried to flash the new Beta update to the OnePlus 6T TMobile version? Does it still give the same error "Build Version does not match Hardware version"?
Click to expand...
Click to collapse
No 'build version does not match hardware version' error when flashing the new beta to TMO converted one plus 6t. I used TWRP 3.3.1.28 and all is good.

We still don't have the "reserve" partition though. OnePlus fonts will be missing and show up as italic fonts. A few apps are also gone but can be installed from play store. You wont pass Safety net so you will miss out on Netflix, etc.
No F/C's. Not sure on battery yet.
Everything else does seem good! I am enjoying it!

Scott said:
We still don't have the "reserve" partition though. OnePlus fonts will be missing and show up as italic fonts. A few apps are also gone but can be installed from play store. You wont pass Safety net so you will miss out on Netflix, etc.
No F/C's. Not sure on battery yet.
Everything else does seem good! I am enjoying it!
Click to expand...
Click to collapse
You can use the reserve partition magisk module...

justforgot said:
Main OP question was if you flash android 10 via zip and tried flashing beta on top to see if it works like it did on android 9. Please let me know if anyone tried this as well. Thank you in advance.
Click to expand...
Click to collapse
I used patched MSM tool to get TMobile variant to international ROM without unlocking bootloader and then I local upgraded to Android 10 stable, then local upgraded to OB 2 and all is well!

So I'm on Android 10 Stable with bootloader unlocked. What happens if I relock bootloader? Will I go into bootloop on restart, and will it get rid of the warning on restart, or do I need to do what @bigmikey307 did?
Update : I did the above but didn't go to beta 2

PapaMag said:
So I'm on Android 10 Stable with bootloader unlocked. What happens if I relock bootloader? Will I go into bootloop on restart, and will it get rid of the warning on restart, or do I need to do what @bigmikey307 did?
Update : I did the above but didn't go to beta 2
Click to expand...
Click to collapse
didn't understood what you meant about "didn't go to beta 2"...
for beta you need to flash via local update since you're on the official update yet. link is on the beta thread or on the Oxygen Updater app from playstore

TJSteveMX said:
didn't understood what you meant about "didn't go to beta 2"...
for beta you need to flash via local update since you're on the official update yet. link is on the beta thread or on the Oxygen Updater app from playstore
Click to expand...
Click to collapse
I just meant I stopped at 10.0 and didn't local upgrade to beta yet

Any word on the Play Protect Certification issue on T-Mo devices? I've been getting by without it on the Stable release, but I'll definitely go Beta of this update resolves the issue.

taylor85345 said:
Any word on the Play Protect Certification issue on T-Mo devices? I've been getting by without it on the Stable release, but I'll definitely go Beta of this update resolves the issue.
Click to expand...
Click to collapse
Nope, not certified. Someone posted some links in the Official Stable thread with instructions on how to do it using root and some magisk modules.

taylor85345 said:
Any word on the Play Protect Certification issue on T-Mo devices? I've been getting by without it on the Stable release, but I'll definitely go Beta of this update resolves the issue.
Click to expand...
Click to collapse
So like @Scott Mentioned, it requires root to pass at the moment. The Magisk mod is called Magiskhide props config and it works perfectly well as a workaround. Good luck!
Sent from my OnePlus6T using XDA Labs

I'm probably overlooking something obvious but I have no idea what it is.
Here's the story; I have a T-Mobile OP6t converted to International.
Flashed the update to OB31 (Open Beta 2).
I have Magisk and Titanium Backup installed, both with root access allowed.
However, I'm unable to get TB to actually uninstall some of the system apps I don't want.
Also, I can't copy and paste (via Solid Explorer) my edited HOSTS file to block ads.
What am I missing?

Scott said:
We still don't have the "reserve" partition though. OnePlus fonts will be missing and show up as italic fonts. A few apps are also gone but can be installed from play store. You wont pass Safety net so you will miss out on Netflix, etc.
No F/C's. Not sure on battery yet.
Everything else does seem good! I am enjoying it!
Click to expand...
Click to collapse
What is the reserve partition? And do I need it/want it?

cultofluna said:
You can use the reserve partition magisk module...
Click to expand...
Click to collapse
Do you have a link?

Scott said:
Do you have a link?
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=1899786940962618515

Scott said:
We still don't have the "reserve" partition though. OnePlus fonts will be missing and show up as italic fonts. A few apps are also gone but can be installed from play store. You wont pass Safety net so you will miss out on Netflix, etc.
No F/C's. Not sure on battery yet.
Everything else does seem good! I am enjoying it![/QUOTE @Scott , which apps are you referring to?
Sent from my ONEPLUS 6T using Tapatalk Pro.
If I've helped you out, please tap the thanks button.
Click to expand...
Click to collapse

xRogerxC said:
@Scott , which apps are you referring to?
Sent from my ONEPLUS 6T using Tapatalk Pro.
If I've helped you out, please tap the thanks button.
Click to expand...
Click to collapse
The OP Weather app for instance, the OP square and round icon packs, e few more that I dont recall. All of them could be downloaded from the play store. You only need the font fox magisk module referenced earlier in this thread. You wont notice these missing apps on a dirty install but you will see it on a clean install or factory reset.

Reinstalling the ROM ZIP via in-built updater fixes the issue. Done it multiple times.

Netflix not working after update to MIUI 11.0.2 Android Q

Hi all, I have just updated to the latest MIUI 11.0.2 from MIUI.eu just to realise that I was unable to use Netflix. (Takes extremely long at loading, end off with a "Device Failure Occured - 501 109"). Does anyone has the same issue?
Thanks!

Mine actually loads with widevine l3
But the play store can't update apps for some reason, it can't download anything too
Sent from my Redmi K20 using Tapatalk

Clear all cache and data from playstore

Tazreean Shahariyr said:
Mine actually loads with widevine l3
But the play store can't update apps for some reason, it can't download anything too
Click to expand...
Click to collapse
If unlocked your bootloader your device becomes uncertified by Google. Which means you can install or even update the Netflix app that came pre installed.you can check this at play store settings then scroll down.

Benfatica said:
If unlocked your bootloader your device becomes uncertified by Google. Which means you can install or even update the Netflix app that came pre installed.you can check this at play store settings then scroll down.
Click to expand...
Click to collapse
Actually, if you use .EU ROM without root you can still be certified by Google. I'm using latest weekly without root and my device is certified, I can download Netflix from PlayStore etc..

VzQzZ said:
Actually, if you use .EU ROM without root you can still be certified by Google. I'm using latest weekly without root and my device is certified, I can download Netflix from PlayStore etc..
Click to expand...
Click to collapse
Rooted with Magisk and PlayStore is certified too.

Micdu70 said:
Rooted with Magisk and PlayStore is certified too.
Click to expand...
Click to collapse
Yep! Me too

VzQzZ said:
Actually, if you use .EU ROM without root you can still be certified by Google. I'm using latest weekly without root and my device is certified, I can download Netflix from PlayStore etc..
Click to expand...
Click to collapse
I ment stock miui, in Xiaomi EU or any other ROM they trick the system so it behaves as if it's locked, you can see this when you connect you device to the miui debloating tool. You can see that it will say your device is locked but it isn't.

Micdu70 said:
Rooted with Magisk and PlayStore is certified too.
Click to expand...
Click to collapse
Hi, how did you install magisk? I have made a patch file, installed with twrp but no matter what I get a recovery bootloop. Only way past was in twrp to allow permissions on busy box and faulity to 644. This lets me get the root and can get magiskhide but none of he other modules will install and save to the modules menu. MIUI 11

So what is the case here, with the same rom version some phones have widevine L1 and others L3?

atabertass said:
So what is the case here, with the same rom version some phones have widevine L1 and others L3?
Click to expand...
Click to collapse
We speak about Google Play Certification and not Widevine, that's not related.

Xiaomi.eu 11.0.2 has unfortunately L3 widewine and this can cause problems (maybe)
Ps: but dev version xiaomi.eu 9.11.28 has full support L1 and also the device is certified on google play. if not, there is a "safety patch magisk module" and it changes the fingerprint of the device (it changes as Huawei phone ) and works awesome

[Question] Safetynet on Openbeta

Hey,
Long time. Rooter (since HTC desire HD) here.
I remember on my older Oneplus phones, installing an beta would stop you passing Safetynet, so banking apps wouldn't work etc. Is this still the case? Can anyone on the 11 betas see if it passes safetynet? I'm not rooted currently!

Anyone?

Havent tried the beta's yet either. But I am rooted and pass safetynet on my 8pro. One of my 1st rooted devices was the HTC DesireHD as well and I did like the Nexus 5 alot.
atm I'm using XXX flashed with magisk and the current Radioactive kernel and my phones gr8 and passes safetynet for banking apps , gpay , netflix etc.

mapester said:
Havent tried the beta's yet either. But I am rooted and pass safetynet on my 8pro. One of my 1st rooted devices was the HTC DesireHD as well and I did like the Nexus 5 alot.
atm I'm using XXX flashed with magisk and the current Radioactive kernel and my phones gr8 and passes safetynet for banking apps , gpay , netflix etc.
Click to expand...
Click to collapse
Yeah with magisk I know you can pass, but I havnt felt the need to root this phone (nor my 7 Pro when I had it) - especially since a lot of people have had a fingerprint enrollment problem (I know you have to backup the persist partition) - I just wanted to test out some android 11 stuff, but it used to be that if you were in a beta, you failed safetynet even if BL was locked. Was just curious, thats all!

manor7777 said:
Yeah with magisk I know you can pass, but I havnt felt the need to root this phone (nor my 7 Pro when I had it) - especially since a lot of people have had a fingerprint enrollment problem (I know you have to backup the persist partition) - I just wanted to test out some android 11 stuff, but it used to be that if you were in a beta, you failed safetynet even if BL was locked. Was just curious, thats all!
Click to expand...
Click to collapse
Just to clarify - the fingerprint enrollment problem has nothing to do with root. It's all about the bootloader. Something happened when the bootloader was relocked (manually or by msmdtool). I believe the issues is fixed on later OOS versions, but haven't really looked into it as I'm not relocking.
Your question, however, the answer depends on when you flash the OB. It seems the OB is released around the same time the build is sent too google for verification, so if you're too quick to flash safetynet fails. If you wait for google to verify the ROM it's all good. There is, as far as I know, no information about when builds are verified. If you flash the ob too soon you can clear ps data and it will pass once google has updated on their part.
Edit: That's how they do it with pre-11 betas, not sure about 11, I guess that's up to google as it's an unreleased OS version. I believe even pixels fail their safetynet checks at this time.

efex said:
Just to clarify - the fingerprint enrollment problem has nothing to do with root. It's all about the bootloader. Something happened when the bootloader was relocked (manually or by msmdtool). I believe the issues is fixed on later OOS versions, but haven't really looked into it as I'm not relocking.
Your question, however, the answer depends on when you flash the OB. It seems the OB is released around the same time the build is sent too google for verification, so if you're too quick to flash safetynet fails. If you wait for google to verify the ROM it's all good. There is, as far as I know, no information about when builds are verified. If you flash the ob too soon you can clear ps data and it will pass once google has updated on their part.
Edit: That's how they do it with pre-11 betas, not sure about 11, I guess that's up to google as it's an unreleased OS version. I believe even pixels fail their safetynet checks at this time.
Click to expand...
Click to collapse
Ah OK, that makes sense. Most of the OnePlus betas I've installed n the past have been after Google. Released the OS to pixels, and they still failed Safetynet, but I also know Google is constantly changing safetynet stuff so that's why I wondered. Thanks anyway!