Database Develop

[RECOVERY][OFFICIAL] TWRP 3.1.1 for Exynos

Disclaimer: Usual disclaimer applies. I've tested this recovery but it might not work due to a different ROM / device / moon phase / etc. Use at your own risk.
Introduction
After working with upstream TWRP developers and fixing some bugs (in TWRP itself and in this port) this device finally has an official port
There were various builds available at different times (some with bugs) but most of them should now be fixed.
Features
Works
backup/restore
installing zips
ADB
MTP
Screen turns off
Basically the rest of this list
format /data
Adoptable storage
Decrypt /data
Doesn't work (please ask if you need this)
Encrypted backup (set password for /data/data)
USB-OTG
Untested
Backup/restore of stock system / data.
Installation instructions
Warning: only use it on the G800F/M/Y, NOT on the G800H! I only tested the G800F, but think G800M/Y will also work. G800H will most likely NOT work, as it is based on a different SoC (Qualcomm).
Download the recovery image from twrp.me. It also includes some installation instructions.
There are more extensive installation instructions over at the LineageOS ROM installation instructions.
I personally prefer using Heimdall, but you can also use Odin. Commands in Download/Odin mode (power off, then press home+Volume-Down+power):
Code:
heimdall flash --RECOVERY recovery.img
If you're using the stock ROM, use:
Code:
heimdall flash --RECOVERY recovery.img --no-reboot
When you come from the stock ROM you have to make sure the stock ROM doesn't overwrite TWRP: Pull the battery, wait 5 seconds, insert it again, and press home + volume up + power to enter TWRP and replace the stock ROM from there.
If you already have TWRP or LineageOS, it's much easier to install from there, see twrp.me.
Another method is using ADB (from your computer). I used it a lot during testing:
Code:
adb root
adb push twrp-3.1.1-1-kminilte.img /dev/block/mmcblk0p10
Changelog
Code:
2017-07-10:
* fix formatting /data while the partition is encrypted
(device is not encrypted by default)
* add support for adoptable storage
* accept kminiltexx etc. for flashing basebands
2017-06-20:
* ADB
* MTP at the same time as ADB
* Screen turns fully off
* fix for restoring backups made using `adb backup --twrp`
Source code
Kernel: https://github.com/TeamWin/android_kernel_samsung_kminilte/tree/cm-14.1
Device: https://github.com/TeamWin/android_device_samsung_kminilte/tree/cm-14.1
This recovery is built using a LineageOS tree. Instructions are similar to the instructions for building LineageOS for the S5 mini. Differences are: you don't need to patch the source (skip that step) and the last step is mka recoveryimage instead of mka bacon - this only builds the recovery resulting in much faster builds. Also see the official build instructions.
Thanks
Other people who have worked on this project:
Team Win, of course, for the recovery itself! In particular bigbiff which has worked with me to make this device official.
hennymcc
RVR
---
Note to moderators: this is my first DevDB thread started on XDA so I may have made mistakes.
XDA:DevDB Information
Team Win Recovery Project, ROM for the Samsung Galaxy S5 Mini
Contributors
ayke, hennymcc, RVR
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: 3.1.1
Stable Release Date: 2017-06-20
Created 2017-06-24
Last Updated 2017-07-09

Thanks!

OFFICIAL TWRP...I can't believe it
Great work on this one...many thanks.

Thanks a million @ayke ! However, I found some bugs I'd like to submit some bugs I discovered:
- Recovery is not SEANDROID enforcing" message when booting TWRP, didn't cause any trouble for me but still - it was fine in your previous unofficial build
- Some zip files (tested with latest modem flashable zip) report "This package is for kminiltexx devices; this is a kminilte", so it doesn't flash and fails with ERROR:7
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
P.S. Is it possible to add support for adopted storage, that would be awesome!
Nevertheless - thanks for making this device officialy supported!

Friedensfurz said:
Thanks a million @ayke ! However, I found some bugs I'd like to submit some bugs I discovered:
- Recovery is not SEANDROID enforcing" message when booting TWRP, didn't cause any trouble for me but still - it was fine in your previous unofficial build
Click to expand...
Click to collapse
The current kernel used upstream is somewhat older and hasn't enabled SELinux yet. I don't see why you would want enforcing SELinux in TWRP, though.
Friedensfurz said:
- Some zip files (tested with latest modem flashable zip) report "This package is for kminiltexx devices; this is a kminilte", so it doesn't flash and fails with ERROR:7
Click to expand...
Click to collapse
I think I have a fix for that, please test https://aykevl.nl/download/2017-06-25-recovery-fix-ota-asserts.img (not tested by me)
Friedensfurz said:
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
Click to expand...
Click to collapse
Nice!
Friedensfurz said:
P.S. Is it possible to add support for adopted storage, that would be awesome!
Click to expand...
Click to collapse
I might look into it. I don't use it at the moment but am considering it.
EDIT: I have fixed it, it will be included in the next build.

any chance for g800h support?

sasukesama said:
any chance for g800h support?
Click to expand...
Click to collapse
Not from me. The G800H is a completely different device. I have a G800F so I can't test it.

ayke said:
I think I have a fix for that, please test https://aykevl.nl/download/2017-06-25-recovery-fix-ota-asserts.img (not tested by me)
Click to expand...
Click to collapse
Sorry, but the build doesn't fix the wrong device id issue - still throws error " This is for kminiltexx your device is kminilte. Anyway - maybe the next build will fix it[emoji6]

Friedensfurz said:
Sorry, but the build doesn't fix the wrong device id issue - still throws error " This is for kminiltexx your device is kminilte. Anyway - maybe the next build will fix it[emoji6]
Click to expand...
Click to collapse
Can you give a link to where you downloaded this zip? Then I can test it myself.

I also get the device error with latest official and 2017-06-25-recovery-fix-ota-asserts.img.
Tried to flash one of Spookcity's kernels, you can find it here (search for "test9" that is what I used lately).
https://github.com/Spookcity/ROMS-G800F/issues/10#issuecomment-301915315
The latest pre-official TWRP 3.1.1-0 works (says kminiltexx).

ayke said:
Can you give a link to where you downloaded this zip? Then I can test it myself.
Click to expand...
Click to collapse
This file causes problems with the device id: http://pt.tapatalk.com/redirect.php...1_22.05.2017_DRE-flashable.zip&au_id=13587482
It is a TWRP flashable baseband file, hope this helps

@Friedensfurz @Pat750
I couldn't find a (still online) kernel from Spookcity and I'd rather not flash a new modem unless I know why I should do that. So I haven't verified it.
But here's another build you can try. My previous attempt was incomplete.
https://aykevl.nl/download/2017-06-27-recovery-fix-ota-asserts-2.img
On my device I've verified it has a ro.product.device property of kminiltexx.

ayke said:
@Friedensfurz @Pat750
I couldn't find a (still online) kernel from Spookcity and I'd rather not flash a new modem unless I know why I should do that. So I haven't verified it.
But here's another build you can try. My previous attempt was incomplete.
https://aykevl.nl/download/2017-06-27-recovery-fix-ota-asserts-2.img
On my device I've verified it has a ro.product.device property of kminiltexx.
Click to expand...
Click to collapse
Yeah,I removed all of my test build links from my google drive, but have a thread on here. I already sent you this though. I will test your new build and see if it helps.
Edit:
Yep,fixed. Good work Ayke!
Sent from my SM-G800F using Tapatalk

Friedensfurz said:
...
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
...
Click to expand...
Click to collapse
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!

fidoedidoe said:
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
Click to expand...
Click to collapse
I have the same problem

Here also this message in unofficial builds, don't tried it, but I think its still present in this version.

fidoedidoe said:
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
Click to expand...
Click to collapse
I still haven't found a method to decrypt the /data volume from within TWRP (a reference earlier in the thread implied it was possible)..the hope being this would mitigate the "wipe / format data" error:
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
What I did discover was that when reverting to an older version of TWRP (2.8.x) using Odin, " format data" (where you have to type "yes" to proceed) didn't error. I'm not sure whether that cured the issue, but after that I updated TWRP image back to 3.1.1.0 and installed my ROM as normal.
Still looking for a recognised method to wipe encrypted /data volume from within latest stable TWRP if anyone has any experience of that.
EDIT
Another thread suggests (to my untrained eye) that "unknown file system 'auto" may be related to how twrp.fstab is configured.
I'm very much out of my here ( so apologies for the crude suggestion), but could it be that another build of a TWRP image is needed where twrp.fstab is changed to allow "format data" to work, ie substitute "fstype" from "auto" to "ext4" as outlined below :
Code:
...
/data ext4 /dev/block/mmcblk0p21 length=-16384
...

fidoedidoe said:
I still haven't found a method to decrypt the /data volume from within TWRP (a reference earlier in the thread implied it was possible)..the hope being this would mitigate the "wipe / format data" error:
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
What I did discover was that when reverting to an older version of TWRP (2.8.x) using Odin, " format data" (where you have to type "yes" to proceed) didn't error. I'm not sure whether that cured the issue, but after that I updated TWRP image back to 3.1.1.0 and installed my ROM as normal.
Still looking for a recognised method to wipe encrypted /data volume from within latest stable TWRP if anyone has any experience of that.
EDIT
Another thread suggests (to my untrained eye) that "unknown file system 'auto" may be related to how twrp.fstab is configured.
I'm very much out of my here ( so apologies for the crude suggestion), but could it be that another build of a TWRP image is needed where twrp.fstab is changed to allow "format data" to work, ie substitute "fstype" from "auto" to "ext4" as outlined below :
Code:
...
/dataext4/dev/block/mmcblk0p21length=-16384
...
Click to expand...
Click to collapse
I got it to work by formatting/repairing/changing filesystem in TWRP. Just try some combinations, it will work eventually

Yes, I think it's because of the 'auto' in the fstab. I've set it to ext4 in this build (for data and cache):
https://aykevl.nl/download/2017-07-03-recovery.img
This build also contains the previous fixes (adoptable storage, fixing the kminiltexx error).
If it fixes the issue for you, I'll push the change for inclusion in the next official build.
I didn't see any negative consequences of changing the FS type in fstab. Even setting the fstab entry to 'f2fs' mounts /data as usual (as ext4) so I think it's safe.

ayke said:
https://aykevl.nl/download/2017-07-03-recovery.img
Click to expand...
Click to collapse
Can someone test this change? Then I'll integrate it in the official build.

Unofficial TWRP for sagit [F2FS+EXT4][Unofficial]

Unofficial TWRP and OrangeFox builds.
TWRP : https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/
OrangeFox - deprecated : https://sourceforge.net/projects/ep...overy/OrangeFox-Unofficial-sagit.img/download
This is TWRP-3.3.1 unofficially updated with lots of new improvements!
What's here but not in the official one?
Compiled with Pie blobs and in pie environment
Updated kernel, based on CAF's latest pie tag and compiled with latest Clang 9.0.3 by Google
Additional debug support - This TWRP won't overwrite /sys/fs/pstore
F2FS support
Cleaned unused HALs from manifests
System as Root variant available
How to install this TWRP?
Boot into fastboot mode by pressing volume down + power when the device is turned off
Connect your device to your computer
Download the TWRP build
Open a shell at the download folder
Rename the downloaded file to twrp.img
Type
Code:
fastboot flash recovery twrp.img
To leave the fastboot mode type
Code:
fastboot reboot
What is F2FS?
F2FS (Flash-Friendly File System) is a flash file system initially developed by Samsung Electronics for the Linux kernel.
The motive for F2FS was to build a file system that, from the start, takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers
Click to expand...
Click to collapse
- Wikipedia
How to use F2FS for /data and /cache?
Reboot into this TWRP
Select wipe > format data then type yes and reboot into recovery again
Then select wipe > advanced wipe select cache then select repair or change file system and select F2FS
Do the same step with Data
Install a supported ROM and GApps
Reboot into the ROM

Thank you for your great work . keep it up

Thanks,I'm following the topic

Sorry for my ignorance....but can somebody tell me the difference between these two?

Shiw Liang said:
Sorry for my ignorance....but can somebody tell me the difference between these two?
Click to expand...
Click to collapse
Between orange fox and twrp? Orange fox is a fork of twrp with some special features and a redesign.

Shiw Liang said:
Sorry for my ignorance....but can somebody tell me the difference between these two?
Click to expand...
Click to collapse
Have a look here - https://orangefox.tech/

DarthJabba9 said:
Have a look here - https://orangefox.tech/
Click to expand...
Click to collapse
happy to see you here, Will sagit devices have an official version? We are looking forward

fr0bs said:
happy to see you here, Will sagit devices have an official version? We are looking forward
Click to expand...
Click to collapse
In due course

New TWRP test build is available!
TWRP was updated to version 3.3.0 and is usable with f2fs.
Download : https://drive.google.com/file/d/1UwT5UBz_8PVugEhWLYlcwKM3VAi25jkI/view
This build is possible due to Ultraschorsch 's support by providing a Google Cloud trial ?

Good evening!
A new build of TWRP is published here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.0

Decryption problem
NeoArian said:
Good evening!
A new build of TWRP is published here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.0
Click to expand...
Click to collapse
I have tryed your latest update with AEX 6.5 and I can't decrypt data. What am I wrong?

perspicio said:
I have tryed your latest update with AEX 6.5 and I can't decrypt data. What am I wrong?
Click to expand...
Click to collapse
There is a problem with decrypting devices formatted with may ASB, I see about it. You could go f2fs or setup rom on April build and upgrade to new one for now.
Edit:// should be fixed here: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.1

I am currently on LineageOS 15 (8.1), and using TWRP 3.2.3. Everything works OK.
But if I try to boot into latest 3.3.1 (both with SAR and without) it doesn't request pattern for decrypting data, and I can't figure out how to force it to.
Without decrypt it shows /sdcard and /data/data as garbage...

Hi @NeoArian, it seems that at least your latest TWRP-sar version has issues with mounting external usb storages: at least my sandisk 64GB key that I always used to save nandroids to is not detected, thus I have to rely on internal memory to save nandroids, fw, and user data.
Using TWRP version 3.2.3-sagit-shev.img I have no issues (but unfortunately no support for your lineageos unofficial builds if I'm not mistaken).
Am I doing something wrong? Do you have any suggestions?

Cavaler said:
I am currently on LineageOS 15 (8.1), and using TWRP 3.2.3. Everything works OK.
But if I try to boot into latest 3.3.1 (both with SAR and without) it doesn't request pattern for decrypting data, and I can't figure out how to force it to.
Without decrypt it shows /sdcard and /data/data as garbage...
Click to expand...
Click to collapse
I thought it was some codes in twrp that cause the problem.
If I use 3.3.1.0 everything works fine. but it won't decrypt my data even I had no pattern for lock screen with 3.3.1.2.
( all mentioned above are official builds )

This version TWRP have arch bug.
This version TWRP can not install the right latest OpenGapps. It will back error 64 and ask user install arm version gapps not the arm64 version.
The details can visit here https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070
Can you fix it in your version?
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-463335444

New twrp update available: https://github.com/xiaomi-msm8998/twrp_device_xiaomi_sagit/releases/tag/3.3.1-20191204
AmaoBilibili said:
This version TWRP can not install the right latest OpenGapps. It will back error 64 and ask user install arm version gapps not the arm64 version.
The details can visit here https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070
Can you fix it in your version?
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1070#issuecomment-463335444
Click to expand...
Click to collapse
I assume that's a problem with OpenGapps installer.

Hi, I'm running twrp 3.3.1-20191204 with your Lineage 17 very happily thanks!
For the last couple of lineage installs though (2019-12-24 and 2020-01-08) I'm getting a failure in twrp when running a backup, on data partition specifically:
createTarFork() process ended with ERROR: 255
recovery.log is far more helpful:
Code:
# tail -n 50 /tmp/recovery.log
I:addFile '/data/anr/anr_2020-01-10-11-49-31-592' including root: 1
==> set selinux context: u:object_r:anr_data_file:s0
I:addFile '/data/per_boot' including root: 1
==> set selinux context: u:object_r:system_data_file:s0
failed to lookup tar policy for '/data/per_boot' - '0eb5afb598811574'
I:Error adding file '/data/per_boot' to '/data/media/0/TWRP/BACKUPS/161a6490/2020-01-10--16-29-03_lineage_sagit-userdebug_10_QQ1B200105004_en/data.ext4.win008'
Error creating backup.
I:ERROR tarList for thread ID 0
Error creating backup.
There's an (empty) folder '/data/per_boot' which seems to be breaking the backup process. I'm not sure if it's lineage itself or one of my apps creating this dir, but if I manually delete it the backup works... then it gets recreated next boot.
A somewhat minor issue, in case it's either easy enough to fix and/or other's run into the same problem!

I assume this twrp version use for flashing gsi. Am I correct?

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

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

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

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

Nice work!!!

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

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

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

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

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

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

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

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

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

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

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

How can i make the twrp permanent ?

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

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

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

ask Decrypt password everytime I reboot to twrp.
Help!

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

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

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

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

Reserved

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

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

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

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

USE TWRP 3.6 from
[RECOVERY][UNOFFICIAL]TWRP 3.6.0 for 2020 Galaxy Tab A7 10.4[SM-T500]
/* * Disclaimer * * Your warranty is now void. * * We're not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features...
forum.xda-developers.com
You need a recent version of fastboot too. Get one

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

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

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

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

Would porting ubports be possible for this device?

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

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

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

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

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

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

System encrypted, /dev/block is read-only

Hi, I have a redmi note 9 that I wanted to mod but I had a lot of problems modding it. I initially installed crDroid 8.7 but the control center animation was lagging and the battery drains fast, so I decided to change the ROM with Project Elixir (Android 12 all ROMs). I saw that crDroid 8.9 came out (September 22, 2022) and there had been some notable changes, as the battery did not run out anymore the animations were fluid, but i was not able to get working google apps.
I tried everything and it wasn't right. (Nik, OpenGapps, MTG nothing) indeed I installed the gapps I had on 8.7 and them didn't work .. So I decided to move to pixel experience android 12 but I had these problems:
On all the roms that I have installed (except I think MIUI) the system is encrypted. I tried flashing a zip, via commands, via recovery but nothing the system is encrypted. I can't access it and in addition I wanted to change the bootanimation but I can't move the zip because it says it's read only and following these commands too I couldn't do it:
adb root
adb disable-verity
adb reboot
adb remount
adb shell
mount -o rw,remount /system
for these commands i also used ADB Sideload (ofc) but also some zips
It says the /dev /<number>/block is read-only and I have not been able to unlock it. (I tried with all these recoveries: TWRP, SHRP (SkyHawk, OrangeFox [UNOFFICIAL but is only for A11]). (If I go from TWRP to sdcard / I have all the files encrypted. I have the phone rooted with magisk.
In addition, I also had problems formatting the phone because the system with both TWRP and SHRP was not deleted or if I restarted the phone after formatting the ROM would open again so to format it I used Pixel Experience which has worked very well so far.

But custom rom already have ability to rw
Anyway you're lucky there thread available google it like
Universal method to get rw

Idk. I have installed Project Elixir, crDroid and this Pixel Experience and are encrypted.
I already googled it....

/dev/* will be always read-only.

And how i can modify the boot animation? Files are encrypted and the zip is in /system/product/media/.zip

/dev/ and /system/ are not same.
Stock MIUI is system read-only.
If you want to mount system as read-write, you need "universal mount system r/w" by @lebigmac
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com

Oh ok, it will work on A12?

I'm not sure.

Ok so tried flashing systemrw_flashable (Universal RW) with sideload bcs i have crypted files.
This is the error that it gave me:
Extracting ...
There was an error extracting the file. Please install unzip and try again.
I tried flashing with SHRP (TWRP based) bcs twrp can't work with adb sideload (for me).
Edit: searched on xda the problem, i installed the BusyBox module in magisk (From Fox Modules Manager) but nothing to do, still same error.

Deltwin said:
Oh ok, it will work on A12?
Click to expand...
Click to collapse
it should start up if you comment out the checkSDK() function in the script itself.
Not sure if you can sideload it probably not. Just execute it like any other script (runnable in both Android and recovery) or flash it like any other flashable zip in recovery.
Keep in mind I'm working on a new version that should fix some issues. Just need to make sure it works perfect on multiple devices b4 I release it...
If you can't get my script to work and you're too impatient to wait for the new version to be released then you could try some of the copycat imitations. There's a couple of those floating around here... Good luck!

lebigmac said:
it should start up if you comment out the checkSDK() function in the script itself.
Not sure if you can sideload it probably not. Just execute it like any other script (runnable in both Android and recovery) or flash it like any other flashable zip in recovery.
Keep in mind I'm working on a new version that should fix some issues. Just need to make sure it works perfect on multiple devices b4 I release it...
If you can't get my script to work and you're too impatient to wait for the new version to be released then you could try some of the copycat imitations. There's a couple of those floating around here... Good luck!
Click to expand...
Click to collapse
But how can be you make sure without some beta testers you neef guys like me and this op who have device in hand to test it and give you feedback

lebigmac said:
it should start up if you comment out the checkSDK() function in the script itself.
Not sure if you can sideload it probably not. Just execute it like any other script (runnable in both Android and recovery) or flash it like any other flashable zip in recovery.
Keep in mind I'm working on a new version that should fix some issues. Just need to make sure it works perfect on multiple devices b4 I release it...
If you can't get my script to work and you're too impatient to wait for the new version to be released then you could try some of the copycat imitations. There's a couple of those floating around here... Good luck!
Click to expand...
Click to collapse
Oh so it cant work in sideload... Good tip if it will work u made a very good script

To be honest I've never used this sideload feature before... What are the advantages of sideloading versus flashing the .zip as usual?
Mr Hassan said:
But how can be you make sure without some beta testers you neef guys like me and this op who have device in hand to test it and give you feedback
Click to expand...
Click to collapse
That's a good idea. I should release an open beta before releasing the final program.
That way we can make sure it works on as many devices as possible

lebigmac said:
To be honest I've never used this sideload feature before... What are the advantages of sideloading versus flashing the .zip as usual?
That's a good idea. I should release an open beta before releasing the final program.
That way we can make sure it works on as many devices as possible
Click to expand...
Click to collapse
Thanks for appreciating the idea
Hope we'll get beta soon but is there any idea date how many days still need to release it
Ok let me show my progress
I make my vendor sys odm to ext4
And ser the logs according to logs
I have rw now
OnePlus8:/ # mount | grep "dm-0"
/dev/block/dm-0 on / type ext4 (rw,seclabel,relatime)
OnePlus8:/ # mount | grep "dm-19"
/dev/block/dm-19 on / type ext4 (rw,seclabel,relatime)
OnePlus8:/ # mount | grep "dm-3"
But the weird thing is still not able to edit
Any file in these parts.

lebigmac said:
it should start up if you comment out the checkSDK() function in the script itself.
Not sure if you can sideload it probably not. Just execute it like any other script (runnable in both Android and recovery) or flash it like any other flashable zip in recovery.
Keep in mind I'm working on a new version that should fix some issues. Just need to make sure it works perfect on multiple devices b4 I release it...
If you can't get my script to work and you're too impatient to wait for the new version to be released then you could try some of the copycat imitations. There's a couple of those floating around here... Good luck!
Click to expand...
Click to collapse
How i can run ur script directly from android?
Like on magisk?

Deltwin said:
How i can run ur script directly from android?
Like on magisk?
Click to expand...
Click to collapse
Hi. Please check the Manual Installation and Examples section of the thread in my signature
And if you're running Android 12+ don't forget to disable the sdkCheck() function in the systemrw.sh script file @ line # 425 like this #sdkCheck
It should work if your only problem is the shared_blocks read-only feature. If your device got the new erofs read-only protection feature then you must wait for next version of my script or try your luck one of the copycat imitations that are floating around.
Good luck!

So after an hard brick at work (so i leaved it for 5 hours with redmi logo on lol) and after many steps i reinstalled MIUI with root... it's running A11 so how i can install it? I need to disable the sdkCheck? I think no if you need it on A12...
Second question i need to flash it before the first boot or i can do it after the first boot?

Deltwin said:
So after an hard brick at work (so i leaved it for 5 hours with redmi logo on lol) and after many steps i reinstalled MIUI with root... it's running A11 so how i can install it? I need to disable the sdkCheck? I think no if you need it on A12...
Second question i need to flash it before the first boot or i can do it after the first boot?
Click to expand...
Click to collapse
I thought hard bricks were unrecoverable?
If your Xiaomi device is running Android 10 or 11 then you don't need to disable the sdkCheck() function in my old script.
Ok here are all the necessary steps in chronological order for you
unlock bootloader
flash stock ROM
install systemrw_1.32
root
debloat
customize
enjoy

No it's possible, i tought not but here i am with my redmi note 9..
jk apart i unbrick with SP Flash tool but i had other problems like NVRAM warning (it fixed automatically with updates idk lol..) and the IMEI was deleted but fortunately i had a flashable backup..
I need to flash the stock rom? I have pixel experience with A12/13
Edit: I tried to flash it (i have the file on the microSD) but it gave me this error:
There was an error extracting the file. Please install unzip and try again.

Well my script was designed for stock A10, A11 ROMs ( or A12 if you're lucky and your device only uses the infamous shared_blocks read-only feature + you must disable sdkCheck() function in script itself ) but I don't see why it shouldn't work on a custom ROM as well
Ok let me try this again but only because it's you
Boot phone into Android OS and make sure it's properly rooted
download the systemrw_1.32_BUNDLE_proper.zip and extract it
extract the systemrw_1.32_flashable.zip
copy the systemrw_1.32 folder into /data/local/tmp/ on your phone
open adb shell or terminal app and type
Bash:
adb shell
su
cd /data/local/tmp/systemrw_1.32
chmod +x ./systemrw.sh
./systemrw.sh in=`realpath /dev/block/by-name/super` size=50
Good luck!