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

[ROM][D6603][UNOFFICIAL][CM-13.0] experimental/under development [2017-01-27]

Search This thread

akincakiner

Member
Jun 12, 2016
27
3
I have a question, i. e., I am a daily user and I am concern about how the upgrade from CM12.1 to Lineage 14.1 will be done, would I got to wipe my data (Meh) or would it be possible to upgrade it as an update ?

First make always a backup before upgrading.
I tryed to do a normal Update without wiping chache/data. but didn't work. and than i tryed with wiping data. that did work for me
 

nailyk

Senior Member
Oct 3, 2015
1,503
2,955
I have a question, i. e., I am a daily user and I am concern about how the upgrade from CM12.1 to Lineage 14.1 will be done, would I got to wipe my data (Meh) or would it be possible to upgrade it as an update ?
Funny, you are asking about cm-12.1 and 14.1 in the 13.0 thread :)
It should work. However I didn't try for a while. Maybe an option will be to pass multiples releases, maybe the 13.0 between.
As 14.1 isn't really usable yet, don't really look at this for now.
 
  • Like
Reactions: MrFantome

nailyk

Senior Member
Oct 3, 2015
1,503
2,955
Briefly, the unique solution is using Stock kernel and you could get it into Z5. Will you be able to do in Z3?
Sorry for this moving but looks like more relevant here ;)

If you reread the thread (around the page 12) you should find all my kernel experiments. I was able to start this rom with almost every 3.4 kernels.
IIRC stock M blobs refused to start with something like "Can't start, unauthorized". A DRM thingamajig I can't figure remain somewhere, *not into the bootloader or in the TA partition* however (experiments also in this thread), it is kernel related.

Said often I make mistake, maybe made something wrong on my first experiment, so if you are comfortable enough to experiment you could try with this cm-13.0. It is (almost) stock based, then replace with stock blobs. (maybe leave the hammerhead adreno in place to keep device booting).

Also the only remaining test to do is the same one, but with concept. Maybe the open sourced concept kernel can start the associated blobs.

Good luck and keep us informed :)

CC: @tomascus

P.S.: I think it is easiest to do those experiments on CM-13.0 because it is M and will not require shim to work properly.
P.S.2: tomascus: if you can provide me a q&d stock kernel I can test if a custom build stock break camera on full stock device.
 
  • Like
Reactions: mattia.bf

tomascus

Recognized Developer
Jun 5, 2012
1,903
2,649
Melbourne
Sorry for this moving but looks like more relevant here ;)

If you reread the thread (around the page 12) you should find all my kernel experiments. I was able to start this rom with almost every 3.4 kernels.
IIRC stock M blobs refused to start with something like "Can't start, unauthorized". A DRM thingamajig I can't figure remain somewhere, *not into the bootloader or in the TA partition* however (experiments also in this thread), it is kernel related.

Said often I make mistake, maybe made something wrong on my first experiment, so if you are comfortable enough to experiment you could try with this cm-13.0. It is (almost) stock based, then replace with stock blobs. (maybe leave the hammerhead adreno in place to keep device booting).

Also the only remaining test to do is the same one, but with concept. Maybe the open sourced concept kernel can start the associated blobs.

Good luck and keep us informed :)

CC: @tomascus

P.S.: I think it is easiest to do those experiments on CM-13.0 because it is M and will not require shim to work properly.
P.S.2: tomascus: if you can provide me a q&d stock kernel I can test if a custom build stock break camera on full stock device.
https://github.com/tunturn/android_kernel_aries_concept
Cm14.1 branch, just import cyanogenmod Leo defconfig and make the defconfig changes I did yesterday
 

nailyk

Senior Member
Oct 3, 2015
1,503
2,955
2017-01-27 release

Nothing new, periodical build.
3.4 tomascus based.
Still CyanogenMod, not LineageOS.
 
  • Like
Reactions: mattia.bf

nailyk

Senior Member
Oct 3, 2015
1,503
2,955

Top Liked Posts

  • There are no posts matching your filters.
  • 14
    What it is
    It is a self cm13 build from official cm sources with a lot of patches. This rom is not intended to be used as daily usages, it is under development! The idea is to share with the community, let know there is an (slow) active cm13 devel for D6603 and maybe have some real dev help :D

    Disclaimer
    Code:
    #include <std_disclaimer.h>
    
    /*
     * Your warranty is now void.
     *
     * 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 me for messing up your device, I will laugh at you.
     *
     */

    Who can use it
    it is only for z3 and unlocked bootloaders

    Prerequisites

    • I highly recommend to upgrade your bootloader before, in case something goes wrong.
    • a twrp in the FOTAKernel/recovery partition
    • wipe data/cache (without wipe /data/media) in twrp (except coming from cm-12.x, upgrade should work)


    Sources

    Version Information
    Created: 2016-08-16
    Last Updated: 2017-01-27
    Status: Fairly unstable / abandoned

    Releases
    z3:
    2017-01-27:
    Download
    md5: 87ca5e27461647b649f0df315ef2ab81
    sha1: d9a4cb6342d3b63e0de1bfefc0fb47520bd5e57e
    • Periodical rebuild.

    2016-12-15:
    Download
    md5: 4f4e8c9ace63010bd5239855e1174fbc
    sha1: efda3d8920398ae9c5daea11367b63432937bd5c
    • Periodical rebuild for securities updates.

    2016-11-23:
    Download
    md5: 66ff7b6362c0d6d473e418bd7ee85c42
    sha1: fe4b0a17dd2db3276c4036fc8d0d54d9c8054e80
    • Periodical rebuild

    2016-10-03:
    Download
    md5: d1b1daa38aec25702c242f7110085eaf
    sha1: 3767b63f47a3f582e4bf8b3012e8cf0f48cb4124
    • Correct wifi path
    • Correct bcmdhd.ko errors (wifi)
    • Correct missing libhardware_legacy include errors (wifi)

    2016-09-14: kernel 3.10
    Download
    md5: 5078772453445a319640fde70aed1d50
    sha1: b64feffda124c436b8f07a06faa445a7b755308b
    • build with kernel 3.10 and with sony aosp blobs 1 2.
    • screen flickering is present
    • camera not working and continuously reboot

    2016-09-08:
    Download
    md5: 500fe665033704bc54954f1d2b7532ce
    sha1: c184295d6784e2b93e58e3866419bcd073698c77
    • nothing specially changed
    • start to regress camera stuff. No more loading errors but not the right blobs


    z3c:
    2016-10-03:
    Download
    md5: 018593359aa7b221128905fd8f950ba9
    sha1: 5fde92524b20796d777bb47f176c01bdb91ba0d5
    • [*] Initial release on xda
    • Correct wifi path
    • Correct bcmdhd.ko errors (wifi)
    • Correct missing libhardware_legacy include errors (wifi)
    Older releases


    P.S.: i'm not affiliated to CyanogenMod
    11
    2016-09-21 release

    New release
    I forget to switch back to the old blobs repo. This release sounds better.
    But i don't know if the 3D acceleration is present. Also the device don't go over 50°C so i'm wondering if the 1,5GHz limit for twrp wasn't included in cm...

    Ok I just tried both a clean and dirty flash of the rom from the 20th. There were 2 uploads though did I get the right one? One of them already had a download. I picked that one.

    Anyway, I had a cursor to control and I didn't have a sim, that's all I found because I restored after that.
    Bluetooth is fine. I was able to play songs through a2dp.
    Also i will edit the OP soon to include a log part.

    P.S.: satstat also show gsm cells, like in post#2
    P.S.2: androidfilehost is still under maintenance so i temporary create a dropbox account. I don't know how reliable it is so please check md5/sha
    10
    Changelog

    This rom is based on kernel 3.4 (cm-12.1) and build with the full cm-13.0 tree.
    Some feature may be unstable, other usable. Please report back, it will give me guidelines.

    ▇ ▅ █ ▅ ▇ ▂ ▃ ▁ What is working ▁ ▅ ▃ ▅ ▅ ▄ ▅ ▇
    • Bluetooth
    • WiFi
    • otg
    • Music
    • System sounds
    • gsm seems working
    • Touchscreen: cp qwerty.idc for some non original touchscreens

    ▇ ▅ █ ▅ ▇ ▂ ▃ ▁ What is not working ▁ ▅ ▃ ▅ ▅ ▄ ▅ ▇
    • Camera
    • Some audio crash -> fixed since 2016-08-18
    • WiFi -> fixed
    • Annoying display glitches -> display perfect on 3.4 kernel
    • Data connection -> fixed since 2016-08-21
    • Off-mode charging
    • Built-in app for video
    • fm radio
    • nfc
    • bluetooth
    Bug stays here, crossed-out, until confirmation it is really working


    ▇ ▅ █ ▅ ▇ ▂ ▃ ▁ What is not tested ▁ ▅ ▃ ▅ ▅ ▄ ▅ ▇
    • In global way, all features related to sim card
    • Radio/data
    • Battery performance

    All my repo are on github, any help apreciated :eek:
    This 3.4 kernel trick on cm-13.0 should work for every xperia shinano based. If other variant need test or information, feel free to contact me.
    10
    No release, some news

    Hi,

    No release for a long time, sorry for that. Since this thread had been opened we manage to get two things:
    - a test boot of cm-14.0 (we succeeded with the @tomascus kernel)
    - a switch to 3.10 kernel, display & media HALs 1.3.3 branches.
    Finally the 1.3.3 build succeed. One time I saw the blue CM guy so I know kernel & display are ok. But seems init or something like that is totally broken: now the device doesn't go after kernel splash screen and when I get an answer from adb it is:
    /sbin/sh command not found.
    dmesg show errors about missing /fstab.qcom
    so i'm wondering if the initrd is extracted.
    Anyway, at this point I think I will throw away all the done job with 1.3.3 branches, getting back to tomascus kernel to check my build tree and see whats happens.
    10
    more blog than dev

    I was ready to open the new cm-14.1 thread when I get some answer from github...
    All my PR to add our z3 where rejected because they want use AOSP HALs instead of caf.

    So I need to build the rom again with the AOSP HALs, getting something satisfying before opening the thread. Sleeping on it make me feel it is too bad to stop as close as something working.

    Maybe some of you saw the pictures taken with my z3, if not here they are.

    There is obviously a lot to fix but @malacha made promising reports.
    Anyway, another month to trash and start again, but hope this time it will be easier as the Sony's dev already work on it for a while and the first shot with AOSP HALs (cm-13.0) was good.

    In any case I'm still working on cm for our devices, for now, and Carbon roms are great if you want upgrade now.
    Thanks for your support.

    P.S.: if needed we hold a copy of the SonyCM caf variant repos, ask on IRC.