• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 10.0.0 [STABLE]

Should I continue this project?

  • Yes, for the XZ2.

    Votes: 60 31.7%
  • Yes, for the XZ2C.

    Votes: 65 34.4%
  • Yes, for the XZ3.

    Votes: 62 32.8%
  • No.

    Votes: 2 1.1%

  • Total voters
    189
Search This thread

xz499

Member
Aug 9, 2020
22
9
Hey
The dumper is just a corner case workaround
The easiest way would be to fastboot boot the stock twrp on the stock ROM, flash the AOSP zip, maybe the dual sim patcher and what you need
Then in fastboot flash the OEM binary
And then you could boot the system or install the sodp twrp.

Nvm, it worked flawlessly at the end.

It was me just being impatient at fastboot commands thinking that bootloader just got stuck.

Also i managed to boot to SODP TWRP and did the mistake of wiping system.
So went back to flash stock again (twice today).

What's the difference between the codenames at your TWRPs in SODP folder at Android FIle Host (like one dated at 11 of June with SODP codename on it, and the other dated at 13 of June without it, as they're both under a SODP folder; again feel to forgive my dumbness if that's a silly/obvious question to you)?

P.D.: Yours is a smart solution. It's just me being dumb or something (it's not only today when it happens to me sadly, lol), or liking to make even harder my life (in this case was the first, rofl).
 

xz499

Member
Aug 9, 2020
22
9
Now the problem i have is that mobile data connection isn't working.

SIM registers and RIL works.

Back on stock it was working and also before of that.
 

MartinX3

Recognized Contributor
Sep 14, 2014
5,852
2,912
Mars
martinx3.github.io
Nvm, it worked flawlessly at the end.

It was me just being impatient at fastboot commands thinking that bootloader just got stuck.

Also i managed to boot to SODP TWRP and did the mistake of wiping system.
So went back to flash stock again (twice today).

What's the difference between the codenames at your TWRPs in SODP folder at Android FIle Host (like one dated at 11 of June with SODP codename on it, and the other dated at 13 of June without it, as they're both under a SODP folder; again feel to forgive my dumbness if that's a silly/obvious question to you)?

P.D.: Yours is a smart solution. It's just me being dumb or something (it's not only today when it happens to me sadly, lol), or liking to make even harder my life (in this case was the first, rofl).

Just use the newest TWRP.
I refactored / reduced the source code, which required a name change.
It made my developer life easier, hehe.

don't worry, I tend to ignore easier solutions as well some times, while I am too much focused fixing something. :silly:

Now the problem i have is that mobile data connection isn't working.

SIM registers and RIL works.

Back on stock it was working and also before of that.

It just needs a few minutes to calibrate?
You have a dual sim device and flashed the dual sim patcher?
You need to enable roaming based on your location?
Your provider has problems in this moment?
You get specific errors in your logs?
 

maverick6664

Senior Member
Aug 18, 2017
86
17
Hi @MartinX3, trying to install this through fastboot using Payload Dumper.

Bootloader struggles to flash a 3,9 GB system file.

Also you shouldn't just drop the bomb of using an standalone code without advertising how to setup and use it.

You should add to OP that python2 is needed and dependencies for it are:
python2-google
python2-protobuf
python2-backports.lzma
python2-pyliblzma

Maybe some of those aren't needed but i just installed them all to cover myself.

Now when it tries to boot it goes to stock recovery (i did follow all steps for flashing an SODP rom), with the next error message:
Cannot load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.

I just flashed latest ODP for TAMA and went from stock upgrade with August security patch.

Are you sure we have to flash a 3,9 GB system image all at once?
Any help will be appreciated.

Just a moment. I use payload_dumper with python3. README.md says
Code:
### System requirement

- Python3, pip
- google protobuf for python `pip install protobuf`

I use payload_dumper.zip with python3 on Fedora 33 and it works great.
 
Last edited:

xz499

Member
Aug 9, 2020
22
9
Just a moment. I use payload_dumper with python3. README.md says
Code:
### System requirement

- Python3, pip
- google protobuf for python `pip install protobuf`

I use payload_dumper.zip with python3 on Fedora 33 and it works great.

The payload Dumper @MartinX3 links in OP says in the first line of extract.py:

Code:
#!/usr/bin/env python2

Sharing that referral to us to that Payload Dumper python3 updated code would be much appreciated, thanks.

---------- Post added at 06:54 PM ---------- Previous post was at 06:46 PM ----------

Just use the newest TWRP.
I refactored / reduced the source code, which required a name change.
It made my developer life easier, hehe.

don't worry, I tend to ignore easier solutions as well some times, while I am too much focused fixing something. :silly:



It just needs a few minutes to calibrate?
You have a dual sim device and flashed the dual sim patcher?
You need to enable roaming based on your location?
Your provider has problems in this moment?
You get specific errors in your logs?

No problem about those names of TWRP.
Now the problem i have is that it's unable to read nor write Internal Storage.
I think it's a problem with SODP encryption. I've seen that kind of behaviour before (random letters and names for files and directories). Tried to format data, wipe internal storage and stablishing a password on the system as it seems to force encryption once it boots.

It just needs a few minutes to calibrate?
You have a dual sim device and flashed the dual sim patcher?
You need to enable roaming based on your location?
Your provider has problems in this moment?
You get specific errors in your logs?

1. Yes, but doesn't get data.
2. No, it's a H8416 (physically only has a SIM hole and a microSD on the plastic pieze).
3. No, it's the main ISP provider for my country.
4. Nope, other SIM for the same provider on a Realme 5 Pro (with LOS 17.1) and works flawlessly
4. Should i get any logcats?
 
Last edited:

MartinX3

Recognized Contributor
Sep 14, 2014
5,852
2,912
Mars
martinx3.github.io
The payload Dumper @MartinX3 links in OP says in the first line of extract.py:

Code:
#!/usr/bin/env python2

Sharing that referral to us to that Payload Dumper python3 updated code would be much appreciated, thanks.

---------- Post added at 06:54 PM ---------- Previous post was at 06:46 PM ----------



No problem about those names of TWRP.
Now the problem i have is that it's unable to read nor write Internal Storage.
I think it's a problem with SODP encryption. I've seen that kind of behaviour before (random letters and names for files and directories). Tried to format data, wipe internal storage and stablishing a password on the system as it seems to force encryption once it boots.



1. Yes, but doesn't get data.
2. No, it's a H8416 (physically only has a SIM hole and a microSD on the plastic pieze).
3. No, it's the main ISP provider for my country.
4. Nope, other SIM for the same provider on a Realme 5 Pro (with LOS 17.1) and works flawlessly
4. Should i get any logcats?

The decryption should work after you installed the TWRP.
This bug should disappear after the migration to the native TWRP 10 and it doesn't harm your data.

Yes, a "logcat -b all" from a fresh boot after you entered your SIM pin and tried the internet.
 

xz499

Member
Aug 9, 2020
22
9
XZ3 H8416 EU Single SIM

The decryption should work after you installed the TWRP.
This bug should disappear after the migration to the native TWRP 10 and it doesn't harm your data.

Yes, a "logcat -b all" from a fresh boot after you entered your SIM pin and tried the internet.

Decryption is not working after TWRP is installed. Bug is still there.

Logcat attached.
 

Attachments

  • 1_logcat-d.log.zip
    161.7 KB · Views: 3

bigrammy

Senior Member
Apr 8, 2011
2,939
2,550
huddersfield
Help our Sony devices.

The Sony Open Devices Project is always happy about volunteers (coding, testing, etc) :)
Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!
Hi MartinX,
Well I have been reaching out to the Sony Open Devices Project but got zero help or advice so far.
Thing is Sony now have quite a extensive range of Mediatek device with most even having functioning custom ROM's like Lineage but we ALL hit the exact same brick wall when it comes to getting the modem working and sim detection working on custom roms :mad:
I am 99.9% sure this is to do with the Sony stuff and NOT Mediatek's.
I don't think any of us working on these MTK devices really understand how all the ta, miscta, nvram modem etc all tie up together :silly:
We would really appreciate some hands on help from someone fully immersed in SODP to pick through the kernel source, ROM, etc to see if they can see what we are all missing.
I could donate a device to anyone who's up for the challenge
To sum up If we can get a top flight dev on board I could donate.
1. Sony L1 (Mediatek MT6737) release firmware Android 7.0
2. FULL Mediatek Android 8.1 source for the MT6737 SoC should any of Stock pre built binaries need tweaking
3. Kernel Source that builds and works 100% with the stock ROM (Courtesy of Sony)
While the L1 is basic it's pretty solid and works well It's sister phone the L2 also shares the same SoC and Kernel source and runs Android 7.1.1.
I think once the missing piece of the puzzle is found this will have a domino effect with all the Sony MTK's being able to run AOSP ROM's and others.
Feel free to PM me if needs be.

Some Example Projects and info:
https://forum.xda-developers.com/xperia-l1/development
https://github.com/PineDevelopment
https://forum.xda-developers.com/xperia-xa/development/tuba-lineageos-14-1-t3878212
https://github.com/SonyCustoms
https://forum.xda-developers.com/xperia-m5/rom-lineageos-13-sony-xperia-m5-hollyss-t3589082
https://github.com/krkshalil/android_device_sony_holly-common
( mt6795 is in the main Linux Kernel if I am not mistaken)
https://github.com/mbgg/linux-mediatek
https://android.googlesource.com/kernel/mediatek/
This smart display BSP below has the mtk drivers left in (drivers/misc/mediatek) and what seem more linux / android def_configs.
https://android.googlesource.com/pl...s/android-o-mr1-iot-release-smart-display-r12





.
 

MartinX3

Recognized Contributor
Sep 14, 2014
5,852
2,912
Mars
martinx3.github.io
Hi MartinX,
Well I have been reaching out to the Sony Open Devices Project but got zero help or advice so far.
Thing is Sony now have quite a extensive range of Mediatek device with most even having functioning custom ROM's like Lineage but we ALL hit the exact same brick wall when it comes to getting the modem working and sim detection working on custom roms :mad:
I am 99.9% sure this is to do with the Sony stuff and NOT Mediatek's.
I don't think any of us working on these MTK devices really understand how all the ta, miscta, nvram modem etc all tie up together :silly:
We would really appreciate some hands on help from someone fully immersed in SODP to pick through the kernel source, ROM, etc to see if they can see what we are all missing.
I could donate a device to anyone who's up for the challenge
To sum up If we can get a top flight dev on board I could donate.
1. Sony L1 (Mediatek MT6737) release firmware Android 7.0
2. FULL Mediatek Android 8.1 source for the MT6737 SoC should any of Stock pre built binaries need tweaking
3. Kernel Source that builds and works 100% with the stock ROM (Courtesy of Sony)
While the L1 is basic it's pretty solid and works well It's sister phone the L2 also shares the same SoC and Kernel source and runs Android 7.1.1.
I think once the missing piece of the puzzle is found this will have a domino effect with all the Sony MTK's being able to run AOSP ROM's and others.
Feel free to PM me if needs be.

Some Example Projects and info:
https://forum.xda-developers.com/xperia-l1/development
https://github.com/PineDevelopment
https://forum.xda-developers.com/xperia-xa/development/tuba-lineageos-14-1-t3878212
https://github.com/SonyCustoms
https://forum.xda-developers.com/xperia-m5/rom-lineageos-13-sony-xperia-m5-hollyss-t3589082
https://github.com/krkshalil/android_device_sony_holly-common
( mt6795 is in the main Linux Kernel if I am not mistaken)
https://github.com/mbgg/linux-mediatek
https://android.googlesource.com/kernel/mediatek/
This smart display BSP below has the mtk drivers left in (drivers/misc/mediatek) and what seem more linux / android def_configs.
https://android.googlesource.com/pl...s/android-o-mr1-iot-release-smart-display-r12
.

Hey :)
As far as I know most of the xperia experience at SODP was made with snapdragons.
But I redirected your message, maybe someone will respond. :)
 

bigrammy

Senior Member
Apr 8, 2011
2,939
2,550
huddersfield
Hey :)
As far as I know most of the xperia experience at SODP was made with snapdragons.
But I redirected your message, maybe someone will respond. :)
Thanks I appreciate that :fingers-crossed:
Nothing mystical about mediatek SoC really. Sure it's a little bit different to snapdragons but I don't think the leap is too far for anyone used to this stuff.
Much more confusing is Sony's implementation of TA, Misc-TA, modem configs, device ID's USB's and general data shuffling :eek:
It's like the old ball under the 3 cup's trick with Sony shuffle shuffle where's it now?
Answer: Not a ****** clue here's my money! Go again I will watch closer this time. mmm Yeh still not got it. Go again :laugh:
 

Haxk20

Senior Member
Aug 18, 2015
494
554
Hi MartinX,
Well I have been reaching out to the Sony Open Devices Project but got zero help or advice so far.
Thing is Sony now have quite a extensive range of Mediatek device with most even having functioning custom ROM's like Lineage but we ALL hit the exact same brick wall when it comes to getting the modem working and sim detection working on custom roms :mad:
I am 99.9% sure this is to do with the Sony stuff and NOT Mediatek's.
I don't think any of us working on these MTK devices really understand how all the ta, miscta, nvram modem etc all tie up together :silly:
We would really appreciate some hands on help from someone fully immersed in SODP to pick through the kernel source, ROM, etc to see if they can see what we are all missing.
I could donate a device to anyone who's up for the challenge
To sum up If we can get a top flight dev on board I could donate.
1. Sony L1 (Mediatek MT6737) release firmware Android 7.0
2. FULL Mediatek Android 8.1 source for the MT6737 SoC should any of Stock pre built binaries need tweaking
3. Kernel Source that builds and works 100% with the stock ROM (Courtesy of Sony)
While the L1 is basic it's pretty solid and works well It's sister phone the L2 also shares the same SoC and Kernel source and runs Android 7.1.1.
I think once the missing piece of the puzzle is found this will have a domino effect with all the Sony MTK's being able to run AOSP ROM's and others.
Feel free to PM me if needs be.

Some Example Projects and info:
https://forum.xda-developers.com/xperia-l1/development
https://github.com/PineDevelopment
https://forum.xda-developers.com/xperia-xa/development/tuba-lineageos-14-1-t3878212
https://github.com/SonyCustoms
https://forum.xda-developers.com/xperia-m5/rom-lineageos-13-sony-xperia-m5-hollyss-t3589082
https://github.com/krkshalil/android_device_sony_holly-common
( mt6795 is in the main Linux Kernel if I am not mistaken)
https://github.com/mbgg/linux-mediatek
https://android.googlesource.com/kernel/mediatek/
This smart display BSP below has the mtk drivers left in (drivers/misc/mediatek) and what seem more linux / android def_configs.
https://android.googlesource.com/pl...s/android-o-mr1-iot-release-smart-display-r12
.

Could you share logcat and dmesg please ?
Otherwise we have no clue what is possibly wrong. It may be a missing library or just wrong code. We dont know without dmesg and logcat.
 

bigrammy

Senior Member
Apr 8, 2011
2,939
2,550
huddersfield
Could you share logcat and dmesg please ?
Otherwise we have no clue what is possibly wrong. It may be a missing library or just wrong code. We dont know without dmesg and logcat.
Hi sorry for the late reply I have been at work today.
Here are some radio logs I have to hand.
This one is without the sim card inserted:
The IMEI's display and everything looks normal.
https://gist.github.com/bigrammy/52f621364c7bb346827e68d5b2d81594

This is the same with the sim inserted:
IMEi's all show as UNKOWN
https://gist.github.com/bigrammy/54d7ac3fbf4696b5189311fc5515246d

I have a dmesg some place and I will point to it when I find it.
I don't want to hijack @MartinX3 thread so can we switch over to the assistance thread I just started in the Xperia L1 dev section.
https://forum.xda-developers.com/xperia-l1/development/sodp-assistance-thread-t4174977

Thanks for the interest. :highfive:



.
 

kirin72212

Member
Jun 7, 2013
13
1
Taipei
can't flash sony-dualsim-patcher v4

HI

My device is H9493

i flash the rom is OK

but when i reboot my phone and used recovery to adb sideload sony-dualsim-patcher v4

it shows e:error in /sideload/package.zip(killed by signal 11)

how can i do to solve this problem?

please help me thank u.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 16
    https://developer.sony.com/develop/open-devices/latest-updates

    OEMv2 got released
    Added camera, sound calibration, sensors. Also fixed keymaster and Adreno.

    The ROM also got stability updates and enhancements.

    The next release I will publish will contain a better camera and fixes against the sound issues (compared to my android 9.0 builds with kernel 4.9).

    The XZ2, XZ2c & XZ3 are on a good way thanks to the Sony Open Devices Developers (Volunteers and Sony Employees). :D
    15
    The Sony Open Devices Project is always happy about volunteers (coding, testing, etc) :)
    Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you!


    Code:
    #include <std_disclaimer.h>
    /*
    *
    * We are not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at us for messing up your device, we will laugh at you.
    *
    */

    This is the AOSP ROM for the Sony Xperia XZ2 (akari), XZ2C (apollo) and XZ3 (akatsuki)

    This ROM build will always mainly based on Sony AOSP Code and maybe include cherry-picks.
    I plan to make monthly builds, after a new security patch level, if there is no need for a critical hotfix.

    FAQ:
    jerpelea said:
    for a complete security patch you have to
    1. flash the stock firmware using https://developer.sony.com/develop/open-devices/get-started/flash-tool/
    2. build and flash the ROM
    * The security patch may affect or not the proprietary parts depending on HW and implementation
    * After official support ends you can still get security updates for kernel and Android but loader and firmware will be stuck to the latest official release

    Bugtracker:

    Bugreport:
    • A bugreport needs
      Code:
      logcat -b all
      and a way to reproduce the issue.
    • A crash of the system requires the content of the /sys/fs/pstore folder as bug report
      • Be aware that a second reboot erases this folder
    • A crash to the recovery partition requires additionally the content of the /dev/block/by-name/misc partition
      • You get the content via `cat /dev/block/by-name/misc partition > /path/to/output/file.txt`
    • To rescue a not responding phone:
      • VOLUP+POWER for 3 Seconds -> RESTART with one Vibration.
      • VOLUP+POWER for 20 Seconds -> SHUTDOWN with 3 Vibrations.
      • VOLUP+POWER+CAMERA for 30 Seconds -> HARDWARE SHUTDOWN by discharging a capacitor.

    Thank you very much for your help, code contribution & testing! (Random order):
    • @jerpelea, the sony employees and their volunteers (people like you and me) coding this wonderful piece of software
    • @dhacke for providing a download server
    • @Raphos for the initial installation manual without a recovery system, after I switched to OTA zips.
    • @kgvarunkanth for the jenkins build server
    • And many thanks to the few donators! :)

    A telegram group for technical SODP stuff:

    XDA:DevDB Information
    AOSP, ROM for the Xperia XZ2

    Contributors
    MartinX3, Sony, SonyAOSP
    Source Code: https://github.com/sonyxperiadev

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.x
    ROM Firmware Required: Latest Stock Firmware
    Based On: AOSP

    Version Information
    Status:
    No Longer Updated
    Current Stable Version: 10

    Created 2019-09-29
    Last Updated 2020-10-23
    9
    Ok, now using it as my daily driver, as far no issues. Lacking suport for night light mode aka yellow screen and ambient display on proximity and accelerometer. Also no Widevine support then no Netflix., the only drawback for me. And GPay do not pass the security test, supposedly due to selinux or something else. :confused:
    LDAC is not working correctly, stuttering audio on every single codec except SBC at 44.1 KHz. KCal is broken.

    Installation procedure:
    • Install the ROM as per OP's guide
    • Install Magisk Manager 7.4.0
    • Copy boot.img to the device via mtp at e.g. /sdcard or /sdcard/downloads
    • Install magisk via magisk manager, chose Manually patch image and select the previously copied boot.img
    • The resulted magisk-patched.img has to be copied back to pc
    • flash magisk-patched.img via fastboot
    • download lastest opengapps beta nano for android 10 (nothing more than 250 Mb)
    • Copy opengapps.zip to the device via mtp
    • Install FK Kernel Manager
    • In FK chose Flasher, uncheck the Reboot after flashing
    • Chose Manual Flasher and pick your opengapps.zip
    • Once flashed go to System settings - System - Reset - Factory reset aka wype everything
    • Wait for the first boot and perform a normal setup with your google account
    • Profit!;)

    https://github.com/topjohnwu/Magisk/releases/download/manager-v7.4.0/MagiskManager-v7.4.0.apk
    https://sourceforge.net/projects/op...ps-arm64-10.0-nano-20191209-BETA.zip/download
    https://play.google.com/store/apps/details?id=com.franco.kernel

    Good luck and keep looking at what you're doing, be ready to use Emma flasher and got your data lost.
    Disclaimer: everything at your own risk
    7
    Download & Installation

    Download ROM:

    Download Drivers:
    • OEM (Tama) binaries
      • Please use the the OEM build which came before my last release, unless otherwise written.

    GCAM Camera App:
    • Suggested GCams But GCAM's aren't usable at the moment until a camera hardware resource budget bug got fixed in the OEM binary blob.

    Installation with a recovery:
    1. fastboot flash oem_a oem_*.img
    2. fastboot flash oem_b oem_*.img
    3. Flash the ROM in a recovery
    4. Reboot into recovery just to make sure you're on the new slot
    5. OpenGapps
    6. Dual Sim Patcher
    7. (In case a modification prevents your device from booting) fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

    Flash the ROM without a recovery:
    1. Extract the payload.bin from the .zip file
    2. Extract the .img files with the Playload Dumper
    3. fastboot flash boot_a boot.img
    4. fastboot flash boot_b boot.img
    5. fastboot flash dtbo_a dtbo.img
    6. fastboot flash dtbo_b dtbo.img
    7. fastboot flash system_a system.img
    8. fastboot flash system_b system.img
    9. fastboot flash vbmeta_a vbmeta.img
    10. fastboot flash vbmeta_b vbmeta.img
    11. fastboot flash vendor_a vendor.img
    12. fastboot flash vendor_b vendor.img
    13. fastboot -w (Wipes your internal storage and the userdata)
    14. Continue with the normal installation
    5
    Is there changelog for the new oem? :)

    Yes, the new OEMv2c fixes the incall audio :D

    Currently I'm compiling the new release with every fix and optimization in the open source part made since last release + dezember security patch level.