Development TWRP for Samsung Galaxy A7 Lite SM-T220 SM-T225 SM-T227

[Skorpion96]

Same here, no touch coming from USA t220 . Using a Dongle and mouse.

Yes that happens because Samsung didn't include touch drivers, so it's a matter of be lucky. If we can boot A13 kernel twrp will be released hopefully with touch support

 

[seanboy2016]

is not bricked

It's a soft brick no?? Regardless I can't flash anything with Odin. Now. It just all fails.. I did use a recovery file I found here to try and solve the problem with no avail . All that did was change when the bootloop starts

 

[abc1054]

Yes that happens because Samsung didn't include touch drivers, so it's a matter of be lucky. If we can boot A13 kernel twrp will be released hopefully with touch support

Can i use A12 t220XXS1BVJ2 for twrp?

 

[ozmage]

Can i use A12 t220XXS1BVJ2 for twrp?

no

 

[abc1054]

no

Thanks. How about a13?

 

[ozmage]

Thanks. How about a13?

Only android 11

 

[Skorpion96]

Can i use A12 t220XXS1BVJ2 for twrp?

If someone will be successful on building and running custom kernel then we can build twrp for A12 or A13

 

[ozmage]

If someone will be successful on building and running custom kernel then we can build twrp for A12 or A13

twrp can be compiled adding dtbo and boot from stock pre-compiled why not try that but indeed twrp needs to be recompiled i had tried replacing the kernel from the recovery.img without luck don't boot

 

[Skorpion96]

twrp can be compiled adding dtbo and boot from stock pre-compiled why not try that but indeed twrp needs to be recompiled i had tried replacing the kernel from the recovery.img without luck don't boot

Try what you want, I hope on your success. Btw sources are different from a version of android to another so probably won't work

 

[ozmage]

Try what you want, I hope on your success. Btw sources are different from a version of android to another so probably won't work

not tested yet but i have enabled force module loading plus magic versioning module sign override this means kernel can boot with any vendor having encrytion nuked and load the modules from vendor/lib/

 

[RealRedPCat]

touch bug, reflash twrp and boot into it again

Touch still doesn't work, even with a reflash

 

[nirogu325]

Touch still doesn't work, even with a reflash

It never does. Use a USB mouse for navigation until or if this ever gets fixed.

 

[zairok]

Hi Team, someone have this problem when try load TWRP into T220

only official released binaries are allowed

How can I fix it?
I tried load vbmeta_disabled_R.tar but i had the same error

thanks in advance

 

[ozmage]

Hi Team, someone have this problem when try load TWRP into T220

only official released binaries are allowed

How can I fix it?
I tried load vbmeta_disabled_R.tar but i had the same error

thanks in advance

flashing with what ?

 

[dxsyrz]

View attachment 5656895
/* * Your warranty is now void. * * I am 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 Recovery * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. */

Remember this is in early development (alpha)

1. Not Working:
2. > Adb Sideloading
3. > Vibration (minor issue)
4. > Other Problems: Sometimes when you boot recovery touch not works and only solution is to re-flash TWRP again from Odin, this is kernel issue, we need custom kernel. I found out that in that case you can reboot with usb otg and mouse connected and twrp could start working on next reboot.

1. Install Instructions
2. Flash TWRP from Odin on AP Slot & Hold Volume Up + Power while flashing until TWRP appears.
3. Go to Advanced > Terminal and type "multidisabler" (without quotes", then data wipe.
4. Now reboot into system, after completing first setup of the device reboot into TWRP again to see if you can see the contents of your Internal Storage, you should, if yes you have successfully disabled Samsung encryption of internal storage.

1. Downloads (SM-T220): https://github.com/Skorpion96/android_device_samsung_gta7lite/releases/
2. Downloads (SM-T225): https://github.com/DevZillion/android_device_samsung_gta7lite/releases/tag/v0.1.0_T225
3. Downloads (SM-T227): https://github.com/DevZillion/android_device_samsung_gta7lite/releases/tag/v0.0.0_T227
4. Credits to me obviously for testing and recovery tree: https://github.com/Skorpion96/gta7lite_recovery
5. and to https://github.com/DevZillion for helping with TWRP.
6. Sources:
7. Device Tree:https://github.com/Skorpion96/android_device_samsung_gta7lite/tree/main
8. TWRP:https://github.com/minimal-manifest-twrp/platform_manifest_twrp_aosp/tree/twrp-11
9. Kernel - Samsung's Stock Kernel built from source.

a11?

 

[Skorpion96]

a11?

yep

 

[ozmage]

yep

sr tried to build new recovery using the stock kernel and dtbo don't set to compile on device tree

 

[ozmage]

check from line 54 to 61

orangefox_device_xiaomi_juice/BoardConfig.mk at ten · Joaquin-000/orangefox_device_xiaomi_juice

Contribute to Joaquin-000/orangefox_device_xiaomi_juice development by creating an account on GitHub.

github.com

 

[Skorpion96]

sr tried to build new recovery using the stock kernel and dtbo don't set to compile on device tree

@Zillion

 

[ozmage]

hmm https://github.com/DevZillion/android_device_samsung_gta7litex/blob/main/BoardConfig.mk
is already set , but twrp is getting compiled with kernel from sources or this is not the current DT used on last builds ?

OK found it

Commits · Skorpion96/android_device_samsung_gta7lite

Contribute to Skorpion96/android_device_samsung_gta7lite development by creating an account on GitHub.

github.com