Develop Bugs

Is it possible to pass new safetynet update with an unlocked bootloader?

I recently ran into a lot of problems due to the fact vr 12 of magisk and the new update to safetynet. I have read that tbe developer of magisk realeased a new version to pass checks. I need to pass as I am an Uber user and in default need Android pay.
I have since tried to go back to stock but ran into problems regarding unlocking my bootloader, currently I am completely stock although my bootloader is unlocked and I can't pass the safetynet check with the new parameters.
I NEED to pass safety net on this device, I don't know what to do, when I lock my bootloader I'm unable to sideload the ROM, with the device unlocked I fail safetynet, will the latest version of magisk work (v13b) with an unlocked bootloader, as my device was soft bricked for 3 days after I locked the bootloader.
Thank you in an advance for any insight on this. Currently I am on stock recovery and unrooted but it seams with the unlocked bootloader I am unable to pass safety net thus unable to use Android pay and subsequently unable to book rides with Uber/Lyft.
Thanks in advance for your help

Sorry I forgot to say I'm running stock recovery and ROM only my bootloader is unlocked, I tried to lock it but adb would not sideload the stock ROM after locking the bootloader. Right now i an as stock as I can be ****
Without a locked bootloader, I don't care if my device is rooted or not I just want to pass the safety net check, I'm failing CTS mismatch, I don't know why after factory resetting my device, why google is doing this IDK I just need to get my device working 100 percent, rooted or not at this point I don't care.
Thank you for your future reply and thank you again if you have helped me before, this is a nightmare, why google is doing this Idk but I funny believe it's in anyone's best interest except possibly but business​.

Quick google search for magisk beta version 13. His newest beta passes safetynet, and i believe he claims its easy to fix in the future as well

I believe you need a custom kernel that bypasses the Safety Net boot-loader check.
If you want to completely go back to stock (and pass safety net) follow this guide: https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/

Magisk 13 BETA or wait for stable.

I previously tried to go completely to stock but ran into problems after locking ​the bootloader,
https://forum.xda-developers.com/oneplus-3/help/tried-to-to-stock-adb-error-read-file-t3621902
As I would be fine with that, I prefer using magisk so I suppose I'll go with that,
What kernel is recommended? I was thinking blu-spark or franko as afaik they work?
After I lock my bootloader I ran into problems, adb would recognize my device along with fastboot although, it would not side load the ROM, so I guess my only option is magisk, I just need to find,
Correct kernel, best version of TWRP recovery (I used to have blu-spark, with franko kernel, this time I think I'm going to go buy with blu-spark)
I appreciate your help, although whatever works is what I'll do, IDK why I can't go back to stock, I've done it before so IDK what has changed, I just need to find the latest version 13 beta of magisk.
Currently im fully stock except for unlocked bootloader and I get the CTS mismatch error on safety net, (these safety net crap is annoying)

I am using Magisk v13 and it is completely free of bugs.
lebeatnik said:
I previously tried to go completely to stock but ran into problems after locking ​the bootloader,
https://forum.xda-developers.com/oneplus-3/help/tried-to-to-stock-adb-error-read-file-t3621902
As I would be fine with that, I prefer using magisk so I suppose I'll go with that,
What kernel is recommended? I was thinking blu-spark or franko as afaik they work?
After I lock my bootloader I ran into problems, adb would recognize my device along with fastboot although, it would not side load the ROM, so I guess my only option is magisk, I just need to find,
Correct kernel, best version of TWRP recovery (I used to have blu-spark, with franko kernel, this time I think I'm going to go buy with blu-spark)
I appreciate your help, although whatever works is what I'll do, IDK why I can't go back to stock, I've done it before so IDK what has changed, I just need to find the latest version 13 beta of magisk.
Currently im fully stock except for unlocked bootloader and I get the CTS mismatch error on safety net, (these safety net crap is annoying)
Click to expand...
Click to collapse

M8s on Marshmallow - systemless root - how?

Hi,
I recently had to return my phone back to stock because of a warranty issue. (battery dying between 25% and 40%)
So chances are high that I will get the phone back with Marshmallow instead of Lollipop.
is there a guide or can anyone give some pointers how to root this device? After a bit of reading I still have a few specific questions, so maybe someone here can help.
A) What TWRP version will I need for the M8s on Marsmallow?
B) Will Magisk systemless root work on this device?
C) If the rooting has succeeded and I remove some bloatware apps from /system/vendor and /privapp and such. Will this trip the Google safety net? Or is safety net not yet applied to our M8s devices?
Thanks!

I don't personally have the M8s version specifically. But as the device forum sections for all the M8 versions in general are becoming pretty quiet; I'll try to help you to the best of my knowledge.
A) The TWRP recovery posted in this (M8s) forum section should work fine on Marshmallow. Looks like it's only updated to 2.8.6
B) Should work, yes. I would suggest the current stable Magisk version, which is 14.0
Backup your stock (unrooted) ROM before trying to root (as you always should - this is best practice and just good common sense). Then if anything goes wrong, you can easily restore to stock.
C) Not sure. But I can tell you on my current device (OnePlus 3T) that removing system (bloat) apps does not trip safety net.

Hi @redpoint73,
Thanks. That takes away some worries and gives me some confidence for giving it a third shot . Nandroid's don't work on the M8s unfortunately, I've tried this once since I botched something up during my first root attempt, put back the Nandroid and my Bluetooth was dead. (and probably more, but I didn't investigate it further back then.)
As in regards of removing bloat, since HTC has the S-on I was only able to remove the pre-installed apps from within TWRP (or else the apps were back after a reboot), so I guess this process remains the same?
Thanks so far and I'll report back my results in this topic. Now I first have to wait to see if they give me my warranty, since the bootloader said relocked and the firm I had to send it to is notorious for blaming factory faults on rooting of the phone. Fingers crossed!

Thijs_Rallye said:
As in regards of removing bloat, since HTC has the S-on I was only able to remove the pre-installed apps from within TWRP (or else the apps were back after a reboot), so I guess this process remains the same?
Click to expand...
Click to collapse
Should be the same, yes.
The reason for this, is that the system is write-protected, even with root. On the M8, there is a kernel mod which disables the write protection (allows you to modify system while booted to OS), but I don't know if there is such a mod for the M8s. But if you were able to do it in TWRP, the same should apply on Marshmallow.

So I finally got my phone back, or well, to be accurate, I got another phone (albeit another M8s) back under warranty. I guess they f'd it up during repairs or something. And as expected my phone was upgraded to Marshmallow.
Anyhow, the more I read about Magisk and systemless rooting the more lost I seem to get lost. Is there somewhere a step by step guide for obtaining root on this phone?
Let me recap from what I've understood so far (SOURCE 1, SOURCE 2 and SOURCE 3)
1) Backup my boot partition, I am still searching how to accomplish this without rooting the phone first. Booting to TWRP without installing resulted in mangling some data in the boot partition, so unfortunately that is not an option. (blanks the OS version)
2) Boot to TWRP and flash the Magisk zip file. There should be an option somewhere in TWRP to enable systemless rooting.
3) ?
So if anyone knows if I am on the right (or wrong) track please let me know .
Thijs
Edit: I can't seem to get the phone boot TWRP for some reason (from my harddrive htc_fastboot boot twrp.img). This used to be possible on my old M8s which I had send in for repairs. Do I really have to flash it because I have no way of backing up the old original recovery .

Okay, since it is kinda dead in here let me bump this for anyone in the same situation. I've managed to install Magisk successfully. The steps involved
1) unlock bootloader
2) flash twrp (htc_fastboot flash recovery twrp.img) I've used the latest version from Captain Throwback which I've found in the OP of the Void_Zero Lineage OS thread.
3) boot the phone and copy magisk systemless root zip and the apk file to your internal storage Grab the uninstaller as well in the topic.
4) reboot to recovery (adb reboot bootloader)
5) flash the zip from within recovery
6) reboot the phone and install the Magisk app.
7) done
Use this guide on your own risk. It worked flawlessly for me but no guarantees .

Stock with unlocked bootloader & root but can't install updates or remove apps.

I bootloader unlocked/rooted this phone so I could uninstall Sprint's bloatware.
It seems without replacing the ROM I can't get rid of the bloat.
Titantium backup says 'failed to locate apk' when I try to uninstall.
I could pay the $5 to freeze them but I should be able to remove the apps.
When I get the security update from Moto it downloads but won't install.
It seems I'm getting the double whammy.
Do I have to unroot or hide something via magisk to get the security updates to work?
Can anyone suggest how to remove the bloat without replacing the ROM?

lip008 said:
I bootloader unlocked/rooted this phone so I could uninstall Sprint's bloatware.
It seems without replacing the ROM I can't get rid of the bloat.
Titantium backup says 'failed to locate apk' when I try to uninstall.
I could pay the $5 to freeze them but I should be able to remove the apps.
When I get the security update from Moto it downloads but won't install.
It seems I'm getting the double whammy.
Do I have to unroot or hide something via magisk to get the security updates to work?
Can anyone suggest how to remove the bloat without replacing the ROM?
Click to expand...
Click to collapse
Searched 'debloat' in our forum and found this.
Most things have been answered, just search a little, it's helps keep these forums cleaner and more efficient.

I will give that a try but can anyone comment about the updates?
Do I have to unroot or lock the bootloader to get Lenovo's security updates?

lip008 said:
I will give that a try but can anyone comment about the updates?
Do I have to unroot or lock the bootloader to get Lenovo's security updates?
Click to expand...
Click to collapse
Unroot, yes. Relock, no. You need to flash all back to complete stock with no edits to any partitions to get updates. TWRP mounts system so once you do any zip install, the hash of system or other partitions changes and the hash check during update will fail.

Uzephi said:
Unroot, yes. Relock, no. You need to flash all back to complete stock with no edits to any partitions to get updates. TWRP mounts system so once you do any zip install, the hash of system or other partitions changes and the hash check during update will fail.
Click to expand...
Click to collapse
Let me ask one last question...lol. Anyway to disable the popup about getting the new device updates since I can't get it with the device rooted?

lip008 said:
Let me ask one last question...lol. Anyway to disable the popup about getting the new device updates since I can't get it with the device rooted?
Click to expand...
Click to collapse
It would be best to flash all then take the update and reboot after. If you must keep your data and not risk losing any, then your best bet is to "disable" or freeze updater.

Need assistance with relocking bootloader on PIXEL 3 XL running Q Beta 3

Just want to know how i can go about re locking the device to set up G-pay
Don't want to end up bricking the device,
Anyone able to assist?

If you are 100% stock, and have a backup of everything of importance, as this will wipe your device, just execute: fastboot flashing lock

I relocked my bootloader on Q DP3, no luck using Google Pay. The beta rom is not CTS compatible.
collindubya said:
Just want to know how i can go about re locking the device to set up G-pay
Don't want to end up bricking the device,
Anyone able to assist?
Click to expand...
Click to collapse

Several people in the Pixel 3 forum are reporting issues with Google Pay on Beta 3, but I used it Tuesday afternoon with no issue. I haven't tried again yet but I updated in the afternoon and rebooted to complete the update when I got in my car to go home. Stopped at the store on the way and used Google Pay without issue.

Gpay works. Did you wipe your wipe after relocking it? I know it says it wipes it. But doesn't truly wipe everything unless you access factory recovery and wipe it there too. I relocked my bl and gpay works fine. Beta 3 is certified now. Look in play store settings. Certified. So everything will work now. Having the oem ticked on with the bl locked will also deny some features. That switch has to be off to be truly locked. After relocking you have to go into settings and flip that off. It will be on after relocking.

Valid Operating System not found

I wasn't fully stock and relocked the bootloader (stupid thing to do, i know) and now it seems like it's bricked as I can't boot to recovery or anything.
Is there ANY way I can fix this without replacing the phone? Or is it destroyed?

You can try using these Lineage OS installation instructions to see if you can get the bootloader unlocked again before you can attempt to start over getting the phone working again.
Install LineageOS on taimen | LineageOS Wiki
wiki.lineageos.org

Trixelit said:
I wasn't fully stock and relocked the bootloader (stupid thing to do, i know) and now it seems like it's bricked as I can't boot to recovery or anything.
Is there ANY way I can fix this without replacing the phone? Or is it destroyed?
Click to expand...
Click to collapse
Without a working recovery there is no way to restore the unit short of paying Google for the privilege. The LineageOS instructions provided will not work as they require the bootloader to be unlocked. Flashing an OTA image from Google also will not work as it requires the stock recovery be present.

Strephon Alkhalikoi said:
Without a working recovery there is no way to restore the unit short of paying Google for the privilege. The LineageOS instructions provided will not work as they require the bootloader to be unlocked. Flashing an OTA image from Google also will not work as it requires the stock recovery be present.
Click to expand...
Click to collapse
That sucks, at least I know not to do that again. (I'm glad that I only did that on my backup phone, not my main phone)