Hi,
I don't want to waste your time, but I think this is a proper time to ask a question.
This tablet(s) are 9 months on the market. Tons of ROMs came to see the daylight, every less important variant of this device got AOSP or CM builds for them, and that's awesome! And everybody enjoy their cool tablets, except ... the owners of the best and most important variant - 10.5 LTE. And there is even official T705 CM12 build! Why not for T805?
I feel sorry I don't have any knowledge in programming or porting, neither I have any pleasure in doing it. But there are a lot of great and talented chiefs who love to port and build good ROMs who make a good TW stuff, and a lot of guys who make AOSP for ... WiFi version. Noone is interested in LTE model, and there is a lot of T805 users out there waiting for AOSP release and asking on every Tx00 threads for builds for their devices.
I have a lot of respect for hard work everyone do here, and we all understand everyone of you - talented chiefs here - have limited time and possibilities. I am personally very grateful for your effort. And don't get my post wrong. All it is about is to ask: Why? Why there are CMs, AOSPs for T800, which I think is not so much different from LTE model,and there is NOTHING AOSP for T805....
I think there will be more than only me to greatly ask for attention from great developers of xda, to ask them for xda miracle for us. Please, make something AOSP for T805... please please please! Let us see this:
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.
*
*/
We all would be so grateful for your help, to let us feel the Google Experience..
Thank you!
HUGE UPDATE
It looks like we got it! Finally, good working Lollipop with LTE on our amazing devices. Now the Tab S got a new life, with pure Google Experience! For everyone interested, check out our great developer who made a HUGE effort to make this happen (big cudos to AndyT12) and his website with updates and downloads:
http://goo.gl/ODCQ94
AAAND HERE WE GO!
Another AOSP from cool developer deadman96385:
http://forum.xda-developers.com/gal...m-liquidsmooth-v4-1-lollipop-sm-t700-t3092696
Unfortunately LTE still does not work here but they have just the initial build se let's be patient! Thank you!
UPDATE ON NEXT GREAT BUILDS
We are happy to see yet another great build with working LTE! This time it's amazing work from developer Nexorr who managed available sources from NVertigo and AndyT to build this ROM! Check the links below to download the stuff:
http://forum.xda-developers.com/showpost.php?p=61934130&postcount=78
http://forum.xda-developers.com/showpost.php?p=61940915&postcount=84
Thank you Nexorr for your huge effort!
Yes.. I'm interested this project... Available for Betatester on my Sm-t805.... Happy to see Android v5.1.1 full working on this device
T805 is alot different than T800. Nvertigo explained why a while back. One simply cannot build without having the device. In my guessing, more people probably have wifi ones vs lte models in which most devs have Idk. Nvertigo made a thread also on how to build/port. http://forum.xda-developers.com/showthread.php?t=3031278
It requires a ton of work so... yeah.
So there is no hope, I guess...
Btw I thought there are much more interested people in the AOSP. I was wrong, it seems. 248 visitors came across this thread without even a word, so let's say it: buy N9 or eat TW rubbish.
Would @nvertigo67 be willing if we all donated to his PayPal or something? I'm not sure if he has seen this thread or not.
callum_88 said:
Would @nvertigo67 be willing if we all donated to his PayPal or something? I'm not sure if he has seen this thread or not.
Click to expand...
Click to collapse
Bring him in.
callum_88 said:
Would @nvertigo67 be willing if we all donated to his PayPal or something? I'm not sure if he has seen this thread or not.
Click to expand...
Click to collapse
Whoever read the cm12.1 for t800 thread knows about how much time I can spend on development untill November: it's hardly enough to keep up the development for t800.
So: no, I will not develop for a different device for now.
I said MANY times: there is a cm11 development for chagalllte and cm12.1 for klimtlte. Thats a good starting point.
nvertigo67 said:
Whoever read the cm12.1 for t800 thread knows about how much time I can spend on development untill November: it's hardly enough to keep up the development for t800.
So: no, I will not develop for a different device for now.
I said MANY times: there is a cm11 development for chagalllte and cm12.1 for klimtlte. Thats a good starting point.
Click to expand...
Click to collapse
And the questions from the first post still apply.
Hi Guys, I said I would do it and have CM12.1 for SM-T805 TAB S 10.5 LTE. Check my blog www.androidstuff.info Cheers
andyt12 said:
Hi Guys, I said I would do it and have CM12.1 for SM-T805 TAB S 10.5 LTE. Check my blog www.androidstuff.info Cheers
Click to expand...
Click to collapse
Hi Andrew! It is so great to hear! This is so cool! Thanks for the information. Are you willing to make xda thread also? Thanks!
PS. Is this build working or it is relatively experimental one? I am worried to lose my data or backups etc..
Hi, i have problems with download, it is so slow and then breaks the download fail. Any oher options to download ?
It was so great CM12.1 for the tab T805 LTE...... and great Job Thanks
One question, must i use your twrp or is it ok with the Original twrp i have 5.0.2 on my tab Iron Rom lollipop
Same here, download fail. But anyway, thank you for your effort! Would really like to try it.
Btw backing up efs, in twrp?
I could use a quick HOW-TO, @andyt12:
with both your provided Odin3.07, and my own Odin3.10, I could not graphically locate either your .md5sum file, nor the .zip ROM archive. At least I *could* enter the file/archive names at the Odin text-entry-box...
but that produced another pair of issues:
-although the suffix ".md5sum" isn't recognized, direct-entry of the filename indicates "binary corrupted" or similar
-entering the .zip archive directly results in Odin message-box saying "success 0/failed 1"
I am really, really excited at the prospect of CM12.1 for my tablet (matching my phone). But I seem to be sort of stuck at some basic point. BTW, I already had TWRP-2.8.6.0 installed on my T805, so I left that and did not try your provided version...
Thank-you for you efforts! I deeply appreciate the work you've put into this!
GordP
is this for t-805y or just t-805 ? since u seem from OZ the version i have is from telstra.
This is awesome. I'm so grateful someone is making a CM12 for t805. Will be trying it soon. Do we have a list of known issues/things that still need work?
andyt12 said:
Hi Guys, I said I would do it and have CM12.1 for SM-T805 TAB S 10.5 LTE. Check my blog www.androidstuff.info Cheers
Click to expand...
Click to collapse
Please put it in Xda it will be helpful to test and to make solutions to help you in this project
I've downloaded the latest build (as of May 30) and re-uploaded it to Mega (with an md5 file): https://mega.nz/#F!JhsSTahA!sEf03jOCUWHFbQXizOX_lA
DarkDvr said:
I've downloaded the latest build (as of May 30) and re-uploaded it to Mega (with an md5 file): https://mega.nz/#F!JhsSTahA!sEf03jOCUWHFbQXizOX_lA
Click to expand...
Click to collapse
There is any issue or bugs in this rom ?
Cuz there is no info about rom
So, here's what I did/got:
To repeat dev's words:
Make sure you use EFS backup tools (for example, there's one in Play store) to backup your EFS/IMEI partitions somewhere in a safe place (not just on a tablet).
1. Was not able to install Andrew's TWRP (Odin claims it's broken, redownloading the tar.md5 didn't help).
2. Used my own TWRP (latest, from XDA) to wipe system/data/caches, then install the CM12 zip Andrew has created.
3. Installed latest 5.1.x gapps (micro) from here: http://www.androidrootz.com/2015/03/download-android-51x-lollipop-pa-gapps.html
4. Rebooted
ROM booted just fine, no errors or issues so far.
Bluetooth tested and works.
Wifi tested and works.
Mobile network and data tested and works.
Root, ADB work
USB works - able to see both device storage & SDcard
CPU: usage seems normal, with cores ranging from 200MHz to 1.9GHz. Although I don't see any cores disabling during no load. Not sure if this is normal.
Performance: subjective. To me, device seems a hell of a lot snappier. Transitions, scrolling, app switching - noticeably smoother than on Lollipop TW.
GPU test: tested in a game (hearthstone), performace is the same as on stock ROM, didn't see any difference.
Temperature: max 43C so far, seems the same.
Camera: both front and back cameras work
Battery: device is sleeping fine, no wakelocks. Battery usage completely flattens when it's sleeping, so, in a few days, I'm expecting a good battery life.
Charging: I think it's the same as on stock: around +500mA when device is ON and on a wall charger.
Bug: Samsung's stock docking keyboard: everything works, expect the app switch button.
Bug: In app switcher - there's an error loading the search widget. No big deal, but it's a thing.
Device info screen
Continuing to test other features, but so far, no issues encountered. Getting really freaking excited.
DarkDvr said:
So, here's what I did/got:
1. Was not able to install Andrew's TWRP (Odin claims it's broken, redownloading the tar.md5 didn't help).
2. Used my own TWRP (latest, from XDA) to wipe system/data/caches, then install the CM12 zip Andrew has created.
3. Installed latest 5.1.x gapps (micro) from here: http://www.androidrootz.com/2015/03/download-android-51x-lollipop-pa-gapps.html
4. Rebooted
ROM booted just fine, no errors or issues so far.
Bluetooth tested and works.
Wifi tested and works.
Mobile network and data tested and works.
Continuing to test other features, but so far, no issues encountered. Getting really freaking excited.
Click to expand...
Click to collapse
Thank you for this info
What about battery and temperature of device ?
And if he used default kernel speed for cpu
Sorry for long questions
Finally what about speed and what is better TW or CM12.1 ?
All the answers before my post ? ??
Related
To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Website:
http://androidarmv6.github.io/
Source code:
https://github.com/androidarmv6
You can watch development as it progresses, or you can sign in and participate here:
http://review.androidarmv6.org/#/q/status:merged
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
sent from my towelrooted LG L34C using daishi4u bumped twrp 2.8.3.0 and bumped key-boot-recovery kernel
...as he looked back on the sleeping giants, exhausted from their long journey, the wizard Androidmeda new that he had taught them all that he could, and they had all that they needed. But he also knew that they would never be able to survive crossing the mountains into the new land. Only their child would be able...
Well I guess this is it my brothers. Seems that all has been tried, and CM-12 will not be released for armv6 devices. But many thanks to our devs for trying. It's been a long run. Amazing, just amazing.
ibub said:
To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Source code:
https://github.com/androidarmv6
ROMs:
http://jenkins.androidarmv6.org
sent from my towelrooted LG L34C using tapatalk
Click to expand...
Click to collapse
Congrats! Nice preface wording, bro! :good:
Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.
Dovidhalevi said:
Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.
Click to expand...
Click to collapse
Thanks, link updated to View/All.
sent from my towelrooted LG L34C using tapatalk
This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...
D3oDex3D_AyusH said:
This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...
Click to expand...
Click to collapse
Just to be clear, this is not my work. Androidarmv6 team (mainly androidmeda for p500) compiles these ROMs. Thanks belong to them (him).
sent from my towelrooted LG L34C using tapatalk
Wut? ART isn't compatible with ARMv6, AFAIK.
Casserole said:
Wut? ART isn't compatible with ARMv6, AFAIK.
Click to expand...
Click to collapse
We shall soon see.
sent from my towelrooted LG L34C using tapatalk
CyanogenMod announces official CM12 Nightlies!
http://phandroid.com/2015/01/05/cyanogenmod-cm12-nightlies/
Do not even expect P500 on the list!
EDIT:
CyanogenMod 12 nightlies now available for 31 devices, based on Android 5.0.1 Lollipop (LRX22C). LG Optimus One is out of the list to be sure
http://blog.gsmarena.com/cyanogenmo...able-31-devices-based-android-5-0-1-lollipop/
While in other hand, our devs are working to port experimentally newer version of CM12 (Android 5.0.2 LRX22G) on armv6 obsolete devices, though! :good:
You can look at development of android_art as it progresses here:
http://review.androidarmv6.org/#/q/status:merged
and here:
http://review.androidarmv6.org/#/c/7676/
Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app
xu3sno said:
Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app
Click to expand...
Click to collapse
Trimmed>>Flashed>>Stuck at CM bootlogo
CCXAlex said:
Trimmed>>Flashed>>Stuck at CM bootlogo
Click to expand...
Click to collapse
+1K
GERRIT_CHANGES: 7676 7748 7693 7651 7751 7792
Code:
7676: * runtime : make entrypoints ARM; if the target arch is lower than
armv7, set armv6.
* compiler: add a new define: ARM_MODE_WORKAROUND, enable it if
the target cpu is arm11. Use ARM assembler and replace
Thumb{1-2} opcodes with ARM ones. Update some code to
support new opcodes
NOTE: kArm is not implemented, probably it use to work only in
portable mode.
7748: Compatibility work around for bad graphics driver dependency
7693: legacy OMX: squashed commit for legacy OMX support for LP
7651: Revert "Revert "Turn on BLE, GATT, and SMP of Bluetooth stack""
7751: msm7x27-common: Initial cm-12 bringup
7792: jemalloc: Force gcc for atomic functions
GCC built-in functions provide advanced things like prefetch, expected, synchronization...
Bootloog attached.
It seems bootloop's culprit is regarding with dynamic shared libraries (lib*.so) which must be fixed first.
It does not work on any device arvm6.
Link
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Also, a reminder of some things you shouldn't do (now or ever): don't ask for ETAs, don't spam the dev thread, and don't PM me asking for information that isn't on a public post.
There are many things that need to be fixed for armv6 devices. I've sorted out the major issues specific to Broadcom hardware, but there are more important issues that need solving for ARMv6 devices in general that are being working on by several people (assembly errors, ART compatibility, build system integration, etc.). It's going to take time. Thanks for your understanding.
Click to expand...
Click to collapse
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
xu3sno said:
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
Click to expand...
Click to collapse
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno
Any PlayStore said:
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno
Click to expand...
Click to collapse
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not
Quote:
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Click to expand...
Click to collapse
Yes, yes, we know or should know. But, hey, who does not want to be the first to see this play? The only reason I am staying off is because of the CM tricks with switching system and data partitions meaning recoveries are not compatible.
Anyway, diehards within the CM universe, once in that bootloop if ART had indeed done its thing, check remaining system space and contents of those /system/app/... folders. My (un-) educated guess is that this may become the big problem.
xu3sno said:
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not
Click to expand...
Click to collapse
I also attempted to install this. Initially my trimming method seems to have broken update binary, so flash failed. Next installed full ROM (/system =189MB) using @HardLight twrp 2.7.0.0 TLS (successfully flashed). Stuck at boot animation. No log (flashing while driving).
sent from my towelrooted LG L34C using tapatalk
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?
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community
There are lineage os builds for only tab s2 8.0 2015 models.
this version is stable without any known issues.
Root is not included here. For root install magisk or su-addon ( https://mirrorbits.lineageos.org/su/addonsu-14.1-arm-signed.zip )
install:
flash with twrp
don't forget to flash gapps ( opengapps.org ) you need version for android 7.1 arm
download:
20180102
t710: https://drive.google.com/open?id=1tkzdpZdGXNouu0ig-NHGErWfmUP_CICP
t715: https://drive.google.com/open?id=1cLX-gWvUM9miJ3JTmcnWeXrNxI0F3II5
test build 20180303 for t710 is here: https://forum.xda-developers.com/showpost.php?p=75756582&postcount=147
sources:
https://github.com/bonuzzz/android_kernel_samsung_gts2
https://github.com/bonuzzz/android_device_samsung_gts2-common
https://github.com/bonuzzz/android_device_samsung_gts28wifi
https://github.com/bonuzzz/android_device_samsung_gts28ltexx
https://github.com/bonuzzz/android_vendor_samsung_gts2-common
https://github.com/bonuzzz/android_vendor_samsung_gts28wifi
https://github.com/bonuzzz/android_vendor_samsung_gts28ltexx
WOW! This is the first build of Lineage that works great on my tab! Didn't test fingerprint but autobrightness and camera is working great. Thank a lot. On T710 by the way.
See my signature for twrp 3.1.1-0 for both gts28wifi and gts28ltexx.
Please note that twrp 3.2.0-0 has just been released! I'll be working on bringing it up to the Galaxy Tab S2 2015 tablets as soon as possible
On a related matter, I own a 9.7 wifi variant and I build for it daily. Netflix doesn't work with the official gts2-common repo, but if you use mine it will. I kept a long since abandoned fix which has worked very well in my builds.
Do we need gapps, thank you sooooooo much for this!!!!
Sent from my SM-T710 using Tapatalk
---------- Post added at 01:04 AM ---------- Previous post was at 12:45 AM ----------
ripee said:
See my signature for twrp 3.1.1-0 for both gts28wifi and gts28ltexx.
Please note that twrp 3.2.0-0 has just been released! I'll be working on bringing it up to the Galaxy Tab S2 2015 tablets as soon as possible
On a related matter, I own a 9.7 wifi variant and I build for it daily. Netflix doesn't work with the official gts2-common repo, but if you use mine it will. I kept a long since abandoned fix which has worked very well in my builds.
Click to expand...
Click to collapse
You sir, are a good among men, which gapps do you recommend? And we can install su manually whithout messing up the fixes you got to make this bad boy run? Once again thank you.
Sent from my SM-T710 using Tapatalk
lahegry said:
Do we need gapps, thank you sooooooo much for this!!!!
Sent from my SM-T710 using Tapatalk
---------- Post added at 01:04 AM ---------- Previous post was at 12:45 AM ----------
You sir, are a good among men, which gapps do you recommend? And we can install su manually whithout messing up the fixes you got to make this bad boy run? Once again thank you.
Click to expand...
Click to collapse
I flash pico on my phone and tablet, but even stock or higher should work if the builds are from official sources. I also recommend Magisk if you wish to root. If these builds have su root, Magisk simply uninstalls it before installing itself.
bonuzzz, you did what most (self proclaimed) devs failed to achieve and deliver for the T710/715 in the last months! i just installed the ROM and tried it out the last few hours. finally got a clean and reliable android for my T710.
it's working really smooth, no issues so far. everything - including bluetooth and fingerprint - is working perfectly [edit: haven't tried it, since not needed: according to some posts in this thread stock camera doesn't seem to be working properly]. i am really anstonished and amazed by this great initial release, thanks a lot. i hope you keep on delivering such a good work.
many thanks and best regards from germany
For me on my T710 the microphone did not work. So it isn't in perfect working order yet and the battery drains quite fast, but it's miles better than the previously shared builds here on XDA, and most certainly usable.
I also had issues with certain apps not working properly, so I ended up going back to stock for now. (more precisely: the Antutu 3D part and the Focus gallery application).
TWRP 3.2.0-0 for gts28wifi and gts28ltexx!
twrp-3.2.0-0-gts28wifi.img
twrp-3.2.0-0-gts28wifi.tar
twrp-3.2.0-0-gts28ltexx.img
twrp-3.2.0-0-gts28ltexx.tar
@ripee,
create your own topic please. dont spam here. thank you
bonuzzz said:
@ripee,
create your own topic please. dont spam here. thank you
Click to expand...
Click to collapse
Sorry if twrp is spam. Best of luck fiddling around with lineage recovery. For everyone's sake, I hope that Netflix works on your builds.
Thanks a lot for this build. An important progress for the T710/T715.
And also thx for the current TWRP link @ripee, missed that one.
Camera app force closed. Dont save any pictures
If you use a third party app like open camera, it actually works really well.
Either way, the microphone doesn't work at all, as in all roms for this device, and sadly it is a deal breaker for me since I use my tablet for video calls all the time.
azenyr said:
If you use a third party app like open camera, it actually works really well.
Either way, the microphone doesn't work at all, as in all roms for this device, and sadly it is a deal breaker for me since I use my tablet for video calls all the time.
Click to expand...
Click to collapse
open camera same problem.
My twrp recovery is old. I update this and I will try again
Having used this ROM for the last few days on a T710, I experienced a very stable system. UI was always smooth, no serious issues so far. :good:
However, I observed some strange behaviours/minor issues:
Fingerprint unlock isn't always working reliably. Sometimes, when trying to unlock the lockscreen, the finger on the fingerprint sensor doesn't seem to be detected and the PIN has to be entered manually.
LiveDisplay is not always active when the device comes from sleep and has to be unlocked. Upon the next sleep/active via short press on the power button iteration, the LiveDisplay mostly works as expected.
Once, presumably a wakelock drained the battery throughout the day until it was empty and the device turned itself off. I don't know why this happened and can't reproduce it.
Altogether a very successful start for this ROM, I will keep it on my device and hope the dev keeps on working on it to further improve it or even update to Lineage 15.x...
Thanks, @bonuzzz!
Sorry for intruding again, but we are about to get official TWRP support! I've been asked to test the "release candidate" images. As I don't have either a gts28wifi or gts28ltexx, I'd like to post the links here and ask for feedback. I'll create a separate TWRP thread once I confirm that these twrp builds work. I apologize again:
http://build.twrp.me/twrp-3.2.1-0-gts28wifi.img
http://build.twrp.me/twrp-3.2.1-0-gts28wifi.img.tar
http://build.twrp.me/twrp-3.2.1-0-gts28ltexx.img
http://build.twrp.me/twrp-3.2.1-0-gts28ltexx.img.tar
ripee said:
Sorry for intruding again, but we are about to get official TWRP support! I've been asked to test the "release candidate" images. As I don't have either a gts28wifi or gts28ltexx, I'd like to post the links here and ask for feedback. I'll create a separate TWRP thread once I confirm that these twrp builds work. I apologize again:
http://build.twrp.me/twrp-3.2.1-0-gts28wifi.img
http://build.twrp.me/twrp-3.2.1-0-gts28wifi.img.tar
http://build.twrp.me/twrp-3.2.1-0-gts28ltexx.img
http://build.twrp.me/twrp-3.2.1-0-gts28ltexx.img.tar
Click to expand...
Click to collapse
Hi! I tested gts28wifi for my SM-T700 but touch sensor is wrong. The interface is unusable for now. Best of luck. But you should start your own thread...
powerade001 said:
Hi! I tested gts28wifi for my SM-T700 but touch sensor is wrong. The interface is unusable for now. Best of luck. But you should start your own thread...
Click to expand...
Click to collapse
ripee said:
Sorry for intruding again, but we are about to get official TWRP support! I've been asked to test the "release candidate" images. As I don't have either a gts28wifi or gts28ltexx, I'd like to post the links here and ask for feedback. I'll create a separate TWRP thread once I confirm that these twrp builds work. I apologize again:
What would be the point of a dedicated thread if it doesn't work? Anyway, thanks for your feedback.
Click to expand...
Click to collapse
ripee said:
ripee said:
Sorry for intruding again, but we are about to get official TWRP support! I've been asked to test the "release candidate" images. As I don't have either a gts28wifi or gts28ltexx, I'd like to post the links here and ask for feedback. I'll create a separate TWRP thread once I confirm that these twrp builds work. I apologize again:
What would be the point of a dedicated thread if it doesn't work? Anyway, thanks for your feedback.
Click to expand...
Click to collapse
The point is,..
If your building it, wouldn't you want it all together so you could track it easier? Now you'll need to read all the threads that you've posted this into to find the results.
I know we all appreciate you doing this. But please make your own thread for it so we can all see what's going on. Without having to read through the 4+ threads this is in.
Keep it up. It's nice to see our tabs still getting some love. Thank you. ?
Click to expand...
Click to collapse
engine95 said:
ripee said:
The point is,..
If your building it, wouldn't you want it all together so you could track it easier? Now you'll need to read all the threads that you've posted this into to find the results.
I know we all appreciate you doing this. But please make your own thread for it so we can all see what's going on. Without having to read through the 4+ threads this is in.
Keep it up. It's nice to see our tabs still getting some love. Thank you.
Click to expand...
Click to collapse
Is it possible to make android oreo??
What are the basic requirements for it??
Click to expand...
Click to collapse
Discontinued.
Awaiting for thread deletion.
Thanks...Nice work after your miui 5 ROM
Help please..
Need someone who can risk his device by testing this ROM......
Happy holi.....
Happy holi my friends...
May this holi bring lots of Colors in your life!! and in mine too.
Kunal Gautam said:
Need someone who can risk his device by testing this ROM......
Click to expand...
Click to collapse
I tried to install but it gives error 7 i think update.script should be rechecked.
Deep_dhimaan said:
I tried to install but it gives error 7 i think update.script should be rechecked.
Click to expand...
Click to collapse
Thank you very much, i've understood whats the problem( as a pm by ashkineeeeee).
New update coming soon. Stay tuned.
Hey bros...
so there were some problem with permissions, it seems that it is fixed now..
Flash the ROM and review here....
----------------------edit 1---------------------
dont flash the rom now!!!
Some files are missing in boot.img
how stupid i am!!
------------------------edit 2-----------------------
Flash it now!
Last build not installed,error 7.
mels01 said:
Last build not installed,error 7.
Click to expand...
Click to collapse
Logs,screenshots?
Try installing from internal storage... Or update your recovery to the latest one by android andi...
Thanks!
Hey, I would like to help out, can I have the link to the ROM?
theportal2 said:
Hey, I would like to help out, can I have the link to the ROM?
Click to expand...
Click to collapse
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Links
Kunal Gautam said:
I agree this message is a bit long but it is worth reading.
- Thanks, but sorry. Even if I give you the links and even if spend your precious time you would only be able to fix the error 7.
- Actually I've already fixed that(or know what's the issue atleast). There are files that are missing from the directories that are listed in the updater script. They cannot be deleted as the original base ROM I compiled was from UA(unlegacy android) that are based on the newer sources.
- Some files that are required for MIUI are also missing.
- Boot.img is incomplete. Which will result in bootloop even if I upload the error 7 fixed ROM.
- I am giving my board exams that are one of the biggest exams in India. And I cannot afford to score less in these.
- All I need is a older base ROM ,CyanogenMod 11 made around may of 2016. And also it must support init.d because the port ROM requires that.
- I've taken permissions from the maker of the port ROM. He has allowed me to proceed.
- All I need is permission from Android-Andi, as only he has older CM ROMs.
- I cannot compile because older sources are not available or maybe I am not known to them
Hope you understand. Thank you.
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Have you seen this CM 11? https://forum.xda-developers.com/galaxy-tab-2/7-inch-development/rom-cm-11-0-galaxy-tab-2-t3737392
Just made last month by @Deltadroid
Links are removed because *the ROM is not complete yet*.
Thanks, but I need to confirm a few things before I could use a ROM(includes init.d support and a bunch of other things). Also, it is very important that deltadroid provide me permission to use his ROM.
Thank you!
Regards,
KG
-----_edit_--------
I just saw deltadroid's thread, the title clearly says that the ROM is for p3110. I want to make a unified one. I need a ROM made with unified device tree.
If I do port, it will only work on p3110 and maybe on every 7" device. I don't want do this.
Sorry, but yeah thanks!
Just wait till 3 april 2018. Most probably I will upload.
Edit 2
Or I must say it an update. 75 percent of the work is done. Somehow I managed to get a base ROM(only I know how). Only build.prop editing and Updater script editing work left(these are the most difficult BTW).
Update coming soon. Stay tuned.
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Kunal Gautam said:
I've updated the links. I've uploaded the new ROM. I've done with porting(i guess). I've used a lot of time.
Flash and review!
Click to expand...
Click to collapse
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
secretwolf98 said:
No wonder the ROM doesn't work.... Security patch is in a wrong format.
"ro.build.version.security_patch=2080-17-March"
It should be, "ro.build.version.security_patch=2018-03-01"
or,
"ro.build.version.security_patch=2018-03-05"
And this, hardly doubt this will work, but idk.
"ro.build.date.utc=999999999999"
Mistakes....................
EDIT**** Build id should be the app id: example lets say the id is 678, on build.prop, it would say 678.
you have, "ro.build.id=KUNAL"
Click to expand...
Click to collapse
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Kunal Gautam said:
You, sir, definitely have a lot to offer. I am afraid that this is not the actual problem. By now, I surely understand the importance of logs. Would be very helpful if someone could arrange me them.
And about your post it seemed really rude, raw, insulting and manipulating to me. But however, helpful. It makes it really hard to continue developing for a 6 years old Tab, with hardware that has nothing to offer in 2018. At least, I am trying.
Since, this was an Alpha build(because I moved sources) these problems are sure to arise. I did the same(build.prop things) with my kinda successful ROM MIUI 5(see it in the 7" forums).
I guess you haven't tasted port ROMs yet. They are hard to build. Alike your compiling ones, you have source, type some commands, turn your computer on for about 5 hours, when done upload it.
I am sure you must have did trail and error (in chemistry and math) porting ROMs is just the same. I am sure, that as a developer, you must know what logs actually mean.
But whatever, thank you for you review(insult I guess).
Click to expand...
Click to collapse
FYI, I port ROMs. It was pointers what to fix, if you wanted to get this ROM better, than it is already.
Kunal Gautam said:
(...)
P.S. - Android-Andi if you read this please reply. You are the only one who can help me(by providing me permissions to use your ROM as a base).
With best regards,
Kunal Gautam
Click to expand...
Click to collapse
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Android-Andi said:
Sorry, I won't give permissions after different people used my ROMs as base in the past without permissions. Hope there is a learning affect....
Since i love OpenSource: Sources are available on every official GitHub (slim, Omni, Lineage, UA) and up to date (note: I wouldn't have to do this, I could keep all device trees private but I am updating them for everyone - always). You'll have to compile your own base ROM to use for such port ROMs (I am not a fan of).
Click to expand...
Click to collapse
Thank you. For at least replying. You works will always be appreciated. Now, I am gonna close this thread. Thanks again!
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