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
Related
Hey,guys! I uesd fastboot to flash system,but it failed
code:
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.040s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.249s
anyone can help me please?
YOUNG MAN. said:
Hey,guys! I uesd fastboot to flash system,but it failed
code:
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.040s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 18.249s
anyone can help me please?
Click to expand...
Click to collapse
Try to use the mfastboot, because the system.img is to big to use the normal fastboot
libnijunior said:
Try to use the mfastboot, because the system.img is to big to use the normal fastboot
Click to expand...
Click to collapse
it failed too
code
target reported max download size of 536870912 bytes
sending 'system' (256089 KB)...
OKAY [ 8.035s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.062s
and sometimes it shows
target reported max download size of 536870912 bytes
sending 'system' (256598 KB)...
OKAY [ 8.046s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.224s
YOUNG MAN. said:
it failed too
code
target reported max download size of 536870912 bytes
sending 'system' (256089 KB)...
OKAY [ 8.035s]
writing 'system'...
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 13.062s
and sometimes it shows
target reported max download size of 536870912 bytes
sending 'system' (256598 KB)...
OKAY [ 8.046s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.224s
Click to expand...
Click to collapse
What version of boot loader do you have? If you already flashed the boot loader of 5.0.2 and you are trying to flash older system images that error appears.
juliospinoza said:
What version of boot loader do you have? If you already flashed the boot loader of 5.0.2 and you are trying to flash older system images that error appears.
Click to expand...
Click to collapse
I Just bought this phone yesterday and it was 5.0 when i got it. Then i updated to 5.1 and the BL version is 60.14 now . I tried to back to 5.0 so it showed this error.
Do you have any way to solve this problem? My phone is bootloop now.
Thanx
YOUNG MAN. said:
I Just bought this phone yesterday and it was 5.0 when i got it. Then i updated to 5.1 and the BL version is 60.14 now . I tried to back to 5.0 so it showed this error.
Do you have any way to solve this problem? My phone is bootloop now.
Thanx
Click to expand...
Click to collapse
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
JulesJam said:
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
Click to expand...
Click to collapse
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
YOUNG MAN. said:
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
Click to expand...
Click to collapse
Yes, they are synonyms. I would install Motorola Device Manager to your PC and let it attempt to repair your phone.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
If it doesn't repair your phone, post back here.
YOUNG MAN. said:
Yes,it is unlocked and i can get into fastboot mode .Is that bootlodader mode?
Click to expand...
Click to collapse
I installed Motorola Device Manager, what should i do next?
JulesJam said:
you really shouldn't downgrade unless you know what you are doing.
Is the bootloader unlocked? Can you get into bootloader mode?
Click to expand...
Click to collapse
I installed Motorola Device Manager and tried again, it still did't work.
code:
C:\Users\Alan\Desktop\ccc>fastboot flash system F:\XT1095\system.img_sparsechunk
.0
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.047s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.217s
YOUNG MAN. said:
I installed Motorola Device Manager and tried again, it still did't work.
Click to expand...
Click to collapse
Did it detect your device at all? Did it try to repair it?
YOUNG MAN. said:
C:\Users\Alan\Desktop\ccc>fastboot flash system F:\XT1095\system.img_sparsechunk
.0
target max-sparse-size: 256MB
sending 'system' (256598 KB)...
OKAY [ 8.047s]
writing 'system'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 13.217s
Click to expand...
Click to collapse
If you are only trying to flash small sparsechunks, have you tried flashing using the latest version of fastboot from Root Junky's site?
http://rootjunkysdl.com/?device=Adb Fastboot Files
Go into developer options and enable OEM unlocking. Then try it.
Edit: Forgot you said you were bootlooped. Can you install the 5.1 image again?
Sent from my XT1095
JulesJam said:
Did it detect your device at all? Did it try to repair it?
If you are only trying to flash small sparsechunks, have you tried flashing using the latest version of fastboot from Root Junky's site?
Click to expand...
Click to collapse
NO,It not detect my phone,it just search new software when i open it.
And I tried the latest version of fastboot,still failed
YOUNG MAN. said:
NO,It not detect my phone,it just search new software when i open it.
And I tried the latest version of fastboot,still failed
Click to expand...
Click to collapse
Did you try RSDLite?
JulesJam said:
Did you try RSDLite?
Click to expand...
Click to collapse
it can't detect my phone
YOUNG MAN. said:
it can't detect my phone
Click to expand...
Click to collapse
When you are in recovery, what does
adb devices
show you? Of course when you open the cmd window you have to navigate to a folder where adb.exe and the other required files are stored in order to use adb commands.
JulesJam said:
When you are in recovery, what does
adb devices
show you? Of course when you open the cmd window you have to navigate to a folder where adb.exe and the other required files are stored in order to use adb commands.
Click to expand...
Click to collapse
it shows View attachment 3294009
but in fastboot mode it shows View attachment 3294012
and my recovery is TWRP 2.8.60
YOUNG MAN. said:
it shows View attachment 3294009
but in fastboot mode it shows View attachment 3294012
and my recovery is TWRP 2.8.60
Click to expand...
Click to collapse
No I mean, connect your phone to your PC when you are in TWRP. Then open a command window. Then navigate to where adb.exe is stored - i.e, at the command prompt type in cd c:\[fill in the directory where adb.exe is stored]
then when you are at the proper directory, at the command prompt in the command window type:
adb devices
then hit enter.
It should return the serial number of your device.
JulesJam said:
No I mean, connect your phone to your PC when you are in TWRP. Then open a command window. Then navigate to where adb.exe is stored - i.e, at the command prompt type in cd c:\[fill in the directory where adb.exe is stored]
then when you are at the proper directory, at the command prompt in the command window type:
adb devices
then hit enter.
It should return the serial number of your device.
Click to expand...
Click to collapse
it shows this:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
device
dustin_b said:
Go into developer options and enable OEM unlocking. Then try it.
Edit: Forgot you said you were bootlooped. Can you install the 5.1 image again?
Sent from my XT1095
Click to expand...
Click to collapse
NO,my recovery is TWRP now ,and I can't flash the original recovery ,it failed.
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
Whenever i try to flash something to boot or recovery partition i get the following error:
Code:
:~/Desktop/New Folder/amonet$ fastboot flash boot boot.img
target reported max download size of 134217728 bytes
sending 'boot' (4676 KB)...
OKAY [ 0.230s]
writing 'boot'...
FAILED (remote:
Checksum Error.)
finished. total time: 0.382s
It is a false checksum error as i have downloaded it multiple times and flashed it to other devices of the same model.
Shamrock3six said:
Whenever i try to flash something to boot or recovery partition i get the following error:
It is a false checksum error as i have downloaded it multiple times and flashed it to other devices of the same model.
Click to expand...
Click to collapse
Just try with SP Flash Tool for Windows and Linux (any distributions).
https://spflashtool.com/
AmznUser444 Dev said:
Just try with SP Flash Tool for Windows and Linux (any distributions).
https://spflashtool.com/
Click to expand...
Click to collapse
What? Completely inappropriate suggestion for all but the most advanced tinkerers. Tossing into a (real) fire would be easier.
I accidently deleted my boot.img on mi Mi 9 Lite (Mi CC9) by doing: fastboot boot "random file". What can I do now?
Can Someone please send me their boot.img or a link?
..
realseal3 said:
..
Click to expand...
Click to collapse
https://www.sendspace.com/file/nddami
:fingers-crossed:
Thank you very much but I get an error message:
Sending 'boot.img' (15360 KB) OKAY [ 0.332s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
realseal3 said:
Sending 'boot.img' (15360 KB) OKAY [ 0.332s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Click to expand...
Click to collapse
What's the rom you have, miui version?
miui_PYXISGlobal_V11.3.3.0.PFCMIXM_6a3205a4b8_9.0
I have this one but it didn't boot before I did anything.
lmt399 said:
What's the rom you have, miui version?
Click to expand...
Click to collapse
realseal3 said:
miui_PYXISGlobal_V11.3.3.0.PFCMIXM_6a3205a4b8_9.0
I have this one but it didn't boot before I did anything.
Click to expand...
Click to collapse
Bootloader unlocked/locked?
Maybe it is better to flash the whole system through fastboot or mi flash tool.
..
It didn't work with the tool but I reflashed twrp and flashed the stock miui rom from there and it worked. Thank you anyway.
Download Fastboot rom and extract, then copy system.img to fastboot folder and also recovery, boot.img too...
Open fastboot:
Type: fastboot format system
Type: Fastboot flash boot boot.img version that you have when you brick device
Type: Fastboot flash system system.img
Type: Fastboot flash recovery recovery.img use wzsx1050 3.3.1-0709 version
Type :Fastboot boot recovery.img and device should reboot in recovery, without Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
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