I extracted the "fastboot oem" commands supported by the Pixel 3 XL from the firmware.
I haven't tested these, since most don't work when the bootloader is locked:
Code:
$ fastboot oem dmesg
FAILED (remote: 'Fastboot OEM command (dmesg) is not allowed when locked')
Finished. Total time: 0.081s
Note that fastboot commands can brick and damage your phone. Be careful when testing.
Here's the list of commands. You can run them with "fastboot oem <command>".
Code:
setbrightness
get_config
set_config
rm_config
get_platform_info
set_platform_info
select-display-panel
esim_erase
esim_atp
uart
off-mode-charge
sha1sum
ramdump
ramdump_sahara
rma
dump-chipid
check-hw-security
HALT
set_display_power_mode
citadel
enable-factory-lock
factory-lock
ddrtest
continue-factory
dmesg
500 Internal Server Error said:
I extracted the "fastboot oem" commands supported by the Pixel 3 XL from the firmware.
I haven't tested these, since most don't work when the bootloader is locked:
Code:
$ fastboot oem dmesg
FAILED (remote: 'Fastboot OEM command (dmesg) is not allowed when locked')
Finished. Total time: 0.081s
Note that fastboot commands can brick and damage your phone. Be careful when testing.
Here's the list of commands. You can run them with "fastboot oem <command>".
Code:
setbrightness
get_config
set_config
rm_config
get_platform_info
set_platform_info
select-display-panel
esim_erase
esim_atp
uart
off-mode-charge
sha1sum
ramdump
ramdump_sahara
rma
dump-chipid
check-hw-security
HALT
set_display_power_mode
citadel
enable-factory-lock
factory-lock
ddrtest
continue-factory
dmesg
Click to expand...
Click to collapse
Any idea what OEM citadel does? I have no clue from a precursory look.
Must be super secret. I can't find anything on that
I couldn't find anything about that either.
Pixel 3 XL, haven't crashed it, YET
its in the crosshatch source code....https://android.googlesource.com/de...bfe57aaaf2cdd656a4476bbfb5c01314a09/device.mk
i believe citadel has to do with the new Titan security chip but I could be wrong
elliwigy said:
i believe citadel has to do with the new Titan security chip but I could be wrong
Click to expand...
Click to collapse
It does seem that is the only command new to the 3 XL compared to the 2xl. The latter does not have the Titan chip
NVM, I misunderstood.
Pixel 3 XL, haven't crashed it, YET
cmh714 said:
its in the crosshatch source code....https://android.googlesource.com/de...bfe57aaaf2cdd656a4476bbfb5c01314a09/device.mk
Click to expand...
Click to collapse
Am I pretty much blind or anything, but it doesn't exist anything regarding what the 'set display power mode' OEM command does within the link to the Crosshatch source(s), or..?
Can you "turn off" Titan and then run commands? Is that something to do with Citadel?
500 Internal Server Error said:
I extracted the "fastboot oem" commands supported by the Pixel 3 XL from the firmware.
I haven't tested these, since most don't work when the bootloader is locked:
Click to expand...
Click to collapse
This is the message I am getting when trying to use anyone of the OEM commands, in this case, the possible adjustment of the display power mode.
FAILED (remote: Fastboot OEM command (set_display_power_mode) is not allowed)
finished. total time: 0.378s
PS C:\Users\Christofferwassberg\Downloads\platform-tools_r28.0.1-windows\platform-tools> fastboot oem set_display_power_
mode
Is it any secret restrictions enabled somewhere that is denying us from modifying, or checking the stats of phone, from the bootloader level?
EDIT: Yes, my bootloader is unlocked.
xFirefly93 said:
This is the message I am getting when trying to use anyone of the OEM commands, in this case, the possible adjustment of the display power mode.
FAILED (remote: Fastboot OEM command (set_display_power_mode) is not allowed)
finished. total time: 0.378s
PS C:\Users\Christofferwassberg\Downloads\platform-tools_r28.0.1-windows\platform-tools> fastboot oem set_display_power_
mode
Is it any secret restrictions enabled somewhere that is denying us from modifying, or checking the stats of phone, from the bootloader level?
EDIT: Yes, my bootloader is unlocked.
Click to expand...
Click to collapse
Yes, the device checks whether the PRODUCTION fuse, in our case, likely just QCOM_SEC_BOOT is blown, and if it is it restricts a whole number of commands/functions.
npjohnson said:
Yes, the device checks whether the PRODUCTION fuse, in our case, likely just QCOM_SEC_BOOT is blown, and if it is it restricts a whole number of commands/functions.
Click to expand...
Click to collapse
Sounds like something that only Samsung would add, but Google? Nah..
xFirefly93 said:
Sounds like something that only Samsung would add, but Google? Nah..
Click to expand...
Click to collapse
That wasn't said in a questioning way lol -- its just how it is.
Every non-Chinese phone has Qualcomm Secure Boot enabled by that exact means (the SEC_BOT Fuse row). If you Google it, you'll find such. It's why we can't run custom bootloader's (exempting S-OFF HTC devices which are an odd and interesting case where QCOM secureboot only verfies very specific chunks of the bootchain the user doesn't normally touch).
QCOM secure boot is literally the industry standard lol - using the production state to limit OEM commands is new as of the Pixel 2, and correctly restricting them is new to the 3 series.
Could you maybe provide some info on how you extracted these commands from the firmware? Might be useful to me and others as well.
npjohnson said:
Any idea what OEM citadel does? I have no clue from a precursory look.
Click to expand...
Click to collapse
This is from sargo. I tried some of the other oem commands that sounded non-destructive, but got a lot of invalid oem command errors.
I didn't try any of these citadel commands, but they do sound interesting. I have no idea if they will apply to the blueline/crosshatch.
Code:
[email protected]:# fastboot oem citadel
...
(bootloader) citadel <command>
(bootloader) Commands:
(bootloader) rescue Try to rescue Citadel
(bootloader) state Print current Citadel state
(bootloader) reset Reset Citadel
(bootloader) reset-locks Reset AVB locks
(bootloader) version Print citadel OS version
(bootloader) reprovision Reprovision device after a RMA unlock
(bootloader) suzyq on|off Enable or disable SuzyQable
FAILED (remote failure)
finished. total time: 0.060s
Does anyone know how to use the citadel commands?
Im trying to restore a bricked 3a. so far here are my attempts
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe oem citadel
(bootloader) citadel <command>
(bootloader) Commands:
(bootloader) rescue Try to rescue Citadel
(bootloader) state Print current Citadel state
(bootloader) reset Reset Citadel
(bootloader) reset-locks Reset AVB locks
(bootloader) version Print citadel OS version
(bootloader) reprovision Reprovision device after a RMA unlock
(bootloader) suzyq on|off Enable or disable SuzyQable
FAILED (remote: '')
fastboot: error: Command failed
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe oem citadel rescue
FAILED (remote: 'no staged data, use fastboot stage <file>')
fastboot: error: Command failed
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe stage bootloader-sargo-b4s4-0.2-5402313.img
Sending 'bootloader-sargo-b4s4-0.2-5402313.img' (8349 KB) OKAY [ 0.355s]
Finished. Total time: 0.413s
PS C:\Program Files (x86)\Minimal ADB and Fastboot> .\fastboot.exe oem citadel rescue
(bootloader) Recovering citadel - it may take a couple of minutes
FAILED (remote: 'failed to rescue citadel Bad Buffer Size')
fastboot: error: Command failed
PS C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
zimmie said:
Does anyone know how to use the citadel commands?
Im trying to restore a bricked 3a. so far here are my attempts
Click to expand...
Click to collapse
Did you ever manage to make this work? I'm in the same situation
Related
Hi, i just bought a Google Pixel from Ebay an tried to install an factory image for Android 9 from the Google Website. After fastboot the flash-all.sh (ive got Ubuntu) it got stuck a on the bootscreen (The Google Logo flashes in an instance and the Screen goes black again). Unfortunally the device is locked again (bootloader ist locked), so adb is not working. fastboot works but when i install some other factory images from the google website the problem with the flashing bootscreen reappears.
Loading into bootloader works:
Product/Variant: sailfish-US-PVT
Serial Number FA72H0300560
CPU: MSM8996SG-AB 0x10001
UFS: 32 GB Samsung
DRAM:4096MB Hynix LPDDR4
Boot-slot: a
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
Could anyone help?
Thanks in advance.
Not sure but I think U can try booting into TWRP using "fastboot flash recovery twrp" command in CMD and than switch boot slot to b, my pixel is in the same situation - I can't boot into slot a and switching to b works
oh sry, the command is "fastboot boot path/to/twrp.img"
Thanks for your help, but it didn't work.
When I try to fastboot with following commands, it says:
sudo ./fastboot boot twrp-3.2.3-1-sailfish.img
Code:
Downloading 'boot.img' OKAY [ 0.785s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 0.963s
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...
Double-check the checksum of the downloaded file.
Open the flash-all.sh file in a text editor, and manually run each of the flash commands individually. See if any of them throw an error.
You might also try to install the OTA.
I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....
ArchArch said:
I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....
Click to expand...
Click to collapse
You need to re-unlock your bootloader first, then. Try fastboot flashing unlock .
No luck.
sudo ./fastboot flashing unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.007s
sudo ./fastboot oem unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.038s
ArchArch said:
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...
Click to expand...
Click to collapse
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.
Levan_i said:
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.
Click to expand...
Click to collapse
He's using linux. The reason his flashes have been unsuccessful is because the bootloader is locked.
Tanks for your efforts so far...
Just for clarification: The initial plan was to root my device, according to the XDA-Guide for rooting an Pixel XL Android 9.0 (with the Files for my "Sailfish"-Pixel) https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866
First when I bought the Pixel the "OEM Unlock"-Option in the Developers-Menu was greyed out.
So i tried out, beneath some other guides, the XDA-Guide for unlocking a Verizon Pixel and it worked. https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
So I thought its an VerizonPixel, installed an Verizon Image from the Google Website, got always the message at bootup that an unlocked bootloader is some sort of threat, closed the Bootloader and the flashing bootscreen-problem began…
Fingerprint lost, I backed up persist in advance, so I restore it by
fastboot flash persist [INSERT YOUR PERSIST.IMG HERE]
not worked,prompted for "Flashing is not allowed for Critical Partitions"
then I tried
adb shell
su
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
I checked /mnt/vendor/persist,files were successfully extracted.
However,the problem still occurred.
Appreciate for any helps.
ChuyanFang said:
Fingerprint lost, I backed up persist in advance, so I restore it by
fastboot flash persist [INSERT YOUR PERSIST.IMG HERE]
not worked,prompted for "Flashing is not allowed for Critical Partitions"
then I tried
adb shell
su
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
I checked /mnt/vendor/persist,files were successfully extracted.
However,the problem still occurred.
Appreciate for any helps.
Click to expand...
Click to collapse
Enter this command first: fastboot flashing unlock_critical
Sent from my OnePlus KB2007 using XDA Labs
jwarrior319 said:
Enter this command first: fastboot flashing unlock_critical
Sent from my OnePlus KB2007 using XDA Labs
Click to expand...
Click to collapse
Thanks for ur reply.
It still doesn't work.
C:\Program Files (x86)\OnePlus Mobile>fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.005s
C:\Program Files (x86)\OnePlus Mobile>fastboot flashing unlock
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.003s
I checked the unlocked status then:
C:\Program Files (x86)\OnePlus Mobile>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.006s]
Finished. Total time: 0.007s
*never mind*
ChuyanFang said:
Thanks for ur reply.
It still doesn't work.
C:\Program Files (x86)\OnePlus Mobile>fastboot flashing unlock_critical
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.005s
C:\Program Files (x86)\OnePlus Mobile>fastboot flashing unlock
FAILED (remote: Device already : unlocked!)
Finished. Total time: 0.003s
I checked the unlocked status then:
C:\Program Files (x86)\OnePlus Mobile>fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.006s]
Finished. Total time: 0.007s
Click to expand...
Click to collapse
Hmm, it wont allow you to unlock critical. Idk how to fix that.
You could try fastboot oem flashing unlock_critical or fastboot oem unlock_critical
Sent from my OnePlus KB2007 using XDA Labs
Good day readers!
This is my first post in this forum, I own a Motorola One Power and I have been trying to unlock my bootloader in order to install TWRP for the past 2 days. When ever i run the command,
> fastboot oem get_unlock_data
terminal shell gives confusing errors.
eg:
$ fastboot oem get_unlock_data
(bootloader) slot-counttas: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixe: not found
...
(bootloader) 'get_unlock_da' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.000s
or
$ fastboot oem get_unlock_data
(bootloader) slot-co: not found
(bootloader) slot-suffi: not found
...
(bootloader) 'get_unlock_datas' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.000s
Notice that I didn't write get_unlock_da yet it still gives such errors. I am unable to unlock my phone and have no clue how to deal with this.
For the love of God, someone help me with this.
Thanks
ps: other commands like fastboot get_var all does the similar thing. Only command that does work is fastboot devices.
bhaunda said:
Good day readers!
This is my first post in this forum, I own a Motorola One Power and I have been trying to unlock my bootloader in order to install TWRP for the past 2 days. When ever i run the command,
> fastboot oem get_unlock_data
terminal shell gives confusing errors.
eg:
$ fastboot oem get_unlock_data
(bootloader) slot-counttas: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixe: not found
...
(bootloader) 'get_unlock_da' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.000s
or
$ fastboot oem get_unlock_data
(bootloader) slot-co: not found
(bootloader) slot-suffi: not found
...
(bootloader) 'get_unlock_datas' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.000s
Notice that I didn't write get_unlock_da yet it still gives such errors. I am unable to unlock my phone and have no clue how to deal with this.
For the love of God, someone help me with this.
Thanks
ps: other commands like fastboot get_var all does the similar thing. Only command that does work is fastboot devices.
Click to expand...
Click to collapse
Do you have chef/XT1942?
There is a forum for this device
Motorola One Power
The Motorola One Power is a 6.2" phone with a 1080x2246p resolution display. The Snapdragon 636 chipset is paired with 3/4GB of RAM and 32/64GB of storage. The main camera is 16+5MP and the selfie camera is 12MP. The battery has a 5000mAh capacity.
forum.xda-developers.com
and a bootloader unlocking thread
[GUIDE] Motorola One Power Unlock/Relock Bootloader,Flashing Custom Recovery,Rooting
UNLOCKING THE BOOTLOADER WARNING:- UNLOCKING YOUR BOOTLOADER VOIDS YOUR WARRANTY.PROCEED AT YOUR OWN RISK. NOTE: Unlocking the bootloader will Wipe/ factory reset your device, and will delete all personal data from your device such as apps...
forum.xda-developers.com
You are using Linux?
sd_shadow said:
Do you have chef/XT1942?
There is a forum for this device
Motorola One Power
The Motorola One Power is a 6.2" phone with a 1080x2246p resolution display. The Snapdragon 636 chipset is paired with 3/4GB of RAM and 32/64GB of storage. The main camera is 16+5MP and the selfie camera is 12MP. The battery has a 5000mAh capacity.
forum.xda-developers.com
and a bootloader unlocking thread
[GUIDE] Motorola One Power Unlock/Relock Bootloader,Flashing Custom Recovery,Rooting
UNLOCKING THE BOOTLOADER WARNING:- UNLOCKING YOUR BOOTLOADER VOIDS YOUR WARRANTY.PROCEED AT YOUR OWN RISK. NOTE: Unlocking the bootloader will Wipe/ factory reset your device, and will delete all personal data from your device such as apps...
forum.xda-developers.com
You are using Linux?
Click to expand...
Click to collapse
So should I delete this thread?
> Yes its chef XT1942-2 64GB PVT
> yes I am using Linux, but the same thing happens in windows as well.
fastboot flashing get_unlock_ability
fastbootflashing unlock
fastboot flashing lock
fastboot flashing unlock_critical
fastboot flashing lock_critical
fastboot oem enable-charger-screen
fastboot oem disable-charger-screen
fastboot oem off-mode-charge
fastboot oem select-display-panel
fastboot oem device-info
fastboot reboot-fastboot
fastboot reboot-bootloader
fastboot oem gpt-info
fastboot oem adb_enable
fastboot oem shutdown
fastboot oem get-dtid
fastboot oem get-hwid
fastboot oem get-prjid
fastboot oem get-skuid
fastboot oem get-rfid
fastboot oem get-featureid
fastboot oem get-jtagid
fastboot oem get-bcid
fastboot oem get-secdispid
fastboot oem get-cpuidhash
fastboot oem get-toolid
fastboot oem isn-info
fastboot oem ssn-info
fastboot oem system-info
fastboot oem get_build_version
fastboot oem get-batcap
fastboot oem get-batvol
fastboot oem get-bootcount
fastboot oem factory-reset
fastboot oem factory-reset2
fastboot oem reboot-recovery
fastboot oem set-permissive
fastboot oem enter-dload
fastboot oem check-s3
fastboot oem EnterShippingMode
fastboot oem check-nrfuse
fastboot oem check-fuse
fastboot oem fuse-info
fastboot oem show-barcode
fastboot oem checksetupwizard
fastboot oem asus-csc_lk
fastboot oem rsa_test_
fastboot oem crc32_
fastboot oem hash_
fastboot oem gen-random
fastboot oem auth-hash
fastboot oem auth-hash_2
fastboot oem auth-hash_3
fastboot oem get-imeiauth
fastboot oem slot_b_enable
fastboot oem get-verify_vbmeta_ret
fastboot oem update-cmdline_
fastboot oem backup-fac
fastboot oem restore-fac
fastboot oem get-pmic-reg_
fastboot oem write-pmic-reg_
fastboot oem reset-boot_count
fastboot oem reset-lock_count
fastboot oem reset-a_retry_count
fastboot oem reset-a_unbootable_count
fastboot oem reset-b_retry_count
fastboot oem reset-b_unbootable_count
fastboot oem force-hwid_
fastboot oem reset-dev_info
fastboot oem reset-auth2
fastboot oem reset-auth3
fastboot oem disable-verity
fastboot oem enable-verity
fastboot oem enable-vbmeta
fastboot oem read-vbmeta
fastboot oem read-rollback
fastboot oem reset-rollback
hi, which one i can use to unlock my bootloader?
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Device authorized: false
(bootloader) Device authorized2: false
(bootloader) WaterMask unlock: N
(bootloader) XBL: Post-CS3-30-ZS673KS-user
(bootloader) ABL: Post-CS3-25-WW-user
(bootloader) CID: ASUS
(bootloader) COUNTRY: WW
(bootloader) Project: ZS673KS
(bootloader) DT ID: 100
(bootloader) SB: Y
(bootloader) SBNR: Y
(bootloader) DDR Manufacturer ID: 1
(bootloader) DDR Device Type: 8
(bootloader) TotalDMCounter: 0
(bootloader) DMCounter: 0
(bootloader) SlotARetryCounter: 0
(bootloader) SlotAUnbootableCounter: 0
(bootloader) SlotBRetryCounter: 0
(bootloader) SlotBUnbootableCounter: 0
(bootloader) BOOT_COUNT: 32
(bootloader) LOCK_COUNT: 1
(bootloader) Check_APDP: 0
(bootloader) rawdump_en: false
(bootloader) Current Slot: b
(bootloader) Slot_b bootable: Bootable
(bootloader) AVB Verity: Enable
(bootloader) Verify vbmeta ret: 0
(bootloader) ABL_FTM: FALSE
(bootloader) SNAPSHOT-UPDATE-STATUS: none
OKAY [ 0.080s]
finished. total time: 0.080s
Following the answer.
fastboot oem device-info does not work for me
Code:
> fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
And i get the same result for any fastboot oem command, even when i type random things
Almost every "generic" commands such as fastboot flashing get_unlock_ability does not work either, giving me a different message
Code:
> fastboot flashing get_unlock_ability
FAILED (remote: 'Unrecognized command flashing get_unlock_ability')
fastboot: error: Command failed
The only commands that worked so far are fastboot reboot-fastboot and fastboot reboot-bootlader
Code:
> fastboot reboot-fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 8.642s
I have a WW device ( i think its a new one ), and i never unlocked the bootloader before, so am i missing something here ??
I really want to check those values to confirm that the device hasnt been unlocked and a few other things.
zvrsd said:
fastboot oem device-info does not work for me
Code:
> fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
And i get the same result for any fastboot oem command, even when i type random things
Almost every "generic" commands such as fastboot flashing get_unlock_ability does not work either, giving me a different message
Code:
> fastboot flashing get_unlock_ability
FAILED (remote: 'Unrecognized command flashing get_unlock_ability')
fastboot: error: Command failed
The only commands that worked so far are fastboot reboot-fastboot and fastboot reboot-bootlader
Code:
> fastboot reboot-fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 8.642s
I have a WW device ( i think its a new one ), and i never unlocked the bootloader before, so am i missing something here ??
I really want to check those values to confirm that the device hasnt been unlocked and a few other things.
Click to expand...
Click to collapse
Your phone is tencent edition or not?
HunterTik said:
Your phone is tencent edition or not?
Click to expand...
Click to collapse
No, its the ROG edition
zvrsd said:
No, its the ROG edition
Click to expand...
Click to collapse
Then use official unlock mathod hope it works for you.
zvrsd said:
fastboot oem device-info does not work for me
Code:
> fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
And i get the same result for any fastboot oem command, even when i type random things
Almost every "generic" commands such as fastboot flashing get_unlock_ability does not work either, giving me a different message
Code:
> fastboot flashing get_unlock_ability
FAILED (remote: 'Unrecognized command flashing get_unlock_ability')
fastboot: error: Command failed
The only commands that worked so far are fastboot reboot-fastboot and fastboot reboot-bootlader
Code:
> fastboot reboot-fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 8.642s
I have a WW device ( i think its a new one ), and i never unlocked the bootloader before, so am i missing something here ??
I really want to check those values to confirm that the device hasnt been unlocked and a few other things.
Click to expand...
Click to collapse
Did this work for you? I have the exact same problem even after using the official bootloader unlock..
zvrsd said:
fastboot oem device-info does not work for me
Code:
> fastboot oem device-info
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
And i get the same result for any fastboot oem command, even when i type random things
Click to expand...
Click to collapse
You're in userspace fastboot. Reboot to the bootloader
The one you get to by using volume up and power is bootloader
From bootloader `fastboot reboot fastboot` -> userspace fastboot
From userspace fastboot, select reboot bootloader -> bootloader
`adb reboot fastboot` -> userspace fastboot
`adb reboot bootloader` -> bootloader
The bootloader also needs to be unlocked for most commands to work.
Andrologic said:
Did this work for you? I have the exact same problem even after using the official bootloader unlock..
Click to expand...
Click to collapse
You might want to check this https://forum.xda-developers.com/t/rog5-fastboot-commands.4255537/post-85135791
After following his instructions, i was able to make the commands work.
Big thanks to him !!
zvrsd said:
You might want to check this https://forum.xda-developers.com/t/rog5-fastboot-commands.4255537/post-85135791
After following his instructions, i was able to make the commands work.
Big thanks to him !!
Click to expand...
Click to collapse
Thanks. Found it - going to try..
Trying to root my phone to flash Alexndr ROM. Phone is Google purchased (NOT verizon) pixel 2 G011A . USB Debug and OEM unlocking are toggled "on."
From the bootloader screen, and connected to the computer, this is the result from the following commands:
fastboot flashing unlock
FAILED (remote: 'Flashing Unlock is not allowed') fastboot: error: Command failed
Click to expand...
Click to collapse
fastboot flashing unlock_critical
FAILED (remote: 'unknown command') fastboot: error: Command failed
Click to expand...
Click to collapse
It is communicating with the device:
fastboot devices
{{device serial number}} fastboot
Click to expand...
Click to collapse
and unlocking the bootloader seems to be enabled on the phone
fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
OKAY [ 0.000s]
Finished. Total Time: 0.000s
Click to expand...
Click to collapse
I've tried all the USB ports on several computers with both Win10 and linux, with the same result.
On the phone itself, developer options are enabled, USB debugging is enabled, and OEM unlocking is enabled. Curiously, OEM unlocking becomes grayed out and disabled after enough failed attempts, but I've been fixing this with a factory reset.
The Android version is 11, build RP1A.201005.004A1
What am I missing here? Why wont this bootloader unlock? Thanks!
I have the same problem. Can someone please explain how to fix this?