Is it possible to have factory reset protection (frp) :with custom rom
Yes and no... If you flash a ROM without Gapps, then no FRP... with Gapps, maybe, depends on the ROM and Gapps package.
FRP is part of Google services in the device, not AOSP Android, so it depends, there is no clear yes or no answer.
Remember, any unlocked device is insecure... period. If you want the protection then stay 100% stock and locked, otherwise your device can be compromised.
Related
Hi guys, i've little problems with my P9 Lite (VNS-L21).
Firstly, it's FRP locked, i forgot mail and password so i can't add any other account to phone.
Secondly, phone is after factory reset, so i can't access it.
Thirdly, it have locked bootloader.
So i landed with FRP locked device without possibility to disable OEM lock to unlock bootloader to wipe /system. Someone on other forum said that is possible to flash clean stock rom here, but i dunno if it need unlocked bootloader.
I'll be grateful for any help
BTW, phone is on latest version of FW i think (B161) so any method of bypass isn't working.
Did you already tried to install stock ROM with dload method?
Yep, today B161 flashed with dload i think (UPDATE.APP and vol+/vol-) and FRP stayed
Can you boot into stock recovery? You can try to do a factory reset but I don't know if it will help, unfortunately I can't help you more :/
Factory reset only wipes /data so it does nothing :/ I need to flash CLEAN system partition, i heard that FRP is there but i dunno how to do is.
Second way to do it is downgrade, but i don't know how to do it with stock recovery :/
Hi,
Samsung Galaxy J5 (2016) - SM-J510FN/DS
I have flashed the TWRP recovery (3.0.2) and then installed SU Root.
As I wanted to turn on "System UI Tuner" but it did not work, I turned off the "developer options" in the settings.
After restart my mobile is now in "Custom binary blocked by frp" [secure fail:kernel].
How can I solve that?
Winf2005 said:
Hi,
Samsung Galaxy J5 (2016) - SM-J510FN/DS
I have flashed the TWRP recovery (3.0.2) and then installed SU Root.
As I wanted to turn on "System UI Tuner" but it did not work, I turned off the "developer options" in the settings.
After restart my mobile is now in "Custom binary blocked by frp" [secure fail:kernel].
How can I solve that?
Click to expand...
Click to collapse
Please reflash the stock firmware. Alternatively I have read that flashing only the boot.img file ahould do the trick without erasing data but I can't really confirm this.
FRP lock is caused by the bootloader detecting that a change was made. To disable security detection you need to keep enabled OEM Unlock in Dev Settings. It gets deactivated always when you turn off dev options.
BTW Samsung removed the System UI tuner from Marshmallow so your best bet for that is an XPOSED module or a custom ROM based on android AOSP, roms that don't have that disabled. Samsung is stupid
Thank you!
The stock firmware was ~1.4GB. After flashing root has gone, but almost all configuration was still there. Either it was not overwritten or the backup of Samsung did the job...
Winf2005 said:
Thank you!
The stock firmware was ~1.4GB. After flashing root has gone, but almost all configuration was still there. Either it was not overwritten or the backup of Samsung did the job...
Click to expand...
Click to collapse
Oh well it did factory reset, right? Also the backup feature is mostly Gogle's that's how I manage to keep most of my information even tho I'm trying new ROMs every month.
The cool thing was, that the installed APPs have all been there. So yes, google maybe did a big part, but I think this was no complete factory reset. I did it completely after the official advice of Samsung's homepage.
When activating the oem unlock you can install Twrp, kernel or custom rom without the activation of FRP security that is activated when you establish a security pattern in the device
When the binary is blocked by the FRP you must install the factory firmware, then enter the recovery and do a factory reset since the FRP prevents external access to the system and data as prevention
You will be prompted for the email and password of the previously used account
Thanks a lot
Amarius1 said:
Please reflash the stock firmware. Alternatively I have read that flashing only the boot.img file ahould do the trick without erasing data but I can't really confirm this.
FRP lock is caused by the bootloader detecting that a change was made. To disable security detection you need to keep enabled OEM Unlock in Dev Settings. It gets deactivated always when you turn off dev options.
BTW Samsung removed the System UI tuner from Marshmallow so your best bet for that is an XPOSED module or a custom ROM based on android AOSP, roms that don't have that disabled. Samsung is stupid
Click to expand...
Click to collapse
I have saved my data on Galaxy J5 2016. You advice to reflash only original "boot.img" is excelent cure.
I have reflashed my phone about 3 times and the last resulting in a fresh start without carrying over any data. My original rooting method was system mode which left me unable to accept OTA updates and was unstable. I am now using systemless magisksu and systemless Xposed with a untouched system partition. And at first I was able to play games like fire emblem heroes and pokemon go without trouble, then after a while I noticed that the same issues were happening again. Fire emblem gives a error code dispite me having hide magisk and automagisk enables for it, same for pokemon go. No matter what I do or how many times I reinstall I always get the errors.
I have read that you cannot hide root if you have a unlocked bootloader which I do. I have a stock ROM but a unlocked bootloader because I have a developer global installed. Do I need to modify my boot.img to not have the flag?
With original developer I think that you can relock the bootloader.... But you have to flash the original recovery too... I think I tried and it stuck so you might consider flashing via fastboot the original developer. I am not sure what happens to root
To lock bootloader you have to go to fastboot mode and type fastboot oem lock
jimger said:
With original developer I think that you can relock the bootloader.... But you have to flash the original recovery too... I think I tried and it stuck so you might consider flashing via fastboot the original developer. I am not sure what happens to root
To lock bootloader you have to go to fastboot mode and type fastboot oem lock
Click to expand...
Click to collapse
1. i have heard that relocking bootloader is actually more dangerous then unlocking and i have permabricked a 3s before and
2. no way will i unhack and relock just so that i can use some apps that to ignorant to leave rooted people alone. i will have to find away to make a custom kernal that removed the saftynet flag. someone was talking about that for another phone.
I don't think it is easy to brick redmi 3s.... Have you tried getting it into edl?
For me even when I had it with black screen I could "do" stuff to it. You can relock it if you use miflash and put developer and/or stable from en.miui.com. It will replace both your system and your recovery but also delete your media to your internal "sd".
I use an xposed module that responds well to safetynet but actually it doesn't really pass. Android pay can't be activated (to me) and I am not sure about pokemon or whatever because I don't use it. But safety net passes. I use an app from play store safetynet helper which in latest version included a basic integrity check. Well my device responds ok to cts profile but fails to basic integrity. Not sure why exactly but even thought I have magisk+ supersu in systemless mode I have touched the /system partition perhaps with adaway or I don't know for sure. I don't know how undroid checks for tampered system partition. I have miui-globe rom which is not official
jimger said:
I don't think it is easy to brick redmi 3s.... Have you tried getting it into edl?
For me even when I had it with black screen I could "do" stuff to it. You can relock it if you use miflash and put developer and/or stable from en.miui.com. It will replace both your system and your recovery but also delete your media to your internal "sd".
I use an xposed module that responds well to safetynet but actually it doesn't really pass. Android pay can't be activated (to me) and I am not sure about pokemon or whatever because I don't use it. But safety net passes. I use an app from play store safetynet helper which in latest version included a basic integrity check. Well my device responds ok to cts profile but fails to basic integrity. Not sure why exactly but even thought I have magisk+ supersu in systemless mode I have touched the /system partition perhaps with adaway or I don't know for sure. I don't know how undroid checks for tampered system partition. I have miui-globe rom which is not official
Click to expand...
Click to collapse
trust me i have tried everything to unbrick that phone it is IMPOSSIBLE no one can fix it, it just sits as spare parts in my storage now as i brought another one
https://forum.xda-developers.com/xiaomi-redmi-3s/help/bricked-redmi-3s-identify-test-force-t3438220
http://en.miui.com/thread-326730-1-1.html
http://en.miui.com/thread-373634-1-1.html
and even when my phone isn't rooted like after a fresh miflash after like 20 minutes the test fails but for that little time before then everything is ok.
Which test?
I saw that you ordered the deep flash cable and still not ok?
Have you tried the modified reboot to edl?
Also have you got x64 windows with test mode enabled?
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
jimger said:
Which test?
I saw that you ordered the deep flash cable and still not ok?
Have you tried the modified reboot to edl?
Also have you got x64 windows with test mode enabled?
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Click to expand...
Click to collapse
yes and yes the cable did not do anything
trust me i have tried everything anyone can ever imagine.
xdarkmario said:
yes and yes the cable did not do anything
trust me i have tried everything anyone can ever imagine.
Click to expand...
Click to collapse
Well don't know Then you are one of the very few... I can't tell anything else
If you reflash in fastboot it will be relocked. And there is no problem at all....
I am still having issues with this, i dont have the knowledge for compiling a kernel from source. no matter what i try i just cant bypass this stupid saftynet. if i flash the phone from scratch it will allow me to use saftynet protected app for a little bit but on reboot or something i cant use use it again.
As far as I know, developer ROMs don't pass SafetyNet, only the stable ROMs. And only with locked bootloader and without any modifications (root, xposed, magisk, etc.). For locking bootloader I recommend you to flash a fastboot ROM in fastboot mode and in MiFlash choose flash all and lock option, this way you will not brick your phone. But if it's not working and as I see you can unlock your bootloader, I recommend you xiaomi.eu ROMs. If all is true, the next release (both of beta and stable) will bypass SafetyNet (of course without modifications, but with this ROM don't lock your bootloader). But since it's based on china ROMs, beta releases are suspended until august. From the stable ROMs MIUI 8.2 doesn't pass SafetyNet yet, so you have to wait to MIUI 8.5.
22Dávid22 said:
As far as I know, developer ROMs don't pass SafetyNet, only the stable ROMs. And only with locked bootloader and without any modifications (root, xposed, magisk, etc.). For locking bootloader I recommend you to flash a fastboot ROM in fastboot mode and in MiFlash choose flash all and lock option, this way you will not brick your phone. But if it's not working and as I see you can unlock your bootloader, I recommend you xiaomi.eu ROMs. If all is true, the next release (both of beta and stable) will bypass SafetyNet (of course without modifications, but with this ROM don't lock your bootloader). But since it's based on china ROMs, beta releases are suspended until august. From the stable ROMs MIUI 8.2 doesn't pass SafetyNet yet, so you have to wait to MIUI 8.5.
Click to expand...
Click to collapse
i know how to relock my bootloader, i have done it before and relocked it as well as my xiaomi account is allowed to do so but for what i do i at least a rooted phone at the least. xposed it a heavy want but not mandatory like root is. i also need to be on the global weekly because the stable haven't added EXfat support yet.
Use magisk 13.3 =_=
jimger said:
I don't think it is easy to brick redmi 3s.... Have you tried getting it into edl?
For me even when I had it with black screen I could "do" stuff to it. You can relock it if you use miflash and put developer and/or stable from en.miui.com. It will replace both your system and your recovery but also delete your media to your internal "sd".
I use an xposed module that responds well to safetynet but actually it doesn't really pass. Android pay can't be activated (to me) and I am not sure about pokemon or whatever because I don't use it. But safety net passes. I use an app from play store safetynet helper which in latest version included a basic integrity check. Well my device responds ok to cts profile but fails to basic integrity. Not sure why exactly but even thought I have magisk+ supersu in systemless mode I have touched the /system partition perhaps with adaway or I don't know for sure. I don't know how undroid checks for tampered system partition. I have miui-globe rom which is not official
Click to expand...
Click to collapse
All the neccessary apps ( android pay & Pokemon ) use basic integrity
I was updating my system security patch from official moto but after restarting it started twrp and asked me if i want to flash that update file, after swiping it opened Twrp homepage(i was unable to restart from its reboot option but i went to the bootloader and started cell (Working correctly currently))
Two Options
1. I should lock the bootloader
2. Leave it as it is.
If option 1. lock my bootloader on stock Android Nougat 7.0 on Moto G4 plus Athene XT1643. As i have stock android and precious data so i only want to lock bootloader Without wiping my system Data (I can wipe if no other way is available).
For option 2. Keep it as it is.
Please suggest me what to do and how?
And tell me about official Oreo or Custom Oreo(best option)
Sorry for my bad English and errors(If any).
Thanks in advance
@cooldude1598 official update can not be flashed through TWRP, you need to have stock recovery and unmodified system/kernel/etc as well.
If you have played with stock ROM (flashed custom kernel/ rooting / installing and flashing other stuff ), it will fail through stock recovery too, for that you need to download appropriate stock ROM according to your current version of stock ROM, and it will erase everything (includes apps and app data, photos, videos and anything on internal storage)
you said, you have system data ?
What is that?
If it is photos, videos, or personal data then move it to external sd card or PC, apps and app-data can be backup through titanium backup, and also move it to safe place.
If not this, then tell us what system data?
Fro another question about LOCKING, it is not necessary to re-lock bootloader, you can go with unlocked bootloader, don't lock again, once you flash stock ROM through fastboot, you can update to any security updates without fail.
English is weak here too, hope you got it what i said.
Hello
I own a clean X Compact phone and I want to unlock bootloader and root it ( Magisk) before install anything on it. Actually it is on Android 8 v34.4 and I can't backup DRM with indicated tools (backup TA), so do I need to backup DRMs if I don't use Sony services except the camera to take pictures ?
If yes, which tool can do this on Android 8 ?
Thanks
Feedback on this.
After done the android 8 update to the last release from sept 2018, I was able to activate the OEM unlock and run fastboot unlock command.
Installation of TWRP is ok
Magisk cause Unsupported/Unknown image format with the v21 . Investigate to know why
Trying to install DRM-Fix-system_Mode.zip and the phone boot loop on fastboot mode.. I'm looking to a way to uninstall this DRM Fix or flash another file,if someone can help.
Finally install Lineage OS 16 after failed to install stock firmware with flashtool. Added OpenGApps and Magisk (v21) to disable non desired apps ( 95%)
It is better to backup the TA in case you would need to get back to the stock firmware or sell device in factory conditions (on stock ROM).
If you have already unlocked the bootloader without backing up the TA first then there is no way to bring the device back to the completely factory state.
mp107 said:
It is better to backup the TA in case you would need to get back to the stock firmware or sell device in factory conditions (on stock ROM).
If you have already unlocked the bootloader without backing up the TA first then there is no way to bring the device back to the completely factory state.
Click to expand...
Click to collapse
Thanks for your precisions.