Database Develop

[ROM][AOSP][4.4/6.0/7.1] Unlegacy Android Project

The Unlegacy-Android Project​Introduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy-Android was born.
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs. As usual, 'espresso' goes for all non-3g versions, 'espresso3g' goes for all 3g versions.
Problems
- Occasional sound stuttering in some games
- No hwrotation (meaning the boot animation is landscape on p31xx). I don't consider this as a problem, as autorotation will take effect after bootup anyways... and most 7" tablets, like the Nexus 7 work this way as well.
- The 7.1 builds are experimental! Means: modem not working perfectly yet.
If you notice anything else, be sure to report it in this thread. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org
Always use the latest TWRP, to flash Android 7.x, you must use TWRP 3.0.3-0 or newer.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices. The aim of this project is to create a fast and stable ROM - although, one could use Xposed to add extra features.
As usual, feedback is appreciated
Want to support development? You can consider donating, I spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Tab 2
Contributors
Ziyan, Android-Andi
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Firmware Required: The latest bootloader for your device.
Version Information
Status: Beta
Current Stable Version: 4.4, 6.0
Created 2016-07-03
Last Updated 2017-10-22

GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
siealex said:
One more note. DO NOT set up your Google account until you grant all permissions, otherwise you will be stuck on the initial setup.
Click to expand...
Click to collapse
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.

Ziyan said:
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Click to expand...
Click to collapse
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?

Bastiary said:
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Click to expand...
Click to collapse
No, at least not yet. I think that the big thing for this will be 3.4 in the near future - I made some very good progress with it, aside from camera not working yet, there are only minor problems remaining

Thank you for everything , dear friend ! And for the support of the old device , and what you are doing and Andi for us ordinary users .
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?

Az-09 said:
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Click to expand...
Click to collapse
Before every new Android release, we devs get all sorts of questions like this. I'd like to say it once and for all: there's no such thing as 'we do not see' the next versions and whatnot. People are being negative for some reason, but we always try and succeed in the end... I'm sure that if you start reading past posts, you'll find a lot of people saying that we1l never see Lollipop or Marshmallow due to the device being too old, lol.

Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...

radz_ said:
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
Click to expand...
Click to collapse
check download tab section.

Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!

pickmod said:
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
Click to expand...
Click to collapse
Yes, that's correct.

Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"

Screeshots

Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
no need for this, it's aosp there isn't any custom features and everybody know how aosp looks

Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
Oh don't worry, I'm working extremely hard in the background almost since like a year... I know a lot about these devices (bought a P5100 specifically for testing 3G on the builds and kernels)
Feature list: well, this is AOSP, and I'd like to keep it this way. Imagine this like the stock ROM on the Nexus devices (with GApps flashed, of course).
Changelog: don't expect anything other than AOSP updates and hardware related fixes and updates - of course, I'm going to write a post each time I release an update, just like I do in the Galaxy Nexus thread however, it's unlikely that I'll add a changelog to the OP (I just don't see the usefulness in it).
Screenshots: will do, but then again, don't expect anything special. Stable and fast pure Android, that is AOSP. As a side note, it's Xposed compatible
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:

Thak you for your effort to keep tab 2 alive . Amazing work. Are RRO Layers compatible with this rom?

Ziyan said:
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Click to expand...
Click to collapse
Hi Ziyan,
I'm glad you mentioned this, as I thought that I was going insane this morning (or just slightly more insane than usual).
Just browsing the new "Unified" forum (to verify my subscriptions) and noticed that the "Dhollmen" threads could be clarified (just like the "Linaro" threads), for example ...
This thread: http://forum.xda-developers.com/showthread.php?t=2176563 could be titled: [KERNEL][P51xx][AOSP] Dhollmen Espresso
This thread: http://forum.xda-developers.com/showthread.php?t=2183830 could be titled: [KERNEL][P31xx][AOSP] Dhollmen Espresso
Just to avoid confusion (I freely admit that I am easily confused).
Thanks.

@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~

Android-Andi said:
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Click to expand...
Click to collapse
Hi Andi,
I only suggested renaming the existing "pair" of threads (they both exist in the Unified Forum) ... Just like the "pair" of Linaro threads (that also both exist in the Unified forum).
The download links in (all four) of the threads (mentioned above) link to unique builds on AFH (for both P31xx and P51xx devices) in this forum: http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Sorry for all the edits (I put the blame on OCD).
Thanks.

mentat said:
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Click to expand...
Click to collapse
Done; I guess this is it then. Like the XDA forum admin said, the best way to handle moving both threads is to move them both to this unified section, and close one of them (preferably the one with the less posts). While we could merge them into one thread, the posts would get all mixed through the other threads posts (because of the date order) and we would lose any sense of a flow in the conversation...

Minimum Custom Recovery version?
@Ziyan @Android-Andi Thanks for bringing new life to this old tabs
Is there any minimum requirement for recovery for flashing this ROM? I'm running pretty old CWM v.6.0.5.1. Is it sufficient?

[Need Help] Porting CyanogenMod 13 for SM-G530H

Hi Guys,
I actually tried to port CyanogenMod 13 from my Samsung Galaxy Tab 2.
Here is some info about this device - http://www.gsmarena.com/samsung_galaxy_tab_2_7_0_p3100-4543.php
Why I choose Galaxy Tab 2? Cause that is the only device i have that has CyanogenMod 13. If there is something wrong please let me know.
Now here is the problem. I modified the System folder. but now i cant switch it into system.new.dat . I tried every single program but no use.
So if anyone can help me converting it into system.new.dat. if anyone can i will upload the files in Drive so let me know.

@tasnim_tamim I'm not breaking your heart but it'll not work.
Completely different processors nd kernel versions.
Try porting from a device which has same processor, Snapdragon 410.
Examples: Lenovo A6000, Samsung J5, Moto g(3rd gen), HTC Desire 510, Samsung A3, Samsung A5 & Many more.
Happy porting! I told you all the devices I knew about by my researches so far.

Has.007 said:
@tasnim_tamim I'm not breaking your heart but it'll not work.
Completely different processors nd kernel versions.
Try porting from a device which has same processor, Snapdragon 410.
Examples: Lenovo A6000, Samsung J5, Moto g(3rd gen), HTC Desire 510, Samsung A3, Samsung A5 & Many more.
Happy porting! I told you all the devices I knew about by my researches so far.
Click to expand...
Click to collapse
No problem. I'll try that. Its my first time I am porting a ROM. So I am a noob at these stuff. But anyway thanks for letting me know about that.

Has.007 said:
@tasnim_tamim I'm not breaking your heart but it'll not work.
Completely different processors nd kernel versions.
Try porting from a device which has same processor, Snapdragon 410.
Examples: Lenovo A6000, Samsung J5, Moto g(3rd gen), HTC Desire 510, Samsung A3, Samsung A5 & Many more.
Happy porting! I told you all the devices I knew about by my researches so far.
Click to expand...
Click to collapse
But the thing I'll like to know from you is how you repack system_ or system.img to system. new.DAT??

@tasnim_tamim You're welcome. You'll need Linux for that.

Has.007 said:
@tasnim_tamim You're welcome. You'll need Linux for that.
Click to expand...
Click to collapse
I have Ubuntu 14.04 dualbooted on my system.
And BTW I have selected a ROM from Moto g 3rd gen 2015 which is CM13. ... I am extremely interested in porting ROM.

tasnim_tamim said:
I have Ubuntu 14.04 dualbooted on my system.
And BTW I have selected a ROM from Moto g 3rd gen 2015 which is CM13. ... I am extremely interested in porting ROM.
Click to expand...
Click to collapse
Here you go open the thread nd you can find what you need to know.
http://forum.xda-developers.com/che...arshmallow-t3283452/post64587718#post64587718
Actually I'm not sure if the Cm13 ROMs will work yet, until @zim555 or any other developer builds a Cm13 kernel.
You can try porting but if you're not successful you should go for 5.0 or 5.1.1 ROMs.

Has.007 said:
Here you go open the thread nd you can find what you need to know.
http://forum.xda-developers.com/che...arshmallow-t3283452/post64587718#post64587718
Actually I'm not sure if the Cm13 ROMs will work yet, until @zim555 or any other developer builds a Cm13 kernel.
You can try porting but if you're not successful you should go for 5.0 or 5.1.1 ROMs.
Click to expand...
Click to collapse
Thanks dude for the link.
I am sure I will stuck in a boot loop because I don't have a kernel. So my expectations are wait for @zim555. If cm13 fails I'll try 5.1.1 dirty unicorn

tasnim_tamim said:
Thanks dude for the link.
I am sure I will stuck in a boot loop because I don't have a kernel. So my expectations are wait for @zim555. If cm13 fails I'll try 5.1.1 dirty unicorn
Click to expand...
Click to collapse
Press the thanks instead.
Yup that's the problem, Zim is actually trying to patch the Cm13 kernel to make it work so I'm sure soon he'll start that project maybe in some days.
Best of luck go for Dirty Unicorns.

Has.007 said:
Press the thanks instead.
Yup that's the problem, Zim is actually trying to patch the Cm13 kernel to make it work so I'm sure soon he'll start that project maybe in some days.
Best of luck go for Dirty Unicorns.
Click to expand...
Click to collapse
Okay, I tried porting 5.1.1 OmniRom using the link you gave me. now i followed everything. everything was fine. but when i tried making system.img it dosent works. any suggestion??

tasnim_tamim said:
Okay, I tried porting 5.1.1 OmniRom using the link you gave me. now i followed everything. everything was fine. but when i tried making system.img it dosent works. any suggestion??
Click to expand...
Click to collapse
Check the name of the file you've in that folder. Change the command accordingly.

Has.007 said:
Check the name of the file you've in that folder. Change the command accordingly.
Click to expand...
Click to collapse
First of all the I already messed the conversion to system.img which after that I had to goto windows and extract the whole damn thing. So now I can't change it to system.new.dat. on my windows there is also a software for that. But that asks for something like Select system.img size. Which is what extremely confuses me. And I said earlier that I completely messed up everything on Ubuntu side that now. Now the thing on thread what it said doesn't even works. I did ported everything. But I can't compress it. If you want I can give you screenshot on windows about the program. So if you can help me with that
BTW I am porting OmniRom 5.1.1 from Moto G 2013

[ROM][UNOFFICIAL][T815][T810][T715][T710][8.1] AOKP Oreo

I made this ROM to test my build environment and I thought I would share it with the community in case someone finds it useful.
Find out more about AOKP here: https://aokp.co/
Sources:
Base ROM: https://github.com/aokp
Device trees and kernel: https://github.com/Exynos5433
My thanks to ripee and the exynos5433 team for supporting this tablet. Check out his thread for LineageOS which contains installation instructions and useful utilities which are also applicable to AOKP. https://forum.xda-developers.com/tab-s2/development/rom-lineageos-15-1-t3879302
Here is what you've been waiting for https://androidfilehost.com/?w=files&flid=296203
AOKP has Lineage SU baked in. If you prefer another root solution or don't want root then flash this immediately after flashing the ROM. https://mirrorbits.lineageos.org/su/addonsu-remove-15.1-arm-signed.zip

Heres a new build: latest upstream changes and security update
https://www.androidfilehost.com/?fid=6006931924117894736

thanks.
good to see t815 getting some love

Bug Wifi
With this last rom the wifi connection doesn't turn on, do you have the same problem? What should i do guys?

New builds being uploaded, now also available for the other tab s2 variants.
https://androidfilehost.com/?w=files&flid=296203

Flashed (clean) the latest for 715. I don't see any errors and all is working well... I use WiFi only so I can't confirm cellular data.

Google photos keeps crashing on T815

Google photos keeps crashing +1
T715Y
others work good by now.
Thanks a lot!

Select Google apps package without photos app and install it from play store. Works here! On 715.

Google Photos crashing seems to be an issue with opengapps. If you install the update to Photos from the Play Store, it starts working again.

How different is the T815 variant to the T815Y variant? I have a T815Y, am I able to use this ROM?

I have been using this as a daily driver for my 815 since your first build. thanks @Inkypen !
i took the liberty of forking your roomserice, i wanted to try to make an all in one build. not working so far, the remove frameworks av, didnt work.
ill keep digging. cheers

Tried flashing for the T810 and get error "E3004: This package is for device: gts210wifi,gts210wifixx; this device is ." and it fails.
Edit: Probably has to do with the old TWRP I use. Doesn't support newer versions, so I just edited the updater-script and it worked fine.

BeardKing said:
Tried flashing for the T810 and get error "E3004: This package is for device: gts210wifi,gts210wifixx; this device is ." and it fails.
Edit: Probably has to do with the old TWRP I use. Doesn't support newer versions, so I just edited the updater-script and it worked fine.
Click to expand...
Click to collapse
New twrp has been out for a while.
What mod did you make in the updater script and how.? Just curious to see your work around

New 710 and 815 up
Building 715 check in a little bit if it's uploaded.
Will do 810 after work

tripLr said:
New 710 and 815 up
Building 715 check in a little bit if it's uploaded.
Will do 810 after work
Click to expand...
Click to collapse
Android file host? Can't find new builds?

My build URL
ArtoD2 said:
Android file host? Can't find new builds?
Click to expand...
Click to collapse
Hi all , as i just started building these for myself from @Inkypen 's sources, I thought i would share the google drive link with everyone
tiny.cc/triplr
I will be updating my signiture
Note, I also build for the note 4 and there is some legacy tabs2 stuff im storing
download from the AOKP_oreo folder
thanks !

anyone else having constant (like, every 5 to 10min) drops? wifi stays on, it just disconnects everywhere and I have to manually select a network all the time, or wait a couple of minutes for it to automatically reconn

Dunno

Hi all.
Due to life issues( work )
And aokp not being used too much
I will be discontinuing builds.
Sources are still at
GitHub.com/exynos5433
Best wishes.

Lineage 17.1 and microg

Hey folks,
I'm trying to get microg on Lineage 17.1 for my Moto G7 plus. I know about the current situation, that motog is not working perfectly with Android 10 for now due to some problems with the Unified nlp. However, I would like to install it, but there are multiple problems:
- microg for lineage is not available yet for lake
- I would need to patch lineage to support signature spoofing for installing it manually. I tested nanodroid patcher which didn't work (I guess because I first have to deodex lineage, but am unsure about that)
- There is a new microg fork called minmicrog
Could you give me some recommendations on a preferred setup? I also thought about building micro for lineage with the docker image but am not sure if this will work out due to limited hardware.
Thanks a lot!

I just got this phone and the development on it i believe is still getting in gear.... I know for sure that you can get microg setup on a custom rom using the nandroid setup...as far as this goes Im gonna try it right now....Ive got every custom rom available for us and most are google pixel based so that just defeats the whole purpose... so Ill try and learn as I go....I believe that Havoc and crdroid have signature spoofing options in there respected settings menus....i will test and report back......Also you can do this with a stock rooted rom with magisk and twrp......
NanoDroid wiki....great instructions
this is what Im gonna follow if you want to try yourself and report back

cobra202 said:
Hey folks,
I'm trying to get microg on Lineage 17.1 for my Moto G7 plus. I know about the current situation, that motog is not working perfectly with Android 10 for now due to some problems with the Unified nlp. However, I would like to install it, but there are multiple problems:
- microg for lineage is not available yet for lake
- I would need to patch lineage to support signature spoofing for installing it manually. I tested nanodroid patcher which didn't work (I guess because I first have to deodex lineage, but am unsure about that)
- There is a new microg fork called minmicrog
Could you give me some recommendations on a preferred setup? I also thought about building micro for lineage with the docker image but am not sure if this will work out due to limited hardware.
Thanks a lot!
Click to expand...
Click to collapse
I got full Microg status with unifiednlp ....and man there is so much bad, old and wrong info.....I pulled it off with a vanilla Arm64 ab gsi which I love it is the best ROM ive tried.......also I found a new way to patch the signature spoof that I wasnt aware of using smaili patcher....and bare minimal installer just released.....seems since micro g and lineage got together more people are wanting to try..... I am so tired,,,,,,it seriously ate me up but I beat it.....if u need links or instructions private messege me .....I will create a forum post probably soon

KtownJeff said:
I got full Microg status with unifiednlp ....and man there is so much bad, old and wrong info.....I pulled it off with a vanilla Arm64 ab gsi which I love it is the best ROM ive tried.......also I found a new way to patch the signature spoof that I wasnt aware of using smaili patcher....and bare minimal installer just released.....seems since micro g and lineage got together more people are wanting to try..... I am so tired,,,,,,it seriously ate me up but I beat it.....if u need links or instructions private messege me .....I will create a forum post probably soon
Click to expand...
Click to collapse
Thanks, sounds interesting, will also give it a try! Finally managed to get lineage 17.1 working with microg building it myself, check github.com/lineageos4microg/docker-lineage-cicd/pull/70. So built went through, could flash it and seems to work like a charm

cobra202 said:
Thanks, sounds interesting, will also give it a try! Finally managed to get lineage 17.1 working with microg building it myself, check github.com/lineageos4microg/docker-lineage-cicd/pull/70. So built went through, could flash it and seems to work like a charm
Click to expand...
Click to collapse
you should try this FLOSS GSI ready made daily driver without any Google.... if you want root flash magisk after you set it up....
https://forum.xda-developers.com/pr...velopment/aosp-10-0-quack-phh-treble-t3992559[/QUOTE]
there is three versions FLOSS, Vanilla, and GAPPS..... make sure you choose ARM64 AB

[SM-T700] [KLIMTWIFI] All-in-one mirror of files for the Galaxy Tab S 8.4 Wi-Fi

Hey there interweb!
This thread is meant as a general area to organise the mess of files scattered across the internet for the original Wi-Fi version of the Samsung Galaxy Tab S 8.4.
This Google Drive folder contains the following:
Stock Odin TAR/MD5 firmware files
ROMs, and their accompanying files + install instructions that have been confirmed to boot,
Kernels that have been confirmed to boot,
Useful mods which are confirmed to work and add genuine capability to your device;
and anything else which I think is useful to those wishing to mod their Tab S.
Link:
androiddev - Google Drive
drive.google.com
If you know of any files which you think should be included, and are not already here, please feel free to either reply to this thread or DM me. If you want any assistance at all, please feel free to do the same, and I will try to assist you to the best of my ability.
All the best,
Cessna
I must reiterate, as always, that although I have tested each of these mods, I am not responsible for bricks, loss of data, or permanent damage to your device. You yourself are choosing to make these modifications, and although they have my quality assurance, I can not guarantee their 100% safety. Just because they worked on my device, does not necessarily mean they will work on yours.

CessnaBroon said:
Hey there interweb!
This thread is meant as a general area to organise the mess of files scattered across the internet for the original Wi-Fi version of the Samsung Galaxy Tab S 8.4.
This Google Drive folder contains the following:
Stock Odin TAR/MD5 firmware files
ROMs, and their accompanying files + install instructions that have been confirmed to boot,
Kernels that have been confirmed to boot,
Useful mods which are confirmed to work and add genuine capability to your device;
and anything else which I think is useful to those wishing to mod their Tab S.
Link:
klimtwifi - Google Drive
drive.google.com
If you know of any files which you think should be included, and are not already here, please feel free to either reply to this thread or DM me. If you want any assistance at all, please feel free to do the same, and I will try to assist you to the best of my ability.
All the best,
Cessna
I must reiterate, as always, that although I have tested each of these mods, I am not responsible for bricks, loss of data, or permanent damage to your device. You yourself are choosing to make these modifications, and although they have my quality assurance, I can not guarantee their 100% safety. Just because they worked on my device, does not necessarily mean they will work on yours.
Click to expand...
Click to collapse
Good idea to gather everything on one place and make the mess a bit easier to handle..
I helped myself with the TWRP and the LOS17, much obliged. Don't really need help otherwise.
That is, unless you know why my t705 (i have one of those too) keeps messing with me and losing charge even when switched off...

prkfsz said:
Good idea to gather everything on one place and make the mess a bit easier to handle..
I helped myself with the TWRP and the LOS17, much obliged. Don't really need help otherwise.
That is, unless you know why my t705 (i have one of those too) keeps messing with me and losing charge even when switched off...
Click to expand...
Click to collapse
I'll be honest, my Tab s battery has decreased to about 2100 mAh from 4900 so it's probably just age I'm afraid. If you use it more, you could do a battery transplant, but I don't have ROMs for klimtlte. Thanks for using my mirror

CessnaBroon said:
I'll be honest, my Tab s battery has decreased to about 2100 mAh from 4900 so it's probably just age I'm afraid. If you use it more, you could do a battery transplant, but I don't have ROMs for klimtlte. Thanks for using my mirror
Click to expand...
Click to collapse
Not battery. Changed it. And the same battery works fine on T700 and does not lose charge when off. Tried flashing other ROM as well, but i can't find solution.

prkfsz said:
Not battery. Changed it. And the same battery works fine on T700 and does not lose charge when off. Tried flashing other ROM as well, but i can't find solution.
Click to expand...
Click to collapse
That's odd. Have you tried flashing a custom kernel in TWRP? If not, I'll upload one to the Google Drive in the /androiddev/klimtlte folder. Will create it soon, along with instructions.

CessnaBroon said:
That's odd. Have you tried flashing a custom kernel in TWRP? If not, I'll upload one to the Google Drive in the /androiddev/klimtlte folder. Will create it soon, along with instructions.
Click to expand...
Click to collapse
Odd indeed. And really frustrating. :-/
Have not tried with custom kernel but can of course do that, if it's simple. But, like i said - it's a T705, you mean there is one already made or are you just going to make one on a coffee break?

prkfsz said:
Odd indeed. And really frustrating. :-/
Have not tried with custom kernel but can of course do that, if it's simple. But, like i said - it's a T705, you mean there is one already made or are you just going to make one on a coffee break?
Click to expand...
Click to collapse
There's one already made I think. I'll see if I can find one and alert you when it's up. Obvs I can't do a check for safety without the hardware so make a full backup of the boot partition just in case. I'll make sure to find one with good reviews

CessnaBroon said:
There's one already made I think. I'll see if I can find one and alert you when it's up. Obvs I can't do a check for safety without the hardware so make a full backup of the boot partition just in case. I'll make sure to find one with good reviews
Click to expand...
Click to collapse
Not sure if i have the time to do it tonight or this weekend, but i will try as soon as i get the chance.
Very gratefull for all the help. I actually have two of them, with the same behaviour and i almost written them off, so..

prkfsz said:
Not sure if i have the time to do it tonight or this weekend, but i will try as soon as i get the chance.
Very gratefull for all the help. I actually have two of them, with the same behaviour and i almost written them off, so..
Click to expand...
Click to collapse
kernel - Google Drive
drive.google.com
Shouldn't take more than 5 minutes. Good luck!

CessnaBroon said:
kernel - Google Drive
drive.google.com
Shouldn't take more than 5 minutes. Good luck!
Click to expand...
Click to collapse
Thank you kindly, sir.
Will try right away, but can't really see if had any effect untill morning.
I thought first to ask you if it is possible to use this on stock too, but then it struck me how stupid idea that is, since it's not the same Android version. Because one of them is on stock and behaving the same way. Which basically leads me to believe that it actually is a hardware fault...

prkfsz said:
Thank you kindly, sir.
Will try right away, but can't really see if had any effect untill morning.
I thought first to ask you if it is possible to use this on stock too, but then it struck me how stupid idea that is, since it's not the same Android version. Because one of them is on stock and behaving the same way. Which basically leads me to believe that it actually is a hardware fault...
Click to expand...
Click to collapse
This should work on stock marshmallow too. I will give it a go and get back to you.

Thank you kindly!

lafinjack said:
Thank you kindly!
Click to expand...
Click to collapse
You're very welcome!

CessnaBroon said:
This should work on stock marshmallow too. I will give it a go and get back to you.
Click to expand...
Click to collapse
Sorry for delay in answering..
Unfortunatelly the error is still present. Like i said, probably a software issue.
Bit thanx anuway!

Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!

darethehair said:
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
Click to expand...
Click to collapse
Hey there! I'll take a closer look once I'm home. Speak to you then

darethehair said:
Thanks for creating a section specifically for the SM-T700! I hope that I can get some practical help on moving forward
On my post here (https://forum.xda-developers.com/t/...d-but-ok-with-resurrection-remix-why.4332701/) I describe my attempt to install a variation of LineageOS 17.1 on my device -- always running into 'E1001'. I eventually settled on an older Resurrection Remix, since someone mentioned that it would ultimately make it possible to move to LineageOS (I have not tried that yet).
Here are some of my questions:
1) In a much larger/older thread (https://forum.xda-developers.com/t/...t700-sm-t705-sm-t800-sm-t800-sm-p600.4270943/) the first step is "Flash latest official Samsung Firmware with ODIN". Is this even relevant to me?
2) In preparation for successfully installing LineageOS, what TWRP clearing/formatting options should I be using? On a completely different device, the instructions were to delete *everything*. Could my wrong choices when doing this for my SM-T700 have contributed to my failures?
3) Now that I (currently) have Resurrection Remix on my SM-T700, can I expect -- with the binaries mentioned in this new subgroup -- to be able to install LineageOS 17.1 *without* running into the 'E1001' problem?
Thanks for any help!
Click to expand...
Click to collapse
Hey! Sorry for the delay. You should flash the latest firmware (it's on updato.com) Using Odin, and then twrp with Odin, and then the custom ROM from twrp, wiping data dalvik and cache before rebooting. Other two are in the mirror.

CessnaBroon said:
Hey! Sorry for the delay. You should flash the latest firmware (it's on updato.com) Using Odin, and then twrp with Odin, and then the custom ROM from twrp, wiping data dalvik and cache before rebooting. Other two are in the mirror.
Click to expand...
Click to collapse
Just an FYI...I was reluctant to start everything over again with Odin and latest Samsung firmware, so I opted to take a chance and merely 'adb push' the LineageOS and GApps that you have on your Google drive (along with some cache erasures as you suggested) and everything seemed to upgrade properly from Resurrection Remix to LineageOS 17.1
A few minor problems so far: camera doesn't work, and initial signon to the tablet with a PIN doesn't work so well (seems to take multiple attempts). In any case, now running Android 10!

These were issues that I faced too - I never found a way to fix them. Neither did the original Dev, but apparently updating to the latest webview fixes chrome crashes. PIN you need to wait 30seconds after boot. Camera works only with clean install and even then sometimes doesn't work.
Hope this helps,
Cessna

I was trying to install TWRP but after reboot when I go to the Recovery mode there is no TWRP. I installed the LOS on my Tab Pro 8.4 and wanted to install LOS on Tab S 8.4 but can't flash the TWRP. Any ideas what I'm doing wrong?
Thanks