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

[ROM][11.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 11.0, so here's my first effort at migrating the Nexus Stock custom ROM for the 2019 Galaxy Tab A 10.0 [SM-T510] to the latest Android OS release. It's very much a work in progress, but it should hopefully help blaze the trail for even better work.
Notes:
The current process may require you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and are generally based on the latest update for the SM-T510. Note that the bootloader in this release has roll-back prevention.
The system is based on eremitein's CAOS GSI project with the latest Stock variant from OpenGApps.
Boot logo and default wallpaper is from my Nexus series of custom ROMs for Android TV, and I'm using the Pixel boot animation with black background.
Stock recovery will be replaced with my latest TWRP build for the SM-T510.
I've dialed back most of scary bootloader warnings and Knox Security branding from the boot sequence.
The properties now correctly identify the device as a tablet, and so the Google Dialer is no longer installed. I've also disabled the Emergency button, but SetupWizard still insists on reminding you to insert a SIM (sigh!).
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Cold charging (low power mode) animates to about 39% and then reboots.
Downloads:
Nexus_Stock_CR_T510XXU5CUL1-20220219.tar.md5 (Odin tarball)
Nexus_Stock_CR_T510XXU5CUL1-20220219.zip (TWRP update)
Build archives:
Android File Host
Change Log:
20220219:
Vendor partition and custom kernel based on T510XXU5CUL1 OEM firmware (December 2021 Update)
System partition based on CAOS 11.0 v315 (January 2022 Security Update)
Latest Google apps from OpenGApps (20220215) w/ rollback for GoogleTTS
20211125:
Vendor partition and custom kernel based on T510XXU5CUJ1 OEM firmware (October 2021 Update)
Update to TWRP v3.6.0 custom recovery on AOSP 11
Latest Google apps from OpenGApps (20211125) w/ rollback for GoogleTTS
20211120:
System partition based on CAOS 11.0 v313+ (October 2021 Security Update)
Latest Google apps from OpenGApps (20211120) w/ rollback for GoogleTTS
20210825:
Vendor partition and custom kernel based on T510XXU5CUF4 OEM firmware (June 2021 Update)
System partition based on CAOS 11.0 v312 (August 2021 Security Update)
Update to TWRP v3.5.2 custom recovery
Latest Google apps from OpenGApps (20210825-TEST)
20210318:
Fixed custom Pixel Launcher so that icon positions are saved.
Fixed clipped pixels on edge of launcher search bar.
Defaults icon layout to 7 columns for main, hotseat and app drawer, just like it used to be for the Nexus 10. (For 6 column layout bump display scaling to Large.)
20210314:
Vendor partition and custom kernel based on T510XXU4BUA1 OEM firmware (January 2021 Update)
System partition based on CAOS 11.0 v302 (March 2021 Security Update)
Update to TWRP v3.5.1 custom recovery
Latest Google apps from OpenGApps (20210130-TEST)
20210216:
Initial build based on T510XXU3BTK1 kernel (November 2020 Update) and CAOS 11.0 v300m.
Latest Google apps from OpenGApps (20210130-TEST)
Instructions:
From OEM stock firmware:
Unlock bootloader
Ensure matching OEM build (e.g. T510XXU3BTK1) is installed
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
When TWRP launches, factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Reboot to system
From existing TWRP install (for incremental updates):
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install, select your update (.zip file), and then swipe to install
Reboot to system
Source:
android_device_samsung_gta3xlwifi
android_device_samsung_gta3xl
Phh-Treble
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @phhusson for Treble GSIs and @eremitein for CAOS, so please show them some love!

Reserved.

Worked fine for me. Thanks.

I can't get Magisk 21.4 to work on this rom after updating with TWRP. I also tried to patch the boot.img with Magisk Manager.
Has someone else this working? I will temporary return to Android 10.

waterpolo said:
I can't get Magisk 21.4 to work on this rom after updating with TWRP. I also tried to patch the boot.img with Magisk Manager.
Has someone else this working? I will temporary return to Android 10.
Click to expand...
Click to collapse
I haven't been able to root any ROM based on AOSP 11.0...even the S variants that include su , but I'm not really an expert on rooting.

Yep magisk not working for me also, thats a shame because it's quite smooth overall, hoping for it to work in the next updates

For my Samsung mobile device I see on the XDA forum that Magisk is included in the ROM and isn't allowed to updated when a new version is released, only the Magisk manager could be updated.
I am afraid that installing seperate as on Android 10 isn't possible anymore.

waterpolo said:
For my Samsung mobile device I see on the XDA forum that Magisk is included in the ROM and isn't allowed to updated when a new version is released, only the Magisk manager could be updated.
I am afraid that installing seperate as on Android 10 isn't possible anymore.
Click to expand...
Click to collapse
The problem with that is that there is no Magisk Manager in Play Store with this ROM.
edit: Something appears to be going on with Google and Magisk and it is NOT just with this ROM or even this device. Apparently Google has not only removed Magisk Manager from the Play Store but have done something to keep it from giving root privileges all together!!!
re-edit: I apologize. I panicked. The problem appears to be with this device and the latest version of Magisk and with this ROM and Magisk. I can get version 20.4 to work with other ROMs, but it hangs with this one.

- scratched -

If anyone finds a version of Magisk that works with this ROM, please post it. I've tried V20.4, which causes a hang during boot, and V21.4, and 21.2, which boot but don't work.

lewmur said:
If anyone finds a version of Magisk that works with this ROM, please post it. I've tried V20.4, which causes a hang during boot, and V21.4, and 21.2, which boot but don't work.
Click to expand...
Click to collapse
Magisk V20.4 isn't for Android 11+. Therefor you have to install V21, but unfortunately is this not working.

is this ROM good for daily use or better to use the Android 10 one?

Broman400 said:
is this ROM good for daily use or better to use the Android 10 one?
Click to expand...
Click to collapse
1)
maybe there a bug with Wifi and connections with WPA3 (with PMF), only WPA2 is working here.
But this is a weak statement, cause I'm running a Beta FW on my Router (FB 7590) with some wifi bugs in the past. - I mean my Galaxy S4 with LOS 18.1 hadn't that - I'm not sure -
- EDIT-
Release Router FW arrived today: same result.
2)
my arranged apps/icons in the bottom line are resetted to the default google after an reboot.
whereby:
removing some google apps out of the bottom line will survive a reboot, all other arrangements won't.
e.g. I removed nearly all google apps and left only the outer left and right (see the above 1st screenshot) and dropped installed apps in the free place.
turns out: only the google apps (playstore + camera) are there after an reboot.
could someone check that ?
PMF:= Protected Management Frames
IEEE 802.11w-2009 - Wikipedia
en.wikipedia.org

Great work out there. Can you do this rom for SM-t515?
I can't find any lineage or ressurection rom for this tab

ryan.sn0w said:
Great work out there. Can you do this rom for SM-t515?
I can't find any lineage or ressurection rom for this tab
Click to expand...
Click to collapse
Sorry, I don't have a SM-T515 and it doesn't share the same kernel as the SM-T510. I've tried building ROMs blindly before, and you really can't do it without hardware for testing.

hi,
you wrote : "Ensure matching OEM build (e.g. T510XXU3BTK1) is installed"
My actual OEM is T510XXU4BUA1 which is newer than 510XXU3BTK1.
So each time i try to flash , I've got the message SYSTEM REV CHECK FAIL DEVICE : 4 BINARY : 3 (VENDOR).
I understand that i need to downgrade to T510XXU3BTK1. Is it possible to downgrade inside ANDROID 10 from an OEM 4 bits to an OEM 3 bits? How to do this?

Found the solution. Flash with heimdall orange fox recovery + multidisabler + RR custum ROM then full wipe + nexus custom ROM. All is working, good job, nice fast ROM.

@isaacragui
could do me a favor ?
with your fresh installed LOS, please check from comment #13, point 2)
I would like to know if it's only me.

rw_on_xda said:
@isaacragui
could do me a favor ?
with your fresh installed LOS, please check from comment #13, point 2)
I would like to know if it's only me.
Click to expand...
Click to collapse
Sorry i've almost immediatly switched to a AOSP ROM after having flashed LOS. Not because not working, but prefer AOSP.
Will check if return to LOS.

isaacragui said:
Sorry i've almost immediatly switched to a AOSP ROM after having flashed LOS. Not because not working, but prefer AOSP.
Will check if return to LOS.
Click to expand...
Click to collapse
thanks anyway

Related

[ROM][OFFICIAL] LineageOS 14.1 for Nexus 9 (flounder)

Reserved
This post is for Nexus 9 (LTE) model.
Important Info
The newest lineage 14.1 flounder_lte (LTE) builds rely on proprietary vendor and firmware components from the N4F27P (October 2017) monthly update from google. This means your device needs to have the vendor and bootloader img from that update. They can be extracted from the factory image on google's site here. Or you can use the ones linked below that I already extracted:
* vendor-flounder_lte-n4f27p.img
* bootloader-flounder_lte-3.50.0.0143.img
The vendor img is flashable with twrp or fastboot, but for the bootloader img use fastboot.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/flounder_lte
LineageOS servers no longer make 14.1 builds for any devices. You can use my builds here. My older builds are here.
Google apps: http://opengapps.org/?arch=arm64&api=7.1&variant=nano (Use arm64 / 7.1)
su addon zip (for root): Install zip / Removal zip
NOTE#1: After su addon install, root is disabled by default. You can enable it in developer options.
NOTE#2: My unofficial builds do not force encrypt.
Weather Provider Addon (Optional)
For those that like the lineage cLock widget, here's the OpenWeather apk you need to get weather info.
https://mirrorbits.lineageos.org/WeatherProviders/OpenWeatherMapWeatherProvider.apk
Note: You'll need an api key from OpenWeather.
Stats
https://stats.lineageos.org/
Credits
Many thanks to the LineageOS team and all the contributors out there in the community :good:
Contributors
Hashbang173, razorloves
Source Code:
Main device tree: https://www.github.com/LineageOS/android_device_htc_flounder_lte/tree/cm-14.1
Inherited device tree: https://www.github.com/LineageOS/android_device_htc_flounder/tree/cm-14.1
Kernel tree: https://www.github.com/LineageOS/android_kernel_htc_flounder/tree/cm-14.1
Vendor tree: https://github.com/TheMuppets/proprietary_vendor_htc/tree/cm-14.1
Android version: 7.1.2 Nougat
Kernel version: Linux 3.10.103
Status: Nightly

Wooooh! It's here

Can Nexus9 (lte) use this rom? If flash this rom only can not use lte,i can accept it.

Yeah! This is great news!
Will definitely flash this rom on my laggy N9

Can I dirty flash from the unofficial builds or should I do a full wipe?

Will it work on the LTE version? I don't mind if LTE does not work as long as I can try out the ROM without getting boot loops.

hextence said:
Will it work on the LTE version? I don't mind if LTE does not work as long as I can try out the ROM without getting boot loops.
Click to expand...
Click to collapse
I think so!

LTE version?
For people who need LTE

perfec

Is the Nexus 9 LTE going to have official support?
Sent from my iPhone using Tapatalk

Thank you very much! I hope it is less laggy than the stock firmware.

vendor image is critical at time of OS installation
Hi there.
First of all, thanks so much for the official N9 build for Lineage. Really appreciate it.
I wanted to describe my experience this morning. I should start by saying that I am *not* a hacker, just an enthusiastic user. I can follow instructions, and have been using non-stock ROMs since Cyanogen 7.
I was upgrading from the most recent version of Cyanogen. Before I started, I upgraded to the latest TWRP. Then when booting into recovery, found that my decryption passphrase didn't work. I downgraded version by version until twrp-3.0.2-0-flounder.img which is apparently the latest that worked. After installing Lineage OS, I upgraded to the newest TWRP again.
More importantly, I wanted to point out that by following the instructions on the Lineage OS wiki for the Nexus 9, I almost got to the point of thinking I had bricked my device.
The main reason is that the instructions don't mention the Vendor image issue at all: https://wiki.lineageos.org/devices/flounder/install
After wiping, installing Lineage OS and GApps pico, I rebooted. When it got to the decryption passphrase, I got the pop-up warning about the Vendor image being mismatched. No problem, I thought, as I've seen that before on Cyanogen installs. I put in my decryption passphrase. The screen remained unchanged for a couple of minutes, then I got something I'd never seen before. A page notifying me that my passphrase was correct, but the system was corrupt, and an option to fix it (no other option was available except to force power-off). So I took that option and it rebooted into TWRP. It boots into recovery and apparently runs a script and reboots the system again. But the same issue occurred again, nothing was fixed.
No problem, I thought, I'll just power-off, boot into the bootloader, enter recovery, and try again. Except that after installing Lineage, I found that volume-down+power button no longer started the bootloader!!! I tried many times, but the best I got was the device booting into the system and getting the same problem where it said the system is corrupt. It was at this point that I thought I had bricked the device - can't boot into system, can't get to the bootloader, so can't get to the recovery.
After many attempts, I tried one last thing:
Boot into system
On the corruption notification screen, I pressed the button to "fix" the system corruption
when the device rebooted into Recovery to run the script, instead of entering my passphrase, I hit cancel. This cancelled the script process but left me in recovery. I then selected reboot -> bootloader. Success!!
I was then able to connect the device to my laptop and copy the Vendor image I had extracted from the official Google system image using
Code:
fastboot flash vendor vendor.img
I then rebooted, and everything worked fine.
So it seems that in this instance, it may be critical to install the Vendor image before the first reboot. In earlier versions of Cyanogen when I had a vendor image mismatch it never prevented the device from booting and I was able to update it later on.
In which case, whoever has access to the wiki on the Lineage website - could you add those instructions in?

Just to add - I now seem to have bricked the device. Everything was working fine. I rooted the device using the supplied zip. It booted up fine. Now it won't reboot. It gets to the decryption passphrase field - verifies the password, continues to boot, and never finishes.
I can't get into the bootloader. Volume down+power doesn't work. Is there another way to do this?

Was using stock android on my Nexus 9. Already had root with the latest TWRP recovery installed. Did not run into any issues during the install(forgot to flash the Gapp at first, but could do it later in recovery, again no issues)
This is the first time I am using a Custom ROM. Got some questions .
1. I have the default apps for the lineage OS along with the same Gapps, How to remove the default lineage OS apps?
4. If anyone can share the advantages of the Nightly over custom ROM , it'll be great.
Other than these, no other major issues so far. will update the thread with the user experience

For anyone with LTE model please test this build. Let me know if there's any issues with lte or anything.
https://www.androidfilehost.com/?fid=889764386195906667
Here's the N4F27E vendor img for the LTE model, if you need it.
vendor-volantisg-n4f27e.img
thanks
No more testing needed. Results were good. Nightlies started for LTE model.

yhvo2gt9 said:
Just to add - I now seem to have bricked the device. Everything was working fine. I rooted the device using the supplied zip. It booted up fine. Now it won't reboot. It gets to the decryption passphrase field - verifies the password, continues to boot, and never finishes.
I can't get into the bootloader. Volume down+power doesn't work. Is there another way to do this?
Click to expand...
Click to collapse
Decryption passphrase in TWRP? Or Lineage?
---------- Post added at 04:51 PM ---------- Previous post was at 04:49 PM ----------
Just to let you all know, I got Lineage up and running, restored from my gmail account. I had stuck with 6.0.1 stock, 7 never cooperated, it was still getting laggy and what not. I will post more details about the install in a bit, but I just wanted to let any curious parties know this build seems to be working OK

Is the poor volume fixed in the official build or do we still need to flash a custom kernel to fix it?

I just flashed a minute ago. I've been waiting for this to be released. I switched over to Lineage on my OnePlus when it first came out. The nexus has been way too laggy on the latest stock releases. I hope this helps. I received a vendor image mismatch error on boot up but so far no issues. I'm going to flash gapps and will report back later. Thanks for working on this!!

The LTE one appears to be working fine in my tablet. Thank you
Sent from my iPhone using Tapatalk

[ROM][SM-T820][SM-T825][UNOFFICIAL] CrDroid-5.9 | Android 9.0 20191024

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
{
"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"
}
Features
https://github.com/crdroidandroid/crdroid_features/blob/9.0/README.mkdn
Instructions
1. Install twrp
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Known Issues:
- speakers during calls
- camera can be buggy, it's work, but some errors in logcat in isp module
Few notes about release:
- the config and the vendor has been re branded
- the kernel has been updated to the last caf kernel LA.UM.7.5.r1-04000-8x96.0 (December 27, 2018). our original samsung kernel based on LA.UM.6.5.r1-05300-8x96.0 (January 04, 2018). I spent 2 weeks to make it work. It was really intersting experience
Links:
CrDroid Builds:
[SM-T820]
4. 20191024: october security patch: https://drive.google.com/file/d/1YseYMPtfFR4D_gyAfvRFp6WHOAg3zdOR/view?usp=sharing
3. 20190812: august security patch: https://drive.google.com/file/d/1ty5v_7fJrzvTa96VclxdsqyeiVg6w4IW/view?usp=sharing
2. 20190708: july security patch: https://drive.google.com/file/d/1730lbHPAdothHyygLphQEM8w0scluJ8K/view?usp=sharing
1. 20190519: https://drive.google.com/file/d/1-nHiiKN1ohX5Lif_sk_HfQx0XhjiwqSb/view?usp=sharing
[SM-T825]
6. 20191024: october security patch: https://drive.google.com/file/d/1m9YM1LSsc_BC42VPJrWbEyY2xTHWE4Ir/view?usp=sharing
5. 20190812: august security patch: https://drive.google.com/file/d/1dI8sMsr5os1dq623FfkHO_2N5NRTWtTp/view?usp=sharing
4. 20190708: july security patch: https://drive.google.com/file/d/12ovfGL6tfTZEX1PNxT-VUCAvjiLu2b_2/view?usp=sharing
3. 20190519: https://drive.google.com/file/d/1yLCMvnQeLN9hHpNf-XDFz5Oeh95CAswu/view?usp=sharing
2. 20190319: fix doze: https://drive.google.com/file/d/1qLgHC5A-ZvBdXPrbJmRT6tofLSwN64uy/view?usp=sharing
1. 20190211: https://drive.google.com/file/d/17CCUDMae5AZYsM0_Xqvyqb4jR8ypijII/view?usp=sharing
TWRP:
Use twrp from https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359
or my repack: https://drive.google.com/file/d/1KyX6xZ8WrcNyHo73-lHhU2dZjX0KFJc1/view?usp=sharing
Gapps:
http://opengapps.org
Platform: ARM64
Android: 9.0
Variant: any, usually I'm using micro or nano
P.s. gapps wizard still buggy in lineage, it can crash
Sources:
Sources: https://github.com/crdroidandroid
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8996
Device: https://github.com/Valera1978/android_device_samsung_gts3llte
Vendor: https://github.com/Valera1978/android_vendor_samsung_gts3llte
Thanks
Thanks to CrDroid team
Thanks to LineageOS team

I'm new to the S3. It's on its way to me. Quick question. Do roms built for the T825 work on the T820?

wmatheney said:
I'm new to the S3. It's on its way to me. Quick question. Do roms built for the T825 work on the T820?
Click to expand...
Click to collapse
No

otg does not work on this rom

Which rome is better this or Lineageos 16? And how do I roast this Rome or the other best?

Hello I have finally rooted with magisk this ROm, but Magisk shows me at SaftyNet the: ctsProfile: False.
I have already hidden all apps with the hiding function but it still does not help. What can I do?

Allstar007 said:
Hello I have finally rooted with magisk this ROm, but Magisk shows me at SaftyNet the: ctsProfile: False.
I have already hidden all apps with the hiding function but it still does not help. What can I do?
Click to expand...
Click to collapse
Hi, use magiskprops module (look in magisk app downloads) to change the device fingerprint (ie make rom pass as vendor made). All custom rom have cts failed because their fingerprint is "something... test-keys/debug-keys".
C.

Is this stable? Does s pen work?? Thanks

glad to hear this pie rom.

hello for about 1-2 weeks my tablet is spinning, I have the feeling that the ROM is very unstable if you use the tablet heavily and the CPUs are all at 100%. Then the tablet gets very hot at the top, the battery runs out very quickly and sometimes the tablet crashes. What can I do there?

Buenas alguien q haya podido hacer root en android 9 en un motomaxx xt1225?

Does this ROM have same issues that T820 LineageOS has with unlocking the tablet after changing the device fingerprint using magisk hide props config? When rebooting and trying to unlock the lock screen loops when using PIN or nothing to unlock. Then I have to hard reboot and it unlocks the first time.

@Valera1978 Thanks so much for your on going development on the Samsung tablets. Your work has always inspired me.
I'm having difficulties getting a fingerprint to register. Is this a common problem for the custom Roms for this device or is this just a problem that I am having?

Hi, can you update this rom like the one you made "Lineage 16" ?

Sadly, I am getting a boot loop after installing this ROM, coming from this ROM any idea what might be wrong?

Valera1978 said:
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
Features
https://github.com/crdroidandroid/crdroid_features/blob/9.0/README.mkdn
Instructions
1. Install twrp
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Known Issues:
- speakers during calls
- camera can be buggy, it's work, but some errors in logcat in isp module
Few notes about release:
- the config and the vendor has been re branded
- the kernel has been updated to the last caf kernel LA.UM.7.5.r1-04000-8x96.0 (December 27, 2018). our original samsung kernel based on LA.UM.6.5.r1-05300-8x96.0 (January 04, 2018). I spent 2 weeks to make it work. It was really intersting experience
Links:
CrDroid Builds:
[SM-T820]
4. 20191024: october security patch: https://drive.google.com/file/d/1YseYMPtfFR4D_gyAfvRFp6WHOAg3zdOR/view?usp=sharing
3. 20190812: august security patch: https://drive.google.com/file/d/1ty5v_7fJrzvTa96VclxdsqyeiVg6w4IW/view?usp=sharing
2. 20190708: july security patch: https://drive.google.com/file/d/1730lbHPAdothHyygLphQEM8w0scluJ8K/view?usp=sharing
1. 20190519: https://drive.google.com/file/d/1-nHiiKN1ohX5Lif_sk_HfQx0XhjiwqSb/view?usp=sharing
[SM-T825]
6. 20191024: october security patch: https://drive.google.com/file/d/1m9YM1LSsc_BC42VPJrWbEyY2xTHWE4Ir/view?usp=sharing
5. 20190812: august security patch: https://drive.google.com/file/d/1dI8sMsr5os1dq623FfkHO_2N5NRTWtTp/view?usp=sharing
4. 20190708: july security patch: https://drive.google.com/file/d/12ovfGL6tfTZEX1PNxT-VUCAvjiLu2b_2/view?usp=sharing
3. 20190519: https://drive.google.com/file/d/1yLCMvnQeLN9hHpNf-XDFz5Oeh95CAswu/view?usp=sharing
2. 20190319: fix doze: https://drive.google.com/file/d/1qLgHC5A-ZvBdXPrbJmRT6tofLSwN64uy/view?usp=sharing
1. 20190211: https://drive.google.com/file/d/17CCUDMae5AZYsM0_Xqvyqb4jR8ypijII/view?usp=sharing
TWRP:
Use twrp from https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359
or my repack: https://drive.google.com/file/d/1KyX6xZ8WrcNyHo73-lHhU2dZjX0KFJc1/view?usp=sharing
Gapps:
http://opengapps.org
Platform: ARM64
Android: 9.0
Variant: any, usually I'm using micro or nano
P.s. gapps wizard still buggy in lineage, it can crash
Sources:
Sources: https://github.com/crdroidandroid
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8996
Device: https://github.com/Valera1978/android_device_samsung_gts3llte
Vendor: https://github.com/Valera1978/android_vendor_samsung_gts3llte
Thanks
Thanks to CrDroid team
Thanks to LineageOS team
Click to expand...
Click to collapse
Thank so much you for the Rom, I don't can't erase data, can't install rom, apparently device features chripytography? I'm able install lineage but, stuck in screen initial with message about don't can continue, erase all, but I'm don't able bypass, can't someone help me ? Thanks so much

Rhobb said:
Thank so much you for the Rom, I don't can't erase data, can't install rom, apparently device features chripytography? I'm able install lineage but, stuck in screen initial with message about don't can continue, erase all, but I'm don't able bypass, can't someone help me ? Thanks so much
Click to expand...
Click to collapse
did you try not only wiping but "Format Data" as well already?
When posting please make it easier to help by specifying device (in threads for more than one) TWRP (source if not in thread) you used and what ever seems helpful.

bmwdroid said:
did you try not only wiping but "Format Data" as well already?
When posting please make it easier to help by specifying device (in threads for more than one) TWRP (source if not in thread) you used and what ever seems helpful.
Click to expand...
Click to collapse
Thanks so much for answer me, I use this twrp https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359
Yesterday I searching here in XDA I make able downgrade Android 9 to Android 8 ,
But twrp is dont able to erase partition data , also dont check the option data, also dont mount data,
The others is just fine ,
I able install lineage but in screen shows message "cripytography error, make hard reset for you restore your data from your Google acount"
Shows buton "Erase All" but dont works
Thanks so much for answer me, great time for you!

Rhobb said:
Thanks so much for answer me, I use this twrp https://forum.xda-developers.com/ga...recovery-twrp-3-1-0-1-samsung-galaxy-t3581359
Yesterday I searching here in XDA I make able downgrade Android 9 to Android 8 ,
But twrp is dont able to erase partition data , also dont check the option data, also dont mount data,
The others is just fine ,
I able install lineage but in screen shows message "cripytography error, make hard reset for you restore your data from your Google acount"
Shows buton "Erase All" but dont works
Thanks so much for answer me, great time for you!
Click to expand...
Click to collapse
Might have been necessary for the device to log out from Google account before doing anything on it.
Think I read somewhere something like this.
As you've flashed TWRP with Odin this seems to be working so it might help to flash stock firmware and then start all over again without logging into Google before.
You have to additionally inquire further more (probably somewhere else) for I don't think I will be able to help you with this specific problem as I never had it.

bmwdroid said:
Might have been necessary for the device to log out from Google account before doing anything on it.
Think I read somewhere something like this.
As you've flashed TWRP with Odin this seems to be working so it might help to flash stock firmware and then start all over again without logging into Google before.
You have to additionally inquire further more (probably somewhere else) for I don't think I will be able to help you with this specific problem as I never had it.
Click to expand...
Click to collapse
Thank you so much for you help me , your explanation help a lot, is great for me learning from you , I did it, I then can downgrade the rom from Android 9 to 8 a second time, in the first I can't make root, and I also find the correct rom Android 8 in other post here in xda, T825XXU3BSD1, then you suggestion run just fine, I make able to root the Tablet, thank you so much for help me , now is root in Android 8, to me is perfectly well so I now already able remove bloatware off my Tablet, I very happy, great time for you !

[ROM][9.0][UNOFFICIAL] Nexus Stock for 2019 Galaxy Tab A 10.1 [SM-T510]

{
"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/T515], here's one I just created based on the September 2019 Update and @AndyYan's LineageOS 16.0 GSI. 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 (T510XXS3ATB4) for the SM-T510.
The system is based on @AndyYan's LineageOS 16.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 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:
SM-T510:
Nexus_Stock_LP_T510XXS3ATB4-20200422.tar.md5 (Odin tarball)
Nexus_Stock_LP_T510XXS3ATB4-20200422.zip (TWRP update)
SM-T515:
No longer supported (since I don't have hardware for testing), but archives are posted here.
Change Log:
20200422:
New private build of LineageOS GSI with April 2020 security patch.
Updated to T510XXS3ATB4 kernel and vendor partition (February 2020 Update)
Updated to latest OpenGApps (20200422), with private fix for Chrome issue.
20200405:
Fixed Double Tap to Wake feature (enabled in Phh Treble Settings).
Fixed crash on first two attempts to launch Phh Treble Settings.
New private build of LineageOS GSI with the above fixes (#663 & #1228).
Updated to latest OpenGApps (20200404), with private fix for Chrome issue.
20200325:
Switched back to Pixel Launcher updated with Nexus tablet device profiles.
New LineageOS GSI build of treble_a64_bvN target with March 2020 Security Update.
Switched to ext2simg for sparse image conversion to improve Odin compatibility and reduce download size.
Updated to OpenGApps 20200311. (Subsequent builds have issues.)
20200308:
Charging after full shutdown will no longer hang during level-of-charge animation.
MTP file transfers no longer require USB Debugging to be enabled.
Updated to T510XXU2ASK5 kernel (November 2019 Update)
Updated to latest OpenGApps (20200307)
20200103:
Updated to T510XXS2ASK1 kernel (November 2019 Update)
Updated to latest OpenGApps (20200103)
20191109:
USB Debugging is enabled by default (MTP workaround)
SurfaceFlinger optimization to improve scrolling performance
Updated to latest OpenGApps (20191109)
Now building TWRP update (.zip file)
20190922:
Switched from AOSP base to LineageOS.
Updated to latest OpenGApps (20191022)
20190921:
Updated to T510XXU2ASI4 kernel and TWRP v3.3.1-5..
20190909:
Scoped MTP fix more tightly, preventing charging cap at 79%.
20190906:
Fixed MTP support, so you can now transfer files easily via USB.
20190828:
Google Play Protect now plays nice. You no longer have to register your GSF ID. (Thanks, @phhusson!)
Removed DeviceID app, since it's now unneeded.
20190825:
AOSP 9.0 v119
Updated to TWRP 3.3.1-2
Restored some security features to custom kernel
20190810:
AOSP 9.0 v117
August security patch
Nexus default wallpaper
20190629:
Initial release based on AOSP 9.0 v114
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
treble_build_los
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!

Oo our first custom rom!! Thanks alot!! Cant wair to try it soon

Important Note: The Night Mode setting in Developer Options is set to "Always off" by default. Don't change it! When I set it to "Automatic (based on time of day)", the screen went black and I couldn't recover without a factory reset. (I'm assuming that this was a bug in SystemUI.apk.)

Thanks for the effort and time you've put into this.
Unfortunately I can't get it to work. I will wait for detailed full instructions. I just keep getting Odin fails.

NightHawkUndead said:
Unfortunately I can't get it to work. I will wait for detailed full instructions. I just keep getting Odin fails.
Click to expand...
Click to collapse
Well, I just verified the MD5s and they match. However, to be a little more squared away, I replaced the original .tar file that I uploaded with a .tar.md5 (a.k.a. "tarball) which has the MD5 footer that Odin can use to verify the file integrity. I've also compressed the contents with LZ4, which cut the size down by a third.
Installing the new tarball with Odin3 v3.13.3 on my tablet went smoothly, so I hope this works for you.

Finally got it to work. Had to flash back to stock. Wipe. Then immediately reboot bootloader again and flash Rom.
How do I go about rooting now?
Edit: nevermind, got it rooted. Everything is working fine now!
Sent you a donation for your work. ? ?

I have a new SM-T510 on T510XXU1ASEF
I flashed this ROM with Oding3 3.13.3. Then it rebooted. The Nexus logo goes by, I am asked to confirm the ROM is non-standard by pressing the "power" button. Then I get the TWRP splash screen, and it hangs.
Tried to flash 3 times, same result.
Is there something to going back to stock, wiping, bootloader, flash again? Or is that just doing things until it works?

garyemiller said:
I flashed this ROM with Oding3 3.13.3. Then it rebooted. The Nexus logo goes by, I am asked to confirm the ROM is non-standard by pressing the "power" button. Then I get the TWRP splash screen, and it hangs.
Click to expand...
Click to collapse
It's important that you wipe the data partition before TWRP boots, since it currently hangs when it encounters an encrypted file system. (Yes, this really shouldn't happen, but I haven't found a fix for that TWRP bug yet.)
Did you select "Wipe data/factory reset" in the stock OEM recovery immediately before you flashed this custom ROM?

"Did you select "Wipe data/factory reset" in the stock OEM recovery immediately before you flashed this custom ROM? "
Yes.
I got it to work. reinstalled stock rom (link above). Booted it stock. Enabled Developer Mode, Enabled USB debugging. confirmed OEM still unlocked. Boot to recovery, wipe, boot to bootloader. Flash this ROM with Odin3. reboot. All is well.
So now I guess I gotta do the Device ID dance. Install Magisk Manager, patch the boot.img from your tar file, then use TWRP to install the magisk_patched.img as boot.
Along the way I also wasted a lot of time trying to flash with heimdall 1.4.2. But that was very flakey. Odin3 just worked.
---------- Post added at 08:46 PM ---------- Previous post was at 08:23 PM ----------
I guess I should mention my biggest issue was unlocking the bootloader. Not like before.
Power off. Hold Vol UP and Vol Down. Plug in USB. Long press Vol UP to unlock.

garyemiller said:
So now I guess I gotta do the Device ID dance. Install Magisk Manager, patch the boot.img from your tar file, then use TWRP to install the magisk_patched.img as boot.
Click to expand...
Click to collapse
If you install Magisk, you might not have to do the device certification dance. It tries to fake out Play Protect.

The device certification was painless. I've doe that before on other devices.
Rooting with Magisk was also painless:
Grab boot.img from your tarball.
adb push boot.img /storeage/emulated/0/Download
patch using Magisk Manager
adb pull /storage/emulated/0/Download/magisk_patched.img .
heimdall flash --BOOT magisk_patched.img
I can't get SafetyNet to pass, even with Magisk SafetyPatch module. But not a big deal to me.
Is there a way to turn off the google page on the launcher?
Thanks for the nice ROM! So much better than stock.
I'm still looking for a good ad blocker for Pie. Up tile now I have used a Raspberry Pi as a dnsmasq server for ad blocking.

garyemiller said:
Is there a way to turn off the google page on the launcher?
Click to expand...
Click to collapse
If you open up the Android One Launcher settings, there's a "Display Google app" option that you can disable.
garyemiller said:
I can't get SafetyNet to pass, even with Magisk SafetyPatch module..
Click to expand...
Click to collapse
Yeah, I've tried the usual tricks like spoofing the fingerprint, but that didn't work either. This kind of hard Play Protect device rejection seems to happen for me whenever the vendor partition is using release keys and the system partition is using test keys.
I haven't found an XDA thread yet that really provided deep insight into the algorithm that Google uses for Play Protect and SafetyNet. And given the proprietary nature of what it's doing, we may never get it. I think our best long-term solution is to get LineageOS 16 builds that pass CTS testing, but we may have to scrounge for 64-bit drivers.

I just went with Nova Launcher. It has been good to me.
I can wait for Lineage to catch up. I'm happy to be rid of bloatware. And with root I can block ads and my firewall works.
Thanks for the ROM! I'm happy!

ankh_hikes said:
Which stock files do I need to replace the nexus boot splash screens? I would like have the Samsung ones.
Click to expand...
Click to collapse
Just restore the original param image. (But seriously, why would you? The stock boot splash is ugly! )

Just ordered my T510, can't wait to try this out when it arrives

d4dave said:
Just ordered my T510, can't wait to try this out when it arrives
Click to expand...
Click to collapse
The 3G/128G config was selling for just $250 USD through Costco until a few days ago. That's a pretty insane value....as long as you aren't stuck with Samsung's One UI, that is.

will there be a new release coming?

DarthGW said:
will there be a new release coming?
Click to expand...
Click to collapse
Yes, I'm trying to build an unofficial LineageOS 16.0 release, but am struggling with some build issues. The primary goal is to deal with the Play Protect device certification (but I definitely won't pass SafetyNet). Eventually, I'll also get to fixing MTP.

wow dude, thanks a lot for you work

Is it possible to install this on the 510 with Product code NEE
PDA T510XXU1ASF2
CSC T510OXM1ASF3
It's the stock may Nordic firmware

[ROM][UNOFFICIAL][G770F/FD][11] LineageOS 18.1 S10 Lite

hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work

immerblind said:
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
Click to expand...
Click to collapse
I think i had to mention this, booting recovery now requires you to have usb plugged in while you're punching the recovery combo to enter recovery.
Also, i've fixed the lineage recovery yesterday, sorry for the hassle.

New release are up! New release have a new repo right here https://github.com/mainey/r5q-archive/releases , hopefully this would be less confusing for the end users to find files needed. The old repo would now only releases new vendor updates from samsung.
New build: https://github.com/mainey/r5q-archive/releases/tag/ROM-20210121
note: i might or might not announce new builds in the future all the time, if you want to be notified when releases are published, make sure to click the watch button on the top right on the github repo page

What's handy?
How did you patch boot.img and root the ROM?
Is there a how-to for noobs? I guess all my knowledge on how to flash custom ROMs from 2 years ago are completely useless after all.
Thanks!
immerblind said:
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
Click to expand...
Click to collapse

Ok, I found the instructions for patching boot.img:
[HOW-TO-ROOT] [G770F/DS] Galaxy S10 Lite International Model
Models: SM-G770F or SM-G770F/DS Frequently used key combinations keys: FORCE REBOOT: Hold "Volume Down" and "Bixby/Power" button. DOWNLOAD MODE: With the phone off, hold "Volume Down" and "Volume Up" button, connect your phone to a computer via...
forum.xda-developers.com
darth.cabs said:
What's handy?
How did you patch boot.img and root the ROM?
Is there a how-to for noobs? I guess all my knowledge on how to flash custom ROMs from 2 years ago are completely useless after all.
Thanks!
Click to expand...
Click to collapse

Got new account nice to be here too..

Vaughnn said:
我想我不得不提一下，启动恢复现在需要您在插入恢复组合以进入恢复时插入USB。
另外，我昨天修复了血统恢复，很抱歉给您带来麻烦。
Click to expand...
Click to collapse
Vaughnn said:
LineageOS是免费的，社区构建的Android 11售后固件发行版，旨在提高设备的现有Android的性能和可靠性。
LineageOS基于Android开源项目，并得到了Android社区中许多人的额外贡献。无需安装任何Google应用程序即可使用它。下面链接的是一个来自另一个Android项目的程序包，这些程序可以还原Google部件。LineageOS仍然包含各种特定于硬件的代码，无论如何它们也正在缓慢地开源。
LineageOS的所有源代码都在LineageOS GitHub中提供。如果您想为LineageOS做出贡献，请访问Gerrit Code Review。您还可以查看更改日志以获取更改和功能的完整列表。
要求： Oneui 3.0（DTL1）。
指示：
Flash Lineage Recovery或从下面的下载文件中获取文件，然后使用此处的说明对其进行刷新
格式化数据/恢复出厂设置
刷新构建（使用adb侧载，或使用mtp将文件推送到sdcard）
重启
笔记：
请勿使GAPP闪烁，这包括最小的GAPP。我将发布带有gapps的版本，直到gapps程序包足够适合我的需求为止。
VoLTE，IMS和其他三星特定的rom功能将不会移植或修复。
在使用指纹之后或之前，屏幕有时会闪烁，这只是免责声明，如果有人使用此版本的癫痫病患者，我将不承担任何责任
错误：
接近度（可能无法在某些应用程序上运行）
5Ghz热点
下载：
r5q 18.1
r5q恢复
支持小组： 电报
报告错误
如果您正在运行自定义内核或已安装Xposed，请不要报告错误
问题发生后立即拿起logcat。（除非您知道自己在做什么，否则请至少包括日志的几页，而不仅仅是最后几行。）
如果是随机重新引导，请抓住/ proc / last_kmsg。（除非您在重新启动之前就可以获取它，否则不要费心获取一个logcat。重新启动之后的logcat是没有用的）
如果从根shell运行“ setenforce 0”后问题消失了，请抓住/data/misc/audit/audit.log
Code:
您的-
LineageOS版本：
LineageOS下载网址：
Gapps版本：
你是否 -
擦拭：
使用钛备份还原：
出现问题后重新启动：
你正在用吗 -
任务杀手：
非库存内核：
其他修改：
根据需要提供任何其他信息（观察/问题发生的频率/它工作的最新版本/等）：[/ CODE]
[B]我会在业余时间做这种事情。如果您喜欢我的工作，请考虑通过单击下面的链接为我买一杯饮料（捐赠）。[/B]
[URL='https://www.paypal.com/donate/?cmd=_donations&[email protected]']贝宝[/URL]
存档链接：[URL='https://github.com/mainey/release-r5q/releases']Github版本[/URL]
内核来源：[URL='https://github.com/mainey/android_kernel_samsung_r5q']Github[/URL]
[/QUOTE]
Hello, I would like to ask how my phone is currently Android 10 and One ui is 2.1. I want to change to LineageOS.
[/QUOTE]
Click to expand...
Click to collapse

immerblind said:
hell of a ride to install this. nearly impossible to make recovery work (its because oneui 3 update i read somewhere?? problems with booting in newly installed recovery after using odin....damn)
my steps to get a proper recovery and this build running
- installed samsung android 11 / oneui3
- patched boot.img and rooted the rom
- installed twrp manager app
- put the twrp img on handy, installed it via twrp manager app
- tataa twrp installed
- had problems to decrypt handy (fixed after i wiped internal storage only)
- installed lineageos via twrp
rom works good so far. all i need works. so i use it as my daily driver. thanks for your work
Click to expand...
Click to collapse
Hello, I would like to ask how my phone is currently Android 10 and One ui is 2.1. I want to change to LineageOS.

Rom is fine. There's simply not much to tell about. It runs runs runs. No problems at all. Twrp or lineageos recovery....whatever. all good
Would it be possible to have a version without Gapps?

Vaughnn said:
New release are up! New release have a new repo right here https://github.com/mainey/r5q-archive/releases , hopefully this would be less confusing for the end users to find files needed. The old repo would now only releases new vendor updates from samsung.
New build: https://github.com/mainey/r5q-archive/releases/tag/ROM-20210121
note: i might or might not announce new builds in the future all the time, if you want to be notified when releases are published, make sure to click the watch button on the top right on the github repo page
Click to expand...
Click to collapse
Is your lineageos 19 beta google-free?

Hi. Can anyone confirm if [BETA] Lineage 19 20220307 Beta 4 is stable enough as daily ROM?
Banking apps work? OIS+EIS during video recording?
Thank you.

Vaughnn said:
Requirement: Oneui 3.0 (DTL1).
Instructions:
Flash Lineage Recovery or grab the files from the download below and use the instruction from there to flash it
Format Data/Factory Reset
Flash the build (Use adb sideload, or push the file to sdcard with mtp)
Reboot
Click to expand...
Click to collapse
First of all thank you for your time and energy.
I'm having problem flashing latest beta 4.
I'm coming android 11 Oneui 3.1. My device is was rooted with unlocked bootloader.
1. I've flashed the lineage recovery via odin (Including vbmeta_disable) and upon reboot (it needed 2 boots to get into recovery) I chose factory reset of the device.
2. I've enabled developer options and saw my bootloader was unlocked.
3. I've booted into recovery
4. I've flashed the lienage os 19 beta 4 with google apps
I keep getting status error 2 and installation is aborted :O(

[ROM] LineageOS 20.0 UNOFFICIAL - 1.2 [2023-05-06]

LineageOS 20.0 for Sony Xperia XZ1
{
"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"
}
RELEASE
This is an alternative ROM for the Sony Xperia XZ1, offering several privacy features.
Please report any issues you observe apart from the ones listed below. Logs are needed for me to fix anything (preferably dmesg and logcat).
DOWNLOAD
You can download the latest releases here:
poplar (G8341):
https://sourceforge.net/projects/yoshino/files/poplar/twrp/
https://sourceforge.net/projects/yoshino/files/poplar/lineage-20.0/
poplar_dsds (G8342):
https://sourceforge.net/projects/yoshino/files/poplar/twrp/
https://sourceforge.net/projects/yoshino/files/poplar/lineage-20.0/
poplar_canada (G8343):
https://sourceforge.net/projects/yoshino/files/poplar/twrp/
https://sourceforge.net/projects/yoshino/files/poplar/lineage-20.0/
poplar KDDI (SOV36)
https://sourceforge.net/projects/yoshino/files/poplar/twrp/
https://sourceforge.net/projects/yoshino/files/poplar/lineage-20.0/
RECOMMENDED GAPPS (others works too)
https://androidfilehost.com/?w=files&flid=322935
INSTALLATION
Before first install: flash and boot into the TWRP provided in this thread, format data, reboot to recovery and wipe all internal partitions, then flash the ROM, GApps and root (if needed).
Note: There is not going to be a LOS su addon anymore. If you need root, flash a root manager of your choice. No guaranteed support from LOS for this.
When updating from previous builds, simply dirty flash the ROM is enough, decryption in new TWRP works now
Recommended GApps: MindTheGapps provided in this thread.
KNOWN ISSUES
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
Currently, LOS isn't feature complete yet, so some things, buttonn, advanced menù etc. may be still missing
You tell me...
Contributors
derf elot, modpunk, Rooted_Ansh
Source Code
poplar: https://github.com/whatawurst/android_device_sony_poplar
poplar_dsds: https://github.com/whatawurst/android_device_sony_poplar_dsds
poplar_canada: https://github.com/whatawurst/android_device_sony_poplar_canada
poplar_KDDI: https://github.com/whatawurst/android_device_sony_poplar_kddi
kernel: https://github.com/whatawurst/android_kernel_sony_msm8998
Rom Information
ROM OS Version: Android 13
ROM Kernel: Linux 4.4
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2023-05-06
ALL CREDITS TO DERF ELOT AND THE OTHER DEVS BEHIND THE ROM, I'M ONLY POSTING IT.
---------------------------------------
Changelogs:
v1.2 (2023-05-10):
- Updated to T QPR2 release (LineageOS upstream)
- Updated to May 2023 Security updates (both ROM and kernel)
- Our kernel now includes updates by CIP and is up-to-date with tag st40 - thanks also to Flamefire for help with some of these (1)
- Reduced zram size to 25% (1gb) of out total RAM to have more to use freely
- Updated BT stuff for QPR2 (maybe offloading is working again? needs confirmation)
- Added the option to reflash the mbn via OpenCS (see Xperia Parts) - thanks also to shank03 & Flamefire (2)
- Fully enabled IMS on Congstar Germany via overlay on lilac
- Possibly some battery/performance optimizations here and there
- Fixed Android Auto support
- Added new LineageOS "Charging control hal" for battery charging care (3)
- Maybe more I forgot...
(1) The CIP kernel includes fixes for issues and security vulnerabilities from 4.14 kernel (see https://git.kernel.org/pub/scm/linux/kernel/git/cip/linux-cip.git)
(2) A somehwat lengthy explanation: This option is off by default on fresh installs. When upgrading, this should be enabled because we enforced this for everybody previously. However, this option is only required for certain carrier mbns that enable IMS. Personally, I know that the O2/Telefonica Germany mbn needs this, otherwise you get a crashing modem at every boot (unless you switch to 3g before rebooting and back to LTE after boot). I generally recommend playing with this option, and if you don't need it (e.g. modem doesn't crash on boot), just keep it off - like mentioned before, this is now the default behavior of OpenCS on fresh installs anyway.
(3) This is not finalized or merged upstream is LineageOS yet, but seems like a nice feature to have and test drive already. Some bugs may be possible.
v1.1 (2023-01-08):
Updated to T QPR1 release (LineageOS upstream)
New default camera app (LineageOS upstream) - yes, we cannot change video fps currently (thanks Sony!)
Any other updates by LineageOS upstream
Kernel security updates (also thanks to Flamefire)
Dropped keyprovd service - it is useless on unlocked BL anyway
Show 4G instead of LTE icon - saves some space too
Enable IMS by default - this still only works if carrier is supported
Fix some selinux denials (also thanks to Flamefire)
Fixup ViLTE dependencies - this might in theory work again, but it's not enabled yet
v1.0 (2022-10-02):
Initial release

Can’t wait to try it !!! Thanks tux

Can i flash this using old twrp version like 3.6.2 - 9?

The rom is great but every time the device reboots and finishes the boot animation it repeats one more time boot animation.
According to the picture, I can't scroll down as usual, can only use those 4 buttons @@ until rebooting (I had landscape rotation to watch youtube then rotate the screen again when the video ends and it's like that
).
rarely but the sound doesn't play even if i keep the volume high or switch to listening to music or watching youtube until the device is restarted
(sorry if I said wrong or wrong grammar, I'm not very good at English. )

raffyei8ht said:
Can i flash this using old twrp version like 3.6.2 - 9?
Click to expand...
Click to collapse
No idea, but for internal memory decription the new one is needed.

Tux111 said:
No idea, but for internal memory decription the new one is needed.
Click to expand...
Click to collapse
What is the use of internal decription if you don't mind me asking

raffyei8ht said:
What is the use of internal decription if you don't mind me asking
Click to expand...
Click to collapse
By default android protect (encrypt) your internal memory. TWRP lacked decryption for a long time, now its supported. This means, with new recovery, you can see and manage your internal memory via TWRP using your lockscreen password. Before, you simply can't.

The fingerprint sensor doesn't work, auto brightness is also not working, does anyone know how to fix it

Each time I reinstalled a rom, some function which worked just fine on that rom stopped functioning, do you guys know how to prevent this

This is a very good ROM. Good for daily use. Didn't encounter any problem. Can't wait for the Pixel Experience Android 13.

ecrissor said:
The fingerprint sensor doesn't work, auto brightness is also not working, does anyone know how to fix it
Click to expand...
Click to collapse
FP perfectly working.
ecrissor said:
Each time I reinstalled a rom, some function which worked just fine on that rom stopped functioning, do you guys know how to prevent this
Click to expand...
Click to collapse
I guess you have some missing files or something like that. Try reflashing stock rom and persist.img, something wrong with your files.

Maybe this is a dumb question, but what is the difference between the twrp provided here and the 'stock' twrp from twrp.me? Will both work?

Nice room
great work

poplar_dsds said:
Maybe this is a dumb question, but what is the difference between the twrp provided here and the 'stock' twrp from twrp.me? Will both work?
Click to expand...
Click to collapse
Both works but this one should be able to decrypt internal memory. No idea if the one from twrp.me does the same or if its the same file.

Tux111 said:
Both works but this one should be able to decrypt internal memory. No idea if the one from twrp.me does the same or if its the same file.
Click to expand...
Click to collapse
Okay i see, thank you! I updated to your version of twrp and dirty flashed the rom from 19.x to this version, worked great, even with apps and so on!
Also thanks for the ROM!

Hi there,
I'm a complete noob on XDA, but I just flashed this TWRP (twrp-3.6.2_12-0-20221002-poplar) over another TWRP (twrp-3.7.0_9-0-poplar) and now, when entering recovery mode I get stuck in loading screen of teamwin Recovery Project 3.6..2_12-0
I can get out of loading screen by pressing all buttons, and device turns off.
I rebooted into fastboot and flashed back the 3..7 TWRP and now things are back to normal.
Any sugestions on what I can do to install this TWRP?

xdatomsgmail said:
Hi there,
I'm a complete noob on XDA, but I just flashed this TWRP (twrp-3.6.2_12-0-20221002-poplar) over another TWRP (twrp-3.7.0_9-0-poplar) and now, when entering recovery mode I get stuck in loading screen of teamwin Recovery Project 3.6..2_12-0
I can get out of loading screen by pressing all buttons, and device turns off.
I rebooted into fastboot and flashed back the 3..7 TWRP and now things are back to normal.
Any sugestions on what I can do to install this TWRP?
Click to expand...
Click to collapse
So, I was able to install lineage-20.0-20221002-UNOFFICIAL-1.0-poplar.zip from this post using TWRP 3.6..2_12-0, without problems.
Did not try to flash twrp-3.7.0_9-0-poplar again.
Is there a thread with future requests? I would like the default browser not to default to google, as the whole point for me is to de-google my phone.

Hi, so I've been absent from Custom Roms for the last couple years - since I got my XZ1 and the DRM key extraction was too much of a hassle for me as I didn't miss much from the stock rom.
Since I got some spare time over the years I was thinking to finally tackle that topic, but I have two questions:
1) The opening post says this
Tux111 said:
Stock camera is not working anymore due to incompatibility of stock library (libimageprocessorjni.so) with new libgui
Click to expand...
Click to collapse
is it even still relevant for me to back up my DRM keys / back up the TA partition if I don't want to go back to stock? what camera are you using then? is the quality comparable? is slow motion still possible?
2)
i know that in the past, safety net checks were just looking for bootloader / root, but they changed to checking if the ROM is signed with a proper signingkey, right? is this rom signed with a non-test-key?
I've got a couple of banking apps on my phone and it would obviously prevent it from being a daily driver if they were not supported anymore :/
Thanks in advance!

New LOS Update 1.1 is here! Enjoy!

xdatomsgmail said:
So, I was able to install lineage-20.0-20221002-UNOFFICIAL-1.0-poplar.zip from this post using TWRP 3.6..2_12-0, without problems.
Did not try to flash twrp-3.7.0_9-0-poplar again.
Is there a thread with future requests? I would like the default browser not to default to google, as the whole point for me is to de-google my phone.
Click to expand...
Click to collapse
By default the browser isn't Google Chrome afaik, so i don't see the problem. Also, tbh, this makes no sense considering Android=Google. Chromium is builded inside the ROM,is part of the ROM,so once you install Android, you are installing something from Google. So i don't get it.
If you don't install gapps, then you don't have Chrome as default browser. Otherwise, flash gapps and remove Chrome.

Better Mobile App

welcome