{
"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 (Nougat), 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 our Gerrit Code Review.
Code:
#include "std_disclaimer.h"
/*
* Your warranty is 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.
*/
Working
Boot
Mobile data
Cam (pics only)
flashlight
fingerprint
sdcard is recognized/mounted
Unknown/Untested
GPS
NFC
calls/sms (should work i guess, because data works)
audio (cant test that in class )
Issues
USB
Wifi
Bluetooth
Recording
Brightness change
Everything i forgot probably
As you can see on the "Working" list, this is a highly experimental build, flash at your own risk, and don't come crying to me if it should brick anything (it didn't for me, but seeing from the TWRP Thread the V30 can be picky).
Dont forget to make a backup!!!
If you want to report any bugs, NEVER do it without providing logs. I can't try to fix things without logs.
Helpful log commands:
logcat (usage: e.g. logcat > /sdcard/logcat.txt )
dumpsys (usage: e.g. dumpsys SurfaceFlinger > /sdcard/dump_sf.txt)
dmesg (usage: e.g. dmesg > /sdcard/dmesg.txt , might need root)
for more examples on how to use the commands, either google (do that first) or ask (only do this if you already googled how to use those commands).
FAQ
USB isn't working. How do I get logs?
In the ramdisk theres a nice little script which will print the logcat to /data/ramoops/cm14.1_<number>_logcat_<date/time>.txt
The logcat is many many hundreds of MB in size, why?
Its currently spammed with something like this:
Code:
E/QMI_FW ( 674): xport_reg Failed for service_id=0x35 version=0x1001 on 15
Replace
Code:
[0-9][0-9]-[0-9][0-9] [0-9][0-9]:[0-9][0-9]:[0-9][0-9].[0-9][0-9][0-9] E/QMI_FW ( [0-9][0-9][0-9]): xport_reg Failed for service_id=0x35 version=0x1001 on [0-9]*[0-9]
in the log with your favorite editor which can use regex with nothing (or delete all those lines if you have that option)
Is there another way to get some logs?
In Developer Options, turn on "Local Terminal", and get a logcat or other logs with that.
The screen glitches, is there a way to fix this?
I hope so, working on this too.
After restoring my backup with TWRP, my phone won't recognize my PIN (not SIM PIN). What todo now?
Just follow the guide on here. Afterwards you have to setup your PIN again (also Fingerprints, and enable Trusted Agents in Settings -> Fingerprints & Security)
Download
Version 0.0.2: https://www.androidfilehost.com/?fid=962187416754470110
Version 0.0.1: https://www.androidfilehost.com/?fid=818070582850487924
XDA:DevDB Information
Unofficial LineageOS 14.1, ROM for the LG V30
Contributors
SGCMarkus
Source Code: https://github.com/SGCMarkus
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
Version Information
Status: Testing
Created 2018-01-25
Last Updated 2018-01-25
Changelog
v 0.0.1 Initial build
it boots
v 0.0.2
Mobile data works
Cam works (pictures only)
fixed graphics glitches
Fingerprint works
flashlight works
SDCard is recognized
If you are interested to contribute/help out/test, hit me up in PM, or join my Discord Server: https://discord.gg/DJRnTRC
I set it up to be a general server for all kinds of LG V30 things, but also for Developers to meet and talk to each other, and help each other out.
Downloading...
I'll try to flash it. I'm new on LG devices (come from Samsung...)
It BOOTS
Mike.YT said:
It BOOTS
Click to expand...
Click to collapse
I agree... FC everywhere
But I hope it's a first step...
Exam time here though, so i couldnt really work on this more :/
But i have hope now for actual Treble support (we have a partition called OP, idk how important the stuff in there is though, 344MB if im not wrong, gathered all the Oreo blobs from the V300S kdz (i hope i have all needed ones), and those take up 324MB xD)
But atleast already a working recovery (TWRP 3.2.1) which would recognize the /OP as /vendor
Will work on each project a bit more when exams are over
i don't know if can help someone to build lineage or aosp based rom, btw here are the link to source and kernel for v30:
h930: http://opensource.lge.com/osSch/list?types=ALL&search=h930
us998: http://opensource.lge.com/osSch/list?types=ALL&search=us998
v300: http://opensource.lge.com/osSch/list?types=ALL&search=v300
Here the content of readme:
1. Android build
- Download original android source code ( android-7.1.2_r4 ) from http://source.android.com
( $repo init -u https://android.googlesource.com/platform/manifest -b android-7.1.2_r4
$repo sync -cdq -j12 --no-tags
$repo start android-7.1.2_r4 --all
)
- Untar opensource packages of LGH930_Nougat_Android.tar.gz into downloaded android source directory
a) tar -xvzf LGH930_Nougat_Android.tar.gz
- And, merge the source into the android source code
- Run following scripts to build android
a) source build/envsetup.sh
b) lunch 1
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain) into the android directory.
- After build, you can find output at out/target/product/generic
2. Kernel Build
- Uncompress using following command at the android directory
a) tar -xvzf LGH930_Nougat_Kernel.tar.gz
- When you compile the kernel source code, you have to add google original "prebuilt" source(toolchain) into the android directory.
- Run following scripts to build kernel
a) cd kernel/msm-4.4
b) mkdir -p out
c) make ARCH=arm64 O=./out joan_global_com_defconfig
d) make ARCH=arm64 O=./out CROSS_COMPILE=$(pwd)/../../prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android- KERNEL_COMPRESSION_SUFFIX=gz -j4
* "-j4" : The number, 4, is the number of multiple jobs to be invoked simultaneously.
- After build, you can find the build image(Image.gz) at out/arch/arm64/boot
Click to expand...
Click to collapse
I always loved to know how to build Kernel or ROM.
I'm not a dev so i cannot solve any FC or any other problem, so I need to know where to get the sources.
Little update here, decided to fix LOS14.1 first as 15.1 didnt wanna work at all ?
SGCMarkus said:
Little update here, decided to fix LOS14.1 first as 15.1 didnt wanna work at all
Click to expand...
Click to collapse
heheh don't give up my little dev... We believe in your skill :good:
Also could someone with a US998 test this?
And check what works (and doesnt)? And then send me the logcat (from /data/ramoops) after copying to the sdcard in twrp or whereever before restoring a backup xD
SGCMarkus said:
Also could someone with a US998 test this?
And check what works (and doesnt)? And then send me the logcat (from /data/ramoops) after copying to the sdcard in twrp or whereever before restoring a backup xD
Click to expand...
Click to collapse
I was just getting ready to ask if this will work on US998. If I get a chance I will try it out but I'm not sure how to do the logcat thing sorry.
foamerman said:
I was just getting ready to ask if this will work on US998. If I get a chance I will try it out but I'm not sure how to do the logcat thing sorry.
Click to expand...
Click to collapse
The logcat is taken automatically, as for idk why it wont be recognized via USB... (same kernel as the TWRP, ramdisk and so should also work), just boot into recovery after you used it a bit (if it even boots, otherwise do the button dance), and there, before you wipe/restore a backup, go to advanced -> file manager, browse to /data/ramoops and copy the log in there to the sdcard or whatever else is safe
SGCMarkus said:
The logcat is taken automatically, as for idk why it wont be recognized via USB... (same kernel as the TWRP, ramdisk and so should also work), just boot into recovery after you used it a bit (if it even boots, otherwise do the button dance), and there, before you wipe/restore a backup, go to advanced -> file manager, browse to /data/ramoops and copy the log in there to the sdcard or whatever else is safe
Click to expand...
Click to collapse
OK but now I have another problem TWRP backup failed on me. So if I do install 14.1 and it doesn't boot I have WETA 1.5 I can do the button dance and go twrp and reinstall weta as soon as I get some time I'll will try it.
---------- Post added at 02:45 PM ---------- Previous post was at 02:26 PM ----------
Sorry one more question I'm guessing we need to download our own gapps too yes? so arm64 7.1 pico would be fine that's the least one
foamerman said:
OK but now I have another problem TWRP backup failed on me. So if I do install 14.1 and it doesn't boot I have WETA 1.5 I can do the button dance and go twrp and reinstall weta as soon as I get some time I'll will try it.
---------- Post added at 02:45 PM ---------- Previous post was at 02:26 PM ----------
Sorry one more question I'm guessing we need to download our own gapps too yes? so arm64 7.1 pico would be fine that's the least one
Click to expand...
Click to collapse
Try it without gapps, its not worth to setup all that, it isnt daily driver ready... and gapps would just add more (unneccessary) stuff to the log ^^
--snip--
Well I tryred it but I got error 7 thats all I got
foamerman said:
Well I tryred it but I got error 7 thats all I got
Click to expand...
Click to collapse
Probably because of wrong device, remove the assert line in the updater-script in side the .zip file
(.zip/META-INF/com/google/android/updater-script)
SGCMarkus said:
Probably because of wrong device, remove the assert line in the updater-script in side the .zip file
(.zip/META-INF/com/google/android/updater-script)
Click to expand...
Click to collapse
OK I unzipped the file and deleted the (.zip/META-INF/com/google/android/updater-script) OK now I need a little help I'm a little slow I'm not sure how to zip it back up
Related
[ROM][5.1.1][OFFICIAL] CyanogenMod 12.1 for S3 Neo[LEGACY]
{
"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"
}
NOTE: PLEASE ALSO READ ALL OF THE FAQ IN THE SECOND POST. IT COVERS MANY OF THE COMMON PROBLEMS AND QUESTIONS!
CyanogenMod 12.1 is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lolipop), 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! 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.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod 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. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
The source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Changelog:
https://www.cmxlog.com/12.1/s3ve3g/
Requirements:
Custom recovery (either TWRP or CyanogenMod)
Soon other things will be added
Known Bugs/Issues: (fixed nightly date)
NFC
If camera not working flash this: LINK
Offline charging(02.09.2016)
(Please don't ask ETA for any bug fixes)
Bug reports for this ROM should be officially submitted via CyanogenMod's Jira bug tracking sytstem. Please fully read the FAQ entry on bugs and bug submission before submitting any tickets.
FAQ, other information:
Soon
Download:
https://download.cyanogenmod.org/?device=s3ve3g
Note to users: I'm not responsible if you brick your phone. See the disclaimer above.
Note to admins/moderators: I'm not a developer / contributor of CyanogenMod and not associated with Cyanogen, Inc. in any way. If this thread is inappropriate, please move/delete it.
Thanks to These People:
Zola
@rox
Abhisek Devkota
Samsung Devs
CyanogenMod Devs
XDA:DevDB Information
Cyanogenmod12.1, ROM for the Samsung Galaxy S3 Neo
Contributors
n1kolaa, Zola III
Source Code: https://github.com/CyanogenMod
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Version Information
Status: No Longer Updated
Stable Release Date: 2016-08-22
Beta Release Date: 2015-10-19
Created 2015-09-23
Last Updated 2018-05-14
How to report problem with new kerel or rom?
tonyp said:
We're on a development site - at least in theory.
To help out development without actually having some knowledge it's really important to know how and when to get logs.
Lately more and more people in this section do grab appropriate logs, which is a good thing and has already helped in fixing a bunch of bugs.
To stop (especially new) people from constantly asking how to get logcats I decided to hand out a quick reference on how to grab logs efficiently via adb / terminal / app.
There is an app which can export apps (see the end of this post), but you should learn how to get logs via adb anyways, as a dmesg is often crucial in case of debugging bsods.
I won't post instructions in how to get adb working - you can use Google or take this CM wiki entry as a starting point.
The three most important log types are:
logcat: the logoutput of the Android system
radio logcat: the log outpur ot your System / BB / RIL communication
kernel log (kmsg / dmesg): the kernel messages
Additionally there's the last_kmsg which is a dump of the kernel log until the last shutdown.
Normal Logcat:
Code:
adb logcat -v time -d > logcat.log
Radio Logcat:
Code:
adb logcat -b radio -v time -d > logcat_radio.log
Note: Cyanogenmod (based) ROMs require the following setting to export kernel logs via adb:
Settings - Developer Options - Root access - choose: "Apps and ADB"
Kernel Log:
Code:
adb shell su -c dmesg > dmesg.log
Last_kmsg:
Code:
adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log
For getting the logs via the Terminal Emulator app the commands differ a little:
Get logs via Terminal Emulator:
Normal Logcat:
Code:
logcat -v time -d > /sdcard/logcat.log
Radio Logcat:
Code:
logcat -b radio -v time -d > /sdcard/logcat_radio.log
Kernel Log:
Code:
su -c dmesg > /sdcard/dmesg.log
Last_kmsg:
Code:
su -c "cat /proc/last_kmsg" > /sdcard/last_kmsg.log
Notes:
-v time will include timestamps in the logcats
-d will export the complete log.
If you want to save a continuous log you can remove the -d parameter - then you need to cancel the logging process via CTRL+C.
To export a continuous kernel log use adb shell su -c "cat /proc/kmsg" > dmesg.log (and cancel it via CTRL+C again).
Exporting logs with an app:
I used to recommend Lumberjack for grabbing logs, but it doesn't work with Jellybean properly anymore and fails to export the dmesg.
I googled for a while and found a great (and fully open sourced) alternative to export logs: SysLog
With this great app there are no more excuses - at least open the app, export all 4 log types and attach the zip file from /sdcard/SysLog to your bug report.
Before anyone asks (duh!), Kernel log = dmesg, Last kernel log= last_kmsg, main log = logcat, modem log = radio log.
Lumberjack still is great to have a look at logs on the phone, but for exporting you probably should use SysLog as it does it quickly and reliable
SysLog (source):
Click to expand...
Click to collapse
#o#
tonyp said:
When to post which kind of logs:
If you got any kind of ROM problems - especially problems with Apps like force closes, attach a logcat.
If there are problems while calling or with your signal attach a radio logcat to the normal logcat.
In kernel threads or on issues which might be kernel related (from A as auto brightness to Z as ZRAM) you need a kernel log
If you had a sudden reboot attach a last_kmsg, then we can check if it's been kernel related
As our phone has always been on the edge of bsod's and freezes, some special notes about them as well:
If you had a bsod and/or freeze a logcat dmesg after rebooting is useless, as it doesn't show anything from before the reboot
There are two things you can do:
While the phone's screen is black connect the cable to your computer and check if the device is accessable via adb (check e.g. with "adb devices").
If it is export the dmesg like explained above. If not go on to step 2:
Note that two of the bsod problems of the ICS/CM kernel have been fixed by pengus by the logs I managed to get while the phone has been in a bsod - which means this is crucial!
Pull the battery and insert it again as quickly as possible. Why? The phone does hold a so called last_kmsg in RAM.
It's non-permanent memory, which means it doesn't survive a loss of power - sometimes we're in luck by a quick pull though.
If we're not in luck the file will be empty or contain scrambled characters.
Last but not least some general remarks:
If you don't provide useful logs we can not help you in 95% of the cases in case we can't reproduce it.
Buf even if we could reproduce it - let's assume one of YOUR apps is force closing. Why should we install the app to reproduce the problem and get the logs ourselves.
YOU want help, so YOU should provide the log.
Every real dev with some coding knowledge will need logs to fix the bugs.
This site is called xda-developers - which means that the initial intention of this forum is the actual development itself - and not "making your phone cool".
The least you can (and must) do is to provide useful help with a clear problem description and attached logs when you run into some issues
Click to expand...
Click to collapse
Donations for s3 dual sim
Use "Send payment" option on paypal
@Ahmad Tawfik: 1,62 USD; 1,18 USD
@S3-Neo 5 USD
@naik2902 6.00 USD
@aelfinn 5.51 USD
@St.Ungulant 5.49 USD
Ulrich 10.99 USD!
@Droidaner 13.49 US
I need about 50 euros for used dual sim phone
FAQ POST
Q: When you will realse CM13.0?
A: DON'T ASK FOR ETA(ETA = Estimated Time of Arrival)
Reserved #2
Is offline charge working with this kernel?
Edit:
sorry but I did not read the 1st post
Everything is fine
Installed and booted without issue. Kernel seems to be changed. :good: :highfive:
Is that working on Resurection Remix 5.5.6 ?
Removed
Ahmad Tawfik said:
Offline charge isn't working for me
Click to expand...
Click to collapse
Read OP...
" ##Bugs:##
no bugs so far(offline charging like cm12.1) "
Btw thanks n1kolaa!
Zokhii said:
Read OP...
" ##Bugs:##
no bugs so far(offline charging like cm12.1) "
Btw thanks n1kolaa!
Click to expand...
Click to collapse
I hope you like it
Np It will be assome to rate it 5 starts and make review.
ahmo67 said:
Is that working on Resurection Remix 5.5.6 ?
Click to expand...
Click to collapse
if its based on cm12.1 it shoud.
Take a backup if you not shure.
Mediafire folder is empty for me
jad88 said:
Mediafire folder is empty for me
Click to expand...
Click to collapse
https://www.mediafire.com/folder/3c3y68hehuv9t/n1kernel
MediaFire links not working...
n1kolaa said:
https://www.mediafire.com/folder/3c3y68hehuv9t/n1kernel
Click to expand...
Click to collapse
It's the same... Maybe it's my browser
Is this kernel base on Rox kernel?
And can you add this future for color calibration --> http://forum.xda-developers.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080
We need this futures.
---------- Post added at 01:48 PM ---------- Previous post was at 01:34 PM ----------
jad88 said:
It's the same... Maybe it's my browser
Click to expand...
Click to collapse
Download one buy one !
Sectorian said:
Is this kernel base on Rox kernel?
And can you add this future for color calibration --> http://forum.xda-developers.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080
We need this futures.
---------- Post added at 01:48 PM ---------- Previous post was at 01:34 PM ----------
Download one buy one !
Click to expand...
Click to collapse
I wont add it. Its based on Rox kernel
I had to login to my mediafire account. It works on latest RR. (Flashed with flashify)
Sorry, one question. If i flash your kernel, did i lose my data?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
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.
You will need to provide your own Google Applications package (gapps).
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 our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for unofficial LineageOS 13.0 builds for LG G4 model H815 only.
Its a continuation of the official one as it was abandoned back in July and I still prefer MM (N has still bugs and does not support encryption).
Known issues:
the kernel has security bugs which need to be addressed
its in testing state as I cant test it atm.. please report back! PLEASE MAKE A FULL BACKUP BEFORE TESTING!!
Installation:
First time flashing LineageOS 13.0 on your device, or coming from another ROM?
Download the zip(s)
Install latest TWRP from the official twrp.me website
Perform a nandroid backup of your current ROM (optional but recommended)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package, install the SU addon package(https://download.lineageos.org/extras, choose arm64)
Reboot
Download:
Google Apps:
OpenGApps (choose arm64, 6.0, nano)
TWRP Recovery:
https://twrp.me/devices/lgg4.html
Full Stock ROMs:
H815 V20D
Bootloader:
Remember ---> Flashing bootloader is risky so you flash at your own risk!
H815 V20D
Modem:
H815 V20D
ROM:
Last known fully working is 20170813! Sorry have to fix the blobs first!
Nightlies: http://droid.binbash.it
Sources:
Android: https://github.com/LineageOS
Device: https://github.com/steadfasterX/los_android_device_lge_h815
Kernel: https://github.com/LineageOS/android_kernel_lge_msm8992
G4 common device tree: https://github.com/LineageOS/android_device_lge_g4-common
Proprietary files: https://github.com/TheMuppets/proprietary_vendor_lge
.
XDA:DevDB Information
lineage-13.0-unofficial, ROM for the LG G4
Contributors
steadfasterX, codeworkx, genesixxbf3
Source Code: https://github.com/steadfasterX/los_android_device_lge_h815
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Bootloader unlocked, v20A (or greater) bootloader stack
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2017-08-21
Created 2017-08-21
Last Updated 2017-11-03
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
{
"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 @nailyk!
Notice: Thread missing information/ credits/ mentions/ stuff etc etc. Work in progress.
All credit for this ROM must go to Nailyk as the main developer of Omni for Leo devices. I am just a tester / thread maintainer for Leo (Z3).
Disclaimer:
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Who can use it?:
This ROM is only for Xperia Z3 users with UNLOCKED and (preferably) UPGRADED bootloaders!
How to install:
%= Only needed at first flash
% Update ROM to .291 with emma (or Flashtools)
% When install is done go into fastboot mode (plug usb + vol down key = blue led)
% Flash this TWRP (version 3.1.x)
Shutdown the device
Unplug the usb cable
Maintain volume down & power until you see twrp splash screen / wait for purple LED on boot and press volume up key
% Wipe system, cache and data
Install rom zip (+ % gapps if you need it)
Reboot
(After first boot if you have initial issues try a second reboot and see if it stops. If not, clean install)
Rolling back to stock:
- Flash stock rom with emma or flashtool
If you flash with flashtool remember to check wipe apps_log and userdata partitions to get a clean install
TWRP:
See Nailyk's TWRP build here for best compatibility (based on Omni sources):
TWRP 3.1.x-x
GAPPS:
Flash any 7.1.2 compatible Gapps package. I suggest OpenGapps.
Alternatively Microg and fdroid will serve you well as an alternative to Google Play Services.
Releases:
Latest:
2017-12-13: Android File Host Download
Mirror: releases.nailyk.fr/omnirom
Change Log: CVE Patches
TWRP 2017-11-21: Android File Host Download
Previous:
2017-12-02: Android File Host Download
Change Log: Fixed scripts for modem files at first boot. No issues with SIM detection, manual script running etc now.
2017-11-21: Android File Host Download
Change Log: Updated Security Patches to latest. No change to ROM.
2017-10-17: Android File Host Download
Change Log:
Code:
Lot of important changes here,
- Device was renamed z3 instead of leo,
- This release ""should"" support all leo variants. However, the script is on early stages: expect troubles.
In case of problem with RIL process the following:
Reboot into recovery,
connect to shell then:
Code:
mount /system
ln -s /system/vendor/etc /vendor/etc
sh /system/etc/init.blobs.sh
This build is patched against wpasupplicant attack (krackattack)
Some improvements about external sdcard & charging.
2017-09-28: Android File Host Download
MD5 Sum: b431c2c720be4a4dfd365a8343ca8115462a3393
Root etc:
For root it is suggested that you see phhSuperUser here: phhSuperUser Thread
Flash options such as Magisk or SuperSU if you wish, but there is not guarantee of support. Magisk 14.0 was tested by myself and working at first release.
Contributors:
@nailyk,
@xkeita, @tomascus, @derf elot, @TheavenginTitan
@tomgus1, @gr8st, @mcgi5sr2, @doriandiaconu, @Robot76, @panzerox123
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: OmniROM
Version Information:
Status: Beta
Logs:
This post will describe how to take logs.
If you are using the ROM and want to make development faster/ easier please simply take a log and post it here in the thread for us to check out.
Take logs when you notice bugs etc and try to reproduce them when taking the log and give us some description of the problem.
First you will need ADB:
Set up any adb environment on you PC (showing windows here for eg.- Linux/ Mac differs):
- For windows a minimal installation will be enough to take logs and takes 15 seconds.
15 second ADB Installer
Then open the folder it is installed to so you see "adb.exe" (obviously different on Linux/Mac).
Open and CMD window in the folder with adb and you can connect your phone.
Enable USB Debugging on the phone!:
Go to Settings - About Phone - Build Number (tap this until Developer options unlocks)
Go to Developer Options and enable "USB Debugging".
Now take the actual logs running adb logcat:
- Back to the PC CMD window.
- When you run the command a window will pop up on the phone asking for access. Say yes.
- Run the command - " adb logcat > logcat.txt "
- This will give you a text file with the log to post to us.
If possible take a dmseg /kmsg:
This is most useful for bootloops etc
You may need root on the device to access these:
- " adb shell su -c dmesg > dmesg.log "
- " adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log "
Screenshots
Screenshots thanks to @Tux111. Find some of his comments and hit thanks for him!
Full showcase of screenshots here: MEGA
What working?
@Dobsgw When you will update missing informations, could you please share informations about changelogs, what works, whats not, special features and some screenshots?
All the users (me too) will appreciate a lot.
I'm gonna get the info on the changes and features etc at some point later this week.
For now all I know is the build is beta but working very well. You all know Nailyk has a very high standard of work.
The current version I have installed is working as normal and since this morning (when I installed) I've seen no issues.
If you have some time it's worth checking out.
For features etc see the Omni ROM website
Dobsgw said:
I'm gonna get the info on the changes and features etc at some point later this week.
For now all I know is the build is beta but working very well. You all know Nailyk has a very high standard of work.
The current version I have installed is working as normal and since this morning (when I installed) I've seen no issues.
If you have some time it's worth checking out.
For features etc see the Omni ROM website
Click to expand...
Click to collapse
Mobile Data don't work. Every time i try to set APN, it automatically disappear. No way to make SIM data work.
The rest of the ROM is kinda awesome, some little bugs but really nicely done. Ah, message app miss. Add it please.
You probably know already but there is no link to TWRP 3.1.x for Z3 and Z3 dual (can be found in xkeita thread of Lineage 14)
Tux111 said:
Mobile Data don't work. Every time i try to set APN, it automatically disappear. No way to make SIM data work.
The rest of the ROM is kinda awesome, some little bugs but really nicely done. Ah, message app miss. Add it please.
Click to expand...
Click to collapse
Please provide full rom log, dmesg & radio log.
What variant? This rom is not dual ready yet.
tiliarou said:
You probably know already but there is no link to TWRP 3.1.x for Z3 and Z3 dual (can be found in xkeita thread of Lineage 14)
Click to expand...
Click to collapse
Xkeita TWRP is fine.
Nailyk also has a brilliant TWRP version found here in the forum.
It is updated to latest just ignore the title. 3.1.1-3
nailyk said:
Please provide full rom log, dmesg & radio log.
What variant? This rom is not dual ready yet.
Click to expand...
Click to collapse
D6603 single SIM.
Can't provide right now, sorry.
EDIT: I'll provide it soon as possible!
How i have to make radio log?
nailyk said:
Please provide full rom log, dmesg & radio log.
What variant? This rom is not dual ready yet.
Click to expand...
Click to collapse
I figured out mobile data work. But there is a bug, inside APN configuration, that automatically delete the APN created if you modify a string inside and after save it.
This time i simply used default APN settings, without modifying anything a part APN "Name" and "APN" and it works.
Here there is the logcat of the bug (over 1 mb can't upload here).
https://mega.nz/#!YAUXUSaA!3w6IWURIGvsHU-Cm9IkFStOsmyj67Sxvt9tbqqD2mG8
Tux111 said:
I figured out mobile data work. But there is a bug, inside APN configuration, that automatically delete the APN created if you modify a string inside and after save it.
This time i simply used default APN settings, without modifying anything a part APN "Name" and "APN" and it works.
Here there is the logcat of the bug (over 1 mb can't uploader here).
https://mega.nz/#!YAUXUSaA!3w6IWURIGvsHU-Cm9IkFStOsmyj67Sxvt9tbqqD2mG8
Click to expand...
Click to collapse
Thank you for taking the time to look into this.
Hopefully not a big issue
Mobile data D6603 german working LTE
Sent from my unknown using XDA-Developers Legacy app
edit
New twrp works fine and omnirom build too! Thx for hard work! ? Greets from German
Sent from my unknown using XDA-Developers Legacy app
App not using SD card photo ecc
Inviato dal mio unknown utilizzando Tapatalk
my BL is unable to get unlocked. but im now on .291 rom and rooted and twrp installed. is there nothing i can do to taste the full working nougat?
what will happen if i flash it onto my device (in this case, the BL is still locked. bootloader unlock allowed : no )
thanks.
leo31 said:
my BL is unable to get unlocked. but im now on .291 rom and rooted and twrp installed. is there nothing i can do to taste the full working nougat?
what will happen if i flash it onto my device (in this case, the BL is still locked. bootloader unlock allowed : no )
thanks.
Click to expand...
Click to collapse
You will have a brick.
Nothing you can do when unlock allowed:no.
The only thing is to contact sony, it is illegal (in some countries) to have an unlockable bootloader.
The images and most of the files do not use the sd card and when you want to pass applications to the system it does not allow attachment screenshot.
You could also add the option to expand the desktop and resize the navigation bar.
{
"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.
*/
About LineageOS:
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (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 Suicide Squirrel and LineageOS Github repos.
If you would like to contribute to do not hesitate to submit patches
**** These builds are for UsU'd devices only ****
UsU? http://bit.do/unlockg4
Requirements
Your device need to be unlocked by UsU
Your bootloader stack should be on MM 20p or higher! (see FAQ #20 for how to upgrade your bootloader stack)
Latest TWRP - PREVIEW build: click
Clean modem partition (so no UsU baseband flashed) - see Installation topic for details
Installation
If you have ever flashed the UsU baseband package: Clean flash the modem partition in TWRP:
- TWRP flashable N modem (recommended)
Full wipe like described here (click & go to FAQ "#zzz") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash LOS
Flash GApps (8.1 - ARM64) if you like to use google apps
Flash SuperSU / Magisk if you want root
Boot (will take long on first boot!)
Enjoy
Download
Get your builds from my leech server
http://leech.binbash.it:8008/lineage/oreo/h815-UsU/
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.
Known issues:
Check the current issues at the github tracker (feel free to help, provide logs etc!)
Credits
LineageOS
ThePiGuy
kessaras
steadfasterX
and more..
Sources
LineageOS
Kernel
device tree
build manifest
XDA:DevDB Information
lineage-usu-h815, ROM for the LG G4
Contributors
steadfasterX, ThePiGuy, kessaras
Source Code: https://github.com/Suicide-Squirrel/local_manifests/tree/los-15.1
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 20p or higher firmware
Based On: pure LineageOS
Version Information
Status: Beta
Created 2018-06-20
Last Updated 2019-07-10
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?
{
"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:
/*
* 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.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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.
Working:
It boots
WiFi
Bluetooth
Camera
Navigation Keys
Fingerprint
Sensors
GPS
RIL
SDCard
Headphones
Ringtones
Bluetooth audio
Known bugs
WiFi Hotspot
Selinux permissive
Stock LOS recovery doesn't boot
Dual SIM
You tell me
Install instructions
Flash the newest T-Virus release (if you have already installed T-Virus, reflash the newest release it contains a fix to TWRP)
After T-Virus has flashed and it has booted to the Android 10 GSI test environment, type this command to reboot to recovery mode
Code:
adb reboot recovery
Once in recovery, copy the Lineage OS zip file to the internal storage
Go to the Install section and flash the Lineage OS zip
After the zip has flashed, go to Wipe->Advanced Wipe, tick the "Dalvik /ART Cache" and "Data" boxes and wipe them
Head to Wipe->Format Data and type yes to format the data partition
Finally go to the Reboot section, select Slot B to switch to the flashed slot and then to System and swipe to reboot
Profit?
OpenGApps/Magisk:
After the ROM successfully boots up, many of will will want to install Magisk and/or OpenGApps. To do that you need to install the latest TWRP release
Code:
adb reboot bootloader
fastboot flash:raw boot --slot=all twrp-3.4.0-0-NB1.img
fastboot reboot
After that reboot to recovery, flash OpenGApps and/or Magisk. If you flash OpenGApps don't forget to wipe the data partition to prevent Google Setup from crashing
Downloads
T-Virus: https://forum.xda-developers.com/nokia-8/development/t-virus-infect-nokia-8-project-treble-t3946249
ROM: https://github.com/GPUCode/android_device_nokia_nb1/releases
TWRP: https://forum.xda-developers.com/nokia-8/development/recovery-twrp-3-4-0-0-nb1-t4187679
Notes:
Only Clean Installation Please
Bug Report Without logs means nothing
Magisk is untested
In case you flashed any gapps, re-flashing is needed if you're updating the ROM
Reporting Bugs:
DO NOT Report bugs if you installed Xposed or weird magisk modules
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
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. Any bug not reported in the bug report format below may be ignored.
Sources:
Device tree (Common): https://github.com/GPUCode/android_device_nokia_msm8998-common/tree/lineage-17.1
Device tree (NB1): https://github.com/GPUCode/android_device_nokia_nb1/tree/lineage-17.1
Kernel: https://github.com/resident-nokia/umbrella
Vendor tree: https://github.com/GPUCode/proprietery_vendor_nokia/tree/lineage-17.1
XDA:DevDB Information
LineageOS 17.1 for NB1, ROM for the Nokia 8
Contributors
THMSP, OneWayGamer, oaid
Source Code: [url]https://github.com/LineageOS[/URL]
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Beta
Created 2020-11-03
Last Updated 2020-11-03[/QUOTE]
Reserved
You gotta be kidding me... @emufan4568
Are you the maintainer? Great work, appreciations.
Should Selinux permissive be considered as BUG? It's a state with its own properties...
Camera is not mentioned to be working or not.
Finally it's here ! Great work :good:
Hopefully I'll be able to use it on a daily basis soon :victory:
Thank for great work sir
Wow great work I knew that you could do it!
How To Install
Help I Cant Install
sdbadshah said:
Help I Cant Install
Click to expand...
Click to collapse
Please go into more detail about the issue you are facing. Just saying "I need help" won't solve anything. Keep in mind this ROM is still beta so expect bugs and crashes
emufan4568 said:
Please go into more detail about the issue you are facing. Just saying "I need help" won't solve anything. Keep in mind this ROM is still beta so expect bugs and crashes
Click to expand...
Click to collapse
The problem with me is i cant understand the method to install iam following the process showed on github but whenever i enter command its says No Such File Dictionary
---------- Post added at 10:09 PM ---------- Previous post was at 09:59 PM ----------
emufan4568 said:
Please go into more detail about the issue you are facing. Just saying "I need help" won't solve anything. Keep in mind this ROM is still beta so expect bugs and crashes
Click to expand...
Click to collapse
And Also My Device Is stucked Into Fastboot mode because i have entered this comand fastboot erase boot_a
after this command iam entering fastboot flash:raw boot_a /path/to/boot.img
but its giving error
---------- Post added at 10:26 PM ---------- Previous post was at 10:09 PM ----------
Now Need Some Help To Install Twrp For Gapps
sdbadshah said:
The problem with me is i cant understand the method to install iam following the process showed on github but whenever i enter command its says No Such File Dictionary
---------- Post added at 10:09 PM ---------- Previous post was at 09:59 PM ----------
And Also My Device Is stucked Into Fastboot mode because i have entered this comand fastboot erase boot_a
after this command iam entering fastboot flash:raw boot_a /path/to/boot.img
but its giving error
---------- Post added at 10:26 PM ---------- Previous post was at 10:09 PM ----------
Now Need Some Help To Install Twrp For Gapps
Click to expand...
Click to collapse
You have to replace "/path/to/boot.img" with the path of the file on your computer... If your prompt is already in the same folder than your files are then just put the filename and it should be ok...
Actually I'm not sure if you should install this ROM as you don't really sound familiar with command prompt, you'd better wait for a stable release as it's just intended for testing.
Bgirka13 said:
You have to replace "/path/to/boot.img" with the path of the file on your computer... If your prompt is already in the same folder than your files are then just put the filename and it should be ok...
Actually I'm not sure if you should install this ROM as you don't really sound familiar with command prompt, you'd better wait for a stable release as it's just intended for testing.
Click to expand...
Click to collapse
Yup iam New Into It But I hAve installed Succecfully But Now What about gapps,How Can I Install Twrp,I Have tried to boot into twrp without Installing But Its Stuck On Powered By Andriod
sdbadshah said:
Yup iam New Into It But I hAve installed Succecfully But Now What about gapps,How Can I Install Twrp,I Have tried to boot into twrp without Installing But Its Stuck On Powered By Andriod
Click to expand...
Click to collapse
The boot command does not work for the Nokia 8. You have to flash T-virus TWRP, then flash OpenGApps, reboot to download mode again and then type "fastboot format userdata" to prevent the Google Setup from crashing. Please read the whole thread before asking any questions
So... I used the rom for a few hours, played with settings, captured some videos and pictures, etc. Controls over buttons amazed me. Camera was good (I didn't have access to pc to compare in detail, but lower volume of photos was apparent, it could be because of higher compression or else), better than stock (except for interface!). Long story short, I came back to stock just for one thing, the ringtones. It looked like that there is some problem with their properties which is preventing usability. Rest is pure awesome.
P.S. (about stock packages) offline ota updates provided by @THMSP (specifically 488L for 488K!) don't seem to work. Also 5.15x firmwares (above 5.150) have problems in their system image file. Their offline updates don't seem to work either.
emufan4568 said:
The boot command does not work for the Nokia 8. You have to flash T-virus TWRP, then flash OpenGApps, reboot to download mode again and then type "fastboot format userdata" to prevent the Google Setup from crashing. Please read the whole thread before asking any questions
Click to expand...
Click to collapse
what's fastboot command to install TWRP, I don't know how to install it.
dongvatm said:
what's fastboot command to install TWRP, I don't know how to install it.
Click to expand...
Click to collapse
You need to use the :raw tag with flash. Running fastboot flash:raw boot_a twrp_treble.img work for me
Arashone said:
So... I used the rom for a few hours, played with settings, captured some videos and pictures, etc. Controls over buttons amazed me. Camera was good (I didn't have access to pc to compare in detail, but lower volume of photos was apparent, it could be because of higher compression or else), better than stock (except for interface!). Long story short, I came back to stock just for one thing, the ringtones. It looked like that there is some problem with their properties which is preventing usability. Rest is pure awesome.
P.S. (about stock packages) offline ota updates provided by @THMSP (specifically 488L for 488K!) don't seem to work. Also 5.15x firmwares (above 5.150) have problems in their system image file. Their offline updates don't seem to work either.
Click to expand...
Click to collapse
Ringtones, Headphones and NFC have been fixed. New build will be up soon
Awesome work man! I have a suggestion, make a modified T-virus with LineageOS bundled with it. I'll start working on AIO 2.0 for Treble soon
Suggestion: Use Google Drive to upload rom files. Github is painstakingly slow af for me, while others work just fine. Please do something about that
My wifi will not work, installed following instructions works fine except for wifi. Phone is TA-1012
New release is up! Download from here: https://github.com/GPUCode/android_device_nokia_nb1/releases/tag/v1.1 Fixes include:
* Headphones
* Ringtones
* Bluetooth audio
* NFC
Now the release comes with a TWRP flashable package. The thread has been updated with new installation instructions