Related
{
"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"
}
[/CENTER]
Introduction
MultiROM is one-of-a-kind multi-boot mod for Redmi note 3. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting, once they are ported to the redmi note 3
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Via MultiROM Manager app (We do not have Official Support, so this is not an option for us yet)
This is the easiest way to install everything MultiROM needs. Install the app (Not for Moto X Play) and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel (If you want to use Kexec) - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
Modified recovery (TWRP_multirom_lux_YYYYMMDD.img) - download the IMG file from second post and use fastboot, TWRP or Flashify app to flash it.
Patched kernel - you can find it in the second post. Download the ZIP file and flash it in recovery. You can use any 3rd-party kernel which include the patch. we dont need patch kernel with the no kexec workaround
MultiROM (multirom-YYYYMMDD-vXX-wt88047-signed.zip) - download the ZIP file from second post and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
XDA:DevDB Information
[MOD][MultiROM][v33][Beta 1][kenzo], Tool/Utility for the Xiaomi Redmi Note 3
Contributors
zeeshanhussain12
Source Code: https://github.com/multirom-nexus6p
Version Information
Status: Beta
Beta Release Date: 2016-06-15
Created 2016-06-15
Last Updated 2016-06-15
Reserved
DOWNLOADS
1. Main Downloads
Multirom :- multirom-20160615-v33-UNOFFICIAL-kenzo.zip
Multirom recovery:- recovery.img
2. third-party kernels with kexec-hardboot patch
no need with kexec workaround
Uninstaller :- multirom_uninstaller.zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.
Reserved
FAQ's
1. Should I flash recovery only via Flashify app?
-Not essentially, You can flash it via recovery.
Boot to TWRP.
Install->Tap on Images(bottom right screen)>Locate and select your recovery.img
Flash to 'Recovery' partition.
Reboot back to TWRP(IMPORTANT).
2.Can I flash any other kernels?
-yes you can flash any roms
3.Which roms can I flash?
-All Android 5.1+ roms can be flashed without any issues.
miui is not supported
4.How to flash without Hardbricking?
-Follow the steps from OP and there are videos to make the things easy in initial pages.
Maximum it causes bootloops(softbrick), not hardbrick if you follow the guide.
5.Can I flash roms to ext-sd card and USB-otg? How?
-Yes you can flash them to ext-sd card and USB-otg.
Boot to TWRP.
Tap on Multirom.
Tap on ADD ROM
Select the right Location
Flashing on ext-sd and USB otg takes some time, so be patient, don't freak out!
sd1 = usb otg
mmcblklpa = sd card
6.Where to find roms installed in my ext-sd and USB? How to boot into 'em?
-After flashing you'll be booted into MultiROM menu.
All your roms flashed on internal memory will be in Internal tab.
Others will be in External tab.
7.How to rename/remove/delete/wipe dalvik & cache or flash any other zips to existing rom?
-Follow
Boot to recovery.
Tap on MultROM
Tap on the rom which you want to remove/add zips.
You'll find all the options you need!
9."Unable to flash, I'm getting errors" / "Executing updater script failed" / "Rom is not booting" ????
-Please provide logs. It'll be located in /data/media/0/multirom/last_kexec. log
It'd great if you can provide the screenshots.
Press VOL DOWN + LOCK KEY to take Screenshots.
10.How to disable auto boot / change rom name / hide roms / brightness of Multirom menu?
-Follow
Boot to recovery.
Tap on MultiROM.
Tap on 3 dots on top right of screen.
Select settings.
Here you find all the customisations for MultiROM menu.
BUGS
- Miui is not supported
Credits @nkk71 for his no kexec workaround @Abhishek from yu forums @TheStrix for cm
NOTE :- All the devs are requested to help in improving this project as it is still in beta stage
Reserved for future....who knows what crazy post will be made here
Good job @zeeshanhussain12
VIDEO GUIDE (SOON WILL BE KENZO SPECIFIC)
Awesome.... Thank you
Sent from my SHIELD Tablet using XDA-Developers mobile app
yes,it looks so good
Sent from my Hol-U19 using XDA-Developers mobile app
Shahan_mik3 said:
Reserved for future....who knows what crazy post will be made here[emoji14]
Good job @zeeshanhussain12
Click to expand...
Click to collapse
Come make eos rom like mi3 here m8.. Im ex-user mi3..
Sent from my Redmi Note 3 using XDA-Developers mobile app
Can't boot to the rom...
The multirom screen shows up and when i select the rom, device reboots and again shows up....
I had to uninstall multirom and now it's booting into my primary rom normally...
This looks interesting. I’m definitely going to try it.
But when you say MIUI not supported, does that mean MIUI doesn’t work as a secondary ROM, or MIUI doesn’t work at all? How about Xiaomi.EU builds that don’t mess with TWRP? I’ve never tried MultiROM, but I have recently been playing with Dual Boot Patcher on my old Redmi 1S. I can get Xiaomi.EU MIUI to work both as a primary and a secondary ROM, but I also have to flash TWRP every time I update it.
Also what happens if I use ROMs with different bootloaders? For example, Santhosh uses stock MM bootloader and Balika011 uses a modified bootloader from AOSP ROM (I think). How would that work?
nice to see you here buddy @zeeshanhussain12.
ayush321 said:
Can't boot to the rom...
The multirom screen shows up and when i select the rom, device reboots and again shows up....
I had to uninstall multirom and now it's booting into my primary rom normally...
Click to expand...
Click to collapse
Working on porting kexec to our kernel ( currently it stuck on mi logo) this workaround is not working with all ROMs
edit- looks like the problem is with dtb. people are using different trees for roms which have different dtb. it is causing this issue. we have to wait for official cm trees or use the roms which is built by same trees . the roms i tried was built by same trees thats why its fine for me
Sent from my Redmi Note 3 using Tapatalk
Filip013 said:
This looks interesting. I’m definitely going to try it.
But when you say MIUI not supported, does that mean MIUI doesn’t work as a secondary ROM, or MIUI doesn’t work at all? How about Xiaomi.EU builds that don’t mess with TWRP? I’ve never tried MultiROM, but I have recently been playing with Dual Boot Patcher on my old Redmi 1S. I can get Xiaomi.EU MIUI to work both as a primary and a secondary ROM, but I also have to flash TWRP every time I update it.
Also what happens if I use ROMs with different bootloaders? For example, Santhosh uses stock MM bootloader and Balika011 uses a modified bootloader from AOSP ROM (I think). How would that work?
Click to expand...
Click to collapse
miui gives error while flashing as secondary. i have not tried Xiaomi.EU roms. i have ported DualBootPatcher too i have it in my drive . it doesn't work well with sd 650 as qcom changed base directory in mm and lp. the current problem is with dtb nearly every rom is using different source which have different dtb, it is causing problems. we just have to wait for one official source or use the roms which is built with same trees
zeeshanhussain12 said:
Working on porting kexec to our kernel ( currently it stuck on mi logo) this workaround is not working with all ROMs
edit- looks like the problem is with dtb. people are using different trees for roms which have different dtb. it is causing this issue. we have to wait for official cm trees or use the roms which is built by same trees . the roms i tried was built by same trees thats why its fine for me
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Can you tell me which roms are currently working with multiROM...
Reserved
Waiting for miui support
Sent from my Redmi Note 3 using XDA-Developers mobile app
Hadi al-Haiqal said:
Come make eos rom like mi3 here m8.. Im ex-user mi3..
Click to expand...
Click to collapse
Haha Eos was the best and can't be replaced
zeeshanhussain12 said:
[/CENTER]
Introduction
MultiROM is one-of-a-kind multi-boot mod for Redmi note 3. It can boot any Android ROM as well as other systems like Ubuntu Touch, Plasma Active, Bohdi Linux or WebOS port, once they are ported to our device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs, daily prebuilt image files to install Ubuntu Touch and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Use for example Ubuntu Touch or Desktop alongside with Android, without the need of device formatting, once they are ported to the redmi note 3
* Boot from USB drive attached via OTG cable
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is messing with boot sector and data partition. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.
Installation
1. Via MultiROM Manager app (We do not have Official Support, so this is not an option for us yet)
This is the easiest way to install everything MultiROM needs. Install the app (Not for Moto X Play) and select MultiROM and recovery on the Install/Update card. If the Status card says Kernel: doesn't have kexec-hardboot patch! in red letters, you have to install also patched kernel (If you want to use Kexec) - either select one on the Install/Update card or get some 3rd-party kernel here on XDA. You are chosing kernel for your primary ROM, not any of your (future) secondary ROMs, so select the version accordingly.
Press "Install" on the Install/Update card to start the installation.
2. Manual installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
MultiROM has 3 parts you need to install:
Modified recovery (TWRP_multirom_lux_YYYYMMDD.img) - download the IMG file from second post and use fastboot, TWRP or Flashify app to flash it.
Patched kernel - you can find it in the second post. Download the ZIP file and flash it in recovery. You can use any 3rd-party kernel which include the patch. we dont need patch kernel with the no kexec workaround
MultiROM (multirom-YYYYMMDD-vXX-wt88047-signed.zip) - download the ZIP file from second post and flash it in recovery.
You current rom will not be erased by the installation.
Download links are in the second post.
Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using USB drive
During installation, recovery lets you select install location. Plug in the USB drive, wait a while and press "refresh" so that it shows partitions on the USB drive. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to USB drives takes a bit longer, because the flash drive is (usually) slower and it needs to create the images, so installation of Ubuntu to 4Gb image on my pretty fast USB drive takes about 20 minutes.
Enumerating USB drive can take a while in MultiROM menu, so when you press the "USB" button in MultiROM, wait a while (max. 30-45s) until it searches the USB drive. It does it by itself, no need to press something, just wait.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - add ROM to boot
- List ROMs - list installed ROMs and manage them
- Inject boot.img file - When you download for example kernel, which is distrubuted as whole boot.img (eg. franco kernel), you have to use this option on it, otherwise you would lose MultiROM.
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - well, settings.
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - flash ZIP to the ROM, for example gapps
- Add/replace boot.img - replaces boot.img used by this ROM, this is more like developer option.
- Re-patch init - this is available only for ubuntu. Use it when ubuntu cannot find root partition, ie. after apt-get upgrade which changed the init script.
XDA:DevDB Information
[MOD][MultiROM][v33][Beta 1][kenzo], Tool/Utility for the Xiaomi Redmi Note 3
Contributors
zeeshanhussain12
Source Code: https://github.com/multirom-nexus6p
Version Information
Status: Beta
Beta Release Date: 2016-06-15
Created 2016-06-15
Last Updated 2016-06-15
Click to expand...
Click to collapse
Awesome Work buddy! Keep going!
@War_machine28 said:
Awesome Work buddy! Keep going!
Click to expand...
Click to collapse
Please don't quote the whole op...
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
Update: March 24 2022: This ROM has been retired and a new one based on LOS 19.1 (and TWRP based on Android 11) have taken its place. New thread here: https://forum.xda-developers.com/t/...4-2020-lineageos-19-1-and-twrp-3-6-1.4421365/
---
Update 9:46am EST July 15 2021: new builds of TWRP and LineageOS with TWRP touch fixed and LOS w/ space for Gapps is now live.
WARNING: USE AT YOUR OWN RISK.
I have successfully ported TWRP and Lineage OS 18.1 to the Samsung Galaxy Tab A7 10.4 (2020), aka SM-T500. This is my first time porting TWRP or LOS, so there may be issues unknown about at this time. Thus far, the only known issue is that the touchscreen in TWRP does not work. This can be worked around by using a USB mouse and/or accessing the device via ADB.
Here are the steps to follow:
Update your device to the latest stock ROM (as of this writing) either using the built-in system updater or via Odin. You want the build that ends with "3BUF3".
Unlock device bootloader using instructions from other threads. This will wipe your device.
Boot into download mode and flash "vbmeta_disabled_R.tar" via Odin in the "Userdata" slot to disable verified boot. This will wipe your device again.
Boot device back into download mode and flash TWRP via Odin in the "AP" slot. If you boot up into the stock ROM rather than booting directly back into download mode then go through the initial setup process of the stock ROM and enable developer tools and ensure OEM Unlocking is still enabled (VaultKeeper can possibly undo OEM Unlocking if you get to the ROM but don't go into Developer Tools and view OEM Unlocking is enabled, so make sure to do this).
Boot device into TWRP (recovery mode) and format (not wipe) your data partition. Then reboot back into TWRP.
Push LineageOS (super.new.ext4.img) to device. Ideally push it to an SD card formatted with ExFat or EXT2/3/4 (FAT/FAT16/FAT32/VFAT won't work due to file-size limitations).
Install LineageOS image to "Super" partition. Make sure to select "Install from Image" in order to show .img files in the install selector screen.
(Optional) Push NikGapps Omni to your device and install the zip. Make sure you include a "nikgapps.config" file in your "/tmp" folder that is configured to install to "system" rather than "product" or "default".
Reboot to system. You should now be in LOS with Gapps.
(Optional, but recommended): Install Magisk via TWRP
(Optional, but recommended): Run fix script to fix brightness slider not working and to make Magisk work. If you didn't install Magisk but only want the brightness fix, just enter "n" when prompted in the script. To run the script:
NOTE: Script has .txt file extension to allow hosting on AFH. Remove that so it's just .sh to match the instructions below.
Download and push to device when booted into TWRP
adb push sm-t500_fixes.sh /tmp
Enter an adb shell
adb shell
Change directories and set permissions
cd /tmp
chmod +x /tmp/sm-t500_fixes.sh
Run script
/tmp/sm-t500_fixes.sh
Tips:
If you are not seeing all of your storage space in the OS on the internal flash, boot to TWRP and format data.
Flash TWRP via "AP" slot and flash VBMeta_Disabler via "Userdata" slot in Odin.
Flash LineageOS as an Image, not as a Zip.
For Gapps, use the latest NikGapps for ARM64 and Android 11/R.
For Gapps, make sure you install to the System partition and not Product. To do this you need to slightly modify a nikgapps.config file. Instructions on that can be found on the NikGapps site.
Downloads:
LineageOS 18.1 20210615 Beta 2: https://www.androidfilehost.com/?fid=14943124697586369438
TWRP 3.5.2 Beta 3: https://www.androidfilehost.com/?fid=14943124697586369439
vbmeta_disabled_R: https://www.androidfilehost.com/?fid=14943124697586369440
Fixes for brightness and Magisk (sm-t500_fixes.sh): https://www.androidfilehost.com/?fid=14943124697586369521
Known Issues:
OS-encrypted storage (Internal Data) not able to be decrypted in TWRP.
Brightness controls don't work: Fixed via "sm-t500_fixes.sh script.
TWRP touch screen doesn't work (use USB keyboard or adb). Should be fixed with TWRP Beta 3.
TWRP formatting external SD card may hardbrick device. Do not do this! Fixed with TWRP Beta 2.
Source (device tree for TWRP from my Github): https://github.com/agreenbhm/android_device_samsung_gta4lwifi
Source (kernel sources from Samsung): https://opensource.samsung.com/uploadSearch?searchValue=Sm-t500#
agreenbhm said:
I have successfully ported TWRP and Lineage OS 18.1 to the Samsung Galaxy Tab A7 10.4 (2020), aka SM-T500. This is my first time porting TWRP or LOS, so there may be issues unknown about at this time. Thus far, the only known issue is that the touchscreen in TWRP does not work. This can be worked around by using a USB mouse and/or accessing the device via ADB.
Here are the rough steps to follow:
Unlock device bootloader using instructions from other threads.
Patch stock ROM (AP) using Magisk, then flash rooted ROM. Will likely need to wipe device after this.
Boot into rooted ROM and ensure "OEM Unlocking" is still enabled in "Developer Tools".
Boot back into download mode and flash "vbmeta_disabled_R.tar" to disable verified boot.
Boot device back into rooted stock ROM to ensure things are still functional (may require a device wipe at this step).
Boot device into download mode and use ODIN to flash TWRP recovery.tar file via "AP" slot.
Boot device into TWRP to verify functionality (hold Vol-Up + Power during boot).
Access TWRP via adb using "adb shell" or with USB mouse (touch functionality currently not working).
Format data partition on device.
Via ADB shell: twrp format data
Via USB mouse: Wipe -> Advanced -> Format Data
Boot device into download mode.
Via ADB shell: twrp reboot download
Via USB mouse: Reboot -> Download
Flash LineageOS tar file via ODIN using the "AP" slot.
If device boots into TWRP after flashing LineageOS, use USB mouse to select: Reboot -> System
Device should boot and stall for ~1m at the Samsung logo screen with red text below, then should go blank and then display LineageOS boot image.
Downloads:
LineageOS 18.1 20210615 with TWRP 3.5.2: https://mega.nz/file/vMVglThZ#TepIHvdEypezq3z4S_4Lln7FRFVfC7CUjVGq3ByFb6U
TWRP 3.5.2: https://mega.nz/file/GYU1yCCQ#JsthI8BYNtfB08Pzt1eeXta2Lb1zCkUI185Zm88dEW4
vbmeta_disabled_R: https://mega.nz/file/iMFx3CQI#8cP4mPoRaQNwDATqt0vKD8wxqRWSTz1EL79U0fNpW8M
Click to expand...
Click to collapse
Great news!! But I think you need to post it in the ROMs, Kernels, Recover thread.
awesome. Will try after work. Also I think you posted in the wrong section.
Which slot to flash the vbmeta?
wizzdome said:
Which slot to flash the vbmeta?
Click to expand...
Click to collapse
AP
Thanks,
After flashing the vbmeta it booted into recovery automatically after what looked like a bootloop in progress, so I wiped with factory reset and then it rebooted fine. (still not sure exactly what the vbmeta does I was hoping it would make it so i didnt get that stupid pop up asking me to hit power button to continue booting due to it having the patched os) anyhow booted fine and twrp installed as you stated without touch screen but mouse with otg works fine. (great job so far) On to LOS... I think I should have checked oem lock before flashing LOS as when I installed I get stuck at boot screen that says oem lock is on... must have been from my factory reset... (facepalm)
Nope... Still sticking on boot with the following showing on the screen...
RPMB fuse not set
RPMB Provisioned
Current BInary: Custom (0x30f)
FRP Lock : OFF
OEM Lock : ON (U) {this was off verified before flash}
KG Status : Checking
Waranty Void : 0x1 (0xE02)
Quallcomm Secureboot : Enable
RP SWREV : B3 (1,1,1,3,1,1) k3 s3
secure download : enable
grdm status : normal (d0000501)
did : 041ce2d22dba
this is displayed in the corner on the bootscreen and looks like it belongs on the download screen, anyhow booting into twrp from this point works however factory reset fails with unable to mount key(something and key(something else) i figure i will let it sit a while as I know sometimes it just takes first boot a while to go through however it doesnt seem to be the problem. Have you had a positive install of the LOS? I am wondering if I had maybe gotten a bad copy of the file. When i go to install I get a pass in odin so not quite sure where to go from here other than back to the factory image any help to get this going would be great... I took on this task cause i needed someting to take my mind off the severely crappy week I have had... so looking forward to anything you can share here...
Actually, userdata is the slot I always use. It might work in both though.
Something to mention: there is not enough space on the /system partition to flash Gapps. I created a build that supports it (with a resized /system partition) but I couldn't get it to flash via Odin. The only way I got it to work was by flashing it via TWRP as an img file. I will be posting that soon. Unfortunately that will be the end of development for now as I hard-bricked the device and need to wait for a repair or replacement. Should be back developing in 2 weeks.
Nevermind what I said here.
jayzarry84 said:
Anyone get this to work? I just flashed the TWRP part but have not been able to get into TWRP
Click to expand...
Click to collapse
Get adb access in the OS and then run "adb reboot recovery"
agreenbhm said:
Get adb access in the OS and then run "adb reboot recovery"
Click to expand...
Click to collapse
question. I don't have an OTG cable and TWRP keeps booting. I've tried rebbot, rebbot bootloader, reboot system. any advice?
jayzarry84 said:
question. I don't have an OTG cable and TWRP keeps booting. I've tried rebbot, rebbot bootloader, reboot system. any advice?
Click to expand...
Click to collapse
You may need to get an otg cable for a USB mouse and choose "reboot system" from the gui. Alternatively, look at the /dev/block/by-name/misc partition and try blanking that out with dd. That has worked sometimes.
jayzarry84 said:
question. I don't have an OTG cable and TWRP keeps booting. I've tried rebbot, rebbot bootloader, reboot system. any advice?
Click to expand...
Click to collapse
Also, from an adb shell, try "twrp reboot". Supposedly that should boot to system, but I feel like in testing I got mixed results. According to the TWRP documentation though that should be the answer.
agreenbhm said:
Also, from an adb shell, try "twrp reboot". Supposedly that should boot to system, but I feel like in testing I got mixed results. According to the TWRP documentation though that should be the answer.
Click to expand...
Click to collapse
Not working. I'll wait for my otg cable to come in
jayzarry84 said:
Not working. I'll wait for my otg cable to come in
Click to expand...
Click to collapse
I was able to use adb to run the TWRP Format Data command and it rebooted the tablet and now LOS has booted up. I think I'm good!
Looking forward to see how this develops
Rom is fast and snappy. Brightness control does not work. I haven’t played too much because of work but that’s what I’ve found so far
Can a mod move this to the rom release section?
agreenbhm said:
Something to mention: there is not enough space on the /system partition to flash Gapps. I created a build that supports it (with a resized /system partition) but I couldn't get it to flash via Odin. The only way I got it to work was by flashing it via TWRP as an img file. I will be posting that soon. Unfortunately that will be the end of development for now as I hard-bricked the device and need to wait for a repair or replacement. Should be back developing in 2 weeks.
Click to expand...
Click to collapse
I've not been able to flash this yet but I know that the latest TWRP versions have a way to fix the system partition to accept gapps. /Wipe/Advanced check system then resize. Sometimes you have to do it more than once if it is a large gapps.
lewmur said:
I've not been able to flash this yet but I know that the latest TWRP versions have a way to fix the system partition to accept gapps. /Wipe/Advanced check system then resize. Sometimes you have to do it more than once if it is a large gapps.
Click to expand...
Click to collapse
I will look into that, but I'm not optimistic it will work. This device does not separately present the system partition, rather it uses a super partition which contains system, vendor, product, and odm. TWRP only shows me the super partition for working with. I was able to resize the system partition by expanding the Lineage image and file system on my pc to match the original stock system partition, then rebuilt the super image with the other partitions it needs.
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
Just before we get started, I would like to say that you will not brick your device if you follow the steps as is without any, and I mean any deviations.
Read what works and what doesn't first!
Okay, enough preface, let's jump right in!
Firstly, pre-requisites(hardware):-
1.A micro SD card
2. A windows PC, windows 7 or later (32 or 64 bit)
3. A USB Type-C cable
4. A galaxy tab A7 running the latest one ui 4.x build
Pre-requisites (software on PC), you'll need:
1.Stock firmware:
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
Download the latest firmware from here
1.1 After downloading it, extract it on the PC and copy the AP file to your micro SD card, as we need it on the tab later
2. Samsung USB drivers
download them from here and install them on your pc, it'll take a while but it's essential for this process
https://developer.samsung.com/android-usb-driver
2.1 Reboot your PC after installing the drivers
3 Download the twrp.img from below
https://forum.xda-developers.com/t/...axy-tab-a7-10-4-sm-t500.4358595/post-87038713
(Yes, correct, download the .img as we won't be using Odin to flash custom recovery)
Copy this to your SD card as well
4. Download Canary apk of magisk delta from link below
https://huskydg.github.io/magisk-files/
Copy the apk to your microSD which has the previously extracted AP file
5. Download dynapatch from the file attached below credits to @redymedan for developing this!
Then move it to your micro SD card
6. Download the GSI image of your choice, and (make sure that it doesn't exceed 3.3GB after extraction) extract it from .img.xz format to .img format and then copy it to the micro SD card
(also, if it exceeds 3.3 GB, don't worry,follow the steps in important notes on how to expand your system partition to accommodate larger GSIs...)
7. If your gsi doesn't have gapps or you want to flash a system mod then download a vndklite variant of your gsi, as system is mounted as RW in vndklite gsi, where's system is mounted as read only in normal gsi images
8. Download Odin and extract it
https://samsungodin.com/
9. Download SmartPack kernel manager apk and copy it to the sdcard too
https://github.com/SmartPack/SmartPack-Kernel-Manager/releases
(We will be using this to flash twrp in a later step)
10. Download the brightness and watchdog fix module from below
Copy it to SD card
(Optional) 11. If you don't want your install storage encrypted, download the following two zips and move them to SD card,
[Pie/10/11] [System-as-root] Multidisabler: disables encryption, Vaultkeeper, auto-flash of stock recovery, proca, wsm, cass, etc.
The multi-disabler started life on the Exynos S10 range, the first Samsung devices to launch with Android 9 (Pie). Since then, it has grown to support a great many Samsung devices running either Android 9, 10 or 11, and with either an Exynos or a...
forum.xda-developers.com
https://zackptg5.com/downloads/archive/Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip
Process to flash GSI:
1) Unlock the bootloader
To unlock the bootloader, follow the steps from here...
https://forum.xda-developers.com/t/...4-unlock-bootloader-root-with-magisk.4185993/
2) After that patch the AP image we copied to the micro SD card earlier and then copy the patched ap to the micro sd card and then to the pc. Steps of patching can be found here
https://forum.xda-developers.com/t/...4-unlock-bootloader-root-with-magisk.4185993/
3) After patching the AP image, copy the patched image from downloads folder to your micro sd card
4. After that turn your device off
5. After the device is fully powered off, hold both volume up and volume down buttons simultaneously and connect it to your pc, then click volume up button once during the prompt to enter download mode
6) After entering download mode, select the BL, CP, and CSC (do not choose HOME_CSC!) files from the extracted firmware, after doing that, for AP, select the patched AP file we copied earlier and then click start on Odin.
7. After the flash is successfully finished, reboot your device and set it up, after setup install the magisk Canary apk from the micro SD card
8. After installing the apk, open it, and click 'OK' on additional setup prompt and the device will reboot after a few seconds
9. After the reboot completes, install the smart pack kernel manager apk we put in the SD card earlier, then open it, then, navigate to
Tools>Backup>(swipe to the right where it says "boot partition")> it changes to recovery partition> click on the plus symbol> two options show up, select the flash recovery option> select the twrp image from SD card (file manager opens automatically)> click on "select" and then flash it...
10. Then open magisk delta app, and reboot to recovery
11. After rebooting to recovery, flash dynapatch
12. Then reboot to recovery (very important)
(Optional)12.1 Flash multidisabler we downloaded earlier, along with disable dm Verity to disable FBE on integral storage. Also, if you intend to disable encryption, do flash both the zips not one.
13. Then select install>Micro SD Card>install image> select GSI image you downloaded> select System Image > swipe to flash, then factory reset and wipe data from within twrp (thank you @shorty9210 for the factory reset part!)
14. Here, hectic nature of you must be used...
15. Boot to your GSI, and set it up as fast as possible as a watchdog crash is triggered every 30-50 seconds which causes a reboot
16. Install magisk apk and reboot for additional setup
17. After reboot, open magisk and install the brightness and watchdog fix module
18. Reboot the device after installing module
19. At this point you won't get random reboots
20. Now you can enjoy your GSI...
Now, onto what works and what doesn't...
Working:
Boot
Touchscreen
Sound
WiFi
Bluetooth
Mobile data
Camera
Microphone
Doze
OTG
Power buttons
Volume buttons
Charging
Rotation
Gyroscope
Calling(works with VoIP)
Not working:
VoLTE
In call audio (in case of Sims)
Auto brightness
Offline charging
Untested:
Cast
USB tethering
MTP
Tested roms:
1. Trebledroid GSIs (don't use, as magisk doesn't work and gapps can't be properly installed for some reason)
2. Pixel experience ( magisk works and it's stable after running the watchdog command)
3. Google GSI (vanilla and Gapps, not recommended, due to it being extremely barebones and not having fixes for DT2W, and headsets)
4. Project Elixir (needs watchdog module, but mostly stable)
Now credits!
To team XDA for keeping this forum alive and well,
@phhusson for developing GSI images that actually made this possible
@topjohnwu for creating magisk
@agreenbhm for the TWRP image and for helping me,
@duyfken for correcting the firmware links, and also, for informing me to add the type of GSI for this device!
@shorty9210 for a correction
@huskydg for magisk delta development
And finally all other members of XDA for taking interest in the modding scene,
Thank you!
I'm quite new to the GSIs as a whole, so, I still can't find any workarounds for issues, I can only list them for everyone to know...
Important notes:
1. If your GSI has phh settings, do the following...
1.1 Enable double tap to wake
Settings>Phh Treble settings>Samsung features >Tick "Enable difficult tap to wake"
1.2 For making headphones work,
Settings>Phh Treble settings>Misc features>Tick "Use alternate way to detect headsets"
Also, Enable developer options>Enable "Disable Bluetooth A2DP hardware offload" and restart when prompted
2. If the gsi ROM you're trying to flash doesn't fit on current system partition, then,
*This process will wipe your system partition and will reset your recovery, so, keep the dynapatch zip and gsi image on hand, you will need it!*
Download latest platform tools from AOSP site, link below
https://developer.android.com/studio/releases/platform-tools
https://forum.xda-developers.com/t/...xy-tab-a7-10-4-sm-t500.4371123/#post-86050459
a) download the product.img from above link
b)Reboot to recovery from magisk app, then, in twrp, click on 'Reboot' button
c) click 'fastboot'
d) the device will now reboot and then after a few seconds, a twrp ui will appear with the text 'fastboot'
e) connect your device to a pc with the latest version of platform tools and drivers installed
f) run these commands in order
fastboot flash product product.img
fastboot erase system
fastboot resize-logical-partition system 3940000000
fastboot reboot recovery
g) after doing so, again reboot to recovery, flash dynapatch zip first
h) again reboot to recovery and flash your gsi image
i) this time images up to 3.9GB will be flashable
j) no need to format data if you're flashing same rom
And that's it you'll be able to enjoy bigger ROMs on your Galaxy Tab A7!
3. follow steps from here to get 4-speaker audio!
Post in thread '[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 19.1 (and TWRP 3.6.1)'
[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 19.1 (and TWRP 3.6.1)
Hello world, I have successfully built LineageOS 19.1 with Gapps for the SM-T500 (Tab A7 10.4 2020) using Andy Yan's LOS GSIs. Lineage is current as of 3/24/2022. I have also compiled TWRP version 3.6.1, based on Android 11 (previous release...
forum.xda-developers.com
4. Previously, we had to use either some magisk modules or SmartPack kernel manager to enable swap so that the device won't crash under load, but, now, 2GB of swap is allocated by default, which is plenty sufficient for daily usage, so, i recommend you not to use any modules or services that enable swap....
5. If zygisk is enabled after module is installed, some users reported that it breaks brightness fix, to remedy that, try flashing permissiver_v5 from below in twrp
Permissiver_v5.zip | by erfanoabdi for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
6. Also, please do not rely on extra dim if brightness fix module won't work, try above step , i did this previously and the edges of my screen got ruined(ghost imaging) due to the heat...
7. Please refrain from using any modules that spoof the device identity as it causes the phh Treble app to not display "Samsung features" at which point you can't use DT2W, so beware...
8. Recommended settings in magisk delta
a)magisk delta>settings>hide magisk app, you will be prompted to allow magisk delta to install apps, allow it and start the hiding> now, the magisk app will be under an alias you chose
b)magisk delta>settings>Zygisk(enable)
c)magisk delta>settings>Bootloop Protection (enable)
d)magisk delta>settings>Magisk Hide
9. Passing safetynet on Gapps GSIs
a)magisk delta>settings>Configure MagiskHide> now, tap on three dots, elect show system apps>then tick the boxes next to the following apps
Google Play Store, Google Play Services, Google Services Framework
b) Install the magisk module "shamiko" version 0.5.2, as later version causes Google services to crash... Download link below(warning, shamiko 0.6 causes all Google services to crash, also, is no longer working with magisk delta, so, use magiskhide present in the delta version)
https://github.com/LSPosed/LSPosed.github.io/releases/tag/shamiko-120
(Optional) You can also install this module below after installing shamiko for a higher chance to not fair safetynet randomly...
Releases · kdrag0n/safetynet-fix
Google SafetyNet attestation workarounds for Magisk - kdrag0n/safetynet-fix
github.com
c) After installing the module, reboot
d) clear data and cache for Google Play Store, Google Play Services, Google Services Framework
e) at this point you should pass safetynet successfully
10. Just a heads up, be sure to only download GSIs from the list in @phhusson GitHub, i.e, link below,
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
And, do not spend money on people that claim to give the "best GSIs" or whatever gibberish they use, only spend money as a donation to a developer, if you really enjoy their work, and would like to support them to keep up thier interest!
I had to mention this to put you on the cautious side of things!
11. Taskbar height is incorrect on some roms, and the magisk module from below link fixes it, credits to @wEER1234 for mentioning this, and to @Coxxs for delaying developing it!
Releases · Coxxs/hide-tablet-taskbar
A Magisk module to hide tablet gesture bar and more [Android 12.1+] - Coxxs/hide-tablet-taskbar
github.com
12. This is for improving the longevity of your device
12.1 To prolong the lifespan of your battery, install the "acc" magisk module, reboof, open a root terminal and run the following commands
acc -s mcc=200
acc -s mcc=3900
The first command limits the charging current to 200 mA and charges the battery at a power of 1.8W which greatly reduces the strain and heat evolved by the battery, and the second command only allows your battery to charge up to 3.9v (52%), as according to battery University, maximum cycles can be achieved by maintaining the voltage battery 3.9 and 3.7
12.2 This is to reduce the Power and heat evolved by the processor
Install smart pack kernel manager, grant root access, go to cpu section, and do the following
Big cpu cores:
Maximum frequency:1056Hz
Minimum frequency:902Hz
Little cpu cores:
Maximum frequency: 1017Hz
Minimum frequency:864Hz
At these frequencies the device stays stable and relatively less hot than at higher clocks...
* This guide is present for legacy reasons, use the guide in the first post *
Just before we get started, I would like to say that you will not brick your device if you follow the steps as is without any, and I mean any deviations.
Read what works and what doesn't first!
Okay, enough preface, let's jump right in!
Firstly, pre-requisites(hardware):-
1.A micro SD card
2. A windows PC, windows 7 or later (32 or 64 bit)
3. A USB Type-C cable
4. A Samsung galaxy tab a7 running Android 11 with January 2022 Security Patch
Pre-requisites (software on the pc), you'll need:-
1.Stock firmware:
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
from this link, select your respective country and download the firmware with January 2022 security patch level, then download it
1.1 After downloading it, extract it on the PC and copy the AP file to your micro SD card, as we need it on the tab later
2. Samsung USB drivers
download them from here and install them on your pc, it'll take a while but it's essential for this process
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
2.1 Reboot your PC after installing the drivers
3. Download TWRP 3.6.1 beta 5 from here
[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 19.1 (and TWRP 3.6.1)
Hello world, I have successfully built LineageOS 19.1 with Gapps for the SM-T500 (Tab A7 10.4 2020) using Andy Yan's LOS GSIs. Lineage is current as of 3/24/2022. I have also compiled TWRP version 3.6.1, based on Android 11 (previous release...
forum.xda-developers.com
this is our custom recovery
4. Download magisk Canary apk from here
GitHub - topjohnwu/Magisk: The Magic Mask for Android
The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.
github.com
And copy the apk to your micro SD card
5. Download the SM-T500-GSI-kernel.zip from here
[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...
forum.xda-developers.com
And copy this file to your micro SD card
6. Download dynapatch from the file attached below credits to @redymedan for developing this!
Then move it to your micro SD card
7. Download the GSI image of your choice, and (make sure that it doesn't exceed 3.3GB after extraction) extract it from .img.xz format to .img format and then copy it to the micro SD card
7.1 If your gsi doesn't have gapps or you want to flash a system mod (eg. Brightness fix) then download a vndklite variant of your gsi, as system is mounted as RW in vndklite gsi, where's system is mounted as read only in normal gsi images
GSI type should be "arm64_ab" if you want to you can also use vndklite variant!
8. Download Odin and extract it
Samsung Odin - Official Odin Download links
Samsung Odin, Official Odin Download links and flashing guides
samsungodin.com
These are all the pre requisites, and yes, every single one is required.
Process to flash GSI:
1) Unlock the bootloader
To unlock the bootloader, follow the steps from here...
[Guide][SM-T500/T505] Galaxy Tab A7 10.4 - Unlock Bootloader & Root with Magisk
I recently purchased the Galaxy Tab A7 10.4 (released in 2020) and couldn't help but notice that there's no dedicated thread in the forums for unlocking the bootloader or rooting (Although, the method should be very similar to what is followed...
forum.xda-developers.com
2) After that patch the AP image we copied to the micro SD card earlier and then copy the patched ap to the micro sd card and then to the pc. Steps of patching can be found here
[Guide][SM-T500/T505] Galaxy Tab A7 10.4 - Unlock Bootloader & Root with Magisk
I recently purchased the Galaxy Tab A7 10.4 (released in 2020) and couldn't help but notice that there's no dedicated thread in the forums for unlocking the bootloader or rooting (Although, the method should be very similar to what is followed...
forum.xda-developers.com
3. After patching the AP image, copy the patched image from downloads folder to your micro sd card
4. After that turn your device off
5. After the device is fully powered off, hold both volume up and volume down buttons simultaneously and connect it to your pc, then click volume up button once during the prompt to enter download mode
6) After entering download mode, select the BL, CP, and CSC (do not choose HOME_CSC!) files from the extracted firmware, after doing that, for AP, select the patched AP file we copied earlier and then click start on Odin.
7. After the flash is successfully finished, reboot your device and set it up, after setup install the magisk Canary apk from the micro SD card
8. After installing the apk, open it, and click 'OK' on additional setup prompt and the device will reboot after a few seconds
9. After the device starts up, turn it off again, and put it in download mode by holding both volume buttons simultaneously and then connecting it to your pc
10. After that, uncheck everything in Odin except AP, and select the TWRP file we downloaded as the AP file, and then click start
11. After the flash is complete, turn the device off and then hold power+volume up and then immediately connect it to your pc immediately
12. You will get warning about custom binary, and xyz, but ignore it and press power button once, then you'll enter the TWRP recovery
13. After entering TWRP flash the dynapatch zip file from your micro SD card
14. After flashing it. use the reboot to recovery option
15. After you device booted to recovery again, go to Wipe>Advanced Wipe and then wipe dalvik cache and cache partition
16. After wiping them, go back to the install section, click on install image
17. After that select your GSI .img file you extracted earlier
18. Then it will ask you on which partition it should flash the image onto
19. You have to select 'System Image' partition (if it isn't available, then flash dynapatch again and reboot to recovery, do it as may times until the System Image partition shows up)
20. Then swipe to flash it,
21. After it flashes, go back to install and install the T500 Kernel zip we put in the micro SD card earlier (this is to prevent reboots after a few seconds)
22. And bam, you're done, set the GSI up, and enjoy!
Now, let's get onto what works and what doesn't
What works:- (will add more as I keep testing)
Boot
Touchscreen
SD Card
Cameras
Speaker (follow point 7 in additional notes for 4-speaker audio!)
Headphones (disable A2DP offload in PHH settings first)
Wifi
Bluetooth
Mobile data
Wifi hotspot
Microphone
Power button
Volume Buttons
4G mobile data (go to mobile networks and select preferred network as 4G first)
Auto rotation
Extra dim
SMS
Charging
HW acceleration
MTP
USB Tethering
OTG
Brightness*
( Run these commands in a terminal emulator
su
echo 100 > /sys/class/backlight/panel0-backlight/brightness)(this is not persistent you have to run this everytime you reboot or you can setup a script or something that runs it during boot time itself)
What doesn't work:-
VoLTE
In call audio
Tested roms:
1. Pixel experience
2.ProtonAOSP
3.crDroid
4. Lineage OS
Not tested:-
Cast (i can't test this I don't have anything to cast to)
* Also be sure to read the important notes as it has highlighted some common issues and their workarounds...
Now credits!
To team XDA for keeping this forum alive and well,
@phhusson for developing GSI images that actually made this possible
@topjohnwu for creating magisk
@agreenbhm for the TWRP image and for helping me,
@duyfken for correcting the firmware links, and also, for informing me to add the type of GSI for this device!
And finally all other members of XDA for taking interest in the modding scene,
Thank you!
I'm quite new to the GSIs as a whole, so, I still can't find any workarounds for issues, I can only list them for everyone to know...
Important notes:-
1) if you are stuck in twrp after selecting reboot to system, then go to Advanced>Terminal and type exit_twrp and then reboot to system
2)The brightness patch has not worked for me on any gsi vndklite or normal, so, if it works for you then you are lucky, if not then I have informed you (brightness fix is in the initial post!)
3) I didn't try OTA updates as we used dynapatch and I'm skeptical about OTAs, so, i recommend you to dirty flash any new releases normally from twrp
4) Disable 'A2DP hardware offload' in Phh Settings>Misc settings and check the box next to disable A2DP offload and then do the same in developer settings too
5) Themed icons causes lags and causes some apps to lock the device up, so, proceed with caution
6) If the gsi ROM you're trying to flash doesn't fit on current system partition, then,
*This process will wipe your system partition and will reset your recovery, so, keep the dynapatch zip and gsi image on hand, you will need it!*
a) Download twrp from the link below (as it has fastboot)
[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
b) Also download the product.img file from the above link
c) Flash this recovery from existing twrp
d) boot to this new twrp
e) here, click on 'Reboot' button
f) click 'fastboot'
g) the device will now reboot and then after a few seconds, a twrp ui will appear with the text 'fastboot'
h) connect your device to a pc with the latest version of platform tools and drivers installed
i) run these commands in order
fastboot flash product product.img
fastboot erase system
fastboot resize-logical-partition system 3940000000
fastboot reboot recovery
j) after doing so, again reboot to recovery, flash dynapatch zip first
k) again reboot to recovery and flash your gsi image
l) this time images up to 3.9GB will be flashable
m) no need to format data if you're flashing same rom
And that's it you'll be able to enjoy bigger ROMs on your Galaxy Tab A7!
Credit goes to @paziusss for this!
7) follow steps from here to get 4-speaker audio!
Post in thread '[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 19.1 (and TWRP 3.6.1)' https://forum.xda-developers.com/t/...eos-19-1-and-twrp-3-6-1.4421365/post-86917225
8. To flash gapps you need to have a Vndklite variant of GSI installed, then, grab your favourite set of gapps (Android 12L/12) depending on your rom and flash them from twrp!
9. For more fluid performance, download "Smart Pack Kernel Manager" from fdroid, open it grant root access, then go to the hamburger menu, select Vritual memory, and move the slider to 2048 mb, then, enable apply on boot, and reboot your device!
Well, I'm back everyone, and I'll be updating the post #1 with new instructions with regards to running Android 13 GSIs, and post #2 contains the old guide in case someone needs it!
Wow. Thank u very very much..will prepared guide ...every thing is clear
One thing i might clarify which is found on pazinuss. Guide. Where he put kernell
Q: Which GSI variant should I choose?
A: arm64 ab. Use the vndklite variant if you want to flash gapps or fix the brightness
The brightness fix is there with kernel also .
Thank you .....🖐️🖐️
drsanusi said:
Wow. Thank u very very much..will prepared guide ...every thing is clear
One thing i might clarify which is found on pazinuss. Guide. Where he put kernell
Q: Which GSI variant should I choose?
A: arm64 ab. Use the vndklite variant if you want to flash gapps or fix the brightness
The brightness fix is there with kernel also .
Thank you .....🖐️🖐️
Click to expand...
Click to collapse
I didn't mention it, as I found out that extra dim intensity control does the job just fine, but I'll add it in either way, thanks!
Hausemaster said:
I didn't mention it, as I found out that extra dim intensity control does the job just fine, but I'll add it in either way, thanks
Click to expand...
Click to collapse
What i mean for who want to flash gapps or root by magisk or flash any file to the rom (vndklite) only support flashing because it is mounted Read and Write but others are Read only .
Thank you
drsanusi said:
What i mean for who want to flash gapps or root by magisk or flash any file to the rom (vndklite) only support flashing because it is mounted Read and Write but others are Read only .
Thank you
Click to expand...
Click to collapse
We initially patched AP file initially, so, magisk will be available even after you flash a gsi but yeah you're correct about the gapps part, I forgot about them as I'm using a Pixel experience gsi, I'll add in the part about vndklite, thanks!
Edit: added it!
Again after step 7 when restart ...the message. (only official binary vbmeta allowed). In red .????.
So disturbing .i do googled revise my steps .even on odin this appear.
On thing i noticed. In developer mode .the oem unlock tab not appear at all.. but before was there ....what i miss ?? Any suggestions
drsanusi said:
Again after step 7 when restart ...the message. (only official binary vbmeta allowed). In red .????.
So disturbing .i do googled revise my steps .even on odin this appear.
On thing i noticed. In developer mode .the oem unlock tab not appear at all.. but before was there ....what i miss ?? Any suggestions
Click to expand...
Click to collapse
Did you boot to system and verify that bootloader was in fact unlocked, as, vaultkeeper will lock bootloader if you don't boot to system after unlocking...
Edit: if you directly flashed without booting, bootloader will relock and you have to wait for 7 days for OEM unlocking to be available again...
Now. After few days of lineage 19
Works like charm wow ...i am happy how lineage rom evolved over these years .
My main concern is battery life i left the tab for 24hr no any drop at all.before on stock was strange drop .
Other things . brightness fix didnt work .
Now one quistion ..if i want to try another one rom what i do .? From the bigening or what step i start
Thank u in advance
drsanusi said:
Now. After few days of lineage 19
Works like charm wow ...i am happy how lineage rom evolved over these years .
My main concern is battery life i left the tab for 24hr no any drop at all.before on stock was strange drop .
Other things . brightness fix didnt work .
Now one quistion ..if i want to try another one rom what i do .? From the bigening or what step i start
Thank u in advance
Click to expand...
Click to collapse
If you want to try another ROM, I suggest you to start from setup 15
drsanusi said:
Now. After few days of lineage 19
Works like charm wow ...i am happy how lineage rom evolved over these years .
My main concern is battery life i left the tab for 24hr no any drop at all.before on stock was strange drop .
Other things . brightness fix didnt work .
Now one quistion ..if i want to try another one rom what i do .? From the bigening or what step i start
Thank u in advance
Click to expand...
Click to collapse
Also, the battery drop may be because of GSI roms not setting cpu frequency according to usage, it just locks it at full frequency causing heat and heavy battery drain, try lowering clockspeeds using a kernel manager
edit: I use smart pack kernel manager
drsanusi said:
Now. After few days of lineage 19
Works like charm wow ...i am happy how lineage rom evolved over these years .
My main concern is battery life i left the tab for 24hr no any drop at all.before on stock was strange drop .
Other things . brightness fix didnt work .
Now one quistion ..if i want to try another one rom what i do .? From the bigening or what step i start
Thank u in advance
Click to expand...
Click to collapse
I found the actual brightness fix from the thread which we downloaded kernel from, I added the commands in the OP here...
If you're flashing big GSIs and flash fails due to insufficient system space, I've added a way to do so in the important notes...
Hausemaster said:
Just before we get started, I would like to say that you will not brick your device if you follow the steps as is without any, and I mean any deviations.
Read what works and what doesn't first!
Okay, enough preface, let's jump right in!
Firstly, pre-requisites(hardware):-
1.A micro SD card
2. A windows PC, windows 7 or later (32 or 64 bit)
3. A USB Type-C cable
4. A Samsung galaxy tab a7 running Android 11 with January 2022 Security Patch
Pre-requisites (software on the pc), you'll need:-
1.Stock firmware:
Samsung Galaxy Tab A7 (Wi-Fi) Firmware Download SM-T500 Free Download
Samsung Galaxy Tab A7 (Wi-Fi) Firmware Download SM-T500 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
from this link, select your respective country and download the firmware with January 2022 security patch level, then download it
1.1 After downloading it, extract it on the PC and copy the AP file to your micro SD card, as we need it on the tab later
2. Samsung USB drivers
download them from here and install them on your pc, it'll take a while but it's essential for this process
https://developer.samsung.com/android-usb-driver
2.1 Reboot your PC after installing the drivers
3. Download TWRP 3.6.1 beta 5 from here
[ROM][SM-T500] Samsung Galaxy Tab A7 10.4 (2020) - LineageOS 19.1 (and TWRP 3.6.1)
Hello world, I have successfully built LineageOS 19.1 with Gapps for the SM-T500 (Tab A7 10.4 2020) using Andy Yan's LOS GSIs. Lineage is current as of 3/24/2022. I have also compiled TWRP version 3.6.1, based on Android 11 (previous release...
forum.xda-developers.com
this is our custom recovery
4. Download magisk Canary apk from here
https://github.com/topjohnwu/Magisk
And copy the apk to your micro SD card
5. Download the SM-T500-GSI-kernel.zip from here
[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...
forum.xda-developers.com
And copy this file to your micro SD card
6. Download dynapatch from the file attached below credits to @redymedan for developing this!
Then move it to your micro SD card
7. Download the GSI image of your choice, and (make sure that it doesn't exceed 3.3GB after extraction) extract it from .img.xz format to .img format and then copy it to the micro SD card
7.1 If your gsi doesn't have gapps or you want to flash a system mod (eg. Brightness fix) then download a vndklite variant of your gsi, as system is mounted as RW in vndklite gsi, where's system is mounted as read only in normal gsi images
8. Download Odin and extract it
Samsung Odin - Official Odin Download links
Samsung Odin, Official Odin Download links and flashing guides
samsungodin.com
These are all the pre requisites, and yes, every single one is required.
Process to flash GSI:
1) Unlock the bootloader
To unlock the bootloader, follow the steps from here...
https://forum.xda-developers.com/t/...4-unlock-bootloader-root-with-magisk.4185993/
2) After that patch the AP image we copied to the micro SD card earlier and then copy the patched ap to the micro sd card and then to the pc. Steps of patching can be found here
[Guide][SM-T500/T505] Galaxy Tab A7 10.4 - Unlock Bootloader & Root with Magisk
I recently purchased the Galaxy Tab A7 10.4 (released in 2020) and couldn't help but notice that there's no dedicated thread in the forums for unlocking the bootloader or rooting (Although, the method should be very similar to what is followed...
forum.xda-developers.com
3. After patching the AP image, copy the patched image from downloads folder to your micro sd card
4. After that turn your device off
5. After the device is fully powered off, hold both volume up and volume down buttons simultaneously and connect it to your pc, then click volume up button once during the prompt to enter download mode
6) After entering download mode, select the BL, CP, and CSC (do not choose HOME_CSC!) files from the extracted firmware, after doing that, for AP, select the patched AP file we copied earlier and then click start on Odin.
7. After the flash is successfully finished, reboot your device and set it up, after setup install the magisk Canary apk from the micro SD card
8. After installing the apk, open it, and click 'OK' on additional setup prompt and the device will reboot after a few seconds
9. After the device starts up, turn it off again, and put it in download mode by holding both volume buttons simultaneously and then connecting it to your pc
10. After that, uncheck everything in Odin except AP, and select the TWRP file we downloaded as the AP file, and then click start
11. After the flash is complete, turn the device off and then hold power+volume up and then immediately connect it to your pc immediately
12. You will get warning about custom binary, and xyz, but ignore it and press power button once, then you'll enter the TWRP recovery
13. After entering TWRP flash the dynapatch zip file from your micro SD card
14. After flashing it. use the reboot to recovery option
15. After you device booted to recovery again, go to Wipe>Advanced Wipe and then wipe dalvik cache and cache partition
16. After wiping them, go back to the install section, click on install image
17. After that select your GSI .img file you extracted earlier
18. Then it will ask you on which partition it should flash the image onto
19. You have to select 'System Image' partition (if it isn't available, then flash dynapatch again and reboot to recovery, do it as may times until the System Image partition shows up)
20. Then swipe to flash it,
21. After it flashes, go back to install and install the T500 Kernel zip we put in the micro SD card earlier (this is to prevent reboots after a few seconds)
22. And bam, you're done, set the GSI up, and enjoy!
Now, let's get onto what works and what doesn't
What works:- (will add more as I keep testing)
Boot
Touchscreen
SD Card
Cameras
Speaker
Headphones (disable A2DP offload in PHH settings first)
Wifi
Bluetooth
Mobile data
Wifi hotspot
Microphone
Power button
Volume Buttons
4G mobile data (go to mobile networks and select preferred network as 4G first)
Auto rotation
Extra dim
SMS
Charging
HW acceleration
MTP
USB Tethering
OTG
Brightness*
( Run these commands in a terminal emulator
su
echo 100 > /sys/class/backlight/panel0-backlight/brightness)(this is not persistent you have to run this everytime you reboot or you can setup a script or something that runs it during boot time itself)
What doesn't work:-
VoLTE
In call audio
Haptic Feedback (vibration)
Not tested:-
Cast (i can't test this I don't have anything to cast to)
* Also be sure to read the important notes as it has highlighted some common issues and their workarounds...
Now credits!
To team XDA for keeping this forum alive and well,
@phhusson for developing GSI images that actually made this possible
@topjohnwu for creating magisk
@agreenbhm for the TWRP image and for helping me,
And finally all other members of XDA for taking interest in the modding scene,
Thank you!
Click to expand...
Click to collapse
Also! This tab does not have a Vibration motor so you might wanna remove that from the "What doesn't work:-" List.
wEER1234 said:
Also! This tab does not have a Vibration motor so you might wanna remove that from the "What doesn't work:-" List.
Click to expand...
Click to collapse
I didn't know that this didn't have one, thanks for the information, will do the necessary changes now!
This may be a silly question, but why exactly are we using the SM-T500 firmware here and not the SM-T505 firmware?
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
duyfken said:
This may be a silly question, but why exactly are we using the SM-T500 firmware here and not the SM-T505 firmware?
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download
Samsung Galaxy Tab A7 (LTE) Firmware Download SM-T505 Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website
samfw.com
Click to expand...
Click to collapse
The firmware is of the t505 version, only the kernel, recovery and other stuff is from t500 as they work and are the only resources available for this device...
Edit: The link preview itself mentioned SM-T505, so, yeah...
Hausemaster said:
The firmware is of the t505 version, only the kernel, recovery and other stuff is from t500 as they work and are the only resources available for this device...
Edit: The link preview itself mentioned SM-T505, so, yeah...
Click to expand...
Click to collapse
I ask as Post 1 instructions has SM-T500 firmware, hence why I linked the SM-T505 firmware here.
Also for reference for those trying to work out which type of GSI image to get when downloading one (from a stock as a rock SM-T505):
{
"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"
}
duyfken said:
I ask as Post 1 instructions has SM-T500 firmware, hence why I linked the SM-T505 firmware here.
Also for reference for those trying to work out which type of GSI image to get when downloading one (from a stock as a rock SM-T505):
Click to expand...
Click to collapse
Oh my! Thanks for the sharp observation, I corrected it now in the OP
Edit: I also added the type of GSI that should be used for this device!
Edit 2: I also mentioned you in the credits, as you're the one who caught the errors! And once again, thank you very much for the corrections you saved the day!