hello guys was testing magisk Firedance-FSTAB-Mod-V1.3 for oreo 8 and all good but I wanted to install xposed and brickeo blocking inpidiendome flashing fastboot img, fastboot mode did not work so I closed it to then reopen it but it was blocked frp oem and I do not know what to do, try to flash the kernel and the ramdisk FAILED (remote: Command not allowed) I do not know what to do, please help me please
Related
Let me explain my story.
Rooted phone, installed dual recovery, decided to have some xposed modules, installed a ton, went into a boot animation, went into recovery and decided to clear system and now I can only access fastboot mode. I tried to fastboot flash boot Z3_DooMLoRD_AdvStkKernel_v01_FW-93.img, but i get FAILED (remote: Command not allowed) at the end so it doesn't work.
I don't think my bootloader is unlocked. So I guess I bricked my phone unless someone has a way to fix it. I literally rooted my phone two days ago.
Flashtool says the same thing.
Model number: D6603.
EDIT: Currently testing if I can flash an FTF.
EDIT: Praise the lord, flashing a new FTF works amazing.
/Thread.
Hello Guys, I am new to the forum. I read a lot of threads, but no one i found had the solution or the exact same problem i have.
I bought a new Xiaomi Redmi 4X and wanted to install the los 14.1 Version I found here in XDA (https://forum.xda-developers.com/android/development/rom-2017-08-07lineage-14-1-t3653016). (I have installed custom roms a few times before and also faced some problems)
I flashed twrp via the fastboot mode using my linux laptop. I installed the los zip file and booted into it, but it was stuck in a boot loop. I wanted to go back into twrp, but it did not work, so i tried it with the fastboot again. Then I saw that oem is locked.
As root user i tried to unlock it with
Code:
# fastboot oem unlock
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.004s
but it doesnt work.
So I am stuck now without any ROM and Recovery, I can only access to the bootloader.
I am happy for any help.
My Honor 6 was bricked after a stock OEM installing. I was tried to use fastboot to install a new recovery, but it shows
Code:
FAILED (remote: Command not allowed)
, however my phone says it is UNLOCKED.
Please help.
Thanks
Hi all,
I really need some help. I was trying to update my Mi4c to MIUI 10, but something went wrong and now I it is in bootloop. It is locked and I can't unlock it anymore.
Since Fastboot is working I tried to enter EDL mode via ADB but it says this
PS C:\fastboot> .\fastboot devices
ecc1a647 fastboot
PS C:\fastboot> .\fastboot oem edl
...
FAILED (command write failed (Unknown error))
finished. total time: 5.002s
Please help,
Thank you
why not you try to flash the miui rom using fastboot mode instead of going to EDL.
You can get the rom file from this url https://mifirm.net/model/libra.ttt
Hello Everyone, I lost my hope with google pixel.
Let me tell you my problem.
1. Custom Rom installed
2. Oem unlock disabled in developer settings
3. and I accidentally locked the boot loader
4. and top of that not been able to boot into recovery because I lost it when I locked the boot loader I think
so as a result I always get this error
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
I tried
flashing unlock
fastboot oem unlock
fastboot flashing unlock_critical
After 2/3 months of relentless trying I lost hope.If anyone can help please help me.
iqbal.jewel said:
Hello Everyone, I lost my hope with google pixel.
Let me tell you my problem.
1. Custom Rom installed
2. Oem unlock disabled in developer settings
3. and I accidentally locked the boot loader
4. and top of that not been able to boot into recovery because I lost it when I locked the boot loader I think
so as a result I always get this error
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
I tried
flashing unlock
fastboot oem unlock
fastboot flashing unlock_critical
After 2/3 months of relentless trying I lost hope.If anyone can help please help me.
Click to expand...
Click to collapse
You can't fix it. :crying: