Instructions:
0. Make sure your bootloader is unlocked
1. Download ROM zip from the link below, and grab Magisk patched boot.img inside the folder as well if you want root access
2. Reboot to bootloader
2.5. Flash updated bootloader.img and radio.img from Google site
3. Use `fastboot -w update LineageOS_microG-bramble-(BUILD DATE HERE)-userdebug-signed.zip` to flash
and yes, you can omit the "-w" parameter if you're not flashing for the first time, aka just updating from previous release
4(optional). Hopefully after flashing you'll be booted into LineageOS, reboot to bootloader again,
and flash the Magisk patched boot.img extracted from the 7z file with `fastboot flash boot magisk_patched.img`,
reboot after finished
5. Enjoy!
Click to expand...
Click to collapse
Download from GitHub Release page
Download(MEGA, won't be updated anymore)
Features:
1. MicroG integrated nicely (Thank OmniROM dev([email protected]) for the repo)
2. Replaced default WebView with Bromite WebView
3. Default DNS was set to UncensoredDNS in framework overlay
4. Removed unnecessary prebuilt APKs
Click to expand...
Click to collapse
Contacts:
Telegram:
Channel for Pixel 4a 5G related stuff
Group for Pixel 4a 5G discussion
Contributors
dic1911
ROM OS Version: Android 12
ROM Kernel: Linux 4.x
ROM Firmware Required: Current
Based On: LineageOS
Version Information
Status: Testing
Created 2021-12-19
Known Issue
1. SMS messages not receiving (Fixed in 2021/12/27)
2. No network access for apps installed in work profile (Looks like ROM side bug, still investigating)
How do I install for the first time? Please help me
trongcccc said:
How do I install for the first time? Please help me
Click to expand...
Click to collapse
Where are you up to? Have you unlocked the boot loader, as per - https://wiki.lineageos.org/devices/bramble/install
I'm running into my pixel 4a5G in a boot loop. I downloaded the wrong lineage product, forgetting that I have A-12. duh.
Just a quick head up, SMS message functionality isn't working in initial build, it's fixed in latest build (2021/12/27)
Hello! Mind elaborating on this step? Thanks!
2.5. Flash updated bootloader.img and radio.img from Google site
(What Google site? Do you have a URL? Specific version?)
kevin71246 said:
Hello! Mind elaborating on this step? Thanks!
2.5. Flash updated bootloader.img and radio.img from Google site
(What Google site? Do you have a URL? Specific version?)
Click to expand...
Click to collapse
Official factory firmware, any version as long as it's Android 12 and for your phone.
Quick question, is this just using the lineage 18.1 device trees or?
EDIT: Nvm i saw the 19 branch
Hey quick question, how do you package the finished build as a bunch of images?
A little heads up, initial build for Lineage 19.1 is now up, without Bromite System WebView for now.
Another build is up, now with Bromite Webview and April security patch!
How do I get support for this 19.1 version? I tried the official Lineage channels but they told me they do not support. I downloaded and installed from here:
LineageOS for microG
lineage.microg.org
nanu.nanu said:
How do I get support for this 19.1 version? I tried the official Lineage channels but they told me they do not support. I downloaded and installed from here:
LineageOS for microG
lineage.microg.org
Click to expand...
Click to collapse
I doubt anyone really provide extra support for that as they're mostly just grab existing LOS stuff and build without further effort afaik.
Related
Hi ,
About:
This is an unofficial 6.0x build of Blisspop compiled using caf source from sultanXDA.
Changes from official build:
--
Code:
All sultanXDA's patch[/color][/b]
--
Code:
SnapdragonCamera[/color][/b]
--
Code:
android_hardware_qcom_media
-
Code:
android_hardware_qcom_display
-
Code:
android_hardware_qcom_audio
-
Code:
android_kernel_oneplus_msm8974
-
Code:
proprietary_vendor_oneplus
-
Code:
proprietary_vendor_oppo
-
Code:
android_frameworks_base
-
Code:
android_frameworks_av
Source used:
1.https://github.com/BlissRoms
2.https://github.com/sultanxda/android_kernel_oneplus_msm8974
Credits:
-sultanXDA
-Blisspop team
-XDA
-Google
Let me know if i have missed any of you .
Latest Download(08/02): (Refer the second post for the older builds)
Blisspop_CAF_MM_08/02
Screenshots:
Uploading..
XDA:DevDB Information
Blisspop, ROM for the OnePlus One
Contributors
Vivek_Neel
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2016-01-20
Last Updated 2016-02-07
Changelog:
V8:
Here
V7:
Here
V6:
Here
V5:
Here
V4:
Here
V3:
Here
V2:
Here
V1 :
Initial release
Older Builds:
Blisspop_CAF_MM_19/01
Reserved
Just in case..
Happy To see bliss marshmallow first caf build
Downloading
Will tell u bugs after testing ?
is it necessary to use latest firmware ?
i mean this :
CM 30/12 from jgcaap
Will give it a test run later today. Looking for something to update to and test.
@Vivek_Neel
Mate...Bliss for MM called Bliss 6.0 and i think you need to drop the *Pop* in your first post + the thread title too just to avoid some confusion...peace
...thread sub/
storm119 said:
@Vivek_Neel
Mate...Bliss for MM called Bliss 6.0 and i think you need to drop the *Pop* in your first post + the thread title too just to avoid some confusion...peace
...thread sub/
Click to expand...
Click to collapse
Yeah sure mate. Will do once i am on my laptop
Is it 6.0 or 6.0.1 ?
shield1331 said:
Is it 6.0 or 6.0.1 ?
Click to expand...
Click to collapse
6.0.1
Just flashed the ROM booted up fine thanks for ROM vivek
Check your inbox when you have a sec bud
Does Bliss6 support encryption?
EDIT: Flashed on top of an already-encrypted device and it decrypts and works just fine.
Blisspop, my favourite lollipop Rom. Now I'm on Temasek 6.0 (CAF) but I will try this one in a few days. Excellent work Vivek_Neel.
Vivek_Neel said:
Older Builds:
Click to expand...
Click to collapse
lol, you should update the OP )
1. refer to post #3 for older builds
2. is the 20160120 latest or "Latest Download(19/01)"
3. nice job, been waiting for this one
Thanks a lot :angel:
Thanks for porting BP to MM!
So I had the last CAF build flashed and decided to upgrade with this rom and had the oppo.verify_trustzone error. Followed instructions posted on Cm13 thread here and it is booting fine
Here are the instructions I used:
If you get an error when trying to install ("oppo.verify_trustzone" error), then first you must install/use TWRP recovery 2.8.6.0 (TWRP 2.8.7.0 cannot properly update the modem). Next, download and flash the latest official CM13.0 nightly. Then, without rebooting from recovery, wipe /system and flash my ROM. This process is necessary to update various firmwares (including TrustZone), as the updated firmware is needed by my ROM. After flashing my ROM, flash a Google apps package, and then reboot.[/COLOR]
Installation instructions (for updating to a newer release):
If you are already running my CM13.0 ROM, then you can update to a newer version of the ROM via the built-in OTA updater or by simply dirty-flashing the new ROM build without wiping anything. HOWEVER, do NOT reinstall Google Apps after installing a new update.
Click to expand...
Click to collapse
flashed open gapps and it booted fine, let it sit for 5 minutes after boot, rebooted in to recovery, and flashed Xposed-v79-sdk23-arm.zip.
Restarted phone and it stuck in bootloop
went back into recovery, sideloaded xposed uninstaller, wiped cache and it boots again.
miss the custom pattern unlock too
OP feel free to continue these builds if you like. OPO builds from source with no issues now but I have no problems with you building unofficial. However if you would like to contribute to the OPO source just let me know via PM and we can get you sorted out.
Just messing with optimization routines and toolchains now. Thank you for all your help man! The team thanks you as well!
ahb83 said:
Thanks for porting BP to MM!
So I had the last CAF build flashed and decided to upgrade with this rom and had the oppo.verify_trustzone error. Followed instructions posted on Cm13 thread here and it is booting fine
Here are the instructions I used:
flashed open gapps and it booted fine, let it sit for 5 minutes after boot, rebooted in to recovery, and flashed Xposed-v79-sdk23-arm.zip.
Restarted phone and it stuck in bootloop
went back into recovery, sideloaded xposed uninstaller, wiped cache and it boots again.
miss the custom pattern unlock too
Click to expand...
Click to collapse
I think you will need newer version of twrp for this MM Rom:
http://build.twrp.me/twrp/twrp-2.8.7.1-bacon.img
RBwai said:
I think you will need newer version of twrp for this MM Rom:
http://build.twrp.me/twrp/twrp-2.8.7.1-bacon.img
Click to expand...
Click to collapse
didn't realize a new one was out, but that did the trick. updating to new one now.
Thanks
LineageOS14.1 (Nougat) unofficial builds for the Droid Razr
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.
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 any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
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.
These are WIP builds of porting LineageOS 14.1 to the Droid 4 (and also other devices using the same device/motorola/omap4-common-infrastructure). They probably won't work, so don't expect too much. Use on your own risk!
Builds:
Current official builds:
https://download.lineageos.org/spyder (Droid Razr)
https://download.lineageos.org/umts_spyder (Razr)
(When migrating from Lineage unofficial, flash this first (manually mount /data in TWRP before flashing and unmount it afterwards) and then directly flash the new image without rebooting)
Su addon for official builds: http://droid.cs.fau.de/lineage-14.1/addonsu/ (The official addon doesn't currently install on Omap4)
Manual beta builds:
http://droid.cs.fau.de/lineage-14.1/
Changes (only device/family specific, CM base is always synced before build and contains more changes):
2017-06-10:
Hotspot fixed
Security updates
CM base updated
Last build before enabling official builds
2017-05-15:
Security updates
CM base updated
2017-04-11:
Fixed mobile data on Verizon
2017-04-05:
DRM playback fixed
2017-04-04:
Camcorder working, thanks to @Android-Andi (thumbnail picture is still wrong, but recorded video seems fine). This probably also fixed other media-related issues.
CM base updated
2016-11-27:
CM base updated
2016-11-13:
SELinux is enforcing
PackageInstaller works on ext3-based userdata again
2016-11-05:
First build
What's working:
Phone (tested on Verizon and on GSM/UMTS in Europe)
Mobile data
WiFi
GPS
Camera
Video recording
Playback of DRM-protected content
Reboot to recovery
What's not working:
Probably most everything else, including, but not limited to:
HDMI
Data encryption (investigating, needs new unreleased safestrap)
Gapps:
OpenGApps
If you install Gapps after the ROM has been booted for the first time you either need to wipe data or manually delete /data/system/users/0/runtime-permissions.xml and reboot. Without this Gapps will crash constantly. This is due to a new permissions-system introduced in Marshmallow.
Installation:
You need a recovery supporting SELinux
A version of Safestrap (3.75) which supports SELinux can be found here: https://github.com/stargo/android_packages_apps_Safestrap/releases/tag/v3.75
A newer version of safestrap which will format userdata as ext4 will be released shortly. You can also just reformat userdata to ext4 in the old Safestrap for now.
Please read the instructions on how to install this version and follow the order of the steps in it.
GSM users with XT912:
These versions (both unofficial and official) automatically switch to GSM/UMTS without installing additional patches.
Source / Repositories:
spyder device-support: https://github.com/LineageOS/android_device_motorola_spyder/tree/cm-14.1
umts_spyder device-support: https://github.com/LineageOS/android_device_motorola_umts_spyder/tree/cm-14.1
omap4-common device-support: https://github.com/LineageOS/android_device_motorola_omap4-common/tree/cm-14.1
omap4-common kernel: https://github.com/LineageOS/android_kernel_motorola_omap4-common/tree/cm-14.1
local manifest to build cm-13 for the Motorola Omap4 devices: http://droid.cs.fau.de/lineage-14.1/local_manifest.xml
XDA:DevDB Information
LineageOS 14.1 for Motorola Droid Razr, ROM for the Motorola Droid RAZR
Contributors
stargo, Hashcode, joojoobee666, Dhacker29
Source Code: https://github.com/CyanogenMod
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2017-06-10
Created 2016-11-13
Last Updated 2017-06-23
Thank you so much stargo what gapps do you use the pico ones ?
tydiamond11 said:
Thank you so much stargo what gapps do you use the pico ones ?
Click to expand...
Click to collapse
The 7.1 Pico work perfectly.
Sent from my Motorola XT912 using XDA Labs
Bobcus Leper said:
The 7.1 Pico work perfectly.
Sent from my Motorola XT912 using XDA Labs
Click to expand...
Click to collapse
I figured out that i was trying to use stock slot lol
Thank you so much guys for remembering razr i hope we will go a long way with you and with razr.
Do you think there is any hope that the bug the RAZR has had since CM 10.2 (that prevents video uploading) could be fixed on Nougat? And if not, is there anyone who knows why it doesn't work?
Thank you for this ROM @stargo :good:
Does it include a kernel image? I could not find it from http://droid.cs.fau.de/cm-14.1/cm-14.1-20161113-UNOFFICIAL-spyder.zip
heroxbd said:
Does it include a kernel image? I could not find it from http://droid.cs.fau.de/cm-14.1/cm-14.1-20161113-UNOFFICIAL-spyder.zip
Click to expand...
Click to collapse
Yes, all CM based ROMs include kernels.
Sent from my Motorola XT912 using XDA Labs
Bobcus Leper said:
Yes, all CM based ROMs include kernels.
Sent from my Motorola XT912 using XDA Labs
Click to expand...
Click to collapse
Not all
Thanks for rom !!
It's seems lag, will any kernel / settings can solve it ?
@stargo,
Thanks for keeping up CM for these devices.
This 14.1 runs very smooth on a X910, but when installed with GApps it becomes much slower (maybe official 13.0 too, but I didn't test it without gapps). The broken File Manager is not nice, however.
Positively, it doesn't include CM Bug Report app, which always crash in CM13.0 (triggered by crash in a page inside Privacy Guard).
But, I see there is no "App data usage" (restrict apps Wi-Fi or Cellular data) in Privacy Guard. Was it removed from 14.1 or just not ready yet?
Just out of curiosity, could you tell me if Safestrap is the only variant of TWRP that works in spyder/umts_spyder? (I couldn't find original TWRP for these). No, I don't dislike Safestrap, I think it's very nice project, especially for preserving stock rom and allowing multi-boot, despite possible performance penalties.
I have another question about Safestrap: If I boot into stock and make a backup of its .img files (they are in internal sdcard/safestrap), do I need a backup made inside twrp or they are the same?
Will you make available a test build of the next Safestrap version?
williamlaw said:
Thanks for rom !!
It's seems lag, will any kernel / settings can solve it ?
Click to expand...
Click to collapse
[emoji6] http://droid.cs.fau.de/jjb666/Kernels/cm14/2016-11-08/
P.S. It works such at was on cm13 (cm13 versions), I mean - nice for battery and performance
from XT910, 925 or 1225 using Tapatalk
Ducadim said:
[emoji6] http://droid.cs.fau.de/jjb666/Kernels/cm14/2016-11-08/
P.S. It works such at was on cm13 (cm13 versions), I mean - nice for battery and performance
from XT910, 925 or 1225 using Tapatalk
Click to expand...
Click to collapse
Which one is great to use ?
Thanks
williamlaw said:
Which one is great to use ?
Thanks
Click to expand...
Click to collapse
For me - cm14.1-OC-FullScale-Lite-2016-11-08.zip, I have tried all versions on cm13, this was only one I can install (just for cm13, of course), so I use the same on cm14.1 and I am not disappointed, but I am have not tried others...
Using daily. Thanks!
Android OS / Cyanogenmod-system Batterydrain
I have this problem since CM13. I tried cm-13.0-20160816-SNAPSHOT-ZNH5YAO0FG-umts_spyder.zip and many nightlies but it's always the same: android os or cyanogenmod system is with 20-40 % the number one batterydrainer and always keeps the device active. With the first cm13 builds and with cm11 I never forced this problem and it made one day but now I can't find a build which doesn't has this problem anymore. I tried different kernels on cm13 but without any effect.
I hoped it would be better on cm14 but unfortunatly it's exactly the same..
Does anyone has an idea or a solution to this problem?
Thank you for any answer!
KonradL said:
always keeps the device active.
Click to expand...
Click to collapse
Are you sure it is not some app you installed, or accidentally changed Android settings to avoid turning screen off? Did you cleanly installed Cm the last time?
"Error code 70" during installing pico GAps
Thank you so much stargo for your work!
I have putted it to the slot 1 with pico GApps. Works great!
But when i putting it in to the stock slot i getting "Error code 70" during installing pico GAps. I tried reformat userdata to ext4.
I checked rm -rf instead of formatting then Wipe/advanced/checked data/Repair or Change File System - and change to EXT4 but when i go back it still ext3.
How to solve this issue?
Thank you.
spacemonkeyss said:
Thank you so much stargo for your work!
I have putted it to the slot 1 with pico GApps. Works great!
But when i putting it in to the stock slot i getting "Error code 70" during installing pico GAps. I tried reformat userdata to ext4.
I checked rm -rf instead of formatting then Wipe/advanced/checked data/Repair or Change File System - and change to EXT4 but when i go back it still ext3.
How to solve this issue?
Thank you.
Click to expand...
Click to collapse
Is the error code 70 stating that you don't have enough space to install gapps?
If you exit the to the first screen in safestrap, check again that data is EXT4 in advanced wipe.
The Unlegacy Android Project
TF201 | TF300T/TG/TL | TF700T
Introduction
Unlegacy Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy Android was born. In our opinion, these ROMs are how the official updates would look.
On top of AOSP, we only include changes which are necessary to support the hardware, be secure, and get acceptable performance. Current features for Asus Transformer Series include:
- Linux kernel 3.4.y (currently 3.4.113)
- BFQ IO scheduler (official kernel 3.4 release), set up so GUI processes have the highest priority
- F2FS support from kernel 4.9 (for /data and /cache)
Installation
You must have NvFlash backup. It is MANDATORY!
You need to use modified TWRP recovery that works with updated F2FS. If you're planning to install GApps, be sure to read the second post!
Problems
Non working/Known bugs:
- Touchscreen failure (sometimes occurs, if touch works after reboot it will work till next reboot);
- Camera (both);
- Dock special keys (top row);
- GUI crashes; - occure less often
Currently, I'm only one from Unlegacy Team, who has TF device. Help in developing or device donation would be highly appreciated.
Downloads
See: http://builds.unlegacy-android.org. Our automated builds ensure that we always have the latest Android security patches merged in, without having to manually start and upload builds Else is enclosed in downloads.
Latest information about OREO builds can be found HERE.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices (see the second post). The aim of this project is to create a fast and stable ROM - although, one could use Xposed (or similar) to add extra features.
As usual, feedback is appreciated
Contacts
You may join Telegram development group, where all fresh staff is published and tests are made.
XDA:DevDB Information
Unlegacy Android Project, ROM for the Asus Eee Pad Transformer Prime
Contributors
Clamor, Ziyan, Narkolai
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Bootloader 4.2 JB
Based On: AOSP
Version Information
Status: Beta
Created 2018-02-18
Last Updated 2018-10-17
Installation gide (for those who uses F2FS)
Before installing ROM you need to update your current recovery with this TWRP, else you will get a bootloop with next format from fastboot. Install zip from your current recovery and reboot into your current system. Than boot into new recovery and install ROM (with factory reset).
Currently 3.4 kernel isn't stable enough for daily use. You may use updated 3.1 _that16 kernel, it works fine with this ROM. To make wifi work with _that16 kernel just move nvram_nh615.txt from system/etc to data/misc/wifi and rename to nvram.txt
You may use KatKiss 7.1 if you want, but you must flash a _that16 kernel every time after flashing KatKiss ROM. Else you will get a bootloop with next format from fastboot.
If you want to go back to ordinary TWRP, you need to make a format from fastboot, flash TWRP and make formats from there as well.
REPARTITION and TREBLE
TF201 users know well what is repartition. While flashing 4.2BL from HB internal storage is reformatted. This thing is exactly the same.
I worked on it for few last weeks to make it stable and simple enough to any user to install this update. As usual NvFlash is MANDATORY!
So, UA_Bootloader.zip includes latest JB4.2 10.6.1.27.5 bootloader, modified TWRP [email protected] from Downloads section and my new partition table. It's main benefits are /system partition increased to 1GB and /vendor partition. This means that we may install bigger gapps packages and support of TF's may be extended plus having /vendor partition gives us at least hardware support for Project Treble, even if there is no 8.1 builds currently.
Before installation copy everything from tablet on PC, else all you data will be lost! To install this update just install it via TWPR and when flashing is finished press reboot into system. Than wait till blue line gets to the end and tablet reboots. Tablet will than stuck into ASUS screen with Device is Unlocked sign in top left corner. Than reboot manually into recovery and format /system to ext4; /cache to ext4 or f2fs; /data to ext4 or f2fs and you are good to go.
New partition table is compatible with all existing ROMs for TF's. If you flash ROM with system in .img file you need after flash into recovery do Wipe -> System -> Advanced Wipe -> Change or resize partition -> Resize filesystem. If you want to restore 4.2 state you can flash HB bootloader or Bootloader 4.2 attached in Downloads section.
Thank you very much for your work !
I see you have done some modifications on github. Can you explain to me how generate system.new.dat & system.transfer.list from your repo in order to create an updated version of this ROM ?
MalibuKoKo said:
Thank you very much for your work !
I see you have done some modifications on github. Can you explain to me how generate system.new.dat & system.transfer.list from your repo in order to create an updated version of this ROM ?
Click to expand...
Click to collapse
Actually you can't build fully working ROM from my source for now. If you would like to help in developing - PM me.
Do I need stock tf201 bootloader, or is this based on the hairybean boadloader? Like Katkiss ROM is based on.
Thanks for sharing this ROM.
goosebickel said:
Do I need stock tf201 bootloader, or is this based on the hairybean boadloader? Like Katkiss ROM is based on.
Thanks for sharing this ROM.
Click to expand...
Click to collapse
Based on latest 4.2 bootloader (like Hairybean). I'll provide a bootloader + new TWRP and separate TWRP as soon as I get a stable recovery build.
General Feedback
Finally got around to flashing your ROM a week ago, following your instructions, everything went fine. I installed your UA-bootloader and flashed _that16 kernel.
Running pretty smooth with Pico gapps installed, after a week, the usual happens, slow loading apps etc, but that is not the ROMs fault, the very slow memory that Asus put into it and Google is slowing it down with constant syncs etc.
Was wondering if you had added compatibility for using MicroG?
Thanks for keeping this old tablet going.
@goosebickel sorry for such a long silence. MicroG are supported as I can say (I installed them but didn't test much).
P.S. If you are still on UA rom there is an update.
Oreo 8.1
Yesterday I have quickly build 8.1 ROM for transformers. There doesn't work almost anything and I won't have excess to my TF201 for a while to fix stuff Rom can be booted with same requirements as N roms. Here is first build. Please don't post any issues/logs from O for now. I know already about all major issues.
Thank you!
Great to see some development for the Transformer Prime
I have some good news. Here is mostly working build with issues from N + non working bt. I'm still working on fixing staff so this isn't last build.
P.S. Remove system/lib/hw/bluetooth.default.so to avoid constant bt crash
Clamor said:
I have some good news. Here is mostly working build with issues from N + non working bt. I'm still working on fixing staff so this isn't last build.
P.S. Remove system/lib/hw/bluetooth.default.so to avoid constant bt crash
Click to expand...
Click to collapse
Are you planning to work on Pie as well once 8.1 is somewhat stable?
shinzz said:
Are you planning to work on Pie as well once 8.1 is somewhat stable?
Click to expand...
Click to collapse
I'm planing to bring up P as well. If O works, P should work as well.
Can the ROM be installed by using the latest KANG TWRP 3.2.3 or do I need to use the TWRP found in the download section?
@shinzz TWRP from download section
any update?
shinzz said:
any update?
Click to expand...
Click to collapse
Noticed the link to the ROM is 404'ed also. - NP
latest 8.1 build, I need some time to update info, but generaly same bugs remain + 8.1 is still unstable.
It will work only with UA TWRP
Clamor said:
latest 8.1 build, I need some time to update info, but generaly same bugs remain + 8.1 is still unstable.
It will work only with UA TWRP
Click to expand...
Click to collapse
My 201 is on KANG's - TWRP 3.2.1-0 and KatKiss, if this ROM just a simple wipe and flash with KANG's - TWRP 3.2.1-0 and the Harry Bean bootloader on my 201 or will I need a different recovery console, bootloader ext. ext? - NP
Note: This is not a ROM based on the ROM shipped with your device. Exynos variants such as International (F), International Dual(Hybrid)-SIM (F/DS), Korean (N) ONLY. In NO way it is compatible with Snapdragon variants including but not limited to American(U/U1/A/T/P/V), Chinese(0/8/6), Hong Kong(0), Japanese(SC-*), Canadian(W) variants.
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (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.
Features Overview:
https://www.xda-developers.com/lineageos-15-feature-list-overview-screenshots-video/
Screenshots:
View attachment 4491847View attachment 4491848View attachment 4491849View attachment 4492992
Device Info:
Galaxy Note 9 (Exynos): TBD
What's working:
TBD
This build is an official LineageOS build. Compliance with our device support requirements is enforced and guaranteed. That means including but not limited to these hardwares will work:
Wi-Fi
Bluetooth
Mobile Network (Calling, Data, etc.)
Audio
USB
GPS
Camera
Fingerprint Sensor
NFC
Etc. Check device support requirements for more.
What's not working:
Applicable exceptions granted in device support requirements.
Obviously Samsung's own features such as Samsung Pay, KNOX, Theme Center, Game Launcher, etc. won't be ported to LineageOS. We may have our own implementation to similar functions, though.
Iris sensor does not work because AOSP upstream does not support that yet.
IMS services (VoLTE, VoWiFi, etc). Samsung has their own proprietary implementation. It is not really possible to easily port that to LineageOS.
Instructions:
Make sure TWRP has been installed and functional
Download the latest build (and optionally gapps)
Download the compatible vendor image (https://androidfilehost.com/?w=files&flid=284041)
Reboot to recovery
Wipe data and cache (required if you switch from other ROMs)
Flash the vendor image
Flash the latest build (and gapps)
Reboot
LineageOS updater will handle updates automatically (OTA).
If you upgrade manually from older official releases to newer releases, you don't need to wipe your data or reflash gapps.
Downloads:
Galaxy Note 9 Exynos (N960F/FDS/N): https://www.androidfilehost.com/?w=files&flid=284057
Root addon: https://download.lineageos.org/extras
Google Apps: https://wiki.lineageos.org/gapps.html
Reporting Bugs:
https://wiki.lineageos.org/bugreport-howto.html
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 /proc/last_kmsg. (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 /proc/avc_msg.
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.
Please use LineageOS BUG tracker to report BUGs. BUGs reported in the thread could be ignored due to large number of posts.
Channel and Group:
LineageOS Channel (News and Updates):
https://t.me/lineageos_star
AOSP-like ROMs (not limited to LineageOS) Group (Discussion, Quick Tech Support and Early Testing):
https://t.me/joinchat/DTrGs0ygFKxHhc3bb11YKw
XDA:DevDB Information
LineageOS for Galaxy Note 9, ROM for the Samsung Galaxy Note 9
Contributors
jesec
Source Code: https://github.com/LineageOS/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Version Information
Status: Stable
Created 2018-10-18
Last Updated 2018-10-18
Reserved
Reserved
Happy days! Thank you Jesse Sir!
Thank you soo much sir
---------- Post added at 07:15 AM ---------- Previous post was at 07:13 AM ----------
And good luck for LOS 16! I'm sure you can give us a sweet slice of pie
I have been waiting for this, once my bootloader is unlock ill see to it, it will be my 1st try to note 9 cfw. Thanks jesec.
Flashed, stuck at bootlogo. Doesn't even loop?
Tried flashing with noverity, tried with magisk, without magisk. Maybe vendor is bad?
s3xxt0y said:
Flashed, stuck at bootlogo. Doesn't even loop?
Tried flashing with noverity, tried with magisk, without magisk. Maybe vendor is bad?
Click to expand...
Click to collapse
yeah i think vendor is broken, try stock vendor
malinathani said:
yeah i think vendor is broken, try stock vendor
Click to expand...
Click to collapse
Flashed with diff stock vendors still stuck @ bootsplash.
Edit: tried without gapps to be sure too. Still no joy.
Jesse - might be worth joining the Note 9 AOSP Telegram. There's 50 of us in there if you need us for testing etc;
https://t.me/joinchat/GnVMLU__5M8g5NaStUlbRg
s3xxt0y said:
Flashed with diff stock vendors still stuck @ bootsplash.
Click to expand...
Click to collapse
bootsplash stuck could be a kernel
Are you sure magisk script ran correctly? Try flashing magisk again and see.
Thanks brother
Hello,
Does S-pen features work?
Thx
how to fix bootsplash?
Well hot damn! :highfive:
muhyidin said:
Hello,
Does S-pen features work?
Thx
Click to expand...
Click to collapse
spen is for touch wiz aka Sam experience
for the rest if the android world it's a mouse pointer.
Thank you @jesec for the effort.. This is exactly what I was looking for.
I tested this on N960F/D got stuck on bootsplash as well, I tried both Stock Vendor and the provided Vendor Images, with or without magisk with no luck.
I tried restoring boot image from previous backup (this might sound stupid) but I got past the splashcreen into Lineage Loading screen, it would stay for a minute then reboot to recovery.
For people who got stuck in the bootsplash
To exit the bootSplash freeze use the download mode button combination: Down+Bigsby+Power until screen goes off then recovery shorcut Up+Bigsby+Power,
Did anyone manage to make this work?
that_same_guy said:
Thank you @jesec for the effort.. This is exactly what I was looking for.
I tested this on N960F/D got stuck on bootsplash as well, I tried both Stock Vendor and the provided Vendor Images, with or without magisk with no luck.
I tried restoring boot image from previous backup (this might sound stupid) but I got past the splashcreen into Lineage Loading screen, it would stay for a minute then reboot to recovery.
For people who got stuck in the bootsplash
To exit the bootSplash freeze use the download mode button combination: Down+Bigsby+Power until screen goes off then recovery shorcut Up+Bigsby+Power,
Did anyone manage to make this work?
Click to expand...
Click to collapse
Same problem here, Stuck on bootloop
Jesec is back
The ROM doesn't boot for anyone curious. I haven't heard of a report of one booting successfully anyway.
bober10113 said:
spen is for touch wiz aka Sam experience
for the rest if the android world it's a mouse pointer.
Click to expand...
Click to collapse
You maybe answer the sensitivity level but there is also the need to some kind of powering off the 500KHz signal send when not using the pen.
Then can we use the sensor to activate the pen ? What about the Bluetooth button ?
The wacom screen could be initialize from the begining with Project Trebble. What's the differences with LOS for S9s ?
HavocOS for moto G5 is here and this is what you need to know
NOTES:
- vanilla build only
BUGS:
none so far
DOWNLOADS:
https://sourceforge.net/projects/gkart-builds/files/cedric/HavocOS/
SOURCE:
ROM: https://github.com/Havoc-OS
Kernel: https://github.com/LineageOS/android_kernel_motorola_msm8953
vendor: https://github.com/JarlPenguin/proprietary_vendor_motorola
Credits:
- HavocOS team for the rom source
- @JarlPenguin for the vendor and kernel sources
greetings and enjoy
Which twrp should i use? Tried flashing with same as lineage 18.1 after flashing stock rom oreo but getting "you need to flash from stock 8.1 ..." Or something like that. What am i missing? Had the same problem with last lineage build. I was trying flash by sideload (only flash option at latest twrp) Did correct wipes, etc. My model is xt1670.
facua92 said:
Which twrp should i use? Tried flashing with same as lineage 18.1 after flashing stock rom oreo but getting "you need to flash from stock 8.1 ..." Or something like that. What am i missing? Had the same problem with last lineage build. I was trying flash by sideload (only flash option at latest twrp) Did correct wipes, etc. My model is xt1670.
Click to expand...
Click to collapse
Your modem in your firmware is outdated
Flash the latest firmware (or at least just the modem part)
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors-obs-2.lolinet.com