Register here: http://gg.gg/oj8lr
These are high level notes for myself (and people like me) who like to know what they’re actually doing when unlocking, rooting, and installing custom firmware on a phone. I’ve done this to varying degrees with my previous two phones, and always end up re-tracing painful footsteps to get things done. So I’m jotting down the bits that are important to me.
Enable the developer menu by repeatedly tapping the Build Number in About Phone. Use this to enable bootloader unlocking in the developer menu. This particular Easter egg might vary among Android versions.
One way or another, get Platform-Tools (package platform-tools) and cd into that directory. I installed CLI Tools and ran sdkmanager platform-tools, which seems to be some kind of Android SDK package manager, but I think it can also be downloaded directly as a tarball or zip file.
This does not work under Oreo. You can push the edited file into system successfully but when you reboot to Android OS, it seems like the file is being replace with original build.prop by bootloader or something. I can confirm none of this methods are working in Moto G5 Plus bootloader unlocked (unrooted). Moto G5s Plus getting new Android security update upto 1 February 2019. The size of the update is around 70.5 MB. This update also includes improved support for Android Messages. There were a few users facing problems using Android Messages on Moto G5s Plus. It seems this issue has been fixed in this update.
Also, download the latest Motorola USB drivers – these know how to talk ADB protocol with your phone, and I presume a chunk of this is vendor specific.
Boot the phone to the primary bootloader, ‘fastboot’ (volume down + power on), and connect it via USB.
Run fastboot oem get_unlock_data to get a hex key. Paste into an editor and join the hex strings into one long string. Discard the rest of the text. Therefore, this output data: –
will be copied and pasted into an editor, and then edited to look something like this: –Bootloader Slot Count Not Found Moto G5s Plus 64gb
This is the hex value you give to Motorola in their unlocking form, they will reply by giving you an unlock code. Curiously, this failed when I used the motorola.com site, yet succeeded when I used what appears to be Motorola’s service in the custhelp.com domain. I believe this is their international service, which looks to be outsourced to another company (is it Oracle?). Anyway, it seems legitimate.
With the unlock code that has been sent to you, run e.g. fastboot oem unlock LAEYQFFXQZSIAK4WI5CT, then run it again as prompted (a safeguard). The second time you run it, the phone will reboot with the unlocked bootloader.
Rooting the device should be a simple matter of copying the su binary to /bin or /usr/bin, but it’s not that simple, not least because actually getting a su binary is frustratingly difficult. There were few trustworthy sources that I could find, and more than a few very dodgy looking sources I found while looking. Bear in mind, this is a tool that has the power to own your device – you should be able to trust it well beyond reasonable doubt.
I am still looking. The whole Android ecosystem has that familiar feel of proprietary hell. Easter eggs, warez-like downloads, lack of concise information. On reflection, this is a sad state of affairs for something that was derived from GNU licenced Free Software. Shame on you Google.Response from fastboot getvar allBootloader Slot Count Not Found Moto G5s Plus ReviewBootloader Slot Count Not Found Moto G5s Plus Specs
Below are the bootloader environment variables defined when fastboot is running.Response from fastboot oem hwBootloader Slot Count Not Found Moto G5s Plus UnlockedResponse from fastboot oem partition
The following appears to be the partition map of the flash memory of the phone.
Looks like quite a lot of flash is given over to a/b partitioning, given that it’s not actually utilised so far as I can tell. A custom ROM would probably be more efficient.
Register here: http://gg.gg/oj8lr
https://diarynote.indered.space
These are high level notes for myself (and people like me) who like to know what they’re actually doing when unlocking, rooting, and installing custom firmware on a phone. I’ve done this to varying degrees with my previous two phones, and always end up re-tracing painful footsteps to get things done. So I’m jotting down the bits that are important to me.
Enable the developer menu by repeatedly tapping the Build Number in About Phone. Use this to enable bootloader unlocking in the developer menu. This particular Easter egg might vary among Android versions.
One way or another, get Platform-Tools (package platform-tools) and cd into that directory. I installed CLI Tools and ran sdkmanager platform-tools, which seems to be some kind of Android SDK package manager, but I think it can also be downloaded directly as a tarball or zip file.
This does not work under Oreo. You can push the edited file into system successfully but when you reboot to Android OS, it seems like the file is being replace with original build.prop by bootloader or something. I can confirm none of this methods are working in Moto G5 Plus bootloader unlocked (unrooted). Moto G5s Plus getting new Android security update upto 1 February 2019. The size of the update is around 70.5 MB. This update also includes improved support for Android Messages. There were a few users facing problems using Android Messages on Moto G5s Plus. It seems this issue has been fixed in this update.
Also, download the latest Motorola USB drivers – these know how to talk ADB protocol with your phone, and I presume a chunk of this is vendor specific.
Boot the phone to the primary bootloader, ‘fastboot’ (volume down + power on), and connect it via USB.
Run fastboot oem get_unlock_data to get a hex key. Paste into an editor and join the hex strings into one long string. Discard the rest of the text. Therefore, this output data: –
will be copied and pasted into an editor, and then edited to look something like this: –Bootloader Slot Count Not Found Moto G5s Plus 64gb
This is the hex value you give to Motorola in their unlocking form, they will reply by giving you an unlock code. Curiously, this failed when I used the motorola.com site, yet succeeded when I used what appears to be Motorola’s service in the custhelp.com domain. I believe this is their international service, which looks to be outsourced to another company (is it Oracle?). Anyway, it seems legitimate.
With the unlock code that has been sent to you, run e.g. fastboot oem unlock LAEYQFFXQZSIAK4WI5CT, then run it again as prompted (a safeguard). The second time you run it, the phone will reboot with the unlocked bootloader.
Rooting the device should be a simple matter of copying the su binary to /bin or /usr/bin, but it’s not that simple, not least because actually getting a su binary is frustratingly difficult. There were few trustworthy sources that I could find, and more than a few very dodgy looking sources I found while looking. Bear in mind, this is a tool that has the power to own your device – you should be able to trust it well beyond reasonable doubt.
I am still looking. The whole Android ecosystem has that familiar feel of proprietary hell. Easter eggs, warez-like downloads, lack of concise information. On reflection, this is a sad state of affairs for something that was derived from GNU licenced Free Software. Shame on you Google.Response from fastboot getvar allBootloader Slot Count Not Found Moto G5s Plus ReviewBootloader Slot Count Not Found Moto G5s Plus Specs
Below are the bootloader environment variables defined when fastboot is running.Response from fastboot oem hwBootloader Slot Count Not Found Moto G5s Plus UnlockedResponse from fastboot oem partition
The following appears to be the partition map of the flash memory of the phone.
Looks like quite a lot of flash is given over to a/b partitioning, given that it’s not actually utilised so far as I can tell. A custom ROM would probably be more efficient.
Register here: http://gg.gg/oj8lr
https://diarynote.indered.space
コメント