[ROM][UNOFFICIAL][10] LineageOS 17.1 for Galaxy J4+ [j4primelte] - Samsung Galaxy J4+ ROMs, Kernels, Recoveries, & Ot

[ROM][UNOFFICIAL][10] LineageOS 17.1 for Galaxy J4+ [j4primelte] - Samsung Galaxy J4+ ROMs, Kernels, Recoveries, & Ot

{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here 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.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
GPS
NFC
Flashlight
Mobicore keystore
Known issues:
VoLTE
Selinux is permissive
Instructions :
If you're on oreo, flash OneUI latest.
Download the latest build.
Reboot to recovery
Flash the latest build.
Optional: Flash GApps for Google Services and Magisk for root.
Reboot
Downloads :
All updates will be here.
Sources :
Device Tree
Common Device Tree
Vendor Blobs
Kernel Source
XDA:DevDB Information
[ROM][UNOFFICIAL][10] LineageOS 17.1 for Galaxy J4+ [j4primelte], ROM for the Samsung Galaxy J4+
Contributors
ataberkozen
Source Code: https://github.com/LineageOS
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: OneUI, U2
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 1.1
Beta Release Date: 2020-02-25
Created 2020-02-25
Last Updated 2020-03-10

Changelogs :
Public Beta 3 - 18/03/2020 :
Fixed a issue which some users have broken ril.
Fixed a issue which some users have broken nfc.
Public Beta 2 - 10/03/2020 :
Merge Security Patch: 5 March 2020
Fix audio on second sim: @Geckyn
Fix HDR on Camera.
Fix FM Radio.
Fix torch releated issues.
Fix Mac Adress releated issues.
LineageOS Source Upstream.
Public Beta 1 - 26/02/2020 :
First public release.

Special Thanks :
@BarryBlackCat for non-stop, day and night testing builds.
@Geckyn for pointing out some stuff. Thanks man.

I will NOT accept your bug report if you are using a custom kernel.
I will NOT accept your bug report if you are using a modification (Like some magisk modules etc.).
I will NOT check your bug report if you didn't provide any logs (Some bugs may will be checked).

Camera doesn't take HDR photo (or hang when switching between HDR and non HDR mode), it also happened on other custom ROM as well.
No magisk module or custom kernel installed.
Here is the logcat with "camera" keyword as filter: https://pastebin.com/RrDvAtjw

Andhika24kd said:
Camera doesn't take HDR photo (or hang when switching between HDR and non HDR mode), it also happened on other custom ROM as well.
No magisk module or custom kernel installed.
Here is the logcat with "camera" keyword as filter: https://pastebin.com/RrDvAtjw
Click to expand...
Click to collapse
Thanks.

KotaMangga said:
Ashyx kernel sir?
Click to expand...
Click to collapse
Let me make the steps clear for you:
1) You must be on Android Pie (custom or stock ROM doesn't matter). If you're on Samsung Oreo (U2), upgrade to Samsung Pie first so the device bootloader will be upgraded to U4 or newer.
2) If you're on Samsung Pie, flash TWRP and do all the required steps (this includes flashing RMM bypass, flashing encryption disabler, and formatting your data). If you're already using custom ROM, just skip this step.
3) Go to TWRP. As far as I remember, you can boot directly to TWRP by pressing POWER + VOL UP when the device is off.
4) In TWRP, swipe to allow modifications. Go to wipe - advanced wipe - and select dalvik/ART, system, data, and cache - swipe to wipe. You may also want to wipe your internal/external storage to avoid dirty data from previous ROM and apps.
5) Go to install - select your ROM zip and flash it - also flash Magisk and GApps after that (if needed)
6) Reboot system. If asked to install TWRP system app, just unselect all checkboxes and press do not install.
7) You're done. First boot will take a while, be patient.
No, kernel is already shipped within the ROM itself. No ROM comes with no kernel (lol). Moreover, most custom kernels on the J4+ forum may not be compatible for Android 10 yet. The OP also stated do not flash custom kernel if you want to get his support. However, if you insisted, make sure to reflash Magisk (if installed before) after flashing custom kernel. Alternatively, flash the custom kernel first before flashing Magisk.
No, OrangeFox recovery is not tested. If you're having trouble flashing the ROM using OrangeFox, unpack TWRP tar file and flash the recovery.img as recovery inside OrangeFox. After reboot, you will have TWRP again as your recovery (press POWER + VOL UP, as stated earlier).
ROM screenshot: (Stock apps are actually there and just like in LOS 16, sorry I already uninstalled most of them)

Andhika24kd said:
Let me make the steps clear for you:
1) You must be on Android Pie (custom or stock ROM doesn't matter). If you're on Samsung Oreo (U2), upgrade to Samsung Pie first so the device bootloader will be upgraded to U4 or newer.
2) If you're on Samsung Pie, flash TWRP and do all the required steps (this includes flashing RMM bypass, flashing encryption disabler, and formatting your data). If you're already using custom ROM, just skip this step.
3) Go to TWRP. As far as I remember, you can boot directly to TWRP by pressing POWER + VOL UP when the device is off.
4) In TWRP, swipe to allow modifications. Go to wipe - advanced wipe - and select dalvik/ART, system, data, and cache - swipe to wipe. You may also want to wipe your internal/external storage to avoid dirty data from previous ROM and apps.
5) Go to install - select your ROM zip and flash it - also flash Magisk and GApps after that (if needed)
6) Reboot system. If asked to install TWRP system app, just unselect all checkboxes and press do not install.
7) You're done. First boot will take a while, be patient.
No, kernel is already shipped within the ROM itself. No ROM comes with no kernel (lol). Moreover, most custom kernels on the J4+ forum may not be compatible for Android 10 yet. The OP also stated do not flash custom kernel if you want to get his support. However, if you insisted, make sure to reflash Magisk (if installed before) after flashing custom kernel. Alternatively, flash the custom kernel first before flashing Magisk.
No, OrangeFox recovery is not tested. If you're having trouble flashing the ROM using OrangeFox, unpack TWRP tar file and flash the recovery.img as recovery inside OrangeFox. After reboot, you will have TWRP again as your recovery (press POWER + VOL UP, as stated earlier).
Click to expand...
Click to collapse
OK , thanks for the tutorial also the full explanation

Can we get some screenshots?

any temp fix for VoLTE and sec sim voice

swarupgolui said:
any temp fix for VoLTE and sec sim voice
Click to expand...
Click to collapse
Maybe you could try sending logcat when attempting voice (call?) on SIM 2. There is a handy app on Play Store called "Logcat Reader" to catch & filter logs easily, just press to round button to record the logs.
I currently can't do it since I don't have someone important to call.

swarupgolui said:
any temp fix for VoLTE and sec sim voice
Click to expand...
Click to collapse
Samsung's ims is heavily OneUI framework dependent. Fixing it is kinda miracle. I don't think it will be ever fixed. But if you contact me on telegram, we might try to fix it. Also trying to fix voice of second sim.

This rom for j6+ sir? , I cant flash it .

KotaMangga said:
This rom for j6+ sir? , I cant flash it .
Click to expand...
Click to collapse
Check the thread on j6+ forum.

ataberkozen said:
Samsung's ims is heavily OneUI framework dependent. Fixing it is kinda miracle. I don't think it will be ever fixed. But if you contact me on telegram, we might try to fix it. Also trying to fix voice of second sim.
Click to expand...
Click to collapse
telegram link?

swarupgolui said:
telegram link?
Click to expand...
Click to collapse
MacTavishAO

ataberkozen said:
MacTavishAO
Click to expand...
Click to collapse
already send the msg reply plz
my id @metalgod_IN

ataberkozen said:
Check the thread on j6+ forum.
Click to expand...
Click to collapse
no, I mean it's for j4+?
E3004 : This package is for j6primelte ; your device is j4primelte.

KotaMangga said:
no, I mean it's for j4+?
E3004 : This package is for j6primelte ; your device is j4primelte.
Click to expand...
Click to collapse
Don't click on "Download Latest Version", click on zip name with j4primelte.

I has installed the rom sir , this rom more faster.
I see little problem :
1. when i change to power saver , battery indicator going red . but after switch mode , its back normal

Related

[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?

[ROM] [ 8.1.0 ] Official madOS - Vernee Thor [MT6753]

Reserved
First time Install Instructions
0) Preparation
0.1) Backup your important data to PC
0.2) Download “twrp_vernee_thor_oreo.img“:
http://www.mediafire.com/file/m58f5ifmopyb209/twrp_vernee_thor_oreo.img
0.3) Download “madOS_8.1.0_thor_2018xxyy.zip“ https://www.facebook.com/MediatekAndroidDevelopers/
0.4) Optional, Download “Google Apps (aka Gapps)“: http://opengapps.org/. Choose: “ARM64“, “Android 8.1“, “nano“ or “pico“ package
1) Flash the recovery and boot to it. (choose option a) if you don't have another TWRP already installed, else choose b))
1.1a) Boot in the BOOTLOADER mode (using ADB: "adb reboot-bootloader").
Then execute command “fastboot flash boot twrp_vernee_thor_oreo.img”;
and then “fastboot reboot” (this is a trick to directly bring you to the newly flashed recovery. You can't boot up your current/stock rom at this point anymore).
1.1b) Boot to your current TWRP. Choose install --> image, and select twrp_vernee_thor_oreo.img“. Then choose “recovery“ as the target. After few seconds, and succesful installation, hit “back“ several times, then go to “reboot --> recovery“
2) Install
2.0) Optional, but recommended: Go to "Wipe --> Advanced Wipe", click "Cache" and then "Repair or Change File system". Then select "Change File system" and choose "F2FS". Swipe to confirm.
Hit "back" three times (you can again choose a partition to change now). Choose "Data" and do as above.
Hit "back" several times, to get back to the main menu. Choose "Reboot --> Recovery".
2.1) While already in recovery (TWRP), connect your phone to pc, and copy “madOS_8.1.0_thor_2018xxyy.zip“ and the Google Apps to your phone.
2.2) Go to "Wipe", and directly slide the slider to the right.
2.3) Get back to main menu with the "back" button
2.4) Go to "Install" and hit “madOS_8.1.0_thor_2018xxyy.zip“, then uncheck all boxes and hit "Add more zips", now choose the Google Apps.
Confirm installation by swiping the slider to the right.
2.5) Reboot System
Click to expand...
Click to collapse
Follow up Install Instructions
Download rom and gapps
boot to recovery
flash rom and gapps
optional: flash superSu/Magisk
reboot system
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: Can I install this rom on any other device, than the one mentioned in the title/description?
A:
WTF! Of course not! It is not mentioned in the title/description for some reason...how stupid can one be?!
If you still come to my thread and ask this stupid question, I'll answer some random nonsense. Don't come to me to complain when you break your device!
Q: Which recovery should I use for this ROM?
A: Latest M.A.D. TWRP 3.2.1-0 recovery for OREO 8.1.0
Q: How do i flash new recovery ?
A:
1: You can flash it with a scatter file
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: Does this rom have any Theme support
A: Yup, We have working Theme Engine (madOS extras)
Update: On Oreo 8.1.0:
- We have extended Theme support even further ( madLauncher, messaging, etc)
- As well as many fixes
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)
IF there are problems in rooting, you need to report it to the root-threads...There's nothing we can do
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 Vulcan?
A: No....duh! v
Q: Does doze work in this build?
A: Yup
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/pico
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.
Pure Nexus
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...

Reserved

Can I install it on my K4 Note?

Pritam Tumma said:
Can I install it on my K4 Note?
Click to expand...
Click to collapse
Can you read?

Is it possible to roolback to nougat (7.1.2) after install this update?

drifeter said:
Is it possible to roolback to nougat (7.1.2) after install this update?
Click to expand...
Click to collapse
Yes, you would need to flash the N twrp, wipe and flash the N rom

"Size of image is larger than target device" trying to flash new recovery. I just wiped everything, now I'm out of OS for this moment xD
Can you help me?
I used your last OS on this phone. It's before october(received it on may of that year) and MT6753
I have twrp 3.0.... from megthebest
Thank you for your patience
--
EDIT: Can I wipe "internal storage"? I didn't wipe everything :v

ZeDdYRov said:
"Size of image is larger than target device" trying to flash new recovery. I just wiped everything, now I'm out of OS for this moment xD
Can you help me?
I used your last OS on this phone. It's before october(received it on may of that year) and MT6753
I have twrp 3.0.... from megthebest
Thank you for your patience
--
EDIT: Can I wipe "internal storage"? I didn't wipe everything :v
Click to expand...
Click to collapse
I'll check the size error in a bit...
Of course you can wipe internal storage, but keep in mind that this is where your pictures are.
edit: checked/flashed the twrp_vernee_thor_oreo.img.... all fine with it...its size is 13.4mb, the recovery partition is 16mb. i suppose this 'megTheBest recovery' just isn't the best....

DerTeufel1980 said:
I'll check the size error in a bit...
Of course you can wipe internal storage, but keep in mind that this is where your pictures are.
Click to expand...
Click to collapse
Thank you for your quick response!
I wiped internal storage, data, cache, and system. Do I should wipe anything more in order for this to work? I'm still stuck on the error. I go to Install - Install Image, pick the twrp_vernee_thor_oreo.img file on Recovery Partition, and receive the message on the comment above.

ZeDdYRov said:
Thank you for your quick response!
I wiped internal storage, data, cache, and system. Do I should wipe anything more in order for this to work? I'm still stuck on the error. I go to Install - Install Image, pick the twrp_vernee_thor_oreo.img file on Recovery Partition, and receive the message on the comment above.
Click to expand...
Click to collapse
Since you already removed everything, I'd suggest to just install the stock 6.0 rom with flashtool and 'firmware upgrade' option

DerTeufel1980 said:
I'll check the size error in a bit...
Of course you can wipe internal storage, but keep in mind that this is where your pictures are.
edit: checked/flashed the twrp_vernee_thor_oreo.img.... all fine with it...its size is 13.4mb, the recovery partition is 16mb. i suppose this 'megTheBest recovery' just isn't the best....
Click to expand...
Click to collapse
lol, I just gave the name of the dev because could help you figure it out. I'm n00b on this :V
I just did sh** with the files. I was trying to flash with a file called twrp_blablabla.img that was 422MB. For some reason I missclicked on the file while saving :v
EDIT: SORRY and Thank you

Yeahhhhhh finally 8.1 on our Thor.... So great!
Thank you so much Mad-team.
Weeeeeeeeeeeeee!!!

DerTeufel1980
Thank you for your work
Everything works without problems.
:good:

I'm on madOS for 40min and I'm loving it. This is fully customize as you want this machine working. Well played!!! LOVE YOU MAD TEAM

Hello again! Software buttons get bugged when we enter on opened apps menu, and its has a ghost start buttons I'm n00b and I found a bug: D

ZeDdYRov said:
Hello again! Software buttons get bugged when we enter on opened apps menu, and its has a ghost start buttons I'm n00b and I found a bug: D
Click to expand...
Click to collapse
I am using softbuttons for a long time and they always work good. Maybe you can try to go back to default settings... Wipe cache/dalvik and try again

This is for the first revision, is it possible for you to make it for the second? Please...

RalphMalph said:
I am using softbuttons for a long time and they always work good. Maybe you can try to go back to default settings... Wipe cache/dalvik and try again
Click to expand...
Click to collapse
If I could be able to change what buttons do... the back button on soft button is on the right, and I'm used to it on the left. There's any option on madOS to change what I'm telling to you?
EDIT: I read second time and notice what you said. I'll try! Thank you for the tip

ppdua said:
This is for the first revision, is it possible for you to make it for the second? Please...
Click to expand...
Click to collapse
Re-read at least the first ten lines of the first post, before asking things like this

[A-ONLY][TREBLE][9.0][A530F/A530W/A730F] Vendor Pie For Galaxy A8/A8+ 2018

I'm not responsible for whatever damage this could possibly cause to your device.
Before Starting Make Sure You Treble Your Device By This Guide here
If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal
Welcome to Pie Vendor For Galaxy A8/A8+ 2018 ONLY FOR A530F/A530W/A730F
Some information you should know..
Full TREBLE Documentation here : https://source.android.com/devices/architecture
Generic System Image (GSI) Documentation here : https://source.android.com/setup/build/gsi
GSIs are not the most stable and many users prove they are unable to read. they just want ready stuff. with this project that is not the case. if you skip the instructions/F.A.Qs and notes, dont bother installing this project as you probably wont be able to get it running.
This is a fully featured VENDOR and KERNEL designed for this device to support project treble, it is based on other Exynos 7885 Vendors and modified to support our devices, i have also added few patches and fixes to this vendor to get the best possible experience
The vendor is pretty much bugles, therefore any bugs you face, Report them to the appropriate Threads of the GSI you installed or github issues section, as those are not mine to fix i only provide the vendor and kernel that allows GSIs to run on.
- VENDOR FEATURES:
Wi-Fi & Hotspot
Telephony & Ril (Mobile Data, Calls, SMS, MMS)
NFC
Camera
Bluetooth
GPS
Fingerprint
All Sensors
- STEPS FOR INSTALLING TREBLE VENDOR:
Make Sure You Treble Your Bevice By This Guide here
Boot into Twrp recovery
Wipe System, Data, Dalvik and Vendor.
Select Vendor_Dumpster.zip
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be A-only_arm64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Reboot to TWRP Recovery
- STEPS FOR INSTALLING GAPPS
Download the appropriate opengapps
Go to TWRP , Install
Pick your OpenGapps.zip
Reboot to System
- KNOWN BUGS:
Bluetooth calls are broken
Credits:
- @ananjaser1211 for his contribution
- @TaifAljaloo for testing
Downloads. Changelogs , F.A.Qs below
XDA:DevDB Information
Project Treble, Vendor for the Samsung Galaxy A8 (2018)
Kernel Source
Contributors
prashantp01
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Current Stable Version: v1
Created 2019-05-17
Last Updated 2019-05-17

{
"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"
}
Come hang with us on our chat : Telegram
----------------------------------------------------------------
Treble Pie Vendor Dumpster V1.0 [LATEST]
Treble folder : Gdrive
Recommended GSI : Gdrive
Generic System Image (list) : Github
---------------------------------------------------------------
Bugs :
1- some users might face SDCard issues
If you did , back up its data and format it in GSI.
2- If you face "Error 70: Insufficient storage space available in the system partition" while flashing Gapps
If you get do this : Wipe > Advanced Wipe > select system > Repair or Change File System > Resize File System
Go back and flash Gapps
V1.0
-initial release

F.A.Q
For more details related to this project, read our dedicated Wiki page here.
Q : Do i need to format internal storage ?
A : No
Q : Can i use the Treble recovery for normal ROMs ?
A : Yes, it is preferred especially when making backups. just be sure to wipe vendor when switching to non treble roms
Q : What Camera is recommended ?
A : Footej and open camera works the best
Q : Can i flash any GSIs ?
A : No, only A-ONLY_ARM64 Are supported
Q : Can i flash any sGSIs ?
A : No unless they match the Arch above

reserved

I just flashed the Lineage OS v16 GSI with this vendor and found no problems other than no network bars (as mentioned above) and there were no problems with the camera and fingerprint. I will notify you later if there is a bugs
Thanks for your hard work ?

Sweet! I'm gonna be up all night!

This is fantastic. The boot time has decreased immensely.
Finally got aosp extended 6.5 to boot. Well i didn't, you did.
What a difference. Ressurection Remix as well. The 9.0. That one seems a bit iffy no matter.
I am noticing a different mobile data icon. It'll say 4g+
Not too far from normal full usage. Thank you.

mindlery said:
This is fantastic. The boot time has decreased immensely.
Finally got aosp extended 6.5 to boot. Well i didn't, you did.
What a difference. Ressurection Remix as well. The 9.0. That one seems a bit iffy no matter.
I am noticing a different mobile data icon. It'll say 4g+
Not too far from normal full usage. Thank you.
Click to expand...
Click to collapse
Where you able to get gapps installed it always failed for me.
This has happened on most of these roms

Yes i was. My method is a bit harsh though. I am a fan of internal destruction
So for the gsi, i wipe everything including internal. Then i reboot to recovery. Swipe to allow modifications. Install vendor. Install system image. Then reboot recovery flash fix boot. I almost never bother with gapps anymore until it boots fully. Then i'll immediately go into recovery and flash gapps then reboot of course.
I got sick of errors myself. If you find one you like or want to go back to then it may be worth trying for that perfect install. Almost there.
---------- Post added at 04:33 AM ---------- Previous post was at 04:20 AM ----------
https://downloads.aospextended.com/treble_gsi
Before only 6.1 worked. Now 6.5 starts in a minute or so. 6.3 boot looped before so i am going to see what happens now.

mindlery said:
Yes i was. My method is a bit harsh though. I am a fan of internal destruction
So for the gsi, i wipe everything including internal. Then i reboot to recovery. Swipe to allow modifications. Install vendor. Install system image. Then reboot recovery flash fix boot. I almost never bother with gapps anymore until it boots fully. Then i'll immediately go into recovery and flash gapps then reboot of course.
I got sick of errors myself. If you find one you like or want to go back to then it may be worth trying for that perfect install. Almost there.
---------- Post added at 04:33 AM ---------- Previous post was at 04:20 AM ----------
https://downloads.aospextended.com/treble_gsi
Before only 6.1 worked. Now 6.5 starts in a minute or so. 6.3 boot looped before so i am going to see what happens now.
Click to expand...
Click to collapse
I'm using ion- v1.0.c 9.0 without any issues.
For some reason on the newer gsi roms you can't get gapps to install.
ion rom gapps are included.

mchlbenner said:
I'm using ion- v1.0.c 9.0 without any issues.
For some reason on the newer gsi roms you can't get gapps to install.
ion rom gapps are included.
Click to expand...
Click to collapse
I have never heard of that. Of course I am downloading but is there any information about it besides a file on android file host?

mindlery said:
I have never heard of that. Of course I am downloading but is there any information about it besides a file on android file host?
Click to expand...
Click to collapse
I had not heard of it also but it seems to work without issue.
Only thing on screenshot you have edit where photo is being stored.

Does this allow me to use system-as-root gsis? Since android 9 treble implementation is supposed to be system as root even on aonly, I would guess so, but I couldn't get my device to boot with one yet.

Weird, I can't even get aospextended to work... It just bootloops without bootanimation.
Edit: nvm, I got it to work, but I had to flash the oreo vendor first, and then the pie vendor.
Edit2: fingerprint doesn't seem to work even with fp patch (it's weird, it registers the fingerprint, and even validates it, but it does nothing on the lockscreen)
Edit3: restart fixed it

I have a few questions
I used to flash the usual custom roms so is this is the same thing i mean that if i can use it to flash custom roms
And which roms exactly working perfectly on this device without any issues
Also should i root my phone before installing it or what exactly should i do
Is it stable and doesn't have any problems or will i face some problems while im using it

For some reason on aosp extended gsi the phone will stay stuck at the charging screen (gray one without percentage) when charging when its turned off, disconnecting the cable doesn't do anything, it stays stuck on this screen till i force reboot

CoinKiller said:
For some reason on aosp extended gsi the phone will stay stuck at the charging screen (gray one without percentage) when charging when its turned off, disconnecting the cable doesn't do anything, it stays stuck on this screen till i force reboot
Click to expand...
Click to collapse
Did you install GSI_Fix_boot.zip?

So I want to install Google phone but I cannot get it to work. Can you give me an alternative ?

If I want to install a different GSI I follow the steps again (install vendor, flash GSI, flash boot fix and fixes if needed) or just wipe system, data, cache and flash the new image+ boot fix

slawdos said:
Did you install GSI_Fix_boot.zip?
Click to expand...
Click to collapse
Yes but i had to format /vendor after installing that zip (it wasnt the zip fault!), Didn't that get installed in /system?

[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.

[ROM][UNOFFICIAL][13] LineageOS 20 for Xperia X Compact

{
"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:
#include <std_disclaimer.h>
/*
* 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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.LineageOS is based on the Android Open Source Project, with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.All the source code for LineageOS is available in the LineageOS GitHub organization.And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.You can also view the changelog for a full list of changes & features.Official LineageOS website : http://lineageos.orgAbout LineageOS Legal : http://lineageos.org/legal
Important Information
1. This ROM operates without ODM images, just follow the installation instructions.2. This ROM does not intended to support Google Camera, but you can try to play with some mods.
About FDE and FBEFull-disk encryption (FDE) has been completely deprecated since Android 13, and now we use software implementation of File-based encryption (FBE).FDE and FBE methods are incompatible with each other. FBE cannot decrypt data encrypted with FDE and cannot encrypt existing files. That's why you need to perform factory reset/format data (not just "wipe data") before switching between ROM's with different encryption methods.To make it a bit clear:- FDE (e.g. stock, LineageOS-16/19) -> FBE (LineageOS-20) -> NOT POSSIBLE! Format data is required.- FBE -> FBE -> POSSIBLE! You can update/upgrade using "dirty" installation as before, in case if encryption methods are the sameMoreover, to work with new encryption you need a recovery with appropriate support.Downloads Links
LineageOS 20:Unofficial: https://sourceforge.net/projects/loire-development/files/lineageos-20/kugoGoogle Applications (optional):MindTheGapps: https://androidfilehost.com/?w=files&flid=322935 (Android 13.0 -> arm64)XDA post about GApps: https://xda-developers.com/download-google-apps-gappsRecommended Recovery (optional):TWRP 3.x: https://forum.xda-developers.com/-/-t3793837
Flashing and updating
Before installation, please make sure you have read and understood everything correctly about FDE and FBE encryption methods.LineageOS clean install:
Download the latest build of LineageOS ROM
Full wipe and factory reset (recommended / backup to make sure not to loose data)
Flash the LineageOS ROM zip from the Recovery
Flash the GApps to have the Google Applications (optional)
Every additional zip you want to flash (optional)
Reboot
LineageOS update/upgrade:
Download the latest build of LineageOS ROM
Wipe cache and dalvik cache
Flash the latest LineageOS ROM zip from the Recovery
Every additional zip you want to flash (optional)
Reboot
You can also update using the built-in Updater (requires at least TWRP 3.6.x or LineageOS Recovery)
About the builds:
Kernel sources: https://github.com/Chippa-a/android_kernel_sony_msm8956
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Grab a logcat right after the problem has occurred
(Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0
(Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Also thanks to:
The LineageOS Team
The SODP Team
Everyone involved in working and testing
Contributors
Chippa_a
ROM OS Version: 13.x
ROM Kernel: Linux 4.9.x
Version Information
Status: Beta

FEATURES AND ISSUES
Boot: Ok
Bluetooth: Unknown
WiFi: Ok
WiFi Hotspot: Unknown
RIL - Phone - Data: Ok
GPS: Ok
Camera: Unknown
Camcorder: Unknown
Lights: Ok
MicroSD: Ok
Accelerometer: Ok
Compass: Ok
Gyroscope: Ok
QTI sensors: Ok
Touchscreen: Ok
FM Radio: N/A
Fingerprint: Ok
Vibrator: Ok
Microphone: Ok
Audio & music: Ok
Bluetooth audio: Ok
NFC: Unknown (HCE: Unknown)
Kernel: Ok (WIP)
Graphics: Ok
3D Rendering: Ok
Clock: Ok
DRM: Unknown
Offline Charging: Ok
USB: Ok
USB Tethering: Unknown
USB OTG: Ok
Encryption: Ok
SEPolicies: Enforcing

It's amazing bro, i can't bealive my device got A13

It seems the device is working again - post removed

soomon said:
I installed this system, and at the 2nd reboot my phone is dead. completely dead. seems it has been bricked before I even could log into my google account.
It doesnt even react to power any more.
Of course the phone is old and wasnt used for a long time, so I dont know if it got bricked by the OS or the hardware.
but it's dead.
be careful people!
Click to expand...
Click to collapse
It's almost impossible to brick this device completely just by ROM, unless you're doing something very unusual or developer-related.
This ROM has been tested by user for more than two weeks and everything was fine. It also been tested by Xperia X users since March, there was nothing like that either... and there never was actually.
Anyway, there is no specific in your message, except "It doesnt even react to power any more". Try to get adb/fastboot modes, charge or flash stock firmware. If no luck, I'm pretty sure it's a hardware issue, probably battery or something else.

I was also thinking about this and it was hard for me to believe the custom OS could actually damage the hardware.
I am happy to report it seems to be the device itself that caused the issue and not the rom. Today it was working Since it is an old device I'm assuming it was a hardware issue, so I deleted my old post.
It's working perfectly now. thank you so much!

I'll install this asap. Cant belive that this device is live again. Im using it as main phone. Gonna post my experience with rom here. Cheers
Edit: Cant seems to make it work . i was on latest stock, did full wipe , installed clean los20 , no gapps no additional zipps . it goes past sony logo shows black screen and immediately restarts on that black screen . Any suggestions ?
Edit 2 : I could not boot to twrp , i needed to install it again after los20 zip, like there is no recovry ? Is that normal ?

After install this rom i found bugs on this rom A13 LOS 20:
-WIFI
-HOTSPOT
-TAP TO WAKE NOT WORK
- GPS can't lock
- NFC
Edit : after reinstall from Lineage 19 to Lineage 20 , Wifi , hotspot , Gps , working fine
Thanks for @Chippa_a and team , share and build rom for x compact

Deep sleep pretty good , keep it up

shandu98 said:
Edit 2 : I could not boot to twrp , i needed to install it again after los20 zip, like there is no recovry ? Is that normal ?
Click to expand...
Click to collapse
Do you have the latest TWRP offered on the other thread? If you get a boot loop back into TWRP you can try tapping restart to system which is an option within TWRP. If you still have problems after with a boot loop try a clean install by wiping dalvik, cache, system, internal storage, followed by formatting data, then reboot to TWRP flash the build and tap restart to system when finished.

my device sony x compact is stuck on twrp logo, is there any solution to fix it?
Note: before stuck on twrp logo, i want to downgrade to A12. but after I entered recovery by (power + vol-) the device was stuck at the twrp logo

Tri Akbar Fitriana said:
my device sony x compact is stuck on twrp logo, is there any solution to fix it?
Note: before stuck on twrp logo, i want to downgrade to A12. but after I entered recovery by (power + vol-) the device was stuck at the twrp logo
Click to expand...
Click to collapse
The same here. The solution for me: i flash stock Rom then Twrp and then los20. After flash los20 twrp stuck on logo, but i can use Los20. Many thanks for los20. Its a great rom.

Asta01 said:
The same here. The solution for me: i flash stock Rom then Twrp and then los20. After flash los20 twrp stuck on logo, but i can use Los20. Many thanks for los20. Its a great rom.
Click to expand...
Click to collapse
if I flash it to stockrom, does it need a TA file? because my TA file is missing.

Tri Akbar Fitriana said:
if I flash it to stockrom, does it need a TA file? because my TA file is missing.
Click to expand...
Click to collapse
I flash Stockrom with flashtool. I dont need TA file.

Tri Akbar Fitriana said:
if I flash it to stockrom, does it need a TA file? because my TA file is missing.
Click to expand...
Click to collapse
No.
Try lineage recovery it works for me, with twrp i get black screen

Chippa_a said:
Moreover, to work with new encryption you need a recovery with appropriate support.
Click to expand...
Click to collapse
For those who have issues with recovery after this ROM.
Please make sure you have installed latest unofficial version (3.7.0_12+) with support for the new FBE encryption method, as stated in OP. Older versions cannot decrypt data encrypted with this method!

Chippa_a said:
For those who have issues with recovery after this ROM.
Please make sure you have installed latest unofficial version (3.7.0_12+) with support for the new FBE encryption method, as stated in OP. Older versions cannot decrypt data encrypted with this method!
Click to expand...
Click to collapse
Thanks,with twrp 3.7.0_12 is twrp working.

Thank you chippa _a. The rom is amazing. I haven't found any bugs so far, and it's incredibly fast. A new life for the Xperia x compact. Thanks alot.

Thanks a lot for this rom! I running it for a few days and no bugs so far
I'm wondering which cam app is the best to use?
And I have one app which doesn't run because my phone is rooted, is there a solution for that?

SietZ said:
Thanks a lot for this rom! I running it for a few days and no bugs so far
I'm wondering which cam app is the best to use?
And I have one app which doesn't run because NY phone is rooted, is there a solution for that?
Click to expand...
Click to collapse
For me is Google cam port "MGC_8.2.204_Parrot043_V1" working perfect.

Database Info

welcome