https://gitlab.com/hackintosh5/TrebleInfo
Credits
https://github.com/8890q/ for LineageOS 19.1/18.1 device tree, kernel, hardware support, blobs
https://forum.xda-developers.com/t/treble-aosp-g930x-g935x-project_pizza-trebleport-v2-0.3956076/ for libsensor blobs
https://github.com/osm0sis/ for anykernel, used for the twrp patching zip
Special thankshttps://github.com/ExpressLuke for hero2lte testing
https://github.com/00p513-dev for suggesting using squashfs for vendor partition, making it possible to skip partition table modding
https://github.com/phhusson for looking into the double tap to wake issues with phh GSI
https://github.com/ivanmeler for prompting me to look into lpm again, now it is migrated into /vendor
Notes:
I do not own a hero2lte(edge)
I'll mostly work on this only during weekends/holidays
and on that note the hero2lte build is not tested by myself
for vndk30 based vendor (LineageOS 18.1), use with android 11 and up GSIs
for vndk32 based vendor (LineageOS 19.1), use with android 12L and up GSIs
2022-06-12 the CACHE partition is now used as vendor, the HIDDEN patition is now used as cache, no more partition table mods required
Updates:
2023-02-23
added store_mode.zip flashable that uses "/sys/class/power_supply/battery/store_mode" and "/sys/module/sec_battery/parameters/store_mode_max" interfaces for limiting battery charging
flash to limit battery charging to 70%, flash again to disable charging limitafter flashing, charging limit can be adjusted at "/system/etc/init/8890_store_mode.rc" by changing "70" on the line "service enable_store_mode /system/bin/8890_store_mode 1 70" to other percentage values
2023-02-15
include libaptX_encoder.so in patchers
adding patches to support phh android 13 GSIs:
includes lineage lmkd, LineageOS/[email protected] seems required for lmkd to work on this kernelfix bluetooth audio by disabling sysbta (generic in-system bluetooth audio implementation), see phhusson/treble_experimentations#2519disable full disk encryption and quota when booting android 13, 8890q/[email protected] 8890q/[email protected] ; FDE still works when using android 12 GSIsdisable healthd offline charging service, conflicts with lpm
2022-10-04
update gps blobs from https://github.com/8890q/proprietary_vendor_samsung/commit/698ddd9acd7bdca78ecea93e06fd78a0d9dbc407
2022-09-05
adding keystore fixes to a12_patcher.zip:
https://github.com/LineageOS/android_system_security/commit/356c125115c0a9b9f9670b5b86b6e291c5ec5404
https://github.com/8890q/patches/commit/9a322b4e71ca784d4a2f71494d1ef0e52f835efe
which fixes keystore apps and device encryption on Google 12L GSI, might also fix some keystore apps issues on phh GSI
2022-07-10
moved lpm to vendor partition
2022-06-26
rebased vndk32 on 2022-06-24 build from ivan
new smaller vendor flasher, flashes only boot and vendor
2022-06-24
lpm_installer.zip should work with Phh and Andy Yan GSIs better now
2022-06-18
vndk30 prop changes, might help booting exotic GSIs
2022-06-13
android 12 data usage meter now works with a12_patcher.zip
2022-06-12
fixed neural network api hal
fixed fingerprint sensor
switched vendor image to squashfs, no CreateVendor required anymore with it's small size
new twrp patcher zip, should no longer cause "twrp is stuck after flashing CreateVendor"
bigger GSIs should fit better now with the original ~4.5GB SYSTEM partition; device native roms can be used without RevertVendor
2022-05-31
fixed wifi tethering
vndk32: rebased on 2022-05-26 12L build from ivan
phh_wifitethering_patcher.zip for wifi hotspot on phh GSIs
2022-05-26
added vndk32 based release
lpm_installer.zip for offline charging
fixed keystore errors on android 12 GSIs, lock screens work now
2022-02-15
rebased on February build from 8890q
January android updates
2021-12-16
install libaudioroute into /vendor/lib
December android updates
2021-12-10
move properties to /vendor
Tested GSIs
vndk30
https://github.com/phhusson/treble_experimentations/releases/tag/v313 (vanilla/bvS)
https://github.com/phhusson/treble_experimentations/releases/tag/v413 (vanilla/bvS)
https://developer.android.com/topic/generic-system-image/releases (android 12 gsi, with a12_patch.zip flashed after)
vndk32
https://github.com/phhusson/treble_experimentations/releases/tag/v413 (vanilla/bvS)
https://developer.android.com/topic/generic-system-image/releases (android 12 gsi, with a12_patch.zip flashed after)
important: system as root builds, you'd want ab build GSIs
Known issues:
some GSIs like official google GSIs lacks the /efs mount point, it has to be added manually or it will boot loop at samsung logo failing to mount /efs
some android 12 GSIs does not boot due to the lack of ebpf on the 3.18 kernel, android 12 GSIs needs to have patched bpfloader and netd, see below
https://github.com/8890q/patches
https://github.com/phhusson/platform_system_bpf/commit/c81966c23d79241458ebf874cfa8662f44705549
https://github.com/phhusson/platform_system_netd/commit/3a6efa1ff3717a613d1ba4a0eff5e751262d1074
data usage stays at 0 MB used on android 12 GSIs, because ebpf is used for metering
a12_patcher.zip attempts to fix the above issues by creating /system_root/efs and importing bpfloader+netd from https://github.com/8890q/patches
a11_patcher.zip creates /system_root/efs if required
usb adb does not work on android 12 GSIs
a legacy implementation of usb adb is required for this kernel, see https://review.lineageos.org/c/LineageOS/android_packages_modules_adb/+/326385
as a workaround, disable usb adb and use wifi adb
Wifi tethering does not work on phh GSIs <= 414
https://github.com/phhusson/vendor_hardware_overlay/tree/pie/Tethering conflicts with our Tethering overlay
flash phh_wifitethering_patcher.zip after installing phh GSIs
Alarm clock not working on aosp GSI
it should be fixed on phh 414 and up, it is not a vendor issue. If you are using an older aosp GSI, flash deskclock_powersaving.zip to fix that. See https://github.com/LineageOS/androi...mmit/8dd096c4cfb647960be1695a57246727878b8c8d
Google android 13 GSIs do not work
post-build patching got more involved in android 13 since on-java patches are now required, stick with phh/treble droid GSIs which already include build time patches for bpf-less kernel support
Disk encryption does not work on android 13 GSIs
full disk encryption is removed in android 13, file based encryption not available currently https://github.com/8890q/android_de...mmit/3cbcf972465419c18bf4850d26320896df465b18
Installation
If you are using the old partition table mod zip heroxlte_CreateVendor_2.0.zip from older versions, first flash heroxlte_RevertVendor_2.0.zip, or revert your partition table other ways such as odin. Skip this step if you have never touched your partition table
Install twrp-3.6.2_9-0 from https://eu.dl.twrp.me/herolte/ (s7) or https://eu.dl.twrp.me/hero2lte/ (s7 edge), as of rignt now newest(twrp-3.7.0_9-0) is too big for flashing
Flash twrp_patcher.zip to enable system.img flashing, it'll reboot to recovery once it's done, tested on 3.6.2_9-0 but newer versions should work unless recovery.fstab changes
Flash vndk32 for android 12.1(api level 32) and android 13.0(api level 33) GSIs, flash vndk30 for android 11(api level 30) and 12(api level 31) GSIs, herolte for s7 and hero2lte for s7edge
Flash the system.img of your choice
If you are using phh GSI version <= 414, flash phh_wifitethering_patcher.zip
If you are using phh GSI version <= 414, flash phh_dt2w_patcher.zip to fix double tap to wake
If you are using phh GSI version <= 413 or pure aosp, flash deskclock_powersaving.zip to fix alarm clock
If you are using an android 12/12L GSI, flash a12_patcher.zip
If you are using an android 11 GSI, flash a11_patcher.zip
If you are using a phh/treble droid android 13 GSI, flash phh_aosp13_patcher.zip
Updating vendor
Flash vndk32 for android 12.1(api level 32) and android 13.0(api level 33) GSIs, flash vndk30 for android 11(api level 30) and 12(api level 31) GSIs, herolte for s7 and hero2lte for s7edge
Undo twrp_patcher.zip and revert to device native romsThis is not required for using device native roms, however OTA updates might require this
Flash the newest twrp again
Format cache using wipe -> select cache -> repair or change file system -> change file system -> ext4
Flash a device native rom
Buildinglineage_build_herolte_vendor_part, lineage_build_hero2lte_vendor_part, lineage_build_herolte_vendor_part_18.1 and lineage_build_hero2lte_vendor_part_18.1 builds lineageos along with treble vendor using https://github.com/lineageos4microg/docker-lineage-cicd
you'll need ~15GB of free ram, ~300GB free disk space and podman
# create directories
mkdir src
mkdir zips
mkdir logs
mkdir ccache
# builds lineage 19.1 along with vndk32 for herolte (s7 flat exynos)
bash lineage_build_herolte_vendor_part
Reporting issues besides the known ones:
You can report them over https://github.com/Kethen/herolte_treble/issues
Downloadshttps://github.com/Kethen/herolte_treble/releases
Never thought I would see this coming to our device, this is absolutely amazing. Thank you for your hard work
Twrp (latest version) got stuck after flashing twrp patcher, i reflashed it with Odin but now my phone is stuck on the Samsung logo, i cant boot to twrp, only to download mode, what do i do?
"some GSIs like official google GSIs lacks the /efs mount point, it has to be added manually or it will boot loop at samsung logo failing to mount /efs"
indeed GSI google Android 13 does not start what do you mean by mounting efs manually can you explain please thank you
Full House said:
"some GSIs like official google GSIs lacks the /efs mount point, it has to be added manually or it will boot loop at samsung logo failing to mount /efs"
indeed GSI google Android 13 does not start what do you mean by mounting efs manually can you explain please thank you
Click to expand...
Click to collapse
it lacks the mount point, so I meant adding the mount point by modifying system and adding a directory called 'efs'
a11_patcher.zip and a12_patcher.zip does that for you
meanwhile, android 13 beta GSI from google does not boot and I probably won't look into it until android 13 source is released
Omarkoopa said:
Twrp (latest version) got stuck after flashing twrp patcher, i reflashed it with Odin but now my phone is stuck on the Samsung logo, i cant boot to twrp, only to download mode, what do i do?
Click to expand...
Click to collapse
assuming you did the odin flash correctly, try booting samsung recovery and factory reset there
katharinechui said:
important: system as root builds, you'd want ab build GSIs
Click to expand...
Click to collapse
We can use A/B builds too? Didn't really understand, sorry
1lopes said:
We can use A/B builds too? Didn't really understand, sorry
Click to expand...
Click to collapse
you can only use A/B builds, which is also known as system as root builds
Support s7?
katharinechui said:
you can only use A/B builds, which is also known as system as root builds
Click to expand...
Click to collapse
Thank you so much for your response.
Ill try and boot a Nippon GSI and update it here, or start testing some GSIs.
Great project, looks like you put some hard effort
1lopes said:
Thank you so much for your response.
Ill try and boot a Nippon GSI and update it here, or start testing some GSIs.
Great project, looks like you put some hard effort
Click to expand...
Click to collapse
nippon GSIs usually have broken selinux policies and other weird oem rom stuffs that prevent booting.
katharinechui said:
nippon GSIs usually have broken selinux policies and other weird oem rom stuffs that prevent booting.
Click to expand...
Click to collapse
I followed your guide, flashed TWRP 3.6.2_9-0, then twrp_patcher.zip, rebooted to recovery and I dont see any .img ROM, only .zip, and I am sure I do have atleast 1 .img system on my SD card.
Then proceeded to reflash stock ROM, reflashed TWRP once again, did the same steps and the same. I don't know what I am doing wrong, please help me.
Edit: Could it be because I didn't revert partitions? Where can I find the files? I don't see them on github.
1lopes said:
I followed your guide, flashed TWRP 3.6.2_9-0, then twrp_patcher.zip, rebooted to recovery and I dont see any .img ROM, only .zip, and I am sure I do have atleast 1 .img system on my SD card.
Click to expand...
Click to collapse
{
"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"
}
1lopes said:
Edit: Could it be because I didn't revert partitions? Where can I find the files? I don't see them on github.
Click to expand...
Click to collapse
You'd only need revert partition if you've changed your partition table in the past. While the zip is available in all previous releases, I forgot to upload it to the latest release. As of this post it has been re-uploaded to the latest release as well.
1lopes said:
Click to expand...
Click to collapse
Ask nippon to fix their GSIs
katharinechui said:
View attachment 5673497View attachment 5673499View attachment 5673501View attachment 5673503
You'd only need revert partition if you've changed your partition table in the past. While the zip is available in all previous releases, I forgot to upload it to the latest release. As of this post it has been re-uploaded to the latest release as well.
Ask nippon to fix their GSIs
Click to expand...
Click to collapse
Ohhh, i am so sorry. I thought there was something wrong I was doing, as I am actually familiar to only .zip flashing on twrp and fastboot too.
thank you so much for the help!
please add offline charger, thanks
Cuonghmm said:
please add offline charger, thanks
Click to expand...
Click to collapse
it works, what do you mean
katharinechui said:
it works, what do you mean
Click to expand...
Click to collapse
yes it works ,s7, mine, charge and use, it's very hot, is there any way to fix it? thanks
Cuonghmm said:
yes it works ,s7, mine, charge and use, it's very hot, is there any way to fix it? thanks
Click to expand...
Click to collapse
Put it in a freezer... Now being serious, no. Thank Exynos and Samsung battery. Disable fast charge or stop charging when it reaches the limit
1lopes said:
Put it in a freezer... Now being serious, no. Thank Exynos and Samsung battery. Disable fast charge or stop charging when it reaches the limit
Click to expand...
Click to collapse
luckily, offline charging works
Cuonghmm said:
yes it works ,s7, mine, charge and use, it's very hot, is there any way to fix it? thanks
Click to expand...
Click to collapse
using a 1 amp or less charger should help with the temps
Related
This is a TWRP fully Treble-ready with "Treble enabler" option in order to repartition safely the device.
Features:
TWRP fully Treble-ready;
Maintained with latest TWRP version;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
USB-OTG fixed
Has 'TWRP survival' function for automatically re-installing TWRP recovery when installing ROMs and kernels;
Adds a "Treble enabler" option that allows you to repartition your device in order to support Treble.
Has the option to shrink userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
If you shrink Userdata, it will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Instructions
Flash the recovery.
Reboot Recovery
Optional - Use the "Advanced > Treble enabler" option for repartition option.
If you opted to repartition for Treble, you are ready to flash a Treble ROM/Vendor pack.
About TWRP survival
TWRP survival is a simple hook that detects if a boot.img will be installed and restores TWRP after it's flashed. This only works if you have booted TWRP with Tissot Manager 2.0 from a real recovery boot - NOT from a recovery 'hot boot' (fastboot boot method).
You will see in the install log if a TWRP survival attempt is successful in the flash text output.
Automatic TWRP survival works when:
Flashing a ROM ZIP (or AIO) with TWRP
Flashing a boot.img in TWRP "Install Image" mode
Automatic TWRP survival does NOT work when:
Flashing a boot.img via fastboot
Restoring boot in a TWRP backup
Any other way of flashing a boot.img
In these cases, be sure the use the TWRP Installer immediately after flashing or restoring a backup - otherwise you may get the device into a confused state (especially if you restore a non-TWRP boot then try to install an AIO ROM without installing a new TWRP first).
Download
https://zenfone3-dev.gitlab.io/recovery/twrp-treble/
FAQ
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) My PC can't see the MTP (storage) device from TWRP!
A) For dualboot compatibility, MTP is automatically disabled at various points. Just enable it manually in the Mounts menu to get access.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes!
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM.
Thanks to:
@CosmicDan for his files for Tissot Manager & this thread template
@makorn645, @planet9, @Oki for Party
XDA:DevDB Information
TWRP Recovery for Zenfone 3, Tool/Utility for the Asus ZenFone 3
Contributors
Giovix92, makorn645,
Source Code: https://github.com/Giovix92/android_device_asus_zenfone3/tree/twrp-8.1
Version Information
Status: Stable
Current Stable Version: 20190312
Stable Release Date: 2019-03-12
Created 2019-03-12
Last Updated 2019-03-12
@Giovix92 Does this mean I can use any ROM that is Treble? Or have some restrictions.
dVinsmoke said:
@Giovix92 Does this mean I can use any ROM that is Treble? Or have some restrictions.
Click to expand...
Click to collapse
Just the treble los16 zenfone3 on our forum for now
iamROOTX said:
Just the treble los16 zenfone3 on our forum for now
Click to expand...
Click to collapse
But then I see no difference from a "normal" ROM ported specifically to a device. Should not Treble support be able to use them on several different devices?
For example, should not I be able to go to the AEX Treble download area and use it on ZF3? If it would not be the same as having to wait for a dev port AEX to ZF3.
I'm really confused lol
dVinsmoke said:
But then I see no difference from a "normal" ROM ported specifically to a device. Should not Treble support be able to use them on several different devices?
For example, should not I be able to go to the AEX Treble download area and use it on ZF3? If it would not be the same as having to wait for a dev port AEX to ZF3.
I'm really confused lol
Click to expand...
Click to collapse
What do you expect? It's still in an early stage of porting. Some device specific bits still run from /system. GSI's may work but I doubt anything will work properly.
And I don't plan of supporting GSIs anyway.
makorn645 said:
What do you expect? It's still in an early stage of porting. Some device specific bits still run from /system. GSI's may work but I doubt anything will work properly.
And I don't plan of supporting GSIs anyway.
Click to expand...
Click to collapse
Being sincere I did not expect anything, since I did not understand anything lol This Treble left me was confused lol
So what's the difference of the Lineage Treble for a Lineage normal running in ZF3?
dVinsmoke said:
Being sincere I did not expect anything, since I did not understand anything lol This Treble left me was confused lol
So what's the difference of the Lineage Treble for a Lineage normal running in ZF3?
Click to expand...
Click to collapse
Currently nothing much ( updated proprietary bits + vendor image taken in place )
Maybe in the near future when everything is in place. I'll seperate Vendor image from builds ( noticable smaller updates )
makorn645 said:
Currently nothing much ( updated proprietary bits + vendor image taken in place )
Maybe in the near future when everything is in place. I'll seperate Vendor image from builds ( noticable smaller updates )
Click to expand...
Click to collapse
Also, when vendor img will be split from the ota package, with (if necessary) some adjustments we can flash GSI ROMs easily.
Great work guys!! Waiting for vendor partition, for some tests!
Williknot said:
Great work guys!! Waiting for vendor partition, for some tests!
Click to expand...
Click to collapse
Well, repartition works fine. After repartition a new /vendor partition of 1024mb will be made.
Although, you'll loose your data (apps+personal). So make sure to do a full backup of your device.
Feedback:
* HAVE A BACKUP. This tool messes with your partition table and is still unstable. Your data partition can be resized to the wrong size.
Will come back after a few months to provide more feedback. Appreciate the work guys.
Works fine for me, data is correctly resized even with multiple changes from normal to treble and back...
Can't seem to wipe /cache partition.
Anyone knows why?
[QS said:
;79165451]Works fine for me, data is correctly resized even with multiple changes from normal to treble and back...
Can't seem to wipe /cache partition.
Anyone knows why?
Click to expand...
Click to collapse
A bugfix release will be coming along with the next LineageOS build.
fcbn98 said:
Feedback:
* HAVE A BACKUP. This tool messes with your partition table and is still unstable. Your data partition can be resized to the wrong size.
Will come back after a few months to provide more feedback. Appreciate the work guys.
Click to expand...
Click to collapse
Well, that's normal.
Since you're going to make a new /vendor partition of about 1024mb, /data should be deleted & recreated in order to give some space to the new partition.
Also, what do you mean with "can be resized to the wrong size"?
The tool is pretty stable tho. Can you give more info such as model (ex. ZE552KL 4/64), script version (ex. 4.3b) & other?
Thanks.
I've successfully installed this tool, although attempting to install the new LOS 16 Android 9 ROM we have on this forum results in an error: 7, "Failed to mount '/vendor' (Invalid argument)"
From what I've perused so far in my research, that error mostly crops up on non-treble builds of TWRP, yet I definitely used the latest version from your website. I also redownloaded the latest version of LOS just to recheck, and yep, nothing's changed.
Any clue about what's going on here? I don't know much about Treble ROMs, or custom ROMing to be all honest.
EDIT: I have found the enable Treble option. Even when enabled and installed, after reboot, the /vendor partition cannot be read. It seems that after doing this too, I can't load files over USB, or mount my SD Card. I'm getting pretty confused as to what's happening. I can't boot into system, and fastboot won't connect to my PC.
Kaisogen said:
I've successfully installed this tool, although attempting to install the new LOS 16 Android 9 ROM we have on this forum results in an error: 7, "Failed to mount '/vendor' (Invalid argument)"
From what I've perused so far in my research, that error mostly crops up on non-treble builds of TWRP, yet I definitely used the latest version from your website. I also redownloaded the latest version of LOS just to recheck, and yep, nothing's changed.
Any clue about what's going on here? I don't know much about Treble ROMs, or custom ROMing to be all honest.
EDIT: I have found the enable Treble option. Even when enabled and installed, after reboot, the /vendor partition cannot be read. It seems that after doing this too, I can't load files over USB, or mount my SD Card. I'm getting pretty confused as to what's happening. I can't boot into system, and fastboot won't connect to my PC.
Click to expand...
Click to collapse
Did you follow these steps properly?
https://zenfone3-dev.gitlab.io/tutorials/repartition
can i flash android q gsi images using treble recovery.
Switching back to stock rom
If I have made the treble partition using this recovery is there any way to go back to stock rom?
Avinash007 said:
If I have made the treble partition using this recovery is there any way to go back to stock rom?
Click to expand...
Click to collapse
Wipe vendor, data, cache, dalvik partition and flash any ROM normally.
Can i flash android Q gsi image using this recovery on ze520kl
{
"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 9 (pie), 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
Audio
FM radio
Torchlight
LED
USB and WLAN tethering
Fingerprint sensor
Broken
You tell me
Source code:
device : https://github.com/lenovo-devs/android_device_lenovo_TB8704, https://github.com/lenovo-devs/android_device_lenovo_tb-common
kernel: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953/tree/lineage-16.0
vendor: https://github.com/lenovo-devs/proprietary_vendor_lenovo
2020-03-20
Enable DT2W
Update Lineage code
mailru: lineage-16.0-20200320-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20200320-UNOFFICIAL-TB8704.zip
boot.img for TB-8704V: boot-los16.0-tb8704v-test20200320.img (source code)
Previous versions:
2019-12-27
Fixed fingerprint scaner issue
mailru: lineage-16.0-20191227-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20191227-UNOFFICIAL-TB8704.zip
boot.img for TB-8704V: boot-los16.0-tb8704v-test20200316.img (source code)
2019-12-25
Fixed OTG mode
enable target ttl for thethering with some operators
Updated Lineage code
mailru: lineage-16.0-20191225-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20191225-UNOFFICIAL-TB8704.zip
2019-08-11
Fixed insert/remove detection for 3.5'' headset plug
Updated Lineage code
mailru: lineage-16.0-20190811-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20190811-UNOFFICIAL-TB8704.zip
2019-07-14
Initial release
mailru: lineage-16.0-20190721-UNOFFICIAL-TB8704.zip
gdrive: lineage-16.0-20190721-UNOFFICIAL-TB8704.zip
How to install
You have to had TWRP installed from this thread TWRP and ROOT for Tab 4 8/10 (Plus) (TB-8704X/F/V,TB-X704L/F, TB-8504X/F, TB-X304L/F)
In TWRP clean Data if you coming from stock ROM and do Install of this ROM. If you have android 8 stock rom installed you have to format Data with data loss, because used encryption is incompatible with android 7.1
TB-8704V (Verizon)
If you have TB-8704V tablet, you have to additionaly flash boot.img from link above after rom intsallation. This tablet has some hardware differences from x and f and requires custom kernel to work,
Thanks
Big thank to @mistersixt, who donated $$ for device.
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0][tb8704f/x] LineageOS 16.0 for Lenovo TAB4 8 plus, ROM for the Lenovo Thinkpad Tablet
Contributors
highwaystar_ru
Source Code: https://github.com/lenovo-devs/android_kernel_lenovo_msm8953/tree/lineage-16.0-wip
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOs
Version Information
Status: Testing
Created 2019-07-21
Last Updated 2019-08-11
Installed it and everything seems to be working great. Many thanks for your work
Can't seem to get it boot on tb8704v (boot loop). I have unlocked rebooted and made sure oem unlock was still checked and installed twrp-3.2.3-0-tb_8704v and then installed rom and gapps. But it just boot loops on restart. I'm missing something?
Thank you so much for all your hard work.
I am unable to install gapps, its stuck on "mounting /persist /system" is there any work around?
wow! can't wait to flash this! thanks so much!
Just noticed in the OP you have "ROM OS Version: 7.x Nougat" Don't you mean 9.x?
Clean installed but stuck on lineage logo, any suggestion? Previously installed L14.1 without issue.
Acel337 said:
Clean installed but stuck on lineage logo, any suggestion? Previously installed L14.1 without issue.
Click to expand...
Click to collapse
Are you on tb8704f?
hunnia41 said:
Are you on tb8704f?
Click to expand...
Click to collapse
Yes, I'm on TB-8704F. Previously installed 14.1 without issue.
Did a clean install: format DATA and cache; again tried with clearing SYSTEM folder as well.
After installing, reboots as normal thenstuck on Lineage ARC loading with no end; left it alone for 30mins but never load into OS.
Acel337 said:
Yes, I'm on TB-8704F. Previously installed 14.1 without issue.
Did a clean install: format DATA and cache; again tried with clearing SYSTEM folder as well.
After installing, reboots as normal thenstuck on Lineage ARC loading with no end; left it alone for 30mins but never load into OS.
Click to expand...
Click to collapse
I did the same . but I had stock 8.1 installed. I installed mindthegapps as well as the ROM and rebooted and everything seems to be working fine.
I also had 14.1 installed before. Unfortunately I have the same problem as Acel337. I have the tb8704x.
Has anyone found a solution yet?
14.1 starts without problems after flashing again.
I dirty flashed over los 14. Then flashed openGapps 9 pico. Then reflashed the latest magisk. ROM boots after about 5 minutes without any issues.
Chrome reloads on occasion. I have root, don't have rw. The remount script doesn't work. Netflix casts well. That's as far as I've got.
Thank you for this!
Update: rw now working
Acel337 said:
Yes, I'm on TB-8704F. Previously installed 14.1 without issue.
Did a clean install: format DATA and cache; again tried with clearing SYSTEM folder as well.
After installing, reboots as normal thenstuck on Lineage ARC loading with no end; left it alone for 30mins but never load into OS.
Click to expand...
Click to collapse
For me evrythin works
8.0 stock rom
install magisk
install twrp
system writable
erase system data.
sideload pie and gapps.
Everyhing works perfectly.
Maybe the difference, that I started from 8.1 stock
Just a thought. It could be, that indirectly the (wrong) encryption cause the problem. Since when booting, the program tries to populate the data partition, and if it cannot do it, since it appears as 0 storage, it might just stuck in a loop.
How do you get /system to be writable?
Installed from stock 8.0 plop to Los16 with Pico gapps. Format data - reboot to recovery then continue with flash procedures (wipe system/cache dalvik etc) I'll be sending a Donation over the next day or so. Having LineageOS for this device is an absolute GodSend @drizzle123 flash the remount rw magisk.zip. I had problems with it previously on stock roms but it seems to be working ok atm fingers crossed. (here's link to post/file) https://forum.xda-developers.com/showpost.php?p=77781453&postcount=1014
Hemphiz said:
Installed from stock 8.0 plop to Los16 with Pico gapps. Format data - reboot to recovery then continue with flash procedures (wipe system/cache dalvik etc) I'll be sending a Donation over the next day or so. Having LineageOS for this device is an absolute GodSend @drizzle123 flash the remount rw magisk.zip. I had problems with it previously on stock roms but it seems to be working ok atm fingers crossed. (here's link to post/file) https://forum.xda-developers.com/showpost.php?p=77781453&postcount=1014
Click to expand...
Click to collapse
"I'll be sending a Donation "
I did too. The first time in my life for firmware. I have no problem so far. (Used it 24 hours.)
---------- Post added at 06:51 AM ---------- Previous post was at 06:34 AM ----------
Acel337 said:
Yes, I'm on TB-8704F. Previously installed 14.1 without issue.
Did a clean install: format DATA and cache; again tried with clearing SYSTEM folder as well.
After installing, reboots as normal thenstuck on Lineage ARC loading with no end; left it alone for 30mins but never load into OS.
Click to expand...
Click to collapse
Seemingly you did everything, which had to be done. If it is a problem with the firmware, maybe it has to do with the encryption. (Cannot encrypt the data.) Just a guess, since it works for so many people.
maybe you should reflash the 8.1 stock rom. If it works, try again to reinstall lineage pie. If it still fails, go back to stock until problem is solved.
The tablet was on latest official 8.1 then changed to LineageOS 14.1. Tried to install to this 16.0 then this issue started.
I have sucessfully installed 14.1 but not to latest 16.0. It's a strange issue.
Could we get some gamepads working up on this mofo please? That would be the Cherry
same here, TB-8704F stuck on lineage bootanimation too
Acel337 said:
The tablet was on latest official 8.1 then changed to LineageOS 14.1. Tried to install to this 16.0 then this issue started.
I have sucessfully installed 14.1 but not to latest 16.0. It's a strange issue.
Click to expand...
Click to collapse
coming from latest 8.1 (TB-8704F_S0010xx_190606_ROW with security update from April 5th) doing the following:
- installed recovery: fastboot flash recovery twrp-3.2.3-0-tb_8704x.img
- booted into recovery and format /data
- again rebooted recovery and wiped /system, /data /cache and /dalvik
- installed "lineage-16.0-20190721-UNOFFICIAL-TB8704.zip" , directly afterwards "open_gapps-arm64-9.0-pico-20190720.zip"
Now, TB-8704F stuck on bootanimation
robidick said:
coming from latest 8.1 (TB-8704F_S0010xx_190606_ROW with security update from April 5th) doing the following:
- installed recovery: fastboot flash recovery twrp-3.2.3-0-tb_8704x.img
- booted into recovery and format /data
- again rebooted recovery and wiped /system, /data /cache and /dalvik
- installed "lineage-16.0-20190721-UNOFFICIAL-TB8704.zip" , directly afterwards "open_gapps-arm64-9.0-pico-20190720.zip"
Now, TB-8704F stuck on bootanimation
Click to expand...
Click to collapse
I did exactly the same thing with the following exceptions. (whether they are significant or not I do not know.
1. Went into twrp without installing it and unrooted with Magisk. (side load)
(Then I do not remember whether I booted up in stock, to check by magisk whether dm-verify was off. It should be)
then I rebooted into fastboot and installed twrp and in my case I made system writable.
After this I proceeded as you discribed.
{
"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"
}
DISCLAIMER
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you
I've put a huge amount of time and effort in this SOLO project (no other dev has been involved), so respect me and respect my work. You are NOT allowed to use this rom, its vendor or any of the other files included as base for your projects.
FEATURES
OneUI 2.0 under Android 10, ported from the SM-A750FN
All G610 variants should be supported
Arm64 with Treble support
Fully deodexed
SIMPLE-KERNEL included, compiled from A600FNXXU5CTB9 sources. Built permissive
Deknoxed, debloated, and removed all samsung useless security stuff in rom and kernel level
N20 multi CSC with additional features (call recording, etc)
And many more!
KNOWN BUGS
Light in capacitive buttons for those devices with hardware buttons
Some 3rd camera apps like footej don't work. Whatsapp video calls could be bugged too. If so, use Whatsapp business
Other inherent bugs from OneUI and/or 7870 limitation
You tell me
DOWNLOAD
Current version: 6.0 (02/12/2020)
More info in 2nd post
INSTALLATION
Vendor partition is required.
Wipe system, data (clean install mandatory), vendor, dalvik&cache and cache
Flash rom zip
Reboot
First boot will take much time, be patient
SCREENSHOTS
https://imgur.com/a/Q5Ysvoz
ROOT
Flash Magisk canary. Stable Magisk will give bootloop.
SUPPORT
Telegram group
CREDITS
Me, for infinite hours spent with this project
Special thanks to @ananjaser1211, @SPARTANICUS and @Valera1978 for their huge contribution to the 7870 development
Thanks to my testers and @neel0210 for camera rework
And thanks one more time to @SaiFurR for his design work with banner
@topjohnwu for Magisk
DONATIONS
I don't need them, I don't need coffees or beers. I really hate see here people with high end devices asking for donations, but you can still donate money to charity. Donate money or simply help people that is really needed. If you like this rom you can make me very happy just pushing THANKS
XDA:DevDB Information
H-ROM A7 PORT, ROM for the Samsung Galaxy J7
Contributors
Astrako
Source Code: https://github.com/samsungexynos7870/android_kernel_samsung_exynos7870/tree/simple_q_permissive
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Oreo bootloader
Version Information
Status: Stable
Current Stable Version: 4.0
Created 2020-07-19
Last Updated 2020-08-27
H-ROM A7 PORT V6.0 (02/12/2020)
November security patch
Fixed Dual sim detection
Added High Perfomance mode
Setting volume in different apps should be fixed
You will need around a 3100Mb system partition, so if you dont have it, go and flash my repartition script
GoogleDrive folder
Mega
Md5: a9f3cacee034142024fd2802eed21b61
Spoiler: Old versions
H-ROM A7 PORT V5.0 (27/08/2020)
Spoiler: Old versions
Firmware ported from A750FNXXU4CTG2. July security patch
Added SIMPLE kernel
Echo in calls should be fixed. Other minor bugs can be present depending the phone/variant
You will need around a 3100Mb system partition, so if you dont have it, go and flash my repartition script
GoogleDrive folder
Mega
Md5: 87fc5ef5c031a2f586d762debcf7b3e0
Added a navbar enabler/disabler to the download folder
H-ROM A7 PORT V4.0 (19/07/2020)
Firmware ported from A750FNOXM4CTE3. June security patch
Specifig bugs: echo in calls
GoogleDrive folder
https://drive.google.com/drive/folders/13UG-hdqWU8nud1JCm6DD0vQXAQjeJCVP
Remember, a lot of time has been put in this project. If you like it and want to support me, no donations at all are required, just pushing thanks buttons.
Reserved
Great job
what is vendor partition? can you explain more detail? this is the first time im going to try treble rom. i dont understand what is vendor partition (what is that? is it a flashable file? or what?)
leo31 said:
what is vendor partition? can you explain more detail? this is the first time im going to try treble rom. i dont understand what is vendor partition (what is that? is it a flashable file? or what?)
Click to expand...
Click to collapse
Vendor partition is a partition that comes with treble supported phones j7 isnt one of them but with project spaget you can enable treble support on our phone so that it can install treble roms. To get the vendor partition got to this link and download the latest version (spaget x) and flash create vendor 2.0 and you will have a vendor partition.
which kernal is install ? .... i have downloaded h20 rom for g610f but i face some problem such as phone stuck and reboot automatically.... so i need to know whick kernal is installed......
Great work on the ROM
Kindly help with a working SIM Toolkit zip file for this ROM. Or anybody with a working SIM Toolkit zip file can help me with it. Thanks.
HELP! no me deja hacer vídeos llamadas en ws, en j7 prime
won't let me make video calls on
facing random reboot twice on setup screen, now it boot. no flash light on camera (light burst from screen?) like stock oreo.
hyperlapse - wide selfie nor working
i dont even know what is hyperlapse
@Astrako will you keep H-ROM A7 and S20 versions support simultaneously?
Adriano-A3 said:
@Astrako will you keep H-ROM A7 and S20 versions support simultaneously?
Click to expand...
Click to collapse
Don't ask ?... just install the rom and enjoy bro
Mscreams said:
Don't ask ... just install the rom and enjoy bro
Click to expand...
Click to collapse
Bruh
I can't install it please get me a complete manual for install
With spaget x project get bootloop l
Without show logo cant boot
Recovery: Orange Fox
Vendor 2
G610f/ds
use vendor create v1 not v2
yahiaashraf111 said:
use vendor create v1 not v2
Click to expand...
Click to collapse
And don't need change recovery ?
Now it's OrangeFox based twrp 3.4.0
Should install spaget x?
What working :
1. Wifi
2. Mobile data
3. Hotspot
4. Bluetooth
5. Gps
6. Camera
7. Phone
8. Live drawing camera
9. screen recording
10. Almost everything are working well
But, so far i found some 'not so important' bugs :
1. Opening battery usages give me FC.
2. I cant rename, remove files inside priv-app folder, but copying files to folder inside priv-app worked.
3. Removing app which located on priv-app folder using titanium backup, did not removed the apps. After reboot, the apps are there again. (Problem number 2, i cant remove apk inside priv-app)
4. no blue-light filter (i dont use it, so i dont care)
5. Some camera feature not working (hyperlase, wide selfie, front facing camera only support 4:3 size for taking photo, but video are fine). I dont know what is the function of icon at the right side of resolution inside camera (right side of 4:3 icon)
6. Since aod is not working and im not using it, better remove it.
7. Cant change clock style on lockscren (inside phone setting), but fixed by installing lockstar
8. Screen mode inside display setting has no effect at all (even stock rom does not have that feature, so.... No problem at all)
I really love this rom! Why? Because :
1. Battery life is PERFECT
2. Performance? This rom is running perfectly smooth on UI, and also while playing game and opening apps.
3. Multitasking is great
4. Android Q on 2016 device? Hell yeah.
Please fix the 1st and 2nd problem, because i need to replace gametool apk inside priv-app folder.
Installation variant 610mn-16gb
Installation variant 610mn-16gb
1- Have prepared the Vendor.zip and revertvendor files specifically this => Spaget Treble ARM64 Vendor V3.0 Based on A750FN Vendor <= not vendor v2.0 and it is not necessary to download Exynos7870_Spaget_X-V3.0. If you want root, download the magisk provided on the first page. Also have OrangeFox-R10.1_2-Unofficial-on7xelte and a version of a preferable rom oreo available to reverse the vendor and reinstall for anything.
2- Before flash create vendor, install OrangeFox-R10.1_2-Unofficial-on7xelte and restart fox recovery, then flash create vendor, without deleting anything and restarting recovery, once in TWRP-Fx, follow the steps on the first page , wipe 1DC, 2C, 3S, 4V, 5D. Internal memory is not necessary (if you view the preload between the partitions, in this step, read notes below), once the wipe has finished, install the ROM and restart. Everything should work perfectly, (at the end of the startup, perform a hard restart before configure, and then it starts without problems, that happened to me, in particular, since generally when finishing the installation of the ROM and when rebooting it usually restarts again, in this case it did not, I start directly until hello .. and then reboot)
3- Optional, once the startup is configured, restart TWRP-FX and flash magisk.
Notes: At the beginning, you could not install any ROMx64, or you needed the vendor partition, you can check the following: when you install TWRP 3.3 and when you start TWRP, the following appears in red letters at the top: “recovery is not seandroid enforcing… .. etc ”it only comes out with twrp from version 3.3, definitely you will not be able to install any rom x64, gsi, etc, since you don't have to get any errors or messages. It means that also like mine you have the smartphone since marshmallow 6.0 and it was root with supersu and odin, and you were making updates from that version; solution: restore with stock Firmware android 8.1 via odin all the partitions (BL-AP-CP-CSC-USERDATA) can be found on the network and downloaded according to your country, but always being oreo stock 8.1. Once this is done, install TWRP 3.2 with odin and then root with magisk latest stable version, not the one provided here. After that, you will be able to install several roms that you could not previously and will not have problems with the vendor, create and revert if you want. Some only install the AP to fix, but I decided on a full restore and start from scratch.
PD: I felt the need to share this experience with you so that those who have the 610mn and have problems can install it without problems, always remember to back up your important data before flashing and having a good battery charge *GOOGLE TRANSLATE*
RODRI2688 said:
Installation variant 610mn-16gb
1- Have prepared the Vendor.zip and revertvendor files specifically this => Spaget Treble ARM64 Vendor V3.0 Based on A750FN Vendor <= not vendor v2.0 and it is not necessary to download Exynos7870_Spaget_X-V3.0. If you want root, download the magisk provided on the first page. Also have OrangeFox-R10.1_2-Unofficial-on7xelte and a version of a preferable rom oreo available to reverse the vendor and reinstall for anything.
2- Before flash create vendor, install OrangeFox-R10.1_2-Unofficial-on7xelte and restart fox recovery, then flash create vendor, without deleting anything and restarting recovery, once in TWRP-Fx, follow the steps on the first page , wipe 1DC, 2C, 3S, 4V, 5D. Internal memory is not necessary (if you view the preload between the partitions, in this step, read notes below), once the wipe has finished, install the ROM and restart. Everything should work perfectly, (at the end of the startup, perform a hard restart before configure, and then it starts without problems, that happened to me, in particular, since generally when finishing the installation of the ROM and when rebooting it usually restarts again, in this case it did not, I start directly until hello .. and then reboot)
3- Optional, once the startup is configured, restart TWRP-FX and flash magisk.
Notes: At the beginning, you could not install any ROMx64, or you needed the vendor partition, you can check the following: when you install TWRP 3.3 and when you start TWRP, the following appears in red letters at the top: “recovery is not seandroid enforcing… .. etc ”it only comes out with twrp from version 3.3, definitely you will not be able to install any rom x64, gsi, etc, since you don't have to get any errors or messages. It means that also like mine you have the smartphone since marshmallow 6.0 and it was root with supersu and odin, and you were making updates from that version; solution: restore with stock Firmware android 8.1 via odin all the partitions (BL-AP-CP-CSC-USERDATA) can be found on the network and downloaded according to your country, but always being oreo stock 8.1. Once this is done, install TWRP 3.2 with odin and then root with magisk latest stable version, not the one provided here. After that, you will be able to install several roms that you could not previously and will not have problems with the vendor, create and revert if you want. Some only install the AP to fix, but I decided on a full restore and start from scratch.
PD: I felt the need to share this experience with you so that those who have the 610mn and have problems can install it without problems, always remember to back up your important data before flashing and having a good battery charge *GOOGLE TRANSLATE*
Click to expand...
Click to collapse
Hello
Thanks for your help
This installation help isn't for F variant?
SyntaxDroid said:
Hello
Thanks for your help
This installation help isn't for F variant?
Click to expand...
Click to collapse
Really if it could work, especially if you have been making updates from android v6, it is best to start the root from android v8.0 or 8.1, once achieved, try the installation, but if you already come from that version, you shouldn't have drawbacks. Try it, it's really worth it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
*
*/
Introduction
LineageOS is a free, community built, aftermarket firmware distribution of Android 12 (S), 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.
Bugs
What's working:
Boot
Bluetooth
Camera / Camcorder
DT2W
FM Radio
Torch
RIL (DATA/Call/SMS)
WiFi
WiFi Hotspot
USB (ADB/MTP/PTP)
NFC
LED lights
Sensors
GPS
Audio Playback
Video Playback
Touch screen
ExFAT SDCard
What's not working:
SELinux is permissive
You tell me.
Installation instructions
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe system / data / cache partitions
Flash ROM.
Optional: Install the Google Apps addon package.
Optional: Install Magisk for Root.
Supported models:
C6602,C6603,C6606
Downloads
Recovery : Official TWRP
Gapps : MindTheGapps 12.1
Magisk (Flash under TWRP): Unofficial Flashable APK
Rom : Download
Sources
Device/Kernel/Vendor Tree: Sources
Donate
DONATE To Me
Big Thanks
LineageOS Team.
all fusion3-common / apq8064 contributors.
@ CyberWalkMaN
@ AdrianDC
@ Chippa_a
Changelogs
2022/08/08
Updated with August security patches.
Upstream updates and fixes.
2022/07/14
Fixed NFC options.
2022/07/13
Updated to Android 12.1.0_r11 with July security patches.
Upstream updates and fixes.
2022/06/14
Updated to Android 12.1.0_r7 with June security patches.
Upstream updates and fixes.
2022/05/13
Updated to Android 12.1.0_r5 with May security patches.
Upstream updates and fixes.
2022/04/08
Updated to Android 12.1.0_r4 with April security patches.
Updated stock app icons.
Upstream updates and fixes.
2022/03/20
Updated to Android 12L with March security patches.
Updated to LineageOS 19.1.
Upstream updates and fixes.
Clean flash recommended.
2022/02/28
Bring back FM Radio.
Bring back Proximity sensor wake up settings for Doze.
2022/02/15
Fixed Camera/Camcorder
Fixed WiFi WPA3 connection issues.
2022/02/14
Initial release of LineageOS 19.0 for Xperia Z.
Screenshots
just flash 18.1 yesterday ，thanks for the new rom.
New build released
Fixed Camera/Camcorder
Fixed WiFi WPA3 connection issues.
thanks for the work. It make my old devices new
New build released
Bring back FM Radio.
Bring back Proximity sensor wake up settings for Doze.
no mirrors found on latest build unfortunately
nyapinkid said:
no mirrors found on latest build unfortunately
Click to expand...
Click to collapse
Re-uploaded.
tarkzim said:
Re-uploaded.
Click to expand...
Click to collapse
my compass acting weird on latest build, iits normal on stock 5.1 tho
no mirrors found for the last build
Thanks for building this rom.
It works faster than LineageOS 18 in my xperia c6603 but need somethings to be fixed:
- after succefully install the rom, we can't boot into TWRP recovery by using adb reboot recovery or by using power button and volume up botton during the boot, It only reboot and reboot to normal boot after passed a black screen in few second. For rooting the rom, need to go to the TWRP recovery. So that I flash the boot by Leneage18 boot.img in the bootloader mode and I use adb shell , dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot to restore the boot of Lineage19 then install magisk.apk.zip at the recovery and reboot.
- The manual network selection still not work.
Sorry for my bad english.
On 6603 do not booting... Stuck on boot logo and reboot repeatedly neverending.
Access to recovery with VolUp if LED in booting is not accessible. I am must sending boot.img to device from PC.
truefriendcz said:
On 6603 do not booting... Stuck on boot logo and reboot repeatedly neverending.
Access to recovery with VolUp if LED in booting is not accessible. I am must sending boot.img to device from PC.
Click to expand...
Click to collapse
You must to verify the format of all partition in twrp by flashing the boot, replace the boot by twrp.img , if you use f2fs It stuck on boot maybe this rom don't support f2fs. You have to backup your data and format all partition to ext4 then install the rom. It work fine for mine .
Two days. Please reupload.
SeraOne said:
You must to verify the format of all partition in twrp by flashing the boot, replace the boot by twrp.img , if you use f2fs It stuck on boot maybe this rom don't support f2fs. You have to backup your data and format all partition to ext4 then install the rom. It work fine for mine .
Click to expand...
Click to collapse
TWRP:
/cache ext4
/system_root ext4
/data ext4
/external_sd vfat and zero all (no inserted Micro card)
Internal Storage: invalid partition selection
Dalvik Cache: invalid partition selection
Edit: After tree reboots sucesfully boted into Android. But TWRP is not accessible.
truefriendcz said:
TWRP:
/cache ext4
/system_root ext4
/data ext4
/external_sd vfat and zero all (no inserted Micro card)
Internal Storage: invalid partition selection
Dalvik Cache: invalid partition selection
Edit: After tree reboots sucesfully boted into Android. But TWRP is not accessible.
Click to expand...
Click to collapse
Same for me I cannot access TWRP anymore. I have tried to flash it again but it still does not want to boot to twrp after that.
New build released
Updated to Android 12L with March security patches.
Updated to LineageOS 19.1.
Upstream updates and fixes.
Clean flash recommended.
Thanks, tarkzim
You've made this Sony Xperia Phone a New phone again. Good job
Clean installed, formatted all partitions including internal DATA.... I've installed the latest LineageOS 19.1, but the GAPPS installation fails and says Android SDK version are not compatible.
Maybe because this build is Android 12.1 but those GAPPS are still Android 12.0 so it's not available yet. I've tested both BiTGApps MindTheGapps. any ideas? I do think this phone is 32-bit ARM.
I've also trouble to have both OS and recovery, I did extract twrp.img to FOTA partition in twrp recovery, after OS install, I wanted to boot recovery in lineageOS by using adb reboot recovery, the phone reboots two times Sony with few 5 seconds with first orange blink, looks it refuses to boot recovery? and the second boots to lineageos again with a purple blink.
So what've figured, if I want to go back to Recovery, I need to enter Fastboot to flash twrp to get into recovery, and to get back normal I should either install full OS or just I simply unzip the "boot.img" from you've installed OS zip.
I was in latest version firmware 10.7.A.0.222
Peace,
iPlasm said:
Thanks, tarkzim
You've made this Sony Xperia Phone a New phone again. Good job
Clean installed, formatted all partitions including internal DATA.... I've installed the latest LineageOS 19.1, but the GAPPS installation fails and says Android SDK version are not compatible.
Maybe because this build is Android 12.1 but those GAPPS are still Android 12.0 so it's not available yet. I've tested both BiTGApps MindTheGapps. any ideas? I do think this phone is 32-bit ARM.
I've also trouble to have both OS and recovery, I did extract twrp.img to FOTA partition in twrp recovery, after OS install, I wanted to boot recovery in lineageOS by using adb reboot recovery, the phone reboots two times Sony with few 5 seconds with first orange blink, looks it refuses to boot recovery? and the second boots to lineageos again with a purple blink.
So what've figured, if I want to go back to Recovery, I need to enter Fastboot to flash twrp to get into recovery, and to get back normal I should either install full OS or just I simply unzip the "boot.img" from you've installed OS zip.
I was in latest version firmware 10.7.A.0.222
Peace,
Click to expand...
Click to collapse
- MindTheGapps 12.1 should be able to be flashed on 12L?
- For reboot-to-recovery feature, I also facing the same thing as yours, no solutions for now
and I'm also flashing twrp before installing new ROM builds.
{
"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"
}
Notes:
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for metadata encryption (which causes mounting errors in log)
Downloads:
twrp_3.7.0_12-2_X200XXS1CWA3.tar.md5
twrp_3.7.0_12-2_X200XXS1CWA3.img
Change Log:
v3.7.0_12-2 (2023-02-28):
Updated to X200XXS1CWA3 (Android 13) OEM stock kernel (Jan 2023 Update).
v3.7.0_12-1 (2023-01-22):
Updated to X200XXU1CVL5 (Android 13) OEM stock kernel (Dec 2022 Update).
v3.7.0_12-0 (2023-01-01):
Fixed issue with MTP sometimes not starting until state is toggled in the Mount panel.
Switched to TWRP 3.7.0 release built from new AOSP-12.1 branch.
Updated to X200XXS1BVJ1 (Android 12) OEM stock kernel (Oct 2022 Security Update).
v3.7.0_11-1 (2022-10-24):
Adjusted dynamic partition size and removed redundant backup image.
v3.7.0_11-0 (2022-10-09):
Updated to TWRP 3.7.0 release built from AOSP-11 branch.
Updated to X200XXU1BVI6 (Android 12) OEM stock kernel.
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
v3.6.2_11-0 (2022-09-04):
Initial TWRP 3.6.2 release built from AOSP-11 branch.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to Recovery
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch the boot.img file. More details on this process are available here. Note that you should just patch the boot.img file and not the whole AP tarball, since this device's bootloader doesn't like the empty vbmeta.img that Magisk will provide.
Source:
android_device_samsung_gta8wifi
Donations:
Your support is always appreciated! Just click here.
Additional Notes:
Ian's Multidisabler script has an issue on this device preventing it from disabling stock recovery auto-restoration. I'm hoping that a fix is forthcoming.
If you root this device with Magisk, be sure to patch only the boot.img file. Patching the AP tarball will generate a blank vbmeta.img, which this device's bootloader doesn't like for some reason.
Works on LTE version sm-x505 ??
Also which is better tab A7 or tab A8 ??
works perfectly. what i did was after rooting with magisk, i downloaded the official twrp app from playstore and downloaded your img to my tab. then i just flashed it from within the app. no issues.
Magendanz said:
Notes:
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this impressive tablet.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for metadata encryption (which causes mounting errors in log)
MTP doesn't start until you disable and reenable in the Mount panel
Downloads:
twrp_3.6.2_11-0_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-0_X200XXU1AVG1.img
Change Log:
v3.6.2_11-0 (2022-09-04):
Initial TWRP 3.6.2 release built from AOSP-11 branch.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to Recovery
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch the boot.img file. More details on this process are available here. Note that you should just patch the boot.img file and not the whole AP tarball, since this device's bootloader doesn't like the empty vbmeta.img that Magisk will provide.
Source:
android_device_samsung_gta8wifi
Donations:
Your support is always appreciated! Just click here.
Click to expand...
Click to collapse
I am so delighted to see that there is major development for this device.
This will open the door for future custom ROMs.
Thank you Magendanz for your effort in bringing this to us.
I can say that is working as expected, thank you so much man. I thought that with TWRP we could be able to install a GSI ROM at least, but nothing at all lol
Tony Ronaldo Matute said:
I can say that is working as expected, thank you so much man. I thought that with TWRP we could be able to install a GSI ROM at least, but nothing at all lol
Click to expand...
Click to collapse
I think it's possible, but just using ChonDow_Flasher didn't work for me...I suspect because the bootloader isn't seeing an AVB hash footer on the GSI image. I had a similar experience when I built TWRP without the hash footer.
Unfortunately, I'm getting a segmentation error when trying to add a hash footer to the GSI using avbtool. It's probably a partition size issue, but I haven't had the time to troubleshoot.
Magendanz said:
I think it's possible, but just using ChonDow_Flasher didn't work for me...I suspect because the bootloader isn't seeing an AVB hash footer on the GSI image. I had a similar experience when I built TWRP without the hash footer.
Unfortunately, I'm getting a segmentation error when trying to add a hash footer to the GSI using avbtool. It's probably a partition size issue, but I haven't had the time to troubleshoot.
Click to expand...
Click to collapse
I had tried different ways also but I give up, the only thing that I can think now is try to use the "reboot to bootloader" feature in TWRP. But well, this processor is going me crazy.
Magendanz said:
Reserved
Click to expand...
Click to collapse
Once we get TWRP can't we just flash Magisk's zip file within TWRP like normally we do?
Also, after restart the tablet, when I tried to get back into TWRP it took me back to Android regular recovery. I had to flash TWRP again using Odin, after enabling MTP, local storage doesn't mount, I wasn't able to copy data in it.
zfk110 said:
Once we get TWRP can't we just flash Magisk's zip file within TWRP like normally we do?
Also, after restart the tablet, when I tried to get back into TWRP it took me back to Android regular recovery. I had to flash TWRP again using Odin, after enabling MTP, local storage doesn't mount, I wasn't able to copy data in it.
Click to expand...
Click to collapse
No, you should patch the boot.img using the Magisk app, then flash it using TWRP or pack in a tarball and use Odin. Don't patch the whole AP, as Magisk will substitute a blank vbmeta.img that the bootloader on this device doesn't like.
Rularick5 said:
works perfectly. what i did was after rooting with magisk, i downloaded the official twrp app from playstore and downloaded your img to my tab. then i just flashed it from within the app. no issues.
Click to expand...
Click to collapse
Was just going to try this method but I'm on AVC1...I'm assuming I need to be on AVG1?
As long as the binary number is the same, im assuming dont quote me, you should be able to flash avg1 then magisk then twrp. Just update to the latest firmware.
I figured that's what I had to do but was trying to avoid that....just rooted a week ago and had no idea about AVG1.
So if I want to upgrade to AVG1 or any other firmware in the future I have to do the whole process again of patching boot.img, flashing through Odin, factory reset and setting up everything again? There's no way to upgrade and retain root?
Not unless you can recieve ota while rooted.
New release is posted...
Downloads:
twrp_3.6.2_11-1_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-1_X200XXU1AVG1.img
Change Log:
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
Magendanz said:
New release is posted...
Downloads:
twrp_3.6.2_11-1_X200XXU1AVG1.tar.md5
twrp_3.6.2_11-1_X200XXU1AVG1.img
Change Log:
v3.6.2_11-1 (2022-09-11):
Fixed Fastboot Mode (fastbootd) so that dynamic partitions (system, product, vendor) can be managed in TWRP.
Click to expand...
Click to collapse
Any news for GSI?
Tony Ronaldo Matute said:
Any news for GSI?
Click to expand...
Click to collapse
I successfully tested fastbootd with OEM images, but the LineageOS GSI I tried was still getting kernel panics. I assume it has to do with this bootloader's AVB 2.0 requirements, which we can't seem to work around in the usual way with a blank vbmeta.img.
Magendanz said:
I successfully tested fastbootd with OEM images, but the LineageOS GSI I tried was still getting kernel panics. I assume it has to do with this bootloader's AVB 2.0 requirements, which we can't seem to work around in the usual way with a blank vbmeta.img.
Click to expand...
Click to collapse
"OEM images", so the Google GSI? Also, maybe could the vb meta zip disabler works?
Tony Ronaldo Matute said:
"OEM images", so the Google GSI? Also, maybe could the vb meta zip disabler works?
Click to expand...
Click to collapse
No, the OEM for this device is Samsung. Please provide a link for this vbmeta disabler, since I've just been using the ones generated by Magisk and my own using avbtool make_vbmeta_image --out vbmeta.img.
Magendanz said:
No, the OEM for this device is Samsung. Please provide a link for this vbmeta disabler, since I've just been using the ones generated by Magisk and my own using avbtool make_vbmeta_image --out vbmeta.img.
Click to expand...
Click to collapse
So, first you can try this disabler:
[Deprecated] Universal DM-Verity, ForceEncrypt, Disk Quota Disabler [11/2/2020]
Hi all! For the past couple of months, I've been looking into making a more universal solution to disable dm-verity and forceencrypt. Needing to take different zips, modify them for different devices, and then cross your fingers when you switch...
forum.xda-developers.com
as well, you can try to use this fastbootd command:
[Solved] VBmeta Flashing and Disable Verity Verification Command Problem
Thought to share with you guys, as many of people like me face problem while disabling the verification while flashing VBMETA.img. Most of the time the below command does not work and causes bootloop, when Installing Custom recovery. So i...
forum.xda-developers.com