Hello, I recently received a Pixel 2 and was able to tick "OEM Unlocking" in developer options. However, when I go into fastboot and try to use "./fastboot flashing unlock" it gives me this: FAILED (remote: 'Flashing Unlock is not allowed')
./fastboot oem device-info gives me this:
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
Anyone ever run into this or have any suggestions?
DELETEME
Any phone(pixel2) that is an RMA replacement regardless if it was an original google edition of the pixel 2 will do this, if you searched you would have found this
Related
Hello guys
I just want help from you guys in order to change Device (MI4) tampered status TRUE to FALSE. I unlocked bootloader once by command -- fastboot oem unlock then again locked it by fastboot oem lock. But Device tampered is still showing as TRUE. I just want to change it to FALSE. Will this effect anything (warranty or something) if i don't change it. Please help???
C:\Windows\system32>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.012s]
finished. total time: 0.013s
Nobody has answered this, wow. I'm having same issue
Erase all partitions via fastboot then turn off and plug in to pc. the device will appear as HS USB QDloader. use QFil to fix. then "device tampered" is gone
Beware: may brick the phone and corrupt the imei number
I used this guide... http://en.miui.com/thread-807252-1-1.html
Every issue in the (bootloader) section is showed as false. Easy guide, easy process
Ignore...
Hello,
So I have been using my Shield Tablet just fine for the past few years but now its locked on the Nvidia logo when it boots up, I've tried going into recovery mode to factory reset but then it just hangs on "No Command" I noticed that the bootloader is locked so I got ABD and fastboot. Once I setup the tablet to register in fastboot devices, I then use 'fastboot oem unlock' like it says to from the Nvidia support forums, but it fails and gives this command. Can anyone help me out to figure out what is wrong?
.... > fastboot oem unlock
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: '(')
fastboot: error: Command failed
Any advice would be helpful
Malzra said:
Hello,
So I have been using my Shield Tablet just fine for the past few years but now its locked on the Nvidia logo when it boots up, I've tried going into recovery mode to factory reset but then it just hangs on "No Command" I noticed that the bootloader is locked so I got ABD and fastboot. Once I setup the tablet to register in fastboot devices, I then use 'fastboot oem unlock' like it says to from the Nvidia support forums, but it fails and gives this command. Can anyone help me out to figure out what is wrong?
.... > fastboot oem unlock
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: '(')
fastboot: error: Command failed
Any advice would be helpful
Click to expand...
Click to collapse
What happens when fastboot flashing unlock
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..
Hello everybody,
I need help to get my phone inbricked. Last year I installed LineageOS on my device and everything worked fine. Since I needed for some reason to relock my phone. I did via fastboot:
Bash:
fastboot oem lock
Since then my phone prints out: "The System has been destroyed ..."
I cannot flash anymore...
Code:
$ fastboot oem device-info
< waiting for any device >
...
(bootloader) Verity mode: true
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.000s]
finished. total time: 0.000s
What can I do to unlock the bootloader?