Related
CyanogenMod is a free, community built distribution of Lollipop which greatly extends the capabilities of your phone.
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 is a highly experimental and unofficial build of CM12 on Xperia TX.
Note that this may be unstable, not booting, missing in features or anything else. Flash at your own risk!
NOTE(20150522):
I got a new phone weeks ago, so TX won't be my daily driver anymore. And this ROM will be discontinued due to limited time and energy. Thanks for your support.
Known bugs:
See post #2
"About phone" screen:
{
"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"
}
Installing instructions:
Flash the ZIP package as usual, then flash the kernel file via fastboot.
A full wipe is recommended before the installation, even if you are coming from last version of CM12.
OLD WAY FOR .IMG FILES:
1. Unzip the system and kernel image
2. Boot the phone into fastboot mode
3. fastboot -i 0xfce flash system system.img
4. fastboot -i 0fxce flash boot boot_f.elf
5. fastboot -i 0xfce reboot
6. Get into recovery at once and wipe data & cache
7. Reboot. The first boot may take very long time.
DESCRIPTION ABOUT INTERNAL STORAGE PERMISSION
ATTENTION:
CM has changed owner of internal storage to 1023:1023 (media_rw:media_rw). This is the default value in AOSP, but different from the one in Sony stock ROMs. I'm considering changing to 1023:1023 in my unofficial builds as well, but I want to hear your opinion first.
Advantage of 1023:1023 is: it's default in AOSP, using this will solve some problems in AOSP-derived ROMs (e.g. moving apps to sdcard may fail with "insufficient space" error. And maybe some more...)
Drawback of 1023:1023 is: it's incompatible with other ROMs. If you switch to other ROMs without changing owner back, you won't be able to write into internal storage, just like those who formatted int storage in 5.0 or recovery.
Advantage and disadvantage of 2800:2800(Sony stock) are the the way round... better compatibility but cause problems with AOSP.
(Changing owner only takes a few lines of code. That's easy)
So which one do you prefer? 1023:1023 or 2800:2800? Please leave your opinion in the reply. Thanks~
20150312- have 2800:2800. 20150319+ have 1023:1023.
Click to expand...
Click to collapse
Download:
NOTE: sdcard owner has been changed to 1023:1023 since 20150319.
If you want to switch to other ROMs, remember to do this before you flash in order to get a writable internal storage.
Code:
su
busybox chown -R 2800:2800 /mnt/media_rw/sdcard0
20150521
https://drive.google.com/file/d/0BwkmhbR5VHpAQmNhWE9IcUJYRXM/view?usp=sharing
OLD VERSION:
20150514
https://drive.google.com/file/d/0BwkmhbR5VHpAOUp0VzJva3BabjA/view?usp=sharing
20150508
https://drive.google.com/file/d/0BwkmhbR5VHpAS3JqdW9YWUkyVms/view?usp=sharing
20150501
https://drive.google.com/file/d/0BwkmhbR5VHpARUFLdTlXM090Zk0/view?usp=sharing
20150424
https://drive.google.com/file/d/0BwkmhbR5VHpAeEhJeC1WcFVYYVk/view?usp=sharing
20150418
https://drive.google.com/file/d/0BwkmhbR5VHpASjIxbVBYQ2R3am8/view?usp=sharing
20150410
https://drive.google.com/file/d/0BwkmhbR5VHpARzBIaFIwbE5Qak0/view?usp=sharing
20150404
https://drive.google.com/file/d/0BwkmhbR5VHpAYmdPLUd2UGNBbTg/view?usp=sharing
20150402
https://drive.google.com/file/d/0BwkmhbR5VHpAVkxWRmx0bWh4X2s/view?usp=sharing
20150325
https://drive.google.com/file/d/0BwkmhbR5VHpAcjdRNU11NUpEanM/view?usp=sharing
NOTE: Screen will go out if brightness is set to minimum. Fix is in the attachment (lights.msm8960.so.zip) Extract this to /system/lib/hw and it will be OK.
20150319
https://drive.google.com/file/d/0BwkmhbR5VHpAWWtCQ1FEOHVaMms/view?usp=sharing
20150312
https://drive.google.com/file/d/0BwkmhbR5VHpAWnM2RnNzVXFwbUk/view?usp=sharing
Rec and permission fix: https://drive.google.com/file/d/0BwkmhbR5VHpAV0ZPUW9RZjF1RXM/view?usp=sharing
Step 1. FIash the ROM zip
Step 2. Flash kernel in fix
Step 3. Put system folder in fix.7z to the phone
(IF YOU HAVE FLASHED BEFORE APPLYING FIX) Step 4. Execute these commands in adb shell/Terminal Emulator
Code:
su
chown 2800:2800 /mnt/media_rw/sdcard0
If you find these instructions hard to understand, you may try this flashable zip by Antiga Prime. Thanks!
20150302
https://drive.google.com/file/d/0BwkmhbR5VHpAa0ZtSXQ5UUxuQ2M/view?usp=sharing
20150128
https://drive.google.com/file/d/0BwkmhbR5VHpARW0xQkswWE5aOWs/view?usp=sharing
20150123
https://drive.google.com/file/d/0BwkmhbR5VHpAM0c2SHd5TzVlems/view?usp=sharing
20150110
https://drive.google.com/file/d/0BwkmhbR5VHpAWkUyTHhqS1M1Nnc/view?usp=sharing
20150103
https://drive.google.com/file/d/0BwkmhbR5VHpANi1UVG1YbVJoQlk/view?usp=sharing
Kernel with TWRP bug fixed: https://drive.google.com/file/d/0BwkmhbR5VHpATjBvblRBU05VbXM/view?usp=sharing
20141226
https://drive.google.com/file/d/0BwkmhbR5VHpANFhTdzQyQTJEUmc/view?usp=sharing
No more separate kernel
20141219
System: https://drive.google.com/file/d/0BwkmhbR5VHpAX25JbXFVRWJxMjQ/view?usp=sharing
Kernel: https://drive.google.com/file/d/0BwkmhbR5VHpAWE5jQUc5aFR2Q28/view?usp=sharing
Cyanogen Recovery is able to install from internal storage now, but it requires signature verification. The kernel file contains Cyanogen recovery without that verification process. Next time this will be merged into system zip file and there will be no more standalone kernel image.
20141212
Kernel: https://drive.google.com/file/d/0BwkmhbR5VHpAYktOYTA1RnJtam8/view?usp=sharing
System: https://drive.google.com/file/d/0BwkmhbR5VHpAZXRockhtY1V0STA/view?usp=sharing
20141207
System: https://drive.google.com/file/d/0BwkmhbR5VHpAcFVYUWpwenhrVnc/view?usp=sharing
Kernel: https://drive.google.com/file/d/0BwkmhbR5VHpAbUF0LVAybm9ZVGs/view?usp=sharing
20141205
System (Google Drive): https://drive.google.com/file/d/0BwkmhbR5VHpAX2VaNUdPUUtTVU0/view?usp=sharing
My removable disk is not with me at this moment, so I couldn't make a TWRP included kernel. Kernels from previous versions should be compatible though.
Kernel (Google Drive): https://drive.google.com/file/d/0BwkmhbR5VHpAUVp2azBRX1VRR28/view?usp=sharing
20141203
Kernel (Google Drive): https://drive.google.com/file/d/0BwkmhbR5VHpAUXA1OXFnakZOZ0U/view?usp=sharing
System (Google Drive): https://drive.google.com/file/d/0BwkmhbR5VHpAbXhXVDRpOFFQQ2s/view?usp=sharing
20141130
System: http://pan.baidu.com/s/1o6LWX5K
Google Drive: https://drive.google.com/file/d/0BwkmhbR5VHpAQjdUcG1RbGxmQms/view?usp=sharing
Kernel: http://pan.baidu.com/s/1gdovtnl
Google Drive: https://drive.google.com/file/d/0BwkmhbR5VHpAcW1GbmF6cVRNSEU/view?usp=sharing
NOTE: Build time and CyanogenMod version in About Phone are not changed. They will when I get enough time to make a clean build.
20141128
System: http://pan.baidu.com/s/1qWCzw4W
Google Drive: https://drive.google.com/file/d/0BwkmhbR5VHpAdUtabGdVblJ3Njg/view?usp=sharing
Kernel: http://pan.baidu.com/s/1qWwQuhm
Google Drive: https://drive.google.com/file/d/0BwkmhbR5VHpAbFo5UDM1VzJSRjA/view?usp=sharing
No standalone kernel from now on. CM's custom recovery has been included (and it's tap-able )Seems not finished yet.
And Superuser has been integrated as well. No need for other apps.
20141127
System ZIP: http://pan.baidu.com/s/1jG3inaQ
Kernel: http://pan.baidu.com/s/1mgBlDgs
Google Drive mirror(kernel): https://drive.google.com/file/d/0BwkmhbR5VHpAYVdMNXVEZDNXZEk/view?usp=sharing
Google Drive mirror(system): https://drive.google.com/file/d/0BwkmhbR5VHpAeGJlakhLc3lYNGM/view?usp=sharing
(Included a unit test app for messaging by mistake, just delete it)
20141125:
System ZIP: http://pan.baidu.com/s/1mgkho5E
Kernel: http://pan.baidu.com/s/1bnm1xV5
20141121:
System ZIP (Recovery flashable): http://pan.baidu.com/s/1i37nOTf
Kernel (Flash after the system - reboot to bootloader in Recovery after flashing the zip above): http://pan.baidu.com/s/1pJHQYld
Initial ver
System image: http://pan.baidu.com/s/1B5Ofk
Kernel: http://pan.baidu.com/s/1nt0ua9N
Device specific sources are on my GitHub (updateing), and kernel is built on kernel-msm repo listed there.
Changelog (FROM UPSTREAM)
20150521
FM Transmitter enabled (it's so lucky that (it seems) only our device fully supports it)
20150514
->post #2
20150508
mainly upstream changes
20150501
->post #2
20150424
Android 5.1.1
-> post #2
new WiFi driver
20150418
workaround about flickers in some apps -> post #2
20150410
-> post #2
20150404
goodbye Microsoft
try to fix abnormal record of battery comsumption of mobile network
20150402
first Android 5.1 build
20150325
Xperia logo functions normally when a notification is cleared when screen is off
20150319
changed internal storage permission to 1023:1023
upstream changes
-> post #2
20150312
upstream changes. (one noticable feature: LiveDisplay)
20150302
upstrem changes
added a FM radio app, but it's not working now.
20150128
-> post #2
mostly upstream features and fixes (new wallpaper, setup wizard, etc)
20150123
-> post #2
theme engine (upstream)
no more sudden change of brightness when turning screen off
SELinux enforcing (mostly upstream with minor changes for TX)
more customization
20150110
mostly upstream changes
20150103
TWRP included (built from source, not a copy of Kitkat kernel. I didn't realize CM Recovery was not meant for custom ROMs...)
-> post #2
20141226
Android 5.0.2
USB Mass Storage support (Settings-Storage-(3dot menu))
-> post #2
20141219
-> post #2
weather shown in status bar
Gallery is materialized
Battery icon selection
20141212
-> post #2
more materialization
icon fixes
20141207
some features from upstream, such as vibrator intensity control
show network mode in network search result
-> post #2
20141205
Mostly upstream fixes, e.g. appearance of Settings app, clickable time & date
Reduced some unused kernel modules
Select dlmalloc as memory allocator. It's jemalloc in previous versions, but fusion3 have dlmalloc choosen. Let's see what will happen... (seems smoother)
20141203
Android 5.0.1
fix: (post #2)
20141130
upstream fixes and new features
TEST: one case about working GPS in post #2
20141128
fix: (in post #2) and some info about GPS
new: CM's handsome recovery
new: integrated Superuser
20141127
fix: (in post #2)
20141125
fix: (in post #2)
new: Message app
new: a small number of personalization settings (quick pulldown etc)
20141121
fix: data and WiFi icon movement
fix: no audio
fix: NFC Service FC
fix: Download / Documents / Call History FC
new: full set of fonts
new: multi user support / Guest Mode
Credits:
Finally thanks CyanogenMod team who merged sources so quickly, and Sony who made all this happen, and a lot more on Gerrit who helped me solve the compliation errors.
One possible bug: no sound. Extract the attached file to /system/etc
If there's nothing wrong, you can ignore this. I can't remmeber if I inlcuded this in the system image...FIXED in 20141121
BUG #2: NFC Service FC after boot. -> Delete /system/etc/permissions/android.hardware.nfc.hce.xml via Recovery (mount /system first)FIXED in 20141121
BUG #3: GApps not working -> Try Gapps in this post
BUG #4: Download and Call History FC.FIXED in 20141121
BUG #5: WiFi hotspot doesn't turn on.FIXED in 20141125
BUG #6: Camera stops working after switching user. -> Delete /data/camera/cache_data.dat and (in terminal emulator) su && pkill mediaserver DIRTY FIX in 20141127
BUG #7: GPS satellites are found but can't get lock -> PLEASE TEST! After every step, try if it can get a lock in 2 mins. If not, do next step and reboot.
1. Add "QUIPC_ENABLED=0" at the end of /etc/gps.conf <- Some successful reports.
2. Set "INTERMEDIATE_POS" to 1, uncomment "ACCURACY_THRES", and set "ACCURACY_THRES" to 1000 (this is the target accuracy - choose as you like)
3. Comment out ACCURACY_THRES STEP 1 INCLUDED SINCE 20141203
BUG #8: Contacts -> Menu -> Import/Export -> Import from storage FC FIXED in 20141125
BUG #9: Dialer -> Call History -> Menu -> Clear Call Logs -> (Select some) -> OK FC FIXED in 20141125
BUG #10: FC when receiving SMS via native Messaging app. Hangouts works though. EMERGENCY FIX: http://pan.baidu.com/s/1gdeRIbL push to /system/priv-app/Mms FIXED in 20141127
BUG #11: Moving 2 apps to internal storage will fail on the second one. SEEMS FIXED (20150123)
BUG #12: Call diverting can't be set After many tries I found this was not a bug of this ROM. It's the network operator to blame. I inserted my SIM to an ancient Nokia and it couldn't set call diverting either. And when I inserted an SIM which had been confirmed that call diverting was working, the settings in this ROM would also work without any problem.
BUG #13: Hanging up when an outgoing call is still ringing will cause Dialer FC. -> Put http://pan.baidu.com/s/1gd28sjp into /system/priv-app/DialerFIXED in 20141128
BUG #14: Audio quality over Bluetooth is terrible. The sound is "slowed down" and pops over time. This fixes A2DP audio quality, but causes phone calls to fail when BT headset is connected. So if you use this phone and BT headset/carkit as daily driver, please replace /system/etc/audio_policy.conf with the one in previous version (or the one in attachment) INFO(FROM 20141219)Bluetooth call and music are all OK now, but there's something that has to be done in order to get music working: make a call when BT headset is connected. You can call any self-service number and hang up after connected. Otherwise the audio quality will still be terrible...
BUG #15: FC when selecting Clock -> Alarms -> (select profile) FIXED in 20141203
BUG #16: Error when finishing manual search for mobile networks FIXED in 20141203
BUG #17: After receiving MMS, default Messaging app will crash. (Hangouts is working) FIXED IN 20141207
BUG #18: Volume keys are not usable when screen is off.Works as we expect now.
BUG #19: User switching is broken (reboot and cannot switch to desired user) Can't reproduce this on 20150103
BUG #20: BT audio is broken... again.(just as well that this only happens when NuPlayer is is use. - I doubt whether we should use this on this old hardware platform) -> Turn NuPlayer off in Development Settings, then look at BUG #14
BUG #21: Music files on int/ext sdcards can't be selected as ringtone (plays a beep). Turning SELinux to permissive solves this.REPORTED FIXED in 20150514, don't know when it got fixed
BUG #22: FM Radio produces no sound.FIXED in 20150514. Note that FM will still remain on when you remove the headphones but no signal can be picked up under such circumstance.
BUG #23: USB Mass Storage is not working. Shows a drive w/o disc on PC. FIXED in 20150319
BUG #24: (Android 5.1) Glitches in some apps, e.g. Fuubo (a Sina Weibo client) (gone with battery saver activated. The animation is still shown but no glitches) WORKAROUND: Add this line to build.prop debug.hwui.render_dirty_regions=false FIXED in 20150424
BUG #25: Mute and hold button in call screen are missing/disabled FIXED in 20150410
BUG #26: Due to new WiFi driver, MAC address will be changed. Will fix in next build. FIXED in 20150501
Amazing! Thanks a lot!
I've sold TX months ago. Now I have a Xperia T. I hope I can try a Lollipop T ROM soon!
DS-1 said:
Amazing! Thanks a lot!
I've sold TX months ago. Now I have a Xperia T. I hope I can try a Lollipop T ROM soon!
Click to expand...
Click to collapse
Thanks for your support
Oh, no: thanks to you! You're doing something really special for our abandoned phones!
By the way, I can't try it on my T, but how's the first feeling with this new rom? What are your first impressions?
updateing said:
Thanks for your support
Click to expand...
Click to collapse
updateing said:
One possible bug: no sound. Extract the attached file to /system/etc
If there's nothing wrong, you can ignore this. I can't remmeber if I inlcuded this in the system image...
BUG #2: NFC Service FC after boot. -> Delete /system/etc/permissions/android.hardware.nfc.hce.xml via Recovery (didn't pack this in...)
Click to expand...
Click to collapse
Thanks for the rom. I can't find /etc/permissions/android.hardware.nfc.hce.xml, when I go into file manager from recovery only system/bin is shown, what to do?
icALASAD said:
Thanks for the rom. I can't find /etc/permissions/android.hardware.nfc.hce.xml, when I go into file manager from recovery only system/bin is shown, what to do?
Click to expand...
Click to collapse
Mount system partition via recovery before entering aroma file manager. :good:
@updateing
Great work!! Gonna give this a shot for XV :good:
Will try to compile with your sources on git. Any recommendations?
WhiteNeo said:
Mount system partition via recovery before entering aroma file manager. :good:
@updateing
Great work!! Gonna give this a shot for XV :good:
Will try to compile with your sources on git. Any recommendations?
Click to expand...
Click to collapse
Thanks, it works.
I've installed PA GApps for Android 5.0 and I'm getting a few app crashes here and there. Downloads/Documents doesn't work at all, Google+ can't connect to the server for some reason, Play Newsstand crashes (downloaded from Play Store) and few things like that. Should I be posting these bugs? Are they rom related or is it because of GApps package?
Also, root works. I'll wipe everything and clean install GApps, see how it goes. Everything crashes for some reason right now.
icALASAD said:
Thanks, it works.
I've installed PA GApps for Android 5.0 and I'm getting a few app crashes here and there. Downloads/Documents doesn't work at all, Google+ can't connect to the server for some reason, Play Newsstand crashes (downloaded from Play Store) and few things like that. Should I be posting these bugs? Are they rom related or is it because of GApps package?
Click to expand...
Click to collapse
Might try the gapps from here.. Link
In other devices' forums, I have read about rom-related issues with certain google apps. So might possibly be rom related..
A logcat of the issues might come in handy.
WhiteNeo said:
Might try the gapps from here.. Link
In other devices' forums, I have read about rom-related issues with certain google apps. So might possibly be rom related..
A logcat of the issues might come in handy.
Click to expand...
Click to collapse
Downloading this right now, I'll see how it goes and let you know asap.
---------- Post added at 09:38 PM ---------- Previous post was at 08:38 PM ----------
Hmm... Downloads/Documents doesn't seem to work. I've cleaned everything and installed rom and gapps from scratch, music didn't work at first, but then I applied the fix and it's working now, DSP manager started working too. Every crash I had seems to be gone, for now at least. Only problem remains Downloads, tried cleaning data, but doesn't help. SuperSU BETA did work, I was able to root it by just flashing zip in recovery. All in all this rom's pretty stable considering that it's an experimental for now.
Also multiple users doesn't work, when you click on that profile icon in the right corner of notification dropdown it just opens up your LOCAL profile, not even the Google one.
---------- Post added 21st November 2014 at 12:03 AM ---------- Previous post was 20th November 2014 at 11:10 PM ----------
And also this
---------- Post added at 12:54 AM ---------- Previous post was at 12:03 AM ----------
Also dialer crashes when I go to history tab.
icALASAD said:
Downloading this right now, I'll see how it goes and let you know asap.
---------- Post added at 09:38 PM ---------- Previous post was at 08:38 PM ----------
Hmm... Downloads/Documents doesn't seem to work. I've cleaned everything and installed rom and gapps from scratch, music didn't work at first, but then I applied the fix and it's working now, DSP manager started working too. Every crash I had seems to be gone, for now at least. Only problem remains Downloads, tried cleaning data, but doesn't help. SuperSU BETA did work, I was able to root it by just flashing zip in recovery. All in all this rom's pretty stable considering that it's an experimental for now.
Click to expand...
Click to collapse
Yes the download manager and dialer are confirmed bugs. I'll sync and make a new build to see if they are fixed.
I'll try adding multi-user support in this build.
You really keep the hard work @updateing
=)
Thank you for bring Lollipop taste to TX user
xD
Wi-Fi icon moves back and forth in status bar when little arrows show up and in Settings some menus have the same icon, like 'Buttons' and 'Home' have the same house icon, also 'Profiles' and 'Location' both have location icon.
icALASAD said:
Wi-Fi icon moves back and forth in status bar when little arrows show up and in Settings some menus have the same icon, like 'Buttons' and 'Home' have the same house icon, also 'Profiles' and 'Location' both have location icon.
Click to expand...
Click to collapse
Will fix in next build. Thanks!
EDIT: wait for upstream to fix the icons in settings...
Great....we have Lollipop build....
i will try it when the bugs is not affecting much on my daily usage
Thanks for the update. Should I install it on clean phone or just upgrade? Also camera button doesn't work
Sorry, but is there any firm hope that we will have this on T (mint)?
tajimura said:
Sorry, but is there any firm hope that we will have this on T (mint)?
Click to expand...
Click to collapse
I am asking myself the same. There are some roms T/TX compatible. Out World be great having Android L on XT.
tajimura said:
Sorry, but is there any firm hope that we will have this on T (mint)?
Click to expand...
Click to collapse
mint is officially supported by CM, don't worry
AOSPA 6.0.1 for the Xperia Z2!
{
"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"
}
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
Instructions
If installing fresh and/or coming from another ROM (including previous PA versions)
Reboot into Recovery (Please use the latest TWRP) and MAKE A BACKUP!
Wipe System, Data, Cache, and Dalvik Cache
Flash Latest OFFICIAL STOCK ROM - This will ensure a clean system and all bootloader etc updated to latest.
Wipe System, Data, Cache, and Dalvik Cache
Flash the ROM
Flash GApps
Flash SuperSU (if you want to have root, that is)
Wipe Caches and Reboot
Profit!
Download Links
ROM: http://get.aospa.co/official/sirius
AOSPA Links
Google+: https://plus.google.com/communities/112514149478109338346
Gerrit: http://gerrit.aospa.co/
GitHub: https://github.com/AOSPA
#StayParanoid
XDA:DevDB Information
Paranoid Android 6.0.x, ROM for the Sony Xperia Z2
Contributors
tomgus1, sonyxperiadev, PA Team
Source Code: https://github.com/AOSPA/
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: AOSPA
Version Information
Status: Stable
Created 2015-05-06
Last Updated 2016-08-11
Changelog
20150704
- Bug fixes
- Added Live Display (Colour Calibration)
- Fixed Double Tap To Wake for sirius
20150619
- Immersive mode QS detail panel clean up.
- QS reorder reset button is now either on Settings/Backup and Reset or long pressing the settings wheel in statusbar header
- Screen unpinning fixed on devices with hardware buttons.
- Volume Panel tweaks.
- Volume Key Controls Settings
- New Settings Cellular drawable
- Fixes to the status bar battery icon
- Much more
20150612
- Immersive Mode
- QS Reorder
- Bug Fixes
20150528
- Wake on plug
- Home button wake
- Theme Engine bug fixes
- Volume Panel enhancements
- Low-level optimizations to our core base
- Loads of bug fixes for several NPEs, ANRs and OOMs.
20150520
- Misc Bug Fixes
- MSIM: Fix issues
- MSIM: Ability to hide empty sim card notifications
- Sound: connect/disconnect notification support (with ability to specify tone)
- Add option to disable search bar on recents
- Heads Up snooze (swipe up on a heads up notification initiates this)
- Change default mode of AppOps to make it more reliable
- Language translations (Thank you to our great Translators!)
- ParanoidOTA: Fix inability to download OTAs
- M8 & Sirius: Enabled QuickBoot
- Sirius: Removed button options in settings until SW button options are integrated.
20150513
- Audio Bug should now be fixed (Thank You CM)
- BackupTool is now fixed so wiping System (and reinstalling Gapps and SuperSU) is now unnecessary.
- Merge of android-5.1.1_r2 tag from AOSP
- Theme Engine support from CM-12.1 - Screenshot fixes (NPE and leaks)
- Cellular Networks migration (accessible through main settings now)
- Mute notification sounds threshold
- ParanoidOTA revamp with Material update
- Status Bar’s Double Tap to Sleep
- Misc Bug Fixes
20150506
Initial Release (Not Many Features)
Whats meant with
Need to use Multirom TWRP from M5
Mikey94 said:
Whats meant with
Need to use Multirom TWRP from M5
Click to expand...
Click to collapse
Sorry, during the development and bringing AOSPA-L to Z2 I had issues using TWRP straight from Dees_Troy and had recovery working when I used the modified Multirom version from Myself5. I can now confirm 2.8.6.0 is working.
Sorry for the confusion. [Updated OP]
Great ROM but playing music it goes loud then gets quiet, any fix?
K-NineHD said:
Great ROM but playing music it goes loud then gets quiet, any fix?
Click to expand...
Click to collapse
Could you grab a log next time that happens, the maintainer can't reproduce it.
Sorry for being such an idiot but how do I get a log?
K-NineHD said:
Sorry for being such an idiot but how do I get a log?
Click to expand...
Click to collapse
No worries try using this app that will gather all the info and then upload the text here and post me the link
All of the text? there is a lot and it will only let me copy one line at a time
---------- Post added at 08:18 PM ---------- Previous post was at 08:15 PM ----------
K-NineHD said:
All of the text? there is a lot and it will only let me copy one line at a time
Click to expand...
Click to collapse
nevermind XD[
---------- Post added at 08:27 PM ---------- Previous post was at 08:25 PM ----------
I'm sorry if I did it wrong but here: http://pastebin.com/g9E8fBwW
K-NineHD said:
All of the text? there is a lot and it will only let me copy one line at a time
---------- Post added at 08:18 PM ---------- Previous post was at 08:15 PM ----------
nevermind XD[
---------- Post added at 08:27 PM ---------- Previous post was at 08:25 PM ----------
I'm sorry if I did it wrong but here: http://pastebin.com/g9E8fBwW
Click to expand...
Click to collapse
That's Perfect :good: Audio error happened?
Yes it is
Same on latest cm12.1 builds... Has something to do with the mixer paths i think... You could try to Flash the "Stereo mod" from the dev section.
Works on Stock based, dont know if it Works with aosp.
---------- Post added at 09:41 PM ---------- Previous post was at 09:39 PM ----------
Here you go:
http://forum.xda-developers.com/xperia-z2/development/z2-t3092146
I used the "further" pack, Cause of a little more volume boost
It didn't work, now the cut off point where the music stays the same is lower
Mikey94 said:
Same on latest cm12.1 builds... Has something to do with the mixer paths i think... You could try to Flash the "Stereo mod" from the dev section.
Works on Stock based, dont know if it Works with aosp.
---------- Post added at 09:41 PM ---------- Previous post was at 09:39 PM ----------
Here you go:
http://forum.xda-developers.com/xperia-z2/development/z2-t3092146
I used the "further" pack, Cause of a little more volume boost
Click to expand...
Click to collapse
Yeah device code is based off CM so those bugs may be present. Myself and another AOSPA-L Dev haven't experienced the issue but I'll look into fixing for next release.
Keep the bug reports coming. Better we get things sorted sooner
Okay, thanks a lot for looking into it! I also experienced it with CM 12.1 by infected_. I'm going to go to stock and see if that fixes it
tomgus1 said:
Yeah device code is based off CM so those bugs may be present. Myself and another AOSPA-L Dev haven't experienced the issue but I'll look into fixing for next release.
Keep the bug reports coming. Better we get things sorted sooner
Click to expand...
Click to collapse
K-NineHD said:
Okay, thanks a lot for looking into it! I also experienced it with CM 12.1 by infected_. I'm going to go to stock and see if that fixes it
Click to expand...
Click to collapse
bug is there also on official builds... its something on the CM12 shinano repos , according to @cdesai .. we have been all week trying to figure it out, but no luck so far.
maybe @tomgus1 have better luck looking at it
this should work on a locked bootloader correct? I cant remember what kernel is used or if I have to bake my own aosp with sony's kernel
T_D_H said:
this should work on a locked bootloader correct? I cant remember what kernel is used or if I have to bake my own aosp with sony's kernel
Click to expand...
Click to collapse
This ROM requires an UNLOCKED BOOTLOADER as with all custom ROMs like AOSP, CyanogenMod etc..
tomgus1 said:
This ROM requires an UNLOCKED BOOTLOADER as with all custom ROMs like AOSP, CyanogenMod etc..
Click to expand...
Click to collapse
not all roms, but thank you for the info
T_D_H said:
not all roms, but thank you for the info
Click to expand...
Click to collapse
If you're flashing a full ROM to /system/, yes, it does require an unlocked bootloader..
{
"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"
}
This is Cypher. An extension to pure Android. Cypher tries to maintain the purity of Android while offering useful features for users. The goal is to give the highest level of performance whilst achieving simplicity.
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 us for messing up your device, we will laugh at you.
*/
Click to expand...
Click to collapse
Note: Builds are updated as soon as possible. There is no build cycle. Information pertaining to your device is displayed
Accordingly. The current build is the latest for your device. If your device is
scheduled to release on a certain day, but the new build isn't displaying, contact
your device maintainer for more information but wait at least 72 h. Please know builds are updated by 12am
EST.
Become apart of our G+ community - JOIN
Quote:
REMINDER
If you're having issues and want to submit a report (Logcat) please make sure you are reporting from the stock kernel, not a modified kernel. Modified kernels can break or fix, even improve things. It depends. I can't get a full clue of the issue when you're not running the original kernel.
Click to expand...
Click to collapse
Features:
- Status bar Customization
- Changeable icons
- Quick pulldown
- Smart pulldown
- Notification count
- Clock position
- Seconds in clock
- Date design
- Quick Settings
- Brightness slider
- Brightness icon
- Tile tap customization
- System
- Screenshot partial and full
- Scrolling cache customization
- Power menu customization
- One-handed mode
INSTALLATION INSTRUCTIONS
- Download the latest build of AOSCP (CypherOS)
- Download Gapps (Optional)
- Take a Nandroid backup
- Recommended - Full wipe and factory reset
- Flash ROM using TWRP
- Flash GApps (Optional)
- Flash Magisk (If you want root)
- Reboot.
- Enjoy!
-UPDATE INSTRUCTIONS-
- Download the latest build of AOSCP (CypherOS)
- Take a Nandroid backup
- Flash ROM using recovery
- Flash GApps.
- Flash Magisk (If you want root)
- Wipe cache
- Wipe dalvik cache
- Reboot
- Enjoy!
BUGS
- Srill don't know and you tell me
DOWNLOADS:
- Helium:
7/15/2017: v4.0.5 Android 7.1.2 r27
8/14/2017: v4.1 Android 7.1.2 r29
8/28/2017: v4.1.1 Android 7.1.2 r29 (lastest source, Cypher version, kernel: Fix torch flash when controled by camera Part-2)
- Hydrogen:
7/15/2017: v4.0.5 Android 7.1.2 r27
8/14/2017: v4.1 Android 7.1.2 r29
8/28/2017: v4.1.1 Android 7.1.2 r29 (lastest source, Cypher version, kernel: Fix torch flash when controled by camera Part-2)
DOWNLOAD ROMS: https://www.androidfilehost.com/?w=files&flid=198962
- Gapps: Here
- Magisk: Here
Credits
CypherOS
LineageOS
Ground Zero Rom
AICP
PureNexus
AOKP
Dirty Unicorns
Paranoid Android
and more....
Source Code: https://github.com/CypherOS/platform_manifest
Contributors
Dungphp
ROM OS Version: 7.x Nougat
Version Information:
Good
OMS???? WOW????
I can't find the clock position...also is there a way to make battery as text ?
wow! sounds a good rom, will have a try, thank you for so great work!
m1n15s said:
I can't find the clock position...also is there a way to make battery as text ?
Click to expand...
Click to collapse
Date and Time -- > Others setting
thanks，Try it all right
---------- Post added at 01:43 AM ---------- Previous post was at 01:43 AM ----------
Everything is fine
CySieben said:
thanks，Try it all right
---------- Post added at 01:43 AM ---------- Previous post was at 01:43 AM ----------
Everything is fine
Click to expand...
Click to collapse
Double tap anywhere to Sleep in this rom
@dungphp I'm having issue with screenshots.. doesn't capture it. Also I remember we had some issues with reading inbuilt storage a while back and a fix was released, not sure if it is related to that... Also doing a clean install and full restore, will report issues if i find any....
Nice to see this rom for our max.
But I have an error, can't install (Helium.)
Just me?
onderduiker said:
Nice to see this rom for our max.
But I have an error, can't install (Helium.)
Just me?
Click to expand...
Click to collapse
And your error during install is....?
something with "checking modem version"
Updater process ended with error 7
Error installing zip file '/sdcard/Download/aosp.......zip
onderduiker said:
something with "checking modem version"
Updater process ended with error 7
Error installing zip file '/sdcard/Download/aosp.......zip
Click to expand...
Click to collapse
Your modem is old.
Now you can fix problem for personal
- extract rom to a folder name as rom name
- delete line 2
assert(xiaomi.verify_modem("1.c1-00012-STD.PROD-1") == "1");
Click to expand...
Click to collapse
in updater-script then save
- zip everythings in folder. Copy to your phone, flash
Deleted !
Neo.Collin said:
@dungphp I'm having issue with screenshots.. doesn't capture it. Also I remember we had some issues with reading inbuilt storage a while back and a fix was released, not sure if it is related to that... Also doing a clean install and full restore, will report issues if i find any....
Click to expand...
Click to collapse
I havent has problem with screenshots. Other bugs i will fix soon
dungphp said:
Your modem is old.
Now you can fix problem for personal
- extract rom to a folder name as rom name
- delete line 2 in updater-script then save
- zip everythings in folder. Copy to your phone, flash
Click to expand...
Click to collapse
Thank you, used totalcommander and install went ok.
There is a big chance to talk with a loudspeaker instead of a handset
---------- Post added at 12:23 PM ---------- Previous post was at 12:22 PM ----------
扬声器发出声音，而不是听筒
In Magisk Manager ctsprofile check fails. Also, it would be good if ambient display options like wake when pulled out of pocket and network traffic indicator were implemented.
Just a humble question: What apps and services are affected by this Magisk/cts failure?
I ask because I want to know what to avoid (I have a principle of avoiding every app that has any kind of opinion about my system configuration since that's none of their business).
E90 Commie said:
Just a humble question: What apps and services are affected by this Magisk/cts failure?
I ask because I want to know what to avoid (I have a principle of avoiding every app that has any kind of opinion about my system configuration since that's none of their business).
Click to expand...
Click to collapse
AFAIK Netflix, Super Mario Run and Pokeman Go are the apps which doesn't run if CTS Mismatch.. there also maybe some Banking apps which may not work run.
E90 Commie said:
Just a humble question: What apps and services are affected by this Magisk/cts failure?
I ask because I want to know what to avoid (I have a principle of avoiding every app that has any kind of opinion about my system configuration since that's none of their business).
Click to expand...
Click to collapse
All my work related apps don't work with root..
---------- Post added at 04:35 AM ---------- Previous post was at 04:12 AM ----------
dungphp said:
I havent has problem with screenshots. Other bugs i will fix soon
Click to expand...
Click to collapse
Screenshots work after clean install.. things I've noticed so far
*I love the fact that this ROM is super fast and super light
*I love that it only has very minimal features, only ones I use
* I see there are 3 launchers preinstalled... Do we really need that many?
* Storage access is an issue, even in camera, downloads (doesn't show option of phone and SD card)
* Magisk doesn't work even with clean install (just ROM and gapps)
* Camera stutters like skipping frames when I move to focus on to a subject, happens after I click a picture, the clicked picture doesn't show up.. should be related to storage access itself. I tried disabling & enabling storage access.. one photo was ok, but after that kept giving green blank color images and freezes up camera.. not sure if RR camera fix will fix this issue!!
---------- Post added at 04:38 AM ---------- Previous post was at 04:35 AM ----------
lckjosh said:
In Magisk Manager ctsprofile check fails. Also, it would be good if ambient display options like wake when pulled out of pocket and network traffic indicator were implemented.
Click to expand...
Click to collapse
Did you check gestures section?? Lifting phone works...
{
"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 14.1 for Huawei Nova CAN-L11
DISCLAIMER:
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* 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.
NOTES
1) If you've found a bug, please report it along with a logcat.
2) If you experience a random reboot, please share /sys/fs/pstore/console-ramoops.
3) It should work on all models, just like LOS 13.
4) Lineage`s root is included (Settings > Developer Options > Root Access. If you want to install Magisk or something else, please uninstall Lineage`s root by flashing addonsu-remove-14.1-arm64-signed.zip in TWRP before installing Magisk or something else.
5) I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
Click to expand...
Click to collapse
LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's working :
Boots
Wifi
Bluetooth
Camera and Camcorder(video recorder)
Video Playback
RIL (Calls, SMS, Data)
Audio ( Recording and Playback )
Sensors
Fingerprint
Notification LED
FM Radio
GPS
NFC
Hotspot
What's not working / bugs:
Camera is / looks zoomed when recording a video (it seems to be same on stock)
HDR?
IMS/Volte
Requirements
Huawei Nova CAN-L11 (should work on the other models too)
Unlocked bootloader ( here's a guide about how to unlock it)
TWRP. The TWRP made by @Grarak is also working fine. You can find it here.
Click to expand...
Click to collapse
Installation
Starting with January 2018 builds you need Nougat /product partition otherwise you'll get bootloop. To get Nougat product partition, you must install / flash EMUI 5 or restore this TWRP backup of Nougat /product partition (more details here). You don't know how to restore that backup? Check the steps from this post.
Make sure you meet the requirements listed above.
Download the ROM and put it on sdcard. If you want GAPPS too, then download Open Gapps too (choose arm64, 7.1 and pico).
Reboot in TWRP by pressing all 3 buttons (Volume UP + Volume Down + Power).
Wipe system, data, cache and dalvik-cache.
Flash the ROM from the directory where you've placed it.
Flash GAPPS (OPTIONALLY).
Reboot.
Click to expand...
Click to collapse
Download
ANDROIDFILEHOST | MEDIAFIRE
Sources
LineageOS: https://github.com/LineageOS
Device: https://github.com/skinzor/android_device_huawei_hwcan
Vendor: https://github.com/skinzor/proprietary_vendor_huawei
Kernel: https://github.com/skinzor/android_kernel_huawei_msm8953-1
Click to expand...
Click to collapse
Donations
You don't have to, but if you like my work and you wish to support the development:
Donate via PayPal:
https://www.paypal.me/Henkate
https://forum.xda-developers.com/donatetome.php?u=4471434
I would use the money to upgrade my PC, so i can build with my own PC instead relaying on Google Cloud Platform.
Credits
@Grarak
@gt_o
@abhishek987
@crpalmer
@FrozenCow
@franciscofranco
@flar2
@Sultanxda
@zx2c4
@ Google for their cloud platform and free trial
@ LineageOS
@ Huawei
XDA:DevDB Information
[ROM][7.1.2][UNOFFICIAL] LineageOS 14.1 [25.05.2018], ROM for the Huawei Nova/Nova Plus
Contributors
#Henkate, Grarak, gt_o
Source Code: https://github.com/skinzor/android_kernel_huawei_msm8953-1
ROM OS Version: 7.x Nougat
ROM Firmware Required: Unlocked bootloader, TWRP
Version Information
Status: Stable
Created 2017-11-13
Last Updated 2018-05-25
Changelog
25 May 2018
* security patch level 5 May 2018
The development has been resumed and is possible thanks to @wangdaning who helped me to get a new Nova. Thank you!
Click to expand...
Click to collapse
15 February 2018
Read this small, but important F.A.Q.
* synced Lineage sources
* security patch level 5 February 2018
* switched to enforcing selinux
Click to expand...
Click to collapse
25 January 2018
ROM
* synced Lineage sources
* security patch level 05.01.2018
* fixed in-call volume slider, mic/sound recorder (it's louder now) thanks to @gt_o. Read more here.
* updated audio configs to B382 and synced few audio props with stock ones
* show "HUAWEI NOVA" instead "Android" when phone is plugged to PC
* removed substratum support.
* added two blobs to fix two errors in logcat
* added the missing device_qcom_common (i don't know how i haven't noticed that till now lol). Now there are 5 profiles: powersave, efficiency, balanced (default), quick and performance. This can be configured at battery settings. As an idea, the powersave profile seems to turn off 3 cores (the cores doesn't seems to turn on when there is a high load though), while the performace one sets all cores to 2ghz. The power hal being used is the one of msm8937, which is also an octa core CPU. This is defined in the power hal's makefile on Lineage's repo (if the processor is msm8953, use the power hal of msm8937). I recommend it to keep the balanced profile (which is enabled by default), but it's up to you.
Kernel
* merged stock kernel source into the CAF one (tag LA.UM.5.6.r1-01300-89xx.0 as this one semeed to be the closest to stock, but also based on the Adreno log)
* got rid of many drivers from Huawei. You can see the commits here. Thanks to @gt_o, huawei's bootfail monitor (HWBFM) has also been removed. Although HWBFM was disabled till now, it was better to get rid of it, to get a cleaner kernel, but also being easier to merge the stock source into CAF.
* cpuset updates (also in ramdisk)
* added WireGuard support, thanks to @zx2c4. WEBSITE | XDA
* removed fsync/crc toggles as it's better to not mess with them
Click to expand...
Click to collapse
9 December 2017
ROM
* synced Lineage sources
* added Substratum support
* fixed blinking mode of notification light
* allow minimum brightness 1 (it was 4 before)
* possibly fixed the power usage reported by bluetooth ( i can't test right now as phone is charging and can;t reset the battery stats)
* Reverted this commit (more details there)
Kernel
* fixed hotspot
* cleaned ramdisk
Click to expand...
Click to collapse
25 November 2017
ROM
* security patch 6 November 2017
* fixed signal icon on 3G (it isnt empty / gray anymore)
* fixed flac audio playback
* updated media configs to N B382
* hide sRGB toggle in developer options
* increased the number of voice call steps from 5 to 8, and media volume steps
from 15 to 20
* increased the handset volume from the default (84) to 88 to improve UX with voice calls
* added ext4 support for /data
* added f2fs support for /cache
* added glove mode (Settings > Display > High touch sensitivity)
* from now on, Lineage`s root is included (Settings > Developer Options > Root Access. If you want to install Magisk or something else, please uninstall Lineage`s root by flashing addonsu-remove-14.1-arm64-signed.zip in TWRP before installing Magisk or something else.
Kernel
* fixed logd/klogd issue (the high cpu usage)
* disabled HUAWEI_DEBUG_MODE config
* added DriveDroid support: allows you to boot your PC from ISO/IMG files stored on your phone [UNTESTED]
* added USB HID gadget support
* CRC toggle; enabled by default (disable it for 30% performance improvement at the risk of data corruption, according to its description)
* FSYNC toggle; enabled by default (disable it to possibly increase performace at the risk of data corruption
Click to expand...
Click to collapse
13 November 2017
* initial release
Click to expand...
Click to collapse
Reserved
Dowloanding ^^
As soon as I can, I'll report back =)
Thank You #Henkate for keeping Nova alive!
Hi, i was waiting for LOS14 so much, thank you for the hard work <3. I just have a few concerns about the unlocking bootloader/rooting/twrping stuff of my MLA-L11, since noone of the methods has been confirmed to work on that model.. And i simply can't risk a 300 € brick. I'm confident with modding, the method seems crystal clear.. Just asking the Dev if he thinks it should works for me. Also, if i should take some cautions and how. Android 7, EMUI 5, full stock. Of course modding is always a risk, but.. you know what i mean. Thanks in advance, i hope that's not off the topic!
Works fine here, thanks a lot for the hard work !!!
Will give it a shot this weekend. I am a teacher and students are doing mid term exams this week, so I kind of need my phone.
For some reason, I can't get it to boot. It is on LOS bootanimation and doesn't boot =/ can't even get a log.
Clean format always, I tried with stock open gapps, pico open gapps, without open gapps. It seems something is wrong with my phone.
then i thought the issue could be I'm coming from EMUI 5.
Then I tried to restore bluesmoothie backup and put LOS over it, nothing =/
I don't know why =/
To all people: I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
GertFromTheWell said:
Hi, i was waiting for LOS14 so much, thank you for the hard work <3. I just have a few concerns about the unlocking bootloader/rooting/twrping stuff of my MLA-L11, since noone of the methods has been confirmed to work on that model.. And i simply can't risk a 300 € brick. I'm confident with modding, the method seems crystal clear.. Just asking the Dev if he thinks it should works for me. Also, if i should take some cautions and how. Android 7, EMUI 5, full stock. Of course modding is always a risk, but.. you know what i mean. Thanks in advance, i hope that's not off the topic!
Click to expand...
Click to collapse
Hi there!
Thank you too for the kind words!
I don't know if it'll work, but it has been confirmed that MLA-L03 has been unlocked with the same method. Theoretically, it should work on your MLA-L11 too since it's one of MLA series.
Also, the process of unlocking bootloader is "general", it isn't meant only for one or two phones/models. If I'm not mistaken, I think you can't even brick a phone when you're trying to unlock the bootloader.
If you'll unlock the bootloader and by any chance LOS14 isn't booting on your model, you'll have to relock the bootloader, download EMUI 5 firmware from Firmware Finder and install it.
LOS 13 could be flashed from EMUI 5, so it shouldn't matter for LOS 14 neither.
Vinnom said:
For some reason, I can't get it to boot. It is on LOS bootanimation and doesn't boot =/ can't even get a log.
Clean format always, I tried with stock open gapps, pico open gapps, without open gapps. It seems something is wrong with my phone.
then i thought the issue could be I'm coming from EMUI 5.
Then I tried to restore bluesmoothie backup and put LOS over it, nothing =/
I don't know why =/
Click to expand...
Click to collapse
What's your Nova model? I've forgot .
Did you take a look at the recovery log after you're flashing LOS 14 or the output from recovery itself? Does it really gets flashed properly?
LOS 13 could be flashed from EMUI 5 too, so that shouldn't matter neither with LOS 14.
I'll make an eng boot.img later (when I'll get access to PC), so you'll be able to take a logcat during booting.
#Henkate said:
To all people: I would appreciate if you could write the Nova model on which you've flashed LOS14, if your model is other than CAN-L11.
Hi there!
Thank you too for the kind words!
I don't know if it'll work, but it has been confirmed that MLA-L03 has been unlocked with the same method. Theoretically, it should work on your MLA-L11 too since it's one of MLA series.
Also, the process of unlocking bootloader is "general", it isn't meant only for one or two phones/models. If I'm not mistaken, I think you can't even brick a phone when you're trying to unlock the bootloader.
If you'll unlock the bootloader and by any chance LOS14 isn't booting on your model, you'll have to relock the bootloader, download EMUI 5 firmware from Firmware Finder and install it.
LOS 13 could be flashed from EMUI 5, so it shouldn't matter for LOS 14 neither.
What's your Nova model? I've forgot .
Did you take a look at the recovery log after you're flashing LOS 14 or the output from recovery itself? Does it really gets flashed properly?
LOS 13 could be flashed from EMUI 5 too, so that shouldn't matter neither with LOS 14.
I'll make an eng boot.img later (when I'll get access to PC), so you'll be able to take a logcat during booting.
Click to expand...
Click to collapse
Mine is CAZ-TL10 (chinese). I'll try again (today I won't be able to, maybe thursday or friday) and take the recovery.log which I forgot :/
However, the twrp output was fine. I had some bad lines:
Failed to mount /cust (always have it)
E: unknown command (two lines of this message after flashing the ROM)
Enviado de meu HUAWEI CAN usando Tapatalk
Vinnom said:
Mine is CAZ-TL10 (chinese). I'll try again (today I won't be able to, maybe thursday or friday) and take the recovery.log which I forgot :/
However, the twrp output was fine. I had some bad lines:
Failed to mount /cust (always have it)
E: unknown command (two lines of this message after flashing the ROM)
Enviado de meu HUAWEI CAN usando Tapatalk
Click to expand...
Click to collapse
I see.
I have the second error too, after flashing the ROM. I haven't checked why, but it doesn't seems to affect anything.
As I've said, i'll provide an eng boot.img later, so you'll be able to take a logcat during boot.
#Henkate said:
As I've said, i'll provide an eng boot.img later, so you'll be able to take a logcat during boot.
Click to expand...
Click to collapse
@Vinnom
Here you go. Install it from recovery.
I have a MLA-L03 and I was on LOS13, followed the steps and everything works fine for me.
sk8buoy said:
I have a MLA-L03 and I was on LOS13, followed the steps and everything works fine for me.
Click to expand...
Click to collapse
Are you having the no sim card bug as well ?
Vive le quebec !!!:good:
icutzo said:
Are you having the no sim card bug as well ?
Vive le quebec !!!:good:
Click to expand...
Click to collapse
Nope, this bug is gone now. When I'm on LTE the icon don't show LTE (it show only the signal strength) but data works fine.
I thought it would be possible for me to try and flash again only in thursday, but I could today.
I tried to different ways:
Clear flashing;
Formating data;
Neither worked.
I took 2 recovery logs, before and after formating data.
I took a logcat while booting, thanks to the eng boot.img provided.
The logs can be found here.
I don't have a clue why it doesn't boot =/
I took a look at the logs, everything seems to be flashed without any problem and I can't understand right the logcat. I hope it can be useful
Runs good in MLA-L11 with some issues:
The camera stop ramdon
-the front camera have issues with post processing.
Using the OP Camera works good.
-all the cores are 2.02ghz all the time the phone is active
-When you get the kernel CAF will be a perfect ROM. thanks for the hard work hetanke !
Vinnom said:
I thought it would be possible for me to try and flash again only in thursday, but I could today.
I tried to different ways:
Clear flashing;
Formating data;
Neither worked.
I took 2 recovery logs, before and after formating data.
I took a logcat while booting, thanks to the eng boot.img provided.
The logs can be found here.
I don't have a clue why it doesn't boot =/
I took a look at the logs, everything seems to be flashed without any problem and I can't understand right the logcat. I hope it can be useful
Click to expand...
Click to collapse
The recovery logs looks fine. I see that you have also installed Magisk and a Titanium Backup zip. Just to be clear, you have tried to install it without anything else too?
1) Did you wait about 5 mins ( although i dont think that much time is required)?
2) Can you take a kernel log too?
Run the following command, while booting (let it run few seconds after you think that you have got bootloop):
Code:
adb shell "cat /dev/kmsg"
I cant find anything wrong in logcat neither. I think the stock kernel may not be compatible with your model, so i will need to use the kernel source for your model or compare the two sources and import changes from CAZ-TL10 source into the one im using now.
The stock kernel source which is being used right now is CAZ_NG_EMUI5.0_opensource. According to Huawei`s website, it is meant for:
HUAWEI Nova,HUAWEI Nova Plus, CAN-L10, L11, MLA-L01,L11,L12,L13, Android 7.0, EMUI 5.0
Click to expand...
Click to collapse
When i search for "CAZ" on their website, i find nothing. But there seems to be:
Cannes-AL10_TL10 HUAWEI nova, Cannes-AL10, TL10, Android 7.0, EMUI 5.0
Click to expand...
Click to collapse
Perhaps thats the right one for CAZ-TL10 too?
imkoma said:
Runs good in MLA-L11 with some issues:
The camera stop ramdon
-the front camera have issues with post processing.
Using the OP Camera works good.
-all the cores are 2.02ghz all the time the phone is active
-When you get the kernel CAF will be a perfect ROM. thanks for the hard work hetanke !
Click to expand...
Click to collapse
Thank you too for your words!
By the way, its Henkate. You can also call me Robert .
1) When exactly camera is stopping and how? I didnt encounter this on my CAN-L11
2) What kind of issues does have front camera? My Nova`s front camera got damaged / broken when my Nova has been damaged, therefore i cant use it nor test it.
3) Regarding the cores, ive wrote at "notes" in first post:
The first thing you want to do after first reboot is to install a file manager and rename /system/bin/logd to "logd.bak" and reboot. You have to do this in order to get rid of the high CPU load. Consider this a workaround until the issue gets solved. Note that this breaks logcat, so you'll have to rename it back to "logd" and reboot to be able to take a logcat.
Click to expand...
Click to collapse
Would be nice if you could share a logcat regarding 1) and 2).
{
"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 11, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/pioneer
Downloads :
https://download.lineageos.org/pioneer
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
[ protip: 20191010+ builds require 50.2 FW (at least bluetooth, dsp, modem from it) If you're still running 50.1 you can flash this package in TWRP: https://androidfilehost.com/?fid=4349826312261716572 unless you're fine with having partially broken audio and broken Egistec fingerprint sensor ;3 ]
However if you want to flash whole firmware package onto both slots, you can follow the guide below:
1. Download latest firmware with XperiFirm.
NOTE: When using mono XperiFirm will fail to unpack the firmware, you can do it manually using following commands:
Code:
for f in FILE_*; do unzip $f; done
unzip boot.zip -d boot
2. Go to the directory where the firmware got downloaded to and remove following files:
- boot_X-FLASH-ALL-18AE_0x00.hash
- boot_X-FLASH-ALL-18AE.sin
- persist_X-FLASH-ALL-18AE_0x00.hash
- persist_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-18AE_0x00.hash
- system_other_X-FLASH-ALL-18AE.sin
- system_other_X-FLASH-ALL-9B8D_0x00.hash
- system_X-FLASH-ALL-18AE_0x00.hash
- system_X-FLASH-ALL-18AE.sin
- system_X-FLASH-ALL-9B8D_0x00.hash
- userdata_X-FLASH-CUST-18AE.sin
- vendor_X-FLASH-ALL-18AE_0x00.hash
- vendor_X-FLASH-ALL-18AE.sin
- vendor_X-FLASH-ALL-9B8D_0x00.hash
3. Turn off your phone, hold vol dn and plug in the USB cable, the screen should be off and green LED lit.
4. Run Newflasher, it'll flash entire FW to your current slot then unplug the USB cable and power on your phone.
5. Reboot to recovery mode (both Lineage recovery and TWRP will work)
6. Flash https://androidfilehost.com/?fid=4349826312261712574
7. Profit?
0
Seppppx said:
@LuK1337
By WFD you mean Wi-Fi direct or Wi-Fi display?
Click to expand...
Click to collapse
Latter one.
Amazing!
Thank you very much and outstanding work OP! I got this device last week installed LOS17.1 right away, and there is v 18 already in the works! So cool.
drkshdwprophet said:
Thank you very much and outstanding work OP! I got this device last week installed LOS17.1 right away, and there is v 18 already in the works! So cool.
Click to expand...
Click to collapse
Did u install it ?
Can I say what's working and what not?
Arbaazhussain said:
Did u install it ?
Can I say what's working and what not?
Click to expand...
Click to collapse
Do it yourself.
LuK1337 said:
Do it yourself.
Click to expand...
Click to collapse
Ok and it was quick reply
---------- Post added at 08:35 PM ---------- Previous post was at 08:33 PM ----------
Should I use nikgapps android 11?
Will it work?
Arbaazhussain said:
Ok and it was quick reply
---------- Post added at 08:35 PM ---------- Previous post was at 08:33 PM ----------
Should I use nikgapps android 11?
Will it work?
Click to expand...
Click to collapse
God only knows.
LuK1337 said:
God only knows.
Click to expand...
Click to collapse
Ok I will try
Root which magisk version should be used?
---------- Post added at 08:40 PM ---------- Previous post was at 08:37 PM ----------
Sir can u say me what are changes brought with everyday build?
Arbaazhussain said:
Ok I will try
Root which magisk version should be used?
---------- Post added at 08:40 PM ---------- Previous post was at 08:37 PM ----------
Sir can u say me what are changes brought with everyday build?
Click to expand...
Click to collapse
Do I look like someone who'd use Magisk? Also no, I'm not going to put my time into writing changelogs.
Thanks for your work!!!
Is it possible that this version will go official some day (after testeing, etc...) or will it never for some known reasons?
emc02 said:
Thanks for your work!!!
Is it possible that this version will go official some day (after testeing, etc...) or will it never for some known reasons?
Click to expand...
Click to collapse
Yeah, it is quite possible that @Arbaazhussain and other people asking about official builds / future plans will annoy me so much that I'll just drop support entirely.
emc02 said:
Thanks for your work!!!
Is it possible that this version will go official some day (after testeing, etc...) or will it never for some known reasons?
Click to expand...
Click to collapse
The builds is always unofficial unless the lineage 18 is released as stable and then maintainers can make it official
So it is unofficial now
later official if luk sir does of course
---------- Post added at 05:26 PM ---------- Previous post was at 05:25 PM ----------
LuK1337 said:
Yeah, it is quite possible that @Arbaazhussain and other people asking about official builds / future plans will annoy me so much that I'll just drop support entirely.
Click to expand...
Click to collapse
Sorry if I have annoyed you
I ask for forgiveness from the depth of my heart
Goddamn, didn't expect this one. Gonna try this one soon
i have installed this ROM. very good. no problems. also have installed nikgapps BASIC. everything is OK. thanks to the dev luK1337
Enviado do meu H4113 através de Tapatalk
Is there a way to activate VOLTE? I thought VOLTE and wifi calling were options on LOS 17. I had bricked this phone trying to update to the last LOS 17 and has been unused for a month or so, so I might be thinking of a rom I had on my XZP. Either way works good so far except I haven't been able to activate it on my new carrier, but that's another story.
Error installing
Hello,
I tried installing this version after using 17.1 for quite a bit. I wiped dalvik/art cache, system and data; flashed new firmware (probably, since on LOS17.1 everything was working perfectly), flashed twrp 3.4.0-1 recovery.
The issue is, i get an error saying Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError)
Updater process ended with ERROR: 1
Any help would be greatly appreciated,
Thanks.
DarkInvaderr said:
Hello,
I tried installing this version after using 17.1 for quite a bit. I wiped dalvik/art cache, system and data; flashed new firmware (probably, since on LOS17.1 everything was working perfectly), flashed twrp 3.4.0-1 recovery.
The issue is, i get an error saying Error applying update: 28 (ErrorCode:: kDownloadOperationExecutionError)
Updater process ended with ERROR: 1
Any help would be greatly appreciated,
Thanks.
Click to expand...
Click to collapse
Try to fastboot boot latest twrp instead.
LuK1337 said:
Try to fastboot boot latest twrp instead.
Click to expand...
Click to collapse
Tried doing that but i either get FAILED (Write to device failed in SendBuffer() (Too many links)) or FAILED (Write to device failed (no link)).
Flashed my firmware again just in case so i guess its not hard bricked?
Ill try to fastboot boot from a different PC to see if the issue is there.
Thanks for replying.