Database Develop

Help! Please

Guys please help. ok
i had oxygenos installed, i flashed resurrection remix, now its asking for a password upon boot... the password was 6432 but wheni input that password, it doesnt let me enter. i have personal photos and stuff on there i need please someone help me

Reinstall oficial recovery, and reinstall twrp (blue spark recomanded)
Trimis de pe al meu ONEPLUS A3003 folosind Tapatalk

Use the unbrick tool i have faced this problem when trying to install Miui however this tool bring you back to marshmallow bootloader locked with stock recovery.

I am a little confused I don't know if the password is being requested in TWRP or when android has booted already. For the 1st scenario you could try the default password 0000 if the issue is when android has already booted try the procedure described below.
1. Go to TWRP recovery
2. Go to Advanced / File manager
3. Navigate to data/system
4. Erase the following files in that folder
- password.key
- pattern.key
- locksettings.db
- locksettings.db-shm
- locksettings.db-wal
Don't worry if you don't see any of those files in the folder, just delete the ones you do see. Reboot your device and you will be able to start android normally.

Move this thread to guides and discussion section. It is confusing for others.

[GUIDE] [Z2 FORCE XT1789-05] Moving Motorola Z2 Force to Project Treble ROMs

What is Google’s Project Treble?
You should read here some Frequently Asked Questions (FAQ) thanks to Recognized Developer @phhusson
This is an index for (all) Treble Projects or also Generic System Image (GSI) list.
This is the known compatible device list.
This is a Guide to build Project Treble GSI ROMs from source
Motorola Z2 Force is NOT a Project Treble compatible device, but it IS a semi-compatible. This means that you can move toward Treble ROMs with some previous steps.
Moving from Lineage 15.1 toward Oreo Treble ROMs
1. Unlock your bootloader or, if it is already unlocked, you can, optionally, download and use a flashall solution to turn back to stock if necessary.
2. Flash and boot Lineage ROM 15.1. Here you have guides to do it. Better if you flash to both slots (changing between then via fastboot set_active other command. This is necessary to get boot and vendor partitions compatible with Treble images.
3. Backup everything you need (see step n.6 below).
4. Remove PINs, passwords, fingerprints.
Now you can follow the default flashing GSI procedures:
1. Download an Android 8.1 (Oreo) Treble system image (ARM 64 with partition type A/B in our case) and move it to phone sdcard (or external one).
2. Remove all PIN, password, fingerprint security and allow USB Debugging.
3. Uninstall Magisk and reboot the phone. Then reboot again into bootloader.
4. Boot (not flash) TWRP Treble (via fastboot boot <twrp.img file name>)
5. Flash the downloaded Treble system image.
6. Flash Open GApps (Platform ARM64, Android 8.1) (if the GSI image does not include them).
7. Factory reset (or wipe data, Dalvik and cache partitions). You'll lose all your data.
8. Boot the phone and set it up, allowing USB Debugging.
9. Boot TWRP image file and then flash zip file it to make it permanent.
10. Reboot into flashed TWRP (mandatory).
11. Flash Magisk and reboot.
Know issues - Oreo
1. So-called "Technicolor" bug when moving into or out dark mode, or when using Substratum themes, when icons and the screen got weird colors effects and stripes. Generally, you could boot into recovery and wipe Dalvik/Cache.
2. ViPER4Android not always compatible with Treble.
3. VoLTE.
Moving from Lineage 15.1 toward Pie Treble ROMs
1. Requirements: have an Oreo Treble ROM already running.
2. Download an Android 9.0 (Pie) Treble system image (ARM 64 with partition type A/B in our case) and move it to phone sdcard (or external one).
3. Remove all PIN, password, fingerprint security and allow USB Debugging.
4. Uninstall Magisk and reboot the phone. Then reboot again into bootloader.
5. If you do not have TWRP yet, flash TWRP image via fastboot flash <twrp.img file name>
6. Reboot into TWRP.
7. Flash the downloaded Treble system image.
8. Flash Open GApps (Platform ARM64, Android 9) (if the GSI image does not include them).
9. Check if vendor partition is mounted via TWRP. If not, mount it.
10. Flash POST-sGSI 3 zip file. More info here.
11. Reflash TWRP.
12. Factory reset (or wipe data, Dalvik and cache partitions). You'll lose all your data (not sdcard).
13. Boot the phone and set it up, allowing USB Debugging. Reboot into TWRP.
14. Flash Magisk and reboot.
Old method:
1-9: The same as above.
10. Flash POST-sGSI zip files -1- and -2-.
11. Flash the Permissiver zip.
12. Factory reset (or wipe data, Dalvik and cache partitions). You'll lose all your data (not sdcard).
13. Boot the phone and set it up, allowing USB Debugging. If you can't boot, return to TWRP, flash/sideload the FBE_Disabler zip and wipe data as stated here. In this last case, you'll lose all your data including sdcard.
14. Flash Magisk and reboot.
Know issues - Pie
1. Message on each boot: "Android System: There's an internal problem with your device. Contact your manufacturer for details". Solution proposed by @palbadi. In details, fix for vendor mismatch popup:
A. In a root file manager, backup both \vendor\build.prop and \system\build.prop files.
B. Open \system\build.prop original file with a root text editor. Copy the line with ro.build.fingerprint variable, for instance:
Code:
ro.build.fingerprint=Android/treble_arm64_bvN/phhgsi_arm64_ab:9/PQ1A.181105.017.A1/64:userdebug/test-keys
C. Open \vendor\build.prop original file with a root text editor. Find the the line with ro.build.fingerprint variable, for instance:
Code:
ro.vendor.build.fingerprint=motorola/nash/nash:8.0.0/OPXS27.109-34-10/5:user/release-keys
D. Paste the copied system variable over the vendor one (replace).
E. Save the \vendor\build.prop file.
F. Reboot.
2. ViPER4Android not always compatible with Treble.
3. VoLTE.
4. The combination of TWRP + Magisk could let you without WiFi. You can try not flashing TWRP in any steps above, just booting it: fastboot boot <twrp.file.name>.img
Moving from Lineage 16 toward Pie Treble ROMs
1. Requirements: have Lineage 16 (Pie) already running.
2. Download an Android 9.0 (Pie) Treble system image (ARM 64 with partition type A/B in our case) and move it to phone sdcard (or external one).
3. Remove all PIN, password, fingerprint security and allow USB Debugging.
4. Uninstall Magisk (if you have it) and reboot the phone. Then reboot again into bootloader.
5. If you do not have TWRP yet, flash TWRP image via fastboot flash <twrp.img file name>
6. Reboot into TWRP.
7. Flash the downloaded Treble system image.
8. Flash Open GApps (Platform ARM64, Android 9) (if the GSI image does not include them).
9. Factory reset (or wipe data, Dalvik and cache partitions). You'll lose all your data (not sdcard).
10. Boot the phone and set it up, allowing USB Debugging. Reboot into TWRP.
11. Flash Magisk and reboot.
Know issues - Pie
1. Message on each boot about Vendor is not up-to-date.
2. ViPER4Android not always compatible with Treble. There is a solution here.
3. VoLTE.
4. The combination of TWRP + Magisk could let you without WiFi. You can try not flashing TWRP in any steps above, just booting it: fastboot boot <twrp.file.name>.img
5. If anytime you lost Wi-Fi (or your Mac address become 02:00:00:00:00:00), see this post.
Support
Discord support channel.
XDA Treble-Enabled Device Questions and Answers.
XDA Treble-Enabled Device Guides, News, & Discussion.
Treble-Enabled ROMs Development.

Muchas gracias por tu apoyo, estaba buscando esta información después de ver los links en tu firma
Google translate
Thank you very much for your support, I was looking for this information after seeing the links in your signature

Thank you. I wish I'd seen this a few days ago, I was trying to get a treble gsi running, but had a hell of a time figuring out what I was doing wrong, turns out there were several thing. I do have one question though, you say as step 4 in moving towards pie to flash twrp. I'm assuming you mean just boot it and not flash? If my assumption is incorrect, which zip did you flash? As there isn't one for treble twrp.

asislife20 said:
Thank you. I wish I'd seen this a few days ago, I was trying to get a treble gsi running, but had a hell of a time figuring out what I was doing wrong, turns out there were several thing. I do have one question though, you say as step 4 in moving towards pie to flash twrp. I'm assuming you mean just boot it and not flash? If my assumption is incorrect, which zip did you flash? As there isn't one for treble twrp.
Click to expand...
Click to collapse
Only boot it from the TWRP that used for flash LineageOS

asislife20 said:
Thank you. I wish I'd seen this a few days ago, I was trying to get a treble gsi running, but had a hell of a time figuring out what I was doing wrong, turns out there were several thing. I do have one question though, you say as step 4 in moving towards pie to flash twrp. I'm assuming you mean just boot it and not flash? If my assumption is incorrect, which zip did you flash? As there isn't one for treble twrp.
Click to expand...
Click to collapse
I have changed the guide and added link. Is it clear now? Thanks.

omnismart said:
Muchas gracias por tu apoyo, estaba buscando esta información después de ver los links en tu firma
Google translate
Thank you very much for your support, I was looking for this information after seeing the links in your signature
Click to expand...
Click to collapse
hola podrias ayudarme a hacer esto en mi dispositivo por favor...

AlucardMemnoch said:
hola podrias ayudarme a hacer esto en mi dispositivo por favor...
Click to expand...
Click to collapse
Aún no me muevo a esta rom, he estado un poco ocupado y requiere respaldar toda la memoria interna para evitar problemas, eso me implica depurar whatsapp.
Revisa el siguiente enlace, tal vez y te ayude un poco por si tienes algún problema y quieras volver a stock.
I still do not move to this rom, I've been a bit busy and requires backup all internal memory to avoid problems, that means I debug whatsapp.
Check the [URL = "https://www.htcmania.com/showpost.php?p=29253595&postcount=2"] next link [/ URL], maybe and it will help you a bit in case you have a problem and you want to go back to stock

Flashed PE 9 img (PE-AB-2018-09-20) instead of 8 over lineage-15.1-20181009-nightly-nash-signed.zip by mistake.... and it happened to be ok ))
So far everything works fine ....
Maybe it's time to optimize Guide?

pakhan8 said:
Maybe it's time to optimize Guide?
Click to expand...
Click to collapse
In which point?

Technical said:
In which point?
Click to expand...
Click to collapse
I think he means the need to first install an 8.1 GSI rom before doing a 9 (Pie) GSI?

CykloneFij said:
I think he means the need to first install an 8.1 GSI rom before doing a 9 (Pie) GSI?
Click to expand...
Click to collapse
Well, I never said that. Anyway, I've updated the guide to make it clear the movement from Lineage 15.1 toward Oreo or Pie.

Does Moto Mods work?
Hello, I would like to know if Moto Mods work with this project. Thank you in advance for your attention.

Pedro Gomes said:
Hello, I would like to know if Moto Mods work with this project. Thank you in advance for your attention.
Click to expand...
Click to collapse
Yes, in theory, all mods work. Some controls and apps (and their functions) could not, though.
You can always test and revert to stock if you want

Technical said:
Yes, in theory, all mods work. Some controls and apps (and their functions) could not, though.
You can always test and revert to stock if you want
Click to expand...
Click to collapse
Okay, thanks for the reply. The warranty on my z2 force is over, so I'll risk installing it following your tutorial. The z2 force is more complicated, but with a little patience I think it will work ...

Latest magisk 17.1 leads to "no wifi and no mobile internet" on pie PixelExperience 9 img (PE-AB-2018-09-20)
Does anybody know how to solve it?

did you get the magisk wifi issue sorted out?

McRoberts said:
did you get the magisk wifi issue sorted out?
Click to expand...
Click to collapse
No. I've tested Magisk v17, beta and also older versions (16.7).

anyone tried and make it work successfully with this guide to follow ?
i check all the replies but no one seem to come back and claim it work .
if you are the one pls let me know , thank you.

fisummer said:
anyone tried and make it work successfully with this guide to follow ?
i check all the replies but no one seem to come back and claim it work .
if you are the one pls let me know , thank you.
Click to expand...
Click to collapse
Yes. it works

mattlowry said:
Yes. it works
Click to expand...
Click to collapse
thanks bro,i really appreciated for your comfirmation.

SOLVED: Flashing Magisk results in Error1: Cannot mount /vendor

I've a Redmi 4a(Rolex) and flashing Magisk results in Cannot mount /vendor
I've started with AOSP Extended but flashing Failed. Searched online to see I must try different ROM, so I switched to Lineage OS15.1 and again Failed. Finally tried with Resurrection Remix but again Failed. Researching more someone suggested to flash boot.img separately but again failed. I'm using TWRP but that can't be the problem as currently I'm on latest version-3.2.3.0
Please help me with this. Or there must be an update to the current Magisk as I see there are many like me. I've also tried different versions of Magisk. I think John Wu (@topjohnwu) must bring an update fixing this problem
Code:
- Mounting /system, /vendor
! Cannot mount /vendor
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v17.zip'
Read Solution Here: https://freaksterism.blogspot.com/2018/10/solved-cannot-mount-vendor-magisk.html

smurfisrael03 said:
I'm using TWRP but that can't be the problem as currently I'm on latest version-3.2.3.0
Click to expand...
Click to collapse
If the TWRP you have installed isn't Treble compatible it doesn't matter if you use the latest version.
Search "cannot mount /vendor" in the Magisk forum and you'll find several threads about it, and that using a compatible TWRP is usually the solution.

Failed
Didgeridoohan said:
If the TWRP you have installed isn't Treble compatible it doesn't matter if you use the latest version.
Search "cannot mount /vendor" in the Magisk forum and you'll find several threads about it, and that using a compatible TWRP is usually the solution.
Click to expand...
Click to collapse
Installed Redwolf Recovery (Treble based) still stuck at the same Fail message---> Cannot mount /vendor
I've searched and tried lots of steps only to fail

Solution:
smurfisrael03 said:
Installed Redwolf Recovery (Treble based) still stuck at the same Fail message---> Cannot mount /vendor
I've searched and tried lots of steps only to fail
Click to expand...
Click to collapse
Okay, So after researching more I got to this link and installed treble based TWRP with /vendor partition:
I don't have 10 posts yet https:// androidfilehost.com/ ?w=file-thanks&fid=818222786056029479&mid=219&download_id=258ad41ee871813957ac9d0b5e669487&tid=1538008115&hc=091581d460197eb7735e89a53540a61fee748ea5e16661bfbf5e05f0cfaaaf32
NOTE: I've Remdi 4A(Rolex) and Treble based ROM(AOSP Extended, RR,Lineage 15.1 --> I've tried all these and they work)
Finally Installed Magisk and Rooted my Redmi 4A

Guys cab you please help? i have the same problem with vendor on mi max 2, what twrp do you advising me to download?

No its not thath the solution.... i tried it many times..

Noexcusses said:
No its not thath the solution.... i tried it many times..
Click to expand...
Click to collapse
Yes it is
You need a TWRP that has correct mount points for /vendor. It's not magisk

yo tengo el mismo problema, al pasar de rr6 a rr7 en xiaomi mi max 2, no me flashea magisk manager, ni version 18.0 ni version 18.1 beta, error 1 siempre, ni a traves de adb sideload ni con twrp, ya no se como rootear esta version de resurrection remix 9.0 PIE, y son dias leyendo hilos pero no lo consigo, gracias por leerme . un saludo.

bandido**** said:
yo tengo el mismo problema, al pasar de rr6 a rr7 en xiaomi mi max 2, no me flashea magisk manager, ni version 18.0 ni version 18.1 beta, error 1 siempre, ni a traves de adb sideload ni con twrp, ya no se como rootear esta version de resurrection remix 9.0 PIE, y son dias leyendo hilos pero no lo consigo, gracias por leerme . un saludo.
Click to expand...
Click to collapse
English please

Magisk

Well hi to rooted user...im in 2020....for those who r searching for the answer on how to fix the problem twrp recovery error 1 on installing magisk....
1. Youll have to find the current os zip file that ur using...
2. extract the bot.img
3. open TWRP then select flash img and choose the bot.img and flash it
4. Then select to flash zip N flash the magisk...
5. Done :fingers-crossed:
Sorry for my bad language
Feel free to ask me

What's that os zip file you are referring to?

jogoh said:
What's that os zip file you are referring to?
Click to expand...
Click to collapse
He means the custom ROM zip file that you've downloaded to flash to your phone.
In other words, to take the original unmodified boot.img from whichever ROM you're using or plan to install, flash that boot image via recovery so as to replace the currently modified boot partition which may be causing Error -1, and once that completes flash Magisk installer zip and let it run the boot image patching process on a clean slate.
It might work. But the issue can also just be the version of the recovery image simply doesn't support Treble. It's happened to me but usually the missing vendor partition doesn't throw an error -1 fail for flashing Magisk, so it may indeed be a corrupt boot image issue and not just TWRP.

In my case, flashing a readmi 5A compatible treble zip via TWRP solved the issue. I dont' know if I am allowed to post an url, but everything I needed I found here (Redmi 4A & 5A users only): "xiaomifirmware.com/roms/project-treble-rom-for-xiaomi-redmi-4a-5a-unified/" (just add the h t t p s protocol before it).

[Guide] [SM-T515] android 9 Install custom ROM'S and ROOT

SIZE="6"]Use this guide if your tablet is running on android 9. Android 10 is not covered in this guide[/SIZE]
Instructions:
Code:
* READ EVERTHING BEFORE YOU START OR ASK QUESTIONS
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard & a lot. :D
I’m not an expert, I’ve just put some pieces together to achieve the following.
If you have problems, I’m not sure if I’m able to help you
You need to have some basic knowledge
Always have the correct software and backup all your data.
o Also download before you start the stock files, so that you are able to quickly reverse everything via: sammobile
Remember to backup your data!!!!
If you have trouble and the tablet is not working flash the firmware which you’ve downloaded via odin
Working ROMS (Which I’ve tested so far):
IF you want to install a custom ROM, you need to choose the correct custom ROM
Choose the ARM 32-bit with 64-bit binder AB (also known as A64B).
LineageOS 17.x GSI here
Legion ROM GSI here
From OEM stock firmware:
Download TWRP https://forum.xda-developers.com/ga...rp-3-3-1-2019-galaxy-tab-10-1-t3934805/page35
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
Check if OEM unlock is enabled in the developer settings (it should be enabled and greyed out) IF so yeey you did It. If not start over.
Install custom ROM:
Well installing a custom Rom is quite easy .
Download a GSI ROM you like and put it on a SD cart
Go into TWRP
Select “install”
Click on “install image”
Click the on the ROM
In the next screen where we need to select the partition, select the “System Image”
Swipe to confirm
If you want ROOT and or install GAPPS follow the extra steps bellow. If NOT, just reboot the system
Extra’s install MAGISK and or install GAPPS
First of all download the files you want.
Magisk: here
GAPPS: here
You want root? You need to prepare the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. Which we can prepare and flash after you finished the setup of the tablet. You need more info check the following: link
Go back to the TWRP home screen
Select “Wipe”
Select advanced wipe
Check “system”
Click on “repair or change file system”
Click on “resize file system” (if you’ve receive an error, don’t worry just do It again).
o You should see “resizing… done.”
Go back to the TWRP home screen
Select “install”
Select the zip file(‘s) you want and flash them
o IF you receive an error if you want to install the GAPPS zip like “not enough space” go back and resize the system partition
o IF you receive an errro if you want to install Magisk, go back and resize the system partition
Remove “dalvik and cache”
Reboot system
Setup your tablet
Now for the last step to root the tablet all the way
Go into Magisk manager
On the Magisk dashboard you’ve should see that you have the latest version of magisk. Press on the “install” button at the right side
o Select “Select and Patch a File” select the TWRP IMG you still have on the SD card
o Magisk should create a “magisk_patched.img”.
If you have the “magisk_patched.img” go into TWRP and flash this IMG over the recovery
o Install
o Select “install image”
o Select the “magisk_patched.img”
o Flash it over the “recovery”
o Reboot system
Yeey you have a Samsung sm-t515 which is rooted and you have a custom ROM.

one last question
massivekind said:
Instructions:
Code:
* READ EVERTHING BEFORE YOU START OR ASK QUESTIONS
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard & a lot. :D
I’m not an expert, I’ve just put some pieces together to achieve the following.
If you have problems, I’m not sure if I’m able to help you
You need to have some basic knowledge
Always have the correct software and backup all your data.
o Also download before you start the stock files, so that you are able to quickly reverse everything via: sammobile
Remember to backup your data!!!!
If you have trouble and the tablet is not working flash the firmware which you’ve downloaded via odin
Working ROMS (Which I’ve tested so far):
IF you want to install a custom ROM, you need to choose the correct custom ROM
Choose the ARM 32-bit with 64-bit binder AB (also known as A64B).
LineageOS 17.x GSI here
Legion ROM GSI here
From OEM stock firmware:
Download TWRP https://forum.xda-developers.com/ga...rp-3-3-1-2019-galaxy-tab-10-1-t3934805/page35
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
Check if OEM unlock is enabled in the developer settings (it should be enabled and greyed out) IF so yeey you did It. If not start over.
Install custom ROM:
Well installing a custom Rom is quite easy .
Download a GSI ROM you like and put it on a SD cart
Go into TWRP
Select “install”
Click on “install image”
Click the on the ROM
In the next screen where we need to select the partition, select the “System Image”
Swipe to confirm
If you want ROOT and or install GAPPS follow the extra steps bellow. If NOT, just reboot the system
Extra’s install MAGISK and or install GAPPS
First of all download the files you want.
Magisk: here
GAPPS: here
You want root? You need to prepare the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. Which we can prepare and flash after you finished the setup of the tablet. You need more info check the following: link
Go back to the TWRP home screen
Select “Wipe”
Select advanced wipe
Check “system”
Click on “repair or change file system”
Click on “resize file system” (if you’ve receive an error, don’t worry just do It again).
o You should see “resizing… done.”
Go back to the TWRP home screen
Select “install”
Select the zip file(‘s) you want and flash them
o IF you receive an error if you want to install the GAPPS zip like “not enough space” go back and resize the system partition
o IF you receive an errro if you want to install Magisk, go back and resize the system partition
Remove “dalvik and cache”
Reboot system
Setup your tablet
Now for the last step to root the tablet all the way
Go into Magisk manager
On the Magisk dashboard you’ve should see that you have the latest version of magisk. Press on the “install” button at the right side
o Select “Select and Patch a File” select the TWRP IMG you still have on the SD card
o Magisk should create a “magisk_patched.img”.
If you have the “magisk_patched.img” go into TWRP and flash this IMG over the recovery
o Install
o Select “install image”
o Select the “magisk_patched.img”
o Flash it over the “recovery”
o Reboot system
Yeey you have a Samsung sm-t515 which is rooted and you have a custom ROM.
Click to expand...
Click to collapse
you have been very kind. I'd like to ask you one last question. for the t515 (since the lineage os is generic) do you also use a particular kernel (which optimizes performance maybe) ?. thanks

gcomunale71 said:
Instructions:
you have been very kind. I'd like to ask you one last question. for the t515 (since the lineage os is generic) do you also use a particular kernel (which optimizes performance maybe) ?. thanks
Click to expand...
Click to collapse
No I don't have any, but if there is one for the 510 give it a try.
Of course backup before flashing

Hi,
Thanks for the guide. Which ROM you recommend? Everything working for you (LTE modem etc)?
Can you now install 64bit apps from Google Play? Any chance you can check if the DJI Fly app is working on your SM-T515?
https://play.google.com/store/apps/details?id=dji.go.v5
Thanks

liamR said:
Hi,
Thanks for the guide. Which ROM you recommend? Everything working for you (LTE modem etc)?
Can you now install 64bit apps from Google Play? Any chance you can check if the DJI Fly app is working on your SM-T515?
https://play.google.com/store/apps/details?id=dji.go.v5
Thanks
Click to expand...
Click to collapse
Well, It's still a 32bit rom. I've tried to install the app but I'm unable (prob because the app is 64bit)
Everything works fine, I'm running the lineageOS ROM. I have a data bundle and I'm able to internet with it (if I want )

massivekind said:
Well, It's still a 32bit rom. I've tried to install the app but I'm unable (prob because the app is 64bit)
Everything works fine, I'm running the lineageOS ROM. I have a data bundle and I'm able to internet with it (if I want )
Click to expand...
Click to collapse
I thought that this custom ROM is 64bit
When I bought the TAB A I thought it's a bargain, I didn't know that I wouldn't be able to install 64bit apps.

massivekind said:
Instructions:
Code:
* READ EVERTHING BEFORE YOU START OR ASK QUESTIONS
* I'm not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you. Hard & a lot. :D
I’m not an expert, I’ve just put some pieces together to achieve the following.
If you have problems, I’m not sure if I’m able to help you
You need to have some basic knowledge
Always have the correct software and backup all your data.
o Also download before you start the stock files, so that you are able to quickly reverse everything via: sammobile
Remember to backup your data!!!!
If you have trouble and the tablet is not working flash the firmware which you’ve downloaded via odin
Working ROMS (Which I’ve tested so far):
IF you want to install a custom ROM, you need to choose the correct custom ROM
Choose the ARM 32-bit with 64-bit binder AB (also known as A64B).
LineageOS 17.x GSI here
Legion ROM GSI here
From OEM stock firmware:
Download TWRP https://forum.xda-developers.com/ga...rp-3-3-1-2019-galaxy-tab-10-1-t3934805/page35
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
Check if OEM unlock is enabled in the developer settings (it should be enabled and greyed out) IF so yeey you did It. If not start over.
Install custom ROM:
Well installing a custom Rom is quite easy .
Download a GSI ROM you like and put it on a SD cart
Go into TWRP
Select “install”
Click on “install image”
Click the on the ROM
In the next screen where we need to select the partition, select the “System Image”
Swipe to confirm
If you want ROOT and or install GAPPS follow the extra steps bellow. If NOT, just reboot the system
Extra’s install MAGISK and or install GAPPS
First of all download the files you want.
Magisk: here
GAPPS: here
You want root? You need to prepare the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. Which we can prepare and flash after you finished the setup of the tablet. You need more info check the following: link
Go back to the TWRP home screen
Select “Wipe”
Select advanced wipe
Check “system”
Click on “repair or change file system”
Click on “resize file system” (if you’ve receive an error, don’t worry just do It again).
o You should see “resizing… done.”
Go back to the TWRP home screen
Select “install”
Select the zip file(‘s) you want and flash them
o IF you receive an error if you want to install the GAPPS zip like “not enough space” go back and resize the system partition
o IF you receive an errro if you want to install Magisk, go back and resize the system partition
Remove “dalvik and cache”
Reboot system
Setup your tablet
Now for the last step to root the tablet all the way
Go into Magisk manager
On the Magisk dashboard you’ve should see that you have the latest version of magisk. Press on the “install” button at the right side
o Select “Select and Patch a File” select the TWRP IMG you still have on the SD card
o Magisk should create a “magisk_patched.img”.
If you have the “magisk_patched.img” go into TWRP and flash this IMG over the recovery
o Install
o Select “install image”
o Select the “magisk_patched.img”
o Flash it over the “recovery”
o Reboot system
Yeey you have a Samsung sm-t515 which is rooted and you have a custom ROM.
Click to expand...
Click to collapse
first of all thanks for the great work.
Sorry if this is a stupid question , but before i brick my new SM-T515 I would rather ask the experts.
Now, i have rooted the stock ROM folowing the steps in https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root with no TWRP and want to install one of the custom ROMs you have tested.
will I lose root if flash the Legion ROM GSI?
if yes, can you please put some steps together to root and install TWRP?
i still have the “magisk_patched.tar" from the stock ROM, would that work for the Legion ROM GSI?

dj-rjay said:
Instructions:
first of all thanks for the great work.
Sorry if this is a stupid question , but before i brick my new SM-T515 I would rather ask the experts.
Now, i have rooted the stock ROM folowing the steps in https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root with no TWRP and want to install one of the custom ROMs you have tested.
will I lose root if flash the Legion ROM GSI?
if yes, can you please put some steps together to root and install TWRP?
i still have the “magisk_patched.tar" from the stock ROM, would that work for the Legion ROM GSI?
Click to expand...
Click to collapse
In theory it should work. I've already covered "root" also in the guide

I've followed the steps and have Lineage installed on my T515, but when I plug it into my computer it can't see the Tablet in Windows Explorer. I've set it to MTP mode and enabled USB debugging. Strange thing is when I use ADB DEVICES I can see it. Also when I plug it in, the tablet makes a sound and it says 'Usb Debugging...' on screen. It just won't show up in Windows.
Also when I try and use File Explorer on the tablet, it can't see the SD Card. I've tried formatting it for 'Portable' but it when I go back in it says it corrupted. When I format it for Phone Storage, it shows the extra space for the phone storage but I also can't see it in the File Explorer.
Anyone else come across this?

Sambuca11 said:
I've followed the steps and have Lineage installed on my T515, but when I plug it into my computer it can't see the Tablet in Windows Explorer. I've set it to MTP mode and enabled USB debugging. Strange thing is when I use ADB DEVICES I can see it. Also when I plug it in, the tablet makes a sound and it says 'Usb Debugging...' on screen. It just won't show up in Windows.
Also when I try and use File Explorer on the tablet, it can't see the SD Card. I've tried formatting it for 'Portable' but it when I go back in it says it corrupted. When I format it for Phone Storage, it shows the extra space for the phone storage but I also can't see it in the File Explorer.
Anyone else come across this?
Click to expand...
Click to collapse
Mm strange, i don't use both functions so I can't really help you.
Maybe you could format the sd card via twrp?
On my side the sd card works. Didn't format the sd card so don't really know

Sambuca11 said:
I've followed the steps and have Lineage installed on my T515, but when I plug it into my computer it can't see the Tablet in Windows Explorer. I've set it to MTP mode and enabled USB debugging. Strange thing is when I use ADB DEVICES I can see it. Also when I plug it in, the tablet makes a sound and it says 'Usb Debugging...' on screen. It just won't show up in Windows.
Also when I try and use File Explorer on the tablet, it can't see the SD Card. I've tried formatting it for 'Portable' but it when I go back in it says it corrupted. When I format it for Phone Storage, it shows the extra space for the phone storage but I also can't see it in the File Explorer.
Anyone else come across this?
Click to expand...
Click to collapse
I have the same issue. Any solution?

zamboj said:
I have the same issue. Any solution?
Click to expand...
Click to collapse
I haven't found one yet, I'm going to try go back to Stock as I need my computer to be able to see the tablet to transfer files over. I've tried installing the Legion custom rom and it does the same thing. I'm not sure but I'd love to get an answer to this and I'd love to use a custom rom.
Are there any other Android 10 roms that I could try?

Sambuca11 said:
I haven't found one yet, I'm going to try go back to Stock as I need my computer to be able to see the tablet to transfer files over. I've tried installing the Legion custom rom and it does the same thing. I'm not sure but I'd love to get an answer to this and I'd love to use a custom rom.
Are there any other Android 10 roms that I could try?
Click to expand...
Click to collapse
I have a work app that need a little more ram: the solution is LineageOs (used 1,2gb vs 1,5gb of the stock rom) and I transfer files through recovery. I tried LegionOS but is full of bugs and file transfer doesn't work the same.

I'm back to stock and my computer and can see my table and the SD card is working fine. Its a shame as I'd love to use LineageOS but for now I'm stuck on stock.

I don’t know what I’m doing wrong so need some help please. I’ve installed TWRP and multidisabler. I’ve wiped the system cache data etc like I was flashing a custom rom.
I’ve downloaded the rom from the links flashed it via system image but I still get the message no os installed rebooted and just a bootloop saying unlocked boot loader press power button to start then nothing no booting image from linageos. Just repeats.
Can anybody tell me or guide me on what I could have done wrong and what what I should being

daljitbanga said:
I don’t know what I’m doing wrong so need some help please. I’ve installed TWRP and multidisabler. I’ve wiped the system cache data etc like I was flashing a custom rom.
I’ve downloaded the rom from the links flashed it via system image but I still get the message no os installed rebooted and just a bootloop saying unlocked boot loader press power button to start then nothing no booting image from linageos. Just repeats.
Can anybody tell me or guide me on what I could have done wrong and what what I should being
Click to expand...
Click to collapse
Mm strange I didn't experience this problem. Like I stated go back to stock and start over. This time don't wipe the system partition.

Thanks for the reply I will try that when I get home later in the day and will post the outcome after.
Are there any other roms the we could also try.

massivekind said:
Mm strange I didn't experience this problem. Like I stated go back to stock and start over. This time don't wipe the system partition.
Click to expand...
Click to collapse
I followed what you said but I’m stilling getting the bootloop for some reason could share links of what rom you downloaded and etc.
Because there must be a mistake in making.
Also to what I’ve been reading is that I need something of treble enabler for the device but I really don’t know.

massivekind said:
Mm strange I didn't experience this problem. Like I stated go back to stock and start over. This time don't wipe the system partition.
Click to expand...
Click to collapse
I finally managed to get LineageOS installed. I just deleted all the files and redone loaded them, returned back to stock and did the whole process all over again.
And it worked. ? ? so maybe somewhere down the line put have been a corrupt download or something.
Custom rom has whole different feeling on the tablet now. Thanks again for tutorial, I’ve been waiting for something like this for a while.
You don’t know of any other roms there out there to try?

daljitbanga said:
I finally managed to get LineageOS installed. I just deleted all the files and redone loaded them, returned back to stock and did the whole process all over again.
And it worked. ? ? so maybe somewhere down the line put have been a corrupt download or something.
Custom rom has whole different feeling on the tablet now. Thanks again for tutorial, I’ve been waiting for something like this for a while.
You don’t know of any other roms there out there to try?
Click to expand...
Click to collapse
You've could try havoc os https://sourceforge.net/projects/ha...v3.5-20200522-Official-a64-ab.img.xz/download
Topic over here, I'm not sure if there are things not working, thats something you'd could figure out
https://forum.xda-developers.com/galaxy-tab-a/how-to/rom-havocos-v3-5-treble-guide-t4108127
I didn't tried this one, but is could be an option

[GUIDE][SM-T290/SM-T290N] Samsung Galaxy Tab A 8.0 (2019) - How to Install LineageOS 18.1 (GSI) + Gapps

Hello!
So recently I was able to install LineageOS 18.1 (GSI) + GApps on my Samsung Galaxy Tab A 8 (SM-T290) tablet and wanted to share how I did it. I noticed a lack of decent step-by-step guides to modding this tablet so I figure I'd share what I learned through scouring multiple threads and through multiple headaches. Fun fact: I also got this working with LineageOS 19 (GSI), however it ran pretty poorly and Android 12 is ugly as hell so why bother anyway? ALSO interestingly enough, you'll see I wrote [SM-T290N] in the title as well. That is the model of the Kid's Edition of this phone, which happens to be the one I had. So I can confirm this process works for the Kid's Edition of this tablet as well as the original.
Some Things To Note
Below I'll list the software/firmware I used in this process. You don't necessarily need to follow this exactly but I don't see any reason not to. The end result is a working install of LineageOS with GApps so if that's what you want I would just follow along step-by-step. ALSO I'm writing this from memory so if I make a mistake please let me know and I'll try and correct it.
Click to expand...
Click to collapse
What You'll Need
Your tablet
A USB Cable to connect your tablet to your PC
A 4GB+ MicroSD card
A Windows PC
Some patience
Instructions
Preparing Your MicroSD Card
1. Place the LineageOS 18.1 .img file from this thread (On SourceForge, there is a section below the files about the naming conventions and how they relate to the hardware of your device and configuration of your ROM. I used the lineage-18.1-20220315-UNOFFICIAL-arm64_bvS-vndklite.img.xz image for my device. If your device is slightly different, you can use Treble Info to determine what ROM you should use. Just make sure to use the VNDKLITE rom if your device supports it.
2. Place the multidisabler .zip folder on there as well. This will preserve encryption provided by TWRP after rebooting.
3. Finally, place the MindTheGapps .zip folder on your SD card (make sure to get the correct version. In my case this was the 11.00-arm64 version).
4. Insert your MicroSD card into your device.
Unlocking the Bootloader
So the first thing you're gonna want to do is unlock your OEM bootloader on your Samsung device.
1. Go to Settings->About Phone->Software Information and look for a field called "Build Number". Tap this Five Times until you see a notification saying developer settings were enabled.
2. Go to Settings->Developer Settings and look for the setting labeled OEM Unlock and turn it on.
If you don't see this setting try connecting to wifi, changing your date and time to around two months prior (I set mine to back to May 2021 since the firmware I was using was set in July 2021), then go back to your developer settings and switch them off and back on again. You should now see the OEM Unlock option.
Click to expand...
Click to collapse
3. From here, you can reboot your device into Recovery Mode by holding the Vol+ and Vol- buttons when the device begins to boot again.
4. You should see a blue screen with some options. Press the Vol+ button to enter Download Mode. This is where you'll use Odin to flash the firmware you need as well as TWRP.
Flashing Firmware
So when I attempted this process I used Magendanz's Unofficial TWRP 3.6.0 as it is the only version of TWRP I found for this device. I also used Odin v3.14.1_3B Patched from this XDA thread. Magendanz's TWRP requires you to have the T290XXU3CUG4 Firmware (I used the XAR region) in order to flash TWRP to your device (you can check wether or not you already have this firmware on your phone by looking the About Phone section again). It takes a while to download though make sure you have some time.
1. Download Odin and run the program. Unzip your firmware folder and use the relevant files when selecting the BL, AP, CP, CSC fields in Odin. I didn't use the HOME_CSC just leave it blank.
2. Connect your device via USB and Flash this firmware to your device.
3. Once your device restarts, go through the setup process and then repeat the Unlocking the Bootloader instructions above in order to make sure it is unlocked again.
4. Reboot your device the same way as stated above.
Flashing TWRP
Before starting, be aware that after you flash TWRP to your device, your device will restart and attempt to open the stock system again. You're going to want to hold the Power and Vol+ buttons simultaneously. You will likely get a warning screen saying that the bootloader is unlocked and may ask you to do a factory reset, this (I believe) is fine. The key here is that once you press the Power Button to continue (as instructed on the warning screen) you'll want to immediately press and hold the Power and Vol+ keys for around 6 Seconds before letting go again (you should be seeing the Samsung Galaxy Tab A logo screen). After letting go, wait around 3-4 seconds, if nothing changes, restart the device by holding all three buttons (Power, Vol+,Vol-) and attempt the process again. It's a pain in the ass but you'll get it eventually. Just make sure not to let the device boot into the system again as that can cause problems in TWRP and you'll likely have to start the process over (from flashing the firmware).
1. Once your tablet is once again in Download Mode, open Odin again and flash the TWRP (tar.md5 file) to the AP (recovery) partition. Do not use any of the other partitions.
2. If this is successful, your phone will begin to reboot. Quickly press and hold the combination of buttons Power and Vol+ until you see the warning dialog pop up. Once you do, release all buttons and be ready to quickly press and release the Power button continue, and then immediately after press and hold the Power and Vol+ buttons again for 6 seconds. After around 6 seconds, release all buttons. Wait around 3-4 seconds and, if the screen does not change to the TWRP logo, restart the device by pressing and holding all buttons simultaneously and try this step again.
3. If you have entered into TWRP, congrats!
Installing Custom ROM + Software in TWRP
1. The first thing you'll want to do is select the Wipe->Format Data. Type 'yes' and hit enter (or swipe I forget which).
2. Next, select Install, and then select your MicroSD card as your storage device. You should see your zip files (if not switch from the install image option).
3. Install the multidisabler, do not reboot
4. Go back into Install and select Install Image (might not be the exact naming) option. Select your MicroSD card as the storage device again and install the LineageOS 18.1 rom. Do not reboot.
5. Go back into Install and select your MindTheGapps zip file and install it.
Now, a lot of people run into a problem when trying to install Gapps which is your device complaining about no more available space in the system partition. If this is the case, go back to Wipe and select Advanced Wipe. Select your system partition and then select Change or Repair Partition. Once you're here you should see the size and available space of your partition. You'll want to hit Resize Partition and let it do it's thing. To confirm it worked, go back to Wipe->Advanced Wipe->Select System->Change or Repair Partition and your available space should be much larger now. Now just attempt to install MindTheGapps again.
Click to expand...
Click to collapse
Final Steps
Once you reboot you should be able to successfully reach the setup screen for Lineage. Go through the steps of setting up your device as usual and be sure that Gapps are installed. Go ahead and re-enable developer settings and enable USB-Debugging and Root Debugging. The reason for this is that, when I first installed Gapps, Google Play Protect would keep throwing warnings at me about my device not being Google Play Certified. This means I couldn't actually use any of the google play services. If you run into the same issue, here are the steps you can take to fix it:
1. First, go into Settings->Apps and find your Google Play Services app. Clear the cache and delete the app data, then reboot your device. If you try and sign into the Google Play store and you are able to without getting any play protect warnings, then you're good you can disregard the following steps.
2. If you are still receiving these warnings, you'll want to head over to this site and follow the instructions (I'm not gonna tell you how to use ADB here). Once you submit your framework ID, reboot your device. Everything should be working fine now.
And that's it! If I am forgetting any steps please let me know, again I am writing this from memory of the process so it may be missing some minor details. I hope this helps!!!

How's the stability, speed and the responsiveness on Lineage with a t290? I have mine rooted debloated and twrp installed but it is slow on stock OS

kkdamion said:
How's the stability, speed and the responsiveness on Lineage with a t290? I have mine rooted debloated and twrp installed but it is slow on stock OS
Click to expand...
Click to collapse
It runs surprisingly well! Much better than stock. There’s virtually no input lag and the battery life is also very solid on lineage.
Where i run into some lag is when trying to use apps that have embedded video in them. For whatever reason the T290 cannot handle video very well at all.
So yeah I would definitely recommend trying it, it’ll really breathe new life into that tablet

i cant get google play services to work and i cant fetch device_id to register the device
i get "no closing qoute" message
adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
/system/bin/sh: no closing quote
EDIT: downloaded "android device id" APK from the internet and gathered the framework id information from the app

kkdamion said:
i cant get google play services to work and i cant fetch device_id to register the device
i get "no closing qoute" message
adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
/system/bin/sh: no closing quote
EDIT: downloaded "android device id" APK from the internet and gathered the framework id information from the app
Click to expand...
Click to collapse
Glad it worked out for you! Let me know if you have any more questions and I'd be happy to help.

Hi! is this applicable also for SM-T295?

for those trying to figure out the Google Play Certified page with the adb command
Code:
adb shell 'sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
"select * from main where name = \"android_id\";"'
do : adb shell
first then paste in :
sqlite3 /data/data/com.google.android.gsf/databases/gservices.db \
"select * from main where name = \"android_id\";"
and it shouldn't give you the error

i must say. linageos on my sm-t290 is really nice
its fast and smooth way much better then stock fw
i would reccomend anyone with a t290/t295 to install this GSI

Im into a bootloop right now after a few fails with installing Lineage on my SM-T290..
Seems like i cant install any rom? not sure how to fix this issue, can anyone point me in the right direction?
Im able to get into TWRP and download mode. but cant install any rom?

thepalek1ng said:
Hello!
So recently I was able to install LineageOS 18.1 (GSI) + GApps on my Samsung Galaxy Tab A 8 (SM-T290) tablet and wanted to share how I did it. I noticed a lack of decent step-by-step guides to modding this tablet so I figure I'd share what I learned through scouring multiple threads and through multiple headaches. Fun fact: I also got this working with LineageOS 19 (GSI), however it ran pretty poorly and Android 12 is ugly as hell so why bother anyway? ALSO interestingly enough, you'll see I wrote [SM-T290N] in the title as well. That is the model of the Kid's Edition of this phone, which happens to be the one I had. So I can confirm this process works for the Kid's Edition of this tablet as well as the original.
What You'll Need
Your tablet
A USB Cable to connect your tablet to your PC
A 4GB+ MicroSD card
A Windows PC
Some patience
Instructions
Preparing Your MicroSD Card
1. Place the LineageOS 18.1 .img file from this thread (On SourceForge, there is a section below the files about the naming conventions and how they relate to the hardware of your device and configuration of your ROM. I used the lineage-18.1-20220315-UNOFFICIAL-arm64_bvS-vndklite.img.xz image for my device. If your device is slightly different, you can use Treble Info to determine what ROM you should use. Just make sure to use the VNDKLITE rom if your device supports it.
2. Place the multidisabler .zip folder on there as well. This will preserve encryption provided by TWRP after rebooting.
3. Finally, place the MindTheGapps .zip folder on your SD card (make sure to get the correct version. In my case this was the 11.00-arm64 version).
4. Insert your MicroSD card into your device.
Unlocking the Bootloader
So the first thing you're gonna want to do is unlock your OEM bootloader on your Samsung device.
1. Go to Settings->About Phone->Software Information and look for a field called "Build Number". Tap this Five Times until you see a notification saying developer settings were enabled.
2. Go to Settings->Developer Settings and look for the setting labeled OEM Unlock and turn it on.
3. From here, you can reboot your device into Recovery Mode by holding the Vol+ and Vol- buttons when the device begins to boot again.
4. You should see a blue screen with some options. Press the Vol+ button to enter Download Mode. This is where you'll use Odin to flash the firmware you need as well as TWRP.
Flashing Firmware
So when I attempted this process I used Magendanz's Unofficial TWRP 3.6.0 as it is the only version of TWRP I found for this device. I also used Odin v3.14.1_3B Patched from this XDA thread. Magendanz's TWRP requires you to have the T290XXU3CUG4 Firmware (I used the XAR region) in order to flash TWRP to your device (you can check wether or not you already have this firmware on your phone by looking the About Phone section again). It takes a while to download though make sure you have some time.
1. Download Odin and run the program. Unzip your firmware folder and use the relevant files when selecting the BL, AP, CP, CSC fields in Odin. I didn't use the HOME_CSC just leave it blank.
2. Connect your device via USB and Flash this firmware to your device.
3. Once your device restarts, go through the setup process and then repeat the Unlocking the Bootloader instructions above in order to make sure it is unlocked again.
4. Reboot your device the same way as stated above.
Flashing TWRP
Before starting, be aware that after you flash TWRP to your device, your device will restart and attempt to open the stock system again. You're going to want to hold the Power and Vol+ buttons simultaneously. You will likely get a warning screen saying that the bootloader is unlocked and may ask you to do a factory reset, this (I believe) is fine. The key here is that once you press the Power Button to continue (as instructed on the warning screen) you'll want to immediately press and hold the Power and Vol+ keys for around 6 Seconds before letting go again (you should be seeing the Samsung Galaxy Tab A logo screen). After letting go, wait around 3-4 seconds, if nothing changes, restart the device by holding all three buttons (Power, Vol+,Vol-) and attempt the process again. It's a pain in the ass but you'll get it eventually. Just make sure not to let the device boot into the system again as that can cause problems in TWRP and you'll likely have to start the process over (from flashing the firmware).
1. Once your tablet is once again in Download Mode, open Odin again and flash the TWRP (tar.md5 file) to the AP (recovery) partition. Do not use any of the other partitions.
2. If this is successful, your phone will begin to reboot. Quickly press and hold the combination of buttons Power and Vol+ until you see the warning dialog pop up. Once you do, release all buttons and be ready to quickly press and release the Power button continue, and then immediately after press and hold the Power and Vol+ buttons again for 6 seconds. After around 6 seconds, release all buttons. Wait around 3-4 seconds and, if the screen does not change to the TWRP logo, restart the device by pressing and holding all buttons simultaneously and try this step again.
3. If you have entered into TWRP, congrats!
Installing Custom ROM + Software in TWRP
1. The first thing you'll want to do is select the Wipe->Format Data. Type 'yes' and hit enter (or swipe I forget which).
2. Next, select Install, and then select your MicroSD card as your storage device. You should see your zip files (if not switch from the install image option).
3. Install the multidisabler, do not reboot
4. Go back into Install and select Install Image (might not be the exact naming) option. Select your MicroSD card as the storage device again and install the LineageOS 18.1 rom. Do not reboot.
5. Go back into Install and select your MindTheGapps zip file and install it.
Final Steps
Once you reboot you should be able to successfully reach the setup screen for Lineage. Go through the steps of setting up your device as usual and be sure that Gapps are installed. Go ahead and re-enable developer settings and enable USB-Debugging and Root Debugging. The reason for this is that, when I first installed Gapps, Google Play Protect would keep throwing warnings at me about my device not being Google Play Certified. This means I couldn't actually use any of the google play services. If you run into the same issue, here are the steps you can take to fix it:
1. First, go into Settings->Apps and find your Google Play Services app. Clear the cache and delete the app data, then reboot your device. If you try and sign into the Google Play store and you are able to without getting any play protect warnings, then you're good you can disregard the following steps.
2. If you are still receiving these warnings, you'll want to head over to this site and follow the instructions (I'm not gonna tell you how to use ADB here). Once you submit your framework ID, reboot your device. Everything should be working fine now.
And that's it! If I am forgetting any steps please let me know, again I am writing this from memory of the process so it may be missing some minor details. I hope this helps!!!
Click to expand...
Click to collapse
bro, I have a problem, my tablet is in a bootloop and I don't know what to do, try with other custom roms but it's the same, what do I have to do so that when I install a custom room it doesn't give me that error?

Flashing the Gapps package resulted in an error: Failure to mount '/system_root' (Invalid argument)

V0latyle said:
Flashing the Gapps package resulted in an error: Failure to mount '/system_root' (Invalid argument)
Click to expand...
Click to collapse
Sorry for the bother, new to Android modding scene.
I went into the recovery menu (oem unlock on) and tried to flash TWRP as written on this guide, but I get a secure check fail : aboot on my device and fail on Odin. What do I do here?
Edit: Aparently my device is SM-T295, basically the LTE version of the same device, which is why it isn't recognising it. My bad.

Do you have any video to teach better ???

HyruleanKnight said:
Sorry for the bother, new to Android modding scene.
I went into the recovery menu (oem unlock on) and tried to flash TWRP as written on this guide, but I get a secure check fail : aboot on my device and fail on Odin. What do I do here?
Edit: Aparently my device is SM-T295, basically the LTE version of the same device, which is why it isn't recognising it. My bad.
Click to expand...
Click to collapse
Shouldn't matter, TWRP is the same for both variants.
There's two ways to get around the secure check fail problem:
After updating via Odin, make sure you immediately interrupt the boot and force reboot into Download Mode. Then, flash TWRP.
Or, after updating, allow your device to boot to Android, skip through the setup wizard (make sure you connect to the internet), and enable Developer Options. Ensure OEM Unlocking is there and grayed out. If not, leave it for a bit until it is. This disables Vaultkeeper on the bootloader. Then, reboot to download mode and flash TWRP.
In both cases, after flashing TWRP, DO NOT let the device boot into Android. Force boot into recovery, then install the Multidisabler from here.
Now to my own problem...
I don't know what I did differently (or wrong) but I cannot get LineageOS to boot correctly on my T290. I was running 18.1 before. I recently updated to CVG3 and followed the same process as I did before - flashed TWRP, then installed the LineageOS GSI to /system.
18.1 continuously bootloops without even loading LineageOS.
19.1 gets to the LineageOS splash screen, and occasionally the setup screen, but continuously reboots also.
After flashing TWRP, I'm installing the multidisabler, then wiping /system, /data, /cache.
Any idea what I'm doing wrong?
@J.Michael any thoughts? You're more familiar with Samsung than I am

V0latyle said:
Shouldn't matter, TWRP is the same for both variants.
There's two ways to get around the secure check fail problem:
After updating via Odin, make sure you immediately interrupt the boot and force reboot into Download Mode. Then, flash TWRP.
Or, after updating, allow your device to boot to Android, skip through the setup wizard (make sure you connect to the internet), and enable Developer Options. Ensure OEM Unlocking is there and grayed out. If not, leave it for a bit until it is. This disables Vaultkeeper on the bootloader. Then, reboot to download mode and flash TWRP.
In both cases, after flashing TWRP, DO NOT let the device boot into Android. Force boot into recovery, then install the Multidisabler from here.
Now to my own problem...
I don't know what I did differently (or wrong) but I cannot get LineageOS to boot correctly on my T290. I was running 18.1 before. I recently updated to CVG3 and followed the same process as I did before - flashed TWRP, then installed the LineageOS GSI to /system.
18.1 continuously bootloops without even loading LineageOS.
19.1 gets to the LineageOS splash screen, and occasionally the setup screen, but continuously reboots also.
After flashing TWRP, I'm installing the multidisabler, then wiping /system, /data, /cache.
Any idea what I'm doing wrong?
@J.Michael any thoughts? You're more familiar with Samsung than I am
Click to expand...
Click to collapse
I think I have a solution.
I see that you are installing the multidisabler after you booted TWRP and by wiping the partitions, however, what you are supposed to do is this:
After you have booted into TWRP and have swiped to allow modifications, go to Wipe> Format Data and type yes. Don't reboot, and don't wipe any other partitions.
After that, go to install and then install the multidisabler, don't reboot.
Then install the latest LineageOS gsi to the system partition, and finally install gapps, then reboot.
Make sure you are choosing the arm64_bvS_vndklite variant, otherwise it will bootloop.
Hope this helps!

Just Mike said:
I think I have a solution.
I see that you are installing the multidisabler after you booted TWRP and by wiping the partitions, however, what you are supposed to do is this:
After you have booted into TWRP and have swiped to allow modifications, go to Wipe> Format Data and type yes. Don't reboot, and don't wipe any other partitions.
After that, go to install and then install the multidisabler, don't reboot.
Then install the latest LineageOS gsi to the system partition, and finally install gapps, then reboot.
Make sure you are choosing the arm64_bvS_vndklite variant, otherwise it will bootloop.
Hope this helps!
Click to expand...
Click to collapse
Okay, so install Multidisabler AFTER wiping data. I'll try that.
I'm using the bgS image so it's already got Google apps. I didn't have any success flashing any of the Gapps packages on the vanilla images.
Is Multidisabler still necessary on Android 11 on this device, or do we just need a patched vbmeta.img?

V0latyle said:
Okay, so install Multidisabler AFTER wiping data. I'll try that.
I'm using the bgS image so it's already got Google apps. I didn't have any success flashing any of the Gapps packages on the vanilla images.
Is Multidisabler still necessary on Android 11 on this device, or do we just need a patched vbmeta.img?
Click to expand...
Click to collapse
Yes, Multidisabler is necessary, otherwise it'll bootloop. I haven't tried anything with a patched vbmeta and frankly don't want to.
The bgS version will work just fine for Android 11.
Currently running Android 13 with LineageOS 20.0, the bvS version. Gotta say it works great. MindtheGapps 13 will work, I haven't encountered any "This device is not certified" issues.

Just Mike said:
Yes, Multidisabler is necessary, otherwise it'll bootloop. I haven't tried anything with a patched vbmeta and frankly don't want to.
The bgS version will work just fine for Android 11.
Currently running Android 13 with LineageOS 20.0, the bvS version. Gotta say it works great. MindtheGapps 13 will work, I haven't encountered any "This device is not certified" issues.
Click to expand...
Click to collapse
Do I need to wipe /system or /boot or anything before installing? I did exactly as you said - rebooted to recovery (was running Samsung stock), formatted data, installed multidisabler, then installed a LineageOS 19 image to /system. It begins to boot (LineageOS animation) then reboots.
Are you using Andy Yan's builds?

V0latyle said:
Do I need to wipe /system or /boot or anything before installing? I did exactly as you said - rebooted to recovery (was running Samsung stock), formatted data, installed multidisabler, then installed a LineageOS 19 image to /system. It begins to boot (LineageOS animation) then reboots.
Are you using Andy Yan's builds?
Click to expand...
Click to collapse
Nope, you don't have to wipe any other partitions, only format data
Yes, I'm using Andy Yan's builds. I'll link the thread here: https://forum.xda-developers.com/t/gsi-13-lineageos-20-trebledroid-based.4517345/
If I may ask, which type GSI from Andy Yan did you use?

Just Mike said:
Nope, you don't have to wipe any other partitions, only format data
Yes, I'm using Andy Yan's builds. I'll link the thread here: https://forum.xda-developers.com/t/gsi-13-lineageos-20-trebledroid-based.4517345/
If I may ask, which type GSI from Andy Yan did you use?
Click to expand...
Click to collapse
Trying to get back into TWRP, just a sec...
-arm64_bgS.img
Flashing the vndklite one now to see if it works
If I can get this working, I plan on using a bgN flavor so I can just install Magisk, since I don't use SuperSU
Edit: vndklite is bootlooping too