Disclaimer:
LineageOS (Lineage Android Distribution) members or anyone else on this website is 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 the products you find here 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. Your warranty will be void if you tamper with any part of your device / software.
How to Install:
1- BACKUP, BACKUP, BACKUP, All will be WIPED!
2 - Unlock bootloader instructions here
3 - Flash the new mandatory TWRP Recovery
4 - Move Rom & Gapps (optional) into device storage
5 - Full Wipes
6- Flash Rom & Gapps (gapps are OPTIONAL)
for GAPPS:
Choose Gapps Package "ARM" > "6.0" > "Pico" or "Nano" visit OpenGAPPS
Working:
Boots
Storages
Bluetooth
Wifi
GPS - GNSS
Audio
Charging
Offline Charging
Video decoding/ Playback (i.e.: Youtube) up to 720p
android marshmallow new features: Adoptable Storage / Multi Window / etc
DRM Widevine : For Netflix, Amazon Prime, etc
Sensor: magnetometer: akm8963
Front Camera: mt9m114_mipi_raw
Front camera: GC0339_RAW
etc ....
NOT Working:
Rear Camera: a5142_mipi_raw
Front Camera: GC0339_RAW (ME173X 8GB) Fixed on build 20220629
Sensors: accelerometer (autorotation)
You tell me
Special Thanks
OMNI Rom
LineageOS
DerTeufel1980 & fire855 ( my Team mates from M.A.D)
GPL Compliance:
GitHub - dragonpt/android_device_asus_me173x: ASUS ME173x device for LineageOS 12.1 & LineageOS 13
ASUS ME173x device for LineageOS 12.1 & LineageOS 13 - GitHub - dragonpt/android_device_asus_me173x: ASUS ME173x device for LineageOS 12.1 & LineageOS 13
github.com
GitHub - dragonpt/android_kernel_asus_me173x_new: ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / 14.1
ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / 14.1 - GitHub - dragonpt/android_kernel_asus_me173x_new: ASUS ME173x [MT6589 - MT8125] Custom Kernel for LineageOS 12.1 / 13 / ...
github.com
--> "asus_mm" branchs
FAQ
Small FAQ:
Q: How can i Unlock the Bootloader?
A: Instructions for Unlocking the Bootloader can be found here
Q: After locking the screen, the screen is all black, and/or flickering and I'm forced to reboot, how can I fix this?
A: If you have this issue, then your device uses the second screen/lcm hardware revision
( the lgld070wx3_dsi_vdo ), please use the second kernel.zip for this variant, it'll be added an second kernel . zip for people with this variant, on the download section with the ROM release
Q: how to flash this second kernel for the new hardware variant ?
A: After flashing the ROM, flash the second kernel afterwards
Q: Where are the Developer Options?
A: Go to Settings>About Tablet, and tap 7 times on the Build Number
Q: Where is the multi-window mode?
A: in the developer options, you can enable it there
Q: How can i root this rom?
A: you can use Magisk , or SuperSU
Magisk: v.23
SuperSu v2.82
note: Magisk builds v24.x and v25.x do NOT work.
Q: Do i really need to update recovery?
A: YES
Q: I can't flash this Rom on recovery, why?
A: You need to update your recovery to TWRP
Q: how to work with twrp?
A: in the first time TWRP boots, it'll ask if you want to allow modifications, slide to YES
Q: how to wipe and flash in twrp?
A: Go "mount" and mount "system"
then go "wipe" > and wipe dalvik / cache / data / System
Q: How can i flash the new recovery?
A: If you already have an custom recovery installed:
Download the new TWRP recovery zip
flash the new recovery
reboot to recovery again, TWRP should be now installed
If you don't have any custom recovery installed:
- You can extract the "recovery.img" from the .zip
- Open an terminal
- Boot to fastboot mode, and type:
Code:
fastboot flash recovery recovery.img
then reboot:
Code:
fastboot reboot
Q: I Love your work, how can i thank you?
A: You can press the "Thanks" button, and if you wish, you can pay me a beer
..
Changelogs
Build 20201221
First Release
Build 20210821
Kernel:
DCT / Power resolve more issues
LCM: nt35521_dsi_vdo: Add backlight enable ctrl function
Fix magnetometer sensor: akm8963
Battery: Corrections
Camera LENS AF (for the rear camera) fixed
Front Camera : mt9m114_mipi_raw ( ME173X 16GB Version) fixed
mmc: more handling fixs
msdc: more fixs
Touch Panel: GT927: Implement a proper suspend & resume
Some other small fixs.
LineageOS source and device:
LineageOS LiveWallpapers, Wallpapers are now included ( as per-user requests)
Gello browser removed, it's depricated and has security risks
Disable Live Display by default (not supported by this device)
Some device clean up
Fix some eGL crashs
Fix some core missing symbols
Added Front camera support ( Pictures )
Some other small fixs.
Build 20220629
Kernel:
Security: Fix the following security issues:
PG SU daemon security fix
CVE-2017-1000365
CVE-2017-2618
CVE-2017-2671
CVE-2016-10208
CVE-2016-10208
CVE-2013-4312
CVE-2016-2550
CVE-2017-9074
CVE-2017-9075
CVE-2017-9076
CVE-2017-9077
CVE-2017-9242
LVT-2017-0002
CVE-2012-6703
CVE-2015-8944
CVE-2016-3857
CVE-2016-9555
CVE-2017-8890
ARM: spectre-v1
ARM: spectre-v2
ARM: Merge some bug fixs
imgsensors:
mt9m114_mipi_raw: Enable NightMode & Improve NightMode handling (better handling of Low light pictures)
gc0339_raw support added (CMOS front camera used in some HW revisions)
Memory management / Others:
Merge ZRAM from Kernel 3.10 version, and backport K 3.10 ZRAM fixs
Merge zsmalloc from Kernel 3.10 version, and backport K 3.10 ZRAM fixs
Add support for LZ4 decompression in the Linux Kernel
Other minor fixs
LineageOS source and device:
device: Added 512 MB Virtual SWAP Memory
Fix GPU PowerVR blobs crash, leading to random reboots & wakeup reboots
Disable OpenGL preloading with PowerVR drivers
SHIM: Add UI shim lib to fix some other random crashs
Remove max app limit
ART: Increase and fine tune the heap limit
Camera & nvram blobs fixs
Other minor fixs
Build 20220718
Fixed Bluetooth, that got broken by mistaque on 20220629 release
Downloads
TWRP 3.1.1
TWRP_3.1.1_ME173X.zip | by superdragonpt for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Build 20220718
https://androidfilehost.com/?fid=15664248565197191338If you have the second hardware Screen revision by LG (check FAQ), flash this
kernel for the Build 20220718
https://androidfilehost.com/?fid=15664248565197191342
Old Builds
Build 20220629
https://www.androidfilehost.com/?fid=15664248565197184858If you have the second hardware Screen revision by LG (check FAQ), flash this
kernel for the Build 20220629
https://www.androidfilehost.com/?fid=15664248565197184860
Build 20201221
lineage-13.0-20201221-UNOFFICIAL-me173x.zip | by superdragonpt for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
If you have the second hardware Screen revision (check FAQ), flash this
kernel for the Build 20201221
Kernel_rev2_Build_20201221.zip | by superdragonpt for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Build 20210821
https://www.androidfilehost.com/?fid=7161016148664790672If you have the second hardware Screen revision by LG (check FAQ), flash this
kernel for the Build 20210821
https://www.androidfilehost.com/?fid=7161016148664790675
Man, you're awesome
But I have issue with wifi. Cant turn it on and my mac adress is 02:00:00:00:00
Bluetooth also not working
gadom92 said:
Man, you're awesome
But I have issue with wifi. Cant turn it on and my mac adress is 02:00:00:00:00
Click to expand...
Click to collapse
Same here
Awesome work, thx and merry xmas
gadom92 said:
Man, you're awesome
But I have issue with wifi. Cant turn it on and my mac adress is 02:00:00:00:00
Bluetooth also not working
Click to expand...
Click to collapse
This seems to be the very same issue some users had with Lineage 12.1...
can** replicate this on my units.
EDIT: i meant, can't replicate this
please try this:
[ROM] [UNOFFICIAL] LineageOS 12.1 |ASUS Memo Pad HD 7 (me173x) [MT8125]
Disclaimer: LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if...
forum.xda-developers.com
Settings > Backup & reset
superdragonpt said:
This seems to be the very same issue some users had with Lineage 12.1...
can replicate this on my units.
please try this:
[ROM] [UNOFFICIAL] LineageOS 12.1 |ASUS Memo Pad HD 7 (me173x) [MT8125]
Disclaimer: LineageOS (Lineage Android Distribution) members or anyone else on this website is not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if...
forum.xda-developers.com
Settings > Backup & reset
Click to expand...
Click to collapse
Did not solve the problem so far. Wifi is even broken after restoring the los 12.1 backup which worked before
Edit: uploaded logcat
Ok, i reflashed the old carliv recovery via fastboot after installing Los13 and i got wifi back ...
And afterwards i flashed twrp again via fastboot and wifi is still working...
Previously i flashed the twrp zip from carliv, i guess this was part of the problem
reflashing recoveries in fastboot not worked for me :/
I also wiped everything including internal storage before, and bootet into each of the two recoveries and to the system from there.
Maybe the carliv recovery changes some things on the system, idk.
Hi, I am so glad that this is still alive project
I upgraded recovery via mtk flesher. Just rename twrp 3.1.1... into recover.img and click "download".
My wifi and bluetooth are working. Sometimes bluetooth have conflict with wifi and plain reboot fix things.
It is strange that not a single one sensor work(acceleration and gravity, magnetic field, orientation and rotation. They all worked in 12.1 beside rotation. Hope thing are going to get fixed up.
Had a few freezes also(hard reset do the job)
Overall I have a feeling that this is smoother than 12.1.
EDIT: It was misleading about recovery flash. You need to extract from twrp_3.1.1_ME173X.zip "recovery.img" and replace in folder where scatter file with old "recovery.image" is.
Gronkdalonka said:
I also wiped everything including internal storage before, and bootet into each of the two recoveries and to the system from there.
Maybe the carliv recovery changes some things on the system, idk.
Click to expand...
Click to collapse
interesting... likely the wiping of internal storage fixed it..
if anyone is having this issue, please try and report back if the following fixs:
in twrp:
Flash this test kernel
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
cheers
Merry Xmas
superdragonpt said:
interesting... likely the wiping of internal storage fixed it..
if anyone is having this issue, please try and report back if the following fixs:
in twrp:
Flash this test kernel
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
cheers
Merry Xmas
Click to expand...
Click to collapse
not working :/
edit: Flashed old recovery trough Flash Tool, than TWRP in Flash tool wipe all what i can and then install LOS 13. Wifi working like a charm
Any chance you can help with source patches?
First of all thanks to snapdragon for the new LOS13 support.
I'm sorry to tell you that all of your mentioned ways to get WiFi back to work did not work for me. What I did and what I tried:
Normal installation way:
Flashed new recovery via old custom recovery
complete wipe
flashed new LOS13 via new TWRP recovery
WiFi not working!
Going back to old custom recovery and back to TWRP
Flashed old custom recovery via TWRP
complete wipe
flashed new TWRP custom recovery via adb sideload since my sd card can only be mounted via new TWRP recovery
complete wipe
flashed new LOS13
WiFi still not work!
This is all I did. I realized that fastbood mode is not working for my device, could be a driver problem since my device is installed as ùó something when plugging it into the pc in fastboot mode, so I tried the way via adb.
Hint: I have the model with the alternative hardware, so the second kernel is required to fix flickering display issue.
I realized that the new TWRP recovery has this issue aswell, so my display is flickering from the right side to the center sometimes in TWRP recovery.
Any ideas what could help getting WiFi back to work?
Thanks in advance!
Edit: Could it be that this WiFi problem has something to do with the following thread:
FIX FOR MAC 02:00:00:00:00(WiFi and hotspot not turning ON)
Important. Root required..... Hey everyone,I saw so many posts regarding Android & iOS that the Mac address is changing to 02:00:00:00:00 and WiFi is greyed out. None of the WiFi or hotspot not turning on.I get the same problem in my Condor and...
forum.xda-developers.com
I read over some postings and googled the mac address 02.00.00.00.00 and it seems that a lot of devices had this problem when updating from android 5 to 6. It seems that it could have something to do with the partitions where the info (mac address, IMEI) are stored, but in general I have not found a solution and a specific description of the problem.
Anyway: If the problem can be solved by doing the steps described in the thread I provided above I’m not able to solve this. I would not describe me as a noob, but it seems that I need root and knowledge of permission management for the fix, and I am not very familiar with Linux.
Could you do the following test:
In twrp:
Full wipes ( system, etc etc and internal storage) be sure you back up your stuff
Then reboot to recovery
( It'll warn there's no OS installed)
Back to recovery
Do full wipes again , plug the tab into pc and copy the rom to internal storage
Reboot to recovery again
( It'll warn again, there's no OS installed)
Proceed to flash the rom
This has worked with a user
Issue: for an unknown reason some devices seems to fail mounting / reading nvram
@ twrp I'll do a build for people with this second hardware revision, flickering is annoying...
Thanks for your fast reply.
I did two full wipes with rebooting into recovery after each wipe as you said, then I copied the OS zip file to internal storage and rebooted again to recovery.
After installing the ROM I rebootet to system and LineageOS was preparing the first start. I started without flashing the kernel for alternative hardware (2nd kernel) to check if it works first.
I'm sorry to tell you that I still got no WiFi and Bluetooth connections, Mac address still is shown as 02-00-00-00-00, WiFi cannot be turned on.
Edit: Seems that is has nothing to do with wipes (on my device). I've tried all kind of wipes via TWRP
Format Data -> yes -> reboot to recovery
Advanced Wipe -> check all (Davlik, Cache, Data, Internal Storage, System -> Again format data -> Yes -> reboot to recovery
flashed ROM, 2nd Kernel and GApps -> Reboot to recovery -> reboot to system
Still no WiFi. Perhaps I should try to go back to stock rom and see if WiFi works there? Do you think this could make the deal?
test this
full wipes
flash rom, then this kernel afterwards
AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Again, thanks for your efforts, it seems to be a really tough and bugging one, since the new kernel did also not fix the problem.
Edit: Just to keep u updated: I just flashed old recovery and afterwords old LineageOS 12, WiFi is working well. So there must be some problem with the update or the update process. I will try to wipe first and then install new recovery and again install new OS, perhaps this will do the job.
Edit2: BTW I forgot to tell you that I had problems with settings -> about tablet -> status on lineageos 12. Just remembered because i wanted to have a look to the mac address. I get an error telling me "unfortunately, settings has stop". Perhaps important for the update?
Important Edit3:
Guess what: I made it to work. I did the following to do it:
1. Format Data and do all wipes possible with TWRP recovery. Reboot to recovery and do the same again.
2. TWRP recovery -> install old recovery
3. In old recovery -> install via sideload (adb sideload) lineageOS12 and second Kernel (for me because of hardware)
4. Boot to system and check if WiFi works well (finish the initialization of the device and connect to a WiFi)
5. Boot to recovery (old recovery) -> WITHOUT WIPING install via sideload TWRP recovery
6. Boot to system. (Still lineageos12) check if WiFi still works
7. Boot to TWRP recovery -> WITHOUT WIPING install lineageos13.
8. Boot to system, finish initialization if necessary and check if WiFi still works.
9. Go to setting and do a factory reset from lineageos13 settings
10. Device will reboot to recovery and do the factory reset and automatically will boot back into system.
11. Finish. All should work now.
I don't know what exactly did the job, so I wanted to provide all steps I did.
Since I never flashed an android custom Rom over another without wiping I don't know what errors this procedure can cause. So if someone knows that please let me now that I can have a look if there are errors.
Thanks again for your assistance.
Related
[ROM][UNOFFICIAL][6.0.1][E6853/E6803] CyanogenMod 13 for the Sony Xperia Z5 Premium [ALPHA]
{
"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"
}
CyanogenMod 13 for the Sony Xperia Z5 E6853 and E6803
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase
performance and reliability over stock Android for your device.
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be
used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps).
CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Before you start
This ROM is only for the E6853 and the E6803
Code:
*
* Your warranty may be voided !
*
* 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.
*
Special Thanks
@CTXz for getting the ball rolling on CyanogenMod for Z5 series and stemming the lion's share to get this working
@oshmoun for providing fixes ASAP
@AndroPlus for providing a great kernel that works with many recoveries
@moonbutt74 for reminding me that smashing your device can provide a solution
@sub77 for teaching me how to work with QCOM (I was on exynos before)
@Joeisgood99 for providing a solid working TWRP-3.0.0.0 build until we had our own
@bazhip for providing a well working twrp 2.8.7.0 for restoring until we had our own
@alphatact1cs has a great overview on lots of topics for the Z5 device family
@auras76 for his great Custom ROM
@infected_ for his experience
Thanks to @mpro420 for help to get Viper4Android working !
Thanks to @jimRnor for Project DiVA SoundMod !
The Sonyxperiadev team for releasing their sources to the public
SonyAOSP team
SonyCM team
Sony Xperia (community) devs
And ofcourse the entire CyanogenMod team!
(Known) Issues
Video Recording
Bluetooth (keeps restarting) (might be fixed, needs feedback + testing)
Camera Colors (can be circumvented by using specific apps CameraNext Mod )
Camera Focus & Sharpness (driver issue, probably since it uses Xperia Z (original) drivers but different lenses ?)
Camera lowlight pictures (might improve with release of Sony's "Experimental AOSP Camera" for the Z5 series, porting of other Framework + Stock Cam app; partially needs DRM magic)
Camera Focus (even with VCM2 actuator changes focus is still kind of murky)
Fingerprint sensor (might work depending on build date of ROM)
Lag after booting up device (Will resolve: lock screen after boot and waiting a few seconds)
Long bootup times & less smoothness with "stock" (prebuilt) kernel
What can not be fixed, changed - aka WONTFIX - NOTOURPROBLEM
There might be potential speed issues with Class 10+ microSD cards not properly being "tuned", in that case switch to slower cards or RMA it which should hopefully solve it. There is a possibility to force slower speeds on cards but that is not really the optimal solution with ultra speed cards and needs further investigation. Samsung (EVO/EVO+) cards, Transcend cards and a few others UHS-I(+) and faster are affected.
What has been Fixed
Horizontal color lines and color glitches during bootup
Gapps
Sudden Lag after some time
NFC
Odd calling numbers
In-call mic
Sound on calls
Camera button
Microphone
Thermal regulation
Red flashy frames
RIL (SIM detection)
Dex pre-optimization
Camera
Sensors
Crash after locking device
microSD access
Flash light / Torch
Full brightness (should be fully working)
Gapps (permissions issues) [occurs occasionally and should be circumvented by full-wipe approach (incl. internal storage)
Hang/Loop during boot stage (should be circumvented by full-wipe approach (incl. internal storage)) (use Custom Kernel, under investigation)
High battery drain [~ 10%-20% per hour] when dirty-flashing system (fastboot -S 256M flash system system.img), make sure to have data backed up, then format /data ; OTA updates should be fine though [need feedback] ); causes are: dirty flashing, certain apps, ROM issues, etc.
Guides/Instructions
Unlocking Bootloader
Warning! The following procedure may void your warranty and will wipe EVERYTHING
Visit Sonys Official Bootloader Unlock guide (Details to all the risks you are taking are located on their site)
After Unlocking your bootloader you can proceed with the next steps
Steps on how to Fastboot, Flashmode, Recovery, Emergency/Force Poweroff
@alphatact1cs has a great overview on lots of topics for the Z5 device family
over at [GUIDE] Sony Xperia Z5 - UNLOCK / ROOT / TWEAKS - OS 5.1.1 / 6.0
There go to the [GUIDE] StockROM section , open it up and under #GENERAL you'll find everything you need to know.
Setting up fastboot and how to use it
For windows users
Please checkout this guide on how to use fastboot on windows
If you prefer to keep a low footprint instead of installing the whole Android SDK, take a look at its thread
[TOOL]Minimal ADB and Fastboot [8-28-15]
For Linux users
Installation
Debian based distros (Debian, Ubuntu etc.)
Open a terminal and enter the following :
Code:
sudo apt-get update && sudo apt-get install android-tools*
Confirm the installation by either hitting enter or typing y
Gentoo based Distros (Gentoo, Funtoo, Sabayon, Scientific Linux)
Once you're in a terminal, enter the following:
Code:
emerge dev-util/android-sdk-update-manager
Other distros (Arch, Fedora, Open Suse etc.)
Please find the apropriate packages to install android fastboot tools for your distro
How to use
Open a terminal in the location your .img file is located or cd into that directory like this:
Code:
cd <path to your directory that contains the .img files>
Replace <path to your directory that contains the .img files> with your actuall path
To boot temporarely into a .img (ex recovery) use the following command (replace <your.img> with your .img file) :
Code:
fastboot boot <yourfile>.img
To flash a kernel image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash boot <your.img>
To flash a recovery image enter the following (replace <your.img> with your .img file):
Code:
fastboot flash recovery <your.img>
To exit fastboot enter :
Code:
fastboot reboot
How to install CM 13
Above all - do a Backup of ALL your data
When I write ALL I mean ALL (this includes the data on your micro SD card,
don't come whining to me if you lose your wedding photos/videos, kids' photos/videos or other important stuff !
For optimal experience I'd recommend my built custom kernel (quicker boot times, higher reliability, more tweakability)
General, in-depth instructions (for the Xperia Z5 !)
Download one of the newer Z5 AndroPlusKernels v20+ by @AndroPlus from his official website (Scroll down and select Z5, then on AndroidFileHost search for Z5_AndroPlusKernel_Permissive_v2 (v20 - v23) and download it)
Extract the flashable zip-file e.g. Z5_AndroPlusKernel_Permissive_v23.zip
Download our TWRP 3.0.1-0 build for the Z5)
Download the appropriate gapps from below (Can be downloaded on your device)
Download the CM 13 Zip for the Z5 from below (Can be downloaded on your device)
Move the GAPPS zip and the CM 13 to your Z5 if you haven't downloaded them on your device
Power Off your Z5 and wait about 10-15 seconds to make sure it's off
To enter fastboot mode hold VOL UP and while holding VOL UP connect your device to your pc via cable
When the notification LED has turned blue you are in fastboot mode
On your PC flash the boot.img that has been extracted from the Z5_AndroPlusKernel_Permissive_v23.zip using fastboot (
Code:
fastboot flash boot boot.img
)
Now flash twrp-3.0.1-0-E6653-20160403.img by using fastboot (
Code:
fastboot flash recovery twrp-3.0.1-0-E6653-20160403.img
)
Once both of those images have been flashed you can reboot the device like so:
Code:
fastboot reboot
Quickly pull the usb cable from the computer (you can leave the other end in the phone's port)
When booting up wait for the notification light to turn yellow at the Sony logo
Once it has turned yellow, you will enter TWRP by pressing VOL UP (or VOL DOWN - up works more reliably)
If you've missed the step above, reboot your device and try the step above again
Alternatively you can force turn off the device via: Power Button + Volume Up , then turn it on again via Power Button
If TWRP asks you to enable read and write, swipe to continue
Go to settings and lower the max brightness to the minimum or one of the lower levels to preserve energy
In TWRP make a full backup to the microSD in case you want to revert back to stock.
After it has finished, in this case Reboot -> System.
Copy over the TWRP folder from the external microSD to your computer (reason: you might not have access to your external SD or have to reformat it
Thank Microsoft, Sony, etc. for that: "Stock" ROM uses texfat , AOSP, CM, etc. uses exfat, ext4, ntfs
The files on the microSD might get corrupted (filesystem problem) or the microSD going crazy (I already had both cases)
Now Power on your phone and follow the steps again to get into TWRP
Swipe to continue (?)
select Wipe > Advanced Wipe
Now ONLY tick Dalvik/ART cache, System, Cache and Data
WARNING! THE NEXT STEP WILL WIPE YOUR SYSTEM AND DATA, MEANING YOU WILL DELETE YOUR STOCK SONY SYSTEM AND ALL YOUR APPS
(You already DID a Backup of your files so nothing to worry about)
Once you've ticked the correct boxes, swipe to wipe
Once the wipe is complete, return to the main menu and select Install
Locate and select your CM 13 Zip
Select "Add more Zips" and add your GAPPS package and finally swipe to install
Once the installation succeeded you can select "Reboot System"
Wait for CM 13 to boot up (Can take several minutes)
Enjoy CM13
OPTIONAL: You can remove your TWRP backup that is located in the TWRP folder if you feel like you will no longer need it
How to ROOT
In CM 13, enable the developer options
Select Root access
Select Apps Only (Or Apps and ADB if you use ADB)
Done
How to disable the Thermal Manager
Before we start I want to set a few questions and warnings. Disabling the thermal manager will cause you device to run slightly hotter, do this at your own risk.
Let's start out with why you would want to disable the thermal manager. At this point it's not recommended to disable the thermal manager as it has been fixed. However some people still want the max performance out of their device. The average heat without the thermal manager will be roughly the same, if not less compared to the stock ROM with it's thermal manager enabled.
So why is the thermal manager even included if it the device runs mostly fine without it. As most of you already know, the Snapdragon 810 (MSM8994) has overheating problems. The first CM boot after flash is responsible for optimizing apps and android and can become extremely resource hungry at that point. Due to that, the device can heat tremendously! Not only can that cause a panic reboot but it can also damage your device in rare cases. To avoid that issue a thermal manager shrinks down process and slowers the boot animation (That's why the CM logo may lag at first boot).
Enough said, let's get going..
To disable the thermal manager you must do the following :
First enable root access (See "How to ROOT" guide)
Open the CM file manager
Go to settings > General Settings > Access Mode
Select root acess mode
Go back to the file manager
Swipe from left to right or press the menu button in the upper left corner
Select Root folder
Open the folder/directory called etc
Delete thermanger.xml
Reboot
Done
How return back to stock via TWRP backup
Reboot your device
Wait for the notification light to turn purple at the Sony logo
Once it has turned purple, you will enter TWRP by pressing VOL UP or VOL DOWN
If you've missed the step above reboot and try again
If TWRP will ask you to enable read and write, swipe to continue
In TWRP select restore and select your backup, then swipe to restore
Once the restore is done you can select "Reboot System"
If your device hangs at the Sony wave boot animation, force shut down and power your device up again.
Downloads
Latest recommended CyanogenMod release for the Sony Xperia Z5 E6853/E6803 :
6.0.1_13.0-20160627-UNOFFICIAL-satsuki_r46_alternate
Latest recommended Kernel for the CM release for the Sony Xperia Z5 E6853/E6803 :
6.0.1_13.0-20160627-UNOFFICIAL-satsuki_r46_alternate
All my releases can be found here on : Android File Host
TWRP for CM/AOSP-based ROMs:
E68XX_TWRP3_SD_recovery.img
Gapps (Select ARM64 > 6.0) :
Open Gapps
[GAPPS][6.0/5.1/5.0][arm/arm64] Official Slim GApps ( recommended )
XPosed for Android:
[OFFICIAL] Xposed for Lollipop/Marshmallow (Installer in Thread)
XPosed Releases
SuperSU in SystemMode:
SuperSU in System-Mode [v2.65-STABLE] [v2.68-BETA] [v2.70-WIP/BETA-RC]
Sound MODs:
[Sound Mod ][Project DiVA][6.0 MM_Z5 series] KitaKami sound mod Prototype 01 (any effect ?)
A.R.I.S.E. Sound Systems - Auditory Research in Sound Enhancement - Exodus RC8.3 (works (RC8.3))
[SOUNDMOD][JB/KK/LP/MM]Project Yume Final, You are the Legend (needs testing)
[SUPER MOD][4.4+/6.0/N][ v7.5.2 ] XTREMEMusic™ THE SOUND THAT YOU'VE NEVER HEARD! (NOT working (7.4), needs testing of 7.5*
[Audio Mod] eXtremeBeats Aural Maximizer (needs testing)
[APP]Material ViPER4Android 2.4.0.1[Light/Dark][LP/MM]
mpro420 said:
1.)zip file install via twrp.
2.)reboot to system.
3.)enable v4a "write to sdcard" permission in setting/apps/viper4android/permission.
4.)open v4a and gain root permission.
5.)install driver for v4a.
6.)reboot system.
7.)[emoji39]
Click to expand...
Click to collapse
Questions and bug reporting
The following questions will be ignored
Inappropriate questions
Requests for other devices
Forced orders, EX. : "PLS FIX!!!!!!"
ETA's
Often repeated questions or requests usually by the same user
Requests that are out of CM's framework (Ex. Adding Sony Apps)
How to report a bug/issue
Explain exactly what happens
Mention a log if you can (Please use hastebin or any other paste site to keep the thread clean)
If you can't mention a log, explain as precise as possible when, why and where it occurs!
Source Code
All Source Code can be obtained from:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
Kernel Source code can be obtained from : zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
We gladly accept any developers that are willing to contribute to this project! Please PM @CTXz if you are interested in joining this project!
Build from Source
http://forum.xda-developers.com/xperia-z5/general/guide-build-cm13-source-z5-z5c-z5p-t3357040
Screen Shots (Z5 compact)
XDA:DevDB Information
CyanogenMod 13 for the Sony Xperia Z5 E6853 and E6803, ROM for the Sony Xperia Z5 Premium
Contributors
CTXz, Moonbutt74 , zacharias.maladroit , oshmoun , infected_
Source Code:
https://github.com/Sony-Kitakami
https://github.com/SonyAosp
https://github.com/sonyxperiadev
https://github.com/CyanogenMod
https://github.com/zachariasmaladroit/android_kernel_sony_msm8994_kitakami_r2
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: 6.0 Recommended
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2016-04-11
Last Updated 2016-06-28
one
two
three
Previous ("legacy") threads,
by moonbutt74:
CM13 Z5P E6853 Beta -- Updated NegaSpork
[Rootable Kernel/ TWRP 3 - E6833/E6853/E6883 Marshsmellow ] [32.1.A.1.163] AU]
ok running cm13 on my 6385 and ran it for 5 mins and very happy will see about battery drain later hope there is very little, i have tried the cameras and they both show a blue picture any ideas?
dominicstg2 said:
ok running cm13 on my 6385 and ran it for 5 mins and very happy will see about battery drain later hope there is very little, i have tried the cameras and they both show a blue picture any ideas?
Click to expand...
Click to collapse
there is very little battery drain compared to Sony Stock ROMs,
It's a limitation in the preview of the camera, you tried to take a picture ? That also isn't very great but better
Use Camera Next Mod ( https://www.androidfilehost.com/?w=files&flid=53956 ) for improvement,
until Alin releases calibrated firmware blobs for the cam the picture will be non-focused and/or blurry for objects farer away than 60 cm
@dominicstg2 Weren't you one of those RR (Resurrection Remix) lovers ?
zacharias.maladroit said:
there is very little battery drain compared to Sony Stock ROMs,
It's a limitation in the preview of the camera, you tried to take a picture ? That also isn't very great but better
Use Camera Next Mod ( https://www.androidfilehost.com/?w=files&flid=53956 ) for improvement,
until Alin releases calibrated firmware blobs for the cam the picture will be non-focused and/or blurry for objects farer away than 60 cm
@dominicstg2 Weren't you one of those RR (Resurrection Remix) lovers ?
Click to expand...
Click to collapse
yes i was one who used the rr also i cant flash the rom on 6.0,1 was coming from stock, tried wiped everything and didnt work it said rom is for our device but said my device is . i had to flash android l to flash the rom any idea? not abig deal because im rocking cm13 also i dont see a drain at all on stock over night would see 5% drop on cm13 not a single % dropped and on rr when i used camera next mod the photo would be fine but on cm13 the camera is still blue when i take a picture? also im very happy that mms works and data its basically daily drivable for me
dominicstg2 said:
yes i was one who used the rr also i cant flash the rom on 6.0,1 was coming from stock, tried wiped everything and didnt work it said rom is for our device but said my device is . i had to flash android l to flash the rom any idea? not abig deal because im rocking cm13 also i dont see a drain at all on stock over night would see 5% drop on cm13 not a single % dropped and on rr when i used camera next mod the photo would be fine but on cm13 the camera is still blue when i take a picture? also im very happy that mms works and data its basically daily drivable for me
Click to expand...
Click to collapse
Was that when I uploaded the first build of RR ?
Cause I hope that this time you have more luck with it and it works:
http://forum.xda-developers.com/showpost.php?p=67538514&postcount=45
Is the taken picture now fine with Camera Next Mod and CM13 ?
Both RR and CM13 now should be pretty close, please give RR another try
Thanks
yes i think it was if not the second build , whats more stable rr or cm13? i had some issues with rr ie 4g didnt alway connect nor did 3g and no the photo is still blue on camera next mod on cm13 and sure il will download it now also can you explain why when i was onn 6.0.1 i couldnt flash cm13 nor rr? it would say its for our device but my device is . and i would have to go back to 6.0 to flash?
zacharias.maladroit said:
Was that when I uploaded the first build of RR ?
Cause I hope that this time you have more luck with it and it works:
http://forum.xda-developers.com/showpost.php?p=67538514&postcount=45
Is the taken picture now fine with Camera Next Mod and CM13 ?
Both RR and CM13 now should be pretty close, please give RR another try
Thanks
Click to expand...
Click to collapse
dominicstg2 said:
yes i think it was if not the second build , whats more stable rr or cm13? i had some issues with rr ie 4g didnt alway connect nor did 3g and no the photo is still blue on camera next mod on cm13 and sure il will download it now also can you explain why when i was onn 6.0.1 i couldnt flash cm13 nor rr? it would say its for our device but my device is . and i would have to go back to 6.0 to flash?
Click to expand...
Click to collapse
It's related to the device string that is in the zip-file of the ROM,
if that doesn't match TWRP, it can not be flashed, unless you modify the zip-file to remove that line.
That mismatch can be made in error (something went wrong during creation, typo, etc.)
or on purpose - in that case it's not so wise to flash the wrong ROM
Oh has other people had this problem?
zacharias.maladroit said:
It's related to the device string that is in the zip-file of the ROM,
if that doesn't match TWRP, it can not be flashed, unless you modify the zip-file to remove that line.
That mismatch can be made in error (something went wrong during creation, typo, etc.)
or on purpose - in that case it's not so wise to flash the wrong ROM
Click to expand...
Click to collapse
dominicstg2 said:
Oh has other people had this problem?
Click to expand...
Click to collapse
yeah, not sure if on Z5 compact,
but certainly on Z5 Premium and Z5
waitting for 6883 ^_^
Thanks Dev.
I join the testing!
Changelog
12.07.2016 == stable/testing/UNOFFICIAL update build
upstream ROM changes 6.0.1_r56 (Android security Patchlevel: 2016-07-01 / 2016-07-05)
ADB enabled by default for better error diagnosis, ADB over WiFi disabled
fingerprint scanner might work
NFC should work again
single SIM ONLY
.
other changes: YOU tell me
.
previous custom kernel (if used) should still work + NFC too, if you encounter issues with NFC please let me know
Click to expand...
Click to collapse
Kernel Source:
https://github.com/zachariasmaladro...mi_r2/commits/Sun-Kernel_cm-13.0_III.1_5_3_cm
ROM Source:
mostly
https://github.com/SonyAosp/
https://github.com/Sony-Kitakami/
https://github.com/sonyxperiadev/
Kernel
Z5P_Sunkernel_Permissive_v13_III.1_5_3.zip
ROM
6.0.1_13.0-20160712-UNOFFICIAL-satsuki_r56
Thanks
zacharias.maladroit said:
Changelog
Kernel Source:
https://github.com/zachariasmaladro...mi_r2/commits/Sun-Kernel_cm-13.0_III.1_5_3_cm
ROM Source:
mostly
https://github.com/SonyAosp/
https://github.com/Sony-Kitakami/
https://github.com/sonyxperiadev/
Kernel
Z5P_Sunkernel_Permissive_v13_III.1_5_3.zip
ROM
6.0.1_13.0-20160712-UNOFFICIAL-satsuki_r56
Thanks
Click to expand...
Click to collapse
Hi Dev ^_^
about version cm13 for Z5P E6883, When will be released ?
Tani_bc said:
Hi Dev ^_^
about version cm13 for Z5P E6883, When will be released ?
Click to expand...
Click to collapse
Don't ask for ETAs on XDA. It is rude.
Sent from my SGP311 using XDA Labs
Tani_bc said:
Hi Dev ^_^
about version cm13 for Z5P E6883, When will be released ?
Click to expand...
Click to collapse
Work in progress,
please take a look at the CM13 thread for the Z5, will ya ?
there are several factors that influence access and working for
microSD, sim cards (both), fingerprint scanner and others
Hi. Just curious, is it possible if I use this on E6883 (Z5 Premium Dual) and flash Dual Enabler thereafter?
LineageOS is a free, community built, aftermarket firmware distribution of Android 7.1 (Nougat), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. Lineage OS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
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.
Compatible device?:
Code:
[LIST]
[*]P8 Lite 2017.
[*]P10 Lite.
[/LIST]
Mandatory:
* hit thank buttons, it's free.
* want more roms for P8 Lite 2017/P9 Lite 2017, simply bring me up beers by the following button.
Requirements:
Unlocked bootloader.
Unlocked FRP.
vendor.img: you must be on stock one, so don't wipe it because with other custom vendor.img will never ever boot.
Emui 5.x B115 (Single Sim) or B170(Dual Sim)
How to Install the ROM?
* reboot to TWRP.
* go to Wipe -> Advanced Wipe.
* check Data -> Change file system -> select EXT4.
* swipe the screen to wipe it .
How can I fix Sim?
* go to Settings -> Extras -> disable "Sim Card Slot2 " and reboot.
How can I enable Google Codecs
* go to Settings -> Extras -> enable "Use Google H264" (it's a bit laggy but better than nothing).
How to enable Double Touch To Wake?
* go to Settings -> Extras -> enable "Double Touch to Wake"
Should I reflash the vendor partition if come from other roms?
* if you coming from Emui 5.x, the answer is no because the custom rom are based on Emui 5.0 source code, so all you
have to is flashing your favorite custom rom
Audio and camera are not working?
* bring up a logcat to help us, instead of writing useless comments.
Gapps:
http://opengapps.org
Working Hardware:
Audio.
Bluetooth.
Browser.
Display.
GPS.
Graphics: only gralloc.
Lights.
RIL.
Sensors.
Storage: both internal & external storage.
Wifi.
Bugs:
Tell me
LineageOS 14.1:
Downloads:
Checkout this
LineageOS 14.1 Downloads
Changelogs:
30/07/2017:
Initial build.
03/08/2017:
Testing hwcomposer, report us if the build boot and run games fine.
Camera will be fixed soon.
21/08/2017:
fix random reboot.
fix some tethering issues.
wifi should be fixed (send me a logcat if not work) it was working on my own pra-lx1..
25/08/2017:
fix sim.
fix hwcomposer (in theory, you should test games for that).
fix wifi..
01/09/2017:
ril has beeb fixed by disable flags for dual sim, my device is single sim.
fix wifi (will try to fix saving password issue).
01/09/2017:
Android 7.1.2 R29.
fix bootloop.
fix random reboot.
to fix lags: disable Ambient Display from Display settings.
15/11/2017:
update HwComposer according to this patch.
Update permissions for Google Play.
Build is smooth and fast even with enabled ambient display
21/12/2017:
fix minor bugs
31/12/2017:
fix camera
06/01/2018:
fix USB & memories.
21/01/2018:
Fix error 7 by adding support for prague devices, so you must flash my latest twrp, the v2.5.
Fix ril on prague devices.
Fix ril crashes, I test the automated voice of ussd code for more than 30 seconds and didn't crash like before.
Note: this rom is only for the Huawei P8 Lite 2017 if you didn't get worked audio or camera on your hi6250 device isn't my fault, just flash my own vendor.img from unbrick guide, that's why I get everything works on my pra-lx1 like the following attached screenshot.
25/01/2018:
Fix audio for P10 Lite
Add support for Vulkan libraries for all hi6250.
Fix camera on some prague devices.
31/01/2018:
Fix Magisk 15.3
Security patches: January 2018
19/02/2018:
security patches: Feb 2018
02/05/2018:
fix call's sensor issue.
latest android 7.1.2 build.
28/12/2019:
Fix Magisk
Fix RIL crash.
Security Patches: 5 Dec 2019
11/06/2020:
New "Extra" thanks to dady8889 for the base (I'll clean up tomorrow)
Fix Mute in Call.
SPL: May 2020
13/06/2020:
Fix Mute in Call.
Fix USSD. (thanks to flex1911 for his emui8 fixes)
Fix RIL Crash again.
[/HIDE]
Source Code:
Device Tree:
https://github.com/hak86/android_device_huawei_hi6250
Kernel GPL:
https://github.com/hak86/android_kernel_huawei_prague
Vendors:
https://github.com/hak86/android_vendor_huawei_hi6250
Credits
@haky 86
@Meticulus special thanks for immense work done in just few days for the hi6250 platform.
Contributors
@haky 86
Source Code: https://github.com/hak86
ROM Kernel: Linux 4.1.x
ROM Firmware Required: EMUI 5.0 or newer
Version Information
Status: Beta
Beta Release Date: 2017-07-30
Created 2017-07-30
Last Updated 2017-12-21
Reserved
ROM stuck at animation boot?
this because you must change the file system from F2FS to EXT4 to done boot process
* reboot to TWRP.
* go to Wipe -> Advanced Wipe.
* check Data -> Change file system -> select EXT4.
* swipe the screen to wipe it .
How can I fix Sim?
* go to Settings -> Extras -> disable "Sim Card Slot2 " and reboot.
How can I enable Google Codecs
* go to Settings -> Extras -> enable "Use Google H264" (it's a bit laggy but better than nothing).
How to enable Double Touch To Wake?
* go to Settings -> Extras -> enable "Double Touch to Wake"
Should I reflash the vendor partition if come from other roms?
* if you coming from Emui 5.x, the answer is no because the custom rom are based on Emui 5.0 source code, so all you
have to is flashing your favorite custom rom
Audio and camera are not working?
* bring up a logcat to help us, instead of writing useless comments.
I got error 7, how can I fix that?
* use my own TWRP recovery. or you can simply remove the whole assert line in the updater-script file inside the META-INF folder save and re-flash.
How can I fix RIL Crashes
flash root.
Copy the phone.prop into /system/vendor and /vendor.
reboot, now you should able to do calls for more than 2 minuts
Calls still crash even with fix SIM
Run adb shell and type the following command xxd /sys/firmware/devicetree/base/hisi,modem_id .
the result will be something like the following out ( for single sim devices):
1|hi6250:/ $ xxd /sys/firmware/devicetree/base/hisi,modem_id
00000000: xxxx x000 ;xx.
Click to expand...
Click to collapse
Search for your xxxxx000, and setup the following flags .
ro.config.client_number=1
ro.config.modem_number=1
persist.dsds.enabled=false
persist.radio.multisim.config=dsds (remove it properly)
for dual sim devices just edit these 2 flags:
ro.config.client_number=1
ro.config.modem_number=1
Save and reboot.
Oh, finally you did it
You can easy fix deep-sleep issue if you'll apply @XePeleato' patch for surfaceflinger , please take a look here , credit goes to @XePeleato !
Second, you can also easly fix the "reboot to erecovery" issue, by applaying my patch for kernel, you should take a look here as well !
I assume Hotspot isn't working, because you need more patches to kernel ... so you can cherry-pick almost all my commits, but as always you should keep authorship, as much as possible
About camera ?? - you can't enable camera so easy ... I'll let you to try , and if you do not succeed in a week, please let me to know and I'll help you
Good luck !
surdu_petru said:
Oh, finally you did it
You can easy fix deep-sleep issue if you'll apply @XePeleato' patch for surfaceflinger , please take a look here , credit goes to @XePeleato !
Second, you can also easly fix the "reboot to erecovery" issue, by applaying my patch for kernel, you should take a look here as well !
I assume Hotspot isn't working, because you need more patches to kernel ... so you can cherry-pick almost all my commits, but as always you should keep authorship, as much as possible
About camera ?? - you can't enable camera so easy ... I'll let you to try , and if you do not succeed in a week, please let me to know and I'll help you
Good luck !
Click to expand...
Click to collapse
Sure bro
I'm make a build right now with that patch, for camera I don't see USE_CAMERA_STUB := true in BoardConfig.mk and also my kernel source has 34 repos for external, are they useful? will do a test with them and report you..the rest are perfect
Installed, testing. No reboots so far.
Dejan Kruljac said:
Installed, testing. No reboots so far.
Click to expand...
Click to collapse
just wait and see..fixing are in progress..will be in nex builds. btw
This works on the P9 Lite 2017 too. The devices have the same hardware, I think even the same Model No. Just wanted to point that out.
Hi,
We have a P8 Lite 2017 and i have install LineageOS...
I have different problem.
The first problem is no sim accept. ( i have two sim in the phone but the Software marked "No sim"...
The second problem is when i shutdown P8 and stard after few minutes, the P8 doesnt start ( P8 blocked on the Logo Lineage OS).
You can help me ??
Thanks
maxilib said:
Hi,
We have a P8 Lite 2017 and i have install LineageOS...
I have different problem.
The first problem is no sim accept. ( i have two sim in the phone but the Software marked "No sim"...
The second problem is when i shutdown P8 and stard after few minutes, the P8 doesnt start ( P8 blocked on the Logo Lineage OS).
You can help me ??
Thanks
Click to expand...
Click to collapse
For sim I can't help you because my device is single sim.
for shutdown/random reboot, I already fix that problem, will be available in the second builld once fix nfc
haky 86 said:
For sim I can't help you because my device is single sim.
for shutdown/random reboot, I already fix that problem, will be available in the second builld once fix nfc
Click to expand...
Click to collapse
Thanks for your reply
I'v tested you version later. But for the SIM, any SIM is recognize in the system ! ( French SIM operator Orange)
I flashed the vendor, did a factory reset in twrp and wiped system, flashed rom zip and opengapps arm64 7.1 pico. it looped on a Lineage logo for 10 minutes. Do i need to format data partition? or factory reset is enough
aciupapa said:
I flashed the vendor, did a factory reset in twrp and wiped system, flashed rom zip and opengapps arm64 7.1 pico. it looped on a Lineage logo for 10 minutes. Do i need to format data partition? or factory reset is enough
Click to expand...
Click to collapse
Data needs to be wiped too everytime you flash a completely new ROM
Vinnipinni said:
Data needs to be wiped too everytime you flash a completely new ROM
Click to expand...
Click to collapse
so, factory reset from twrp is not enough and i need to choose "format data", the option above twrp slider yep?
aciupapa said:
so, factory reset from twrp is not enough and i need to choose "format data", the option above twrp slider yep?
Click to expand...
Click to collapse
Yes.
Vinnipinni said:
Yes.
Click to expand...
Click to collapse
OK, thanks. I'll back everything up and wait for next build
aciupapa said:
OK, thanks. I'll back everything up and wait for next build
Click to expand...
Click to collapse
Yeah. Just keep in mind that you cannot backup data at all. Only the Internal space with your PC. But always make backups of other stuff and keep at least one on your PC, so if something breaks, you can always go back. Data isn't that important to safe, if you wiped data, it's like a factory reset.
Please read the OP, of course you'll need to wipe data, cache, system.
haky 86 said:
Please read the OP, of course you'll need to wipe data, cache, system.
Click to expand...
Click to collapse
did that. still hangs on lineage bootanimation, waited for 10 mins or so
I don't quite understand how to patch the surfaceflinger. Can someone tell me what am I supposed to do?
First my respect. I also tried it. But I failed. Is not bad, there are experts like @haky 86. Great work, thank you.
When I tested the version for the 6x in the morning, I had to format between the data partition and re-install the EMUI. Since then your TWRP works perfectly. Complete backups include Data Partition. Restoring is also perfect. Tomorrow I want to try your Lineage OS. Hope the Revovery works there perfectly synonymous.
Paranoid Android is a custom ROM aiming to extend the system, working on enhancing the already existing beauty of Android and following the same design philosophies that were set forward by Google for Android Open Source Project.
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.
Compatible device?:
Code:
[LIST]
[*]All devices that use hi6250 chipset and use kernel 4.1.
[/LIST]
Mandatory:
* hit thank buttons, it's free.
* want more roms for P8 Lite 2017/P9 Lite 2017, simply bring me up beers by the following button.
Requirements:
TWRP.
Unlocked bootloader.
Unlocked FRP.
vendor.img: you must be on stock one, so don't wipe it because with other custom vendor.img will never ever boot.
This ROM is provided by CodeOfHonor
Installation Guide:
Make sure to the stock backup saved on pc, I'm not responsible for any bricked or damage.
Reboot to TWRP.
Go to Wipe.
Choose Advance Wipe.
Check on Data and change file system to EXT4, will not ever boot with F2FS.
Wipe cache, data, dalvik and system.
Flash the rom.
Reboot and have fun then.
Working:
Audio.
Bluetooth.
Camera: it's fully works with stock or other apps .
Display.
Graphis: both gralloc & hwcomposer.
Lights.
NFC.
RIL.
Sensors.
Storages.
Wifi
Bugs:
Dual sim might will not work all variants, so don't waste your time by asking me to fix it.
You don't like it?, easy revert to Emui 5.x.
Downloads:
**13/05/2018**
pa_hi6250-7.3.1-EOL-20180513.zip|500.4 MB
Changelogs:
**13/05/2018**
Boot with F2FS without problems.
Fix Magisk.
Source Code:
Device Tree:
https://github.com/codeofhonor-dev/android_device_huawei_hi6250
Kernel GPL:
https://github.com/codeofhonor-dev/android_kernel_huawei_hi6250
Vendors:
https://github.com/codeofhonor-dev/android_vendor_huawei_hi6250
XDA:DevDB Information
AOSPA Paranoid for Hi6250, ROM for the Honor 6X
Contributors
haky 86, HassanMirza01, felix-development
Source Code: https://github.com/codeofhonor-dev, Meticulus and the stuff of CodeOfHonor.
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 4.x
ROM Firmware Required: Emiui 5.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: 7.3.1
Stable Release Date: 2018-04-27
Beta Release Date: 2018-04-27
Created 2018-04-27
Last Updated 2018-04-27
ROM stuck at animation boot?
this because you must change the file system from F2FS to EXT4 to done boot process
* reboot to TWRP.
* go to Wipe -> Advanced Wipe.
* check Data -> Change file system -> select EXT4.
* swipe the screen to wipe it .
How can I fix Sim?
* go to Settings -> Extras -> disable "Sim Card Slot2 " and reboot.
How can I enable Google Codecs
* go to Settings -> Extras -> enable "Use Google H264" (it's a bit laggy but better than nothing).
How to enable Double Touch To Wake?
* go to Settings -> Extras -> enable "Double Touch to Wake"
Should I reflash the vendor partition if come from other roms?
* if you coming from Emui 5.x, the answer is no because the custom rom are based on Emui 5.0 source code, so all you
have to is flashing your favorite custom rom
Audio and camera are not working?
* bring up a logcat to help us, instead of writing useless comments.
I got error 7, how can I fix that?
* use my own TWRP recovery. or you can simply remove the whole assert line in the updater-script file inside the META-INF folder save and re-flash.
How can I fix RIL Crashes
flash root.
Copy the phone.prop into /system/vendor and /vendor.
reboot, now you should able to do calls for more than 2 minuts
Calls still crash even with fix SIM
Run adb shell and type the following command xxd /sys/firmware/devicetree/base/hisi,modem_id .
the result will be something like the following out ( for single sim devices):
1|hi6250:/ $ xxd /sys/firmware/devicetree/base/hisi,modem_id
00000000: xxxx x000 ;xx.
Click to expand...
Click to collapse
Search for your xxxxx000, and setup the following flags .
ro.config.client_number=1
ro.config.modem_number=1
persist.dsds.enabled=false
persist.radio.multisim.config=dsds (remove it properly)
for dual sim devices just edit these 2 flags:
ro.config.client_number=1
ro.config.modem_number=1
Save and reboot.
I'm coming from EliteRom 7.5 and I love AOSPA but there are 2 little problems I have with this rom.
First of all fingerprint doesn't work correctly, no matter how often I press my finger on the sensor it stays at the ~10% mark.
The other problem is that I don't know how to root this rom. I tried installing magisk manager and flashing the zip but I get error 1 in TWRP.
Except this issues it's working very nicely on my device.
Thanks in advance for helping me out
MadMurl0c said:
I'm coming from EliteRom 7.5 and I love AOSPA but there are 2 little problems I have with this rom.
First of all fingerprint doesn't work correctly, no matter how often I press my finger on the sensor it stays at the ~10% mark.
The other problem is that I don't know how to root this rom. I tried installing magisk manager and flashing the zip but I get error 1 in TWRP.
Except this issues it's working very nicely on my device.
Thanks in advance for helping me out
Click to expand...
Click to collapse
10% mark?
Did you entirely remove all the fingerprints before flashing this Tom?
Go back to Elite or Stock, remove all fingerprints and reinstall the Rom
For Root, you can try changing recovery or using an older version of Magisk that worked for you
I am currently reverting back to stock and will try to flash the rom again, I guess I didn't remove the fingerprints before flashing.
I tried Magisk Version 15 and 16 which both worked on EliteRom, I even tried SuperSu which didn't gave me an error message in twrp but It didn't work tho. After flashing the zip there was no "SuperSu" App so I downloaded it from the playstore, the app told me "root not found". Do you know what the cause of this could be?
Edit: Fingerprints are working now But root still doesn't
After I downgrade from emui 8 to emui 5 in 5 minutes now I can fix this rom so expect a build within these days
hoping to try this rom , following for updates
Hey guys I just installed the rom, but I did notice that I don't have access to any Gapps. How to I install them? I'm using TWRP. I was just able to get my unlock code from Honor today, so I unlocked and rooted, and flashed your rom as the first thing, so I'm running a fresh flash of the latest version.
Flash package with Twrp: https://opengapps.org/
Thanks guys, I realized that yesterday right after I posted lol. So far I'm really loving the plain stock-ness of this rom, hopefully it give the device some more life so I won't have to upgrade soon.
MadMurl0c said:
I am currently reverting back to stock and will try to flash the rom again, I guess I didn't remove the fingerprints before flashing.
I tried Magisk Version 15 and 16 which both worked on EliteRom, I even tried SuperSu which didn't gave me an error message in twrp but It didn't work tho. After flashing the zip there was no "SuperSu" App so I downloaded it from the playstore, the app told me "root not found". Do you know what the cause of this could be?
Edit: Fingerprints are working now But root still doesn't
Click to expand...
Click to collapse
Yeah I'm having the same issue to, with no root.
Can someone tell me why this rom is different to all others ? Why is this one using stock vendor and can we easy revert to Emui ? Why don't all others ?
I'm on stock now.
How is the quality of the photos compared to stock rom? It is possible to install Emui camera or other huawei cameras?
** Note **
developments of hi6250 is end reason: switch to another phone, have phone.
** Note **
Developments for hi6250 has been resumed but just for this ROM, sorry for the inconvenience.
I'm already downloading the source for releasing new build but AOSPA will take a wile since have bigger source.
** Note **
Downloads:
**13/05/2018**
pa_hi6250-7.3.1-EOL-20180513.zip|500.4 MB
Changelogs:
**13/05/2018**
Boot with F2FS without problems.
Fix Magisk.
Had anyone tried installing Xposed yet?
Support BLL version? Honor 6X
The rom overall is great and smoorh, even F2FS works now
But somehow magisk still doesn't work. It says
Code:
! System installed root detected, mount rw :(
when I try to flash the magisk.zip file.
MadMurl0c said:
The rom overall is great and smoorh, even F2FS works now
But somehow magisk still doesn't work. It says
Code:
! System installed root detected, mount rw :(
when I try to flash the magisk.zip file.
Click to expand...
Click to collapse
Guys to flash magisk or superSU use Meticulus TWRP, other twrp like eliteTwrp show an error when it is recompilling the boot.img
{
"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.
*/
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.
What works:
Calls/SMS/Mobile data
Wifi
Bluetooth
GPS
Camera (Photo/Video/Flashlight/HAL3)
Audio
Fingerprint sensor
DT2W
Keydisabler
Notification LED
Torchlight
NFC
Broken
You tell me
Source code:
device tree: https://github.com/HighwayStar/android_device_nubia_nx549j
device-common: https://github.com/HighwayStar/android_device_nubia_msm8953-common
kernel: https://github.com/HighwayStar/android_kernel_nubia_msm8953
vendor: https://github.com/HighwayStar/android_vendor_nubia
Clean code with kernel rebased on top of latest caf oreo msm8953 tag.
Download
2018-10-21
Updated kernel
Update Lineage code
mailru: lineage-15.1-20181021-UNOFFICIAL-nx549j.zip
gdrive: lineage-15.1-20181021-UNOFFICIAL-nx549j.zip
Previous versions:
2018-10-03
Added ability to power on device when alarm set
mailru: lineage-15.1-20181003-UNOFFICIAL-nx549j.zip
gdrive: lineage-15.1-20181003-UNOFFICIAL-nx549j.zip
2018-10-02
Added FM radio
Ambient display (power on display on notification recieved)
mailru: lineage-15.1-20181001-UNOFFICIAL-nx549j.zip
gdrive: lineage-15.1-20181001-UNOFFICIAL-nx549j.zip
2018-09-25
Updated audio configs
Added sepolicy rules,selinux in enforcing mode now
Added stock thermal config
Fixed LiveDisplay
mailru: lineage-15.1-20180925-UNOFFICIAL-nx549j.zip
gdrive: lineage-15.1-20180925-UNOFFICIAL-nx549j.zip
2018-09-16
Added exfat sdcard support
Updated mount option for /data partition. It should provide more performance and longer flash ROM live.
Fixed calls recording.
Added missing perfromance profiles config file (powerhint.xml). This should result in better powersave when idle and better performance on demanding tasks.
Made LED config same as was in 14.1.
Default screen brightness set to match stock rom (lower than was in previous version).
Added kernel config options recommended for oreo builds. Now battery stats should calc better apps use. Added BFQ IO scheduler.
mailru: lineage-15.1-20180916-UNOFFICIAL-nx549j.zip
gdrive: lineage-15.1-20180916-UNOFFICIAL-nx549j.zip
2018-09-15
* Initial release
gdrive: lineage-15.1-20180915-UNOFFICIAL-nx549j.zip
mailru: lineage-15.1-20180915-UNOFFICIAL-nx549j.zip
To install this you have to install TWRP first. I can recommend this version, built with same kernel as ROM. nx549-twrp-3.2.1.img
If you want to use google apps use ARM64 Android 8.1 opengapps package https://opengapps.org/.
If you need root use Lineage addonsu or Magisk
This rom supports Google camera mods. You can get HDR+ working with one of version from here https://www.celsoazevedo.com/files/android/google-camera/ One of known working version is MGC_5.1.018.177624777-41364271.apk. to make HDR+ avaliable you have to select model Nexus 6P in settings and restart app (this means swipe it from recent apps or reboot).
XDA:DevDB Information
[ROM][UNOFFICIAL][8.1.0][nx549j] LineageOS 15.1 for Nubia z11 mini s [21/10/2018], ROM for all devices (see above for details)
Contributors
highwaystar_ru
Source Code: https://github.com/HighwayStar/android_kernel_nubia_msm8953
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Based On: LineageOs
Version Information
Status: Testing
Created 2018-09-15
Last Updated 2018-10-21
New build uploaded.
Full sources are up too, including vendor blobs used. Feel free to help with development and build other oreo roms.
have persist partition wiped, how to recover
I like the rom, but before flash the rom, I wiped data, system, cache, persist partition with the twrp recovery, and find:
1. wifi and blutooth is unusable (no mac for bluetooth, wifi mac becomes 02:00:00...)
2. nearly all the sensors are not usable now, but phone call and message is still ok
tried:
1, wipe and flash the official rom v3.09 from fast boot: nubia emergency recovery, not work
2, wipe and with nubia emergency tool v1.16, flash the recovery in fastboot nubia emergency download mode, no backup file and not work
3, tried QPST_2.7.474, but it stops to work frequently, and can hardly do anything
now I'm just using the phone without wifi and most sensors, is there any tidy method to recover all the functions of my nubia z11 mini s,
or could you please backup the persist partition, and tell how to modify the it to make it recover?
Thanks very much!
rtgiskard said:
I like the rom, but before flash the rom, I wiped data, system, cache, persist partition with the twrp recovery, and find:
1. wifi and blutooth is unusable (no mac for bluetooth, wifi mac becomes 02:00:00...)
2. nearly all the sensors are not usable now, but phone call and message is still ok
tried:
1, wipe and flash the official rom v3.09 from fast boot: nubia emergency recovery, not work
2, wipe and with nubia emergency tool v1.16, flash the recovery in fastboot nubia emergency download mode, no backup file and not work
3, tried QPST_2.7.474, but it stops to work frequently, and can hardly do anything
now I'm just using the phone without wifi and most sensors, is there any tidy method to recover all the functions of my nubia z11 mini s,
or could you please backup the persist partition, and tell how to modify the it to make it recover?
Thanks very much!
Click to expand...
Click to collapse
Did you backup params of the device,
If yes then use it with nubia emergency recovery tool if you didn't then you can get persist img if you search in temporary folder of windows while running nubia emergency recovery tool but you have to manually change mac addresses.
Znooper said:
Did you backup params of the device,
If yes then use it with nubia emergency recovery tool if you didn't then you can get persist img if you search in temporary folder of windows while running nubia emergency recovery tool but you have to manually change mac addresses.
Click to expand...
Click to collapse
thank you so much! by default where is the persist.img file and does this file only exist during the flsh process?
and how to maunually change the mac address?:fingers-crossed:
--
it's in %USER%\AppData\Roaming\Nbrt\000ECB4A ... and is kept after the flash done.
the image extracted there is android sparse image, it can be converted to raw image with the tool here:
android-simg2img in github (no links allowed for me now)
there is only several file in the initial persist image, confirmed that wifi works so long as the three file copied back to /persist, and to change the mac addr, modify Intf0MacAddress in WCNSS_qcom_cfg.ini
Now, it's flashing the official rom, to check if all the function are recovered, especially the sensors ... later to report
rtgiskard said:
thank you so much! by default where is the persist.img file and does this file only exist during the flsh process?
and how to maunually change the mac address?:fingers-crossed:
Click to expand...
Click to collapse
So sorry but I'm not able to get that location (am away from my device) but you can find it in temporary folder after selecting recovery option in emergency tool.
Changing mac address is a easy task you can google it up and find many articles on it.
Or https://beebom.com/how-change-mac-address-android/
Go here .
rtgiskard said:
thank you so much! by default where is the persist.img file and does this file only exist during the flsh process?
and how to maunually change the mac address?:fingers-crossed:
--
it's in %USER%\AppData\Roaming\Nbrt\000ECB4A ... and is kept after the flash done.
the image extracted there is android sparse image, it can be converted to raw image with the tool here:
android-simg2img in github (no links allowed for me now)
there is only several file in the initial persist image, confirmed that wifi works so long as the three file copied back to /persist, and to change the mac addr, modify Intf0MacAddress in WCNSS_qcom_cfg.ini
Now, it's flashing the official rom, to check if all the function are recovered, especially the sensors ... later to report
Click to expand...
Click to collapse
confirmed! now all sensors works, at leasdt for the vendor rom! I can flash lineageos finally!
but seems that for the vendor rom, the mac address is regenerated from other info rather than get from the WCNSS_qcom_cfg.ini ...
about the persist partition
for now, I flashed this rom, and before flash, I wiped the persist image and copied back some file from the initial persist.img, but after system boot, most sensors does not work still, should I replace the persist partition with the one which works well for the official rom.
the question is:
1. should the persist partition be wiped before flash the rom
2, may I wipe the persist partiton and copy back some initial file from persist.img after the rom boot several times
3, may I replace the whole persist partition with a working one after the rom booted several times
thank you so much!
few sensors does not work for sometime
the step I flash the rom:
flash the twrp from the link here
wipe everything I can wipe(including the persist partition)
reflash the official boot.img, recover official persist.img got from the nubia emergency tool
flash the offcial rom with only the first assertion in the zip deleted(as the ro.product.name is NX549J and can not modify it in the twrp recovery)
wipe all cache and reboot the official rom
confirm that everything works fine and reboot to twrp recovery
backup the persist partition
wipe all cache, system, data, internal storage, sdcard, do not touch persist partition this time
flash this lineageos rom, gapps nano, su plugin
wipe all cache and reboot
on the fisrt reboot, seems that evrything works except for the four sensors:
gravity
linear acceleration
rotation
orientation
and the second or third reboot after installed many apps, they comback to life, but on the other reboot, they are not usable again, with the official rom, every sensor works on each reboot.
question:
why the four sensor is special compared to the other sensors?
why it worked once and how to recover them completely
thanks very much!
more feedback
rtgiskard said:
the step I flash the rom:
flash the twrp from the link here
wipe everything I can wipe(including the persist partition)
reflash the official boot.img, recover official persist.img got from the nubia emergency tool
flash the offcial rom with only the first assertion in the zip deleted(as the ro.product.name is NX549J and can not modify it in the twrp recovery)
wipe all cache and reboot the official rom
confirm that everything works fine and reboot to twrp recovery
backup the persist partition
wipe all cache, system, data, internal storage, sdcard, do not touch persist partition this time
flash this lineageos rom, gapps nano, su plugin
wipe all cache and reboot
on the fisrt reboot, seems that evrything works except for the four sensors:
gravity
linear acceleration
rotation
orientation
and the second or third reboot after installed many apps, they comback to life, but on the other reboot, they are not usable again, with the official rom, every sensor works on each reboot.
question:
why the four sensor is special compared to the other sensors?
why it worked once and how to recover them completely
thanks very much!
Click to expand...
Click to collapse
seems that it's related to the service bootup sequence or maybe, this problem appears in random on boot,
and I found once only the gravity sensor not working.
another problem:
if enabled adb on usb, it's better to have the service delayed on boot or there may be big chances that the adb device id is not initialized to ro.serialno.
Twrp doesnt work please fix it . The best ROM for nubia z11 mini s until done.
rtgiskard said:
seems that it's related to the service bootup sequence or maybe, this problem appears in random on boot,
and I found once only the gravity sensor not working.
another problem:
if enabled adb on usb, it's better to have the service delayed on boot or there may be big chances that the adb device id is not initialized to ro.serialno.
Click to expand...
Click to collapse
highwaystar_ru said:
New build uploaded.
Full sources are up too, including vendor blobs used. Feel free to help with development and build other oreo roms.
Click to expand...
Click to collapse
halo
Android_device_nubia_msm8953-common /sepolicy/ error while compiling rr
Thanks for your great work.
Installed and testing.
So far, not working: FM radio, which is missing.
Would be great to have Nubia camera working for this build as well.
Cheers!
2018-09-25
Updated audio configs
Added sepolicy rules,selinux in enforcing mode now
Added stock thermal config
Fixed LiveDisplay
BLACK★ROCK SHOOTER said:
halo
Android_device_nubia_msm8953-common /sepolicy/ error while compiling rr
Click to expand...
Click to collapse
sepolicy was incomplete, should be fixed now.
Can't flash this ROM
Hello I'm really happy when someone still making new roms for this luxury device. Got lineage 14.1 as last perfect fitted ROM. I'm waiting really long time for Android 8.1 and when I was found it..just can't flash it successfully I'm using TWRP Nubia Style and flashing from internal memory. Never had any problem with this option of flashing and with this ROM (Lineage 15.1) I just getting a red message after start installation about something like: "Error code 7, This rom is for device: nx549j and your device is..." And nothing. Tried to keep system readable only and tried too check allowing modifies,but still no effect. Can you please teach me what I'm doing wrong? (Flashed every other rom before without any problems. Like Mokee, Lineage,CrDroid,RR and etc..) BTW. Ofc my phone is Nubia z11 mini s (nx549j). And got a next special question.. Is really hard to integrate to lineage ROMs things which are implemented in original Nubia ROM? Like: Nubia Camera (with that luxury quality - Google camera is broken),Good audio sound - speaker,Qualcomm Izat function and etc? Why to not add it to rom when this is only for this model? Thanks for the response
ampoking said:
"Error code 7, This rom is for device: nx549j and your device is..."
Click to expand...
Click to collapse
What version of twrp do you have? To flash oreo roms you have to use at least twrp 3.2.0.
highwaystar_ru said:
sepolicy was incomplete, should be fixed now.
Click to expand...
Click to collapse
yes! but I'm in trouble
The headphones and many of the Settings don't work
can you help me?
log:
https://drive.google.com/file/d/1OtjAbfbQIEvoDnQ6SDaMlL3Guv7n-0Ks/view?usp=drivesdk
Thank you very much！
BLACK★ROCK SHOOTER said:
yes! but I'm in trouble
The headphones and many of the Settings don't work
can you help me?
log:
https://drive.google.com/file/d/1OtjAbfbQIEvoDnQ6SDaMlL3Guv7n-0Ks/view?usp=drivesdk
Thank you very much！
Click to expand...
Click to collapse
The same trouble: I build havocos but the headphone don't work.
{
"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:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, 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 organization.And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.You can also view the changelog for a full list of changes & features.Official LineageOS website : http://lineageos.orgAbout LineageOS Legal : http://lineageos.org/legal
Important Information
1. This ROM operates without ODM images, just follow the installation instructions.2. This ROM does not intended to support Google Camera, but you can try to play with some mods.
About FDE and FBEFull-disk encryption (FDE) has been completely deprecated since Android 13, and now we use software implementation of File-based encryption (FBE).FDE and FBE methods are incompatible with each other. FBE cannot decrypt data encrypted with FDE and cannot encrypt existing files. That's why you need to perform factory reset/format data (not just "wipe data") before switching between ROM's with different encryption methods.To make it a bit clear:- FDE (e.g. stock, LineageOS-16/19) -> FBE (LineageOS-20) -> NOT POSSIBLE! Format data is required.- FBE -> FBE -> POSSIBLE! You can update/upgrade using "dirty" installation as before, in case if encryption methods are the sameMoreover, to work with new encryption you need a recovery with appropriate support.Downloads Links
LineageOS 20:Unofficial: https://sourceforge.net/projects/loire-development/files/lineageos-20/kugoGoogle Applications (optional):MindTheGapps: https://androidfilehost.com/?w=files&flid=322935 (Android 13.0 -> arm64)XDA post about GApps: https://xda-developers.com/download-google-apps-gappsRecommended Recovery (optional):TWRP 3.x: https://forum.xda-developers.com/-/-t3793837
Flashing and updating
Before installation, please make sure you have read and understood everything correctly about FDE and FBE encryption methods.LineageOS clean install:
Download the latest build of LineageOS ROM
Full wipe and factory reset (recommended / backup to make sure not to loose data)
Flash the LineageOS ROM zip from the Recovery
Flash the GApps to have the Google Applications (optional)
Every additional zip you want to flash (optional)
Reboot
LineageOS update/upgrade:
Download the latest build of LineageOS ROM
Wipe cache and dalvik cache
Flash the latest LineageOS ROM zip from the Recovery
Every additional zip you want to flash (optional)
Reboot
You can also update using the built-in Updater (requires at least TWRP 3.6.x or LineageOS Recovery)
About the builds:
Kernel sources: https://github.com/Chippa-a/android_kernel_sony_msm8956
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
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)
Also thanks to:
The LineageOS Team
The SODP Team
Everyone involved in working and testing
Contributors
Chippa_a
ROM OS Version: 13.x
ROM Kernel: Linux 4.9.x
Version Information
Status: Beta
FEATURES AND ISSUES
Boot: Ok
Bluetooth: Unknown
WiFi: Ok
WiFi Hotspot: Unknown
RIL - Phone - Data: Ok
GPS: Ok
Camera: Unknown
Camcorder: Unknown
Lights: Ok
MicroSD: Ok
Accelerometer: Ok
Compass: Ok
Gyroscope: Ok
QTI sensors: Ok
Touchscreen: Ok
FM Radio: N/A
Fingerprint: Ok
Vibrator: Ok
Microphone: Ok
Audio & music: Ok
Bluetooth audio: Ok
NFC: Unknown (HCE: Unknown)
Kernel: Ok (WIP)
Graphics: Ok
3D Rendering: Ok
Clock: Ok
DRM: Unknown
Offline Charging: Ok
USB: Ok
USB Tethering: Unknown
USB OTG: Ok
Encryption: Ok
SEPolicies: Enforcing
It's amazing bro, i can't bealive my device got A13
It seems the device is working again - post removed
soomon said:
I installed this system, and at the 2nd reboot my phone is dead. completely dead. seems it has been bricked before I even could log into my google account.
It doesnt even react to power any more.
Of course the phone is old and wasnt used for a long time, so I dont know if it got bricked by the OS or the hardware.
but it's dead.
be careful people!
Click to expand...
Click to collapse
It's almost impossible to brick this device completely just by ROM, unless you're doing something very unusual or developer-related.
This ROM has been tested by user for more than two weeks and everything was fine. It also been tested by Xperia X users since March, there was nothing like that either... and there never was actually.
Anyway, there is no specific in your message, except "It doesnt even react to power any more". Try to get adb/fastboot modes, charge or flash stock firmware. If no luck, I'm pretty sure it's a hardware issue, probably battery or something else.
I was also thinking about this and it was hard for me to believe the custom OS could actually damage the hardware.
I am happy to report it seems to be the device itself that caused the issue and not the rom. Today it was working Since it is an old device I'm assuming it was a hardware issue, so I deleted my old post.
It's working perfectly now. thank you so much!
I'll install this asap. Cant belive that this device is live again. Im using it as main phone. Gonna post my experience with rom here. Cheers
Edit: Cant seems to make it work . i was on latest stock, did full wipe , installed clean los20 , no gapps no additional zipps . it goes past sony logo shows black screen and immediately restarts on that black screen . Any suggestions ?
Edit 2 : I could not boot to twrp , i needed to install it again after los20 zip, like there is no recovry ? Is that normal ?
After install this rom i found bugs on this rom A13 LOS 20:
-WIFI
-HOTSPOT
-TAP TO WAKE NOT WORK
- GPS can't lock
- NFC
Edit : after reinstall from Lineage 19 to Lineage 20 , Wifi , hotspot , Gps , working fine
Thanks for @Chippa_a and team , share and build rom for x compact
Deep sleep pretty good , keep it up
shandu98 said:
Edit 2 : I could not boot to twrp , i needed to install it again after los20 zip, like there is no recovry ? Is that normal ?
Click to expand...
Click to collapse
Do you have the latest TWRP offered on the other thread? If you get a boot loop back into TWRP you can try tapping restart to system which is an option within TWRP. If you still have problems after with a boot loop try a clean install by wiping dalvik, cache, system, internal storage, followed by formatting data, then reboot to TWRP flash the build and tap restart to system when finished.
my device sony x compact is stuck on twrp logo, is there any solution to fix it?
Note: before stuck on twrp logo, i want to downgrade to A12. but after I entered recovery by (power + vol-) the device was stuck at the twrp logo
Tri Akbar Fitriana said:
my device sony x compact is stuck on twrp logo, is there any solution to fix it?
Note: before stuck on twrp logo, i want to downgrade to A12. but after I entered recovery by (power + vol-) the device was stuck at the twrp logo
Click to expand...
Click to collapse
The same here. The solution for me: i flash stock Rom then Twrp and then los20. After flash los20 twrp stuck on logo, but i can use Los20. Many thanks for los20. Its a great rom.
Asta01 said:
The same here. The solution for me: i flash stock Rom then Twrp and then los20. After flash los20 twrp stuck on logo, but i can use Los20. Many thanks for los20. Its a great rom.
Click to expand...
Click to collapse
if I flash it to stockrom, does it need a TA file? because my TA file is missing.
Tri Akbar Fitriana said:
if I flash it to stockrom, does it need a TA file? because my TA file is missing.
Click to expand...
Click to collapse
I flash Stockrom with flashtool. I dont need TA file.
Tri Akbar Fitriana said:
if I flash it to stockrom, does it need a TA file? because my TA file is missing.
Click to expand...
Click to collapse
No.
Try lineage recovery it works for me, with twrp i get black screen
Chippa_a said:
Moreover, to work with new encryption you need a recovery with appropriate support.
Click to expand...
Click to collapse
For those who have issues with recovery after this ROM.
Please make sure you have installed latest unofficial version (3.7.0_12+) with support for the new FBE encryption method, as stated in OP. Older versions cannot decrypt data encrypted with this method!
Chippa_a said:
For those who have issues with recovery after this ROM.
Please make sure you have installed latest unofficial version (3.7.0_12+) with support for the new FBE encryption method, as stated in OP. Older versions cannot decrypt data encrypted with this method!
Click to expand...
Click to collapse
Thanks,with twrp 3.7.0_12 is twrp working.
Thank you chippa _a. The rom is amazing. I haven't found any bugs so far, and it's incredibly fast. A new life for the Xperia x compact. Thanks alot.
Thanks a lot for this rom! I running it for a few days and no bugs so far
I'm wondering which cam app is the best to use?
And I have one app which doesn't run because my phone is rooted, is there a solution for that?
SietZ said:
Thanks a lot for this rom! I running it for a few days and no bugs so far
I'm wondering which cam app is the best to use?
And I have one app which doesn't run because NY phone is rooted, is there a solution for that?
Click to expand...
Click to collapse
For me is Google cam port "MGC_8.2.204_Parrot043_V1" working perfect.