Related
Hello
This is TWRP v 2.8.1.0 for the S4 Mini. It works for the I9195 - I do not know if it works for similar devices.
The problem was that TWRP after version 2.7.1.0 did not boot up - the phone tried to enter recovery mode but eventually booted into android.
This is because of commit https://gerrit.omnirom.org/#/c/8471/ which does not seem to work nice with the S4 Mini.
DISCLAIMER : You apply this recovery at your own risk - if something breaks or bricks I am not responsible
IMPORTANT NOTE :
a) The attached file is NOT a flashable ZIP and I will not provide one. You have to unpack the attached file and use heimdall or dd. If someone wants to provide a flashable zip - I am fine with that.
b) There is no F2FS support.
c) I do not know if there are still problems with the recovery sometimes not booting up - I tried it a couple of times and it worked every time. Tell us if you experience booting problems.
d) I am no coder - so I cannot help with things like encryption, luks or similar wishes.
How to install:
a) Boot your phone to download mode
b) Connect phone to PC
c) Get root on your PC
d) Unzip attached ZIP file
e) Check md5sum
f) heimdall flash --RECOVERY recovery.img --no-reboot (dd should work as well - take care of the right partition)
Thanks goes to:
Teamwin
OliverG96
_that
Additional information:
If you want to build this by yourself from sources open file twrp-functions.cpp and search for line:
Code:
int TWFunc::Set_Brightness(std::string brightness_value)
You can change it like that:
Code:
int TWFunc::Set_Brightness(std::string brightness_value)
{
return 0;
std::string brightness_file = DataManager::GetStrValue("tw_brightness_file");;
This should fix the problem. According to one of the developers there should also be a flag for specifying a brightness file that one can probably set to /nobrightness.
It works great on my I9195 !
From your recovery, i created the Odin version and flashed it.
Thank you very much.
I attach the Odin version of your recovery (Instructions: unzip the .zip file, and flash the .tar.md5 file with Odin 3.09 into AP field)
Recovery flashable ZIP version of TWRP 2.8.1.0 attached.
Mounting both (Internal and External) doesnt work
mike_san said:
Mounting both (Internal and External) doesnt work
Click to expand...
Click to collapse
What do you mean? Mounting works for me - I can mount System and Micro SDCard and I can access the files there with the TWRP File Manager. So no problem here. Works also with adb - I got access to the full file system. Might be a problem with your phone/setup.
thomson.aa said:
What do you mean? Mounting works for me - I can mount System and Micro SDCard and I can access the files there with the TWRP File Manager. So no problem here. Works also with adb - I got access to the full file system. Might be a problem with your phone/setup.
Click to expand...
Click to collapse
I confirm this.
I tried to mount and unmount System, Data and micro Sdcard... all ok.
Will it work with f4k kernel ?
lars85destroyer: both CM 12 and f4k work fine with or. As the recovery used isn't kernel dependent anyway, it's not an issue.
Works great so far, noticed only one (minor) issue:
I need to use encryption for my phone and for its backups as well (I'm a sysadmin and my phone is fully equipped to access my datacenter). When using keyboard to type encryption/decryption passwords, somethimes I hit one key and completely another key gets pressed, can't be due to fat fingers because wrong key that gets pressed is usually very far from the original one. This was very iritating sometimes since I needed to type passwords for 3-4 times in a row for them to work. Figured out how to prevent this, I look at whole keyboard carefully on every keystroke and I'm usually able to see when it gets buggy and hits wrong key (keystroke animation is trigerred), but this isn't very fast or comfortable...
I think I had the same problem with early versions of TWRP 2.7 posted here but it has been resolved in newer ones. Otherwise, works as a charm, if someone added full F2FS support it would be totally perfect
PS If my memory serves me well, fix was build.prop related.
ericlnu said:
lars85destroyer: both CM 12 and f4k work fine with or. As the recovery used isn't kernel dependent anyway, it's not an issue.
Click to expand...
Click to collapse
works fine on aicp, Thanks
s.basketbuild.com/devs/F4k/twrp/serranoltexx
this one have F2FS
CTR Recovery for Galaxy A5
Hi all,
I've ported CTR Recovery from the developer carliv (now bluefirebird) on our Galaxy A5.
This recovery is based on the old CWM, by koush, with some features you can find in the original post HERE, so if you are tired of the TWRP recovery and u are looking for something similar to the old CWM, don't hesitate to download this
NOTE: It should work in any A500 variant, but it's tested only on SM-A500FU variant, so flash on other variants at your own risk!
Desclaimer:
Code:
echo "I'm not responsable for bricked phones, overheat phones, for global warming, for phones that want to suicide without a reason and for imminent explosions"
DOWNLOADS: You can download the recovery here: https://www.androidfilehost.com/?w=files&flid=82499
HOW TO FLASH:
ON WINDOWS (Odin method)
1) Download Odin
2) Download the recovery (with .tar extension)
3) Go in download mode by pressing Power Button + Vol - + Home Button
4) Connect your smartphone to the PC
5) Open odin version 3.9 or 3.10
6) Select AP button and open the recovery file
7) Press start
8) Enjoy
ON LINUX (Heimdall method):
1) Extract tar file with:
$ tar xvf recovery_file.tar
You will find a recovery.img file
2) Open Heimdall Frontend
3) Select pit file (you can find it on sammobile)
4) Select recovery partition
5) Load the recovery.img file and flash
6 Enjoy
ON ANDROID (Need Root)
1) Download flashify or rashr
2) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
3) Open flashify or rashr and select recovery file
4) Flash it
5) Enjoy
ON RECOVERY
IF YOU ARE ON TWRP:
1) Extract recovery file with apps such as zArchiver and you will find a recovery.img file
2) Reboot to recovery
3) Go to install zip menu
4) Select "Install Image" box
5) Select recovery.img file and flash in recovery partition
6) Reboot to recovery
6) Enjoy
ON TERMINAL
If you are on Android (any rom, TWRP, or CTR) (Need Root)
1) Open terminal. If you are on CTR you need Aroma FileManager
2) run:
$ dd if=/path/to/recovery.img of=/dev/block/bootdevice/by-name/recovery
If you are on adb run:
$ adb shell dd=/path/to/recovery.img (inside the phone, not the path of the recovery.img stored in the pc) of=/dev/block/bootdevice/by/name/recovery
3) Enjoy
[NEW] CTR with CWM graphics section
Well, since CWM support ended with cm-11.0, and no one resurrected it, I've decided to give my contributo to the best recovery (in my opinion) which written the begin of android customization, for flashing zip roms, take nandroid backups... So, as I said, since no one resurrected it, I've decided to modify ctr sources, which are based on CWM recovery and which are compilable in cm-12.1 and cm-13.0, for creating a recovery which has, CTR features, but which really like the old CWM.
-So, what does this version offer?
~If you want to know what does it include, please see read this (green highlighted text)
NOTE: If you want to compile with cwm recovery you need my fork which you can find here:
https://github.com/DeadSquirrel01/carliv_touch_recovery_new only cm-12.1 branch for the moment
Then you need to add in BoardConfig.mk (in the device tree) the following flag:
USE_CWM_GRAPHICS := true
otherwise it will compile standard CTR
Flashing instuctions:
Look at "HOW TO FLASH" section
Download Link: Same as CTR recovery link, but you have to download the ones wich have a name which begins with "[CWM]"
OTHER NOTE: Since I've compiled CTR with CWM graphich with an half crapped cm-12.1 source tree, and adb doesn't work (except in sideload), I couldn't take screenshot, so, I've uploaded some photos, instead, which are taken with my ~4 years ago Samsung Galaxy Pocket, so don't flame me for bad quality , and since I tried to upload in attachments, but it doen't show the photo when clicking on the attachment, I've upload a zip with 4 screenshots
HERE (Google Drive Link)
Credits:
@bluefirebird for recovery sources
@TheWhisp for device tree
Me (DeadSquirrel01) for porting the recovery , adding CWM graphics, editing images and adding some cwm features
Sources:
Device Tree: https://github.com/DeadSquirrel01/android_device_samsung_a5-common
CTR: https://github.com/carliv/carliv_touch_recovery_new
CTR with CWM graphics: https://github.com/DeadSquirrel01/carliv_touch_recovery_new branch cm-12.1 only for the moment and you need to add "USE_CWM_GRAPHICS := true" in BoardConfig.mk
Changelog
03/09/2016 (update N2):
_ Add menu color change: you can now change highligh+text color to 3 different colors: blue (default), green or orange.
See my github commit for info, I wrote some awesome comments
06/10/2017 (Update N3):
_Save menu color setting to /sdcard/clockworkmod/cwm_config, so that it's not lost on reboot, resulting a recovery which has always the blue color, even if the user has chosen orange or green.
Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.
Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work
oss_mosis said:
Thanks for this contribution, try it just have time. For now, I walk with your version of TWRP working well. This CTR Recovery is compatible for install ROMs Marshmallow (Base Stock and CM13 Based)? Cheers.
Click to expand...
Click to collapse
Yes you can install roms
meemb said:
Thank you DeadSquirrel01 it works perfectly on my A500G running stock marshmallow 6.0.1. Great work
Click to expand...
Click to collapse
Thanks for the support
you welcome brother
DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse
DeadSquirrel01 said:
Yes you can install roms
Thanks bro, unfortunately I have not been able to prove that the screen of my Galaxy A5 is broken and the phone is unusable for now, but I have already shared this Post on Facebook Group so that other users go testing, any news will be reporting here.
A hug. :good:
Click to expand...
Click to collapse
Thanks bro
Nice Recovery.. Succesfully rooted my stock 6.0.1 by flashing supersu (you can flash this file to root on any android which have custom recoveries) on this recovery. It is like stock recovery but with a lot of features.
@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...
corsicanu said:
@DeadSquirrel01 works well on A500F (Duos). Also i tried to get stuck in recovery mode with no succes . So i can say it`s better than twrp. I was waiting for this moment since i got the phone . Many many thanks! Cheers!
LE: Wait a second... So how this recovery has almost 3 months and isn`t that known?
LE2: Some feedback - mount usb storage doesn`t do anything (yes i have sdcard). Also no adb support. So is kinda impossible to push files into phone while it`s in recovery...
Click to expand...
Click to collapse
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now
DeadSquirrel01 said:
You can only use sideload regarding adb and i think it isn't known coz everyone use only twrp now
Click to expand...
Click to collapse
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..
corsicanu said:
Personally i`m more with CWM.. Simple and yet so complex. TWRP is a bit more polished on the UI side, but that bug that keeps me in the recovery drives me crazy [emoji35] . This CTR recovery it`s able to reset the flag and push the device out of recovery... So it`s better IMO.
Anyway i read here and there that Nougat based roms can be flashed in CWM 6.0.5.x so i`ll try to port Philz latest recovery on our device, since i had it for years on my retired devices. Thanks for all your work and for the source!
LE: Sideload doesn`t work since adb isn`t enabled on the recovery..
Click to expand...
Click to collapse
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port
DeadSquirrel01 said:
Windows adb? With linux adb works perfectly but with windows adb not ¯\_(ツ)_/¯
And... good luck with your philz port
Click to expand...
Click to collapse
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Cheers!
So i rebooted in linux and here`s the output:
Code:
[email protected] ~ $ adb devices
List of devices attached
???????????? no permissions
[email protected] ~ $ adb shell
error: insufficient permissions for device
And when tryin` to Mount USB Mass storage this is the output:
Code:
Error mounting /dev/sr1 at /media/hades/671D-12F5: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,shortname=mixed,utf8=1,showexec,flush" "/dev/sr1" "/media/hades/671D-12F5"' exited with non-zero exit status 32: mount: /dev/sr1 is write-protected, mounting read-only
mount: /dev/sr1: can't read superblock
I have 32gb class 10 sdcard formatted as fat32.. And from what i see it tries to mount as vfat, this for sure is from the fstab..
Any ideas?
corsicanu said:
Thanks... It`s on my todo list but i don`t have enough time to do anything now. About the adb - shouldn`t be same thing? What`s the difference between adb in linux and windows? Wait to switch linux to test. Could also be something specific to my device since you made the recovery for FU and i have F.. Will edit this post in a minute. Cheers!
Click to expand...
Click to collapse
Since it's a recovery it works with any a500xx variant (same chipset ) and also it's the same thing with roms for example on my pac-rom rom noone said it doesn't boot on a500xx. Regarding adb, bad drivers i think
I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery
Qcraft said:
I don't know how much i can thank you, when i use TWRP my phone won't boot into the system but it works perfectly with this recovery
Click to expand...
Click to collapse
So use thiz
What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far
akil777 said:
What I like in it is while I am in this recovery and my phone is charging, and I select reboot, it boot to the system unlike other recovery.
I had installled custom ROMs, Flashed kernel image, and used ADB sideload so far
Click to expand...
Click to collapse
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal
DeadSquirrel01 said:
anyway if in twrp it doesn't reboot you can run $ reboot in advanced->terminal
Click to expand...
Click to collapse
Yep.. this terminal has commands nearly or exactly like linux ubuntu.
akil777 said:
Yep.. this terminal has commands nearly or exactly like linux ubuntu.
Click to expand...
Click to collapse
Yes, the commands of any linux distro, but they are less... only indispensable commands
This version of TWRP works on both the TB-X605F (wifi) and TB-X605L (LTE). It does not work for the TB-X605FC/FL (Tab M10 FHD Rel).
Warning: this TWRP is for the Lenovo Smart Tab M10 with the Snapdragon 450 (SDA450) chipset. This image will not work for the second gen M10 (TB-X606F/L), which use a Mediatek SOC. See this thread.
For the M10 HD (TB-X505F/L), see this thread. For the TB-X505X, see this thread.
Code:
#include <std_disclaimer.h>
/*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Possible issues with TB-X605L
If the latest version of TWRP for TB-X605F doesn't work for your TB-X605L model, try version 3.4.0-0 from twrp.me.
Installation
TWRP for this device is officially supported. You can download it from twrp.me or in the TWRP App (from the PlayStore). Installation instructions are included on twrp.me.
It is recommended that you also install Magisk. This will ensure TWRP remains your default recovery.
Step-by-step guide
download TWRP to your PC (see the Download section below)
download magisk.zip to your MicroSD or OTG device. Get the latest Magisk zip file here.
if your bootloader is already unlocked, go to step 4. To unlock bootloader:
on tablet: go to Settings->System->About and press "Build number" 7 times to enable Developer Options.
on tablet: go to Settings->System->DeveloperOptions. Turn on: "OEM unlocking" and "USB debugging".
connect tablet to your computer. Tablet will ask for permission to "Allow USB debugging". Tick "always allow" and select "OK".
backup any files you want to keep to an external device (MicroSD/OTG/computer), because the next step will wipe all your photos, files, google account etc on the tablet.
Now unlock the bootloader:
Code:
adb reboot bootloader
fastboot oem unlock-go
fastboot reboot
flash the twrp image:
Code:
adb reboot bootloader
fastboot flash recovery twrp.img
if you haven't loaded Magisk yet, go to step 6. If you have already loaded Magisk, you can just reboot and you're finished:
Code:
fastboot reboot
adb reboot recovery
load Magisk (step one): reboot to recovery. Do not reboot into the system, because it will over-write TWRP with stock recovery. If that happens, go back to step 4 and start again. When you issue the reboot command (below), you have to immediately press the button combination to reboot to recovery (TWRP). Here are the steps:
issue the reboot command:
Code:
fastboot reboot
immediately press and hold all three buttons (Pwr+VolUp+VolDown). The tablet might reboot twice. Release all the buttons when you see the TWRP screen, or hear your PC acknowledge that ADB is connected.
load Magisk (step two): flash Magisk. In TWRP:
select "Install"
use "select storage" to locate device you stored magisk.zip on.
press the OK button
select the Magisk zip file
swipe to confirm Flash
when Magisk is finished, hit the back button to go back to main TWRP screen.
select "Reboot" then "System"
if the Magisk Manager app wasn't automatically loaded, you can get it here.
finished!
If you prefer to use button combos, rather than fastboot/ADB commands:
Vol Down + Power = fastboot mode
Vol Up + Vol Down + Power = recovery mode
Changelog
Code:
02/03/2022 - TWRP 3.6.1_9: new TWRP release
23/11/2021 - TWRP 3.6.0_9: new TWRP release
01/01/2021 - TWRP 3.5.0-0: new TWRP release
21/11/2020 - TWRP 3.4.0-1: new official version with SPL patch
19/11/2020 - promoted security patch level to 2099-12-31. No need to worry about SPLs ever again.
02/09/2020 - promote security patch level to 2020-08-01 for TB-X605F_S210208_200807_ROW
06/08/2020 - officially supported
31/07/2020 - upgrade to TWRP 3.4.0-0
- data decryption working (security patch 2020-04-01)
- landscape mode (by popular demand)
- add more partitions to Backup options
15/01/2020 - reverted to API 28 (Android Pie)
- renamed "sdcard1" to "external_sd"
- changed [ro.build.incremental.version] in preparation for OTA #4
24/11/2019 - fixed date/time & EDL reboot mode
- dropped back to API 27
20/11/2019 - initial commit (API 28) - encryption/decryption not working
Downloads
official
TWRP for X605F: twrp.me
Source code
github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-9.0
github.com/TeamWin/android_device_lenovo_X605F (official)
github.com/Yahoo-Mike/recovery_device_lenovo_X605F (unofficial)
FAQ
See the third post for answers to some FAQs like:
Will this TWRP work with other M10 and P10 devices?
Why is my "Data" partition empty (0 MB)?
how do I root my device?
Credits
The guys at TeamWin Recovery Project.
Everyone whose device trees I plagiarised from GitHub.
The amazing work of @Chaser42, @Long_Sam and others to get this project started.
XDA:DevDB Information
X605F Recovery, Tool/Utility for the Lenovo Thinkpad Tablet
Contributors
Yahoo Mike, Chaser42
Source Code: https://github.com/TeamWin/android_device_lenovo_X605F
Version Information
Status: Testing
Created 2019-11-19
Last Updated 2022-05-22 (v3.6.1 and warning for TB-X605L)
Encryption/Decryption
When you load the stock ROM, it creates and automatically encrypts the data partition. If you are not using the correct TWRP version, the data partition might be empty (0 MB). This is because TWRP failed to decrypt the data partition.
If your data partition is 0MB in TWRP, make sure you have loaded the latest version of TWRP (Nov 2020 or newer). Older builds required the security patch levels to match on TWRP and your system.
If you want to remove encryption completely, then you can use the dm-verity-forceencrypt tool. @turboperson123 has put together some instructions to remove encryption. If you've already loaded TWRP, then you only need to follow steps 6 and 7 from that post. @turboperson123 's method uses @Zackptg5 's Universal DM-Verity, ForceEncrypt, Disk Quota Disablers tool to remove encryption and dm-verity.
FAQs
Can I use this TWRP on other M10 and P10 tablets?
There are quite a few variants of these Tabs that use the Snapdragon 450 (SDM450) chipset:
TB-X605F (Tab M10 wifi) - tested working this TWRP
TB-X605L (Tab M10 LTE) - tested working with TWRP ( thanks @alexupsa )
TB-X705F/L (Tab P10) - no. Use the twrp available on this thread.
For the TB-X505F/L (M10 HD) see this post.
NOTE: the TB-606F/L (M10 2nd gen), TB-X605FC (M10 FHD) use different chipsets, so this TWRP won't work.
Why is my "Data" partition 0MB?
See the second post in this thread.
What should I backup?
Short answer: everything.
But the bare minimum might include:
System Image
Vendor Image
Firmware/Modem
Persist
Data
Cache
Boot
How do I root my device?
To root your device, here are the instructions for the:
X705F (thanks to @Chaser42)
X605F/L - follow steps 6 & 7 in the OP above. If you don't want to load TWRP, then try something like @Long_Sam's patched boot.img method.
X505F/L - follow the "step by step guide" in the OP above. Just make sure you use twrp for X505F (not for X605F).
How do I load OTAs with TWRP?
Note: if you ran the dm-verity-forceencrypt tool to unencrypt your /data, then the steps below will not work.
select "uninstall" in the Magisk Manager app. If MM doesn't reboot the system, then reboot - this will re-install stock recovery.
install the OTA (either in the system or using stock recovery).
re-flash TWRP (for the new security patch level)
re-install Magisk
TB-X605L working properly. Thank you!
TB-X605L working properly. Thank you!
Yahoo Mike said:
This is a work in progress. Volunteer testers are very welcome.
Click to expand...
Click to collapse
Wow...
That's really huge...
As we say here : "Monsieur, chapeau bas !"
Long_Sam
Lenovo has released quite a few variants of the Tab M10 now. I'm not sure this TWRP will work on all of them.
There are now even variants of a variant !
Code:
[B]M10[/B] with SDM-450 models: X605F (wifi) & X605L (LTE)
[B]M10 HD[/B] with SDM-429 models: X505F (wifi), X505L (LTE) & X505X (LTE Bands 1,2,3,4,5,7,8,20,38,40)
[B]M10 FHD[/B] with SDM-450 models: X605FC (wifi) & X605LC (LTE)
The M10 I have is shipped with a Snapdragon 450 (SDM-450) chipset & Hardware Code 63. But I see on their US site that Lenovo are now putting the SDM-429 in the X605. This might cause a problem with TWRP. I'm not sure if the kernels will be compatible.
The TWRP I've posted is for the X605F/L SDM450 (HW=63). I might need to compile a different TWRP for the SDM429 versions of the X605 & the X505.
If your X605 or X505 shipped with the SDM429, can you let me know if this TWRP works ? I need to know the Hardware Version, CPU and Hardware Code. Hardware Version and CPU are in System->About. The Hardware Code is in brackets after the S/N on the sticker on the back of the tablet, eg S/N Hxxxxxxx (63).
If you have an X605FC/LC, let me know if this TWRP works. I think it will, but I want make sure.
I have one with the 429 TB-X505F SD429 HW71 If i get some time today I might be bale to try it. I'll post soon as I do.
This morning I successfully compiled and ran the P10 kernel source on my M10. I had to tweak the config a bit. I tested it in TWRP. No problems.
Tomorrow, I'll inject it into the boot.img of the system ROM and see what happens. If it is mostly stable, then we're on the way to LOS for the M10. If it's completely stable, I'll push the source up to github.
I'll continue to use the stock kernel for the released versions of TWRP in this thread, though.
Thanks to @clsA for helping me work out that the M10 kernel is a subset of the P10 kernel.
@Yahoo Mike
thx for the twrp
succesfully flashed on my X605L
"Stock recovery image (recovery_stockROM.img) from TB-X605F_USR_S200065_1905280020_Q00332_ROW - just in case something goes wrong & you need to restore stock recovery. Only use this image on a TB-X605F. If you need it for any other variant, just ask in this thread and we'll track it down for you."
do you have the stock recovery for the X605L ?
how can i backup "DATA" inside twrp ?
will this help ?
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
OSIRIS2010 said:
...
do you have the stock recovery for the X605L ?
Click to expand...
Click to collapse
Now I think of it, you don't need it. If TWRP fails to flash, then stock recovery will still be there. If stock recovery is still not loading, just boot into the system and shutdown. When you shutdown, the system will re-flash stock recovery for you.
OSIRIS2010 said:
...
how can i backup "DATA" inside twrp ?
Click to expand...
Click to collapse
Have a look at the second post.
TL;DR...the dm-verity-forceencrypt tool will do it. But it will break the next OTA. The unencrypted P10 guys are having problems at the moment with this.
I've tried to get TWRP to unencrypt the data partition, but I can't get KeyMaster to initialise successfully. Maybe the next version of TWRP will be able to do it.
Yooo. Sorry I took so long works been crazy. I cant get it to reboot into twrp recovery. Its flashes the 605 recovery then I follow the next steps in the guide but I can only get it to reboot to the stock recovery screen. Run the reboot recovery command then immediately hold the volume + - down along with power. I tried a lot I let reboot twice then let off, and nothing then I tried several more times. Reflashing then the next step. I must not be holding my mouth...err I mean pushing the buttons right or the recovery just isn't gonna work. Add I'm very newbie at rooting and customizing. I've I've rooted one phone. A 70$ moto g5 plus I got off Ebay that was basically brand new. Installed twrp recovery and magisk. I bought that cause I have SD note 9 I cant root and have this need to play YouTube videos in my truck lol. Let me know if you have any suggestions I can try. Or ideas that might make it work. I pretty much fubard the tab and (at a different time) before I tried this recovery and was able to reflash stock img though odin.
11mackey11 said:
Yooo. Sorry I took so long works been crazy. I cant get it to reboot into twrp recovery. Its flashes the 605 recovery then I follow the next steps in the guide but I can only get it to reboot to the stock recovery screen. Run the reboot recovery command then immediately hold the volume + - down along with power. I tried a lot I let reboot twice then let off, and nothing then I tried several more times. Reflashing then the next step. I must not be holding my mouth...err I mean pushing the buttons right or the recovery just isn't gonna work. Add I'm very newbie at rooting and customizing. ...
Click to expand...
Click to collapse
Don't be too hard on yourself...you've done well to get this far.
I just had a quick look at the kernel for the X505F. It's very different from the X605F. So this TWRP definitely won't work for you. Sorry.
If you want me to build a TWRP for the X505F, PM me and we'll work something out.
How do you remove twrp I think that or magisk is giving me the booting issues. Half the time I reboot for things it gets stuck. Not sure if it's root or twrp but I can't seem to remove either.
cbomb1337 said:
How do you remove twrp I think that or magisk is giving me the booting issues. Half the time I reboot for things it gets stuck. Not sure if it's root or twrp but I can't seem to remove either.
Click to expand...
Click to collapse
If you uninstall Magisk, then the system will overwrite TWRP with stock recovery the next time you reboot. Just tap "uninstall" in the Magisk Manager app. You can also remove Magisk from TWRP following these instructions.
What kind of boot issues are you having? Are you using a TB-X605F with SDA450? Or is it something similar?
I am using Tb 605f it seems to be booting fine now after removing this riru module and edxposed. I'll just leave that and stick with just viper 4 Android lol
Do you know if them modules for increasing speed work? I think one of them was called fde and there the doze one.
cbomb1337 said:
I am using Tb 605f it seems to be booting fine now after removing this riru module and edxposed. I'll just leave that and stick with just viper 4 Android lol
Do you know if them modules for increasing speed work? I think one of them was called fde and there the doze one.
Click to expand...
Click to collapse
Good to hear it's all working again.
Sorry, I haven't tried any of those tweaks.
Lenovo have updated the stock ROM they serve for the TB-X605F through LMSA rescue. It's now at TB-X605F_USR_S210126_1910290024_Q00332_ROW. This is the latest update. There are no OTAs to apply. The M10 is due for a security OTA pretty soon, though. The P10 has already received it.
Unfortunately, it's no longer possible to post a direct link to Lenovo's website for this ROM. You'll have to use LMSA to get it.
FYI. Lenovo have changed how they serve the stock ROM. The ROM is now kept at rsdsecure-cloud.motorola.com. LMSA seems to generate (or request and receive) a one-off time-limited credentialed ticket for the download. You can't download the zip files without the credentials attached to the URL.
If you really want to, you can still intercept the URL in download_resources.json in the LMSA download folder.
is there anything new in the update. i might hold of because i dont want to lose root.
cbomb1337 said:
is there anything new in the update. i might hold of because i dont want to lose root.
Click to expand...
Click to collapse
No, there's nothing new. This isn't really an update, it just seems to be a consolidation of the old stock ROM and incremental OTAs.
This is only for M10 wifi (TB-X605F) with SDA450.
The latest OTA for TB-X605F has just landed. It's available on your tablet, or directly from: TB-X605F_USR_S210126_191029_Q00332_ROW_TO_TB-X605F_USR_S210152_200120_Q00332_ROW_WCE26E2CD5.zip.
The update takes the M10 to:
Code:
build: TB-X605F_USR_S210152_200120_ROW
security patch: 1 January 2020
kernel: 3.18.120-perf-gd60e12b6-dirty
If you have TWRP and root, you'll need to:
select "uninstall" in the Magisk Manager app
install the OTA (from SD card) in recovery and reboot
re-flash TWRP
re-install Magisk
only if you unencrypted the data partition
If you have unencrypted your data partition, it will be re-encrypted during this process. Make sure you back it up before you start the OTA. You might also need to restore the TWRP backup you made of the vendor partition, before the OTA will run. Once the OTA, TWRP and Magisk are installed, you can re-run the dm-verity tool.
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.
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!