Hi all,
Here is the thread about Phh-Treble for Android 10.0, codename Quack.
The goal of Phh-Treble for Android 10.0 is the same as for Android 8.0, 8.1, and 9.0: Bring latest AOSP to the maximum number of devices running Google-certified Treble[1], with full hardware support.
You can download latest release at https://github.com/phhusson/treble_experimentations/releases
Which variant do I pick
To know which variant to download, use https://play.google.com/store/apps/details?id=tk.hack5.treblecheck . Don't use other Treble Check apps, they'll give erronous informations.
And then, you're free to choose between vanilla and gapps variant.
What works?
On some devices, everything. They are still not the majority though.
What you can expect on the majority of devices?
It should boot successfully on pretty much all devices with Google-certified Treble. [1]
Most features should work on the majority of devices out-of-the-box: RIL, WiFi, brightness control, buttons, gestures, ...
However, many devices still have issues with hardware video decoding and camera.
Is device XXX supported?
If it's a Google-certified Treble, yes it is. Unlike Google's GSI, Treble devices supported, there is no exception.
There might be bugs of course, but if you help me, I'll fix them!
Which vendor to use?
1. Always use your actual device's vendor
2. Always use OEM unmodified vendor, not some custom vendor
3. This includes boot.img. boot.img and vendor MUST BE the same version.
4. If you're on an Android 8.0 vendor, you'll need to stick to vendors with Security Patch Level before April 2019 (that's a bug of my GSI)
Enjoy!
[1] How do I know my device is Google-certified Treble?
Well it's easy, if your device has first been released with Oreo or more recent, and it has google apps, it has a Google-certified Treble.
Please note that this means only the vendor provided by the OEM is certified, not the one from device-specific ROM.
free post
I want to test it on op7 as soon as possible
Sent from my GM1903 using Tapatalk
---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------
Thank you very much
Sent from my GM1903 using Tapatalk
Nice build, on G6 Play only works with oreo vendor.
A test img boots with pie vendor boots but no sound.
Excellent work :good:
Works well on Huawei P10 lite ( emui 8 ) except:
- Fast battery drain & battery usage isn't aviable
- Unknown model/build number
- There is an internal problem .. ( message ) on boot
- Camera fixed using a patch ( libcamxxx )
Well phh keep up the good worwork, you're doing something different and we appreciate your time and effort in helping other devices with little or no custom ROMs support enjoy the latest version of AOSP
Brilliant work ?
So replying to what you said on the other thread. I wasn't flashing magisk with android q on the s9+ Exynos, does that matter? Because you said that we need your modded magisk
Ive tested v. AOSP 10.0 on the p8lite2017 (PRA-LX1)
Everything seems to work fine, so you will be able to use it daily even now. Everything is fixed but for NFC you need to flash a fix and for GPS: it is partly working and instable. I don't know if there are any improvements in the Versions after v206 since they don't boot.
Every version since v206 will bootloop. You can try to dirty flash it over an booting android 10 ROM but this will cause system problems.
Thanks for everything!
NfC Fix:
https://forum.xda-developers.com/p1...al-fixes-hi6250-devices-t3936745/post81021365
Thanks for all developments!
Last Edit: 13th January 2020
I'm on mi 9 lite (mi cc9) most things work but lockscreen cant be set other then swipe.
{
"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"
}
Please,fix sound
Gửi từ SM-G610F của tôi bằng cách sử dụng Tapatalk
last build v201.. booted properly on YSL Arm64 A only....
Mi 5s Plus
Working - google play service, call, sms, mtp, camera, wifi, mobile data, magisk (phh modified version only), IR blaster, music & video
Not working - bluetooth, gps, some softwares installed through magisk failed to get storage permission (the same software in apk version has no problem).
:good:
Consumer name: Moto X4
Developer name: payton
Model: XT1900-1
Boot type: AB
Arm type: Arm64
Consumer type: Google Fi
Cellular provider: Google Fi
Location: USA
SD card used? No. - Internal storage only (32 GB)
Before install? Full wipe + full firmware flash = clean device
File: system-quack-arm64-ab-gapps.img
Status: Bootable but not yet useable.
Hardware:
The thumbprint device is not working. This means you cannot swipe for navigation or unlock your phone using a thumbprint.
No sound on calls. -- But can make calls
Reboot device is always greeted with "SIM card added" notice telling me to reboot the device. -- I can ignore this and make phone calls.
ROM Software:
Andriod Webview cannot be installed (error received when updating bundled Chrome)
Developer options: OEM unlock is greyed out -- The phone is unlocked.
The navigation menu when enabled does not display.
Google which is bundled with Gapps cannot update.
google pixel can't pass safetynet ?
thus google apps don't work
anyone can ??
phhusson said:
free post
Click to expand...
Click to collapse
Clean flash arm64 a only vanilla on my s9+ with magisk v20 and a custom kernel, but won't boot. I have a logcat if you want that? Not sure why it won't boot. Seems it can't find ANYTHING that is supposed to be in the treble manifest.xml for the device
Nice work. Thanks
I cant get it to boot on my moto g7 power, treble and a/b enabled. flash twrp , install image to system but it just reboots as if there is no OS, system is mounted when flashed.
winxuser said:
Clean flash arm64 a only vanilla on my s9+ with magisk v20 and a custom kernel, but won't boot. I have a logcat if you want that? Not sure why it won't boot. Seems it can't find ANYTHING that is supposed to be in the treble manifest.xml for the device
Click to expand...
Click to collapse
I have successfully installed v201 on my s9+ using csj1 vendor and using latest ww(yarpins) kernel for oneui although this release isnt stable enough for our device as of many UI glitches and many random reboots
justcallmeTHEKID said:
I cant get it to boot on my moto g7 power, treble and a/b enabled. flash twrp , install image to system but it just reboots as if there is no OS, system is mounted when flashed.
Click to expand...
Click to collapse
I'd need logs to confirm, but your issue is likely to be fixed with https://github.com/phhusson/platfor...mmit/477ef41ac3a639f4c34c8ecf323d25ed2d3e8e8e so next release should be good to go.
Related
{
"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"
}
Team OpenKirin presents AOSP Oreo 8.1 for Honor View 10.
It is based upon android-8.1_r14 branch and comes preshipped with a barebones GApps setup.
Current issues:
2G/3G network only show full strength
Wifi Display
QuickCharge/SuperCharge UI indicators missing
Installation
unlock bootloader & extract downloaded zip
flash system.img via fastboot
Code:
[I]command:[/I]
fastboot flash system system.img
do a factory reset via stock recovery and enjoy
Download
https://mega.nz/#!L85zXIbD!xFvraCLhmppx4st0EIjvI5WCaMlKjxO9caGrC3v2CWI
Credits
* @phhusson
* @LuK1337
* @OldDroid
* @surdu_petru
* @XePeleato
Special Thanks
* @svetius
XDA:DevDB Information
Treble AOSP Oreo MR1, ROM for the Honor View 10
Contributors
OldDroid, surdu_petru, XePeleato
Source Code: https://github.com/OpenKirin-Treble
ROM OS Version: 8.x Oreo
Version Information
Status: Testing
Created 2018-02-23
Last Updated 2018-02-22
Reserved
Changelog
* v1 - initial version
* v2 - the cam update
added stock huawei camera
fixed apps not beeing able to read from external storage
add a security patch ui indicator for the oem base under system -> about phone in settings
Good to see lot of ROMS coming...
All these seems to have same bugs for now.
Is this camera same as stock app? If not, are all the features like portrait mode, pro mode works?
venreddy said:
Good to see lot of ROMS coming...
All these seems to have same bugs for now.
Is this camera same as stock app? If not, are all the features like portrait mode, pro mode works?
Click to expand...
Click to collapse
initial release doesn't have the stock cam, yet - thats comming in the next update.
Magisk 16.0 works just fine on this rom, safetynet passes and even my banking apps are working without detecting root
Regards
OldDroid said:
initial release doesn't have the stock cam, yet - thats comming in the next update.
Magisk 16.0 works just fine on this rom, safetynet passes and even my banking apps are working without detecting root
Regards
Click to expand...
Click to collapse
Good thanks.
Thanks Guys....I am using lineage ...was waiting for AOSP 8.1..going to flash it soon.:good:
Good job again.
Thanks for the rom. Just curious why the IMG size is almost double of AOSP rom ?
OldDroid said:
Magisk 16.0 works just fine on this rom, safetynet passes and even my banking apps are working without detecting root
Click to expand...
Click to collapse
I don't get safetynet pass. That's how I tried:
1. Wipe data/factory reset
2. Wipe cache
3. fastboot flash system system.img (this ROM here)
4. fastboot flash ramdisk BKL-L09_ramdisk.img
5. Boot Android
6. fastboot flash ramdisk patched_boot.img
7. Boot Android
8. Install Magisk Manager 5.6.1 -> safetynet fails, Banking apps refuse to start
Any idea?
Nexus lover said:
Apparently I'm not smart enough to get safetynet pass, with or without root.
That's how I tried:
1. Wipe data/factory reset
2. Wipe cache
3. fastboot flash system system.img (this ROM here)
4. Boot Android
5. flash ramdisk patched_boot.img
6. Boot Android
7. Install Magisk Manager 5.6.1 -> safetynet fails, Banking apps refuse to start
Any idea?
Click to expand...
Click to collapse
After you finish flashing the rom
1.Put the Magisk manager and ramdisk boot.img onto the storage of the phone .
2. Install the Magisk Manager.
3. Magisk Manager will prompt you to install the latest Magisk apk which is version 16.
4. Click install and patch boot image.
5. The manager will bring you to the file manager , and you search for the original ramdisk boot IMG. And click on it once.
6 .Wait for the manager to do the patching of boot.img and eventually a patched boot.img is formed .
7. Transfer the patched boot IMG to you ADB file on your computer.
8. Put your phone in fastboot mode and flash it.
9. Reboot and your phone is rooted.
Does the IR blaster now work on the Mate 10 (Pro) ? Apparently there were some issues reported in the previous version.
chen8894 said:
1...
9. Reboot and your phone is rooted.
Click to expand...
Click to collapse
Nobody said it's not rooted. The problem is it doesn't pass safetynet.
New update is up!
Changelog:
* added stock huawei camera
* fixed apps not beeing able to read from external storage
* add a security patch ui indicator for the oem base under system -> about phone in settings
Check OP for download link.
Regards
OldDroid said:
New update is up!
Changelog:
* added stock huawei camera
* fixed apps not beeing able to read from external storage
* add a security patch ui indicator for the oem base under system -> about phone in settings
Check OP for download link.
Regards
Click to expand...
Click to collapse
Great!!!!! Does all features of stock camera works?
Volte working or is Volte a generally problem of all Aosp Rom?
tasar said:
Volte working or is Volte a generally problem of all Aosp Rom?
Click to expand...
Click to collapse
If you need VoLTE you should use stock EMUI for moment. And yes, all custom ROMs have this issue ... no need to ask on each thread the same question !
When the issue will be fixed, it will be clearly stated in OP - so you don't need to ask every day if VoLTE was fixed or not
surdu_petru said:
If you need VoLTE you should use stock EMUI for moment. And yes, all custom ROMs have this issue ... no need to ask on each thread the same question !
When the issue will be fixed, it will be clearly stated in OP - so you don't need to ask every day if VoLTE was fixed or not
Click to expand...
Click to collapse
I don't see VoLTE issue has been mentioned in OP known issues section.
Also please let me know any other issues in this rom?
IR, fingerprint, face unlock, front/rear portrait mode, nfc, huawei share... Working or not?
Do you think desktop mode can be ported over for the mate 10/pro?
hands0m3 said:
Do you think desktop mode can be ported over for the mate 10/pro?
Click to expand...
Click to collapse
It definitely can be, but probably won't happen or at least not right now. We need to port EMUI framework and that requires a lot of work and I think that there are definitely other priorities first
OldDroid said:
New update is up!
Changelog:
* added stock huawei camera
* fixed apps not beeing able to read from external storage
* add a security patch ui indicator for the oem base under system -> about phone in settings
Check OP for download link.
Regards
Click to expand...
Click to collapse
Plz update for honor 8 pro too .. , is this v10 emui stock camera in this rom any difference from that u put in your honor 8 pro's rom stock camera ?
{
"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:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
Click for feature list
Flashing Instructions:
Pre-installation:
TWRP of course (Download from here)
Firmware (Download from here - 10.3.7)
Magisk can also be used just make sure you flash it after a first successful boot (after passed setup screen)
First time installation:
Backup your data to PC, OTG flash drive
Flash recovery (TWRP) downloaded from above link and boot to recovery
Wipe system, data, cache and format data, then reboot to TWRP
Copy firmware, ROM base and Gapps to internal memory then flash them in TWRP in same order
Reboot and enjoy
Update installation:
Boot to TWRP and make a backup
Flash firmware and reboot to TWRP (if there is new firmware available)
Wipe system and cache
Flash updated ROM base and Gapps (and Magisk after boot to system if you had this as root method)
Reboot and enjoy
Download:
ROM https://crdroid.net/beryllium
Changelog: https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/9.0/changelog_beryllium.txt
Thermal mod addon: https://sourceforge.net/projects/crdroid/files/beryllium/5.x/addon/enforcing
Known isues:
- Please tell me
Visit official website @ crDroid.net
crDroid Poco Telegram
crDroid Community Telegram
If you like our work, consider a donation! gwolfu paypal
XDA:DevDB Information
[ROM] crDroid v5, ROM for the Xiaomi Poco F1
Contributors
gwolfu, LOS team
Source Code: https://github.com/LineageOS/android_kernel_xiaomi_sdm845
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: 10.3.7
Based On: LineageOS
Version Information
Status: No Longer Updated
Current Stable Version: 5.10
Created 2018-11-11
Last Updated 2020-01-08
Reserved
quick info
download link is live
enjoy
Tomorrow test, have performance or at the moment nothing?
Enviado desde mi Poco F1 mediante Tapatalk
joni2012 said:
Tomorrow test, have performance or at the moment nothing?
Enviado desde mi Poco F1 mediante Tapatalk
Click to expand...
Click to collapse
this is pretty much first build
haven't had the chance to test performance but should be on par with LOS at least
Will try next day's
Sent from my Poco F1 using XDA Labs
Old friend always same team jeje
2WildFirE said:
Will try next day's
Sent from my Poco F1 using XDA Labs
Click to expand...
Click to collapse
Enviado desde mi Poco F1 mediante Tapatalk
---------- Post added at 10:21 PM ---------- Previous post was at 10:20 PM ----------
No problem, yes yes first compilation
gwolfu said:
this is pretty much first build
haven't had the chance to test performance but should be on par with LOS at least
Click to expand...
Click to collapse
Enviado desde mi Poco F1 mediante Tapatalk
Guys, I was on OnePlus 5T, and gwolfu is a really kind man and an absolutely awesome developer that is maintaining some devices with crDroid. crDroid on OP5T was great for me! Let me thank you another time here @gwolfu and perhaps that I'll join Poco community some time! I'm just hesitating to get this device. Good luck gwolfu
Im getting "Decryption unsuccessful" with "the password you entered is correct, but unfortunately your data is corrupt". this error does not come up when i flash other ROMs.
Tried just now.... After booting it showed phone crashing error... Then showed some internal errors... Finally booted but no network on both SIMs (Jio n Vodafone) ... Showing no IMEI..
I was already on 8.11.7 vender n firmware but still I flashed it again to see if problem resolves but still same...
Tested dark mode n accents which works flawlessly...
auto Brightness working too...
Rom was quite fluid n snappy but due to no network issue I shifted back to Havoc 2.0...
Would love to see great rom n thanks alot to the dev for his efforts...it's official build so expecting it to b the best rom later on... Again thank you for your efforts....
thanks man
quick review:
very stable rom fast and smooth
in every boot there's a pop-up saying about internal problem
ctsProfile false
In the lock screen the location of the battery icon and Wi-Fi changes after unlock back to right location
and there's some options are missing
no option to change dpi manually
no option to swap back and recent
Ryry
Mohammed779 said:
Im getting "Decryption unsuccessful" with "the password you entered is correct, but unfortunately your data is corrupt". this error does not come up when i flash other ROMs.
Click to expand...
Click to collapse
sorry, when exactly do you get this?
tried formatting data in TWRP?
rohanbaviskar530 said:
Tried just now.... After booting it showed phone crashing error... Then showed some internal errors... Finally booted but no network on both SIMs (Jio n Vodafone) ... Showing no IMEI..
I was already on 8.11.7 vender n firmware but still I flashed it again to see if problem resolves but still same...
Tested dark mode n accents which works flawlessly...
auto Brightness working too...
Rom was quite fluid n snappy but due to no network issue I shifted back to Havoc 2.0...
Would love to see great rom n thanks alot to the dev for his efforts...it's official build so expecting it to b the best rom later on... Again thank you for your efforts....
Click to expand...
Click to collapse
internal error on boot is known (should be fixed by next build)
as for sim issue, you don't have a log by chance (as it's working fine here)
gwolfu said:
sorry, when exactly do you get this?
tried formatting data in TWRP?
internal error on boot is known (should be fixed by next build)
as for sim issue, you don't have a log by chance (as it's working fine here)
Click to expand...
Click to collapse
I get it on first boot after I try to enter the decryption pattern. I do format data and system before installing a new ROM. Using a different ROM worked normally so no idea why was it happening with this ROM.
Thanks,
Edit: after formatting the entire phone, including internal storage, i was able to boot to the ROM.
So sim card not detected and notch icons are cutout due to rounded edges of the phone. also a vibration intensity adjuster would be great.
Hi @gwolfu,
I Formatted Internal data to decrypt, Flashed 8.11.7 pie firmware, ROM, open gapps nano, DisableEncryptionZipMagisk17.3 and rebooted. I did not get the network signal. *#06# returned empty popup representing no imei. After flashing some other ROMs, got my signal in that ROM. Don't know what could be the issue.
Nice! Fm radio?
Build 20181113 is ready
Changelog:
- fixed build fingerpring causing a message to pop-up on startup (There's an internal problem with your device contact your device manufacturer)
- fixed SIM detection (and carrier)
- removed su by default
- removed AppOps (still incomplete)
- some other small changes
Please report bugs you encounter, I'll try my best to fix them.
gwolfu said:
Build 20181113 is ready
Changelog:
- fixed build fingerpring causing a message to pop-up on startup (There's an internal problem with your device contact your device manufacturer)
- fixed SIM detection (and carrier)
- removed su by default
- removed AppOps (still incomplete)
- some other small changes
Please report bugs you encounter, I'll try my best to fix them.
Click to expand...
Click to collapse
The internal problem message still pops up.
Thanks,
Mohammed779 said:
The internal problem message still pops up.
Thanks,
Click to expand...
Click to collapse
Make sure to flash vendor file listed in op
Build 20181117 is ready
Changelog:
- updated to November security patches
- updated crDroid styles
- updated gesture settings
- updated Snap cam
- some other general bug fixes and performance improvements
Original thread
{
"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"
}
Background:
This is a natural continuation/extension of the LineageOS 17.x and 18.x GSIs I've been making since November 2019.
Disclaimer:
This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
No flashing instructions will be offered. If you're here in this forum, you should know what you're doing.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Compressed as .xz archives - extract first.
Vanilla except for these changes:
Modifications needed to make it build/boot/feature-complete
Revived navbar layout tuning via sysui_nav_bar tunable
Disabled "vendor mismatch" warning on boot
Signature spoofing support from MicroG
Default stretch-to-fullscreen (force apps to render in longer than 16:9)
Stuff on GitHub (builders-only):
Since builders' stuff aren't really interesting to end users, I decided not to separately document the modifications needed in this post; instead just check out the scripts/patches, where most things should be self-explanatory: treble_build_los, treble_patches (PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you need some clues.
Donate?
https://paypal.me/AndyCGYan
Instructions?
jeeeu94 said:
Instructions?
Click to expand...
Click to collapse
Download and flash system via fastboot or twrp.
MAREK10747 said:
Download and flash system via fastboot or twrp.
Click to expand...
Click to collapse
Hello , for Redmi 7a correct type is treble_arm64_av* ( ARM 64-bit, A-only ) ?
kosmasgr said:
Hello , for Redmi 7a correct type is treble_arm64_av* ( ARM 64-bit, A-only ) ?
Click to expand...
Click to collapse
Not only , A/B works too , but updates update only A partition . You can use A/B image , I have A/B image from @phhusson GSI . For use arm64 images you must patch your device to arm64 . Bases for arm64 is everywhere , but after install base files you can make upgrade to my gameing firmware for better performance .
MAREK10747 said:
Not only , A/B works too , but updates update only A partition . You can use A/B image , I have A/B image from @phhusson GSI . For use arm64 images you must patch your device to arm64 . Bases for arm64 is everywhere , but after install base files you can make upgrade to my gameing firmware for better performance .
Click to expand...
Click to collapse
Thanks , im on crdroid android 10 now and twrp 64 bit istalled
Planning to try this ROM soon,
Any feedbacks?
Thanks.
kosmasgr said:
Thanks , im on crdroid android 10 now and twrp 64 bit istalled
Click to expand...
Click to collapse
If TWRP 64 bit installed, can I use ARM64 or just ARM?
Hi, I'm using 64-bit TWRP and am currently using the Redmi 8 MIUI 12 port. (So I have the 64-bit base). What treble version will work for Redmi 7A?
Hello, Do you need to expand the system to install?
Good ROM. The attempt to install gapps failed. How to solve it?
thank you.
Hi and thanks, yes, latest GSI android 11: AOSP 11.0 v300.m by phhusson working on my Redmi 7A pine (16GB) absolutely properly.
I used TWRP 64bit 3.4: https://androidfilehost.com/?fid=10763459528675581361 , Wiped system, cache, data and Format data, then flash this base: https://drive.google.com/uc?id=1MWxfIf3AepQIGFXDPTpRnZ1G9fnTkheY&export=download and after that flash this version of GSI (including gapps): https://github.com/phhusson/treble_....m/system-roar-arm64-ab-vndklite-gapps.img.xz and looks like everything working good, even bluetooth and GCam 8.1!
(Magisk no work, any versions, but in GSI is inbuilt some type of SU and it is working.)
Only infrared not working in my device and after restart I see info about "intrnal error in device....." (dismatch vendor prop probably or somwthing like that), but when i closed window, it have not effect on functionality - everything exclude infra working like a charm!)
(For PC transfer data you must set in developer settings type of USB connection on transfer, and then is working!)
when in twrp the lineage rom doesnt show but it does when viewing on my computer
Hello,
i´ve "tested" this ROM on my Xiaomi Redmi 7a but it dosen´t boot after flashing with TWRP.
- lineage-18.1-20210212-UNOFFICIAL-treble_a64_bvS
- lineage-18.1-20210212-UNOFFICIAL-treble_a64_bvS-vndklite
TWRP says: "Image Flashing successfully".
After the press on the "System-Reboot-Button" TWRP warns me that no OS is installed.
After the Reboot the Phone boot only to TWRP.
With 17.0 and 17.1 Images i have no problems to boot after flashing.
Sorry for my bad english.
EDIT 2021/03/20: After Upgrade my Xiaomi Redmi 7a to 64bit the ROM is booting after flashing with TWRP.
- lineage-18.1-20210212-UNOFFICIAL-treble_arm64_bvS-vndklite
- lineage-18.1-20210317-UNOFFICIAL-treble_arm64_bvS-vndklite
But I have 2 huge Bugs with both ROMs:
1. Can´t decrypt Data with PIN or Password in TWRP (TWRP says everytime: password incorrect)
2. Data-Transfer over USB to PC doesn´t work (not selectable)
lineage-18.1-20210317-UNOFFICIAL-treble_arm64_bvS-vndklite has 2 more little Bugs:
1. No Ringtones are selectable
2. Design & Backgrounds are not accessible from Homescreen
Greetings. Everything works well, thanks. Is it possible to add FaceUnlock (Face ID) to Lineage 18.1 on my Redmi 7A? Using magisk or TWRP?
Zwer121 said:
Greetings. Everything works well, thanks. Is it possible to add FaceUnlock (Face ID) to Lineage 18.1 on my Redmi 7A? Using magisk or TWRP?
Click to expand...
Click to collapse
you have tutorials bro?
Hi guys.
I used a different way:
coming from Stock Rom (V11.0.3.0) --> from https://c.mi.com//miuidownload/detail?device=1900369 via Miflash
fastboot unofficial twrp 3.3.1.1 pine --> from https://www.mediafire.com/file/irntn5ccdiguuuu/TWRP-20191023-3.3.1.0-pine.img/file
format & wipe
flash fw+vendor-arm64_pine_11.0.11GLOBAL-v1.2.zip --> from http://www.mediafire.com/file/yz5o5fn7yx9zkgv/file
and yes this is a higher version than this:
Axident1973 said:
then flash this base: https://drive.google.com/uc?id=1MWxfIf3AepQIGFXDPTpRnZ1G9fnTkheY&export=download
Click to expand...
Click to collapse
then i flashed different .img files:
1st.
this Rom from
[ROM][9.0][OFFICIAL][PINE][NIGHTLY][SHARE] MoKee Open Source Android Project
/* * 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...
forum.xda-developers.com
but the new Android 10 version --> from https://download.mokeedev.com/pine.html
boots completely but crashes then
2nd.
system-roar-arm64-ab-vanilla.img --> from https://github.com/phhusson/treble_experimentations/releases/tag/v304
after startup "internal android error" occures but it works
haven'd tested much, but didn't noticed any bugs in the first place. stock camera and brightness works.
3rd.
suggeted lineage-18.1-20210411-UNOFFICIAL-treble_arm64_bvS.img rom --> from https://sourceforge.net/projects/andyyan-gsi/files/lineage-18.x/
works but with flickering brightness sensor
so i repeated it, and the second time it works fine
then another try with flashing magisk --> from https://magisk.me/zip/
but ramdisk = No
so not possible? (only in recovery mode)
and flashing fm fix --> from https://androidfilehost.com/?fid=8889791610682885147
What's working:
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
LED
Not tested:
GPS
VoLTE
ViLTE
Known issues:
Notification LED can only be used with white color
signed with public keys (Trust Agent warning)
root only possible with magisk on recovery mode
if i can find a way to root i would be happy with my Android 11 phone
thanks and greetings
I miss the automatic call recording feature in this version. Manual activation on every calls working correctly, but it is impractical.
{
"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"
}
Well, we're finally getting some relatively stable builds of AOSP GSIs and OpenGApps for Android 11.0, so here's my first effort at migrating the Nexus Stock custom ROM for the 2019 Galaxy Tab A 10.0 [SM-T510] to the latest Android OS release. It's very much a work in progress, but it should hopefully help blaze the trail for even better work.
Notes:
The current process may require you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and are generally based on the latest update for the SM-T510. Note that the bootloader in this release has roll-back prevention.
The system is based on eremitein's CAOS GSI project with the latest Stock variant from OpenGApps.
Boot logo and default wallpaper is from my Nexus series of custom ROMs for Android TV, and I'm using the Pixel boot animation with black background.
Stock recovery will be replaced with my latest TWRP build for the SM-T510.
I've dialed back most of scary bootloader warnings and Knox Security branding from the boot sequence.
The properties now correctly identify the device as a tablet, and so the Google Dialer is no longer installed. I've also disabled the Emergency button, but SetupWizard still insists on reminding you to insert a SIM (sigh!).
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 file-based encryption
Cold charging (low power mode) animates to about 39% and then reboots.
Downloads:
Nexus_Stock_CR_T510XXU5CUL1-20220219.tar.md5 (Odin tarball)
Nexus_Stock_CR_T510XXU5CUL1-20220219.zip (TWRP update)
Build archives:
Android File Host
Change Log:
20220219:
Vendor partition and custom kernel based on T510XXU5CUL1 OEM firmware (December 2021 Update)
System partition based on CAOS 11.0 v315 (January 2022 Security Update)
Latest Google apps from OpenGApps (20220215) w/ rollback for GoogleTTS
20211125:
Vendor partition and custom kernel based on T510XXU5CUJ1 OEM firmware (October 2021 Update)
Update to TWRP v3.6.0 custom recovery on AOSP 11
Latest Google apps from OpenGApps (20211125) w/ rollback for GoogleTTS
20211120:
System partition based on CAOS 11.0 v313+ (October 2021 Security Update)
Latest Google apps from OpenGApps (20211120) w/ rollback for GoogleTTS
20210825:
Vendor partition and custom kernel based on T510XXU5CUF4 OEM firmware (June 2021 Update)
System partition based on CAOS 11.0 v312 (August 2021 Security Update)
Update to TWRP v3.5.2 custom recovery
Latest Google apps from OpenGApps (20210825-TEST)
20210318:
Fixed custom Pixel Launcher so that icon positions are saved.
Fixed clipped pixels on edge of launcher search bar.
Defaults icon layout to 7 columns for main, hotseat and app drawer, just like it used to be for the Nexus 10. (For 6 column layout bump display scaling to Large.)
20210314:
Vendor partition and custom kernel based on T510XXU4BUA1 OEM firmware (January 2021 Update)
System partition based on CAOS 11.0 v302 (March 2021 Security Update)
Update to TWRP v3.5.1 custom recovery
Latest Google apps from OpenGApps (20210130-TEST)
20210216:
Initial build based on T510XXU3BTK1 kernel (November 2020 Update) and CAOS 11.0 v300m.
Latest Google apps from OpenGApps (20210130-TEST)
Instructions:
From OEM stock firmware:
Unlock bootloader
Ensure matching OEM build (e.g. T510XXU3BTK1) is installed
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
When TWRP launches, factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Reboot to system
From existing TWRP install (for incremental updates):
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install, select your update (.zip file), and then swipe to install
Reboot to system
Source:
android_device_samsung_gta3xlwifi
android_device_samsung_gta3xl
Phh-Treble
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @phhusson for Treble GSIs and @eremitein for CAOS, so please show them some love!
Reserved.
Worked fine for me. Thanks.
I can't get Magisk 21.4 to work on this rom after updating with TWRP. I also tried to patch the boot.img with Magisk Manager.
Has someone else this working? I will temporary return to Android 10.
waterpolo said:
I can't get Magisk 21.4 to work on this rom after updating with TWRP. I also tried to patch the boot.img with Magisk Manager.
Has someone else this working? I will temporary return to Android 10.
Click to expand...
Click to collapse
I haven't been able to root any ROM based on AOSP 11.0...even the S variants that include su , but I'm not really an expert on rooting.
Yep magisk not working for me also, thats a shame because it's quite smooth overall, hoping for it to work in the next updates
For my Samsung mobile device I see on the XDA forum that Magisk is included in the ROM and isn't allowed to updated when a new version is released, only the Magisk manager could be updated.
I am afraid that installing seperate as on Android 10 isn't possible anymore.
waterpolo said:
For my Samsung mobile device I see on the XDA forum that Magisk is included in the ROM and isn't allowed to updated when a new version is released, only the Magisk manager could be updated.
I am afraid that installing seperate as on Android 10 isn't possible anymore.
Click to expand...
Click to collapse
The problem with that is that there is no Magisk Manager in Play Store with this ROM.
edit: Something appears to be going on with Google and Magisk and it is NOT just with this ROM or even this device. Apparently Google has not only removed Magisk Manager from the Play Store but have done something to keep it from giving root privileges all together!!!
re-edit: I apologize. I panicked. The problem appears to be with this device and the latest version of Magisk and with this ROM and Magisk. I can get version 20.4 to work with other ROMs, but it hangs with this one.
- scratched -
If anyone finds a version of Magisk that works with this ROM, please post it. I've tried V20.4, which causes a hang during boot, and V21.4, and 21.2, which boot but don't work.
lewmur said:
If anyone finds a version of Magisk that works with this ROM, please post it. I've tried V20.4, which causes a hang during boot, and V21.4, and 21.2, which boot but don't work.
Click to expand...
Click to collapse
Magisk V20.4 isn't for Android 11+. Therefor you have to install V21, but unfortunately is this not working.
is this ROM good for daily use or better to use the Android 10 one?
Broman400 said:
is this ROM good for daily use or better to use the Android 10 one?
Click to expand...
Click to collapse
1)
maybe there a bug with Wifi and connections with WPA3 (with PMF), only WPA2 is working here.
But this is a weak statement, cause I'm running a Beta FW on my Router (FB 7590) with some wifi bugs in the past. - I mean my Galaxy S4 with LOS 18.1 hadn't that - I'm not sure -
- EDIT-
Release Router FW arrived today: same result.
2)
my arranged apps/icons in the bottom line are resetted to the default google after an reboot.
whereby:
removing some google apps out of the bottom line will survive a reboot, all other arrangements won't.
e.g. I removed nearly all google apps and left only the outer left and right (see the above 1st screenshot) and dropped installed apps in the free place.
turns out: only the google apps (playstore + camera) are there after an reboot.
could someone check that ?
PMF:= Protected Management Frames
IEEE 802.11w-2009 - Wikipedia
en.wikipedia.org
Great work out there. Can you do this rom for SM-t515?
I can't find any lineage or ressurection rom for this tab
ryan.sn0w said:
Great work out there. Can you do this rom for SM-t515?
I can't find any lineage or ressurection rom for this tab
Click to expand...
Click to collapse
Sorry, I don't have a SM-T515 and it doesn't share the same kernel as the SM-T510. I've tried building ROMs blindly before, and you really can't do it without hardware for testing.
hi,
you wrote : "Ensure matching OEM build (e.g. T510XXU3BTK1) is installed"
My actual OEM is T510XXU4BUA1 which is newer than 510XXU3BTK1.
So each time i try to flash , I've got the message SYSTEM REV CHECK FAIL DEVICE : 4 BINARY : 3 (VENDOR).
I understand that i need to downgrade to T510XXU3BTK1. Is it possible to downgrade inside ANDROID 10 from an OEM 4 bits to an OEM 3 bits? How to do this?
Found the solution. Flash with heimdall orange fox recovery + multidisabler + RR custum ROM then full wipe + nexus custom ROM. All is working, good job, nice fast ROM.
@isaacragui
could do me a favor ?
with your fresh installed LOS, please check from comment #13, point 2)
I would like to know if it's only me.
rw_on_xda said:
@isaacragui
could do me a favor ?
with your fresh installed LOS, please check from comment #13, point 2)
I would like to know if it's only me.
Click to expand...
Click to collapse
Sorry i've almost immediatly switched to a AOSP ROM after having flashed LOS. Not because not working, but prefer AOSP.
Will check if return to LOS.
isaacragui said:
Sorry i've almost immediatly switched to a AOSP ROM after having flashed LOS. Not because not working, but prefer AOSP.
Will check if return to LOS.
Click to expand...
Click to collapse
thanks anyway
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ArrowOS
ABOUT
ArrowOS is an AOSP/CAF based project started with the aim of keeping things simple, clean and neat.
Website: https://arrowos.net
Telegram: Channel | TG Portal/Links
Github: https://github.com/ArrowOS
Code Review: review.arrowos.net
E-mail: arrowos.contact
PayPal: Donate to us
Blog: blog.arrowos.net
Checkout more documentation at (maintainership/contributing): Check this out
WHAT WORKS?
Almost everything
WHAT DOESN'T WORK?
Volte, Wifi Calling and other samsung proprietary apps
Be sure to include a log : check how to
DOWNLOADS
ArrowOS - Downloads
SUPPORT GROUP
Telegram
Read our blog article/post about:
* HOW-TO report a bug
* GAPPS and VANILLA variants
* Checking build integrity
ROM Source: https://github.com/ArrowOS
Kernel Source: https://github.com/ArrowOS-Devices/android_kernel_samsung_exynos9810
CREDITS
ArrowOS Team for the rom sources
All the tester and developers in Exynos9810 TG group
Official Arrow 12.1 OSS is hereChangelog :
Arrow 12.1 based on Android 12.1.
May Security update
Fully rebased on latest Joisp(los19.1) trees.
Audio hal updated to V7
Using stock oneui APN config file for better carrier support.
Updated Mali blobs and many other from N770F.
Fixed USB Audio.
Fixed WPA2-EAP connection.
Dolby profile works similar to stock oneui.
Fixed Spen cursor and landscape mode.
Kernel upstreamed from 4.9.291 to 4.9.312 thanks to @nils
Increase the thickness of Status bar to fit privacy indicators pills. Thanks to @Dylan for convincing me lol.
Support for N variant.
Switch to aidl vibration hal , better effect and be customized from the accessibility menu.
Fixed Ok google
Better overall performance and battery life,
F2FS support for both data and cache.
And many more small changes here and there.
Known Bugs:5Ghz HotspotWhat about encryption:
Flashable zip to enable encryption is in this post
How to enable encryption
I posted this in Telegram Channel :"One important thing is the encryption thing and I know the majority voted for it to be included but I'm truly sorry to go against the majority as encryption will make my development work much slower and there will be always a risk to lose data from my side which I can't afford. So no force encryption in arrow-12.1 and it won't work unless it was forced at boot(changed in fstab).However I'm planning to provide a flashable file that will enable encryption but it need further testing to make sure everything is working correctly.I hope everyone understand my decision and sorry again if you don't agree with it."Flashing InstructionSteps : Coming from Arrow 12.0 or different ROMs1-Wipe vendor , system , data , cache2- Flash Rom , gapps (for Vanilla version) and magisk (if needed) 3- RebootFrom unofficial Arrow 12.1Drifty flash.
Difference between Arrow 11 and Arrow 12 for our devices :
Kernel is updated from scratch to latest android-4.9 including F2FS
LZ4 was updated to latest available.
Zstd was updated from linux kernel 5.10.
Ok google is fully working (on/off screen)
Google maps no longer zoomed
Cleaned up the trees
Recommend Gapps for vanilla version:
Flamegapps basic
How to make ok google working (Vanilla version)
Flash flamegapps basic
Flash flamegapps addon (search and assistant)
Assign google app as default assistant
Give google app all permissions
Device reboot after selecting usb transfer
In case device reboot when selecting usb transfer you can do the following:
A- Disable usb debugging in developer settings.
Or
B- from developer settings select usb transfer as default usb configuration
Flashing Instruction
Coming from noble ROM (one UI 3.1) you need to wipe vendor then flash Your device's stock vendor Coming from aosp , no vendor wipe/flash is needed.
Steps :
1-Wipe vendor , system , data , cache
2-flash vendor as vendor image (only if you were on noble ROM (one UI 3.1)
3-Rom , gapps (for Vanilla version) and magisk (if needed)
4- Reboot and Ur good to go .
thanks, awesome OS
Thanks for this awesome rom! How to flash when coming from Stock rom? (Stock oneUI 2.5 Android 10)
BinukaSL said:
Thanks for this awesome rom! How to flash when coming from Stock rom? (Stock oneUI 2.5 Android 10)
Click to expand...
Click to collapse
Backup your data
Make sure you have twrp installed
Then wipe system,data, cache
Flash ROM
How do i root this
Great Rom...Thanks.. But is there any way to use Stock Note 9 Camera on this rom?
Is the ability to pause apps part of the rom? Check on the screenshots.
Adoorkhan said:
Great Rom...Thanks.. But is there any way to use Stock Note 9 Camera on this rom?
Click to expand...
Click to collapse
It is already mentioned in the OP that , "samsung proprietary apps wont work" in any of the AOSP ROMs. That includes, Samsung Camera also which can not be ported to AOSP ROMs.
N960N can use this rom
Been using this rom for about 4 days now and I must say it's just perfect. So far I haven't encounter any bugs, the performance is great and the ui is stunning. Highly recommend it. Device - Note 9
levi.king said:
N960N can use this rom
Click to expand...
Click to collapse
Yes. make sure to flash your stock vendor if coming from noble rom
My apologies if this is the wrong forum thread. I saw the article below.
Samsung Galaxy S9 and Galaxy Note 9 can now run Android 12, unofficially
The Samsung Galaxy S9, S9 Plus, and Galaxy Note 9 have received unofficial ports of Android 12 through the ArrowOS custom ROM. Read on!
www.xda-developers.com
I have a "Verizon" Note 9. Is it possible for me to upgrade to Android 12 or is my phone locked? My understanding is that Verizon locks their Samsung phones.
I tried to install it, but it enters the download location and stays, can you help?
I was installing this rom and was coming from noble rom. I did not do a proper wipe after which now the phone is dead. I am not seeing any thing. When I press power button i dont see any thing. Only force restart works (volume down and power button) but after that nothing happens. Any idea how to fix.
mkanet said:
My apologies if this is the wrong forum thread. I saw the article below.
Samsung Galaxy S9 and Galaxy Note 9 can now run Android 12, unofficially
The Samsung Galaxy S9, S9 Plus, and Galaxy Note 9 have received unofficial ports of Android 12 through the ArrowOS custom ROM. Read on!
www.xda-developers.com
I have a "Verizon" Note 9. Is it possible for me to upgrade to Android 12 or is my phone locked? My understanding is that Verizon locks their Samsung phones.
Click to expand...
Click to collapse
you need to unlock the bootloader first. I don't know if this is possible.
dyolal2 said:
I tried to install it, but it enters the download location and stays, can you help?
Click to expand...
Click to collapse
Flash your stock vendor. I will add vendors to the main post later today.
sherry9oct said:
I was installing this rom and was coming from noble rom. I did not do a proper wipe after which now the phone is dead. I am not seeing any thing. When I press power button i dont see any thing. Only force restart works (volume down and power button) but after that nothing happens. Any idea how to fix.
Click to expand...
Click to collapse
flash any oneui 2.5 then boot to system / reboot to twrp and follow the instructions
Works perfectly! I feel like battery life also better than oneUI <3 Thank you for the great effort!
Clock app is crashing, I've installed the linked Gapps Arrow-v12.0-crownlte-OFFICIAL-20211227-GAPPS.zip. Anyone facing this problem?
vinodrodricks said:
Clock app is crashing, I've installed the linked Gapps Arrow-v12.0-crownlte-OFFICIAL-20211227-GAPPS.zip. Anyone facing this problem?
Click to expand...
Click to collapse
Nope, seems to work fine. I've also installed the linked gapps
Aadil321 said:
Nope, seems to work fine. I've also installed the linked gapps
Click to expand...
Click to collapse
My bad, installation process was wrong. It's working now