Mostly I want it to remove built-in apps and install apps to the sd card instead of internal. Fastboot getvar all (bootloader) slot-count: not found (bootloader) slot-suffixes: not found (bootloader) slot-suffixes: not found (bootloader) version: 0.5 (bootloader) version-bootloader: moto-msm8953-C0.87(.) (bootloader) product: potter (bootloader) board: potter (bootloader) secure: yes. Moto g4 plus xt1643 flash file need.!!!Solved If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. I've followed the guides but stupid Motorola is telling me that I can't unlock the bootloader so I'm blocked with. Sudo./fastboot flash recovery twrp-3.0.2-0-surnia.img (bootloader) has-slot:recovery: not found target reported max download size of 268435456 bytes sending 'recovery' (16152 KB). OKAY 0.509s writing 'recovery'.

• Bootloader Slot Count Not Found Moto G6
• Bootloader Slot Count Not Found Moto G3
• Bootloader Slot Count Not Found Moto G4 Plus

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.

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: –

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 all

Below are the bootloader environment variables defined when fastboot is running.

Response from fastboot oem hw

Bootloader Slot Count Not Found Moto G6

Response from fastboot oem partition

Bootloader Slot Count Not Found Moto G3

The following appears to be the partition map of the flash memory of the phone.

Bootloader Slot Count Not Found Moto G4 Plus

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.