[ROM][8.1.0]LineageOS-15.1[Joan][Treblelized][Unofficial] - LG V30 ROMs, Kernels, Recoveries, & Other Developm

[ROM][8.1.0]LineageOS-15.1[Joan][Treblelized][Unofficial] - LG V30 ROMs, Kernels, Recoveries, & Other Developm

{
"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 8.0 (Oreo), 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. You can also view the Changelog for a full list of changes & features.
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.
*/
What's working :
RIL (Calls, SMS, Data)
Fingerprint
Wi-Fi
Bluetooth
Camera
Video Recording
Video Playback
Audio
Sensors
Hotspot
Flash
GPS
What's not working :
Boot doesnt work all the time (just dont reboot the phone, i guess)
GSIs (Generic System Images) work fine though for some reason
DAC(?)
Selinux is permissive
Exfat (when enabled makes system slow down, and eventually crash)
Where are the features?
LineageOS is in development process so don't complain about xyz features missing.
Instructions :
Download the build
If you dont have a vendor partition yet, create one GUIDE
Reboot to recovery
Flash the latest build
Reboot
Downloads :
Here
H932 Build
Sources:
Device Tree: h930 + joan-common
Kernel: msm8998
Vendor: lge
lineage-15.1-treble branch
XDA:DevDB Information
LineageOS 15.1 - Treble, ROM for the LG V30
Contributors
SGCMarkus, rashed97
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: Oreo
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2018-05-13
Created 2018-05-13
Last Updated 2018-10-03

Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
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 dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Changelogs
Release 13.05.2018
- Initial release
Release 16.05.2018
- Fixed boot (temporarily disabled sdcardfs)
Release 18.05.2018
-enabled sdcardfs again (fixed, took the OP5(T) driver, not the broken LG one)
-reduces system image size by around 10MB, so our friends who repartitioned have a bit more room for that, same for vendor
Release 21.05.2018
-updated to latest LineageOS sources
-enabled burnin protection in overlays
-re-enabled exfat driver in the kernel (may cause issues for some sdcards, may need to reformat them, as they could "load" forever and make the system crash eventually)
-cherry-picked https://review.lineageos.org/c/Linea..._base/+/210106 (should fix acccess to wide angle camera on apps that support it)
Release 01.06.2018
- Updated Autobrightness from Taimen (Pixel 2 XL), as it has the same panel
- Enabled the AoD option (you might have to unlock the phone twice or so though, LOS source is currently broken, nothing i can do)
- Updated to latest LOS sources
- Nuked lge/common and moved gestures into our tree
Release 22.07.2018
- Updated blobs to H930 V20R
- fixed vibration becoming dull after a while
- all other past changes from normal LOS since last update here
- updated source
Release 29.08.2018
- Updated Source
- Updated blobs to H930 21a
- Vibration motor ready for P GSIs

Frequently Asked Questions:
Q. Can this ROM be flashed through TWRP?
A. Yes, proceed with the latest TWRP image
Q. Sounds good. How can I contribute to project?
A. Test the build as much as you can and report bugs which can be reproduced with exact steps and are not random.
Q. How to disable "Apps running in background" dialog?
A. When you see the dialog, long press on it and select "Settings". From there, you'll have a toggle to disable it.
Q. Does this work on the US998?
A. Hasn't been tested yet. Try it out and report (but make a backup first as always).

Hi Markus!another thanks for you work!
In the next days i'll try one of your rom (probably the treble one after repartitioning).
I've a doubt...the reboot problem happen only with standard los15.1 or also with the gsi of this thread?
Do you think to release an gsi of crdroid also? I would prefer to test a rom with more customization option!

okaiuz said:
Hi Markus!another thanks for you work!
In the next days i'll try one of your rom (probably the treble one after repartitioning).
I've a doubt...the reboot problem happen only with standard los15.1 or also with the gsi of this thread?
Do you think to release an gsi of crdroid also? I would prefer to test a rom with more customization option!
Click to expand...
Click to collapse
The reboot problems only occur with the 2 LineageOS builds, not with GSIs (or i was just really extremly lucky, but i doubt that).
On LOS i have a ~20% boot chance (did once 35 boot tries after another...), and on GSIs it boot always like 6 or 7 times after another. Suppose it works there, really unlikely i was that lucky lol
The GSI of LOS by phhuson also works btw (just no double tap 2 wake).
I would actually love to make way more ROMs.... I even had a CrDroid test build once (to check if its only LOS with that problem), but sadly im out of space now.... dont have more space than for LOS :/

Ok markus,
One more question: the bootloop problems happen even with phhuson's gsi of los and rr?(if you have tested).
I will try your tremble enabled los as soon as possible and let you know!

okaiuz said:
Ok markus,
One more question: the bootloop problems happen even with phhuson's gsi of los and rr?(if you have tested).
I will try your tremble enabled los as soon as possible and let you know!
Click to expand...
Click to collapse
phhusons LOS and RR worked fine for me the last time i tried them ... Has to be something in my device tree... somewhere... hiding... that doesnt land on /vendor i guess....
Tried so much already.... dont wanna count the number of builds and logs i made over the past.... ehh, 1.5 months by now lol (with not really progress btw, except fixing vibrator and nfc, treblelizing was a work of 2 or 3 days tbh, and only did that becuase i was stuck on the boot issue, and wanted to know if it happens with GSIs too or not)

SGCMarkus said:
phhusons LOS and RR worked fine for me the last time i tried them ... Has to be something in my device tree... somewhere... hiding... that doesnt land on /vendor i guess....
Tried so much already.... dont wanna count the number of builds and logs i made over the past.... ehh, 1.5 months by now lol (with not really progress btw, except fixing vibrator and nfc, treblelizing was a work of 2 or 3 days tbh, and only did that becuase i was stuck on the boot issue, and wanted to know if it happens with GSIs too or not)
Click to expand...
Click to collapse
i have to thank you again for you work!
Thursday i'll try to partition my v30+ and try your treblelized los!
i give a chance even to phh los, aosp and rr!
i 'll yo know my experience, hoping that you can fix the boot problem!
Regards!

i am following (mostly reading) the development here very closely. reading because i dont have that much time atm for regular flashing and the problems that come with it sometimes. and i need the phone as a daily driver
i have to say thank you for your work here. Treble support and LOS 15.1! this is absolutely awesome.
one thing that was mentioned some times before is the DAC on LOS. That is on big reason why i bought the phone. If this could be possible i would switch to LOS without thinking. i hope it will soon.
Thanks again for that and keep up the good work.

donky kong 017 said:
i am following (mostly reading) the development here very closely. reading because i dont have that much time atm for regular flashing and the problems that come with it sometimes. and i need the phone as a daily driver
i have to say thank you for your work here. Treble support and LOS 15.1! this is absolutely awesome.
one thing that was mentioned some times before is the DAC on LOS. That is on big reason why i bought the phone. If this could be possible i would switch to LOS without thinking. i hope it will soon.
Thanks again for that and keep up the good work.
Click to expand...
Click to collapse
Use Viper4Android and the predicament is solved.

Nikola Jovanovic said:
Use Viper4Android and the predicament is solved.
Click to expand...
Click to collapse
does viper use the quad DAC. AFAIK no. ATM i use the V30 Quad DAC and Ainur Sauron

As it also counts for this, i will simply refer to my post in the other LOS thread
https://forum.xda-developers.com/showpost.php?p=76536335&postcount=20

you're the best!
tnx to phh also!

how bad can you **** up the "treblelize" thing?
What method do you prefer? Treble or no treble on the V30?

elba96 said:
how bad can you **** up the "treblelize" thing?
What method do you prefer? Treble or no treble on the V30?
Click to expand...
Click to collapse
Both are the same basically (same set of features). If you treblelize it, ofcourse making backups of everything like you always should do (also of your GPT, if something goes wrong, you can simply restore that again), not that much can go wrong actually.
Could also write a complete manual guide (how i did it actually, but that needs a PC/VirtualMachine with a Linux installed), but the script should really just do fine
With the treblelized version, you can also try out GSIs (made by phhusson), they work really nice, but you wont have things like double tap 2 wake for example (didnt try if you can enable it via kernel aduitor yet though)
Its totally your choice ^^
PS: build with fixed boot should be up now here too

SGCMarkus said:
Both are the same basically (same set of features). If you treblelize it, ofcourse making backups of everything like you always should do (also of your GPT, if something goes wrong, you can simply restore that again), not that much can go wrong actually.
Could also write a complete manual guide (how i did it actually, but that needs a PC/VirtualMachine with a Linux installed), but the script should really just do fine
With the treblelized version, you can also try out GSIs (made by phhusson), they work really nice, but you wont have things like double tap 2 wake for example (didnt try if you can enable it via kernel aduitor yet though)
Its totally your choice ^^
PS: build with fixed boot should be up now here too
Click to expand...
Click to collapse
Thanks for the fast reply!
A guide from you would actually really help
I have a VM with Linux so that would be very convinient
would you suggest your ROM for daily use? I can live without the Quad DAC, but i really like the battery life of the rooted stock ROM.
Are there still sever bugs?

maybe a stupid question, but if i use your script for repartition and create vendor partition can i flash the non treblelized version of your rom?
And if this is possible can i mantain my data partition without wipe it?
ambient display is working on los?

Hmm I have a problem with installing the LOS roms.
I have repartioned my device according to your guide (at least I think I have).
But somehow I can't install neither of the roms, with or without treble. At first the install seams fine but when it is at the end I get "Updater error: 7" or something similar and a message about not beeing able to mount /system (mounting system works after wiping it again).
Installing stock roms works fine.
You have a clue what could cause the problem?
I use Oreo firmware and your oreo twrp.

okaiuz said:
maybe a stupid question, but if i use your script for repartition and create vendor partition can i flash the non treblelized version of your rom?
And if this is possible can i mantain my data partition without wipe it?
ambient display is working on los?
Click to expand...
Click to collapse
Yes, you can still use the non treblelized version
Still working on adding features though, fixing major bugs first ^^
Doblix said:
Hmm I have a problem with installing the LOS roms.
I have repartioned my device according to your guide (at least I think I have).
But somehow I can't install neither of the roms, with or without treble. At first the install seams fine but when it is at the end I get "Updater error: 7" or something similar and a message about not beeing able to mount /system (mounting system works after wiping it again).
Installing stock roms works fine.
You have a clue what could cause the problem?
I use Oreo firmware and your oreo twrp.
Click to expand...
Click to collapse
Can you send me the /tmp/recovery.log (copy it to your sdcard AFTER you tried to install, and no reboot inbetween), either adb pull /tmp/sdcard via pc, or TWRP has an option to copy it i believe.
Didnt have this error myself
Also check in your TWRP, either via its terminal, or adb shell:
ls /dev/block/bootdevice/by-name/
if theres "vendor" listed.
elba96 said:
Thanks for the fast reply!
A guide from you would actually really help
I have a VM with Linux so that would be very convinient
would you suggest your ROM for daily use? I can live without the Quad DAC, but i really like the battery life of the rooted stock ROM.
Are there still sever bugs?
Click to expand...
Click to collapse
My testers say its ready for daily usage
Couldnt test for battery life yet myself. Didnt have the time to setup everything a new... University life is tough

SGCMarkus said:
Can you send me the /tmp/recovery.log (copy it to your sdcard AFTER you tried to install, and no reboot inbetween), either adb pull /tmp/sdcard via pc, or TWRP has an option to copy it i believe.
Didnt have this error myself
Also check in your TWRP, either via its terminal, or adb shell:
ls /dev/block/bootdevice/by-name/
if theres "vendor" listed.
Click to expand...
Click to collapse
Yes vendor is listed there and I could also format it. I am at university right now and reverted to stock to be able to use it (which can be flashed fine btw.), I will see when I find the time to flash again and post the log here then.

Related

[ROM][H815][6.0|MM][UNOFFICIAL] Lineage OS 13.0 for LG G4

FAQ
1. Q: Encryption is not possible?
A: if the GUI for encrypting the device is not working:
Its highly recommended to backup all your data including the internal storage (I recommend FlashFire or / and Titanium)
Flash my screenlock fix (search here at XDA) in TWRP.
Reboot to android.
ensure that you met all usual requirements (battery, screen lock set) and then open a terminal or adb shell. Type:
vdc cryptfs enablecrypto inplace pin 1234
Replace 1234 with your desired pin ofc.
sfX

Reserved

Hi steadfasterX !
Thanks for keeping this alive ! I'm still on an old 13.0 version, it runs fine ATM.
steadfasterX said:
the kernel has security bugs which need to be addressed
Click to expand...
Click to collapse
Could you please be more precise on this ?
Where those bugs also in genesixx build, or are they specific to your build ?
Are these bugs LOS specific, or are they AOSP related ?
Thanks !

thewild said:
Hi steadfasterX !
Thanks for keeping this alive ! I'm still on an old 13.0 version, it runs fine ATM.
Could you please be more precise on this ?
Where those bugs also in genesixx build, or are they specific to your build ?
Are these bugs LOS specific, or are they AOSP related ?
Thanks !
Click to expand...
Click to collapse
its the same source then the official build (and so genessix) used so it should work the same way but as my device is broken atm and I await repair I cannot test it..
Last time I checked the security patches in my build got increased to July 2017 where the latest official ones had June..
so afaik there should be no critical issues in Android but the kernel is last time updated in May 2016 (should be the same for genessix builds).
My plan is maybe to integrate the Llama kernel and backport fixes from the 14.x tree.
don't expect that this happen in the near future (we can hope though) because atm I'm quite busy with my unofficial unlock stuff.
.

OK I'll keep an eye on this thread then.
Good luck !

Any tester reports?

Netsab said:
Any tester reports?
Click to expand...
Click to collapse
Yes.. I use that ROM with my unofficial unlock testers. Atm I cannot test cell service but it boots up fine, WiFi, cam etc works fine.
sfX
Sent from my LG-H815 using XDA Labs

Hi,
I can't make encryption work.
Can you write a procedure to use it with this ROM, please?
What I did:
- Install TWRP latest version
- Install latest nightly
- Remove gate keeper (using this)
- Launch encryption
What happened:
- Device reboot, display a green android on a black screen for a second, then reboot again try to boot on LineageOS but it froze after maybe a minute.
- I put off the battery and reboot the phone, that boot normally (data not encrypted but not corrupted either).
Thanks by advance

zeduck said:
Hi,
I can't make encryption work.
Can you write a procedure to use it with this ROM, please?
What I did:
- Install TWRP latest version
- Install latest nightly
- Remove gate keeper (using this)
- Launch encryption
What happened:
- Device reboot, display a green android on a black screen for a second, then reboot again try to boot on LineageOS but it froze after maybe a minute.
- I put off the battery and reboot the phone, that boot normally (data not encrypted but not corrupted either).
Thanks by advance
Click to expand...
Click to collapse
thx for testing..
yea I rem that there was a "trick" .. Could you try this build pls: http://droid.binbash.it:58885/h815/lineage-13.0-20170912-UNOFFICIAL-h815.zip
It includes an insecure kernel which will allow to debug.
Factory Reset in TWRP
Flash in TWRP
Boot Android
Enable encryption
when it reboots open a terminal and type (linux or FWUL): while true; do adb logcat ;done
on windows ensure that once the logcat aborts that you restart it immediately again!! and use just adb logcat
if using windows or linux: ensure the terminal buffer is big enough bc thats a a lot to handle.. (go into the settings of the cmd or terminal and set it to a very high value. e.g. 5000000)
let it bootloop and boot into Android again (logcat should run all the time)
CTRL+C when its completed with the above
copy & paste the whole stuff in a text file and attach it here
sfX

Are there any special modifications that would make it work?
Because I use this ROM as a daily driver and I would appreciate not to backup and reflash several times
If not, I will take the time to test this weekend.

zeduck said:
Are there any special modifications that would make it work?
Because I use this ROM as a daily driver and I would appreciate not to backup and reflash several times
If not, I will take the time to test this weekend.
Click to expand...
Click to collapse
without logs I cannot say anything for sure...
It may can be solved by just typing the encrypt command over adb or it requires to modify the ROM..
If you like you can try the following but keep in mind that having a complete Backup is a good idea always and when I say complete I mean including internal storage which is not be backuped by TWRP!! Use e.g FlashFire app to accomplish this. I would take a TWRP backup for all (use my latest beta!!!) and then FlashFire to backup internal storage.
Encryption often fails to a wrong formatted data partition so this can be a reason as well.
Try this:
Backup as described above
In TWRP select wipe - advanced - press "Format data" button to format the data partition
Boot android
set a pin or password for the lock screen!
Encrypt
If succeeded restore backup with FlashFire
As always there is a risk and it requires some time so I would not recommend to do this on a busy day.. as you say at the weekend fe.
Then we can try to use the adb commands and if that doesn't work as well the logcat..
sfX
Sent from my LG-H815 using XDA Labs

Hi !
I gave a try with lineage-13.0-20170918-UNOFFICIAL-h815.zip that I dirty-flashed over my previous lineage-13.0-20170204-UNOFFICIAL-h815 version.
Everything went fine (I had to replace the su zip/app though), except that satellite location would not work (network location was fine) : I kept getting
Code:
QCOM PowerHAL : Failed to acquire lock.
in logcat.
I'll give another try with the latest lineage-13.0-20170927-UNOFFICIAL-h815.zip.
If that fails too, I guess I'll have to clean-flash it then.
EDIT :
Bad news : after a clean flash, I keep getting
Code:
QCOM PowerHAL : Failed to acquire lock.
in logcat.

No GPS?! Kind of annoying bug... I'm still in 20170608 build and that news don't make me want to updated. I use GPS everyday, so this is very annoying

Netsab said:
No GPS?! Kind of annoying bug... I'm still in 20170608 build and that news don't make me want to updated. I use GPS everyday, so this is very annoying
Click to expand...
Click to collapse
After flashing several successive versions of that ROM, I discovered that version lineage-13.0-20170813-UNOFFICIAL-h815.zip seems to be the last one with satellite location working fine.
Starting from lineage-13.0-20170814-UNOFFICIAL-h815.zip, satellite location stops working. I guess something is broken in that build.
@steadfasterX :
Can you look and see what's happened with 20170814 ? Thanks !
@Netsab :
You can safely upgrade to 20170813.

breversa said:
After flashing several successive versions of that ROM, I discovered that version lineage-13.0-20170813-UNOFFICIAL-h815.zip seems to be the last one with satellite location working fine.
Starting from lineage-13.0-20170814-UNOFFICIAL-h815.zip, satellite location stops working. I guess something is broken in that build.
@steadfasterX :
Can you look and see what's happened with 20170814 ? Thanks !
@Netsab :
You can safely upgrade to 20170813.
Click to expand...
Click to collapse
Thanks you, I'll try.

breversa said:
After flashing several successive versions of that ROM, I discovered that version lineage-13.0-20170813-UNOFFICIAL-h815.zip seems to be the last one with satellite location working fine.
Starting from lineage-13.0-20170814-UNOFFICIAL-h815.zip, satellite location stops working. I guess something is broken in that build.
@steadfasterX :
Can you look and see what's happened with 20170814 ? Thanks !
@Netsab :
You can safely upgrade to 20170813.
Click to expand...
Click to collapse
thanks for your report. btw a dmesg is very helpful in these cases but the above should be fixed on next build.
next build will also have all proprietary stuff upgraded to v20p.
sfX
EDIT
new build is up
.

Hey sfX,
When trying to dirty-flash 20170930 over 20170813, the phone gets stuck on the boot animation (for over 30 minutes).
I did not try to clean-flash it though ; I thought I'd let you know first.

Sir SteadfasterX!
I use Unofficial 13.0-20170625-UNOFFICIAL-h815 as a daily driver and it never crashed once. I will try yours in near future, beginning with a dirty flash (but with a backup in case).
My question is, do the Bluetooth APT-X include in this rom?
One of my other phones Sony Z5 (modded stock) includes from factory an APT-X notifier, whenever it connects to a Bluetooth with APT-X I get a toast message that the device using "BLUETOOTH apt-x".
I see in Nougat 7 that it is possible to check in "developer mode" which Bluetooth protocol that currently is in use.
[Request] It would be nice if you could pick Bluetooth APT-X drivers/codec from above version of LinageOS14
Thank you very much!
I have attached the spoken AptxNotifier.APK from Sony z5 Marshmallow

datorprofessor said:
Sir SteadfasterX!
I use Unofficial 13.0-20170625-UNOFFICAIL-h815 as a daily driver and it never crashed once. I will try yours in near future, beginning with a dirty flash (but with a backup in case).
My question is, do the Bluetooth APT-X include in this rom?
One of my other phones Sony Z5 (modded stock) includes from factory an APT-X notifier, whenever it connects to a Bluetooth with APT-X I get a toast message that the device using "BLUETOOTH apt-x".
I see in Nougat 7 that it is possible to check in "developer mode" which Bluetooth protocol that currently is in use.
[Request] It would be nice if you could pick Bluetooth APT-X drivers/codec from above version of LinageOS14
Thank you very much!
I have attached the spoken AptxNotifier.APK from Sony z5 Marshmallow
Click to expand...
Click to collapse
Better wait until I fixed the current nightlies..
nice app btw. when all is fixed i may take a look into it
Sent from my LG-H815 using XDA Labs

[ROM][UNOFFICIAL][Android 11] LineageOS 18.1 [joyeuse/miatol][22/01/21]

{
"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 18.1 is a free, community built, aftermarket firmware distribution of Android 11, 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. You can also view the Changelog for a full list of changes & features.
We have progressed to LineageOS 18.1
Flash instructions :
Use latest pbr recovery for miatol, supports decryption - beta available here, https://pitchblackrecovery.com/joyeuse/.
DO NOT - Wipe data!, ONLY FORMAT, otherwise you may hose the phone.
There is a way to fix this without the fastboot factory clean, flash and lock with the official Xiaomi tool, which was forcing you to clean and lock... now available here: https://github.com/Szaki/XiaomiADBFastbootTools
If you hose the phone, use this tool - you need to install JRE though, as the tool is Java base. Put your phone is fastboot, use the tool to download the latest global rom (or whichever). Then go to where its downloaded, extract the .xy/tar file, then go back into the tool and under "image" select the folder INSIDE the folder you just extracted, then select "clean install" and install it. This will flash the majority of imgs but will error out at the end and be unable to create the "user data" partition.
That's okay, because all of the partitions will be setup again, and you can flash any rom you want again. So when its done, and still in fastboot, fastboot flash recovery recovery.img (recovery.img being the latest joyeuse pbr recovery, you renamed to recovery.img and were in that folder in the command prompt, so it will flash that recovery) or use the tool to select that recovery and it will flash it for you and reboot into for you if you like.
(Do this step last, after Magisk, if you want to unencrypt, no worries if you don't unencrypt - PBR recovery will decrypt your data ON THE SECOND TRY OF ENTERING YOUR SCREENLOCK PIN NUMBER...), the new PBR Miatol Beta 10/14/20, fixes this issue, it is now decrypted on the first entry of the phone's lockscreen PIN. Then flash disable_dm-verity_forceencrypt.zip available here for those who want decrypted data partition: https://zackptg5.com/android.php#disverfe and other places as well.
If you are encrypted and decide to unencrypt later, you will need to flash the disable_dm-verity_forceencrypt.zip in miatol recovery, then format data. Store roms, gapps, recoveries (just in case), disable_dm-verity, magisk install and uninstall and all that stuff on the SD card, so you can use them in PBR after you format DATA (the first step after installing PBR miatol recovery), just FYI. Then do the following:
Flash ROM
Flash OpenGAPPS for android 11 nano
Boot into android, make sure its working and install Magisk Manager 8.0.7, then reboot into recovery and install Magisk 21.4 (in recovery, I did not need to extract the boot.img and patch in Magisk Manager, and reboot into recovery to flash the patched boot.img, but your results may be different): https://github.com/topjohnwu/Magisk/releases. If you want to unencrypt (no guarantees its permanent though) you need to format data, THEN FLASH MAGISK, then flash disable_dm-verity (always the last step)- I usually wipe dalvik and cache too.
USE LATEST MIATOL PBR RECOVERY, PLEASE.
SD card issues resolved with the implementation of the EXFat android driver.
Source Code: https://github.com/LineageOS
Kernel Source: https://github.com/Redmi-SM6250 or Stock kernel from Miui
Apologies for the lack of updates, was diagnosed with stage 4 metastatic cancer and this project was not on my priority list anymore...
Update 28/1/21:
Release notes:
LineageOS
Device: Unified (Miatoll)
Developers: ScaryMen1325 & Loptr4
ROM Version: 18.1
Android Version: Android 11
Build date: 22/01/2021
Status: UNOFFICIAL
Changelog:
• Fixed power related issues
• Added useful apps (thanks to Dev: Emulond for that)
• Other fixes and performance improvements
Notes:
• It's 2nd test version, if you found bugs, give log.
• Using loki kernel by default, haven't tested custom kernel.
Download here:
https://drive.google.com/file/d/1M5-cRBfrRdBdNYGzy5G9bOa1Ncf5JkE4/view?usp=sharing
Please note this is a unified release, you should do a clean install unless you're coming from a unified ROM alreadyl.
Will keep you more regularly updated now that I'm out of the hospital....

Perfect will try tonight

Belpek said:
Perfect will try tonight
Click to expand...
Click to collapse
Have you tried it?
How is it? Good for daily?

There are so many Joyeuse LineageOS ROMs I don't even know where to start.

i don't see you mentioned mobile network in bugs section; does it work? i'll try this rom in a couple hours

Tell me please. If phone will be locked with black screen and i say "ok google". Will it work? Or it will work only if screen is unlocked?

sorry if its not much, since i can't do much on this rom. flashed nikogapps, google sign-in succeded but it seems that i cant install anything from play store.
(dumb me forgot to screenshot, it only says "something went wrong" when i try to install an app from play store)
about ok google from lockscreen/screen off, i tried it, also not working. can't confirm about volte since volte still relatively new here and hasn't developed that much.

Why nikgapps? Open gapps nano is recommended.
Sent from my Redmi Note 9 Pro using Tapatalk

Flash it and using it by now, so far so good, sometimes it gets a little freeze but nothing serious, miracast reboots phone so dunno if this is a bug or not, proximity sensor is another one cuz while I was in speaking with my pal screen was on all the time and my ear activated bluetooth and DND
Have nothing to talk about VoLTE cuz in my country is not available.
ANX modules left my phone in bootloop so instead I went for GCam. Flash unofficial opengapps nano and make sure to use Wi-Fi to complete the first run.
Magisk canary works so it can be rooted.
Keep the hard work!
*Sorry if I made some writing mistakes, english is not my native language. Cheers!!

Tried flashing the latest build (02.10.20) using the latest TWRP from the thread you linked but I get the "can't install package over new build" error. Is it required to come from stock miui?

gigahurts said:
...
Newer Build:
https://mega.nz/file/PlkgiSzS#C_tIspgbtGDrweztQ83lADHyEQf4dTkIUiSAqgjVAFk
NOTE: You should be on 11.0.7.0 QJZMIXM (EU) Global firmware for this build. Also, I have a newer build, but its not ready for primetime and has issues with SMS and Call Log enabling permissions.
Oh, and BTW, if you hose your ROM/Phone, just flash vbmeta.img in fastboot to avoid using the factory fastboot img flash, otherwise you many need to wait another 7 days to unlock the bootloader.
...
The dev for this build is: @wight554, all thanks and credit go to him, he is awesome, and I, for one, seriously appreciate this ROM as it works very well for me. It is so snappy and smooth, with a super fast boot time, no reboots and generally pretty frickin AWESOME!
...
Click to expand...
Click to collapse
First of all, thank you guys @gigahurts & @wight554 very much for working on supporting this device :good::good:
Could you pretty please confirm that you intend to continue working on this and maintain this device? I am planning to buy two joyeuse devices for daily usage and I would like to be at least partially sure I can run LineageOS on them. Also do you think the current known issues will be possible to resolve in the near-ish future? :fingers-crossed: Thanks for your reply in advance. All the best.

Swiftor said:
First of all, thank you guys @gigahurts & @wight554 very much for working on supporting this device :good::good:
Could you pretty please confirm that you intend to continue working on this and maintain this device? I am planning to buy two joyeuse devices for daily usage and I would like to be at least partially sure I can run LineageOS on them. Also do you think the current known issues will be possible to resolve in the near-ish future? :fingers-crossed: Thanks for your reply in advance. All the best.
Click to expand...
Click to collapse
hey Swiftor,
We will continue to work on this rom. LineageOS has been around a long time, development has spread across so many devices, however, the hardware of many devices is very similar, so support will continue. The last Redmi Note 8 pro, had a mediatek SOC, and made development difficult until MIUI decided to release its source. The snapdragon platform is very mature and is more easily and readily available to develop roms for. Redmi Note 10 pro has been released in India, and has a slightly better processor 765g vs 730g, but the kernel and hardware are very similar, so I development for this phone and the Note 10 pro should parallel and continue. We are working on submitting an official 18.0 release, but have to have all hardware (and software) fully functional and as close to zero bugs as possible. I predict development to continue as long as Xiaomi continues to release new MIUI roms for this device (and they continue to release roms for phones much, much older than this).
I have updated the first post with a newer release. Let me know if you have any issues and I will try to help.
Thanks for the props too

does magisk 21 work on the latest build? really excited for android 11

So this will not be compatible with curtana devices?

Thanks to all developers for this rom. Installed on Curtana with Magisk canary, I had to use Magisk props to pass safetynet. All seems to be working ok.??

everything is working perfectly and its showing charging rapidly , it was on 88% and showing 10 minutes until full
everything is completely smooth gonna keep it for my daily use

Bantryred said:
Thanks to all developers for this rom. Installed on Curtana with Magisk canary, I had to use Magisk props to pass safetynet. All seems to be working ok.
Click to expand...
Click to collapse
hi! wich props do u use for fingerprint? i can't pass safety on my joyeuse

there're few thing that you need to fix @gigahurts
1) you putting wrong kernel source. its should be this link
2) why would you mirror it when you can get it in his sourceforge

Why is today's build 590MB while all others are 1.1GB?

pwnaz said:
hi! wich props do u use for fingerprint? i can't pass safety on my joyeuse
Click to expand...
Click to collapse
Sorry for the delay, Im on Curtana so dont know if it makes a difference, but I used no. 16 - mi 10 Global(11)
I also had to hide Magisk Manager

Development [ROM][UNOFFICIAL][Q/A10][SM-J530F] /e/ OS for Samsung J5 2017 (j5y17lte) - BYE Google, HELLO Privacy!

{
"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"
}
brought to you by the
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.
*/
About /e/
/e/ is an a mobile ecosystem (ROM + onlines services) that:
is open source
is pro-privacy
is compatible with most existing Android applications
cares about usability
is as far as possible freed from shackles by Google and OEMs
already exists!
It’s the alternative to the Apple/Google duopoly on the smartphone.
... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
a set of sorted and improved default open source applications
various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.
Features
Based on the stable Lineage OS
microG fully pre-installed with Signature Spoofing in restricted mode!
All features described on the /e/ page: What is e
All features and fixes of LineageOS
My builds come with full OTA update support
... you know that thing which informs you that a new update is there and where you just click to download + install
Difference from pure /e/
UNOFFICIAL builds (having the tag UNOFFICIALin ROM filename):
There are no differences. its pure /e/. just an unofficial build (this ROM is currently still in progress to get approved by /e/ for official builds)
Note (2022-09-09):
This project was in the transition to become official which got stuck due to build issues on /e/ site. Because of that I stopped building UNOFFICIAL as they made no sense when my code becomes official and just providing CUSTOM builds atm. As the process to become official takes longer then expected I will likely build UNOFFICIAL again in the (hopefully) near future.
Note (2022-11-22):
All open issues have been fixed, first official test builds finally work as they should. the current progress becoming official can be tracked here
I won't build a new UNOFFICIAL release atm in the hope this process will be finished soon
the camera will have a stretched preview as it is pure /e/ and so my modification (see CUSTOM) won't apply there.
You can always install the fixed cam version from here (opencamera_sfX_j5_fixPreview.apk) though and install in parallel to the stock one (the reason why I changed the package id for that modded one to "foundation.e.camera.j5").
CUSTOM builds (having the tag CUSTOM in ROM filename):
The following apps are included: click
A note about Google Play Store / Phonesky: Phonesky is THE original Google Play store - "just" modified that it works without the Google service dependencies. It is still the original google play store though.
Besides the fact this Play store works on the microG backend it allows to use paid apps - which is something some users requested.
Google Play Store / Phonesky can be easily disabled in the App settings screen (must be re-done after every upgrade though).
The stretched camera preview (photo & video recording) is "fixed" (since v1.5):
Unfortunately this works for the /e/ STOCK camera app ONLY so if you install any other camera app you will have that stretched preview there again
For those being curious: the code changes can be found here always.
the app package id has changed to "foundation.e.camera.j5" to allow a parallel install with the stock cam version (on OFFICIAL and/or UNOFFICIAL builds)
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
When your current STOCK firmware or the latest you had flashed is not PIE (Android 9) then flash the following STOCK version: J530FXXS7CTF1 (pie)
selinux: permissive (will be set to enforcing once I got some user feedback if my build working as stable for others as for me)
Camera preview is "stretched". This affects the preview only, pictures taken are fine. sorry there is no known way to solve that afaik.
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP build.
This ROM has been tested with stock firmware J530FXXS7CTF1 . If you use an older one switch to this first. If you have a newer one things might not work for you (like cam etc)
Do a full (i.e. Nandroid) backup before doing anything!
Installation
Full clean install as described here (FAQ #2) is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash /e/
Optional (if you want root): Flash Magisk
Flashing OpenGapps ????? NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
Boot it (will take a bit on first boot!!! be patient!)
Enjoy the most easy way to have a privacy focused and google-free phone!
Download
Get your builds from my leech server (new installs or re-installs)
https://leech.binbash.rocks:8008/e-os/a10/j5y17lte/
If you have a previous version of my(!) /e/ Q installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have built-in OTA support!)
Note:
Builds are updated as soon as possible. There is no build cycle.
Information pertaining to your device is displayed accordingly.
The current build is the latest for your device.
Changelogs
search results from this thread: click
Support
Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
nailyk
Astrako, wth.. you did an AWESOME job for this SoC!
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
The Exynos7870 Team
and more..
Sources
build manifest
XDA:DevDB Information
j5y17lte_eos-q_unofficial, ROM for the Samsung Galaxy J5
Contributors
steadfasterX, nailyk, Astrako for ALL Q porting stuff!!! and: ananjaser1211,DarkLord1731,Exynos7870 Team (github)
Source Code: https://gitlab.e.foundation/e
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: only tested on PIE bootloader - so upgrade if you are on Oreo or older
Based On: Lineage OS
Version Information
Status: Stable
Created 2020-10-01

.
Frequently Asked Questions (FAQ)
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
if you have an audio issue follow FAQ #6 instead.
Often selinux can cause issues so try that at very first:
Code:
if you have magisk installed:
adb shell
su
setenforce permissive
When " usb debugging root" is enabled in developer settings:
adb root
adb shell
setenforce permissive
Try again and if the issue is gone when in permissive mode: provide me a logcat as described here -> on step 3 I need the SELINUX log (option D)
If your issue is not solved with selinux permissive click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
Yes. With your help! What you can do? Test and report EVEN SUCCESS in this thread.
Q #4: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #5: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audio issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #6: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?
First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:
In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.
The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.
Q #7: What is the difference between CUSTOM and UNOFFICIAL builds?
UNOFFICIAL is like pure /e/ - untouched. This is the base for OFFICIAL builds (coming soon)
CUSTOM:
removed: /e/ Apps (read here why)
added: AuroraStore, F-Droid, F-Droid xtra repos (manual enable required), DNS66 (adblock w/o root), Omega Launcher (as alternative Launcher)
Q #8: Banking not working? Your app <fill-in-appname> does not work because root is detected?
So you wanna install and use a banking app or any other which is trying to detect root? The following might help you out:
[ROM][UNOFFICIAL|CUSTOM|LOCKEDBL][Q/A10][hotdog] /e/ OS for OnePlus 7T Pro - BYE Google, HELLO privacy and security (LOCK your BOOTLOADER)!
brought to you by the /* * 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...
forum.xda-developers.com
--> See FAQ 8 there!Yes that FAQ was written for a oneplus device but is generic for every device and model.
.-

Reserved

Excellent work Stead, and glad to see you here!

Gooooood Work!
Will love to see it on other 7870s as well....

Astrako said:
Excellent work Stead, and glad to see you here!
Click to expand...
Click to collapse
Without your work it would had take several (more) weeks to finish , so that thanks goes back to you dude
Sent from my OnePlus 7T Pro using XDA Labs

amazing work sir
it works perfectly so far
sad cuz i cant flash other kernels but hey its smooth af even with stock kernel
keep up the good work

Thanks a lot, it works fine for me - except for the GPS...

tiboleplubo said:
Thanks a lot, it works fine for me - except for the GPS...
Click to expand...
Click to collapse
What was the last stock version you flashed ? Also: share a screenshot of your baseband version in android settings.
Sent from my OnePlus 7T Pro using XDA Labs

steadfasterX said:
What was the last stock version you flashed ? Also: share a screenshot of your baseband version in android settings.
Sent from my OnePlus 7T Pro using XDA Labs
Click to expand...
Click to collapse
The last version that was available on SamMobile... It was "J530FXXU6CSK9_J530FXEF6CSL1_XEF"... if that's what you asked...
Here is the screenshot : https://ibb.co/7Q8jq2N

tiboleplubo said:
The last version that was available on SamMobile... It was "J530FXXU6CSK9_J530FXEF6CSL1_XEF"... if that's what you asked...
Here is the screenshot : https://ibb.co/7Q8jq2N
Click to expand...
Click to collapse
Well i would expect that it should work but as it does not flash the J530FXXS7CTF1 stock firmware . You could also try just flashing the modem partition of that firmware but if you dont know how then the fulk stock firmware is the easiest.
Sent from my OnePlus 7T Pro using XDA Labs

steadfasterX said:
Well i would expect that it should work but as it does not flash the J530FXXS7CTF1 stock firmware . You could also try just flashing the modem partition of that firmware but if you dont know how then the fulk stock firmware is the easiest.
Click to expand...
Click to collapse
It works now ! (I don't understand, I didn't do anything... Just think I had not been patient enough ^^')
Sorry for disturbing ^^' Anyway, thanks again, I hope we'll get an official build !

Gapps
Hi, thanks for your work. Please, i need to have gapp on this Rom, how i can (if is possible) install it?

pupunar said:
Hi, thanks for your work. Please, i need to have gapp on this Rom, how i can (if is possible) install it?
Click to expand...
Click to collapse
uhm.. you want to use /e/ which main goal is to live without google.... and you want to install google bloat and spyware on it? maybe read the Installation topic again?
View attachment 5119347
if you really need gapps (really?) and so google crap then simply go with LOS instead.
.-

Hey !
Quick question, I currently have an unofficial CrDroid on my phone that works great, except for the camera, which is stretched in almost all the apps...
So, just to be sure, does the camera work flawlessly in this rom ?
Thanks for your hard work ! :victory:

lPolarisl said:
Hey !
Quick question, I currently have an unofficial CrDroid on my phone that works great, except for the camera, which is stretched in almost all the apps...
So, just to be sure, does the camera work flawlessly in this rom ?
Thanks for your hard work ! :victory:
Click to expand...
Click to collapse
Yea within my vacation i had an user report about that. Will check that soon.
Sent from my OnePlus 7T Pro using XDA Labs

Hi, I have a question, I have only one app on my phone that use the Google Service Framework sadly..
I'm pretty sure I already know the answer, but will it work with /e/ ?

Morceaux said:
Hi, I have a question, I have only one app on my phone that use the Google Service Framework sadly..
I'm pretty sure I already know the answer, but will it work with /e/ ?
Click to expand...
Click to collapse
maybe if you tell what "it" is?
.-

steadfasterX said:
maybe if you tell what "it" is?
.-
Click to expand...
Click to collapse
Yeah, my bad >.>
It's Pulse SMS
(I tried to use it without the Gapps on my actual ROM, but It didn't work)

Morceaux said:
Yeah, my bad >.>
It's Pulse SMS
(I tried to use it without the Gapps on my actual ROM, but It didn't work)
Click to expand...
Click to collapse
should work according to https://community.e.foundation/t/sms-mms-app-question/1615
but the only way to find out for sure is try and see
(/e/ has microG included so that is way different then just choosing a ROM without installing gapps)
.-

[ROM] LineageOS 19.1 UNOFFICIAL - 1.3 [vendor & FBE] [2022-04-20]

LineageOS 19.1 for Sony Xperia XZ Premium
{
"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"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ Premium, offering several privacy features.
Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything (preferably dmesg and logcat). I can't test NFC very thoroughly, to please report your findings.
FEATURES
Signed with dev keys
Up-to-date kernel
WireGuard kernel support
Real vendor partition
FBE instead of FDE encryption
DOWNLOAD
You can download the latest releases and TWRP here:
https://androidfilehost.com/?w=files&flid=333825
Check the ChangeLog below for firmware requirements!
INSTALLATION
This build uses a real vendor partition in place for the (now) useless oem partition. You will therefore need the modified TWRP with vendor/FBE support linked above.
Before first install: flash and boot into TWRP, format data, reboot to recovery and wipe all internal partitions.
After above step / any subsequent dirty flashes: Boot into recovery, put the ROM, GApps and root (if needed) on sdcard and flash.
Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.
When updating from previous builds, simply dirty flash the ROM, together with any GApps and/or other modifications - addon.d will not work due to currently unavailable TWRP decryption.
Recommended GApps: MindTheGapps-12.1.0
KNOWN ISSUES
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
You tell me...
Contributors
derf elot, modpunk, Rooted_Ansh
Thanks to the yoshino testers (let me know if I forgot to add you)
coin3x, feduss, GiaSen, Gizanagi, hsheemi, kaancaliskan, No1Alien, sohrab1985
Source Code
maple: https://github.com/whatawurst/android_device_sony_maple
maple_dsds: https://github.com/whatawurst/android_device_sony_maple_dsds
kernel: https://github.com/whatawurst/android_kernel_sony_msm8998
Rom Information
ROM OS Version: Android 12.1 / 12L
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Current Stable Version: 1.3
Stable Release Date: 2022-04-20

SECURITY ADVICE
Don't flash ROMs or Magisk modules which set SELinux to permissive or you welcome malware on your device!
How to get root?
As mentioned before, there will not be an official su addon from LOS anymore. If you need root, flash an unofficial solution.

REQUIRED FIRMWARE: 47.2.A.10.107 (47.2.A.11.239 should also work as there isn't any real changes)
CHANGELOG
2022-04-20 | 1.3| 47.2.A.10.107
Initial release

Thanks for your work. And can the kernel support f2fs filesystem？ Does the camera work if i use another gpu driver？

ssdsw said:
Thanks for your work. And can the kernel support f2fs filesystem？ Does the camera work if i use another gpu driver？
Click to expand...
Click to collapse
f2fs is enabled in the kernel ( https://github.com/whatawurst/andro...8998-yoshino-maple_dsds_defconfig#L4632-L4636 ), but that doesn't mean you can use it as is. You would have to adjust the fstab's. No that I would recommend it, seeing as f2fs hasn't really received a lot of updates/(security) fixes for 4.4 kernels in recent times.
And no, you cannot update the gpu drivers. The Sony stock camera blobs are quite dependent on a specific tag.

derf elot said:
f2fs is enabled in the kernel ( https://github.com/whatawurst/andro...8998-yoshino-maple_dsds_defconfig#L4632-L4636 ), but that doesn't mean you can use it as is. You would have to adjust the fstab's. No that I would recommend it, seeing as f2fs hasn't really received a lot of updates/(security) fixes for 4.4 kernels in recent times.
And no, you cannot update the gpu drivers. The Sony stock camera blobs are quite dependent on a specific tag.
Click to expand...
Click to collapse
is there any clues/guide on how to edit the fstab?
so we can use f2fs on data & cache

is signature spoofing (for microg) enabled?
and as i already have installed the ArrowOS build of avl.callista which is based on your work: flash Stock ROM and then install your twrp+rom? or is stock rom step not necessary and it's enough to flash twrp+rom?

m00ns0rr0w said:
is signature spoofing (for microg) enabled?
and as i already have installed the ArrowOS build of avl.callista which is based on your work: flash Stock ROM and then install your twrp+rom? or is stock rom step not necessary and it's enough to flash twrp+rom?
Click to expand...
Click to collapse
no, spoofing is not enabled. I have made builds for 19 before with spoofing enabled, so it works. but rebuilding with spoofing enabled takes a while every time, since it includes changes in fw/b and that's a hefty compile.
as for flashing over another rom: it may or may not work. upgrading from los 18 should work by flashing rom together with 12.1 microg, but no idea about migrating from one rom to another.

derf elot said:
no, spoofing is not enabled. I have made builds for 19 before with spoofing enabled, so it works. but rebuilding with spoofing enabled takes a while every time, since it includes changes in fw/b and that's a hefty compile.
as for flashing over another rom: it may or may not work. upgrading from los 18 should work by flashing rom together with 12.1 microg, but no idea about migrating from one rom to another.
Click to expand...
Click to collapse
hi,
thx for your answer. i was just curious, as the arrowos build is based on your work and has signature spoofing enabled. But if, as you write, that's a lot of work then ... no problem. the arrowos version is stable
And, without signature spoofing, the part with "howto best migrate from rom A to rom B" is obsolete Self-building doesn't seem to be an option, as the hardware requirements seem a bit ... ambitious

Thanks for the great ROM.
I did a few tests today and I couldn't find anything broken.
The only issue I have found so far is when I take a picture or video with Open Camera and try to open it for preview inside the app. It does not work.

Thanks for your working on the ROM.
I found that LOS installed on my G8142 seems to have screen always on when charging, both on 18.1 and 19.1 (which is this one). How to turn it off?

Very nice, THANK YOU for great rom, i am testing it rn, so far so good.
To save someone a troubles i encountered:
I am comming from rooted stock .107, please all do flash correct TWRP!!! , i was slopy but have experience in flashing so i just dirtyflashed it on old TWRP, phone hanged prior to accessing twrp, could not hardreset or annything haha and i had to pull my battery so please just in case FLASH CORRECT TWRP
I like it alot, am switching to daily

stipi69 said:
Very nice, THANK YOU for great rom, i am testing it rn, so far so good.
To save someone a troubles i encountered:
I am comming from rooted stock .107, please all do flash correct TWRP!!! , i was slopy but have experience in flashing so i just dirtyflashed it on old TWRP, phone hanged prior to accessing twrp, could not hardreset or annything haha and i had to pull my battery so please just in case FLASH CORRECT TWRP
I like it alot, am switching to daily
Click to expand...
Click to collapse
Great, yes it needs the twrp I uploaded because of vendor partition and change from fde to fbe.
But just for reference, pulling the battery should not be necessary if it gets stuck. it should be enough to press and hold vol up (or down, I forget because I haven't needed it in a while) + power. it'll vibrate once, but keep holding it until it vibrates twice in quick succession. that should power it off. you can then enter fastboot to flash twrp or flash mode to flash stock.

derf elot said:
Great, yes it needs the twrp I uploaded because of vendor partition and change from fde to fbe.
But just for reference, pulling the battery should not be necessary if it gets stuck. it should be enough to press and hold vol up (or down, I forget because I haven't needed it in a while) + power. it'll vibrate once, but keep holding it until it vibrates twice in quick succession. that should power it off. you can then enter fastboot to flash twrp or flash mode to flash stock.
Click to expand...
Click to collapse
I agree, but i have faulty vol+ key so i was having a hard part sadlly.
Can i ask you something i see this problem 1+ years on all Lineage roms and i am not a developer:
SETTINGS / DISPLAY / LIVE DISPLAY / COLOR PROFILE / VIVID
If i choose this profile i get like 8 bit colors after a while of use, but realy like this profile... i adjusted it manualy now its good looking and stable but wondering if it is XZ P specific or all lineage

short message: my SIM card isn't working with this ROM.
long message: today i installed this ROM. I first flashed stock ROM, booted into it once, and then flashed this ROM. But, as with the ArrowOS ROM, my SIM card isn't working.
More Details: after fresh install of this ROM and during boot i enter the SIM PIN (so that works), but after boot it says: "service not available" (Dienst nicht verfügbar). I'm unable to get it working.
Provider: congstar (telekom daughter). The SIM worked with stock ROM, and it works in an older Samsung S5. Just for curiosity i flashed stock ROM again and
Yeah, i know, no warranty, but... someone had such a problem before?
thx

geee... getting crazy here... after the next (test) flash of this ROM the SIM suddenly works, as well as phone calls, SMS, ...
what's the difference to the first flash? after latest stock ROM flash i left the SIM inside, and the stock ROM (or the telekom software) did some settings, rebooted, and then i started the last flash. Is there something magic that is happening here?
if i had more hair all of it would be bright gray...

OK, after almost a week... no SIM card problems anymore. ROM is running stable.
Just some apps that somehow rely on Google Play Services (or microg maybe) don't run: apps that warn regarding severe weather conditions or catastrophes, like 'DWD Warnwetter', 'NINA KatWarn' etc.. Push notifications...

ROM is stable, and i finally managed the signature spoofing + microg stuff. Thx to @Yokurt815 and his little list in the XZ1C thread - going step by step, writing it all down, finally succeeded.
Am i right that the magisk/lygisk stuff has to be done again after flashing an possibly upcoming ROM update?

Big thanks to @derf elot for this rom
A couple of things though . . .
Anyone got this setting to turn on?
All languages set to English AU
Mind the gapps 12.1 installed
Google set to default assistant
Also, trying to search in settings causes a crash.

shoey63 said:
Big thanks to @derf elot for this rom
A couple of things though . . .
Anyone got this setting to turn on?
All languages set to English AU
Mind the gapps 12.1 installed
Google set to default assistant
Also, trying to search in settings causes a crash.
View attachment 5643169
Click to expand...
Click to collapse
Edited: NVM, seems like it won't work neither.
You need to set Ok Google/Hey Google at first boot; otherwise, it won't work.

[ROM][Android 11][Z00T][Z00L] ArrowOS v11.0 [18.05.2023][STABLE]

{
"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"
}
ArrowOS
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
ABOUT
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | Chat
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
Blog: blog.arrowos.net
Pre-installation:
TWRP(Z00T) (Download from here)
TWRP(Z00L) (Download from here)
NikGapps core (Download from here)
Installation:
Backup your data to PC, OTG flash drive
Flash recovery and boot to recovery
Wipe system, data, cache and dalvik, then reboot to recovery
Copy ArrowOS and Gapps to internal memory then flash them in TWRP in same order
Reboot and enjoy
Download:
Google Drive Folder
What's not working?
USB Debugging (Wireless Debugging works fine, you can use it instead...)
What's working?
Everything else?
Known minor issues:
Rarely, opening the settings from quick settings can crash the system-ui. This issue is not persistent and if it happens, only happens after a reboot or restarting system-ui(like changing ui elements from customization options).
Opening a notification will solve this issue until the next reboot, also this problem didn't happen when i had a password/pin protection.
ROM OS Version: Android 11
ROM Kernel: Linux 3.10.108
Based On: AOSP
Android Security Update: September 5 2022
SELinux: Enforcing
Status: Stable

I made this rom for personal use and can't regularly update or maintain it. Don't have enough time or storage space on my drives for it. So, if you find some other bugs feel free to report it for other users but i probably won't be able to fix them. Apart from the hotspot problem i didn't encounter any major issues...
I made 2 roms for these devices, crDroid and ArrowOS, wanted to see if ArrowOS was more lightweight and faster compared to crDroid... didn't see much difference in terms of performance. and ArrowOS dropped android 11 support so the security updates are a bit behind. anyways, since i already built it why not share it? so you guys have a vanilla rom option as well... personally i'll stick with the crDroid for now. but it's a personal preference.
link to the crDroid thread: https://forum.xda-developers.com/t/...d-v7-29-unofficial-20-04-2023-stable.4578239/

Thanks so much for your effort and great work.

@OP It just so happens my Z00T JUST got her cracked screen as SERIOUSLY bloated battery (seriously, it pushed the screen up 1mm bottom right corner... Till I popped the back cover that is, lol!) Replaced!
I actually beta tested for a dev way back when these where new, lol
Gimmie a day, I'll report back, if your still wanting Laser feedback?
Cheers either way!

lenigma1too said:
@OP It just so happens my Z00T JUST got her cracked screen as SERIOUSLY bloated battery (seriously, it pushed the screen up 1mm bottom right corner... Till I popped the back cover that is, lol!) Replaced!
I actually beta tested for a dev way back when these where new, lol
Gimmie a day, I'll report back, if your still wanting Laser feedback?
Cheers either way!
Click to expand...
Click to collapse
yeah would be nice. i'd like to see if it works on Z00L and if the same bugs are present or if there are more bugs... i don't have any way of testing that variant but since every other developer built roms for these 2 devices together and both had similar experience i'd assume Z00L would be fine as well...

zenfone selfie said:
yeah would be nice. i'd like to see if it works on Z00L and if the same bugs are present or if there are more bugs... i don't have any way of testing that variant but since every other developer built roms for these 2 devices together and both had similar experience i'd assume Z00L would be fine as well...
Click to expand...
Click to collapse
*Open mouth, insert foot*
Its actually the ze551kl, the 1080p variant of the Z00L 720p.
But, rereading your op, it IS this variant you couldn't test, correct?
Anyways, now that I'm no longer lying to you (), I'll be testing on a ze551kl, not ze550kl or selfie

lenigma1too said:
*Open mouth, insert foot*
Its actually the ze551kl, the 1080p variant of the Z00L 720p.
But, rereading your op, it IS this variant you couldn't test, correct?
Anyways, now that I'm no longer lying to you (), I'll be testing on a ze551kl, not ze550kl or selfie
Click to expand...
Click to collapse
i think that's a Z00T as well? still... even if it's the same code, it's still a different device. any testing is better than none i just wanna know if the Z00L rooms are working tho i compiled em but still no feedback for em.

zenfone selfie said:
i think that's a Z00T as well? still... even if it's the same code, it's still a different device. any testing is better than none i just wanna know if the Z00L rooms are working tho i compiled em but still no feedback for em.
Click to expand...
Click to collapse
Thanks for the great work and effort to keep these devices alive.
Today I only tried the installation on ze550kl z00l and everything went fine. Twrp 3.3.1-0 is nikgapps core arm64. I haven't been able to test it thoroughly, but the basic functions work very well. The audio is also great, unlike previous versions of Android 10 where the audio sometimes worked and sometimes it didn't.
Immediately after, as recommended by you, I installed CrDroid, so I can't say about this rom.
A thousand thanks

jimjack12 said:
Thanks for the great work and effort to keep these devices alive.
Today I only tried the installation on ze550kl z00l and everything went fine. Twrp 3.3.1-0 is nikgapps core arm64. I haven't been able to test it thoroughly, but the basic functions work very well. The audio is also great, unlike previous versions of Android 10 where the audio sometimes worked and sometimes it didn't.
Immediately after, as recommended by you, I installed CrDroid, so I can't say about this rom.
A thousand thanks
Click to expand...
Click to collapse
by audio do you mean the loudspeaker issue during calls? or was there another audio bug in the 10 roms? i didn't actually use 10 on this phone. just tested briefly and loudspeaker issue was big enough for me to just walk away. don't know all the details about previous roms except for groovy nougat.

Con l'audio intendo che non si sentiva nulla completamente, suoneria, musica, ecc...
Questa versione tuttavia non sembra avere questo problema.

Hi @selfie zenfon.
With the little time I have available, I tried to do some tests on ze550kl z00ld.
As mentioned in the previous post, I installed crDroid, with twrp 3.3.1-0, but after doing a factory data reset as the operating system and after the first recharge, the smartphone went into bootloop.
Then I installed Twrp 3.7.0_9 and Arrowos. I also tried doing a factory data reset with this rom and it has been working fine for about 3 days without any bootloop.
I can also say that it is about 10% smoother than CrDroid.
I would also try CrDroid with Twrp 3.7.0_9 as soon as possible to see if it will bootloop again.
Also I want to compliment you: I don't know if you are a developer and I don't know how you compiled these roms, but I can tell you that they work very well and I can say that they are among the best custom roms for these devices.
Thanks so much for the great job

last and probably the final build is up!
hotspot fix applied to the arrowos as well...
enable blurs option is removed.
face unlock wasn't working on this rom so removed the relevant packages and it won't show up in the settings anymore.
duckduckgo browser won't be pre-installed as a system app as it's available on playstore.
this build doesn't have a pre-installed browser right now, but as i said i made these roms for my personal use first... i won't be using ddg and not having a pre-installed browser isn't a problem for me.

jimjack12 said:
Hi @selfie zenfon.
With the little time I have available, I tried to do some tests on ze550kl z00ld.
As mentioned in the previous post, I installed crDroid, with twrp 3.3.1-0, but after doing a factory data reset as the operating system and after the first recharge, the smartphone went into bootloop.
Then I installed Twrp 3.7.0_9 and Arrowos. I also tried doing a factory data reset with this rom and it has been working fine for about 3 days without any bootloop.
I can also say that it is about 10% smoother than CrDroid.
I would also try CrDroid with Twrp 3.7.0_9 as soon as possible to see if it will bootloop again.
Also I want to compliment you: I don't know if you are a developer and I don't know how you compiled these roms, but I can tell you that they work very well and I can say that they are among the best custom roms for these devices.
Thanks so much for the great job
Click to expand...
Click to collapse
tried 3.7.0_9 again, no matter what... i can't install any roms with it. either it says factory reset on the first boot and reboots to the recovery. or system boots up but can't do anything... can't install apps, take photos etc. my storage becomes unusable. if i wipe the partitions using older version and install the rom with the latest, then it works. but if i wipe my phone with the new twrp is causes that problem... @str4610 also used a newer twrp without any issues but i don't know. i can't make it work
don't know anything about the crdroid bootloops, i didn't have that problem yet. but if this rom works better for you that's fine. applied the hotspot fix now this one is a fully functional option as well...
also it would be nice if you can test the latest builds for both if you have some spare time. i can test the z00t but i don't know if the z00l builds even booting up should work but can't be certain without actual testing.
edit: ah twrp was fine. my phone was messed up lol had to resize my data partition and everything is ok with the latest twrp now.

Thanks so much for the great job.
I confirm the installation of the new version of CrDroid and ArrowOs (It's a pity that this rom has been abandoned..).
TWRP used: 3.7.0_9-0.
Installation:
1) Format the data
2) Wipe system, data, cache and dalvik
3) Reboot into Twrp and install CrDroid+NikGapps Core
To speed up the system a bit, enable developer options and scale animations from 1 -> 0.5
I confirm the following features:
-Bluetooth
- Double tap to turn off/wake the screen
- Wifi
- Torch
- Camera
- Basic functions.
Not using the smartphone as a daily driver, I can't say more.
Thank you so much for your time and effort to maintain this device.

@jimjack12
thanks for testing it most of the custom rom groups stopped developing 11 long before arrow did. it's still not that far behind and security updates are not "that" important on such an old phone. and i can't promise to update crdroid or lineage either. i don't have enough storage on my drives so i was using an old sata 2 hdd from 2007/2008 lol
can't regularly set this development environment for just the updates.
120gb off brand ssd hanging for system/swap/cache and 640gb old af hdd with some badsectors is for android source code not ideal... all my actual drives are almost full...

final update is released... applied the last patches i made for crdroid, all cores should be online for all the devices now. didn't get any bug reports for arrowos but since my device sources were the same, i assumed it would have the same issue.

Last time I checked the previous update prior to the latest one didn't had the Smart Orientation. Rest was all good.
Is it implemented now???

CapTain335 said:
Last time I checked the previous update prior to the latest one didn't had the Smart Orientation. Rest was all good.
Is it implemented now???
Click to expand...
Click to collapse
no feature updates. just applied the fixes i made for crdroid.

zenfone selfie said:
View attachment 5913753
I made this rom for personal use and can't regularly update or maintain it. Don't have enough time or storage space on my drives for it. So, if you find some other bugs feel free to report it for other users but i probably won't be able to fix them. Apart from the hotspot problem i didn't encounter any major issues...
I made 2 roms for these devices, crDroid and ArrowOS, wanted to see if ArrowOS was more lightweight and faster compared to crDroid... didn't see much difference in terms of performance. and ArrowOS dropped android 11 support so the security updates are a bit behind. anyways, since i already built it why not share it? so you guys have a vanilla rom option as well... personally i'll stick with the crDroid for now. but it's a personal preference.
link to the crDroid thread: https://forum.xda-developers.com/t/...d-v7-29-unofficial-20-04-2023-stable.4578239/
Click to expand...
Click to collapse
sorry, on my cellphone, Asus Zenfone Selfie can't be flashed
i am using Z00T version

fdxnameword said:
sorry, on my cellphone, Asus Zenfone Selfie can't be flashed
i am using Z00T version
Click to expand...
Click to collapse
zenfone selfie works fine with this rom. its my own test device. maybe your download failed? or file corrupted while copying to the phone? what's the error you're getting?
if the phone was encrypted it might require a data format(not wipe)

Develop Bugs

welcome