Idk why, the problem resolved it self. I plugged it up to the cable and did nothing. Screen flashed once, then booted into BootLoader.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Ok. So I was going back to complete stock using the RUU method from - http://forum.xda-developers.com/showthread.php?t=1705484
I followed everything and got up to locking the bootloader. I got this message when doing
fastboot oem lock
It said
C:\fastboot> fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (No such file or directory))
finished. total time: 0.359s
C:\fastboot> fastboot reboot-bootloader
< waiting for device >
And now I have a screen with lines, kinda like a dead TV and a blinking led light. Phone won't respond to buttons or commands.
That means u did not connect the phone via USB in fast boot our ur device is not getting detected try installing htc drivers again
Sent from my One V
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.
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:
good friends after an update my google pixel stays in boot loop I have tried several ways to unlock the bootloader to install a stock rom from flashboot but every time i try to unlock the bootloader it tells me that i have to activate or unlock the oem option
I tried to do it with the adb flashtool but it gives me error
c:\adb>fastboot oem unlock
FAILED <remote: oem unlock is not allowed>
finished. total time: 0.044s
c:\adb>
I can not enter the Android system either from my Google Pixel since it is damaged the same to activate the option of OEM
I need someone to help me with this problem because the phone does not let me do anything for the fastboot because the bootloader and the OEM are blocked
Hi, I need some help with unlocking the bootloader of my phone [Huawei Y5 (DRA-LX3)] Please!
So, I am using the adb7fastboot method to unlock the bootloader, there are very limited options to do this process, but I've managed to find what might be the unlocker code for the command:
Code:
fastboot oem unlock xxxxxxxxxx (the unlock code)
Naturally, the warning screen appears on my phone (the one that tells you about erasing all of the data by unlocking the phone), and when I select "Yes" the phone displays an error:
unlock failed... return to fastboot in 3s
And the adb/fastboot window goes something like this:
Code:
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock failed - Err:0x7
)
finished. total time: 6.137s
What do you think? Is there a solution that can save my life? Thanks by the way!