[RECOVERY][Official] TWRP for the Samsung Galaxy Tab A 9.7 WiFi - Samsung Galaxy Tab A series ROMs, Kernels, Recover

TWRP for the Samsung Galaxy Tab A (gt510wifi)
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* 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. Hard & a lot.
*
*/
Latest Stable Release
TWRP website
Instructions
How to install TWRP using ODIN
1) Go to Settings » About phone » and tap “Build number” seven times to enable “Developer options”.
2) Go back to the main Settings page, scroll to bottom and select“Developer options” from there.
3) Under Developer options, look for “Enable OEM unlock” checkbox/toggle and make sure you check it or turn it ON. If the checkbox does not exist, you can skip this step.
4) Now boot your Samsung Android device into Download mode. To do so follow the steps below:
5) Switch off your device.
6) Press and hold “Home + Power + Volume down” buttons for a few seconds until you see a warning screen.
Press Volume Up on the warning screen to accept it and boot into Download mode.
Once your device is in download mode, connect it to the PC with a USB cable. The Odin will automatically detect the device and show an “Added!!” message. If not your device is not connected properly.
7) Now click on the AP tab on Odin window and select the TWRP recovery .tar file that you downloaded for your device.
8) Uncheck auto reboot in the options tab.
9) Click the Start button on Odin to start flashing and wait for it to finish the process.
Once it finished successfully, a pass message on the Odin screen will pop up.
Now you can disconnect your device. Reboot the device by pressing volume down + power + home.
When the screen goes black, press volume up, power and home to get into TWRP recovery.
Done! TWRP is now installed on your device.
Issues
None known.
Kernel source:
https://github.com/Galaxy-MSM8916/android_kernel_samsung_msm8916
Sources:
Device tree
TWRP Version: 3.2.3-0
Version Information:
Recovery Target Device: Samsung Galaxy Tab A [ SM-T550 ]
Status: Stable
Release Date: 24-09-2018

Reserved

Statted above is the following:
Version Information:
Recovery Target Device: Samsung Galaxy Tab A [ SM-T550 ]
Status: Stable
Release Date: 24-09-2018
Are you certain that the model number is correct? I have the Samsung Galaxy Tab A 9.7" (model number SM-P550) HENCE = P550. Not being an prick just making sure is all. Thanks for posting this by the way, L8R!

kidcrazie said:
Are you certain that the model number is correct? I have the Samsung Galaxy Tab A 9.7" (model number SM-P550) HENCE = P550. Not being an prick just making sure is all. Thanks for posting this by the way, L8R!
Click to expand...
Click to collapse
There are two versions of the Samsung Galaxy Tab A 9.7. One without pen and one with s-pen.
SM-T550 = no pen.
SM-P550 = s-pen.
https://www.samsung.com/levant/tablets/galaxy-tab-a-9-7-t550/SM-T550NZWAMID/
https://www.samsung.com/us/product/...b&mdlUrlName=SM-P550NZAAXAR&pageUrlName=specs

There are two versions of the Samsung Galaxy Tab A 9.7. One without pen and one with s-pen.
SM-T550 = no pen.
SM-P550 = s-pen.
>>>retiredtab
I stand corrected/informed now. I hadn't come across this version in stores before. I was under the impression that only WiFi & LTE/WiFi versions were available.

Crazy

Hey @virsys, if you have time can you please create a twrp also for the sm-t555 (gt510lte). @ashyx also built a working one a few years ago, but it's not updated.
I'm not able to build/update one due to lack of skills and i don't really feel to f**k up my device trying to do that.
Here's the link of ashyx with the devicetree: https://github.com/ashyx/TWRP_Samsung_gt510lte
Thanks in advance,
Cheers,
DJLeleX

Hello!
I'm trying to upgrade TWRP on my SM-T550, from 3.6.2_9-0 to the (current) latest 3.7.0_9-0 (from https://eu.dl.twrp.me/gt510wifi/).
However, when trying to flash twrp-3.7.0_9-0-gt510wifi.img from TWRP, I get the following error message:
Size of image is larger than target device
Am I doing something wrong?
FWIW, this tablet is running LineageOS 19.1 from https://forum.xda-developers.com/t/...-for-galaxy-tab-a-sm-t550-dec-9-2022.4479347/

breversa said:
I'm trying to upgrade TWRP on my SM-T550, from 3.6.2_9-0 to the (current) latest 3.7.0_9-0 (from https://eu.dl.twrp.me/gt510wifi/).
However, when trying to flash twrp-3.7.0_9-0-gt510wifi.img from TWRP, I get the following error message:
Size of image is larger than target device
Am I doing something wrong?
FWIW, this tablet is running LineageOS 19.1 from https://forum.xda-developers.com/t/...-for-galaxy-tab-a-sm-t550-dec-9-2022.4479347/
Click to expand...
Click to collapse
There's a reason my FAQ states that you MUST use a certain version of TWRP when using my roms/builds. More details already written at
https://forum.xda-developers.com/t/...or-sm-t810-dec-12-2022.4430349/#post-86745013
Again, even though it's on the official TWRP site doesn't mean it's been tested or code is maintained and kept up to date.
As newer version of TWRP add more functionality and get more code bloat, the recovery size will get bigger and may not fit the recovery partition. There are ways to minimise the rom size, but the maintainer has to make those changes, test and submit them to TWRP github.

Thanks @retiredtab for explaining why it is necessary to stick with your recommended TWRP version, and not the latest official one.

virsys said:
TWRP Version: 3.2.3-0
Version Information:
Recovery Target Device: Samsung Galaxy Tab A [ SM-T550 ]
Status: Stable
Release Date: 24-09-2018
Click to expand...
Click to collapse
+ at https://github.com/VirsysElectron/twrp_device_samsung_gt510wifi
--> Last changes 4 years ago
Why is it possible that there are many newer Versions at
Download TWRP for gt510wifi
Download TWRP Open Recovery for gt510wifi
eu.dl.twrp.me
At https://eu.dl.twrp.me/gt510wifi/, there is linked this thread.
So if maintainer has changed, is there a reason why the link has not been updated?
@ maintainer (virsys??)
- would you be so kindly and update the recovery according to this:
[CLOSED][RECOVERY] [TWRP] Fix • Backup Internal Storage • backup option
O B S O L E T E Fix for • Backup Internal Storage • backup option Universal TWRP Bind Mount Enabler It is a well known fact that TWRP Backup does did not include Internal Storage aka /storage/emulated/0 If you ever wonder how to backup...
forum.xda-developers.com
- shrink your recovery as described from retiredtab to make it working with his custom-rom
Thanks.

official TWRP releases are auto-generated even if maintainer is absent. (actually you can patch your fstab yourself in 5 minutes, just unpack twrp.img, add the line /storage... repack and flash. it's so simple it's not even worth a guide.)
as for the file size.. well IMHO this a big failure not including some file size check according to partition size. reminds me on the days of clockworkmod recovery. should be fixed in build bot ASAP, consequently not releasing new versions without maintenance.

breversa said:
However, when trying to flash twrp-3.7.0_9-0-gt510wifi.img from TWRP, I get the following error message:
Size of image is larger than target device
Click to expand...
Click to collapse
wait... file size is 15 MB so this can't be true? partition should have at least 32/64 MB nowadays.
did you repartition whole phone with LineageOS or something?

aIecxs said:
did you repartition whole phone with LineageOS or something?
Click to expand...
Click to collapse
I think so. I am not sure.
I am using LOS 18 unoffical from retiredtab.
When I installed this image the first time, I set the tick at "install LOS-Recovery".
This was a mistake. So I installed TWRP 3.6 from this thread.
Is it possible to change partition sizes without flashing any Partition? How?

do you have the same warning?
Size of image is larger than target device
@Leonniar had similar issue
Leonniar said:
When trying to flash boot and the patched .img I get:
Code:
fastboot: error: boot partition is smaller than boot image
Click to expand...
Click to collapse
turned out it was just issue with length of file name, not actually partition itself...
Leonniar said:
I fixed it by shortening the name of the file from: magisk_patched_[random_strings].img to magisk_boot.img
Click to expand...
Click to collapse

Hi! I have a question, I have a Samsung tablet with the model SM-P555M, can this recovery work without problems? I want to install the official Samsung ROM that comes with Android Nougat

Related

[RECOVERY][SM-A700FD][TWRP][3.0.2.0] TeamWin Recovery Project

Code:
#include
/*
* 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 ROM
* 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.
*/
Warning
This recovery will TRIP your Knox Counter and your warranty will be void.
This recovery is only for Samsung Galaxy A700FD Qualcomm Snapdragon variant running 5.0.2 (lollipop).
Tested Safely on following devices.
Samsung Galaxy A700FD
Why TWRP ? Why not some rooted firmware which keeps warranty safe ?
TWRP is a custom recovery. It has many more functionality than stock recovery! if something goes wrong while flashing something you can always make a backup use this recovery which can be restored when things get messed. if mess is of large extend you can always flash stock firmware.
Why new TWRP Recovery ?
The older version which was released will not be compatible with cm structure due to mount points and hence this recovery will be supportable for all custom flashing.
Instructions
Follow the instructions carefully.
Step 1 :
Install Samsung Drivers and connect your device to PC. let it install drivers and if its updating let it update. your device drivers should be perfectly installed without a single failure.
Link to Samsung Drivers
Step 2 :
Download Odin 3 you can use 3.07 or 3.09
You can download Odin from here
Download the TWRP Recovery
Step 3:
Turn of your device and go to odin mode [ Vol down + power + home button (all at the same time) ] release it when you see Galaxy A7 Logo
Press vol up to confirm
Step 4:
Now that you are in Odin Mode connect your device via USB cable.
Now open Odin3 3.09 or 3.07 that you have downloaded.
If there is a pop-up like Installing ADB drivers let it get finished it usually updates.
Make sure the COM : xx (xx is usb port number it can be any number so dont worry about it,just verify COM is lit up)
Now select AP and browse to where you have .tar file and select it
Make Sure only Default Auto Reboot and F. Reset Time is ticked and nothing.verify twice only these 2 are ticked.
Untick Auto Reboot if you are installing recovery for first time!
Click Start and wait for the process to end. DO NOT Interrupt during this time.
Once it says PASS. BOOT INTO RECOVERY USING VOL UP + HOME + POWER BUTTON.
Done.
Credits:
TWRP Team for their awesome recovery.
@RVR for testing recovery!
XDA:DevDB Information
TeamWin Recovery Project, ROM for the Samsung Galaxy A Series
Contributors
jackeagle
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 3.0.2.0
Stable Release Date: 2016-03-07
Created 2016-03-07
Last Updated 2016-05-25
Downloads
TWRP Build 1
TWRP Build 2 (V3.0.0)
TWRP v3.0.2.0 (Build 3)
TWRP v3.0.2.0 (Build 4)
Changelog
Code:
27/06/2016
- Added Compatibility for Samsung Marshmallow Firmware Release
- Merged with Samsung Marshmallow kernel release
- TWRP upstream merge.
25/05/2016
- Fixed Recovery Loop Issues.
- Fixed MTP Media Transfer on Recovery.
- Added EFS Partition Backup Option
- Fixed Brightness Slider
- Updated TWRP to latest v3.0.2.0
07/03/2016
- Updated TWRP to v3.0.0
20/11/2015
- Initial Release
Reserved 2
I need a custom recovery for Galaxy A8 (A800F) please.
Thanks
How to root Galaxy A700FD and install a recovery running on lolipop 5.0.2.
Developers please go for Samsung Galaxy A7 A700FD ..
Sent from my SM-A700FD using Tapatalk
Nice keep posting about A700FD
Sent from my SM-A700FD using Tapatalk
TWRP Link is dead.
TWRP updated to v3.0.0.
Links are in OP.
Enjoy!
jackeagle said:
TWRP updated to v3.0.0.
Links are in OP.
Enjoy!
Click to expand...
Click to collapse
build 2 is invalid ,help
nukedanoob said:
build 2 is invalid ,help
Click to expand...
Click to collapse
Use this link: https://www.androidfilehost.com/?fid=24438995911970888
and what if I can't flash because of secure boot enabled?
(in download mode there is a line "Qualcomm Secureboot - Enabled (CSB)" and "Write Protection - Enabled". I think this is the cause).
what should I do? any help appreciated.
nevermind. it was a faulty cable.
lifehijack said:
Use this link: https://www.androidfilehost.com/?fid=24438995911970888
Click to expand...
Click to collapse
thanks
A7000 want to twrp 3.0.0too
来自我的 SM-A7000 上的 Tapatalk
lifehijack said:
Use this link: https://www.androidfilehost.com/?fid=24438995911970888
Click to expand...
Click to collapse
works fine,just rename the file
Qualcomm Secure Boot is enabled and trying to flash recovery gives this message on phone
secure check fail : recovery
Custom Binary(recovery) Blocked by A/L
Odin says Fail
Solved: Disabled Reactivation Lock in security settings
Phone booting into recovery each time when I reboot the phone. How to come out of recovery mode boot loop?
Can i use it on my a7000?
Hello jackeagle, I ask you to continue the CM13 E5 project, I enjoyed the rom! If I can help in any way! even a my donation and my friends for you to continue the rom!
Always get kernel not seandroid enforcing .... i cannot boot to the system i just installed... just a blank screen
. .

[Updated] Root and TWRP and restore wrong IMEI's and rotating MAC for 7.1.1 Stock Rom

I had some trouble to root the Elephone S7 7.1.1 Stock Rom. Therefore here is the short HowTo...
*** Root and TWRP for Elephone S7 4GB 7.1.1 Stock Rom http://bbs.elephone.hk/thread-12886-1-1.html
* SP_Flash_Tool download latest version e.g.: SP_Flash_Tool_v5.1720_Win.zip from http://spflashtools.com/category/windows
* SuperSU download latest version e.g.: SuperSU-v2.82-201705271822.zip from http://www.supersu.com/download
* Stock Rom download latest version e.g.: s7_4g_20170517133805_v2.3.zip from https://mega.nz/#!Z4AmRRTK!XLyd4O8HaS4B_XVNMdSn5OPX76rXDkOYXVekvn-9lMM
* TWRP 3.0.3 by Jemmini download latest version e.g.: recovery.img from https://www.dropbox.com/s/b7u3k1mgpppxlyx/recovery.img?dl=0
* create two folders, one for Stock Rom and one for TWRP
* unpack Stock Rom and copy MT6797_Android_scatter.txt into TWRP directory
optional:
* OpenGAps arm64 / 7.1 / stock download latest version e.g.: open_gapps-arm64-7.1-stock-20170629.zip http://opengapps.org/
* in OpenGAps zip delete from \GApps\ folder whatever you don't want
optional:
* AdAway v2.3 download latest apk from https://labs.xda-developers.com/store/app/org.adaway discussion https://forum.xda-developers.com/showthread.php?t=2190753
* AdAway systemless hosts download latest version e.g.: AdAway_systemless_hosts_v2.zip from https://www.androidfilehost.com/?fid=24438995911977059
optional:
* my_bootanimation.zip
* change your favorite boot animation in my_bootanimation.zip\system\media\
* add your own tweaks in my_bootanimation.zip\system\tweaks.prop
SP_Flash_Tool for Stock Rom:
* select Download-Agent: SP_Flash_Tool_v5.1720_Win\MTK_AllInOne_DA.bin
* select Scatter-Loading-File: Stock Rom\MT6797_Android_scatter.txt
* Firmware Upgrade
* switch phone off
* click Download and press "Power" to connect the phone
* after "Download OK" unplug USB and press "Power" to start phone
SP_Flash_Tool for TWRP:
* select Download-Agent: SP_Flash_Tool_v5.1720_Win\MTK_AllInOne_DA.bin
* select Scatter-Loading-File: TWRP\MT6797_Android_scatter.txt
* Download Only
* switch phone off
* click Download and press "Power" to connect the phone
* !!! after "Download OK" unplug USB and press "Home + Power" (about 10 seconds) until enter recovery !!!
* on phone select "recovery" with "Home" and "Vol -" for OK
* in TWRP select and install
SuperSu
optional Open Gaps
optional AdAway systemless hosts
optional my_bootanimation.zip
* reboot (may loop some times)
tip:
* "adb reboot recovery" doesn't work
* therefore switch phone off and press "Home + Power" (about 10 seconds) until enter recovery
* select "recovery" with "Home" and "Vol -" for OK to enter TWRP
*** restore wrong IMEI's after update to 7.1.1 Stock Rom http://bbs.elephone.hk/thread-13641-1-1.html
* Maui META download latest version e.g.: MauiMETA_exe_v9.1724.0.rar from https://www.needrom.com/download/maui-meta-3g-ver-7-1444-0-0/
* IMEI's from phone box
Maui META:
* switch phone off and unplug USB
* press and hold the "Vol- + Power" Button and connect USB, release the "Vol- + Power" Button and click "Reconnect" (wait until the ball turns yellow)
* !!! retry if it not works !!!
* in the selection box scroll to the IMEI download option and select (it will open a new window)
* copy !!! only the first 14 digits !!! of the 1st IMEI and paste in the IMEI field
* click the "Download To Flash" button and wait until message "Download IMEI to flash successfully"
* repeat this two steps for SIM_2
* close the window, click "Disconnect", unplug USB and restart phone
* check IMEI's in Settings > About Phone > Status
*** restore rotating MAC after update to 7.1.1 Stock Rom https://androidrookies.com/how-to-change-wlan-mac-address-on-mtk/
* in Playstore install "Root Explorer"
* HxD Hex Editor for Windows download latest version https://mh-nexus.de/downloads/HxDSetup.zip
* in Root Explorer copy \nvdata\APCFG\APRDEB\WIFI to \sdcard
* now copy WIFI file to Windows and edit with HxD Hex Editor
* for Your last MAC e.g.: 00:08:22:a8:e3:fb write it in Offset (h) 04 to 09
00 01 02 03 04 05 06 07 08 09
06 01 00 00 00 08 22 A8 E3 FB
* copy WIFI back to \sdcard
* in Root Explorer copy \sdcard\WIFI to \nvdata\APCFG\APRDEB\ and set permission to 660 (rw-rw—)
Have Fun
Thanks
I have problems, this is what I do, for twrp:
- Connect USB to phone
- Start Smart phone flash
- Select scatter file
- Click on download
- Press power in the phone
There, it doesnt download anything. The phone just boots up normally. It could be a driver problem since when it boots it says that the device couldnt not be recognized but where I can find the drivers?
Edit: finally i got it to work but not in a nice way. I tried to turn driver signature off, installing new VCOM drivers for S7 but nothing. So I just went to my other computer with Windows 7 64 bit and it worked all fine the first time. In this computer I have Windows 10 64 bit and always have problems with these things related to phones and flashing.
Thanks for the instructions.
Some comments:
You never mention that you should create a TWRP folder, so that confused me for a while.
You explicitly refer to Windows versions of files in your instructions, even though it's unnecessary. I did the process on Linux and it worked perfectly fine.
The recovery is not fixed for OTA updates. The first OTA update I got bricked my system and I had to reinstall everything. Is there a fixed version of the TWRP available for this phone? I know there's a fixed version for the Elephone P7000 here: bbs.elephone.hk/thread-5332-1-30.html
OpenGApps gave me many issues with crashing services and apps not starting. I decided to leave it out entirely, since the necessary apps are available in the Stock ROM. (I tried all GApps variants from pico to stock)
Even with a rooted system, I could not remove some OEM apps (such as the OTA app that will break the system). Is there a way to remove those anyway?
Hi. TWRP installed on my s7 (X25 - 4/64 G} but can't reboot (hanging logo). Pls. help me to fix it. Thanks
d1237 said:
Hi. TWRP installed on my s7 (X25 - 4/64 G} but can't reboot (hanging logo). Pls. help me to fix it. Thanks
Click to expand...
Click to collapse
Please try to install original Stock Rom with SP_Flash_Tool. And then retry to install TWRP.
Ghostbird said:
Thanks for the instructions.
Some comments:
You never mention that you should create a TWRP folder, so that confused me for a while.
You explicitly refer to Windows versions of files in your instructions, even though it's unnecessary. I did the process on Linux and it worked perfectly fine.
The recovery is not fixed for OTA updates. The first OTA update I got bricked my system and I had to reinstall everything. Is there a fixed version of the TWRP available for this phone? I know there's a fixed version for the Elephone P7000 here: bbs.elephone.hk/thread-5332-1-30.html
OpenGApps gave me many issues with crashing services and apps not starting. I decided to leave it out entirely, since the necessary apps are available in the Stock ROM. (I tried all GApps variants from pico to stock)
Even with a rooted system, I could not remove some OEM apps (such as the OTA app that will break the system). Is there a way to remove those anyway?
Click to expand...
Click to collapse
Hi Ghostbird, thank You for Your support!
* I have added the TWRP folder in the HowTo.
* Do You have tested the HypoTurtle TWRP? Works OTA update now?
* OpenGApps working without any problems, but i never tried to remove OEM apps.
* I have installed Stock Rom, updated OTA and then installed TWRP. No problems since then.
below You find my GApps folder:
batteryusage-all.tar.lz
calculatorgoogle-all.tar.lz
calendargoogle-all.tar.lz
calsync-all.tar.lz
cameragoogle-arm64.tar.lz
cameragoogle-common.tar.lz
cameragooglelegacy-arm.tar.lz
cameragooglelegacy-common.tar.lz
chrome-arm64.tar.lz
clockgoogle-all.tar.lz
contactsgoogle-all.tar.lz
dialerframework-common.tar.lz
dialergoogle-all.tar.lz
exchangegoogle-all.tar.lz
gmail-all.tar.lz
hangouts-arm64.tar.lz
keyboardgoogle-arm64.tar.lz
messenger-arm64.tar.lz
newsstand-all.tar.lz
newswidget-all.tar.lz
pixelicons-all.tar.lz
pixellauncher-all.tar.lz
storagemanagergoogle-all.tar.lz
taggoogle-all.tar.lz
Hi everyone
Link for twrp is down
Someone can post in attachement please ?
Regard
Bradco said:
Hi everyone
Link for twrp is down
Someone can post in attachement please ?
Regard
Click to expand...
Click to collapse
This should work for you. Used on my S7.
bluiis48 said:
This should work for you. Used on my S7.
Click to expand...
Click to collapse
thank you very much for the file, it does not work for me. it starts well on the recovery but can not start the system, still block on the logo.
I'm on s7_4g_20170814163417_v2.4.
Ah, I am still on the July release, have been holding off on the August ROM waiting to see if anything showed up for September but it looks like that might be game over for updates. Thanks for letting me know, saves me some time. I find the July one not too bad. Roll back for root ?
bluiis48 said:
Ah, I am still on the July release, have been holding off on the August ROM waiting to see if anything showed up for September but it looks like that might be game over for updates. Thanks for letting me know, saves me some time. I find the July one not too bad. Roll back for root ?
Click to expand...
Click to collapse
you're welcome , for root it's all good with magisk.
you install the latest version of magisk manager, you get the file boot.img from your rom, you patch this file via magisk manager and you just flash the new boot.img via flashtool. After root is functional.
Y'll try this : https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861
Thanks, I will give that a try when I finally decide to load the 0814 update (or newer if one becomes available). Can I ask why you were needing TWRP ? Also did you notice any improvement with the 0814 update? I have an S8 in transit and will be passing this S7 on to my wife but the S8 could be a while yet when Canada Post gets it. Magisk may work on that also, same X25 and ram.
bluiis48 said:
Thanks, I will give that a try when I finally decide to load the 0814 update (or newer if one becomes available). Can I ask why you were needing TWRP ? Also did you notice any improvement with the 0814 update? I have an S8 in transit and will be passing this S7 on to my wife but the S8 could be a while yet when Canada Post gets it. Magisk may work on that also, same X25 and ram.
Click to expand...
Click to collapse
of course a custom recovery is always useful, nandroid backup and flash some .zip.
for it is the first version of android 7 that I test and I find it very stable without problems.
Ha yes I wonder the purchase of a s8 tell me if it great
Yes I will give you my opinion but it will be a while because our customs and mail is very slow. As I remember I had a hard time with TWRP when I loaded the 20170517 stock rom. I finally did a full format with SPflashtool and when it seemed stuck at the boot animation I left it alone for maybe half an hour and it finally came to life so that version of TWRP does work for 7.1.1 for me.
bluiis48 said:
Yes I will give you my opinion but it will be a while because our customs and mail is very slow. As I remember I had a hard time with TWRP when I loaded the 20170517 stock rom. I finally did a full format with SPflashtool and when it seemed stuck at the boot animation I left it alone for maybe half an hour and it finally came to life so that version of TWRP does work for 7.1.1 for me.
Click to expand...
Click to collapse
ok I understand, little question about SP flash tool to make a full format you used which option DOWNLOAD ONLY / FIRMWARE UPGRADE or the other so I no longer remember the name ?
Bradco said:
ok I understand, little question about SP flash tool to make a full format you used which option DOWNLOAD ONLY / FIRMWARE UPGRADE or the other so I no longer remember the name ?
Click to expand...
Click to collapse
The other is format all + download and that may work for you. It was a while ago, when I went from Android 6 to 7 and I do not want to steer you in the wrong direction. From what I remember I used the format tab on SP Flashtool and pretty much formatted everything. Yesterday I tried for the 0814 OTA by using the clean option in Super SU (which basically uninstalls it ) and flashing the stock recovery for the existing ROM version using SP Flashtool. The OTA would not complete because of a sector mismatch so I flashed TWRP recovery again, which actually rebooted pretty fast then reinstalled the Super SU zip using TWRP. If you want TWRP recovery maybe try it again without formatting anything and give the boot more time. I am not going to bother flashing the complete 0814 ROM until I pass on the phone to my wife because I don't want to go through the app and user credential reloads and fixing the IMEI's and WIFI mac. The Google backup to Drive feature is not available in settings - same for many who are on 7.1.1 even the "name brand" phones.
bluiis48 said:
The other is format all + download and that may work for you. It was a while ago, when I went from Android 6 to 7 and I do not want to steer you in the wrong direction. From what I remember I used the format tab on SP Flashtool and pretty much formatted everything. Yesterday I tried for the 0814 OTA by using the clean option in Super SU (which basically uninstalls it ) and flashing the stock recovery for the existing ROM version using SP Flashtool. The OTA would not complete because of a sector mismatch so I flashed TWRP recovery again, which actually rebooted pretty fast then reinstalled the Super SU zip using TWRP. If you want TWRP recovery maybe try it again without formatting anything and give the boot more time. I am not going to bother flashing the complete 0814 ROM until I pass on the phone to my wife because I don't want to go through the app and user credential reloads and fixing the IMEI's and WIFI mac. The Google backup to Drive feature is not available in settings - same for many who are on 7.1.1 even the "name brand" phones.
Click to expand...
Click to collapse
With each new installation of rom, I start all (long but more stable).
For the problem of wifi and IMEI for having 5 elephone I have never encountered this problem even with version 0814. For the recovery custom it is weird that the start of the phone is long. this afternoon I tried to make a port of TWRP with base on TWRP 3.1 (compatible android 7 for p9000) with stock recovery, but I'm not sure it is functional. i'm not understand everything .
I just saw that the thread be updated, even tuto with the rom s7_4g_20170517133805_v2.3.zip I'm not sure that it works.
I followed the tutorial on first page and it works for me but I am using the 0517 stock rom. I don't think you need to Port TWRP because it does work with the one I posted. If you have time try starting with the 0517 and follow steps on page one. If that works you can try the same with 0814.
IMPORTANT THOUGHT do you have OEM unlocking (allow the bootloader to be unlocked) enabled in developer options ? This is the first phone where I found that to be necessary.
bluiis48 said:
I followed the tutorial on first page and it works for me but I am using the 0517 stock rom. I don't think you need to Port TWRP because it does work with the one I posted. If you have time try starting with the 0517 and follow steps on page one. If that works you can try the same with 0814.
IMPORTANT THOUGHT do you have OEM unlocking (allow the bootloader to be unlocked) enabled in developer options ? This is the first phone where I found that to be necessary.
Click to expand...
Click to collapse
I just look into the options for developers and OEM unlocking is turned off. do you think I'll have to activate it ?
Ps : I never needed it
EDIT 1 :
at this stage :
SP_Flash_Tool for Stock Rom:
* select Download Agent: SP_Flash_Tool_v5.1720_Win \ MTK_AllInOne_DA.bin
* select Scatter-Loading-File: Stock Rom \ MT6797_Android_scatter.txt
* Firmware Upgrade
Before doing firmaware upgrade in what version of rom do I have to?

[ROM][Ubuntu Touch][UNOFFICIAL] SM-T510/T515 - Samsung Galaxy Tab A 10.1 (2019)

I have been developing Ubuntu Touch for the Tab A 10.1 2019
This ROM has been tested on both SM-T510 (WiFi version) and SM-T515 (WiFi + LTE)
Any developers reading this and has the device with them and are interested in the project may contact me :
@midhunvnadh on Telegram
Not Working :-
Bluetooth
Audio
Anbox (Android Emulator)
MTP
I am trying to fix these.
Download Files
Download the Halium arm32 GSI file : from Here
(Optional) Download SamsungUSBTethering zip : from here
Ubports Patched Kernel : from here
Get all the above files copied to your External SD Card
Installation
WARNING : I am NOT responsible for any damage caused to your device
If you are following this post, please takeup full responsibility of your device.
Noobs at flashing ROM's can click here: https://telegra.ph/Installing-Ubuntu-Touch-T510T515-08-22
Thanks to @ahamshubham for making this
1.0 Flash STOCK Android 9.0 Pie on your device and install TWRP.
(Because not tested on STOCK Android 10.0)
1.5 Boot into TWRP and Wipe all except external SD. REBOOT to recovery.
2.0 On TWRP : Flash the Lineage 16.0 build. DON'T REBOOT.
3.0 On TWRP : Goto Install -> Install Image -> (Flash halium-boot.img) DON'T REBOOT.
4.0 On TWRP : Goto Install -> (Flash ubports_GSI_installer_V1-arm32.zip).
5.0 (Optional) : Goto Install -> (Flash samsung-usb-tethering.zip)
5.1 Reboot.
(Incase : unable to boot ? , boot into TWRP -> reboot -> system)
samsung-usb-tethering.zip is used to get an SSH console from device to PC. Credits to @erfanoabdi
Please report all the errors you encounter here.
Sources
Kernel : https://github.com/midhunvnadh/android_kernel_samsung_gta3xlwifi
Device Tree : https://github.com/midhunvnadh/device_samsung_gta3xlwifi
GSI arm32 : https://github.com/midhunvnadh/android_device_halium_ubport
The Device tree is a dummy tree with kernel sources linked. Which serves a purpose of compiling halium-boot.img. For more info contact me.
Donations are always appreciated : Just click here
Reserved
Reserved
Pick me! Pick me!
I will gladly take that on. Just got down installing lineage ,17.1 with Kali Linux.. I will see what I can't get done tonight.
mikehunt723 said:
I will gladly take that on. Just got down installing lineage ,17.1 with Kali Linux.. I will see what I can't get done tonight.
Click to expand...
Click to collapse
Hello, you gave me a first reply... !!!
This is my real thread post on ROM's.
I didn't understand what you meant by "Pick me" and "I will gladly take that on. "
Are you looking forward to make contribution to this project ?
Bruh this is amazing work, keep it going!
This looks like an interesting project, none of the download links work for me
nubianprince said:
This looks like an interesting project, none of the download links work for me
Click to expand...
Click to collapse
It is a direct link. It works for me ?
Can you support Galaxy Tab A6?
Mohamed677 said:
Can you support Galaxy Tab A6?
Click to expand...
Click to collapse
I can try if you can give me a device.
Mohamed677 said:
Can you support Galaxy Tab A6?
Click to expand...
Click to collapse
The sm-t580? I tryed like a month ago, and i got the boot.img file to compile for halium7, but not the system image, and los14 is broken so it cant work anyway, and, when i tryed to compile using halium9, i had missing libs.
I also tryed postmarketOS, and it did not boot
(Well, if it did, and i think it did because it didnt reboot into download mode automatically), and screen and usb wasnt working
MIDHUN.V.NADH said:
1.0 Flash STOCK Android 9.0 Pie on your device and install TWRP.
Click to expand...
Click to collapse
Wow. This is exciting news. Really have been longing for a non-android based OS for a long time. Thanks a ton. Will surely donate when I get a job(currently unemployed due to covid):good:
What do you mean by installing stock? You are going to installing LOS 16.0 so can that not be the starting point? Do I have to go back and install stock using Odin and do the whole process again?
aveemashfaq said:
Wow. This is exciting news. Really have been longing for a non-android based OS for a long time. Thanks a ton. Will surely donate when I get a job(currently unemployed due to covid):good:
What do you mean by installing stock? You are going to installing LOS 16.0 so can that not be the starting point? Do I have to go back and install stock using Odin and do the whole process again?
Click to expand...
Click to collapse
Yes, you have to do all those steps.
Why I am asking everyone to install Stock 9.0 is because :
1. On Samsung Exynos Devices developers have an hard time developing Ubuntu Touch.
2. There are changes in partition structure going on from upgrade to Stock 9.0 to 10.0
3. The kernel source of stock Android 9.0 is VERY different from 10.0
4. I wasn't able to get logs from Stock 10.0 due to the partition changes mentioned on (2)
5. Halium 9.0 (Build Engine for Touch) highly recommends Android 9.0/Lineage 16.0 as a base to install upon.
6. Moreover I haven't tested if it boots on stock 10.0 because of (2), (3), (5) and I am currently fixing the bugs.
Please try to out on AOSP 10.0 and let me know if it work
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Geek_Ceará said:
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Click to expand...
Click to collapse
Hi !, Were you able to boot into the OS ?
I haven't faced that issue can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32.
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Geek_Ceará said:
Hello! I installed it on my Galaxy Tab A 2019 T510, however, a strange problem happens. Suddenly the screen goes dark and I can't do anything, even pressing the power button. A little while later the screen goes black, forcing me to use the Volume - / Power keys to restart. Anyone else going through this? I have another question: the installation file (ubports gsi) says arm32. Is the architecture of this tablet arm34 or arm64?
Click to expand...
Click to collapse
Hi ! Thank you for your reply.
Were you able to boot into the OS ?
I haven't faced that issue. Can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32 eventhough some devices with the same SoC has full arm64.
I am trying to port arm64 vendor into the device but I think arm32 will be better because the device only has 2GB RAM (Atleast on my device)
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Worked!!
I was looking forward to run Ubuntu Touch on my Samsung Galaxy Tab A (SM-T515NZKDINU). I contacted MIDHUN.V.NADH, he helped me through the process and we got Ubuntu Touch running on my device. I would like to thank him for his help and his post. I, however, felt that I could not follow the instructions in the post very easily. Maybe, this is because I am doing something like this for the first time. So, I compiled a list of instructions to follow. I will send him this list of instructions and post them here too. I feel they will be helpful for people looking to run Ubuntu Touch on the same device.
MIDHUN.V.NADH said:
Hi !, Were you able to boot into the OS ?
I haven't faced that issue can you elaborate ?
The Tablet has an arm64 kernel but the vendor and system are both arm32.
I had to make the arm32 GSI for ubuntu touch to run on this tablet.
The GSI will also work for devices with the arm32 vendor and system.
Click to expand...
Click to collapse
Yes. I managed to initialize, however, this problem happens to me. I uninstalled Ubuntu and returned to android. Someday, when I have something stable, I test it again.
And about the processor architecture, I understand your explanation. Thank you!
Just adding instructions on how I did it on my device
My device details:
Device Model Number: SM-T515 (NZKDINU)
Linux Kernel Version: 4.4.111-17420370
Instructions for SM-T515:
1) Download these files using the links given in the post I am commenting on:
a) Halium arm32 GSI file
b) Ubports Patched Kernel
c) (Optional) SamsungUSBTethering zip
2) Copy all the above files to your External SD Card and insert this SD card in the device (tablet)
3) Flash STOCK Android 9.0 Pie on your device (tablet) and install TWRP:
a) For installing TWRP, use the following post: https://forum.xda-developers.com/ga...very-twrp-3-3-1-2019-galaxy-tab-10-1-t3934805. The instructions for installing TWRP as given in this post are:
i) Unlock bootloader (See the end of my comment)
ii) Hold Vol Up & Vol Down buttons during restart to enter Download mode
iii) Install TWRP to AP with Odin
iv) Hold Power & Vol Up buttons during restart to enter TWRP recovery
v) On TWRP: Swipe to allow modifications
vi) On TWRP: Wipe -> Advanced Wipe -> Select all except SD card
vii) On TWRP: Reboot -> Recovery
4) On TWRP: Go to Install -> Install Image -> (Flash halium-boot.img. Partition to flash image is BOOT). DON'T REBOOT. PRESS BACK.
5) On TWRP: Go to Install -> (Flash ubports_GSI_installer_V1-arm32.zip. Don't check any check boxes)
6) (Optional) On TWRP: Goto Install -> (Flash samsung-usb-tethering.zip)
7) Reboot
8) Ubuntu Touch will open. The password is: phablet
Unlocking Bootloader (Check this post: https://www.getdroidtips.com/oem-unlocking/):
1) Enable Developer Mode in Device Settings
2) Enable OEM Unlocking Option in Developer options after connecting to WiFi and setting the year in the phone to the year 2019
3) Get into Device Unlock Mode: Press (Volume Up Key + Volume Down Key + Insert USB Cable in the phone) while restarting the phone
4) Unlock bootloader. (Very Important!!) DON'T LET THE DEVICE BOOT INTO THE ANDROID OS AFTER UNLOCKING DEVICE BOOTLOADER
MIDHUN.V.NADH said:
Yes, you have to do all those steps.
Why I am asking everyone to install Stock 9.0 is because :
1. On Samsung Exynos Devices developers have an hard time developing Ubuntu Touch.
2. There are changes in partition structure going on from upgrade to Stock 9.0 to 10.0
3. The kernel source of stock Android 9.0 is VERY different from 10.0
4. I wasn't able to get logs from Stock 10.0 due to the partition changes mentioned on (2)
5. Halium 9.0 (Build Engine for Touch) highly recommends Android 9.0/Lineage 16.0 as a base to install upon.
6. Moreover I haven't tested if it boots on stock 10.0 because of (2), (3), (5) and I am currently fixing the bugs.
Please try to out on AOSP 10.0 and let me know if it work
Click to expand...
Click to collapse
Hi, I just tried it out on my device. I had stock 9.0 over which I had flashed Lineage OS 17.1(based on Android 10). Over that, I flashed LOS 16, halium-boot, ubports-gsi and usb tethering. Worked for me.
I have to say, I have a pinephone and it seems that ubports on Samsung tab is faster than on pinephone.
antoine62 said:
The sm-t580? I tryed like a month ago, and i got the boot.img file to compile for halium7, but not the system image, and los15 is broken so it cant work anyway, and, when i tryed to compile using halium9, i had missing libs.
I also tryed postmarketOS, and it did not boot
(Well, if it did, and i think it did because it didnt reboot into download mode automatically), and screen and usb wasnt working
Click to expand...
Click to collapse
Did you ever get this to work/ any tips for trying because I really want this to work (I am trying at the moment).

Galaxy SII custom firmware / root in 2021

I have a Samsung Galaxy SII ( GT-I9100 ) which was retrieved from a dumpster. I love the removable battery. I would like to know what custom firmware you recommend for it. I could also use any tutorials you recommend to flash it. I have looked at some but I wonder which is best for my requirements:
* The latest Android release is unimportant (I can live with Android 5.0 to be honest)
* Having Google bundled apps is unimportant (all Google apps will be uninstalled, if present).
* I want the good reliability / stability and no alpha or beta releases.
I am only interested in root access & reliable firmware with which I can install open-source apps from f-droid.org. Thanks for any suggestions.
comfortable said:
I have a Samsung Galaxy SII ( GT-I9100 ) which was retrieved from a dumpster. I love the removable battery. I would like to know what custom firmware you recommend for it. I could also use any tutorials you recommend to flash it. I have looked at some but I wonder which is best for my requirements:
* The latest Android release is unimportant (I can live with Android 5.0 to be honest)
* Having Google bundled apps is unimportant (all Google apps will be uninstalled, if present).
* I want the good reliability / stability and no alpha or beta releases.
I am only interested in root access & reliable firmware with which I can install open-source apps from f-droid.org. Thanks for any suggestions.
Click to expand...
Click to collapse
Lineage OS 17.1 Android 10, that works pretty well.
[ROM][UNOFFICIAL][10.0.0][r41][I9100] LineageOS 17.1
/* ** Your warranty is now void. ** ** 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...
forum.xda-developers.com
Another opportunity for you would be replicant. It is based on LineageOS, but tries to run on free-software only and a mainlined kernel. They don't ship with any google apps and and offer Android 6 (currently upgrading to Android 9 for all of their devices.
You will need modified TWRP to flash this and do not ask me why.
You need odin 3.07 as it is the last version of odin that supports S II.
Odin 3.07 https://odindownloader.com/download/odin3-v3-07
Update offically to 4.1.2, Delete All Samsung and Google accounts, go to settings and phone information, click 7 times build number(Just randomly click All numbers 7x and you will eventually done), go back to settings, click on developer Options, and toggle BOTH oem unlock and USB debugging.
Then follow below steps
Pit: i9100-LOS-16.0-Emulated-Storage.pit
PDA: i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
1. Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
2. Start ODIN 3.07 on your PC.
3. Connect your phone via USB to your PC.
4. Press volume up on your phone, ODIN should detect your phone.
5. In ODIN Options tab:
Auto Reboot : unchecked
Re-Partition: checked
PIT : i9100-LOS-16.0-Emulated-Storage.pit
PDA : i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
6. Press Start.
7. After succesful flash, reboot phone into Recovery:
- Press Volume up + Power/Standby + Home and hold for 10 seconds.
The phone shuts down.
- Repeat Press Volume up + Power/Standby + Home and hold for 10 seconds
Phone boots in recovery TWRP 3.3.1-1.
8. Swipe to Allow Modifications
9. In TWRP 3.3.1-1 you need to format partions
- Wipe -> Format Data -> Type [yes]
- Wipe -> Advanced Wipe -> Select:
* Davik / ART Cache
* Cache
* System
* Non-emulated Storage
10. Flash the modified TWRP here https://androidfilehost.com/?fid=8889791610682894303 by Transferring TWRP.img to phone via USB cable≧Flash≧select image≧this image
11.Go to home and Reboot≧recovery
12. In new TWRP flash this http://ww.androidfilehost.com/?fid=17248734326145712187 and then stable magisk and reboot.
well gapps also not builded in in lineageos.
Thanks for all the responses. All the choices sound like they will get the job done. I'm currently deciding which one to try first.
jjgvv said:
12. In new TWRP flash this http://ww.androidfilehost.com/?fid=17248734326145712187 and then stable magisk and reboot.
Click to expand...
Click to collapse
Much appreciated. I was preparing all the files you mentioned but got a broken link on this one. Could you re-check please?
comfortable said:
Thanks for all the responses. All the choices sound like they will get the job done. I'm currently deciding which one to try first.
Much appreciated. I was preparing all the files you mentioned but got a broken link on this one. Could you re-check please?
Click to expand...
Click to collapse
lineage-17.1-20210107-UNOFFICIAL-i9100.zip | by rINanDO for Galaxy S2
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
I downloaded both the Replicant files and the Lineage files. I had a look at replicant and the set-up seems to be a lot more invovled, so I have decided to do Lineage first. The firmware download size with Replicant is much less bloated, which appeals to me, especially for older hardware. So I will probably try that eventually.
jjgvv said:
go back to settings, click on developer Options, and toggle BOTH oem unlock and USB debugging.
Then follow below steps
Click to expand...
Click to collapse
I gave it a quick attempt yesterday. In Developer Options I found "USB debugging" but there was no "OEM Unlock" setting anywhere. In any case, I proceeded:
Odin says:
All threads completed. (succeed 0 / failed 0)
I'm led to believe I need to get the Samsung drivers so I will do that later today. I have read that installing Kies installs the drivers so maybe that's the best route.
comfortable said:
I downloaded both the Replicant files and the Lineage files. I had a look at replicant and the set-up seems to be a lot more invovled, so I have decided to do Lineage first. The firmware download size with Replicant is much less bloated, which appeals to me, especially for older hardware. So I will probably try that eventually.
I gave it a quick attempt yesterday. In Developer Options I found "USB debugging" but there was no "OEM Unlock" setting anywhere. In any case, I proceeded:
Odin says:
All threads completed. (succeed 0 / failed 0)
I'm led to believe I need to get the Samsung drivers so I will do that later today. I have read that installing Kies installs the drivers so maybe that's the best route.
Click to expand...
Click to collapse
you are not carrier locked or sth?
comfortable said:
I downloaded both the Replicant files and the Lineage files. I had a look at replicant and the set-up seems to be a lot more invovled, so I have decided to do Lineage first. The firmware download size with Replicant is much less bloated, which appeals to me, especially for older hardware. So I will probably try that eventually.
I gave it a quick attempt yesterday. In Developer Options I found "USB debugging" but there was no "OEM Unlock" setting anywhere. In any case, I proceeded:
Odin says:
All threads completed. (succeed 0 / failed 0)
I'm led to believe I need to get the Samsung drivers so I will do that later today. I have read that installing Kies installs the drivers so maybe that's the best route.
Click to expand...
Click to collapse
I will give you a alternative way. first, update to 4.1.2
then, install rashr https://m.apkpure.com/root-rashr-flash-tool/de.mkrtchyan.recoverytools but do not open it . you need to install it first because Otherwise installation will be blocked by kingroot.
then you guessed that root by kingroot https://kingroot.en.uptodown.com/android
Tutorial https://www.google.com/url?sa=t&sou...BMAF6BAgIEAE&usg=AOvVaw3cA8ZHKR3yqQaY6NvHnO4I
Then you can open rashr. download this TWRP as rashr only flashes.img files. https://www.androidfilehost.com/?fid=8889791610682894303
select RECOVERY FROM STORAGE and select the .img TWRP.
it will ask you to reboot recovery .
in recovery you wipe All in advanced wipe except microsd and USB otg. Then transfer the .zip rom to phone by dumping it into internal storage using a computer. Flash it by flash button and selecting the zip, but do not Install gapps. select Reboot and Pay attention here: Do not install TWRP app! Uncheck All prompt to install TWRP app and reboot system.
jjgvv said:
You will need modified TWRP to flash this and do not ask me why.
You need odin 3.07 as it is the last version of odin that supports S II.
Odin 3.07 https://odindownloader.com/download/odin3-v3-07
Update offically to 4.1.2, Delete All Samsung and Google accounts, go to settings and phone information, click 7 times build number(Just randomly click All numbers 7x and you will eventually done), go back to settings, click on developer Options, and toggle BOTH oem unlock and USB debugging.
Then follow below steps
Pit: i9100-LOS-16.0-Emulated-Storage.pit
PDA: i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
1. Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
2. Start ODIN 3.07 on your PC.
3. Connect your phone via USB to your PC.
4. Press volume up on your phone, ODIN should detect your phone.
5. In ODIN Options tab:
Auto Reboot : unchecked
Re-Partition: checked
PIT : i9100-LOS-16.0-Emulated-Storage.pit
PDA : i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
6. Press Start.
7. After succesful flash, reboot phone into Recovery:
- Press Volume up + Power/Standby + Home and hold for 10 seconds.
The phone shuts down.
- Repeat Press Volume up + Power/Standby + Home and hold for 10 seconds
Phone boots in recovery TWRP 3.3.1-1.
8. Swipe to Allow Modifications
9. In TWRP 3.3.1-1 you need to format partions
- Wipe -> Format Data -> Type [yes]
- Wipe -> Advanced Wipe -> Select:
* Davik / ART Cache
* Cache
* System
* Non-emulated Storage
10. Flash the modified TWRP here https://androidfilehost.com/?fid=8889791610682894303 by Transferring TWRP.img to phone via USB cable≧Flash≧select image≧this image
11.Go to home and Reboot≧recovery
12. In new TWRP flash this http://ww.androidfilehost.com/?fid=17248734326145712187 and then stable magisk and reboot.
Click to expand...
Click to collapse
↑quoted from Lineage 17.1 Thread and modified
jjgvv said:
you are not carrier locked or sth?
Click to expand...
Click to collapse
Not sure. I haven't put a SIM card in this thing at all. Does having no OEM Unlock option mean that it's locked to a single carrier? I literally found this phone in the dumpster and I will be using it on wi-fi (occasionally) and offline (mostly).
Re: Kingroot
Not keen on this at all since I have read it is malware.
comfortable said:
Not sure. I haven't put a SIM card in this thing at all. Does having no OEM Unlock option mean that it's locked to a single carrier? I literally found this phone in the dumpster and I will be using it on wi-fi (occasionally) and offline (mostly).
Re: Kingroot
Not keen on this at all since I have read it is malware.
Click to expand...
Click to collapse
try other 1 click root apps then
model number is I9100 or What I mean? or I9100g? it is different
jjgvv said:
model number is I9100 or What I mean? or I9100g? it is different
Click to expand...
Click to collapse
GT-I9100. There is no G
I will try with Samsung drivers later tonight & see if the first method works. I am not keen on many of those 'easy' rooting apps, but I appreciate the help. I have big trust issues with them.
glad to see that, also one click root apps can do whatever they want like installing a malicious app without permission and hack device, though I bite the bullet and tried on my xperia c.
very reasonable doubt
Lineage is installed. However, it is still unrooted. Does anyone have any tips for getting this rooted?
=======
* I have tried the Magisk app and patching "boot.img" several times. That resulted in an error: Unsupported / invalid file, or words to that effect.
* I have tried downloading the Magisk zip file using the Magisk app. I tried flashing that freshly-downloaded Magisk zip file in TWRP. No go. Error: 1
* I have tried downloading various Magisk zip files off Github and flashing in TWRP. No go. Error: 1
* I have tried the official TWRP app that seemed to insist on downloading an official I9100 TWRP file. I flashed this TWRP file using my existing TWRP Recovery. After that, I couldn't get into Recovery at all (using the 3 finger salute). It would always just boot LineageOS instead.
=======
So I decided to start-over. I started up Odin again and started from scratch. I have spent most of the day dicking-around here. Now I am back to having LineageOS installed without root again. I tried Magisk again. No go. Same error 1. Still no root.
I can't recall a time where installing custom firmware and rooting was 100% smooth. Even when flashing in Odin all the checkboxes were greyed-out, so I couldn't even select an option if I tried. I don't know why.
Anyway, any tips to get root are greatly appreciated! SuperSU?:
comfortable said:
Lineage is installed. However, it is still unrooted. Does anyone have any tips for getting this rooted?
=======
* I have tried the Magisk app and patching "boot.img" several times. That resulted in an error: Unsupported / invalid file, or words to that effect.
* I have tried downloading the Magisk zip file using the Magisk app. I tried flashing that freshly-downloaded Magisk zip file in TWRP. No go. Error: 1
* I have tried downloading various Magisk zip files off Github and flashing in TWRP. No go. Error: 1
* I have tried the official TWRP app that seemed to insist on downloading an official I9100 TWRP file. I flashed this TWRP file using my existing TWRP Recovery. After that, I couldn't get into Recovery at all (using the 3 finger salute). It would always just boot LineageOS instead.
=======
So I decided to start-over. I started up Odin again and started from scratch. I have spent most of the day dicking-around here. Now I am back to having LineageOS installed without root again. I tried Magisk again. No go. Same error 1. Still no root.
I can't recall a time where installing custom firmware and rooting was 100% smooth. Even when flashing in Odin all the checkboxes were greyed-out, so I couldn't even select an option if I tried. I don't know why.
Anyway, any tips to get root are greatly appreciated! SuperSU?:
Click to expand...
Click to collapse
You could either try heimdall (alternativ to odin, if odin does not work for you: https://www.glassechidna.com.au/heimdall/
or even try CF-Autoroot: https://desktop.firmware.mobi/

[RECOVERY][UNOFFICIAL][SM-T820][SM-T825][2022-12-11] TWRP 3.7.0_9.0 for Galaxy Tab S3

Code:
/*
* Your warranty will be VOID after installing a custom ROM.
*
* Get notified yourself that 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 ROM
* 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.
*/
# Team Win Recovery Project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
You can find the source code for TWRP at github.com/teamwin/android_bootable_recovery/
# Features
Flashing a ROM
Factory reset
Erasing the partitions including system, data, cache, internal storage
Backup and restore
Supports F2FS formatting
USB ADB/MTP/OTG
# Downloads
Galaxy Tab S3 LTE (gts3llte, SM-T825)
Galaxy Tab S3 WiFi (gts3lwifi, SM-T820)
# How to install
You have to unlock your bootloader in advance. Check "OEM Unlock" in the device settings.
## Via Odin/Heimdall
Download "twrp-*-gts3l*.img.tar"from the given link.
Check the file name to yours, gts3llte or gts3lwifi.
Enter the download mode by pressing the volume-down + home + power buttons at the same time.
Open Odin or Heimdall and set the AP slot as the downloaded recovery file.
Flash.
Reboot to the recovery by pressing the volume-up + home + power buttons at the same time.
Done.
## Via rooted ADB
This is for those who can get the rooted ADB shell, by the custom ROM or previous TWRP, etc.
Download "twrp-*-gts3l*.img"from the given link.
Check the file name to yours, gts3llte or gts3lwifi.
In this guide, assume that the file is named "twrp.img".
Copy the recovery file into somewhere the device can access.
Enter the ADB shell with rooted mode.
In the shell, go to the directory that the recovery file copied.
Enter the command, "dd if=twrp.img of=/dev/block/bootdevice/by-name/recovery"
Reboot to the recovery by pressing the volume-up + home + power buttons at the same time.
Done.
# Notes
It may slow until formatting data partition when you are from the stock ROM. It tries to mount data partition using ext4 filesystem but it fails repeatedly.
# Sources
Device Tree
gts3llte: https://github.com/awesometic/android_device_samsung_gts3llte-twrp
gts3lwifi: https://github.com/awesometic/android_device_samsung_gts3lwifi-twrp
Kernel: https://github.com/awesometic/android_kernel_samsung_msm8996
# Buy me a coffee
If you like my efforts or would like to support me, please don't hesitate to buy me a cup of coffee.
https://www.paypal.com/paypalme/awesometic
# Credits / Special thanks to
Android Open Source Project
TeamWin Team
LineageOS Team
OmniROM Team
TWRP Minimal Manifests
@Valera1978 for his amazing previous work including his MSM8996 kernel
@ashyx for his amazing previous work on his TWRP
@EonOfBlack for confirming its working on SM-T820
## Changelogs
2021. 11. 30
Updated TWRP version to 3.6.0
Started to use my custom kernel
Set the kernel to "awesometic-kernel-v0.3"
Merged CAF tag LA.UM.7.6.r1-07800-89xx.0
Now it supports F2FS file system
Improved performance
And some more but not related to the recovery
2021. 7. 9
Initial release
reserved
Nice to see TWRP for the sm820...
Cannot really test since my tabs3 is needed as a daily, but that might just change soon...
Flashed with an old TWRP. It works. Can't test with stock rom either... Strange bug with the shell:
Code:
libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfffffffffffffff0 in tid 635 (ls), pid 635 (ls) Segmentation fault
It happens only when trying to access /external_sd/ (ls, find, etc.) no problem at / or /sdcard/ /external_sd/ is accessible with the internal file browser. Portrait orientation? Why not.
I have flashed with tweaked ROM https://forum.xda-developers.com/t/rom-sm-t820-tweaked-rom-sm-t820-tweaked.3659433/ via adb shell. It work right
Awesometic said:
Code:
/*
* Your warranty will be VOID after installing a custom ROM.
*
* Get notified yourself that 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 ROM
* 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.
*/
# Team Win Recovery Project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
You can find the source code for TWRP at github.com/teamwin/android_bootable_recovery/
# Features
Flashing a ROM
Factory reset
Erasing the partitions including system, data, cache, internal storage
USB ADB/MTP/OTG
## Prepared but not tested
Backup and restore
Hardware decryption
# Downloads
Galaxy Tab S3 LTE (gts3llte, SM-T825)
Galaxy Tab S3 WiFi (gts3lwifi, SM-T820)
# How to install
You have to unlock your bootloader in advance. Check "OEM Unlock" in the device settings.
## Via Odin/Heimdall
Download "twrp-3.5.2_9-0-gts3l*.img.tar"from the given link.
Check the file name to yours, gts3llte or gts3lwifi.
Enter the download mode by pressing the volume-down + home + power buttons at the same time.
Open Odin or Heimdall and set the AP slot as the downloaded recovery file.
Flash.
Reboot to the recovery by pressing the volume-up + home + power buttons at the same time.
Done.
## Via rooted ADB
This is for those who can get the rooted ADB shell, by the custom ROM or previous TWRP, etc.
Download "twrp-3.5.2_9-0-gts3l*.img"from the given link.
Check the file name to yours, gts3llte or gts3lwifi.
In this guide, assume that the file is named "twrp.img".
Copy the recovery file into somewhere the device can access.
Enter the ADB shell with rooted mode.
In the shell, go to the directory that the recovery file copied.
Enter the command, "dd if=twrp.img of=/dev/block/bootdevice/by-name/recovery"
Reboot to the recovery by pressing the volume-up + home + power buttons at the same time.
Done.
# Notes [2021. 7. 9]
I started roughly, so the recovery has some files for dealing with hardware encrypted file system, but I couldn't test yet because I need the stock ROM to test but I should keep the workflow with my LineageOS. If anyone can test this then please let me know it works or not.
# Sources
Device Tree
gts3llte: https://github.com/awesometic/android_device_samsung_gts3llte-twrp
gts3lwifi: https://github.com/awesometic/android_device_samsung_gts3lwifi-twrp
Kernel: https://github.com/awesometic/android_kernel_samsung_msm8996
# Buy me a coffee
If you like my efforts or would like to support me, please don't hesitate to buy me a cup of coffee.
https://www.paypal.com/paypalme/awesometic
# Credits / Special thanks to
Android Open Source Project
TeamWin Team
LineageOS Team
OmniROM Team
TWRP Minimal Manifests
@Valera1978 for his amazing previous work including his MSM8996 kernel
@ashyx for his amazing previous work on his TWRP
@EonOfBlack for confirming its working on SM-T820
Click to expand...
Click to collapse
I would like to help to add dualboot for sm-t820, is there some project in this direction ?
Thanks, Good job!!
samsuffit said:
Flashed with an old TWRP. It works. Can't test with stock rom either... Strange bug with the shell:
Code:
libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfffffffffffffff0 in tid 635 (ls), pid 635 (ls) Segmentation fault
It happens only when trying to access /external_sd/ (ls, find, etc.) no problem at / or /sdcard/ /external_sd/ is accessible with the internal file browser. Portrait orientation? Why not.
Click to expand...
Click to collapse
Actually, on my side, I have no issue when accessing the SD card, /external_sd. I'm usually putting a file into that directory through ADB. Sorry, don't know why that happens..
If there's no problem when you use another TWRP, can you tell me which one?
XolYnrac said:
I would like to help to add dualboot for sm-t820, is there some project in this direction ?
Thanks, Good job!!
Click to expand...
Click to collapse
There's no plan for something related to the dual-boot.
Awesometic said:
Actually, on my side, I have no issue when accessing the SD card, /external_sd. I'm usually putting a file into that directory through ADB. Sorry, don't know why that happens..
If there's no problem when you use another TWRP, can you tell me which one?
Click to expand...
Click to collapse
I tried again, before I messed it up https://forum.xda-developers.com/t/rom-sm-t820-tweaked-rom-sm-t820-tweaked.3659433/post-85316477 and had the same error. Before I was using TWRP 3.2.1-1 and I never had any error with adb shell. The error wasn't with adb push, but adb shell.
I'm a bit tired of this damned tablet, I don't know, it was a bit expensive for a Digital Photo Frame.
---
Interesting. So, I succesfully "unbrick" this doomed tablet with the method of the seven days, then I flashed your TWRP with Heimdall, with the option '--no-reboot' and pressed Home/Vol+/Power to reboot immediately in recovery. The splash screen appear and nothing. I flashed TWRP 3.2.1-1 wich can be find in this forum, reboot in recovery, I had this new red message "RECOVERY IS NOT SEANANDROID ENFORCED" and... it worked. Format Data, wipe everything, flash Lineage, Magisk, as usual, reboot in recovery. Inside TWRP 3.2.1-1 I flashed your TWRP 3.5.2_9-0 and... it worked!
From Stock Rom:
- Flash with Heimdall/Odin -> NOT OK
- Flash with TWRP -> OK
Still, I have the error.
Code:
[email protected] $ adb shell
gts3lwifi:/ # ls /external_sd/
libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfffffffffffffff0 in tid 4616 (ls), pid 4616 (ls)
Segmentation fault
samsuffit said:
I tried again, before I messed it up https://forum.xda-developers.com/t/rom-sm-t820-tweaked-rom-sm-t820-tweaked.3659433/post-85316477 and had the same error. Before I was using TWRP 3.2.1-1 and I never had any error with adb shell. The error wasn't with adb push, but adb shell.
I'm a bit tired of this damned tablet, I don't know, it was a bit expensive for a Digital Photo Frame.
---
Interesting. So, I succesfully "unbrick" this doomed tablet with the method of the seven days, then I flashed your TWRP with Heimdall, with the option '--no-reboot' and pressed Home/Vol+/Power to reboot immediately in recovery. The splash screen appear and nothing. I flashed TWRP 3.2.1-1 wich can be find in this forum, reboot in recovery, I had this new red message "RECOVERY IS NOT SEANANDROID ENFORCED" and... it worked. Format Data, wipe everything, flash Lineage, Magisk, as usual, reboot in recovery. Inside TWRP 3.2.1-1 I flashed your TWRP 3.5.2_9-0 and... it worked!
From Stock Rom:
- Flash with Heimdall/Odin -> NOT OK
- Flash with TWRP -> OK
Still, I have the error.
Code:
[email protected] $ adb shell
gts3lwifi:/ # ls /external_sd/
libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xfffffffffffffff0 in tid 4616 (ls), pid 4616 (ls)
Segmentation fault
Click to expand...
Click to collapse
I haven't faced that issue so far. Actually I use only one kind of SD card so probably I couldn't find that issue.
Could you attach the logcat when the error occurs?
Awesometic said:
I haven't faced that issue so far. Actually I use only one kind of SD card so probably I couldn't find that issue.
Could you attach the logcat when the error occurs?
Click to expand...
Click to collapse
Unfortunately there isn't logcat in recovery and the recovery.log dump doesn't show anything. /external_sd is mounted correctly, that's why I can access it with the internal file browser or choose it to pick up a file to flash. kernel.log (dmesg) doesn't show anything either. The problem is with the shell, busybox. I can't help you more, I'll think to an other way to find where's the error come from.
Reading the logs, I've found where the date and time are, for my other problem in the other thread.
Code:
I:Created '/persist' folder.
I:TWFunc::Fixup_Time: Pre-fix date and time: 2017-01-01--09-56-37
I:TWFunc::Fixup_Time: Setting time offset from file /sys/class/rtc/rtc0/since_epoch
I:TWFunc::Fixup_Time: will attempt to use the ats files now.
I:TWFunc::Fixup_Time: Setting time offset from file /persist/time/ats_2, offset 1592833667239
I:TWFunc::Fixup_Time: Date and time corrected: 2020-06-22--23-44-25
samsuffit said:
Unfortunately there isn't logcat in recovery and the recovery.log dump doesn't show anything. /external_sd is mounted correctly, that's why I can access it with the internal file browser or choose it to pick up a file to flash. kernel.log (dmesg) doesn't show anything either. The problem is with the shell, busybox. I can't help you more, I'll think to an other way to find where's the error come from.
Reading the logs, I've found where the date and time are, for my other problem in the other thread.
Code:
I:Created '/persist' folder.
I:TWFunc::Fixup_Time: Pre-fix date and time: 2017-01-01--09-56-37
I:TWFunc::Fixup_Time: Setting time offset from file /sys/class/rtc/rtc0/since_epoch
I:TWFunc::Fixup_Time: will attempt to use the ats files now.
I:TWFunc::Fixup_Time: Setting time offset from file /persist/time/ats_2, offset 1592833667239
I:TWFunc::Fixup_Time: Date and time corrected: 2020-06-22--23-44-25
Click to expand...
Click to collapse
Oh okay, thank you for the report anyway.
And the date/time issue, I didn't know that the time data is stored into the /persist directory.
twrp seems very stable, however incredibly slow to start. it takes 30 to 40 seconds ro get the twrp boot screen for me (t820) other thsn that it works well, I also tested this out by not flashing the kg/rmm state patch, as well the the encryption disabler and was able to boot back to this recovery without my data getting absolutely wiped. before with asyx twrp, twrp would delete all system files and data if those two zip files werent flashed, especially when updating the rom or dirty flashing. so far so good keep it up.
LedgendaryEpics said:
twrp seems very stable, however incredibly slow to start. it takes 30 to 40 seconds ro get the twrp boot screen for me (t820) other thsn that it works well, I also tested this out by not flashing the kg/rmm state patch, as well the the encryption disabler and was able to boot back to this recovery without my data getting absolutely wiped. before with asyx twrp, twrp would delete all system files and data if those two zip files werent flashed, especially when updating the rom or dirty flashing. so far so good keep it up.
Click to expand...
Click to collapse
Yeah I'm using my TWRP and I agree that there's a performance issue. Will look into this problem.
Awesometic said:
Yeah I'm using my TWRP and I agree that there's a performance issue. Will look into this problem.
Click to expand...
Click to collapse
I'd love to see camera first, cause that's what I need much more, than a fast booting TWRP.
That I'm using only once a month or less and if it needs 40"' or 5' to start doesn't bother me.
I have 2 questions. Do I need to install the patch, Tab3 oreo forced encryption disabler??
Second, do i need to uncheck auto reboot after install this twrp version?
hinghing1113 said:
I have 2 questions. Do I need to install the patch, Tab3 oreo forced encryption disabler??
Second, do i need to uncheck auto reboot after install this twrp version?
Click to expand...
Click to collapse
1. Well I never installed so it seems not necessary
2. If you mean Odin flashing the TWRP, surely.
Otherwise the old stock recovery gets revived when auto rebooting and not into TWRP directly.
Does this require root?
I can successfully get into TWRP and format Data but rebooting makes my T820 act as it were factory reset (boots up to setup wizard) and replaces TWRP with stock recovery. I'm not selecting read only mode when first opening TWRP. I'm not latest stock firmware
fulleden said:
Does this require root?
I can successfully get into TWRP and format Data but rebooting makes my T820 act as it were factory reset (boots up to setup wizard) and replaces TWRP with stock recovery. I'm not selecting read only mode when first opening TWRP. I'm not latest stock firmware
Click to expand...
Click to collapse
Hello.
Strange. Once you have installed TWRP recovery on your tablet then it should not be turned into the stock recovery again automatically. I believe.
Have you checked OEM unlock option in the Developer options menu? I don' know it is possible to enter the custom recovery without checking that option..
Awesometic said:
Hello.
Strange. Once you have installed TWRP recovery on your tablet then it should not be turned into the stock recovery again automatically. I believe.
Have you checked OEM unlock option in the Developer options menu? I don' know it is possible to enter the custom recovery without checking that option..
Click to expand...
Click to collapse
I agree. I didn't realize the stock recover could overwrite TWRP once you were able to boot into it. Yes, I did have the bootloader unlocked (by OEM unlock in Dev Options, not sure there's another way). I was using Odin to flash and even tried a few different versions. The tablet originally had the latest Oreo Rom. I tried downgrading it to an older Oreo and also tried a Nougant rom. I had to do a "Format Data", otherwise I would get a boot loop and it seems to me that this then forced a "factory reset" on the next restart where it would sit on the Samsung logo for a very long time. I tried several different angles. I could reboot from TWRP back into TWRP. I even tried flashing TWRP on top of TWRP. Every time I went to boot into Android, it would take forever while it was apparently performing a rebuild of something. I was trying to avoid root to avoid tripping Knox. My ultimate goal was to systemize an app using TWRP which I've done on several older Samsung tablets.
In the end, I flashed Magisk then everything worked on the first try. Booting into Android went quick and I still had TWRP. I tripped Knox but in the end I was able to get what I needed onto the tablet. All is fine now.
Thanks for your work on this TWRP recovery and for sticking around to help support it.

Categories

Resources