Database Info

[ROM][UNOFFICIAL][UBER 4.9.4][Surnia ][7.1.2 r29] HalogenOS CAF [OMS]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Android, Reimagined.
For the best experience, view the thread on a web browser like Chromium or Firefox.
Desktop: Brilliant. Mobile: Good. Tapatalk: OK. XDA-Labs: Horrible.
Code:
YOU are doing modifications to your device.
YOU are responsible for what you do.
We are not responsible for any damages, data loss or any type of unexpected,
bad or damaging results! If you have SERIOUS problems with this software,
please contact the developers or maintainers. We are not liable for anything
bad that happens to your device.
As long as you are responsible, some companies such as OnePlus
WILL HONOR IT. Some people occasionally describe them as heroes.
Don't be stupid and bet on that though, please be responsible for what you do.
We prohibit you from overclocking to 1337 GHz thinking, that an OEM would
replace your glorious space heater etc.
We recommend you to take the advice above regardless.
halogenOS Checklist
Although no data should be lost or damaged by the flashing process,
we advise you to follow the following steps if you are coming from another rom:
Please take a full nandroid backup!
Please copy your back up to an external device.
Backing up your Internal Storage is also recommended.
When completed, please clean flash the build!
XOS is a new generation cutting-edge OS for Android based on Code Aurora Forum releases.
What is XOS?
halogenOS, also known as XOS is a new Android ROM which ships with the global aim to
become a modular ROM which keeps as high as potentially possible operating
performance on your mobile device while still maintaining a sufficient feature
base of nice, small and minimal features that would not be available via any
external feature base, extension, mod or plugin.
We hope you have a truly halogenified experience!
Internals of XOS
At core, the ROM is composed mainly of components from CodeAuroraForums (CAF),
featuring only extremely minor set of components from CyanogenMod (CM) which
have been added to source in order to allow for better cross-device compatibility.
Our LOVE to others
A huge thanks goes to those behind the CodeAuroraForums (CAF), the CyanogenMod
organization and all of its
contributors for the sources used in the development of the base ROM which we
started with inclusive of all the work and dedication their team puts in order to
keep us updated on the awesome contributions that they make.
We will be keen on ensuring that we be up to date with the code from our base sources,
with regular ROM updates hopefully coming from time to time.
Please do not ask for ETA's (else you shall be spooked by Mr Skeltal). Almost all of us are
students, and with the current lifestyles and routines we have, it is not that easy to acquire
time to develop the ROM, though we'll be sure to keep you updated and release OTAs as
soon as they are available and ready for publication. If you want to be really updated quick,
then join us on Telegram: http://telegram.me/halogenos
Visit our website for features such as: Downloads, Information etc.
http://halogenos.org
(Not finished yet)
​
Common stuff
The ROM is super stable as of now and we'll maintain a clean and proper ROM.
Known issues are going to be fixed as soon as possible. We don't have infinite time.
Highlights :
Substratum
Full media support (FFMPEG, video codecs, ...)
Great Audio quality, no distortions, no crap
Optimized many portions of the system including surfaceflinger, inputflinger, System Server, and more
Super fast boot
Superuser-capable
Great battery life
Soundmod support (not all soundmods work on Nougat, it's not our fault)
addon.d support (backups your gapps etc. when flashing new build - don't wipe system before flashing!)
init.d support
BusyBox
Disabled Access Time for all partitions (We don't need access time. When access time is enabled, it will store the exact date of the access when a file is accessed, what just wastes write cycles (in theory) and has impact in I/O performance.)
Super smooth
Signature Spoofing toggle (Support for MicroG)
Support for trusted third-party WebViews like Chrome
Long press on home for assist toggle
Security Patches in kernel
OpenGapps (Mini/Micro/Nano recommended) and Banks GApps support
Full KeyHandler & KeyDisabler support
Dexpreopt for faster (first) boot time and less space consumption on data partition
Upgrade & Boot the ROM in just 5 minutes - no more endless waiting for flashing a new build
Very high compatibility with other ROMs
How to update the ROM:
Download the latest zip
Reboot into TWRP (Please use official TWRP)
Do not wipe anything
Flash the ROM
Flash SuperSU 2.79 or newer if you want (Download 2.82 here)
or
Flash Magisk v13.1 if you want from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Reboot
You don't need to wipe Cache/Dalvik.
You don't need to flash gapps again. There is some magic going on which keeps your GApps. Just make sure that you don't wipe system before flashing.
You don't need more than 5 minutes.
How to install the ROM for the first time:
Download the latest zip
Reboot into TWRP (Please use official TWRP)
Wipe system, data and cache (If you want to try a dirty flash, dont wipe anything)
Flash the ROM
Flash gapps if you want
Flash SuperSU 2.79 or newer if you want (Download 2.82 here)
or
Flash Magisk v13.1 if you want from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Reboot
@regalstreak
@xdvs23 (actually xdevs23, but that was already taken on XDA)
@sewer56lol
@jbw716
@marpe
@dango99
@hunter_bruhh
@MSF-Jarvis
@keessonnema
​
ROM Download Links
Download halogenOS now
ROM Sources
All sources incl. ROM @ GitHub Organisation
Kernel source-https://github.com/LineageOS/android_kernel_motorola_msm8916
Device source- https://github.com/LineageOS/android_device_motorola_surnia
https://github.com/LineageOS/android_device_motorola_msm8916-common
Vendor source- https://github.com/theMuppets/proprietary_vendor_motorola
​
Join our
Telegram group
Telegram News Channel
Telegram Off-Topic Group
​
Credits
CodeAurora
CyanogenMod
And everyone else who contributed and helps us!
In case you feel left out here, please contact us! ​
XDA: DevDB Information
HalogenOS, ROM for the Moto E 2015 Surnia
Contributors
amarc78
Source Code: https://github.com/halogenOS
Change Log: https://github.com/halogenOS/android_vendor_xos/blob/XOS-7.0/Changelog.md
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Cm 14.x firmware
Based On: CAF
Version Information
Status: Stable
Current Stable Version: 7.1.2
Stable Release Date: 2017-05-24
Created 2017-05-24
Last Updated 2017-08-17

Reserved

Reserved

I should mention that you'll have no nav bar when you first boot. You'll have to go into settings and enable it. So don't freak out when you get stuck in an app, just go into settings from quick settings. I'll try to enable it and upload a new build asap.

amarc78 said:
I should mention that you'll have no nav bar when you first boot. You'll have to go into settings and enable it. So don't freak out when you get stuck in an app, just go into settings from quick settings. I'll try to enable it and upload a new build asap.
Click to expand...
Click to collapse
I was stuck in the initial configuration because I did not have a lower navigation bar, I restarted the power button for a long time and I started the bootloop. I tried twice to blink the rom and I could not get out of bootloop. Waiting for new construction .... thanks, nonetheless. good job.

ENRIQUEMM said:
I was stuck in the initial configuration because I did not have a lower navigation bar, I restarted the power button for a long time and I started the bootloop. I tried twice to blink the rom and I could not get out of bootloop. Waiting for new construction .... thanks, nonetheless. good job.
Click to expand...
Click to collapse
That's strange. I flashed a few builds and didn't have that problem. I'll see what I can do.

I'm running a new build now, the nav bar should be activated on first boot. If so, I'll post it shortly.

Wonderful ROM Works to perfection

RubenPCA said:
Wonderful ROM Works to perfection
Click to expand...
Click to collapse
It does run great. Very quick and smooth.
Sent from my LGLS755 using XDA Labs

Great job
My steps
All wipe
Flash ROM
Flash gapps
Flash supersu
Reboot
Init and freezing then reboot and bootloop
Reflash only ROM and gapps
Run
This ROM is fantástic
Just an observation, try to install it from the official twrp 3.1.1 and after doing the backup I was unable to access the recovery. Nor restarting in recovery mode even from the fastboot. I had to put back the squid twrp through adb ...
Sorry my bad english
Enviado desde mi XT1524 mediante Tapatalk

Thanks man rom works perfectly ! No issues on first boot!

Has anyone else noticed a bluetooth connection failure?
Connecting to my smart clock turns off in seconds.
I regret not being able to attach the log, but due to bootloop problems when installing supersu I do not have it rooted.

ENRIQUEMM said:
Has anyone else noticed a bluetooth connection failure?
Connecting to my smart clock turns off in seconds.
I regret not being able to attach the log, but due to bootloop problems when installing supersu I do not have it rooted.
Click to expand...
Click to collapse
I forgot to mention some Bluetooth issues, but I haven't had any trouble staying connected to anything. I thought the only problem was inbound file transfer. I'm working on it. I've been using Magisk without any issues by the way.

After installing magiks v12 I play the connection to my smartwatch and the same problem is disconnected in seconds

ENRIQUEMM said:
After installing magiks v12 I play the connection to my smartwatch and the same problem is disconnected in seconds
Click to expand...
Click to collapse
I think you misunderstood. I didn't mean installing Magisk would fix your Bluetooth problem. You can take a log now though right? I don't have a smartwatch and I haven't had problems staying connected to devices I have so a log may be helpful.

amarc78 said:
I think you misunderstood. I didn't mean installing Magisk would fix your Bluetooth problem. You can take a log now though right? I don't have a smartwatch and I haven't had problems staying connected to devices I have so a log may be helpful.
Click to expand...
Click to collapse
I wanted to have robot access for the registration of the bug attach it to the previous post. Thank you

ENRIQUEMM said:
I wanted to have robot access for the registration of the bug attach it to the previous post. Thank you
Click to expand...
Click to collapse
There is an updated SuperSU I see. https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
I haven't tested it yet though.

New build is up. Bluetooth should be all fixed now. @ENRIQUEMM I don't have a smart watch to test with if you want to try again and let me know if your problem is fixed.

Hi. You guys work hard I know it. I couldn't get past the get started screen no matter what I tried.

801legend said:
Hi. You guys work hard I know it. I couldn't get past the get started screen no matter what I tried.
Click to expand...
Click to collapse
Sometimes old Gapps or a bad data connection can make the setupwizard hang. If you weren't using up to date Gapps try updating them. I'f that doesn't work. Try selecting not using any data or WiFi connection on setup. It worked fine for me with 6-17 Open Gapps before I uploaded the build.
Sent from my Motorola XT1526 using XDA Labs

[ROM] [ 8.1.0 ] Official madOS - Vernee Apollo Lite & X [MT6797]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is a Official Build of madOS ( based on AOSP 8.1.0 ) for Vernee Apollo Lite & X with MTK 6797 SoC
madOS is based on pure A.O.S.P. with many additional customizations and MediaTek support.
Code:
#include
/*
* Your warranty is now void.
*
* I am 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.
*/
Installation Instructions:
The latest 7.1.2 build must be flashed in SPFT with firmware upgrade mode before this ROM can be flashed (Downloads: VAL, VAX)
Download ROM from M.A.D. Facebook
OR from xda DevDB
Download 8.1 GApps from xda devdb (Mirror)
Backup
Flash new mandatory new Oreo TWRP (available on downloads)
Boot to the new TWRP recovery
full Wipes (dont come crying if you didn't .. ;p )
Install rom (optionally following by GAPPS if you use them)
Optional: go to: wipe --> Advanced Wipe, tick 'cache' and klick 'repair or change File System' --> change File System --> F2FS --> swipe to the right (hit back several times, and proceed the same way with 'data').
Reboot System
Working:
RIL (Calls /SMS, Data connection, etc)
Wifi
Bluetooth
FM Radio
All Sensors
Fingerprint
Lights
Both storages & MTP
HW de/encoding
Camera (photos and video)
GPS & aGPS
Audio
madOS Extras (the features ya'all used too), plus, some new features we added on Oreo)
Bugs:
-
XDA:DevDB Information
madOS_O_VAL_VAX, ROM for all devices (see above for details)
Contributors
fire855, DerTeufel1980, superdragonpt
Source Code: https://github.com/MediatekAndroidDevelopers
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP
Based On: AOSP
Version Information
Status: Stable
Stable Release Date: 2017-12-25
Created 2017-12-25
Last Updated 2018-01-13

General F.A.Q.
Q: What the hell is madOS ?
A: madOS, (M.A.D. Team OS), is a ROM based on pure A.O.S.P. with extended capabilities and customizations made by or merge/adapted by M.A.D. Team.
Q: Which recovery should I use for this ROM?
A: Latest M.A.D. TWRP 3.2.1-0 recovery
--> Check xda Download Section
Q: How do i flash new recovery ?
A:
1: You can flash it with a scatter file (LP rom layout)
2: You can simply flash it from the existing twrp recovery: Install> Install image> Select Oreo TWRP> Select "Recovery" as partition to flash.
Reboot to recovery to use new one
Q: Do i need to make full wipes?
A: YES, dont come crying at me, if you didn't .... ;p
Q: What is "full wipes" ?
A: To Wipe : Cache; System; DATA ...
Q: What should i use f2fs or ext4?
A: Both are supported, choose the one you desire
Q: is the Data connection issue of going to / from 4G still present?
A: nope data switchs pretty fast on our new RIL
2G>3G>4G | 4G>3G>2G pretty fast
Q: Does this rom have any Theme support
A: Yup, We have working Theme Engine (madOS extras)
Q: Some translations are missing for my language, can I help?
A: Sure you can, please check our translations repo available here , you can either do a pull request, or if you don't know how to work with git, sent us the XML. Strings for your language ( Check Readme on repo).
Q: I want to report a bug(s) do you have an issue tracker?
A: Yeah... madOS issue tracker
Q: What's working ?
A: Check first Post for current status
Q: App "x" doesn't work, why?
A: Probably not compatible with OREO yet, feedback is welcome
Q: Is the rom rooted?
A: NO, But you can easily root with :
1: Magisk ( v14 onwards.)
2: Super SU ( v2.82 onwards)
Q: Should i root together with rom ?
A: Not advised.. mainly the Magisk that gives some weird issues...
Flash ROM and GAPPS (if you use gapps), after first boot get back to recovery and flash your desire rooting method
Q: Does xposed work?
A: Is there Xposed for O? ... then no ;p
Q: How is battery life with Oreo?
A: Pretty awesome
Q: Does this build support Vulkan?
A: No....duh! v
Q: Does doze work in this build?
A: Yup
Q: Does 4k video recording work?
A: Yes, but not every phone supports it. If 4k worked in the stock rom, it will work in madOS too.
Q: when will (feature/issue here) be fixed?
A: NO ETA , please
Porting F.A.Q.
No porting support, no port questions allowed on this thread, and porting PMs will be auto-deleted, porting replies will be reported as well
G.APPS F.A.Q.
Q:What GAPPS package should I use?
A:OpenGapps arm64 nano/mini
Since there's no Official GAPPS for 8.1.0 just yet...
... we had built OpenGapps nano and pico versions
--> Check Download Section
Q: How to properly install GAPPS?
A:Flash Rom + Flash Gapps at once
CREDITS and Thanks
madOS Team
Our translators, credits list here
A.O.S.P.
AOSPA
DU (Dirty Unicorns)
Omni
HELP supporting madOS
We do this on our free time, however we do have costs on maintaining this :/
Any donation is highly appreciated
You can donate by using
this link
If the above doesn't work in your country, then you can directly donate by using this e-mail adress: [email protected]
About madOS Proprietary Apps
You are NOT allowed by any means, to use our madOS apps on any other build, your rom
This is exclusively for OFFICIAL madOS ROM releases
@To Moderators: Feel free to clean the thread, whenever users start spamming, severe OT, or questioning about porting...

Changelogs
[Stable] Build [8.1.0] 20171225
First Release
madOS version: 2.1
Patch Level: 8.1.0 [OPM1] December 5, 2017
Kernel: 3.18.89 (o-8.1.0 branch)
[Stable] Build [8.1.0] 20180102
madOS version: 2.1.1
Fixed UI lags / hangs
Fixed deepsleep
Fixed screen recording
Fixed video playback issues
Updated graphics system
Improved GSM/LTE signal handling
Fixed alarms
Fixed FMRadio
Fixed wallpaper scrolling setting in madLauncher
Fixed 5GHz hotspot issues
Improvements in bluetooth for A2DP
Updated included APNs list
madOS color Engine:
Rebased & many improvements on the engine
Better support on theming Quick Settings
New option to override default Google 8.1 QS theming
New reset button to get back to default 8.1 theming
New MAD mode

Merry Christmas !!

Thanks. Merry Christmas.
The computer died. I will not make the sd card backup.

Marry Xmas to all.

Wow.... Oreo release and directly 8.1 weeeeeeeeeeee!
Didn't expect this before the new year, what a surprise.
Thanx you @fire855
Thank you MAD-team

Hi,
How to install ROM and gapps?
On TWRP or using flash?
Thank you

Should we come from the last 7.1.2 build (which has different partitions from stock)?

I really appreciate the work, but it's somewhat unflashable. New recovery is not stable, it gets stuck sometimes. Also I didn't manage to bring 8.1 to run with Gapps yet.
€: To provide somewhat more information: System crashes when running playstore.
€2: Full wipe made, advanced wipe and wiped every partition. It gets stuck coincidential, there's no proper reason for it, it got stuck once when I flashed MadOS itself, second time it got stuck flashing gapps, so I hope I get it run that night...
€3: Recovery freezes and after 30 seconds (approx) phone reboots.
€4: Nope, I don't get it to work, goddamnit. It freezes almost immediately after I enter my pin.

Help please...
I install new TRWP OREO on old twrp...
when reboot the phone shutoff and does nothing... i cant turn on...

TJFA81 said:
Help please...
I install new TRWP OREO on old twrp...
when reboot the phone shutoff and does nothing... i cant turn on...
Click to expand...
Click to collapse
Hold VOL+ and POWER when rebooting. Then you can choose to boot into TWRP. There you copy the new recovery image and then flash Oreo.

Xorianator said:
Hold VOL+ and POWER when rebooting. Then you can choose to boot into TWRP. There you copy the new recovery image and then flash Oreo.
Click to expand...
Click to collapse
I cant...
When choose recovery the phone freezes. black screen
To install new TWRP OREO its only necessary flash the file recovery.img???

TJFA81 said:
I cant...
When choose recovery the phone freezes. black screen
To install new TWRP OREO its only necessary flash the file recovery.img???
Click to expand...
Click to collapse
Yes, you only have to bring the recovery up again.
What you can also do is: Go back to 7.1 (flash it with SPflashtool) and then do the steps

Xorianator said:
Yes, you only have to bring the recovery up again.
What you can also do is: Go back to 7.1 (flash it with SPflashtool) and then do the steps
Click to expand...
Click to collapse
I cant go to recovery...
Can start the phone but cant go to recovery after flash new recovery file posted on MAD facebook.
I dont have 8.1 because of that, just did the first step anda now cant go to recovery

TJFA81 said:
I cant go to recovery...
Can start the phone but cant go to recovery after flash new recovery file posted on MAD facebook.
I dont have 8.1 because of that, just did the first step anda now cant go to recovery
Click to expand...
Click to collapse
Reflash 7.1 image using SPflashtool, I made a guide for this There you go. Then you can repeat.
Okay so 8.1 is not working at all... I get somewhat a weird failure on screen, the screen "sacks" down (main UI Activity just "fall down", status bar is still up) and then it freezes... Looking forward to get this fixed soon.
€: And the boot time is horrible, before I see a screen it's black for idk 2 Minutes
€3: Nvm lol, actually the phone is now unable to boot in System....
€4: Give it a try with "optional" F2FS File system step, let's see.
€5: Nope, didn't fix a thing. So well, at least I could capture this "sack down" thing:
The red line is where the display ends. As you can see the symbols are still in place. The blue line marks where the activity "sack down" and if this happens (which happens just on coincidence) nothing will happen any further, system's frozen and it reboots afterwards.

TJFA81 said:
Hi,
How to install ROM and gapps?
On TWRP or using flash?
Thank you
Click to expand...
Click to collapse
TWRP

Xorianator said:
Reflash 7.1 image using SPflashtool, I made a guide for this There you go. Then you can repeat.
Okay so 8.1 is not working at all... I get somewhat a weird failure on screen, the screen "sacks" down (main UI Activity just "fall down", status bar is still up) and then it freezes... Looking forward to get this fixed soon.
€: And the boot time is horrible, before I see a screen it's black for idk 2 Minutes
€3: Nvm lol, actually the phone is now unable to boot in System....
€4: Give it a try with "optional" F2FS File system step, let's see.
Click to expand...
Click to collapse
Thank you, already did it... reflash recovery.img but by spflashtool. Now im inside twrp3.2.1...
Now its time to try install oreo and gapps

cedricboquiren said:
Should we come from the last 7.1.2 build (which has different partitions from stock)?
Click to expand...
Click to collapse
Yes, the latest 7.1.2 is mandatory. Added this to the first post now too.

I tried to install the new rom, after I installed the new twrp, the phone is still restarting, I tried to return to 7.1.2 with spft but no success even does not connect with the laptop, what I could do they do?

[RECOVERY][tulip] TWRP-3.2.3-x [UNOFFICIAL][20181214]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device here
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
DOWNLOAD:
Note this is a very preliminary build. Feel free to report bugs.
Do flash disable force encryption mod, reboot recovery & then wipe /data as /data decryption doesn't work as of now.
twrp*.img
Fastboot Flashing Code
Code:
[CENTER]fastboot flash recovery twrp*.img[/CENTER]
BUGS:
/data decryption does not work
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Device tree
Kernel source: Prebuilt stock kernel
XDA:DevDB Information
[RECOVERY] TWRP-3.2.3-x [tulip], Tool/Utility for the Xiaomi Redmi Note 6 Pro
Contributors
Shivam Kumar Jha
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information
Status: Testing
Created 2018-12-14
Last Updated 2018-12-14

Reserved for changelog.

Thanks for this huge job

Is there a link the official/universal disable force encryption mod somewhere? Or are there different mods for different devices (cause of treble or something)?

Is there any possibility of having the phone encrypted and also be accessible (ability to decrypt) in TWRP? I mean is it a matter of development or is there a security measure preventing it?
Enddo said:
Is there a link the official/universal disable force encryption mod somewhere? Or are there different mods for different devices (cause of treble or something)?
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389

Super

Hi. I am yet to unlock the bootloader of my RN6 Pro. Once I do it I'll be getting rid of MIUI and install LOS.
In order to make the recovery work, do I have to decrypt the device? Also, to decrypt I have to flash TWRP from PC(ADB) then wipe /data from TWRP, right? TIA.

can i update this recovery on sayad1 twrp recovery from sayad1
https://forum.xda-developers.com/re...pment/unoficialtwrp-redmi-note-6-pro-t3863679
Sent from my Redmi Note 6 Pro using Tapatalk

the more important question is > any reasons to update the sayad1 twrp ?

can i flash this rom via sayad1 recovery ??
Sent from my Redmi Note 6 Pro using Tapatalk

if you know why then try and let us know if this one will be better than sayad1 twrp,
and make backup before
for flashing by fastboot you would need an img file ?

phonepete said:
if you know why then try and let us know if this one will be better than sayad1 twrp,
and make backup before
for flashing by fastboot you would need an img file ?
Click to expand...
Click to collapse
i want to flash lineage 15.1 with recovery best this one ya sayad1?
Sent from my Redmi Note 6 Pro using Tapatalk

Shivam Kumar Jha said:
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system, functions often unsupported by stock recovery images. It is, therefore, often installed when rooting Android devices, although it isn't dependent on a device being rooted to be installed.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
1) Install the TWRP app from the Play Store or grab the apk from our website
2) Open the app, agree to the terms, and enable root access
3) Select TWRP Flash
4) Search for your device and select the version you wish to download
5) Once the download is complete, select the file (it's usually in your downloads folder) and then Flash Recovery
OR:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device here
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
DOWNLOAD:
Note this is a very preliminary build. Feel free to report bugs.
Do flash disable force encryption mod, reboot recovery & then wipe /data as /data decryption doesn't work as of now.
twrp*.img
Fastboot Flashing Code
Code:
[CENTER]fastboot flash recovery twrp*.img[/CENTER]
BUGS:
/data decryption does not work
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Device tree
Kernel source: Prebuilt stock kernel
XDA:DevDB Information
[RECOVERY] TWRP-3.2.3-x [tulip], Tool/Utility for the Xiaomi Redmi Note 6 Pro
Contributors
Shivam Kumar Jha
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information
Status: Testing
Created 2018-12-14
Last Updated 2018-12-14
Click to expand...
Click to collapse
Thanks for your work.
Keep debugging... Regards,

Thanks for your work indeed @Shivam Kumar Jha !
I've read in the Github tha release 3.2.3-1 of twrp solved the decrypt issue for many devices. Can anyone try to build it for tulip?

Hi Shivam Kumar Jha,
Do you have any news about decryption that does not work?
Regards,

[ROM][DISCONTINUED][9] LineageOS 16.0 [deb][flo]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device. All the source code for LineageOS is available in the LineageOS Github repo. If you would like to contribute to LineageOS, please visit our Gerrit Code Review.​
Code:
* [B][U]Your warranty is now void.[/U][/B]
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your 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.
FREQUENTLY ASKED QUESTIONS
(Please read them BEFORE posting anything in the thread!)​Q: Whenever I try flashing any lineage-16.0 build, I get the following error in TWRP: Updater process ended with ERROR: 7
A: This error appears whenever you try to flash an Oreo-based rom within a version of TWRP older than 3.2. Simply flash the linked below version 3.2 or higher, reboot back into recovery, and flash the rom zip again.
Q: I am seeing Error 7 when trying to flash a GApps package.
A: This is due to the system partition being too small to fit both the rom and the GApps package. You need to re-partition it with a tool such as the one created by Clamor (linked below). You will only need to do this once.
Q: When will any of the variants receive official builds from LineageOS?
A: Not before all the issues listed under "Bugs" below are fixed.
Note to Junior Members: It is frowned upon in the XDA community to ask for ETA's on builds, features, bug fixes, or other improvements to the code or its functionality.
Q: What will some of the differences be between unofficial and official builds?
A: The following technical changes will take effect:
- Built-in su root will be removed: You will have to download and install the su addon from LineageOS Extras.
- Phone status > LineageOS updates will be activated, allowing for the OTA downloading of official builds.
- The official builds will be digitally signed by Lineage to prove that they do not contain malicious source code and are able to pass the Play Store's SafetyNet check.
Note: Each official build will be cooked and released by LineageOS on their schedule and only if no major unexpected bug is introduced into the source code. The developers will announce if and when their source code will be submitted to Lineage for official support and when we can expect to see the first official builds.
Q: How often will new builds be released?
A: About once a week for both deb and flo, as soon as possible after each new Android security patch level is merged, and of course whenever a new feature is added or a bug is fixed.
[REPARTITION] Nexus 7 (2013) Repartition [FLO/DEB] [16GB/32GB] [UA TWRP]
ROMs
pitrus-
- LTE: deb
- Wi-Fi: flo
LineageOS Extras
- addonsu-16.0-arm-signed.zip
- addonsu-remove-16.0-arm-signed.zip
Magisk
Open GApps
How to flash LineageOS and Open GApps​1. Move any files you want to keep to your computer or flash drive via a USB OTG cable – ! Or you will lose them !
2. Download your LineageOS Rom and GApps Package,
3. Boot into Recovery Mode (Hold volume up and Power button until you see TWRP's splash screen),
4. Wipe > Advanced Wipe > Select On (enable tick) for Dalvik / Art Cache, System, Data, Internal Storage, Cache,
5. Swipe to Wipe at Bottom of Screen,
6. Back to Main start screen,
7. Wipe > Format Data,
8. Type 'Yes' and press blue checkmark at the bottom-right corner,
9. Go Back to Main Start Screen,
10. Move your LineageOS Rom and GApps Package to the internal storage,
11. Install > select a zip file to flash (optionally, Add More Zips > select another zip file to flash),
11. After you have finished installing the Rom and GApps > Wipe Cache/Dalvik > Swipe to Wipe,
12. Reboot System! Enjoy!
Typically if you do not do a Clean Install then you are not allowed to report errors or problems. If you Dirty Install and you do have problems then you will be asked to Wipe All and Clean Install and see if the problems still exist. This is a DAILY changing rom and any bug that you found was not working on the previous day's build may be fixed with todays daily build. On a side note, the code implemented to fix that bug could potentially break something that worked on that previous build. So reporting problems on a day old build that you dirty flashed over whichever build of whichever rom you had flashed previously will not be accepted as a true error.
Problems known to happen after a Dirty Installation​1. A muddled up mess of a system. You are taking a rom and installing a newer rom with changes over the top of your old rom. Between these two periods of time during which you used your phone and created data, changed system options, and used apps. This is absolutely increasing the risk of causing problems somewhere in the system/data partitions. Some people have luck with Dirty Flashing. However, it's always hit-and-miss because of what we mentioned above about bug fixes breaking previously working functions. Dirty flashing doesn't only create problems if the source code of the system data and the system settings of the new build are significantly different from those of your previous build. That's not to say that Clean Installing won't ever create problems, but only bugs present on a Cleanly Installed rom are relevant for development purposes.
* Clean Install: Fully wiping everything and installing the rom onto a fully clean system/data partition of the phone.
* Dirty Install: Installing the rom and GApps over top of the older rom to save time and not have to reinstall all the user apps and tweaking system and app settings that usually take a lot of time to set up as you like.
Bugs
- Encryption does not work at all. Upon encrypting your tablet, you will be unable to reboot into System. This is a bug in all AOSP-based custom Pie roms for deb and flo.
- You tell us!
Changelog
All major features and bug fixes are discussed in detail by the developers in the thread, whenever they are implemented. All builds include the latest upstream Changes for all devices from LineageOS.
Credits
- Every open source developer and user who contributes directly or indirectly to the LineageOS community in the development of and in providing feedback for deb and flo.
Sources
- deb device tree
- flo device tree
- kernel
- blobs
XDA:DevDB Information
LineageOS 16.0, ROM for the Nexus 7 (2013)
Contributors
ripee, followmsi, pitrus-, flex1911, Clamor
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: System partition large enough to accommodate the rom and GApps.
Version Information
Status: Stable
Current Stable Version: 9
Stable Release Date: 2019-08-11
Created 2019-02-22
Last Updated 2019-11-10

Reserved

Reserved

Awesome! Keep up the great work and thank you for keeping this devices development alive

JT1510365 said:
Awesome! Keep up the great work and thank you for keeping this devices development alive
Click to expand...
Click to collapse
All credit to followmsi and flex1911

oh yeah maga
make android great again

Is this the same ROM you can find in followmsi androidfilehost directory?
https://androidfilehost.com/?w=files&flid=289297
Yesterday I try the Ressurection Remix 7.0
Everything works fine.
But in Kodi i cannot use the h264 hardware decoder.
Have this Rom the same issue?

DaCl88 said:
Is this the same ROM you can find in followmsi androidfilehost directory?
https://androidfilehost.com/?w=files&flid=289297
Yesterday I try the Ressurection Remix 7.0
Everything works fine.
But in Kodi i cannot use the h264 hardware decoder.
Have this Rom the same issue?
Click to expand...
Click to collapse
Since the sources I linked are followmsi's, yes this is the same rom, but built more recently to take advantage of the lineage commits added since followmsi's last build. Because of this, it will have the same h.264 bug in Kodi.

Rom is working very well but I cannot flash Gapps. I chosen Pico 9.0 arm. Which one should I use ? Thank you !

gaja22 said:
Rom is working very well but I cannot flash Gapps. I chosen Pico 9.0 arm. Which one should I use ? Thank you !
Click to expand...
Click to collapse
Did you re-partition the memory, as described in the FAQ's in the OP?

ripee said:
All credit to followmsi and flex1911
Click to expand...
Click to collapse
Of course

To a person who has installed this ROM, I have one question. If the orientation is locked to Landscape, when you turn on the screen, does the screen start from landscape mode, or does it start from portrait mode and quickly rotates to landscape mode?
It does not happen on the official LOS 14.1, but it did happen with unofficial LOS 15.1. This rotation is problematic, because it often causes a significant delay when I turn on the screen, depending on the app I had been using.

Thx!
Will test this ROM!

yourrealking said:
To a person who has installed this ROM, I have one question. If the orientation is locked to Landscape, when you turn on the screen, does the screen start from landscape mode, or does it start from portrait mode and quickly rotates to landscape mode?
It does not happen on the official LOS 14.1, but it did happen with unofficial LOS 15.1. This rotation is problematic, because it often causes a significant delay when I turn on the screen, depending on the app I had been using.
Click to expand...
Click to collapse
Hello, my lock screen will be temporarily displayed in portrait then rotates to landscape.

Quick question. A full data wipe? As in a full data partition wipe including rom backups, pictures, videos, personal files? Cant say I have ever hear of a rom requesting this and I have been flashing roms for a decade. Perhaps I am missing something. Is this only the first time I flash and then a dirty flash for daily builds?

hlxanthus said:
Quick question. A full data wipe? As in a full data partition wipe including rom backups, pictures, videos, personal files? Cant say I have ever hear of a rom requesting this and I have been flashing roms for a decade. Perhaps I am missing something. Is this only the first time I flash and then a dirty flash for daily builds?
Click to expand...
Click to collapse
A full data wipe cleans the data partition on which user apps and system settings reside. Your personal files are on the internal storage partition, which does NOT get wiped by TWRP when factory wiping.
Yes, clean flash prior to the first flash, then dirty flash subsequent builds.

ripee said:
A full data wipe cleans the data partition on which user apps and system settings reside. Your personal files are on the internal storage partition, which does NOT get wiped by TWRP when factory wiping.
Yes, clean flash prior to the first flash, then dirty flash subsequent builds.
Click to expand...
Click to collapse
Read the OP's instructions again. It clearly says to wipe data and internal storage.

Hi and thanks for (the) pie. It works great for the main user but i have a strange problem with a secondary (or guest) user:
Whenever i switch to the secondary user the navigation bar (three buttons) disappears. The bar is not just hidden but seems to be really gone/killed. When switching back to the main user the bar is still missing and i need to restart to get it back. Any ideas?

The pie ROM works great on my Nexus. Thank you so much. It's amazing. I hope you plan to add the security patches every month. Thx.

hlxanthus said:
Read the OP's instructions again. It clearly says to wipe data and internal storage.
Click to expand...
Click to collapse
Yes, I have read the OP. Wiping both data and internal storage is for the sake of less experienced users who should be starting fresh no matter what rom they're coming from. As you have more experience, please use your judgment to wipe whatever you know needs to be wiped.

[10] LineageOS 17.1 for z3c

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* Your warranty is now void.
*
* I am 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.
*/[/COLOR]
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation instructions
Prerequisites:
Unlocked Sony Xperia Z3 Compact
Fastboot drivers to install TWRP
Micro-USB Cable to connect your phone to your computer
Install:
Reboot to TWRP. *
Wipe cache, dalvik cache, data and system.
Install ROM.
Install 10.0 Gapps for ARM. **
* recommended TWRP: Post #2
** optional, opengapps
Downloads
Download the ROM
Over the Air Updates
To use OTA updates please read Post #2
Sources
DEVICE:
https://github.com/LineageOS/android_device_sony_z3c
https://github.com/LineageOS/android_device_sony_msm8974-common
https://github.com/LineageOS/android_device_sony_shinano-common
KERNEL:
https://github.com/LineageOS/android_kernel_sony_msm8974
Addons
OpenGapps
Magisk
Thanks
Whole LineageOS Team for this amazing ROM
@koron393
@SpiritCroc
@Myself5
@nailyk
@drakonizer
@rcstar6696
@tomascus
I hope I haven't forgot anyone
Bugs
Current hardware support state: Gist
WHAT'S BROKEN
You tell me.
XDA:DevDB Information
LineageOS 17.1 for z3c, ROM for the Sony Xperia Z3 Compact
Contributors
NeoArian
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: 23.5.A.1.291
Based On: AOSP
Version Information
Status: Beta
Created 2019-10-02
Last Updated 2020-01-04

OTA and TWRP recovery
Over the Air Updates
My upload script automatically pushed OTA updates to my GitHub.
If you want to make them visible through the Updater you can flash the attached magisk module LineageOS-17.1_z3c-OTA-v1.zip or add the line
Code:
lineage.updater.uri=https://raw.githubusercontent.com/ArianK16a/OTA/lineage-17.1/z3c.json
manually to your build.prop. You should use the recommended TWRP so that the updates flash fine.
TWRP recovery
TWRP 3.3.1 for our z3c with Android 10!
The TWRP for Android 10 is attached to this post.
Source is available at: https://github.com/z3c-pie/twrp_device_sony_z3c/tree/android-10.0
Changelog for twrp-3.3.1-1-z3c-20191212-sar.img
Improved System as root support, /system is a symlink to /system_root/system now
Changelog for twrp-3.3.1-1-A10.0-z3c.img
Added Bootlogo, booting from offline state will display the original sony logo now instead of nothing
Fixed fastboot boot
Updated kernel cmdline from 23.5.A.1.291
How to install this build:
Reboot to fastboot by holding volume up while connecting your device to your computer
Open a terminal and move to the directory with TWRP in it
Rename the downloaded image to twrp.img
Type
Code:
fastboot flash recovery twrp.img
Boot into TWRP while the device is powered off press the power and volume down button
Feel free to ask questions or give feedback about TWRP here .
Have a nice day!
Additional information about the recovery on this device:
First of all we should make the basics clear: On our Z3 Compact we have got a bootloader update which can boot a recovery from powered off state by pressing volume down and the power button. Because we haven't ever had this updated bootloader and not all sony devices received the update, there have been some intelligent people who brought a special init binary which can handle recovery boots during a normal boot. This means when using advanced reboot from the ROM or pressing a volume key while the sony logo appears at boot. https://github.com/LineageOS/android_device_sony_common/commits/lineage-16.0
To make this work there is this method to extract the ramdisk: https://github.com/LineageOS/androi...eage-16.0/extract_ramdisk/extract_ramdisk.cpp which uses zlib to decompress it. So far so good, zlib can decompress the default compression for recovery ramdisk which is gzip. However LZMA is more effective to reduce the size so we took it's advantage: https://github.com/omnirom/android_...mmit/885b01223a460d3f2500155ea415bdc8573679bc in order to fit recoverys compiled from recent environments (android-9.0 in my case) into our small FOTAKernel partition.
According to this change the init_sony can't handle the recovery boot anymore because it can't decompress the recovery's ramdisk so nailyk and Diewi (as far as i know) added support to decompress LZMA compressed ramdisk's with this chain: https://github.com/sonyxperiadev/device-sony-common-init/pull/20/commits
However these commits have never been merged into the LineageOS/android_device_sony_common nor the sonyxperiadev/device-sony-common-init. Since your ROM, CarbonROM, is using a fork of LineageOS/android_device_sony_common is missing these commits the recovery boot fails with a kernel panic, like this: https://del.dog/egawososux.htm
So you can either use a recovery which doesn't compress the ramdisk with LZMA (for example the one from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192 or ask your ROM developer to pick the according commits into the sony_common tree/use my fork of LineageOS's one https://github.com/z3c-pie/android_...mits/fa85dfcc07f42d73f9a1abf1f4c82d8bf0486a93 which would enable you to use recent TWRP builds with a LZMA compressed ramdisk.
I hope i presented it clearly and in the right way,
Have a nice day!
EDIT: Minimized patch for LZMA is available here: https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923
Click to expand...
Click to collapse

The new build is up!
Get it from here: https://sourceforge.net/projects/ep...age-17.0-20191002-UNOFFICIAL-z3c.zip/download
Make sure to use the new TWRP from Post #2 because Android 10 introduces System-as-Root which can lead to weird behaviour in the old TWRP.
Note that there are not all features from LineageOS 16.0 ported over yet and there can be unexpected, yet unlisted bugs.
MY personal hardware support list can be found here: https://gist.github.com/ArianK16a/1e46c463a5c910efb322d9cf0e16c3c0 but as always, i can't guarantee you anything!
Happy flashing!

I will try, thx :>
but there are no opengapps for 10,
what about this? will be good?
https://www.cyanogenmods.org/download-gapps-for-android-10/

hah ok now I don`t know anything... ;/
still same problem with this freakin camera and torch exactly like in v16
all my steps:
1.
flashtool64 -> Stock Android 6.0.1 for D5803 - 23.5.A.1.291 - Unbranded - Baltic Generic (1288-5413)
https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
2.
TWRP for 6.01 - with this https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
Kernel .575 -> recovery for mm575 ->kernel .291
3.
installation of yours TWRP - twrp-3.3.1-A10.0-z3c
4. in twrp 3.3.1 wipe cache, dalvik cache, data and system, rom installation
5. camera and torch doesn`t working ;/ "camera keeps stopping" and torch is greyed out

NIce, thank you

hhpl said:
hah ok now I don`t know anything... ;/
still same problem with this freakin camera and torch exactly like in v16
all my steps:
1.
flashtool64 -> Stock Android 6.0.1 for D5803 - 23.5.A.1.291 - Unbranded - Baltic Generic (1288-5413)
https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
2.
TWRP for 6.01 - with this https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
Kernel .575 -> recovery for mm575 ->kernel .291
3.
installation of yours TWRP - twrp-3.3.1-A10.0-z3c
4. in twrp 3.3.1 wipe cache, dalvik cache, data and system, rom installation
5. camera and torch doesn`t working ;/ "camera keeps stopping" and torch is greyed out
Click to expand...
Click to collapse
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
hhpl said:
I will try, thx :>
but there are no opengapps for 10,
what about this? will be good?
https://www.cyanogenmods.org/download-gapps-for-android-10/
Click to expand...
Click to collapse
There are GApps: https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/

NeoArian said:
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
Click to expand...
Click to collapse
ok I had something in my head that I needed first this marshmallow recovery... I don`t know why
but now I flashed once again 291 and then yours twrp and wiped all the stuff ofc included data and still torch and camera doesn`t work ;/

hhpl said:
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
ok I had something in my head that I needed first this marshmallow recovery... I don`t know why
but now I flashed once again 291 and then yours twrp and wiped all the stuff ofc included data and still torch and camera doesn`t work ;/
Click to expand...
Click to collapse
Format is not wipe. Make sure that twrp asks you to confirm by typing yes.

NeoArian said:
Format is not wipe. Make sure that twrp asks you to confirm by typing yes.
Click to expand...
Click to collapse
ok done, once again nothing new, still same situation

Can this ROM be installed on top of LineageOS 16 without wape?

Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks

marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
Are you talking about the GApps I posted a few posts back? https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/ If I remember correctly I didn't have problems while I tested them...

NeoArian said:
Are you talking about the GApps I posted a few posts back? https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/ If I remember correctly I didn't have problems while I tested them...
Click to expand...
Click to collapse
No, I found a beta version on Google.
Gotta check again with the one you provided, I'll edit this post in a while
Edit: buttons don't work again

marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
wow, so what I`m doing wrong... could you tell me how you install this rom step by step and what rom you had before? steps before installation and steps after or something, I have installed this rom 10 times and never got my camera work, that is crazy

hhpl said:
wow, so what I`m doing wrong... could you tell me how you install this rom step by step and what rom you had before? steps before installation and steps after or something, I have installed this rom 10 times and never got my camera work, that is crazy
Click to expand...
Click to collapse
The same basic steps you'll find in the OP

marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
I've experienced the same issue after installing gapps - only back button works. Gesture navigation is working fine.
Other bugs I've noticed:
-battery icon style cannot be changed
-launching camera app with hardware button doesn't work
-system accent color cannot be changed (there is only one option listed)

Barciej33 said:
Other bugs I've noticed:
-battery icon style cannot be changed
-launching camera app with hardware button doesn't work
-system accent color cannot be changed (there is only one option listed)
Click to expand...
Click to collapse
You must read 1st to 3rd post.
LOS17 is just getting started.
Note that there are not all features from LineageOS 16.0 ported over yet and there can be unexpected
Click to expand...
Click to collapse

@NeoArian Any chance for a screen recording of how it runs?

JamesMars said:
@NeoArian Any chance for a screen recording of how it runs?
Click to expand...
Click to collapse
No? If you are interested you can test it yourself.
I have my holidays now anyway.