Develop Bugs

[Q] Complete noob needs help relocking bootloader

Okay so I have the One X, decided I wanted to root it even though I have NO IDEA what its all about (yes I know Im an idiot). I basically got as far as unlocking the bootloader then something went wrong and I couldnt get any further. I basically just want to relock the bootloader but I have no idea how. Like I said, Im a complete noob and need someone to really walk me through this the simplest way there is. Ps Im on a mac, which Im sure makes it even more difficult.
Any help is greatly appreciated :/

well, i don't know anything about mac, but i do know how to re-lock the bootloader under microsoft windows.
All you have to do is download FASTBOOT in any windows pc, download it from here
press and hold volume down + power button on your phone (to enter bootloader)
when in bootloader, enter fastboot mode by just hitting power key once,
now connect USB to pc and the phone
u'll see FASTBOOT PC written in your phone screen,
now go to the downloaded fastboot folder in ur pc,
hold SHIFT and Right click, Select OPEN COMMAND WINDOW HERE,
in the command window, just write : fastboot oem lock
That's it!

thanks so much for your reply. I'm gonna hold out and see if anyone can give me a mac reply but I'm gonna see if anyone I know can lend me their laptops and try what you said. thanks again
Sent from my HTC One X using xda app-developers app

becatron said:
thanks so much for your reply. I'm gonna hold out and see if anyone can give me a mac reply but I'm gonna see if anyone I know can lend me their laptops and try what you said. thanks again
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
here is a thread explaining how to unlock on mac, quite simple steps
to lock the bootloader, all u need is to write ./fastboot-mac oem lock instead of ./fastboot-mac oem unlock :good:

I tried that link before and its never worked. I dont have a great understanding of Terminal and it usual gives me something along the lines of 'no such file or directory'.
Edit: I just got '-bash: ./fasboot-mac: No such file or directory'

becatron said:
I tried that link before and its never worked. I dont have a great understanding of Terminal and it usual gives me something along the lines of 'no such file or directory'.
Edit: I just got '-bash: ./fasboot-mac: No such file or directory'
Click to expand...
Click to collapse
That means that you haven't downloaded fastboot!
You need to download fastboot.exe to perform this operation.
or simply visit some friend with a windows pc and do the task

still can't get my hands on a Windows laptop :/ just moved house too so don't even have any wifi agh.

One question, do you have the Android SDK installed? I can help you with the mac since it is the same as linux
arun6106 said:
That means that you haven't downloaded fastboot!
You need to download fastboot.exe to perform this operation.
or simply visit some friend with a windows pc and do the task
Click to expand...
Click to collapse
.exe extentions doesn't work on Macs :silly:

matt95 said:
One question, do you have the Android SDK installed? I can help you with the mac since it is the same as linux
Click to expand...
Click to collapse
I'm sorry but Wtf does sdk mean?

becatron said:
I'm sorry but Wtf does sdk mean?
Click to expand...
Click to collapse
Lol, download this file then unzip it, using the terminal go to that folder and type
Code:
./fastboot oem lock

matt95 said:
Lol, download this file then unzip it, using the terminal go to that folder and type
Code:
./fastboot oem lock
Click to expand...
Click to collapse
I'll try this tomorrow after work. thank you for taking pity on me and helping and not laughing me off the forum

becatron said:
I'll try this tomorrow after work. thank you for taking pity on me and helping and not laughing me off the forum
Click to expand...
Click to collapse
Don't worry :good: no one is a genius in here

matt95 said:
Lol, download this file then unzip it, using the terminal go to that folder and type
Code:
./fastboot oem lock
Click to expand...
Click to collapse
Okay so just tried this and its not working. How and what exactly do I type? When I type ./fastboot oem lock it just brings up a big page of abbreviations and commands. Its also saying ERROR: Could not get pipe properties
This is so stressful

becatron said:
Okay so just tried this and its not working. How and what exactly do I type? When I type ./fastboot oem lock it just brings up a big page of abbreviations and commands. Its also saying ERROR: Could not get pipe properties
This is so stressful
Click to expand...
Click to collapse
Is your phone in fastboot mode? if yes it should work, you should see a red highlighted "fastboot usb"

matt95 said:
Is your phone in fastboot mode? if yes it should work, you should see a red highlighted "fastboot usb"
Click to expand...
Click to collapse
Yep it is.. This is what I got
Rebeccas-MacBook:~ administrator$ /Users/administrator/Downloads/android\ 3/fastboot oem lock
ERROR: could not get pipe properties
ERROR: could not get pipe properties
ERROR: could not get pipe properties
...
ERROR: bulkOut endpoint not assigned
FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
I know im probably not writing it properly

You need to download the file I posted, unzip it, navigate to that folder and then try to type exactly what I write
Code:
./fastboot
paste here what you get
Sent from my HTC One using XDA Premium 4 mobile app

matt95 said:
You need to download the file I posted, unzip it, navigate to that folder and then try to type exactly what I write
Code:
./fastboot
paste here what you get
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is what I get when I type ./fastboot
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
format <partition> format 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
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
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
Rebeccas-MacBook:~ administrator$

OK! fastboot is working, now do it again but type
Code:
./fastboot oem lock

matt95 said:
OK! fastboot is working, now do it again but type
Code:
./fastboot oem lock
Click to expand...
Click to collapse
Nope its still not working
Rebeccas-MacBook:~ administrator$ ./fastboot oem lock
-bash: ./fastboot: No such file or directory
Rebeccas-MacBook:~ administrator$ /Users/administrator/Downloads/android\ 3/fastboot ./fastboot oem lock
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
format <partition> format 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
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
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
Rebeccas-MacBook:~ administrator$

You have to type
Code:
./fastboot oem lock
not
Code:
3/fastboot ./fastboot oem lock

I need help with htc one m8

hi i rooted my phone and have messed up .
i used twrp recovery
now my phone says it doesnt have any OS
can somwbody help me on how to install new OSand make my device working again

Exact same problem. If I get it figured out I'll let you know.

Copy ROM on ExtSD card...mount extsd in TWRP, then install from there...

ravi3535 said:
hi i rooted my phone and have messed up .
i used twrp recovery
now my phone says it doesnt have any OS
can somwbody help me on how to install new OSand make my device working again
Click to expand...
Click to collapse
Boot to bootloader/fastboot then run command fastboot getvar all
Post here the result (delete serial no. & imei no.)
Will see what we can do later

ckpv5 said:
Boot to bootloader/fastboot then run command fastboot getvar all
Post here the result (delete serial no. & imei no.)
Will see what we can do later
Click to expand...
Click to collapse
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot getvar
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
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> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
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:\Program Files (x86)\Android\android-sdk\platform-tools>
this is what i get

flyera343 said:
Copy ROM on ExtSD card...mount extsd in TWRP, then install from there...
Click to expand...
Click to collapse
i did try it i said mp5 file missing

fastboot getvar all
You missed "all"

ckpv5 said:
fastboot getvar all
You missed "all"
Click to expand...
Click to collapse
sorry dude i will try that when i get home at college at the momet
thanks for help mate

Pixel XL stuck in boot animation

I have a rooted Pixel XL. I kept the OEM ROM. Besides being rooted it's stock. I'm selling the phone and did a factory reset within the menu. It rebooted and now it's stuck in the boot animation screen. I went into recovery mode and wiped it that way as well. When I reboot, it's the same thing. I see the "Google" logo, but then it's just stuck on the animation screen. Did I forget to do something? Do I have to re-lock it before I wipe it? Thank you

flint24 said:
I have a rooted Pixel XL. I kept the OEM ROM. Besides being rooted it's stock. I'm selling the phone and did a factory reset within the menu. It rebooted and now it's stuck in the boot animation screen. I went into recovery mode and wiped it that way as well. When I reboot, it's the same thing. I see the "Google" logo, but then it's just stuck on the animation screen. Did I forget to do something? Do I have to re-lock it before I wipe it? Thank you
Click to expand...
Click to collapse
First and foremost don't relock it. If you want to clean it up for selling purposes, then you're best bet is to flash a full factory image. Nice and easy and the phone will be complete stock after.

Post above is dead on, just flash all. Also remember to properly remove your Google account so the buyer doesn't have problems.
Sent from my Pixel XL using XDA Labs

toknitup420 said:
First and foremost don't relock it. If you want to clean it up for selling purposes, then you're best bet is to flash a full factory image. Nice and easy and the phone will be complete stock after.
Click to expand...
Click to collapse
Thanks. It actually came back up after rebooting it a few times. I'm still a little concerned as I don't want the buyer to go through the same hassle should he also try to factory reset it from the menu. I didn't change the image at all, just unlocked the bootloader and rooted the phone. I'm afraid to **** with it any more. It's working now. I'm just hoping the buyer doesn't a) play with the factory reset and b) mind the "bootloader is unlocked" message when the phone is rebooted.

flint24 said:
Thanks. It actually came back up after rebooting it a few times. I'm still a little concerned as I don't want the buyer to go through the same hassle should he also try to factory reset it from the menu. I didn't change the image at all, just unlocked the bootloader and rooted the phone. I'm afraid to **** with it any more. It's working now. I'm just hoping the buyer doesn't a) play with the factory reset and b) mind the "bootloader is unlocked" message when the phone is rebooted.
Click to expand...
Click to collapse
Wait I'm confused. Did you sell the phone in a non bootable state? Do you have twrp on it?

toknitup420 said:
Wait I'm confused. Did you sell the phone in a non bootable state? Do you have twrp on it?
Click to expand...
Click to collapse
No it boots. It boots into whatever image was on it when I bought it at Verizon. I just unlocked the bootloader and gave myself root access. I didn't use TWRP.

Ok now I have a new problem. The guy I sold the phone to didn't like that the bootloader was unlocked. He called Google who made him re-lock the bootloader. So he sent the phone back to me completely bricked. Now I get a RED exclamation triangle on the boot screen, saying the device is corrupt and can't be trusted. Then it shuts off. It doesn't even go to the bouncing ball Google startup screen. I'm able to get into the bootloader screen which confirms that it's locked. However I'm unable to get to a recovery. When I press the vol up/down buttons to choose recovery, it just reboots and shuts off like before. I can only get to the bootloader.
Is there anything I can do to salvage this phone? Thanks guys.
Edit 1: I'm able to boot into safe mode.
Edit 2: I'm not longer able to get into safe mode. It freezes during the boot and the bouncing balls just stop. A "G" comes up, then it turns off.

Nevermind disregard

Is there any way to boot into safe mode from fastboot? Or install a recovery, even stock recovery, without the bootloader being unlocked?
Sent from my EDI-AL10 using Tapatalk

flint24 said:
Is there any way to boot into safe mode from fastboot?
Click to expand...
Click to collapse
This was the very first result when I googled your question. Hope it helps?
https://recomhub.com/blog/how-to-start-google-pixel-and-pixel-xl-in-safe-mode/
flint24 said:
Or install a recovery, even stock recovery, without the bootloader being unlocked?
Click to expand...
Click to collapse
I'm pretty sure it's not possible. About 97% sure.
But I haven't researched it or anything.

CZ Eddie said:
This was the very first result when I googled your question. Hope it helps?
https://recomhub.com/blog/how-to-start-google-pixel-and-pixel-xl-in-safe-mode/
I'm pretty sure it's not possible. About 97% sure.
But I haven't researched it or anything.
Click to expand...
Click to collapse
Thanks but I've been trying to get back into safe mode this way for days now. I was able to do it once, but never again for some strange reason. Since it turns off immediately after boot, I have to go into fastboot then run the fastboot continue command just to get to the Google startup screen. Then I press and hold volume down. It's only worked once.
Sent from my EDI-AL10 using Tapatalk

flint24 said:
Thanks but I've been trying to get back into safe mode this way for days now. I was able to do it once, but never again for some strange reason. Since it turns off immediately after boot, I have to go into fastboot then run the fastboot continue command just to get to the Google startup screen. Then I press and hold volume down. It's only worked once.
Sent from my EDI-AL10 using Tapatalk
Click to expand...
Click to collapse
I get it now. You're looking for a way to access Safe Mode specifically from within Fastboot.
Try this link?
http://android.stackexchange.com/questions/131188/entering-safe-mode-from-adb-shell
Please let us know what you find out.
Sharing [info] is caring.
EDIT: That link is for ADB, not Fastboot. oops.

CZ Eddie said:
I get it now. You're looking for a way to access Safe Mode specifically from within Fastboot.
Try this link?
http://android.stackexchange.com/questions/131188/entering-safe-mode-from-adb-shell
Please let us know what you find out.
Sharing [info] is caring.
EDIT: That link is for ADB, not Fastboot. oops.
Click to expand...
Click to collapse
Do you have to be in recovery mode to run adb commands? I'm only able to get into fastboot mode.
Sent from my EDI-AL10 using Tapatalk

flint24 said:
Do you have to be in recovery mode to run adb commands? I'm only able to get into fastboot mode.
Click to expand...
Click to collapse
Yep, sorry. That's why I edited my post.
ADB only works from recovery.
I googled for a couple minutes but couldn't find a Safe Mode command for fastboot. Sorry.
---------- Post added at 05:18 PM ---------- Previous post was at 05:17 PM ----------
What happens if you get into Fastboot and run the command "fastboot continue"?

CZ Eddie said:
Yep, sorry. That's why I edited my post.
ADB only works from recovery.
I googled for a couple minutes but couldn't find a Safe Mode command for fastboot. Sorry.
Click to expand...
Click to collapse
You see my pain here man lol. My phone is completely jacked. Whoever this guy called who bought my phone (I think it was Google) had him hack proof the phone.
Sent from my EDI-AL10 using Tapatalk

CZ Eddie said:
Yep, sorry. That's why I edited my post.
ADB only works from recovery.
I googled for a couple minutes but couldn't find a Safe Mode command for fastboot. Sorry.
---------- Post added at 05:18 PM ---------- Previous post was at 05:17 PM ----------
What happens if you get into Fastboot and run the command "fastboot continue"?
Click to expand...
Click to collapse
It starts to boot. I see the spinning balls, then they stop and stand in place. Sometimes I see a "G" and then the screen goes dark. It's not off though. The screen just does dark
Sent from my EDI-AL10 using Tapatalk

flint24 said:
It starts to boot. I see the spinning balls, then they stop and stand in place. Sometimes I see a "G" and then the screen goes dark. It's not off though. The screen just does dark
Click to expand...
Click to collapse
There does not appear to be a safe mode option for fastboot.
I'm very uncomfortable offering suggestions here because I'm out of my depth and your phone is a Verizon that was unlocked and then re-locked which is even more of an unknown for me.
Have you tried to fasboot anything like flash-all.bat or fastboot boot twrp.img just to see what happens?
I'm just throwing stuff on the wall here. TWRP probably won't work because it sounds like you're relocked.
Anything you do from here on could likely brick your phone even harder.
Here's a list of fastoot commands.
I'm really interested to know if unlock works, or if the critical unlock works and lets you boot a boot img or something to gain access to recovery.
Check out all the various unlock options.
Again, I'm out of my depth and doing ANYTHING here could brick you harder.
May be best to wait for some better help.
Code:
C:\Users\xxx\AppData\Local\Android\sdk1\platform-tools>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
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.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request
.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
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.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [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 erase partition before
formatting.
-s <specific device> Specify a device. For USB, provide ei
ther
a serial number or path to device por
t.
For ethernet, provide an address in t
he
form <protocol>:<hostname>[:port] whe
re
<protocol> is either tcp or udp.
-p <product> Specify product name.
-c <cmdline> Override kernel commandline.
-i <vendor id> Specify a custom USB vendor id.
-b, --base <base_addr> Specify a custom kernel base
address (default: 0x10000000).
--kernel-offset Specify a custom kernel offset.
(default: 0x00008000)
--ramdisk-offset Specify a custom ramdisk offset.
(default: 0x01000000)
--tags-offset Specify a custom tags offset.
(default: 0x00000100)
-n, --page-size <page size> Specify the nand page size
(default: 2048).
-S <size>[K|M|G] Automatically sparse files greater
than 'size'. 0 to disable.
--slot <slot> Specify slot name to be used if the
device supports slots. All operations
on partitions that support slots will
be done on the slot specified.
'all' can be given to refer to all sl
ots.
'other' can be given to refer to a
non-current slot. If this flag is not
used, slotted partitions will default
to the current active slot.
-a, --set-active[=<slot>] Sets the active slot. If no slot is
provided, this will default to the va
lue
given by --slot. If slots are not
supported, this sets the current slot
to be active. This will run after all
non-reboot commands.
--skip-secondary Will not flash secondary slots when
performing a flashall or update. This
will preserve data on other slots.
--unbuffered Do not buffer input or output.
--version Display version.
-h, --help show this message.
C:\Users\xxx\AppData\Local\Android\sdk1\platform-tools>
---------- Post added at 05:39 PM ---------- Previous post was at 05:37 PM ----------
Here is my guide for the flash-all.bat if you want to see if it works.
I think you might have to be unlocked though?
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478

CZ Eddie said:
There does not appear to be a safe mode option for fastboot.
I'm very uncomfortable offering suggestions here because I'm out of my depth and your phone is a Verizon that was unlocked and then re-locked which is even more of an unknown for me.
Have you tried to fasboot anything like flash-all.bat or fastboot boot twrp.img just to see what happens?
I'm just throwing stuff on the wall here. TWRP probably won't work because it sounds like you're relocked.
Anything you do from here on could likely brick your phone even harder.
Here's a list of fastoot commands.
I'm really interested to know if unlock works, or if the critical unlock works and lets you boot a boot img or something to gain access to recovery.
Check out all the various unlock options.
Again, I'm out of my depth and doing ANYTHING here could brick you harder.
May be best to wait for some better help.
Code:
C:\Users\xxx\AppData\Local\Android\sdk1\platform-tools>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
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.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request
.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
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.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [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 erase partition before
formatting.
-s <specific device> Specify a device. For USB, provide ei
ther
a serial number or path to device por
t.
For ethernet, provide an address in t
he
form <protocol>:<hostname>[:port] whe
re
<protocol> is either tcp or udp.
-p <product> Specify product name.
-c <cmdline> Override kernel commandline.
-i <vendor id> Specify a custom USB vendor id.
-b, --base <base_addr> Specify a custom kernel base
address (default: 0x10000000).
--kernel-offset Specify a custom kernel offset.
(default: 0x00008000)
--ramdisk-offset Specify a custom ramdisk offset.
(default: 0x01000000)
--tags-offset Specify a custom tags offset.
(default: 0x00000100)
-n, --page-size <page size> Specify the nand page size
(default: 2048).
-S <size>[K|M|G] Automatically sparse files greater
than 'size'. 0 to disable.
--slot <slot> Specify slot name to be used if the
device supports slots. All operations
on partitions that support slots will
be done on the slot specified.
'all' can be given to refer to all sl
ots.
'other' can be given to refer to a
non-current slot. If this flag is not
used, slotted partitions will default
to the current active slot.
-a, --set-active[=<slot>] Sets the active slot. If no slot is
provided, this will default to the va
lue
given by --slot. If slots are not
supported, this sets the current slot
to be active. This will run after all
non-reboot commands.
--skip-secondary Will not flash secondary slots when
performing a flashall or update. This
will preserve data on other slots.
--unbuffered Do not buffer input or output.
--version Display version.
-h, --help show this message.
C:\Users\xxx\AppData\Local\Android\sdk1\platform-tools>
---------- Post added at 05:39 PM ---------- Previous post was at 05:37 PM ----------
Here is my guide for the flash-all.bat if you want to see if it works.
I think you might have to be unlocked though?
https://forum.xda-developers.com/pixel-xl/how-to/info-how-restored-to-stock-soft-t3494478
Click to expand...
Click to collapse
Yes it definitely has to be unlocked to run the flash-all.bat or flash-all.sh (I'm using a mac). I've tried it and it gives me an "oem unlock not allowed" message. I'll try the other commands I haven't tried yet from your list
Sent from my EDI-AL10 using Tapatalk

What about flashing unlock_bootloader request? Also fastboot flashing unlock critical. I am sure this can get fixed.

biggiesmalls657 said:
What about flashing unlock_bootloader request? Also fastboot flashing unlock critical. I am sure this can get fixed.
Click to expand...
Click to collapse
I can only do flashboot oem, not flashboot flashing. I think the newer versions of fastboot only does the oem command.
flashboot oem unlock_bootloader and flashboot oem unlock critical both fail (remote: oem unlock is not allowed)
Sent from my EDI-AL10 using Tapatalk

Pixel C - fastboot unsupported command

Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !

Did you unlock your device first with "fastboot oem unlock"?

redukt said:
Did you unlock your device first with "fastboot oem unlock"?
Click to expand...
Click to collapse
Yes i did this before, i was running on Remix OS

I don't know if this is of relevance but there were new fastboot commands introduced from Android M (?) and I have recollection about "partial unlock" - two flags required to be set and if only one was set it could be reported that the bootloader was unlocked but fastboot saw it as locked. Above may be totally wrong.
Here's the difference between old and current fastboot commands. Note the new lock/unlock commands
Code:
************************ OLD **************************************
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
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> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
************************ NEW **************************************
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
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.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
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.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
reboot-bootloader Reboot device into bootloader.
help Show this help message.

-Yazh- said:
Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !
Click to expand...
Click to collapse
Hi, I'm just wondering if you were able to fix your tablet. I ran into the same problem as you here and am not able to find a solution to it.

Hi !!
Sorry for bad news, but i didn't found any solution since my Pixel C was bricked. Maybe there is a solution, but I dropped it before finding it.
I hope you find something to fix it !

@viii_xvi Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html

peterk-1 said:
Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
Click to expand...
Click to collapse
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
peterk-1 said:
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?

viii_xvi said:
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?
Click to expand...
Click to collapse
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.

peterk-1 said:
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.
Click to expand...
Click to collapse
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
fastboot: usage: no command
Click to expand...
Click to collapse

viii_xvi said:
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
Click to expand...
Click to collapse
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.

rhmanoa said:
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.
Click to expand...
Click to collapse
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.

viii_xvi said:
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.
Click to expand...
Click to collapse
Just bought today, same issue, have you solved it?

mansonstein said:
Just bought today, same issue, have you solved it?
Click to expand...
Click to collapse
No, I didn't manage to fix it.

did you found a solution yet？
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command

richardwia said:
did you found a solution yet？
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command
Click to expand...
Click to collapse
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.

viii_xvi said:
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.
Click to expand...
Click to collapse
really？where I can find the“fix fastboot in advanced options”？

richardwia said:
really？where I can find the“fix fastboot in advanced options”？
Click to expand...
Click to collapse
I believe I'm not qualified to help you as I disposed of my tablet months ago. All the advice I've given is off of memory and may not be accurate. That being said, I won't help you anymore in fear of giving inaccurate information that may lead to bricking of your tablet.

I have a pixel C, flashed with latest 3-rd pixel experience before, someday i tried to flash back to factory image, hit the same trouble like this topic, i came here several times before, no solution, today, i found another article about this , it's solved my trouble.
sorry i am new here, i couldn't share the outside article link.
would like to share what i did on my pixel c.
1. root your pixel c
2. adb shell //this command could be executed under recovery mode too.
3. su
4. fwtool vbnv write dev_boot_fastboot_full_cap 1
5. adb reboot fastboot
then you could flash anything you want.

I had this just now - I finally got fed up of my Pixel C being so laggy and also chrome opening up as blank pages (I switched to brace to fix this, but it's abit crashy).
Anyhow I found that after
adb reboot bootloader
that
fastboot flash recovery twrp.img
was failing for me in the "Writing" stage
I discovered that the fix was to use
adb flashing unlock
then it will ask you a question (power button to confirm and one of teh volume keys to cancel).
after this it spins with erasing for a while and then comes back to fastboot after which
fastboot flash recovery twrp.img
Worked, after this you get an annoying 30s delay for each restart, I think that can be fixed by
adb flashing lock
I'll verify this when I've finished flashing a usable ROM to my Pixel C...

FastbootD mode

i'm on stock 10.0.12 firmware using r30.0.4 platform tools. when i'm in bootloader mode and type fastboot reboot fastboot i get just fastboot help:
PS F:\ONEPLUS 7T\platform-tools_r30.0.4-windows\platform-tools> 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
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> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
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 F:\ONEPLUS 7T\platform-tools_r30.0.4-windows\platform-tools>
how can i enter fastbootD mode?

To enter in fastbootd you need the newest platforn-tools aka adb and fastboot files
When you got that you reboot to bootloader(fastboot mode) and then use the fastbootd
Just use google tobsearch for fastbootd op7t
---------- Post added at 08:37 AM ---------- Previous post was at 08:35 AM ----------
Or look closely here
https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
It gives link to latest platfom-tools

Makerrr said:
To enter in fastbootd you need the newest platforn-tools aka adb and fastboot files
When you got that you reboot to bootloader(fastboot mode) and then use the fastbootd
Just use google tobsearch for fastbootd op7t
---------- Post added at 08:37 AM ---------- Previous post was at 08:35 AM ----------
Or look closely here
https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
It gives link to latest platfom-tools[/QUOTE
thanks for your reply but i think that platform tools r30.0.4 is the newest platform tools. if u know abt newest one and be kind enough to give the link i'll be more than grateful
Click to expand...
Click to collapse

That's the latest one.
You should be able to boot fastbootd!
When in fastboot mode run fastboot reboot fastbootd
And your device should reboot in a stock recovery looking environment, that's fastbootd

Makerrr said:
That's the latest one.
You should be able to boot fastbootd!
When in fastboot mode run fastboot reboot fastbootd
And your device should reboot in a stock recovery looking environment, that's fastbootd
Click to expand...
Click to collapse
maybe it should but it doesn't. that's how my problem started.

altojd said:
maybe it should but it doesn't. that's how my problem started.
Click to expand...
Click to collapse
Execute command with .exe once you're in the folder like fastboot.exe reboot fastboot

Lossyx said:
Execute command with .exe once you're in the folder like fastboot.exe reboot fastboot
Click to expand...
Click to collapse
did it and nothing has changed. the problem remains

have you found a solution to this? i am unable to get onto fastbootd mode
C:\platform-tools>adb reboot fastboot
C:\platform-tools>fastboot getvar is-userspace
is-userspace: no
Finished. Total time: 0.009s

I'm having a similar problem: I can get into fastbootd (chinese/english menu), but I can't send any fastboot commands, it always just says "waiting for device" and 'fastboot devices' shows nothing. If I try to flash things half will fail with "partition not found" because I can only flash in fastboot, not fastbootd. Once flashed I only get bootloader booting message and then it crashes into Qualcomm CrashDump mode and all I can do is wait and then hours later it's magically back to fastbootd but still can't send commands to it, even though OnePlus_USB_Drivers_Setup.exe is installed. Any ideas??

I had issues until used the all in one tool to flash it, then it worked perfect.

thetoady said:
I had issues until used the all in one tool to flash it, then it worked perfect.
Click to expand...
Click to collapse
is fastbootd any good? i tried to use fastboot devices and getvar all command but does not do anything this on lg v60

altojd said:
i'm on stock 10.0.12 firmware using r30.0.4 platform tools. when i'm in bootloader mode and type fastboot reboot fastboot i get just fastboot help:
PS F:\ONEPLUS 7T\platform-tools_r30.0.4-windows\platform-tools> 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
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> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
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 F:\ONEPLUS 7T\platform-tools_r30.0.4-windows\platform-tools>
how can i enter fastbootD mode?
Click to expand...
Click to collapse
Reflash stock recovery, then fastboot reboot fastboot to get into fastbootd

HueyT said:
Reflash stock recovery, then fastboot reboot fastboot to get into fastbootd
Click to expand...
Click to collapse
where is stock recovery?

can someone explain me the use for fastbootd, in my case i seem to have regular fastboot and fastbootd. in fastbootd i cant execute any commands. its completely new to me and i havent found any proper documentation or tutorials going in depth with it so its all just going over my head.

HueyT said:
Reflash stock recovery, then fastboot reboot fastboot to get into fastbootd
Click to expand...
Click to collapse
I'd be surprised if reflashing the stock recovery magically fixed the problem.

Makerrr said:
That's the latest one.
You should be able to boot fastbootd!
When in fastboot mode run fastboot reboot fastbootd
And your device should reboot in a stock recovery looking environment, that's fastbootd
Click to expand...
Click to collapse
i have installed twrp recovery so am i able to go in fastbootd mode?

FakeGemstone said:
I'd be surprised if reflashing the stock recovery magically fixed the problem.
Click to expand...
Click to collapse
fastbootd is apart of recovery on many devices.
"The bootloader is expected to load and boot into the recovery image upon seeing boot-fastboot in the BCB command. Recovery then parses the BCB message and switches to fastbootd mode."

shaniKhan0 said:
i have installed twrp recovery so am i able to go in fastbootd mode?
Click to expand...
Click to collapse
If your TWRP is newer then you can still enter fastboot from TWRP, on my device using "adb reboot fastboot" will reboot my device into TWRP then enter some weird TWRP fastboot mode. However windows doesn't seem to detect that this is a device in ADB/Fastboot mode and won't load drivers so if you're on windows you'd have to enter device manager, browse for drivers, "let me pick from all available drivers" find google inc (Assuming you already have those drivers) and select android debugging interface drivers and install. After that your device should work just fine and "getvar is-userspace" should return "yes"

Brandon.Bissonnette said:
If your TWRP is newer then you can still enter fastboot from TWRP, on my device using "adb reboot fastboot" will reboot my device into TWRP then enter some weird TWRP fastboot mode. However windows doesn't seem to detect that this is a device in ADB/Fastboot mode and won't load drivers so if you're on windows you'd have to enter device manager, browse for drivers, "let me pick from all available drivers" find google inc (Assuming you already have those drivers) and select android debugging interface drivers and install. After that your device should work just fine and "getvar is-userspace" should return "yes"
Click to expand...
Click to collapse
not working....facing same problem . on oneplus 8T. can you suggest something