Related
Team Win Recovery Project 2.x, or twrp2 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.
TWRP 3.2.1 Changelog: https://twrp.me/site/update/2017/12/09/twrp-3.2.1-0-released.html
Installation instructions: Use the official TWRP app (requires root), available here and here. If you already have TWRP installed, you can also download the latest available img and flash it from recovery.
DOWNLOAD (palman): https://dl.twrp.me/palman/
DOWNLOAD (v500): https://dl.twrp.me/v500/
More info: https://twrp.me/devices/lggpad83.html
Warning: builds for v500 require kitkat bootloader. If you are stuck on Lollipop bootloader, check this post.
Device source (palman): https://github.com/TeamWin/android_device_lge_palman
* The kernel in palman source is from 5.1 official build (source found here).
Device source (v500): https://github.com/TeamWin/android_device_lge_v500
* The kernel in v500 source is based on cm-14.1 sources.
XDA:DevDB Information
Team Win Recovery Project, Tool/Utility for the LG G Pad 8.3
Contributors
fefifofum, Dees_Troy, bigbiff
Source Code: https://github.com/omnirom/android_bootable_recovery
Version Information
Status: Stable
Created 2015-06-15
Last Updated 2017-12-10
Thanks very much for this! Great work! That is really nice that there is now official support for awifi/v500.
I assume the images are bumped?
Are the kernel sources for official twrp using your kernel sources?
Sources
This is the device repo for awifi/v500: https://github.com/TeamWin/android_device_lge_v500
The kernel in awifi/v500 repo was compiled from here, which is V50030A based.
This is the device repo for palman/v510: https://github.com/TeamWin/android_device_lge_palman
The kernel in palman/v510 repo is from 5.1 official build.
So, now we should be able to just flash the .img file directly within TWRP to update.
Deltadroid said:
So, now we should be able to just flash the .img file directly within TWRP to update.
Click to expand...
Click to collapse
Yes!
The repo for v510 is going to be renamed since it doesn't need to follow the "cyanogen" way, which is using the model name instead of the device name. That's why there is a little confusion with the names v500/awifi and v510/palman. The GPE repo will be named palman (which is the correct way) and the non GPE repo will stay as v500 (it should be called awifi), since almost every custom rom uses "cyanogen" way. If we wanted the non GPE to be named correctly we would need the devs of every custom rom to add an assert to their boardconfig so both, v500 and awifi, would be valid at installation time. It's just one line change.
Do we need to have TWRP recovery already flashed or can I just flash this recovery in the stock 20D with root?
Do we only need root access and flash the recovery using the TWRP manager from Play Store in stock 20D?
fefifofum, firstly, thanks for making an official TWRP for the V510.
Secondly, can you please enable backup of recovery partition?
luisbraz said:
Do we need to have TWRP recovery already flashed or can I just flash this recovery in the stock 20D with root?
Do we only need root access and flash the recovery using the TWRP manager from Play Store in stock 20D?
Click to expand...
Click to collapse
There are three ways to install TWRP explained at the installation details. Two of them require root and the third one requires twrp >= 2.8.4.0. Choose the one that is easier for you, they all should work.
aidfarh said:
fefifofum, firstly, thanks for making an official TWRP for the V510.
Secondly, can you please enable backup of recovery partition?
Click to expand...
Click to collapse
I could try, but it needs to go through gerrit. Why would you need to backup recovery partition?
fefifofum said:
Why would you need to backup recovery partition?
Click to expand...
Click to collapse
It's not strictly needed, but good to have for completeness. For example, if I flash a new version of TWRP and then find that's there a bug, I could just restore the previous version from backup. Of course, I could always just use fastboot or flashify to flash the old version, but it's nice to have the option.
fefifofum said:
There are three ways to install TWRP explained at the installation details. Two of them require root and the third one requires twrp >= 2.8.4.0. Choose the one that is easier for you, they all should work.
I could try, but it needs to go through gerrit. Why would you need to backup recovery partition?
Click to expand...
Click to collapse
I know, but I just want to be shure that this time I don't brick the tablet.
So you confirm that when we are stock with version 20D we just need root access? It's not necessary anymore a loky exploitable aboot?
Sorry for being a pain in the ass!
EDIT: Thank you @fefifofum for your work
I have installed the TWRP manager and selected install TWRP. Which version should I flash? The latest 2.8.1.0? And the twpr - awifi. img or the openrecovery - twrp - awifi. img?
I'm on stock 20d version with root. Thanks in advance.
aidfarh said:
It's not strictly needed, but good to have for completeness. For example, if I flash a new version of TWRP and then find that's there a bug, I could just restore the previous version from backup. Of course, I could always just use fastboot or flashify to flash the old version, but it's nice to have the option.
Click to expand...
Click to collapse
Old versions will still be available to download, so if a new version had issues you could always download and install an older version. No need to backup recovery I guess...
luisbraz said:
I know, but I just want to be shure that this time I don't brick the tablet.
So you confirm that when we are stock with version 20D we just need root access? It's not necessary anymore a loky exploitable aboot?
Sorry for being a pain in the ass!
EDIT: Thank you @fefifofum for your work
Click to expand...
Click to collapse
We don't need loki anymore, you just need to be on kitkat bootloader.
luisbraz said:
I have installed the TWRP manager and selected install TWRP. Which version should I flash? The latest 2.8.1.0? And the twpr - awifi. img or the openrecovery - twrp - awifi. img?
I'm on stock 20d version with root. Thanks in advance.
Click to expand...
Click to collapse
It looks like TWRP manager didn't update the images for the gpad. I will talk to them so they fix it and remove the old images, there should only be one version available: 2.8.6.0. Until then, please use the "dd" installation method.
fefifofum said:
It looks like TWRP manager didn't update the images for the gpad. I will talk to them so they fix it and remove the old images, there should only be one version available: 2.8.6.0. Until then, please use the "dd" installation method.
Click to expand...
Click to collapse
Thanks.
I think I'll wait for the TWRP manager update.
EDIT: Couldn’t wait and tried the dd method. For the first time, after thousands of attempts, I have the TWRP installed in the tablet!
luisbraz said:
Thanks.
I think I'll wait for the TWRP manager update.
EDIT: Couldn’t wait and tried the dd method. For the first time, after thousands of attempts, I have the TWRP installed in the tablet!
Click to expand...
Click to collapse
Glad to hear that! It seems the app TWRP manager cannot reach the new servers where official builds of TWRP are, so it's better not to use the app installation method to avoid installing old versions.
@fefifofum thanks a lot!!! I'm using slim alpha 4, what bootloader should I flash to solve the backlight problem? Thanks again
Pd: use rashr app to flash twrp, download .img and flash from internal memory, no problems. Don't use twrp manager.
bokoy said:
@fefifofum thanks a lot!!! I'm using slim alpha 4, what bootloader should I flash to solve the backlight problem? Thanks again
Pd: use rashr app to flash twrp, download .img and flash from internal memory, no problems. Don't use twrp manager.
Click to expand...
Click to collapse
I guess V50010B bootloader is what you need, but then you will probably have brightness issues while using this recovery.
New version
TWRP 2.8.7.0 released.
fefifofum said:
TWRP 2.8.7.0 released.
Click to expand...
Click to collapse
Hi all!
I have now TWRP 2.8.6.0 taken from here: http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
Which are the differences between these recoverys? Which is the better to install?
Thanks!
Hey Guys! How to upgrade from this version? http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
I have a v50020d model.
D4xel said:
Hi all!
I have now TWRP 2.8.6.0 taken from here: http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
Which are the differences between these recoverys? Which is the better to install?
Thanks!
Click to expand...
Click to collapse
This one is official (without the quotes), doesn't require loki and is adapted to kitkat bootloader backlight. The other one you mention is adapted to jellybean bootloader backlight and requires loki. Just install the one that fits your needs.
cianz94 said:
Hey Guys! How to upgrade from this version? http://forum.xda-developers.com/lg-g-pad-83/orig-development/recovery-twrp-2-8-2-0-v500-t2968472
I have a v50020d model.
Click to expand...
Click to collapse
You have the install instructions on the first post. You can also download the image and flash it with THIS APP.
Hey,
TWRP 3.1.1 Touch Recovery beta version is released for Xiaomi Mi A1.
Download - Go to downloads tab
Update:
1. Magisk v13.4 is working fine.
Workaround for Xposed:
Xposed is not installing through TWRP and when tried with App, still it's giving errors. So below is the temporary solution till we get a permanent one.
1. Don't flash TWRP. Just boot into it from bootloader by using command - fastboot boot recovery_name.img
2. Flash latest SuperSU zip.
3. Reboot to System.
4. Your phone will be rooted now and install Xposed through app.
Important:
1. Don't flash it, just boot into it.
2. If flashed, re-flash the latest stock boot image.
Instructions:
1. Download the twrp image and twrp installer zip
2. fastboot boot twrp-3.1.1-tissot-beta.img
3. Flash twrp-installer-tissot-3.1.1.zip
4. Reboot to recovery
Flash Magisk v13.4 built for Pixel devices by @Goodwin_c. Available in the downloads tab.
Issues:
1. Flashing SuperSU will break TWRP. SuperSU will work, but TWRP will be gone.
2. Xposed won't flash without modification.
Future update:
1. Make TWRP and SuperSU to co-exist
2. Compatibility with Xposed and Latest Magisk
Disclaimer:
We are not responsible for anything that may happen to your phone as a result of installing custom recoveries, roms and/or kernels. you do so at your own risk and take the responsibility upon yourself.
XDA:DevDB Information
TWRP 3.1.1 for Mi A1, Tool/Utility for the Xiaomi Mi A1
Contributors
mahefooz4u, ravinder0003, Thanks to @Dees_Troy and TWRP Team
Source Code: https://github.com/mahefooz/android_device_xiaomi_tissot
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2017-10-15
Created 2017-10-13
Last Updated 2017-10-16
good work bro waiting for development to start
Great work!
Celebrations
The first step towards the good community has been taken
Great were all waiting for devs to take a look at this devices ! Will it be official when you've fixed the boot issue ? thanks
great work!! thanks guys :good: Will I be able to flash Aroma Uninstaller to debloat?
deepakmohank said:
great work!! thanks guys :good: Will I be able to flash Aroma Uninstaller to debloat?
Click to expand...
Click to collapse
Yes, Aroma installer is working
thank-you. Have you tried the way Pixel devices boot twrp, send twrp zip to internal, then flash?
---------- Post added at 11:28 AM ---------- Previous post was at 11:01 AM ----------
Sorry for asking too many questions, one more to add, which s the partition that mounts when we mount System from twrp? Is it a or b?
Coolio
lakyman said:
Great were all waiting for devs to take a look at this devices ! Will it be official when you've fixed the boot issue ? thanks
Click to expand...
Click to collapse
Don't expect too much from now.
Wait for sometime as this is ported
Great work waiting for stable version... ?
great, thank you very much!!!
deepakmohank said:
Sorry for asking too many questions, one more to add, which s the partition that mounts when we mount System from twrp? Is it a or b?
Click to expand...
Click to collapse
yea good question, I'd like to know about it too..
marhensa said:
great, thank you very much!!!
yea good question, I'd like to know about it too..
Click to expand...
Click to collapse
I could see in Pixel forums about flashing twrp. It has options to back up a, b partitions or even both. Atm no access to computer, will need to check whether urs allow us the same.
Pixel twrp a/b link:
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Surprise!!!
Booted TWRP? But isn't temporary? Sad ?.
But don't worry, I have created a zip, ahh actually ported a zip ?, to flash TWRP permanently ?.
But please do note that I haven't tested this personally yet, as I'm in a bus, traveling right now.
But if guys have guts, then go ahead, & try this, & please report back .
Instructions:
Boot TWRP & just flash this zip from TWRP. That's all...
Link:
https://www.androidfilehost.com/?fid=962021903579484616
Update Test 2: https://www.androidfilehost.com/?fid=962021903579484804
If it works, please don't forget to hit thanks...
deepakmohank said:
I could see in Pixel forums about flashing twrp. It has options to back up a, b partitions or even both. Atm no access to computer, will need to check whether urs allow us the same.
Pixel twrp a/b link:
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Click to expand...
Click to collapse
No support for a/b system. Only active system can be reached
Thanks for great effort by devs
thanks for sharing~
hope it works~
Hi!
I just want to post my experiences so far.
TWRP booted up fine, also backup and MTP works.
I tried flashing magisk v14.2, which's installer told me the B slot is currenly active etc. Flashed without any problem. But rebooting the device I got bootloop.
Restoring the boot image from the backup made the device back to booting state.
ghpranav said:
Booted TWRP? But isn't temporary? Sad ?.
But don't worry, I have created a zip, ahh actually ported a zip ?, to flash TWRP permanently ?.
But please do note that I haven't tested this personally yet, as I'm in a bus, traveling right now.
But if guys have guts, then go ahead, & try this, & please report back .
Instructions:
Boot TWRP & just flash this zip from TWRP. That's all...
If it works, please don't forget to hit thanks...
Click to expand...
Click to collapse
unfortunately it does not work
h**p://kephost-image.tk/files/64k6re0jfsp4zmienhkr.png
TaRsY said:
Hi!
I just want to post my experiences so far.
TWRP booted up fine, also backup and MTP works.
I tried flashing magisk v14.2, which's installer told me the B slot is currenly active etc. Flashed without any problem. But rebooting the device I got bootloop.
Restoring the boot image from the backup made the device back to booting state.
Click to expand...
Click to collapse
Somehow Magisk is not yet working in Mi A1. Either flashed through recovery or other method, getting bootloop and other issues.
TaRsY said:
Hi!
I just want to post my experiences so far.
TWRP booted up fine, also backup and MTP works.
I tried flashing magisk v14.2, which's installer told me the B slot is currenly active etc. Flashed without any problem. But rebooting the device I got bootloop.
Restoring the boot image from the backup made the device back to booting state.
Click to expand...
Click to collapse
If you know then Magisk is not supported officially for A/B partitons devices including Pixel
Unofficial Lineages OS for Razr HD (xt926_jbbl)
This is only for JBBL do NOT try on KKBL
I am not responsible for bricked devices, loss of data, dead SD cards,
* loss of hair, 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, everyone will laugh at
* you and I will deny any wrong doing or responsibility.
Procedure
NB: You must format your Data and Cache partitions as F2FS
Download the latest PICO or NANO GApps from OpenGapps
Backup your internal SD Card, off of the device eg USD or Hard Disk
Boot to TWRP
Make a nandroid backup, and ensure this backup is not on the device itself
Format your data partition and cache partition to F2FS (do NOT post for instructions on how
to do this on this thread!)
Wipe Cache , System & Dalvik-Cache
Flash the ROM Zip
Flash Gapps ARM -> 7.1
Wipe cache and dalvic
Done - Reboot to [System]
Wait...
lineage-14.1-20200214-UNOFFICIAL-xt926_jbbl
Security patch level Feb 05, 2020
Changelog https://www.lineageoslog.com/14.1
Download rom and recovery here: https://www.androidfilehost.com/?w=files&flid=304892
Known issues:
You tell me
XDA:DevDB Information
Unofficial Lineage 14.1 XT926_JBBL, ROM for the Motorola Droid RAZR HD
Contributors
Wheels564
Source Code: https://github.com/wheels564
Thanks go out to the Lineage team for maintaining Nougat roms
Also thanks to Metalor for his source work which this rom is based on
And DiamondJohn for his tutorial on building TWRP from source
ROM OS Version: 7.x Nougat
ROM Firmware Required: JBBL
Based On: Lineage
Version Information
Status: Nightly
Created 2020-02-18
Last Updated 2020-02-18
Reserved
Reserved again
Wow, twrp 3.1.1, impressive. I really didn't think that we could get it up that high. Good work! And feel free to try a higher twrp version (minimal manifest 8.1 does give you twrp 3.3.1 )
Btw, decompiled your recovery. Not sure where you have your twrp flags, but whatever board config file they are in, add in TW_EXCLUDE_SUPERSU := true , as magisk is the replacement to supersu
palmbeach05 said:
Wow, twrp 3.1.1, impressive. I really didn't think that we could get it up that high. Good work! And feel free to try a higher twrp version (minimal manifest 8.1 does give you twrp 3.3.1 )
Btw, decompiled your recovery. Not sure where you have your twrp flags, but whatever board config file they are in, add in TW_EXCLUDE_SUPERSU := true , as magisk is the replacement to supersu
Click to expand...
Click to collapse
Minimal manifest from Lineage only goes to nougat. The rest of twrp is on Omni. I have to rebrand everything to Omni and there are other changes that need to be made for it to build. It's gonna take some time and I don't have a lot of it right now. BTW I have twrp working on mb886 but you have to use a mouse. I got lineage 13 to install on it but am having trouble with 14.1.
palmbeach05 said:
Wow, twrp 3.1.1, impressive. I really didn't think that we could get it up that high. Good work! And feel free to try a higher twrp version (minimal manifest 8.1 does give you twrp 3.3.1 )
Btw, decompiled your recovery. Not sure where you have your twrp flags, but whatever board config file they are in, add in TW_EXCLUDE_SUPERSU := true , as magisk is the replacement to supersu
Click to expand...
Click to collapse
Just compiled a new recovery. Check and see if thats what you want. My main computer is compiling a rom right now.
Sorry for a novice question. Can I install the TWRP image in my xt907 TWRP on my xt926.
yoshkapundrick said:
Sorry for a novice question. Can I install the TWRP image in my xt907 TWRP on my xt926.
Click to expand...
Click to collapse
If you have JBBL you can use the TWRP from the link to androidfilehost. It's specifically made for the xt926 but only if you have jelly bean boot loader and not Kit Kat boot loader.
Wheels564 said:
If you have JBBL you can use the TWRP from the link to androidfilehost. It's specifically made for the xt926 but only if you have jelly bean boot loader and not Kit Kat boot loader.
Click to expand...
Click to collapse
I have a jbbl. But can I directly install the image file while in the TWRP that I currently have which is the jbbl for the 907 version 3.1.1 or do I have to side load it again. Sorry for the basic questions i am a novice.
Wheels564 said:
Just compiled a new recovery. Check and see if thats what you want. My main computer is compiling a rom right now.
Click to expand...
Click to collapse
I don't have the ahd available right now, its in a box somewhere, but i will test as soon as i can. I can still look at it by decompiling the img though.
If you grab up omni's android_bootable_recovery and replace it with what you have in your local directory, it should work. For fun, i've taken out my old droid x and did a swap like that and it worked. Like i said, just passing along some ideas/advice.
yoshkapundrick said:
I have a jbbl. But can I directly install the image file while in the TWRP that I currently have which is the jbbl for the 907 version 3.1.1 or do I have to side load it again. Sorry for the basic questions i am a novice.
Click to expand...
Click to collapse
Unless you change recovery to the xt926_jbbl version you will get error 7. Recovery is looking for the assert line in the rom zip file which prevents people from flashing the wrong rom. There's plenty of threads here that guide you how to flash recovery. Once you flash recovery and rom your phone will show as Razr HD and screen resolution will be correct. Also HDMI out will work.
Using minimal ADB and Fastboot
Make sure recovery image is in adb and fastboot folder
1. Rename twrp image to recovery.img
2. "Adb reboot bootloader"
3. "fastboot flash recovery recovery.img
4. "fastboot reboot"
Leave out quotes
yoshkapundrick said:
I have a jbbl. But can I directly install the image file while in the TWRP that I currently have which is the jbbl for the 907 version 3.1.1 or do I have to side load it again. Sorry for the basic questions i am a novice.
Click to expand...
Click to collapse
OMG OMG can you say TWRP 3.3.1-0 for the xt926_jbbl and xt907_jbbl? You were right!! New life for these old devices? I made one to test on the xt907. I did a backup and all seems well. I'll try the version for the xt926 when i get off work and post it on androidfilehost. Kudos
Wheels564 said:
OMG OMG can you say TWRP 3.3.1-0 for the xt926_jbbl and xt907_jbbl? You were right!! New life for these old devices? I made one to test on the xt907. I did a backup and all seems well. I'll try the version for the xt926 when i get off work and post it on androidfilehost. Kudos
Click to expand...
Click to collapse
Would a comparison to Lazarus be inappropriate on XDA LOL ?
twrp3.3.1.0 xt926_jbbl
Recovery "twrp3.3.1.0 xt926_jbbl wheels564" is up on androidfilehost.
Recovery here: https://www.androidfilehost.com/?fid=4349826312261727895
Flashed the TWRP image directly over my JBBL for xt907 version 3.1.1 with no problems. Then flashed rom and similarly no problems.
---------- Post added at 11:37 PM ---------- Previous post was at 10:38 PM ----------
Minor point, camera a no go using open camera and other camera apps.
yoshkapundrick said:
Flashed the TWRP image directly over my JBBL for xt907 version 3.1.1 with no problems. Then flashed rom and similarly no problems.
---------- Post added at 11:37 PM ---------- Previous post was at 10:38 PM ----------
Minor point, camera a no go using open camera and other camera apps.
Click to expand...
Click to collapse
Your right, I'll have to find out where it went. It's still on the Feb 06 version (Jan 5 security patch date)
I must say that your rom is very nimble like DiamondJohn's roms. It is a very big deal when you are dealing with 1GB of ram.
I have other old devices (like a Motorola Xoom) with custom roms that are problematic with 1GB of ram.
Thank you very much
New build up
lineage-14.1-20200222-UNOFFICIAL-xt926_jbbl
Link: https://www.androidfilehost.com/?fid=4349826312261729680
Changelog:
Added missing camera wrapper
Clean flash only, dirty flash will not restore missing camera app.
If you use Open Camera a dirty flash does restore it's functionality.
New build up
lineage-14.1-20200226-UNOFFICIAL-xt926_jbbl
Changelog:
NFC fixes
Link: https://www.androidfilehost.com/?fid=4349826312261732779
Disclaimer : I am in no way an experienced developer and make sure that you have the stock firmware if needed. Please do not follow this guide if you do not know what you are doing.
Description
This is something I thought of doing as I needed this tablet for university work. I do not promise support but will post if I get more things like this done.
Kernel with Defex disabled for Samsung Galaxy Tab A 8.0 (2017) T385.
The boot image was repacked with a stock boot image and a custom compiled kernel only with modifications to remove defex and to be able to flash magisk on the latest firmware (XME-T385DXU3CTH2-20200828114930) which it was extracted from.
The ZImage is attached if you want to repack it by yourself.
I do not guarantee if this will work on your device. Flash at your own risk.
Notes on Flashing and Root
What I have used :
1. Flash boot.img to BOOT in heimdall with `--no-reboot`
heimdall flash --no-reboot --BOOT boot.img
2. Use key combo to get into TWRP Recovery
3. Factory Reset -> Type yes
4. Reboot into TWRP Recovery
5. Flash Universal+DM-Verity+and+ForceEncrypt+Disabler+(2020-11-02)
6. Flash RMM_Bypass_v3
7. Reboot into System and verify that the kernel version is correct (3.18.120 Feb 9 2021)
8. Reboot to Recovery and flash Magisk normally
Download
Github Release
Credits
@corsicanu - RMM_Bypass_V3
@SebaUbuntu - Device Tree Skeleton
References
RMM Bypass Guide
Compiling Kernel Guide
Defex Discussion Github Magisk
Android Image Kitchen
Probably keep another post just in case.
Its worked and my SM-T385 has been rooted !!!
Thank you so much for your kernel @brokenaxe
GitHub Link not working !!!
Thankyou sooo much mann.. You don't know how frustrated I was with three SM-T385 tabs in my office which were dead slow and desperately needed root. Those things straight up bootlooped after installing magisk and I was always back to square one. You're a lifesaver. Thanks again...
PLEASE BEFORE YOU decide to try this recovery, you MUST read all of post 1 and 2 (about 3 minute read). If you think this is an unreasonable request, then stop reading now and find another recovery. Thank you.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this software.
BACKUP YOUR DATA BEFORE trying this TWRP.
Source code
Kernel source
https://github.com/retiredtab/android_kernel_samsung_universal5433
Device tree
https://github.com/retiredtab/TWRP_gts28wifi/tree/main/gts28wifi
TWRP source code (built using minimal manifest TWRP 7.1)
https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni/tree/twrp-7.1
Download TWRP from
https://sourceforge.net/projects/retiredtab/files/SM-T710/TWRP/
Installation Instructions
You MUST be running stock 7.0 to have the latest bootloader before flashing this TWRP.
Note I do NOT run Windows OS so there are no provided instructions on how to install TWRP using Windows. There's lots of tutorials and videos online on how to install TWRP via Windows. Do your own research. If this is unreasonable to you, don't use this TWRP. Questions regarding how to install TWRP using Windows/odin will go unanswered.
You need to boot the T710 into download mode. Power off. Press home button + power + volume down (farthest away from power button) at the same time. Let go when you see "Warning" text on the screen, then choose volume up to continue. Your screen should now show "Downloading... Do not turn off target"
Linux users can use heimdall to flash this recovery. For example,
Code:
heimdall flash --RECOVERY TWRP_3.5.2_9_SM-T710_20210719_Unofficial.img
After flashing the recovery image, you must boot into recovery immediately (using the hardware key combination) to run TWRP, otherwise the Samsung software will overwrite TWRP and you will have to start over again. I usually am already pressing the recovery hardware key combination while the recovery image is being flashed. The flash process will be very quick (a few seconds at most).
The recovery hardware key combination is home button + power + volume up (volume up is closest to the power button) all pressed at the same time.
Updates
Unless Android 12 or LineageOS 19.0 requires some mandatory changes to TWRP, this will be the only TWRP build I make for the forseeable future. There will be no planned updates to 3.5 unless there's a major bug or security vulnerability. The only time you need to boot into TWRP is to upgrade the custom rom.
I have been using this TWRP since Aug 19, 2021.
The "official" TWRP T710 ALL have broken MTP and adb in every version which is why I built my own despite reporting these problems to the maintainer.
Reserved.
Thank you so much for this! I teared my hair out for many, many hours thinking I had issues with drivers on my PC why adb or MTP never worked in every official TWRP release I've tried... I thought I'd give yours a try and voila! It works! Beautifully so.
Thank you, thank you, thank you!
Whenever i flash this specific build of TWRP my tab instantly bootloops.
cammykool said:
Whenever i flash this specific build of TWRP my tab instantly bootloops.
Click to expand...
Click to collapse
What bootloops? Is it TWRP that bootloops? Stock Samsung OS? LineageOS? How are you flashing it? Heimdall? Odin? Give more details.
retiredtab said:
What bootloops? Is it TWRP that bootloops? Stock Samsung OS? LineageOS? How are you flashing it? Heimdall? Odin? Give more details.
Click to expand...
Click to collapse
Sorry. Was a quick type. And I've done a bit more troubleshooting. The older builds with broken MTP seem to boot perfectly. But flashing the build outlined here seems to get the tablet stuck at the Tab S2 screen. The only place it can go is DL. system won't boot again unless I reflash a system image. The tablet was still on a build of 5.1.1 though and I know these modern recoveries probably don't expect that so i am letting it update the stock stuff now.
Yup that was it. Updated to 7.0 and the recovery flashed and ran perfectly! Thank you!
cammykool said:
Yup that was it. Updated to 7.0 and the recovery flashed and ran perfectly! Thank you!
Click to expand...
Click to collapse
Thanks for reporting back. I added this one line to the installation instructions in post #1.
"You MUST be running stock 7.0 to have the latest bootloader before flashing this TWRP."
PS. If you want to use my 18.1 T710 rom, it's over at
https://forum.xda-developers.com/t/...neageos-18-1-for-sm-t710-may-12-2022.4430339/
retiredtab said:
Thanks for reporting back. I added this one line to the installation instructions in post #1.
"You MUST be running stock 7.0 to have the latest bootloader before flashing this TWRP."
PS. If you want to use my 18.1 T710 rom, it's over at
https://forum.xda-developers.com/t/...neageos-18-1-for-sm-t710-may-12-2022.4430339/
Click to expand...
Click to collapse
Thank you! That was actually the plan! Running it now and posted in the other thread!
Thank you for nice work, I've installed it on my T715, it works very well, just now my device is recognized as T710 too. Could you please provide a build for T715? As the function of adb/mpt doesn't work on all of twrp for T715 too.
Was running LoS 16 and decided to update. Went to stock 7.0 then LoS 18.1 using this version of TWRP without any problems or the issues some other versions of TWRP have! Thanks