Take our customer survey to evaluate your visit.
It should only take a few minutes to answer five quick questions. Just click the Launch survey button at the end of your visit to begin.
2017-10-03 12:43 PM
Is there any step I've misssed to flash the
SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v02_tone.img for my Xperia XZ ?
log ( run as root):
fastboot flash oem SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v02_tone.img
target reported max download size of 268435456 bytes
sending 'oem' (212596 KB)...
OKAY [ 9.656s]
FAILED (remote: Command not allowed)
finished. total time: 9.670s
shasum from zip checked
2017-10-04 02:54 PM
unfortunately to fix this issue you have to wait for the next Sony software release because a bootloader update is needed
The hacky option is you want to test the image is to
1. convert the sparse vendor image to a regular ext4 image
2. copy the regular ext4 image to the data partition
3. flash the regular ext4 image to the oem partition using dd
2017-10-07 09:59 PM - edited 2017-10-08 06:09 AM
I caught a typo in a prior post and was able to reach the adb push step but I get errors trying to write to the device. I have not been able to upgrade beyond the stock rom since the Xperia flash tool does not show anything newer. I'm using the XZ Premium dual sim FR version.
# ../adb push * /odm/ adb: error: failed to copy 'bin/adsprpcd' to '/odm/bin/adsprpcd': remote secure_mkdirs failed: Read-only file system adb: error: failed to copy 'firmware/a530_pfp.fw' to '/odm/firmware/a530_pfp.fw': couldn't read from device adb: error: failed to send ID_SEND message '/odm/lib/libC2D2.so,33188': Success adb: error: failed to send ID_SEND message '/odm/lib64/libC2D2.so,33188': Success adb: warning: skipping empty directory 'lost+found/' lost+found/: 0 files pushed. 1 file skipped. 0 files pushed. 1 file skipped. 1.3 MB/s (22156 bytes in 0.016s)
I used some grey market tools download and flash 45.0.A.7.137 before successfully trying the oem img again, but I would still like to know the proper way to do it within the confines of AOSP and official support.
2017-10-09 10:20 AM
You need to remount the /odm partition to be writable, and I edited my previous post to reflect this. The same steps apply for the XZ Premium Dual, model no. G8142.
2017-10-09 03:39 PM
as I wrote in my previous post, you are not supposed to use adb to push independent files.
If you use adb you will lose both permissions and selinux lables and device will not boot corectly
2018-04-20 08:37 PM
I really want to know , if SW_binaries_for_Xperia_Android equals the file named ODM?
Is it has anotner name called vendor?
When I flash Omni rom and AOSP, I was asked to flash SW_binaries too.
When I try to build Lineage or other rom, I was asked to provide vendor.
So I wonder if they are the same thing.
If so, can I build Lineage rom without vendor? For I can flash vendor additionally after flashing Lineage.
Or do I need to write some code to extract vendor from my device?
hope your reply.
2018-04-23 10:35 AM
Sony AOSP build page shows OEM (as shown below) , is it odm or oem?
fastboot flash oem SW_binaries_for_Xperia_AOSP_O_MR0_4.4_<release version>_<platform>.img
2018-04-30 10:43 AM
please use the Sony Flashtool to update your device then you can flash the oem partition as it is described in the guide