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

[ROM][Z3/Z3DUAL][deprecated] LineageOS 14.1 [CLOSED]

Status
Not open for further replies.
Search This thread

anifwidodo

Member
Mar 29, 2016
9
0
Over all i really love this rom. But I cant enter recovery and i lost it. since i flash this rom, and my other problem is my device always restart in 30-40 minutes. :rolleyes:. Please @nailyk anyone help me. thanks
 

tiliarou

Senior Member
Oct 13, 2011
209
89
Wait wait, to flash this ROM i must upgrade my bootloader, loosing forever TA partition (with no chance to recover it with a backup): Really?

Where did you see you can't recover it with backup ?? TA backup and restore is feasible, you can go back to stock, you can also flash a custom kernel with drm patch.
Correct me if I'm wrong but I didn't understand what you state from reading OP...
 

Tux111

Senior Member
Feb 25, 2012
731
363
Biancavilla(CT)
tuxnews.it
Where did you see you can't recover it with backup ?? TA backup and restore is feasible, you can go back to stock, you can also flash a custom kernel with drm patch.
Correct me if I'm wrong but I didn't understand what you state from reading OP...

At topic start "Who can use it
It is only for Z3 and UNLOCKED UPGRADED BOOTLOADERS"

If you follow that link, post say that "Upgrading bootloader is not revertible". After this:
"The TA partition is heavily upgraded so no regress available.
Also ta partitions backup should be consistent with bootloaders versions!"

This clearly mean that if i upgrade my bootloader, i can't, in every way, reset my TA Partition with DRM keys (because i cant come back to a no-upgraded bootloader).
Correct me if i'm wrong (really hope i am).
 
Last edited:

nailyk

Senior Member
Oct 3, 2015
1,503
2,955
At topic start "Who can use it
It is only for Z3 and UNLOCKED UPGRADED BOOTLOADERS"

If you follow that link, post say that "Upgrading bootloader is not revertible". After this:
"The TA partition is heavily upgraded so no regress available.
Also ta partitions backup should be consistent with bootloaders versions!"

This clearly mean that if i upgrade my bootloader, i can't, in every way, reset my TA Partition with DRM keys (because i cant come back to a no-upgraded bootloader).
Correct me if i'm wrong (really hope i am).
Your partially right.

Downgrading bootloader should be possible. However I never was able to. (dont mean it is not possible).

The flashing process is this one, almost meaning you never can got to stock + relock again. Am not saying it is impossible, juste as I canot be sure I prefere warn there is a high risk of brick.



Good luck.
 
  • Like
Reactions: tiliarou

tiliarou

Senior Member
Oct 13, 2011
209
89
At topic start "Who can use it
It is only for Z3 and UNLOCKED UPGRADED BOOTLOADERS"

If you follow that link, post say that "Upgrading bootloader is not revertible". After this:
"The TA partition is heavily upgraded so no regress available.
Also ta partitions backup should be consistent with bootloaders versions!"

This clearly mean that if i upgrade my bootloader, i can't, in every way, reset my TA Partition with DRM keys (because i cant come back to a no-upgraded bootloader).
Correct me if i'm wrong (really hope i am).

My bad, I thought that downgrade was easy.
But the DRM like restoration is almost the same in terms of camera drm functions, it will not put back your TA partition ut a generic DRM to have camera features enabled.
 

Tux111

Senior Member
Feb 25, 2012
731
363
Biancavilla(CT)
tuxnews.it
That file only restore some functions of DRM keys, don't restore your real DRM keys (i think you will miss some stock features). I used that package to enable stock features again AFTER i reset my real DRM keys and it worked.
A part of that, many users tried to restore theyre functionality with that file but failed (and its not clear how and why).

In the post i previously linked "TA partition is heavily upgraded, so no regress available". That restore package quite surely work trying to restore TA partition, that's why quite surely it will fail for upgraded bootloader (not revertible).
 
Last edited:
  • Like
Reactions: tiliarou

xkeita

Senior Member
Mar 18, 2012
608
1,633
Santiago
Hi all, just posting an update! (Two updates in fact, you'll find 2017-07-01 in the link below)

Since this is nailyk's thread for LOS it's a bit hard for me to keep every post up to date so I migrated all info into a new thread found here. This does not mean that nailyk won't be working with us, he's still part of the team and we're currently migrating our sources to official LineageOS repos. So expect good things to happen soon.
 

fefepato

Senior Member
Sep 9, 2013
78
25
Angol
Hi all, just posting an update! (Two updates in fact, you'll find 2017-07-01 in the link below)

Since this is nailyk's thread for LOS it's a bit hard for me to keep every post up to date so I migrated all info into a new thread found here. This does not mean that nailyk won't be working with us, he's still part of the team and we're currently migrating our sources to official LineageOS repos. So expect good things to happen soon.

Thanks for the great news!...Cant wait for Oficial Builds!!

Can i dirty flash over the last build?? or should i clean data and cache??
 

brianpee

Senior Member
May 21, 2012
83
30
Hi all, just posting an update! (Two updates in fact, you'll find 2017-07-01 in the link below)

Since this is nailyk's thread for LOS it's a bit hard for me to keep every post up to date so I migrated all info into a new thread found here. This does not mean that nailyk won't be working with us, he's still part of the team and we're currently migrating our sources to official LineageOS repos. So expect good things to happen soon.


Migrating sources to official LineageOS repo = Official soon? :)
 

xkeita

Senior Member
Mar 18, 2012
608
1,633
Santiago

Astorec

New member
Dec 25, 2015
2
0
Updating?

Hello,
Just wanted to let you know I've been using the 14.1-20170517 release for a while now and I'm loving it! Besides the known BT issues, and random restarts** everything is smooth and running well.

I was just wondering, in order to update the ROM to the newest release, will I have to re-flash completely, or can I dirty flash the 2017-06-13 release and save having to back everything up and reinstall all my apps etc? (Nandroid backups never seem to work for me...)

Thanks for the hard work and fantastic ROM! :good:

**The random restarts seem to occur during periods of high ram usage, like when I have several intensive applications open at once. Not too much of a bother, my phone probably should be restarted every now and again anyway ;) I can try to provide a log and more details when I'm home.
 

Bäcker

Senior Member
Jan 4, 2007
486
242
Hello,
Just wanted to let you know I've been using the 14.1-20170517 release for a while now and I'm loving it! Besides the known BT issues, and random restarts** everything is smooth and running well.

I was just wondering, in order to update the ROM to the newest release, will I have to re-flash completely, or can I dirty flash the 2017-06-13 release and save having to back everything up and reinstall all my apps etc? (Nandroid backups never seem to work for me...)

Thanks for the hard work and fantastic ROM! :good:

**The random restarts seem to occur during periods of high ram usage, like when I have several intensive applications open at once. Not too much of a bother, my phone probably should be restarted every now and again anyway ;) I can try to provide a log and more details when I'm home.

Just dirty flash. Having a backup is always a good thing though.
 
  • Like
Reactions: Dobsgw and Astorec

nailyk

Senior Member
Oct 3, 2015
1,503
2,955
Bye :)

Time for some news

Maybe some of you know we moved to lineage os repo into the week-end. This had no other meaning, just using another gerrit and/or repo URLs. More informations into @tomascus post.

Ok here is the tricky part...
Am dropping "official" status as LineageOS. It means I wont be an official maintainer anymore (for Lineage).
Obviously it is not about stealing the device you just offered to me, I will still help @xkeita working on the dual version, just we changed a bit the process.

Am working on something else (for shinano) and, with the lot of work the team make here, it should be almost easy.

tl;dr: Am not LineageOS maintainer anymore, only contributor.


Also @xkeita opened his own thread with the recent sources move. So it is time to leave this thread.
Stay nice and relevant.

Many thanks all and see you soon
https%3A%2F%2Fforum.xda-developers.com%2Fimages%2Fsmilies%2Fsmile.gif
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 84
    lineage_logo_strip_onteal_500x120.png

    Click here to get to the new post where we'll keep updating this rom

    What it is
    It is an LineageOS 14.1 alpha build from official LineageOS sources devices trees and fresh caf 3.4 kernel port. This is not related anymore (2017-03-22) to the Sony Open Device Project (sonyxperiadev). They work on a different way and we are helping each others as often as possible.
    This rom is worked to be as stable as possible to be used as a daily driver. There are no changes into LineageOS sources, manifest to build is attached in this post. The idea is to share this built with the community to improve this rom. If it is good enough, maybe, someday, get official again for our D6603. Thanks a lot to @tomascus who made this possible. (his donate link)​

    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 UPGRADED BOOTLOADERS

    How to install

    %= Only needed at first flash
    1. % Update ROM to .291 with emma (or Flashtools)
    2. % When install is done go into fastboot mode (plug usb + vol down key = blue led)
    3. % Flash this TWRP (version 3.1.x) | If you are a Z3 Dual user, flash zip below before installing Z3 Dual version. / If you already are in .291 and have a working TWRP (modded rom/kernel/adv kernel) you can use the flashable zips below instead.
    4. Shutdown the device
    5. Unplug the usb cable
    6. Maintain volume down & power until you see twrp splash screen
    7. % Wipe system, cache and data
    8. Install rom zip (+ % gapps if you need it)
    9. Reboot


    Rolling back to stock
    • Flash stock rom with emma or flashtool
      If you flash with flashtool remember to check wipe apps_log and userdata partitions to get a clean install

    What gapps to flash?
    Use f-droid :p
    You can flash any gapps you want, our partition is 2GB and rom is 700MB:
    Code:
    z3:/ # df -h
    Filesystem Size Used Avail Use% Mounted on
    /dev/block/mmcblk0p23 2.4G 680M 1.7G 28% /system
    Just take 'arm' and not 'arm64'
    Gapps need to be flashed at first rom flash!


    NEW RELEASE
    2017-06-13:

    Xperia Z3
    Xperia Z3 Dual

    Temporal Z3 Dual rom (fixes SIM problems)
    Many thanks to @xkeita for providing a working rom as soon as the device get delivered.
    20170622 / b8a79c826ddf0a786010cc04b3943b2e
    twrp / 61e8c27f19c114dc9ac1f33dd4c7fb39
    Rom is tagged nailyk because I build it but everything on it is @xkeita work!
    Many thanks everybody :)

    What's new:
    Code:
    - Updated Camera profiles
    - Reworked Z3 Dual RIL
    - Updated Audio HAL flags
    - BFQ I/O Scheduler
    - Bluetooth aptX support
    - Qualcomm Connectivity Engine support
    - Imported audio ids from original .291
    - ANC Headphones support
    - Dual Mic config enabled for voice calls/audio recording
    - Ok Google everywhere fixed (untested)
    - Tweaked autobrightness  (again)

    Release notes:
    • 2017-06-09 is just a minor update with some [experimental] tweaks for bt connections and fixed minor issues with z3dual

    Older Releases

    Based on Kernel 3.4
    Some of these can be found here
    Release History
    Code:
    2017-06-09:
    - Tweaked a little bluetooth values (untested)
    - Fixed Z3 Dual sim problems
    - Latest Google source (7.1.2_r17) 
    - June security updates
    - Permission fixes for new PowerHAL
    - Z3 and Z3 Dual code cleanup
    - Forced camera modes to [email protected], [email protected], [email protected], [email protected]
    - Fixed all of the device sensors (they're all online and working properly now)
    - Latest LineageOS updates
    - Smoother UI rendering with CPU
    
    2017-05-17:
    - Tweaked general audio output processing 
    - Updated vendor audio libraries configs (enables qcom effects)
    - Auto brightness/brightness changes
    - New thermanager configs based on stock
    - Changed deprecated Gello for Jelly
    - Some device tree cleanup
    - General radio/wifi tcp updates
    
    2017-04-16
    - Audio changes, 
    - NFC fixes, 
    - Brightness changes, 
    - Verbosity increased for logs after night reboot + PERISTENT_TRACER
    - No more vol- buton at boot time
    - A lot more
    
    2017-04-05:
    - Enforcing selinux
    
    2017-04-01:
    - Audio fixes
    - Encryption fix
    - A lot more that I can't remember right now
    
    2017-03-22:
    - Full rework based on stock 3.4 kernel

    Based on Kernel 3.10 by @nailyk
    2017-01-23:

    2017-01-15:
    • Download / 2
    • md5: 8b8898c18d631dc7f9d78a18b1e7500f / b40c7ba870ae579827e1bd7a427afc1f
    • sha1: 588d2c1e0fd2ef4790706980fc1050a8d793d559 / f28ba7714987a94c5ba43a6ee39fe05f0b5a5fca
    • Use of the reworked device trees
    • Include some experimental kernel pull requests

    2017-01-01:
    • Download
    • md5: 6c5abcbeda01c75344cd4296bb2358d1
    • sha1: a46ef81e2d26ac9610f16cb90bc13e63d58a2983
    • Switch to LineageOS
    • Bluetooth deepsleep fixed

    2016-12-02:
    • Download
    • md5: 496de65608fd4236f5d451a4179e1ce8
    • sha1: 74a25eabc0f8ac5be3458bd9d98461f9519c7c73
    • Bluetooth improvements

    P.S.: i'm almost affiliated to LineageOS, just like tomascus who made everything.


    Sources
    Manifest file.
    Everything else is Lineage.
    Contribute gerrit.

    XDA:DevDB Information
    LOS-14.1, ROM for the Sony Xperia Z3

    Contributors
    nailyk, xkeita
    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.4.x
    Based On: LineageOS

    Version Information
    Status: Beta
    Beta Release Date: 2017-06-09

    Created 2016-11-27
    Last Updated 2017-07-01
    50
    Why no news

    Not been here for a while because we where working on something new: a 3.4 tree (full stock) for our devices.
    And we finally get camera working.
    Now we need time to cleanup, fix useless things like wifi and ril but we will have good cam on Lineage :)

    Thanks all for support and patience.

    P.S.: xda crop picture, original one is 10MB.
    40
    2017-03-05: 3.4 port state

    Some progress on ril side for d6603.
    But still a lot of work to do:
    - thermal is not working need tuning (;)),
    - bluetooth is broken,
    - ril call doesn't really work withouth headset (acdb problem?),
    - wifi ok (untested @5Ghz),
    - lights ok,
    - camera ok (video recording too @ 1080p30 only),
    - deepsleep sometimes broke,
    - f2fs not working
    - and a lot more ;)
    33
    Game Over


    Time for an... Update.

    Maybe some of you already known but I don't have d6603 anymore.
    The first dev phone get a SMC pulled of (my bad) and doesn't work properly anymore.
    Right now all my reflow attempt failed.

    The other device is hardly software bricked because that great bootloader signature doesn't work anymore.
    Note: don't try to write junk into tz partition.
    It looks to be unsolvable because Sony made great things again and prevent normal msm8974 low level disaster recovery working, replaced by their useless own.

    So I doesn't have device anymore, fixing them will take a while and mostly will not work. Game over for me. Hopefully you have a lot of great dev working on this which wont leave you.
    @xkeita was ok to take the next of this thread. He now have full right here.
    @malacha will help him as much as he can but is now maintaining another rom.

    Was a pleasure to make my first android experience here.
    Many thanks to all of you.