Related
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.x (Nougat),
which is designed to increase performance and reliability over stock Android for your device.
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.
Official LineageOS website : http://lineageos.org
Downloads Links
LineageOS 14.x (Unlocked Bootloader) :
Nightlies : https://download.lineageos.org/odin
Google Applications (optional) :
OpenGapps : http://opengapps.org/ (Use packages for ARM, Android 7.x, Micro or Pico)
Information : Flash the GApps before the first boot. If not, a clean flash is recommended.
Informations and references :
About LineageOS updates : ChangeLog available on http://www.cmxlog.com/14.1/odin/
About LineageOS device side : See my GitHub trees linked below
Flashing and updating
LineageOS clean install :
- (Optional) Flash the boot.img kernel from the ROM zip with Fastboot or Flashtool
- (Optional) Wipe the data & cache (Backup to make sure not to loose data)
- Flash the LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps to have the Google Applications
- (Optional) Every additional zip you want to flash
- Reboot
LineageOS update / upgrade :
- (Information) Don't wipe anything unless you want to
- (CM / UNOFFICIAL) Nothing to wipe when switching
- (FUTURE RELEASES) Might need clean, informations will be updated
- Flash the latest LineageOS ROM zip from the Recovery
- (Optional) Flash the GApps on first install / upgrade. Not required later, but do update sometimes
- (Optional) Every additional zip you want to flash
- Reboot
LineageOS addonsu for root access :
- (Information) Read the Root section of the Q&A thread
- (Download) Download the addonsu for arm : LineageOS Downloads / Extras
- (Optional) Flash the zip on a working Lineage installation (once)
- (Information) Upon ROM updates, the addonsu is preserved
- Reboot
About the builds
Device tree : https://github.com/fusion3-common/android_device_sony_Odin/commits/cm-14.1
Kernel sources : https://github.com/fusion3-common/android_kernel_sony_apq8064/commits/cm-14.1
Vendor blobs : https://github.com/fusion3-common/proprietary_vendor_sony/commits/cm-14.1
Issues and reports
- Report issues only if you are using the ROM kernel
- If an additional mod is installed, make sure it's unrelated, and mention it
- Make sure the issue wasn't discussed earlier in the threads
- Share a log of the error with CatLog for example
About LineageOS Legal : http://lineageos.org/legal/
The LineageOS team would like to thank everyone involved
in helping with testing, coding, debugging & documenting! Enjoy!
[/INDENT]
LineageOS available for Odin also thanks to :
- The LineageOS Team
- The CyanogenMod Team
- Everyone involved in working and testing
XDA:DevDB Information
[ROM][NIGHTLIES][7.1] LineageOS 14.1 for Xperia ZL, ROM for the Sony Xperia ZL
Contributors
Daedroza, AdrianDC, Chippa_a, Olivier, Namelos, CyberwalkmaN, sigprof
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2017-07-17
Last Updated 2017-11-10
Reserved
FEATURES AND ISSUES
Code:
- Boot : Ok
- GApps : OpenGApps Micro Ok
- FOTA Recovery : Ok (see below)
- WiFi : Ok (real SONY MAC address)
- Bluetooth : Ok (real SONY MAC address)
- WiFi Hotspot : Ok (2.4GHz and 5GHz)
- RIL - Phone - Data : Ok
- GPS : Ok
- Camera : Ok
- Camcorder : Ok
- Lights : Ok
- MicroSD : Ok
- Accelerometer : Ok
- Compass : Ok
- Gyroscope : Ok
- AOSP sensors : Ok
- FM Radio : Ok
- Vibrator : Ok
- Microphone : Ok
- Audio & external audio : Ok
- Bluetooth audio : Ok
- NFC : Ok
- Kernel : Ok, Updating frequently
- Graphics : Ok
- 3D Rendering : Ok
- Clock : Ok
- Offline Charging : Ok
- SEPolicies : Fully enforced
Thanks and good luck on getting this official.
Thanks for your hard work,it works fine
Successfully upgraded from Chippa_a's unofficial Lineage 170413 build without wipe. Thanks.
after bootind in recovery (twrp), wiped cache and data, flashed the zip lineage-14.1-20170716-UNOFFICIAL-odin.zip and open_gapps-arm-7.1-mini-20170722.zip and rebooted. After that, only black screen and no boot into system, only fastboot or flash mode...
previously using a stock rom in 5.1.1 with root and recovery.
any help?
ps: after that, tried to flash the boot.img in fast boot mode, get this error:
>fastboot flash boot c:\boot.img
sending 'boot' (14972 KB)...
OKAY [ 0.293s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.297s
PS 2: tried flashing a ftf via flashtool, but get some errors too...
23/036/2017 18:36:01 - INFO - Opening device for R/W
23/036/2017 18:36:03 - INFO - Reading device information
23/036/2017 18:36:12 - INFO - Unable to read from phone after having opened it.
23/036/2017 18:36:12 - INFO - trying to continue anyway
23/036/2017 18:36:12 - INFO - Phone ready for flashmode operations.
23/036/2017 18:36:12 - INFO - Opening TA partition 2
23/036/2017 18:36:12 - INFO - Start Flashing
23/036/2017 18:36:12 - INFO - No loader in the bundle. Searching for one
23/036/2017 18:36:16 - INFO - Processing loader.sin
23/036/2017 18:36:16 - INFO - Checking header
23/036/2017 18:36:16 - ERROR - Processing of loader.sin finished with errors.
23/036/2017 18:36:16 - INFO - Ending flash session
23/036/2017 18:36:16 - ERROR - Error in processHeader : 22 : O dispositivo não reconhece o comando.
23/036/2017 18:36:16 - ERROR - Error flashing. Aborted
23/036/2017 18:36:16 - INFO - Device disconnected
@saddambea looks like you bootloader is not unlocked. Is that possible? If you back up you TA partition with twrp and recover from those backups you will relock your bootloader.
NamenIos said:
@saddambea looks like you bootloader is not unlocked. Is that possible? If you back up you TA partition with twrp and recover from those backups you will relock your bootloader.
Click to expand...
Click to collapse
yes, i think it´s possible, my bl may be locked. couldn´t unlock via fastboot after that
and now, i can´t even boot to recovery. tried to flash recovery.img through fastboot with no success...
saddambea said:
yes, i think it´s possible, my bl may be locked. couldn´t unlock via fastboot after that...
Click to expand...
Click to collapse
What error did you get? Maybe you have to go back to stock via flashtool for this.
saddambea said:
... and now, i can´t even boot to recovery.
Click to expand...
Click to collapse
This should be normal if you used Dual Recovery on the stock rom before. Dualrecovery is on the /system partition, that you wiped while flashing.
saddambea said:
... tried to flash recovery.img through fastboot with no success...
Click to expand...
Click to collapse
This can't work as we don't have have a recovery partition. Our recovery is either in the boot.img or the system partition. LineageOS uses the boot.img and optionally then boots the recovery in the FOTA Kernel partition if you press vol up.
Uploading a new build as we speak. The changelog since 2016 is (I'm just being vague here, I don't remember all the issues, but I do have all the logs with me, if someone is interested):
1. Fix ancient F2FS bug (Specific to Fusion3)
2. Fix https://forum.xda-developers.com/showpost.php?p=69849473&postcount=1243
3. Fix https://forum.xda-developers.com/showpost.php?p=68245138&postcount=1130
4. Fix for input_evdev specific to us
5. Fix for SWAP
6. Fix for C5502 Double Tap to Wake Screen Freeze.
7. Many other improvements like ZRAM / Process Reclaim / Perf / mmc / Anon Reclaim etc
8. Changes from Chippa_a for XML audio configuration is also picked, I don't know maybe you will see a improvement @gorillanobka?
I haven't gone much into detail, but please send logs (dmesg / last_kmsg / logcat) wherever possible if you face something. At the moment, I only have C5502 (Fusion3 Dogo) with me. Yuga / Odin has hardware specific to them (other than chipset), so I won't be able to reproduce them on my device if you get some event changes / sensors changes.
I've also included a minor hack for auto-brightness. Let me know how you feel about it.
Please give it a go? Thanks
Thank you Daedroza!
You're a scholar and a gentleman. Gimme a week or so ( I am caught up with assignments and exams ) and i will have a look at it...
I'm pretty sure it will be a super stable build as always...
I am already running a Chippa's build with some changes to the XML audio if i am not wrong, and i could already hear some improvements.
The notifications remained very low though... I think the EU specific limitation for the audio needs to be commented / removed in order to see serious improvements .
Kind regards
Gorilla no Baka
Daedroza said:
Uploading a new build as we speak. The changelog since 2016 is (I'm just being vague here, I don't remember all the issues, but I do have all the logs with me, if someone is interested):
1. Fix ancient F2FS bug (Specific to Fusion3)
2. Fix https://forum.xda-developers.com/showpost.php?p=69849473&postcount=1243
3. Fix https://forum.xda-developers.com/showpost.php?p=68245138&postcount=1130
4. Fix for input_evdev specific to us
5. Fix for SWAP
6. Fix for C5502 Double Tap to Wake Screen Freeze.
7. Many other improvements like ZRAM / Process Reclaim / Perf / mmc / Anon Reclaim etc
8. Changes from Chippa_a for XML audio configuration is also picked, I don't know maybe you will see a improvement @gorillanobka?
I haven't gone much into detail, but please send logs (dmesg / last_kmsg / logcat) wherever possible if you face something. At the moment, I only have C5502 (Fusion3 Dogo) with me. Yuga / Odin has hardware specific to them (other than chipset), so I won't be able to reproduce them on my device if you get some event changes / sensors changes.
I've also included a minor hack for auto-brightness. Let me know how you feel about it.
Please give it a go? Thanks
Click to expand...
Click to collapse
Thank you for continuing with this phone. I plan to download this new build momentarily and try, but I have two long running issues and wonder if you might comment.
One is that this seems to come from the C6503 which has a different set of cellular bands, and I think that means my C6506 cannot access them. Is that correct? I seem to have poorer coverage in some areas than with the stock Sony software (which is now ancient of course). I have no done a deep dive to see, other than to see cynogenmod now lineage seems to be specific to the less-bands phone modem?
The more specific question is this: after some days or weeks, the phone's display gets laggy on scrolls; two specific places I use a lot are the CNN app and the News360 app. I found a fresh install cleared it up nicely, then over time it gets worse. I experimented (takes a long time as it is reproducible only over a long time) and found it is the Dalvik cache. If I clear that and reboot -- smooth as silk. A couple weeks later, have to do it again. Any thoughts as to what is happening? It's easily fixable now that I know a full install is not needed, but it just seems strange. Anyone else seeing it? Try wiping just Dalvik, see if it helps.
Linwood.Ferguson said:
Thank you for continuing with this phone. I plan to download this new build momentarily and try, but I have two long running issues and wonder if you might comment.
One is that this seems to come from the C6503 which has a different set of cellular bands, and I think that means my C6506 cannot access them. Is that correct? I seem to have poorer coverage in some areas than with the stock Sony software (which is now ancient of course). I have no done a deep dive to see, other than to see cynogenmod now lineage seems to be specific to the less-bands phone modem?
The more specific question is this: after some days or weeks, the phone's display gets laggy on scrolls; two specific places I use a lot are the CNN app and the News360 app. I found a fresh install cleared it up nicely, then over time it gets worse. I experimented (takes a long time as it is reproducible only over a long time) and found it is the Dalvik cache. If I clear that and reboot -- smooth as silk. A couple weeks later, have to do it again. Any thoughts as to what is happening? It's easily fixable now that I know a full install is not needed, but it just seems strange. Anyone else seeing it? Try wiping just Dalvik, see if it helps.
Click to expand...
Click to collapse
- No idea about phone coverage. I had preferred if you could do a diff with signal measuring app or something of sort? That would give you a base stock result and one from Lineage.
- The phone's display gets slow / laggy / unresponsive systemwide or it just the apps? Maybe both the apps consume a lot of space on internal and cache. Hence you need to clear them.
On the original firmware there was a dialer code to show usable bands; it does not work on LineageOS. I have tried without success to find a way to tell which bands are supported in the current OS. With some playstore apps I can see the current band but not all usable bands.
The original C6506 (odin rimy) documentation listed the bands available, and compared to the C6503 (odin gina). There are a number of differences. The C6506 supports LTE I, IV and XVII that the C6503 does not; the C6503 supports LTE III, VII, VIII and XX that the C6506 does not. My understanding (but I am not certain) is that this is a hardware limitation of the device, which of course corresponds to the stock firmware. It could also be that the radios are the same, but the restriction on bands was purely in software tied to the model.
My reading of old postings on the cynogenmod software was it was based on the C6503, and so my question is what is the result. It seems POSSIBLE that it only then supports the bands they had in common: LTE I and V, which leaves a lot missing. Or it is also POSSIBLE that it supports all the C6503 bands which (again, my loose understanding) were not ideal for US/AT&T use, which is what the C6506 was fo.
Basically I know only enough to wonder if the LineageOS is limiting the bands the phone can use? And how I might tell for sure? And/or if you have all the source, can you tell, or is this buried in the blobs that are opaque?
As to the laggy: I think it is the whole system, but it is hard to say as I'm generally using some app. They do begin to start up slower as well as operate slower, but it is most noticeable on things that scroll. Frankly I would likely not notice other slowness if the scrolling did not hesitate. A list of stories in the CNN app, for example, if you touch and start scrolling hesitates nearly a second before it moves. Clear dalvik and there's no hesitation. It is also worth noting I use very little on the phone - mail, CNN, News360, weatherbug, calendar, and the phone are just about it. All visible resources (that I know how to look at) show lots of free space. Now that I know how to quickly fix it not a big deal.
Does the IR blaster work with this build? Does it work with other apps like Anymote?
According to Sonys whitepaper the C6506 should support LTE Band I, Band II, Band IV, Band V and Band XVII (1, 2, 4, 5 and 17). The supported bands are stored in partitions not touched by LineageOS (see here). You have to check which bands your provider uses in your region and then use an app to check if you get connected to which band, I don't think there is an alternative. The old dialer code won't work, as it is sony specific. I too haven't found an app that shows available LTE networks regardless of your contract and possibly this is not even possible on standard Android APIs.
Performance (in scrolling and in general) doesn't seem worse than on stock for me (in fact it feels better). I use F2FS, but I doubt it changes anything on your performance problems. Once we get all this in the official repos and get a weekly build status, there will probably be some experimental stuff that will be tried out and surfaces here. For now the focus is more on getting the officially supported status.
edit:
JLBouras said:
Does the IR blaster work with this build? Does it work with other apps like Anymote?
Click to expand...
Click to collapse
Only with one app (the one that worked on CM13), root access and selinux disabled, we have to add file permissions, ownership and selinux rules. This is not yet tested enough though. edit: Just tested with selinux disabled, works well with preconfigured remotes, slightly flaky when learning imo.
NamenIos said:
According to Sonys whitepaper the C6506 should support LTE Band I, Band II, Band IV, Band V and Band XVII (1, 2, 4, 5 and 17). The supported bands are stored in partitions not touched by LineageOS ....
The old dialer code won't work, as it is sony specific. I too haven't found an app that shows available LTE networks regardless of your contract and possibly this is not even possible on standard Android APIs.
Click to expand...
Click to collapse
That's the list of the supported bands, but I know I read years ago that the (not sure if this is the right word?) modem used by Cynogenmod for this phone started as the 6503. Does the software incorporated within LineageOS support all bands listed in the partition mentioned?
I tried to find the old discussion I remember without success. Closest I got was this which brings it up (look for "bands"), but people are saying "mine works". The issue of course is if some bands work but not others the phone may "work" but not have the same coverage where you have less bands or more congestion.
I was hoping there was a way to actually query the phone for which have actual hardware+software support, but it sounds like there no longer exists that ability with the loss of that service menu.
NamenIos said:
Performance (in scrolling and in general) doesn't seem worse than on stock for me (in fact it feels better). I use F2FS, but I doubt it changes anything on your performance problems. Once we get all this in the official repos and get a weekly build status, there will probably be some experimental stuff that will be tried out and surfaces here. For now the focus is more on getting the officially supported status.
Click to expand...
Click to collapse
Frankly it may have been the same there. I'm wondering if, being news related apps I use most, if they are leaking/cluttering up the cache in some way more than normal use (Dalvik is for the VM, right? Do apps cache data there or just the VM cache app code there?). Regardless, I have an easy workaround, it takes just a few minutes to clear and get back fully up.
I absolutely agree getting fully supported is great. I hope to get a Pixel2 when they come out, and leave this as a backup phone, so would love to get a few more years utility out of it. It's been a really great phone, I still rarely see any with the low percentage of wasted space on the front as this.
Linwood.Ferguson said:
That's the list of the supported bands, but I know I read years ago that the (not sure if this is the right word?) modem used by Cynogenmod for this phone started as the 6503.
Click to expand...
Click to collapse
Modem partitions are not affected in case of installation of LineageOS/CyanogenMod. This ROM is universal for all models (C6502/6503/6506).
NamenIos said:
The supported bands are stored in partitions not touched by LineageOS
Click to expand...
Click to collapse
New build is up folks.
- Security patches till July 2017.
- Clean build, inclusive of all changes by LineageOS till yesterday.
- Includes DRM libraries.
- All other standard bugfixes from cm-13.0 thread, all of them. YES, all of them.
- Attempt to fix a problem as told here (https://forum.xda-developers.com/showpost.php?p=73250499&postcount=16)
Folks, this has been a year long journey for me, let's face it, I am learner, so I need your feedback here. Even a smallest problem (like force closes) will seen as long as you provide logs. Regarding stability, we're not pushing devices that reboot or mess up after some time. A lot of people are involved in completing this and I would like to thank all of them. And good feedbacks are welcome too, if it works for you
Daedroza said:
New build is up folks.
- Security patches till July 2017.
- Clean build, inclusive of all changes by LineageOS till yesterday.
- Includes DRM libraries.
- All other standard bugfixes from cm-13.0 thread, all of them. YES, all of them.
- Attempt to fix a problem as told here (https://forum.xda-developers.com/showpost.php?p=73250499&postcount=16)
Folks, this has been a year long journey for me, let's face it, I am learner, so I need your feedback here. Even a smallest problem (like force closes) will seen as long as you provide logs. Regarding stability, we're not pushing devices that reboot or mess up after some time. A lot of people are involved in completing this and I would like to thank all of them. And good feedbacks are welcome too, if it works for you
Click to expand...
Click to collapse
And just a day later, August Security Patches was released...
Introduction
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.
Requirements
Your device need to be unlocked either officially (h815 international or h811) or by UsU
Your bootloader stack should be on MM 20p (20x for H811) or higher! (see FAQ #20 for how to upgrade your bootloader stack).
.... and for your convenience I have even created TWRP flashable files for that here
in particular that means this thread is for:
F500 (UsU'd)
H810 (UsU'd)
H811
H812 (UsU'd)
H815 (official unlocked or UsU'd)
H819 (UsU'd)
LS991 (UsU'd)
US991 (UsU'd)
VS986 (UsU'd)
Latest TWRP - PREVIEW build: click
Do a full Nandroid backup before doing anything!
Installation Instructions
This single very first step is for UsU'd devices only:
If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
If you do not know if you ever flashed it simply flash your modem partition again and you can be sure. This can't do any harm.
If you have no backup:
- TWRP flashable MM modems (N might not work)
Full clean install as described here (FAQ "#2") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash LOS
Optional: Flash GApps (8.1 - ARM64 for LOS 15.1, 7.1 - ARM64 for LOS 14.1) if you like
Optional (if you want root): Flash the official LOS root-addon (addonsu-15.1-arm64-signed.zip or addonsu-14.1-arm64-signed.zip) or Magisk (do not report issues if you have Magisk installed though!)
Boot (will take a bit on first boot!!!)
Enjoy
For more detailed instructions, please see my website (thepiguy0.github.io/installing)
Update Instructions
To update from a previous version of my rom:
If it is an old version of the rom, it is recommended to do a clean flash - Be aware that your data will be deleted
If it is a relatively recent version, a dirty flash should be ok - wipe cache and dalvik cache and then flash on top of your current installation - This keeps all your files
Current Issues
For a current list of all issues including possible workarounds:
Open issues
Issues with workarounds available
Summary (again check out the above linked issue tracker for a current state):
Bluetooth calling FIXED!
Flashlight icon on quick toggles FIXED!
SIM pin unlocking (Ril works, better to use an unlocked sim card for now) FIXED!
Magisk when encrypted - state UNKNOWN
Permissive SELinux FIXED!
Probably more undiscovered bugs
Downloads
Get the latest builds from steadfasterX's server
Get the legacy builds from my Google drive
Building from source
If you want to build this from source, follow the LG H815 build guide (replace H815 with H811 if needed). Immediately before the "repo sync" step, copy our local manifest (https://github.com/Suicide-Squirrel/local_manifests/blob/los-15.1/roomservice.xml) into the .repo/local_manifests/ folder. Now run repo sync.
Then miss out breakfast and proprietary files steps before continuing with Jack memory optimisations
Changelog
Go through the results here: click
older ones click here:
20/05/2018
WiFi Hotspot is now fixed
H811 audio is fixed
More audio enhancements behind the scenes
Increased performance in Titan Kernel
28/04/2018
Audio is now fully working (with the exception of bluetooth calling)
Camera and screen recorder are now both fully fixed and work
Latest Lineage and Titan updates
FAQ
Will be added as the time goes.
Credits
@kessaras, @steadfasterX and the LineageOS team
Sources
Lineage source code - https://github.com/LineageOS/
Device trees and kernel (forked from cypheros) - https://github.com/suicide-squirrel/
Proprietary files - https://github.com/CypherOS/
PREVIOUS OP (for historical reasons)
Introduction
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.
Requirements
LG G4 H815/H811
Latest MM firmware for H811 and latest Nougat/MM firmware for H815
Latest official TWRP or the latest TWRP preview from steadfasterX's server - This prevents the error 7 from appearing
For UsU devices, follow @steadfasterX's instructions for TWRP
Installation Instructions
Download appropriate zip for your device along with any additional modules such as gapps (arm64 android 8.1 needed)
Recommended - Create a full nandroid backup to allow you to restore to your previous OS if needed
Wipe system, data, cache and dalvik cache - Be aware that this WILL remove your currently installed OS and wipe your apps and most data
Flash the lineage zip, followed immediately by gapps if applicable
Reboot into system and wait for boot
For more detailed instructions, please see my website (thepiguy0.github.io/installing)
Update Instructions
To update from a previous version of my rom:
If it is an old version of the rom, it is recommended to do a clean flash - Be aware that your data will be deleted
If it is a relatively recent version, a dirty flash should be ok - wipe cache and dalvik cache and then flash on top of your current installation - This keeps all your files
Current Issues
For a current list of all issues including possible workarounds:
Open issues
Issues with workarounds available
Summary (again check out the above linked issue tracker for a current state):
Bluetooth calling
Flashlight icon on quick toggles
SIM pin unlocking (Ril works, better to use an unlocked sim card for now)
Magisk when encrypted
Permissive SELinux
Probably more undiscovered bugs
Downloads
Get the latest builds from steadfasterX's server
Get the legacy builds from my Google drive
Building from source
If you want to build this from source, follow the LG H815 build guide (replace H815 with H811 if needed). Immediately before the "repo sync" step, copy our local manifest (https://github.com/Suicide-Squirrel/local_manifests/blob/los-15.1/roomservice.xml) into the .repo/local_manifests/ folder. Now run repo sync.
Then miss out breakfast and proprietary files steps before continuing with Jack memory optimisations
Changelog
20/05/2018
WiFi Hotspot is now fixed
H811 audio is fixed
More audio enhancements behind the scenes
Increased performance in Titan Kernel
28/04/2018
Audio is now fully working (with the exception of bluetooth calling)
Camera and screen recorder are now both fully fixed and work
Latest Lineage and Titan updates
FAQ
Will be added as the time goes.
Credits
@kessaras, @steadfasterX and the LineageOS team
Sources
Lineage source code - https://github.com/LineageOS/
Device trees and kernel (forked from cypheros) - https://github.com/suicide-squirrel/
Proprietary files - https://github.com/CypherOS/
XDA:DevDB Information
LineageOS 14.1/15.1 for LG G4, ROM for the LG G4
Contributors
ThePiGuy, steadfasterX, kessaras, berkantkz and LineageOS
Source Code: https://github.com/LineageOS/
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: v20 (or higher for H815) bootloader and modem
Based On: Lineage OS
Version Information
Status: Stable
Current Beta Version: 20180428
Beta Release Date: 2018-04-28
Created 2018-04-26
Last Updated 2019-12-22
Reserved
Reserved
Great work!
Need more stability to have a try but following it closely!
Thanks a lot.
Good job!
I missed Lineage OS.
Is encryption working?
YOU, @ThePiGuy, built this (with help from others)? Well done man.
Good luck and Godspeed man
zeduck said:
Good job!
I missed Lineage OS.
Is encryption working?
Click to expand...
Click to collapse
Yes it is
ThePiGuy said:
Yes it is
Click to expand...
Click to collapse
Is it trimming working with encryption ( fstrim -v /data ) without the error transport endpoint not connected?
Thanks!
talk to @codeworkx.
if your commits you added are clean and crystal clear of what you did and you kept authorship, maybe you should update the official and get some logs to them to also help you.
Minor bugs of audio and maybe some props to make the camera function correctly are not hard bugs. Me i do not have the time sorry. I do not even have the time with AOSCP now that im working so much :/
Great job keeping LOS on this device. I'm holding on to it as I still find it fast and useful.
While there is a lens on the audio configuration it would be awesome to see this phone enabled for hires audio (up to 24bit / 192KHz) under LOS. I know people are skeptical of the difference but DAC is able to do this and it should simply be an edit of the relevant audio_policy_configuration.xml(?) file to enable the extra sound profiles above 16/48.
hteles said:
Is it trimming working with encryption ( fstrim -v /data ) without the error transport endpoint not connected?
Thanks!
Click to expand...
Click to collapse
I have no idea (give it a go if you want )
belrik said:
Great job keeping LOS on this device. I'm holding on to it as I still find it fast and useful.
While there is a lens on the audio configuration it would be awesome to see this phone enabled for hires audio (up to 24bit / 192KHz) under LOS. I know people are skeptical of the difference but DAC is able to do this and it should simply be an edit of the relevant audio_policy_configuration.xml(?) file to enable the extra sound profiles above 16/48.
Click to expand...
Click to collapse
First things first, got to get the audio working in the first place . And also, nobody seems to have seen the error that it kicks out in the logcat, so it might take a while to get it working - I'll try porting the cm-14.1 trees to lineage-15.1 rather than porting oreo cypheros trees to see if that makes a difference
@ThePiGuy what are the known bugs for this rom?
NummerEinsNerd said:
@ThePiGuy what are the known bugs for this rom?
Click to expand...
Click to collapse
All in the title post above (under Current Issues). Basically audio is fully broken (so this is purely testing at the moment - not suitable for a daily driver), camera is broken along with the lineage voice and screen recorder crashing.
ThePiGuy said:
All in the title post above (under Current Issues). Basically audio is fully broken (so this is purely testing at the moment - not suitable for a daily driver), camera is broken along with the lineage voice and screen recorder crashing.
Click to expand...
Click to collapse
All camera apps ? Even Google s ?
If Google's work, then it's just a prop.
Also yes that's normal since Los uses snap and maybe it needs different props , it may needs a couple different things to call for build and some overlay settings in a config.
The other Los developers should already know how to make this work since they have ported many phones.
Me I never developed in los, I don't know.
kessaras said:
All camera apps ? Even Google s ?
If Google's work, then it's just a prop.
Also yes that's normal since Los uses snap and maybe it needs different props , it may needs a couple different things to call for build and some overlay settings in a config.
The other Los developers should already know how to make this work since they have ported many phones.
Me I never developed in los, I don't know.
Click to expand...
Click to collapse
I haven't tested any others yet. I'm mainly focusing on the audio at the moment
Great job bringing LOS back to life for the G4!
Thanks for your effort! I will monitor this Thread closely and hope you soon find the audio issues
Hi,
Even though I'm not quite experienced, I'd like to join the development of this rom. Right after installing it on my device and reading the logcat, I've partially fixed the audio problem. I've also created a pull request and given enough information on GitHub repository.
Edit: Full message from GitHub
These missing files which had to be under "/system/vendor/etc" folder lead to crashes on the apps which use sound. By placing them to where they have to be, crashes on music player when trying to play any music and video recording are fixed. Although there has been no sound yet, these changes are required in order to prevent crashes.
Also, there may be another way in order to fix crashes instead of doing these changes. It is to edit the paths to "/system/etc/" as the files are already placed there.
I guess the lines for "/system/etc" can be removed as well but I am not sure if there are any system part that uses this directory. It's better to let them stay under "/system/etc" as well.
Additional message:
These changes also fixed handset and earphones. The handset is working on calls and earphones work on video/music now. However, the speaker still doesn't work. Video recording works as well as the built-in microphone does.
Additional message 2:
From now on, neither audio nor screen recorder crash. Both work well.
Click to expand...
Click to collapse
berkantkz said:
Hi,
Even though I'm not quite experienced, I'd like to join development of this rom. Right after installing it on my device and reading the logcat, I've partially fixed the audio problem. I've also created a pull request and given enough information on GitHub repository.
Click to expand...
Click to collapse
Brilliant!!! Thanks Don't worry about not being experienced - this is my first proper project at getting a rom going, so I'm learning as well
New H815 build out (20180428) with fixed audio, camera and screen/audio recorder. This has given rise to the fact that BT calling is indeed broken like it is on AOSCP
H811 build coming out soon.
Massive thanks to @berkantkz, without whom I wouldn't have been able to do it
Edit: H811 build is up as well now
LineageOS 15.1 (Beta v1.01)
for Moto E5 Play (james)
Boost Mobile/Virgin Mobile/Sprint Variants
LineageOS 15.1 is a free, community-built, aftermarket firmware distribution of Android 8.1.0 Oreo, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project (AOSP) with extra contributions from a myriad of developers and enthusiasts within the Android community. LineageOS can be used without need of having any Google application installed. LineageOS does still include various hardware-specific code, which is slowly being open sourced.
LineageOS Source Code: https://github.com/LineageOS
LineageOS Changelog: https://www.cmxlog.com/15.1
LineageOS Gerrit Code Review: https://review.lineageos.org/#/q/status:open
Kernel Source Code MSM8920: https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-OCP27.91-23
This is a LineageOS 15.1 build based on Project Treble. More specifically, it is based on XDA Recognized Developer @phhusson's Phh-Treble and his ARM32 Vanilla GSI. Because the Moto E5 Play is officially supported by Project Treble, I have taken the vanilla GSI and made it bootable for our device. Along with a modified kernel from the stock Android 8.0.0 OS, I've compiled a TWRP flashable Lineage 15.1 custom ROM for the james. This vanilla ROM is very much bare-bones -- no GApps, no SU addon, etc. -- and is likely chocked full of bugs at this time. So, without further ado.....
DISCLAIMER: Your warranty is hereby null, void, and held for naught. By proceeding further, you are assuming full responsibility for any good or bad consequences which may result from flashing this ROM. While I have installed and tested this ROM on my own device, and can confirm boot up and basic functionality, I cannot yet elaborate on bugs and other types of instabilities. This is truly a work in progress at this point. So, to sum it up, FLASH THIS AT YOUR OWN RISK. I am hereby absolved of any liability from bricked, damaged, or otherwise inoperable devices.
SPECIFICATIONS:
Android Version: 8.1.0
Build: OPM2.171026.006
Kernel Version: 3.18.71
Security Patch Level: June 5, 2018
Build Date: June 26, 2018
LineageOS API: llama (9)
STATUS: Beta
Created: Thu, July 29, 2018 15:00:00
REQUIREMENTS/INSTRUCTIONS:
1. First and foremost, an unlocked bootloader is necessary;
2. TWRP custom recovery installed and force encryption disabled. Please visit @CodyF86's thread on how to do this, and please be sure and hit the THANKS button if you used his work;
3. Download the ROM zip from the below download link and store it on external device storage;
4. Boot your device into TWRP recovery;
5. Select Wipe, and swipe to perform a factory data reset. Now, select Wipe and then Format Data, and follow all prompts to commence formatting;
6. Reboot Recovery (often necessary to ensure proper mounting of /userdata after formatting the partition;
7. Select Install, navigate to the location of the ROM zip, and swipe to commence installation;
8. Reboot System (1st boot up can take around 3 minutes or more);
NOTE: This vanilla ROM does not include GApps so, if you want GApps, visit https://opengapps.org/ and download a package of your preference. If installing GApps, simply flash the package during the above installation process after Step 7, then Reboot System.
BUGS:
Working:
RIL
Bluetooth
WiFi
Not Working:
Camera
Please properly report bugs, with submission of a bug report if you know how. If not, please give a clear and concise explanation of the bug. NOTE: Please DO NOT report bugs if you are running modifications such as Magisk Modules, Xposed Framework, etc. This makes it nearly impossible to pinpoint, troubleshoot and fix bugs and instabilities. Also, please know that I am not a ROM maintainer for Project Treble or LineageOS. So, while I will do my best to resolve bugs and provide some bug fixes and updates, please do not ask for ETAs. I work 55+ hours a week at Motorola Mobility, LLC., so I don't always get a lot of free time.
THANKS & MENTIONS:
Thanks to @SuperR. for his awesome Windows Kitchen;
Thanks to @CodyF86 for breaking ground and building TWRP for the james;
Thanks and credits to @phhusson for his Phh-Treble Vanilla GSIs;
Thanks to the entire LineageOS team;
DOWNLOAD LINK:
LineageOS 15.1 (Beta v1.01): https://drive.google.com/open?id=1TPl879IQvVH2ajYG6ZJ2kobp_rMgRfE5
Guys please provide feedback and feel free to contribute on this. I have more custom ROMs on the way such as ResurrectionRemix, PixelExperience, and AOSP-Extended. But I don't have a lot of free time to maintain ROMs, so I'm going to need help ironing out bugs and compiling patches.
Hum that's weird, wifi works for me on Moto E5
For camera, I have the fix pending for two months, I just haven't committed it yet -_-'
Thanks so much for commenting. After wiping the Dalvik/ART & /cache, WiFi is now working. I'll keep my eyes open for your pending camera commit.
Update: WiFi,, Bluetooth and RIL appear to be functional. Over the next few days I'm in hopes that user feedback will provide me with more insight as to bugs & instabilities.
this boots fine on e5 plus after flashing e5plus-noverity kernel and magisk as for ril data and all i cant tell you until i fix my sprint e5plus modem files messed them up by accidently flashing a differnt e5plus rom will report back more when i manage to completly fix my phone
allenjthomsen said:
this boots fine on e5 plus after flashing e5plus-noverity kernel and magisk as for ril data and all i cant tell you until i fix my sprint e5plus modem files messed them up by accidently flashing a differnt e5plus rom will report back more when i manage to completly fix my phone
Click to expand...
Click to collapse
Ok thanks @allenjthomsen. Yeah there seems to be many of us in the same boat -- patiently waiting for Motorola Mobility to either release or "leak" some factory images for the Moto E5 series devices. I'm actually drafting a baseband radio thread now for the James, compiling a TWRP flashable installer to restore radio/modem firmware and reset the network config to factory default. I know of a couple of devs over at Android Central that may can dump baseband partitions for your device. Also, please provide me with your Baseband Version. Thanks...
I have a bootable Android 9.0-DP3 ROM for the James. Lots of stuff broken, so I'm going to get it more stable, implement a working GApps package, etc. before posting it. Going to try and get our camera app working on this ROM also, maybe see if I can talk @phhusson into sharing his fix. Hint hint
i can dump files if needed and btw i tried your lineage os and i couldnt get data but got signal and camera crash other than that it ran great on my replacement E5 Plus Sprint model
allenjthomsen said:
i can dump files if needed and btw i tried your lineage os and i couldnt get data but got signal and camera crash other than that it ran great on my replacement E5 Plus Sprint model
Click to expand...
Click to collapse
Thank you for your feedback. I have a camera fix underway. As far as data connectivity I've had some issues myself, so I'm dissecting that issue too.
I have the same problem with the camera with GSI roms on a motorola e5 plus (rhannah). I get the impression that Motorola has something not standard in its handling of cameras of this family of devices
What DPI is this device? 320dpi right?
nachoxda79 said:
What DPI is this device? 320dpi right?
Click to expand...
Click to collapse
Yes. 320dpi (xhdpi); 1280 x 720 resolution
MotoJunkie01 said:
Yes. 320dpi (xhdpi); 1280 x 720 resolution
Click to expand...
Click to collapse
Thanks dude.
@MotoJunkie01 Hey, if you get a second pm me. I got your rom to boot on the g6 play by switching kernels, so I decided to compile a treble rom myself and I can compile it successfully, but the rom won't boot...clang seg faults like 30 times trying to compile it, so I think that is the actual issue, but wanted to bounce a few things off of you. No worries, thanks.
CodyF86 said:
@MotoJunkie01 Hey, if you get a second pm me. I got your rom to boot on the g6 play by switching kernels, so I decided to compile a treble rom myself and I can compile it successfully, but the rom won't boot...clang seg faults like 30 times trying to compile it, so I think that is the actual issue, but wanted to bounce a few things off of you. No worries, thanks.
Click to expand...
Click to collapse
I tried to PM you but sending failed. I'll get on my PC and login through the browser. I think my messaging settings are preventing the PM from sending.
Thanks for your work. Would this Lineage ROM work for the T-Mobile variant of the E5 Play (XT1921-3)?
konradsa said:
Thanks for your work. Would this Lineage ROM work for the T-Mobile variant of the E5 Play (XT1921-3)?
Click to expand...
Click to collapse
Not likely. There's no real danger in trying it because my installer does not flash sensitive partitions, but only /system & /boot. While I don't perceive any chance of bricking your device, it would be at your own risk. You would be better off flashing your device with a Treble GSI. While this ROM is technically based on a Project Treble GSI, I done some mods to the stock boot image and compiled the installer from porting. Hence, the ROM should not be characterized as a GSI itself. By the way I do have firmware for the xt1921-3, which I will be posting in my Moto E5 firmware thread over the next couple days.
my model is moto e5 play (XT1920-15)
my model is moto e5 play (XT1920-15) , will it work also my codename is not james. also how we can backup stock rom. before trying dont we need stock rom for this phone , so we can be secure.
rehannasim said:
my model is moto e5 play (XT1920-15) , will it work also my codename is not james. also how we can backup stock rom. before trying dont we need stock rom for this phone , so we can be secure.
Click to expand...
Click to collapse
I can only confirm compatibility with the xt1921-5. But before trying it, as you have correctly noted, it is crucial to have a suitable backup of your /system and /boot partition, just in case anything goes wrong. Most times, backups are made using a custom recovery such as TWRP. However I'm not familiar with your variant and therefore do not know of a working TWRP for your device. I will check my firmware archive and see if I can find a package for your model.
Update; unfortunately, at this time I cannot find firmware or custom recovery for your variant. I would urge you to post under the Q&A thread and ask if any members have your model.
Welcome to MIUI sGSI For Galaxy J7 2017
TESTED ON J730X
Some information you should know..
This is a fully working MIUI sGSI with Android version 9.0
If you want to report a Bug, read the F.A.Q First Then provide a logCat OR LoggingKit.zip with detailed explanation
Read the instructions and the F.A.Q Before installing the rom or posting a reply.
I don't own any files here, except patch files.
So, we are here with sGSI. It's normally called "unstable" and "not for daily usage" so users are recommended to go for GSI. But GSI lacks features and has AOSP-like design that some users may be bored of that. And now we finally break that law. sGSI can now be used as daily drivers.
As the nature of these sGSI go, it was a non stop battle for almost 3 weeks straight to get it to this point where all features are working as expected. if you appreacite this work Hit the Thanks button
RULES OF POSTING : READ everything before commenting, And especially the instlal steps, the rom has been tested throughly for a long time, so if you have an critical issue like not booting or no sim, you missed the instructions, posts that are irrelevant to this project will be ignored(Constructive criticism is welcomed). If you do face a new bug however, dont just say "hey bug here" provide more information, and a LOGCAT, bug reports without logcats will most likely be ignored.
FEATURES:
Based on MiuiMiX 11 by MMX Team 9.12.26 using ErfanTools
Android 9.0
MIUII 11 Features
Semi-SIM support (Currently one SIM only)
Heavily debloated
Zipaligned
Very Optimised
Battery and performance focused
Full MIUI without missing vital apps
Rootable with Magisk
RMM/KnoxGuard/Defex Free
And many more
Kernel:
You can choose either latest CronosKernel by @ananjaser1211, or KRAKEN kernel by @SPARTANICUS
Install steps:
ensure you have LATEST TWRP from Here
Download all the files in the DOWNLOAD section
Wipe everything (SYSTEM,DATA,CACHE,DALVIK and preferably Internal storage all together)
Flash Project Spaget 3.0 (not X!) here and follow the steps there.
Flash MIUI-Aonly-9-20191230-ErfanGSI.img to SYSTEM
Flash your desired kernel, either Cronos or KRAKEN (must be using Treble version)
[IMPORTANT] Flash Magisk in order to have patch working
Flash sGSI-Patch.zip
Flash NFC Patch
After the boot animation is on for 30~60 Seconds. Hold VolumeDown+power until the device reboots
Install Google Play Services apk in Downloads section in order to get setup working
Setup your rom and READ the F.A.Q for more information.
BUGS:
Signal bar doesn't work (always empty) but it's acturally working
FM Radio (No FM Radio app in image)
Only one SIM is working at the moment
VoLTE not working (need another fixes)
SCREENSHOTS:
Imgur
CREDITS:
IF you helped in this GSI and i forgot you, tell me in a PM or in a reply
@ananjaser1211 for his Project Spaget, CronosKernel and HUGE contribution for Exy7870
@SPARTANICUS for KRAKEN Kernel
@SrCDA for his NFC patch
@erfanoabdi for his tools to port GSIs
And the rest of EliteTeam
DOWNLOADS ARE IN POST 2
DOWNLOADS:
Official Treble support Group : Telegram
----------------------------------------------------------------
All files are uploaded here: Google Drive
GSI: Here (My Google Drive acted up and does not let me upload any more files)
FAQ:
Good idea to read this F.A.Q While the rom is installing
Notes:
Q : Brightness bar not working / Camera doesn't work
A : You have flashed Spaget X instead of Spaget 3.0. Reinstall again
Q : Phone doesn't detect any SIM cards
A : Flash latest Cronos/KRAKEN kernel
Q : Everything on my screen is so small [J730 only]
A : Go to Settings > Developer settings > Set screen density to 411
Q : I got front camera stretch
A : Change resolution from 16:9 to 4:3
Q : Can I use front flashlight?
A : No, Samsung has their own libs, for now no apps can use front flashlight. Back flashlight still works
Q : How is battery Life ?
A : With some tests and some cycles, it will be better than stock due to optimzations
Q : the phone wont install any apps
A : Reboot
One more
does the rom have some type of error for daily use
VoLTE : Not work, need flash Magisk Module and using Phone App to VoLTE work
All work normal, just a Android Pie but like Android Q MIUI :good:
Great work
The first boot is so longer? I've waiting more than 10 minutes and don't boot. Or is bootloop?
And i've not found the MIUI-Patch.zip, only sGSI-Patch.zip
What android version is this? Can i flash the official magisk? There's no camera stretch bug? Like other gsi rom?
gabriel.oliveira.brito said:
The first boot is so longer? I've waiting more than 10 minutes and don't boot. Or is bootloop?
Click to expand...
Click to collapse
After the boot animation is on for 30~60 Seconds. Hold VolumeDown+power until the device reboots
gabriel.oliveira.brito said:
And i've not found the MIUI-Patch.zip, only sGSI-Patch.zip
Click to expand...
Click to collapse
Thanks for noticing, I forgot to rename the file.
NindoS said:
VoLTE : Not work, need flash Magisk Module and using Phone App to VoLTE work
Click to expand...
Click to collapse
I don't use VoLTE, so I couldn't test if it works. Can you tell me which Magisk module you used?
NindoS said:
All work normal, just a Android Pie but like Android Q MIUI :good:
Great work
Click to expand...
Click to collapse
Nice
Updated FAQ and sGSI patch. I forgot to add an important fix in patch, so anyone using this MIUI, reflash the new patch right now :good:
I tried again, followed all the steps as requested. On the first boot, I restarted the phone after approximately 30 seconds. But I still bootloop. I'm using Project Spaget 3.0, but I can't find a topic in the forum. Could you send me your Project Spaget zip file?
My logcat is on attachments
nfc not working. I installed the fix on the twrp and it failed, I had to install the fix when I started the cell phone so that it did not give me an error and it appears as a module installed in magisk but it does not work
Working fine but having bug
I have a bug with the WhatsApp application when viewing the stories that contain videos are not played and the app freezes.
I attach my log Cat about the error
I have problems with external storage, the system does recognize it but with third-party apps such as file explorer or streaming apps like spotify they don't detect external storage, I've tried to modify the vold.fstab and nothing. some fix they have
dani_hedz said:
I have problems with external storage, the system does recognize it but with third-party apps such as file explorer or streaming apps like spotify they don't detect external storage, I've tried to modify the vold.fstab and nothing. some fix they have
Click to expand...
Click to collapse
It's sGSI related problem, don't know why it happens
argenmu09 said:
nfc not working. I installed the fix on the twrp and it failed, I had to install the fix when I started the cell phone so that it did not give me an error and it appears as a module installed in magisk but it does not work
Click to expand...
Click to collapse
It works for me
Wi-Fi not working
Hi!
First: I am NOT a dev or contributor of this rom. Please visit before going ahead: https://forum.xda-developers.com/t/gsi-11-lineageos-18-x-gsi-all-archs.4205461/
Second: You do anything at your own risk and should know how to recover a non booting device!
Just playing around with this rom on my SHT-AL09, tested on version 20210317 so far:
Working
- Mobile network including 4G (German carrier Telekom)
- Outgoing & Incoming calls
- Bluetooth
- 2,4 & 5g Wifi
- Front & Back camera
- Video recording
- MTP
- SDcard
- GPS (seems to be working on Telegram)
- Fingerprint reader
Not Working:
- Mobile network icon shows no signal strength
- VoLTE
- VoWIFI
How to install:
- Make a backup.
- Device needs to have bootloader unlocked.
- Visit the above link again --> sourceforge --> lineage-18.x and download version "...treble_arm64_bv*" + unpack it.
- Visit: https://www.xda-developers.com/flash-generic-system-image-project-treble-device/ (I have done it via bootloader method.)
How to update:
- Dont know yet.
Unfortunately I cant get TWRP to work, so I cant test gapps or root. If you have a clue, please let me know - thx!
So you tested a GSI Lineage ROM on the your M5, is it rooted? Should be great to see magisk included in any room, i use Phh treble Quack, it's pre-rooted with su.
Hi @massima
according to this post by one of the dev's Magisk is broken and supersu should be used instead. I can confirm that this works. You do not need working TRWP, just install the app from fdroid, as mentioned.
For me the rom works well, but as I use the tablet without gapps and only as a youtube player (YT Vanced works fine!), I have not really tested "real world szenarios" yet. Also I cannot say something regarding camera quality and battery performance in comparsion to the stock rom, as I went straigt to Linage 15.1 when I got the tablet in 2018.
Yes, i remember that magisk is incompatible with GSI images. I never used Lineage, for me an AOSP experience is the best. I'm waiting to upgrade to Quack when it will receive its last update probably a vanilla edition because the gapps version has a RO system partition and the vnk version doesn't fit, every version is prerooted with phh-su.
Thanks
P.S.: i added a page of our beloved M5 in the phh's wiki.
massima said:
Yes, i remember that magisk is incompatible with GSI images. I never used Lineage, for me an AOSP experience is the best. I'm waiting to upgrade to Quack when it will receive its last update probably a vanilla edition because the gapps version has a RO system partition and the vnk version doesn't fit, every version is prerooted with phh-su.
Thanks
P.S.: i added a page of our beloved M5 in the phh's wiki.
Click to expand...
Click to collapse
Hi Massima,
Sorry for this noob question - where would I find the M5 entry in the phh's wiki?
And generally, is it possible to install a treble rom on the M5 with gapps and functioning bluetooth? I've been using Openkirin so far but no luck with bluetooth there.
Many thanks for any help you can offer.
spoo333 said:
Hi Massima,
Sorry for this noob question - where would I find the M5 entry in the phh's wiki?
And generally, is it possible to install a treble rom on the M5 with gapps and functioning bluetooth? I've been using Openkirin so far but no luck with bluetooth there.
Many thanks for any help you can offer.
Click to expand...
Click to collapse
This is the link, just search your device mine is the M5 8" wifi (sht-w09). You can flash a vanilla (no gapps), the gapps version (be aware is Read Only). if you need a rewritable System partition download the vndklite version (arm64-AB-gapps-vndklite is 2,9Gb but it will not fit in the standard partition <2,9GB ).
I haven't ever tested the bluetooth so i can't say if it works.
Thanks for your reply and the link. I'll check it out if I can figure out the flashing etc.
Flashing seems relatively straightforward. Curious if Bluetooth works. Mine is the CMR-W09-C432
Thanks for the report. This finally gave me confidence to upgrade mine. I did an upgrade from huawai 9.1 to ASOP Phhusson with gapps. I had to register the device at google to get access to gapps -pretty straightforward (https://www.google.com/android/uncertified/). It was relatively straightforward and took about an hour, which was mainly spend on reading.
Steffe89 said:
Thanks for the report. This finally gave me confidence to upgrade mine. I did an upgrade from huawai 9.1 to ASOP Phhusson with gapps. I had to register the device at google to get access to gapps -pretty straightforward (https://www.google.com/android/uncertified/). It was relatively straightforward and took about an hour, which was mainly spend on reading.
Click to expand...
Click to collapse
May I know how to do because when I key command in my pc adb shell, it shows:
C:\adb>adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \ "select * from main where name = "android_id";"'
/system/bin/sh: sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \ select * from main where name = android_id;: inaccessible or not found
Thanks
toystory2000 said:
May I know how to do because when I key command in my pc adb shell, it shows:
C:\adb>adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \ "select * from main where name = "android_id";"'
/system/bin/sh: sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \ select * from main where name = android_id;: inaccessible or not found
Thanks
Click to expand...
Click to collapse
Sure. There's a typo in the line, hence i wrote it in several commands, e.g.
> adb shell
> sqlite3 /data/data/com.google.android.gsf/databases/gservices.db
> "select * from main where name = "android_id";
Anyone know how to install magisk? I succeed patching recovery_ramdisk.img. However, does not flash properly (no warnings). My guess is that phh.superuser interveens and needs to be uninstalled (https://github.com/phhusson/device_phh_treble/blob/android-9.0/phh-securize.sh). As adb root i'm unable to do so though.
@Steffe89
"Magisk compatibility is mostly broken since Android 11 - use PHH-SU instead. Install the app and you'll get root for apps."
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Besuz said:
@Steffe89
"Magisk compatibility is mostly broken since Android 11 - use PHH-SU instead. Install the app and you'll get root for apps."
[DISCONTINUED][GSI][11] LineageOS 18.x GSI (all archs)
Background: This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019. LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance...
forum.xda-developers.com
Click to expand...
Click to collapse
Maybe.... According to many posts v21 brings stable magisk support to android 11 so that is a little contradictory....
Anyhow, I'm not really interested in root. I want try and see if magisk with universal patch could make root-hating apps and widewine L1 drm work.
Steffe89 said:
Sure. There's a typo in the line, hence i wrote it in several commands, e.g.
> adb shell
> sqlite3 /data/data/com.google.android.gsf/databases/gservices.db
> "select * from main where name = "android_id";
Anyone know how to install magisk? I succeed patching recovery_ramdisk.img. However, does not flash properly (no warnings). My guess is that phh.superuser interveens and needs to be uninstalled (https://github.com/phhusson/device_phh_treble/blob/android-9.0/phh-securize.sh). As adb root i'm unable to do so though.
Click to expand...
Click to collapse
Thanks a lot
Steffe89 said:
Sure. There's a typo in the line, hence i wrote it in several commands, e.g.
> adb shell
> sqlite3 /data/data/com.google.android.gsf/databases/gservices.db
> "select * from main where name = "android_id";
Anyone know how to install magisk? I succeed patching recovery_ramdisk.img. However, does not flash properly (no warnings). My guess is that phh.superuser interveens and needs to be uninstalled (https://github.com/phhusson/device_phh_treble/blob/android-9.0/phh-securize.sh). As adb root i'm unable to do so though.
Click to expand...
Click to collapse
You're probably aware of that anyway, but just checking that you didn't use "fastboot flash ramdisk patched_boot.img" or "fastboot flash recovery_ramdisk patched_boot.img"
spoo333 said:
You're probably aware of that anyway, but just checking that you didn't use "fastboot flash ramdisk patched_boot.img" or "fastboot flash recovery_ramdisk patched_boot.img"
Click to expand...
Click to collapse
sorry, meant to write: ... not "fastboot flash ramdisk patched_boot.img" but "fastboot flash recovery_ramdisk patched_boot.img"
I am not really sure that I did I correctly, but yes. I followed these instructions https://topjohnwu.github.io/Magisk/install.html#Huawei.
I think the problem is that I failed to remove phh-
Perhaps try again and check that you've got recovery_ramdisk as the target?
I'm also curious because I'm currently on Openkirin and would like to try what you've been doing. Currently have Magisk installed and wouldn't want to be without it because of Adaway etc.
Do you mind describing your steps: you had official Huawei 9.1 installed, then unlocked the bootloader, flashed Phhusson and then added Gapps?
@spoo333: i tried to send an image from my M5 to the pc and viceversa with bluetooth, no problem.
@Steffe89:
i read in the phh' s telegram channel to remove root with the securize option, then clean the cache. I did't test it.
I found this in the phh's gsi channel:
flash super su phh
create sbin
edit init.environ.rc (it's on /)
add line
export PATH /sbin:/vendor/bin:/system/bin
save
remove su in system/bin
done flash magisk
Once again i don't test it, i'm using phh supersu. See/write here.
massima said:
@spoo333: i tried to send an image from my M5 to the pc and viceversa with bluetooth, no problem.
@Steffe89:
i read in the phh' s telegram channel to remove root with the securize option, then clean the cache. I did't test it.
I found this in the phh's gsi channel:
flash super su phh
create sbin
edit init.environ.rc (it's on /)
add line
export PATH /sbin:/vendor/bin:/system/bin
save
remove su in system/bin
done flash magisk
Once again i don't test it, i'm using phh supersu. See/write here.
Click to expand...
Click to collapse
Massima, that's encouraging to hear re bluetooth. Hope Bluetooth headphones would work too...