Database Develop

Installing GSI ROM on realme XT RMX1921

Code:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
Hi guys!
I just want to share how to flash GSI on our realme XT RMX1921.
I've testing Phh's Quack (Android 10) and booted.
You maybe can test another GSI and then report it here.
I haven't testing another AOSP GSI or even OEM GSI like OOS / MIUI / H2OS.
I'll update if I was testing it and boot successfully.
If you have simpler way to install GSI then tell me tho.
Here is the steps :
1. Unlock your XT's bootloader and make sure you have installing adb fastboot on your Windows / Linux / Mac
2. Flash TWRP by thesprintster here : https://forum.xda-developers.com/re...ecovery-unofficial-twrp-realme-5-pro-t3985459
3. Download LineageOS by thesprintster here : https://forum.xda-developers.com/realme-xt/development/rom-lineageos-16-0-t3985463
4. Open LOS zip and take the boot.img
5. Download vbmeta by thesprintster here : https://drive.google.com/drive/folders/1JwIpix76opSAToa-4X4YdT_SH5JUOxJQ
6. Download Phh's Quack here : https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559 (select arm64-ab-gapps or arm64-ab-vanilla)
6a. You can download another GSIs like ExpressLuke GSIs here : https://forum.xda-developers.com/project-treble/trebleenabled-device-discussion/gsi-expressluke-built-gsis-t4003457 and make sure you download the ARM64 AB variant.
7. Boot to TWRP and backup your vendor image (or maybe all your vendor + system + boot + data if you want to back to ColorOS) incase to avoid any error
8. Wipe all except vendor
9. Back to bootloader / fastboot, put your vbmeta.img to your adb fastboot folder
10. Flash vbmeta.img by typing fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
11. Boot to TWRP and copy Phh's Quack System image and LOS boot.img to your rXT
12. Flash boot and system image
13. Flash Gapps (if you download the vanilla variant) or if you want Google-less you can skip this
14. Reboot to system
15. Wait for booting aprrox. 4 minutes
Bug list on Phh's Quack GSI (and another Phh's based GSIs) tested on rXT 8/128 :
- Fingerprint not working (realme disable fingerprint since bootloader unlocked)
- VoLTE not working (global GSI bugs)
- Status bar on side (like battery and clock) got cropped and mis-positioned How to fix clock and battery logo : Go to Settings - Phh Treble Settings - Misc features - Set rounded corners diameter : 15 (or above 15, just fill with values you want)
- Bluetooth Media not working
- you tell?
Tested GSIs :
- Quack Phh-Treble arm64-ab-gapps v202 by phhusson
- Evolution-X 3.3 20191111 ARM64-AB by turbolukex5
Enjoy! :fingers-crossed:

You can correct status bar cropping by enabling developer options and selecting cutout.

I'll just add this here in case anyone needs it.
Also , if anyone finds workarounds for VoLTE, please feel free to post it.

[RECOVERY][3.4.0-14][phoenix/in]Unofficial TWRP for Xiaomi Poco X2/Redmi K30 (Beta)

Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
Features:
- Decryption works
- Otg works
- Flash Rom works
- F2FS support
- Fastboot boot command support
Not working:
- Fastbootd
- Adb sideload
- Backup restore and image flash (system-vendor-product)
- Android 11 fully support
Download:
TWRP 3.4.0-14 Unofficial by mauronofrio
TWRP 3.4.0-12 Unofficial by mauronofrio
TWRP 3.4.0-10 Unofficial by mauronofrio
To Flash the TWRP:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP manually or using a fastboot command.
Code:
fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img
or
Code:
fastboot oem reboot-recovery
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/Teamwin/android_bootable_recovery
https://github.com/mauronofrio/android_device_xiaomi_phoenix
https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150
My Telegram TWRP Support Group:
https://t.me/twrp_Mauronofrio
Donations:
Credits:
- Thanks to @merothh for the hard testing and other support
- Thanks to @bigbiff and @Captain_Throwback for the hard work on this android 10 TWRP
Thanks to all testers on the Telegram Group
Created 2020-09-16

Nice work the first build...
Thanks and waiting for 2nd build.....

mauronofrio said:
- Backup restore and image flash (system-vendor-product)
Click to expand...
Click to collapse
But does backup & restore for the data partition work?

Nice work!!!

Ya_SG said:
But does backup & restore for the data partition work?
Click to expand...
Click to collapse
it is in non working list

Nice. May I ask does Format data works reliably yet? (mean after Format data and flash rom, the phone won't automatically encrypt)

Never_Sm1le said:
Nice. May I ask does Format data works reliably yet? (mean after Format data and flash rom, the phone won't automatically encrypt)
Click to expand...
Click to collapse
Yes works

Finally!
Now I don't have to be afraid the phone will brick because of unknown sourced twrp from chinese.

Martensite said:
Finally!
Now I don't have to be afraid the phone will brick because of unknown sourced twrp from chinese.
Click to expand...
Click to collapse
I'm using the chinese one for months and it does not have any issues.
Until this has stable status or official status I'm more afraid of flashing this one

It's always asking for the password. Even though i did format data using that chinese twrp, when i flash this, it asks for password again.

TWRP 3.4.0-14 for Xiaomi Poco X2 (phoenix-phoenixin):
- Fixed decryption request also when the device is not encrypted.
TWRP 3.4.0-14 Unofficial by mauronofrio

mauronofrio said:
TWRP 3.4.0-14 for Xiaomi Poco X2 (phoenix-phoenixin):
- Fixed decryption request also when the device is not encrypted.
So the remaining issues still exist?
Thanks btw for new build
Click to expand...
Click to collapse

internal storage not showing in pc from this latest build. cannot copy rom zips to internal

This TWRP is worked on my Redmi k30 Phoenix. I have tried 'recovery-TWRP-3.4.0B-0209-REDMI_K30-CN-wzsx150', but failed boot twrp.
Thank u so much 'Dev', Please continue releasing newer version <3

arifn82 said:
internal storage not showing in pc from this latest build. cannot copy rom zips to internal
Click to expand...
Click to collapse
reboot again in TWRP, connect USB cable to pc. now u can see internal storage

How can i make the twrp permanent ?

Userbaban said:
How can i make the twrp permanent ?
Click to expand...
Click to collapse
Don't Flash stock ROM/ official ROM .

'boot ' fastboot command in lastest platform-tools won't work in that way.It assume the file is a KERNEL,not a whole boot image.This will only make device go blackscreen.Check the binaries' help before run this command!

I found a problem.
If I use WIPE to format internal storage in TWRP and still can't mount internal storage after rebooting recovery.
It will not be possible to copy ROM files properly.
If you restart the system, re-entering TWRP after a successful system boot will restore the system to normal.
I wonder if it can be fixed?

ask Decrypt password everytime I reboot to twrp.
Help!

[RECOVERY][TB-X505F][UNOFFICIAL] TWRP 3.6.x for Lenovo Tab M10 HD

This version of TWRP works on the Lenovo TB-X505F (wifi).
For the TB-X505X, see this thread. For the TB-X605F/L, see this thread.
For the TB-X606F/L, see this thread. The X606F/L is the second gen M10 and it uses a Mediatek SOC.
Code:
#include <std_disclaimer.h>
/*
* We are 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 us for messing up your device, we will laugh at you.
*/
Working:
AFAIK, everything is working including:
data decryption
MTP
Known issues:
time not adjusting for Daylight Saving
OTA (for a workaround see this post)
Before installing TWRP
Before you install TWRP, upgrade your tablet to the Android 9 (Pie) or Android 10 (Q) stock ROM.
This tablet shipped with Android 8 (Oreo), in which the bootloader did not allow unlocking. When you tried to unlock the bootloader, it gave this error message:
Code:
fastboot oem unlock-go
FAILED (remote: 'unknown command')
fastboot: error: Command failed
Installation
It is recommended that you also install Magisk. This will ensure TWRP remains your default recovery.
Step-by-step guide
download TWRP to your PC (see the Download section below)
download magisk.apk to your MicroSD or OTG device. Get the latest Magisk apk file here. Rename the filetype from apk to zip (for example Magisk-v22.0.zip)
if your bootloader is already unlocked, go to step 4. To unlock bootloader:
on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
on tablet: go to Settings->System->DeveloperOptions. Turn on: "OEM unlocking" and "USB debugging".
connect tablet to your computer. Tablet will ask for permission to "Allow USB debugging". Tick "always allow" and select "OK".
backup any files you want to keep to an external device (MicroSD/OTG/computer), because the next step will wipe all your photos, files, google account etc on the tablet.
Now unlock the bootloader:
Code:
adb reboot bootloader
fastboot oem unlock-go
fastboot reboot
flash the twrp image:
Code:
adb reboot bootloader
fastboot flash recovery twrp.img
if you haven't loaded Magisk yet, go to step 6. If you have already loaded Magisk, you can just reboot and you're finished:
Code:
fastboot reboot
adb reboot recovery
load Magisk (step one): reboot to recovery. Do not reboot into the system, because it will over-write TWRP with stock recovery. If that happens, go back to step 4 and start again. When you issue the reboot command (below), you have to immediately press the button combination to reboot to recovery (TWRP). Here are the steps:
issue the reboot command:
Code:
fastboot reboot
immediately press and hold all three buttons (Pwr+VolUp+VolDown). The tablet might reboot twice. Release all the buttons when you see the TWRP screen, or hear your PC acknowledge that ADB is connected.
load Magisk (step two): flash Magisk. In TWRP:
select "Install"
use "select storage" to locate device you stored magisk.zip on.
press the OK button
select the Magisk zip file
swipe to confirm Flash
when Magisk is finished, hit the "Reboot System" button
finished!
If you prefer to use button combos, rather than fastboot/ADB commands:
Vol Down + Power = fastboot mode
Vol Up + Vol Down + Power = recovery mode
Changelog
Code:
01/03/2023 - bug fix: data partition again backs up and restores correctly
20/01/2023 - add TW_EXTRA_LANGUAGES and TB_X505F_S001149_221115_ROW kernel (credit to @Tonyha7 )
30/12/2022 - add system partition to AdvancedWipe (TB_X505F_S001147_220830_ROW firmware only)
15/11/2022 - TWRP 3.7.0-0 update
- support for TB_X505F_S001147_220830_ROW
18/12/2021 - TWRP 3.6.0-0 update
- support for A12 decryption (keymaster)
27/03/2021 - TWRP 3.5.1-0 update
- change to landscape mode for tablets
01/01/2021 - TWRP 3.5.0-0: initial release
Downloads
TWRP 3.7.0-0 for X505F: twrp-X505F_11.img (for TB_X505F_S001147_220830_ROW and above)
TWRP 3.6.0-0 for X505F: twrp-X505F_11_2021.img (for earlier stock ROMs)
Source code
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
https://github.com/Yahoo-Mike/recovery_device_lenovo_X505F/tree/android-11.0
Credits
The guys at TeamWin Recovery Project.
Everyone whose device trees I plagiarised from GitHub.
Contributors
Yahoo Mike
Tonyha7
Last Updated 2023-03-01 (fix /data backup/restore)
Created 2021-01-01

reserved

Thanks for useful post,
Possible to reboot into recovery from fastboot?

zubair1836 said:
Thanks for useful post,
Possible to reboot into recovery from fastboot?
Click to expand...
Click to collapse
Not that I know of. The bootloader accepts the command fastboot reboot recovery, but boots to system anyway.

Hello there, I've been looking how to install this on my slow tablet for almost like an hour. Could there be some tutorial or extended explanation to the process and installation, I'm such a noob, sorry.

This worked for me. Thank you for your effort and the TWRP!

Worked for me too - many thanks!
Can't wait for a custom ROM!
TWRP Recovery Installation Steps
1. Download android platform tools
2. Unlock developer mode on the M10
3. Enable USB debugging on the M10
3. OEM unlock enable on the M10
4. XDA download TWRP copy to sd
5. Download Magisk app (from Github!!! johnwu), change extension to .zip
6. Adb to fastboot
7. fastboot flash recovery [filename.img]
8. Turn off device
9. Turn on device holding all 3 buttons, release when see Lenovo splash screen
10. In TWRP find Magisk zip
11. Install Magisk
Stock ROM Recovery
1. Download qualcomm drivers 64 bit install
2. Download Lenovo recovery and image tool windows app from Lenovo support website
3. Fastboot oem edl
4. Turn off M10
5. Start recovery windows app, wait till instructions
6. Hold volume up (up is the side of the button closest to the front camera) and insert cable
7. Release button after windows app detects device
8. Troubleshoot by checking windows device manager for the M10 appears as a Qualcomm device

I'm thinking about getting one of these tablets, but before I do so I'd like to know that the screen lock still works after installing TWRP.
This might sound like a crazy question, but my Samsung Tab A won't set a screen lock - pattern, PIN or password - once TWRP has been installed, and I'd rather not run into the same issue again.

Heeni said:
I'm thinking about getting one of these tablets, but before I do so I'd like to know that the screen lock still works after installing TWRP.
This might sound like a crazy question, but my Samsung Tab A won't set a screen lock - pattern, PIN or password - once TWRP has been installed, and I'd rather not run into the same issue again.
Click to expand...
Click to collapse
Confirmed working normally.

zubair1836 said:
Confirmed working normally.
Click to expand...
Click to collapse
Many thanks.

Thank you! TWRP is working fine!
Stupid me flashed before I installed the Android 10 OTA, so I had to temporarily go back to stock recovery. Unfortunately beamingbadger's method didn't work for me.
This is how it worked for me:
Download the OTA via Lenovo's "Rescue And Smart Assistant"
The stock recovery image will be in the Download folder (default path: C:\ProgramData\LMSA\Download\RomFiles) called "recovery.img"
Flash the recovery.img the same way as you would with the twrp img (adb reboot bootloader -> fastboot flash recovery recovery.img)
fastboot reboot
Install OTA
Flash TWRP recovery + Magisk again (follow the steps from the first post, skip bootloader unlock)

The method I use to install OTAs is:
open Magisk App
select "Uninstall Magisk", then the "Restore Images" option
reboot to Android (you will have no root access and stock recovery is restored)
apply OTA
re-flash twrp and install Magisk
NOTE 1: if you've unencrypted your data partition, it will be re-encrypted by this process.
NOTE 2: the new Magisk App (v22) can be installed in TWRP by renaming the *.apk to *.zip. See the new install instructions.

What's involved with running gsi ROMs on this device? It's got the same SoC as my Samsung Tab, which runs them well, so I'm assuming that this tab will also, but I'd like to know if there are any traps that I need to be aware of.

I can partly answer my own question. It all went more smoothly than I expected: installing TWRP, Magisk and then LineageOS R Mod //LiR, followed by Disable_Dm-Verity_enfec.zip.
If I want to try other GSI ROMs, do I need to flash stock before trying another one? I've had some trouble doing that (won't boot) and it's possibly to do with encryption.

Heeni said:
I can partly answer my own question. It all went more smoothly than I expected: installing TWRP, Magisk and then LineageOS R Mod //LiR, followed by Disable_Dm-Verity_enfec.zip.
Click to expand...
Click to collapse
That's great news. Well done.
Heeni said:
If I want to try other GSI ROMs, do I need to flash stock before trying another one? I've had some trouble doing that (won't boot) and it's possibly to do with encryption.
Click to expand...
Click to collapse
On my X605F I do this in twrp for a new GSI install:
format (not wipe) data partition. This is the option where you have to confirm by swiping.
factory reset. This clears the caches.
restore the stock boot and vendor partitions (from a backup I made). This is because Magisk can touch these partitions.
install the GSI system image
install anything else I need like disable_Dm-Verity, Magisk, gapps etc
I don't know what LOS R Mod //LiR does to your system. If it touches any other partitions, you should restore those to stock too.

Thanks for that. It gives me something to go on with. I've downloaded the stock ROM from lolinet, so I can grab the boot and vendor images from that.

I was able to try a couple of other GSI ROMs and I've settled on AndyYan's LineageOS 17.1 for now. The only serious installation issue I had - which I can laugh about in hindsight - was thinking I'd got myself into a very bad bootloop, when all I needed to do was let go of the power button after the Lenovo logo appeared.
On this tablet, there is no navigation capability at all (no navbar, no gestures, no setting to configure them) on installation, and I have to set it using adb. I suspect it goes back to PHH basic ROMs, but I don't feel like doing yet another install and testing right at this moment. Is this happening on the other tablets that you're testing, or is it unique to this one?

I just posted the v3.5.1 update to twrp.
It's also changed to landscape mode, as many of you requested.

Quick question, how do i apply new system updates with twrp installed? Should i not bother? Also, i forgot how to block check for updates!

will this allow flashing of stock roms download from lenovo recovery? ive been stuck on an ancient android 9 version because the ota updater fails.

[ROM][UNOFFICIAL] LineageOS 18.1 for Xperia 10 II [Gcam] [Performance]

{
"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:
#include <std_disclaimer.h>
/*
* 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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 11.x (R),
which is designed to increase performance and reliability over stock Android for your device.
All the source code for LineageOS is available in the LineageOS GitHub repo.
And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Official LineageOS website : http://lineageos.org
About LineageOS Legal : http://lineageos.org/legal/
Important Information
1. This ROM has nothing related to ODM images! So you don't need to ask/install anything like that, just follow the instructions.
2. This ROM support Google Camera (GCam)! You need to flash Gapps at first.
3. You need to flash Stock Android 11 before flashing this ROM.
4. For VoLTE, you need to boot into stock firmware and enable it before flashing this ROM!
5.If you cam from SODP ROMs, you need to go back to official Android 11 firmware, and boot into launcher.
6.This ROM works fo both dual and single models.
Downloads Links
LineageOS 18.1:
Unofficial-build: Link
Recovery: Link
Google Applications (optional):
NikGapps, MindTheGapps. OpenGapps.
Information: Flash the GApps before the first boot. If not, a clean flash is recommended.
Flashing and updating
How to flash
Make sure you upgraded to Official Android 11.0 from Sony
Unlock bootloader is necessary.
Download latest platform-tools from google
1. Install fastbootd drivers, guidance
You can install google's usb debug drivers.
2. Download Lineage Recovery from AFH above.
3. Put your device into fastboot by volume up key.
4. Type the following command to flash the recovery:
Code:
fastboot flash recovery recovery.img
fastboot flash dtbo dtbo.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
fastboot reboot recovery
5. Sideload the ROM package.
6. If you are first time to flash LineageOS, Wipe data plz.
Gapps:
After flashing ROM via siddeload, Reboot to recovery, choose Apply from ADB, then sideload the gapps package on your PC with adb tool:
Code:
adb sideload <PATH OF GAPPS>
Never flash oem from SODP!!
If you flashed oem and meet any issues, I could only say you are a hanhan.
Root access:
Flash Magisk in recovery.
Twrp:
See this: Link
Gcam:
Recommond this one with my xml config.
Notice: You could only switch to front camera from telescope camera in Gcam.
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Share a log of the error with CatLog for example
Also thanks to:
Cubbins
The SDOP team
The LineageOS Team
The CyanogenMod Team
XDA:DevDB Information
Lineage-18.1 for Xperia 10 II, ROM for the Sony Xperia 10 II
Contributors
Sjll
Source Code:
https://github.com/sony-sm6125
Donation
https://paypal.me/sjllls
ROM OS Version: Android 11
ROM Kernel: Linux 4.14
Version Information
Status: Stable
Created 2021-01-16
Last Updated 2021-10-10

FEATURES AND ISSUES
Code:
- Boot: Ok
- Bluetooth: Ok
- WiFi: Ok
- WiFi Hotspot: Ok
- Wireless display: Ok
- RIL - Phone - Data: Ok
- VoLTE: Ok
- GPS: Ok
- Camera: Ok
- Camcorder: Ok
- Lights: Ok
- MicroSD: Ok
- Accelerometer: Ok
- Compass: Ok
- Gyroscope: Ok
- QTI sensors: Ok
- Touchscreen: Ok
- FM Radio: NA
- Fingerprint: Ok
- Vibrator: Ok
- Microphone: Ok
- Audio & music: Ok
- Bluetooth audio: Ok
- NFC: Not tested
- Kernel: Ok
- Graphics: Ok
- 3D Rendering: Ok
- Clock: Ok
- DRM: Widewine L3
- Offline Charging: Ok
- USB: Ok
- USB Tethering: Ok
- USB OTG: Ok
- Encryption: Ok
- SEPolicies: Enforce

Reserved

Will it work on the dual SIM version XQ-AU52?

ig2205 said:
Will it work on the dual SIM version XQ-AU52?
Click to expand...
Click to collapse
Of course.

i wish we can have it for our xperia 5ii lol

Any way of upgrading to this (ie dirty flashing) from your LineageOS 17.1 version? Or is it necessary to wipe and reinstall stock Android 10 first?

dreDREb13 said:
Any way of upgrading to this (ie dirty flashing) from your LineageOS 17.1 version? Or is it necessary to wipe and reinstall stock Android 10 first?
Click to expand...
Click to collapse
Flash directly, if you don't meet any issue, there is no need to wipe the data.
flyl0 said:
i wish we can have it for our xperia 5ii lol
Click to expand...
Click to collapse
Coming.

Sjll said:
Flash directly, if you don't meet any issue, there is no need to wipe the data.
Coming.
Click to expand...
Click to collapse
It would be even better Resurrection Remix
But I'm glad LOS 18.1 is coming, can't wait to try it!

Sjll said:
Flash directly, if you don't meet any issue, there is no need to wipe the data.
Click to expand...
Click to collapse
Sweet. This is great work, thanks so much!
Does the flashing have to be done through fastboot via the method described for initial install, or can adb sideload be used to install the zip package via recovery as an update instead?

erasing 'metadata'...
FAILED (remote: Erasing is not allowed for partition)
...
sending sparse 'system' 1/2
OKAY [ 21.700s]
writing 'system' 1/2...
FAILED (remote: No such partition.)
I have that every time. What to do in fastbootd mode?

dreDREb13 said:
Sweet. This is great work, thanks so much!
Does the flashing have to be done through fastboot via the method described for initial install, or can adb sideload be used to install the zip package via recovery as an update instead?
Click to expand...
Click to collapse
OTA package will remove vendor partition, I will provide OTA package until building vendor image Then we will go LineageOS official.
ig2205 said:
erasing 'metadata'...
FAILED (remote: Erasing is not allowed for partition)
...
sending sparse 'system' 1/2
OKAY [ 21.700s]
writing 'system' 1/2...
FAILED (remote: No such partition.)
I have that every time. What to do in fastbootd mode?
Click to expand...
Click to collapse
You should be in fastboot mode and not fastbootd mode,
If you are really in fastbootd mode and not work, try fastbootd mode in official recovery image.

Will this rom be rebased on the Android 11 stock ROM sources once we have them?

You should be in fastboot mode and not fastbootd mode,
If you are really in fastbootd mode and not work, try fastbootd mode in official recovery image.
Now it looks like this and I don't know whether to continue doing something?

KriiXOne said:
Will this rom be rebased on the Android 11 stock ROM sources once we have them?
Click to expand...
Click to collapse
Maybe, stock 10 blobs works fine on LineageOS 18.1. A
ig2205 said:
You should be in fastboot mode and not fastbootd mode,
If you are really in fastbootd mode and not work, try fastbootd mode in official recovery image.
Now it looks like this and I don't know whether to continue doing something?
Click to expand...
Click to collapse
LineageOS or stock Recovery?
If LineageOS Rec is broken, try stock rec plz.
BTW, also use latest adb fastboot tools from google.
FastbootD driver is also necessary.

Just wondering, how's the camera performance (in terms of start-up and focus speeds) in these custom ROM's compared to stock? Getting rather annoyed by the performance of the stock ROM / camera app.

Sjll said:
Maybe, stock 10 blobs works fine on LineageOS 18.1. A
LineageOS or stock Recovery?
If LineageOS Rec is broken, try stock rec plz.
BTW, also use latest adb fastboot tools from google.
FastbootD driver is also necessary.
Click to expand...
Click to collapse
The problem is with stock recovery.
I installed a new system, drivers, reinstalled programs, changed usb sockets and nothing. I have no idea anymore.

ig2205 said:
The problem is with stock recovery.
I installed a new system, drivers, reinstalled programs, changed usb sockets and nothing. I have no idea anymore.
Click to expand...
Click to collapse
Run
Code:
fastboot getvar all
Post the result here plz.

Sjll said:
Run
Code:
fastboot getvar all
Post the result here plz.
Click to expand...
Click to collapse
Is that the point?

So I installed and everything booted up fine, but I hit a couple snags.
One, it looks like Open GApps hasn't officially released Android 11.0 builds yet, so I had to find test versions through their sourceforge to run.
Two, upon booting I'm having trouble using a third party launcher (KISS Launcher) with gesture navigation. For some reason it won't recognize the multitasking/return to home feature along the bottom, though the side gestures work fine. Not sure if that's something to do with the test builds of GApps or not. I made sure all gestures were turned off to check if maybe it's a conflict but it still didn't work. And the launcher ran just fine on my 17.1 install, so not sure what the issue is.
Three, my wallpaper that I have set to the correct resolution of the phone is now zoomed in slightly. It looks like this is a feature of the new notification shade, as when I pull it down it zooms out my wallpaper to the correct size. However, I can't seem to find a way of turning this feature off or getting my wallpaper to fit properly.
EDIT: I rebooted again after first boot and my issues with the third party launcher and gesture navigation went away. After looking into it more it looks like that wallpaper zoom feature is apparently baked in to Android 11, so no way of disabling that at the moment. Hopefully there's a change that can come in to remove that feature...
All looks good otherwise and this is turning out great!

[Guide][SM-T500] Galaxy Tab A7 10.4 - Flash LineageOS or any other GSI rom.

These are instructions to flash LineageOS 18.1 GSI builds on our SM-T500. The same instructions should work for any other GSI rom out there.
Some instructions here, like flashing an empty product.img and resizing system partition, are not necessary if you want to flash a rom that fits in system and bundles gapps with it.
Prerequisites:
* SM-T500 with BUJ1 FW
* Unlocked bootloader
* Verified Boot disabled
* TWRP installed
* fastboot and adb installed on your computer.
Step 1: boot to fastboot.
Boot in TWRP and press "reboot" -> "fastboot". Wait until the tablet reboots and, after a few seconds, check that you can see your device with
Code:
fastboot devices
Now flash product.img and system.img and resize system image to the entire available size of the super partition:
Code:
fastboot flash product product.img
fastboot erase system
fastboot flash system lineage-18.1-20211214-UNOFFICIAL-treble_arm64_bvS-vndklite.img
fastboot resize-logical-partition system 3940000000
fastboot reboot recovery
Step 2: back in recovery
We need to resize the logical system partition to take up all the space we asigned to it. That's only mandatory if you want to flash gapps later on. If your rom comes with gapps bundled you don't need to do this.
Code:
adb shell
mount /dev/block/bootdevice/by-name/system /system_root
umount /system_root
e2fsck -f /dev/block/bootdevice/by-name/system
resize2fs /dev/block/bootdevice/by-name/system 961915
Step 3: finish it
Now you need to go to "wipe" -> "format data" and confirm. After that you can flash gapps if you want. You must use MindTheGapps arm64 version.
If you choose to flash gapps you'll need to follow https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)#how-to-bypass-certified-device-after-first-boot
Some stuff won't work out of the box (brightness, MTP, bluetooth or wired audio). Please see the next post to learn how to workaround these issues.

Known issues (and workarounds)
1. MTP doesn't work
You need to flash SM-T500-GSI-kernel.zip from TWRP. Do it only once unless you reverted back to stock boot.img.
2. The rom I've flashed (mostly PixelExperience) reboots after a few seconds/minutes
You need to flash SM-T500-GSI-kernel.zip from TWRP. Do it only once unless you reverted back to stock boot.img.
3. Brightness doesn't work
You need to flash SM-T500-GSI-brightness-fix.zip from TWRP. You need to repeat this again after flashing a new system.img with the same or different rom.
4. Audio doesn't work via bluetooth/jack headphones.
Follow the AUDIO FIX section of https://forum.xda-developers.com/t/...s-nairo-and-some-post-install-tweaks.4364963/, as suggested by @wesleyvanneck12345678
* kernel sources: https://github.com/pazos/android_kernel_samsung_gta4lwifi/

FAQ
Q: Which GSI variant should I choose?
A: arm64 ab. Use the vndklite variant if you want to flash gapps or fix the brightness.
Q: Do I need to format data after flashing a different ROM?
A: YES
Q: Do I need to format data after flashing a different version of the same ROM?
A: Most likely YES, but you can try without formatting and see if it boots.
Q: Do gapps survive rom changes (diffent versions of the same rom or different roms)?
A: NOPE. You need to flash them again.
Q: Do GSI roms work with Magisk?
A: They should if they're based on PHH builds and are up-to-date.
Q: How to bypass SafetyNet?
A: I don't know, I don't care.

Reserved

Thank you very much for this guide, this really opens things up for thre A7 as far as custom roms go. I do like the OneUI 3.1 on this tablet, however I find I don't use much of the OneUI specific features. An AOSP/Lineage build should be lighter on resources and storage.
I do have a question, when you do "fastboot flash product product.img", where exactly do you get the poroduct.img from? Is this somewhere in the stock firmware or do I find it elsewhere?
Thanks again!

Whoops, sorry. I forgot to attach it here. It is already attached in https://forum.xda-developers.com/t/...xy-tab-a7-10-4-sm-t500.4371123/#post-86050459, so you can pick it up from there if you're in a hurry. If not I will add it to OP.

All done! I'm now running the LineageOS 18.1 version you mentioned in the directions. So far so good, however after flashing both the brightness fix and the GSI kernel, I am still unable to control brightness and I do not have MTP. Just to clarify, I install both of these zips via the TWRP menu, correct?
One other thing that I've noticed is that the tablet does not sleep when closing the Samsung Book cover like it does in the stock OneUI. I wonder if a magisk or LSposed module could helo us out here?

paziusss said:
These are instructions to flash LineageOS 18.1 GSI builds on our SM-T500. The same instructions should work for any other GSI rom out there.
Some instructions here, like flashing an empty product.img and resizing system partition, are not necessary if you want to flash a rom that fits in system and bundles gapps with it.
Prerequisites:
* SM-T500 with BUJ1 FW
* Unlocked bootloader
* Verified Boot disabled
* TWRP installed
* fastboot and adb installed on your computer.
Step 1: boot to fastboot.
Boot in TWRP and press "reboot" -> "fastboot". Wait until the tablet reboots and, after a few seconds, check that you can see your device with
Code:
fastboot devices
Now flash product.img and system.img and resize system image to the entire available size of the super partition:
Code:
fastboot flash product product.img
fastboot erase system
fastboot flash system lineage-18.1-20211214-UNOFFICIAL-treble_arm64_bvS-vndklite.img
fastboot resize-logical-partition system 3940000000
fastboot reboot recovery
Step 2: back in recovery
We need to resize the logical system partition to take up all the space we asigned to it. That's only mandatory if you want to flash gapps later on. If your rom comes with gapps bundled you don't need to do this.
Code:
adb shell
mount /dev/block/dm-0 /system_root
umount /system_root
e2fsck -f /dev/block/dm-0
resize2fs /dev/block/dm-0 961915
Step 3: finish it
Now you need to go to "wipe" -> "format data" and confirm. After that you can flash gapps if you want. You must use MindTheGapps arm64 version.
If you choose to flash gapps you'll need to follow https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)#how-to-bypass-certified-device-after-first-boot
Some stuff won't work out of the box (brightness, MTP, bluetooth or wired audio). Please see the next post to learn how to workaround these issues.
Click to expand...
Click to collapse
paziusss said:
These are instructions to flash LineageOS 18.1 GSI builds on our SM-T500. The same instructions should work for any other GSI rom out there.
Some instructions here, like flashing an empty product.img and resizing system partition, are not necessary if you want to flash a rom that fits in system and bundles gapps with it.
Prerequisites:
* SM-T500 with BUJ1 FW
* Unlocked bootloader
* Verified Boot disabled
* TWRP installed
* fastboot and adb installed on your computer.
Step 1: boot to fastboot.
Boot in TWRP and press "reboot" -> "fastboot". Wait until the tablet reboots and, after a few seconds, check that you can see your device with
Code:
fastboot devices
Now flash product.img and system.img and resize system image to the entire available size of the super partition:
Code:
fastboot flash product product.img
fastboot erase system
fastboot flash system lineage-18.1-20211214-UNOFFICIAL-treble_arm64_bvS-vndklite.img
fastboot resize-logical-partition system 3940000000
fastboot reboot recovery
Step 2: back in recovery
We need to resize the logical system partition to take up all the space we asigned to it. That's only mandatory if you want to flash gapps later on. If your rom comes with gapps bundled you don't need to do this.
Code:
adb shell
mount /dev/block/dm-0 /system_root
umount /system_root
e2fsck -f /dev/block/dm-0
resize2fs /dev/block/dm-0 961915
Step 3: finish it
Now you need to go to "wipe" -> "format data" and confirm. After that you can flash gapps if you want. You must use MindTheGapps arm64 version.
If you choose to flash gapps you'll need to follow https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)#how-to-bypass-certified-device-after-first-boot
Some stuff won't work out of the box (brightness, MTP, bluetooth or wired audio). Please see the next post to learn how to workaround these issues.
Click to expand...
Click to collapse
I've tried this from both a Win11 and a Mint 20.2 box and get the same errors. The resize-logical-partition cmd unknown command and the fastboot reboot recovery says unknown target.

USE TWRP 3.6 from
[RECOVERY][UNOFFICIAL]TWRP 3.6.0 for 2020 Galaxy Tab A7 10.4[SM-T500]
/* * Disclaimer * * Your warranty is now void. * * We're 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...
forum.xda-developers.com
You need a recent version of fastboot too. Get one

NeilR2 said:
All done! I'm now running the LineageOS 18.1 version you mentioned in the directions. So far so good, however after flashing both the brightness fix and the GSI kernel, I am still unable to control brightness and I do not have MTP. Just to clarify, I install both of these zips via the TWRP menu, correct?
One other thing that I've noticed is that the tablet does not sleep when closing the Samsung Book cover like it does in the stock OneUI. I wonder if a magisk or LSposed module could helo us out here?
Click to expand...
Click to collapse
MTP is disabled by default. You need to plug the tablet to your computer, go to the "slightly" hidden notification and select transfer files instead of the default "charge only".
Agree with the brightness thing. I will upload a new version when I have a minute. It should be placed in rw-system.sh, not in phh-on-boot.sh.
Thanks for the feedback on the sleepcover stuff. I think lineage has a package that does that job, maybe it isn't included on this build. No idea if you can handle it using magisk or hoking into zygote process, I guess not.

I've finally succeeded in flashing LOS 19 and doing all of the resizing bit. Final step is getting gapps flashed. The recommendation I saw was to use MindTheGapps. The closest one I could find was MindTheGapps-11.0.0-arm64-20210920_084011.zip and it didn't work. It said is was for LOS 18 "or higher". Is there one for LOS 19?

I would like to point out that my system_root partition is /dev/block/dm-1 and not /dev/block/dm-0... I have wondered if this was due to differing recoveries however I am using your latest recovery and it is the same for me... so I would suggest that others do:
Bash:
adb shell
cat /tmp/recovery.log
That will show which one system_root is located at then you can continue with the resize.. otherwise it will give an error saying there arent enough blocks...

ragarcia87 said:
I would like to point out that my system_root partition is /dev/block/dm-1 and not /dev/block/dm-0
Click to expand...
Click to collapse
Thanks!! Never thought about it . Fixed!

Would porting ubports be possible for this device?

paziusss said:
Known issues (and workarounds)
1. MTP doesn't work
You need to flash SM-T500-GSI-kernel.zip from TWRP. Do it only once unless you reverted back to stock boot.img.
2. The rom I've flashed (mostly PixelExperience) reboots after a few seconds/minutes
You need to flash SM-T500-GSI-kernel.zip from TWRP. Do it only once unless you reverted back to stock boot.img.
3. Brightness doesn't work
You need to flash SM-T500-GSI-brightness-fix.zip from TWRP. You need to repeat this again after flashing a new system.img with the same or different rom.
4. Audio doesn't work via bluetooth/jack headphones.
Follow the AUDIO FIX section of https://forum.xda-developers.com/t/...s-nairo-and-some-post-install-tweaks.4364963/, as suggested by @wesleyvanneck12345678
* kernel sources: https://github.com/pazos/android_kernel_samsung_gta4lwifi/
Click to expand...
Click to collapse
I flashed both the kernel and brightness zips but brightness slider still does nothing.

Juppy99 said:
Would porting ubports be possible for this device?
Click to expand...
Click to collapse
Someone please corrent me if I am wrong, but I think the stock kernel needs to have Halium patches applied to it for UbPorts to work. I am not sure what exactly is involved in doing this, but I believe that it is possible. Though that does not mean it will not have bugs without major work being done beyond patching the kernel.

lewmur said:
I flashed both the kernel and brightness zips but brightness slider still does nothing.
Click to expand...
Click to collapse
paziusss said:
For now you can get it working with just 3 commands, until you reboot your device:
Click to expand...
Click to collapse
paziusss said:
adb shell
su
echo 100 > /sys/class/backlight/panel0-backlight/brightness
Click to expand...
Click to collapse
This from the TWRP thread works, the zip didn't. I use Tasker to run the script every boot.

paziusss said:
d confirm. After that you can flash gapps if you want. You must use MindTheGapps arm64 version.
If you choose to flash gapps you'll need to follow https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)#how-to-bypass-certified-device-after-first-boot
Some stuff won't work out of the box (brightness, MTP, bluetooth or wired audio). Please see the next post to learn how to workaround these issues.
Click to expand...
Click to collapse
The get info apk in that link doesn't work in LOS 19. Does anyone know of one that will? Or of another way to get the GFW id?

this is cool, thanks op.....worked a doddle on arch linux, after I followed your instructions for installing TWRP using heimdall
thanks again, u da man! hope you have a happy and prosperous 2022

Tirofog said:
This from the TWRP thread works, the zip didn't. I use Tasker to run the script every boot.
Click to expand...
Click to collapse
Sorry, could you explain better how you set up tasker for that? I can't seem to manage to do it. I 've read somewhere that tasker might have problems with sudo commands... thank you!