What version ROM? 'm on T500XXU3AUC6 and I can force allow apps option from within Dev option but it still won't allow me to move any apps across via Storage or Apps menu.I found that you can move apps to SD card on the updated stock rom by turning on a setting in developer options called force allow apps on SD or something along those lines. It does not let you moves system or stock apps but you can move the apps you install from the playstore. The my files storage explorer won't show the change in storage. To see your actual storage visit your installed apps on the play store. This will show your true free space. To move apps after turning the setting on... go to settings...apps.... select an app you want to move... choose storage. If it can be moved to SD you will have a button that says change. When you click that it gives option internal or sd... choose SD m and it will pop up a button that says move... click move and wait till it has moved.... rinse repeat with other apps will give you more room.
Note. If you move widgets to SD they will no longer load until you put them back to internal.
If there is no OEM option in Dev it is because you don't have a Google Account registered so there is no need to enable OEM. Remember, unlocking the bootloader and enabling OEM are two entirely different things. One has NOTHING to do with the other. The bootloader has to be unlocked to flash anything other than a stock ROM. OEM needs to be enabled to prevent the FRP lock from engaging when performing a factory reset. But ONLY if there is a Google Account present on the device.I messed something up. Odin failed to flash vbmeta_disabled_R, and after some time of trying various things, I decided to re-lock bootloader from Download mode, in hopes that unlocking it again would maybe make flashing work. But now there is no OEM Unlock option in developer options, fastboot can't unlock it either.
Am I in "unlock jail"? Or did I permanently mess up my tablet?
I must say that I am quite disappointed with quality of instruction in OP / this thread.
Would it be possible to get a more detailed guide, with steps explained more accurately?
I would gladly contribute to the creation of such guide.
Would it make sense to make a GitLab/GitHub repository at this point?
So that we can have a guide in nice README.md, that people can contribute to as they wish? And also so that we have a nice issue tracker?
This thread is not exactly the best example of organised information.
edit: somehow managed to trick the developer options to display the OEM Unlocking toggle again. followed some guide that instructed me to disable automatic time & timezone, disable auto system update in developer options, disable auto update download in Software Update and to tap on Manual Download in software update. Did not seem to work at first, but it did work for some reason after I connected to WiFi.
It still did not unlock the bootloader after restart, but the option to unlock did appear in download mode.
So now bootloader is unlocked again and I am back to getting Odin to successfuly flash vbmeta_disabled_R.
edit 2: bloody hell
I got it to work, LineageOS is installed. But there were so many pit-falls and obstacles on the way that at some point I considered giving up.
But at least I learned a lot about how Samsung is brutally locking down their tech.
I am not sure if any of these issues were reported already, but here are the ones that I see on my tablet now:
- WiFi not working
- Gyroscope not working (screen not rotating when auto-rotate is enabled)
- when connected through USB cable, the MTP file transfer does not work (File browser does detect the device, but fails to display the content)
As I said, I am willing to contribute my newly gained knowledge towards something that will make installation easier.
Feel free to tell me how I could do that.
I not sure what you're talking about but OEM unlocking is directly tied to bootloader unlocking (just 2 different names for it). FRP and Google accounts have nothing to do with any of this. Please think twice before spreading misinformation.If there is no OEM option in Dev it is because you don't have a Google Account registered so there is no need to enable OEM. Remember, unlocking the bootloader and enabling OEM are two entirely different things. One has NOTHING to do with the other. The bootloader has to be unlocked to flash anything other than a stock ROM. OEM needs to be enabled to prevent the FRP lock from engaging when performing a factory reset. But ONLY if there is a Google Account present on the device.
Also, Samsung tablet don't use fastboot. That is what Odin is for.
OEM has been around for years with the FRP lock. It is only in the last couple of years that Samsung has started locking the bootloader on tablets that weren't tied to a carrier. If you remove all of the Google Accounts prior to a factory reset and don't add when you reboot, OEM will be either grey out but enable, or not appear at all. What IS necessary is to have Dev mode enabled. I have been doing this since Android 2 with at least a dozen tablets, so don't try teaching grandpa to suck eggs.Im
I not sure what you're talking about but OEM unlocking is directly tied to bootloader unlocking (just 2 different names for it). FRP and Google accounts have nothing to do with any of this. Please think twice before spreading misinformation.
IIRC I had to connect to wifi before the OEM Unlocking setting appeared in developer settings. Probably so Samsung can make sure the device isn't blacklisted somehow or supposed to be linked to Knox Mobile Enrollment.
OEM has been around for years with the FRP lock. It is only in the last couple of years that Samsung has started locking the bootloader on tablets that weren't tied to a carrier. If you remove all of the Google Accounts prior to a factory reset and don't add when you reboot, OEM will be either grey out but enable, or not appear at all. What IS necessary is to have Dev mode enabled. I have been doing this since Android 2 with at least a dozen tablets, so don't try teaching grandpa to suck eggs.
edit: Also there are custom ROMs which don't have an OEM option. You can factory reset them without the FRP lock engaging.
Once you root the tablet you can use app2sds to move the biggest app on the sd, i don't recomend using adoptable storage because is buggy and add more problems than the ones ytou want to fix it. I also recomend to get a high quality sd since cheap one won't make the apps runs fineBeen following thread, seems to be some inconveniences in disk partitions to small. Would disk size issue go away if bought the larger 64GB size? Also seems part of install appears to be creation or resizing partitions, would the extra disk space (64gb) get added to main partition or would have to manually resize partitons assuming all of this thread is done for the 32GB size?
You have to go to /Settings/Display and enable rotation.
Great news!! But I think you need to post it in the ROMs, Kernels, Recover thread.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.
- 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
I made a new build yesterday however I can't test it yet since my device is not back to me yet. If you want a copy to try dm me and I will share it. But be warned, I don't even know if it boots (though you could always reflash the old one if that's the case). The goal of the new build was to fix the SD card bug and make the touchscreen work.
Thanks for the reply. The sources can be found on the Github repo I made, which is here: https://github.com/agreenbhm/android_device_samsung_gta4lwifi.Just tested your Beta2 of twrp (something that I usually don't do) and touch is working. MTP is not working; as I have a "working" (no decryption) twrp from quite some time if you share your source I may can help you (if you're interested).
I have no intention on sharing builds or getting too much involved here on xda.. I own this device from a week before lockdown ended, I've managed to make a "working"ish twrp-3.5.1 and lineage-17.1 recovery (with fastbootd). Then I've started again to work so I've dropped the project to port LineageOS.. but if you're willing to share your source I may can help iron some bugs when I have time.
Didn't test your Lineage build (maybe I will), I still have to update to official 11 firmware.