Every time I try and run a fastboot command... it just shows the fastboot help menu.
"fastboot devices" = menu
"fastboot recovery c:\recovery-en-goapk-0630-1029.img" = menu
all i ever get is:
--------------------------------
Fastboot version 1.0
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
setserial <serial> set the device serial number
setrev <rev> set the device hardware revision
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
----------------------------------------------------
i am unlocked.
i am in fastboot mode on my phone
i have used fastboot before to install 2.3.4 and i had zero issues
Anyone know why this could be happening?
no reply yet?
"fastboot flash recovery c:\recovery-en-goapk-0630-1029.img"
nevermind... im an idiot.
DISREGARD!
lol it happens.
i actually figured it out right as you posted a reply. thanks a lot, though!
Writing recovery failed. Any idea????
Trying the S-OFF method but can't seem to get it to work. Downloaded the file and tried clicking it to execute it but nothing happens. I see tutorials for Windows, but what about Linux? Can someone please help?
jerrold24 said:
Trying the S-OFF method but can't seem to get it to work. Downloaded the file and tried clicking it to execute it but nothing happens. I see tutorials for Windows, but what about Linux? Can someone please help?
Click to expand...
Click to collapse
Did you download the linux version?
Yea I did but nothing happened. I got the beta key too.
Sent from my PG86100 using XDA Premium App
BDawgTrap said:
Did you download the linux version?
Click to expand...
Click to collapse
This is what I'm getting
[email protected]:~/android-sdk-linux_x86/tools$ android
[email protected]:~/android-sdk-linux_x86/tools$ fastboot flash_image recovery recovery-twrp-shooter-1.0.0.img
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
Um, your fastboot command shows you are trying to flash twrp recovery. That is not S-OFF. You have to get S-OFF first.
go to this website and download the linux one. get s-off and then flash twrp through fastboot
http://revolutionary.io/
Need some help please with something that has gone wrong with my first attempt to alter Android. I wanted to install a custom recovery, root the phone and take it from there.
I have a Moto e 1st edition, xt1021, system info given below.
I unlocked the boot loader, installed Minimal ADB Fastboot 1.4.3, downloaded the latest TWRP image 3.3.1.-condor for the Moto e from the TWRP website.
I used flashboot flash recovery initially to install the TWRP image, which failed, but has wiped the stock recovery. I cannot boot into recovery or do a factory reset.
The phone will boot normally. If I try a factory reset, it boots normally. If I boot into recovery, I get the Android image on his back with a red triangle, and “no command”. If I go into system recovery from here, and try both 'update by adb sideload' or 'update from sd card', both fail.
I have tried flashboot boot recovery using a stock recovery, but the phone is stuck on the initial Moto logo.
I have also tried to install an earlier TWRP recovery, 2.7.1-condor and CWM 6.o.4.7 falcon but this has failed to install also.
I have now reached the limit of my abilities – any help much appreciated, but please spell out in words of one syllable if possible.
=========================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb devices
List of devices attached
ZX1B245XHK device
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb shell pm list features
feature:reqGlEsVersion=0x30000
feature:android.hardware.audio.output
feature:android.hardware.bluetooth
feature:android.hardware.bluetooth_le
feature:android.hardware.camera
feature:android.hardware.camera.any
feature:android.hardware.faketouch
feature:android.hardware.location
feature:android.hardware.location.gps
feature:android.hardware.location.network
feature:android.hardware.microphone
feature:android.hardware.screen.landscape
feature:android.hardware.screen.portrait
feature:android.hardware.sensor.accelerometer
feature:android.hardware.sensor.light
feature:android.hardware.sensor.proximity
feature:android.hardware.telephony
feature:android.hardware.telephony.cdma
feature:android.hardware.telephony.gsm
feature:android.hardware.touchscreen
feature:android.hardware.touchscreen.multitouch
feature:android.hardware.touchscreen.multitouch.distinct
feature:android.hardware.touchscreen.multitouch.jazzhand
feature:android.hardware.usb.accessory
feature:android.hardware.usb.host
feature:android.hardware.wifi
feature:android.hardware.wifi.direct
feature:android.software.app_widgets
feature:android.software.backup
feature:android.software.connectionservice
feature:android.software.device_admin
feature:android.software.home_screen
feature:android.software.input_methods
feature:android.software.live_wallpaper
feature:android.software.managed_users
feature:android.software.print
feature:android.software.sip
feature:android.software.voice_recognizers
feature:android.software.webview
feature:com.motorola.camera
feature:com.motorola.camera.chalmers
feature:com.motorola.context
feature:com.motorola.hardware.tier.
feature:com.motorola.hardware.wave.0
feature:com.motorola.smartaction2
feature:com.motorola.smartactions2_1.1
feature:com.motorola.software.bodyguard
feature:com.motorola.software.device.condor_umts
feature:com.motorola.software.fmradioservice
feature:com.motorola.software.fmrecording
feature:com.motorola.software.guideme
feature:com.motorola.software.product.condor_tescogb
feature:com.motorola.software.storageoptimizer
feature:com.motorola.software.x_line
==================================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>adb reboot bootloader
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>fastboot flash recovery C:
\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3\twrp-2.7.2.0-hlte-4.3.img
target reported max download size of 299892736 bytes
sending 'recovery' (10738 KB)...
OKAY [ 0.608s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) image size exceeds limit
(bootloader) Failed to flash partition recovery
FAILED (remote failure)
finished. total time: 0.686s
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>fastboot boot C:\Users\ME\
Desktop\phone\Minimal_ADB_Fastboot_v1.4.3\recovery-clockwork-6.0.4.7-falcon.img
downloading 'boot.img'...
OKAY [ 0.406s]
booting...
OKAY [ 0.499s]
finished. total time: 0.920s
========================================================
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>FASTBOOT GETVAR ALL
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootlo
ader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Users\ME\Desktop\phone\Minimal_ADB_Fastboot_v1.4.3>
My phone does not enter into FastBootD mode when I enter "fastboot reboot fastboot"..
The screen on my phone doesn't change at all when I enter the command, and my computer adb window reads the following, it's some sort of help menu;
Any advice? Thank you it's very much appreciated.
PS C:\adb> fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\adb
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
You need to update your adb/fastboot. Download the latest platform tools from the link above.
That seems a bit odd since I just downloaded it 2 days ago from Google! Could have got an old link but I doubt it...
Didn't work unfortunately!
I downloaded the zip file from the link, unzipped with 7zip and got "platform-tools_r30.0.5-windows". Within there is a folder named Platform Tools.. I held shift and right clicked on the white space in that folder and opened a powershell.. Ran this:
PS C:\Users\CSW\Downloads\platform-tools_r30.0.5-windows\platform-tools> fastboot devices
ZY227FVPN4 fastboot
PS C:\Users\CSW\Downloads\platform-tools_r30.0.5-windows\platform-tools> fastboot reboot fastboot
usage: fastboot [ <option> ] <command>
And received the same help menu and no change on my phone.. Same result.
Listen.....reboot to recovery. It's an empty barren wasteland, until: hold the power key down for a 3 second count, now, continuing to hold the power key down, hold the volume up key down for a 2 count: 1, and 2, and...release.
On the new menu enter fastboot - this is fastbootd.
bronkish said:
Listen.....reboot to recovery. It's an empty barren wasteland, until: hold the power key down for a 3 second count, now, continuing to hold the power key down, hold the volume up key down for a 2 count: 1, and 2, and...release.
On the new menu enter fastboot - this is fastbootd.
Click to expand...
Click to collapse
I've done that button pressing. Android robot with a warning triangle is shown. And it is stuck.
sevasnex said:
I've done that button pressing. Android robot with a warning triangle is shown. And it is stuck.
Click to expand...
Click to collapse
hold power an hit vol-up once then release
The trick for our SOFIA is to execute the ADB command while the phone is POWERED ON (System booted up like normal - like when use the phone, make calls, etc) and NOT in fastboot/bootloader mode:
Enable USB Debugging in developer options on phone
Connect USB cable
Answer confirmation/security prompts on phone and PC
Type "adb reboot fastboot" at ADB CLI
FASTBOOTD will now appear in red letters at the top - you are in FASTBOOTD mode
Hope this helps!
Hi there,
The device is
- usb debugging;
- oem unlock in Developer options;
both enabled.
adb devices recognized device.
In fastboot mode,
Code:
fastboot oem unlock
returned
Code:
OKAY [ 0.007s]
Finished. Total time: 0.019s
And the device rebooted from fastboot mode into Twrp recovery.
After the device rebooted into fastboot mode, fastboot oem device-info showed
Code:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.072s]
Finished. Total time: 0.072s
Bootloader remained unlocked.
In addition, fastboot flashing unlock produced
Code:
FAILED (remote: 'unknown command')
fastboot: error: Command failed
How to unlock the bootloader of this device?
May you need any further information, please do not hesitate to contact me.
Thanks in advance.
Hi there,
after fastboot oem unlock, the device booted into recovery.
And fastboot erase cache , it returns
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' FAILED (remote: 'device is locked. Cannot erase')
The same result was produced after fastboot erase recovery.
How to solve it?
Thanks.
Wen
PS: The device was detected following fastboot devices
sounds like you did not unlock bootloader right way. most devices need another predecessor step: oem unlocking in developer options.
Btw do not use fastboot erase command at all, do not follow any tutorial that suggest this.
aIecxs said:
sounds like you did not unlock bootloader right way. most devices need another predecessor step: oem unlocking in developer options.
Btw do not use fastboot erase command at all, do not follow any tutorial that suggest this.
Click to expand...
Click to collapse
Thanks for your reply.
Could you please specify the reason that "fastboot erase" commands should not be used?
fastboot 'erase' is dangerous command. it will erase the entire partition, which is not what you want. for example erasing recovery (like you tried) will brick your device (what was the intention behind?)
'erase' is useless intermediate step in most cases. for example when fastboot 'flash' recovery, the recovery partition will be sequentially overwritten from given file anyway. you can just skip erase it doesn't matter in such case.
partitions containing mountable file system must formatted like this (unlocked bootloader required)
Code:
fastboot format:ext4 cache
fastboot format:f2fs userdata
without formatting, the phone cannot mount the partition and will brick (few phones are smart enough to complete the formatting step automatically, though)
aIecxs said:
fastboot 'erase' is dangerous command. it will erase the entire partition, which is not what you want. for example erasing recovery (like you tried) will brick your device (what was the intention behind?)
'erase' is useless intermediate step in most cases. for example when fastboot 'flash' recovery, the recovery partition will be sequentially overwritten from given file anyway. you can just skip erase it doesn't matter in such case.
partitions containing mountable file system must formatted like this (unlocked bootloader required)
Code:
fastboot format:ext4 cache
fastboot format:f2fs userdata
without formatting, the phone cannot mount the partition and will brick (few phones are smart enough to complete the formatting step automatically, though)
Click to expand...
Click to collapse
Hi, thank you for your replies, sorry for my belated responsiveness, owing to the recent recovery from (severe) covid symptoms.
I once used "fastboot erase recovery" because the device was stuck on the logo of newly installed recovery, and had no other means to resolve it.
So do you mean that the right way to format cache, userdata or system partitions should include the format of the partition (ex. ext4, f2fs) in adb commands fastboot format:ext4 cache, fastboot format:f2fs userdata?
If so, will the simple command fastboot erase userdata do the same thing, given that userdata is located in one simple partition, ex. mmcblk0p43?
Both fastboot format:ext4 system and fastboot erase system will wipe out the same partition (say, mmcblk0p19 where the system partition is lcoated)?
What is the function to include disk format (ext4 or f2fs) in adb commands?
aIecxs said:
sounds like you did not unlock bootloader right way. most devices need another predecessor step: oem unlocking in developer options.
Btw do not use fastboot erase command at all, do not follow any tutorial that suggest this.
Click to expand...
Click to collapse
Hi,
I tried to unlock the device by fasboot oem unlock, it booted into recovery one more time.
And I verified in "Developer options", "OEM unlocking" is enabled.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to resolve it?
Thanks.
unexpected behaviour. did you try fastboot flashing unlock as well?
wenyendev said:
Both fastboot format:ext4 system and fastboot erase system will wipe out the same partition (say, mmcblk0p19 where the system partition is located)?
What is the function to include disk format (ext4 or f2fs) in adb commands?
Click to expand...
Click to collapse
Yes, but there is a difference.
erase will delete entire partition.
format will only format file system.
including file system type is optional.
aIecxs said:
unexpected behaviour. did you try fastboot flashing unlock as well?
Yes, but there is a difference.
erase will delete entire partition.
format will only format file system.
including file system type is optional.
Click to expand...
Click to collapse
Yes, it was the same difference.
What is the difference between "delete entire partition" and "format file system"?
Thanks.
wenyendev said:
What is the difference between "delete entire partition" and "format file system"?
Click to expand...
Click to collapse
I assume once in your life you have created partition table with one or more partitions on single disk, be it windows or linux. every partition must formatted to receive a valid file system (NTFS FAT32 ext4 swap etc.) otherwise the raw partition is just unused inaccessable disk space.
"format file system" is when you format existing partition to valid file system type, in order to make it mountable
Ok thanks.
What else do "delete entire partition" and "format file system" do, apart from wiping out the data?
So the difference between two is that one would be mountable afterwards, the other not?
right. erase will just write 00 00 00 00 00 00 00 00 zeros on whole partition (invalid/empty disk space)
format will create a valid file system, so partition becomes useable.
aIecxs said:
without formatting, the phone cannot mount the partition and will brick (few phones are smart enough to complete the formatting step automatically, though)
Click to expand...
Click to collapse
to be nitpicky: partitions aren't mounted. file systems are.
Thanks.
So fastboot erase userdata,
fastboot erase system,
fastboot erase cache,
fastboot erase recovery
will overwrite their respective partitions (userdata, system, cache, recovery) by 00 00 00 00?
And by format like factory-reset, the data remain intact on the file system?
What are the relations between file systems and partitions?
It's good to be nitpicky in the context.
Here, by "mountable" you mean "to be able to read and write" (the file systems)?
Thanks in advance.
if you erase cache partition, the phone will no longer boot.
wenyendev said:
And by format like factory-reset, the data remain intact on the file system?
Click to expand...
Click to collapse
on formatting, no data remains intact, new (empty) file system is written to partition.
https://www.wikipedia.org/wiki/Disk_formatting
aIecxs said:
if you erase cache partition, the phone will no longer boot.
on formatting, no data remains intact, new (empty) file system is written to partition.
https://www.wikipedia.org/wiki/Disk_formatting
Click to expand...
Click to collapse
It is contrary to my experience.
After running fastboot erase cache, the device safely rebooted.
Here, "intact" means not overwritten by new data.
your bootloader is locked, therefore any harmful cmd (such as flash, erase, format) is forbidden and has no effect. (btw phone gave you warning you mixed up cmds format with erase)
Code:
fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache'
FAILED (remote: 'device is locked. Cannot erase')
I said on formatting, no data remains (nothing survives) because it is overwritten by new file system.
(Maybe on quick format some data may survive, but not provided by file system and therefore invisible/non existent, like free disk space.)
I was talking about fastboot erase cache that worked on another bootloader-free device.
then you are lucky your phone...
aIecxs said:
(few phones are smart enough to complete the formatting step automatically, though)
Click to expand...
Click to collapse
aIecxs said:
unexpected behaviour. did you try fastboot flashing unlock as well?
Yes, but there is a difference.
erase will delete entire partition.
format will only format file system.
including file system type is optional.
Click to expand...
Click to collapse
fastboot flashing unlock produced the following error.
What brand/device model/android version you are trying to unlock?
Code:
adb shell
$ getprop ro.build.fingerprint
$ getprop sys.get_unlock_ability
$ getprop ro.oem_unlock_supported
$ getprop ro.oem_unlock_allowed