My device is not passing safteynet(cts Profile) with or without magisk...anyone?
Attachments
Last edited:
Right now I'm using FP on boot and have been using it for a week and rebooting almost every day(for school to put in my locker) and it has been fine so farYes, that's possible and what happened to some users.
They needed to go to recovery and delete the Lockscreen security afterwards...
My device is not passing safteynet(cts Profile) with or without magisk...anyone?
why it's not working with October vendor?
it's still asking for September vendor
Yes
Boot stuck at the ACIP animation after latest OTA update. What is the problem?
BTW, same...had to clean flashBoot stuck at the ACIP animation after latest OTA update. What is the problem?
Oh, you asked for the magic ETA, lol...
I fix it by dowloading the "magiskhide props config" module in magisk, and then run it in a terminal using command "props", apply the option 1 "fingerprint".
Can you give link to module pls?thx btwI fix it by dowloading the "magiskhide props config" module in magisk, and then run it in a terminal using command "props", apply the option 1 "fingerprint".
Factory Images for flashing via FASTBOOT:
Starting with Oct 26th Weekly: Current: 8.1.0 (OPM7.181005.003, Oct 2018)
Including Oct 23th Weekly: Previous: 8.1.0 (OPM6.171019.030.K1, Sep 2018)
**********************************************************************************************************************************************************************
After oct 26 ota and updating vendor and radio images, ctsProtile passes finally without magisk prop mod :laugh:Hey Guys,
First of all, SORRY for delay. And also really very sorry If my delay was the cause for the issues in your devices.
The OP was updated and the sources will be updated today and starting with next weekly, you'll need the stock images from recent Google leak - 8.1.0 (OPM7.181005.003, Oct 2018)
Cheerz
P.S. Guys, Started our Jenkins and you'll get the updated with Oct 2018 sources today's Weekly.
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
@razorloves added a comment - 2017-09-11 8:42 PM
Thanks to ezio84 for letting me know this is caused by using gapps that doesn't include these files:
com.google.android.camera.experimental2016.jar
com.google.android.camera.experimental2016.xml
Beans gapps includes these files, so I recommend you use those.
If you want to use opengapps, those needed files are only included in stock and super variants.
Or, use the aroma opengapps variant and choose the google camera option.
Factory Images for flashing via FASTBOOT:
Starting with March 7th Nightly: Current: 8.1.0 (OPM3.171019.016, Mar 2018)
Previous (Including March 6th Nightly): 8.1.0 (OPM3.171019.014, Feb 2018)
I'd suggest these steps to get your Project Fi SIM discovered:
1. Go to post #1 and install the ROM completely following the instructions.
2. Setup your phone, but skip the window about inserting the SIM card.
3. When your phone is setup (it will be without Fi service) go to settings and choose security.
4. Make sure you select "none" as the security option. You don't want a pin for sure.
5. Reboot into "Recovery" and follow the steps in post #1 to install the ROM and Vendor image.
6. Your phone should boot normally and discover the Fi SIM card.
As you can see from my post count I am new at helping anyone. Hopefully I did this right