Database Users

Unlock Bootloader without wipe? Root? 6.0

Hello,
I am looking for a smooth method to lock and unlock the bootloader on my Nexus Player. Although being it is not a phone I guess I could just leave it unlocked... I am also looking for the best current method to root the Nexus Player on 6.0. I have been searching but I keep coming across guides for lollipop.
Thank you in advance!

Unlock/root guides are similar. They are the same except for the files used.
For Android M - i use fugu-mra58k. Use Chainfire's beta-supersu-v2.51 and it requires custom boot img, can be found on his tread http://forum.xda-developers.com/apps...ellow-t3219344. There is supersu2.52 but im not sure if it will have issues. My NP was already unlocked so I just flashed factory,moved supersu2.51 zip, boot into bootloader and flash twrp and CF's custom boot.img. At this point DO NOT restart NP, just boot it into twrp and flash supersu (you'll need otg+mouse attached). reboot and you should be good to go.

Bootloader unlocking

Why cant the s5 be unlocked with an oem unlock commanf like any other phone unlocks? Sony, Motorola, etc. Can be unlocked this way but why not samsung?

Directions:
Before You Try This Method You Need To Download And Install
eMMC_CID_Checker_.apk And Check Your CID
Attachment 4059204 [/SIZE][/B][/CENTER]
Your CID Number will be the first two numbers in the eMMC Box under CID
15=Bootloader That Can Be Unlocked And Custom TWRP Recovery Can Be Installed
11=Bootloader that CANNOT Be Unlocked. You can only have root through Lollipop 5.0 with SafeStrap Recovery or FlashFire. You can use Marshmallow ROMs but only non-rooted one, preferably with the use of SafeStrap. This Will Allow Easy downgrade to Lollipop to reroot and flashing of certain modified Marshmallow ROMs and mod zips

SafetyNet Check Fails on Recently Unrooted Phone

unrooted XT1644 (previously Magisk rooted)
bootloader unlocked
TWRP 3.1.1-0
ElementalX kernel 3.10.84
OS version: 7.0
Security patch level: June 1, 2017, firmware NPJ25.93-14.5
Baseband: M8952_70030.25.03.62R ATHENE_RETUSA_CUST
SafetyNet app failed "CTS profile" on unrooted Android. Oddly, my phone passed SafetyNet when I used Magisk. But after restoring my phone from a Nandroid backup taken before Magisk was flashed, it no longer passes. Might there be file directory remnants of Magisk that are affecting the SafetyNet result? Any troubleshooting steps appreciated.
There's now a September 1, 2017 OEM security OTA update waiting for me in my Notifications bar. I'm hopeful that the update will create a new system partition that'll get rid of what's causing the SafetyNet fail. Unfortunately a logo.bin TWRP flash fix made a change to my system partition settings that won't allow me to safely take an OTA update. The last time I flashed a security update was through the kindness of someone who provided a TWRP-flashable zip of the June 2017 NPJ25.93-14.5 OTA file. I'm hoping the same will eventually be provided for the September OTA update.

Same case with me too but I have model XT1643 (Indian Version), Build number: NPJS25.93.14-10.
Also, while booting up I still get bootloader unlocked warning and in Google Play Store it is showing Device Certification as Uncertified.
When I type fastboot oem lock in cmd bootloader slot count, bootloader slot suffixes and one more bootloader line all are showing not found.
And yes, in Bootloader Unlock warning it is showing 'ID: Bad key'
Other than this my device is working fine, IMEI numbers and Fingerprint sensor is working perfectly.
I followed guide by tywinlannister7: https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Please can anyone tell how can I correct it.

Its the Elemental X kernel. If you don't have magisk installed, it trips the safetynet. I am using a XT1642, I experienced this about a year ago when I was first experimenting with custom firmware.

I downloaded the September 1, 2017 security patch update but would prefer to flash it via TWRP instead of letting the system install it. However I can't even determine where it was downloaded to and I can't access the root directory anymore. Is it safe to manually flash it on an unrooted system containing TWRP, ElementalX kernel and the logo.bin boot screen fix? I'm especially concerned about flashing it on a system that doesn't pass SafetyNet.

TCUofficial said:
Its the Elemental X kernel. If you don't have magisk installed, it trips the safetynet.
Click to expand...
Click to collapse
Thank you for that essential information. I won't consider it a problem since the phone doesn't have NFC, so no Android Pay support anyway. However, I need some additional info before proceeding with the update.
Do I need to get rid of the ElementalX kernel and restore the original?
Do I need to undo the logo.bin bootloader unlock screen fix?
Do I need to get rid of TWRP before allowing the system to install the security patch?
Thanks.

Sorry to be redundant but I am pressed for an answer. Thanks in advance.
RE: downloaded but installed Moto G4+ September 1, 2017 security patch NPJS25.93-14-10.
- Can the patch be safely installed after TWRP has been flashed on the phone?
- Can the patch be safely installed after an ElementalX kernel has been flashed on the phone?

mel2000 said:
Can the patch be safely installed after TWRP has been flashed on the phone?
- Can the patch be safely installed after an ElementalX kernel has been flashed on the phone?
Click to expand...
Click to collapse
Answer is NO to both your questions. You need a STOCK boot image and a stock recovery image to “patch” (by which I think you mean upgrade via an OTA) your phone.

mel2000 said:
Sorry to be redundant but I am pressed for an answer. Thanks in advance.
RE: downloaded but installed Moto G4+ September 1, 2017 security patch NPJS25.93-14-10.
- Can the patch be safely installed after TWRP has been flashed on the phone?
- Can the patch be safely installed after an ElementalX kernel has been flashed on the phone?
Click to expand...
Click to collapse
In addition to zeomal's reply, your device would also need an unmodified system partition (no root, readonly, so no TWRP modifications) else the OTA will fail too.
Furthermore, I don't think the update you've downloaded is suitable for US retail devices, and if flashed might stop you from receiving future OTA updates. If you want the stock NPJ25.93-14.5 full ROM to revert to: https://androidfilehost.com/?fid=673368273298984458
Or the NPJ25.93-14.7 stock ROM: https://androidfilehost.com/?fid=817906626617945295 Of course, either of these will reset your device to stock, erasing TWRP, root and ElementalX and most likely your data, so back up. However, they should permit you to take OTA updates. Flash only in fastboot.
If you've already installed NPJS25.93-14-10, then you won't likely get the OTA update if installed on US devices.
As for SafetyNet/ device uncertified, I recall that's likely due to an unlocked bootloader. Magisk has the ability to hide the bootloader unlocked status from Safetynet, hence why when you removed magisk, the Safetynet detection saw your unlocked bootloader and therefore trips Safetynet. An easy way to get Safetynet passed is to reflash ElementalX and magisk.

I want to thank both zeomal and echo92 for their prompt and clear responses. I will address related issues before I move on.
EDIT: Used OEM Flash.bat to reupdate to June 2017 NPJ25.93-14.5, then allowed NPJ25.93-14.7 to be installed from Moto. All went well with an unlocked bootloader. Didn't lose any apps.
- TWRP (gone)
- ElementalX (gone)
- Logo.bin fix (gone)
- SafetyNet (failed - due to unlocked bootloader)
Thanks again to all.

FRP Custom binary

Plase help i have grand prime G530H running stock kitkat then i upgraded to 5.0.2 lollipop russian firmware G530XXU2BPB2 to install custom rom, i installed twrp and custom rom with no problems, now running latest RR Rom, since 5.0.2 lollipop i didnt login to any google account, my question is if i login to google account using RR / Custom roms, is there a chance to block custom binary frp after reboot? I read some threads about custom frp, it is said that need to enable oem unlock but after upgrading to lollipop firmware there is no oem unlock on dev options.

test_only said:
Plase help i have grand prime G530H running stock kitkat then i upgraded to 5.0.2 lollipop russian firmware G530XXU2BPB2 to install custom rom, i installed twrp and custom rom with no problems, now running latest RR Rom, since 5.0.2 lollipop i didnt login to any google account, my question is if i login to google account using RR / Custom roms, is there a chance to block custom binary frp after reboot? I read some threads about custom frp, it is said that need to enable oem unlock but after upgrading to lollipop firmware there is no oem unlock on dev options.
Click to expand...
Click to collapse
FRP lock will not trigger if you login to your Google account. If the frp lock was triggered it would ask you to login to your Google account that you had on your stock ROM at the beginning anyway. So it's absolutely safe to login to Google account.
FRP lock only triggers if you tried to wipe data and cache from stock recovery while having a pin or password protected Device. The phone won't let you boot.

tasnim_tamim said:
FRP lock will not trigger if you login to your Google account. If the frp lock was triggered it would ask you to login to your Google account that you had on your stock ROM at the beginning anyway. So it's absolutely safe to login to Google account.
FRP lock only triggers if you tried to wipe data and cache from stock recovery while having a pin or password protected Device. The phone won't let you boot.
Click to expand...
Click to collapse
Thanks for the feedback, i mean custom binary blocked by frp red text on boot screen like bricked and refuses to boot, if installed root or flashed twrp on odin, but nevermind.. sorry for the noob question, my bad... i've found that custom binary error only present in protected or locked bootloader, so it need to enable oem unlock in dev options before installing root/twrp, other GP variants haa protected bootloader, while g530x variant has already unlocked bootloader so no oem unlock in dev options in settings, its safe to install root/twrp/custom.

test_only said:
Thanks for the feedback, i mean custom binary blocked by frp red text on boot screen like bricked and refuses to boot, if installed root or flashed twrp on odin, but nevermind.. sorry for the noob question, my bad... i've found that custom binary error only present in protected or locked bootloader, so it need to enable oem unlock in dev options before installing root/twrp, other GP variants haa protected bootloader, while g530x variant has already unlocked bootloader so no oem unlock in dev options in settings, its safe to install root/twrp/custom.
Click to expand...
Click to collapse
Looks like you found out your answer.
Just to let you know, it's not impossible to get a frp lock in G530H. Yes I know it's a common case in devices like G531H (Value Edition) or some carrier phones which has locked bootloaders. But I even heard some cases of frp lock in g530h due to some failure while flashing firmware from Odin. But it still should not effect you. As you were able to install custom ROM.. so your safe .

SM-G531M - FRP can't be disabled when logged into Google

Hi! I have flashed successfully a stock rom of Android 5.1.1 on this device (SM-G531M) using the latest Odin. I enabled the developer options and then OEM Unlock and USB Debugging. Flashed TWRP, everything great. Once TWRP was on my device I installed Magisk following the instructions and no problem. So having root access and TWRP on my phone, really happy that no problems came up on the way, I decide to log into my Google account to update and get some apps and here is when the problems appear. I checked that OEM Unlock is still on and reboot my phone to find that FRP is on and can't boot because of root (can't get in recovery either because TWRP is not the stock recovery), so I flash the device again with the stock rom and find out that I can't remove FRP lock to flash TWRP again. I try removing my google account and FRP is off, so I have to choose:
a) root access and TWRP recovery or
b) Google Account and get new apps or update the ones I have.
Nowhere I looked I could find any answer or anyone having this issue. Can someone tell me what am I doing wrong? I really have no idea why this happens, is a Google update that does this to everyone or what's going on?
Thanks in advance!