C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (22732 KB)...
OKAY [ 0.489s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.499s
How do i fix this error? It's preventing me from installing twrp on my device. I have my bootloader unlocked and yet it refuses to work everytime.
Bootloader and frp unlock ?
jac10000 said:
Bootloader and frp unlock ?
Click to expand...
Click to collapse
I lost patience and decided to relock my bootloader and unlock it again. Now i face another mess of a problem.
jac10000 said:
Bootloader and frp unlock ?
Click to expand...
Click to collapse
Somehow, after relocking the bootloader, the android keyboard has refused to function anymore. And if i can't set up a wifi connection and configure my phone to start up, i'll be stuck and unable to use my phone any longer. So much for locking my phone to start the rooting process from scratch.
Ribombee said:
Somehow, after relocking the bootloader, the android keyboard has refused to function anymore. And if i can't set up a wifi connection and configure my phone to start up, i'll be stuck and unable to use my phone any longer. So much for locking my phone to start the rooting process from scratch.
Click to expand...
Click to collapse
Make sure to unlock your bootloader and FRP is unlocked. Which firmware/region are you currently using?
dexz said:
Make sure to unlock your bootloader and FRP is unlocked. Which firmware/region are you currently using?
Click to expand...
Click to collapse
I attempted to unlock the bootloader, which was the original plan, but my keyboard doesn't show up at all when i try to set up my wifi and sign into my phone to unlock the FRP. I'm stuck with Google Voice and i still can't find a way to start using my phone again because of it.
Ribombee said:
I attempted to unlock the bootloader, which was the original plan, but my keyboard doesn't show up at all when i try to set up my wifi and sign into my phone to unlock the FRP. I'm stuck with Google Voice and i still can't find a way to start using my phone again because of it.
Click to expand...
Click to collapse
So I assumed you are in Nougat. Reflash update_data.zip again via twrp (if you are using it)
dexz said:
So I assumed you are in Nougat. Reflash update_data.zip again via twrp (if you are using it)
Click to expand...
Click to collapse
I can't do that either. My bootloader is locked as we speak. I was planning on trying to lock it back and then unlock it again then attempt to install TWRP again. However, my keyboard magically disappeared from existence after i locked the bootloader.
Ribombee said:
I can't do that either. My bootloader is locked as we speak. I was planning on trying to lock it back and then unlock it again then attempt to install TWRP again. However, my keyboard magically disappeared from existence after i locked the bootloader.
Click to expand...
Click to collapse
The one way now you need to unlock your bootloader and install twrp. Since internet storage will be encrypted. You have to format data then install update_data.zip and update.zip again.
P/S: You can't install nougat via dload that's why you need twrp.
dexz said:
The one way now you need to unlock your bootloader and install twrp. Since internet storage will be encrypted. You have to format data then install update_data.zip and update.zip again.
P/S: You can't install nougat via dload that's why you need twrp.
Click to expand...
Click to collapse
But how do i unlock bootloader now if i can't enter the device to enable usb debugging and oem unlock?
Ribombee said:
But how do i unlock bootloader now if i can't enter the device to enable usb debugging and oem unlock?
Click to expand...
Click to collapse
You need to go bootloader mode. Shutdown your phone then press volume down and plug in usb cable. You will automatic go to bootloader mode the one with white background then type fastboot oem unlock your-unlock-password
P/S: You don't need to enable usb debugging to unlock your bootloader.
dexz said:
You need to go bootloader mode. Shutdown your phone then press volume down and plug in usb cable. You will automatic go to bootloader mode the one with white background then type fastboot oem unlock your-unlock-password
Click to expand...
Click to collapse
When i do that, it gives me this error.
C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem unlock 2044045691602471
...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
I can only unlock the bootloader if i unlock the Oem Unlock setting in Developer Options and USB Debugging, both of which i cannot do since my keyboard isn't working anymore. And Google Voice is below useless.
Ribombee said:
When i do that, it gives me this error.
C:\Program Files (x86)\Minimal ADB and Fastboot> fastboot oem unlock 2044045691602471
...
FAILED (remote: Command not allowed)
finished. total time: 0.017s
I can only unlock the bootloader if i unlock the Oem Unlock setting in Developer Options and USB Debugging, both of which i cannot do since my keyboard isn't working anymore. And Google Voice is below useless.
Click to expand...
Click to collapse
If you are in Nougat. You can't enable oem unlock. Either it won't showing or in greyed color. You need to enable it from EMUI 4/4.1
dexz said:
If you are in Nougat. You can't enable oem unlock. Either it won't showing or in greyed color. You need to enable it from EMUI 4/4.1
Click to expand...
Click to collapse
Well that just made things ten times better.
I should probably just give up on the phone.
You can just "rollback" to Emui 4.0 and unlock the Oem Unlock setting in Developer Options.
Need some help if someone can do that
- I have oem unlocked my b/l with unlock code, install twrp, try some polished rom but i don't like it and try to go back to oem locked state to flash an RUU file through ADB...
When i go to download/fastboot mode and type a "fastboot oem lock" command i have a message
"C:\adb>fastboot oem lock
...
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X01, enable unlock
OKAY [ 0.028s]
finished. total time: 0.029s"
to my PC and on my phone i have a question "Yes to OEM lock and hard reset or No to live..."
I point to Yes and when confirm that my phone rebooted to a loop rebooting and blinking display with HTC logo and red words text...
Whatever i try to do it's always blinking/rebooting
Is there any way to normallise my phone and turn to any normal state?!
TNX
I moved out from previous state!!!
What a luck!
Dont know how but pressed VolUp+VolDown+Power and gone to bootloader state. After that have to unlock b/l again and after that when gone to Recovery, my TWRP is still there what a sweetness....
When enter to TWRP just some quick tex "Decrypting phone" and immediately rebooting to a normal state with all working phone states!
Is there any way to lock b/l again, turn to OEM state and to do a normal/regular HTC updating???
My last HTC update was 1.64.401.10 and European version...
Any advice?
TNX
Flash stock recovery: https://forum.xda-developers.com/u-ultra/development/unlocked-model-stock-recovery-t3585622 and you should be able to lock your bootloader successfully.
Never update with a third-party recovery. After you are done updating, install custom recovery again.
Ok.
I didn't know that
Tnx
Hi all, I had official MIUI Global 11 on Android 10 on a phone with unlocked bootloader and a recovery. I wanted to re-lock the bootloader, so I went to fastboot and I gave the command to lock it.
Obviously (but I didn't even imagine it) the devide DID lock, but now it doesn't start any longer. ""System destroyed" is the message.
What I want to get is one of these two results: having a working phone OR having everything erased.
What I have already tried is:
- installing a firmware via fastboot: failed because the bootloader is locked
- flashing single .img via fastboot: failed because the bootloader is locked
- erase partitions: failed because the bootloader is locked
- unlock again the phone via fastboot: failed
- unlock again the phone via Mi Unlock: failed because missing authorization in developer options
Let's add the fact that I don't have windows, but Mac, that reduces the available options.
ANY SUGGESTIONS?
You can use Platform tools in windows.As far as i know platform tools can be used both locked and unlocked bootloader.You can search on YouTube how to flash mi phones through platform tools.
francanna said:
Hi all, I had official MIUI Global 11 on Android 10 on a phone with unlocked bootloader and a recovery. I wanted to re-lock the bootloader, so I went to fastboot and I gave the command to lock it.
Obviously (but I didn't even imagine it) the devide DID lock, but now it doesn't start any longer. ""System destroyed" is the message.
What I want to get is one of these two results: having a working phone OR having everything erased.
What I have already tried is:
- installing a firmware via fastboot: failed because the bootloader is locked
- flashing single .img via fastboot: failed because the bootloader is locked
- erase partitions: failed because the bootloader is locked
- unlock again the phone via fastboot: failed
- unlock again the phone via Mi Unlock: failed because missing authorization in developer options
Let's add the fact that I don't have windows, but Mac, that reduces the available options.
ANY SUGGESTIONS?
Click to expand...
Click to collapse
I think that the only way to flash it successfully again is to use QPST ,but you need to open the phone remove battery and get 9008 port , check in YouTube.
Hello to all gurus here
my Redmi Note 7 had a screen broken...I can only hardy recognize when it's in fastboot or recovery.... Touch not working.
The bootloader is locked, I am not sure if USB Debugging was enabled, but I suppose it was not because I get the following:
C:\MyDocs\TEMP\Varie\platform-tools>fastboot oem unlock
FAILED (remote: 'Token Verify Failed, Reboot the device
')
fastboot: error: Command failed
In this terrific scenario, is there any way on earth to recover my data?
I can only see my device in fastboot mode for what I can say...
On the other hand I could probably install a TWRP (which should already have debugging enabled) using fastboot but it seems to me it should clear all my user data.
Any way out?
Thanks in advance
unlocking bootloader requires bonded mi account in developer options and can only unlocked from miunlock tool. btw that will erase userdata during unlock for security reasons
Hello, I'm new here so if I miss any Forum rules please let me know.
TL;DR: I unlocked the bootloader of my VNS-L31 with PotatoNV and now I get the Message FAILED (remote: 'image verification error')
So, i want to install a Custom ROM in order to get OTG Support for my Smartphone. I'm new to this but as I figured out I need to do the following Steps.
1. Unlock Bootloader using PotatoNV
2. Install TWRP
3. Root via SU
3. Install CustomRom via TWRP
I think I managed to unlock my bootloader as I get the "your device cant be trusted" message every time I boot. I can enter fastboot mode with ADB and my device is recognized when it's in fastboot mode. when I try now to install TWRP (i tried different versions) I get the following message:
J:\Smartphone\TWRP\platform-tools_r31.0.2-windows\platform-tools>fastboot flash recovery twrp-3.1.1-0-venus.img
Sending 'recovery' (24464 KB) OKAY [ 0.648s]
Writing 'recovery' FAILED (remote: 'image verification error')
fastboot: error: Command failed
Reading the Forums suggested to relock the Bootloader and then unlock it again in good old " did you turn it off and on again" manner. but when I googled how to relock and unlock I got the warning that a lot of devices cant be unlocked a second time. So should I try to relock it via fastboot ? if I do so, can I unlock it again with the new unlockcode i set in PotatoNV, or do I need to open my phone for Testpoint mode and unlock it with PotatoNV again?
so hopefully i didn't miss any necessary information and someone here can help me or point me in the right direction
greetings
Elfenfreund
PS: Pardon my Writing. It's late and my English is not very trained.
No need to relock. Just unlock it again using the code given by the Potato. Then try flashing again the image.