Database Develop

[Q] XT1095 fastboot flash system.img failed

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.

[Q] Nexus 6 Factory Images

I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.

GuardianUSMC said:
I have been doing this for a while but I am relatively new to Android and specifically to Nexus 6 so bear with me. If the question has already been asked, answered or discussed, I apologize but a quick search didn't reveal anything so here I am. Also please refrain from unkind and snarky comments, just be professional and helpful please.
My question has to do with the Factory Images from Google, such as 5.1.0 (LMY47I) available direct from Google Developers. Are these files considered "at root"? or do they need to be rooted still? And if they need to be rooted, can they be rooted BEFORE the flashing?
Thank you in advance.
Click to expand...
Click to collapse
No, you cannot ad root to the image before flashing.
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.

gee2012 said:
No, you cannot ad root to the image before flashing.
Click to expand...
Click to collapse
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Best/easiest way to root is:
- Enable usb debugging and enable OEM UNLOCK in developer options
- Unlock the bootloader in fastboot with cmd command: fastboot oem unlock
- Flash the latest factory image in fastboot/bootloader mode. You have too flash the img`s seperately.
- Then flash or boot into TWRP and flash the latest superSU.zip and reboot
- Install BusyBox from Play and you`re all set.
Click to expand...
Click to collapse
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.

GuardianUSMC said:
Well that's unfortunate. So the factory images provided directly by Google are NOT at root already either?
Thank you, I apologize for not including this information earlier but I currently have an unlocked OEM (did that before I rooted the phone) but since the OTA will not install and frankly I have always been a fan of clean install over upgrade and patch, so decided to just go ahead and flash the latest image. But I figured this time to research and see if I can do some prep to make it go smoother and quicker.
Thank you for the steps but I do have one question about what you said. You say flash or boot into TWRP, since that is not installed by default images, that means grab it of the TWRP page, which I was looking at earlier, and then flash that so I can do SU. The default recovery doesn't allow you to flash the SU? I just hate too add too many unnecessary things if I can do it with what's there. Which brings me to the busybox, is it necessary and if so, for what exactly? I have never actually found myself face to face with it for anything.
Thank you again for the response, I appreciate it.
Click to expand...
Click to collapse
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.

gee2012 said:
Just place TWRP in the fastboot/platform-tools folder, reboot into fastboot and in cmd type : fastboot boot name-recovery.img. Now you can flash the superSU.zip and still keep stock recovery. You can`t flash custom files with the stock recovery no.
Click to expand...
Click to collapse
Got it, thank you very much for your assistance.
Too bad the Factory Images from Google are not already rooted.

GuardianUSMC said:
So the factory images provided directly by Google are NOT at root already either?
Click to expand...
Click to collapse
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
So for example on a linux machine you will have the root directory:
/
Within root, you will have other directories such as:
/bin
/etc
/usr
See here for more information:
http://www.thegeekstuff.com/2010/09/linux-file-system-structure/
So root is kind of like the C:\ drive on a Windows PC. Everything to do with the OS and User directories are within there.
Your Android device is the same, however, /bin, /etc (etc) are not at the root of the device. They sit within the system partition, which sits within root. so /system/bin, /system/etc. When you flash a factory image, it flashes the images to /system, /cache, /userdata (and a few other places) where as the root of the device remains largely untouched.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.

@rootSU,
Excellent mini tutorial. I wish this could be stickied on the General roll up thread. Thank you very much.

rootSU said:
Hi,
We're getting mixed up with terminology here. The images are not AT root, but also are NOT rooted. These mean different things so I want to elaborate on that for you.
Click to expand...
Click to collapse
I appreciate that and forgive me I know I used the terms interchangeably and that's my bad.
The android kernel is linux based, which means that the terminology and device structure are loaned from that technology. Root in linux terms, means the root of the device. This is if you imagine the file structure of a computer using directories, the very top-most directory in the structure that every other directory sits within, is called root.
Click to expand...
Click to collapse
yes I am familiar with that and I was using the term to mean having root privileges, again my bad.
Now in order to access these root directories, you must have a superuser account (su) and the process for achieving this on android is called "rooting". If you succeed in this process, you have "rooted" or have "root" which is sort of incorrect and leads to confusion.
Click to expand...
Click to collapse
Understood, I have done that and my device is currently rooted. I was more looking into making an image that is already rooted, to borrow a term from Windows, slipstream the root functionality pre-flashing. I was told not going to happen, that's fine. Although when I had my HTC Evo 4G, I had pre-rooted images that I had created with the bloat removed and I was flashing them with root functionality out of the box, but that's another story, I guess Nexus 6 is a different animal and dealing with Lollipop probably more difficult than Gingerbread.
I know this isn't too related to your question, but I wanted to clarify it in case you weren't sure - based on the phrasing of your question.
Click to expand...
Click to collapse
No but I appreciate you taking the time, thank you.
Right now mostly I am frustrated with the fact that the factory images provided by google will not flash right and keep *****ing about missing .sig files. I have tried flashing them individually by taking the root, system, recovery images out of the zip file and doing them individually as been suggested all over the place but no luck there there, keeps *****ing about the partitions instead, makes no sense. The bootloader and radio images go through without a hitch but the rest is just a mess.

Just to share, I am trying to flash the factory image that I mentioned in my original post, so I won't repost it. Here is what did so far to no avail, so any assistance would be greatly appreciated:
I issue the command adb reboot bootloader and it successful reboots the phone into the bootloader
Extracting the folder shamu-lmy47i containing the following files:
bootloader-shamu-moto-apq8084-71.08.img
flash-all.bat
flash-all.sh
flash-base.sh
image-shamu-lmy47i.zip
radio-shamu-d4.0-9625-02.95.img
Opening the batch file you see the following (I have removed the copyright header for sake of brevity)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy47i.zip
echo Press any key to exit...
pause >nul
exit
Since the only thing I want to add to this is root, I add this after the image update:
Code:
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
So we let it rip and this is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.548s]
finished. total time: 0.674s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.720s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.102s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
downloading 'boot.img'...
OKAY [ 0.393s]
booting...
OKAY [ 0.024s]
finished. total time: 0.419s
Press any key to exit...
As we can see, bootloader image flashes just fine
The radio image flashes just fine
System image on the other hand does not update complaining about missing .sig files:
fastboot -w update image-shamu-lmy47i.zip said:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1778160592 bytes
error: update package missing system.img
Click to expand...
Click to collapse
The files inside this system zip are:
android-info.txt
boot.img
cache.img
recovery.img
system.img
userdata.img
Ironically the SuperSU image flashes just fine and reboots the phone
I am frustrated by the fact that the system image update step fails and nothing out there explains why? I have even tried to extract each of those images from the zip file and flashing them individually using the fastboot flashall but getting the same error as well as other errors.
Can anyone lend an assist on this and help me figure out how to overcome that hurdle PLEASE?

Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.

Evolution_Freak said:
Follow method 2 here:
http://forum.xda-developers.com/showthread.php?t=2954008
Do not use flashall.
Also, please provide more information on the errors. That matters.
Click to expand...
Click to collapse
I did provide everything step by step the only thing I didn't provide was the errors on the individual images that are within the update zip file. Which I suppose is my bad:
Code:
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
and I have tried flashall last because documentation states it will do boot, recovery and system but I have also done them using individual commands too. But more on that after I take a look at what you posted in the link. Stay tuned. Thank you.

Alright, good news, it worked and thank you for pointing to the resource that allowed me to figure out why I was getting the partition errors, now I know.
I modified the batch file as follows:
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
adb reboot bootloader
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase cache
fastboot flash cache cache.img
fastboot reboot-bootloader
fastboot boot CF-Auto-Root-shamu-shamu-nexus6.img
echo Press any key to exit...
pause >nul
exit
it went through the whole process and here is the resulting output:
Code:
C:\Users\Major\Desktop\shamu-lmy47i>flash-all.bat
< waiting for device >
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.123s]
writing 'bootloader'...
(bootloader) flashing partition ...
(bootloader) This may take a few seconds if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
(bootloader) flashing rpm ...
(bootloader) flashing tz ...
(bootloader) flashing sdi ...
(bootloader) flashing logo ...
OKAY [ 0.508s]
finished. total time: 0.632s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.002s
< waiting for device >
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.722s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 1.110s]
finished. total time: 3.834s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
target reported max download size of 536870912 bytes
sending sparse 'system' (522196 KB)...
OKAY [ 22.442s]
writing 'system'...
OKAY [ 7.691s]
sending sparse 'system' (510114 KB)...
OKAY [ 21.723s]
writing 'system'...
OKAY [ 6.674s]
sending sparse 'system' (514997 KB)...
OKAY [ 21.128s]
writing 'system'...
OKAY [ 7.778s]
sending sparse 'system' (189177 KB)...
OKAY [ 7.652s]
writing 'system'...
OKAY [ 2.328s]
finished. total time: 97.428s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 11.844s]
sending 'userdata' (138868 KB)...
OKAY [ 4.518s]
writing 'userdata'...
OKAY [ 1.949s]
finished. total time: 18.315s
target reported max download size of 536870912 bytes
sending 'boot' (7681 KB)...
OKAY [ 0.247s]
writing 'boot'...
OKAY [ 0.110s]
finished. total time: 0.359s
target reported max download size of 536870912 bytes
sending 'recovery' (8273 KB)...
OKAY [ 0.266s]
writing 'recovery'...
OKAY [ 0.116s]
finished. total time: 0.384s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.045s]
finished. total time: 0.046s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.013s]
sending 'cache' (6248 KB)...
OKAY [ 0.204s]
writing 'cache'...
OKAY [ 0.097s]
finished. total time: 0.318s
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
downloading 'boot.img'...
OKAY [ 0.399s]
booting...
OKAY [ 0.035s]
finished. total time: 0.436s
Thank you for everyone's input and assistance here, you rock.

Waiting for any device :)

im stuck with this piece of sh*t phone and "waiting for any device". I flashed TWRP 142314 times on my phone, and today this bloody problem comes out and i cant f*king solve it. My drivers and everything is up to date, expect something named "S1 Boot Fastboot" (warning sing near that in device manager). I have no idea what the hell is that and i cant flash twrp and install custom rom. Any ideas, excpet that one about uninstalling win10 )))

yey, a new problem:
C:\Users\nevas\Desktop\sony\ADB\platform-tools-latest-windows\platform-tools>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.350s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.356s

nevenx said:
yey, a new problem:
C:\Users\nevas\Desktop\sony\ADB\platform-tools-latest-windows\platform-tools>fastboot flash recovery twrp.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.350s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.356s
Click to expand...
Click to collapse
You can't flash TWRP to the recovery partition on the Xperia Z. It doesn't use the recovery partition; instead, it uses the FOTAKernel partition, which is inaccessible by Fastboot. If you want to destroy your old stock firmware and install custom ROM, flash TWRP to boot partition. The phone should not boot to the firmware and boots straight to TWRP.

Unable to unlock/flash recovery

I am trying to unlock the bootloader and flash TWRP for the first time. I followed the steps from here: https://wiki.lineageos.org/devices/s2/install
I turned on the unlock option in settings and unlocked via fastboot, rebooted it manually (it didn't reboot), and then tried to flash:
Code:
$ ./fastboot oem unlock-go
OKAY [ 0.007s]
Finished. Total time: 0.007s
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.859s]
Writing 'recovery' FAILED (remote: 'Partition flashing is not allowed')
fastboot: error: Command failed
$ ./fastboot reboot
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.001s
$ ./adb reboot bootloader
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.779s]
Writing 'recovery' FAILED (remote: 'Partition flashing is not allowed')
fastboot: error: Command failed
$ ./fastboot oem unlock-go
OKAY [ 0.007s]
Finished. Total time: 0.007s
$ ./fastboot flash recovery twrp-3.3.1-0-s2.img
Sending 'recovery' (24618 KB) OKAY [ 0.836s]
Writing 'recovery' OKAY [ 0.231s]
Finished. Total time: 1.071s
$ ./fastboot reboot recovery
Rebooting into recovery OKAY [ 0.001s]
Finished. Total time: 0.001s
However, I got into the stock recovery page instead of TWRP. You can see above that the flash failed before I rebooted, but succeeded after that. Interesting observations:
- The above webpage indicates that the device should reset when I reboot, but it didn't, which means the unlock didn't work.
- When I went back to bootloader, the first attempt to flash failed, but when I ran another unlock it worked though apparently it did nothing.
Am I missing a step? I am using fastboot version 29.0.6-6198805 on Mac OS Mojave 10.14.6.

Don't reboot to recovery via a command after flashing it.
Try rebooting using buttons, vol-up + power.

kalehrl said:
Don't reboot to recovery via a command after flashing it.
Try rebooting using buttons, vol-up + power.
Click to expand...
Click to collapse
Thank you! That got me into TWRP with a dialog titled "Unmodified System Partition" with a slider to allow modifications. I am googling to see what this dialogue is about and how to get TWRP to permanently get installed.

That's normal. Just enable modifications and that's it.

kalehrl said:
That's normal. Just enable modifications and that's it.
Click to expand...
Click to collapse
OK, I don't remember seeing it before (I haven't flashed in at least a couple of years). I ran `adb reboot recovery` and it did go back into TWRP, so I am assuming that it did get persisted. For some reason "Never show this screen..." option didn't work, which is fine, but does it indicate that something is still readonly?

I don't think so.
You're good to proceed.

I was able to sideload the ROM and opengapps nano and it is booting up for the first time. I skipped the optional step to install root (AddonSU), I guess I can do it later too if I feel the need to get root. Thanks a lot for your quick help.

No problem.
If you want to root it, do it with Magisk.
Nowadays, LineageOS team recommend it.

remove TWRP and install Linageos recovery error.

I have a pixel 5, i installed linageos recovery and lineageos rom
however when i tried TWRP it now is frozen on splashscreen for recovery project 3.7.0_11.0
i tried flashing back lineage, it says it worked but when i restart recovery the same splash screen is there.
>fastboot flash vendor_boot vendor_boot.img
Sending 'vendor_boot_b' (98304 KB) OKAY [ 2.986s]
Writing 'vendor_boot_b' OKAY [ 2.071s]
Finished. Total time: 5.329s
Click to expand...
Click to collapse
When i try to simple boot recovery i get this error.
>fastboot boot vendor_boot.img
creating boot image...
creating boot image - 100665344 bytes
Sending 'boot.img' (98306 KB) OKAY [ 2.972s]
Booting (bootloader) boot.img missing cmdline or OS version
FAILED (remote: 'Error verifying the received boot.img: Unsupported')
fastboot: error: Command failed
Click to expand...
Click to collapse
And same error when i try booting TWRP
>fastboot boot twrp-3.7.0_11-0-redfin.img
Sending 'boot.img' (98304 KB) OKAY [ 2.936s]
Booting (bootloader) boot.img missing cmdline or OS version
OKAY [ 2.318s]
Finished. Total time: 5.343s
Click to expand...
Click to collapse
after trying to boot TWRP it does this error and then goes into recovery mode back to splash screen
How do i wipe recovery and get linageos recovery back in my pixel please?

if TWRP stuck on splash screen you can still use it from cmd line
https://twrp.me/faq/openrecoveryscript.html