Google play protect problem

[Eggstones]

Hi. Tried to install lineage yesterday (didn't go well at all). After that car crash I did a factory reset to get back to scratch. However, I cannot reinstsll Netflix now. Google play protect seems to be fine so I'm not sure what is wrong now.

Edit: Google pointed me in the wrong direction. I seen to have lost the certification when I tried to install lineage. What do I need to do to fix this?

 

[Eggstones]

Is the problem due to me unlocking the bootloader or would cleaning the cache/data on Google play fix this?

 

[Dirk]

Is the problem due to me unlocking the bootloader or would cleaning the cache/data on Google play fix this?

Play Protect has nothing to do with it. Your Bootloader in unlocked so you are failing Safetynet. Are you on OOS now or LOS? It's not clear in your post because you said you installed LOS and then did a Factory Reset. That would leave you still on LOS. But you also said back to scratch. So are you on OOS or LOS?

Relocking your Bootloader is possible on both OOS or LOS. That fixes the Safetynet issue either way. Or you can use Magisk on either to fix the Safetynet issue too.

 

[Eggstones]

Play Protect has nothing to do with it. Your Bootloader in unlocked so you are failing Safetynet. Are you on OOS now or LOS? It's not clear in your post because you said you installed LOS and then did a Factory Reset. That would leave you still on LOS. But you also said back to scratch. So are you on OOS or LOS?

Relocking your Bootloader is possible on both OOS or LOS. That fixes the Safetynet issue either way. Or you can use Magisk on either to fix the Safetynet issue too.

I couldn't install twrp as it didn't recognise the image file so couldn't proceed with lineage. (Have to say the install guide expect the user to really know a heck of a lot of stuff that should be in the guides). Ended up doing a factory reset back to OOS 9.0.5 (I think that is the latest stock version).

So locking the bootloader would fix this issue? It only seems like Netflix is being cranky.

Not rooted so I don't I can use magisk.

 

[Dirk]

I couldn't install twrp as it didn't recognise the image file so couldn't proceed with lineage. (Have to say the install guide expect the user to really know a heck of a lot of stuff that should be in the guides). Ended up doing a factory reset back to OOS 9.0.5 (I think that is the latest stock version).

So locking the bootloader would fix this issue? It only seems like Netflix is being cranky.

Not rooted so I don't I can use magisk.

Magisk is the root method, and also used to fix Safetynet issues. You would need TWRP installed though.

Locking the Bootloader right now will fix the issue you are having. It will also factory reset your phone again, so be prepared for that.

That said, installing TWRP is easy if you follow the guides carefully and avoid the obvious pifalls, or simply trying to use the wrong TWRP is a common issue.

In case you still want to try LOS:

This TWRP:

Download twrp-3.3.1-0-oneplus3.img

Follow this guide from funkwizard:

Flashing TWRP Recovery


Adjust the following settings on the phone:

USB Debugging:
On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging

Enable OEM Unlocking:
On your phone go to Settings > Developer options. Then enable the 'OEM Unlocking' option and make sure that from now on, OEM unlocking option is enabled before you reboot. Sometimes, it might get disabled itself.

Enable Advanced Reboot:
On your phone go to Settings > Developer options. Then enable the 'Advanced Reboot' option.

Place TWRP image in the Platform Tools folder in C:\adb

Then boot into fastboot/bootloader mode on your phone by holding volume up + power or selecting the reboot to bootloader via advanced reboot options.

Open a new command prompt in the platform tools folder and run the following command:

fastboot flash recovery (file name).img

Once the flash has completed, Don't use the "Fastboot Reboot" Command Instead unplug your phone then Manually boot it into recovery by keeping Power + Volume Down button pressed, or you can also use the command:

fastboot boot recovery.img

/Guide.

Just to be clear, when you fastboot flash the TWRP image i linked you to, the command will be:

fastboot flash recovery twrp-3.3.1-0-oneplus3.img

Make sure your phone is actually in fastboot mode when you do this. Just follow the guide. (On Windows 10 a command prompt window can be opened in the platform tools folder by typing 'cmd' in the Address Bar in that folder, using Windows Explorer).

Once you have flashed TWRP, you do need to boot straight into that Recovery. If you boot into the OS, the stock Recovery will overwrite TWRP again. (follow the guide).

Once you are in TWRP, swipe to 'allow modifications'. (If you decide to go down the custom ROM path you will need to Format /Data and Wipe Partitions, then connect to your PC and transfer any zips you need to install to Internal Storage).

You will have to decide for yourself whether you want to be rooted with Magisk. While it can be used to fix Safetynet issues, it's not needed for that. If you want root access, flash Magisk. If you don't want root, don't. Simple.

Let's say for arguments sake you don't want to be rooted and have sucessfully installed TWRP. Next step would be to install LOS. Assuming you want a stable ROM, it would be LOS 16 you install. So you would flash the latest build of that along with Gapps and the second Zip in this post:

https://forum.xda-developers.com/showpost.php?p=78433987&postcount=3 which is:

https://drive.google.com/open?id=1Yy...2YSyxEXNXWolH5 (sec-patch-2019-08-01.zip)

That zip takes care of one Safetynet problem. (CTS Profile).

Once you have LOS setup you can relock your Bootloader. That then takes care of the remaining Safetynet issue.

Clear Cache/Data on the Play Store App and reboot. Use the 'Root and Safetynet Checker' App to test Safetynet status. Once it shows 'Passed', Netflix and Banking Apps (Including Google Pay) that rely on Safetynet will all work.

Or stay on OOS and relock your Bootloader. Only you know what you want, although it seems that after our previous discussions you are ready to dip your toes into the custom ROM scene. Don't let some early setbacks deter you. You're almost there.

 

[Eggstones]

At the moment I'm just trying to get back to where I started. Funk wizards guide is slightly different from the one on the lineage wiki page. I got as far as installing twrp but got only an error message (something on the lines can't load image). Not sure if that's due to adb being wrongly installed or the image being in the wrong folder. Don't think the wiki page mentioned advanced boot mentioned above. Slightly surprised that my banking apps work fine but not Netflix. You would have thought they would be more 'cranky'.

 

[Eggstones]

Been trying again today to do this and am failing massively. Everything seemed fine till I tried to do a backup with helium. Helium is not recognising my OnePlus 3t. Tried to install the drivers that comes with the phone but stopped it after the instal had gone on for about 30 minutes.
Tried the ADB route but the command line doesn't recognise the command. Not sure how to check if it is installed prooerly. Can't remember how I did on my old laptop but on my new hp it doesn't seem to have worked. Remember it being very straightforward so don't understand why it has failed this time
ADB was installed using the lineage page's instructions.

 

[BillGoss]

Been trying again today to do this and am failing massively. Everything seemed fine till I tried to do a backup with helium. Helium is not recognising my OnePlus 3t. Tried to install the drivers that comes with the phone but stopped it after the instal had gone on for about 30 minutes.
Tried the ADB route but the command line doesn't recognise the command. Not sure how to check if it is installed prooerly. Can't remember how I did on my old laptop but on my new hp it doesn't seem to have worked. Remember it being very straightforward so don't understand why it has failed this time
ADB was installed using the lineage page's instructions.

Here's a way to test that ADB can connect to your phone:
- open a PowerShell (a more modern version of CMD) session by right-clicking on the folder where you extracted the ADB files (the folder that contains adb.exe).
- type (without the quotes) ".\adb version". That will tell you the version of ADB your running and that you can execute the command.
- connect your phone to your PC then type ".\adb devices" on your PC. You should get a prompt on your phone asking if you want to trust your PC - say yes. Then you'll get the ID of your phone listed on your PC if everything works ok.

If that all works but just typing "adb devices" doesn't, then that means you haven't set up the of environment settings properly on your PC.

Sent from my OnePlus 3T using XDA Labs

 

[Eggstones]

Here's a way to test that ADB can connect to your phone:
- open a PowerShell (a more modern version of CMD) session by right-clicking on the folder where you extracted the ADB files (the folder that contains adb.exe).
- type (without the quotes) ".\adb version". That will tell you the version of ADB your running and that you can execute the command.
- connect your phone to your PC then type ".\adb devices" on your PC. You should get a prompt on your phone asking if you want to trust your PC - say yes. Then you'll get the ID of your phone listed on your PC if everything works ok.

If that all works but just typing "adb devices" doesn't, then that means you haven't set up the of environment settings properly on your PC.

Sorry but I do not follow. Type where? If I right click on the folder there is nothing opening up where I can write the command in. Only the normal file options show up.
If I search for it using the windows 10 search function I can start it but it doesn't recognise ./adb as a command. So where have I gone wrong?

 

[BillGoss]

@Eggstones
Sorry, I meant to say shift-right-click on the folder and then select "Open PowerShell window here" from the menu.

Sent from my OnePlus 3T using XDA Labs

 

[Eggstones]

Thanks. That worked. I have version 1.0.41.

So now the question is why isn't it recognising my phone. I can see it when I go into the file explorer and open all subfolders.

 

[BillGoss]

Thanks. That worked. I have version 1.0.41.

So now the question is why isn't it recognising my phone. I can see it when I go into the file explorer and open all subfolders.

What worked?
1. typing "./adb version"
2. typing "adb version"
3. typing "./adb devices"

And please quote my post otherwise I can't tell that you've replied.

Sent from my OnePlus 3T using XDA Labs

 

[Eggstones]

What worked?
1. typing "./adb version"
2. typing "adb version"
3. typing "./adb devices"

And please quote my post otherwise I can't tell that you've replied.

Sorry. Yes all of the above. Have now managed to back up the phone (ok didn't get a promt to confirm backup but it seems to have worked). Not sure why I need to write "./adb" to make the commands work but is seems to have done the trick.
Let's see if I can get lineage on the phone now.
And thanks again for your help and patience

 

[BillGoss]

Sorry. Yes all of the above. Have now managed to back up the phone (ok didn't get a promt to confirm backup but it seems to have worked). Not sure why I need to write "./adb" to make the commands work but is seems to have done the trick.
Let's see if I can get lineage on the phone now.
And thanks again for your help and patience

Glad you got it working. But you said that all three commands worked, the second of which had just "adb version", then said you had to use ./adb. If the second one worked then just plain adb should work all the time.

Sent from my OnePlus 3T using XDA Labs

 

[Eggstones]

Glad you got it working. But you said that all three commands worked, the second of which had just "adb version", then said you had to use ./adb. If the second one worked then just plain adb should work all the time.

For some reason ADB is only recognised as a command if I use ./ In front of it . No idea why but at least it is working. Will try to do the ROM tomorrow.
There might be crying

 

[BillGoss]

For some reason ADB is only recognised as a command if I use ./ In front of it . No idea why but at least it is working. Will try to do the ROM tomorrow.
There might be crying

That means you haven't set up the Windows environment properly.
The setup instructions in https://wiki.lineageos.org/adb_fastboot_guide.html say:

On Windows 10:
Open the Start menu, and type “advanced system settings”
Select “View advanced system settings”
Click on the Advanced tab
Open the “Environment Variables” window
Select the Path variable under “System Variables” and click the “Edit” button
Click the “Edit Text” button
Append ;%USERPROFILE%\adb-fastboot\platform-tools to the end of the existing Path definition (the semi-colon separates each path entry)

Can you share:
1. What your Windows Path looks like (screenshot?) and
2. The full path of the folder where you installed ADB

Sent from my OnePlus 3T using XDA Labs

 

[Eggstones]

That means you haven't set up the Windows environment properly.
The setup instructions in https://wiki.lineageos.org/adb_fastboot_guide.html say:

Can you share:
1. What your Windows Path looks like (screenshot?) and
2. The full path of the folder where you installed ADB

Will post that later. When I set it up I followed that guide, but wouldn't be surprised if the pathway thing is wrong as it is a bit opaque in my view.

 

[Eggstones]

That means you haven't set up the Windows environment properly.
The setup instructions in https://wiki.lineageos.org/adb_fastboot_guide.html say:

Can you share:
1. What your Windows Path looks like (screenshot?) and
2. The full path of the folder where you installed ADB

I think I know what's gone wrong.

Pathway: C:\platform-tools

I'm guessing that is the line that should be in the environmental variables...

 

[BillGoss]

I think I know what's gone wrong.

Pathway: C:\platform-tools

I'm guessing that is the line that should be in the environmental variables...

I'd be very surprised if C:\platform-tools is the correct path unless that's actually where you put the unzipped folder.
And kjien\adb... is definitely not right (doesn't include a drive name).

If you use Windows Explorer and select the folder that contains the ADB files and then click on the "Copy path" icon in the menu ribbon (next to the Copy and Paste buttons), then the clipboard will have the correct path.

Sent from my OnePlus 3T using XDA Labs

 

[Eggstones]

I'd be very surprised if C:\platform-tools is the correct path unless that's actually where you put the unzipped folder.
And kjien\adb... is definitely not right (doesn't include a drive name).

If you use Windows Explorer and select the folder that contains the ADB files and then click on the "Copy path" icon in the menu ribbon (next to the Copy and Paste buttons), then the clipboard will have the correct path.

That is what I did to get the path. So should C:\platform-tools replace kjien\adb to make it work?