Database Users

FAILED (remote: Command not allowed)

Hello,
I'm pretty new to rooting Sony devices and I can't seem to install custom roms on my Xperia Z2 using fastboot. My bootloader is unlocked (i've checked several times), USB debugging is checked and it believe my drivers are properly installed (fastboot devices cmd recognizes my device) but when i try to run "fastboot flash zip rom.zip" i get this annoying FAILED (remote: Command not allowed) message. I've looked through several threads but I can find any solution that applies to my case.
Any ideas would be welcome.
Thanks

I called Sony. Their official story is they do not support unlocking their own phones.
I asked her why, she said we just dont support unlocking the bootloader on some phones.
Im going to go break this phone and never recommend or buy sony products ever again

What exactly are you trying to flash?
Fastboot doesn't flash .zip files (I think). Whatever you are trying to flash must be extracted from the .zip file, then flashed via fastboot.
If you are trying to flash a custom kernel, you must have the boot.img file extracted from the .zip file in the same folder as the adb_fastboot folder, then hold in Shift then right-click and select, 'Open command window here' then type in cmd, 'fastboot flash boot boot.img'.
Once it says, 'Waiting for device', hold in the volume-up button on the phone and insert the USB cable into the phone.
Hope this helps.

I'm trying to flash android lollipop. I've tried extracting the boot.img flash it and then try to boot on recovery. A few times nothing happened and I couldn't force restore even using adb. Other times I just got stuck on the splash screen or in a loop reboot.
From what I've found online you can flash with flashboot using "flashboot flash zip Rom.zip" it starts transferring the room but it immediately does to the failed remote command not allowed error.
Sent from my D6503 using XDA Free mobile app

Where did you find that this command works for Xperia devices? I don't say that it can't work, but I see it for the first time (reading XDA for several years). All ROMs which I flashed were via flashtool or recovery, never through fastboot.
The best solution is to follow installation instruction of the given ROM.

RoamenCota
As far as I know most brands don't really support development but have you tried this the Sony Boot loader unlocking website?
_mysiak_
As for the cmd I found it online but I think it was an HTC forum. I guess it might not work in Xperia devices. I'm able to flash with flashtool but so far I've only managed to brick the phone.
Sent from my D6503 using XDA Free mobile app

Which ROM exactly are you trying to flash and what steps have you done?

_mysiak_ said:
Which ROM exactly are you trying to flash and what steps have you done?
Click to expand...
Click to collapse
I've tried flashing the [ROM][WIP]AOSP 5.0 Beta v2.0 from krabappel and the [ROM][SIRIUS][LP][5.0.1][SM-4.9] CyanogenMod 12 Unofficial [NIGHTLY BUILDS] from infected_ (sorry i'm not allowed to post links). As for the first one the process seems a bit more complex since there is a v2 plus an OTA to install. I've tried the second one first with flashboot but it didn't really work. With flash tool i've ended up bricking the phone.

CM is usually flashed via recovery (CWM, TWRP,..) - download ZIP, put it on SD card, boot into recovery, flash from there, reboot. Flashtool or fastboot should not be required. I would advise you to continue in ROM specific topics about any special installation steps/instructions.

_mysiak_ said:
CM is usually flashed via recovery (CWM, TWRP,..) - download ZIP, put it on SD card, boot into recovery, flash from there, reboot. Flashtool or fastboot should not be required. I would advise you to continue in ROM specific topics about any special installation steps/instructions.
Click to expand...
Click to collapse
For some reason that rom isn't able to be installed in TWRP recover. There's some install error may due to the fact that's a beta and not completely stable. If it doesn't work i'll just wait for a more stable version.
Just curious, even if it's a zip file, if I extract the complete package to the fastboot/adb folder and run "fastboot flash boot boot.img" there's no reason not to work right?

amrcardoso said:
For some reason that rom isn't able to be installed in TWRP recover. There's some install error may due to the fact that's a beta and not completely stable. If it doesn't work i'll just wait for a more stable version.
Just curious, even if it's a zip file, if I extract the complete package to the fastboot/adb folder and run "fastboot flash boot boot.img" there's no reason not to work right?
Click to expand...
Click to collapse
I don't think that it's worth the effort to flash those ROMs, unless you are really curious. Otherwise you should stick to verified and fully working ROMs.
It depends what you expect from that command. It will work, but it'll flash only kernel. System and other partitions remain untouched. Most probably you'll get bootloop with such combination.

_mysiak_ said:
I don't think that it's worth the effort to flash those ROMs, unless you are really curious. Otherwise you should stick to verified and fully working ROMs.
It depends what you expect from that command. It will work, but it'll flash only kernel. System and other partitions remain untouched. Most probably you'll get bootloop with such combination.
Click to expand...
Click to collapse
I'll probably stick with the zip flashing via recovery. But what step am I missing to flash a rom thorugh fastboot?

That most probably it's not possible to flash ROM via fastboot on Xperia devices. You have to use flashtool for FTF files and recovery for custom ROMs. Fastboot is used to flash kernel only.

_mysiak_ said:
That most probably it's not possible to flash ROM via fastboot on Xperia devices. You have to use flashtool for FTF files and recovery for custom ROMs. Fastboot is used to flash kernel only.
Click to expand...
Click to collapse
I have been able to flash the stock FTF but never a ROM using flashtool. Maybe that's why.
Thanks

Can't enter recovery anymore [TWRP]

Yesterday I've been trying to root my device using the official Oneplus video on YouTube . Everything was fine until I tried to flash the recovery. I flashed TWRP recovery using adb fastboot flash recovery (file) but then when I entered recovery the recovery didn't change. So I flashed it again, went into recovery and I finally got TWRP recovery. Then I flashed SuperSU and rooted my device. But now when I try to enter recovery I just get a black screen (OP logo not even showing). I can still enter fastboot and the operating system. If I use a booting app I see the Oneplus logo but after that it's a black screen so I need to press the power button for a couple of seconds to power it on. What can I do to solve this? The recovery is important for me.
Thanks in advance!
EDIT 1: If I check if my bootloader is unlocked using android sdk I see that my bootloader is locked. I am sure that I unlocked the bootloader before rooting my device. My mind is completely ****ed atm do I need to do everything again?

https://forums.oneplus.net/threads/...-custom-recovery-root-efs-backup-more.345478/
download that toolkit. It worked for many.

Any update on how it worked out?
Sent from my ONE A2001 using Tapatalk

Toolbox works very well, I think is the best tool for our OnePlus2.

Can't boot into recovery no matter how many times it is installed

Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?

carterl96 said:
Hey XDA, Recently installed Paranoid Android coming from Chroma and it's not stuck in a boot loop. I can boot just fine every time besides the annoying corruption google warning, but no matter how many times I try to install TWRP it just won't let me boot into recovery. I'm using WugFresh's NRT kit. Can't seem to figure it out. Any suggestions?
Click to expand...
Click to collapse
My suggestion is for you to fastboot flash the TWRP recovery image instead of using a toolkit. You cant see the inner workings of a toolkit and have no idea of what it is doing. The toolkit could be using the wrong commands to install a recovery image to your 6P. Go to www.twrp.me and search for the recovery image for your specific device and download the file. Next, rename the file to recovery.img Then, on your PC, navigate to the folder where you downloaded the TWRP image. Open a command prompt in that folder by pressing and holding the SHIFT KEY + RIGHT CLICK on your mouse and select OPEN A COMMAND WINDOW HERE. Boot to the bootloader on your device and connect it to your PC. Then type this:
fastboot flash recovery recovery.img
Then type this:
fastboot reboot bootloader
fastboot reboot recovery
Here is the link to download TWRP for your Nexus 6P
This will reboot your device to TWRP
All of this is based on the assumption that you have a working ADB installation and unlocked the bootloader and have USB Debugging turned on in DEVELOPER OPTIONS.
Sent from my Nexus 6 using XDA-Developers mobile app

Same thing, successful install and it won't open. Just shows the dead android when going to recovery.

carterl96 said:
Same thing, successful install and it won't open. Just shows the dead android when going to recovery.
Click to expand...
Click to collapse
You get the same results after fastboot flashing the TWRP image? I'd say your next step is to start fresh by fastboot flashing the factory images to return to a fully stock state. Then fastboot flash TWRP again.
Sent from my Nexus 6 using XDA-Developers mobile app

Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought

tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
I thought about that too. What is probably happening is his custom recovery is being patched by the ROM each time he boots into recovery. Thanks for picking up on that. I forgot to include that in my last post.
Sent from my Nexus 6 using XDA-Developers mobile app

tech_head said:
Do not boot directly into system after flashing the custom recovery.
After flashing boot into TWRP. I remember on previous devices that I owned that if you do not boot into the custom recovery after flashing it, you revert to the factory recovery.
Just a thought
Click to expand...
Click to collapse
That's correct. After flashing TWRP the next step is reboot into the bootloader using the volume keys and power key , then from there boot into recovery using the volume keys and power key, then the phone can be rebooted from TWRP into Android and then after that TWRP should stick.

If the boot image is not patched, the ROM will overwrite TWRP once you reboot. flashing latest SU from TWRP will prevent this.

Thanks for all the replies guys! All the advice combined got it to work. I did some more research and found that Paranoid doesn't actually come preprooted like all the other roms I've been used to. So using the tool kit I just had it root it with the latest SuperSu and also flash a custom recovery. It has booted into TWRP no problems now a few times. Hopefully it will stay like this. Will keep everyone posted and appreciate the advice. Thanks XDA!

asus zenfone 5 bricked and i can only go into bootloader ,recovery not working

I was using lollipop os on my Asus zenfone 5 t100f ,then i tried to update it to marshmallow but after the update, my device is bricked.I can enter into bootloader by pressing volume up+ power key but from bootloader whenever I try to go into recovery mode it stuck at Asus logo.i had tried every method from this forum like xFSTK downloader, Asus flash tool, ADB, etc.while using ADB with command prompt every command is executed without any problem like flashing fastboot,recovery,etc.but even after flashing recovery I am unable to get into recovery mode .please help me to get into recovery mode so I can apply update using ADB and stock ROM .
thank you.

Do not create new thread, there are a LOT of thread with those problems.. search for them.

reply
kihope12 said:
Do not create new thread, there are a LOT of thread with those problems.. search for them.
Click to expand...
Click to collapse
sorry for that
I have already tried many methods to debrick my device but none of them worked and my problem is different than others . I am able to enter into bootloader as well as when i flash new recovery images results are okay but when i enter into recovery mode it just stuck on asus logo please help

what recovery are you using exactly? Tried reflashing it yet?

reply
nheolinkin said:
what recovery are you using exactly? Tried reflashing it yet?
Click to expand...
Click to collapse
i am using lollipop recovery and already tried flashing recovery using command prompt and bootloader i am able to successfully flash the recovery image.but after flashing when i try to enter into recovery mode it stuck on asus logo.i have tried different recovery images as well as costom recovery but neither worked please help

sachin8618 said:
i am using lollipop recovery and already tried flashing recovery using command prompt and bootloader i am able to successfully flash the recovery image.but after flashing when i try to enter into recovery mode it stuck on asus logo.i have tried different recovery images as well as costom recovery but neither worked please help
Click to expand...
Click to collapse
Flash system.img throught fastboot.

Unable to flash TWRP on Moto e3 power with latest software update

I'm trying to flash TWRP (twrp-3.2.1-0-taido.img) on my Moto E3 Power. I had successfully rooted this phone once, and that's why the phone is unlocked. So when I try to flash custom recovery using the command "sudo fastboot flash recovery twrp-3.2.1-0-taido.img", it says it completed successfully, but instead of booting into twrp, my phone is starting up completely. When I tried booting up custom recovery using "sudo fastboot boot twrp-3.2.1-0-taido.img", the same thing happened again.
The software on my phone is "23.0.XT1706_S151_180706_ROW". So far I've been unable to flash twrp on this phone, but I got it to work an year ago. Please, can anyone help me what's going wrong here? I'm following the tips on xda-forums using which other users were able to flash the same recovery on their phones.

you can try this
ajyotirmay said:
I'm trying to flash TWRP (twrp-3.2.1-0-taido.img) on my Moto E3 Power. I had successfully rooted this phone once, and that's why the phone is unlocked. So when I try to flash custom recovery using the command "sudo fastboot flash recovery twrp-3.2.1-0-taido.img", it says it completed successfully, but instead of booting into twrp, my phone is starting up completely. When I tried booting up custom recovery using "sudo fastboot boot twrp-3.2.1-0-taido.img", the same thing happened again.
The software on my phone is "23.0.XT1706_S151_180706_ROW". So far I've been unable to flash twrp on this phone, but I got it to work an year ago. Please, can anyone help me what's going wrong here? I'm following the tips on xda-forums using which other users were able to flash the same recovery on their phones.
Click to expand...
Click to collapse
Get into the fastboot mode try again unlock your oem
'fastboot oem unlock'(volume up on your phone and select yes ) --->'fastboot format userdata' now flash the twrp recovery the link is below try this it may work worked fine for me and dont know really why the updated twrp is not flashing
My Google Drive link for TWRP recovery:-https://drive.google.com/file/d/0BylQ6RZ2mIP_cElxMzFoRVEyRDg/view?usp=sharing