Related
I thought I would share this ROM just in case anyone wants something a little different to the Shipped Stock Sony Firmware
The ROM is based on Sony XA F3111 (Single SIM UK Firmware)
Firmware Version: 33.3.A.1.97
Build Date: Fri Sep 15 04:41:21 CST 2017
It has only been tested on my own UK version Sony XA F3111
BootLoader needs to be Unlocked and of course Usual T&C's apply. Use at your own risk don't blame me if you brick your device or lose your valuable data etc etc.
So what's different about this ROM??
Ok so I have been working on this for quite sometime during the little free time I have.
The ROM is my own preferences only and it may not be to everyone's tastes so you're quite welcome to take it, leave it, add to it, strip it, mod it, etc, etc.
The ROM ditches the not so useful stuff of Sony's but retains what I consider the good stuff like Music Album and the Camera.
Where possible I have replaced the Sony stuff with Google's Stuff which receive regular updates and keep the Rom looking fresh.
The trick to this ROM was finding a good balance without breaking anything in the process which I think I have now achieved.
This is a list of the visible apps installed, there are quite a few none visible Sony & MediaTek apps still installed that relate to settings functions and some background stuff.
Google Apps:
Clock
Calculator
Contacts
Calendar
Chrome
Drive
Files
GMail
Hangouts
Maps
Messages
Phone
Photos
Play Store
Wallpapers
YouTube
Sony Apps:
Album (Please disable this in /settings/app It will constantly search for other apps I removed otherwise. Use the pre-installed Google Photos app instead)
Camera
Music
Radio
Swiftkey (Left this in because I like it)
There is nothing Fancy about this ROM it's based on pure stock with the mods being restricted to the following.
Converted boot.elf to Boot.img
forceencryption Removed.
dm-verity Removed
I converted all the images in the stock Boot Animation so it is now a much more pleasing black rather than the awful white burning out your eyeballs one.
I remember messing with the logo partition once before and that did not end well so I left it alone. Sadly the logo splashscreen is still the awful white version.
TWRP Recovery fixed to support more partitions (Backing Up and Restore)
Flashing InstructionsThe ROM is packaged as a TWRP Backup containing system, oem, boot and recovery (TWRP)
First you will need to install this TWRP HERE which has oem partition support and others too.
1. Install the TWRP Recovery above.
2. Boot to the new TWRP and backup oem, system and boot then move it to a safe place off device or to and external sdcard. Same goes for anything you value like pictures, music, etc, etc
3. Once you have Backed Up everything FORMAT your /data partition using TWRP. Wipe > Format Data (type yes to confirm)
When that's done choose Wipe > Advanced Wipe and select Dalvik / ART Cache and Cache after that from the TWRP menu choose Reboot and select Recovery
4. When back in recovery swipe to allow then do a quick Backup of any small partition like boot or recovery. This will just create the folders on your clean data partition unless your default backup is external sdcard.
5. Now extract/unpack the downloaded ROM from HERE and move the folder SonyXA-Android-One to TWRP/BACKUPS/Sony_XA/
6. Once done go to TWRP Menu and choose Restore and select SonyXA-Android-One
7. Once done go to the Reboot Menu and Choose Power OFF
8. Wait a few Mins and power on normally.
First boot can take a while but if you see the boot animation start everything should be fine so go have a brew while you wait.
Play Services will want to Update so allow that then most apps will need to be updated to the latest version.
Arrange the app icons and widgets on your Home screen and choose a nice wallpaper or live wallpaper and your done.
Hopefully everything will be quick & smooth. :fingers-crossed:
The ROM is not pre rooted so Root in the usual way using Magisk
PS: Ensure you check your app permissions and Default APPS the Phone app is Not the Default one even though it's the only one installed so please choose it Manually along with any others that do not set by themselves.
Thanks
Some Screenshots
{
"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"
}
......
.....
.....
Thank you so much! I'm looking a long time for a custom ROM for xperia xa. The hardware and the device itself are still good for an average user like me but the bloatware are really annoying. A custom ROM based on stock ROM brings the stability but better performance, I hope. I will definitely try it at the next weekend. :good:.
If some one else tried it, please post your experience with other country versions.
z4Android said:
Thank you so much! I'm looking a long time for a custom ROM for xperia xa. The hardware and the device itself are still good for an average user like me but the bloatware are really annoying. A custom ROM based on stock ROM brings the stability but better performance, I hope. I will definitely try it at the next weekend. :good:.
If some one else tried it, please post your experience with other country versions.
Click to expand...
Click to collapse
Thanks. :good:
Be sure to let me know how you get on with it. :fingers-crossed:
I am not sure where you are from or which version of the XA you have but I am sure the ROM could be easily adapted for your own version.
All I would need would be a backup of your /oem & /boot partitions and the build.prop from your /system .
There is a modem config file in /oem which states telefonica uk I am unsure if this has any effect at all as I am sure I have flashed firmware from other European regions with no noticable effects.
I'm from Germany. I not sure but I think it should be no problems installing on my device f3111 single sim like yours (but german version of course ).
I'm not at home now. When I get back I will try your ROM. If it doesn't work I will backup OEM and boot partition as you mentioned. Last time I try to make a backup with twrp I got a error that system cannot be mounted. No idea why, so I hope I don't need make backup (I will just backup my data manually).
z4Android said:
I'm from Germany. I not sure but I think it should be no problems installing on my device f3111 single sim like yours (but german version of course ).
I'm not at home now. When I get back I will try your ROM. If it doesn't work I will backup OEM and boot partition as you mentioned. Last time I try to make a backup with twrp I got a error that system cannot be mounted. No idea why, so I hope I don't need make backup (I will just backup my data manually).
Click to expand...
Click to collapse
Hi, Your version should have no issues as it's identical to mine :good:
As for TWRP yes it does have issues with Unmounting /system for some reason
So if you mount /system from the Mount Menu TWRP or auto mount system you will not be able to Unmount mount it due to the "device or resource busy" error
If this happens you will need to ensure auto mounting is unselected and reboot to recovery from the Reboot menu.
I will look into the TWRP issue later to make things easier
Greetings,
quick question: Does the ROM restore procedure keep the TWRP on the boot partition somehow? Will it be possible to boot in TWRP after restoring the modded ROM?
I got the "bluesplash" ROM right now, it's modded quite similar and was restored by TWRP the same way. If only TWRP would sill be accessible...
Bluesummerz said:
Greetings,
quick question: Does the ROM restore procedure keep the TWRP on the boot partition somehow? Will it be possible to boot in TWRP after restoring the modded ROM?
I got the "bluesplash" ROM right now, it's modded quite similar and was restored by TWRP the same way. If only TWRP would sill be accessible...
Click to expand...
Click to collapse
TWRP lives in the Recovery partition which can be accessed by holding Volume Down and pressing the Power button until you see the logo then release the Power button but keep holding the volume down.
This ROM is based on Android 7.0 and I think your current bluesplash ROM is based on Android 6.0 if I am not mistaken so there may be some unknown issues so I would recommend upgrading your device to 7.0 before flashing this ROM
bigrammy said:
TWRP lives in the Recovery partition which can be accessed by holding Volume Down and pressing the Power button until you see the logo then release the Power button but keep holding the volume down.
This ROM is based on Android 7.0 and I think your current bluesplash ROM is based on Android 6.0 if I am not mistaken so there may be some unknown issues so I would recommend upgrading your device to 7.0 before flashing this ROM
Click to expand...
Click to collapse
Hey, thanks for the quick response!
of course I meant recovery but still maybe you can clear this one up for me in general. Since I'm looking our for a decent custom ROM (and while waiting for the LinageOS port) I was wondering about some stuff...
1. You're right the bluesplash ROM is Android 6. It does have some nice features which I guess have to weight off for against how much I'd like Android 7. Also Security Update status of Bluesplash is January 2017 and won't update beyond that... while the screenshot here tells it's August 2017.
2.
I unlocked the bootloader, flashed the TWRP by fastboot and used the TWRP on my F3111 to successfully restore the bluesplash ROM. Now holding down Volume- while booting to enter TWRP does NOT work any more. You'll still see like one quick 'flicker' on the boot animation which kinda suggests "ok, would have booted to recovery, but not this time".
Here comes the part I never really understood even after using this awesome forum for finding and flashing custom ROMs for several phones. Even though, TWRP is on the recovery and the kernel is on the boot partition (right?) so often you'll read instructions on TWRP threads containing download links for recovery.img AND boot.img. I had - or guess I had to - fastboot-flash both .img files to boot into TWRP.
I never had this when the flashing was done by TWRP "install" .zip mechanisms. Bluesplash as well as this ROM - if I'm not mistaken - comes not in that format but by the Backup/Restore TWRP feature. So for me it seems, that using "install .zip" does flash system partition and maybe boot but keeping recovery for re-entering TWRP, while the "Restore backup" also flashes the boot.img in a way such that TWRP won't boot. Also just re-flashing recovery.img and boot.img after restoring Bluesplash kinda break the normal, non-TWRP boot
--> So how can this be, how is it supposed to be and what is the connection between recovery and boot partitions when it comes to TWRP?
--> does all of this goes for this Android 7 ROM as well? Can anyone verify that on this ROM you'll still be able to boot in TWRP?
3. I know now I got the Sony Xperia XA F3111. When I first got it with stock firmware, I somehow flashed TWRP and when I USB connected the phone while in TWRP to a PC, it showed up as "ukulele". I thought I got "tuba" which was reinforced when some ROM couldn't get flashed, saying "this rom [...] is for ukulele [...] this is tuba".
Bluesummerz said:
Hey, thanks for the quick response!
of course I meant recovery but still maybe you can clear this one up for me in general. Since I'm looking our for a decent custom ROM (and while waiting for the LinageOS port) I was wondering about some stuff...
1. You're right the bluesplash ROM is Android 6. It does have some nice features which I guess have to weight off for against how much I'd like Android 7. Also Security Update status of Bluesplash is January 2017 and won't update beyond that... while the screenshot here tells it's August 2017.
2.
I unlocked the bootloader, flashed the TWRP by fastboot and used the TWRP on my F3111 to successfully restore the bluesplash ROM. Now holding down Volume- while booting to enter TWRP does NOT work any more. You'll still see like one quick 'flicker' on the boot animation which kinda suggests "ok, would have booted to recovery, but not this time".
Here comes the part I never really understood even after using this awesome forum for finding and flashing custom ROMs for several phones. Even though, TWRP is on the recovery and the kernel is on the boot partition (right?) so often you'll read instructions on TWRP threads containing download links for recovery.img AND boot.img. I had - or guess I had to - fastboot-flash both .img files to boot into TWRP.
I never had this when the flashing was done by TWRP "install" .zip mechanisms. Bluesplash as well as this ROM - if I'm not mistaken - comes not in that format but by the Backup/Restore TWRP feature. So for me it seems, that using "install .zip" does flash system partition and maybe boot but keeping recovery for re-entering TWRP, while the "Restore backup" also flashes the boot.img in a way such that TWRP won't boot. Also just re-flashing recovery.img and boot.img after restoring Bluesplash kinda break the normal, non-TWRP boot
--> So how can this be, how is it supposed to be and what is the connection between recovery and boot partitions when it comes to TWRP?
--> does all of this goes for this Android 7 ROM as well? Can anyone verify that on this ROM you'll still be able to boot in TWRP?
3. I know now I got the Sony Xperia XA F3111. When I first got it with stock firmware, I somehow flashed TWRP and when I USB connected the phone while in TWRP to a PC, it showed up as "ukulele". I thought I got "tuba" which was reinforced when some ROM couldn't get flashed, saying "this rom [...] is for ukulele [...] this is tuba".
Click to expand...
Click to collapse
You are confusing things beyond what they need to be
This is why I said you should first upgrade to 7.0 You can use FlashTool for this if need be. After that is done simply rename the recovery.emmc.win & boot.emmc.win from the download to recovery.img & boot.img then fastboot them to recovery & boot respectively.
You Should now be able to boot to TWRP and use restore once your /data partition is FORMATED per the instructions above.
TWRP is a stand alone recovery.img complete with the kernel and on Android 7.0 you can boot to recovery without any issue providing the bootloader is unlocked.
You would need to be at this stage for flashing Lineage 14.1 anyway so may as well do it now just in case we make any break through on that which is still very much a WIP.
bigrammy said:
You are confusing things beyond what they need to be
This is why I said you should first upgrade to 7.0 You can use FlashTool for this if need be. After that is done simply rename the recovery.emmc.win & boot.emmc.win from the download to recovery.img & boot.img then fastboot them to recovery & boot respectively.
You Should now be able to boot to TWRP and use restore once your /data partition is FORMATED per the instructions above.
TWRP is a stand alone recovery.img complete with the kernel and on Android 7.0 you can boot to recovery without any issue providing the bootloader is unlocked.
You would need to be at this stage for flashing Lineage 14.1 anyway so may as well do it now just in case we make any break through on that which is still very much a WIP.
Click to expand...
Click to collapse
And that is exactly why I like these forums, if you provide enough insight to a question, you'll get the full-spectrum answer, splendid!
And yes, confusing things is in my nature, also I might find it troublesome to know when I get like off topic here, so please stop me the moment, it would be better to switch to pm.
So the image format in those firmware bundles, typically having the emmc.win file extension are actually the same binary format as the fastboot .img ones? Now that's good to know.
Upgrading with FlashTool: I'll use the stock Android 7 Firmware for this right?
After that I fastboot recovery first, then boot using the renamed files from this threads ROM, got it. And then booting into TWRP, doing the system format, making it 'ready' for the restore.
And if everything goes as planned, you would guarantee, that after this thread's ROM is restored, booting into TWRP does work?
PS
indeed, Linage for F3111 would be glorious, meanwhile, what does WIP stand for (no native speaker here from Germany)
Bluesummerz said:
So the image format in those firmware bundles, typically having the emmc.win file extension are actually the same binary format as the fastboot .img ones? Now that's good to know.
Click to expand...
Click to collapse
Correct they are essentially a dd backup of the entire partition in question.
[Edit] To expand TWRP does not convert anything so if those partitions had the stock recovery & boot .elf format on them when the backup was performed they will still be .elf's which are not fastboot compatible. Those in my ROM have already been converted to .img format which is compatible with fastboot.
If you ever got stuck for some reason then you could simply use FlashTool to restore the Stock Recovery (fotakernel), Boot, OEM & System
Bluesummerz said:
Upgrading with FlashTool: I'll use the stock Android 7 Firmware for this right?
Click to expand...
Click to collapse
Correct.
My Phone is restored using the F3111_33.3.A.1.97_1302-4476_R2B.ftf (FlashTool Firmware) and the ROM is based on this version.
Try to use a 33.3.A.1.97 if possible as I know that works.
Bluesummerz said:
After that I fastboot recovery first, then boot using the renamed files from this threads ROM, got it. And then booting into TWRP, doing the system format, making it 'ready' for the restore.
Click to expand...
Click to collapse
Fastboot the recovery and the boot then You Simply need to follow the Flashing Instructions from step 2 in the first post from this point.
It is /data that gets wiped manually BTW (By The Way). TWRP will take care of the /system during it's restore tasks.
Bluesummerz said:
And if everything goes as planned, you would guarantee, that after this thread's ROM is restored, booting into TWRP does work?
Click to expand...
Click to collapse
Yes providing you did everything correctly I see no reason why it would not work for you unless your device is a extra special Sony XA
Bluesummerz said:
indeed, Linage for F3111 would be glorious, meanwhile, what does WIP stand for (no native speaker here from Germany)
Click to expand...
Click to collapse
It stands for a Work In Progress.
The term work-in-progress (WIP) describes partially finished goods awaiting completion.
Does it has VOLTE support
Great work bro
I am from India using f3116 Dual Sim version
I really wanted VOLTE
does anyone tried it?????
altmash mirza said:
Great work bro
I am from India using f3116 Dual Sim version
I really wanted VOLTE
does anyone tried it?????
Click to expand...
Click to collapse
Not sure about VOLTE
If anyone did try this ROM nobody reported back
I guess this device is dead now as there seems to be very little activity which is a shame
drm fix working in case we use sony backups?
Hi, i just want to give a feedback. I could restore your backup successfully. Every things work fine, no issuses till now. Thank you very much. :good:
Do you plan to make a rom based on oreo or maybe pie it would be great.
z4Android said:
Hi, i just want to give a feedback. I could restore your backup successfully. Every things work fine, no issuses till now. Thank you very much. :good:
Do you plan to make a rom based on oreo or maybe pie it would be great.
Click to expand...
Click to collapse
Thanks for the feed back. :good:
Sorry no Oreo or Pie unless we fix the Ril issue on none Stock custom ROM's like the Lineage 14.1
bootlogo
bigrammy said:
I thought I would share this ROM just in case anyone wants something a little different to the Shipped Stock Sony Firmware
The ROM is based on Sony XA F3111 (Single SIM UK Firmware)
Firmware Version: 33.3.A.1.97
Build Date: Fri Sep 15 04:41:21 CST 2017
It has only been tested on my own UK version Sony XA F3111
There is nothing Fancy about this ROM it's based on pure stock with the mods being restricted to the following.
Converted boot.elf to Boot.img
forceencryption Removed.
dm-verity Removed
I converted all the images in the stock Boot Animation so it is now a much more pleasing black rather than the awful white burning out your eyeballs one.
I remember messing with the logo partition once before and that did not end well so I left it alone. Sadly the logo splashscreen is still the awful white version.
TWRP Recovery fixed to support more partitions (Backing Up and Restore)
Click to expand...
Click to collapse
hello sir @bigrammy,
i want to ask about bootlogo.
i have follow this guide :
1. https://forum.xda-developers.com/android/general/info-how-to-device-partition-info-adb-t3766930 : for get detail of android partition
2. https://forum.xda-developers.com/showthread.php?t=1953726 : For Changing Bootlogo App
3. https://forum.xda-developers.com/oneplus-3t/themes/change-oem-splash-screen-t3516818 : for flash and dump logo partition
i have done with editing bootlogo, but i cant flash logo.img to logo partition.
twrp : black screen - no boot
fastboot : not allowed
can you guide me to doing this?
Hello, I got this phone from my grandfather and I would like to give it to my little sister, the system being really bloat I want to put a custom rom on the phone to have more space and battery life, so I found yours which loook very nice, can you just tell me if that this rom is 100% compatible with a European Xperia XA F3111 ? Also, is the rom easy to use ? for an 11 years old girl ?
Thanks a lot, great job !!
Codetrr said:
hello sir @bigrammy,
i want to ask about bootlogo.
i have follow this guide :
1. https://forum.xda-developers.com/android/general/info-how-to-device-partition-info-adb-t3766930 : for get detail of android partition
2. https://forum.xda-developers.com/showthread.php?t=1953726 : For Changing Bootlogo App
3. https://forum.xda-developers.com/oneplus-3t/themes/change-oem-splash-screen-t3516818 : for flash and dump logo partition
i have done with editing bootlogo, but i cant flash logo.img to logo partition.
twrp : black screen - no boot
fastboot : not allowed
can you guide me to doing this?
Click to expand...
Click to collapse
If your TWRP is not working you should fix this FIRST before doing anything else.
Warning: The logo partition is very important and as I said before it's part of the secure boot chain so if the logo does match the signature and or hash the ROM will boot loop or soft brick it did for me when I tried to change it so be very careful and make sure you can recover the phone with FlashTool.
To find partitions on Mediatek devices use this cmd.
Code:
ls -l /dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name
This will give you a list of all partitions by-name and the actual dev block.
The logo partition is
Code:
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo
So to flash the logo.img with dd you would copy the logo.img to your internal sdcard and use the following cmd.
Code:
dd if=/sdcard/logo.img of=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo
Sorry I cannot test your logo's because my wife use's this phone now as her everyday phone so she would not let me mess around with it now.
Akinimaginable said:
Hello, I got this phone from my grandfather and I would like to give it to my little sister, the system being really bloat I want to put a custom rom on the phone to have more space and battery life, so I found yours which loook very nice, can you just tell me if that this rom is 100% compatible with a European Xperia XA F3111 ? Also, is the rom easy to use ? for an 11 years old girl ?
Thanks a lot, great job !!
Click to expand...
Click to collapse
The ROM is just stock ROM with most bloat ware removed and Google alternatives installed. I would recommend not to use the Sony "Album" app as it requires some other Sony apps which I removed and it continually looks for these apps. So just disable it in /settings/apps and use the pre-installed Google photos instead.
Also ensure you manually set the Phone app as the default dialer even though it's the only one or you will not be able to make or answer calls.
11 year girl! I would not worry they probably know more than we do at that age :laugh:
Yes it should be 100% compatible with a European Xperia XA F3111 ?
How to do this ?
I just rooted and flashed my old LG, and probably the by the "good" method. So if you have a link for the way to root and flash this phone, you'll make me very happy. I know that I have to go in adb flash TWRP as recovery, go in recovery by resetting the phone. Once this is done I have to wipe the phone, put the rom (and opengaps ?). And finally flash the rom. But previously I saw a lot of commands and warning so I'm a bit confused ?
Thanks for your attention ??
{
"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"
}
In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510], here's a build of LineageOS 18.1 I just created based on the latest OEM stock firmware and @AndyYan's latest LineageOS 18.1 GSI. It's very much a work in progress, but it should hopefully help blaze the trail for even more custom ROMs for this tablet.
Notes:
The current process requires 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 latest Android 11 release (T510XXU5CVG2).
Stock recovery will be replaced with my latest TWRP build for the SM-T510.
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:
lineage-18.1-20220907-UNOFFICIAL-T510XXU5CVG2.tar.md5 (Odin tarball)
lineage-18.1-20220907-UNOFFICIAL-T510XXU5CVG2.zip (TWRP update)
Build archives:
Android File Host
Change Log:
20220907:
Based on the latest build of LineageOS 18.1 GSI (20220715) with July 2022 Security Patch.
Updated to the latest Android 11 OEM kernel and vendor partition (T510XXU5CVG2).
Update to TWRP v3.6.2 custom recovery on AOSP 11.
20220417:
Based on the latest build of LineageOS 18.1 GSI (20220414) with April 2022 Security Patch.
Updated to the latest Android 11 OEM kernel and vendor partition (T510XXU5CVB1).
Update to TWRP v3.6.1 custom recovery on AOSP 11.
Replaced default wallpaper with custom one inspired by my Nexus ROMs.
Boots normally for offline (cold) charging.
20210526:
Based on the latest build of LineageOS 17.1 GSI (20210512) with May 2021 Security Patch.
Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU4BUA1).
20201121:
Based on the latest build of LineageOS 17.1 GSI (20201114) with November 2020 Security Patch.
Updated to the new Android 10 OEM kernel and vendor partition (T510XXU3BTH4).
20200812:
Based on the latest build of LineageOS 17.1 GSI (20200808) with August 2020 Security Patch.
Updated to the latest Android 10 OEM kernel and vendor partition (T510XXU3BTFN).
20200713:
Based on the latest build of LineageOS 17.1 GSI (20200713) with July 2020 Security Patch.
Updated to the OEM May 2020 Security Update (T510XXS3ATE3) kernel and vendor partition.
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.
20200321:
Switched to latest stable version of ext2simg command for sparse image conversion.
20200314:
Now based on the latest build of LineageOS 17.1 GSI (20200309).
Fixed potential image corruption issue from outdated img2simg command.
20200308:
Charging after full shutdown will no longer hang during level-of-charge animation.
20200301:
Initial release based on lineage-17.1-20200227-UNOFFICIAL-treble_a64_bvN
MTP file transfers no longer require USB Debugging to be enabled.
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
If TWRP launches, factory reset with Wipe->Format Data and reboot to system. (Not necessary for incremental upgrades.)
From existing TWRP install:
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install, Install Image, select your update (.img file), and then swipe to install
Factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Reboot to system
Source:
android_device_samsung_gta3xlwifi
treble_build_los
Phh-Treble
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @AndyYan and @phhusson for Treble GSIs, so please show them some love here and here!
Does the ethernet-function (LAN) work?
When I try to installing gapps in twrp, twrp crashes and reboots. Using open gapps arm pico. Is there a way to install google apps on this rom?
andreasoz said:
When I try to installing gapps in twrp, twrp crashes and reboots. Using open gapps arm pico. Is there a way to install google apps on this rom?
Click to expand...
Click to collapse
Yes, I've noticed that myself, and it seems to occur when writing to certain modified vendor partitions. Anyone have an idea of what might cause that?
Magendanz said:
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, factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Reboot to system
Click to expand...
Click to collapse
Hiya
Just got this device today.. pretty stoked to get it rooted & Lineage going.. thanks for your projects & info
I'm curious do I need to change any of the Options tab in Odin ?
Auto Reboot off for example ?
Auto Reboot & F. Reset Time are checked by default none of the others are.
At this point in this device's progress assuming I unlocked correctly & get into Download mode.. flash with Odin successfully I should just Auto Reboot right into TWRP & can go from there ?
NoKnox is a thing of the past ?
What about Multi-disabler ?
If I install Magisk & plan to how do I ensure I don't "boot outside Magisk" I keep hearing people say.. where Vaultkeeper & similar things may become problematic or so I've read.
Someone did offer some advice on not booting outside Magisk a few weeks ago I'm going to go find their message too but yeah I've read a lot of threads here & it seems like since certain packages & older methods like patching TWRP with Magisk are things of the past.. I just want to confirm what all else is
is charging past 80% an issue at all with this ROM ?
That's one thing I see people mention about custom kernels is they fix that.. well that & EX or Franco would be rad if they exist for this device & rom
/salute
jaladhjin said:
I'm curious do I need to change any of the Options tab in Odin ? Auto Reboot off for example ?
Click to expand...
Click to collapse
Nope.
jaladhjin said:
NoKnox is a thing of the past ?
Click to expand...
Click to collapse
Yep.
jaladhjin said:
What about Multi-disabler ?
Click to expand...
Click to collapse
You still need to run Multi-disabler if you're installing TWRP, but it's baked into this custom ROM.
jaladhjin said:
is charging past 80% an issue at all with this ROM ?
Click to expand...
Click to collapse
No longer an issue with this custom kernel.
jaladhjin said:
If I install Magisk...
Click to expand...
Click to collapse
I don't use Magisk, and so I'm really not the person to ask. Note, however, that custom kernels in boot and recovery partitions are slightly different wrt MTP. Boot kernel uses Google MTP and recovery one uses Samsung MTP to maintain compatibility with OEM system if patched with Magisk.
Thanks for sharing this and great job! Got it up and running smoothly with gapps and magisk pretty easily.
Haven't noticed any major issues other than that my SD card can't be read. It keeps showing the notification "Issue with SD Card - Tap to fix". I'm able to format the card successfully but the error returns the sd card isn't readable. Tried it with two different brands and getting the same issue.
andreasoz said:
When I try to installing gapps in twrp, twrp crashes and reboots. Using open gapps arm pico. Is there a way to install google apps on this rom?
Click to expand...
Click to collapse
OpenGapps won't work. I tried and a few and managed to get it working with BiTGApps for Android 10. You can get it here:
https://sourceforge.net/projects/opengapps/files/
https://www.cyanogenmods.org/downloads/bitgapps-for-android-10-download/
I successfully installed lineage, but then I had to go back to stock. now when I try to install it again, I am only getting a error; "only official released binaries are allowed to be flashed(BOOT)"
I cannot get back into lineage any advice?
I used odin and flased the BL AP and CSC nothing is changing, wont even let me install twrp any more
Warrenchild said:
I successfully installed lineage, but then I had to go back to stock. now when I try to install it again, I am only getting a error; "only official released binaries are allowed to be flashed(BOOT)"
I cannot get back into lineage any advice?
I used odin and flased the BL AP and CSC nothing is changing, wont even let me install twrp any more
Click to expand...
Click to collapse
Did you re-enable Developer mode and OEM?
lewmur said:
Did you re-enable Developer mode and OEM?
Click to expand...
Click to collapse
it was never locked again to being with. the option was greyed out saying it was already unlocked. but I did relock it then unlock it. no avail. is there a timer or something with these tablets if you mess up?
I even downgraded to sk1 and then let it do a OTA update while locked
Warrenchild said:
it was never locked again to being with. the option was greyed out saying it was already unlocked. but I did relock it then unlock it. no avail. is there a timer or something with these tablets if you mess up?
I even downgraded to sk1 and then let it do a OTA update while locked
Click to expand...
Click to collapse
I'm confused by your terminology. The bootloader is locked or unlocked. Developer mode and OEM are enabled or disabled. I'm assuming you are referering to OEM but I'm not certain. Normally when coming from stock, you enable Developer and OEM and then unlock the bootloader. That will also cause a "factory reset". You then need to reboot and once again enable Developer mode. OEM will normally still be enabled and grayed out. Then you can start the Odin flashing. Also, you shouldn't let it do the OTA because the TWRP needs to match SK1.
edit: The original instruction are a little confusing. They tell you that after each step you have to boot and enable Dev mode in order to chech OEM enable. The real reason is that you have to enable Dev mode in order to flash anything but stock. Without it enabled, you get the message in red saying that only original firmware can be installed.
lewmur said:
I'm confused by your terminology. The bootloader is locked or unlocked. Developer mode and OEM are enabled or disabled. I'm assuming you are referering to OEM but I'm not certain. Normally when coming from stock, you enable Developer and OEM and then unlock the bootloader. That will also cause a "factory reset". You then need to reboot and once again enable Developer mode. OEM will normally still be enabled and grayed out. Then you can start the Odin flashing. Also, you shouldn't let it do the OTA because the TWRP needs to match SK1.
Click to expand...
Click to collapse
I already successfully installed lineage. I was doing it for a business who needs to have the tablet rooted, but the program they needed was finiky with the custom rom, so I tried to go back to factory.
Where I think I messed up is I flashed all the BL, AP, and CSC, from the stock firmware. how ever I wanted to throw lineage on to test and now when I try to flash lineage again it gives me an error on the tablet.
Error : "only official released binaries are allowed to be flashed(BOOT)"
and the flash stalls out on odin.
So i checked to see if it was boot unlocked still it was. so I reverted to sk1 (my tablet was bought from the store yesterday with sk5) and I let the tablet OTA update, and tried the process again to no avail.
Warrenchild said:
I already successfully installed lineage. I was doing it for a business who needs to have the tablet rooted, but the program they needed was finiky with the custom rom, so I tried to go back to factory.
Where I think I messed up is I flashed all the BL, AP, and CSC, from the stock firmware. how ever I wanted to throw lineage on to test and now when I try to flash lineage again it gives me an error on the tablet.
Error : "only official released binaries are allowed to be flashed(BOOT)"
and the flash stalls out on odin.
So i checked to see if it was boot unlocked still it was. so I reverted to sk1 (my tablet was bought from the store yesterday with sk5) and I let the tablet OTA update, and tried the process again to no avail.
Click to expand...
Click to collapse
Did you read my "edit" where I said that was caused by not having enable Developer mode?
lewmur said:
Did you read my "edit" where I said that was caused by not having enable Developer mode?
Click to expand...
Click to collapse
I did not see your edit, thank you I will try and inform the community.
installing
BiTGApps-arm-10.0.0-R1_signed
BiTGApps-arm-10.0.0-v0.2_signed
open_gapps-arm-10.0-pico-20200219
open_gapps-arm-10.0-nano-20200305
with twrp will force reboot while installing
what maybe not work is miracast/widi. i can't find my tv with my tab.
phh-treble entry in settings does nothing / does not open.
(both last points also not work with your [ROM][10.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510])
[email protected] said:
installing
BiTGApps-arm-10.0.0-R1_signed
BiTGApps-arm-10.0.0-v0.2_signed
open_gapps-arm-10.0-pico-20200219
open_gapps-arm-10.0-nano-20200305
with twrp will force reboot while installing
what maybe not work is miracast/widi. i can't find my tv with my tab.
phh-treble entry in settings does nothing / does not open.
(both last points also not work with your [ROM][10.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510])
Click to expand...
Click to collapse
Miracast is no longer supported in Android 9 or 10. It isn't just this ROM. Chromecast is still supported but not miracast.
lewmur said:
Miracast is no longer supported in Android 9 or 10. It isn't just this ROM. Chromecast is still supported but not miracast.
Click to expand...
Click to collapse
my mi a1 with stock pie and the t510 stock rom still can use it
[email protected] said:
my mi a1 with stock pie and the t510 stock rom still can use it
Click to expand...
Click to collapse
Maybe so. But it isn't officialy supported, so if it doesn't work, it doesn't work. I tried it with several apps on several ROMs and could only get it work on my T580 by reverting to an Android 8. Every thing I tried in Pie either froze or caused the tablet to reboot.
Warrenchild said:
it was never locked again to being with. the option was greyed out saying it was already unlocked. but I did relock it then unlock it. no avail. is there a timer or something with these tablets if you mess up?
Click to expand...
Click to collapse
You triggered Samsung's VaultKeeper "feature" when you rolled back to the OEM firmware. In order to prevent that, you need to immediately enable Developer Options while connected to the Internet after setup (before rebooting). If you don't, VaultKeeper places the device in a hybrid state where it looks like the bootloader is still unlocked, but it still won't allow Odin to flash firmware unless it's signed with Samsung's release keys.
Flashing a known-good OEM firmware should remedy the problem, provided you verify that the OEM Unlocking setting is enabled in Developer Options and go back for a Volume Up long press from the blue warning screen to complete the bootloader unlock. Did you do that after booting while holding the Volume Up & Down with the USB cable attached?
betacrypt said:
Thanks for sharing this and great job! Got it up and running smoothly with gapps and magisk pretty easily.
Haven't noticed any major issues other than that my SD card can't be read. It keeps showing the notification "Issue with SD Card - Tap to fix". I'm able to format the card successfully but the error returns the sd card isn't readable. Tried it with two different brands and getting the same issue.
OpenGapps won't work. I tried and a few and managed to get it working with BiTGApps for Android 10. You can get it here:
https://sourceforge.net/projects/opengapps/files/
https://www.cyanogenmods.org/downloads/bitgapps-for-android-10-download/
Click to expand...
Click to collapse
No luck for me with this, TWRP still reboots when trying to install gapps/bitgapps . I'm not sure what else to try.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
/*
* 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.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 10 (Q), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's not working:
Moto Fingerprint Gestures
You tell me
Instructions:
Download the ROM
Backup each and every partition from TWRP Recovery(optional)
Make a full wipe (system, vendor, data, cache, dalvik)
Flash LineageOS Package
Flash gapps
And at last Reboot!
[First boot will take few minutes]
Clean Flash is always recommended!
Downloads:
ROM
GAPPS
XDAevDB Information
LineageOS 17.1 for Ali, ROM for the Moto G6
Contributors
@BetoxxDios
@Electimon
@abhishek_d9
@jeangraff30
ROM OS version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: Unlocked bootloader, Custom recovery
Based On: AOSP
Version information
Status: Stable
Current Stable Version: LineageOS
Stable Release Date: 2020-10-06
Created 2020-10-06
Last Updated 2020-10-06
Hi,
Thanks, I was waiting for this. I will test it on the weekend. Can you please move the thread to "Moto G6 ROMs, Kernels, Recoveries, & Other Development" section? It will be easier to find it.
roypen said:
Hi,
Thanks, I was waiting for this. I will test it on the weekend. Can you please move the thread to "Moto G6 ROMs, Kernels, Recoveries, & Other Development" section? It will be easier to find it.
Click to expand...
Click to collapse
Hi, I request to Moderators move the thread to that section. I don't have permissions to move it.
tomarc said:
Thanks you ! This is great news for me.
Can you fix the Moto Fingerprint Gestures ? Or maybe the rom has it own alternative ?
Click to expand...
Click to collapse
I'm trying to solve moto gestures but don't get a solution yet, the alternative are the android 10 gestures but they work with the screen, not with fingerprint
tomarc said:
Thanks you ! This is great news for me.
Can you fix the Moto Fingerprint Gestures ? Or maybe the rom has it own alternative ?
Click to expand...
Click to collapse
I'm trying to solve moto gestures but don't get a solution yet, the alternative are the android 10 gestures but they work with the screen, not with fingerprint
Thank you
Thank you very much for building and posting this ROM. I would very much like to try it on my G6 (XT1925-5).
Following this thread, I got as far as unlocking the bootloader and booting TWRP from fastboot. But could not flash anything because of a locked boot.img. I have requested an edited boot.img and hope to get a reply.
Is there perhaps another way to get my G6 (XT1925-5) with firmware version PPSS29.55-37-7-10 to be able to run LineageOS?
Thanks in advance,
FWieP
fwiep said:
Thank you very much for building and posting this ROM. I would very much like to try it on my G6 (XT1925-5).
Following this thread, I got as far as unlocking the bootloader and booting TWRP from fastboot. But could not flash anything because of a locked boot.img. I have requested an edited boot.img and hope to get a reply.
Is there perhaps another way to get my G6 (XT1925-5) with firmware version PPSS29.55-37-7-10 to be able to run LineageOS?
Thanks in advance,
FWieP
Click to expand...
Click to collapse
Hi, which twrp did you try? You might want to use the twrp64 as this LOS17.1-build is a 64 Bit
nightmw said:
Hi, which twrp did you try? You might want to use the twrp64 as this LOS17.1-build is a 64 Bit
Click to expand...
Click to collapse
Thanks for the reply. I used twrp-3.4.0-0-ali, downloaded from the official download page.
Is there a special download page for 64bit TWRP?
Kind regards,
FWieP
tomarc said:
You can find it here : https://forum.xda-developers.com/moto-g6/development/twrp-twrp-64-bit-ali-t4093879
Click to expand...
Click to collapse
Once again: thank you all. I downloaded the mali.img and booted TWRP from it.
Then, I flashed the new LineageOS 17.1 and OpenGapps - without any problems, warnings or errors.
If there is no way to flash TWRP into the recovery partition permanently, I can live with that.
Most important thing is, I can flash the system partition when needed.
Hope to see more of your work!
Kind regards,
FWieP
BetoxxDios said:
What's not working:
Moto Fingerprint Gestures
You tell me
Contributors
@BetoxxDios
@Electimon
@abhishek_d9
@jeangraff30
Click to expand...
Click to collapse
Having flashed this ROM a few days ago, I find it nearly perfect. Nearly
the October 2020 security patches are available from LineageOS; can they be included?
Would it be possible for you to share your kernel (link to source) and roomservice.xml?
I would like to try and build the ROM myself. Perhaps contribute, at least providing a mirror for the ROM files?
If not you (@BetoxxDios), perhaps the other contributors (@Electimon, @abhishek_d9, @jeangraff30) ?
Thanks!
Kind regards,
FWieP
failed to load kernel!
On my XT1925-5 I have flashed this rom serveral times, no errors, but it fails to boot.
When I restore the backup, I'm on stock again...
After installing twrp (mali.img) I did format data, reboot onto twrp, wipe, install etc.
Still it will boot only to fastboot: failed to load kernel!
Any suggestions?
Close, but no cigar - yet
fwiep said:
Would it be possible for you to share your kernel (link to source) and roomservice.xml?
I would like to try and build the ROM myself.
Click to expand...
Click to collapse
Thanks @BetoxxDios for providing the links to kernel, device and vendor trees in a private message.
After expanding the RAM of my machine to 16GB and some very educational experiments, the build finally succeeded.
TWRP flashed the ROM without any errors. Yeah!
Then the first reboot. I know that this usually takes a long time - say, 5 minutes. I've left it booting for more than 4 hours, but it doesn't get past the bootanimation.
Can anyone help me in solving this piece of the puzzle? Are there any logs I can get at while the phone is not yet adb-ready? What does LineageOS do while booting for the first time?
Thanks and kind regards,
FWieP
P.S. For the moment, I've flashed @BetoxxDios' original ROM. It's better (and safer) than Motorola's stock firmware.
fwiep said:
.
Then the first reboot. I know that this usually takes a long time - say, 5 minutes. I've left it booting for more than 4 hours, but it doesn't get past the bootanimation.
Can anyone help me in solving this piece of the puzzle? Are there any logs I can get at while the phone is not yet adb-ready? What does LineageOS do while booting for the first time?
Thanks and kind regards,
FWieP
A frozen boot screen like that has happened to me many times. Usually 1 of 2 issues. 1. Gapps problem 2. Magisk problem.
Cheers.
Click to expand...
Click to collapse
Baronstragen said:
A frozen boot screen like that has happened to me many times. Usually 1 of 2 issues. 1. Gapps problem 2. Magisk problem.
Click to expand...
Click to collapse
Thanks for the tip.
I'm afraid this is another issue - I haven't flashed any Gapps with my ROM (yet), and have never even used Magisk before.
@BetoxxDios has shown me a way to get logfiles during boot: build an -eng variant instead of -user or -userdebug.
Now, we're investigating what's going wrong. To be continued!
Kind regards,
FWieP
tomarc said:
Yes, you can flash it permanently :
Fastboot flash recovery xxx.img ; xxx.img being the name of the recovery file.
Click to expand...
Click to collapse
Up until today, I thought this wouldn't work. When doing so, fastboot would say:
Code:
writing 'recovery'...
(bootloader) Image not signed or corrupt
And thus, I thought it had not flashed at all.
Today, I read elsewhere on this forum, to simply ignore this message and check whether it flashed. It actually has!
So, thank you, once again
Kind regards,
FWieP
---------- Post added at 17:22 ---------- Previous post was at 17:08 ----------
fwiep said:
Now, we're investigating what's going wrong. To be continued!
Click to expand...
Click to collapse
And continue it does.
Right from the start, while building this ROM, I got an error about an undefined shared library: libqsap_sdk in /device/motorola/ali/libshims/Android.mk.
I saw it was in a section marked "optional", so I commented it out. And the build succeeded. Yes! After flashing, I got the looping boot-animation. D'oh!
But then, while trying to build another ROM (Resurrection Remix OS 8.6.3 by @abhishek_d9), I got the same error.
I again commented the section out, built the ROM successfully, but got the same looping boot-animation after flashing.
So, XDA to the rescue: I found this post which explains to include '/system/qcom' from LineageOS to get that libqsap_sdk included. I've added it to my roomservice.xml and have started another build. It looks very promising.
Maybe case solved? I'll let you know.
Update
Close, but no cigar. The looping boot-animation still persists. I'll investigate further...
Kind regards,
FWieP
whats-in-a-name said:
On my XT1925-5 I have flashed this rom serveral times, no errors, but it fails to boot.
When I restore the backup, I'm on stock again...
After installing twrp (mali.img) I did format data, reboot onto twrp, wipe, install etc.
Still it will boot only to fastboot: failed to load kernel!
Any suggestions?
Click to expand...
Click to collapse
I bought a new phone, also XT1925-5 and unlocked. But also here, I get the same error:
failed to load kernel!
Stock Android was 8.0 and this rom is 10. could that be a problem?
Solved 'kernel not found'
whats-in-a-name said:
I bought a new phone, also XT1925-5 and unlocked. But also here, I get the same error:
failed to load kernel!
Stock Android was 8.0 and this rom is 10. could that be a problem?
Click to expand...
Click to collapse
I used Motorola Rescue and Smart Assistant Tool
First of all I restored the phone by using the rescue_and_smart_assistant and installed Android 9
Then I used: fastboot boot mali.img
In TWRP, I removed encryption by installing: Force_Encryption_Disabler_For_ALI_Oreo_v2.zip
Wipe, the standard wipe (factory reset) + Format data
Then reboot to bootloader, and again load TWRP: fastboot boot mali.img
Wipe again and install the system (lineage-17.1-20201001-UNOFFICIAL-ali.zip)
install Magisk
Wipe cache and Dalvik
reboot into system
whats-in-a-name said:
Solved 'kernel not found'
I used Motorola Rescue and Smart Assistant Tool
First of all I restored the phone by using the rescue_and_smart_assistant and installed Android 9
Then I used: fastboot boot mali.img
In TWRP, I removed encryption by installing: Force_Encryption_Disabler_For_ALI_Oreo_v2.zip
Wipe, the standard wipe (factory reset) + Format data
Then reboot to bootloader, and again load TWRP: fastboot boot mali.img
Wipe again and install the system (lineage-17.1-20201001-UNOFFICIAL-ali.zip)
install Magisk
Wipe cache and Dalvik
reboot into system
Click to expand...
Click to collapse
I tried all of that and keep getting "updater process ended with ERROR: 255 Error installing zip file...." Any way to fix this issue? I'm on XT1925-6 32gb.
Never mind, I had the wrong TWRP installed like a dope.
I installed the ROM following your instructions and other sources:
- unlocked the bootloader
- flashed the unofficial TWRP recovery for the moto g6 ali (https://forum.xda-developers.com/t/twrp-unofficial-twrp-64-bit-for-ali.4093879/)
- wiped system, data, cache and dalvik, my device has no vendor partition though
- flashed your Lineage Rom
- flashed the most recent GAPPS, for Android 10, arm 64, stock
Then rebooting the phone will just end up in an infinite boot animation.
Doing it all over without the gapps and the phone boots just fine. So it seems that the gapps installation is somehow causing the trouble. I tried many different gapps packages, but all without any success.
Could you provide a link to a gapp package that is known to work with your ROM?
Thanks in advance!
I installed the ROM following your instructions and other sources:
- unlocked the bootloader
- flashed the unofficial TWRP recovery for the moto g6 ali (https://forum.xda-developers.com/t/twrp-unofficial-twrp-64-bit-for-ali.4093879/)
- wiped system, data, cache and dalvik, my device has no vendor partition though
- flashed your Lineage Rom
- flashed the most recent GAPPS, for Android 10, arm 64, stock
Then rebooting the phone will just end up in an infinite boot animation.
Doing it all over without the gapps and the phone boots just fine. So it seems that the gapps installation is somehow causing the trouble. I tried many different gapps packages, but all without any success.
Could you provide a link to a gapp package that is known to work with your ROM?
Thanks in advance!
OFFICIAL LINEAGE OS 17.1 NIGHTLIES
LineageOS Downloads
download.lineageos.org
The most recent build was dated 25th Feb 2021. [Edit UPDATED to most recent build date].
The previous offerings were 2021-01-28; 2021-02-04 ; 2021-02-11; 2021-02-18.
{
"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"
}
CEDRIC WIKI
Info about cedric | LineageOS Wiki
wiki.lineageos.org
Hi, I tried to install it on OPP28.85-19-4-2 but the installation failed (infinite loop at start-up). According to this https://wiki.lineageos.org/devices/cedric/install the latest Android 8.1 firmware is required. Which one is it ? Thanks !
QRXpMUvS said:
Hi, I tried to install it on OPP28.85-19-4-2 but the installation failed (infinite loop at start-up). According to this https://wiki.lineageos.org/devices/cedric/install the latest Android 8.1 firmware is required. Which one is it ? Thanks !
Click to expand...
Click to collapse
Any oero firmware will do as your base
Flash via fastboot - if you don't know which to choose use the latest retail version
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
How to flash rom
Go to twrp
Select wipe
Format data - option on the right (will format everything on phone including personal files so backup first!)
Restart to twrp
Wipe then advanced wipe
Wipe system data and cache
Select install from main menu
Install rom zip
Install gapps (you want arm64 android 10 nano)
Install magisk (optional for root access & to hide apps from detecting root/custom rom)
Wipe delvik cache
Restart
Encrypt phone again if required once booted from phone settings menu
Thanks, I did as you explained, but I am still stuck with a lineageos logo looping for a few dozens of minuts before the phone restarts and goes straight to TWRP.
QRXpMUvS said:
Thanks, I did as you explained, but I am still stuck with a lineageos logo looping for a few dozens of minuts before the phone restarts and goes straight to TWRP.
Click to expand...
Click to collapse
Wipe system data cache and flash rom without gapps or magisk
Does it boot?
If yes wipe everything again and flash rom zip but flash gapps as well this time. And if it boots flash magisk (no need to wipe to flash magisk)
If magisk causes it to boot loop flash an older version
If none of the above works and you have the same issue trying to flash another rom eg lineage mint then its user error somewhere or an issue unrelated to the rom zip
Hi,
i updated my G5 to the official LOS. Although VoWifi and VoLTE are enabled in settings, none of them are working (They didn't work on the unofficial version either).
According to my network operator, these functions are activated.
Unter Phone Info (*#*#4636#*#* in dialer's app) it says "IMS Registration: Not Registered"
Is there anything I can do about this?
Thanks!
TheFixItMan said:
Wipe system data cache and flash rom without gapps or magisk
Does it boot?
If yes wipe everything again and flash rom zip but flash gapps as well this time. And if it boots flash magisk (no need to wipe to flash magisk)
If magisk causes it to boot loop flash an older version
If none of the above works and you have the same issue trying to flash another rom eg lineage mint then its user error somewhere or an issue unrelated to the rom zip
Click to expand...
Click to collapse
I tried without gapps and magisk, it does not boot, same with Mint.
So if I understand well, the problem is probably on my side
What I did :
New firmware using fastboot following these commands.
At this stage, TWRP had disappear (!), I reinstalled it using fastboot. Is it normal ?
Then I installed lineageos.
QRXpMUvS said:
I tried without gapps and magisk, it does not boot, same with Mint.
So if I understand well, the problem is probably on my side
What I did :
New firmware using fastboot following these commands.
At this stage, TWRP had disappear (!), I reinstalled it using fastboot. Is it normal ?
Then I installed lineageos.
Click to expand...
Click to collapse
I have the same problem. I can't get Lineage or Mint to boot on my Cedric.
I've tried TWRP 3.4 , and 3.5 and neither made a difference. I have been through the instructions on the lineage site many times, and I'm sure I'm not missing a step
But every time the device sticks at lineage boot logo for a long time, before returning to fastboot mode.
If I re-flash 8.1 using fastboot, the phone works again, then go from the top with twrp and lineage, and we're back to logo and eventually fastboot again.
So, although I cannot help yet, you are not alone.
Edit:
My cedric is the 3GB RAM XT1676 model which I think might be somewhat rare version?
HarpingOn said:
So, although I cannot help yet, you are not alone.
Click to expand...
Click to collapse
Thanks ! By chance, do you know any unofficial rom (not necessarely 17.1) correctly booting on 8.1 ?
QRXpMUvS said:
Thanks ! By chance, do you know any unofficial rom (not necessarely 17.1) correctly booting on 8.1 ?
Click to expand...
Click to collapse
I have only tried mint and official 17.1. Get the same problem with both sadly.
I just realised, on the installation instructions it says to flash the recovery from the lineage download page, not twrp
So I tried:
motog5> fastboot flash recovery lineage-17.1-20210225-recovery-cedric.img
target reported max download size of 535822336 bytes
Sending 'recovery' (18390 KB)...
OKAY [ 0.586s]
Writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
The cedric recovery image on the download page is about 2MB larger than the TWRP recovery.
So should I be using the lineage provided recovery to flash this?
edit:
I managed to get the cedric to boot the lineage supplied recovery by doing:
motog5> fastboot boot lineage-17.1-20210225-recovery-cedric.img
I then used that recovery (looks good by the way, smart looking recovery), but after flashing the matching lineage-17.1 image ( adb sideload lineage-17.1-20210225-nightly-cedric-signed.zip) , I still get the long running boot animation, and dumped back into bootloader after a while.
I think I should stop now, I'm getting tired
For your info everyone: the OP is not the developer. I am neither. I just patch the official builds and that is Mint.
HarpingOn said:
I just realised, on the installation instructions it says to flash the recovery from the lineage download page, not twrp
So I tried:
motog5> fastboot flash recovery lineage-17.1-20210225-recovery-cedric.img
target reported max download size of 535822336 bytes
Sending 'recovery' (18390 KB)...
OKAY [ 0.586s]
Writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
The cedric recovery image on the download page is about 2MB larger than the TWRP recovery.
So should I be using the lineage provided recovery to flash this?
edit:
I managed to get the cedric to boot the lineage supplied recovery by doing:
motog5> fastboot boot lineage-17.1-20210225-recovery-cedric.img
I then used that recovery (looks good by the way, smart looking recovery), but after flashing the matching lineage-17.1 image ( adb sideload lineage-17.1-20210225-nightly-cedric-signed.zip) , I still get the long running boot animation, and dumped back into bootloader after a while.
I think I should stop now, I'm getting tired
Click to expand...
Click to collapse
If you could give me logs, I'll check.
nift4 said:
If you could give me logs, I'll check.
Click to expand...
Click to collapse
My problem was that I was starting from the GB release of Cedric stock 8.1 as I'm in the UK. If I flashed the GB version, then no Lineage ROM would boot. Not this, and not the Mint one.
If you check out the Mint thread, what I did was use Fastboot to flash an international version of stock 8.1, then I could add TWRP and flash this successfully.
I ended up testing Lineage With microG, but actually successfully flashed this, and Mint as well.
So I'd say to anyone struggling to get a working flash of this ROM, try a different CEDRIC set of fastboot files.
as im aware, you need to flash from stock 8.1 but sometimes if youre on pie you gotta flash nougat and then oreo to flash custom roms i tried flashing that rom before but got no succes with bootlop but i didnt knew this i have tried unnoficial los 17 but never though about trying again the one from los page, guess its Worth a try
update: i got to flash and boot but the system reboots randomly, mostly when i open apps
also twitter doesnt login into my account for a weird reason dunno why. guess ill loke other roms around
Lighto97 said:
update: i got to flash and boot but the system reboots randomly, mostly when i open apps
also twitter doesnt login into my account for a weird reason dunno why. guess ill loke other roms around
Click to expand...
Click to collapse
You need to been on oreo firmware to flash this rom - preferably the latest retail version
You also need gapps that are arm64 android 10 nano
See my instructions above for how to flash rom correctly (post #3)
Without any logs the devs will put it down to user error
TheFixItMan said:
You need to been on oreo firmware to flash this rom - preferably the latest retail version
You also need gapps that are arm64 android 10 nano
See my instructions above for how to flash rom correctly (post #3)
Without any logs the devs will put it down to user error
Click to expand...
Click to collapse
oh damm i always forgot i have to send the log for them to track the issue, i already uninstaled anyway.
i did followed the steps the right way (thank you), right now im flashing stock nougat to try out LOS 14.1 (which i love and seems to be reeealy stable)
thank you very much to all involved for this … this gives a new lease of life to the moto g5. i tried both the official version and a microg4lineageos build - both work flawlessly afaict.
a few observations:
camera works, both photos and videos. the new camera app is quite usable.
coming from a build derived from codezeros 16.0-tree, i had to revert to the stock firmware to be able to install this. not doing so resulted in boot loops, wiping everything did not help
the los recovery cannot be flashed, it seems to be too big for the recovery partition. twrp works fine.
tfbb said:
thank you very much to all involved for this … this gives a new lease of life to the moto g5. i tried both the official version and a microg4lineageos build - both work flawlessly afaict.
a few observations:
camera works, both photos and videos. the new camera app is quite usable.
coming from a build derived from codezeros 16.0-tree, i had to revert to the stock firmware to be able to install this. not doing so resulted in boot loops, wiping everything did not help
the los recovery cannot be flashed, it seems to be too big for the recovery partition. twrp works fine.
Click to expand...
Click to collapse
i know how to boot with that LOS recovery, instead of flash comand you use boot command so the device will bot into recovery suing the image.
{
"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"
}
In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510], here's a build of LineageOS 19.1 I just created based on the latest OEM stock firmware and @AndyYan's latest LineageOS 19.1 GSI. It's very much a work in progress, but it should hopefully help blaze the trail for even more custom ROMs for this tablet.
Notes:
The current process requires 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 latest Android 11 release (T510XXU5CWA1).
Stock recovery will be replaced with my latest TWRP build for the SM-T510.
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:
lineage-19.1-20230403-UNOFFICIAL-T510XXU5CWA1.tar.md5 (Odin tarball)
lineage-19.1-20230403-UNOFFICIAL-T510XXU5CWA1.zip (TWRP update)
Build archives:
Android File Host
Change Log:
20230403:
Updated to LineageOS 19.1 GSI (20230323) with March 2023 security patch and GApps.
Based on the latest Android 11 OEM kernel and vendor partition (T510XXU5CWA1).
Includes TWRP v3.7.0 custom recovery built on AOSP 11.
20220918:
Initial release based on LineageOS 19.1 GSI (20220912) with Sept. 2022 security patch and GApps.
Based on the latest Android 11 OEM kernel and vendor partition (T510XXU5CVG2).
Includes TWRP v3.6.2 custom recovery built on AOSP 11.
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
If TWRP launches, factory reset with Wipe->Format Data and reboot to system. (Not necessary for incremental upgrades.)
From existing TWRP install:
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install, Install Image, select your update (.img file), and then swipe to install
Factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Reboot to system
Source:
android_device_samsung_gta3xlwifi
treble_build_los
Phh-Treble
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @AndyYan and @phhusson for Treble GSIs, so please show them some love here and here!
Reserved
Thank you dear @Magendanz very much for keeping my Old Youtube Tab Alive!
Quick Question, is an update from "lineage-18.1-20220417-UNOFFICIAL-T510XXU5CVB1.zip" to the new 19.1 Possible or do i have to update the base version first?
Good evening Mr. Magendanz,
i installed this ROM on my Samsung SM-T510 and my tab/back/home buttons are not in the middle/bottom position they are in the right corner (i had this issue also with another unffocial lineage Os 19.1 Rom for SM-T510)
How can i solve this ?
NJey90 said:
Good evening Mr. Magendanz,
i installed this ROM on my Samsung SM-T510 and my tab/back/home buttons are not in the middle/bottom position they are in the right corner (i had this issue also with another unffocial lineage Os 19.1 Rom for SM-T510)
How can i solve this ?
Click to expand...
Click to collapse
Is the task bare active? I have the same layout when it is. You can turn it off in settings, but research the bar, you might want to use it.
@Magendanz , I dirty installed it over my lineageos gsi, and it works great so far. One problem I see, and had with the gsi is that I have a notification to finish installation, but there is no way to get past the network selection. There is no button to either skip or continue. Is there a way to fix this?
Thank you for this - I know how hard it is given your other responsibilities!
Thanks Magendanz for this news!
Coming from LineageOS 17.1 (lineage-17.1-20200812-UNOFFICIAL-T510XXU3BTFN), what would be the sequence of steps for updating to this rom ?
Thanks.
galoneta said:
Coming from LineageOS 17.1 (lineage-17.1-20200812-UNOFFICIAL-T510XXU3BTFN), what would be the sequence of steps for updating to this rom ?
Click to expand...
Click to collapse
I recommend you download and install the T510XXU5CVG2 firmware, do a clean install with Odin...but intercept the restart by holding Vol Up & Down so that you reenter Download mode. Then, install this custom ROM with Odin and intercept the restart by holding Power + Vol Up to enter TWRP. From there, do a factory reset and reboot to system.
If you inadvertently miss the restart intercept and have to run through OEM setup, make sure to connect to the Internet and then enter Developer options to disarm Vaultkeeper. Don't try to flash anything else until you've verified the OEM Unlock is still on (but disabled).
Magendanz said:
I recommend you download and install the T510XXU5CVG2 firmware, do a clean install with Odin...but intercept the restart by holding Vol Up & Down so that you reenter Download mode. Then, install this custom ROM with Odin and intercept the restart by holding Power + Vol Up to enter TWRP. From there, do a factory reset and reboot to system.
If you inadvertently miss the restart intercept and have to run through OEM setup, make sure to connect to the Internet and then enter Developer options to disarm Vaultkeeper. Don't try to flash anything else until you've verified the OEM Unlock is still on (but disabled).
Click to expand...
Click to collapse
Thanks Magendanz for this clarifying tutorial!
So you must first always update \ have the samsung base AND the custom recovery to a MINIMUM combination set? In this case the minimum "combo" set would be a samsung rom with android 11 as base (and recovery 3.6) right ?
Will try this sequence and give feedback as soon as possible.
Thanks again.
Hey there, just wondering -- does hardware video acceleration work on this build seeing as its based on a GSI? Thanks
I tried to flash this on T515 via twrp. Seems like it only detect and allow install on t510
Can you also make a variant for sm-t515?
Cheers and thanks
dissidius said:
Can you also make a variant for sm-t515?
Cheers and thanks
Click to expand...
Click to collapse
In the ten or so years I've been dealing with Samsung tablets and XDA, I must have seen this question asked at least a hundred times. "Can you make the wifi ROM work on the LTE version?" of whatever tablet or vice versa. And the answer is always "No." They are two different animals and normally the dev has one or the other. And it is very difficult to make a ROM for a device you don't have. And the same thing goes for tablets with the S Pen. They are NOT the same.
lewmur said:
In the ten or so years I've been dealing with Samsung tablets and XDA, I must have seen this question asked at least a hundred times. "Can you make the wifi ROM work on the LTE version?" of whatever tablet or vice versa. And the answer is always "No." They are two different animals and normally the dev has one or the other. And it is very difficult to make a ROM for a device you don't have. And the same thing goes for tablets with the S Pen. They are NOT the same.
Click to expand...
Click to collapse
of course mate i like your passion in explaining such things but i belive *i can be wrong of course* that i wasn't asking on a Xiaomi Poco thread..... this two devices are very much similar, smt510 twrp works correcly on smt515 for example. Just maybe the rom could also work with some little tweaks. Thanks
dissidius said:
of course mate i like your passion in explaining such things but i belive *i can be wrong of course* that i wasn't asking on a Xiaomi Poco thread..... this two devices are very much similar, smt510 twrp works correcly on smt515 for example. Just maybe the rom could also work with some little tweaks. Thanks
Click to expand...
Click to collapse
Yes, TWRP can work on both but recovery doesn't access the LTE modem. And, again, I'm stating MY experience from over ten years of having people ask the question about many, many SAMSUNG tablets only.
Has anyone successfully installed MindTheGApps on lineageos19? did you use an sdcard or adb or some other method? I don't have access to an sdcard but I am curious if this is the only way. I have not been successful in using adb..... yet!
This version of Lineage 19 already has Gapps installed. So MindtheGapps is not needed. Installing it using the tar ball and Odin means you don't need an SD card. Or have I missed something?
dissidius said:
Can you also make a variant for sm-t515?
Cheers and thanks
Click to expand...
Click to collapse
I installed this on my T515 via TWRP and it worked just fine. Haven't tried LTE though, but the os installed perfectly.
DingusestDingus said:
I installed this on my T515 via TWRP and it worked just fine. Haven't tried LTE though, but the os installed perfectly.
Click to expand...
Click to collapse
Scratch that, I restarted it and its now in a bootloop
This is the 2019 version. I can't get this to install. Bootloader is unlocked and tablet is rooted