[JDCTeam][TREBLE][v6 RC2][Gemini] The Full Treble support project - Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev

[JDCTeam][TREBLE][v6 RC2][Gemini] The Full Treble support project - Xiaomi Mi 5 ROMs, Kernels, Recoveries, & Other Dev

FAQ Section...
This is the FAQ (Frequently Asked Questions).
Have a look here before asking in the thread... in the worst case you will not find the answer you are searching!
If this section is useful for most users needs, I'll be glad to continue investing time to update this Q/A list!!
Q1:Fingerprint wake/home button works?
A: Yes, now we have the complete support and this feature is available on standard GSI roms (treble support is ready for it)
Q2: How can I revert back from treble to custom ROM whenever required?
A: Just flash the custom rom you like from TWRP and that's all. Custom rom flash will overwrite the boot.img,system and vendor partitions.
Q3: If I revert to a Custom rom, what I need to do to restore treble support?
A: Just flash the Treble zip through TWRP as the first time. Treble support need boot.img and vendor.img to be installed into the phone... nothing more... nothing less...
Q4: Phh GSI rom is quite poor in functionality. Why?
A: The purpose of Phh GSI AOSP rom is not to be a custom/featured rom. It is an experimental project that is born to have a common rom (better to say the same system.img) usable on many devices with treble support.
This support can be native, acquired after an Oreo original update or as we have done a custom integration on an "unsupported" device.
The meaning today of using a GSI rom is not to be a perfect rom for dayly use... or let's say, it can be a dayly rom only for users that like pure vanilla code.
In future we hope that many others custom roms will move to be a GSI (as JDC will try to do), so we will have the treble base to use these new project also on our devices.
Q5: If a new version of treble support is out, did I need to flash it or not?
A: Our project is on the way. This means that if is available a new update from us, it is for sure an enhancement with more support of feature or fixes.
In case you will need to install a GSI rom, check always here if there is any new version and get it.
In case you are running a custom rom without treble support, DO NOT update with treble flash, because most probably you will break your current installation.
Treble flash is 100% safe from the phone point of view... isn't safe for your current installation!! Why? Mainly because your current boot.img will be overwritten with treble support... 99% you will get a bootloop with a not treble rom!
Q6: How to get ROOT on phh gsi?
A: Firstly download the phh-gapps-su image. After installation, go to the market and install "phh superuser" app to manage the su access for the apps that need it. In the other cases, you can flash from TWRP the correct Magisk zip to gain root.
Q7: Where I can find the GSI images available?
A: Have a look in the OP post over here... there you can find the available ones. In any case here the LINK to the Treble Enabled Device Development section on XDA or here on GSI & sGSI List page
Q8: Everytime I entered the password, it says Decryption Unsuccessful!
A: You have internal SD encrypted. If after MIUI stock, you haven't FORMATTED the internal SD (FORMAT is not WIPE... Format will erase all data and files from the phone, so you must know what you are doing before formatting), the phone result as encrypted, so the rom is asking the password to decrypt the datas... Decryption Unsuccesful clearly states that the decryption procedure is not working. Post about the issue on the GSI rom you are using and provide logs to the developer to help digging the problem... if Developer will answer that encryption is not supported, you can only do one thing: backup all your data, files and pictures on an external storage (eg. a PC) and procede with a FORMAT DATA from TWRP to "destroy" the encryption and "free your phone from it"!
Q9: Is Google Camera working on Gsi?
A: Yes. But remember you need to install gapps package to let gcam works as it should.
We tested Gcam up to v6.1.021 on AOSiP Gsi. If you have greenish selfies pics, go in the Settings -> Fix ->and enable the fix for Front Camera and reboot. For SlowMotion, set 120fps.
Q10: Why can't flash a micro gapps and only pico is flashable?
A: If you get an error of Insufficent space on system partition, you need to resize the partition. Do in this way:
Flash the SYSTEM.IMG you wanna use (select a Vanilla based one)
Reboot to RECOVERY
MOUNT the SYSTEM partition
Go in WIPE menu -> ADVANCED WIPE -> select SYSTEM from the list and press the button REPAIR OR CHANGE FILE SYSTEM
select RESIZE FILE SYSTEM
than SWIPE to execute the command...
in case of error (you will see in red), repeat the RESIZE until it goes completed (Resizing... Done)
After this operation, the system partition will be resized to his maximum dimension (on Mi5 is around 2992MB)
before the installation of gapps package, do a REBOOT to recovery and after MOUNT the SYSTEM partition (check that it is really mounted)
Now you can flash the micro gapps without problem.
Q11: Is there any Magisk version working on Treble gsi?
A: Yes, you need to get v18.1 version or newer with treble support (check around).
Q12: VoLTE is working[/B]?
A: Yes. Install this ims.apk to use it!
Q13: ADB Logs are needed in case of Issue reporting...
A: In case you need help and want report an issue (eg. a boot problem), we need logcat of the phone. Just as sample, we report here what to do (but you must able to do by yourself... we are not giving help on how to do...)
prepare a PC (with adb package to support debug via usb connection)
flash on the phone our treble and the GSI image (just these 2 files, not any patch or other stuff)
reboot the phone
connect the usb cable
after the Mi logo screen, wait to hear from PC a sound that means the usb periferial has been recognised
go in a command window and type:
--> adb devices (if the phone is connected, you will see the code written after the command executed)
--> adb shell logcat > bootlog.txt (this will start real time recording of logs into the pc in the bootlog.txt file)
--> when the phone has completed boot/reboot (eg. a boot loop or fastboot), you need to press Ctrl+C from keyboard to stop log recording.
send attached to the issue description post the bootlog.txt
...let's dev check what's happening by reading the logcat.
... list will be updated...

Miscellanea...
Download (public versions history)
Here you can find the shared folder with all the version released of Treble support: GEMINI-TREBLE
Changelog's
v6 (20190316) - Release Candidate 2 full versioned_vndk v28
- VERSİONED_VNDK support is fully implemented
- FIXED NFC support
- FIXED Ambient Display main icon size and settings menu icons style... Thanks to Subezhj for helping fixing.
- FIXED ConfigPanel - Fingerprint settings menu icons style
v5 (20190308) - Release Candidate full versioned_vndk v28
- VERSİONED_VNDK support is fully implemented
- Mostly all library dependencies between system/vendor which are called as violations against treble's rule are succesfully eliminated
- Updated kernel as per treble's kernel docs (enforced)
- Vendor image's version is now 28
- Misc updates and fixes
- GSI Pie roms support (check in OP for some links)
- JDC PIE GSI rom given just as a preview for testing (JDC PIE GSI is build from sources without ANY hack!!)... It's pure AOSP as Google bring to their devices... NOTE: No support for gapps... they do not complete setup... you are advised.
v4 (20180409) - Beta partially versioned_vndk with the following updates:
- VERSİONED_VNDK support is partially implemented
- Lots of library dependencies between system/vendor which are called as violations against treble's rule are succesfully eliminated, only small number of lib dependencies which needs to be resolved are left
- Updated kernel as per treble's kernel docs
- Vendor image is now using google's stock vndk-sp, ll-ndk libs which are called as treble layer libs
- Vendor image's version is now 27.1.0
- Misc updates and fixes
v3 (20180329) - Beta status with the following updates:
- Updated camera Hal from latest qualcomm 8996 repo
- Hexedited more libs and removed more vendor system dependency (better treble and preparation for versioned vndk)
- Updated wifi configs from lates CAF
v2 (20180318) - Still alpha build with the following updates:
- Upstreamed kernel
- Hexedited blobs to correct path (for treble)
- Linker issues fixed
- Vendor overlays
- Latest device tree updates from CAF and miui oreo beta
- Disabled non-working apps (custom xiaomi doze package and configpanel app which were designed to work with LOS APIs)
- Disabled userspace thermal hal initialization which we dont have in cameraHal (faster cam launch)
- Increased jpeg quality parameters
- other misc. dev tree updates
v1 (20180310) - Initial release (Alpha)
Reported/Known Issues
- Camera works perfectly, but on some apk after a shot is taken with Flash active, the camera do not get more pictures... Close the app will clear the issue and you can get other pictures! Suggestion: do not use the flash with this camera apk if you have the issue! ... or use a working camera apk (is a better solution)!
to be updated...

Big thanx and credits also goes to @smeroni68
All of the story is started with the identifying unused CUST partition which xiaomi left on our device Mi5 https://forum.xda-developers.com/showpost.php?p=74702470&postcount=300
And after we determined that the /cust partiton is unused on AOSP roms, we used it as /vendor partition as per the requirement of Full-Treble https://github.com/sirmordred/android_device_xiaomi_gemini-twrp/commit/5faf9c4e162e8144b71f87d6d21c384931b1ac0c nearly 3 month ago
And that is also the reason of nearly all devices which get Full-Treble support via custom implementation, are Xiaomi devices (Redmi Note 4, Mi5S and our Mi5)
Thanx also to my teammates who contributed this project :good:
Our goal is now separating/isolating all vendor <=> system interactions (which will be enforced on future android releases for treble devices) and stabilizing vendor.img while getting closer to pure AOSP sources
Enjoy

...

...

Finally we are out for both MI5 and MI5S... yeah... now let's go ahead...

Thanks for all JDCTeam

Great Job dude! Finally we got treble. Downloading now. Can't wait flashing.
通过我的 MI 5 上的 Tapatalk发言

Thank you Sir, downloading now

Great news ..only one query .. How can I revert back from treble to custom ROM whenever required?

kishan314 said:
Great news ..only one query .. How can I revert back from treble to custom ROM whenever required?
Click to expand...
Click to collapse
Good question... I'll report also in post#2 in FAQ section.
Q: How can I revert back from treble to custom ROM whenever required?
A: Just flash the custom rom you like from TWRP and that's all. Custom rom flash will overwrite the boot.img and the system partition... vendor partition will stay there waiting for your next test!

So... P GSI is coming for the "old" Mi5. Thank u guys! This is the way

atembleque said:
So... P GSI is coming for the "old" Mi5. Thank u guys! This is the way
Click to expand...
Click to collapse
This is something we can try to build... but only when sources of P will be released and will be good to build an AOSP based on them...

Very very thankful

Thanks for your hardwork, downloading now.

When charging, the battery icon won't show. The bug is phh's?
Sent from my MI 5 using Tapatalk

Installed. Yeap, we finally got a vanilla android
For first alpha, it working flawlessly.
Some bugs i founded.
1. After magisk install on stock kernel, got bootloop. Fixed after installing AEXMod latest kernel.
2. Gcam not working. buildprop (vendor folder) doesnt help. Got FC anyway
3. HMP... stock governor settings cant provide smooth scrolling in settings, 820 sd stuttering like 210, okay. It happens on every gemini hmp kernel on 8.1 oreo. Maybe some to perfd related. Need EAS.
4. Gpay wont work, magisk can't help, maybe device id change will help
All other working fine

MichaelPan01 said:
When charging, the battery icon won't show. The bug is phh's?
Sent from my MI 5 using Tapatalk
Click to expand...
Click to collapse
Here it is working.
Have you set the battery icon visibility status under the statusbar settings?
StealthHD said:
Installed. Yeap, we finally got a vanilla android
For first alpha, it working flawlessly.
Some bugs i founded.
1. After magisk install on stock kernel, got bootloop. Fixed after installing AEXMod latest kernel.
2. Gcam not working. buildprop (vendor folder) doesnt help. Got FC anyway
3. HMP... stock governor settings cant provide smooth scrolling in settings, 820 sd stuttering like 210, okay. It happens on every gemini hmp kernel on 8.1 oreo. Maybe some to perfd related. Need EAS.
4. Gpay wont work, magisk can't help, maybe device id change will help
All other working fine
Click to expand...
Click to collapse
1) Phh rom support natively Phh superuser app (from market) with stock kernel and phh-gapps-su gsi image.
2) Gcam require API2/HAL3 support, and on phh gsi hasn't been implemented (as written is an experimental rom with the meaning to be compatible with stock Oreo treble devices). Instead, it has API1/HAL1 support for stock vanilla camera.
3) Stock kernel is HMP. We do not develop till now the EAS kernel on stock treble kernel (we will do for our JDC gsi).
4) Magisk is clearly reported into Phh thread to not be used. In custom development we have a plus, because we can change the kernel (as you have done)...
Thanks for this testing report.

Related

[Treble][ARM64][AOSP][J730X]Project_Spaget X

{
"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"
}
Welcome to Project Spaget X ARM64 Treble For Galaxy J530X/J730X/G610X/J701X/J710X
Some information you should know..
This is a full Treble ARM64 Vendor/Kernel implementation for the Exynos7870 Supported devices
If you want to report a Bug, read the F.A.Q First Then provide a logCat OR LoggingKit.zip with detailed explanation
Read the instructions and the F.A.Q Before installing the rom or posting a reply.
[FOR DEVS] You are allowed to customize this vendor if you want to use it in ROMs with proper credits. but not to distribute 1:1 copies
- Personal Notes
And here we are, few leaks and reworks later. X is here. i went with a letter this time just because it looks cool. This is officially going to be EOL for ARM64 AONLY vendors that i make (unless a critical bug was here that needed attention) . i dont have alot of time to work on 7870 And when i do i prefer it to be on something more productive than Treble
Anywya, TLDR : alot changed, alot was fixed. its a new vendor, flash and enjoy
Old releases
Alright, The "second" Treble update is here, this time it is FULLY ARM64 compatible. Thanks to the hard-work of @Astrako who managed to boot ARM64 Exynos 7885 bases on our device. This project is HEAVILY based on his work. and i would like to make that very clear. This is not a OneMan job. this took alot of hardwork by many people to make it reach the stage it is at. basically we are official minus the tag. This project is also possible thanks to my dear friends @Kique119 @me2 @SPARTANICUS and my other testers who spent day and night testing this with me.
At this stage, everything is mostly GSI related.
And finally, the cherry on top, is support for 3 more devices. Thanks to the devs who assisted me on adding support for their own devices. mentioned below.
If you appreciate this ambitious project, consider hitting thanks, supporting the thread, and donating (Paypal) to support my development (using cocaine of-course)
- Initial Notes:
Supports ONLY the mentioned devices Above
1. Don't forget to check bugs before asking questions
2. Since most of the GSIs are AOSP, forget about VoLTE, Knox features, Samsung apps, Camera mods or features, or other Samsung related features.
3. You can use any non-treble rom even if you have treble vendor installed, as long as you flash a non-treble kernel. The rom will ignore your vendor and everything will be as non treble.
- General Features :
- based on G965F Vendor with VNDK-28
- Adapted to J730/J530/G610/J710/J701 devices
- latest CronosKernelV5 included with most of the features of OneUI kernel + many more
- misc things enabled in framework overlay for better experience
- Seamless GSI patching, without user intervention
- Seamless setup process, with dynamic Scripts
- And Spaget
- How to Install Project Spaget:
- Flash `Exynos7870_CreateVendor` and reboot recovery
- Flash `Exynos7870_Spaget_X`
- Flash your desired ARM64_AONLY GSI
- Read OPTIONAL below
- What GSIs are support/recommended ?:
- Avoid sGSIs and flash source built GSIs (Such as PHH,PE)
- ARM64_AONLY GSIs only
- I recommend Pixel-experience or evo x and luke GSIs
- if you want a daily rom. avoid sGSIs
- More can be found here : Treble
- I dont have googleapps. what do i do ?:
ONLY for gsis that does not come with google apps
- Download Gapps pacakge from Here (ARM64 > VER > Micro or lower
- Go to TWRP > Wipe > Advanced Wipe > Tick System > Repair > Resize
- Flash opengapps_xxxx
- I need more info. where do i get it ?
Ask in this thread. if you need more , head to
Spaget Notes and support : Telegram Group
General bugs (GSI):
- offline charging is broken in Android 10 roms
- Bluetooth Calls
- Some GSIs might not include a camera, use Footej
- Some camera apps will have stretch
- I dont like it, how do i revert ?:
- Reboot to recovery
- Flash `Exynos7870_RevertVendor`
- Reboot recovery
- Flash any non treble rom or restore your previous twrp backup
Is that all ? I have treble now ? what about all the complicate process before ?
Yes, you now have a project treble device, ready to flash any GSI/sGSI of your choice aslong as it fits in your SYSTEM partition.
The entire process changed and now is much more seamless and noob-friendly. yet take caution as always
What if i didn't boot ?
In some cases, you might be stuck at a bootanimation loop or a splash loop, in this case follow the troubleshooting steps in the F.A.Q post
Credits
@corsicanu For great help with the repartition scripts, GSI patching and tons other throughout the years.
@Astrako for making booting ARM64 a possibility. and allowing this project to exists. kudos
@Kique119 For his awesome testing and documenting this project, without him there would be no spaget
@KassemSYR, for G610F Support and testing.
@Zero_Cool7870 , @DAvinash97 , @mohitsama and ORIGINALNAME123 for J710/J701 support
@SPARTANICUS For his great work maintaining KRAKEN kernel, which supports this project fully
Testers :
@Kique119 @LuanTeles @ion1s @djedjy @vsmhell @fetaiharbin @Mizo2019 @Me2 @LelMwhLwl @@rlukas210
@PedroDomeneghi @DaffyMirror4318 @bien2004official @AleeX157 @Alijouhara
And many more i cant remember the usernames of. please mention
Downloads. Changelogs , F.A.Qs below
OldPost (a64)---
So, i have been hesitated to release this project since last year. GSIs are not the most stable and many J 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 7870 Vendors and modified to support our devices, i have also added few patches and updates that even official 7870 vendors do not have. to get the best possible experience
I have also added a GSI_PATCH zip that should be used if you want to have the least amount of bugs.
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.
- STEPS FOR INSTALLING TREBLE VENDOR:
Flash “Treble_Jx30F.img” in TWRP as Image (Selecting RECOVERY)
Reboot recovery.
Wipe System, Data, Dalvik and Vendor.
Flash "jxy17lte_Vendor_9.0_v1.0.zip".
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be arm_binder64/A64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Flash "GSI_Patch.zip".
[OPTIONAL] Flash the “Gapps_patched.zip”
- STEPS FOR INSTALLING GAPPS:
If you flash Gapps, Google will spam you with fullscreen warnings and notifications about your device not being certified. But don't worry, you can certify it.
Just reach the homescreen, then proceed to install the "Device ID.apk". Use it to grab the Google Services Framework ID and paste it here: https://www.google.com/android/uncertified/
And paste the ID there. Then wait a few minutes and reboot. Few seconds after rebooting, you'll be done and you'll be able to normally log in as always.
- [OPTIONAL]STEPS FOR INSTALLING Magisk_GAPPS:
** Note : This gapps is recommended for all **
Download latest gapps from http://opengapps.org
place in /sdcard or /external_sd
flash magisk.zip
flash magiskgapps.zip
- Confirmed working GSIs :
** You can only use ARM_BINDER64 / A64 GSIs **
PHH AOSP V113 : Github
OmniROM GSI : XDA
Liquid Remix : GoogleDrive
Pixel Experience With Gapps : GitHub
Resurrection Remix : RR
XenonHD : TeamHorizon
P.S : only Omni and PHH Do not require the GSI_PATCH_FP The rest do in order to get Fingerprint working
- Known GSI Bugs:
Bluetooth calls are broken
Some 3rd party cameras have stretched pictures
And more here at Github Issue
Credits
@corsicanu For general help through out the years
@prashantp01 For overlay fixes and native camera fix. and other contributions
@Kique119 For his awesome testing and documenting this project
Testers :
@Kique119 @LuanTeles @ion1s @djedjy @vsmhell @fetaiharbin @Mizo2019 @Me2 @LelMwhLwl
And few more that didn't give me their usernames
Downloads. Changelogs , F.A.Qs below
XDA:DevDB Information
Treble, ROM for the Samsung Galaxy J7 (2017)
Contributors
ananjaser1211
Source Code: https://github.com/ananjaser1211/Helios_7870
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest bootloader and modem
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: X
Stable Release Date: 2020-01-13
Created 2019-05-11
Last Updated 2020-01-13

Downloads and changelogs
NewsChannel : Telegram
Come hang with us on our chat : Telegram
Official Treble support Group : Telegram
----------------------------------------------------------------
SpagetX Treble ARM64 Vendor Based on G965F VNDK-28
GoogleDrive : Download
P.S : If you failed to download please login and save the folder
P.S 2 : This requires Pie bootloader and modem on devices that supports them (I.E not j710 or g610)
----------------------------------------------------------------
Spaget Treble ARM64 Vendor V3.0 Based on A750FN Vendor
MegaDrive Download : MEGA
GoogleDrive Mirror : GDrive
Documentation : Here
Spaget X
- ReMade fully based on VNDK-28 S9 Vendor
- Based on Project Pizza Treble (8890)
- included most fixes for audio, webview and others
- added fixes for camera
- removed alot of obsolete hacks
- samsung offline charging added
- Re-did props and features and overlays
- Added patches for Android 10 Roms
- Fixed nuke.sh script on 10 roms
- fixed performance in some GSIs
- Fixed thermal , power , memtrack and other HALs
- Improved OMX fixes
- Removed alot of samsung security services
- Improved Wifi, NFC, graphics , camera and other fixes
- Fixed some reboots on G610
- Fixed Youtube Crashes and OMX issues on most devices
- Addressed alot of random reboots
- Fixed GNSS/GPS on some variants
- Removed HKTweaks due to reboots
- Fixes for J710 Wifi and bluetooth
- Tons of other changes and improvments
[COLOR=""]Spaget V3.0[/COLOR]
- Fully based on A750FN 64Bit Vendor
- Seamlessly integrated ALL patches into the vendor
- No longer do you need customized TWRPs, patches, zips whatever. just the vendor and GSI
- Fixed all the VENDOR related issues we had
- Audio, camera, NFC, everything is redone from scratch and improved
- Supports Android Q booting
- Updated overlays and configs
- Added support for J710/J701/G610
- Updated to Helios V4.0 Kernel with tons of changes and goodies
- Automatic GSI patching at first boot
- New repartition script with extended support. fail safes, backup features and tons more
- Live TWRP patching, so it will patch whatever twrp you have instead of using my own
- And tons more through out the months of testing, using and developing
- Please read the thread agian to understand how to use it
OLD(a64)
----------------------------------------------------------------
Treble Vendor V1.5 Based on Stable A600FN Pie Vendor
Full TREBLE Documentation and guides here : GoogleDocs
Treble folder mirror : MEGA
Treble Vendor V1.0 Based on Stable A600FN Pie Vendor
GoogleDrive Project : Download
Full TREBLE Documentation and guides here : GoogleDocs
Treble folder mirror : MEGA
---------------------------------------------------------------
V1.5
1- HeliosPro 3.1 Kernel
2- Added HKTweaks
3- Fingerprint fix for All GSIs
4- Hotspot fix for All GSIs
5- AdaptiveBrightness
6- Updated included overlays with more features and pie base
7- DualbootPatcher J5/J7 Seperation
GSI_PATCH_V2.0
1- Patch fingerprint libs for all GSIs
2- Switch to samsung fingerprint
3- Add device model number detection
4- replace gsi fingerprint with stock one
GSI_PATCH_FP
1- Special patch for PE/RR/LR and other roms that do not have working FP
2- Do not flash on OMNI/PHH
3- Must be flashed AFTER the Vendor/GSI
Kernel updates
- Updated base to latest pie source
- reworked and updated helios ramdisk tweaks
- Reverted old hacks to fix some bugs
- Performance and battery greatly improved
- F2FS enabled
- LZ4 Enabled
- GPU Performance Greatly improved
- Full CPU/GPU/DEVFREQ/MIF/CAMERA Voltage control and more
- Magisk V19.1 included
Bugs :
1- some users might face SDCard issues while using PE
- if you did , back up its data and format it in PE
V1.0
-initial release
- Helios Kernel 2.8

F.A.Q
Q: Device requirements ?
A : you MUST be on an Pie Bootloader and Modem, otherwise you will have no sim, no lockscreen etc (Devices such as J710 and G610 can use OREO)
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 : Any GSI that is ARM64_AONLY is supported [8/9/10]

Additional
One more

Oh God

Great job. Fm radio and volte work?

Xxxnano said:
Great job. Fm radio and volte work?
Click to expand...
Click to collapse
That depends on what GSI you plan to install. Go try one out and let others know.

Xxxnano said:
Great job. Fm radio and volte work?
Click to expand...
Click to collapse
No and No, this is an AOSP project. they dont support Samsung VoLTE or FM

Can anyone will make a video exactly what is this and how to install properly ..
I'm so confused here is so many details ?

Imtiaz ansari said:
Can anyone will make a video exactly what is this and how to install properly ..
I'm so confused here is so many details ?
Click to expand...
Click to collapse
Not the rom for you then. save your time and use something else

Xxxnano said:
Great job. Fm radio and volte work?
Click to expand...
Click to collapse
Volte works in custom rom after this?

Can i install an Oreo GSI or just Pie GSI's?
Anyway i'm gona try one of the images linked on google drive

Congrats guyz :good:
Including the long ears bunny

for j7 neo, please

When I install magicgapps everything seems normal giving me that its succesfully installed but when the system boots I dont have any gapps installed? What am I doing wrong? I installed the RR Rom. I mention that i took the gapps from the official website. I followed every step from the thread...

You are the best ?

Thank You anan Great rom

Well, i've tried all the GSI's linked on the google drive folder of the project and just AOSP booted up and this one have two bugs, all the configurations related to the simcard doesn't work and the simcard don't work, i can't get signal.
Another question, "A64" means "ARM64"? or there's another variant called "A64"?

Yolomean12 said:
Well, i've tried all the GSI's linked on the google drive folder of the project and just AOSP booted up and this one have two bugs, all the configurations related to the simcard doesn't work and the simcard don't work, i can't get signal.
Another question, "A64" means "ARM64"? or there's another variant called "A64"?
Click to expand...
Click to collapse
Type these commands in terminal:
Code:
su
setprop persist.sys.phh.sdk_override /vendor/bin/hw/rild=27

I have tried Omina gsi and it works OK, only the camera images are stretched, but this is a known bug.

[Treble][ARM64][AOSP][J710X]Project_Spaget X

{
"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"
}
Welcome to Project Spaget X ARM64 Treble For Galaxy J530X/J730X/G610X/J701X/J710X
Some information you should know..
This is a full Treble ARM64 Vendor/Kernel implementation for the Exynos7870 Supported devices
If you want to report a Bug, read the F.A.Q First Then provide a logCat OR LoggingKit.zip with detailed explanation
Read the instructions and the F.A.Q Before installing the rom or posting a reply.
[FOR DEVS] You are allowed to customize this vendor if you want to use it in ROMs with proper credits. but not to distribute 1:1 copies
- Personal Notes
And here we are, few leaks and reworks later. X is here. i went with a letter this time just because it looks cool. This is officially going to be EOL for ARM64 AONLY vendors that i make (unless a critical bug was here that needed attention) . i dont have alot of time to work on 7870 And when i do i prefer it to be on something more productive than Treble
Anywya, TLDR : alot changed, alot was fixed. its a new vendor, flash and enjoy
Old releases
Alright, The "second" Treble update is here, this time it is FULLY ARM64 compatible. Thanks to the hard-work of @Astrako who managed to boot ARM64 Exynos 7885 bases on our device. This project is HEAVILY based on his work. and i would like to make that very clear. This is not a OneMan job. this took alot of hardwork by many people to make it reach the stage it is at. basically we are official minus the tag. This project is also possible thanks to my dear friends @Kique119 @me2 @SPARTANICUS and my other testers who spent day and night testing this with me.
At this stage, everything is mostly GSI related.
And finally, the cherry on top, is support for 3 more devices. Thanks to the devs who assisted me on adding support for their own devices. mentioned below.
If you appreciate this ambitious project, consider hitting thanks, supporting the thread, and donating (Paypal) to support my development (using cocaine of-course)
- Initial Notes:
Supports ONLY the mentioned devices Above
1. Don't forget to check bugs before asking questions
2. Since most of the GSIs are AOSP, forget about VoLTE, Knox features, Samsung apps, Camera mods or features, or other Samsung related features.
3. You can use any non-treble rom even if you have treble vendor installed, as long as you flash a non-treble kernel. The rom will ignore your vendor and everything will be as non treble.
- General Features :
- based on G965F Vendor with VNDK-28
- Adapted to J730/J530/G610/J710/J701 devices
- latest CronosKernelV5 included with most of the features of OneUI kernel + many more
- misc things enabled in framework overlay for better experience
- Seamless GSI patching, without user intervention
- Seamless setup process, with dynamic Scripts
- And Spaget
- How to Install Project Spaget:
- Flash `Exynos7870_CreateVendor` and reboot recovery
- Flash `Exynos7870_Spaget_X`
- Flash your desired ARM64_AONLY GSI
- Read OPTIONAL below
- What GSIs are support/recommended ?:
- Avoid sGSIs and flash source built GSIs (Such as PHH,PE)
- ARM64_AONLY GSIs only
- I recommend Pixel-experience or evo x and luke GSIs
- if you want a daily rom. avoid sGSIs
- More can be found here : Treble
- I dont have googleapps. what do i do ?:
ONLY for gsis that does not come with google apps
- Download Gapps pacakge from Here (ARM64 > VER > Micro or lower
- Go to TWRP > Wipe > Advanced Wipe > Tick System > Repair > Resize
- Flash opengapps_xxxx
- I need more info. where do i get it ?
Ask in this thread. if you need more , head to
Spaget Notes and support : Telegram Group
General bugs (GSI):
- offline charging is broken in Android 10 roms
- Bluetooth Calls
- Some GSIs might not include a camera, use Footej
- Some camera apps will have stretch
- I dont like it, how do i revert ?:
- Reboot to recovery
- Flash `Exynos7870_RevertVendor`
- Reboot recovery
- Flash any non treble rom or restore your previous twrp backup
Is that all ? I have treble now ? what about all the complicate process before ?
Yes, you now have a project treble device, ready to flash any GSI/sGSI of your choice aslong as it fits in your SYSTEM partition.
The entire process changed and now is much more seamless and noob-friendly. yet take caution as always
What if i didn't boot ?
In some cases, you might be stuck at a bootanimation loop or a splash loop, in this case follow the troubleshooting steps in the F.A.Q post
Credits
@corsicanu For great help with the repartition scripts, GSI patching and tons other throughout the years.
@Astrako for making booting ARM64 a possibility. and allowing this project to exists. kudos
@Kique119 For his awesome testing and documenting this project, without him there would be no spaget
@KassemSYR, for G610F Support and testing.
@Zero_Cool7870 , @DAvinash97 , @mohitsama and ORIGINALNAME123 for J710/J701 support
@SPARTANICUS For his great work maintaining KRAKEN kernel, which supports this project fully
Testers :
@Kique119 @LuanTeles @ion1s @djedjy @vsmhell @fetaiharbin @Mizo2019 @Me2 @LelMwhLwl @@rlukas210
@PedroDomeneghi @DaffyMirror4318 @bien2004official @AleeX157 @Alijouhara
And many more i cant remember the usernames of. please mention
Downloads. Changelogs , F.A.Qs below
OldPost (a64)---
So, i have been hesitated to release this project since last year. GSIs are not the most stable and many J 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 7870 Vendors and modified to support our devices, i have also added few patches and updates that even official 7870 vendors do not have. to get the best possible experience
I have also added a GSI_PATCH zip that should be used if you want to have the least amount of bugs.
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.
- STEPS FOR INSTALLING TREBLE VENDOR:
Flash “Treble_Jx30F.img” in TWRP as Image (Selecting RECOVERY)
Reboot recovery.
Wipe System, Data, Dalvik and Vendor.
Flash "jxy17lte_Vendor_9.0_v1.0.zip".
- STEPS FOR INSTALLING GSIs:
Download the desired GSI (it MUST be arm_binder64/A64 Variant)
unpack it if it wasn't in .IMG format
Go to TWRP , Install , Install IMAGE
Pick your GSI and select SYSTEM IMAGE
Flash "GSI_Patch.zip".
[OPTIONAL] Flash the “Gapps_patched.zip”
- STEPS FOR INSTALLING GAPPS:
If you flash Gapps, Google will spam you with fullscreen warnings and notifications about your device not being certified. But don't worry, you can certify it.
Just reach the homescreen, then proceed to install the "Device ID.apk". Use it to grab the Google Services Framework ID and paste it here: https://www.google.com/android/uncertified/
And paste the ID there. Then wait a few minutes and reboot. Few seconds after rebooting, you'll be done and you'll be able to normally log in as always.
- [OPTIONAL]STEPS FOR INSTALLING Magisk_GAPPS:
** Note : This gapps is recommended for all **
Download latest gapps from http://opengapps.org
place in /sdcard or /external_sd
flash magisk.zip
flash magiskgapps.zip
- Confirmed working GSIs :
** You can only use ARM_BINDER64 / A64 GSIs **
PHH AOSP V113 : Github
OmniROM GSI : XDA
Liquid Remix : GoogleDrive
Pixel Experience With Gapps : GitHub
Resurrection Remix : RR
XenonHD : TeamHorizon
P.S : only Omni and PHH Do not require the GSI_PATCH_FP The rest do in order to get Fingerprint working
- Known GSI Bugs:
Bluetooth calls are broken
Some 3rd party cameras have stretched pictures
And more here at Github Issue
Credits
@corsicanu For general help through out the years
@prashantp01 For overlay fixes and native camera fix. and other contributions
@Kique119 For his awesome testing and documenting this project
Testers :
@Kique119 @LuanTeles @ion1s @djedjy @vsmhell @fetaiharbin @Mizo2019 @Me2 @LelMwhLwl
And few more that didn't give me their usernames
Downloads. Changelogs , F.A.Qs below
XDA:DevDB Information
Project Spaget. Treble ARM64 Vendor, ROM for the Samsung Galaxy J7
Contributors
ananjaser1211, corsicanu, Astrako
Source Code: https://github.com/ananjaser1211/Helios_7870
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Latest bootloader and modem
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: X
Stable Release Date: 2020-01-13
Created 2019-07-31
Last Updated 2020-01-13

Downloads and changelogs
NewsChannel : Telegram
Come hang with us on our chat : Telegram
Official Treble support Group : Telegram
----------------------------------------------------------------
SpagetX Treble ARM64 Vendor Based on G965F VNDK-28
GoogleDrive : Download
P.S : If you failed to download please login and save the folder
P.S 2 : This requires Pie bootloader and modem on devices that supports them (I.E not j710 or g610)
----------------------------------------------------------------
Spaget Treble ARM64 Vendor V3.0 Based on A750FN Vendor
MegaDrive Download : MEGA
GoogleDrive Mirror : GDrive
Documentation : Here
Spaget X
- ReMade fully based on VNDK-28 S9 Vendor
- Based on Project Pizza Treble (8890)
- included most fixes for audio, webview and others
- added fixes for camera
- removed alot of obsolete hacks
- samsung offline charging added
- Re-did props and features and overlays
- Added patches for Android 10 Roms
- Fixed nuke.sh script on 10 roms
- fixed performance in some GSIs
- Fixed thermal , power , memtrack and other HALs
- Improved OMX fixes
- Removed alot of samsung security services
- Improved Wifi, NFC, graphics , camera and other fixes
- Fixed some reboots on G610
- Fixed Youtube Crashes and OMX issues on most devices
- Addressed alot of random reboots
- Fixed GNSS/GPS on some variants
- Removed HKTweaks due to reboots
- Fixes for J710 Wifi and bluetooth
- Tons of other changes and improvments
[COLOR=""]Spaget V3.0[/COLOR]
- Fully based on A750FN 64Bit Vendor
- Seamlessly integrated ALL patches into the vendor
- No longer do you need customized TWRPs, patches, zips whatever. just the vendor and GSI
- Fixed all the VENDOR related issues we had
- Audio, camera, NFC, everything is redone from scratch and improved
- Supports Android Q booting
- Updated overlays and configs
- Added support for J710/J701/G610
- Updated to Helios V4.0 Kernel with tons of changes and goodies
- Automatic GSI patching at first boot
- New repartition script with extended support. fail safes, backup features and tons more
- Live TWRP patching, so it will patch whatever twrp you have instead of using my own
- And tons more through out the months of testing, using and developing
- Please read the thread agian to understand how to use it
OLD(a64)
----------------------------------------------------------------
Treble Vendor V1.5 Based on Stable A600FN Pie Vendor
Full TREBLE Documentation and guides here : GoogleDocs
Treble folder mirror : MEGA
Treble Vendor V1.0 Based on Stable A600FN Pie Vendor
GoogleDrive Project : Download
Full TREBLE Documentation and guides here : GoogleDocs
Treble folder mirror : MEGA
---------------------------------------------------------------
V1.5
1- HeliosPro 3.1 Kernel
2- Added HKTweaks
3- Fingerprint fix for All GSIs
4- Hotspot fix for All GSIs
5- AdaptiveBrightness
6- Updated included overlays with more features and pie base
7- DualbootPatcher J5/J7 Seperation
GSI_PATCH_V2.0
1- Patch fingerprint libs for all GSIs
2- Switch to samsung fingerprint
3- Add device model number detection
4- replace gsi fingerprint with stock one
GSI_PATCH_FP
1- Special patch for PE/RR/LR and other roms that do not have working FP
2- Do not flash on OMNI/PHH
3- Must be flashed AFTER the Vendor/GSI
Kernel updates
- Updated base to latest pie source
- reworked and updated helios ramdisk tweaks
- Reverted old hacks to fix some bugs
- Performance and battery greatly improved
- F2FS enabled
- LZ4 Enabled
- GPU Performance Greatly improved
- Full CPU/GPU/DEVFREQ/MIF/CAMERA Voltage control and more
- Magisk V19.1 included
Bugs :
1- some users might face SDCard issues while using PE
- if you did , back up its data and format it in PE
V1.0
-initial release
- Helios Kernel 2.8

F.A.Q
Q: Device requirements ?
A : you MUST be on an Pie Bootloader and Modem, otherwise you will have no sim, no lockscreen etc (Devices such as J710 and G610 can use OREO)
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 : Any GSI that is ARM64_AONLY is supported [8/9/10]

Enjoy, and please report any issues you face HERE and not in the other threads.
And read the thread few times before asking. Yes this supports your J710Whatever

This is only for J710 Users who got no wifi. BT fix will come later (you can do it yourself by editing the vendor.zip/variant/jx/fs/etc and removing the bluetooth folder.
reflashing vendor + gsi + fix
Wifi FIX : here

Great work sir.

ananjaser1211 said:
Enjoy, and please report any issues you face HERE and not in the other threads.
And read the thread few times before asking. Yes this supports your J710Whatever
Click to expand...
Click to collapse
When I flash these create vendor and project spaget zips, It gives a partition error like this:
Failed to mount "/vendor" (Block device required)
And My phone didn't boot GSI roms because of this.

Anyone tried this with Resurrection Remix (Im getting bootloops here: pastebin.com/raw/NnieJ1Px) or LineageOS (bootloops the same as RR)?
Edit: Every GSI bootloops the same, tried several roms. Stay away until it'll be stable enough.

TRalperenTR said:
When I flash these create vendor and project spaget zips, It gives a partition error like this:
Failed to mount "/vendor" (Block device required)
And My phone didn't boot GSI roms because of this.
Click to expand...
Click to collapse
siemanator said:
Anyone tried this with Resurrection Remix (Im getting bootloops here: pastebin.com/raw/NnieJ1Px) or LineageOS (bootloops the same as RR)?
Edit: Every GSI bootloops the same, tried several roms. Stay away until it'll be stable enough.
Click to expand...
Click to collapse
it has been tested, and this is nothing but user error.
if you are being stuck at splash, go follow the instructions again, as it has booted on several J710 variants already. after you flash the vendor zip you must reboot back to recovery, then check your vendor size in wipe menu, if it is less than 350MB, or doesnt exist, then you had some previous repartitioner installed that broke the process
finally be sure you are downloading arm64 gsi and a tested one, i have not tested RR or LOS (since they are both either outdated or doesnt work on samsung vendors)
flash PE , evox , havoc and so on

ananjaser1211 said:
it has been tested, and this is nothing but user error.
if you are being stuck at splash, go follow the instructions again, as it has booted on several J710 variants already. after you flash the vendor zip you must reboot back to recovery, then check your vendor size in wipe menu, if it is less than 350MB, or doesnt exist, then you had some previous repartitioner installed that broke the process
finally be sure you are downloading arm64 gsi and a tested one, i have not tested RR or LOS (since they are both either outdated or doesnt work on samsung vendors)
flash PE , evox , havoc and so on
Click to expand...
Click to collapse
Suggest fix

ananjaser1211 said:
This is only for J710 Users who got no wifi. BT fix will come later (you can do it yourself by editing the vendor.zip/variant/jx/fs/etc and removing the bluetooth folder.
reflashing vendor + gsi + fix
Wifi FIX : here
Click to expand...
Click to collapse
Waiting for the bluetooth fix sir

Followed all instructions andi am stuck at bootloop.
My j7 2016 is rooted with heilos 2.6 kernel with twrp recovery. Should i install stock rom and reinstall twrp and then the whole mentioned process in this post. Some one guide me please.

Flash “Treble_Jx30F.img” in TWRP as Image (Selecting RECOVERY)
Are you sure that as recovery?
Flash "jxy17lte_Vendor_9.0_v1.0.zip".
Write that zip file damaged.
Any solution?
---------- Post added at 02:09 PM ---------- Previous post was at 01:57 PM ----------
Sulltan Mehmood said:
Followed all instructions andi am stuck at bootloop.
My j7 2016 is rooted with heilos 2.6 kernel with twrp recovery. Should i install stock rom and reinstall twrp and then the whole mentioned process in this post. Some one guide me please.
Click to expand...
Click to collapse
Same me....

Sulltan Mehmood said:
Followed all instructions andi am stuck at bootloop.
My j7 2016 is rooted with heilos 2.6 kernel with twrp recovery. Should i install stock rom and reinstall twrp and then the whole mentioned process in this post. Some one guide me please.
Click to expand...
Click to collapse
NO.....you have to boot to TWRP. Once you're in recovery, you must wipe data, system, cache, dalvik, and vendor, then flash the RevertVendor.zip and after that you can go back to your stock rom or any other non-treble rom.

Sulltan Mehmood said:
Suggest fix
Click to expand...
Click to collapse
Flash pit file with stock rom via odin.

Tried again on my J7 1016, but after flashing vendor, reboot and flashing sparget I cannot mount system. Any solution?

Thanks so much for your work.

There is one problem with this release same as before with roms that used HeliosKernel is that the kernel has no deep sleep and it drains battery like no tomorrow, it drained battery from 80% to 5% in standby over night.

I got error while
- Flashing `Exynos7870_ProjectSpaget_V3.0`
Below is image where error is shown. How can I fix this error please help me.

I got error 255 by flashing image!? Any solution?

[ROM] [TREBLE] AOSP Extended Android 10 Q J710x

Welcome to AOSP Extended 7.1 Android Q 10.0 For Galaxy J5/J7
Only For J530X/J730X/J710X Eynos7870
{
"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"
}
Quote:
Warning : Me nor XDA Are responsible for any damage that might be caused after flashing any file provided here. Please take caution and be aware of what you are doing. And Always backup!
Compatible Kernel Chonos Kernel 5.0
Use only Magisk for Phhusson's Rom source : updated link below !
I am not the developer of this project, technically the rom is for any device with treble support
- Credits to @igors1974
Oficial page XDA release 9.0
Oficial SF page https://sourceforge.net/projects/amber-gsi/files/AospExtended/
What Working ???
- Camera (kernel treble)
- Google apps
- All Sensor
- So much feature will work perfect
- Google Play Permission (Only OpenGapps !!!)
- Alway On Display ( AMOLED/Super AMOLED Only )
What NOT Working ???
- Volte
- Alway On Display AOD
- You Tell Me
What Bug's?
Camera Front stretch, use Footej Camera and change Mega Pixel to 12.8MP
How to install :
Download Project Treblue
iNSTALL Create Vendor 2.0
iNSTALL Project Treblue
rEBOOT to Recovery
uNPACK Your ROM using RAR apk from Google Play
iNSTALL AOSP Extended Android Q img (Arm64 A Only)
iNSTALL CronosKernel
iNSTALL Magisk : Install -> Magisk for J710X/J730X.zip and flash
Use only this version Magisk or your system bootloop
rEBOOT and wait start your ROM
Download
Magisk Canary for Phhusson's Rom Source only :
https://drive.google.com/file/d/1w2NIrqZpMG5GkK-Nm-qpe_yXXJ-bZ2Cb/view
ROM AOSP Extended 7.1 Android 10 Q
https://sourceforge.net/projects/gsi-albus/files/arm64/android10/aex/2020-04-21-_aex.7z/download
Or
https://sourceforge.net/projects/amber-gsi/files/AospExtended/AospExtended-10-arm64-a-vanilla.img.xz
To unpack install RAR apk from Play Store
Gapps
BitGapps minimal and Optimized for Android 10 Q
https://bitgapps.cf/arm64/Q/
Or
https://androidfilehost.com/?fid=4349826312261650975
Or Pico or Nano
Open Google Apps Compatilhe two options
https://opengapps.org/ Nano Or Pico
Fix SIM Misc (fix SIM Card not work)
Ares Kernel (J7X users) :
https://github.com/SPART4NICUS/android_kernel_samsung_exynos7870/releases/tag/RC2
Kraken RC14 (J710X/J730X/J701X support) :
https://forum.xda-developers.com/galaxy-j7-2017/development/kernel-project-butter-t3957185
Thank You special for
@NindoS by Magisk Compatible Android Q
@ananjaser1211 SpagetX and Cronos Kernel
@SPARTANICUS kernel kraken RC14
@Our Mine for Google Apps fix
@igors1974 for develpment of this ROM Treble
@strix for Project Treblue
ROM OS Version: 10.x Android Q Arm64 A Only
ROM Kernel: Linux 3.x
ROM Firmware Required: Pie bootloader and modem
Kernel Required: Kernel Treble
Based On: Treble Project and Treblue
The surprising reason for my success is Jesus.
-Version Information
Status: Stable
Current Version: AOSP Extended V 7.1 Android Q 10.0
Stable Release Date: 2020-01-14
Created 2020-01-14.
Last Updated 2020-06-06

Changelogs
Aosp extended 7.1
Merge April security patch (10.0.0_r33)
Update all of our packages
Update pre-built apks
Add LS media art blur customisation
Add toggle for FP with vibration
Add toggle for persistent settings icon on QS panel
Add option to force full screen aspect ratio on pre-O applications
Add volume key cursor control
Add in-call vibration options
Add toggle for display data disabled indicator
Add toggle for roaming indicator
Add HW navigation button light customisation
Add HW key disable support
Add support for home button wake
Add CPU info overlay
Add LS visualiser with customisation
Add toggle for QS footer warnings
Add smart pull down
Add brightness slider position customisation
Add brightness slider toggle
Add auto-brightness icon toggle
Add status bar brightness control gesture
Add battery bar
Add less boring heads-up
Add option to mute media with gesture
Add kill app button to notification guts
Add custom carrier label and label placement
Add notch support for carrier label
Add custom rounded corner and padding preferences
Add CM screen security customisation (Custom pattern size, Dots visibility etc.)
Add toggle to DT2W on doze
Add battery/notification light customisation
Add toggle for on-screen navigation bar with customisation
Add option to swap recents and back
Add fruity pebbles for switching accent colour
Add theme QS tile
Improve auto-brightness slider UI/UX
Bring back our system themes
Fix few theming issues
There is a new boot animation!
Bug fixes and performance improvements
Aosp extended 7.0
Initial version with latest security patches
A clean flash is always recommended. Bug reports are not appreciated if not clean flashed.
Remove any kind of security PINs/Password and Fingerprints before flashing this build.

Treble support reserved
As part of Android 8.0 Oreo, Google released a major rearchitecting of the Android OS called Project Treble. The change aimed to help make OS updates easier, faster and less costly for device manufacturers. On top of that, Project Treble also made it possible to boot a generic, AOSP-based system image without modifying the boot or vendor image. Manufacturers seeking Google certification are required to test their devices for Treble compliance by booting this Generic System Image (GSI) and verify basic hardware functionality. However, they’re not required to make sure that everything works on the GSI. This resulted in GSIs being fairly functional on some devices and completely broken on others. To overcome this issue, developers released custom GSIs that are designed to work on as many devices as possible and with few bugs. Late last month, XDA Recognized Developer phhusson released an Android 10 based GSI that can be installed on any device that supports Project Treble. And now, XDA Recognized Contributor AndyYan has released an unofficial LineageOS 17 GSI.
The unofficial LineageOS 17 GSI offers a more customized and user-friendly version of the Android 10 GSI released last month. This new GSI should boot on any Android device that supports Project Treble, which means most devices that launched with Android 8.0+. Although it’s worth noting that Project Treble support is only required for devices with Google certifications, so you may face some issues while installing this GSI on devices imported from China.
Before you go ahead and install the LineageOS 17 GSI on your device, you should know that it’s based on phhusson’s release and, therefore, it carries forward some of the same issues and bugs. So it would be best to try out phhusson’s release on your device and report any bugs you encounter here. In case you don’t encounter any major issues, you can be sure that the LineageOS GSI would also work on your device. If you’re new to flashing GSIs, you can check out our tutorial here.
CHangelog.
FAQ.
Editing...

onenyon said:
Test AOSP Extended too for me this is fantastic ROM
Click to expand...
Click to collapse
@onenyon 
 @Eugene1503
Install TWRP
install create vendor and SpagetX
Wipe your system and data cache and dalvi
Install new rom
Install kernel cronos and Reboot
After first boot test rom, reboot twrp and flash magisk and Gapps.
hacker

hacker812c said:
@onenyon
@Eugene1503
Install TWRP
install create vendor and SpagetX
Wipe your system and data cache and dalvi
Install new rom
Install kernel cronos and Reboot
After first boot test rom, reboot twrp and flash magisk and Gapps.
hacker
Click to expand...
Click to collapse
Thanks, I understood that we should install Gapps after testing the Rom. When i tried before testing, it boot looped. I'll try!

Eugene1503 said:
Thanks, I understood that we should install Gapps after testing the Rom. When i tried before testing, it boot looped. Thanks again. What about Havoc Os?... If this question is comfortable
Click to expand...
Click to collapse
Havoc is fast and stable recomend
Boot loop reinstall create vendor and Spagetx
All android 10 treble is stable.
Install create vendor, spagetx and install rom only and test.
Magisk use only magisk special version for treble.
Best Regards
Hacker

I'm running on Havos OS 3.1 on my J7 2016 ( 710FN ) everything is working fine + stable, i only had to use a fix for youtube, everything is fine now, just saying
The experience with hacker812c's rom should be the same, stable

abstrkt1337 said:
I'm running on Havos OS 3.1 on my J7 2016 ( 710FN ) everything is working fine + stable, i only had to use a fix for youtube, everything is fine now, just saying
The experience with hacker812c's rom should be the same, stable
Click to expand...
Click to collapse
Thank you for report
Havoc and all roms Treble is fantástic

abstrkt1337 said:
I'm running on Havos OS 3.1 on my J7 2016 ( 710FN ) everything is working fine + stable, i only had to use a fix for youtube, everything is fine now, just saying
The experience with hacker812c's rom should be the same, stable
Click to expand...
Click to collapse
Thank you for your report, my friend
New ROM Android 10 Q Updated today
if possible press thanks in my first post
StagOS is based Lineage
https://sourceforge.net/projects/am...020/StagOS-10-arm64-a-vanilla.img.xz/download
Open Gapps fixed for AOSP and Lineage
https://androidfilehost.com/?w=files&flid=304777

EDIT: I've found ARM (32) based, and now lets see if this work

Se8870 said:
EDIT: I've found ARM (32) based, and now lets see if this work
Click to expand...
Click to collapse
Thank you for participate
Arm64 run perfectly with treble

Phone reboots when accessing YouTube (both in YouTube vanced app and browser) .is there any fix for this?

How to use the home button to turn on the screen?

What is create vendor 2.0? How to install it? Thanks

spiritforme said:
What is create vendor 2.0? How to install it? Thanks
Click to expand...
Click to collapse
This file is making partition and patching Recovery to start with Gsi rom
---------- Post added at 11:52 AM ---------- Previous post was at 11:46 AM ----------
spiritforme said:
What is create vendor 2.0? How to install it? Thanks
Click to expand...
Click to collapse
You can download creat vendor from this forum LINK

hmm

Is 64 bits?
this rom is 64 bits?

work perfectly on SM-J710 FN
This rom works as expected.
only youtube keeps crashing, but i've found a solution and now its back to normal.
also, VoLTE WORKING if you install kraken RC12
wifi working, 4G working, and NFC WORKING
EDIT: if you want youtube fix, flash this on TWRP after you install the rom.
https://mega.nz/#!HnxWjQLK!ajyjTJWMceRwcTSu7zKtXvQGDSKKU3L1ohO--SmgiPE
---------- Post added at 09:09 AM ---------- Previous post was at 09:07 AM ----------
YERTZ said:
this rom is 64 bits?
Click to expand...
Click to collapse
its not 64 bit, but ARM64 my guy.
SM-J710xx can be switched to ARM64 using spaghetX and you can try it.

Since @ananjaser1211 has stopped working for j7 2016 and project spaget x is a arm64 treble wirh some bugs like youtube reboot, if you use @SirDoz's project treble the reboot problem will be fixed.

Youtube reboot J7 2016
Hello, I tried to flash the youtube_fix.zip after installing the AOSP ROM in my Samsung J7 2016 but my phone still reboots when I try to play a youtube video.
Any idea how to fix it?
EDIT: Worked on Samsung J7 2016
1) Root your phone
2) Install Root Explorer
3) Grant root privileges to that app
4) open Root Explorer and mount R/W (top-right) your root '/','/system','/system/vendor', '/system/vendor/etc'
5) copy corrected youtube_fix XML files (see @Se8870 post) in '/system/vendor/etc' and modify existing files
6) mount r/o previous paths
7)reboot

[ROM][UNOFFICIAL][alpha] LineageOS 17.1 for Redmi K30 5G (picasso) (20200419)

{
"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"
}
WARNING
DO NOT try to install this on the non-5G version of Redmi K30. This ROM is ONLY intended for Redmi K30 5G and they are NOT the same device. Their difference is more than just 5G or non-5G.
Introduction
This is an UNOFFICIAL port of LineageOS 17.1 (based on Android 10) for the device Redmi K30 5G, codenamed Picasso.
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, 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 Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's working
- All basic mobile phone features (Wi-Fi, Bluetooth, Cellular Data, Phone Calls, SMS, etc., incl. 5G and VoLTE)
Known Issues
- (For Chinese Users) NO Alipay / WeChat Pay fingerprint support, and no plan to add support for them. Ask Alibaba / Tencent to support the standard Android biometrics API, not me to make my ROM support their API.
- 3.5mm jack does not work for some reason. (Will be fixed in the next release) Fixed since 20200311
- Wi-Fi display is not implemented since I have no device to test it on
- VoWiFi is not tested since I have no carrier support
- No 5G toggle. You cannot disable / enable 5G support. It's on by default and it goes to 5G if it can. (Note: there seems to be a dedicated network type option now in settings - mobile network for 5G NR, but I checked AOSP source code and that's only for 5G SA, and 5G NSA still falls under LTE, not the NR type)
- CTS does not pass because xiaomi's build fingerprint is not CTS-verified. You are on your own finding a solution to this. (Hint: Magisk modules)
- (For Developers) I cannot build a working DTB image from the sources provided by Xiaomi. I do not know the exact reason and for now I'm using prebuilt DTB and DTBO images, which you can extract from the official ROM and its boot.img.
- I'm not sure if there is any other issue, but at least nothing deal-breaking for me.
Instructions (Install / Upgrade) (IMPORTANT)
Side Note: I am fully aware that there is a TWRP port for this device, however it seems to be based on a modified version of TWRP whose source code I cannot find. The official TWRP repository (that I can see) does not even support Android 10 dynamic partitions yet, let alone porting it to this device. Of course it is possible that the author of that TWRP port has access to some internal testing version of TWRP, but since I cannot access the source code either way, I cannot do tests on the TWRP port. The LineageOS recovery I ported is adjusted specifically for this ROM and I have only tested the ROM on my LineageOS recovery port. If you choose to use the TWRP port, you are on your own, and do not ask me for problems you may encounter by using that port.
1. Install LineageOS 17.1 Recovery following my guide in the other thread (https://forum.xda-developers.com/re...covery-lineageos-recovery-17-1-redmi-t4059879), DO NOT use TWRP because it will NOT work for devices with dynamic partitions.
2. Reboot to LineageOS Recovery, wipe all data (skip if you are upgrading) (BACKUP ALL YOUR DATA TO A COMPUTER BEFORE FLASHING)
3. Flash required OFFICIAL MIUI version via adb sideload before flashing LineageOS 17.1. (consult the Downloads section for the corresponding MIUI version required for each LineageOS release)
- Flash OFFICIAL, not Xiaomi.eu or any other modified version.
- You can skip this step if you already have the required MIUI firmware + vendor version flashed before (e.g. if you upgrade from an older release of my LineageOS port and I did not change the required MIUI version)
- You can choose to try installing LOS on non-tested MIUI versions, though they are not tested so expect some hiccups or even disasters.
- DO NOT just flash the firmware of the required MIUI version. Always flash the full MIUI ROM (no additional wiping needed if you do not actually boot into MIUI). This ROM depends on the vendor partition provided by MIUI to work. You will need to flash at least the firmware PLUS the vendor and odm partition images of its required MIUI version for the ROM to actually work.
4. Flash LineageOS 17.1 zip via adb sideload
5. Reboot to Recovery (If you want to install Magisk or OpenGAPPS or both, else just reboot to system
6. Select "Mount /system" in the rebooted Recovery, ignore any error that may pop up on the screen
7. If you would like to, install Magisk (you MUST use a version later than or equal to 20.4)
8. If you would like to, install patched OpenGAPPS zip (available in Downloads section. You MUST use the patched OpenGAPPS for now.)
9. Reboot and enjoy. Magisk may cause your phone to double-boot (i.e. auto-reboot after the logo disappears) on first boot. If your phone boots up the second time then it will be fine.
Downloads
20200419: https://mega.nz/file/LAJjCYDT#L1Rd-WFJQ7SaU3vfAxU2y7AJsfH9qZ3fSAKMTQhgPWM
(MIUI firmware / vendor version tested on: miui_PICASSO_V11.0.11.0.QGICNXM_65ec88895f_10.0)
Changelog:
- Updated LOS source (April patch)
- You can now install the OFFICIAL version of Magisk >= 20.4 without modification
20200311: https://mega.nz/#!iB53SIKQ!ewdfMNFHmHjOemDDuYcgQO2t1KgrB9hx6YXYAdLKxU4
(MIUI firmware / vendor version tested on: miui_PICASSO_V11.0.11.0.QGICNXM_65ec88895f_10.0)
Changelog:
- Fixed 3.5mm jack support
- Lowered minimum allowable brightness to match the auto brightness curve
- Synchronized LineageOS 17.1 March Security Patch update
20200307: https://mega.nz/#!KQ5jkbAQ!dJspI92ls3BiVGk8FIGbVf4b4QBkwaaLUUr_NKX020A
(MIUI firmware / vendor version tested on: miui_PICASSO_V11.0.11.0.QGICNXM_65ec88895f_10.0)
Patched OpenGAPPS 20200306 (2): https://mega.nz/#!2EwVzAJR!NmBbO1_ao5ziyup6UVx64lZK06_VGNXSsFDA9T4sOO0
(Changelog: added `sync` after flashing to ensure everything is actually written to /system; also added a flag to `tar` to ignore creation times because that seems to break sometimes in our recovery)
Patched OpenGAPPS 20200306: https://mega.nz/#!2NgHXL6T!Z7J6AbJ7i4y9AuflIF0v_7KLbAO8XVV4ACsk13oz380
(What's patched: the `busybox` included in OpenGAPPS cannot mount the system partition as Read-Write in LineageOS Recovery for some reason. I edited the install script to use the `mount` command provided by the recovery instead of busybox. Also I removed the unmounting at the end of installation since it seem to stall the whole recovery, which means you will have to flash OpenGAPPS at the very last of your flashing process.)
XDA:DevDB Information
LineageOS 17.1 for Redmi K30 5G, ROM for the Redmi K30 5G
Contributors
PeterCxy
Source Code: https://github.com/PeterCxy/android_device_xiaomi_picasso
ROM OS Version: Android 10
Version Information
Status: Alpha
Created 2020-03-08
Last Updated 2020-03-08

I've been trying to compile the os from your device tree these days...now it's a waste of time
Anyway, I've followed you on GitHub. Thank you for doing so much!

zhufucdev said:
I've been trying to compile the os from your device tree these days...now it's a waste of time
Anyway, I've followed you on GitHub. Thank you for doing so much!
Click to expand...
Click to collapse
Sorry for that, you need some additional patches in LineageOS to actually build it successfully (you can search for patches by me on LOS gerrit: https://review.lineageos.org/q/owner:peter%40cxy.moe). Also I haven't uploaded the prebuilt DTB / DTBO image in my device tree. You will need to extract those on your own (or maybe you can help me figure out why the official open-source version does not work)

PeterCxy said:
Sorry for that, you need some additional patches in LineageOS to actually build it successfully (you can search for patches by me on LOS gerrit: https://review.lineageos.org/q/owner:peter%40cxy.moe). Also I haven't uploaded the prebuilt DTB / DTBO image in my device tree. You will need to extract those on your own (or maybe you can help me figure out why the official open-source version does not work)
Click to expand...
Click to collapse
I'm sorry but I am basically a noob on ROM porting. I'm only familiar with some basic linux commands and Android developing.

Hi, there! There is something I can't figure out:
Is there any checksums for ROM?
BTW, is there any force encryption feature in LineageOS?
However, thanks for your ROM.

RiverYKB said:
Hi, there! There is something I can't figure out:
Is there any checksums for ROM?
BTW, is there any force encryption feature in LineageOS?
However, thanks for your ROM.
Click to expand...
Click to collapse
No checksum, but since Mega.nz uses end-to-end-encryption it should do checksum on its own. Also you can verify the package against testkeys.
Force encryption is of course enabled by default.

PeterCxy said:
No checksum, but since Mega.nz uses end-to-end-encryption it should do checksum on its own. Also you can verify the package against testkeys.
Force encryption is of course enabled by default.
Click to expand...
Click to collapse
I'm just worrying about my downloaded ROM. Because you know some of E2EE file send platforms (such as Mega.nz) is being blocked by Chinese Gov. ?So I have to download with VPN.
But it's just fine.

Do not try it on the non 5G K30, oh ok means now I definitely have to try it.

Ya_SG said:
Do not try it on the non 5G K30, oh ok means now I definitely have to try it.
Click to expand...
Click to collapse
You may have better luck trying a K20 ROM on non-5G K30 than trying this one. The non-5G K30 shares the same kernel source tree with K20 instead of K30 5G. (of course, existing K20 kernels and thus ROMs do not even support dynamic partitions, so you would probably not be able to boot either way)

Hi!
I know I'm a really noob, but I ran into a problem.
So before I flash LineageOS, my /sdcard and /data is already encrypted.
And I backed my files to /sdcard, then I wiped /data and flashed LineageOS.
I can boot to LineageOS properly now, but I can't access my backup files in /sdcard, it's all garbled.
Is there any way to help?
Thank you very much.

RiverYKB said:
Hi!
I know I'm a really noob, but I ran into a problem.
So before I flash LineageOS, my /sdcard and /data is already encrypted.
And I backed my files to /sdcard, then I wiped /data and flashed LineageOS.
I can boot to LineageOS properly now, but I can't access my backup files in /sdcard, it's all garbled.
Is there any way to help?
Thank you very much.
Click to expand...
Click to collapse
looks like you have wiped the encryption keys for some reason. Unfortunately, there's nothing I can do to help in this case.

RiverYKB said:
Hi!
I know I'm a really noob, but I ran into a problem.
So before I flash LineageOS, my /sdcard and /data is already encrypted.
And I backed my files to /sdcard, then I wiped /data and flashed LineageOS.
I can boot to LineageOS properly now, but I can't access my backup files in /sdcard, it's all garbled.
Is there any way to help?
Thank you very much.
Click to expand...
Click to collapse
Hi RiverYKB
The point I guess is to decrypt the data partition, which can be easily done using a TWRP recovery. So I suggest flashing TWRP via fastboot with your computer. You should be able to decrypt your data with the password set before lineage os was flashed.

Updated 20200311

PeterCxy said:
Updated 20200311
Click to expand...
Click to collapse
it looks like bootloop after flash 0311 version, logcat file below
htdeletemetps://drive.google.com/file/d/1INO9nNnEyR_JxmJRvZzhNrOVfWrDIuwv/view?usp=sharing

Cedric1223 said:
it looks like bootloop after flash 0311 version, logcat file below
htdeletemetps://drive.google.com/file/d/1INO9nNnEyR_JxmJRvZzhNrOVfWrDIuwv/view?usp=sharing
Click to expand...
Click to collapse
Your issue seems gapps-related. Make sure you flash my patched version of gapps, not the official version. Did you upgrade to 0311 from 0307 or just flash 0311? If you upgraded, make sure you re-flash gapps after the upgrade.

I will try when next update comes, thank you for your great rom port
PeterCxy said:
Your issue seems gapps-related. Make sure you flash my patched version of gapps, not the official version. Did you upgrade to 0311 from 0307 or just flash 0311? If you upgraded, make sure you re-flash gapps after the upgrade.
Click to expand...
Click to collapse

This rom working on poco x2 4g?

fromjeet said:
This rom working on poco x2 4g?
Click to expand...
Click to collapse
of course not

It looks like if I set a password for Hotspot, other devices can not connect this hotspot
if no password for hotspot, it works perfectly

Thanks for your ROM since I have been using it for a couple of days with no critical problem found. However,
1. Since 5G NSA falls under LTE, is it possible to make it displaying "NR" or something else to indicate that the phone is on 5G network? If impossible, is there any other ways to know whether the phone is on 5G or not?
2. Is there a working root solution for it?
Thank you for your time and effort

[DISCONTINUED][ZS620KL] LineageOS 19.1 (Android 12.1) for the Asus Zenfone 5z

Features over Stock
FM Radio, File-Based Encryption (which allows power-off Alarm to actually work and no annoying PIN prompt half-ways through boot), QTI Bluetooth stack
KNOWN BUGS
ViLTE does not work
4K UHD Video recording does not work in LineageOS Snap Camera app. (A workaround is to use other camera apps like OpenCamera or Gcam Mods)
Touch sometimes doesn't work in Lineage Recovery. The workaround is to use the volume buttons to move around the menu and power to select or to reboot to recovery.
SafetyNet does not pass (Unfortunately, this is not possible as your SoC has hardware attestation... the workaround is to use unsupported mods like Magisk which tbh I haven't tried myself as I don't root my devices, but other users said that plus the SafetyNet Magisk mod works)
Frequently Asked Questions
Is there a different way to unlock the bootloader than the Asus official method? You can try the unofficial bootloader unlock here

Heyyo, a new test build is going up! It will be ready within 10 minutes of this post. lineage-19.1-20220406-UNOFFICIAL-Z01R is stable and pre-official! This is what the official builds will be like whenever 19.1 goes live (whenver that is? No idea lol). Offline charging bug is fixed and QTI bluetooth too thanks to Edward's kernel.
Release lineage-19.1 lineage-19.1-20220406-UNOFFICIAL-Z01R - lineageos-for-z01r - OSDN
Release lineage-19.1 lineage-19.1-20220406-UNOFFICIAL-Z01R - lineageos-for-z01r #osdn
osdn.net

ThE_MarD said:
Heyyo, a new test build is going up! It will be ready within 10 minutes of this post. lineage-19.1-20220406-UNOFFICIAL-Z01R is stable and pre-official! This is what the official builds will be like whenever 19.1 goes live (whenver that is? No idea lol). Offline charging bug is fixed and QTI bluetooth too thanks to Edward's kernel.
Release lineage-19.1 lineage-19.1-20220406-UNOFFICIAL-Z01R - lineageos-for-z01r - OSDN
Release lineage-19.1 lineage-19.1-20220406-UNOFFICIAL-Z01R - lineageos-for-z01r #osdn
osdn.net
Click to expand...
Click to collapse
This rom now official right ? I saw it on lineage official download with nightly status.
Anw, can i just download the nightly and update using updater or should i use sideload to update ?

Heyyo @semuabaik, yes we are official now! One of 19 devices that got official builds of 19 heh
You will need to manually update to official as OTA via Lineage Updater only works if you're already on an official build that is the same version. Upgrading versions must be done manually as any additions like GApps would need to be updated too.

ThE_MarD said:
Heyyo @semuabaik, yes we are official now! One of 19 devices that got official builds of 19 heh
You will need to manually update to official as OTA via Lineage Updater only works if you're already on an official build that is the same version. Upgrading versions must be done manually as any additions like GApps would need to be updated too.
Click to expand...
Click to collapse
Ah so the step is the same when i updated from 18 to 19.1
But i can't get my laptop to detect my phone anymore since i update to 19.1
I tried to change the cable, different slots, etc but nothing worked then i used the same cable to my brother's phone and every cables i tried worked.

@semuabaik you can use USB OTG if you have a USB flash drive or micro SDcard

I am to install lineageos 19, however when I install GApps, the phone gets stuck at the boot animations. I have wiped the phone and started from scratch 3 times. Any thoughts?
Edit: I am going to try the GApps version that doesn't specify 64 bit and report back.

Update, it boot loops no matter which version of GApps is used. I might go back to one of the builds that isn't a nightly and try that.

ThE_MarD said:
Heyyo @semuabaik, yes we are official now! One of 19 devices that got official builds of 19 heh
Click to expand...
Click to collapse
This is a fantastic surprise. Thanks so much @ThE_MarD & team! It is working brilliantly. Not at all what I'd expect from a nightly.
semuabaik said:
can't get my laptop to detect my phone anymore since i update to 19.1
Click to expand...
Click to collapse
If you are running Windows, download the (Windows 8) USB drivers directly from ASUS support. Unpack and direct device manager to the unpacked drivers. Works up to W10 for ADB in powershell (prefix with .\), not sure about W11.
Cyb3rk1ll said:
Update, it boot loops no matter which version of GApps is used.
Click to expand...
Click to collapse
First time go for me & device can be restarted without issue. Wrote the recovery image, OS and gapps to SD rather than using ADB, but otherwise followed the official instructions using:
20220516 nightly
gapps version MindTheGapps-12.1.0-arm64-20220416_174313
GL if you give it another go!

Heyyo @Cyb3rk1ll , can you please specify which GApps and package name it is you are trying to install?
@Incoherent Ian , tbh it's crazy how good Z01R works on custom ROMs! It actually works best out of all my devices too haha... Only real downside is Widevine L1 because Asus wiped DRM keys on bootloader unlock...
From what I've heard? Newer Asus devices don't wipe DRM keys, so they can do L1 the lucky buggers

Hi, its possible relock the bootloader s SafetyNet pass im test?

So I believe I managed to brick my phone while retaining access to TWRP... I'm kinda panicking right now and would appreciate some help.
(I never flashed GAPPs throughout this as I want to degoogle my life, but I had them before)
I was running EvolutionX and decided to clean flash the latest LineageOS build. No errors, but booting resulted in it rebooting straight back to recovery. TWRP logs mentioned Android Rescue Party with reason enablefilecrypto.
The only thing I did that wasn't usual was flashing a new version of TWRP directly to boot_a instead of just boot.
Wiped Data and Cache, tried again, same thing. Restored my EvolutionX backup. Now it just got stuck on the Powered by Android screen, didn't do anything. Clean flashed EvolutionX and after a few reboots it entered a cycle of lockscreen for 2 seconds - boot animation - lockscreen.
This is when I decided to use the Linea recovery, use ADB sideloas and follow the installation steps as closely as possible, which resulted in the same recovery bootloop. Somewhere throughout all this I tried the LineageOS build just before the last (maybe the latest was broken) to no avail.
Sorry for the wall of text but I wanted to explain all that I've tried. I'm not sure what to do anymore. What can I do?

Heyyo @DarkAlpha.Sete sorry but for some reason, I didn't get a notification for your post.
Just to check, when you said clean flash, did you format data? Wiping data in TWRP doesn't count as it doesn't format the part of the partition that handles encryption and I'm unsure if EvoX or other ROMs even have any encryption on Z01R.
On LineageOS, we use File-Based Encryption to ensure future compatibility with encryption on Android as Google has depreciated Full-Disk Encrytption back on A10. ZenUI stock ROM used FDE, so definitely coming from stock a Format Data is required (and tbh recommended on any device anyways).
Your device isn't bricked, it's just a matter of finding the solution and I suspect it is encryption is the issue.

ThE_MarD said:
Heyyo @DarkAlpha.Sete sorry but for some reason, I didn't get a notification for your post.
Just to check, when you said clean flash, did you format data? Wiping data in TWRP doesn't count as it doesn't format the part of the partition that handles encryption and I'm unsure if EvoX or other ROMs even have any encryption on Z01R.
On LineageOS, we use File-Based Encryption to ensure future compatibility with encryption on Android as Google has depreciated Full-Disk Encrytption back on A10. ZenUI stock ROM used FDE, so definitely coming from stock a Format Data is required (and tbh recommended on any device anyways).
Your device isn't bricked, it's just a matter of finding the solution and I suspect it is encryption is the issue.
Click to expand...
Click to collapse
Intially, do I did not. Something I later found to be a mistake when chatting with the guys over at IRC. I also tried clean flashing with a regular format again to no avail. Even tried the LOS recovery and followed the install instructions as closely as possible (sideloading). TWRP logs would show a message about failing to enable file based encryption (Android Rescue Party). LOS just gave me a screen asking to factory reset, which solved nothing.
I also tried just flashing EvoX again (had no encryption), but it just rebooted back to recovery. Do note that every time I flashed LineageOS/EvolutionX I either formatted or wiped data and tried on both slots most of the times. Nothing changed. Another thing of note is that I was never flashing gapps (trying to degoogle).
Later I even tried LOS 18.1, but no boot as well. By the way, 19 rebooted to recovery right after the Powered by Android screen, but 18.1 got to the boot animation... and stayed there for 15 minutes after which I gave up and flashed stock via the bootloader. Tried flashing LOS again after stock - same thing -, so I'm on stock now.
Sorry for this insane wall of text, but I didn't want to miss anything. Hopefully anything can be taken out of this.

Hmm super odd... Ok, next time you try it, can you check via TWRP if there is anything in here? And if so download a copy and send it to me?
/sys/fs/pstore
Or you can do via terminal
Code:
adb pull /sys/fs/pstore

Dear @ The_Mard
First and foremost, fantastic and fabulous development. You have practically extended the life of the Asus Zenfone 5Z by a straight 12 months! As such in India, 5G - with all band support will take 6 to 12 months (especially handsets with mmwave support), till then I can manage with 5Z.
I have 3 sets of queries / doubts which I have posted as 3 different posts - for better understanding and clarity! When you do have spare time, please do share your thoughts - in the following posts!
I have 3 - 5Z mobiles and I use 2 as my daily driver and 1 as back-up. Yet to update Lineage OS - planning to start with Lineage OS from September 1st. Got to clarify before going all out.
@ThE_MarD

My 1st / First Set of Queries! (My Handset is ZS621KL (Asus Zenfone 5z - 8 GB - 256 GB)
Would like to understand, whether the Lineage OS 19.x will support the standards features of Qualcomm 845 Chipset?
1. Cellular LTE Carrier Aggregation Support - 2x20 MHz carrier aggregation (Up-Load), 5x20 MHz carrier aggregation (Download).
I'm on Jio Network and I have CA supported SIM. Standard Asus ROM used to indicate 4G+ as the network indicator. Will Lineage OS support 2CA for Upload and 5CA for download?
2. Wi fi Support - Does it support Peak 256 QAM Wi-Fi, MU-MIMO & Multi-gigabit Wi-Fi. For MU-MIMO, is it 2x2 or 3x3?
3. Will Lineage OS support Qualcomm® Qualcomm® Quick Charge™ 4 technology?
4. Does Lineage OS support all the APIs - Vulkan® 1.1, OpenCL™ 2.0 Full, DirectX® 12 & OpenGL® ES 3.2?
5. Will Lineage OS support Qualcomm® aptX™ audio playback support & Qualcomm® aptX™ HD?
@ThE_MarD

My 2nd / Second Set of Queries!
These set of queries are from your initial logs #
1. Is the ViLTE working now?
2. any plans to enable 4K UHD Video recording in LineageOS Snap Camera app itself?
3. Is there anyway to activate Widevine L1 using some method - from any other Asus Phone or any other 845 Chipset model or something of that sort? Will writing to Asus through email or Asus Forums help? I can attempt, in case if it's feasible!
@ThE_MarD

My 3rd & Final Set of Queries!
1. Lineage OS Updates - When I check for updates in Lineage OS, I see the update files listed as full 900 MB or so - which means it's a full file download.
Not only it takes bandwidth, but, it seems to rewrite the whole code once again and not merely update the changes alone.
The official upgrades used to be incremental and small in size - where-in I know that it only updates the relevant part of the code which requires change.
Is my understanding right or am I off the standard lineage logic?
I'm also worried that one such FULL LINEAGE update one day will knock off my data and will start as if it's going to be a FRESH upgrade! it will disturb my day to day life an hence such questions!
2. Since I will be moving to Lineage OS, is there any app - which If I install in mobile will keep sending the errors / bugs as log file to the developer? This will help pass the bugs issues / automatically!
If my understanding is right, then the lines in the log file will be (possibly) coloured differentially - which means all error lines will be RED in colour which will help you to address the issues!
Point 2 above is just my wish list and hence was checking if an option of that sort is possible - either automatically or manually!
@ThE_MarD

Develop Bugs

welcome