Repository navigation
v2.5.2: the bootloader state from the bootloader, the new look and grey icon - #5
Merged
Merged
Conversation
The phone with a puzzle piece on dark teal, the same icon as on ifoknr.com and the other Fastboot Studio tools (webroot/logo.svg). For the next release.
…lue and slate fills, rounded cards and pill buttons; IFOKNR in violet
…tions), less room above the header and under the bottom navigation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A user's Xiaomi msm8937 (KernelSU, unlocked) showed "Bootloader: locked". Its old bootloader puts only
androidboot.verifiedbootstate=orangeon the kernel command line (novbmeta.device_state, noflash.locked), and the ROM setsro.boot.vbmeta.device_stateandro.boot.flash.lockedto "locked" for Play Integrity, so the Companion fell back to those properties.boot_statein lib/detect.sh now decides in this order:vbmeta.device_state, thenflash.locked, from bootconfig or the command line;With a root manager present the state is unlocked whatever those say (a locked bootloader does not start a modified boot image), the same rule as Fastboot Studio Mobile. When the properties say locked but the real state is unlocked,
spoofedis true, sofbs factsand the Phone page in Fastboot Studio get the right answer too.WebUI: an unknown state shows "?" instead of "locked", and the note under Boot and security explains that the ROM or a hiding module changed the boot properties.
Tests: three new cases on the fake phone (orange only on the command line with locked properties; no bootloader words with root; no root and no bootloader words). 234 / 234 under sh and dash, shellcheck clean, WebUI smoke test passes.
Version v2.5.2 in module.prop, update.json and fbs. Merge together with the release, so update.json never points at a zip that does not exist yet.