If anyone can give me the following information it would be useful in adding the Pixel C to the Unified Android Toolkit.
1. Is the "Allow OEM unlock" option present in the developer options (needs checking before bootloader can be unlocked)?
2. What is the key combo to boot the device to fastboot mode manually?
3. Is it a standard bootloader screen (i.e. down volume and power to boot to recovery)?
4. What instructions do you get on the device after running fastboot flashing unlock to unlock the bootloader?
If anyone can fill in any of the information or add anything that would be useful then please do..
Mark.
1. Is the "Allow OEM unlock" option present in the developer options (needs checking before bootloader can be unlocked)?
A: Yes
2. What is the key combo to boot the device to fastboot mode manually?
A: Power + Volume down (when in landscape). The bootloader has an option to "Switch to fastboot mode" which you select with volume down and then the power button. It will switch to a screen that says "Waiting for fastboot command..." with no option to go back.
3. Is it a standard bootloader screen (i.e. down volume and power to boot to recovery)?
A: Yes. Here is a picture of it: https://goo.gl/photos/YQ5FVKf6HAWQWwd5A
4. What instructions do you get on the device after running fastboot flashing unlock to unlock the bootloader?
A: You are given the option to press power to unlock the bootloader or volume down to cancel. The device then says the bootloader is unlocked and it will reboot in 30 seconds. After that, you get the recovery robot with an "Erasing" dialog.
oRAirwolf said:
1. Is the "Allow OEM unlock" option present in the developer options (needs checking before bootloader can be unlocked)?
A: Yes
2. What is the key combo to boot the device to fastboot mode manually?
A: Power + Volume down (when in landscape). The bootloader has an option to "Switch to fastboot mode" which you select with volume down and then the power button. It will switch to a screen that says "Waiting for fastboot command..." with no option to go back.
3. Is it a standard bootloader screen (i.e. down volume and power to boot to recovery)?
A: Yes. Here is a picture of it: https://goo.gl/photos/YQ5FVKf6HAWQWwd5A
4. What instructions do you get on the device after running fastboot flashing unlock to unlock the bootloader?
A: You are given the option to press power to unlock the bootloader or volume down to cancel. The device then says the bootloader is unlocked and it will reboot in 30 seconds. After that, you get the recovery robot with an "Erasing" dialog.
Click to expand...
Click to collapse
Thanks for the quick response. Just need a bit more info about the actual bootloader.
Do you know if fastboot commands can be sent after booting to the bootloader mode? Or do you have to boot to bootloader and then select "switch to fastboot" to accept an input? If you have used adb with the device could you run adb reboot bootloader and tell me if the device goes to the bootloader or the fastboot screen.
I also need error messages when unlocking. If you (or someone else) could run the following that would be great.
1. With "Allow OEM unlock" NOT ticked, boot to fastboot and run fastboot flashing unlock >> what is the exact error message.
2. With the device already bootloader unlocked, boot to fastboot and run fastboot flashing unlock >> what is the exact error message.
I think thats all thats needed for now to make a basic toolkit for the Pixel C to unlock, backup data, flash stock image, etc. If a custom recovery becomes available then it will then be very simple to add a root process.
Mark.
I am heading to bed but if nobody has replied before I get to work this afternoon, I will be happy to get answers to the rest of your questions.
oRAirwolf said:
I am heading to bed but if nobody has replied before I get to work this afternoon, I will be happy to get answers to the rest of your questions.
Click to expand...
Click to collapse
Thanks I appreciate it.
Mark.
mskip said:
Thanks for the quick response. Just need a bit more info about the actual bootloader.
Do you know if fastboot commands can be sent after booting to the bootloader mode? Or do you have to boot to bootloader and then select "switch to fastboot" to accept an input? If you have used adb with the device could you run adb reboot bootloader and tell me if the device goes to the bootloader or the fastboot screen.
I also need error messages when unlocking. If you (or someone else) could run the following that would be great.
1. With "Allow OEM unlock" NOT ticked, boot to fastboot and run fastboot flashing unlock >> what is the exact error message.
2. With the device already bootloader unlocked, boot to fastboot and run fastboot flashing unlock >> what is the exact error message.
I think thats all thats needed for now to make a basic toolkit for the Pixel C to unlock, backup data, flash stock image, etc. If a custom recovery becomes available then it will then be very simple to add a root process.
Mark.
Click to expand...
Click to collapse
If I boot into the bootloader, I am unable to issue fastboot commands until I select "Switch to fastboot mode."
Using ADB, when I issue the "adb reboot bootloader" command when the device is on normally, it goes directly to the fastboot screen and says "Waiting for fastboot command..."
When "Allow OEM unlock" is not ticked and I boot to fastboot and issue "fastboot flashing unlock," I get no error message on the device, but I do see the following in the command prompt:
Code:
C:\>fastboot flashing unlock
...
FAILED (remote: Device already unlocked)
finished. total time: 0.005s
When "Allow OEM unlock" is not ticked, the bootloader is unlocked, I boot to fastboot, and issue "fastboot flashing lock," I get no error message on the device, but I do see the following in the command prompt:
Code:
C:\>fastboot flashing lock
...
FAILED (remote: Enable OEM unlock is not set)
finished. total time: 0.020s
When the bootloader is unlocked and in the fastboot screen, if I issue "fastboot flashing unlock," I get no error message on the device, but I do see the following in the command prompt:
Code:
C:\>fastboot flashing unlock
...
FAILED (remote: Device already unlocked)
finished. total time: 0.003s
Let me know if there is anything else you need.
Related
Hi guys,
I flashed stock back to my phone and relocked the bootloader by "fastboot oem lock".
I been stuck with this for the last 2 days searching for solution on how to get my phone unlocked and rooted again.
This is what I have tried so far:
1. Rumrunner 1.10.605.10 and 1.10.605.15 firmware (flashed 1.10.605.10 and updated to 15) - Run just fine, but it does not change anything on the phone. Still shows RELOCKED S-off and NO Root.
2. Firewater (temp-root method) - Temproot: Root acquired. Firewater: "there really isn't a helluva lot to do here. bye bye"
3. Flashing CM recovery - failed remote not allowed
Could someone please help me to get back Root access and UNLOCK my phone?
Thank you in advance.
If your s-off, all you have to do is fastboot flash a custom recovery.
Code:
fastboot flash recovery name_of_recovery_file.img
Then flash superuser zip thru recovery. Then you will be rooted. Also it is a myth that you need to relock the bootloader to do an ruu, so that wasnt really needed. Not sure exactly how to unlock the bootloader again.
cmlusco said:
If your s-off, all you have to do is fastboot flash a custom recovery.
Code:
fastboot flash recovery name_of_recovery_file.img
Then flash superuser zip thru recovery. Then you will be rooted. Also it is a myth that you need to relock the bootloader to do an ruu, so that wasnt really needed. Not sure exactly how to unlock the bootloader again.
Click to expand...
Click to collapse
Thank you for your reply.
I have tried to flash recovery several times, and both TWRP and CWM gives the same error: FAILED remote not allowed
Code:
sending 'recovery' (8784 KB)...
OKAY [ 1.097s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.134s
I tried the following recoveries:
openrecovery-twrp-2.6.3.3-m7vzw
recovery-clockwork-6.0.4.4-m7vzw
recovery-clockwork-6.0.4.7-m7vzw
recovery-clockwork-touch-6.0.4.5-m7vzw
recovery-clockwork-touch-6.0.4.7-m7vzw
NELORAO said:
Thank you for your reply.
I have tried to flash recovery several times, and both TWRP and CWM gives the same error: FAILED remote not allowed
Code:
sending 'recovery' (8784 KB)...
OKAY [ 1.097s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.134s
I tried the following recoveries:
openrecovery-twrp-2.6.3.3-m7vzw
recovery-clockwork-6.0.4.4-m7vzw
recovery-clockwork-6.0.4.7-m7vzw
recovery-clockwork-touch-6.0.4.5-m7vzw
recovery-clockwork-touch-6.0.4.7-m7vzw
Click to expand...
Click to collapse
Ok try this then.
1. Download this file http://vzw1files.dyndns.org/RECOVERIES/twrp/Twrp_2.6.3.4_RUU_Mode.zip, and place it on your pc in the same folder as fastboot.exe and adb.exe. Rename it to recovery.zip
2. Connect the phone to the pc and open a cmd prompt to where the files are, and type the following.
Code:
adb reboot bootloader
Wait for hboot.
Code:
fastboot oem rebootRUU
Wait for grey HTC logo.
Code:
fastboot flash zip recovery.zip
Wait for cmd window to say it has finished.
Code:
fastboot reboot-bootloader
3. Hit power button to select bootloader, and then use the power button again to select recovery.
If all is well you should boot to TWRP 2.6.3.4. Then flash Superuser http://vzw1files.dyndns.org/Superuser/superuser.zip and you will be rooted.
.
NELORAO said:
Hi guys,
I flashed stock back to my phone and relocked the bootloader by "fastboot oem lock".
I been stuck with this for the last 2 days searching for solution on how to get my phone unlocked and rooted again.
This is what I have tried so far:
1. Rumrunner 1.10.605.10 and 1.10.605.15 firmware (flashed 1.10.605.10 and updated to 15) - Run just fine, but it does not change anything on the phone. Still shows RELOCKED S-off and NO Root.
2. Firewater (temp-root method) - Temproot: Root acquired. Firewater: "there really isn't a helluva lot to do here. bye bye"
3. Flashing CM recovery - failed remote not allowed
Could someone please help me to get back Root access and UNLOCK my phone?
Thank you in advance.
Click to expand...
Click to collapse
Enable USB Debugging in Settings.
To do so, go to build information and tap it 7 times.
This will enable the Developer options in settings.
In there, check the box for Usb Debugging.
You should then be able to fastboot flash the recovery as per usual.
Good luck! :good:
cmlusco said:
Ok try this then.
1. Download this file http://vzw1files.dyndns.org/RECOVERIES/twrp/Twrp_2.6.3.4_RUU_Mode.zip, and place it on your pc in the same folder as fastboot.exe and adb.exe. Rename it to recovery.zip
2. Connect the phone to the pc and open a cmd prompt to where the files are, and type the following.
Code:
adb reboot bootloader
Wait for hboot.
Code:
fastboot oem rebootRUU
Wait for grey HTC logo.
Code:
fastboot flash zip recovery.zip
Wait for cmd window to say it has finished.
Code:
fastboot reboot-bootloader
3. Hit power button to select bootloader, and then use the power button again to select recovery.
If all is well you should boot to TWRP 2.6.3.4. Then flash Superuser http://vzw1files.dyndns.org/Superuser/superuser.zip and you will be rooted.
.
Click to expand...
Click to collapse
Dude, there just aren't enough words to say thank you.
Again, thank you so much, everything works like a charm now.
santod040 said:
Enable USB Debugging in Settings.
To do so, go to build information and tap it 7 times.
This will enable the Developer options in settings.
In there, check the box for Usb Debugging.
You should then be able to fastboot flash the recovery as per usual.
Good luck! :good:
Click to expand...
Click to collapse
Thank you, I was finally able to flash your KitKat Rom that I have been dreaming for the last 3 days. :laugh:
Again, thank you so much.
cmlusco said:
Ok try this then.
1. Download this file, and place it on your pc in the same folder as fastboot.exe and adb.exe. Rename it to recovery.zip
2. Connect the phone to the pc and open a cmd prompt to where the files are, and type the following.
Code:
adb reboot bootloader
Wait for hboot.
Code:
fastboot oem rebootRUU
Wait for grey HTC logo.
Code:
fastboot flash zip recovery.zip
Wait for cmd window to say it has finished.
Code:
fastboot reboot-bootloader
3. Hit power button to select bootloader, and then use the power button again to select recovery.
If all is well you should boot to TWRP 2.6.3.4. Then flash Superuser and you will be rooted.
.
Click to expand...
Click to collapse
Holy crap dude. I thought my phone was bricked. Thank you so much for that!
I Was trying to unlock bootloader on my Rogers(CAN) HTC One M9 (himault-att) but now my phone is unresponsive at the confirm unlock bootloader screen.
The commands I ran to get to the screen were:
Code:
fastboot oem rebootRUU
fastboot oem get_identifier_key
fastboot flash unlocktoken Unlock_Code.bin
After the last command my phone went to the Unlock bootloader? screen asking me to confirm or deny unlocking my bootloader and is no longer responding to fastboot or hardware keys.
All fastboot commands timeout after 5 seconds and return
Code:
FAILED (command write failed (Unknown Error))
however fastboot reboot times out at 5 seconds and returns finished. fastboot devices obviously shows my device as attached. My current plan is to wait for the battery to drain (it sucks not being able to pull the battery) and then attempt a normal boot. Any advice?
be.plante said:
I Was trying to unlock bootloader on my Rogers(CAN) HTC One M9 (himault-att) but now my phone is unresponsive at the confirm unlock bootloader screen.
The commands I ran to get to the screen were:
Code:
fastboot oem rebootRUU
fastboot oem get_identifier_key
fastboot flash unlocktoken Unlock_Code.bin
After the last command my phone went to the Unlock bootloader? screen asking me to confirm or deny unlocking my bootloader and is no longer responding to fastboot or hardware keys.
All fastboot commands timeout after 5 seconds and return
Code:
FAILED (command write failed (Unknown Error))
however fastboot reboot times out at 5 seconds and returns finished. fastboot devices obviously shows my device as attached. My current plan is to wait for the battery to drain (it sucks not being able to pull the battery) and then attempt a normal boot. Any advice?
Click to expand...
Click to collapse
Hold power and volume up till the phone reboots and try again
Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock
I used TWRP and SuperSU to root and modify the buildprops to enable and get an early look at the windowing in Android N beta on my Pixel C release 5 ahead of time.
When Release 5 NPD90G was available I decided to flash back to stock from Developer Preview 4 NPD56N rooted with SuperSU and flashed with TWRP. I like root - I run Ubuntu and Win 7. I don't mind running a rooted device if it doesn't have all my work and financial data. When the final N release is out, the Pixel C will become my work machine. It's almost there.
I'm naturally paranoid. I change my long passwords frequently and use 2 factor authentication for everything. So if I can, I'll take a stock release. See my instructions for wiping Android devices: How to wipe an Android Phone: the paranoid editon
I could not flash the NPD90G stock bootloader because of an error "remote: unsupported command"
Here's how I fixed it.
Updated the SDK manager including SDK Tools and USB drivers.
With the Pixel C in recovery mode, {hold the power key and volume down}
In TWRP mount System and reboot to recovery
>ADB Shell.
From ADB Shell I ran
>fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable Fast boot.
Then I changed from TWRP to Fastboot mode {power button plus hold the volume up button}
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
See Note 1. Below
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
Note 1.
The first time through I flashed the following line items which resulted in the resting robot Andi. I don't think I needed to do this, but if the above instructions don't work, run the following before continuing for {flash bootloader bootloader-dragon-google_smaug.7900.27.0.img}
>flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot reboot-bootloader
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img
Twrp can't flash
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Tugio said:
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Click to expand...
Click to collapse
When in fastboot mode, use:
Code:
fastboot boot twrp-local-file-on-computer.img
DanBUK said:
When in fastboot mode, use:
Click to expand...
Click to collapse
It's nice of you to help a fellow XDA user. But I suspect he's already solved his problem of three months ago.....
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
lllopa said:
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
Click to expand...
Click to collapse
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Make sure you have the latest version of fastboot and adb. I get these errors almost every month if I don't update.
https://developer.android.com/studio/releases/platform-tools.html
@stevep2007, thank you so much! I've been dealing with this "remote: unsupported command" nonsense for days now after trying to revert back to an older Oreo version of Lineage. This did the trick!
How can I solve the problem when my Pixel C is not unlocked? My Pixel made an update and after installing the Update I got the green little man. Now I have no Chance to activate USB debugging etc. Its also not possible to install twrp.img
How can I go to ADB shell with locked bootloader? Or isn't it possible?
Fastboot devices shows me my tablet. ADB devices also show my tablet with "sideload".
But every try to flash my Pixel fails. I alway get the message .... remote: unknown command.......fastboot error: command failed
flash-all.bat showes that all "*.img are missing" error: command failed... unknown command etc.......
So any idea to get my Pixel working again? ADB shell would make it I think. But how with locked bootloader.
_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
This did it for me!! Thanks much. I also updated platform-tools at the same time, who knows which did it
_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
bernardomarx said:
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
Click to expand...
Click to collapse
Sorry replied incorrectly
Days past I successfully unlocked the bootloader on my girlfriend's Taimen handset, flashed TWRP etc etc. No hitches whatsoever. I bought another for myself via the Google Store.
I booted it up today. As was on hers, OEM Unlock is prevented until I allow the handset to update to 8.1.
Done. OEM unlock then accessible and enabled.
I used my girlfriend's same PC with the same Minimal ADB and Fastboot, rebooted to fastboot and execute
Code:
fastboot flashing unlock_critical
Are you sure? ...volume up/down and power button to commit. Done. The unlock appeared successful as it rebooted to the out of box setup routine again.
I transferred the TWRP zip to the handset and rebooted to fastboot. Upon executing the command to temp boot TWRP from the IMG file fastboot
Code:
boot path "C:\Program Files (x86)\Minimal ADB and Fastboot\twrp-3.2.1-2-taimen.img"
I got the following response...
Code:
downloading 'boot.img'...
OKAY [ 0.870s]
booting...
FAILED (remote: Can not boot in Lock State)
finished. total time: 0.873s
Sure enough I look down at the handset and the fastboot menu reflects it's locked again. Weird.
I reboot and check OEM unlock. It reflects OEM unlock still toggled on. I go back to fastboot and again execute
Code:
fastboot flashing unlock_critical
Code:
FAILED (remote: Device already : unlocked!)
finished. total time: 0.002s
This is despite fastboot clearly showing "device state - locked"
I regress to dev options and toggle OEM unlock off. Reboot. Toggle OEM Unlock back on.
Same ill behavior.
Am I missing something??
try fastboot flashing unlock
depending on bootloader version you no longer need to fastboot flashing unlock_critical
see here.
@uicnren You a gentlemen and a scholar. Simple as that. Thanks.
Pay_It_Forward_Pete said:
@uicnren You a gentlemen and a scholar. Simple as that. Thanks.
Click to expand...
Click to collapse
:good:
I've tried to unlock my device with enable OEM unlock in the developer options, because it is needed for enable VoLTE in my regions(with QPST). But it seems that device doesn't recognize it's allowed to unlock. Every advanced fastboot command in fastboot mode returns "FAILED (remote: 'Command not supported in default implementation')".
Is this possible to you who using the device to unlock the bootloader with fastboot? Or, OTA updates I've received blocked that?
How unlock the bootloader?My HTC U20 5G no download mode in bootloader !!!!!
Try
fastboot oem get_identifier_token --- error
fastboot flashing unlock --- error
fastboot oem unlock --- error
Yes I have the same problem. I thought it was Win 10, so I tried Win 7 as well, but got the same error there too.
Check if "USB debugging" and "OEM unlocking" are activated in Developer options
iourikil said:
Check if "USB debugging" and "OEM unlocking" are activated in Developer options
Click to expand...
Click to collapse
Yes, both options are activated (at least in my case).
Both commands "fastboot flashing unlock" and "fastboot oem unlock" result in "FAILED (remote: 'unknown command'), fastboot: error: Command failed".
I have no problem with Desire 20 pro and have no guess why it doesn't work with U20
C:\adb>adb reboot bootloader
C:\adb>fastboot devices
CN06D1V02*** fastboot
C:\adb>fastboot flashing unlock
...
OKAY [ 0.040s]
finished. total time: 0.042s
iourikil said:
I have no problem with Desire 20 pro and have no guess why it doesn't work with U20
Click to expand...
Click to collapse
It also works with the U19e, very annoying that they changed it.
iourikil said:
I have no problem with Desire 20 pro and have no guess why it doesn't work with U20
C:\adb>adb reboot bootloader
C:\adb>fastboot devices
CN06D1V02*** fastboot
C:\adb>fastboot flashing unlock
...
OKAY [ 0.040s]
finished. total time: 0.042s
Click to expand...
Click to collapse
In U20 fastboot can't use this way and In bootloader no download mode to select. >"<
elimiriel said:
I've tried to unlock my device with enable OEM unlock in the developer options, because it is needed for enable VoLTE in my regions(with QPST). But it seems that device doesn't recognize it's allowed to unlock. Every advanced fastboot command in fastboot mode returns "FAILED (remote: 'Command not supported in default implementation')".
Is this possible to you who using the device to unlock the bootloader with fastboot? Or, OTA updates I've received blocked that?
Click to expand...
Click to collapse
for anyone that might come across this problem. I had the same issue trying to use fastboot to relock my bootloader. Found the answer on another forum. I was using adb to reboot to fastboot mode to run the command. This was the problem. I needed to reboot to the bootloader to run the command
elimiriel said:
I've tried to unlock my device with enable OEM unlock in the developer options, because it is needed for enable VoLTE in my regions(with QPST). But it seems that device doesn't recognize it's allowed to unlock. Every advanced fastboot command in fastboot mode returns "FAILED (remote: 'Command not supported in default implementation')".
Is this possible to you who using the device to unlock the bootloader with fastboot? Or, OTA updates I've received blocked that?
Click to expand...
Click to collapse
Try rebooting to the bootloader screen instead of directly rebooting. This solved my problem.
Hi there,
Just wanted to check in and see if anyone has managed to get bootloader unlocked?
Or is the htc u20 out of luck....
arcslt18 said:
Try rebooting to the bootloader screen instead of directly rebooting. This solved my problem.
Click to expand...
Click to collapse
can you teach me how to do that?
thank you
mofish said:
can you teach me how to do that?
thank you
Click to expand...
Click to collapse
Hi, Just manually enter the fast boot mode with power key+Volume Up or Down depending upon the model and make, You can search this online how to enter Bootloader mode for one particular device. Once you are in Bootloader, Try Fastboot mode and Enter your commands. Should work
Anyone figure this out on Nord n200 5g T-Mobile variant? Please help