Related
LineageOS is a free, community built, aftermarket firmware distribution of Android 9.0 (Pie), which is designed to increase performance and reliability over stock Android for your device.
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.
*
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
{
"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"
}
-------------
Hello, I'm very excited to tell you that Project Treble is ready to run on our phone. Although it's not stable with always something broken, It's still a nice chance to undergo other ROMs that you want.
Beware that it is only a proof-of-concept try to let everyone know our device is still powerful. They are still well prepared for future Android release. However, the GSIs will never be more stable than device-specific ROMs. This Treble ROM is not suitable for daily use.
The main reason why official LineageOS of our device didn't ship with Project Treble is that we don't have fully binderized camera HALs from Oneplus. If we want to support Treble there must be a lot of compromises.
Things working:
Everything, including camera.
Things not working:
1. [A-only & A/B] SELinux is set to permissive for most GSIs.
Unnecessary and won't fix for now.
2. [A/B] Reboot and stuck at boot animation while GSI installation.
Solution: Use adb for a reboot, don't just hold the power button. After this the system will boot, at least we could get console-ramoops correctly for debugging.
The step-by-step guide on how to treblize your device:
Treble needs a partition called "Vendor", but our device does not have this device. What we need to do is to create a vendor partition by our selves.
I made a custom TWRP Treble build to do this process, here is what you should do in TWRP.
0. Warning
Our device is really old, some users may experience storage failure (Known as CRC failure), please be careful when you treblize your device. If you meet any problem, please check the 9008 unbrick guides in the forum.
1. Flash this TWRP in the download link below.
2. Boot it up and go to "Advanced" -> "Terminal", Type treblize and run.
Treblize is a shell that we could modify our partition. It basically does the same thing as the commands below.
Code:
/sbin/sgdisk --typecode=5:8300 /dev/block/sdf
/sbin/sgdisk --change-name=5:vendor /dev/block/sdf
3. Reboot your phone to your current system to check if there is storage failure.
It's very important. Some of the users report it may cause storage broken. You'd better check it first before flashing LOS Treble.
4. Reboot your phone to TWRP.
5. Flash LOS Treble in the download link below.
After these processes, you have got a treblized Oneplus3. Boot it up to check if everything works, or just trying other GSIs anyway.
The step-by-step guide on how to flash GSIs:
0. Treblize.
1. Choose and flash LOS Treble solution first for the vendor partition.
Because of the supporting of system-as-root for our device, you can now use every GSIs if possible. I personally recommend the system-as-root solution for future android standards, although they are basically the same some old recovery install scripts may be broken like opengapps will not working anymore according to the report.
2. Flash A-only or A/B GSI image according to the flag in the download section.
3. Wipe data.
Q&A:
1. Q: What are the limitations to our devices?
A: Sizes. Our device has 3154116608 bytes or 3.15G of system storage. Some GSIs may be larger than our device and due to TWRP's bug it won't be recognized. Here is a guide for linux users to make self modified GSIs images of smaller size.
Code:
sudo simg2img <system.img> system.ext4.img
sudo mount -t ext4 -o loop system.ext4.img system/
sudo chown -R <username>:<username> system/
#then enter the system/app folder and remove gmail, maps, google play music, drive, etc.
makeext4fs -T 0 filecontexts -l 3154116608 -L system -system -s flash.img system/
2. Q: Something is broken in some GSIs!
A: That may or may not be our device's fault.
3. Q: Can I install other third-party kernels?
A: You need to make sure that kernel supports mounting vendor partition, or it will brick your device.
Also, the device now is supporting system-as-root, which requires new kernel patchs. Kernels claimed that for treble previously may not work anymore.
4. Q: How to revert my treblized device?
A: Unnecessary. But you can do it yourself with the sgdisk command-line tool, or just use the 9008 tool if you are lazy.
5: Q: How do I install a non-treble ROM with my "treblized" device?
A: As normal. They won't affect each other.
Thanks:
dianlujitao and other LOS devs for current device tree
XiNGRZ for op5 treblize reference
a lot of testers
Chat Group:
https://t.me/joinchat/BrAZb0Zf9p3q7Qz_No5AUA
Join the chat group for sGSI QPR6 guide and more!
Downloads:
[New][A/B] LineageOS 16.0 Treble system-as-root: https://mega.nz/#F!UgdQRYSD!8s-_u2HJQZDEqNnFOnejxQ
[Old][A-only] LineageOS 16.0 Treble: https://mega.nz/#F!A0VmQAaC!Mc3HYZgAkxeoQwGkZyJvwg
[Deprcated][A-only] LineageOS 15.1 Treble: https://androidfilehost.com/?w=files&flid=280568
XDA:DevDB Information
LineageOS Treble, ROM for the OnePlus 3
Contributors
simonsmh, dianlujitao, chenxingyu,
Source Code: https://github.com/OP3Treble
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: OxygenOS/H2OS 9.0.x
Based On: LineageOS
Version Information
Status: Alpha
Created 2018-08-17
Last Updated 2019-08-27
Short update logs.
20190826:
Support system-as-root, flash A/B GSIs instead of A-only.
thanks to zuk-devs
20190731:
Camera fixed in Q
Reserved
Awesome work. Long live 3/3T.
Is this Android pie or Oreo? Title says 15.1
MarcoLK said:
Is this Android pie or Oreo? Title says 15.1
Click to expand...
Click to collapse
U can flash any GSI either pie or Oreo. Camera and volte is broken on pie
Good work guys, I think I'll wait for the camera issue to be fixed before risking to brick my device though
After flashing gsi system img how to make it boot ?I tried , but failed. But booted in my redmi note 4x both gsi and sGSI.
Wow.. Thanks:good:
Sent from my OnePlus3T using XDA Labs
This is incredibly exciting! I hope this also inspires OnePlus to release official treble support.
Before i dare to flash this i would like to know, what is the rollback plan for this if you want to bring the device back to factory state and does it break compatibility with for example the stock rom and stock recovery?
For those that already jumped ship and installed a GSI image, can you test if one of the following mods works?
Arnova v8.2 https://www.celsoazevedo.com/files/android/google-camera/f/GoogleCamera-Pixel2Mod-Arnova8G2-V8.2.apk
Tolyan v1.0.7 https://www.celsoazevedo.com/files/...f/MGC_5.3.015_B-S-G-based_v.1.0.7_TlnNeun.apk
Skulshady https://www.celsoazevedo.com/files/android/google-camera/f/skulshady_gcam_5.1.018_Mod_v6_fix.apk
These are various modded APK's that may contain a fix for the camera issues. No root required to flash.
henk717 said:
This is incredibly exciting! I hope this also inspires OnePlus to release official treble support.
Before i dare to flash this i would like to know, what is the rollback plan for this if you want to bring the device back to factory state and does it break compatibility with for example the stock rom and stock recovery?
Click to expand...
Click to collapse
You don't need to roll back. Just like op5, it's still working if oneplus offer us official treble support.
At least you can either modify the partition label or use 9008 tools to return stock.
Great news.
Hope fixes in future
drmuruga said:
After flashing gsi system img how to make it boot ?I tried , but failed. But booted in my redmi note 4x both gsi and sGSI.
Click to expand...
Click to collapse
What GSI did you try to flash.
---------- Post added at 09:19 PM ---------- Previous post was at 09:18 PM ----------
henk717 said:
This is incredibly exciting! I hope this also inspires OnePlus to release official treble support.
Before i dare to flash this i would like to know, what is the rollback plan for this if you want to bring the device back to factory state and does it break compatibility with for example the stock rom and stock recovery?
For those that already jumped ship and installed a GSI image, can you test if one of the following mods works?
Arnova v8.2 https://www.celsoazevedo.com/files/android/google-camera/f/GoogleCamera-Pixel2Mod-Arnova8G2-V8.2.apk
Tolyan v1.0.7 https://www.celsoazevedo.com/files/...f/MGC_5.3.015_B-S-G-based_v.1.0.7_TlnNeun.apk
Skulshady https://www.celsoazevedo.com/files/android/google-camera/f/skulshady_gcam_5.1.018_Mod_v6_fix.apk
These are various modded APK's that may contain a fix for the camera issues. No root required to flash.
Click to expand...
Click to collapse
No, the camera does not work at all.
Does re-partitioning involve internal storage/data partition data loss?
Edit: P.S.: Could I suggest to open a dedicated thread for TWRP Treble as a guide for making our device treble-enabled? I think it could be useful and clearer.
edoardotavecchio said:
Does re-partitioning involve internal storage/data partition data loss?
Edit: P.S.: Could I suggest to open a dedicated thread for TWRP Treble as a guide for making our device treble-enabled? I think it could be useful and clearer.
Click to expand...
Click to collapse
Basically it won't. But formating /data is still suggested to avoid some problems.
Wow, excellent!
Was waiting for this since so long.
Amazing work.
Gonna try it out soon.
Some questions though,
Can I use any of the GSI or I'll have to use provided lineage GSI only?
If I want to use an android pie GSI, then which gapps should I use? I need full gapps.
Also, The camera isn't even working in third party applications such as WhatsApp also?
Which 9.0 GSI is good, is there any AOSP GSI?
Are there any other bugs?
Final thing, can someone please provide me the link for the thread for oneplus3t where 9008 unbrick recovery procedure is there?
You can use any GSI but when i tried android pie GSI wifi dont work and 4G was broken and camera was not working
MODERATOR NOTICE: YOUTUBE LINK REMOVED
From watching this video, I guess that Lineage stock camera app doesn't work, but others do, correct?
xpissio said:
From watching this video, I guess that Lineage stock camera app doesn't work, but others do, correct?
Click to expand...
Click to collapse
Yes. And camera works only on Oreo GSI's and not on pie yet.
I'm not responsible for whatever damage this could possibly cause to your device.
Before Starting Make Sure You Treble Your Device By This Guide here
If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal
Welcome to Pie Vendor For Galaxy A8/A8+ 2018 ONLY FOR A530F/A530W/A730F
Some information you should know..
Full TREBLE Documentation here : https://source.android.com/devices/architecture
Generic System Image (GSI) Documentation here : https://source.android.com/setup/build/gsi
GSIs are not the most stable and many users prove they are unable to read. they just want ready stuff. with this project that is not the case. if you skip the instructions/F.A.Qs and notes, dont bother installing this project as you probably wont be able to get it running.
This is a fully featured VENDOR and KERNEL designed for this device to support project treble, it is based on other Exynos 7885 Vendors and modified to support our devices, i have also added few patches and fixes to this vendor to get the best possible experience
The vendor is pretty much bugles, therefore any bugs you face, Report them to the appropriate Threads of the GSI you installed or github issues section, as those are not mine to fix i only provide the vendor and kernel that allows GSIs to run on.
- VENDOR FEATURES:
Wi-Fi & Hotspot
Telephony & Ril (Mobile Data, Calls, SMS, MMS)
NFC
Camera
Bluetooth
GPS
Fingerprint
All Sensors
- STEPS FOR INSTALLING TREBLE VENDOR:
Make Sure You Treble Your Bevice By This Guide here
Boot into Twrp recovery
Wipe System, Data, Dalvik and Vendor.
Select Vendor_Dumpster.zip
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be A-only_arm64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Reboot to TWRP Recovery
- STEPS FOR INSTALLING GAPPS
Download the appropriate opengapps
Go to TWRP , Install
Pick your OpenGapps.zip
Reboot to System
- KNOWN BUGS:
Bluetooth calls are broken
Credits:
- @ananjaser1211 for his contribution
- @TaifAljaloo for testing
Downloads. Changelogs , F.A.Qs below
XDA:DevDB Information
Project Treble, Vendor for the Samsung Galaxy A8 (2018)
Kernel Source
Contributors
prashantp01
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Current Stable Version: v1
Created 2019-05-17
Last Updated 2019-05-17
{
"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"
}
Come hang with us on our chat : Telegram
----------------------------------------------------------------
Treble Pie Vendor Dumpster V1.0 [LATEST]
Treble folder : Gdrive
Recommended GSI : Gdrive
Generic System Image (list) : Github
---------------------------------------------------------------
Bugs :
1- some users might face SDCard issues
If you did , back up its data and format it in GSI.
2- If you face "Error 70: Insufficient storage space available in the system partition" while flashing Gapps
If you get do this : Wipe > Advanced Wipe > select system > Repair or Change File System > Resize File System
Go back and flash Gapps
V1.0
-initial release
F.A.Q
For more details related to this project, read our dedicated Wiki page here.
Q : Do i need to format internal storage ?
A : No
Q : Can i use the Treble recovery for normal ROMs ?
A : Yes, it is preferred especially when making backups. just be sure to wipe vendor when switching to non treble roms
Q : What Camera is recommended ?
A : Footej and open camera works the best
Q : Can i flash any GSIs ?
A : No, only A-ONLY_ARM64 Are supported
Q : Can i flash any sGSIs ?
A : No unless they match the Arch above
reserved
I just flashed the Lineage OS v16 GSI with this vendor and found no problems other than no network bars (as mentioned above) and there were no problems with the camera and fingerprint. I will notify you later if there is a bugs
Thanks for your hard work ?
Sweet! I'm gonna be up all night!
This is fantastic. The boot time has decreased immensely.
Finally got aosp extended 6.5 to boot. Well i didn't, you did.
What a difference. Ressurection Remix as well. The 9.0. That one seems a bit iffy no matter.
I am noticing a different mobile data icon. It'll say 4g+
Not too far from normal full usage. Thank you.
mindlery said:
This is fantastic. The boot time has decreased immensely.
Finally got aosp extended 6.5 to boot. Well i didn't, you did.
What a difference. Ressurection Remix as well. The 9.0. That one seems a bit iffy no matter.
I am noticing a different mobile data icon. It'll say 4g+
Not too far from normal full usage. Thank you.
Click to expand...
Click to collapse
Where you able to get gapps installed it always failed for me.
This has happened on most of these roms
Yes i was. My method is a bit harsh though. I am a fan of internal destruction
So for the gsi, i wipe everything including internal. Then i reboot to recovery. Swipe to allow modifications. Install vendor. Install system image. Then reboot recovery flash fix boot. I almost never bother with gapps anymore until it boots fully. Then i'll immediately go into recovery and flash gapps then reboot of course.
I got sick of errors myself. If you find one you like or want to go back to then it may be worth trying for that perfect install. Almost there.
---------- Post added at 04:33 AM ---------- Previous post was at 04:20 AM ----------
https://downloads.aospextended.com/treble_gsi
Before only 6.1 worked. Now 6.5 starts in a minute or so. 6.3 boot looped before so i am going to see what happens now.
mindlery said:
Yes i was. My method is a bit harsh though. I am a fan of internal destruction
So for the gsi, i wipe everything including internal. Then i reboot to recovery. Swipe to allow modifications. Install vendor. Install system image. Then reboot recovery flash fix boot. I almost never bother with gapps anymore until it boots fully. Then i'll immediately go into recovery and flash gapps then reboot of course.
I got sick of errors myself. If you find one you like or want to go back to then it may be worth trying for that perfect install. Almost there.
---------- Post added at 04:33 AM ---------- Previous post was at 04:20 AM ----------
https://downloads.aospextended.com/treble_gsi
Before only 6.1 worked. Now 6.5 starts in a minute or so. 6.3 boot looped before so i am going to see what happens now.
Click to expand...
Click to collapse
I'm using ion- v1.0.c 9.0 without any issues.
For some reason on the newer gsi roms you can't get gapps to install.
ion rom gapps are included.
mchlbenner said:
I'm using ion- v1.0.c 9.0 without any issues.
For some reason on the newer gsi roms you can't get gapps to install.
ion rom gapps are included.
Click to expand...
Click to collapse
I have never heard of that. Of course I am downloading but is there any information about it besides a file on android file host?
mindlery said:
I have never heard of that. Of course I am downloading but is there any information about it besides a file on android file host?
Click to expand...
Click to collapse
I had not heard of it also but it seems to work without issue.
Only thing on screenshot you have edit where photo is being stored.
Does this allow me to use system-as-root gsis? Since android 9 treble implementation is supposed to be system as root even on aonly, I would guess so, but I couldn't get my device to boot with one yet.
Weird, I can't even get aospextended to work... It just bootloops without bootanimation.
Edit: nvm, I got it to work, but I had to flash the oreo vendor first, and then the pie vendor.
Edit2: fingerprint doesn't seem to work even with fp patch (it's weird, it registers the fingerprint, and even validates it, but it does nothing on the lockscreen)
Edit3: restart fixed it
I have a few questions
I used to flash the usual custom roms so is this is the same thing i mean that if i can use it to flash custom roms
And which roms exactly working perfectly on this device without any issues
Also should i root my phone before installing it or what exactly should i do
Is it stable and doesn't have any problems or will i face some problems while im using it
For some reason on aosp extended gsi the phone will stay stuck at the charging screen (gray one without percentage) when charging when its turned off, disconnecting the cable doesn't do anything, it stays stuck on this screen till i force reboot
CoinKiller said:
For some reason on aosp extended gsi the phone will stay stuck at the charging screen (gray one without percentage) when charging when its turned off, disconnecting the cable doesn't do anything, it stays stuck on this screen till i force reboot
Click to expand...
Click to collapse
Did you install GSI_Fix_boot.zip?
So I want to install Google phone but I cannot get it to work. Can you give me an alternative ?
If I want to install a different GSI I follow the steps again (install vendor, flash GSI, flash boot fix and fixes if needed) or just wipe system, data, cache and flash the new image+ boot fix
slawdos said:
Did you install GSI_Fix_boot.zip?
Click to expand...
Click to collapse
Yes but i had to format /vendor after installing that zip (it wasnt the zip fault!), Didn't that get installed in /system?
{
"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:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* 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.
*/[/COLOR]
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Your data, your rules. With powerful tools such as Privacy Guard, you are in control of what your apps can do whenever you want.
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation instructions
Prerequisites:
Unlocked Sony Xperia Z3 Compact
Fastboot drivers to install TWRP
Micro-USB Cable to connect your phone to your computer
Install:
Reboot to TWRP. *
Wipe cache, dalvik cache, data and system.
Install ROM.
Install 10.0 Gapps for ARM. **
* recommended TWRP: Post #2
** optional, opengapps
Downloads
Download the ROM
Over the Air Updates
To use OTA updates please read Post #2
Sources
DEVICE:
https://github.com/LineageOS/android_device_sony_z3c
https://github.com/LineageOS/android_device_sony_msm8974-common
https://github.com/LineageOS/android_device_sony_shinano-common
KERNEL:
https://github.com/LineageOS/android_kernel_sony_msm8974
Addons
OpenGapps
Magisk
Thanks
Whole LineageOS Team for this amazing ROM
@koron393
@SpiritCroc
@Myself5
@nailyk
@drakonizer
@rcstar6696
@tomascus
I hope I haven't forgot anyone
Bugs
Current hardware support state: Gist
WHAT'S BROKEN
You tell me.
XDA:DevDB Information
LineageOS 17.1 for z3c, ROM for the Sony Xperia Z3 Compact
Contributors
NeoArian
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: 23.5.A.1.291
Based On: AOSP
Version Information
Status: Beta
Created 2019-10-02
Last Updated 2020-01-04
OTA and TWRP recovery
Over the Air Updates
My upload script automatically pushed OTA updates to my GitHub.
If you want to make them visible through the Updater you can flash the attached magisk module LineageOS-17.1_z3c-OTA-v1.zip or add the line
Code:
lineage.updater.uri=https://raw.githubusercontent.com/ArianK16a/OTA/lineage-17.1/z3c.json
manually to your build.prop. You should use the recommended TWRP so that the updates flash fine.
TWRP recovery
TWRP 3.3.1 for our z3c with Android 10!
The TWRP for Android 10 is attached to this post.
Source is available at: https://github.com/z3c-pie/twrp_device_sony_z3c/tree/android-10.0
Changelog for twrp-3.3.1-1-z3c-20191212-sar.img
Improved System as root support, /system is a symlink to /system_root/system now
Changelog for twrp-3.3.1-1-A10.0-z3c.img
Added Bootlogo, booting from offline state will display the original sony logo now instead of nothing
Fixed fastboot boot
Updated kernel cmdline from 23.5.A.1.291
How to install this build:
Reboot to fastboot by holding volume up while connecting your device to your computer
Open a terminal and move to the directory with TWRP in it
Rename the downloaded image to twrp.img
Type
Code:
fastboot flash recovery twrp.img
Boot into TWRP while the device is powered off press the power and volume down button
Feel free to ask questions or give feedback about TWRP here .
Have a nice day!
Additional information about the recovery on this device:
First of all we should make the basics clear: On our Z3 Compact we have got a bootloader update which can boot a recovery from powered off state by pressing volume down and the power button. Because we haven't ever had this updated bootloader and not all sony devices received the update, there have been some intelligent people who brought a special init binary which can handle recovery boots during a normal boot. This means when using advanced reboot from the ROM or pressing a volume key while the sony logo appears at boot. https://github.com/LineageOS/android_device_sony_common/commits/lineage-16.0
To make this work there is this method to extract the ramdisk: https://github.com/LineageOS/androi...eage-16.0/extract_ramdisk/extract_ramdisk.cpp which uses zlib to decompress it. So far so good, zlib can decompress the default compression for recovery ramdisk which is gzip. However LZMA is more effective to reduce the size so we took it's advantage: https://github.com/omnirom/android_...mmit/885b01223a460d3f2500155ea415bdc8573679bc in order to fit recoverys compiled from recent environments (android-9.0 in my case) into our small FOTAKernel partition.
According to this change the init_sony can't handle the recovery boot anymore because it can't decompress the recovery's ramdisk so nailyk and Diewi (as far as i know) added support to decompress LZMA compressed ramdisk's with this chain: https://github.com/sonyxperiadev/device-sony-common-init/pull/20/commits
However these commits have never been merged into the LineageOS/android_device_sony_common nor the sonyxperiadev/device-sony-common-init. Since your ROM, CarbonROM, is using a fork of LineageOS/android_device_sony_common is missing these commits the recovery boot fails with a kernel panic, like this: https://del.dog/egawososux.htm
So you can either use a recovery which doesn't compress the ramdisk with LZMA (for example the one from here: https://forum.xda-developers.com/z3-compact/development/recovery-twrp-3-2-3-0-aries-t3837192 or ask your ROM developer to pick the according commits into the sony_common tree/use my fork of LineageOS's one https://github.com/z3c-pie/android_...mits/fa85dfcc07f42d73f9a1abf1f4c82d8bf0486a93 which would enable you to use recent TWRP builds with a LZMA compressed ramdisk.
I hope i presented it clearly and in the right way,
Have a nice day!
EDIT: Minimized patch for LZMA is available here: https://review.lineageos.org/c/LineageOS/android_device_sony_common/+/252923
Click to expand...
Click to collapse
The new build is up!
Get it from here: https://sourceforge.net/projects/ep...age-17.0-20191002-UNOFFICIAL-z3c.zip/download
Make sure to use the new TWRP from Post #2 because Android 10 introduces System-as-Root which can lead to weird behaviour in the old TWRP.
Note that there are not all features from LineageOS 16.0 ported over yet and there can be unexpected, yet unlisted bugs.
MY personal hardware support list can be found here: https://gist.github.com/ArianK16a/1e46c463a5c910efb322d9cf0e16c3c0 but as always, i can't guarantee you anything!
Happy flashing!
I will try, thx :>
but there are no opengapps for 10,
what about this? will be good?
https://www.cyanogenmods.org/download-gapps-for-android-10/
hah ok now I don`t know anything... ;/
still same problem with this freakin camera and torch exactly like in v16
all my steps:
1.
flashtool64 -> Stock Android 6.0.1 for D5803 - 23.5.A.1.291 - Unbranded - Baltic Generic (1288-5413)
https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
2.
TWRP for 6.01 - with this https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
Kernel .575 -> recovery for mm575 ->kernel .291
3.
installation of yours TWRP - twrp-3.3.1-A10.0-z3c
4. in twrp 3.3.1 wipe cache, dalvik cache, data and system, rom installation
5. camera and torch doesn`t working ;/ "camera keeps stopping" and torch is greyed out
NIce, thank you
hhpl said:
hah ok now I don`t know anything... ;/
still same problem with this freakin camera and torch exactly like in v16
all my steps:
1.
flashtool64 -> Stock Android 6.0.1 for D5803 - 23.5.A.1.291 - Unbranded - Baltic Generic (1288-5413)
https://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706
2.
TWRP for 6.01 - with this https://forum.xda-developers.com/z3-compact/general/recovery-root-mm-575-lb-t3418714
Kernel .575 -> recovery for mm575 ->kernel .291
3.
installation of yours TWRP - twrp-3.3.1-A10.0-z3c
4. in twrp 3.3.1 wipe cache, dalvik cache, data and system, rom installation
5. camera and torch doesn`t working ;/ "camera keeps stopping" and torch is greyed out
Click to expand...
Click to collapse
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
hhpl said:
I will try, thx :>
but there are no opengapps for 10,
what about this? will be good?
https://www.cyanogenmods.org/download-gapps-for-android-10/
Click to expand...
Click to collapse
There are GApps: https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/
NeoArian said:
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
Click to expand...
Click to collapse
ok I had something in my head that I needed first this marshmallow recovery... I don`t know why
but now I flashed once again 291 and then yours twrp and wiped all the stuff ofc included data and still torch and camera doesn`t work ;/
hhpl said:
I don't understand what you are doing after you flashed stock. Can you also format data within my twrp? I have recognised that the /data partition size has been set wrong in most older TWRP's.
ok I had something in my head that I needed first this marshmallow recovery... I don`t know why
but now I flashed once again 291 and then yours twrp and wiped all the stuff ofc included data and still torch and camera doesn`t work ;/
Click to expand...
Click to collapse
Format is not wipe. Make sure that twrp asks you to confirm by typing yes.
NeoArian said:
Format is not wipe. Make sure that twrp asks you to confirm by typing yes.
Click to expand...
Click to collapse
ok done, once again nothing new, still same situation
Can this ROM be installed on top of LineageOS 16 without wape?
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
Are you talking about the GApps I posted a few posts back? https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/ If I remember correctly I didn't have problems while I tested them...
NeoArian said:
Are you talking about the GApps I posted a few posts back? https://sourceforge.net/projects/opengapps/files/arm/beta/20190928/ If I remember correctly I didn't have problems while I tested them...
Click to expand...
Click to collapse
No, I found a beta version on Google.
Gotta check again with the one you provided, I'll edit this post in a while
Edit: buttons don't work again
marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
wow, so what I`m doing wrong... could you tell me how you install this rom step by step and what rom you had before? steps before installation and steps after or something, I have installed this rom 10 times and never got my camera work, that is crazy
hhpl said:
wow, so what I`m doing wrong... could you tell me how you install this rom step by step and what rom you had before? steps before installation and steps after or something, I have installed this rom 10 times and never got my camera work, that is crazy
Click to expand...
Click to collapse
The same basic steps you'll find in the OP
marcogiannetta said:
Camera and Bluetooth are fine.
Flashing the only gapps for Android 10 I found made the navbar buttons not to work.
I guess we should wait for better gapps build.
Great anyway, thanks
Click to expand...
Click to collapse
I've experienced the same issue after installing gapps - only back button works. Gesture navigation is working fine.
Other bugs I've noticed:
-battery icon style cannot be changed
-launching camera app with hardware button doesn't work
-system accent color cannot be changed (there is only one option listed)
Barciej33 said:
Other bugs I've noticed:
-battery icon style cannot be changed
-launching camera app with hardware button doesn't work
-system accent color cannot be changed (there is only one option listed)
Click to expand...
Click to collapse
You must read 1st to 3rd post.
LOS17 is just getting started.
Note that there are not all features from LineageOS 16.0 ported over yet and there can be unexpected
Click to expand...
Click to collapse
@NeoArian Any chance for a screen recording of how it runs?
JamesMars said:
@NeoArian Any chance for a screen recording of how it runs?
Click to expand...
Click to collapse
No? If you are interested you can test it yourself.
I have my holidays now anyway.
{
"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"
}
Evolution X 6.5 for the Lenovo Xiaoxin Pad Plus (Lenovo P11 5G WiFi) [TB-J607F]
Code:
/*
* Your warranty is void. Or valId, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
Keep Evolving
Pixel UI, customization, and more, we are Evolution X!
- Team Evolution X -
@joeyhuab
@RealAkito
@AnierinB
Reach us on Twitter! @EvolutionXROM
Just flash and check "The Evolver". We have tons of features combined together from different ROMs.
DO NOT FLASH GAPPS, ALREADY INCLUDED
* Probable lost frames when dragging the apps from app drawer to the home screen.
* If you open the Wallpaper Picker in 2-Pane layout (Like open it via Settings), the Wallpaper will be zoomed incorrectly and look blurry. (Note: if you want to set the wallpaper, open the wallpaper picker from the Launcher).
First Time Install / Clean Flash
1. Reboot to Recovery
2. Download the zip for your device
3. Flash whichever recovery you desire in both slots
4. Format Data
5. If you are going to flash from stock ROM, switch to the other slot in recovery, then reboot to recovery
6. Enable ADB Sideload feature, then Sideload the package to your tablet
Code:
adb sideload <path to the flashable zip>
7. Reboot to System and #KeepEvolving
Update / Dirty Flash
1. Reboot to Recovery
2. Download the update for your device
3. Flash the ROM via ADB Sideload
4. Reboot to System and #KeepEvolving
Android OS version: 12.1.0_r11
Security patch level: July 2022
Build author: bigsaltyfishes
Source code: https://github.com/Evolution-X
Kernel Source code: https://github.com/bigsaltyfishes/kernel_lenovo_J607Z
ROM Developer: Joey Huab
Changelog:
2022-07-07:
Notes: Clean Flash Required
Device Changes:
1. Switch to Proton Clang
2. Switch to SkiaGL Threaded Renderer
3. Import Vulkan Overlay from Pixel 5
4. Enable DT2W
5. Import missing governor script from stock rom
6. Import Lenovo side changes to init scripts
Kernel Changes:
1. Upstream kernel to 4.19.250
2. Merge Tag LA.UM.9.12.r1-14300-SMxx50.0
Very good work. Is it possible to get an EvolutionX rom for the tb-j706f ?
Can we get 606f support as well?
I noticed that you recently merged latest caf on your kernel. Did you recover your device?
If you did, could you please tell me how your touch panel is detected as, in your deviceinfohw? (It would be more helpful if you upload your device info onto deviceinfohw, although I understand that it may be hard to in some regions)
I have a similar but different J606F, and the bad manufacturer lenovo didn't include touch panel driver in the kernel, lol.
Thanks
LegendOcta said:
I noticed that you recently merged latest caf on your kernel. Did you recover your device?
If you did, could you please tell me how your touch panel is detected as, in your deviceinfohw? (It would be more helpful if you upload your device info onto deviceinfohw, although I understand that it may be hard to in some regions)
I have a similar but different J606F, and the bad manufacturer lenovo didn't include touch panel driver in the kernel, lol.
Thanks
Click to expand...
Click to collapse
I've already recover my device. Here are the screenshot of Device info Hw, hope it is helpful for you.
LegendOcta said:
I noticed that you recently merged latest caf on your kernel. Did you recover your device?
If you did, could you please tell me how your touch panel is detected as, in your deviceinfohw? (It would be more helpful if you upload your device info onto deviceinfohw, although I understand that it may be hard to in some regions)
I have a similar but different J606F, and the bad manufacturer lenovo didn't include touch panel driver in the kernel, lol.
Thanks
Click to expand...
Click to collapse
Hi!
I've got an J606L, and I'm going crazy because of Lenovo didn't include the touchscreen driver in the opnesource package... I've tried to make TWRP/OrangeFox recovery, but the touchscreen don't work.
Can we somehow use this J607 kernel source in your opinion? In HWinfo almost everything is the same for me. Touchscreen, wifi, als/ps, acc.meter, gyro etc. Thanks for the dev/screenshot OP!
Marci344 said:
Hi!
I've got an J606L, and I'm going crazy because of Lenovo didn't include the touchscreen driver in the opnesource package... I've tried to make TWRP/OrangeFox recovery, but the touchscreen don't work.
Can we somehow use this J607 kernel source in your opinion? In HWinfo almost everything is the same for me. Touchscreen, wifi, als/ps, acc.meter, gyro etc. Thanks for the dev/screenshot OP!
Click to expand...
Click to collapse
I don't think you can't directly use this J607 kernel source as the soc of J606(sm6115) is different from J607(sm7225), but I found that the kernel version of J606 in stock rom is same as J607, maybe the J607 kernel source code can serve as a reference for you to fix the J606 kernel source code. Also, If you want to fix touchscreen in TWRP/OrangeFox, you need to import touchscreen firmware from stock rom.
bigsaltyfishes said:
I don't think you can't directly use this J607 kernel source as the soc of J606(sm6115) is different from J607(sm7225), but I found that the kernel version of J606 in stock rom is same as J607, maybe the J607 kernel source code can serve as a reference for you to fix the J606 kernel source code. Also, If you want to fix touchscreen in TWRP/OrangeFox, you need to import touchscreen firmware from stock rom.
Click to expand...
Click to collapse
Hi!
Yes I've seen your kernel source. I think it will help me for the building, because there is many similarity. Even the filesystem is 1:1 same. I've got final exams in the next few weeks in the Uni too, but after that I will try to make it.
One question tho. How can you export the touchscreen files from the stock rom? I dont know how look your tablet's firmware, but the J606L has a very stupid firmware structure, with superpartitions, and I cannot get any useful stuff out from it, just the vbmeta, boot/recovery images.
Thank you, and sorry for the offtopic.
Marci344 said:
Hi!
Yes I've seen your kernel source. I think it will help me for the building, because there is many similarity. Even the filesystem is 1:1 same. I've got final exams in the next few weeks in the Uni too, but after that I will try to make it.
One question tho. How can you export the touchscreen files from the stock rom? I dont know how look your tablet's firmware, but the J606L has a very stupid firmware structure, with superpartitions, and I cannot get any useful stuff out from it, just the vbmeta, boot/recovery images.
Thank you, and sorry for the offtopic.
Click to expand...
Click to collapse
You can find firmware you need in /vendor/firmware. If it is hard for you to extract them from your tablet, you can simply extract them from 9008 Images. Partitions in super partition are simply named as super_*.img in 9008 package, they are raw images, you can directly mount them with ro option (They have share_blocks feature, you can't mount them in rw mode).
can i flash it on j706f?
Marci344 said:
Hi!
I've got an J606L, and I'm going crazy because of Lenovo didn't include the touchscreen driver in the opnesource package... I've tried to make TWRP/OrangeFox recovery, but the touchscreen don't work.
Can we somehow use this J607 kernel source in your opinion? In HWinfo almost everything is the same for me. Touchscreen, wifi, als/ps, acc.meter, gyro etc. Thanks for the dev/screenshot OP!
Click to expand...
Click to collapse
The thing that's missing is the kernel module for the NT356(something)_HostDL or something in the kernel's {SRCROOT}/drivers/input/touchscreen/NT35something_HostDL.
The driver, IS available in a P11 LTe or something's kernel source available in lenovo downlooad page. (Sorry, my memory is very inaccurate, I was trying bunch of stuffs when I bought my P11 last year, it's a bit hazy now)
I made the driver located there, modded Makefile, got some kernel compile issue, and I somehow solved it, but the spi read only got value 00000000 and it didn't work. (You can get more info from postmarketOS-offtopic Matrix chatroom, chat history is logged in there, I got help from somebody a long time ago and there are conversations about this)
I got touchscreen to work with a prebuilt kernel (Lost the device tree) but that's it..
I hope we make something out of lenovo's junky kernel source codes.. The device has potentials!
bigsaltyfishes said:
I've already recover my device. Here are the screenshot of Device info Hw, hope it is helpful for you.View attachment 5625467
Click to expand...
Click to collapse
Wonderful that you recovered it!
Thanks a lot for the screenshot. It seems like that you have the himax touchscreen variant. (I was trying to ask you to test the driver for nt365blahblah touch screen, if your variant was the one that had it)
hi sir, i flashed crdroid gsi on my j706f, but the settings doesnt look like your rom which show in two pane, can i edit build.prop to get it show as your rom settings? or what should i edit? thank you very much.
sabosanbosocho said:
hi sir, i flashed crdroid gsi on my j706f, but the settings doesnt look like your rom which show in two pane, can i edit build.prop to get it show as your rom settings? or what should i edit? thank you very much.
Click to expand...
Click to collapse
You can't enable it by simply editing build.prop. This feature related to an optional package called androidx.window.extensions. Ask GSI builder add this package or build it yourself.
great work!
overall pretty pleasant experience, and nice feature set. However, two problems
1. as mentioned, adding app icon to the homescreen doesn't work sometimes and it laggs out
2. this is the deal breaker for me, as the volume slider doesn't work. and video play back stuffers probably due to this.
---
update:
the second issue ragarding to the volume slider, it only breaks after playing emby, not sure if other app also break it but that's the only one i found so far. a reboot would fix it
Please make Evolution X happen to TB-J606F also! it's with an older SOC, and we don't get A12 update. A lot of people have it, but not much support
Does widevine security L1?
bigsaltyfishes said:
You can't enable it by simply editing build.prop. This feature related to an optional package called androidx.window.extensions. Ask GSI builder add this package or build it yourself.
Click to expand...
Click to collapse
did you add that by yourself or that was included in evox source code?
mdve123 said:
Please make Evolution X happen to TB-J606F also! it's with an older SOC, and we don't get A12 update. A lot of people have it, but not much support
Click to expand...
Click to collapse
you can flash google gsi (android 12), its works good.
Generic System Image releases | Platform | Android Developers
developer.android.com
{
"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.