when I'm trying to install twrp through adb this is the error I get, bootloader is unlocked, so is oem unlock any ideas?
Related
I have a rooted device then i updated my device via firmware finder without unrooting my device. But my recovery was on stock recovery and erecovery was twrp. After update installed device automatically been unrooted. Phone is unlocked frp is unlocked too but when i try to flash twrp on fastboot mode it wont flash (command error) even when i type "fastboot oem device-info" it will get same error.
Can someone know what exactly is the problem. I just want to flash twrp so that i can root my device again. Thanks in advance.
Have you activated USB debug in the device settings?
Yes.
[Q] fastboot oem unlock with correct code fails with "command did not succeed"
Hi,
I recently got an xperia Z into my hands and wanted to unlock the bootloader.
I checked the IMEI in the system settings and requested and received an unlock code for the device.
I unlocked the bootloader with the code,
but now I am not able to flash or boot anything via fastboot (device still boots normally though).
When trying to flash e.g. twrp to the boot partition
(
Code:
fastboot flash boot boot.img
)
it fails with "remote: command not allowed"
Also trying
Code:
fastboot boot boot.img
does not work properly:
In this case it just reboots into Android.
I am using Linux to flash stuff.
I already tried using the flashtool, which also didnt bring me any success.
Does anyone have an idea or a solution to this problem?
Best regards
I can't relock my bootloader. Haven't rooted or anything. I unlocked it, couldnt flash the kernel for root so gave up on it and wanted to relock my bootloader. Getting these errors:
c:\adb>fastboot flashing lock_critical
FAILED (Write to device failed (No such file or directory))
fastboot: error: Command failed
Any ideas?
wschamps42 said:
I can't relock my bootloader. Haven't rooted or anything. I unlocked it, couldnt flash the kernel for root so gave up on it and wanted to relock my bootloader. Getting these errors:
c:\adb>fastboot flashing lock_critical
FAILED (Write to device failed (No such file or directory))
fastboot: error: Command failed
Any ideas?
Click to expand...
Click to collapse
Are you sure the kernel didn't flash at all?
I'd recommend flashing a factory image and then trying to lock it just in case something went wrong.
If it still doesn't work is your device showing on CMD using "fastboot devices"?
I'm getting the error device already locked even though my bootloader clearly states that the bootloader is in unlocked. I just flashed the factory image for the phone and still same error. Any ideas?
Rox598 said:
Are you sure the kernel didn't flash at all?
I'd recommend flashing a factory image and then trying to lock it just in case something went wrong.
If it still doesn't work is your device showing on CMD using "fastboot devices"?
Click to expand...
Click to collapse
hello i was able to get it to show up in fastboot devices but i am unable to relock...when i try to get it to relock it goes and says waiting for device even though its in fast boot mode.
Hey All, I flashed TWRP 3.3.1 from the offical TWRP app, but when my phone rebooted it goes to:
ERROR MODE
Attention!
Please update System again
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed)
I can get to fastboot, but the functions are extremely limited and I keep getting
Phone Unlocked
FRP Lock
Whenever I try to flash using fastboot, I keep getting an error
"FAILED (remote: 'Command not allowed')"
I think this has to do with the FRP Lock, but I can't figure out how to unlock it???
Can anyone provide any help? Is my phone a literal brick now?
Any help is appreciated!!
I'm running on realme 8i with RMX3151_11_C.19, locked bootloader
(sorry for my english)
If I run adb reboot fastboot it boots in recovery, but I can still run fastboot devices. With adb reboot recovery it boots in recovery, but it's not recognized infastboot. Unfortunatly, fastboot oem unlock returns
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
Does anyone know why is it like that and if I unlock the bootloader will I be able to flash custom recovery like on a normal phone?
Treeager said:
I'm running on realme 8i with RMX3151_11_C.19, locked bootloader
(sorry for my english)
If I run adb reboot fastboot it boots in recovery, but I can still run fastboot devices. With adb reboot recovery it boots in recovery, but it's not recognized infastboot. Unfortunatly, fastboot oem unlock returns
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
Does anyone know why is it like that
Click to expand...
Click to collapse
adb reboot bootloader
mvikrant97 said:
adb reboot bootloader
Click to expand...
Click to collapse
This only reboots the phone
Treeager said:
I'm running on realme 8i with RMX3151_11_C.19, locked bootloader
(sorry for my english)
If I run adb reboot fastboot it boots in recovery, but I can still run fastboot devices. With adb reboot recovery it boots in recovery, but it's not recognized infastboot. Unfortunatly, fastboot oem unlock returns
Code:
FAILED (remote: 'Unable to open fastboot HAL')
fastboot: error: Command failed
Does anyone know why is it like that and if I unlock the bootloader will I be able to flash custom recovery like on a normal phone?
Click to expand...
Click to collapse
The fastest way to unlock your phone's bootloader is using mtk client.
You will find plenty of tutorials on youtube as well as XDA on how to use mtk client.
Please comment down here if you need any help.
UPDATE: So I unlocked the bootloader with mtk, and with this weird fastboot I can flash recoveries. But if I do "adb reboot fastboot", I can execute fastboot commands, but the recovery becomes the stock recovery wich is a little strange to me... Anyway, how to decrypt the storage in twrp? And also I am trying to install Pixel OS from here. I installed the pixel recovery too.