[ROM][10.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510] - Samsung Galaxy Tab A series ROMs, Kernels, Recover

[ROM][10.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510] - Samsung Galaxy Tab A series ROMs, Kernels, Recover

{
"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 10.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 this one is based on the October 2020 Update (T510XXU4BUA1) for the SM-T510.
The new release is based on @eremitein's CAOS 10.0 GSI (CQ), which is an extremely lightweight set of tweaks to AOSP.
Previous releases were based on @AndyYan's LineageOS 17.1 GSI (LQ) or @phhusson's AOSP 10.0 (AQ).
Includes common set of Google apps from 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 and Messenger are 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
Downloads:
Nexus_Stock_CQ_T510XXU4BUA1-20210508.tar.md5 (Odin tarball)
Nexus_Stock_CQ_T510XXU4BUA1-20210508.zip (TWRP update)
Build archives:
Android File Host
Change Log:
20210508:
Updated to TWRP v3.5.2.
Updated to latest stable 10.0 release of OpenGapps Stock variant (20200508).
20210327:
Google Assistant setup no longer fails in Setup Wizard.
Updated to latest stable 10.0 release of OpenGapps Stock variant (20200327) with fix for Google News.
20210322:
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.)
Based on latest CAOS 10.0 v224 GSI build (20201029) with October 2020 security patch.
Updated to the OEM January 2021 Security Update (T510XXU4BUA1) kernel and vendor partition.
Updated to latest stable 10.0 release of OpenGapps Stock variant (20200311) with fix for Google News.
20201130:
Based on AOSP GSI v222 (20200806) with August 2020 security patch.
20201121:
Based on latest LineageOS 17.1 GSI build (20201114) with November 2020 security patch.
Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU3BTH4).
Updated to latest stable 10.0 release of OpenGapps Stock variant (20201121), which now includes Google Recorder.
20200812:
Based on latest LineageOS 17.1 GSI build (20200808) with August 2020 security patch.
20200807:
Based on AOSP GSI v222 (20200806) with August 2020 security patch.
Includes patches to provide simple theme configuration section in Settings > Display, add Recovery to power menu, and match Pixel appearance.
Updated to the new Android 10 OEM kernel and vendor partition (T510XXU3BTFN).
Updated to latest stable 10.0 release of OpenGapps Stock variant (20200714).
20200713:
Based on the latest build of LineageOS 17.1 GSI (20200713) with July 2020 security patch.
20200712:
Based on AOSP GSI v221 (20200708) with July 2020 security patch and patch to provide simple theme configuration section in Settings > Display.
Updated to the OEM May 2020 Security Update (T510XXS3ATE3) kernel and vendor partition.
Updated to latest stable 10.0 release of OpenGapps Stock variant (20200711).
20200413:
Fixed Double Tap to Wake feature (enabled in Phh Treble Settings).
Fixed crash on first two attempts to launch Phh Treble Settings.
Based on the latest build of LineageOS 17.1 GSI (20200413).
Updated to the OEM T510XXS3ATB4 kernel and vendor partition.
Updated to latest release of OpenGapps (20200409-TEST), with private fix for Chrome issue.
20200314:
Fixed potential image corruption issue from outdated img2simg command.
20200312:
Now based on the latest build of LineageOS 17.1 GSI (20200309).
Uses v703 build of Pixel Launcher with 6x6 and 7x7 icon profiles migrated from the Android One Launcher.
Charging after full shutdown will no longer hang during level-of-charge animation.
MTP file transfers no longer require USB Debugging to be enabled.
20200223:
Initial build based on T510XXU2ASK5 kernel (November 2019 Update) and AOSP 10.0 v212.
Latest Google apps from OpenGApps (20200216-TEST)
Instructions:
From OEM stock firmware:
Unlock bootloader
Ensure matching OEM build (e.g. T510XXU3BTFN) 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 @eremitein and @phhusson for Treble GSIs, so please show them some love here!

Magendanz said:
Well, we're finally getting some relatively stable builds of AOSP GSIs and OpenGApps for Android 10.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 this one is based on the November 2019 Update (T510XXU2ASK5) for the SM-T510.
The system is based on @phhusson's AOSP 10.0 GSI 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.
This is using the Pixel Launcher, but home screen layout is not ideal for this device and I may switch back to the Android One Launcher.
The properties now correctly identify the device as a tablet, and so the Google Dialer and Messenger are 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:
Double-tap to wake
Support for file-based encryption
MTP currently requires USB Debugging to be enabled.
Charging after full shutdown will hang during level-of-charge animation.
Downloads:
SM-T510:
Nexus_Stock_AQ_T510XXU2ASK5-20200223.tar.md5 (Odin tarball)
Nexus_Stock_AQ_T510XXU2ASK5-20200223.zip (TWRP update)
Change Log:
20200223:
Initial build based on T510XXU2ASK5 kernel (November 2019 Update) and AOSP 10.0 v212.
Latest Google apps from OpenGApps (20200216-TEST)
Instructions:
From OEM stock firmware:
Unlock bootloader
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, wipe data if installing for first time. (Not necessary for incremental upgrades.)
Reboot to system
From existing TWRP install: (No need for data wipe.)
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, so please show him some love here!
Click to expand...
Click to collapse
That was quick . I just bought a SM-T510 and will wait a bit before installing this ROM. Thanks for the great work.

Thanks for this new ROM !
Quick questions:
1. does it support exFAT FS on µSD card ?
2. will a dirty flash over the original Nexus work ?

THANK YOU
Code:
@Magendanz
!!
All your roms are solid, especially your MECOOL tvstock roms!
:victory::victory:
Is this (or chance of) a 64bit ROM?

Thanks for the update. It's installed including Magisk and Multidisabler. I am successfully rooted and checking things out. No issues so far. Great work.

Did the upgrade from the previous 9.0 rom (20191109) with the TWRP version.
I'm getting android.process.acore crashes on the home screen flashing up constantly.
So far I've tried wiping the caches but still happening.
edit: did a full wipe and it's gone away. Now to reinstall everything...

leonkernan said:
edit: did a full wipe and it's gone away. Now to reinstall everything...
Click to expand...
Click to collapse
Yeah, I should have mentioned that I don't recommend a dirty flash from Android Pie. Please do a factory wipe.
You should be fine doing incremental updates on Android 10 later, though.

milsabords said:
Does it support exFAT FS on µSD card?
Click to expand...
Click to collapse
Initial testing with exFAT looks promising. I just formatted a 64GB µSD card as exFAT on my PC and was able to play a 2.0 GB video file from it on the SM-T510 with no problems.

Magendanz said:
Initial testing with exFAT looks promising. I just formatted a 64GB µSD card as exFAT on my PC and was able to play a 2.0 GB video file from it on the SM-T510 with no problems.
Click to expand...
Click to collapse
Great news
If it all goes well maybe you can add exFAT to some futute version of your LOS 16 ROM as well?
Currently on your LOS 16 ROM - works perfectly only missing exFAT...

Magendanz said:
Well, we're finally getting some relatively stable builds of AOSP GSIs and OpenGApps for Android 10.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.
.
.
.
Click to expand...
Click to collapse
Thank you so much for this ROM!!!! The tablet feels like a complete new device. No lags, no slowdowns etc., the performance is just incredible compared to the Stock ROM and it's themeable with Swift Installer. I can't thank you enough... well sure I can... drink some beer or coffee with the 10 bucks I donated, you really deserved it. :good:
I'm looking forward to the next releases, I hope you can iron out the things like MTP needs USB debugging etc. and I have one little request for the end: would you mind making a lite version of this ROM with just the Pico GApps package? I guess I'm not the only one that doesn't need/want the whole GSuite.

DeathMD said:
I have one little request for the end: would you mind making a lite version of this ROM with just the Pico GApps package?
Click to expand...
Click to collapse
My Nexus custom ROMs for media players usually include Nano and Stock (and TVStock) variants, but I intentionally released Stock only for this tablet to reduce my build times and storage footprint. Since you don't recover unused space from the system partition, it doesn't really hurt to have the extra Google apps, but I understand that it could take space from the user partition if you allowed them to be updated. With me just starting a new teaching job and working on a master's degree, I just haven't had any extra bandwidth, but I'll reevaluate in the summer.

Works much better than the 9.0 one, thanks.

Storage Permission Issue
I'm a noob at this, so forgive me if i'm missing something simple. I've got the ROM installed and most everything works. I even managed to get Kali Nethunter installed and working, which was my ultimate goal. However, i'm forced to save files only to the actual external SDCARD because I can't write to /SDCARD or /storage/emulated/0. In other words for example, I can't use the camera because it doesn't see a usable storage device. If I open a terminal as root, and cd to /SDCARD, I can't create a directory or file, it says permissions are denied. I tried taking a screenshot of me using Total Commander as superuser attempting to create a folder in /storage/emulated/0 and it says it couldn't save the screenshot "do to limited storage space". There are no folders in either /storage/emulated/0 or /SDCARD (which is a soft link). Any idea what I did wrong, or what I could do to fix it? It looks like the filesystem is read only, but i'm not seeing that from the "mount" command.
Starting from a stock ROM, here's what I did:
I unlocked the device, and I had to login to Google and then do the time trick others had mentioned to see the "OEM Unlocking" option.
I then used Odin to flash TWRP.
After testing TWRP, i then realized there was a ROM that included twrp, so I flashed that using Odin.
Booted to TWRP, and wiped Data, followed by installing multi-disabler and Magisk.
Then booted into the ROM.
Thanks for any help on this.

commradd said:
I'm a noob at this, so forgive me if i'm missing something simple. I've got the ROM installed and most everything works. I even managed to get Kali Nethunter installed and working, which was my ultimate goal. However, i'm forced to save files only to the actual external SDCARD because I can't write to /SDCARD or /storage/emulated/0. In other words for example, I can't use the camera because it doesn't see a usable storage device. If I open a terminal as root, and cd to /SDCARD, I can't create a directory or file, it says permissions are denied. I tried taking a screenshot of me using Total Commander as superuser attempting to create a folder in /storage/emulated/0 and it says it couldn't save the screenshot "do to limited storage space". There are no folders in either /storage/emulated/0 or /SDCARD (which is a soft link). Any idea what I did wrong, or what I could do to fix it? It looks like the filesystem is read only, but i'm not seeing that from the "mount" command.
Starting from a stock ROM, here's what I did:
I unlocked the device, and I had to login to Google and then do the time trick others had mentioned to see the "OEM Unlocking" option.
I then used Odin to flash TWRP.
After testing TWRP, i then realized there was a ROM that included twrp, so I flashed that using Odin.
Booted to TWRP, and wiped Data, followed by installing multi-disabler and Magisk.
Then booted into the ROM.
Thanks for any help on this.
Click to expand...
Click to collapse
Well, i decided to re-flash the ROM from TWRP, and while there i wiped the internal storage. Everything is working now! This device is much faster than it was, thanks for this ROM!

So, here's a version that's based on Andy's latest build of LineageOS 17.1.
Downloads:
SM-T510:
Nexus_Stock_LQ_T510XXU2ASK5-20200301.tar.md5 (Odin tarball)
Nexus_Stock_LQ_T510XXU2ASK5-20200301.zip (TWRP update)
Do you prefer this over the AOSP version?

Thank you again for your work. Will you be supporting the Android 9.0-build in your other thread as well or do you expect your users to switch to this ROM based on 10.0?
Would you describe this ROM as as stable as 9.0 or are there any backdraws?

StarGeneral said:
Thank you again for your work. Will you be supporting the Android 9.0-build in your other thread as well or do you expect your users to switch to this ROM based on 10.0?
Would you describe this ROM as as stable as 9.0 or are there any backdraws?
Click to expand...
Click to collapse
I just switched over to it for my main tablet, so ask me again in a few days. By then I should be more aware of any issues.

Hello
i have flashed your Rom both variants and they run very good, thank you for your work. But is there a way to get Widevine L1 to get working with unlocked bootloader ?.

OpenGAPPS...
Magendanz said:
My Nexus custom ROMs for media players usually include Nano and Stock (and TVStock) variants, but I intentionally released Stock only for this tablet to reduce my build times and storage footprint. Since you don't recover unused space from the system partition, it doesn't really hurt to have the extra Google apps, but I understand that it could take space from the user partition if you allowed them to be updated. With me just starting a new teaching job and working on a master's degree, I just haven't had any extra bandwidth, but I'll reevaluate in the summer.
Click to expand...
Click to collapse
Have you considered leaving out GAPPS and having us download and install them ourselves? That would make it easier for everybody, and we could choose to entirely skip it if we want. Same for v9.

Kenaz Rune said:
Have you considered leaving out GAPPS and having us download and install them ourselves? That would make it easier for everybody, and we could choose to entirely skip it if we want. Same for v9.
Click to expand...
Click to collapse
I release LineageOS builds (16.0 & 17.1) for that. And I don't know about "easier for everybody", since many novice users might not be comfortable installing OpenGApps in TWRP.

Related

[lt03wifi][P600][ROM][CM13.0][6.0.1]CM13.0 UNOFFICIAL Builds -

Joshndroid's UNOFFICIAL CM13.0 BUILDS
DISCLAIMER
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
*/
This thread is currently under maintenance. Should there be any inaccurate information, please PM me. Images and formatting will be handled at a future date.
{
"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"
}
...not ready yet
I use my TWRP version linked in Second post
Clean Install
1. Download the appropriate ROM using links provide in the second post.
2. Download the appropriate GApps following the links in the second post.
3. Back up any and all important data.
5. WIPE DALVIK/CACHE/DATA/FACTORY RESET.
6. WIPE SYSTEM. <<-- You don't have to do this unless you want too
7. Flash the ROM in recovery.
7.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
8. Flash the GApps.
9. Reboot Device.
Dirty Flash
1. Download the appropriate ROM using links provide in the second post.
2. WIPE CACHE/DALVIK. (I find wiping /SYSTEM can stop some issues with play store F/C’s)
3. Install the zip from recovery.
4. Install GApps (ensure that they are from the same build, otherwise you must do a clean installation when using a newer GApps package)
3.1. DO NOT FIX PERMISSIONS AFTER FLASHING, doing so will cause a bootloop.
5. Reboot Device.
More:
Screenshot 2
screenshot 3
probably others i havn't found as yet
@RaymanFX - without him there would be no original trees for our device, simple.
@ShevT - without him there would be no cm-13.0 for our device, simple.
Source
Joshndroid Source
Note 10.1 Device Tree
Note 10.1 Kernel
Note 10.1 Vendor Files
CyanogenMod
Rom Source

Shared Google Drive Device Folder (have Rom shared directly to your Google Drive Folder)
see here for further - http://forum.xda-developers.com/showpost.php?p=65753816&postcount=4
Alternate Download - Basketbuild Download
https://s.basketbuild.com/devs/Joshndroid/CM13.0/lt03wifi
GApps - 6.0 GApps Package
http://opengapps.org/ (select ARM & 6.0)
I have be extremely pleased with Open Gapps and you can even download daily packages, I have tried the micro, mini and nano packages with good success so far - All credit to their team and original thread source can be found here for important information and updates - http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
SuperSU for flashing via recovery - Credit to @Chainfire
http://download.chainfire.eu/supersu

Joshndroid's TWRP with F2FS support
https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
F2FS is called the 'flash friendly file system.' Realistically it has been developed to assist mobile type devices with EMMC get better read speeds, among other things, to achieve a better user experience.
Still want to know a bit more check this out – https://en.wikipedia.org/wiki/F2FS. Further have a look here for benchmarks completed on another device - http://forum.xda-developers.com/show....php?t=2697069
So, how do I get F2FS?
Firstly, your going to need to have partitions that are in F2FS format and with that you need a recovery which is capable of doing that. In the second post you will see a link for an F2FS supported recovery.
Secondly, your going to need a ROM that supports it. That means, the ROM itself to support mounting partitions correctly, etc. as well as the KERNEL so it can utilise the partitions and actually boot the device.
Yeah okay, so its entirely intertwined, now what?
Well, we now have the recovery, ROM and kernel all working with F2FS we need to put it in to practice
Follow these steps (you will need a micro sdcard inserted into your device)
Complete these steps in their entirety and accurately (if I find out you didn't complete a step or skipped one because you 'know better', leading to a bricked device, I wont be happy). They might seem condescending, but hey 2 extra minutes/step may make the difference.
1. Go to https://dl.twrp.me/lt03wifiue/ and download the appropriate stock TWRP (I recommend 2.8.6.0 now) .IMG file AND .zip of your recovery and place onto your EXTERNAL SD CARD (these are in case something doesn't work)
2. While at https://dl.twrp.me/lt03wifiue/ download the same IMG.TAR and place those files into your usual ODIN directory (in case we REALLY need to flash back a recovery) - If you need Odin, download that as well.
3. Download my latest ROM zip anything from V17.6 will be supporting f2fs unless stated otherwise. Place this file into your EXTERNAL SDCARD also.
4. Download your latest version of gapps and have a supersu zip handy (latest). Place these files into your EXTERNAL SDCARD
5. Okay download my f2fs supported recovery signified by F2FS in the name (ZIP or IMG will work in TWRP 2.8.6.0). Link in second post or https://s.basketbuild.com/devs/Joshndroid/TWRP/lt03xxxx
6. Place the F2FS supported recovery into your EXTERNAL SDCARD
7. BACKUP all important files from your device's INTERNAL SDCARD as it will be WIPED when formatting to a new partition type (and I mean it will be GONE)
8. reboot into your recovery
9. select the F2FS IMG file or ZIP and flash as necessary.
10. If successful reboot back to recovery. (if not see below, it may be to do with your current twrp version)
11. BACKUP EVERYTHING to EXTERNAL SDCARD (this will save partition info, boot/userdata/system). If super keen, transfer a copy to computer
12. Okay now the partitioning
- Go to wipe
- Go to advanced wipe
- click on cache
- click on repair or change file system
- click on change file system
- click on F2FS
- swipe to confirm
- click back till you get to the partition selection again
- Repeat step 12 changing 'cache' for 'data' and then for 'system'
13. Go back to the main menu
14. Flash ROM zip, Gapps and Super Su
15. Reboot
Optionals
16. Download a free app called 'disk info' from play store
17. check your partitions are now listed as F2FS. if they list as EXT4, you've done something wrong and need to try it again.
QUICK FAQ
Is this safe?
Yes, provided you do it correctly you wont have any issues.
Do it need to do it each time I flash my ROM?
No, you only need to convert once. Then each ROM flash will see your partitions as F2FS and format accordingly.
But I know the device formats system or other partitions during ROM flash, why do I have to do it manually?
Because the ROM zip detects the partition file system type. It will then format it with the correct tool. If you don't essentially set the file system to F2FS how does it know to format with F2FS.
Does my favourite kernel support F2FS?
probably not, check with the developer and ask them to support F2FS. If they are stuck, point them in my direction I will help.
I followed the steps correctly and get a black screen after booting?
You have probably messed something up, this seems to be kernel related. If you tried to flash a custom kernel, don't. Use only the bundled kernel until you know your favourite custom kernel supports f2fs.
Can I have some partitions as EXT4 and some as F2FS?
Probably, but I don't recommend it. Don't half complete this mod, either go full F2FS or remain at EXT4.
What about other partitions I see/know about? Can these be F2FS too?
No, they are not supported
Only System, Data (userdata) and Cache are supported, these are the typical partitions supported by other ROM devs for other devices.
So I don't have a recovery, or when I reboot to recovery it goes straight to the ROM, or I just get a blank screen?
Your recovery isn't working or didn't flash correctly. Your going to have to flash TWRP 2.8.6.0 with ODIN and try the steps again (I've tested 2.8.6.0 with the F2FS supported IMG and the ZIP file and both work)
I don't like/want F2FS can I go back?
Yes, follow the steps once again and where it says F2FS in step 12, change it to EXT4.
Can I revert to an old backup, but it was before I changed to F2FS?
Yes you can, but FIRST you MUST re-partition back to EXT4 before restoring your old backup. If that means using an older TWRP (not mine) it will still format your device back to EXT4, just do it BEFORE you restore.
Can I just restore a backup of F2FS?
Yes, but see the above ^^^ you will need to format to F2FS before restoring.
Will EXT4 still be supported?
Yes
Is F2FS better?
Not really sure, I haven't had enough time to play with it. It doesn't feel much 'faster' maybe im just being cynical lol.
I really broke/bricked my device, HELP?
if you have a stock firmware your best solution is to flash that with Odin.
Where's your TWRP source?
here - https://github.com/Joshndroid/androi...ung_lt03wifiue
Can I build my own TWRP?
Yes, but you need omnirom source so its not really worth doing it.

Google Shares
Rules -
1. I WILL NOT be keeping your PM or your email address anywhere once you have been added to the share, i WILL be respecting privacy so I expect the same in return.
2. I WILL however, be creating a google doc (probably in each rom folder) to signify by XDA username only who is in the share. (This is for a couple reasons, 1 - because I can keep track of who I have added to the share, 2 - people can see if they have been added or not to the share to either remind, 3 - It keeps people accountable when their, somewhat, online identity is linked to something.)
3. Do NOT spam me with PM's if I dont get to add you within a day. I am very active on the forums due to mobile access, but to add to the share I will need to be at home. If you have not been added and see your username in the google doc after 2 days, politely PM me again.
4. If you do not use the below template (as it has all the information I will be requiring on my end to add you), You wont be added (so 2 days will pass, you wont see your name or a rom and then check the info u sent me).
5. First download for yourself is going to be rather big (about 4 roms worth). I want to keep atleast a couple roms in the share so that if something is wrong, I can pull a download or whatever at it will not affect anything to severely.
6. You will not have any access to modify or delete the files. I am the owner and you guys will only be able to download/view (which is all you need).
Okay so how can you let me know your in.
First PM me using this template:
XDA Username -
Email (google drive account) -
Rom -
Devices (some have more than one) -
I will add you to the share, I will add you to the local google doc, you will get a device folder and your files will start to sync locally to your PC.
Couple quick FAQ's
How do you know when a new rom is on the share?
You could check it manually, I also was toying with a solution that I could share within the drive that would conduct periodic checks, problem is is that it would rely on a generated file as well as direct links (something that is hard to come by on file sharing services to firstly predict and script & usually requires you to manually click a share button to get a link).
However, there is a google chrome based extention that will notify you by tracking a folder when something new has been added to a google drive folder - https://chrome.google.com/webstore/detail/folder-notifications-for/pamfobflonhoblkekglgpplpibfnckna
This will only track and send an email based on tracking 1 folder.
I am looking into the paid version myself ($2 - http://ez34.net/ezdrive/folder-notif) that will track 10 folders (which is a lot).
Can I get roms from the other locations?
Yes. I have done this setup to quicken my workflow to get roms out, the quicker you guys get them, the happier you's are. Now the primary issue I have it sync'ing to other file services to ensure I limit my bandwidth in uploading (to reduce wait times) and to keep things concurrent across. If i upload to google drive first and sync to other locations on my end, its quicker than me manually uploading to locations.
Remember the first few days I will be spammed with PM's to add everyone who wants to join, I may be a bit slow. But once that is out of the way it will be back to usual and we will then see the benefit of it. I am big on automation, the more I can automate, including checks and failsafes, the more we become something like can be provided by big rom providers.

so;
why did i make a new thread?
Well, i was tired of spamming the other thread that is of a nightly status with these unofficial builds. I pretty much run these builds each time i run a temasek build so they will be frequent enough.
Why havnt you just submitted to CM your the maintainer?
Well, everything is not fixed yet i have been looking at the camera and once that is fixed will probably submit it for nightly status for cm-13.0
what will happen then?
This will be the main thread for cm-13.0 as it continues on, through these unofficial builds and hopefully on to nightlies once the camera is done.
what about android N?
Waaaaaaaay to early to speculate about that yet.
Anything different to base cm-13.0?
Slightly, as the rom is built using UBERTC 4.9 for the rom, the kernel specifially is untouched (unlike temasek builds)

New build March 10 2016 is up on basketbuild and google shares... cheers
Further for some rom updates whatever/follow me on twitter (DW i don't spam) - @joshndroid

Thanks you for the ROM!
This is This is stable or beta or testing? Thanks

Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?

TruThug407 said:
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
Click to expand...
Click to collapse
I prefer to use the temasek build, because of the temasek settings and the omniswitch support, but i think both releases are stable.

TruThug407 said:
Is da kernel changes da only difference from dis an your temasek build an which do u think is more stable...?
Click to expand...
Click to collapse
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom

joshndroid said:
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
Click to expand...
Click to collapse
Thanks bruh just makin sure....

joshndroid said:
Both have the same stability I havnt had one reboot on either rom but I don't get to use it enough because it gets flashed so much.
Apart from rom changes in temasek with more settings and stuff in the Temasek version. This version is vanilla cm builds.
Both roms are built with ubertc for the rom itself and there is no further kernel optimization for this rom
Click to expand...
Click to collapse
Are you planning to keep maintaining the updates on both? I currently have your Temasek version but if you are looking to focus your time on this one then I'll switch

Sy Borg said:
Are you planning to keep maintaining the updates on both? I currently have your Temasek version but if you are looking to focus your time on this one then I'll switch
Click to expand...
Click to collapse
Temasek is his main project so it will get updated more often than dis one I think he started dis one to get it goin to nightly once da camera is fixed....

Gapps for temasek cm13 - difficulty
I flashed the temasek cm13 to my 600. Works cool, except I can't find a gapps 6.0 package that works. Every time I flash the gapps, I get two errors that take over the tablet: "unfortunately setup wizard has stopped" and "unfortunately google play services has stopped." I've tried the recommended gapps here, and the a-gapps package.
Any ideas on getting gapps to work here? Any other recommended gapps packages?
Thanx in advance...
...joe

jaypea500 said:
I flashed the temasek cm13 to my 600. Works cool, except I can't find a gapps 6.0 package that works. Every time I flash the gapps, I get two errors that take over the tablet: "unfortunately setup wizard has stopped" and "unfortunately google play services has stopped." I've tried the recommended gapps here, and the a-gapps package.
Any ideas on getting gapps to work here? Any other recommended gapps packages?
Thanx in advance...
...joe
Click to expand...
Click to collapse
Bro I have a perfectly fine gapps package linked in second post (opengapps.org)...
These packages work fine for 7 devices I use.

yeah, I fixed it. it wasn't the gapps package. I keep forgetting that when flashing a new rom you need to immediately flash gapps without rebooting in between. the older I get, the more drips out of my colander-brain...

New build 18032016 is up on basketbuild and Google shares

Preparing SD card causes black screen
I had a drop down when said a new sd card had been detected. I could either use it for photos or make it non removable (guess that means Linux format). I requested the sd card be configured and not make removable. I got an instant black screen, which i left over night , the tablet was no longer frozen but the partition table on the sdcard was corrupt.
Any ideas how to get this to work ?

XDAdeveloperHTC said:
I had a drop down when said a new sd card had been detected. I could either use it for photos or make it non removable (guess that means Linux format). I requested the sd card be configured and not make removable. I got an instant black screen, which i left over night , the tablet was no longer frozen but the partition table on the sdcard was corrupt.
Any ideas how to get this to work ?
Click to expand...
Click to collapse
Don't use that... Just use it as external storage.

drm problem
Hi,
i've installed the latest version and get a DRM Error. DRM Widevine is missing...
Thx for a reply
JMF

[ROM] [UNOFFICIAL] LineageOS 13.0 for the M.O.J.O.

Wowzers, you really did it! Thanks for putting some life into this marvellous device (or trying to anyway)!
Anyway, I've installed it. I used the older TWRP 2.8.2.0. Not sure if I need to be using something more recent now, but it worked.
Code:
What is your--
LineageOS version: 13
LineageOS Download: https://drive.google.com/open?id=1NJCHZo58BnZIyELYBqlx-0Fy61uBWCAO
Gapps version: open_gapps-arm-6.0-nano-20171228
Did you--
wipe: YES
restore with titanium backup: NO
reboot after having the issue: NO
Installed nicely and with no upset. It takes a while on first boot for those of you giving this a go, so allow a moment or two while it gets things together.
Got to say I am very impressed. It's Lineage 13! On the MOJO! Yes AudioFX doesn't work as you say, but it seems the rest does! However, I'm having a couple of issues you may be able to help with. Firstly, I tried rooting the device in the same way I did CM 12.1, basically by going into developer options and selecting root access. However, there's only an option to root via ADB, no apps access. Is this intentional? I was unable to install my quick reboot app meaning one has to hard shut down (i.e. pull the plug) on the device which is never an elegant way to do things. What is the best solution to root this please? Many thanks.
I also notice that when trying to use a browser, be it Firefox or Chrome, to download something it gives you an error. I tried to download a simple file and Firefox just failed, but luckily Chrome was a bit more verbose and explains why. It said it did not have access to the internal storage despite me confirming all the options after installing it. Not sure what's happening here.
Other than these things, at this early stage the only other thing I noticed was some tearing of the screen on animated transitions. Occasionally it seems to pull and break up a bit when whipping around.
I think I speak for everyone here when I say - THANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOU!!! I look forward to further adventures with this ROM!

K-Project said:
Wowzers, you really did it! Thanks for putting some life into this marvellous device (or trying to anyway)!
Anyway, I've installed it. I used the older TWRP 2.8.2.0. Not sure if I need to be using something more recent now, but it worked.
Code:
What is your--
LineageOS version: 13
LineageOS Download: https://drive.google.com/open?id=1NJCHZo58BnZIyELYBqlx-0Fy61uBWCAO
Gapps version: open_gapps-arm-6.0-nano-20171228
Did you--
wipe: YES
restore with titanium backup: NO
reboot after having the issue: NO
Installed nicely and with no upset. It takes a while on first boot for those of you giving this a go, so allow a moment or two while it gets things together.
Got to say I am very impressed. It's Lineage 13! On the MOJO! Yes AudioFX doesn't work as you say, but it seems the rest does! However, I'm having a couple of issues you may be able to help with. Firstly, I tried rooting the device in the same way I did CM 12.1, basically by going into developer options and selecting root access. However, there's only an option to root via ADB, no apps access. Is this intentional? I was unable to install my quick reboot app meaning one has to hard shut down (i.e. pull the plug) on the device which is never an elegant way to do things. What is the best solution to root this please? Many thanks.
I also notice that when trying to use a browser, be it Firefox or Chrome, to download something it gives you an error. I tried to download a simple file and Firefox just failed, but luckily Chrome was a bit more verbose and explains why. It said it did not have access to the internal storage despite me confirming all the options after installing it. Not sure what's happening here.
Other than these things, at this early stage the only other thing I noticed was some tearing of the screen on animated transitions. Occasionally it seems to pull and break up a bit when whipping around.
I think I speak for everyone here when I say - THANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOUTHANKYOU!!! I look forward to further adventures with this ROM!
Click to expand...
Click to collapse
I personaly use TWRP-2.8.7.0.
For full root you need to install root addon, it's how Lineage is made.
And try to reboot or force close chrome or firefox, sometimes it doesn't take permission at first launch, hope it works because I didn't try chrome.
Have you made an advanced wipe? because without format system the install script will backup some garbage of the previous rom witch can cause issue.

Thanks for replying.
Yes I did an advanced wipe. I wanted to be sure that this was cleanly done.
I'm not familiar at all with Lineage so I had no idea about root addons. I think I've found them now, so I'll reflash the device and post back later. Thanks for the heads up.
I didn't attempt to reboot either Chrome or Firefox so I'll give that another go too after the reflash.

Code:
What is your--
LineageOS version: 13
LineageOS Download: [url]https://drive.google.com/open?id=1NJCHZo58BnZIyELYBqlx-0Fy61uBWCAO[/url]
Gapps version: open_gapps-arm-6.0-pico-20171228
Did you--
wipe: YES FULL
restore with titanium backup: NO
reboot after having the issue: NO
Youtube works perfect (my "test" video plays) :highfive:
Still two other crashes is here View attachment 2017-12-28-20-39-36e.txt
Process ru.norgen.homevideo (pid 3189) has died
Process com.lolapp.lolapptv (pid 3527) has died
Nice work - looks very promissing

This is amazing , wow , thanks so much ,I will try it asap

Nice, next week I have again a good internet connection so I can sync the lineageos tree. I'll then will try to port androidTV

Very impressed with the WiFi so far. No issues that I've discovered, though of course this is an early stage. It works even when booting with an SD card in.
OK, so reflash... I switched to TWRP 2.8.7.0 as you said.
Following your reply I grabbed the Lineage AddonSu package that seemed relevant, but unfortunately this would not flash. It gave me an error message 4 and said there was a problem with the binary. I tried it twice but no luck. However, I had an older Super Su package I kept from a while ago (2.46) and flashed this. It worked fine and even updated from the Play Store OK. This allowed me to install and use the reboot app just fine. So I set about installing some apps.
As you stated, after a reboot of Firefox it downloads fine. Simply permit it access to your storage, and then close and reopen. This works.
I installed both Kodi and Retroarch but I am getting no sound at all. At first I thought I'd done something wrong in the settings for both apps and the device but it appears not. There's no sound at all. I will attempt a reboot again but it didn't work after a couple of reboots. Is this expected at this stage or is there something I need to do? Please let me know.
Anyway, my thanks again for a great update. I really hope you carry on the work and I look forward to continuing with this OS. I hope my posts are helping rather than causing any problem.
---------- Post added at 10:52 PM ---------- Previous post was at 10:47 PM ----------
Only other thing I noticed was the MOJO seems to get very warm and does seem to lag a little bit with the mouse after half an hour. I checked the memory usage and it seemed OK, so perhaps it's hammering the CPU? I dunno, but thought it worth mentioning to see if other folks notice the same thing.

awesome thanks for this

[Sorry for multiple posts]
Sound is back today. Not sure what happened but it's working fine. I've decided to just set everything up as I normally have it and really see how it goes. So far everything seems to be working as it should.
Awesome!
However, I am definitely experiencing some lag once the device has been on for some time. I've been playing with the MOJO all morning and there's definitely screen tearing and some lagginess in transitions over time. It seems better after a reboot, but it's not long before it creeps back in again. I'll be curious to see if anyone else has this issue.

K-Project said:
Very impressed with the WiFi so far. No issues that I've discovered, though of course this is an early stage. It works even when booting with an SD card in.
OK, so reflash... I switched to TWRP 2.8.7.0 as you said.
Following your reply I grabbed the Lineage AddonSu package that seemed relevant, but unfortunately this would not flash. It gave me an error message 4 and said there was a problem with the binary. I tried it twice but no luck. However, I had an older Super Su package I kept from a while ago (2.46) and flashed this. It worked fine and even updated from the Play Store OK. This allowed me to install and use the reboot app just fine. So I set about installing some apps.
---------- Post added at 10:52 PM ---------- Previous post was at 10:47 PM ----------
[/COLOR]Only other thing I noticed was the MOJO seems to get very warm and does seem to lag a little bit with the mouse after half an hour. I checked the memory usage and it seemed OK, so perhaps it's hammering the CPU? I dunno, but thought it worth mentioning to see if other folks notice the same thing.
Click to expand...
Click to collapse
I havn't seen su addon issue before because I havn't try it yet! the issue is in twrp, so I have two option: make a compatible addon or a new twrp recovery.
I'm going for the new twrp solution because it will also allow Lineage 14.1 install if i want to try it.
For the lags I need to check clocking parameters, maybe they are wrong.

nono2lozere said:
I havn't seen su addon issue before because I havn't try it yet! the issue is in twrp, so I have two option: make a compatible addon or a new twrp recovery.
I'm going for the new twrp solution because it will also allow Lineage 14.1 install if i want to try it.
For the lags I need to check clocking parameters, maybe they are wrong.
Click to expand...
Click to collapse
I was testing with TWRP 2.8.2 and addonsu-13.0-arm-signed.zip - everything was fine.
Only Lineage SU was forgetting "allow" after reboot...
P.S. TWRP 2.8.7 was doing something wrong with CM builds or OpenGapps or SuperSU installation - only don't remember what... Now long time sitting on 2.8.2 - everything OK :angel:

nono2lozere said:
I havn't seen su addon issue before because I havn't try it yet! the issue is in twrp, so I have two option: make a compatible addon or a new twrp recovery.
I'm going for the new twrp solution because it will also allow Lineage 14.1 install if i want to try it.
For the lags I need to check clocking parameters, maybe they are wrong.
Click to expand...
Click to collapse
Not sure if there's a better way to check CPU, but I notice when using KODI it runs at 100% all the time. I use an external drive with my media files, and while they would play you could tell it was struggling. Lots of stutter, despite changing the settings etc.
rahsoft said:
I was testing with TWRP 2.8.2 and addonsu-13.0-arm-signed.zip - everything was fine.
Only Lineage SU was forgetting "allow" after reboot...
P.S. TWRP 2.8.7 was doing something wrong with CM builds or OpenGapps or SuperSU installation - only don't remember what... Now long time sitting on 2.8.2 - everything OK :angel:
Click to expand...
Click to collapse
I'd be curious to know what the difference is. Like I say, I ended up using TWRP 2.8.7.0-mojo and then flashed the older SuperSu 2.46 zip. This seems to work and has done the job, but I wonder if it there's an incompatibility that is causing my lag issues...?

Don't know if anyone can help here. Installed this and it just upgraded my CM 12.0 I had installed.
I lost root so couldn't boot back into recovery using an app.
I went to boot into recovery using PC and a male to male (which I did originally when flashing CM 12.0 but it just sends me to a boot loop with the liniage os intro scene.
If I boot again normally I get back to Lineage OS. Problem is I wanted to install this as all my apps were crashing constantly after a year of no issues (with CM12).
They're still crashing with Lineage OS but I can't get it to recovery mode for a fresh install.

TrentLane said:
Don't know if anyone can help here. Installed this and it just upgraded my CM 12.0 I had installed.
I lost root so couldn't boot back into recovery using an app.
I went to boot into recovery using PC and a male to male (which I did originally when flashing CM 12.0 but it just sends me to a boot loop with the liniage os intro scene.
If I boot again normally I get back to Lineage OS. Problem is I wanted to install this as all my apps were crashing constantly after a year of no issues (with CM12).
They're still crashing with Lineage OS but I can't get it to recovery mode for a fresh install.
Click to expand...
Click to collapse
Are you sure you've plugged the male-to-male USB cable into the right slot? It has to be in the USB2 one or the MOJO will continue to boot as normal. I know this as I did exactly the same thing very recently. Plug your mouse into the blue USB3 slot instead.
You cannot brick the MOJO unless the hardware has failed. It can always be rescued by connecting it to a PC/laptop and reflashing TWRP then ROM etc. I posted here not so long ago that my MOJO suddenly and for no real reason decided to plunge into a bootloop just as it was installing some simple updates from the Play store. It had been absolutely fine for nearly two years. Nevertheless I was able to connect it to the laptop and reflash and run TWRP. There I completely erased the device and installed Lineage 13 as the timing couldn't have been more perfect.

TrentLane said:
Installed this and it just upgraded my CM 12.0 I had installed.
Click to expand...
Click to collapse
Wait... so can I upgrade from CM 12.1 without losing anything?!

EdoNINJA93 said:
Wait... so can I upgrade from CM 12.1 without losing anything?!
Click to expand...
Click to collapse
don't think so
Instructions :
Download the latest build and gapps
Reboot to recovery
Go Wipe->Advanced->Select system,cache and data partition
Flash the latest build and gapps
Reboot
Click to expand...
Click to collapse

Wmapa said:
don't think so
Click to expand...
Click to collapse
It would have been too good to be true...
From his message it seemed that all the apps remained untouched... :/

EdoNINJA93 said:
Wait... so can I upgrade from CM 12.1 without losing anything?!
Click to expand...
Click to collapse
You can try but make a backup before, I don't know if it's possible.

First post updated.
Enjoy new build!

[ROM][UNOFFICIAL][9] LineageOS4Microg 16.0 (by Bernie_nix)

Rom Built by Bernie_nixKnown issues:
USB-C headphones work for music, watching videos, etc. They don't work in the phone app...yet. (working on this)
Some users report VOIP calls don't work properly. YMMV. Skype, Whatsapp, Nextcloud Talk, working great for me.
Automatic updates not yet implemented but will be in a future build.
You tell me.
Install Instructions(If coming from stock or another rom):
Prerequisites: Coming from stock rom with bootloader unlocked, Developer settings enabled, android debugging enabled.
(1) ADB reboot bootloader,
(2) Fastboot boot twrp.img
(3) Install copy A/B partitions zip,
(4) Select Wipe button, Advanced Wipe, Choose: Dalvik/ART Cache, Data, Internal Storage, System. Then Swipe to Wipe all of these.
(5) Select Back arrow button
(6) Select Format Data Button. Type yes
(7) Select Install button. Choose rom zip. Swipe to confirm flash.
(8) Press back arrow button 2x to get back to main screen. Select Wipe button. Select format data button. Type yes.
(9) Reboot. Phone will mention "no os installed." Ignore it. Proceed with reboot. Phone will boot twice, then take you to the lineage recovery screen. Use volume down button to select Factory data reset, press power button, select yes to delete data. Phone will reboot into lineageos4microg.
DO NOT install twrp installer/orange fox installer until after phone boots into lineageos4microg or it will not boot. After you have setup lineageos, you can then reboot into twrp and install orange fox or twrp and magisk if you choose. Do not ever install any GAPPS on this ROM.
Upgrade Instructions(If coming from one of my previous builds):
(1) ADB reboot bootloader,
(2) Fastboot boot twrp.img
(3) Select Install button. Choose rom zip. Swipe to confirm flash.
(4) Select Wipe button, Advanced Wipe, Choose: Dalvik/ART Cache
(5) Reboot(6) If you had Magisk installed, you can then reboot into TWRP/Ofox and flash magisk.zip
Tips for Use
1. Root can be enabled in this build by going to Developer Settings->Root Access->Apps and ADB
2. To turn off battery led when charging, Settings>Apps & notifications>Notifications>Battery Light
3. To set up Microg,
(1) open MicroG app,
(2) press self-check, press battery optimizations ignored and allow,
(3) go back one screen, select unified nlp settings, configure location backends, press the checkbox next to mozilla location service and ok, configure address lookup backends, press checkbox next to nominatum and ok,
(4) then go through Google services from top to bottom and enter your information.
(5) Enable location from pull-down shade. Open maps, get your location. Go back to Microg. Run self-check. All boxes should show a check.
(6) Microg is setup in less than 5 minutes and fully working.
(7) Turn off location from pull-down shade bc they're tracking you 4. Want a better GPS experience? Install Deja Vu Location Service, GSM Location Service and Radiocells.org Unified Network Location Provider Backend from F-Droid. Works great with Google Maps or OSM.
5. Looking for a great camera? Try Hypercam for Moto G7 from gcambrasil at https://gcambrasil.com.br/motorola
1. After installing, go to internal storage, create folder "gcam" (without quotes), create folder "Configs" inside of "gcam," and place the Pixelmod_byJGB.xml (attached) file in that folder.
2. Open up Hypercam, double tap on black space near camera button, load Pixelmod_byJGB.xml file.
Reporting bugs:
DO NOT Report bugs if you're running a custom kernel or you installed Xposed.
Please report bugs in this thread.
Logcats are helpful but not required. Grab a full logcat right after the problem has occurred.
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Thread Purpose & LimitsThis thread has been created to discuss the installation and use of this rom. If you have questions about building roms, this thread is not the place to do it. Please create a thread under Q/A and/or visit the Telegram group https://t.me/mG7Power. I'm happy to help but going to the telegram group or opening a Q/A thread allows many users to assist you and will help to keep this thread on-topic. Failure to follow this request will result in a warning followed by report to XDA if continued. Some excellent resources for building microg include https://lineage.microg.org/ and https://8192.one/post/lineage_build_with_docker/.
Download:
Change log
1. Latest March security update
Status: Stable
ROM OS Version: 9.x Pie
Android Security Patch Level: Mar. 5, 2020
Download link: https://www.androidfilehost.com/?fid=4349826312261741637
MD5: 54b467570f65ce85f164bd8e99943ab7
Older Versions:
Change log
1. Latest sources
2. Root option enabled in development settings
Status: Stable
ROM OS Version: 9.x Pie
Android Security Patch Level: Feb. 5, 2020
Download link: https://androidfilehost.com/?fid=4349826312261727435
MD5: aeb4aa1141c6d74ac016e8fba797c245
Next update news...:
Mar 10, 2020 - Currently working on USB-C audio during phone calls, increasing audio volume. Once USB-C audio gets fixed, I'll enable OTA updates.
Source and Additional Links
https://github.com/LineageOS
https://github.com/LineageOS/android...otorola_sdm632
Telegram group for additional ROMS, files and support: https://t.me/mG7Power
Rom Last Updated Mar. 10, 2020
Thread Info Last Updated Mar. 10, 2020
Guide on how to build your own posted here: https://forum.xda-developers.com/g7...d-lineageos4microg-16-0-t4070079#post82069641

hi im really interested in this rom but If twrp is already my permanent recovery, this rom won't install correctly?
edit.. tried it anyway since this is a secondary phone, figured i didnt have much to lose, followed instructions to the TEE, and it installed just fine.

clarkkentxda said:
hi im really interested in this rom but If twrp is already my permanent recovery, this rom won't install correctly?
edit.. tried it anyway since this is a secondary phone, figured i didnt have much to lose, followed instructions to the TEE, and it installed just fine.
Click to expand...
Click to collapse
I should have another update with OTA server and a few other fixes soon. It's also super quick to update from current build. Stay tuned and enjoy!

Bernie_nix said:
I should have another update with OTA server and a few other fixes soon. It's also super quick to update from current build. Stay tuned and enjoy!
Click to expand...
Click to collapse
Thanks for your efforts, I've been enjoying it, it's hard to find a rom that offers a little privacy from google, most things are working just fine, one thing I've noticed is that video is super super dark, No matter if it's stock camera or open camera but that's all I've came across in the issues department so far

clarkkentxda said:
Thanks for your efforts, I've been enjoying it, it's hard to find a rom that offers a little privacy from google, most things are working just fine, one thing I've noticed is that video is super super dark, No matter if it's stock camera or open camera but that's all I've came across in the issues department so far
Click to expand...
Click to collapse
Thanks for your feedback! No problems with video if using a different app. Try Hypercam version 1.3.030119.0645build-6.1.021

Bernie_nix said:
Thanks for your feedback! No problems with video if using a different app. Try Hypercam version 1.3.030119.0645build-6.1.021
Click to expand...
Click to collapse
Hypercam works like a charm, thank you for the suggestion! does hyper cam rely on anything google related like services or frameworks or binarys? (not sure what to call it since im not a developer) i'm wondering because I own a pixel 3a and im thinking of installing graphene os but any apps that rely on those ran on those will not work on graphene

clarkkentxda said:
Hypercam works like a charm, thank you for the suggestion! does hyper cam rely on anything google related like services or frameworks or binarys? (not sure what to call it since im not a developer) i'm wondering because I own a pixel 3a and im thinking of installing graphene os but any apps that rely on those ran on those will not work on graphene
Click to expand...
Click to collapse
Hypercam is ported from gcam so YMMV. Given that it works on this ROM with microg, if it has any hooks they probably aren't deep. I'd give it a go

I've been a user of root explorer (pro) for seven+ years or so now. I side loaded the apk that I extracted from a previous setup on my phone and it works perfect. Some may already know that but just figured I'd share. Awesome job on this rom! Appreciate you sharing your builds!! :good:

flash713 said:
I've been a user of root explorer (pro) for seven+ years or so now. I side loaded the apk that I extracted from a previous setup on my phone and it works perfect. Some may already know that but just figured I'd share. Awesome job on this rom! Appreciate you sharing your builds!! :good:
Click to expand...
Click to collapse
Glad you like it and thanks for your feedback; tip on root explorer pro.

Bernie_nix said:
Glad you like it and thanks for your feedback; tip on root explorer pro.
Click to expand...
Click to collapse
Couple questions.. What busy box are you using and where did you get it? I've been using Osmosis’s magisk module busy box for so long idk where to even begin. haha. I attempted to install one from fdroid but it failed install. Can I flash his busy box in recovery? Probably not because we are using the LOS built in root instead of magisk correct? Would all hell break loose if I flashed magisk root now and something would possibly get messed up? Thinking if that's what I wanted I would have had to flash it in the beginning so it would over ride the other root...?
This rom runs better than anything besides ugly stock moto on my device. I was off work yesterday so I started messing with my device, hours went by and my battery barely moved at all. Not having Google play services really saves a good bit of juice. Havoc has spoofing now too. I vote that it becomes mandatory for all roms to have signature spoofing. :victory: Should call it the ImNOtgoingback rom or something. I’ve used micro g and fdroid before on previous devices but never for as long as I've been using this. Im like a binge crackflasher nowadays instead -vs- back when Euroskank CM10 bacon was on and popping every morning at around 6am central time the world would all flash. One last thing.. Do you decrypt your data or leave it encrypted? Reason I ask is I was wondering what method you do or would do if you wanted to decrypt?
This rom really runs great! Anyone who hasn't tried this yet should!
Edit
Ps: I've used many great gcams but HyperCam is most definitely at the top of my list. It reminds me of the pictures my Pixel XL used to take. Awesome camera app! Thanks for recommending it and sharing links!

not being picky, but can we have a regular LOS build please? I mean, without microG.
The last syberhexen one is dated 2019-10-01 so it would be nice to have an update to it.

DanAlucard said:
not being picky, but can we have a regular LOS build please? I mean, without microG.
The last syberhexen one is dated 2019-10-01 so it would be nice to have an update to it.
Click to expand...
Click to collapse
You're right, but it's not easy to be a maintainer - and use your free time to resolve problems for others.
Maybe you should try to create your own build using code created by more advanced users synced with latest LineageOS repo.
If you're interested in that, here's an attached manifest file which would build working LineageOS 16.0 for ocean with February security patch - I'm using such one right now(built 3 days ago), but with microg. It's all possible thanks to LineageOS team and Dark98 (and many others) work, as you can see.
Good luck

robson_89 said:
You're right, but it's not easy to be a maintainer - and use your free time to resolve problems for others.
Maybe you should try to create your own build using code created by more advanced users synced with latest LineageOS repo.
If you're interested in that, here's an attached manifest file which would build working LineageOS 16.0 for ocean with February security patch - I'm using such one right now(built 3 days ago), but with microg. It's all possible thanks to LineageOS team and Dark98 (and many others) work, as you can see.
Good luck
Click to expand...
Click to collapse
Thanks a lot. Will have a look at it. Who knows, maybe I end up maintaining it

DanAlucard said:
Thanks a lot. Will have a look at it. Who knows, maybe I end up maintaining it
Click to expand...
Click to collapse
That would be great!
In the meantime, i've built and updated my LOS 16 as attached - forgot to add screenshot previously.

DanAlucard said:
not being picky, but can we have a regular LOS build please? I mean, without microG.
The last syberhexen one is dated 2019-10-01 so it would be nice to have an update to it.
Click to expand...
Click to collapse
Not from me. I build this for personal use, share it and have no interest in a vanilla los build. Robson is correct. Go with his build of you don't want microg.

flash713 said:
Couple questions.. What busy box are you using and where did you get it? I've been using Osmosis’s magisk module busy box for so long idk where to even begin. haha. I attempted to install one from fdroid but it failed install. Can I flash his busy box in recovery? Probably not because we are using the LOS built in root instead of magisk correct? Would all hell break loose if I flashed magisk root now and something would possibly get messed up? Thinking if that's what I wanted I would have had to flash it in the beginning so it would over ride the other root...?
This rom runs better than anything besides ugly stock moto on my device. I was off work yesterday so I started messing with my device, hours went by and my battery barely moved at all. Not having Google play services really saves a good bit of juice. Havoc has spoofing now too. I vote that it becomes mandatory for all roms to have signature spoofing. :victory: Should call it the ImNOtgoingback rom or something. I’ve used micro g and fdroid before on previous devices but never for as long as I've been using this. Im like a binge crackflasher nowadays instead -vs- back when Euroskank CM10 bacon was on and popping every morning at around 6am central time the world would all flash. One last thing.. Do you decrypt your data or leave it encrypted? Reason I ask is I was wondering what method you do or would do if you wanted to decrypt?
This rom really runs great! Anyone who hasn't tried this yet should!
Edit
Ps: I've used many great gcams but HyperCam is most definitely at the top of my list. It reminds me of the pictures my Pixel XL used to take. Awesome camera app! Thanks for recommending it and sharing links!
Click to expand...
Click to collapse
Thank you for your kind words! I use busybox from osmosis via magisk module; yes, I enjoy magisk on this rom. Busybox (osmosis) actually makes apps like Titanium Backup work great if you've purchased a non-Google play license file from them. This rom is my personal build that I uploaded to xda and shared, and I plan on maintaining it for some time. So...Magisk flashed via twrp/ofox works great, and so does busybox magisk.
+1 on your comment about Hypercam. Completely agree about hypercam. I've tested a lot on this device and of course am open to suggestions.
I will update this rom via the Lineageos patches, however, the Feb update hasn't been pushed yet so no new rom for now. I have isolated a few bugs, e.g. usb-c for calls and am working on OTA, however, I am going to release a surprise test build in the next couple of days (hopefully). It's building as we speak, and I will test before releasing. Stay tuned, and I look forward to yours and others feedback and questions.
P.S. I am a linux user and believe in the power of open-source. If you or others have any questions or comments, feel free to reach me via the telegram link in the 1st post; I usually answer a bit quicker there but also answer on here. Best wishes and thanks again!
P.S.S. Welcome Robson to our open-source team! If any of you are looking for a lineageos build without microg, check out his post a couple of posts above.

generally audio is lower quality than stock rom, it's not as loud and not as clear.

clarkkentxda said:
generally audio is lower quality than stock rom, it's not as loud and not as clear.
Click to expand...
Click to collapse
Did you try the audiofx app that is included?

Bernie_nix said:
Did you try the audiofx app that is included?
Click to expand...
Click to collapse
Indeed sir, it doesn't help all that much for me though.

rottenwheel said:
I accompany this sentiment. It happens with most Motorola Moto G devices I own and use: if kept with stock builds both camera and audio have a far better quality than custom ROMs do. Motorola engineers do hell of a job when working on their OEM firmware. It is a real shame yet not so far from reality that we need to take these tradeoffs to obtain better privacy.
An idea that comes to mind is for us to debloat the stock build, bake in microG and possibly update security patches as they come out. Motorola Moto G1 (falcon) has something alike with IDCrisis - https://forum.xda-developers.com/moto-g/development/rom-identity-crisis-6-t3324595
Thank you for the heads-up, though. I definitely love the audio on stock.
Click to expand...
Click to collapse
Unfortunately you can't do that with stock. Microg requires signature spoofing enabled in the ROM which is a patch applied when building a ROM. You could try patching stock to enable signature spoofing with a tool like Heystack but it most likely won't work on stock. Another route is using another ROM with signature spoofing support e.g. crdroid or omni, applying signature spoofing patch if necessary and then patching in twrp with something like nanodroid patcher.
That being said I am working through desired edits and bugs in this ROM but can't provide any ETAs. I encourage anyone with a bit of coding experience or interest to build their own and learn. Making changes to rom builds is not hard, just time consuming and unfortunately doesnt pay the bills...so its done in hobby time. I do plan on maintaining this ROM for some time though and will probably be on Pie longer than most users until 10 is ready; right now 10 has way too many bugs for me to use or build for daily driver material.

[ROM][UNOFFICIAL][matisse][millet] crDroid 6.27 (Discontinued)

{
"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"
}
https://crdroid.net/
crDroid is a LineageOS-based CustomRom.
This one is based on LOS 17.1.
Special Thanks to matteo0026, who is maintaining the device sources and TWRP.
Disclaimer
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions or a nuclear war that comes as a result of flashing this ROM. Please make also be sure that you have always a full backup ready. Best to use: Nandroid Backup via TWRP
Installation instructions :
Be sure to have installed the latest TWRP recovery (you can find it in downloads)
Download the latest build and GApps (ARM, 9.0, I advice pico package) and copy it to your external SD-Card
Make a full Backup of your Data and copy it to your external SD-Card or USB-OTG
Boot to recovery mode
Wipe > Advanced wipe > Select system, data, cache and dalvik/art cache (and, if you want to clean more, select even internal storage, which deletes all the content in /sdcard) and do swipe to wipe. Format /data. When it's finished go to home page
Install > select ROM zip file > swipe to flash and when it's finished go to home page
Do the same thing to flash GApps and Root (if needed)
Reboot > System
Update instructions :
Be sure to have installed latest TWRP build
Download the latest build
Boot to recovery mode
Install > select ROM zip file > swipe to flash and, when it's finished go to home page
Reboot > System
Known issues :
crDroid 5.12 (discontinued)
This ROM is discontinued because of not fixable bugs.
Matisse is working but better use 6.xx or 7.xx
All Millet Devices -> Camera is not working, no fix so far.
crDroid 6.xx
Camera is working at all Devices
Face Unlock is working at all Devices
Downloads :
crDroid 5.12 (discontinued)
matisse (10.1) devices: Androidfilehost, Mega
millet (8.0) devices: Androidfilehost, Mega
crDroid 6.xx
matisse (10.1) devices: Androidfilehost, Mega
millet (8.0) devices: Androidfilehost, Mega
Other Stuff
TWRP Recovery Matisse and Millet: XDA, Mega, Matisse, Millet
GApps: https://opengapps.org/ (ARM, 10)
Magisk: https://github.com/topjohnwu/Magisk
Contributors:
crazydrive22, matteo0026 and all the S3NEO devs that provided the base for developing Pie on Tab 4
Source Code:
https://github.com/lineageos for samsung msm8226 common device and kernel source, with some patches coming from Gerrit for device source
https://github.com/s3neo for matisse and millet and specific variants device and vendor source
Thread started at 2021-01-31
Thread updated at 2022-06-25

will test this rom on my smtt330nu millet wifi, on the weekend when i have some free time.

Love your work! It works perfect on my matissewifi! No known issues! Have a lot of thanks, crazydrive22!

New Builds with February Security Patch are online.
There's still no fix for the broken Camera at Millet-Devices.

thanks excellent ROM on sm-t530

.. regular updates! I like it!

crazydrive22 said:
New Builds with February Security Patch are online.
There's still no fix for the broken Camera at Millet-Devices.
Click to expand...
Click to collapse
HI Crazydrive22,
Just downloaded latest Feb update for MilletWifi.
This build has some major issues, same as original crROM Version.
1. When updating using dirty flash, or clean version. Using TWRP v3.4.0-4 millet version, Nandroid backup does backup, Boot partition that is Rooted with Magisk 20.4. Your Rom overwrites Boot partition. Therefore Magisk Root is removed, therefore needs to restored.
2. After flashing both crROM versions released in Jan and now Feb. Require latest version GAPPS Nano, to be reflashed again, to stop Google Play services, crashing every minute or so. Reflash Gapps fixed that , as well other random Google apps, also crashing continuously.
3. After finally getting things back to normal, on latest crROM Version, needed a couple of restarts, as Tab4 was slow to respond, to some apps to operate at normal speed, compared to Matteo's builds. I have been using for 12 months now.
4. Then found internal memory is running out of space. Had plenty of spare, before using this ROM. Needs more research to find cause. Originally did a Wipe then clean flash and reinstalled all 100 odd apps, via Google Cloud.
5. I restored previous Matteo, Jan 21 build Nandroid backup with same number apps, plenty of internal memory left.
6. Tried to install your LOS16 Dec build, to compare with Matteo version. Downloaded from both sources, listed above in Post 1. Zip file crashes each time.
Found I needed to repair it , to allow me to open it. That is why, TWRP flash failed.
I did MD5 compare, that passes each time. So I suggest you need to upload again, a recompiled LOS16 ROM.
7. I have been working with Matteo, to help solve the Millet version CAMERA issues, over the last few months. But Matteo, has run out of ideas, at the moment.
8. So I decided to try crROM build by you.
But sadly still got issues with saving photos, but video front and rear camera works.
Panorama works saving photos. But photo saving crashes Camera app, with same unknown message, same as Matteo's ROM.
SO I suggest you have a look at the issues mentioned, and keep trying to resolve the camera issues with Matteo.
Great work so far, thanks for your effort to add another ROM for these OLD Devices.
Hope that helps you with some feedback, I have found some minor issues, that I had managed to fix easily.
Cheers
BeeJ1109

BeeJ1109 said:
HI Crazydrive22,
Just downloaded latest Feb update for MilletWifi.
This build has some major issues, same as original crROM Version.
1. When updating using dirty flash, or clean version. Using TWRP v3.4.0-4 millet version, Nandroid backup does backup, Boot partition that is Rooted with Magisk 20.4. Your Rom overwrites Boot partition. Therefore Magisk Root is removed, therefore needs to restored.
2. After flashing both crROM versions released in Jan and now Feb. Require latest version GAPPS Nano, to be reflashed again, to stop Google Play services, crashing every minute or so. Reflash Gapps fixed that , as well other random Google apps, also crashing continuously.
3. After finally getting things back to normal, on latest crROM Version, needed a couple of restarts, as Tab4 was slow to respond, to some apps to operate at normal speed, compared to Matteo's builds. I have been using for 12 months now.
4. Then found internal memory is running out of space. Had plenty of spare, before using this ROM. Needs more research to find cause. Originally did a Wipe then clean flash and reinstalled all 100 odd apps, via Google Cloud.
5. I restored previous Matteo, Jan 21 build Nandroid backup with same number apps, plenty of internal memory left.
6. Tried to install your LOS16 Dec build, to compare with Matteo version. Downloaded from both sources, listed above in Post 1. Zip file crashes each time.
Found I needed to repair it , to allow me to open it. That is why, TWRP flash failed.
I did MD5 compare, that passes each time. So I suggest you need to upload again, a recompiled LOS16 ROM.
7. I have been working with Matteo, to help solve the Millet version CAMERA issues, over the last few months. But Matteo, has run out of ideas, at the moment.
8. So I decided to try crROM build by you.
But sadly still got issues with saving photos, but video front and rear camera works.
Panorama works saving photos. But photo saving crashes Camera app, with same unknown message, same as Matteo's ROM.
SO I suggest you have a look at the issues mentioned, and keep trying to resolve the camera issues with Matteo.
Great work so far, thanks for your effort to add another ROM for these OLD Devices.
Hope that helps you with some feedback, I have found some minor issues, that I had managed to fix easily.
Cheers
BeeJ1109
Click to expand...
Click to collapse
Thanks for your Feedback. Unfortunately I don't own a Millet Device and can't reproduce this errors atm. I'm looking to buy one in the next time.
Could you please dl and test my latest LOS16 Build i uploaded today? This should be exactly the same as Matteos, cause i'm using his Device Tree.
Cheers

crazydrive22 said:
Thanks for your Feedback. Unfortunately I don't own a Millet Device and can't reproduce this errors atm. I'm looking to buy one in the next time.
Could you please dl and test my latest LOS16 Build i uploaded today? This should be exactly the same as Matteos, cause i'm using his Device Tree.
Cheers
Click to expand...
Click to collapse
Hi crazydrive22,
I will try LOS16 Build for you.
Another issue with crROM.
Adding extra Icons on Home screen. Work OK. But I save them to lawn chair option on internal memory and extSD card for backup. Backups produced OK on both locations. But Restore only restored original icons on 3 screens, but not newly added icons on any of the 3 screens including Home screen. Tried a few times, created extra backup files on internal and ext SD card. Available in Restore list. Copied files created between both. File size increases as I add more icons to Home or other screens. Just not showing up when I restore any created file.
I want to use this option, by installing the crdroid home 9 app. On Matteo ROMs, so I can Restore icons, on all screens, after a re-flash of any ROM. Would really be useful, save heaps of time, as I have some 100 odd apps.
Any ideas.
Cheers BeeJ1109

Hi Crazydrive22,
Sorry Tried LOS16 Latest version. Boot loops everytime.
Let it go until TWRP reboots as Recovery.
Re flashed a couple times, wiped cache, dalvik , system a few times, no change, still boot looping.
Cheers. BeeJ1109

Working perfect! No bugs!
When update to Android 10.0?
My Tablet: SM-T530
Before Andrdoid 5.0.2 and now Android 9.0!

Hi,
Flash does not work with twrp 3.0.0, but this is the latest official twrp.
Can you suggest a TWRP version for this ROM?

Hi All,
TWRP 3.4.0-4 by Matteo works. My device is Milletwifi.
Reflashed again after doing tests on Stock ROM for Matteo, did Wipe Cache, Dalvik & System, then reflashed this latest version.
Booted OK This Time. Instability with Google Play Service, So reflashed Nano Gapps. Fixed instability. But WiFi had issues, would not accept Password on several of my WiFi connections on both 2.4 or 5Ghz channels being Routers, Repeater, or Extenders.
Still using Stock EFS & Modem, same partitions, have not been overwritten. WiFi D.L was > 54Mbps, U.L > 18Mbps. Works great on Stock ROM.
So this ROM LOS16 Feb Build has issues. Camera does not work, same as Matteo's LOS 16. In fact this ROM appears to be identical to Matteo's LOS16. Apart from being compiled, by Crazydrive22. Therefore different title in About. Not sure what Crazydrive22 is trying to achieve here, apart from proving the Compile works, using the same repository sources as Matteo.
So I have restored back to Matteo ROM Feb Build. WiFi is back to same as before.
So I attached files.
Cheers BJ

ufa said:
Hi,
Flash does not work with twrp 3.0.0, but this is the latest official twrp.
Can you suggest a TWRP version for this ROM?
Click to expand...
Click to collapse
Its works with 3.5.0.9

Thank you all. Unofficial TWRP from Matteo worked.

makin17 said:
Working perfect! No bugs!
When update to Android 10.0?
My Tablet: SM-T530
Before Andrdoid 5.0.2 and now Android 9.0!
Click to expand...
Click to collapse
I'm planning to go to 10 and also 11 but there's no ETA atm. I'm working with Matteos Device Sources, so as soon he's ready, i'll be, too.

ufa said:
Hi,
Flash does not work with twrp 3.0.0, but this is the latest official twrp.
Can you suggest a TWRP version for this ROM?
Click to expand...
Click to collapse
BeeJ1109 said:
Hi All,
TWRP 3.4.0-4 by Matteo works. My device is Milletwifi.
So this ROM LOS16 Feb Build has issues. Camera does not work, same as Matteo's LOS 16. In fact this ROM appears to be identical to Matteo's LOS16. Apart from being compiled, by Crazydrive22. Therefore different title in About. Not sure what Crazydrive22 is trying to achieve here, apart from proving the Compile works, using the same repository sources as Matteo.
Click to expand...
Click to collapse
Sorry Guys, i was very busy the last time.
Matteo decided to go to LOS17 and LOS18, so I will build LOS16 for the future.
That's why we are building side by side, to check if everything is working well.
And as you've seen, it was a good idea.
With the next build (around 5th of March) everything should work on Millet, except the Camera.

god to know.

crazydrive22 said:
I'm planning to go to 10 and also 11 but there's no ETA atm. I'm working with Matteos Device Sources, so as soon he's ready, i'll be, too.
Click to expand...
Click to collapse
Update with OTA update or reinstall new ROM with Android 10?

makin17 said:
Update with OTA update or reinstall new ROM with Android 10?
Click to expand...
Click to collapse
If you switch the Version always clean flash with TWRP.
Updates as long as it is BETA via TWRP.
Maybe i'll go to OTA later, but there's no ETA so far.

[UNOFFICIAL][ROM]ALPHA LineageOS 19.1 for Galaxy Tab A [SM-T550] May 6, 2023

PLEASE BEFORE YOU decide to try this rom, you MUST read all of post 1, 2, 3 and 4 (about 10 minute read). If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
BACKUP YOUR DATA AND OLD rom BEFORE trying my rom.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT use this rom. You must know how to use these tools to revert back to your old rom.
If you are new to flashing custom roms, do NOT attempt this.
If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. camera
What doesn't work
1. selinux is permissive. I have tried to make this build enforcing for weeks, but when I do, the OS doesn't boot and there is no adb logcat output despite making an "eng" build. Without adb logcat output, it's virtually impossible to determine what is wrong and I'm not spending anymore time on it. If having enforcing mode is important to you, use my 18.1 builds.
2. keyboard bug workaround. When prompted to enter something like a Bluetooth pin or text based password, sometimes the keyboard is not shown on the screen or off screen. The workaround is to goto settings, system, languages & input, on-screen keyboard, Android Keyboard (AOSP), appearance & layout, theme and choose "Material - follow system settings".
This keyboard bug is a LineageOS bug as per
https://review.lineageos.org/c/LineageOS/android_packages_inputmethods_LatinIME/+/325438
3. gapps. Some of you require gapps for whatever reason. I use Aurora Store for my purposes and thus have NO KNOWLEDGE of the current state of gapps.
There are various gapps projects (at least 5 in 2022). Each has pros and cons. It's your job to do the research and find a suitable gapps project. I suggest you allocate at least a couple of hours doing your own research. My rom works by itself fine without gapps. DO NOT talk about gapps in this thread. As a courtesy to gapps users, if you want to talk about gapps, I have opened a new thread at
https://forum.xda-developers.com/t/...m-t35x-sm-t550-sm-t560nu-and-sm-p550.4479285/
so you may discuss gapps wrt to the msm8916 platform. I will NOT be participating in that thread as I do NOT use gapps.
Thanks
1. LineageOS team for source code.
2. Kyle Harrison
- looking through the adb logcat and suggesting that my binder code was too old to work with Android 12's keystore2 code
- for the graphics and legacy camera patches to allow msm8916 to work with Android 12
- for his Motorola LineageOS 19.1 device trees so I could use his patches as a template for msm8916
3. @tarkzim
- adding back audio hal 2.0 and legacy camera hal 1.0 into the LineageOS trees
- helping me think through the msm8916 random reboots which was due to the TCP/IP patches
- maintaing and updating his repos so I can study them for learning purposes
4. pre ALPHA testers @breversa , @XDA_username00 for willing to test pre ALPHA builds and leaving feedback.

FAQ - I spent hundreds of hours building this rom. It was frustrating process from Nov 2021 to Aug 2022 running into bug after bug. The least you can do is spend a few minutes reading everything before posting.
Q1. Where are the source and kernel source files?
A1. The kernel source files are at
https://github.com/retiredtab/android_kernel_samsung_msm8916
The device tree files are at
https://github.com/retiredtab/android_device_samsung_msm8916-common/tree/lineage-19.1
https://github.com/retiredtab/android_device_samsung_gt510wifi/tree/lineage-19.1
https://github.com/retiredtab/device_samsung_gte-common/tree/lineage-19.1
The vendor tree files are at
https://github.com/retiredtab/android_vendor_samsung_gt510wifi/tree/lineage-19.1
https://github.com/retiredtab/vendor_samsung_msm8916-common/tree/lineage-19.1
The manifest.xml (or roomservice.xml) and build instructions for 19.1 are at
https://github.com/retiredtab/LineageOS-build-manifests
Q2. Is this ALPHA rom suitable as a daily driver?
A2. It can be depending on your requirements. I can't test every app so you try it yourself to see if it's suitable. I've been using this rom myself since mid March 2022 with no major issues. I suggest you do a clean install, see FAQ 11, and flash this 19.1 ROM BY ITSELF (no gapps, magisk, etc) and see if you like it. If you do like it and want to add gapps then see FAQ 12.
Q3. What if my app, xyz, doesn't work?
A3. If your app doesn't work, then go back to your old rom.
Q4. Your rom is laggy and buggy.
A4. If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps. You can run a lot of software without using gapps. Research fdroid, newpipe, Aurora store etc.
Q5. What TWRP should I use?
A5. You MUST use TWRP 3.5.2_9. Get it from
https://dl.twrp.me/gt510wifi/
Q6. Why should I use this rom?
A6. If you don't like this rom, then don't use it.
Q7. Will you offer monthly updates with security patches?
A7. I will try to offer monthly security patches, but that all depends on if I continue to have high speed Internet in the future.
Q8. Can you help me? I'm a newbie. Can you provide step by step instructions?
A8. I don't have the time to help newbies, so please do your own research. There are lots of tutorials, videos, etc on how to flash roms. Newbie questions must be posted in the Questions and Answers forum, not here.
Q9. Can I report a bug with respect to the rom?
A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
You must provide an adb logcat of the problem and tell me how to reproduce it. Note I will not be downloading any apps that require money or an userid/password. For example, if you have problems with Netflix, I cannot help you since I don't have a paid subscription. If you use some app that requires an userid/password, I cannot help you as I'm not willing to create another userid/password even if it's free.
To get a logcat, open up a terminal window.
Code:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occured, then stop trace by hitting ctrl-c
# attach the problem.txt ZIPPED as text files don't seem to get attached properly
Q10. Will you still build 18.1 for this device?
A10. Yes, for rest of 2022, but I will make a decision in January 2023 on how 18.1 and 19.1 will be maintained. If you like to help by building 18.1/19.1, please let me know.
Q11. Do I need to erase everything and format my data?
A11. Yes, you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 19.1 when you are coming from stock or an earlier version of LineageOS or from another custom rom. If you get stuck at the boot animation for more than 5 minutes, it's likely because you didn't follow the instructions I just wrote. Dirty flashes from stock, other custom roms or older LineageOS versions are not supported and not likely to work.
Q12. What gapps should I use?
A12. I don't use gapps anymore. I use Aurora Store. As of Nov 6, 2021, I no longer make recommendations on which gapps to use as your mileage may vary.
Let me by crystal clear. YOU NEED TO DO YOUR OWN HOMEWORK selecting between the various gapps offered. There are 5: opengapps, nikgapps, mindthegapps, flamegapps and bitgapps. Each one will have it's own installation instructions. The only recommendation I will offer to use the SMALLEST version of gapps.
Don't be surprised that whatever gapps you use might have problems like "Just a sec", voice not working, updating google play store please wait, etc. These are NOT problems of the OS as the OS will run fine without gapps. These are gapps problems and you must ask in the gapps forum why it doesn't work.
In addition, some of the gapps may not install properly when using TWRP and say "cannot /mnt/system". For those cases, please use the LineageOS recovery.img you can download from
https://sourceforge.net/projects/retiredtab/files/SM-T550/LineageOS-recovery/
By flashing the LineageOS recovery.img, it will overwrite the existing TWRP and you will get a different UI.
Q13. I'm having problems with gapps, can you answer why it's not working?
A13. I WILL NOT answer any questions regarding gapps. This thread is about the rom, not gapps. Android does not depend on gapps in order to work.
Questions about gapps, for your courtesy, should be asked at
https://forum.xda-developers.com/t/...m-t35x-sm-t550-sm-t560nu-and-sm-p550.4479285/
Q14. Why isn't my post answered or ignored?
A14. Questions already answered in the FAQ will be completely ignored. Again, I do not use Windows OS or gapps.
Q16. What speed up/optimization tips do you suggest?
A16.
1. Turn off animations. Go into developer settings, scroll down to the drawing section, and set window, transition and animator scale all to "off".
2. If you don't have a google account, don't install gapps. Use Aurora Store to get your apps as you can get all the same apps from the play store using an anonymous login.
3. Dont' run more than 2 apps at the same time. You can probably listen to music in the background and use a web browser at the same time, but don't expect great performance from a 2015 entry level tablet.
4. Use a web browser like Brave that has built in adblock and privacy features.
5. Use newpipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
6. Look for apps that are open source, ad free and lightweight.
7. Remove all unused quick setting "bubbles" from the quick pull down menu. I only need and have 6.
Q17. Does this rom support Magisk for root?
A17. I don't use Magisk myself so I don't know and Magisk is always being updated to fool Google's certification process. Others have reported Magisk as working, but I won't answer any questions regarding it.
Q18. Will this rom ever become official?
A18. With 19.1, legacy devices like ours will NEVER be official due to lack of ebpf support. See https://lineageos.org/Changelog-26/
Also, I don't want the responsibilities that come with being an official maintainer.
Q19. What is the difference between this rom and others?
A19. This rom tries to be pure LineageOS with little to no modifications.
Q20. Will there be any major 19.1 code modifications in the future?
A20. I don't anticipate any major modifications. There may be some small bug fixes and minor code cleanup, but all the hard work in getting the rom up and running and fixing all the major bugs have been done completed. This doesn't mean the code is perfect or well organized, but I won't be doing any major changes now that 19.1 is working.
Q21. Why did you fork the device and vendor trees for 19.1?
A21. The msm8916 repos seem geared towards phones and sometimes do not work or cause boot animation loops for tablets so I decided to fork their repos. In other words, what's deemed as msm8916-common code isn't common to all devices.
In addition, since I'm building SM-T350, SM-T357W, SM-T550, SM-P550 and SM-T560NU (all use the same msm8916 code), it seems easier to maintain all of them if I can control my own code repos and not worry if my changes affects the phones or not.
I have completely decommonized and rearranged the 19.1 msm8916-common tree so it's easier for me to maintain and build.
Q22. Can you build a variant of this device? For example, a LTE or S-pen version.
A22. If I don't physically have the device, I cannot and will not build it unless I can boot and test it myself. Even then, there's no guarantee that I can get those variant features working.
Q23. Can I load this rom on a variant devivce like LTE or S-pen version?
A23. The rom is built for the device explicitly listed. If you are an advanced user and understand TWRP, adb, odin, heimdall, you can try loading it on a LTE or S-pen variant by modifying the updater-script, but it may cause a bricked device, bootloops or non functionality of LTE/S-pen. You have been informed and warned!
Q24. What major code changes are in 19.1 vs 18.1.
A24.
- iptables has been removed in favour of ebpf
- keystore v1 has been replaced with keystore v2 which requires that the binder calls have some built-in security
- audio hal 2.0 has been deprecated
- legacy camera hal 1.0 and snap app have deprecated
Q25. I don't like the taskbar, how do I turn it off?
A25. Choose settings, type task into the search bar. Choose enable taskbar and disable taskbar. This will leave the on screen nav bar. If you want to disable that, go to settings, system, gestures, system navigation, gesture navigation.
Q26. Okay, I understand the consequences and that this is ALPHA rom and willing to take the risks outlined, now where can I find the rom?
A26. You can download it from https://sourceforge.net/projects/retiredtab/files/SM-T550/19.1/

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.
19.1 has been my daily driver since March 2022.
May 6, 2023 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-05
2. Whatever LineageOS changed since Apr 5 patches. About 7,400 files had to be recompiled.
Apr 13, 2023 release notes
1. Apr 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-04
2. Whatever LineageOS changed since Mar 5 patches. About 23,000 files had to be recompiled.
March 19, 2023 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-03
2. Whatever LineageOS changed since Feb 5 patches. About 24,500 files had to be recompiled.
Feb 12, 2023 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-02
2. Whatever LineageOS changed since Jan 5 patches. About 12,500 files had to be recompiled.
Jan 8, 2023 release notes
1. Jan 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-01
2. Whatever LineageOS changed since Dec 5 patches. About 4,400 files had to be recompiled.
Dec 9, 2022 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-12
2. Whatever LineageOS changed since Nov 5 patches. About 4,700 files had to be recompiled.
Nov 11, 2022 release notes
1. Nov 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-11
2. Whatever LineageOS changed since Oct 5 patches. About 5,400 files had to be recompiled.
Oct 7, 2022 release notes
1. Oct 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-10
2. Whatever LineageOS changed since Sept 5 patches. About 4,500 files had to be recompiled.
Sept 12, 2022 release notes
1. Sept 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-09
2. Switched to different timekeep repo that works with Android 12 and up.
3. Whatever LineageOS changed since Aug 5 patches. About 4,700 files had to be recompiled.
Aug 10, 2022 release notes
1. Aug 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-08
2. Initial ALPHA release to public.

Reserved.

Wanted to report no issues with this recent version via in-place upgrade from last month's v19.1 alpha test build.
For anyone still running v17 or v18 wondering if it's worth upgrading, it depends on your use case.
Here's mine if it helps:
I use this SM-T550 tablet on a semi-regular basis for web browsing, reading e-books, and watching video content.
Using v3.6.2_90 TRWP with a microSD card and some Bluetooth headphones.
No gapps, Bromite Chromium browser, NewPipe, and all other apps downloaded via anonymous session using Aurora Store (which also works great with tracking updates).
Apps: Bitwarden (still slow, but faster than when on v18), Netguard, Netflix (no DRM issues), Nova Launcher, Plex, United Airlines app (need the Bromite browser installed for DRM content to play), and Amazon Kindle.

Works great.

bierma32 said:
Works great.
Click to expand...
Click to collapse
can you give more info please. is good for the daily use? thanks

I used now more than 4 weeks and all what I have tested works perfect.
It is my daily driver.
Bluetooth works , WiFi connection is much stable if you have an worse signal.
Battery consumption I much better than Los 18.1

I have the smt550. Do you have a guide to root it and install this rom? Where can i find it? Thanks

vuoshinotizy said:
can you give more info please. is good for the daily use? thanks
Click to expand...
Click to collapse
Everything seems to work (except RIL as mine is an LTE device). Just bear in mind that SELinux is disabled, so you might not want to use the tablet to store sensitive data.
vuoshinotizy said:
I have the smt550. Do you have a guide to root it and install this rom? Where can i find it? Thanks
Click to expand...
Click to collapse
A general guide to install a custom OS for a Samsung device can be found on the LineageOS website. Here's an example for a different Samsung device https://wiki.lineageos.org/devices/beyond1lte/install
The main differences are you'll need to refer to the original post Q5 to obtain a custom recovery (TWRP) and Q26 to obtain the LineageOS build.

New build lineage-19.1-20220912-UNOFFICIAL-gt510wifi.zip
NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.
19.1 has been my daily driver since March 2022.
Sept 12, 2022 release notes
1. Sept 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-09
2. Switched to different timekeep repo that works with Android 12 and up.
3. Whatever LineageOS changed since Aug 5 patches. About 4,700 files had to be recompiled.

retiredtab said:
New build lineage-19.1-20220912-UNOFFICIAL-gt510wifi.zip
Click to expand...
Click to collapse
No issues with in place upgrade. Still works great!

vuoshinotizy said:
I have the smt550. Do you have a guide to root it and install this rom? Where can i find it? Thanks
Click to expand...
Click to collapse
Just sent you PM with the steps I used to get it on mine.

retiredtab said:
PLEASE BEFORE YOU decide to try this rom, you MUST read all of post 1, 2, 3 and 4 (about 10 minute read). If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
BACKUP YOUR DATA AND OLD rom BEFORE trying my rom.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT use this rom. You must know how to use these tools to revert back to your old rom.
If you are new to flashing custom roms, do NOT attempt this.
If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. camera
What doesn't work
1. selinux is permissive. I have tried to make this build enforcing for weeks, but when I do, the OS doesn't boot and there is no adb logcat output despite making an "eng" build. Without adb logcat output, it's virtually impossible to determine what is wrong and I'm not spending anymore time on it. If having enforcing mode is important to you, use my 18.1 builds.
2. keyboard bug workaround. When prompted to enter something like a Bluetooth pin or text based password, sometimes the keyboard is not shown on the screen or off screen. The workaround is to goto settings, system, languages & input, on-screen keyboard, Android Keyboard (AOSP), appearance & layout, theme and choose "Material - follow system settings".
This keyboard bug is a LineageOS bug as per
https://review.lineageos.org/c/LineageOS/android_packages_inputmethods_LatinIME/+/325438
3. gapps. Some of you require gapps for whatever reason. I use Aurora Store for my purposes and thus have NO KNOWLEDGE of the current state of gapps.
There are various gapps projects (at least 5 in 2022). Each has pros and cons. It's your job to do the research and find a suitable gapps project. I suggest you allocate at least a couple of hours doing your own research. My rom works by itself fine without gapps. DO NOT talk about gapps in this thread. As a courtesy to gapps users, if you want to talk about gapps, I have opened a new thread at
https://forum.xda-developers.com/t/...m-t35x-sm-t550-sm-t560nu-and-sm-p550.4479285/
so you may discuss gapps wrt to the msm8916 platform. I will NOT be participating in that thread as I do NOT use gapps.
Thanks
1. LineageOS team for source code.
2. Kyle Harrison
- looking through the adb logcat and suggesting that my binder code was too old to work with Android 12's keystore2 code
- for the graphics and legacy camera patches to allow msm8916 to work with Android 12
- for his Motorola LineageOS 19.1 device trees so I could use his patches as a template for msm8916
3. @tarkzim
- adding back audio hal 2.0 and legacy camera hal 1.0 into the LineageOS trees
- helping me think through the msm8916 random reboots which was due to the TCP/IP patches
- maintaing and updating his repos so I can study them for learning purposes
4. pre ALPHA testers @breversa , @XDA_username00 for willing to test pre ALPHA builds and leaving feedback.
Click to expand...
Click to collapse
Hi, Installed 19.1 recovery, did factory reset, formatted system and installed 19.1 version. No error messages. Unfortunately it keeps booting into recovery only. What did I do wrong?

Zomer123 said:
Hi, Installed 19.1 recovery, did factory reset, formatted system and installed 19.1 version. No error messages. Unfortunately it keeps booting into recovery only. What did I do wrong?
Click to expand...
Click to collapse
At first you have to tell us from which ROM or OS ( Stock ) you are comming.
Which Recovery you have installed ? TWRP or Lineage Recovery.
Have flashed only LOS 19.1 or LOS + Gapps ( which Version ) or have you flashed LOS + Gapps and Magisk ?
Try it again , factory reset and wipe cache , Data ( int. Sdcard ) System.
Flash Los and reboot system.
Is this OK . next step factory reset, flash Los and Gapps
Reboot system and so on.

bierma32 said:
At first you have to tell us from which ROM or OS ( Stock ) you are comming.
Which Recovery you have installed ? TWRP or Lineage Recovery.
Have flashed only LOS 19.1 or LOS + Gapps ( which Version ) or have you flashed LOS + Gapps and Magisk ?
Try it again , factory reset and wipe cache , Data ( int. Sdcard ) System.
Flash Los and reboot system.
Is this OK . next step factory reset, flash Los and Gapps
Reboot system and so on.
Click to expand...
Click to collapse
Coming from los 18.1 (aug 2022)... Installed los 19.1 recovery. Then factory reset etc. Then installed los 19.1 (sept). No gapps, no magisk...

Zomer123 said:
Coming from los 18.1 (aug 2022)... Installed los 19.1 recovery. Then factory reset etc. Then installed los 19.1 (sept). No gapps, no magisk...
Click to expand...
Click to collapse
Is there a reason for going with the LOS recovery image instead of TWRP? TWRP has worked great for me since v17 and haven't had a need for recovery with the SD Card, but then you might have a particular use case.
Remember you'll need to wipe the dalvik/data/internal storage/cache/system partitions first, then format data before installing the OS.
Hope any of that helps.

XDA_username00 said:
Is there a reason for going with the LOS recovery image instead of TWRP? TWRP has worked great for me since v17 and haven't had a need for recovery with the SD Card, but then you might have a particular use case.
Remember you'll need to wipe the dalvik/data/internal storage/cache/system partitions first, then format data before installing the OS.
Hope any of that helps.
Click to expand...
Click to collapse
I already solved it by flashing twrp using Odin.

Zomer123 said:
I already solved it by flashing twrp using Odin.
Click to expand...
Click to collapse
What was the reason that you have flashed the Lineage Recovery, since TWRP worked before ?

bierma32 said:
What was the reason that you have flashed the Lineage Recovery, since TWRP worked before ?
Click to expand...
Click to collapse
Idk, thought that it would be necessary to flash the 19.1 rom... But I also got back to 18.1 version since 19.1 is more laggy and has ugly QS tiles.

Better Mobile App

welcome