Hello,
a friend gave me hier "bricked" fon. I could get it booting again, system is up and running - but with any sdcard. Not the external and neither the internal one.
That means I cant put a SAPIMG.nph or anything else to the sdcard.
I cant download an apk or modify anything.
adb shell is working, but certainly su not.
adb push hboot_2010_signed.img /sdcard
certainly doesnt work either, there is no sdcard!
ok, I tried now different fastboot operations.
to come closer:
./fastboot flash recovery recovery-RA-sapphire-v1.7.0G-cyan.img
sending 'recovery' (4528 KB)... FAILED (remote: not allow)
... etc... all the normal stuff.. nothing wortks, I usualy get "Not allowed on a production phone"
What to do now, I have no clue anymore!
here my data:
./fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x880705C0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 64
INFOTAG:hwid 0x1
INFOTAG:skuid 0x1E300
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x2
INFODevice CID is not super CID
INFOCID is VODAP102
INFOsetting.cid::VODAP102
INFOserial number: HT93YKF06262
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =346
INFOactive commandline: board_sapphire.disable_uart3=1 board_sap
INFOphire.usb_h2w_sw=1 board_sapphire.disable_sdcard=1 smisize=6
INFO4 androidboot.baseband=2.22.19.26I androidboot.cid=VODAP102
INFO androidboot.carrier=VODA-Germany androidboot.keycaps=qwerty
INFO androidboot.mode=normal androidboot.serialno=HT93YKF06262 a
INFOndroidboot.bootloader=1.33.0007 no_console_suspend=1 console
INFO=null
INFOPARTITIOM_NUM_MAX =6 Valid partition num=6
Do you see? There is the kernel option board_sapphire.disable_sdcard=1 set !!! But I cant disable it with a fastboot -c option.
./fastboot getvar version-main
version-main: 1.89.162.1
./fastboot getvar cid
cid: VODAP102C??a
#########
Any help is appreciated, thanks!
Code:
fastboot oem enableqxdm 0
Regarding root... follow my guide found in my signature..
./fastboot oem enableqxdm 0
... INFO[ERR] Command error !!!
OKAY
./fastboot devices
HT93YKF06262 fastboot
[[email protected] HTC]# ./fastboot flash recovery recovery-RA-sapphire-v1.7.0G-cyan.img
sending 'recovery' (4528 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
this seemed to get me a little further:
./fastboot oem rebootRUU
... OKAY
[[email protected] HTC]# ./fastboot -c "board_sapphire.disable_sdcard=0 board_sapphire.disable_uart3=0" reboot
rebooting...
YEAH!"
but then..... still no sdcard when the OS was up :-(
any ideas?
Type
Code:
fastboot oem h
and post here the result.
Root and recovery = follow my guide found in my signature...
Just replace all "/sdcard" paths with "/data/local/tmp"
Note: Not all Moto G 2015 are unlockable, though the procedure for all of them is the same.
Also it would be great to keep this page open while following through on your PC instead of your phone as you'll be rebooting and resetting your phone by following this procedure.
Click to expand...
Click to collapse
Prerequisites:
ADB (Android Debugging Bridge) tools for your OS (Windows/Linux/Mac)
Windows: https://dl.google.com/android/repository/sdk-tools-windows-3859397.zip
Mac: https://dl.google.com/android/repository/sdk-tools-darwin-3859397.zip
Linux: https://dl.google.com/android/repository/sdk-tools-linux-3859397.zip
Custom Recovery Image (TWRP or some other that you prefer):
https://forum.xda-developers.com/devdb/project/?id=11051#downloads
(Official TWRP web hosted version)https://twrp.me/motorola/motorolamotog2015.html
https://dl.twrp.me/osprey
https://eu.dl.twrp.me/osprey
USB Cable to Connect the phone to the computer
The Phone: Moto G 2015 (preferably Fully Charged)
The device drivers (for Windows and Mac): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
A good and active Internet Connection
An active Email address and client to quickly view it.
In this tutorial I'll be referring to Linux terminal, Mac Terminal & Windows Command prompt/Powershell simply as terminal.
Click to expand...
Click to collapse
Installing adb and fastboot
Google hosts zips including only adb and fastboot. You can set these up for use with the instructions below.
On Windows
Download the Windows zip (Full version: https://dl.google.com/android/repository/sdk-tools-windows-3859397.zip)(barebones version: https://dl.google.com/android/repository/platform-tools-latest-windows.zip) from Google.
Extract it somewhere - for example, %USERPROFILE%\adb-fastboot
• On Windows 7/8:
1. From the desktop, right-click My Computer and select Properties
2. In the System Properties window, click on the Advanced tab
3. In the Advanced section, click the Environment Variables button
4. In the Environment Variables window, highlight the Path variable in the Systems Variable section and click the Edit button
5. Append ";%USERPROFILE%\adb-fastboot\platform-tools" to the end of the existing Path definition (the semi-colon separates each path entry)
• On Windows 10:
1. Open the Start menu, and type “advanced system settings”
2. Select “View advanced system settings”
3. Click on the Advanced tab
4. Open the “Environment Variables” window
5. Select the Path variable under “System Variables” and click the “Edit” button
6. Click the “Edit Text” button
7. Append ";%USERPROFILE%\adb-fastboot\platform-tools" to the end of the existing Path definition (the semi-colon separates each path entry)
• Install the device drivers linked in prerequisites (or from Motorolla support site), and reboot.
On macOS
Download the macOS zip (full version: https://dl.google.com/android/repository/sdk-tools-darwin-3859397.zip)(Barebones version: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip) from Google.
Extract it somewhere - for example, ~/adb-fastboot.
Add the following to ~/.bash_profile:
Code:
if [ -d "$HOME/adb-fastboot/platform-tools" ] ; then
export PATH="$HOME/adb-fastboot/platform-tools:$PATH"
fi
Log out and back in.
On Linux
Download the Linux zip (Full version: https://dl.google.com/android/repository/sdk-tools-linux-3859397.zip)(Barebones version: https://dl.google.com/android/repository/platform-tools-latest-linux.zip) from Google.
Extract it somewhere - for example, ~/adb-fastboot.
Add the following to ~/.profile:
Code:
if [ -d "$HOME/adb-fastboot/platform-tools" ] ; then
export PATH="$HOME/adb-fastboot/platform-tools:$PATH"
fi
Log out and back in.
You may also need to set up udev rules: see this repository (https://github.com/M0Rf30/android-udev-rules#installation) for more info.
Setting up adb
To use adb with your device, you’ll need to enable developer options and USB debugging:
1. Open Settings, and select “About”.
2. Tap on “Build number” seven times.
3. Go back, and select “Developer options”.
4. Scroll down, and check the “Android debugging” entry under “Debugging”.
5. Plug your device into your computer.
6. On the computer, open up a terminal/command prompt and type adb devices.
7. A dialog should show on your device, asking you to allow usb debugging. Check “always allow”, and choose “OK”.
Congratulations! adb is now ready to use with your device.
Unlocking the bootloader
Note: The steps below only need to be run once per device.
Code:
Warning: Unlocking the bootloader will erase all data on your device! Before
proceeding, ensure the data you would like to retain is backed up to your PC and/or
your Google account, or equivalent.
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. Incase you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone.
3. Get the current status of your bootloader:
Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
• Hold Volume Down & Power simultaneously. On the next screen use Volume
Down and Volume Up to scroll and Power to select.
Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>", try running
Code:
fastboot
as root/Administrator.
From the same terminal, type the following command to get the bootloader status:
Code:
fastboot oem device-info
4. Follow the instructions at Motorola Support (https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a) to unlock your bootloader, you will need to register at this site with a working/active email to recieve the OEM unlock code.
Note: If your device is not supported by the Motorola Bootloader Unlock
website, you will need to use an alternative bootloader unlock method like
SunShine (http://theroot.ninja/index.html).
Installing a custom recovery using fastboot
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. Incase you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone. This needs to be done again due to resetting of your phone.
3. Download recovery - visit twrp.me to obtain the latest version of Team Win
Recovery Project for your device. Moto G 2015 does have an official TWRP recovery that you can find here: https://twrp.me/motorola/motorolamotog2015.html
4. Connect your device to your PC via USB.
5. Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
• Hold Volume Down & Power simultaneously. On the next screen use Volume
Down and Volume Up to scroll and Power to select.
Click to expand...
Click to collapse
6. Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>" , try running
Code:
fastboot
as root/Administrator.
7. Flash recovery onto your device:
Code:
fastboot flash recovery your_recovery_img.img
This command assumes the recovery image is present in your current working directory (Check using DIR on command prompt or ls command on terminal)
If it isn't you can change your current directory to the directory containing the recovery image or copy/move the recovery image to your current working directory.
8. Now reboot into recovery to verify the installation:
• Hold Volume Down & Power simultaneously. On the next screen use Volume
Down to scroll to recovery and then use Power to select.
That's all folks. You may now root your phone, or even flash a custom ROM. I suggest getting openGapps for the custom ROM if you wish to use Google play services on the custom ROM.
Popular adb commands
Code:
adb shell
Launches a shell on the device accessed through the terminal on your computer.
Code:
adb push <local> <remote>
Pushes the file <local> to <remote>
Code:
adb pull <remote> [<local>]
Pulls the file <remote> to <local>. If <local> isn’t specified, it will pull to the current folder.
Code:
adb logcat
Allows you to view the device log in real-time. You can use adb logcat -b radio to view radio logs, and adb logcat -C to view logs in colour
Code:
adb install <file>
Installs the given .apk file to your device
<local> refers to location on your computer (like c:\\Users\%USERPROFILE%\adb-fastboot on windows or ~/adb-fastboot on unix based OS), while <remote> refers to location on your android device (like "/sdcard/", without quotes)
Thanks to @acejavelin for helping members troubleshoot problems that they faced
Nice tutorial... I have nothing to add, this is pretty comprehensive. Well done!
I have unlocked the device with this guide, but unable to flash recovery. I downloaded the file twrp-osprey-3.1.0-r1 & copied it in adb-fastboot folder. Now when I try to flash the recovery it says "no such file or directory" Does anyone know the fix? I tried extracting the file but winzip gives an error!
Dhaval1703 said:
I have unlocked the device with this guide, but unable to flash recovery. I downloaded the file twrp-osprey-3.1.0-r1 & copied it in adb-fastboot folder. Now when I try to flash the recovery it says "no such file or directory" Does anyone know the fix? I tried extracting the file but winzip gives an error!
Click to expand...
Click to collapse
This is a command line error in Windows, you are not issuing the command properly. Assuming you are using the current file from here: https://dl.twrp.me/osprey/ and have placed the file in your adb-fastboot folder, the command is:
Code:
fastboot flash recovery twrp-3.1.1-0-osprey.img
If edited name of file will need to put for example recovery.img. img not just .img found this out the hard way
Sent from my Robin using Tapatalk
toxicmender said:
Note: Not all Moto G 2015 are unlockable, though the procedure for all of them is the same.
Unlocking the bootloader
Note: The steps below only need to be run once per device.
Code:
Warning: Unlocking the bootloader will erase all data on your device! Before
proceeding, ensure the data you would like to retain is backed up to your PC and/or
your Google account, or equivalent.
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. Incase you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone.
3. Get the current status of your bootloader:
Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
• Hold Volume Down & Power simultaneously. On the next screen use Volume
Down and Volume Up to scroll and Power to select.
Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>", try running
Code:
fastboot
as root/Administrator.
From the same terminal, type the following command to get the bootloader status:
Code:
fastboot oem device-info
4. Follow the instructions at Motorola Support (https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a) to unlock your bootloader, you will need to register at this site with a working/active email to recieve the OEM unlock code.
Note: If your device is not supported by the Motorola Bootloader Unlock
website, you will need to use an alternative bootloader unlock method like
SunShine (http://theroot.ninja/index.html).
Click to expand...
Click to collapse
Hey...
I'm not able to do so. There is no chance to get to developer mode or usb debugging mode. what can i do now?
please help. thx
wavebooster said:
Hey...
I'm not able to do so. There is no chance to get to developer mode or usb debugging mode. what can i do now?
please help. thx
Click to expand...
Click to collapse
Not able to do what?
USB Debugging Mode is not needed, but you need to have OEM Unlocking enabled... If that isn't possible, try Sunshine but it isn't free.
acejavelin said:
Not able to do what?
USB Debugging Mode is not needed, but you need to have OEM Unlocking enabled... If that isn't possible, try Sunshine but it isn't free.
Click to expand...
Click to collapse
OK, I checked to enable the OEM Unlock but with the step 4 on motorola website I have some problems. There is no code when I follow the instructions. According to the list I should be able to unlock my phone.
Here the Code when I tried to get the code to enter it on the moto website:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8916-80.CB
(bootloader) product: osprey
(bootloader) board: osprey
(bootloader) secure: yes
(bootloader) hwrev: 0x82B0
(bootloader) radio: 0x4
(bootloader) emmc: 8GB Samsung REV=07 PRV=01 TYPE=57
(bootloader) ram: 1024MB Samsung S8 SDRAM DIE=4Gb
(bootloader) cpu: MSM8916
(bootloader) serialno: ZY22228MXD
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: 1856E20A00000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: "i deleted this"
(bootloader) meid:
(bootloader) date: 07-11-2015
(bootloader) sku: XT1541
(bootloader) battid: SNN5959A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Feb 25 9:46:27 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/osprey_reteu/osprey_umts:
(bootloader) ro.build.fingerprint[1]: 6.0.1/MPI24.107-55/33:user/release
(bootloader) ro.build.fingerprint[2]: -keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.61.55.osprey_rete
(bootloader) ro.build.version.full[1]: u.reteu.en.EU
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.BR.1.1.3_RB1.
(bootloader) ro.build.version.qcom[1]: 05.01.00.032.015
(bootloader) version-baseband[0]: M8916_2020632.44.03.21.54R OSPREY_EMEA
(bootloader) version-baseband[1]: _CUST
but when I try to "fastboot oem get_unlock_data" then I get following:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.388s
I tried it with different usb cables, on different PC's, with android sdk and minimal adb...
no chance..
Do you have any ideas?
wavebooster said:
but when I try to "fastboot oem get_unlock_data" then I get following:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.388s
[/SIZE][/SIZE]
I tried it with different usb cables, on different PC's, with android sdk and minimal adb...
no chance..
Do you have any ideas?
Click to expand...
Click to collapse
The bootloader "slot" thing is nothing, in newer devices that shipped with Nougat they use an A-B software slot configuration, the message in red just means that fastboot didn't detect any software slots which is normal with this device but has no effect on functionality.
Try a factory reset then see if you can get the unlock token. Otherwise I would suggest trying to find an older version of fastboot, or even Moto's mFastboot and see if that gives different results.
Otherwise, Moto is not very forthcoming for help unlocking and there is nothing we can do if we can't get the unlock token, although they do have an official forum and discussions related to unlocking are in the Development area, but since this is not a "developer" edition device, they often will not help very much.
What OS are you using? Another thing is many people find that using Linux works better than using Windows, since most Linux distros have fastboot and ADB bundled and it is a little older version.
Hello, thank you very much for your work, just one question, since I'm setting up all of this for a friend and can't try it up for myself.
In the sdk-tools-windows-3859397.zip there's a folder called 'tools' is it the way it should be? Thank you again for your consideration
--------------update
Since no one answered me yet I'm going to add some info:
I did try it and I can't seem to get it to work, where should I open the cmd? And should I actually digit: "adb drivers"? Because the console output is "adb command not recognised".
Thank you again ☺
Alberto.Laurella said:
Hello, thank you very much for your work, just one question, since I'm setting up all of this for a friend and can't try it up for myself.
In the sdk-tools-windows-3859397.zip there's a folder called 'tools' is it the way it should be? Thank you again for your consideration
--------------update
Since no one answered me yet I'm going to add some info:
I did try it and I can't seem to get it to work, where should I open the cmd? And should I actually digit: "adb drivers"? Because the console output is "adb command not recognised".
Thank you again
Click to expand...
Click to collapse
There are instructions for adding the directory of tools to windows (Check Installing adb tools -> on windows) but if you don't want to do something like that, then you could open the command prompt/powershell/terminal in the directory containing all the tools like "adb.exe" or "adb" (on *nix devices) and run all the commands with "./" prefix at the beginning of each adb command like "./adb devices" on *nix devices or if you're using powershell on windows 10, the prefix is not required if you're using cmd.exe (command prompt on windows 7 or older) . In case you wish to flash a file you can either copy paste it into the folder containing "adb.exe" or just "adb" (on *nix devices) or type the full path to the file you wish to use.
hola como les va les comento mi problema
yo intento cargarle el sistema pero como el bootloader no esta desbloqueado no me deja eh intentado desbloquearlo y tampoco me deja no tengo la depuracion usb abilitada ni la opcion de oem ay alguna posibilidad de que se pueda desbloquear el bootloader para reinstalarle el sistema operativo el sistema me lo carga pero antes de cargar con el sistema se reinicia eh intentado de todo ya muchas grasias colegas les habla walter desde argentina
walter19941994 said:
hola como les va les comento mi problema
yo intento cargarle el sistema pero como el bootloader no esta desbloqueado no me deja eh intentado desbloquearlo y tampoco me deja no tengo la depuracion usb abilitada ni la opcion de oem ay alguna posibilidad de que se pueda desbloquear el bootloader para reinstalarle el sistema operativo el sistema me lo carga pero antes de cargar con el sistema se reinicia eh intentado de todo ya muchas grasias colegas les habla walter desde argentina
Click to expand...
Click to collapse
I don't understand Spanish (i think you typed spanish), if you could try to explain it in English that would be great or type simple spanish which translates easily through services like translate.google.com
walter19941994 said:
hola como les va les comento mi problema
yo intento cargarle el sistema pero como el bootloader no esta desbloqueado no me deja eh intentado desbloquearlo y tampoco me deja no tengo la depuracion usb abilitada ni la opcion de oem ay alguna posibilidad de que se pueda desbloquear el bootloader para reinstalarle el sistema operativo el sistema me lo carga pero antes de cargar con el sistema se reinicia eh intentado de todo ya muchas grasias colegas les habla walter desde argentina
Click to expand...
Click to collapse
Hola Walter, comentanos un poco mejor tu problema. El teléfono no inicia? Cómo llegaste a esa situación?
Need help
toxicmender said:
Prerequisites:
ADB (Android Debugging Bridge) tools for your OS (Windows/Linux/Mac)
Windows: https://dl.google.com/android/repository/sdk-tools-windows-3859397.zip
Mac: https://dl.google.com/android/repository/sdk-tools-darwin-3859397.zip
Linux: https://dl.google.com/android/repository/sdk-tools-linux-3859397.zip
Custom Recovery Image (TWRP or some other that you prefer):
https://forum.xda-developers.com/devdb/project/?id=11051#downloads
(Official TWRP web hosted version)https://twrp.me/motorola/motorolamotog2015.html
https://dl.twrp.me/osprey
https://eu.dl.twrp.me/osprey
USB Cable to Connect the phone to the computer
The Phone: Moto G 2015 (preferably Fully Charged)
The device drivers (for Windows and Mac): https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
A good and active Internet Connection
An active Email address and client to quickly view it.
Installing adb and fastboot
Google hosts zips including only adb and fastboot. You can set these up for use with the instructions below.
On Windows
Download the Windows zip (Full version: https://dl.google.com/android/repository/sdk-tools-windows-3859397.zip)(barebones version: https://dl.google.com/android/repository/platform-tools-latest-windows.zip) from Google.
Extract it somewhere - for example, %USERPROFILE%\adb-fastboot
• On Windows 7/8:
1. From the desktop, right-click My Computer and select Properties
2. In the System Properties window, click on the Advanced tab
3. In the Advanced section, click the Environment Variables button
4. In the Environment Variables window, highlight the Path variable in the Systems Variable section and click the Edit button
5. Append ";%USERPROFILE%\adb-fastboot\platform-tools" to the end of the existing Path definition (the semi-colon separates each path entry)
• On Windows 10:
1. Open the Start menu, and type “advanced system settings”
2. Select “View advanced system settings”
3. Click on the Advanced tab
4. Open the “Environment Variables” window
5. Select the Path variable under “System Variables” and click the “Edit” button
6. Click the “Edit Text” button
7. Append ";%USERPROFILE%\adb-fastboot\platform-tools" to the end of the existing Path definition (the semi-colon separates each path entry)
• Install the device drivers linked in prerequisites (or from Motorolla support site), and reboot.
On macOS
Download the macOS zip (full version: https://dl.google.com/android/repository/sdk-tools-darwin-3859397.zip)(Barebones version: https://dl.google.com/android/repository/platform-tools-latest-darwin.zip) from Google.
Extract it somewhere - for example, ~/adb-fastboot.
Add the following to ~/.bash_profile:
Code:
if [ -d "$HOME/adb-fastboot/platform-tools" ] ; then
export PATH="$HOME/adb-fastboot/platform-tools:$PATH"
fi
Log out and back in.
On Linux
Download the Linux zip (Full version: https://dl.google.com/android/repository/sdk-tools-linux-3859397.zip)(Barebones version: https://dl.google.com/android/repository/platform-tools-latest-linux.zip) from Google.
Extract it somewhere - for example, ~/adb-fastboot.
Add the following to ~/.profile:
Code:
if [ -d "$HOME/adb-fastboot/platform-tools" ] ; then
export PATH="$HOME/adb-fastboot/platform-tools:$PATH"
fi
Log out and back in.
You may also need to set up udev rules: see this repository (https://github.com/M0Rf30/android-udev-rules#installation) for more info.
Setting up adb
To use adb with your device, you’ll need to enable developer options and USB debugging:
1. Open Settings, and select “About”.
2. Tap on “Build number” seven times.
3. Go back, and select “Developer options”.
4. Scroll down, and check the “Android debugging” entry under “Debugging”.
5. Plug your device into your computer.
6. On the computer, open up a terminal/command prompt and type adb devices.
7. A dialog should show on your device, asking you to allow usb debugging. Check “always allow”, and choose “OK”.
Congratulations! adb is now ready to use with your device.
Unlocking the bootloader
Note: The steps below only need to be run once per device.
Code:
Warning: Unlocking the bootloader will erase all data on your device! Before
proceeding, ensure the data you would like to retain is backed up to your PC and/or
your Google account, or equivalent.
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. Incase you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone.
3. Get the current status of your bootloader:
Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
You can also boot into fastboot mode via a key combination:
• Hold Volume Down & Power simultaneously. On the next screen use Volume
Down and Volume Up to scroll and Power to select.
Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>", try running
Code:
fastboot
as root/Administrator.
From the same terminal, type the following command to get the bootloader status:
Code:
fastboot oem device-info
4. Follow the instructions at Motorola Support (https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a) to unlock your bootloader, you will need to register at this site with a working/active email to recieve the OEM unlock code.
Note: If your device is not supported by the Motorola Bootloader Unlock
website, you will need to use an alternative bootloader unlock method like
SunShine (http://theroot.ninja/index.html).
Installing a custom recovery using fastboot
1. Make sure your computer has working fastboot and adb.
2. Enable USB debugging & OEM unlocking on your device under Settings->Developer Options. Incase you don't see Developer Options, then you need to unlock it by tapping Build Number 7 times in Settings->About Phone. This needs to be done again due to resetting of your phone.
3. Download recovery - visit twrp.me to obtain the latest version of Team Win
Recovery Project for your device. Moto G 2015 does have an official TWRP recovery that you can find here: https://twrp.me/motorola/motorolamotog2015.html
4. Connect your device to your PC via USB.
5. Open a terminal on the PC and boot the device to fastboot mode by typing:
Code:
adb reboot bootloader
6. Once the device is in fastboot mode, verify your PC finds it by typing:
Code:
fastboot devices
If you see "no permissions fastboot" or "<waiting for device>" , try running
Code:
fastboot
as root/Administrator.
7. Flash recovery onto your device:
Code:
fastboot flash recovery your_recovery_img.img
This command assumes the recovery image is present in your current working directory (Check using DIR on command prompt or ls command on terminal)
If it isn't you can change your current directory to the directory containing the recovery image or copy/move the recovery image to your current working directory.
8. Now reboot into recovery to verify the installation:
• Hold Volume Down & Power simultaneously. On the next screen use Volume
Down to scroll to recovery and then use Power to select.
That's all folks. You may now root your phone, or even flash a custom ROM. I suggest getting openGapps for the custom ROM if you wish to use Google play services on the custom ROM.
Popular adb commands
Code:
adb shell
Launches a shell on the device accessed through the terminal on your computer.
Code:
adb push <local> <remote>
Pushes the file <local> to <remote>
Code:
adb pull <remote> [<local>]
Pulls the file <remote> to <local>. If <local> isn’t specified, it will pull to the current folder.
Code:
adb logcat
Allows you to view the device log in real-time. You can use adb logcat -b radio to view radio logs, and adb logcat -C to view logs in colour
Code:
adb install <file>
Installs the given .apk file to your device
<local> refers to location on your computer (like c:\\Users\%USERPROFILE%\adb-fastboot on windows or ~/adb-fastboot on unix based OS), while <remote> refers to location on your android device (like "/sdcard/", without quotes)
Thanks to @acejavelin for helping members troubleshoot problems that they faced
Click to expand...
Click to collapse
I want to unlock the bootloader of Moto g3. But I'm facing some problem
1, OEM unlocking not enabled
2, device in software brick condition
3, can't enter into recovery option ( when it enter into recovery mode it will show no command message for 1/2 sec and turn display off and turn on,same loop again)
https://drive.google.com/file/d/1lPBuEij-Wl1COHMH_5FT0_0VFS6Mfbuq/view?usp=drivesdk
Is there any way to fix this problem???? ?
akhiltj114 said:
I want to unlock the bootloader of Moto g3. But I'm facing some problem
1, OEM unlocking not enabled
2, device in software brick condition
3, can't enter into recovery option ( when it enter into recovery mode it will show no command message for 1/2 sec and turn display off and turn on,same loop again)
https://drive.google.com/file/d/1lPBuEij-Wl1COHMH_5FT0_0VFS6Mfbuq/view?usp=drivesdk
Is there any way to fix this problem???? ?
Click to expand...
Click to collapse
Assuming you tried "fastboot erase userdata"?
Otherwise probably not much you can do... Unlocking the bootloader in this condition is impossible, but it might not matter because it sounds like your eMMC (the internal storage chip) may have failed. It is not replaceable except by mainboard swap.
Bootloader locked and unable to access recovery, not much anyone except Moto can do to help that situation.
Is there any way to check eMMC status (using fastboot command )
akhiltj114 said:
Is there any way to check eMMC status (using fastboot command )
Click to expand...
Click to collapse
No... Fastboot doesn't have anything that in-depth in it. Sorry.
Anyone got an idea why I can't unlock the bootloader with the on the Moto site ?
Moto G3
(bootloader) 3A55840906041441#5A593232323236
(bootloader) 4A4E56004D6F746F4733000000#F708
(bootloader) F4ADF4333F57809EAC2EF3FB1C464B2
(bootloader) AD819#CAD5D20A00000000000000000
(bootloader) 0000000
D:\Incomming\platform-tools-latest-windows\platform-tools>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-msm8916-80.CF
(bootloader) product: osprey
(bootloader) board: osprey
(bootloader) secure: yes
(bootloader) hwrev: 0x82B0
(bootloader) radio: 0x4
(bootloader) emmc: 8GB SKHynix REV=07 PRV=08 TYPE=57
(bootloader) ram: 1024MB Hynix S8 SDRAM DIE=8Gb
(bootloader) cpu: MSM8916
(bootloader) serialno: ZY22226JNV
(bootloader) cid: 0x0007
(bootloader) channelid: 0x41
(bootloader) uid: CAD5D20A00000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxxxxxxx
(bootloader) meid:
(bootloader) date: 07-11-2015
(bootloader) sku: XT1541
(bootloader) battid: SNN5959A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed May 23 20:25:40 UTC 2018"
(bootloader) ro.build.fingerprint[0]: motorola/osprey_reteu_2gb/osprey_u
(bootloader) ro.build.fingerprint[1]: 2:6.0.1/MPIS24.107-55-2-17/19:user
(bootloader) ro.build.fingerprint[2]: /release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.226.17.osprey_ret
(bootloader) ro.build.version.full[1]: eu_2gb.reteu.en.EU
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.BR.1.1.3_RB1.
(bootloader) ro.build.version.qcom[1]: 05.01.00.032.015
(bootloader) version-baseband[0]: M8916_2020632.44.03.21.54.01R OSPREY_E
(bootloader) version-baseband[1]: MEA_CUST
(bootloader) kernel.version[0]: Linux version 3.10.49-g2e9678a (hudsoncm
(bootloader) kernel.version[1]: @ilclbld83) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Thu Apr 6 10:50:21 CDT 2017
(bootloader) sbl1.git: git=MBM-NG-V80.CF-0-g7abea31
(bootloader) rpm.git: git=MBM-NG-V80.CF-0-g932f716
(bootloader) tz.git: git=MBM-NG-V80.CF-0-gf07dc55
(bootloader) hyp.git: git=MBM-NG-V80.CF-0-gf07dc55
(bootloader) aboot.git: git=MBM-NG-V80.CF-0-g8bfe213
(bootloader) partition-type:modem: raw
(bootloader) partition-type:sbl1: raw
(bootloader) partition-typeSmiley Very HappyDR: raw
(bootloader) partition-type:aboot: raw
(bootloader) partition-type:rpm: raw
(bootloader) partition-type:tz: raw
(bootloader) partition-type:hyp: raw
(bootloader) partition-type:utags: raw
(bootloader) partition-type:misc: raw
(bootloader) partition-typeSmiley TongueadA: raw
(bootloader) partition-type:abootBackup: raw
(bootloader) partition-type:rpmBackup: raw
(bootloader) partition-type:tzBackup: raw
(bootloader) partition-type:hypBackup: raw
(bootloader) partition-type:utagsBackup: raw
(bootloader) partition-type:logs: raw
(bootloader) partition-type:frp: raw
(bootloader) partition-typeSmiley TongueadB: raw
(bootloader) partition-type:modemst1: raw
(bootloader) partition-type:modemst2: raw
(bootloader) partition-type:hob: raw
(bootloader) partition-type:dhob: raw
(bootloader) partition-type:fsg: raw
(bootloader) partition-type:fsc: raw
(bootloader) partition-type:cid: raw
(bootloader) partition-type:metadata: raw
(bootloader) partition-type:logo: raw
(bootloader) partition-type:clogo: raw
(bootloader) partition-typeSmiley Tongueersist: raw
(bootloader) partition-type:kpan: raw
(bootloader) partition-type:boot: raw
(bootloader) partition-type:recovery: raw
(bootloader) partition-type:ssd: raw
(bootloader) partition-typeSmiley TongueadC: raw
(bootloader) partition-type:sp: raw
(bootloader) partition-type:keystore: raw
(bootloader) partition-typeSmiley Surprisedem: raw
(bootloader) partition-type:carrier: ext4
(bootloader) partition-type:customize: raw
(bootloader) partition-type:cache: raw
(bootloader) partition-type:system: raw
(bootloader) partition-type:userdata: raw
(bootloader) partition-size:modem: 0x00000000027e0000
(bootloader) partition-size:sbl1: 0x0000000000080000
(bootloader) partition-sizeSmiley Very HappyDR: 0x0000000000020000
(bootloader) partition-size:aboot: 0x0000000000113000
(bootloader) partition-size:rpm: 0x000000000003e800
(bootloader) partition-size:tz: 0x000000000008c000
(bootloader) partition-size:hyp: 0x0000000000020000
(bootloader) partition-size:utags: 0x0000000000080000
(bootloader) partition-size:misc: 0x0000000000080000
(bootloader) partition-sizeSmiley TongueadA: 0x000000000036f000
(bootloader) partition-size:abootBackup: 0x0000000000113000
(bootloader) partition-size:rpmBackup: 0x000000000003e800
(bootloader) partition-size:tzBackup: 0x000000000008c000
(bootloader) partition-size:hypBackup: 0x0000000000020000
(bootloader) partition-size:utagsBackup: 0x0000000000080000
(bootloader) partition-size:logs: 0x0000000000200000
(bootloader) partition-size:frp: 0x0000000000080000
(bootloader) partition-sizeSmiley TongueadB: 0x000000000022f000
(bootloader) partition-size:modemst1: 0x0000000000180000
(bootloader) partition-size:modemst2: 0x0000000000180000
(bootloader) partition-size:hob: 0x000000000007a000
(bootloader) partition-size:dhob: 0x0000000000008000
(bootloader) partition-size:fsg: 0x0000000000300000
(bootloader) partition-size:fsc: 0x0000000000000400
(bootloader) partition-size:cid: 0x0000000000020000
(bootloader) partition-size:metadata: 0x0000000000080000
(bootloader) partition-size:logo: 0x0000000000400000
(bootloader) partition-size:clogo: 0x0000000000400000
(bootloader) partition-sizeSmiley Tongueersist: 0x0000000000800000
(bootloader) partition-size:kpan: 0x0000000000800000
(bootloader) partition-size:boot: 0x0000000001000000
(bootloader) partition-size:recovery: 0x0000000001019000
(bootloader) partition-size:ssd: 0x0000000000002000
(bootloader) partition-sizeSmiley TongueadC: 0x000000000087e000
(bootloader) partition-size:sp: 0x0000000000800000
(bootloader) partition-size:keystore: 0x0000000000800000
(bootloader) partition-sizeSmiley Surprisedem: 0x0000000001000000
(bootloader) partition-size:carrier: 0x0000000001000000
(bootloader) partition-size:customize: 0x0000000002000000
(bootloader) partition-size:cache: 0x0000000010000000
(bootloader) partition-size:system: 0x0000000091000000
(bootloader) partition-size:userdata: 0x0000000121fe0000
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (77)
(bootloader) ro.carrier: retgb
all: listed above
finished. total time: 0.373s
cid: 0x0007
Should work.
freshmike said:
Anyone got an idea why I can't unlock the bootloader with the on the Moto site ?
Moto G3
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 268435456
(bootloader) reason: Volume down key pressed
(bootloader) imei: xxxxxxxxxx
(bootloader) meid:
(bootloader) date: 07-11-2015
(bootloader) sku: XT1541
(
Should work.
Click to expand...
Click to collapse
Nope, looks fine. If you can't get the token from the site, you have to go to Moto. Unfortunately, there is no other option as there is nothing we can do. Your bootloader state is 0, and I assume you have OEM unlocking set in Dev Options and are entering the key correctly. There is nothing anyone can do to assist you except Moto.
My G5 plus came with NPN25.137-67 Indian version. Flashed TWRP and rooted. Now I want to go back to stock. I understand 67 full stock firmware is not available and I may need to downgrade using this firmware:-
[XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip].
But I came across some posts talking about problems of bootloader and partition table (gpt) downgrade since my phone came originally with 67. From what I can understand if your bootloader gets downgraded then phone will be hard bricked after receiving the OTA.
So I am guessing I cannot go back to stock ?
handy5876 said:
My G5 plus came with NPN25.137-67 Indian version. Flashed TWRP and rooted. Now I want to go back to stock. I understand 67 full stock firmware is not available and I may need to downgrade using this firmware:-
[XT1681-XT1683_POTTER_BRASIL_LATAM_MEXICO_7.0_NPN25.137-15_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip].
But I came across some posts talking about problems of bootloader and partition table (gpt) downgrade since my phone came originally with 67. From what I can understand if your bootloader gets downgraded then phone will be hard bricked after receiving the OTA.
So I am guessing I cannot go back to stock ?
Click to expand...
Click to collapse
Maybe, you can try to flash the latest twrp flashable build and replace recovery and logo with the stock files (one without the warning sign) and lock the bootloader. Can someone please confirm this?
Done
Ok I got it done. It works. Thanks to these posts/threads and the full 67 firmware.
1. https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835
2. https://forum.xda-developers.com/showpost.php?p=74251898&postcount=6
3. https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
To those who want to have a look at my command log it is in the attachment as a text file.
many thanks to run for my xt1680 AT & T Mexico greetings ...
handy5876 said:
Ok I got it done. It works. Thanks to these posts/threads and the full 67 firmware.
1. https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835
2. https://forum.xda-developers.com/showpost.php?p=74251898&postcount=6
3. https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
To those who want to have a look at my command log it is in the attachment as a text file.
Click to expand...
Click to collapse
i tried in my potter, but its not working, i flashed POTTER_NPN25.137-67-5 stock rom in my divice, its saying downgrading os , what to do
Chandru1166 said:
i tried in my potter, but its not working, i flashed POTTER_NPN25.137-67-5 stock rom in my divice, its saying downgrading os , what to do
Click to expand...
Click to collapse
Did you try as per the command log I provided ?
handy5876 said:
Did you try as per the command log I provided ?
Click to expand...
Click to collapse
yes , i tried your command log
unable to download as the download link is not active
handy5876 said:
Ok I got it done. It works. Thanks to these posts/threads and the full 67 firmware.
1. https://forum.xda-developers.com/g5-plus/how-to/lock-bootloader-moto-g5-plus-indian-t3638835
2. https://forum.xda-developers.com/showpost.php?p=74251898&postcount=6
3. https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
To those who want to have a look at my command log it is in the attachment as a text file.
Click to expand...
Click to collapse
Hi ,
Please provide me the active link .. Thanks in advance
i can't lock bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.172s]
finished. total time: 0.188s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.203s]
finished. total time: 0.203s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (102931 KB)...
OKAY [ 4.110s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 4.235s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (516109 KB)...
OKAY [ 25.440s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 25.596s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (505697 KB)...
OKAY [ 24.730s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.777s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (524284 KB)...
OKAY [ 27.119s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 27.150s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (517278 KB)...
OKAY [ 24.449s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.481s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.4
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (469093 KB)...
OKAY [ 23.088s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 23.155s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.757s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.977s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Still require signed boot.img
OKAY [ 0.172s]
finished. total time: 0.188s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot-bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.175s]
finished. total time: 0.238s
DhruvanBhalara said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.172s]
finished. total time: 0.188s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.203s]
finished. total time: 0.203s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (102931 KB)...
OKAY [ 4.110s]
writing 'oem'...
(bootloader) Security version downgrade
(bootloader) Image o failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 4.235s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (516109 KB)...
OKAY [ 25.440s]
writing 'system'...
(bootloader) Security version downgrade
(bootloader) Image s failed validation
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 25.596s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (505697 KB)...
OKAY [ 24.730s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.777s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (524284 KB)...
OKAY [ 27.119s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 27.150s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (517278 KB)...
OKAY [ 24.449s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.481s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img
_sparsechunk.4
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (469093 KB)...
OKAY [ 23.088s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 23.155s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.757s]
writing 'boot'...
(bootloader) Security version downgrade
(bootloader) Image boot failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.977s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Still require signed boot.img
OKAY [ 0.172s]
finished. total time: 0.188s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot reboot-bootloader
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting into bootloader...
OKAY [ 0.175s]
finished. total time: 0.238s
Click to expand...
Click to collapse
did you found the solution?
Cant Resolve , all methods tried but oem locking says Check 'Allow OEM Unlock' in Android Settings > Developer>Options
Couldn't attach Image, Newbie here
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.192s]
finished. total time: 0.193s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.192s]
finished. total time: 0.194s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (335878 KB)...
OKAY [ 10.360s]
writing 'oem'...
OKAY [ 2.911s]
finished. total time: 13.300s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (504257 KB)...
OKAY [ 15.479s]
writing 'system'...
OKAY [ 5.211s]
finished. total time: 20.690s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (503874 KB)...
OKAY [ 15.915s]
writing 'system'...
OKAY [ 4.346s]
finished. total time: 20.261s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (513245 KB)...
OKAY [ 15.650s]
writing 'system'...
OKAY [ 5.420s]
finished. total time: 21.079s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (523018 KB)...
OKAY [ 16.063s]
writing 'system'...
OKAY [ 4.248s]
finished. total time: 20.321s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (524250 KB)...
OKAY [ 16.431s]
writing 'system'...
OKAY [ 5.030s]
finished. total time: 21.474s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (489238 KB)...
OKAY [ 14.167s]
writing 'system'...
OKAY [ 4.544s]
finished. total time: 18.711s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.486s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.348s]
finished. total time: 0.849s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.169s]
finished. total time: 0.169s
ananya13 said:
Cant Resolve , all methods tried but oem locking says Check 'Allow OEM Unlock' in Android Settings > Developer>Options
Couldn't attach Image, Newbie here
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.192s]
finished. total time: 0.193s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.192s]
finished. total time: 0.194s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash oem oem.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotem: not found
target reported max download size of 536870912 bytes
sending 'oem' (335878 KB)...
OKAY [ 10.360s]
writing 'oem'...
OKAY [ 2.911s]
finished. total time: 13.300s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.0
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (504257 KB)...
OKAY [ 15.479s]
writing 'system'...
OKAY [ 5.211s]
finished. total time: 20.690s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.1
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (503874 KB)...
OKAY [ 15.915s]
writing 'system'...
OKAY [ 4.346s]
finished. total time: 20.261s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.2
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (513245 KB)...
OKAY [ 15.650s]
writing 'system'...
OKAY [ 5.420s]
finished. total time: 21.079s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (523018 KB)...
OKAY [ 16.063s]
writing 'system'...
OKAY [ 4.248s]
finished. total time: 20.321s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.4
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (524250 KB)...
OKAY [ 16.431s]
writing 'system'...
OKAY [ 5.030s]
finished. total time: 21.474s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.5
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending 'system' (489238 KB)...
OKAY [ 14.167s]
writing 'system'...
OKAY [ 4.544s]
finished. total time: 18.711s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.486s]
writing 'boot'...
(bootloader) Image signed with key bad key
OKAY [ 0.348s]
finished. total time: 0.849s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.169s]
finished. total time: 0.169s
Click to expand...
Click to collapse
Why do you want to lock your device bootloader, it could cause many problems in future. Just leave it unlock, you will find it helpful in future. But, if you still want to lock. Did you enable allow OEM unlock and try locking the bootloader!?
riyan65 said:
Why do you want to lock your device bootloader, it could cause many problems in future. Just leave it unlock, you will find it helpful in future. But, if you still want to lock. Did you enable allow OEM unlock and try locking the bootloader!?
Click to expand...
Click to collapse
Yes, I want to show you picture but couldn't upload here cause I'm a newbie
In the picture, the allow OEM unlocking option is toggled to off and it is greyed out, I couldn't toggle it on
ananya13 said:
Yes, I want to show you picture but couldn't upload here cause I'm a newbie
In the picture, the allow OEM unlocking option is toggled to off and it is greyed out, I couldn't toggle it on
Click to expand...
Click to collapse
Did you try format the device or reflashing the Device. Mostly it could fix that bug.
riyan65 said:
Did you try format the device or reflashing the Device. Mostly it could fix that bug.
Click to expand...
Click to collapse
Yes many times, I think my bootloader is stucked in this situation
couldn't relock bootloader
https://ibb.co/RggYPzv
riyan65 said:
Did you try format the device or reflashing the Device. Mostly it could fix that bug.
Click to expand...
Click to collapse
https://ibb.co/RggYPzv
have a look on this image
ananya13 said:
https://ibb.co/RggYPzv
have a look on this image
Click to expand...
Click to collapse
As said above, reflash the actual firmware.
For what reason do you want to relock the BL? It could cause problems and there are no real advantages in doing it.
Sent from my Mi 9T using XDA Labs
ananya13 said:
Yes, I want to show you picture but couldn't upload here cause I'm a newbie
In the picture, the allow OEM unlocking option is toggled to off and it is greyed out, I couldn't toggle it on
Click to expand...
Click to collapse
There are 9 system files on oreo firmware... You're flashing only 6.