On smartphones this can be a custom Android distribution or another mobile operating system. It can make advanced customizations possible, such as installing a custom firmware. They were new phones, never used.An unlocked Android bootloader, showing additional available optionsīootloader unlocking is the process of disabling the bootloader security that makes secure boot possible.
I bought 3 of these phones at only USD$120 each to test and they were suppose to ship “Unlocked” with Android 9 (Pie) but they arrived with Android 10 (Q) and had to update OTA connect to the internet briefly to get the OEM Unlock un-greyed out. What appears to be happening is something is blocking the G7+ from communicating back the unlock code to the Linux terminal (or an update from Motorola removed the information needed for the unlock key). fastboot oem from 's directions given directly above I can tell the Linux box is communicating to the G7+ because of what shows up on the “BOOTLOADER LOGS” picture (on phone), in red white we see “cmd: oem get_unlock_data” show up after executing the Linux terminal command above. Clearly there is code we can’t see interfering with the unlock keys being returned to the adb reboot fastboot devices I am a Linux noob but determined to get good using it so I can get off the Apple/Microsoft crack.ĮDIT: but to your point the Bootloader Log on the phone still shows “oem get_unlock_data” but… it returns the garbage above to the terminal. (bootloader) ‘get_unlock_datas’ is not a supported oem commandįrom what relayed to me, yes the “./” (reinforces to use the instruction “use from here”) tells the host device to look directly in the /Desktop/platform-tools portion of the directory (where I have Andriod SDK tools located) for the “fastboot” file.
Screenshot from 20-26-50 504×579 46.9 cd fastboot oem get_unlock_data
0 kommentar(er)
