Requirements:
installed:
1.twrp3.2.3-z2x
ZUK edge Treble - Google Drive
drive.google.com
2.Z2151_CN_OPEN_USER_Q00030.1_O_ZUI_4.0.282_ST_181017_qpst
Installation:
1.TWRP---wipe---Format Data(Type yes).
2.Flash partition.zip
3. Wipe the Dalvik/ART cache, cache, system, data .
4. Flash RR-O-v6.1.0-20180728-z2x-Unofficial
ZUK edge Treble - Google Drive
drive.google.com
5.Wipe factory Reset(Some GSI may have to be wipe: system, cache, data, dalvik/cache。)
6. Flash android10、11 GSI arm64 Aonly image
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
7. Wipe factory Reset
8. Reboot and enjoy!
9.Optional Flash Certification_Patch_V2,[R]TeamDrivers_OpenGL-Vulkan_SD820-SD821_v4.5(For android10 GSI only!)
ZUK edge Treble - Google Drive
drive.google.com
Android 11 GSI notification ringtone fix:
On TWRP, mount system, advanced setup file management.
Copy the file“mediaextractor” and paste it into:
system/system_ext/apex/com.android.media/etc/seccomp_policy/mediaextractor.policy
Android 11 GSI Flash Screen Fix:
Flash GSI img files and boot the system, back to TWRP flash "adreno-5xx-v313-rev23-treble"。
Android 11 GSI Aonly Magisk Solutions:
1- Install magisk apk
2- Go to twrp & flash MAGISKA11-a-only
3- Flash Magisk-v22-canary-phh
4- Reboot and enjoy
DotOS-arm64-a-only and AncientOS-R-Society-v5.2-ARM64_A-only-Iron-20210227-vanilla can't boot,The following zip files can help boot and fix bugs.after flash GSI img to the system partition,flash this zip,wipe factory reset,reboot.
Thanks:
Art Chen
@hamido @kukuruyuk_pagi，@iam，@eternityson,@Ashle
AOSP V300.l
CAOS V300l avZ
Very interesting thread.
For gsi system a only as flyme emui coloros is same steps?
TarAntonio said:
Very interesting thread.
For gsi system a only as flyme emui coloros is same steps?
Click to expand...
Click to collapse
you device SD/vndk/Aonly or ab?go to learn GSI:https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
crDROID 6.14 work well.thanks:Braialindo, Guilherme2041
Tims Fong said:
you device SD/vndk/Aonly or ab?go to learn GSI:https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
Click to expand...
Click to collapse
Hey are you talking about zuk edge? What learn . I flashed an havoc pie gsi
someone has the link to download ?? ----> Z2151_CN_OPEN_USER_Q00030.1_O_ZUI_4.0.282_ST_181017_qpst
I get an error on twrp trying to flash RR-O-v6.1.0-20180728-z2x-Unofficial. It reads E2001: Unable to mount Vendor. Any help ?
Meminsim said:
I get an error on twrp trying to flash RR-O-v6.1.0-20180728-z2x-Unofficial. It reads E2001: Unable to mount Vendor. Any help ?
Click to expand...
Click to collapse
do you use this TWRP" recovery_vendor "?
Yes I do. Twrp 3.2.1
Meminsim said:
Yes I do. Twrp 3.2.1
Click to expand...
Click to collapse
try reboot to recovery,flash RR6.1.0 again.
I'm just telling you that on AOSP 11.0 V300.m still no have a notification ringtone, and you can't install a display driver, otherwise you can't boot.
Havoc-OS-v4.1-20210208-arm64-aonly-Official.img
CAOS V300m
lineage-18.1-20210212-UNOFFICIAL-treble_arm64_avS.img
I've almost tested all of gsis
same problem for most of them is that camera is too slow and too laggy. u may w8 for 10 secs until camera operates.
most of gsis have problem with fingerprint sensor.
is there any solution for these problems?
Agostino251 said:
I've almost tested all of gsis
same problem for most of them is that camera is too slow and too laggy. u may w8 for 10 secs until camera operates.
most of gsis have problem with fingerprint sensor.
is there any solution for these problems?
Click to expand...
Click to collapse
Yes, these are the characteristics of GSI, 1. No automatic brightness. 2. It takes 10 seconds for the front and rear cameras to switch. 3. Fingerprint unlock is not sensitive. Overlay is required to resolve these issues：https://github.com/phhusson/treble_experimentations/wiki/How-to-create-an-overlay?
Please come to this group and you will learn more: https://t.me/phhtreble
caos-v300m-210219-arm64-avZ.img + open_gapps-arm64-11.0-nano-20210130-TEST + adreno-5xx-v313-rev23-treble，Notification ringtones have been fixed, are already very stable, and can be used daily.thanks： eremitein
lir-v300m-210221-arm64-avZ.img + open_gapps-arm64-11.0-nano-20210130-TEST
thanks： eremitein
Related
Project Treble For Xperia XBased on Sony Open DevicesThanks to Pavel's KernelI am not responsible for bricked devices, dead SD cards,.Suitable for F5121 and F5122Reboot after your first boot please!
请中文用户遵守XDA规则，使用双语留言
If Your Camera doesn't work, see #141 please
Required files:
Our treble file could support Erfans's Android Q GSI, You need to flash this fix.
If you meet crash, you need to delete vendor/overlay.
If you meet endless bootanimite, Try to force reboot.
[New SODP Kernel version]
V20190812:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.zip
V20190811:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.zip
[Pavel's Kernel versions]
V20190702:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v9_loire.zip
V20190503:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v8_loire.zip
V20190501:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v8_loire.zip
[Old SODP Kernel versions]
V20190429:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v8_loire.zip
V20190323:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v7_loire.zip
V20190210:Link With: SW_binaries_for_Xperia_Android_9.0_2.3.2_v5_loire.zip
[OEM-File]
DownloadLink
[TWRP-Q]
DownloadLink
How to go Treble?
First: Flash Twrp I built which supports a Vendor Partition
Code:
fastboot flash recovery < Path of recovery.img >
Second:Wipe Data and Cache, then flash Treble-X-sjll-XXX.zip in Twrp .
Notice:If you failed when flashing Treble-X-sjll-XXX.zip in Twrp or can't boot into desktop. Please do follwing command:
Code:
fastboot flash boot < Path of boot.img >
Code:
fastboot flash cache < Path of vendor.img >
Third: flash SW_binaries provided by Sony.
You can download it from Sony official website.
Code:
fastboot flash oem < Path of OEM.img >
Optional step If treble file without system
Fourth: Flash a GSI compatible System image and boot!
Code:
fastboot flash system < Path of GSI-System.img >
Google Camera Guide:
1.Gcam must work with Google play services.
2. Suzu doesn't support raw Format Raw10, we should set raw Format to Raw Sensor .
3.We should set Viewfinder Format to YUV_420_888
4.Please enable: Buffer Fix to Fix viewfinder lags.
5. Suzu only support Init SlowMo at 120 FPS
Recommend Gcam Version:
ARNOVA8G2 Link
Gcam_6.1.021_Advanced_V1.7beta3.190707.0105.apk
Gcam_6.2.030_Advanced_V2.2beta5.190704.1015.apk
Update and known BUG:
20190812:
Update:
1. Thermal back, you will not hot in this summer.
2. CPU quiet back, suzu will be cold as ice.
3. F2FS support for cache(Qnovo) and userdata partitions.
20190811:
Update:
1. Go back to SODP kernel.
2. Performance and stability improve.
3. A lot of Fixes of SODP.
20190716:
Update:
1. New twrp-Q uploaded.
V20190702:
Fixes:
1. Cancel OverClock.
2.New CAF imported in kernel.
3.Forcecryptable canceled. If you upgrade from old version, you need to format userdata and use new TWRP-Q.
Bugs:
Need feedback.
V20190503:
Fixes:
1. New PowerHAL.
Bugs:
Need feedback.
V20190501:
Fixes:
1. Use Pavel's kernel source codes.
2. Quick Charge 3.0 works fine.
Bugs:
Need feedback.
V20190210:
Bugs:
1. Quick Charge is broken, you can use computer USB port charge.
2. Camera doesn't work on first boot, you need to reboot.
Source Codes
Sjll
Kernel
Contributors
Sjll @Cubbins
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Paypal
I am very happy to receive your donation.
Version Information
Status: Testing
Created 2019-02-10
Last Updated 2019-08-12
Hi! And it is possible to flash system.img via TWRP?
Since the latest TWRP (3.2.2.2) can flash those partitions, can we flash through it?
realthrash said:
Since the latest TWRP (3.2.2.2) can flash those partitions, can we flash through it?
Click to expand...
Click to collapse
no, I tried
Is it A Only or A/B type?
sebasrock156 said:
Is it A Only or A/B type?
Click to expand...
Click to collapse
A only.
[email protected] said:
Hi! And it is possible to flash system.img via TWRP?
Click to expand...
Click to collapse
realthrash said:
Since the latest TWRP (3.2.2.2) can flash those partitions, can we flash through it?
Click to expand...
Click to collapse
Use the twrp provided by me, it can flash these partition with an img file.
After install this ROM..I dont have root acces and how to enter the treble twrp because I cant enter it after flashed this ROM:crying:
So I just installed the ROM.
On my first try, it just did not boot. Stuck at Sony logo. I then flashed the latests stock .ftf, did the installation again and managed it to boot. Seems that I did not have the latest bootloader
After the initial boot, I wanted to enter recovery again, but could not get into it. I then flashed TWRP 3.2.3.2 and could install the gapps from there. The system also runs with this recovery.
What I already tested:
- camera shows only up to 17,1 Megapixels, but works
- front camera works
- camera button works
- WIFI works
- mobile data wiht LTE work, but I had to type in the APN manually
- phone calls work
- fingerprint works
- bluetooth works, but I cannot pair with my Garmin watch (have the same problem when using lineage OS)
Overall the system looks and feels really great! Added some screenshots too!
Well done, @Sjll ; Thank you very much!
Thelooks14 said:
After install this ROM..I dont have root acces and how to enter the treble twrp because I cant enter it after flashed this ROM:crying:
Click to expand...
Click to collapse
Just using fastboot flash a GSI in system partition.
Please use the twrp I privide for treble.
If you want to go to recovery, just shutdown and hold power and Vol-.
sessions04 said:
So I just installed the ROM.
On my first try, it just did not boot. Stuck at Sony logo. I then flashed the latests stock .ftf, did the installation again and managed it to boot. Seems that I did not have the latest bootloader
After the initial boot, I wanted to enter recovery again, but could not get into it. I then flashed TWRP 3.2.3.2 and could install the gapps from there. The system also runs with this recovery.
What I already tested:
- camera shows only up to 17,1 Megapixels, but works
- front camera works
- camera button works
- WIFI works
- mobile data wiht LTE work, but I had to type in the APN manually
- phone calls work
- fingerprint works
- bluetooth works, but I cannot pair with my Garmin watch (have the same problem when using lineage OS)
Overall the system looks and feels really great! Added some screenshots too!
Well done, @Sjll ; Thank you very much!
Click to expand...
Click to collapse
You can flash a GSI to get better experience. Thanks for your feedback!
Sjll said:
Just using fastboot flash a GSI in system partition.
Please use the twrp I privide for treble.
If you want to go to recovery, just shutdown and hold power and Vol-.
Click to expand...
Click to collapse
Where I can download GSI?
sessions04 said:
So I just installed the ROM.
On my first try, it just did not boot. Stuck at Sony logo. I then flashed the latests stock .ftf, did the installation again and managed it to boot. Seems that I did not have the latest bootloader
After the initial boot, I wanted to enter recovery again, but could not get into it. I then flashed TWRP 3.2.3.2 and could install the gapps from there. The system also runs with this recovery.
What I already tested:
- camera shows only up to 17,1 Megapixels, but works
- front camera works
- camera button works
- WIFI works
- mobile data wiht LTE work, but I had to type in the APN manually
- phone calls work
- fingerprint works
- bluetooth works, but I cannot pair with my Garmin watch (have the same problem when using lineage OS)
Overall the system looks and feels really great! Added some screenshots too!
Well done, @Sjll ; Thank you very much!
Click to expand...
Click to collapse
can you still enter recovery mode now?
I could only enter recovery with TWRP 3.2.3.2!
So I jused Sjll's recovery vor initial installation and then changed to 3.2.3.2
But I am not sure, if the Treble updates will work with this TWRP...
I used your guide to install another treble ROM
Thanks
One question:
I can root without any problem, but if I reboot the phone the data partition gets encrypted, ¿what can I do to solve this?
Today I made a lot of pictures with the front camera and with the back camera. . AF just doesn't get a sharp picture. Front camera is totaly useless for selfies, even with perfect light conditions.
I downloaded Google Camera app, which makes it a little bit better, but still not comparable to the stock Sony Camera App. Oh, and it just shows 13 MPx max res.
Too bad!
Anyone here with better results?
sessions04 said:
Today I made a lot of pictures with the front camera and with the back camera. . AF just doesn't get a sharp picture. Front camera is totaly useless for selfies, even with perfect light conditions.
I downloaded Google Camera app, which makes it a little bit better, but still not comparable to the stock Sony Camera App. Oh, and it just shows 13 MPx max res.
Too bad!
Anyone here with better results?
Click to expand...
Click to collapse
These are bugs of SODP. only waitting for their fix.
where to get boot.img?I can't flash zip
There is a Link in the first post, next to
"[Tested]
V20190210 Link... "
You find the "twrp-Q.img" there.
WARNING: You'll most probably loose ALL your data, and might break your phone. Please use with extreme caution!
The goal of this ROM is to experience ColorOS 6.0 on any non-oppo and non-realme phone.
For a list of treble supported devices, consult and fill https://github.com/phhusson/treble_experimentations/wiki
How to flash:
1- Flash a treble pie rom (CAF vendor recommended.)
2- Extract 7z file and flash system.img
3- If base rom isn't permissive flash permissiver.
4- Reboot
Bugs:
- Fingerprint
- Since it's oem port maybe more on your device. But common bug is Fingerprint.
Download:
system.img for A-A/B ARM64 devices
Telegram Account: MacTavishAO In case of any problem please send me logs.
Thanks to: @erfanoabdi for everything..
Reserved. You can follow me on github.
Changelog:
1.0: Initial release.
Does it include stock sounds and ringtones? Thanks
ZoiraP said:
Does it include stock sounds and ringtones? Thanks
Click to expand...
Click to collapse
yes
Nice work.
Keep it up.
After reebot after flashing system, back to recovery. Any solution? Device Nubia Z17 (NX563J)
surfer30 said:
After reebot after flashing system, back to recovery. Any solution? Device Nubia Z17 (NX563J)
Click to expand...
Click to collapse
You need pie treble vendor, permissiver.
I flashed over Lineage 16GSI (android 9). But not flashed permissiver - you sugested tryed once more?
Kanka Lenovo Z5 direk crash diag bölümüne atıyor dediklerini harfiyen yaptığım halde.
Lenovo Z5(L78011) didnt work.
Stuck on boot logo. My Vendor is CAF and flashed permissiver V2
Couldn't flash in nokia 6.1 plus
Image file size larger than target device eror in twrp ..
Plz solve my problem..:crying:
Either bootloops or doesn't get past the boot image on Note9 N960F no matter what. (Different kernels, flash on different systems etc.)
rahul387 said:
Image file size larger than target device eror in twrp ..
Plz solve my problem..:crying:
Click to expand...
Click to collapse
That isnt how it works
Some random said:
That isnt how it works
Click to expand...
Click to collapse
When i flash color os in my nokia 6.1 plus .. its showing me that the image file is bigger than target device!!
Any solution for me ..?
I have 2 questions :
1) Can I flash this ROM on Mi Max 2 with Orange Fox 10 recovery?
2) Can this be used for daily life usage?
Thank you
No boot
System partition smaller than image
rahul387 said:
When i flash color os in my nokia 6.1 plus .. its showing me that the image file is bigger than target device!!
Any solution for me ..?
Click to expand...
Click to collapse
I read that we have to resize the system partition when that error occurs. It's too advanced for me so I left it.
Kicked into fastboot
I've tried installing it exactly as described here and also how it's described for other pie GSIs for oneplus5t but I only get kicked into the fastboot mode. I really like to try out this rom on an amoled display. Any specific methods I should follow? (I used mokee phh treble vendor as that was recommended in most forums, am also decrypted..maybe i have to try by flashing noverity too) all gsi tutorials and pages for oneplus 5t are about a year old so i'm not sure I can follow that and succeed. Any help would be appreciated. Thanks.
I cant install in redmi 6a
Galaxy A3 2017? (a3y17lte)
I have discovered a thread of the project treble port, how to fix stuck on boot screen?
Dont worry guys if u got confused with the flashing steps of encryption and decryption
[Flashing process from miui or any Custom rom] :-
Install Ptwrp
Format data By typing "YES"
Flash latest Chinese wkly fw
Flash ROM
Flash GAPPS (Optional)
Flash Fcrypt (Optional) [This will make u decrypted]
Reboot
Enjoy
In Custom ROMS Encryption To Encryption :
If you are encrypted and want to switch roms:
1. Remove lock screen password
2. Back up your apps and stuffs
3. Boot to recovery
4. Wipe only Data in advance wipe
5. Flash new ROM and stuffs (Make sure it is properly wrappedkey supported) else can get error or worst.
5. Reboot
6 Done. Profit :good:
Encryption to Decryption :
If u are encrypted and want to get decrypted :
1. First format data (by typing yes)
2. Flash latest Chinese wkly fw
3. Flash rom then gapps then fcrypt zip and
4. Done.. (Magisk is optional after 1st boot).
5. Profit :good:
[ Decryption to Decryption ]
If decrypted and want to stay decrypted
1. Go adv. wipe :- wipe [data, system, vendor , dalvik, caches]
2. Flash ROM
3. Flash GAPPS (Optional)
4. Flash Fcrypt
5. Reboot
6. Enjoy
Note : Make sure you you flash latest Chinese wkly fw.?
Well if you found it useful then Hit the thanks button (it's FREE of Cost)
WELL, IF U LIKE MY WORK Then HIT the Thanks Button . KThanks.
Thanks a lot buddy really needed this. U helped me a lot . Kudos 2 ur hardwork #lifesaver
Hey..what are the steps to move from custom rom (decrypted) to MIUI (decrypted) ?
Thanks ?
sujju said:
Hey..what are the steps to move from custom rom (decrypted) to MIUI (decrypted) ?
Click to expand...
Click to collapse
Who wants to go to miui hahahaha..
anyways
1. Format data
2. Flash Miui recovery zip
3. Flash “no-verity-force-encrypt.zip” file.
4. Reboot
5. ENJOY :good:
RupeshRN said:
Thanks
Click to expand...
Click to collapse
:angel::angel:
sourav24071999 said:
Who wants to go to miui hahahaha..
anyways
1. Format data
2. Flash Miui recovery zip
3. Flash “no-verity-force-encrypt.zip” file.
4. Reboot
5. ENJOY :good:
Click to expand...
Click to collapse
Thanks..
Just to be sure, formatting data would erase internal storage. You mean then I would sideload the zips through TWRP?
sujju said:
Thanks..
Just to be sure, formatting data would erase internal storage. You mean then I would sideload the zips through TWRP?
Click to expand...
Click to collapse
Yes formattinfg data will erase ur storage . NO sideload
sourav24071999 said:
Dont worry guys if u got confused with the flashing steps of encryption and decryption
[Flashing process from miui or any Custom rom] :-
Install Ptwrp
Format data By typing "YES"
Flash latest Chinese wkly fw
Flash ROM
Flash GAPPS (Optional)
Flash Fcrypt (Optional) [This will make u decrypted]
Reboot
Enjoy
In Custom ROMS Encryption To Encryption :
If you are encrypted and want to switch roms:
1. Remove lock screen password
2. Back up your apps and stuffs
3. Boot to recovery
4. Wipe only Data in advance wipe
5. Flash new ROM and stuffs (Make sure it is properly wrappedkey supported) else can get error or worst.
5. Reboot
6 Done. Profit :good:
Encryption to Decryption :
If u are encrypted and want to get decrypted :
1. First format data (by typing yes)
2. Flash latest Chinese wkly fw
3. Flash rom then gapps then fcrypt zip and
4. Done.. (Magisk is optional after 1st boot).
5. Profit :good:
[ Decryption to Decryption ]
If decrypted and want to stay decrypted
1. Go adv. wipe :- wipe [data, system, vendor , dalvik, caches]
2. Flash ROM
3. Flash GAPPS (Optional)
4. Flash Fcrypt
5. Reboot
6. Enjoy
Note : Make sure you you flash latest Chinese wkly fw.?
Click to expand...
Click to collapse
Damn the community really needed this. Good job man.
Could you also add steps to move from MIUI to Custom? (Both encrypted) and vice versa.
im on the previous weekly build of xiaomi.eu rom and i haven't flashed fcrypt disabler, Now how should i update my rom to the latest weekly build? can i use the built-in updater app or should i follow some other procedure? also is it fine to stay encrypted?
Naveenthemi said:
Damn the community really needed this. Good job man.
Could you also add steps to move from MIUI to Custom? (Both encrypted) and vice versa.
Click to expand...
Click to collapse
?? Welcome
Sachin ET said:
im on the previous weekly build of xiaomi.eu rom and i haven't flashed fcrypt disabler, Now how should i update my rom to the latest weekly build? can i use the built-in updater app or should i follow some other procedure? also is it fine to stay encrypted?
Click to expand...
Click to collapse
Use in build ota updater
Hi, can somebody link the fcrypt zip?
Hello,
I was on MIUI , then flashed PE 10,
switched back to MIUI.
Sensors aren't working now !
I tried with MIUI Fastboot rom as well as ZIP file.
still no luck
suggestions please !
How to go back to miui 11 from pe 10 rom
I was in miui 11 encrypted , then i came to pe 10 encrypted , now how can i go back to miui 11 without losing sensor?
rasik107 said:
Hello,
I was on MIUI , then flashed PE 10,
switched back to MIUI.
Sensors aren't working now !
I tried with MIUI Fastboot rom as well as ZIP file.
still no luck
suggestions please !
Click to expand...
Click to collapse
Ofc it wont be wrking.. y dont u guys read changelogs or imp notes if u flash pe then roll back to miui rip to sensors and L1 . For fix check violet official grp. or pe for violet grp.
John878 said:
I was in miui 11 encrypted , then i came to pe 10 encrypted , now how can i go back to miui 11 without losing sensor?
Click to expand...
Click to collapse
Stick to Andriod 10 roms.
sourav24071999 said:
Stick to Andriod 10 roms.
Click to expand...
Click to collapse
That means once you came to PE, than no way to go back to MIUI?
drjmvgami said:
That means once you came to PE, than no way to go back to MIUI?
Click to expand...
Click to collapse
No.. untill memeui fix this
Is it gona encrypt havoc os because it already decrypted?
So, since there is not alot of development going on for our device, i thought we could maybe work together to get something done four our Mi Note 10.
Android Q (10) Guide
1) Flash Miui 12 beta
2) Flash Latest OrangeFox Recovery
3) Format Data
4) Wipe dalvik and cache
5) Reboot to Recovery
6) Flash an GSI of your choice (Arm64-AB)
7)Resize the system partition
8) Optional: Flash Opengapps
9) Optional: Flash Magisk
Restart system
Enjoy
(Big thanks to deathhall)
For me Havoc Q works really well, also face unlock works with Havoc
Havoc specific bugs: SMS doesnt work with 4G, Gcam works only with the main lens and frontfacing lens
Havoc 3.6
Android Pie (9) Guide
How to flash these on the Mi Note 10?
1) Flash Orange Fox TWRP
2) Factory reset in TWRP / format Data!
4) Fastboot: fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5) Download the ARM64-AB version of your desired rom
6) Flash AB system.img of your GSI in TWRP
7) Flash magisk
8) reboot
That worked for me with both GSIs
Lineage OS 16.0
HAVOC OS 2.9
Whats not working?
- Fingerprint (Needs custom overlay)
- Automatic Brightness (Needs custom overlay)
- Camera works fine, but Video seems a little bit weird
- NFC, but this can be fixed with a magisk module
NFC FIX
Kind of a fix for automatic brightness
Video fix
If you have weird notification sounds delete the SoundFX folder from /Vendor/lib and /Vendor/lib64
Framework-res.apk (Provided by ChriZer)
Great work my friend, hopefully these will be the stepping stones to development and we can get the ball rolling on more in the future!
Sent from my MI CC9 Pro using Tapatalk
- flash an Xiaomi OTA update like 1.0.1.0 (around 2,5gb)
Link please.
ztocker said:
- flash an Xiaomi OTA update like 1.0.1.0 (around 2,5gb)
Link please.
Click to expand...
Click to collapse
Try with 11.0.12
Couldnt get either to actually boot, couldn't get any OTA's to actually flash with OrangeFox.
I flashed:
miui_TUCANAEEAGlobal_V11.0.11.0.PFDEUXM_9fa3ae20ce_9.0
then tried to flash:
miui-blockota-tucana_eea_global-V11.0.11.0.PFDEUXM-V11.0.12.0.PFDEUXM-ecf4ee46b2-9.0
and just get an error.
I tried following your steps written in the OP, but the BlockOTA fails to flash. Or if I just use a fresh install and Format data, and try to install the GSI's it rewrites the system to system_root and magisk won't install and it just bootloops.
deathhall said:
Couldnt get either to actually boot, couldn't get any OTA's to actually flash with OrangeFox.
I flashed:
miui_TUCANAEEAGlobal_V11.0.11.0.PFDEUXM_9fa3ae20ce_9.0
then tried to flash:
miui-blockota-tucana_eea_global-V11.0.11.0.PFDEUXM-V11.0.12.0.PFDEUXM-ecf4ee46b2-9.0
and just get an error.
I tried following your steps written in the OP, but the BlockOTA fails to flash. Or if I just use a fresh install and Format data, and try to install the GSI's it rewrites the system to system_root and magisk won't install and it just bootloops.
Click to expand...
Click to collapse
Maybe try 11.0.1. since its alot bigger than 12 and 11
Android 11 GSi is out can you give it a shot?
Status?
Is anybody using the LOS GSI as a daily driver?
If there is just the small amount of bugs like in the description, it might be fine for now. At least for me.
Or are there other small bugs 'not worth mentioning' ?
In another parallel thread 'Will there be a custom ROM?', two heros decided to work on our phone... I wish them the best!
Hi all, I have spent a good few weeks testing almost all Android 10 (Q) GSIs for tucana (our device). My findings are relatively positive and are as follows:
I got Pixel Experience as well as EvolutionX from @expressLukeGSI to boot and both seem to work with minimal bugs... The main bug I found was an audio bug commoly associated with GSIs; the audio sounds as if the device is underwater. A simple fix to this bug was flashing audiofix for GSIs.
I also got OxygenOS to boot from @erfanGSI as well as others but these had major bugs (e.g. device reboots automatically, immediately after connecting to WIFI).
Other Android Q GSIs that booted include LineageOS, CAOS, AOSP, Descendant as well as Havoc (from GSI page - Android Q Section - on Github). With regards to LineageOS, once rooted with magisk it will NOT boot.
Under Display Fingerprint does NOT work on any GSIs currently and Face Unlock only works on specific GSIs.
If you'd like more info on the GSIs I have tested or would like me to test further please don't hesitate to contact me via private message, I'll be glad to help wherever possible.
LDP12 said:
Hi all, I have spent a good few weeks testing almost all Android 10 (Q) GSIs for tucana (our device). My findings are relatively positive and are as follows:
I got Pixel Experience as well as EvolutionX from @expressLukeGSI to boot and both seem to work with minimal bugs... The main bug I found was an audio bug commoly associated with GSIs; the audio sounds as if the device is underwater. A simple fix to this bug was flashing audiofix for GSIs.
I also got OxygenOS to boot from @erfanGSI as well as others but these had major bugs (e.g. device reboots automatically, immediately after connecting to WIFI).
Other Android Q GSIs that booted include CAOS, AOSP, Descendant as well as Havoc (from GSI page - Android Q Section - on Github).
If you'd like more info on the GSIs I have tested or would like me to test further please don't hesitate to contact me via private message, I'll be glad to help wherever possible.
Click to expand...
Click to collapse
No fingerprint right?
Fingerprint on GSIs
iSonik said:
No fingerprint right?
Click to expand...
Click to collapse
Unfortunately no fingerprint on any GSIs currently
LDP12 said:
Unfortunately no fingerprint on any GSIs currently
Click to expand...
Click to collapse
Thats not a minor bug imo
iSonik said:
Thats not a minor bug imo
Click to expand...
Click to collapse
Completely opinion based; I can live without it.
I have edited my original post to include this.
LDP12 said:
Completely opinion based; I can live without it.
I have edited my original post to include this.
Click to expand...
Click to collapse
Yeah thats why i said "imo". But that also means no autobrightness
iSonik said:
Yeah thats why i said "imo". But that also means no autobrightness
Click to expand...
Click to collapse
Sorry, I never saw the "imo" part of your reply.
That is correct, once again this is minor for me but maybe not for some. Although I can confirm that battery drain is significantly decreased when using GSIs. Even without the auto brightness battery life is much better.
I am currently using/testing the Evolution X GSI from ExpressLukeGSI.
LDP12 said:
Sorry, I never saw the "imo" part of your reply.
That is correct, once again this is minor for me but maybe not for some. Although I can confirm that battery drain is significantly decreased when using GSIs. Even without the auto brightness battery life is much better.
I am currently using/testing the Evolution X GSI from ExpressLukeGSI.
Click to expand...
Click to collapse
Yeah batterylife on GSIs is insane, maybe ill try one again. But the missing fingerprint and faceunlock bother me quite alot
BTW are you using Q GSIs?
iSonik said:
Yeah batterylife on GSIs is insane, maybe ill try one again. But the missing fingerprint and faceunlock bother me quite alot
BTW are you using Q GSIs?
Click to expand...
Click to collapse
Yes, I am using Q GSIs
Interesting, i cant get GSIs to boot, did you do something different?
Are you wiping Dalvik, System, Data and Cache, and then flashing the preferred GSI?
If the above method is not working, search "Download the MIUI 12 Closed Beta for Xiaomi and Redmi devices XDA" on google, download MIUI 12 beta for tucana/Mi Note 10 (our device) and flash it in TWRP. Then perform a wipe as usual and flash preferred GSI.
iSonik said:
Interesting, i cant get GSIs to boot, did you do something different?
Click to expand...
Click to collapse
I was on MIUI 20.6.11 -MiRoom when I flashed the Bliss GSI, my exact steps where:
Flash Latest OrangeFox Recovery
Formata Data
Format dalvik and cache
Reboot to Recovery
Flash GSI -Arm64-AB or BvN depending on the owner
Go to Data in the manage partition menu and resize partition
Flash Opengapps, I used 10.0 Pico
Restart system
Admittedly, I flashed the GSI but not the gapps first, just to see if it would boot, which it did. then I formatted only cache and dalvik, then resized and flashed Gapps. and it booted and took me right into the setup from the notification that came up when it booted.
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Wiki.
Recovery
The LineageOS 17.1 reovery is recommended
If you still want to use TWRP never install the TWRP app as system app. Otherwise your device won't boot
Current lineage 17.1 shamu nightlies are based on the N6F27M October 2017 update from google.
So you should be using the radio and bootloader img from that update.
Before you flash a bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one and don't need to flash it again.
They can be extracted from the factory image on google's site here.
Or you can use the ones linked below that I already extracted:
radio-shamu-d4.01-9625-05.45+fsg-9625-02.117.img
bootloader-shamu-moto-apq8084-72.04.img
IMPORTANT NOTE FOR VERIZON USERS: Google released a separate October 2017 security update (NGI77B) just for verizon users that has a different radio. So you'll want to flash it. I repeat, THIS RADIO IS JUST FOR VERIZON USERS.
radio-shamu-d4.01-9625-05.51+fsg-9625-02.118.img
You can use fastboot to flash the bootloader and radio.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/shamu
Google apps: Opengapps Use an ARM (not ARM64) package for Android 10
HEADS UP: When you initially install LineageOS, be sure you flash the gapps package with your ROM. If you boot your ROM, then go back and try to flash gapps after, you're gonna have a bad time.
Changelog
Builddate: 2020.06.17
Changes:
[new] June security updates
[new] LineageOS clock
Builddate: 2020.05.29
Changes:
[new] May security updates
[fix] ULL audio fixes
[new] Add back serif fonts
[fix] Screen turning itself on when no lockscreen is set
[new] Etar calendar
Builddate: 2020.04.12
Changes:
[new] April security updates ROM & kernel
Builddate: 2020.04.08
Changes:
[new] Initial LineagOS 17.1 release
Known Issues:
[bug] Trusted voice is not working and probably never will
[bug] TWRP is not able do decrypt your data if you encrypted it with lineage-16.0
[bug] IMS is not working - if you need it you have to stay on lineage-15.1
XDA:DevDB Information
LineageOS, ROM for the Nexus 6
Contributors
Elektroschmock, elektroschmock, npjohnson
Source Code: http://github.com/lineagos
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Version Information
Status: Nightly
Created 2020-04-08
Last Updated 2020-04-08
Reserved
First build isn't out yet, but I don't want the LineageOS 16.0 thread to be spammed with 17.1 questions
Will waiting for the build you might want to read the Changlog for the first LineageOS 17.1 release:
Changelog 24
Will there be a possibility to root?
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Thanks @Elektroschmock and @npjohnson for keeping the Nexus 6 alive in 2020. :good:
Eazy said:
Will there be a possibility to root?
Click to expand...
Click to collapse
Yes you can use your root solution of choice.
Only thing coming with the ROM is adb root.
dlbarron said:
Should we wait for 17.1 to flash the radio and bootloader or can we do it now to get it out of the way?
What are the commands for flashing those two images?
Click to expand...
Click to collapse
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Elektroschmock said:
Actually you should already have those radio and bootloader images if you had the latest stock image installed at one point.
Commands are:
fastboot flash bootlader [name_of_the_bootloader_image]
and
fastboot flash radio [name_of_the_radio_image]
Click to expand...
Click to collapse
Actually, I've been running Lineage and CM before that since I brought the phone home. So there's no way I had the latest stock image installed ever.
Thanks, I'm all set
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
BootloopedMillennials said:
Welp I did a stupid.
Flashed the new 17.1 recovery via fastboot. Then I tried to sideload via adb (based on the instructions) but Linux machine kept complaining about needs adb root. Tried with root permission nothing, Then came the stupid. Rebooted into recovery and tried to apply the update. Well that went how I expected, badly. Stuck on LOS loading screen.
Needed a fresh install anyway.
Stick to the instructions, guys.
Click to expand...
Click to collapse
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
xrenoix said:
Hello you can flash twrp with your pc after boot in twrp flash 17.1 + gapps micro + magisk 20.4 + wipe data + wipe dalvik + wipe cache reboot and it work perfectly ! Ps no intall twrp app in twrp recovery before reboot or you have bootloop Cordialy
BIG THANKS @Elektroschmock very Nice work
Click to expand...
Click to collapse
My system got corrupted by the previous process. So I had to do a fresh install.
BootloopedMillennials said:
My system got corrupted by the previous process. So I had to do a fresh install.
Click to expand...
Click to collapse
Hello you have test wipe system with twrp ? Or test repair ? And use pico gapps for trébuchet launcher not work with mirco gapps but pixel launcher work ? !
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Best would be to use built in update. Unless you want to do a clean install, there's no reason to do it.
the update inside of lineage is blocking updating to lineage 17.1 , i tried tha earlier and i jsut tried it again. then it gives the link to the wiki page.so thats not going to work.i will have to do the old method of flashing through twrp or hoping that there is a command line approach to flashing lineage through lineage recovery.
mrk2815 said:
whats the exact steps to do in twrp.as i stated in los 16 thread i am blind and require twrp open script command line to flash my lineage builds in the past as i have to also enable accessibility services and talkback and google text to speech . so can that also be done with lineage recovery or am i just stuck with twrp and then install lineage 17.1 and open gapps . What's the best advice in my situation .
Click to expand...
Click to collapse
Sorry, I didn't ignore your question, but I first had to check.
It's kind of hard to imagine how a blind person would do it if you can see.
If you have Lineage recovery installed and are able to boot into recovery do the following steps:
Press the Volume Down button 1 time
Press the power button two times
You are now in the adb apply update mode.
There you can install all the zip files you want. I guess you script does the rebooting to system itself.
If you need further help just ask.
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
s_dino said:
@Elektroschmock
Thanks for your hard work!
I have two questions, if lineage recovery wipe the internal storage every time when I wipe the data or system? and when I flash the boot animation it seems not work. May you give some suggestion? Thank you!
Click to expand...
Click to collapse
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Elektroschmock said:
The recovery doesn't do anything on it's own. If you want to wipe any partition you need to select the corrosponding entry in the recovery.
I don't know about which bootanimation you are talking about. Do you mean the bootloader?
Before you flash bootloader or radio image please boot to bootloader and check what you have currently installed. You might already have the right one.
Click to expand...
Click to collapse
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
s_dino said:
In TWRP I can select only wipe data/cache/system, the internal storage can be retained. The lineage recovery haven't the "wipe internal storage" option, so how can I wipe the data/system and keep the internal storage at the same time? Do I need to update the recovery version when I update the system daily build?
I mean I want use the google original boot animation to replace the lineage boot animation, but not success.
Click to expand...
Click to collapse
You still have those options:
Go to "Factory Reset"
There you can choose which partition you want to wipe.
- Wipe data/factory reset
- Wipe cache
- Wipe system
I guess you want the "wipe system" option
Sorry we don't support modifying our builds for obvius reasons. If you want to do that you are on your own. Sorry.
runekock said:
I noticed this: "disable audio rotation tracking"
https://review.lineageos.org/c/LineageOS/android_device_moto_shamu/+/272403
Is that the end of stereo sound in landscape? (Of course if that is necessary to fix the loss of sound in calls, it is totally worth it, just curious).
Click to expand...
Click to collapse
It's just a test. Non of us was able to trigger the loss of audio. Youl'll still have stereo but it won't switch channels if you turn your device.