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

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

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

Related

[ROM][6.0.1][UNOFFICIAL] Lineage OS 13

{
"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.
*/
Status : ALPHA 5
This version is mainly for testers but anybody can flash it, since there is no more critical issues :victory:
This build is userdebug flavor. ADB and ROOT are disabled by default.
Installation instructions
First of all, update your Mate to EMUI 4.1 (that has the good kernel version)
Like always: BACKUP, BACKUP BACKUP !
Wipe every partitions (except your SD and your internal storage) See below.
You can flash GApps (see the frequently asked questions below).
Enjoy.
- NXT-AL10, NXT-L29 and NXT-L09 reported as booting
- Xposed reported as working
- Second SIM reported as working (NXT-L29)
Important note : L-09 variant is UNSTABLE for now.
Working
- Since Alpha 1
Partial and temporary GApps implementation
Launchers (Pixel/Google Now)
Themes (include animated)
- Since Alpha 2
RIL
Audio
Microphone
WiFi
Bluetooth
Security (Pin/Password/Pattern..)
GPS over data
Google Apps (include widgets and theme )
HiSuite full compatibility
- Since Alpha 3
SD Card
Tethering (WIFI + BT)
Offline charge
USB Access (MTP/PTP + MIDI input)
OTA Updates (by the built-in CM Updater)
Enhanced boot time (+/- 1min)
- Since Alpha 4
LCD Backlight adjustments
Notification Led
Enhanced boot caching
USB Tethering
Fix sensors
Fix ambiant display
Fix Sleep Of Death (thanks to XePeleato)
Fix FLP (location)
Fix GPS
- Since Alpha 5
RIL Signal
Bluetooth (now considered as stable)
Camera (Both, picture only)
Lineage skin/rebrand
Not Working
Camera (video mode)
Native cast
Fingerprint
Fast Charge
NFC
FM Radio
Known issues:
GPS module(fully working, available in the next release)
Another (ghost) SD Card is recognized and is incompatible with CM -> just ignore it for now. This entry will disappear with the next (OTA) update.
RIL working irregularly on AL-10 (unconfirmed) and L-09 devices
Offline charge not working (fixed, available in the next release)
You prefer to wait for a fully working ROM
You can follow the porting status here : https://github.com/PaulFasola/android_device_huawei_next/projects/1
Downloads
Current release, Alpha 5
Click here
Do a full wipe before installing this update or you could try the (risky) migration tool
Previous release, Alpha 4
Click here
Archives
Click here
Source Code
https://github.com/PaulFasola/android_device_huawei_next
You'll find the kernel and the vendor repos as well (check the readme)
Donators
android09
danywalkert
Azti Iluna
basimzanaty
drairoh
My dear tester Kingzak34
Many thanks to you guys !
Credits
* Nexolight for the useful advises
* Meticulus for the glitchy screen issue!
* Surdu_perdu's work for some ramdisk issues!
* _Ekko (freenode) for his help on the rild issues (symbols, symbols symbols...) and rild proper init
XDA:DevDB Information
[ROM][6.0.1][UNOFFICIAL] Lineage OS 13 Port, ROM for the Huawei Mate 8
Contributors
_skypol0
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: No Longer Updated
Created 2016-12-05
Last Updated 2017-09-15

Reserved
Changelogs
Alpha 3.1 - OTA only
LCD Backlight (manual update, temporary disable adaptive brightness and sensors are still off-line)
Leds (charge/notification etc..)
Drastically reduce battery consumption
Better boot caching for apps optimization
Bases for enabling the sensors soon
Fix in-game latency for complex animations (like 3D transitions)
Alpha 5.1 - (Full)OTA / download
Link: click here
Fully fix the GPS (satellites acquisition, bad wakelocks...)
Fix offline charge (animation) and adjust the settings for a faster charge (rapid charge still In the to-do list).
Have the latest LineageOS 13 core changes

Downloading now, I will test soon. Thanks for your work
UPDATE: I had to remove assert line in your updater-script, as my ro.build.product was Mate8 not next. After install i am currently stuck on the boot loader "Your device is booting now"
UPDATE 2: It worked!! Seemed like an issue on my end, i had to update to emui 4.1 before I was able to get the ROM to boot. Everything seems great so far. The only issue I faced was with the screen artifacting, and of course the issues you already listed. Great work :good:

FREQUENTLY ASKED QUESTIONS
I come from EMUI 4.1, can I flash this ROM ?
Yes, but you will need to full wipe and follow the instructions in OP
I'm on EMUI 5.X or 4.0, can I flash this ROM ?
You should roll back to EMUI 4.1 then follow OP instructions
My phone is asking for a password on boot
The master key of the old EMUI is not known and that's why we had to wipe userdata (this remove encryption).
So, that means that your Data partition is not wiped, and you have to wipe it !
Flash the Cyanogenmod recovery (built with this ROM, located in the same folder) and do a full factory reset, this work everytime.
Once done, reboot and flash this custom TWRP that handle non-encrypted userdata. You will be able to open the SD Card, flash whatever you want and restore your backup.
NB : If you flash back the stock ROM, this last will re-encrypt /data and everything will work as always.
I've waited for 10 minutes and the Cyanogen boot animation is still here
Something is wrong and prevent CM to complete the boot sequence. This is an issue to report (see below).
This ROM does not contain GApps, what should I take ?
You can find GApps package on OpenGapps
You'll need to take for ARM64 and Android 6.0 and then choose the package you want.
Tested so far : Full, Stock, Nano
I've found an issue
First of all, thanks for helping @_skypol0 !
> Open a ticket here <
Check if there is not a similar issue before posting
Fill the issue (Your device infos (kernel version, last EMUI update version etc.) , What is the problem ?, how can we reproduce it ? etc. Please put as many information as possible)
Share a paste/haste/ghost/...bin of your logcat and dmesg

Wont use it but thanks for developing it (i dont like roms based on clean android). Might be a huge step in futrue development on Mate family.

Awesome!!
Man, you've convinced me not to sell my mate 8 anymore, It's great potential. I'm looking forward for the beta version of this!

Was going to sell my mate 8 also. But now will test once basic functions are ok.

khanem said:
Was going to sell my mate 8 also. But now will test once basic functions are ok.
Click to expand...
Click to collapse
RIL an audio should be fixed with the next release later this week

I'm excited for Alpha 2

UnchartedRd said:
Downloading now, I will test soon. Thanks for your work
UPDATE: I had to remove assert line in your updater-script, as my ro.build.product was Mate8 not next. After install i am currently stuck on the boot loader "Your device is booting now"
UPDATE 2: It worked!! Seemed like an issue on my end, i had to update to emui 4.1 before I was able to get the ROM to boot. Everything seems great so far. The only issue I faced was with the screen artifacting, and of course the issues you already listed. Great work :good:
Click to expand...
Click to collapse
Oh, yeah, thanks for pointing it out ! I have built CM-13 with the 4.1's kernel and so this last can't work with lower versions I edit the thread.
(for any other problem, open an issue on Github, I can miss infos here!)

_skypol0 said:
Oh, yeah, thanks for pointing it out ! I have built CM-13 with the 4.1's kernel and so this last can't work with lower versions I edit the thread.
(for any other problem, open an issue on Github, I can miss infos here!)
Click to expand...
Click to collapse
No problem, I'll post on github if I find anything else

You mean B320?

Thanks for your effort friend, I'll definitely be glad to test it once it gets a bit more stable.

Oh my god... it's really happening...

Once SD support works, I'll glady test this on my NXT-L09.

THANKS DUDE! SWEET! Hope stable rom will get here soon! but wouldt be better starting with cm14? just saying!!

albertwesquer said:
THANKS DUDE! SWEET! Hope stable rom will get here soon! but wouldt be better starting with cm14? just saying!!
Click to expand...
Click to collapse
Huawei hasn't released a stable build of nougat yet, its only been beta builds. Once Huawei releases nougat for M8, he can work on it.

And on the other side Cm14 is far from stable
Tapatalké depuis mon MEGA Mate 8 !

well i didnt know we had to have nougat in our mate 8 in order to have cm14, in that case cm13 should be ready since 6.0 have quite some time in our device! SO THERE'S HOPE!

Amazing I cant beileve im really seeing it

[ROM] [Final Build 1] 01/09 LineageOS 14.1 | Android 7.1.2 | Final

{
"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 7.1.2(Nougat), which is designed to increase performance and reliability over stock Android for your device.
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!
*/
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 on 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.
Unofficial builds of LineageOS 14.1 (Android 7.1.2) for the Elephone P9000
Code:
Changelog:
Fixed HDR
Fixed Deepsleep
Fixed all random reboots
Fixed Wi-Fi, Usb, BT tethering
Fixed memory leaks
Fixed offline charging
Fixed interface/and system bugs
Fixed logs spam
Fixed all other bugs, provided by users
Fix's of codecs ( Now multimedia working more and more better)
Fixed FPS of video recording in Screen recorder and Footej Camera APS
For video recording use app from Google Play Store (Footej camera ONLY (She is provide stable recording with high FPS)
Added Doze support
System optimisation
And a lot of other fixed for you :highfive:
Working:
It is boots and hardware accelerated!
WiFi
Fast charge
Camera
Offline charging
GPS
AGPS
Vibration
Audio
Auto brightness
RAM and ROM
Rotation
All sensors
NFC (Payments, pairing (TESTED!))
HDR
Lazer autofocus
Flashlight (Statusbar and Camera)
Bluetooth
External SD
RIL for SMS/Calls/Internet/Lte on 1 and 2 SIM
MTP and Mass Storage mode
Audio over Bluetooth ((a2dp)Music and etc)
Fingerprint Scanner
FM Radio
Wi-fi Tethering
Home button like in stock
Special button like in stock + new feature (Check it)
F2FS
In progress:
Video recording in stock camera app ( use Footej camera app from Play Store for video recording)
Download LineageOS:
Final Build 1:
https://www.androidfilehost.com/?fid=961840155545592306
How to install LineageOS 14.1 on your P9000:
For installation of new LineageOS 14.1 you need to do next action only one time. Next builds can be installed like about it written in point 2:
0. If on your phone installed stock Nougat(if not, go to point 2), you should install latest Android 6.0 ROM and after install any TWRP from github
1. Download ROM
1.1 Download Gapps: https://www.androidfilehost.com/?fid=817550096634792652
1.2 Copy Gapps And ROM on SD Card
Attention! If you user of old LineageOS and CyanogenMod ROMs, install next builds of LineageOS from this step.
2 Boot in to Recovery mode (on dissabled phone press Vol. Up and Power on buttons, wait of entering in to recovery mode).
Steps:
Copy ROM and GAPPS on sd card, if you still not copied
Choose: Factory reset
Choose: Data reset
Return, choose: Install
Choose downloaded LOS build
Wait of successfully flashing
After, don't reboot
Choose downloaded Gapps package
Wait of successfully flashing
Reboot your phone
Sources:
Device Tree: https://github.com/Deepflex/android_device_elephone_p9000-nougat
Device Common: https://github.com/Deepflex/android_device_cyanogen_mt6755-common
Vendor Tree: https://github.com/Deepflex/android_vendor_elephone_p9000-nougat
Kernel sources: https://github.com/Deepflex/android_kernel_elephone_p9000/tree/flexy
Thanks to:
Leskal
Mohancm
CyanogenMod team
Wuxianlin
Ferhung
SHVED
Xen0n
JonnyXDA
olegsvs
Visi0nary
DeckerSU
Gearlabs
andyrichardson
Team M.A.D
Appendix:
If you want to mirror the files or port the ROM to another device, I encourage you to do so! Only please respect my work and give proper credits. Also, if you like my works, you can donate to me. Thank you!
XDA:DevDB Information
LineageOS, ROM for the Elephone P9000
Contributors
Deepflex
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest Android 6.0 Stock
Based On: LineageOS
Version Information
Status: Final
Current Final Version: Final Build 1
Final Release Date: 2017-09-01
Created 2017-08-10
Last Updated 2017-09-01

Reserved.

Wow great job, to bad i'm on vacation , and alto i've got time enough i need my phone functions in proper these weeks to Stay in touch for family reasons.
I love to Read other comments.
Thnx deepflex for the hard work done sofar, i guess other p9000 look a likes would benifit from youre hard work in this.

thx
I'm going to try it right now people

Are the branches of the kernel both updated, i would like to try and build aicp, based out of these sources. Also can i flash this version on the updated preloader, or do i need to go back to the old one?

Yay, that's good news. However, did you just copied the description of the old entry for LOS 13 or is it really based on Android 6? I'd make more sense to preload the phone with Android 7 stock rom for Android 7.1 based system.
Good job, appreciate your continuous work and look forward to a stable build also.

TheMRK said:
Yay, that's good news. However, did you just copied the description of the old entry for LOS 13 or is it really based on Android 6? I'd make more sense to preload the phone with Android 7 stock rom for Android 7.1 based system.
Good job, appreciate your continuous work and look forward to a stable build also.
Click to expand...
Click to collapse
Hello!. Description for los14.1, not copied from los13

Great news!!!! I'll wait until everything is working.
Thanks a lot!

Do not forget
!!! You must have a Android 6 rom loaded !!!!
If you use Android 7 you will be stuck in a bootloop...
so please if you are using Android 7 ... downgrade to the stock ROM first ( i used : Elephone P9000_Android 6.0_20160810 OTA)
and do not forget .. first boot wil take more then 5min .. so please be patient
Thanks deepflex for this rom . testing has now started !
michael

megasounds said:
Do not forget
!!! You must have a Android 6 rom loaded !!!!
If you use Android 7 you will be stuck in a bootloop...
so please if you are using Android 7 ... downgrade to the stock ROM first ( i used : Elephone P9000_Android 6.0_20160810 OTA)
and do not forget .. first boot wil take more then 5min .. so please be patient
Thanks deepflex for this rom . testing has now started !
michael
Click to expand...
Click to collapse
Hello. Waiting for feedback :highfive:

Ruben Craveiro said:
Are the branches of the kernel both updated, i would like to try and build aicp, based out of these sources. Also can i flash this version on the updated preloader, or do i need to go back to the old one?
Click to expand...
Click to collapse
Soon. Use Leskal open-source brunches

Deepflex said:
Hello. Waiting for feedback :highfive:
Click to expand...
Click to collapse
Hahaha ok no problemo !
-when i use open gapps "stock" version i have a lot of errors and slow system , so i cleaned the phone completely , reinstalled the phone with your beta and used the open gapps NANO package ... so far so good
-i know the camera is not working correctly but can you please fix this asap !!!
-speed is great
-wifi is faster then Android 6
-the default left button is not working well , i had to reset this to an other app. I set it now to "phone", so when i press the left extra button on the device it goes strait to the phone app. Thats working SUPER!
-sometimes the phone "hangs" doing nothing... reboot is needed.
-power button doesn't work .
-when installing i get 2 errors :
patching system image unconditionally...
E:unknown command [log]
E:unknown command [log]
-sound is great ! even louder than stock android 6
-after first boot i doesn't see my simm , just reboot it and its there and working.
michael

OK got 2.........810 Android 6 Rom installed lost my imei flashed recovery installed los14.1 bot no Sims but one thing is strange Maui Meter to recovery imei only seems to work when i installed Android 7 stable 2......418 i can restore my imei but in Android 6 what i need no way any plan?

can you port this rom to umi super ? umi super and elephone ar very very similar please
thanks

kurador911 said:
can you port this rom to umi super ? umi super and elephone ar very very similar please
thanks
Click to expand...
Click to collapse
if its so simillar you can port it yourself.. are you expecting someone will just say yes, to a device they dont even have? ...

Ruben Craveiro said:
if its so simillar you can port it yourself.. are you expecting someone will just say yes, to a device they dont even have? ...
Click to expand...
Click to collapse
**** you men, i dont ask anything for you.

kurador911 said:
**** you men, i dont ask anything for you.
Click to expand...
Click to collapse
Hm ok, no need to insult, why? just why?... and why do you even ask for someone to port a rom, to a device they *dont even have*? its just spamming with things that will never be done... if you want the rom so much you should talk to the developers of your device to try and port the rom from this device to your device or simply try and port it yourself... Another tip, is that you try to improve your education, and be nicer to people. Insulting wont get you anywhere....

kurador911 said:
can you port this rom to umi super ? umi super and elephone ar very very similar please
thanks
Click to expand...
Click to collapse
https://github.com/Deepflex/android...-nougat/blob/master/proprietary-files-mtk.txt
Copy this lib's/bin's from your stock in ROM. For unpack of sdat use sdat2img, and ext4unpacker. Or make flashable zip with this lib's/bin's.
kurador911 said:
**** you men, i dont ask anything for you.
Click to expand...
Click to collapse
And, please, don't need agression. Ruben says all correctly.

Hi deepflex
i tried everything but the power button doesn't work. I reinstalled several time android 6 and played with variuos openGapps packages.
i ended up with your Beta version and openGapps nano.
I CAN NOT make the power button work to instaled lock the phone....so when the phone is unlocked i can not make it lock.
I installed the Lock app from the playstore to lock my phone.
conclusion : unlock with the power button works but locking the phone with the power button DOES NOT work.
Also a reset to factory default from the OS does not work ! it will end up with a device thats only booting in to recovery mode.
michael

megasounds said:
Hi deepflex
i tried everything but the power button doesn't work. I reinstalled several time android 6 and played with variuos openGapps packages.
i ended up with your Beta version and openGapps nano.
I CAN NOT make the power button work to instaled lock the phone....so when the phone is unlocked i can not make it lock.
I installed the Lock app from the playstore to lock my phone.
conclusion : unlock with the power button works but locking the phone with the power button DOES NOT work.
Also a reset to factory default from the OS does not work ! it will end up with a device thats only booting in to recovery mode.
michael
Click to expand...
Click to collapse
Hello! Thank you for feedback. It's fixed. In next build

[ROM][8.1.0]LineageOS-15.1[Joan][Treblelized][Unofficial]

{
"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.

[ROM][UNOFFICIAL][O][UsU] LineageOS 15.1 [H815] DEPRECATED

Reserved

Hey! I'm using it and it works flawlessly except 1 thing for me. I use bt calls much but now it has background noise as mentioned in known issues section. I can live without it but I hope you to solve this problem. Is there anything I can do for help? Thanks again @steadfasterX

emrtnl said:
Hey! I'm using it and it works flawlessly except 1 thing for me. I use bt calls much but now it has background noise as mentioned in known issues section. I can live without it but I hope you to solve this problem. Is there anything I can do for help? Thanks again @steadfasterX
Click to expand...
Click to collapse
Thanks for offering your help but unfortunately you can't do anything at the moment. I'm working on it at highest priority because I need it by myself but this issue is absolutely a nightmare and not easy to fix
Sent from my LG-H815 using XDA Labs

Thank You!
First of all, THANK YOU @steadfasterX for your work. I'm so happy there are still active developers for the G4, i'm finally free from the LG's claws.
I'm currently running the latest version of LOS available and here's a list of bugs/errors I found:
- I can't find/connect to 5GHz Wireless networks;
- The torch tile isn't working;
- Feels like even 2.4Ghz wi-fi connections are slowed down;
- SeLinux is permissive;
- Not an error, but I coudn't get Floatify to work on my lockscreen, guess it is not compatible with Oreo yet.
I didn't have issues with bluetooth media as some people had, though. There's no background noise
I hope this feedback help you somehow

igorgpsouza said:
First of all, THANK YOU @steadfasterX for your work. I'm so happy there are still active developers for the G4, i'm finally free from the LG's claws.
I'm currently running the latest version of LOS available and here's a list of bugs/errors I found:
- I can't find/connect to 5GHz Wireless networks;
- The torch tile isn't working;
- Feels like even 2.4Ghz wi-fi connections are slowed down;
- SeLinux is permissive;
- Not an error, but I coudn't get Floatify to work on my lockscreen, guess it is not compatible with Oreo yet.
I didn't have issues with bluetooth media as some people had, though. There's no background noise
I hope this feedback help you somehow
Click to expand...
Click to collapse
BT music is ok but calls has that bad noise.

Thanks for building this. Think I prefer Lineage to AOSCP.
Just a couple of issues that I have noticed so far.
I have the same problem on this ROM that I had using AOSCP. I tried to change the lockscreen to pattern during the initial setup wizard but it crashed and next time round I just skipped that step. Now when I try and set my lockscreen it just crashes the settings app.
Also torch tile doesn't work in the quick settings panel.

Rich Rich said:
Thanks for building this. Think I prefer Lineage to AOSCP.
Just a couple of issues that I have noticed so far.
I have the same problem on this ROM that I had using AOSCP. I tried to change the lockscreen to pattern during the initial setup wizard but it crashed and next time round I just skipped that step. Now when I try and set my lockscreen it just crashes the settings app.
Also torch tile doesn't work in the quick settings panel.
Click to expand...
Click to collapse
torch tile --> check the Known Issues in the OP for a workaround
regarding the settings crash: without logs no one can help you
adb shell
su
logcat -b all -c
logcat -b all
(now immediately reproduce the crash)
ctrl+c to cancel
Click to expand...
Click to collapse
copy the whole console output and paste it at http://bpaste.net (ensure you set the dropdown there to never)

steadfasterX said:
torch tile --> check the Known Issues in the OP for a workaround
regarding the settings crash: without logs no one can help you
copy the whole console output and paste it at http://bpaste.net (ensure you set the dropdown there to never)
Click to expand...
Click to collapse
https://bpaste.net/show/b78884ff63dc
---------- Post added at 09:42 AM ---------- Previous post was at 09:01 AM ----------
Just realised I wasn't rooted so went and flashed SuperSU.
Do you need me to produce another log with root?

Rich Rich said:
https://bpaste.net/show/b78884ff63dc
---------- Post added at 09:42 AM ---------- Previous post was at 09:01 AM ----------
Just realised I wasn't rooted so went and flashed SuperSU.
Do you need me to produce another log with root?
Click to expand...
Click to collapse
no. all good.

Rich Rich said:
https://bpaste.net/show/b78884ff63dc
---------- Post added at 09:42 AM ---------- Previous post was at 09:01 AM ----------
Just realised I wasn't rooted so went and flashed SuperSU.
Do you need me to produce another log with root?
Click to expand...
Click to collapse
please do a backup in TWRP
then flash this TEST kernel in TWRP: http://leech.binbash.it:8008/kernel...ental/h815_usu_los_boot_TEST-build-1-oreo.zip
try again to access the settings screen

steadfasterX said:
please do a backup in TWRP
then flash this TEST kernel in TWRP: http://leech.binbash.it:8008/kernel...ental/h815_usu_los_boot_TEST-build-1-oreo.zip
try again to access the settings screen
Click to expand...
Click to collapse
Same error again. Here's log;
https://bpaste.net/show/2290419a8aee

Rich Rich said:
Same error again. Here's log;
https://bpaste.net/show/2290419a8aee
Click to expand...
Click to collapse
ok I have my h815 UsU'd as well and I cannot reproduce your issue.
Do you have tried to do a clean flash (means format system! --> FORMAT data! --> flash ROM) ?
Hint: obviously this will delete ALL your internal storage so take care of that and I recommend to use the app FlashFire for the backup of your internal storage before doing the above
.

steadfasterX said:
ok I have my h815 UsU'd as well and I cannot reproduce your issue.
Do you have tried to do a clean flash (means format system! --> FORMAT data! --> flash ROM) ?
Hint: obviously this will delete ALL your internal storage so take care of that and I recommend to use the app FlashFire for the backup of your internal storage before doing the above
.
Click to expand...
Click to collapse
Just tried that. Still the same.
Tried it twice, once as you said then again by picking all the wipe options. If I try set a password or code it will crash then ask me to re-enter the password which always fails.
Think I'll just use it without a lockscreen.

New build up
Happy leeching
@Rich Rich try that one too. Its really strange that it does work here and for you not. what firmware version is your bootloader stack?
Sent from my LG-H815 using XDA Labs

steadfasterX said:
New build up
Happy leeching
@Rich Rich try that one too. Its really strange that it does work here and for you not. what firmware version is your bootloader stack?
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Just flashed that and it's the same. My device is an import from Taiwan, so originally on the TWN firmware is that makes a difference.
How do I check the bootloader stack? I used the UsU guide and flashed the files given there.

Rich Rich said:
Just flashed that and it's the same. My device is an import from Taiwan, so originally on the TWN firmware is that makes a difference.
How do I check the bootloader stack? I used the UsU guide and flashed the files given there.
Click to expand...
Click to collapse
and what was the exact firmware version you were on before flashing UsU?
you can use SALT and check "Firmware (system)" in the main screen. its not 100% but we will see.
if you have followed the unlock guide you would have a backup of that. Then its enough to do this (requires Linux/FWUL):
Open a terminal in the directory where you have your SALT backup before UsU'd.
Then:
Code:
strings misc.bin | grep LG
and paste the whole output

steadfasterX said:
and what was the exact firmware version you were on before flashing UsU?
you can use SALT and check "Firmware (system)" in the main screen. its not 100% but we will see.
if you have followed the unlock guide you would have a backup of that. Then its enough to do this (requires Linux/FWUL):
Open a terminal in the directory where you have your SALT backup before UsU'd.
Then:
Code:
strings misc.bin | grep LG
and paste the whole output
Click to expand...
Click to collapse
I've attached a screenshot of my SALT window. Hope this shows the info needed.

Rich Rich said:
I've attached a screenshot of my SALT window. Hope this shows the info needed.
Click to expand...
Click to collapse
you know that you are using an outdated version of SALT? current is 3.16 atm.
now check the backup files as mentioned.
.

steadfasterX said:
you know that you are using an outdated version of SALT? current is 3.16 atm.
now check the backup files as mentioned.
.
Click to expand...
Click to collapse
Don't know where the backup files are stored. I just have SALT installed in a standalone VMWare Linux machine, I'm not Linux literate so not sure where to start looking for the files. What's the default backup location?

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

Develop Bugs

welcome