Related
Latest TWRP changelog :
New features of 3.2.3-0:
Changelog)
Download Link - 64 bits version (non-treble)
twrp-3.2.3-0-64bits.img
Download Link - Treble version (64bits too)
twrp-3.2.3-0-treble.img
Working/Bugs
I have just tested on 16 GB variant and all seems to be working. If something is broken lemme know.
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to wipe data once via twrp wipe options and reboot back to twrp for functioning of /data
Installation Guide
Make sure you have unlocked bootloader
Reboot to bootloader
fastboot flash recovery twrp-****.img (if you want permanent flash) or fastboot boot twrp-****.img (if you want temporary
boot)
XDA:DevDB Information
[Unofficial] TWRP 3.2.3-0 Moto G5, Tool/Utility for the Moto G5
Contributors
ZJRDroid
Source Code: Local manifests
Version Information
Status: Stable
Stable Release Date: 2019-01-18
Created 2019-01-18
Last Updated 2019-01-18
Thanks for the updated TWRP! Works like a charm
Are there any circumstances which would make it necessary to use the non-treble version?
image not signed or corrupted moto g 5 cedric. is this for cedric?
edit2: my friend used the fastboot boot recovery option the recovery booted and asked a password, then he pressed back and the other screen with the swipe button has appeares (allow system modifications) and now what to do? the sdcard folder doesn't have nothing inside, neither the external sd
update3: after requering the password he pressed back and then formatted the phone, phone booted into the stock rom, and the twrp is gone.
update4: tried install viperos cedric android 9.0.0 gave error 7 I don't know what to do twrp is working, he tried this https://www.youtube.com/watch?v=VCqROwIGLLE and now stock rom is gone. we are loosing hope ;-;
update 5: tried using the twrp provided by this guy https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737/page11 but nothing. still error 7 even doing the procedure above ^^
update 6: Forget everything you read, upthere^^^^ he downloaded the rom for a different phone XD
so anone tested any treble roms from the project forum on our phones with this twrp?
luigge said:
edit2: my friend used the fastboot boot recovery option the recovery booted and asked a password, then he pressed back and the other screen with the swipe button has appeares (allow system modifications) and now what to do? the sdcard folder doesn't have nothing inside, neither the external sd
Click to expand...
Click to collapse
What did he do exactly to avoid the password screen?
so...does this fix some of the issues present in the previous treble recovery? such as the camera not working? flashlight not working? crashes? can i use it as a daily driver?
I tried this ones. Camera working and no crashes, really stable.
[PORTED][semi-GSI][PPR2.181005.003][UNOFFICIAL]P sGSI PR2[A-ONLY]
......
[8.1][sGSI]MIUI10 for Project Treble
......
[9.0] [UNOFFICIAL] [ARM64 A-ONLY] AOSiP Pizza Alpha [EXPERIMENTAL] (Camera crashes but open camera works with videos)
.......
[GSI] OmniROM 8.1 [Unofficial] [ARM64]-[A-Only] [21.10.18]
Those i tested for like 1 hour and in this time everything works good. Iam staying with Omni cuz it feels uber fast and stable.
alright so here's a question: the lineage treble build to flash before the img is down, so where can i find a treble-ised rom to flash before the actual image?
fenerbuuh said:
I tried this ones. Camera working and no crashes, really stable.
[PORTED][semi-GSI][PPR2.181005.003][UNOFFICIAL]P sGSI PR2[A-ONLY]
......
[8.1][sGSI]MIUI10 for Project Treble
......
[9.0] [UNOFFICIAL] [ARM64 A-ONLY] AOSiP Pizza Alpha [EXPERIMENTAL] (Camera crashes but open camera works with videos)
.......
[GSI] OmniROM 8.1 [Unofficial] [ARM64]-[A-Only] [21.10.18]
Those i tested for like 1 hour and in this time everything works good. Iam staying with Omni cuz it feels uber fast and stable.
Click to expand...
Click to collapse
how'd you get the MIUI10 sGSI working on your phone? mine keeps rebooting into twrp
Links for both versions are down. Can you re-upload, please?
actuallynxthing said:
Links for both versions are down. Can you re-upload, please?
Click to expand...
Click to collapse
here
Both of these are not working for me.
All I get is the normal, stock recovery screen.
But yeah, do note that I had installed the 3.3 official which worked for just one boot. After that, I'm getting the stock recovery screen too.
---------- Post added at 04:58 AM ---------- Previous post was at 04:14 AM ----------
eljoantonyn said:
Both of these are not working for me.
All I get is the normal, stock recovery screen.
But yeah, do note that I had installed the 3.3 official which worked for just one boot. After that, I'm getting the stock recovery screen too.
Click to expand...
Click to collapse
Spoke too soon !
Got it working.
Now I need to see why it says "wrong password" while trying to decrypt.
Link fallen
Would you people kindly stop deleting your files from android file host, sick of broken links
Cloudane said:
Would you people kindly stop deleting your files from android file host, sick of broken links
Click to expand...
Click to collapse
I would use the 64bit twrp in the link below
It's not treble but then there's no stable treble roms for this device anyway (which is probably why this twrp is not maintained)
The following 64bit twrp will work with all 64bit custom roms
https://drive.google.com/open?id=1MLlljM7BzMj9Da57LeyBHyg81cHdW1cB
Treble version works good in XT 1670 (2GB 32GB). Some laggy gui, but good. Ty for your hard work!
He.Art said:
Treble version works good in XT 1670 (2GB 32GB). Some laggy gui, but good. Ty for your hard work!
Click to expand...
Click to collapse
If you want an never version use Jarl's TWRP - it works perfectly fine except if you encrypt backups (not the same as backing up encrypted data)
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.
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.
I have been developing Ubuntu Touch for the Tab A 10.1 2019
This ROM has been tested on both SM-T510 (WiFi version) and SM-T515 (WiFi + LTE)
Any developers reading this and has the device with them and are interested in the project may contact me :
@midhunvnadh on Telegram
Not Working :-
Bluetooth
Audio
Anbox (Android Emulator)
MTP
I am trying to fix these.
Download Files
Download the Halium arm32 GSI file : from Here
(Optional) Download SamsungUSBTethering zip : from here
Ubports Patched Kernel : from here
Get all the above files copied to your External SD Card
Installation
WARNING : I am NOT responsible for any damage caused to your device
If you are following this post, please takeup full responsibility of your device.
Noobs at flashing ROM's can click here: https://telegra.ph/Installing-Ubuntu-Touch-T510T515-08-22
Thanks to @ahamshubham for making this
1.0 Flash STOCK Android 9.0 Pie on your device and install TWRP.
(Because not tested on STOCK Android 10.0)
1.5 Boot into TWRP and Wipe all except external SD. REBOOT to recovery.
2.0 On TWRP : Flash the Lineage 16.0 build. DON'T REBOOT.
3.0 On TWRP : Goto Install -> Install Image -> (Flash halium-boot.img) DON'T REBOOT.
4.0 On TWRP : Goto Install -> (Flash ubports_GSI_installer_V1-arm32.zip).
5.0 (Optional) : Goto Install -> (Flash samsung-usb-tethering.zip)
5.1 Reboot.
(Incase : unable to boot ? , boot into TWRP -> reboot -> system)
samsung-usb-tethering.zip is used to get an SSH console from device to PC. Credits to @erfanoabdi
Please report all the errors you encounter here.
Sources
Kernel : https://github.com/midhunvnadh/android_kernel_samsung_gta3xlwifi
Device Tree : https://github.com/midhunvnadh/device_samsung_gta3xlwifi
GSI arm32 : https://github.com/midhunvnadh/android_device_halium_ubport
The Device tree is a dummy tree with kernel sources linked. Which serves a purpose of compiling halium-boot.img. For more info contact me.
Donations are always appreciated : Just click here
Reserved
Reserved
Pick me! Pick me!
I will gladly take that on. Just got down installing lineage ,17.1 with Kali Linux.. I will see what I can't get done tonight.
mikehunt723 said:
I will gladly take that on. Just got down installing lineage ,17.1 with Kali Linux.. I will see what I can't get done tonight.
Click to expand...
Click to collapse
Hello, you gave me a first reply... !!!
This is my real thread post on ROM's.
I didn't understand what you meant by "Pick me" and "I will gladly take that on. "
Are you looking forward to make contribution to this project ?
Bruh this is amazing work, keep it going!
This looks like an interesting project, none of the download links work for me
nubianprince said:
This looks like an interesting project, none of the download links work for me
Click to expand...
Click to collapse
It is a direct link. It works for me ?
Can you support Galaxy Tab A6?
Mohamed677 said:
Can you support Galaxy Tab A6?
Click to expand...
Click to collapse
I can try if you can give me a device.
Mohamed677 said:
Can you support Galaxy Tab A6?
Click to expand...
Click to collapse
The sm-t580? I tryed like a month ago, and i got the boot.img file to compile for halium7, but not the system image, and los14 is broken so it cant work anyway, and, when i tryed to compile using halium9, i had missing libs.
I also tryed postmarketOS, and it did not boot
(Well, if it did, and i think it did because it didnt reboot into download mode automatically), and screen and usb wasnt working
MIDHUN.V.NADH said:
1.0 Flash STOCK Android 9.0 Pie on your device and install TWRP.
Click to expand...
Click to collapse
Wow. This is exciting news. Really have been longing for a non-android based OS for a long time. Thanks a ton. Will surely donate when I get a job(currently unemployed due to covid):good:
What do you mean by installing stock? You are going to installing LOS 16.0 so can that not be the starting point? Do I have to go back and install stock using Odin and do the whole process again?
aveemashfaq said:
Wow. This is exciting news. Really have been longing for a non-android based OS for a long time. Thanks a ton. Will surely donate when I get a job(currently unemployed due to covid):good:
What do you mean by installing stock? You are going to installing LOS 16.0 so can that not be the starting point? Do I have to go back and install stock using Odin and do the whole process again?
Click to expand...
Click to collapse
Yes, you have to do all those steps.
Why I am asking everyone to install Stock 9.0 is because :
1. On Samsung Exynos Devices developers have an hard time developing Ubuntu Touch.
2. There are changes in partition structure going on from upgrade to Stock 9.0 to 10.0
3. The kernel source of stock Android 9.0 is VERY different from 10.0
4. I wasn't able to get logs from Stock 10.0 due to the partition changes mentioned on (2)
5. Halium 9.0 (Build Engine for Touch) highly recommends Android 9.0/Lineage 16.0 as a base to install upon.
6. Moreover I haven't tested if it boots on stock 10.0 because of (2), (3), (5) and I am currently fixing the bugs.
Please try to out on AOSP 10.0 and let me know if it work
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Geek_Ceará said:
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Click to expand...
Click to collapse
Hi !, Were you able to boot into the OS ?
I haven't faced that issue can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32.
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Geek_Ceará said:
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Click to expand...
Click to collapse
Hi ! Thank you for your reply.
Were you able to boot into the OS ?
I haven't faced that issue. Can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32 eventhough some devices with the same SoC has full arm64.
I am trying to port arm64 vendor into the device but I think arm32 will be better because the device only has 2GB RAM (Atleast on my device)
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Worked!!
I was looking forward to run Ubuntu Touch on my Samsung Galaxy Tab A (SM-T515NZKDINU). I contacted MIDHUN.V.NADH, he helped me through the process and we got Ubuntu Touch running on my device. I would like to thank him for his help and his post. I, however, felt that I could not follow the instructions in the post very easily. Maybe, this is because I am doing something like this for the first time. So, I compiled a list of instructions to follow. I will send him this list of instructions and post them here too. I feel they will be helpful for people looking to run Ubuntu Touch on the same device.
MIDHUN.V.NADH said:
Hi !, Were you able to boot into the OS ?
I haven't faced that issue can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32.
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Click to expand...
Click to collapse
Yes. I managed to initialize, however, this problem happens to me. I uninstalled Ubuntu and returned to android. Someday, when I have something stable, I test it again.
And about the processor architecture, I understand your explanation. Thank you!
Just adding instructions on how I did it on my device
My device details:
Device Model Number: SM-T515 (NZKDINU)
Linux Kernel Version: 4.4.111-17420370
Instructions for SM-T515:
1) Download these files using the links given in the post I am commenting on:
a) Halium arm32 GSI file
b) Ubports Patched Kernel
c) (Optional) SamsungUSBTethering zip
2) Copy all the above files to your External SD Card and insert this SD card in the device (tablet)
3) Flash STOCK Android 9.0 Pie on your device (tablet) and install TWRP:
a) For installing TWRP, use the following post: https://forum.xda-developers.com/ga...very-twrp-3-3-1-2019-galaxy-tab-10-1-t3934805. The instructions for installing TWRP as given in this post are:
i) Unlock bootloader (See the end of my comment)
ii) Hold Vol Up & Vol Down buttons during restart to enter Download mode
iii) Install TWRP to AP with Odin
iv) Hold Power & Vol Up buttons during restart to enter TWRP recovery
v) On TWRP: Swipe to allow modifications
vi) On TWRP: Wipe -> Advanced Wipe -> Select all except SD card
vii) On TWRP: Reboot -> Recovery
4) On TWRP: Go to Install -> Install Image -> (Flash halium-boot.img. Partition to flash image is BOOT). DON'T REBOOT. PRESS BACK.
5) On TWRP: Go to Install -> (Flash ubports_GSI_installer_V1-arm32.zip. Don't check any check boxes)
6) (Optional) On TWRP: Goto Install -> (Flash samsung-usb-tethering.zip)
7) Reboot
8) Ubuntu Touch will open. The password is: phablet
Unlocking Bootloader (Check this post: https://www.getdroidtips.com/oem-unlocking/):
1) Enable Developer Mode in Device Settings
2) Enable OEM Unlocking Option in Developer options after connecting to WiFi and setting the year in the phone to the year 2019
3) Get into Device Unlock Mode: Press (Volume Up Key + Volume Down Key + Insert USB Cable in the phone) while restarting the phone
4) Unlock bootloader. (Very Important!!) DON'T LET THE DEVICE BOOT INTO THE ANDROID OS AFTER UNLOCKING DEVICE BOOTLOADER
MIDHUN.V.NADH said:
Yes, you have to do all those steps.
Why I am asking everyone to install Stock 9.0 is because :
1. On Samsung Exynos Devices developers have an hard time developing Ubuntu Touch.
2. There are changes in partition structure going on from upgrade to Stock 9.0 to 10.0
3. The kernel source of stock Android 9.0 is VERY different from 10.0
4. I wasn't able to get logs from Stock 10.0 due to the partition changes mentioned on (2)
5. Halium 9.0 (Build Engine for Touch) highly recommends Android 9.0/Lineage 16.0 as a base to install upon.
6. Moreover I haven't tested if it boots on stock 10.0 because of (2), (3), (5) and I am currently fixing the bugs.
Please try to out on AOSP 10.0 and let me know if it work
Click to expand...
Click to collapse
Hi, I just tried it out on my device. I had stock 9.0 over which I had flashed Lineage OS 17.1(based on Android 10). Over that, I flashed LOS 16, halium-boot, ubports-gsi and usb tethering. Worked for me.
I have to say, I have a pinephone and it seems that ubports on Samsung tab is faster than on pinephone.
antoine62 said:
The sm-t580? I tryed like a month ago, and i got the boot.img file to compile for halium7, but not the system image, and los15 is broken so it cant work anyway, and, when i tryed to compile using halium9, i had missing libs.
I also tryed postmarketOS, and it did not boot
(Well, if it did, and i think it did because it didnt reboot into download mode automatically), and screen and usb wasnt working
Click to expand...
Click to collapse
Did you ever get this to work/ any tips for trying because I really want this to work (I am trying at the moment).