I've tried to install CM11 on xperia V (rooted) with T4.3_PhilZCWM_6.0.4.7_LB_v1.7 but I got error 7 and when reboot my device dont boot I tired to going to costume recovery but can't do it (broken recovery) so I can't install recovery flash-able .zip file again. and can't find *.img file in it!
How I can get stock or costume recovery file as .img for use flash in fastboot? or Can I flash custom recovery .zip file via fastboot?
and tried: fastboot flash recovery T4.3_PhilZCWM_6.0.4.7_LB_v1.7.zip
Get:
sending 'recovery' (3201 KB)...
(bootloader) USB download speed was 16392kB/s
OKAY [ 0.218s]
writing 'recovery'...
(bootloader) Flash of partition 'recovery' requested
FAILED (remote: Partition not found)
thank you for help
Answer is:
Sony phones doesn't have separate recovery partition. Its recovery is incorporated to the boot.img, which contains also the kernel.
Custom kernels normally comes with the recovery. You only need to "fastboot flash boot boot.img"
source: http://forum.xda-developers.com/member.php?u=4023029
So: extract boot.img from CM11.zip file and fastboot flash boot.img and recovery will accessible
Related
after restoring 5.1 again from Indonesian to Indian.. Philz could not Format my user data or wipe cache.. So I flashed without wiping..and it successfully booted but now I can't find philz Recovery in Recovery mode..it booted to stock! What can I do now?
nand.96 said:
after restoring 5.1 again from Indonesian to Indian.. Philz could not Format my user data or wipe cache.. So I flashed without wiping..and it successfully booted but now I can't find philz Recovery in Recovery mode..it booted to stock! What can I do now?
Click to expand...
Click to collapse
Yes That Backup Rom had stock recovery. if u need philz recovery after installed that rom u can flash philz recovery by Android one Tool Kit available in this forum.
Narasimman91 said:
Yes That Backup Rom had stock recovery. if u need philz recovery after installed that rom u can flash philz recovery by Android one Tool Kit available in this forum.
Click to expand...
Click to collapse
i tries android one toolkit.. it is not recognizing my device.. i tried minimal adb.. it recognizes my device... i also went to fastboot ..gave flash recovery command.. it also said succes saying all this-->
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (6626 KB)...
OKAY [ 0.202s]
writing 'recovery'...
OKAY [ 0.400s]
finished. total time: 0.618s
C:\Program Files\Minimal ADB and Fastboot>fastboot reboot
.. but after reboot i m again on stock.. No philZ! plzz help
nand.96 said:
i tries android one toolkit.. it is not recognizing my device.. i tried minimal adb.. it recognizes my device... i also went to fastboot ..gave flash recovery command.. it also said succes saying all this-->
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (6626 KB)...
OKAY [ 0.202s]
writing 'recovery'...
OKAY [ 0.400s]
finished. total time: 0.618s
C:\Program Files\Minimal ADB and Fastboot>fastboot reboot
.. but after reboot i m again on stock.. No philZ! plzz help
Click to expand...
Click to collapse
First Download fastboot unlock scripts. (attached zip file)
1.extract that file
2.press shift key and mouse right key and then select open command here
3. reboot into fastboot mode on ur phone
4. connect to ur phone via usb
5. then type following command: fastboot oem unlock and fastboot format userdata
after did above method andorid one tool kit detect ur phone
now u can flash philz recovery.
Thanks.. Flashed PhilZ successfully! But i can't Root my device using philz now... I tried Adb sideload ,installing zip directly of supersu..zip What can i do now?
Download the latest supersu.zip,google it, then flast it uaing philz recovery.Only the latest supersu.zip can root ur phone as other versions does not support android 5.1
Yes. Flash not less than v2.45 of SuperSU zip as they won't work. I have flashed v2.45 currently n it works fine..
hello, i have try everything but cant flash boot image, maybe someone know what i'm doing wrong.
my device:
xperia z c6603
bootloader unlocked
no root
developer options on (adb)
to get kernel.sin i use original firmware from sony emma tool than i use 7zip to extract the kernel.sin,
i also use the androxyde flashtool Tools->Bundles->FILESETdecrypt then extract from .ftf file.
kernel.elf i get with flashtool->tools->sin editor->extract data
kernel.img i get thru rename .elf to .img like here http://forum.xda-developers.com/showthread.php?t=2699858
then i use fastboot devices in cmd.exe (admin) with "fastboot flash boot kernel.elf" also "fastboot flash boot kernel.img"
HTML:
C:\platform-tools>fastboot flash boot kernel.elf
sending 'boot' (9000 KB)...
OKAY [ 0.288s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.295s
HTML:
C:\platform-tools>fastboot flash boot kernel.img
sending 'boot' (9000 KB)...
OKAY [ 0.288s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.296s
i also use flashtool for this get same error (see picture)
first i use drivers from sony and xperia companion everything is fine in device manager, i also can erase system, boot and userdata thru fastboot so the drivers are fine.
but for testing i install the driver from androxyde flashtool and done all from begin, same problem here with FAILED (remote: image is not a boot image)
i use win 8.1 64bit as administrator
for install drivers i deactivated the driver signature
can use adb thru cmd.exe (device is correctly shown)
can use fastboot for "fastboot erase boot" for example (device is correctly shown)
i unlocked the bootloader with sony unlock code, no problems
pls help, dont know what i can do else.
now i root my phone and try to extract the boot.img from my android phone (see on picture).
the boot.img was successfully copy to my sdcard, then i reboot into fastboot and try to flash.
no success same error again: FAILED (remote: image is not a boot image)
slowly i get desperate
i try to flash newest twrp,
fastboot flash boot twrp.img
this works without problems, so driver and usb cable is fine.
Do you got a solution?
Michael
I searched a lot of articles all flashed to the recovery partition
Code:
>fastboot flash recovery boot_twrp_UNOFFICIAL.img
Sending 'recovery' (65536 KB) OKAY [ 2.062s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I found some information that Android 11 uses Virtual A/B
Do I need to modify boot.img to install custom recovery in Android 11?
AceSheep said:
I searched a lot of articles all flashed to the recovery partition
Code:
>fastboot flash recovery boot_twrp_UNOFFICIAL.img
Sending 'recovery' (65536 KB) OKAY [ 2.062s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I found some information that Android 11 uses Virtual A/B
Do I need to modify boot.img to install custom recovery in Android 11?
Click to expand...
Click to collapse
fastboot boot twrp.img
Go ti advanced and install current twrp
Otherwise u can installiert it temporarly on boot, fastboot flash Boot twrp.IMG
Now you can Boot into it using hardwarebuttons....Herr u can flash it finaly
Did u find a working twrp....this one here doesnt work....also otg mouse not working in that one
bambamGN2 said:
Otherwise u can installiert it temporarly on boot, fastboot flash Boot twrp.IMG
Now you can Boot into it using hardwarebuttons....Herr u can flash it finaly
Did u find a working twrp....this one here doesnt work....also otg mouse not working in that one
Click to expand...
Click to collapse
I use a type-c hub to connect a wireless mouse and it works
I used this command and it didn’t work normally, it will enter the system normally after restart
Code:
>fastboot boot images\boot_twrp_UNOFFICIAL.img
Sending 'boot.img' (65536 KB) OKAY [ 1.735s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
This command can start to TWRP but cannot install it
Code:
>fastboot flash boot_b images\boot_twrp_UNOFFICIAL.img
>fastboot set_active b
>fastboot reboot
Do I still need to unpack boot.img and copy the ramdisk file
AceSheep said:
I used this command and it didn’t work normally, it will enter the system normally after restart
Code:
>fastboot boot images\boot_twrp_UNOFFICIAL.img
Sending 'boot.img' (65536 KB) OKAY [ 1.735s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
This command can start to TWRP but cannot install it
Code:
>fastboot flash boot_b images\boot_twrp_UNOFFICIAL.img
>fastboot set_active b
>fastboot reboot
Do I still need to unpack boot.img and copy the ramdisk file
Click to expand...
Click to collapse
fastboot boot twrp_UNOFFICIAL.img
This work for sure
This topic is great, but I'm afraid many of us would totally miss the information in here, do anyone has the will to turn the information here into a little "how to TWRP" guide as a topic here? That would be awesome!
My device is Redmi Note 10 5G China and the EEA rom flashed. Using twrp will get stuck in the logo and cannot enter.
Before that, I can start twrp using China rom. I'm still looking for reasons
----------
P.S. Does anyone know how to compile twrp for Android 11? I need a little help
AceSheep said:
----------
P.S. Does anyone know how to compile twrp for Android 11? I need a little help
Click to expand...
Click to collapse
No but maybe this helps????
Make A TWRP Tree For Your Device & Build.md
GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
i suggest for now stay on stock recovery. you can root phone installing magisk via fastboot. and the only way to try custom rom is flashing the gsi ported generic rom. the nippon gsi telefram group have a lot of gsi. but my advice is wait miu13 update. most of gsi have audio incompatibility. but if you like aosp roms this is the only way. mtk full custom roms for our device dont exist
I am on 12.5.4.0 stock ROM. I am unable to overwrite the stock MIUI recovery. I always get the error message:
FAILED (Status read failed (Too many links))
The recovery image that i am using is a lineage OS 18.1 recovery image that i obtained from a Telegram group on a new lineage 18.1 ROM. I also tried a TWRP image by wzsx, with the same result.
I also tried disabling vbmeta with the command:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta\vbmeta_vd171--V12.5.3.0.RJOMIXM.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta' (4 KB) OKAY [ 0.016s]
Writing 'vbmeta' OKAY [ 0.000s]
Finished. Total time: 0.016s
But after reboot it goes back to MIUI recovery.
Previously i had flashed crDroid ROM with an SHRP recovery. I remember getting the same "Too many links" error that time too, but i have forgotten how i managed to flash SHRP that time.
I tried using SP FLash Tool , but here too i get an error message " Invalid scatter file name" or something like that for the scatter file in the 12.5.4.0 stock ROM. Then i tried MTK tool to create a scatter file for my Redmi Note 9 but this time i get an error saying it is unabke to read the ROM storage format. Can anyone please help?
Do:
fastboot flash vbmeta vbmeta_vd171--V12.5.3.0.RJOMIXM.img
Is same to do:
fastboot --disable-verity --disable-verification flash vbmeta original_stock_vbmeta.img
It seens a problem with typing.
Did you try to use quotes?
Like
fastboot flash recovery "here is the place/of/image.img"
VD171 said:
It seens a problem with typing.
Did you try to use quotes?
Like
fastboot flash recovery "here is the place/of/image.img"
Click to expand...
Click to collapse
Thanks for the reply. No i don't think it's a problem with typing:
fastboot flash recovery recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.992s]
Writing 'recovery' OKAY [ 0.881s]
Finished. Total time: 2.878s
Now i tried going back to 12.0.6.0 stock ROM with TWRP-RedmiNote9-V12.0.6.0.QJOMIXM-20201213-wzsx15-sanja56. This time success:
C:\Users\iamam\Downloads\TWRP>fastboot flash recovery recovery.img
Sending 'recovery' (34076 KB) OKAY [ 0.855s]
Writing 'recovery' OKAY [ 0.453s]
Finished. Total time: 1.340s
fastboot boot recovery.img
Sending 'boot.img' (34076 KB) OKAY [ 1.017s]
Booting OKAY [ 0.051s]
Finished. Total time: 1.103s
But IT STILL BOOTS INTO MIUI stock RECOVERY!! I can't understand it. Just for fun i changed recovery.img in the fastboot ROM to the recovery.img that i wanted but MiFlash fails (obviously!!!!). Is there a way to check recovery partition on the phone?
12Frodo said:
Thanks for the reply. No i don't think it's a problem with typing:
fastboot flash recovery recovery.img
Sending 'recovery' (65536 KB) OKAY [ 1.992s]
Writing 'recovery' OKAY [ 0.881s]
Finished. Total time: 2.878s
Now i tried going back to 12.0.6.0 stock ROM with TWRP-RedmiNote9-V12.0.6.0.QJOMIXM-20201213-wzsx15-sanja56. This time success:
C:\Users\iamam\Downloads\TWRP>fastboot flash recovery recovery.img
Sending 'recovery' (34076 KB) OKAY [ 0.855s]
Writing 'recovery' OKAY [ 0.453s]
Finished. Total time: 1.340s
fastboot boot recovery.img
Sending 'boot.img' (34076 KB) OKAY [ 1.017s]
Booting OKAY [ 0.051s]
Finished. Total time: 1.103s
But IT STILL BOOTS INTO MIUI stock RECOVERY!! I can't understand it. Just for fun i changed recovery.img in the fastboot ROM to the recovery.img that i wanted but MiFlash fails (obviously!!!!). Is there a way to check recovery partition on the phone?
Click to expand...
Click to collapse
Are you sure are not booting into MIUI after flashing? because MIUI installs back the default recovery.
vagelis199 said:
Are you sure are not booting into MIUI after flashing? because MIUI installs back the default recovery.
Click to expand...
Click to collapse
Exactly.
If you want to use custom recovery but without root/magisk, you need to flash my patched boot image.
This patched boot image does NOT install back the default recovery and does NOT install root/magisk.
[BOOT][IMG][PATCHED] Boot Image Partition without OVERWRITE OF RECOVERY for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED BOOT.IMG for MERLIN by VD171 For what do I need it ? At every boot, MIUI overwrites RECOVERY partition for stock rom recovery partition and replaces any custom recovery like TWRP. This patch disables this overwriting and keep any custom...
forum.xda-developers.com
VD171 said:
Exactly.
If you want to use custom recovery but without root/magisk, you need to flash my patched boot image.
This patched boot image does NOT install back the default recovery and does NOT install root/magisk.
[BOOT][IMG][PATCHED] Boot Image Partition without OVERWRITE OF RECOVERY for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED BOOT.IMG for MERLIN by VD171 For what do I need it ? At every boot, MIUI overwrites RECOVERY partition for stock rom recovery partition and replaces any custom recovery like TWRP. This patch disables this overwriting and keep any custom...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks to everybody who replied. But i am using the command "fastboot reboot recovery" after flashing the recovery. But you are right, i did realise that if you just reboot to a stock ROM it reinstalls the stock recovery. Mea Culpa. But i wish this was explained someplace like a general explainer to a newbie.
Anyway, i downloaded the "Platform tools SDK" and used that fastboot and it now installs SHRP and Lineaage OS 18.1 recovery. But TWRP is still a problem. But at least i can install any custom ROM that i want. And yes, thanks VD171, i won't forget to use your patched boot image from now on.
12Frodo said:
Thanks to everybody who replied. But i am using the command "fastboot reboot recovery" after flashing the recovery. But you are right, i did realise that if you just reboot to a stock ROM it reinstalls the stock recovery. Mea Culpa. But i wish this was explained someplace like a general explainer to a newbie.
Anyway, i downloaded the "Platform tools SDK" and used that fastboot and it now installs SHRP and Lineaage OS 18.1 recovery. But TWRP is still a problem. But at least i can install any custom ROM that i want. And yes, thanks VD171, i won't forget to use your patched boot image from now on.
Click to expand...
Click to collapse
You are welcome, my friend.
Enjoy
Sadly, no one says that to you.
But, if you want to enter in recovery, just type "fastboot reboot" and hold the Vol Up button.
I am currently trying to flash TWRP to my old Xperia Z and when I try to flash it, fastboot spew me with an error:
Sending 'recovery' (15198 kB) OKAY [ 0.500s]
Writing 'recovery' FAILED (remote: 'Command not allowed')
fastboot: error: command failed
I unlocked the bootloader already and Treble Check reported that I have A-only
Can someone give me some solution to this?
The only way i got my phone to flash is by flashing it via the Sony Mobile Flasher
Dl: https://www.ytechb.com/sony-mobile-flasher/
once there unpack the RAR file
then get the fastboot and flasher drivers
and the driver for your specific model
then connect your device in fastboot mode
click the flash button (top left corner)
click fastboot mode
click flash kenel
change the explorer to search for .img files
click the TWRP img for you phone
hopefully should work