I am trying to install cwm recovery through fastboot. But I am getting the error as partition 'recovery' not support flash. Please any one help me to fix this. Whether I need to change anything on the recovery partition?
Related
Hi, I want to install TWRP Recovery with Flashify but I get this error, what I can do?
Please Help
i
i don't know if this bug inside the app or not...
but as the error message said there is no recovery partition (or maybe app cannot recognize it)
so try to flash recovery manual by adb
the key command is this
Code:
astboot flash recovery FILE.IMG
but its better to read carefully
This is good guide
:good:
I do that and it seems to work but when i try to reboot into recovery mode I get an back screen with a orange led. What happen?
Hi, I'm trying to install a recovery for my xperia u (st25i) and a custom room (cm-12.1-20150704-UNOFFICIAL-kumquat).
I'm a bit confused... is the kernel included inside the room or do I have to look for one with the cwm included. And how can I flash it using fastboot. I already have the room ready to install but since I don't have any recovery installed (I keep trying volume + or - while powering on and nothing...).
I supose the command is: fastboot flash recovery recovery.img
Not sure about how to flash the room.
I found this but it seems the link it's down...
I would appreciate a link to the CWM recovery and the commands to flash it and also the custom room.
Thanks!
ChazyTheBest said:
Hi, I'm trying to install a recovery for my xperia u (st25i) and a custom room (cm-12.1-20150704-UNOFFICIAL-kumquat).
I'm a bit confused... is the kernel included inside the room or do I have to look for one with the cwm included. And how can I flash it using fastboot. I already have the room ready to install but since I don't have any recovery installed (I keep trying volume + or - while powering on and nothing...).
I supose the command is: fastboot flash recovery recovery.img
Not sure about how to flash the room.
I found this but it seems the link it's down...
I would appreciate a link to the CWM recovery and the commands to flash it and also the custom room.
Thanks!
Click to expand...
Click to collapse
try to extract boot.img from the rom zip then install it via flashtool (you must have root and fastboot driver installed ).to do that poweroff phone hold vol + and plugin usb cable u will see blue led open flashtool choise fastboot and flash boot.img that you extract from cm rom zip .after flash boot reboot your device and try vol- you will enter twrp than flash rom from sdcard .sorry for my english
amin44 said:
try to extract boot.img from the rom zip then install it via flashtool (you must have root and fastboot driver installed ).to do that poweroff phone hold vol + and plugin usb cable u will see blue led open flashtool choise fastboot and flash boot.img that you extract from cm rom zip .after flash boot reboot your device and try vol- you will enter twrp than flash rom from sdcard .sorry for my english
Click to expand...
Click to collapse
Thanks for your answer. I was able to flash an old version of the CWM recovery, but I think I just fukd up... By mistake I zeroed the userdata/sdcard partition (using diskpart clean all), since then I cannot mount it in the CWM recovery: it always says "Can't mount /sdcard/", everywhere, trying to partition it, trying to factory reset... any option will give me that error. I already tried giving it format, fat, fat32, extfat... none works.
I tried some fastboot commands like erase userdata and so, and now I can't even mount the /data/ partition that I was able to mount.
But I'll try flashing it using the flashtool as you say.
Edit: Fixed! It seems the recovery from that kernel repaired the partitions and I was able to install the zip from there. Thanks!
ChazyTheBest said:
Thanks for your answer. I was able to flash an old version of the CWM recovery, but I think I just fukd up... By mistake I zeroed the userdata/sdcard partition (using diskpart clean all), since then I cannot mount it in the CWM recovery: it always says "Can't mount /sdcard/", everywhere, trying to partition it, trying to factory reset... any option will give me that error. I already tried giving it format, fat, fat32, extfat... none works.
I tried some fastboot commands like erase userdata and so, and now I can't even mount the /data/ partition that I was able to mount.
But I'll try flashing it using the flashtool as you say.
Edit: Fixed! It seems the recovery from that kernel repaired the partitions and I was able to install the zip from there. Thanks!
Click to expand...
Click to collapse
your partiton are ok the problam is that you can not install a lollipop
/kitkat rom via cwm recovery you need a twrp recovery next time before flash lollipop rom via cwm flash a kernel that have twrp like bravo kernel then u can flash rom without problam
Hello,
I soft-bricked my Padfone A86 when I tried to flash my own kernel using TWRP 2.7.1.1. Before that I was running a rooted Android 5.0.2 (fw version WW-12.4.0.59) with TWRP recovery that I installed like described in an article at padfoneclub.com.
Installing the custom ROM damaged (at least) the boot and recovery partitions. That means I only have access to fastboot which I can not use to flash to those partitions:
Code:
fastboot flash recovery twrp-2.7.1.1-unofficial.img
target reported max download size of 1879048192 bytes
sending 'recovery' (10124 KB)...
OKAY [ 0.321s]
writing 'recovery'...
FAILED (remote: Security is Enable, close 'flash' function !!)
finished. total time: 0.338s
The remote: Security is Enable, close 'flash' function !! error must have been introduced by a patch to the bootloader because I don't recall having this issue when I first flashed TWRP back then when I was running some previous firmware version.
What I can do though is to boot the boot.img (only from fw versions 10.12.3.116 and 10.12.3.130) like this: fastboot boot boot.img
Using saferoot I managed to get root access which enables me to write to the recovery and boot partitions like this:
Code:
dd if=/sdcard/twrp-2.7.1.1-unofficial.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery bs=4096; sync;
Although I can confirm that the memory gets changed using the dd command the bootloader neither loads recovery nor the system on the boot partition.
I looked at a hexdump of the recovery partition and it seems like the only thing stored in it is the TWRP image followed by zeroes. Trying different block sizes didn't help neither.
Confusingly that method seemed to work for some people. Maybe TWRP requires to be written over some stock recovery and can't boot on its own?
I was only able to try to flash the stock recovery for fw versions above 10.12.3.13 as ASUS only included patch-files for the recovery partition before. That didn't work neither. I was assuming that the recovery is running on its own and does not depend on being the same version as the system (or the bootloader). Or might there be something on a different partition that prevents the recovery from working properly?
Booting into recovery results in getting into fastboot mode (fastboot continue doesn't help).
Booting the system stops at the bootloader which shows the error message: ERROR: Can not load Invalid boot image!!
The frustrating thing is that although I seem to have full access to the device memory I still don't manage to fix the recovery partition.
Any help or ideas would be greatly appreciated.
Thunder Storm said:
Hello,
I soft-bricked my Padfone A86 when I tried to flash my own kernel using TWRP 2.7.1.1. Before that I was running a rooted Android 5.0.2 (fw version WW-12.4.0.59) with TWRP recovery that I installed like described in an article at padfoneclub.com.
Installing the custom ROM damaged (at least) the boot and recovery partitions. That means I only have access to fastboot which I can not use to flash to those partitions:
Code:
fastboot flash recovery twrp-2.7.1.1-unofficial.img
target reported max download size of 1879048192 bytes
sending 'recovery' (10124 KB)...
OKAY [ 0.321s]
writing 'recovery'...
FAILED (remote: Security is Enable, close 'flash' function !!)
finished. total time: 0.338s
The remote: Security is Enable, close 'flash' function !! error must have been introduced by a patch to the bootloader because I don't recall having this issue when I first flashed TWRP back then when I was running some previous firmware version.
What I can do though is to boot the boot.img (only from fw versions 10.12.3.116 and 10.12.3.130) like this: fastboot boot boot.img
Using saferoot I managed to get root access which enables me to write to the recovery and boot partitions like this:
Code:
dd if=/sdcard/twrp-2.7.1.1-unofficial.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery bs=4096; sync;
Although I can confirm that the memory gets changed using the dd command the bootloader neither loads recovery nor the system on the boot partition.
I looked at a hexdump of the recovery partition and it seems like the only thing stored in it is the TWRP image followed by zeroes.
Confusingly that method seemed to work for some people. Maybe TWRP requires to be written over some stock recovery and can't boot on its own?
I was only able to try to flash the stock recovery for fw versions above 10.12.3.13 as ASUS only included patch-files for the recovery partition before. That didn't work neither. I was assuming that the recovery is running on its own and does not depend on being the same version as the system (or the bootloader). Or might there be something on a different partition that prevents the recovery from working properly?
Booting into recovery results in getting into fastboot mode (fastboot continue doesn't help).
Booting the system stops at the bootloader which shows the error message: ERROR: Can not load Invalid boot image!!
The frustrating thing is that although I seem to have full access to the device memory I still don't manage to fix the recovery partition.
Any help or ideas would be greatly appreciated.
Click to expand...
Click to collapse
Try getting rid of the bs part. Flash the image at it's normal size.
Sent from my XT1609 using Tapatalk
Thanks for your reply.
I flashed both TWRP and stock recovery without the bs parameter. Same results as before: it doesn't boot into recovery.
hi.
FastBoot recovery failed: partition 'recovery' not support flash
My mobile is honor 3c lite hol-u19 running official Android OS 4.4.2.
I am trying to install twrp recovery through fastboot. I tried executing the command
fastboot flash recovery recovery.img
But I am getting the error as partition 'recovery' not support flash. Please any one help me to fix this. Whether I need to change anything on the recovery partition?
I'm trying to boot an image without flashing it to my Xiaomi:
fastboot boot Image
creating boot image...
creating boot image - 35883008 bytes
Sending 'boot.img' (35042 KB) OKAY [ 0.829s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Isn't there a way to do it? It's a Poco M3
Poco M3 has separate recovery partition and TWRP is available too. Why don't you flash it?
You mean flashing the kernel to the recovery partition? How would this work? Flash boot.img to recovery, then do adb reboot recovery, and test the kernel,without rewriting the original kernel?
aIecxs said:
Poco M3 has separate recovery partition and TWRP is available too. Why don't you flash it?
Click to expand...
Click to collapse
You mean flashing the kernel to the recovery partition? How would this work? Flash boot.img to recovery, then do adb reboot recovery, and test the kernel,without rewriting the original kernel?
no I mean flash boot.img to boot and twrp to recovery as usual. I am using this TWRP - encryption only worked on very first boot (don't ask me why) but that was good enough to backup userdata and everything