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?
Related
After i got my unlock Code from Huawei and enabled Usb Debugging mode and Oem unlock in developer options,I've Unlocked my bootloader Successfully.
my phone Started to Do a factory reset and it failed so i did it by myself manually.
after that i enabled Usb Debugging mode ,but i couldnt enable oem unlock option and i boot my phone to fastboot and Started flashing the TWRP...but it said:
Writing...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
can Someone help me to Flash recovery and root my phone?
phone info's:
Model:MHA-L29
Build num. : MHA-L29C185B138
Bootloader Unlocked
Maybe lock it and unlock again.
gm007 said:
Maybe lock it and unlock again.
Click to expand...
Click to collapse
the problem is that i cant do any operation on Bootloader including locking bootloader...
ezraiil1 said:
the problem is that i cant do any operation on Bootloader including locking bootloader...
Click to expand...
Click to collapse
C:\Users\Abolfazl\Desktop\>fastboot flash recovery 1.img
target reported max download size of 471859200 bytes
sending 'recovery' (20702 KB)...
OKAY [ 0.500s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
C:\Users\Abolfazl\Desktop\>fastboot flash recovery 1.img
target reported max download size of 471859200 bytes
sending 'recovery' (20702 KB)...
OKAY [ 0.500s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
C:\Users\Abolfazl\Desktop\>fastboot oem lock
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\Users\Abolfazl\Desktop\>fastboot oem unlock *********
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\Users\Abolfazl\Desktop\>fastboot oem lock
...
FAILED (remote: Command not allowed)
finished. total time: 0.016s
C:\Users\Abolfazl\Desktop\>fastboot devices
AHK7N16B18003212 fastboot
What version of fastboot do you have?
5[Strogino] said:
What version of fastboot do you have?
Click to expand...
Click to collapse
Minimal ADB and Fastboot
ezraiil1 said:
After i got my unlock Code from Huawei and enabled Usb Debugging mode and Oem unlock in developer options,I've Unlocked my bootloader Successfully.
my phone Started to Do a factory reset and it failed so i did it by myself manually.
after that i enabled Usb Debugging mode ,but i couldnt enable oem unlock option and i boot my phone to fastboot and Started flashing the TWRP...but it said:
Writing...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
can Someone help me to Flash recovery and root my phone?
phone info's:
Model:MHA-L29
Build num. : MHA-L29C185B138
Bootloader Unlocked
Click to expand...
Click to collapse
try to revoke usb debugging then enable again
eddmecha said:
try to revoke usb debugging then enable again
Click to expand...
Click to collapse
it doesnt work...
ezraiil1 said:
it doesnt work...
Click to expand...
Click to collapse
have you tried with a different cable & pc?how about your drivers?is it the lastest?
I had the exact same problem. Disable everything related to "Find my phone" and restart. TWRP will flash after this.
ezraiil1 said:
After i got my unlock Code from Huawei and enabled Usb Debugging mode and Oem unlock in developer options,I've Unlocked my bootloader Successfully.
my phone Started to Do a factory reset and it failed so i did it by myself manually.
after that i enabled Usb Debugging mode ,but i couldnt enable oem unlock option and i boot my phone to fastboot and Started flashing the TWRP...but it said:
Writing...
FAILED (remote: Command not allowed)
finished. total time: 0.500s
can Someone help me to Flash recovery and root my phone?
phone info's:
Model:MHA-L29
Build num. : MHA-L29C185B138
Bootloader Unlocked
Click to expand...
Click to collapse
eddmecha said:
have you tried with a different cable & pc?how about your drivers?is it the lastest?
Click to expand...
Click to collapse
Problem Solved.
Had to pay 30$ to Funkyhuawei to Flash a firmware and Unlock it again.
Problem Solved.
Had to pay 30$ to Funkyhuawei to Flash a firmware and Unlock it again.
Thank you everybody,all of you were Useless xD
love u all.
Cya!
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…
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
fastboot oem get_unlock_code
FAILED (remote: 'Unknow command')
fastboot: error: Command failed
Why is this happening?
I am using ubuntu 22.04 and have installed platform -tools _r33.0.2-linux.zip
Also attempted in Windows 10 with all the drivers with the same failure.
It is the t-mobile version and my sim card is unlocked.
Developer options, usb debugging on , oem unlocking toggled on.
the only thing that doesn't work in bootloader is oem commands.
I bought the phone from ONePlus.
It is a model IN2015
use MSM tool to revert then try again
so i am trying to unlock bootloader in my device tecno spark 8c i enter the fastboot mode and tried the command fastboot oem unlock it say message ok but nothing happenes if i try to flash the vbmeta it says the bootloader locked and need to be unlocked how to unlock it?
What happened is that you got a OK, means phone's bootloader now got unlocked.
To deal with bootloader you run Fastboot commands from the Windows shell, either CMD or PowerShell.
no it didnt get unlock it only say message ok
i tried this command fastboot getvar unlocked
which give me message unlocked:no and i am running linux so i am using its commandline working with it and as i say it didnt get unlocked what is the problem i cant figure it out
jwoegerbauer said:
What happened is that you got a OK, means phone's bootloader now got unlocked.
To deal with bootloader you run Fastboot commands from the Windows shell, either CMD or PowerShell.
Click to expand...
Click to collapse
[[email protected]]-[~]
>>> adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
[[email protected]]-[~]
>>> adb reboot bootloader
error: insufficient permissions for device
See [http://developer.android.com/tools/device.html] for more information
[[email protected]]-[~]
>>> adb reboot bootloader
[[email protected]]-[~]
>>> fastboot oem unlock
< waiting for any device >
FAILED (remote: 'Unlock bootloader fail.')
fastboot: error: Command failed
[[email protected]]-[~]
>>> fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.018s]
< waiting for any device >
Finished. Total time: 17.010s
[[email protected]]-[~]
>>> fastboot oem unlock
OKAY [ 0.001s]
Finished. Total time: 0.001s
[[email protected]]-[~]
>>> fastboot getvar unlocked
unlocked: no
Finished. Total time: 0.001s
[[email protected]]-[~]
>>>
here is the commands and the output as u see and i already enabled oem in the developer options
Reboot Android to make changes permanent
jwoegerbauer said:
Reboot Android to make changes permanent
Click to expand...
Click to collapse
u mean reboot after i did the command?
i did it nothing change
try this method
https://forum.xda-developers.com/t/is-my-life-really-worth-it.4217751/post-84295797
fastboot flashing unlock