{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* Your warranty is now (expired?) 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.
*/
I'm working on Ubuntu Touch port for Asus Zenfone 2 Laser (Z00ED).
For more info - from Ubuntu Touch GSI:
What is Ubuntu Touch?
Ubuntu Touch is the touch-friendly mobile version of Ubuntu.
This operating system is developed and maintained by UBports: An international community of passionate volunteers.
This means Ubuntu Touch is 100% community driven and independent.
What is Halium?
Halium is the collaborative project to unify the Hardware Abstraction Layer for projects which run GNU/Linux on mobile devices with pre-installed Android.
Click to expand...
Click to collapse
This port of Ubuntu Touch is running on Halium 7.1, which is based on Android 7.1 (Nougat).
NOTE: This port is not stable! Don't use it as your daily driver. You can, however, set up dual booting with Android.
What works, what doesn't work + porting notes
Everything can be found here.
We're looking for someone to test on Z00RD. It should at least reach the Ubuntu Touch splash screen. Read the note about 8 GB devices below.
How to install
Format data (recommended) and flash the downloaded ZIP file in a custom recovery.
The default password is phablet
NOTE: 8 GB variant is NOT SUPPORTED! Flash only on 16 GB variants. We're trying to find a way to flash it on 8 GB variants, but it's not available right now because Ubuntu Touch needs at least 5.6 GB in /data. Please wait until this way is available. Don't even try to flash on 8 GB devices.
Download
SourceForge
-----------------
If you find any bugs that aren't mentioned in the device checklist, make sure to report them
-----------------
Screenshots
See the attachments.
Device sources (UBports):
Device tree
Common device tree
Kernel
Vendor tree
Device manifest (for Halium)
The device manifest is already included with the Halium 7.1 source tree.
XDA:DevDB Information
Ubuntu Touch Z00ED, ROM for the Zenfone 2 Laser
Contributors
adazem009
Max Mesa
Halium version: 7.1
ROM OS Version: 16.04 (xenial)
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Upgrade to Android M first
Based On: Halium / LineageOS
Version Information
Status: Beta
Created 2020-11-26
That's sooooo cool! Can't wait to test a stable version. Keep up the good work!
Banasura said:
That's sooooo cool! Can't wait to test a stable version. Keep up the good work!
Click to expand...
Click to collapse
Thanks
I'll upload the initial build today and add a link to the thread.
Anyway, I'm surprised that people still use this device. :laugh: It's pretty old and I thought that there are only a few people who use it.
Update - 11/28/2020
v0.1.0
Initial build has been uploaded. You can download it here.
Known bugs:
Camera app reboots to EDL
Sound doesn't work
Flashlight doesn't work
Bluetooth probably broken
SIM card not detected
WiFi has to be enabled manually using SSH.
Vibrator doesn't work
Pressing the power button will show the power menu.
Update - 11/28/2020
v0.1.1
Download
Optimized display settings
Nice!
Great...but please make it stable
nhASIF said:
Great...but please make it stable
Click to expand...
Click to collapse
I'm working on it. The next build should improve performance and fix WiFi.
looks great!
does usb tethering is working?
i would try it on z00rd
upd: bootloop =(
apostrof said:
looks great!
does usb tethering is working?
i would try it on z00rd
upd: bootloop =(
Click to expand...
Click to collapse
It's probably because of missing udev rules. I'll try to add them for Z00RD in the next builds.
Max Mesa said:
I've installed it. Nice job! The ROM is pretty interesting, but laggy, it looks like hw acceleration (gpu) is broken, but I am not sure. Also I've found some new bugs in addition to the listed ones. Navbar, DT2W (double tap to wake), MTP (connection to the PC) and Bluetooth are not working. APT can neither update sources list nor install anything. Offline charging (on powered off smartphone) shows ??/100%. Usual TWRP can't decrypt FBE and access Ubuntu files. So, that's all I've found. Luckily, SD card works, and WiFi needs only one command to be enabled (echo sta > /sys/module/wlan/parameters/fwpath). Pressing power button seems to work as intended. I'll watch this thread and try new versions when I have time. Here are some screenshots:
Spoiler: Screenshots
View attachment 5205977
View attachment 5205979
View attachment 5205981
View attachment 5205983
View attachment 5205985
View attachment 5205987
View attachment 5205989
View attachment 5205991
View attachment 5205993
View attachment 5205995
Click to expand...
Click to collapse
View attachment 5205997
Thanks for trying it out, I'll do some testing and add the bugs to the list. For apt update, this is normal. The root filesystem is mounted read-only by default. To install packages, you need to remount it read-write: sudo mount -o remount,rw /
I had a break for a few months, but will continue with the development again
I've set up the build system again, and I'm going to do some testing and make WiFi working on boot.
Update - 03/17/2021
Screenshots were added to the thread.
Next build is coming this or the next month.
Update - 03/27/2021
v0.1.2
Download
Fixed camera app rebooting to EDL. Camera still doesn't work, but at least the app doesn't crash the OS.
Applied AppArmor kernel patches
Fixed vibrator
Fixed WiFi, it now enables automatically at boot.
Initial support for Z00RD (untested)
Known issues in this build:
Hotspot works, but it breaks WiFi. Either reboot or run this command (as root, NOT using sudo) after using hotspot:
echo sta > /sys/module/wlan/parameters/fwpath
Notes:
Initial support for Z00RD is here. I can't test it as I don't have this device. Anyone who has got a Z00RD, please test this build and tell me if it's stuck in a bootloop. If it is, you'll need to connect the device using a USB cable and login using SSH as `[email protected]`. Then, execute these commands:
sudo -i # And enter your password
cat /var/lib/lxc/android/rootfs/ueventd*.rc|grep ^/dev|sed -e 's/^\/dev\///'|awk '{printf "ACTION==\"add\", KERNEL==\"%s\", OWNER=\"%s\", GROUP=\"%s\", MODE=\"%s\"\n",$1,$3,$4,$2}' | sed -e 's/\r//' >/usr/lib/lxc-android-config/70-Z00RD.rules
reboot
The device should reboot and boot to the Unity 8 screen. If this doesn't work, these builds will never be compatible with Z00RD, and I'd need to use the Z00RD's device tree instead. Again, I don't have this device, so I won't compile it for Z00RD.
I was trying to make modem working, but it crashes the device and reboots to emergency download mode. If you have some experience with this device (e. g. ROM building, especially Nougat ROMs), tell me if you've ever experienced this. PM me and I'll tell more about this issue.
apostrof said:
looks great!
does usb tethering is working?
i would try it on z00rd
upd: bootloop =(
Click to expand...
Click to collapse
I uploaded build v0.1.2. Can you test it on Z00RD? I don't have this device, so you have to add udev rules manually. Read the post above for more info.
i try to install 0.1.2 - it does not boot, then i to connect ssh, but i cant connect using SSH as `[email protected]`
upd: 1 thing: the package was installed too fast, but wrote that it is ok
apostrof said:
i try to install 0.1.2 - it does not boot, then i to connect ssh, but i cant connect using SSH as `[email protected]`
upd: 1 thing: the package was installed too fast, but wrote that it is ok
Click to expand...
Click to collapse
Do you see the splash screen?
If yes, you should be able to connect if you're on Linux.
ssh [email protected]
no, didn't see the splash screen
apostrof said:
no, didn't see the splash screen
Click to expand...
Click to collapse
What do you see when you boot? Is it stuck at Asus logo or a black screen? The kernel I built should work for Z00RD too, maybe something is wrong with the Android container.
on the boot i see only default asus logo, if i turn off the phone and connect the charger - i see "Charging ??\100"
apostrof said:
on the boot i see only default asus logo, if i turn off the phone and connect the charger - i see "Charging ??\100"
Click to expand...
Click to collapse
Yeah, that charging "animation" bug is known. I don't know why it doesn't boot, but what do you see in your computer when you connect the device? Connect it to a PC and hold the power button. If you see something like Halium initrd Failed to boot, it means it failed to mount the rootfs or it failed because of some weird kernel configs.
Related
Hello everybody, I'm glad to share these days' work of bringing Marshmallow to the OnePlus One.
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.
*/
This ROM is based on CAF release LA.BF.1.1.3-00110-8x74.0, with some little modification to some components to make it build. The kernel is based on CM12.1. You can check the kernel source on my GitHub. Links will be posted later.
Nearly all basic feature should be working: 4G data, 4G->3G fallback on calls, SMS, camera/camcorder, BT, WiFi, MTP, 4K recording, HW decoding etc.
kexec hardboot is supported.
Known issues:
1. Stock camera doesn't work well. Here is a list of comparison:
Feature - Working on Stock camera - OppoCamera port - CameraNextMod?
Switching front/back cam - No - Yes - Yes
Camcorder <=1080p - No - Yes - Yes
4K Recording - No - No - Yes
Click to expand...
Click to collapse
(maybe I should get a monospace font in Firefox)
2. Battery drains... a little faster? (Just a little)
3. The ROM comes with ancient Launcher2. Launcher3 is not included. I will post this as an attachment. Launcher3 has been added since 20151018
4. Picture in apps are sometimes automatically zoomed out (and distorted) and can not be zoomed in. Is this a common problem among AOSP-based Marshmallow ROMs? I tried AOSP and CAF sources, and they both have the same issue. Need to change DPI via build.prop
5. Security related: SELinux is disabledpermissive in 20151018. HW Crypto is not working. Software-based credentials storage.
6. No gestures (DT2W etc) Workaround available in Q&A
7. Kernel panics/reboots on switching adb on & off.
8. WiFi AP still runs on 2.4G even when 5G is selected.
If you find more issues, feel free to post here. However, I may not be able to solve them since schoolwork is so heavy... And this ROM may not be updated regularly.
Video Tutorials by @udimars30:
https://www.youtube.com/watch?v=XxjnTae2nCM - How to install ROM and Gapps
https://www.youtube.com/watch?v=kWZcxVs992c - How to get root
https://www.youtube.com/watch?v=vZ7qW4j3Kso - How to enable softkeys, Now on Tap
Thanks!
Q&A:
1. Kernel Compatibility
The kernel of this ROM is based on CM12.1, but not exactly the same. You can not use kernels built for CM12.1 with this ROM. Marshmallow requires new features like updated SELinux, uid_cputime, etc, but CM12.1 source does not contain these features. You can take a look at commits and it will be clear.
Click to expand...
Click to collapse
2. Recovery Compatibility
I am using TWRP 2.8.7.0 with MultiROM support (TWRP_multirom_bacon_20150803-00.img from MultiROM thread). If you can not get the ROM installed properly, please try updating your recovery.
Click to expand...
Click to collapse
3. Rooting
Since this is a experimental build, I have turned off SELinux completely. SELinux is permissive. Just flash SuperSU 2.50 zip in the recovery and it will be fine.
Click to expand...
Click to collapse
4. F2FS Support
The kernel has F2FS driver builtin and corresponding entries in fstab file (as CM does). Vold has F2FS files as well, so you can give it a try. But I can not guarantee that it will work flawlessly.
EDIT: Some people tested and reported it not working. Make a backup before you try.
Click to expand...
Click to collapse
5. GApps
I'm using DeltaGapps with SetupWizard removed (yes it is the one that keeps force closing. you can disable that via adb as well). I think the lack of permissions(appops_whitelist.xml I guess) caused this failure. After allowing every permission required by Google apps and adding the account manually, Sync and Store works as expected. Now on Tap seems broken. Maps is working, and gets a lock in secs..
There are some other GApps package links in the first few pages. Some people say Now on Tap works with them, you can have a try.
Click to expand...
Click to collapse
6. Disabling HW Keys and Enabling Softkeys - The Easy Way
Code:
echo qemu.hw.mainkeys=0 >> /system/build.prop
reboot # enables soft keys
echo 0 > /proc/touchpanel/keypad_enable # disables hw keys, need to do this on every boot
Click to expand...
Click to collapse
7. Where Is The App Switcher?
If you are comfortable with softkeys, goto 6.
If you are not, goto 3 and take a look at http://forum.xda-developers.com/showpost.php?p=63313126&postcount=115double tap the home key.
Click to expand...
Click to collapse
8. LCD Density
Code:
wm density 440 # if you want 440
wm density reset # self-explanatory
Above will lead to corrupted pics.
Change
Code:
ro.sf.lcd_density=480
to
Code:
ro.sf.lcd_density=VALUE_YOU_WANT
(Note: I did this before installing GApps, not sure if this is related to Google Now Launcher FCs)
Click to expand...
Click to collapse
9. DT2W Workaround
Code:
echo 1 > /proc/touchpanel/double_tap_enable # do this on every boot
Then add this line to /system/usr/keylayout/Generic.kl:
Code:
key 255 POWER
DT2W has been added into settings since 20151027.
Click to expand...
Click to collapse
10. Apps Not Working
Settings -> Apps -> YOUR_APP -> Permissions -> Turn on everything
Click to expand...
Click to collapse
11. Fixing random freezes
http://forum.xda-developers.com/showpost.php?p=63378883&postcount=682
Thanks @The Dork Knight Rises
Click to expand...
Click to collapse
Now screenshot spoiler (with Google Now Launcher):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Discussion Thread:
http://forum.xda-developers.com/oneplus-one/general/discussion-homemade-android-6-0-t3227234
Download:
20151027
https://drive.google.com/file/d/0BwkmhbR5VHpAdWRxQ0ZraVgyT00/view?usp=sharing
Marshmallow's native DT2W setting (thanks CM)
USB MIDI support (What for?)
Fixed some crashes by removing SeempLog (try TiBu and network settings)
Double tap on Home key now brings up Recent View
Added a reboot option in power key menu/global actions menu
Note: if you have drain when NFC is on (or NFC setting is grayed out), please attach a logcat of booting process. I can not reproduce this on my phone... Thanks!
20151018
https://drive.google.com/file/d/0BwkmhbR5VHpAekdWT2NlVWNlNnc/view?usp=sharing
Mirror by @c43211 http://c43211.com/aosp_bacon-ota-eng.hamster-20151018.zip
Mirror by @Killer.shubham http://d-h.st/9fOO
Fixed network mode selection (2G/3G/4G switch)
Fixed network location
DT2W workaround: see Q&A
20151015
https://drive.google.com/file/d/0BwkmhbR5VHpAUVVDYkVJOFJoYVE/view?usp=sharing
Mirror by @itskapil at http://downloadmirror.co/android/tx/aosp_bacon-ota-eng.hamster.zip
Mirror by @Killer.shubham at http://d-h.st/3oBU
Mirror by @c43211 at http://c43211.com/aosp_bacon-ota-eng.hamster.zip
Thanks!
MAKE A BACKUP FIRST!
(I'm using TWRP 2.8.7.0 and it works well with this package.)
Sources:
Kernel: https://github.com/updateing/android_kernel_oneplus_msm8974 (marshmallow branch)
Device tree: https://github.com/updateing/android_device_oneplus_bacon
Blobs: https://github.com/updateing/proprietary_vendor_oneplus
local_manifest: http://www.hastebin.com/netamapate.xml
Hope you can enjoy the new feel of Marshmallow!
Wow! Need this rom to improve.
Excited flashing now!
Sent from my A0001 using Tapatalk
Finally the sweet taste of marshmallow on the OnePlus One!
Great work ! ^_^
Battery drains faster?
Guess I'll wait a little bit longer, as it's the main reason I wanna switch to M.
Kernel dilemma
If the kernel on it is based on cm 12.1 .. Can we flash any other kernels that work with CM 12.1? It should work or atleast i hope so! But yeah I'll try and get back!
Cheers! Keep up the good work!
Do we need to flash gapps & supersu?
Sent from my A0001 using Tapatalk
will it work with F2FS ? separate build would be helpful, if its not tested i will test it
---------- Post added at 11:06 AM ---------- Previous post was at 11:05 AM ----------
horizon_KJ said:
If the kernel on it is based on cm 12.1 .. Can we flash any other kernels that work with CM 12.1? It should work or atleast i hope so! But yeah I'll try and get back!
Cheers! Keep up the good work!
Click to expand...
Click to collapse
i guess it would be tweaked for more compatibility to android 6.0
Great work man !!
Anyone flashed it successfully?
Nice achievement! Glad to see you made it boot.
Finally the bacon.
Was almost regretting for getting this phone
~KV said:
Anyone flashed it successfully?
Click to expand...
Click to collapse
I'm on F2FS didn't tested it
Killer.shubham said:
I'm on F2FS didn't tested it
Click to expand...
Click to collapse
If you flashed it, go to terminal to see if it's on f2fs or not?
Finally ...!!!!
Will test soon ?
This Rom's developer is little busy so we should get other developers work on it and probably get this thread featured?
Tested and WORKING ( I don't if f2fs works)
as a reminder to everyone.. .NO ETA's pls. lets respect the dev.. compiling is already a good thing, and making it boot is a great achievement..
ianstump said:
Tested and WORKING ( I don't if f2fs works)
Click to expand...
Click to collapse
will report in 10 mins
1. flashing it without any custom kernel (probably wont work)
2.flashing rom zip + ak CAF kernel. (hoping for it)
..
Results
1. TWRP says no OS installed ( System is 22mb)
2.Flashing failed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
Status : ALPHA 5
This version is mainly for testers but anybody can flash it, since there is no more critical issues :victory:
This build is userdebug flavor. ADB and ROOT are disabled by default.
Installation instructions
First of all, update your Mate to EMUI 4.1 (that has the good kernel version)
Like always: BACKUP, BACKUP BACKUP !
Wipe every partitions (except your SD and your internal storage) See below.
You can flash GApps (see the frequently asked questions below).
Enjoy.
- NXT-AL10, NXT-L29 and NXT-L09 reported as booting
- Xposed reported as working
- Second SIM reported as working (NXT-L29)
Important note : L-09 variant is UNSTABLE for now.
Working
- Since Alpha 1
Partial and temporary GApps implementation
Launchers (Pixel/Google Now)
Themes (include animated)
- Since Alpha 2
RIL
Audio
Microphone
WiFi
Bluetooth
Security (Pin/Password/Pattern..)
GPS over data
Google Apps (include widgets and theme )
HiSuite full compatibility
- Since Alpha 3
SD Card
Tethering (WIFI + BT)
Offline charge
USB Access (MTP/PTP + MIDI input)
OTA Updates (by the built-in CM Updater)
Enhanced boot time (+/- 1min)
- Since Alpha 4
LCD Backlight adjustments
Notification Led
Enhanced boot caching
USB Tethering
Fix sensors
Fix ambiant display
Fix Sleep Of Death (thanks to XePeleato)
Fix FLP (location)
Fix GPS
- Since Alpha 5
RIL Signal
Bluetooth (now considered as stable)
Camera (Both, picture only)
Lineage skin/rebrand
Not Working
Camera (video mode)
Native cast
Fingerprint
Fast Charge
NFC
FM Radio
Known issues:
GPS module(fully working, available in the next release)
Another (ghost) SD Card is recognized and is incompatible with CM -> just ignore it for now. This entry will disappear with the next (OTA) update.
RIL working irregularly on AL-10 (unconfirmed) and L-09 devices
Offline charge not working (fixed, available in the next release)
You prefer to wait for a fully working ROM
You can follow the porting status here : https://github.com/PaulFasola/android_device_huawei_next/projects/1
Downloads
Current release, Alpha 5
Click here
Do a full wipe before installing this update or you could try the (risky) migration tool
Previous release, Alpha 4
Click here
Archives
Click here
Source Code
https://github.com/PaulFasola/android_device_huawei_next
You'll find the kernel and the vendor repos as well (check the readme)
Donators
android09
danywalkert
Azti Iluna
basimzanaty
drairoh
My dear tester Kingzak34
Many thanks to you guys !
Credits
* Nexolight for the useful advises
* Meticulus for the glitchy screen issue!
* Surdu_perdu's work for some ramdisk issues!
* _Ekko (freenode) for his help on the rild issues (symbols, symbols symbols...) and rild proper init
XDA:DevDB Information
[ROM][6.0.1][UNOFFICIAL] Lineage OS 13 Port, ROM for the Huawei Mate 8
Contributors
_skypol0
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: No Longer Updated
Created 2016-12-05
Last Updated 2017-09-15
Reserved
Changelogs
Alpha 3.1 - OTA only
LCD Backlight (manual update, temporary disable adaptive brightness and sensors are still off-line)
Leds (charge/notification etc..)
Drastically reduce battery consumption
Better boot caching for apps optimization
Bases for enabling the sensors soon
Fix in-game latency for complex animations (like 3D transitions)
Alpha 5.1 - (Full)OTA / download
Link: click here
Fully fix the GPS (satellites acquisition, bad wakelocks...)
Fix offline charge (animation) and adjust the settings for a faster charge (rapid charge still In the to-do list).
Have the latest LineageOS 13 core changes
Downloading now, I will test soon. Thanks for your work
UPDATE: I had to remove assert line in your updater-script, as my ro.build.product was Mate8 not next. After install i am currently stuck on the boot loader "Your device is booting now"
UPDATE 2: It worked!! Seemed like an issue on my end, i had to update to emui 4.1 before I was able to get the ROM to boot. Everything seems great so far. The only issue I faced was with the screen artifacting, and of course the issues you already listed. Great work :good:
FREQUENTLY ASKED QUESTIONS
I come from EMUI 4.1, can I flash this ROM ?
Yes, but you will need to full wipe and follow the instructions in OP
I'm on EMUI 5.X or 4.0, can I flash this ROM ?
You should roll back to EMUI 4.1 then follow OP instructions
My phone is asking for a password on boot
The master key of the old EMUI is not known and that's why we had to wipe userdata (this remove encryption).
So, that means that your Data partition is not wiped, and you have to wipe it !
Flash the Cyanogenmod recovery (built with this ROM, located in the same folder) and do a full factory reset, this work everytime.
Once done, reboot and flash this custom TWRP that handle non-encrypted userdata. You will be able to open the SD Card, flash whatever you want and restore your backup.
NB : If you flash back the stock ROM, this last will re-encrypt /data and everything will work as always.
I've waited for 10 minutes and the Cyanogen boot animation is still here
Something is wrong and prevent CM to complete the boot sequence. This is an issue to report (see below).
This ROM does not contain GApps, what should I take ?
You can find GApps package on OpenGapps
You'll need to take for ARM64 and Android 6.0 and then choose the package you want.
Tested so far : Full, Stock, Nano
I've found an issue
First of all, thanks for helping @_skypol0 !
> Open a ticket here <
Check if there is not a similar issue before posting
Fill the issue (Your device infos (kernel version, last EMUI update version etc.) , What is the problem ?, how can we reproduce it ? etc. Please put as many information as possible)
Share a paste/haste/ghost/...bin of your logcat and dmesg
Wont use it but thanks for developing it (i dont like roms based on clean android). Might be a huge step in futrue development on Mate family.
Awesome!!
Man, you've convinced me not to sell my mate 8 anymore, It's great potential. I'm looking forward for the beta version of this!
Was going to sell my mate 8 also. But now will test once basic functions are ok.
khanem said:
Was going to sell my mate 8 also. But now will test once basic functions are ok.
Click to expand...
Click to collapse
RIL an audio should be fixed with the next release later this week
I'm excited for Alpha 2
UnchartedRd said:
Downloading now, I will test soon. Thanks for your work
UPDATE: I had to remove assert line in your updater-script, as my ro.build.product was Mate8 not next. After install i am currently stuck on the boot loader "Your device is booting now"
UPDATE 2: It worked!! Seemed like an issue on my end, i had to update to emui 4.1 before I was able to get the ROM to boot. Everything seems great so far. The only issue I faced was with the screen artifacting, and of course the issues you already listed. Great work :good:
Click to expand...
Click to collapse
Oh, yeah, thanks for pointing it out ! I have built CM-13 with the 4.1's kernel and so this last can't work with lower versions I edit the thread.
(for any other problem, open an issue on Github, I can miss infos here!)
_skypol0 said:
Oh, yeah, thanks for pointing it out ! I have built CM-13 with the 4.1's kernel and so this last can't work with lower versions I edit the thread.
(for any other problem, open an issue on Github, I can miss infos here!)
Click to expand...
Click to collapse
No problem, I'll post on github if I find anything else
You mean B320?
Thanks for your effort friend, I'll definitely be glad to test it once it gets a bit more stable.
Oh my god... it's really happening...
Once SD support works, I'll glady test this on my NXT-L09.
THANKS DUDE! SWEET! Hope stable rom will get here soon! but wouldt be better starting with cm14? just saying!!
albertwesquer said:
THANKS DUDE! SWEET! Hope stable rom will get here soon! but wouldt be better starting with cm14? just saying!!
Click to expand...
Click to collapse
Huawei hasn't released a stable build of nougat yet, its only been beta builds. Once Huawei releases nougat for M8, he can work on it.
And on the other side Cm14 is far from stable
Tapatalké depuis mon MEGA Mate 8 !
well i didnt know we had to have nougat in our mate 8 in order to have cm14, in that case cm13 should be ready since 6.0 have quite some time in our device! SO THERE'S HOPE!
Amazing I cant beileve im really seeing it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community.
It can be used without any need to have any Google application installed.
You will need to provide your own Google Applications package (gapps).
LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for unofficial LineageOS 13.0 builds for LG G4 model H815 only.
Its a continuation of the official one as it was abandoned back in July and I still prefer MM (N has still bugs and does not support encryption).
Known issues:
the kernel has security bugs which need to be addressed
its in testing state as I cant test it atm.. please report back! PLEASE MAKE A FULL BACKUP BEFORE TESTING!!
Installation:
First time flashing LineageOS 13.0 on your device, or coming from another ROM?
Download the zip(s)
Install latest TWRP from the official twrp.me website
Perform a nandroid backup of your current ROM (optional but recommended)
Wipe data/factory reset
Flash LineageOS
Optional: Install the Google Apps addon package, install the SU addon package(https://download.lineageos.org/extras, choose arm64)
Reboot
Download:
Google Apps:
OpenGApps (choose arm64, 6.0, nano)
TWRP Recovery:
https://twrp.me/devices/lgg4.html
Full Stock ROMs:
H815 V20D
Bootloader:
Remember ---> Flashing bootloader is risky so you flash at your own risk!
H815 V20D
Modem:
H815 V20D
ROM:
Last known fully working is 20170813! Sorry have to fix the blobs first!
Nightlies: http://droid.binbash.it
Sources:
Android: https://github.com/LineageOS
Device: https://github.com/steadfasterX/los_android_device_lge_h815
Kernel: https://github.com/LineageOS/android_kernel_lge_msm8992
G4 common device tree: https://github.com/LineageOS/android_device_lge_g4-common
Proprietary files: https://github.com/TheMuppets/proprietary_vendor_lge
.
XDA:DevDB Information
lineage-13.0-unofficial, ROM for the LG G4
Contributors
steadfasterX, codeworkx, genesixxbf3
Source Code: https://github.com/steadfasterX/los_android_device_lge_h815
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Bootloader unlocked, v20A (or greater) bootloader stack
Based On: LineageOS
Version Information
Status: Beta
Beta Release Date: 2017-08-21
Created 2017-08-21
Last Updated 2017-11-03
FAQ
1. Q: Encryption is not possible?
A: if the GUI for encrypting the device is not working:
Its highly recommended to backup all your data including the internal storage (I recommend FlashFire or / and Titanium)
Flash my screenlock fix (search here at XDA) in TWRP.
Reboot to android.
ensure that you met all usual requirements (battery, screen lock set) and then open a terminal or adb shell. Type:
vdc cryptfs enablecrypto inplace pin 1234
Replace 1234 with your desired pin ofc.
sfX
Reserved
Hi steadfasterX !
Thanks for keeping this alive ! I'm still on an old 13.0 version, it runs fine ATM.
steadfasterX said:
the kernel has security bugs which need to be addressed
Click to expand...
Click to collapse
Could you please be more precise on this ?
Where those bugs also in genesixx build, or are they specific to your build ?
Are these bugs LOS specific, or are they AOSP related ?
Thanks !
thewild said:
Hi steadfasterX !
Thanks for keeping this alive ! I'm still on an old 13.0 version, it runs fine ATM.
Could you please be more precise on this ?
Where those bugs also in genesixx build, or are they specific to your build ?
Are these bugs LOS specific, or are they AOSP related ?
Thanks !
Click to expand...
Click to collapse
its the same source then the official build (and so genessix) used so it should work the same way but as my device is broken atm and I await repair I cannot test it..
Last time I checked the security patches in my build got increased to July 2017 where the latest official ones had June..
so afaik there should be no critical issues in Android but the kernel is last time updated in May 2016 (should be the same for genessix builds).
My plan is maybe to integrate the Llama kernel and backport fixes from the 14.x tree.
don't expect that this happen in the near future (we can hope though) because atm I'm quite busy with my unofficial unlock stuff.
.
OK I'll keep an eye on this thread then.
Good luck !
Any tester reports?
Netsab said:
Any tester reports?
Click to expand...
Click to collapse
Yes.. I use that ROM with my unofficial unlock testers. Atm I cannot test cell service but it boots up fine, WiFi, cam etc works fine.
sfX
Sent from my LG-H815 using XDA Labs
Hi,
I can't make encryption work.
Can you write a procedure to use it with this ROM, please?
What I did:
- Install TWRP latest version
- Install latest nightly
- Remove gate keeper (using this)
- Launch encryption
What happened:
- Device reboot, display a green android on a black screen for a second, then reboot again try to boot on LineageOS but it froze after maybe a minute.
- I put off the battery and reboot the phone, that boot normally (data not encrypted but not corrupted either).
Thanks by advance
zeduck said:
Hi,
I can't make encryption work.
Can you write a procedure to use it with this ROM, please?
What I did:
- Install TWRP latest version
- Install latest nightly
- Remove gate keeper (using this)
- Launch encryption
What happened:
- Device reboot, display a green android on a black screen for a second, then reboot again try to boot on LineageOS but it froze after maybe a minute.
- I put off the battery and reboot the phone, that boot normally (data not encrypted but not corrupted either).
Thanks by advance
Click to expand...
Click to collapse
thx for testing..
yea I rem that there was a "trick" .. Could you try this build pls: http://droid.binbash.it:58885/h815/lineage-13.0-20170912-UNOFFICIAL-h815.zip
It includes an insecure kernel which will allow to debug.
Factory Reset in TWRP
Flash in TWRP
Boot Android
Enable encryption
when it reboots open a terminal and type (linux or FWUL): while true; do adb logcat ;done
on windows ensure that once the logcat aborts that you restart it immediately again!! and use just adb logcat
if using windows or linux: ensure the terminal buffer is big enough bc thats a a lot to handle.. (go into the settings of the cmd or terminal and set it to a very high value. e.g. 5000000)
let it bootloop and boot into Android again (logcat should run all the time)
CTRL+C when its completed with the above
copy & paste the whole stuff in a text file and attach it here
sfX
Are there any special modifications that would make it work?
Because I use this ROM as a daily driver and I would appreciate not to backup and reflash several times
If not, I will take the time to test this weekend.
zeduck said:
Are there any special modifications that would make it work?
Because I use this ROM as a daily driver and I would appreciate not to backup and reflash several times
If not, I will take the time to test this weekend.
Click to expand...
Click to collapse
without logs I cannot say anything for sure...
It may can be solved by just typing the encrypt command over adb or it requires to modify the ROM..
If you like you can try the following but keep in mind that having a complete Backup is a good idea always and when I say complete I mean including internal storage which is not be backuped by TWRP!! Use e.g FlashFire app to accomplish this. I would take a TWRP backup for all (use my latest beta!!!) and then FlashFire to backup internal storage.
Encryption often fails to a wrong formatted data partition so this can be a reason as well.
Try this:
Backup as described above
In TWRP select wipe - advanced - press "Format data" button to format the data partition
Boot android
set a pin or password for the lock screen!
Encrypt
If succeeded restore backup with FlashFire
As always there is a risk and it requires some time so I would not recommend to do this on a busy day.. as you say at the weekend fe.
Then we can try to use the adb commands and if that doesn't work as well the logcat..
sfX
Sent from my LG-H815 using XDA Labs
Hi !
I gave a try with lineage-13.0-20170918-UNOFFICIAL-h815.zip that I dirty-flashed over my previous lineage-13.0-20170204-UNOFFICIAL-h815 version.
Everything went fine (I had to replace the su zip/app though), except that satellite location would not work (network location was fine) : I kept getting
Code:
QCOM PowerHAL : Failed to acquire lock.
in logcat.
I'll give another try with the latest lineage-13.0-20170927-UNOFFICIAL-h815.zip.
If that fails too, I guess I'll have to clean-flash it then.
EDIT :
Bad news : after a clean flash, I keep getting
Code:
QCOM PowerHAL : Failed to acquire lock.
in logcat.
No GPS?! Kind of annoying bug... I'm still in 20170608 build and that news don't make me want to updated. I use GPS everyday, so this is very annoying
Netsab said:
No GPS?! Kind of annoying bug... I'm still in 20170608 build and that news don't make me want to updated. I use GPS everyday, so this is very annoying
Click to expand...
Click to collapse
After flashing several successive versions of that ROM, I discovered that version lineage-13.0-20170813-UNOFFICIAL-h815.zip seems to be the last one with satellite location working fine.
Starting from lineage-13.0-20170814-UNOFFICIAL-h815.zip, satellite location stops working. I guess something is broken in that build.
@steadfasterX :
Can you look and see what's happened with 20170814 ? Thanks !
@Netsab :
You can safely upgrade to 20170813.
breversa said:
After flashing several successive versions of that ROM, I discovered that version lineage-13.0-20170813-UNOFFICIAL-h815.zip seems to be the last one with satellite location working fine.
Starting from lineage-13.0-20170814-UNOFFICIAL-h815.zip, satellite location stops working. I guess something is broken in that build.
@steadfasterX :
Can you look and see what's happened with 20170814 ? Thanks !
@Netsab :
You can safely upgrade to 20170813.
Click to expand...
Click to collapse
Thanks you, I'll try.
breversa said:
After flashing several successive versions of that ROM, I discovered that version lineage-13.0-20170813-UNOFFICIAL-h815.zip seems to be the last one with satellite location working fine.
Starting from lineage-13.0-20170814-UNOFFICIAL-h815.zip, satellite location stops working. I guess something is broken in that build.
@steadfasterX :
Can you look and see what's happened with 20170814 ? Thanks !
@Netsab :
You can safely upgrade to 20170813.
Click to expand...
Click to collapse
thanks for your report. btw a dmesg is very helpful in these cases but the above should be fixed on next build.
next build will also have all proprietary stuff upgraded to v20p.
sfX
EDIT
new build is up
.
Hey sfX,
When trying to dirty-flash 20170930 over 20170813, the phone gets stuck on the boot animation (for over 30 minutes).
I did not try to clean-flash it though ; I thought I'd let you know first.
Sir SteadfasterX!
I use Unofficial 13.0-20170625-UNOFFICIAL-h815 as a daily driver and it never crashed once. I will try yours in near future, beginning with a dirty flash (but with a backup in case).
My question is, do the Bluetooth APT-X include in this rom?
One of my other phones Sony Z5 (modded stock) includes from factory an APT-X notifier, whenever it connects to a Bluetooth with APT-X I get a toast message that the device using "BLUETOOTH apt-x".
I see in Nougat 7 that it is possible to check in "developer mode" which Bluetooth protocol that currently is in use.
[Request] It would be nice if you could pick Bluetooth APT-X drivers/codec from above version of LinageOS14
Thank you very much!
I have attached the spoken AptxNotifier.APK from Sony z5 Marshmallow
datorprofessor said:
Sir SteadfasterX!
I use Unofficial 13.0-20170625-UNOFFICAIL-h815 as a daily driver and it never crashed once. I will try yours in near future, beginning with a dirty flash (but with a backup in case).
My question is, do the Bluetooth APT-X include in this rom?
One of my other phones Sony Z5 (modded stock) includes from factory an APT-X notifier, whenever it connects to a Bluetooth with APT-X I get a toast message that the device using "BLUETOOTH apt-x".
I see in Nougat 7 that it is possible to check in "developer mode" which Bluetooth protocol that currently is in use.
[Request] It would be nice if you could pick Bluetooth APT-X drivers/codec from above version of LinageOS14
Thank you very much!
I have attached the spoken AptxNotifier.APK from Sony z5 Marshmallow
Click to expand...
Click to collapse
Better wait until I fixed the current nightlies..
nice app btw. when all is fixed i may take a look into it
Sent from my LG-H815 using XDA Labs
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Brought to you by @nailyk!
Notice: Thread missing information/ credits/ mentions/ stuff etc etc. Work in progress.
All credit for this ROM must go to Nailyk as the main developer of Omni for Leo devices. I am just a tester / thread maintainer for Leo (Z3).
Disclaimer:
Code:
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
Who can use it?:
This ROM is only for Xperia Z3 users with UNLOCKED and (preferably) UPGRADED bootloaders!
How to install:
%= Only needed at first flash
% Update ROM to .291 with emma (or Flashtools)
% When install is done go into fastboot mode (plug usb + vol down key = blue led)
% Flash this TWRP (version 3.1.x)
Shutdown the device
Unplug the usb cable
Maintain volume down & power until you see twrp splash screen / wait for purple LED on boot and press volume up key
% Wipe system, cache and data
Install rom zip (+ % gapps if you need it)
Reboot
(After first boot if you have initial issues try a second reboot and see if it stops. If not, clean install)
Rolling back to stock:
- Flash stock rom with emma or flashtool
If you flash with flashtool remember to check wipe apps_log and userdata partitions to get a clean install
TWRP:
See Nailyk's TWRP build here for best compatibility (based on Omni sources):
TWRP 3.1.x-x
GAPPS:
Flash any 7.1.2 compatible Gapps package. I suggest OpenGapps.
Alternatively Microg and fdroid will serve you well as an alternative to Google Play Services.
Releases:
Latest:
2017-12-13: Android File Host Download
Mirror: releases.nailyk.fr/omnirom
Change Log: CVE Patches
TWRP 2017-11-21: Android File Host Download
Previous:
2017-12-02: Android File Host Download
Change Log: Fixed scripts for modem files at first boot. No issues with SIM detection, manual script running etc now.
2017-11-21: Android File Host Download
Change Log: Updated Security Patches to latest. No change to ROM.
2017-10-17: Android File Host Download
Change Log:
Code:
Lot of important changes here,
- Device was renamed z3 instead of leo,
- This release ""should"" support all leo variants. However, the script is on early stages: expect troubles.
In case of problem with RIL process the following:
Reboot into recovery,
connect to shell then:
Code:
mount /system
ln -s /system/vendor/etc /vendor/etc
sh /system/etc/init.blobs.sh
This build is patched against wpasupplicant attack (krackattack)
Some improvements about external sdcard & charging.
2017-09-28: Android File Host Download
MD5 Sum: b431c2c720be4a4dfd365a8343ca8115462a3393
Root etc:
For root it is suggested that you see phhSuperUser here: phhSuperUser Thread
Flash options such as Magisk or SuperSU if you wish, but there is not guarantee of support. Magisk 14.0 was tested by myself and working at first release.
Contributors:
@nailyk,
@xkeita, @tomascus, @derf elot, @TheavenginTitan
@tomgus1, @gr8st, @mcgi5sr2, @doriandiaconu, @Robot76, @panzerox123
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: OmniROM
Version Information:
Status: Beta
Logs:
This post will describe how to take logs.
If you are using the ROM and want to make development faster/ easier please simply take a log and post it here in the thread for us to check out.
Take logs when you notice bugs etc and try to reproduce them when taking the log and give us some description of the problem.
First you will need ADB:
Set up any adb environment on you PC (showing windows here for eg.- Linux/ Mac differs):
- For windows a minimal installation will be enough to take logs and takes 15 seconds.
15 second ADB Installer
Then open the folder it is installed to so you see "adb.exe" (obviously different on Linux/Mac).
Open and CMD window in the folder with adb and you can connect your phone.
Enable USB Debugging on the phone!:
Go to Settings - About Phone - Build Number (tap this until Developer options unlocks)
Go to Developer Options and enable "USB Debugging".
Now take the actual logs running adb logcat:
- Back to the PC CMD window.
- When you run the command a window will pop up on the phone asking for access. Say yes.
- Run the command - " adb logcat > logcat.txt "
- This will give you a text file with the log to post to us.
If possible take a dmseg /kmsg:
This is most useful for bootloops etc
You may need root on the device to access these:
- " adb shell su -c dmesg > dmesg.log "
- " adb shell su -c "cat /proc/last_kmsg" > last_kmsg.log "
Screenshots
Screenshots thanks to @Tux111. Find some of his comments and hit thanks for him!
Full showcase of screenshots here: MEGA
What working?
@Dobsgw When you will update missing informations, could you please share informations about changelogs, what works, whats not, special features and some screenshots?
All the users (me too) will appreciate a lot.
I'm gonna get the info on the changes and features etc at some point later this week.
For now all I know is the build is beta but working very well. You all know Nailyk has a very high standard of work.
The current version I have installed is working as normal and since this morning (when I installed) I've seen no issues.
If you have some time it's worth checking out.
For features etc see the Omni ROM website
Dobsgw said:
I'm gonna get the info on the changes and features etc at some point later this week.
For now all I know is the build is beta but working very well. You all know Nailyk has a very high standard of work.
The current version I have installed is working as normal and since this morning (when I installed) I've seen no issues.
If you have some time it's worth checking out.
For features etc see the Omni ROM website
Click to expand...
Click to collapse
Mobile Data don't work. Every time i try to set APN, it automatically disappear. No way to make SIM data work.
The rest of the ROM is kinda awesome, some little bugs but really nicely done. Ah, message app miss. Add it please.
You probably know already but there is no link to TWRP 3.1.x for Z3 and Z3 dual (can be found in xkeita thread of Lineage 14)
Tux111 said:
Mobile Data don't work. Every time i try to set APN, it automatically disappear. No way to make SIM data work.
The rest of the ROM is kinda awesome, some little bugs but really nicely done. Ah, message app miss. Add it please.
Click to expand...
Click to collapse
Please provide full rom log, dmesg & radio log.
What variant? This rom is not dual ready yet.
tiliarou said:
You probably know already but there is no link to TWRP 3.1.x for Z3 and Z3 dual (can be found in xkeita thread of Lineage 14)
Click to expand...
Click to collapse
Xkeita TWRP is fine.
Nailyk also has a brilliant TWRP version found here in the forum.
It is updated to latest just ignore the title. 3.1.1-3
nailyk said:
Please provide full rom log, dmesg & radio log.
What variant? This rom is not dual ready yet.
Click to expand...
Click to collapse
D6603 single SIM.
Can't provide right now, sorry.
EDIT: I'll provide it soon as possible!
How i have to make radio log?
nailyk said:
Please provide full rom log, dmesg & radio log.
What variant? This rom is not dual ready yet.
Click to expand...
Click to collapse
I figured out mobile data work. But there is a bug, inside APN configuration, that automatically delete the APN created if you modify a string inside and after save it.
This time i simply used default APN settings, without modifying anything a part APN "Name" and "APN" and it works.
Here there is the logcat of the bug (over 1 mb can't upload here).
https://mega.nz/#!YAUXUSaA!3w6IWURIGvsHU-Cm9IkFStOsmyj67Sxvt9tbqqD2mG8
Tux111 said:
I figured out mobile data work. But there is a bug, inside APN configuration, that automatically delete the APN created if you modify a string inside and after save it.
This time i simply used default APN settings, without modifying anything a part APN "Name" and "APN" and it works.
Here there is the logcat of the bug (over 1 mb can't uploader here).
https://mega.nz/#!YAUXUSaA!3w6IWURIGvsHU-Cm9IkFStOsmyj67Sxvt9tbqqD2mG8
Click to expand...
Click to collapse
Thank you for taking the time to look into this.
Hopefully not a big issue
Mobile data D6603 german working LTE
Sent from my unknown using XDA-Developers Legacy app
edit
New twrp works fine and omnirom build too! Thx for hard work! ? Greets from German
Sent from my unknown using XDA-Developers Legacy app
App not using SD card photo ecc
Inviato dal mio unknown utilizzando Tapatalk
my BL is unable to get unlocked. but im now on .291 rom and rooted and twrp installed. is there nothing i can do to taste the full working nougat?
what will happen if i flash it onto my device (in this case, the BL is still locked. bootloader unlock allowed : no )
thanks.
leo31 said:
my BL is unable to get unlocked. but im now on .291 rom and rooted and twrp installed. is there nothing i can do to taste the full working nougat?
what will happen if i flash it onto my device (in this case, the BL is still locked. bootloader unlock allowed : no )
thanks.
Click to expand...
Click to collapse
You will have a brick.
Nothing you can do when unlock allowed:no.
The only thing is to contact sony, it is illegal (in some countries) to have an unlockable bootloader.
The images and most of the files do not use the sd card and when you want to pass applications to the system it does not allow attachment screenshot.
You could also add the option to expand the desktop and resize the navigation bar.
ArrowOS-12 for Asus Zenfone 5z (Z01R) !Welcome to ArrowOS!ArrowOS is an AOSP based project started with the aim of keeping things simple, clean and neat. We added just the right and mostly used stuff that will be actually USEFUL at the end of the day, aiming to deliver smooth performance with better battery life.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
Code:
* Your warranty is void. Or valid, probably?
* I am not responsible for bricked devices, dead SD cards
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modificiations, and if
* you point your finger at me for messing up your device, I will LMAO at you.
Features!- Stockish and smooth UI
- Built for performance and battery
- As stable as stock roms or maybe better
- Customization section isn't added yet as A12 is in initial phase
Download
Build Details!- kernel version: 4.9.309-IceWiz (link to kernel)
- Vanilla and Gapps build (both release)
- Vendor included (encrypt)Steps to flash!- Go to TWRP
- wipe system, data and dalvik
- flash Arrow-12.zip
- flash TWRP.zip
- reboot recovery
- flash Gapps, magisk or additional zips if needed
- reboot systemBugs!- Nothing found in my testing
- Bt media has also been fixed
Buy us a cold-drink
Android Version - 12.1
Build Date - 27-07-2022
Maintained by - EdwardWu(bluehomewu)
Kernel Version - 4.9.309-IceWiz (link to kernel)
Special thanks to -ArrowOS group, Adeveloper, Marc, Aryan, Ayan, Kailas, Apon, obviously I also, and others
I followed this guide https://forum.xda-developers.com/t/guide-noob-friendly-custom-rom-flashing-guide.3944849/ and I'm stuck in bootanimation(arrowos). What do you think is the problem?
Best ROM for Asus Zenfone 5Z. Way better than Evolution X or DerpFest. No bugs at all, even McDonald's app works, please continue your struggle to port this ROM on this phone. Problems: Face recognition not working, software update section cannot be found
MrBluie_ said:
Best ROM for Asus Zenfone 5Z. Way better than Evolution X or DerpFest. No bugs at all, even McDonald's app works, please continue your struggle to port this ROM on this phone. Problems: Face recognition not working, software update section cannot be found
Click to expand...
Click to collapse
Thanks bro,remember join device group to get latest updates, will release at device group and channel.
FaceUnlock:
Untill now, Official Arrow-OS build, still not included faceunlock yet.
Software Update:
Because we're community build, not Official. Give me some time, I will apply Official.
Hi! Download links from ArrowOS website are not working (January 13th 2022 build of OS) and I see that the links from xda are not working too. Can you fix them please? I love to see those updates, ArrowOS is the best for Asus Zenfone 5Z ZS620KL. Thanks my friend!
MrBluie_ said:
Hi! Download links from ArrowOS website are not working (January 13th 2022 build of OS) and I see that the links from xda are not working too. Can you fix them please? I love to see those updates, ArrowOS is the best for Asus Zenfone 5Z ZS620KL. Thanks my friend!
Click to expand...
Click to collapse
Community experience version will cleaning on Arrow-OS server every week.
So please check new build and download link from my Telegram channel
Edward の ROMs
About Edward: https://t.me/Edward_ROMs/23
t.me
This UI is very good for daily use. just observed issue with Camera access: When camera access is turned off and if i go to Instagram camera, it asks me to enable camera access but if i cancel this access, it still opens the front camera and i am able to use front camera....(Seems like a major security breach but not sure if this is the same case with stable official a12 roms.)
Let me know if anyone has solutions to this issue. Thanks!
JuanTamqd21 said:
I followed this guide https://forum.xda-developers.com/t/guide-noob-friendly-custom-rom-flashing-guide.3944849/ and I'm stuck in bootanimation(arrowos). What do you think is the problem?
Click to expand...
Click to collapse
happened to me too, the boot screen keeps on animating. for very long. I dunno what happened. I tried formatting data but nothing.
amitrahi04 said:
happened to me too, the boot screen keeps on animating. for very long. I dunno what happened. I tried formatting data but nothing.
Click to expand...
Click to collapse
If you have followed all the steps exactly as mentioned in the link, then may be the file you downloaded is corrupted. Try downloading the file again and flash it. Or better download an older version of this ROM and flash it.
.
08-02-2022 Changelog:
• Synced with latest source changes
(https://t.me/ArrowOS)
• Kernel: Update to 4.9.299 Icewiz
• Device: Device Tree re-write based on Lineage OS, thanks @ReallySnow for help
• Device: SELinux is enofrcing now. Please remember backup and format userdata.
• Device: DATA support encrypt right now.
12-02-2022 Changelog:
• Synced with latest source changes
(https://t.me/ArrowOS)
• Kernel: Update to 4.9.301 Icewiz
• Device: Fix DRM cause Apps crash issue.
JuanTamqd21 said:
I followed this guide https://forum.xda-developers.com/t/guide-noob-friendly-custom-rom-flashing-guide.3944849/ and I'm stuck in bootanimation(arrowos). What do you think is the problem?
Click to expand...
Click to collapse
When I installed first time this - get the same behavior - bootloop and I did not pay attention so when I connect phone to computer - it's mounted with strange folder names. I've get back to stock firmware and before give one more try to custom firmware - I've reset phone to factory defaults and after phone rebot to first boot and ask to setup language and other settings - reboot to recovery, flashed twrp, rebooted and twrp ask me to enter password to decrypt encrypted data volume. No any passwords I've used is okay so I've go to format and format just data (in advanced mode format it's still says can't mount encrypted volume and of course can't format it). After format - phone was mounted on computer with normal folder names and the rest of instructions how to install firmware was go smoothly.
Can anyone confirm that screen rotation is not work at all? I've tried to turn it on - not worked. Tried to turn off then on - not work. Rebooted phone - still no screen rotation. Tried in browsers and launcher.
shashilx said:
誰能確認屏幕旋轉根本不起作用？我試圖打開它 - 沒用。試圖關閉然後打開 - 不起作用。重新啟動手機 - 仍然沒有屏幕旋轉。在瀏覽器和啟動器中嘗試過。
Click to expand...
Click to collapse
I'm on Arrow-v12.0-Z01R-COMMUNITY-20220212-GAPPS build and screen rotation not work ((( what can i do to diagnose problem?
23-02-2022 Changelog:
• Synced with latest source changes
(https://t.me/ArrowOS)
• Kernel: Update to 4.9.302 Icewiz
shashilx said:
Can anyone confirm that screen rotation is not work at all? I've tried to turn it on - not worked. Tried to turn off then on - not work. Rebooted phone - still no screen rotation. Tried in browsers and launcher.
Click to expand...
Click to collapse
No problem for me on the latest version, rotation works well.
Thanks for the great ROM ! I am using it for few days and works great. I noticed only one little issue - in the Google app settings, assistant section, the option for "OK google" command is greyed out. In stock version it seems to be OK, but after update from play store this issue occured. The only glue I found here on XDA is that the app should be in the /system/priv-app folder. Default ROM version of app is in the /system_ext/priv-app and then update from play store is in /data folder. Maybe this could help. Thanks once again for the very good ROM.
Thank you so much for the rom. Everything works fine except LTE which doesn't work. I only have connection via WIFI. Hope you can solve the problem.