Possible explanation why nexus 5 didn't have the new device protection topic
So, just posted this a while ago at reddit, and some guy over there points out that maybe XDA is better place for this.
I'm just realized this afternoon by looking my android one device (sprout_b, indonesian version).
The Indian version (sprout) got updated to lollipop, and have the new device protection. Even if I flashed and used the said update on my device, I can't use the new device protection.
So I tried to compare both system files and boot.img, and found 1 partition missing on my device, FRP.
I investigated more about this, and it seems that both nexus 6 and 9 got this partition too (under the name PST).
And then, wild sudden clarity appears! FRP = Factory Reset Protection.
So, both my devices (nexus 5 and nexian journey 1 -android one- ) probably didn't receive this protection, because the partition needed for it isn't there.
For more info, here's the fstabs from both android one branch (sprout and sprout_b):
sprout:
sprout_b:
FRP is also mentioned in file_contexts file in boot.img:
I'm just realized this afternoon by looking my android one device (sprout_b, indonesian version).
The Indian version (sprout) got updated to lollipop, and have the new device protection. Even if I flashed and used the said update on my device, I can't use the new device protection.
So I tried to compare both system files and boot.img, and found 1 partition missing on my device, FRP.
I investigated more about this, and it seems that both nexus 6 and 9 got this partition too (under the name PST).
And then, wild sudden clarity appears! FRP = Factory Reset Protection.
So, both my devices (nexus 5 and nexian journey 1 -android one- ) probably didn't receive this protection, because the partition needed for it isn't there.
For more info, here's the fstabs from both android one branch (sprout and sprout_b):
sprout:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,encryptable=/dev/block/platform/mtk-msdc.0/by-name/metadata
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check
/dev/block/platform/mtk-msdc.0/by-name/oem /oem ext4 ro,context=u:object_r:oemfs:s0,nosuid,nodev wait
/devices/platform/mtk-msdc.1/mmc_host* auto vfat defaults voldmanaged=sdcard0:auto,noemulatedsd
/dev/block/platform/mtk-msdc.0/by-name/frp /persistent emmc defaults defaults
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/mtk-msdc.0/by-name/system /system ext4 ro wait
/dev/block/platform/mtk-msdc.0/by-name/userdata /data ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check,encryptable=/dev/block/platform/mtk-msdc.0/by-name/metadata
/dev/block/platform/mtk-msdc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,noauto_da_alloc,discard wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect1 /protect_f ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check
/dev/block/platform/mtk-msdc.0/by-name/protect2 /protect_s ext4 noatime,nosuid,nodev,noauto_da_alloc,commit=1,nodelalloc wait,check
/dev/block/platform/mtk-msdc.0/by-name/oem /oem ext4 ro,context=u:object_r:oemfs:s0,nosuid,nodev wait
/devices/platform/mtk-msdc.1/mmc_host* auto vfat defaults voldmanaged=sdcard1:auto
Code:
/dev/block/mmcblk0p18 u:object_r:frp_block_device:s0
xda-developers
- [Q] Nexus 4 endless Bootloop. Help !! topic
- [Q] Is it possible to use same icons as S6 Theme in Nova Launcher? topic
- [Q] Is it possible to have a file download on internal storage and external? topic
- Possible Fix for HRM / Google Fix Bug - Google Play Services Update topic
- Possible Root? topic
- [Q] External Mic possible? Any tips? topic
- [Q] Possible battery drain after root? topic
- [Q] Possible to make a ROM with these files? topic
- [Q] Is it possible to use only 4 cores on Exynos ? topic
- Possible to disable volume warning when headphone plugged in? topic
- [Q] Is it possible to take pictures on a Lollipop 5.1 Rom?? topic
- Best Full Protection Case? topic
- Anyway to get Viper4Android with write protection on? topic
- [Q] Samsung protection plus mobile elite topic
- Knox active protection boosting performance? topic
- "Didn't catch that" topic
- apps didn't sync topic
- apps didn't sync topic
- Asus, you had me at "Intel Atom", but lost me when you didn't bring it to US sooner topic
- Possible explanation why nexus 5 didn't have the new device protection topic
0 commentaires:
Enregistrer un commentaire