So I got my FRP unlock code from a service center on call (I don't have one in my city). But when I type:
fastboot oem frp-unlock *password*
It still shows FRP Lock upon reboot.
Please help, I flashed a Treble system image which didn't boot and somehow corrupted my TWRP recovery; I tried locking the bootloader and trying dload method, but now I'm stuck with a locked bootloader and locked FRP; dload doesn't work, eRecovery WiFi recovery doesn't work.
Again, I've got my FRP unlock code and after fastboot oem frp-unlock *password* , it shows:
...
<bootloader> The device will reboot and do factory reset...
OKAY [ 3.221s ]
finished. total time: 3.221s
It reboots, still FRP lock shown in fastboot
Related
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
Hello and merry christmas.
I wanted to flash my BQ M5 with the new firmware 5.1.1 and now i'm stuck in bootloader with no way out?
To shorten it up: I did a fastboot flash sec sec.dat because i thought that this would fix things.
After a reboot-bootloader i ended up on a Fastboot-screen with a Linux Penguin in the middle. (i never had this before)
now any flash command suddenly ends in FAILED (remote: device is locked. Cannot flash images)
(flash-commands worked before with a unlocked bootloader)
but re-unlocking the bootloader with
fastboot oem unlock-go ends in FAILED (remote: oem unlock is not allowed)
(This worked before after enabling OEM-unlock in the Developer options.)
Robooting brings it directly to the penguin-bootloader with no possibility to flash anything(?) or to unlock(?)
Is it now totally bricked?
Thanks for any advice!!
AK
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!