Database Develop

[REPO][DEV] CyanogenMod 12 for GALAXY Grand Prime

</> Developpers Only </>
As you may know it, GALAXY Grand Prime is powered by a 64Bit Entry-Level Quad Core CPU, that makes developpment on this device VERY HARD It's like Intel Atom Processors
Anyway, I tried to make a repo for building TWRP GALAXY Grand Prime by refering to Huawei G620S' Repo by GitHub member "EloYGomeZ" BIG thanks to him.
If you're interested in building TWRP, you can use this repo. Feel free to use it, but please remember to give credits when done.
The Repo isn't yet done, it may contains many bugs and errors; plus I can't test it or test a TWRP build since I don't have my hand on that device (should have one in 2 weeks).
Update as of 18/6/2015: TWRP has been compiled for Grand Prime
TWRP ==> http://forum.xda-developers.com/grand-prime/development/share-twrp-2-8-4-0-galaxy-prime-t3064506
Philz Touch :
Download ==> https://mega.co.nz/#!SQ8XkIiI!Kj_9rhfVY8bz0nRjZGDGra4Bs3Nen-87O4vhWGHlVzc
Thread ==> http://forum.xda-developers.com/gra...share-galaxy-grand-prime-sm-g530h-f0-t3057571
Source ==> http://www.phonandroid.com/forum/ph...d-galaxy-grand-prime-sm-g530f-fz-t116883.html
Current CM12 ETA:​- Compiled successfully
- Bootable
- CanNOT get to home launcher!
GitHub an sources:
@K_TECH 's device tree and all sources needed to compile cm12 ==> https://github.com/fortunave3gxx
fortuna3g TWRP Repo ==> https://github.com/Nonta72/fortuna3g-twrp (mine)
Huawei G620S TWRP Repo (used as a reference): https://github.com/Nonta72/android_device_huawei_g620s-twrp (EloYGomeZ)
Device Tree (WIP): https://github.com/Nonta72/fortuna3g-tree (mine)
Source Code for KK: http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=SM-G530​

Wow great,
IMO, its not about 64bit chipset, as we know, lenovo a6000/k30 have the same chipset 64bit.
But have development, we have CWM, Phillz recovery, cm11, MIUI rom
The main problem to devevelop grand prime is qualcomm secure bootloader that protect the device. We need to disable the secure bootloader first. CMIIW

Shinkumara said:
Wow great,
IMO, its not about 64bit chipset, as we know, lenovo a6000/k30 have the same chipset 64bit.
But have development, we have CWM, Phillz recovery, cm11, MIUI rom
The main problem to devevelop grand prime is qualcomm secure bootloader that protect the device. We need to disable the secure bootloader first. CMIIW
Click to expand...
Click to collapse
I didn't see Lenovo a6000 CWM/TWRP and Custom ROMs yet.
About Bootloader on Grand Prime, I never heard about this
Maybe we should start unlocking this 1st
I can't do anything as of now, since I don't have the decice yet.

i hope i can learn somewhere how to build twrp. Anyway i will support u guys.

Samir96 said:
i hope i can learn somewhere how to build twrp. Anyway i will support u guys.
Click to expand...
Click to collapse
If you think you can be tester and don't care about flashing your phone at least twice a day, then you can help!

can you please fix it. recently i don't have the device. building cm 11

nilimahona said:
can you please fix it. recently i don't have the device. building cm 11
Click to expand...
Click to collapse
What's the problem with the BoardConfig ?
PS: I also don't own the device yet.
The board config should be in KK Kernel source.

I'll test extensively I have 8 sm-g530az (cricket USA)
All rooted with cwm philz recovery
Nonta72 said:
If you think you can be tester and don't care about flashing your phone at least twice a day, then you can help!
Click to expand...
Click to collapse

krazy_smokezalot said:
I'll test extensively I have 8 sm-g530az (cricket USA)
All rooted with cwm philz recovery
Click to expand...
Click to collapse
The device already have CWM.
All you need now is CyanogenMod.

Nonta72 said:
The device already have CWM.
All you need now is CyanogenMod.
Click to expand...
Click to collapse
Would you know if anyone has started on that project?

krazy_smokezalot said:
Would you know if anyone has started on that project?
Click to expand...
Click to collapse
I already started, currently getting the device tree ready.

Lets start ^_^
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I'm getting stuck in this error :3
source: http://github.com/fortunave3gxx

Try "apt-cache search audio_defs.h" to find the dev package that is missing. Sometimes it work
Sent from my SM-G530FZ using XDA Free mobile app

kentone said:
Try "apt-cache search audio_defs.h" to find the dev package that is missing. Sometimes it work
Sent from my SM-G530FZ using XDA Free mobile app
Click to expand...
Click to collapse
Nevermind, i solved that errors in an hour ago ^_^

The build progress has been done, but i get an error when i try to flash it"binnary error". And it's come from recovery
If it ready, i'll upload my device configuration, Stay tuned
my own source: http://github.com/fortunave3gxx

K_TECH said:
The build progress has been done, but i get an error when i try to flash it"binnary error". And it's come from recovery
If it ready, i'll upload my device configuration, Stay tuned
my own source: http://github.com/fortunave3gxx
Click to expand...
Click to collapse
try to replace the update-binary in META-INF folder

The you can building kernel from source code boeffla working with grand prime ... kernel boeffla is 1 of the famous kernel. if you are building is too good. I very much hope into you. Thx you

Nonta72 said:
try to replace the update-binary in META-INF folder
Click to expand...
Click to collapse
Can you share your update-binary?

recoman said:
The you can building kernel from source code boeffla working with grand prime ... kernel boeffla is 1 of the famous kernel. if you are building is too good. I very much hope into you. Thx you
Click to expand...
Click to collapse
I don't think Lord Boeffla does support the Grand Prime.
K_TECH said:
Can you share your update-binary?
Click to expand...
Click to collapse
I'd love to, but I don't have the device yet. That's why I even stopped the project.
Suggestion: try to find a similar device (same chipset) that have CM or a CWM ROM, download that ROM and replace your binary with the one in that ROM. I heard the Huawei G620S (with MSM8916) have a working CyanogenMod, you may want to check that out.
Suggestion 2: make sure your updater-script is well formed, I can help you with that if needed, just upload that file.

[ROM][6.0.1]LineageOS 13[KRACK & BlueBorne patch][MAR-18]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi there, everybody! I am still using Marshmallow on my phone for various reasons. But the latest clean Lineage 13 that we have is with March 2017 security patches - so it is quite old now. I saw that there is a new MM ROM in XDA - the Lineage OS 13 with MicroG patch one. But when I saw what MicroG is, I really didn't even think about flashing this ROM - I am not privacy-concerned because all the Google services are useful to me, and I don't like using custom kernels on Lineage. The stock one works the best for me.
So for people like me - who like the clean Lineage and don't want to have any issues with Google Services, I built a Lineage 13 from Source with the latest security patches from Google.
Again, I am not telling you the ROM with MicroG patch is bad. It's actually a pretty great ROM. I'm just uploading this one, so that people like you have choices - either flash this clean one, or the one with the MicroG patch.
It has root built in. You can find it in the developer options. No need to flash the extra ZIP.
ChangeLog:
Version 20180319:
Updated Lineage sources (including new fixes, improvements, etc.)
Theoretically should work better
1 March 2018 security patch
Using Squid Kernel 22b by default
Version 20171115:
Initial booting Release
Contains KRACK fix and BlueBorne fix
Rooted by default
Installation:
Download the ROM from the downloads tab on the top of this thread
Download OpenGAPPS (or other ones which work with Lineage)
Wipe the Data, Cache and Dalvik (ART Cache)
Flash the ROM
Flash the GAPPS (optional)
Reboot and enjoy!
Important:
Each build of this ROM is made via the Windows 10 Subsytem for Linux. If anyone has problems with building Android on WSL, simply PM me and I'll be glad to help you.
XDA:DevDB Information
LineageOS 13 (2018), ROM for the Moto G 2015
Contributors
nicolasmart, squid2, CyanogenMod (formely Lineage)
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.x
Based On: Lineage OS
Version Information
Status: Stable
Current Stable Version: 2017-11-05
Stable Release Date: 2017-11-05
Created 2017-11-05
Last Updated 2018-03-19

Nice initiative.. Is VOLTE is added in this ?

rahul9999 said:
Nice initiative.. Is VOLTE is added in this ?
Click to expand...
Click to collapse
I don't personally use VoLTE since my carrier doesn't have it yet. It should be there but I can't really test it out, so I would wait for you to tell me.

nicolasmart said:
I don't personally use VoLTE since my carrier doesn't have it yet. It should be there but I can't really test it out, so I would wait for you to tell me.
Click to expand...
Click to collapse
I would like to test but not possible for me.. hope someone confirm this..

I have a problem here in instalation.
The rom does not start. It stays on the first screen and nothing happens.

the ROM has a problem and is that it does not start when we just installed it, I hope and fix it, great.

ive been using this room for a few days and had no problems, the security patch level says October 1st though.

ironzy said:
ive been using this room for a few days and had no problems, the security patch level says October 1st though.
Click to expand...
Click to collapse
Whaat? It works for you? I can't get my device to boot on my own ROM XD. What SKU are you using? I'm on XT1451

nicolasmart said:
Whaat? It works for you? I can't get my device to boot on my own ROM XD. What SKU are you using? I'm on XT1451
Click to expand...
Click to collapse
not sure what SKU means, I flashed the squid kernel after flashing the rom and it all works fine, the battery life is awesome.

ironzy said:
not sure what SKU means, I flashed the squid kernel after flashing the rom and it all works fine, the battery life is awesome.
Click to expand...
Click to collapse
He mean to say which variant you're on.. like I'm on XT 1550 2GB Ram.. If you dont know how to check this then just remove back cover of you're phone & see Model no. mentioned..

rahul9999 said:
He mean to say which variant you're on.. like I'm on XT 1550 2GB Ram.. If you dont know how to check this then just remove back cover of you're phone & see Model no. mentioned..
Click to expand...
Click to collapse
xt1541

Im using LineageOS 13 25/05/2017 build. Please, can you update the same for Moto G3-TE (merlin).
My SKU (XT1557) .
Thanks in advance:laugh:

ironzy said:
ive been using this room for a few days and had no problems, the security patch level says October 1st though.
Click to expand...
Click to collapse
wft, ami does not work for me, it stays in the moto logo and does not advance.
I have the xt1540

Erick_Summer said:
wft, ami does not work for me, it stays in the moto logo and does not advance.
I have the xt1540
Click to expand...
Click to collapse
try doing a full wipe then flashing the rom and then the squid kernel, that's the way I installed it and it works fine.

ironzy said:
try doing a full wipe then flashing the rom and then the squid kernel, that's the way I installed it and it works fine.
Click to expand...
Click to collapse
Ooooh!!! I know why it works for you!! You changed the kernel! My kernel is just bad!!! OK. Replacing it with stock Squid Kernel

Project Update
Old build deleted. The new one is coming up tomorrow.

nicolasmart said:
Old build deleted. The new one is coming up tomorrow.
Click to expand...
Click to collapse
you compiled it wrong this time, it gives error when installing it by recovery

Erick_Summer said:
you compiled it wrong this time, it gives error when installing it by recovery
Click to expand...
Click to collapse
the rom doesn't install on the latest twrp

Erick_Summer said:
you compiled it wrong this time, it gives error when installing it by recovery
Click to expand...
Click to collapse
ironzy said:
the rom doesn't install on the latest twrp
Click to expand...
Click to collapse
The ROM is installable with twrp-osprey-3.1.1-r1, the newer version adds support for newer android version. I guess it also means dropping support for older version of android. But again this ROM doesn't boot for me even after flashing was successful.

ajaysingh23 said:
The ROM is installable with twrp-osprey-3.1.1-r1, the newer version adds support for newer android version. I guess it also means dropping support for older version of android. But again this ROM doesn't boot for me even after flashing was successful.
Click to expand...
Click to collapse
support wasn't dropped for older versions of android, the rom just needs changing to work with the new twrp, the micro g version installs fine on the latest twrp.

[KERNEL][FIRE G5] Zest Kernel reBORN 🍋 - May - CM12.1

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
*** Disclamer
Please behave responsibly and avoid thermonuclear war. I am
not responsible for any bricked devices, etc.
Introduction
This is Zest Kernel. It's an optimized kernel for our device which includes a few nifty features. Built, on every security update, you'll have the best of the best. Features will be listed below and shared, to the most of my ability, across all my supported devices. This isn't just my kernel it's yours too - request any features you like and I'll try to add them in. However, I'm also busy with studies so please don't ask for dumb stuff.
THIS DEVICE IS CURRENTLY A TESTING KERNEL AND MAY NOT WORK. BACKUP YOUR BOOT.IMG BEFOREHAND.
Click to expand...
Click to collapse
Features
Built on UBERnaro toolchain
High tickrate to avoid jitter
Lib optimisations
F2FS support
Click to expand...
Click to collapse
Installation instructions
* Flash via TWRP, or Franco Kernel Manager (needs testing for this device)
* Enjoy!
Click to expand...
Click to collapse
Download
Latest is available at ftp://ftp.lasterhub.me.
Click to expand...
Click to collapse
FAQ
Tag me in XDA's Amazon.. oh wait. There's no group (yet?). Just PM me for now.
Click to expand...
Click to collapse
Special Thanks To
Code:
* MTK for being retarded
​
XDA:DevDB Information
Zest Kernel Projecc, Kernel for the Amazon Fire
Contributors
LazerL0rd, ggow, k4y0z
Source Code: https://gitlab.com/ZKP/ford
Kernel Special Features:
Version Information
Status: Testing
Created 2019-05-28
Last Updated 2019-05-29

LazerL0rd said:
Last Updated 2019-05-28
Click to expand...
Click to collapse
Nice.
May I ask for a little safety step to be added. Someone here is gonna not read and try to flash this on 'Austin'
And your anykernel.sh has device check set at NO. (do.devicecheck=0). Maybe better to make it (do.devicecheck=1)

Hi, On top of latest lineage rom, it gave me bootloop. Reflashing stock boot image fixed. Is it me or it's still under development?

newinnov said:
Hi, On top of latest lineage rom, it gave me bootloop. Reflashing stock boot image fixed. Is it me or it's still under development?
Click to expand...
Click to collapse
Austin or ford?

Rortiz2 said:
Austin or ford?
Click to expand...
Click to collapse
Ford 2015 it is

mrmazak said:
Nice.
May I ask for a little safety step to be added. Someone here is gonna not read and try to flash this on 'Austin'
And your anykernel.sh has device check set at NO. (do.devicecheck=0). Maybe better to make it (do.devicecheck=1)
Click to expand...
Click to collapse
Ah, yes. Weirdly some TWRPs react funnily to this command so on-release I always leave it off. Seems there's only one TWRP here tho. Thanks, will do :highfive:.

newinnov said:
Hi, On top of latest lineage rom, it gave me bootloop. Reflashing stock boot image fixed. Is it me or it's still under development?
Click to expand...
Click to collapse
The kernel seems to be pretty much correct, it's the flashing procedure that I'm uncertain of. It's the same base kernel @ggow uses with some building fixes and my additions. But yes, this is a development kernel until anyone can actually get it working with the patch.

LazerL0rd said:
The kernel seems to be pretty much correct, it's the flashing procedure that I'm uncertain of. It's the same base kernel @ggow uses with some building fixes and my additions. But yes, this is a development kernel until anyone can actually get it working with the patch.
Click to expand...
Click to collapse
I had a stock built kernel from unmodified Amazon source, and installed it with anykernel, before I discontinued the project. @ggow showed me up. Way up, by making his kernel free from that Amazon log feature.
Anyway anykernel flashes this device with the exploit no problem.
Think I had used anykernel 2 though. You have used 3.
I will look again, and see if I see any difference in the scripts.
EDIT:
I just tried to flash with the anykernel2 script i had used before. And result was bootlooping on the Amazon logo.

mrmazak said:
I had a stock built kernel from unmodified Amazon source, and installed it with anykernel, before I discontinued the project. @ggow showed me up. Way up, by making his kernel free from that Amazon log feature.
Anyway anykernel flashes this device with the exploit no problem.
Think I had used anykernel 2 though. You have used 3.
I will look again, and see if I see any difference in the scripts.
EDIT:
I just tried to flash with the anykernel2 script i had used before. And result was bootlooping on the Amazon logo.
Click to expand...
Click to collapse
I tried both AK2 and AK3 with osm0sis seeing no issues in my AK configuration, so it’s not that.
Yah, I think something was changed and some sort of check was added in. I think I tried dm-verity disabling too but I may be wrong. My kernel is available at https://lasterhub.me/zk.html for anyone to try though ( click menu then BETA before selecting as no release version was released yet ).

I can't get the link to work? This ded?

beynolds.rurt said:
I can't get the link to work? This ded?
Click to expand...
Click to collapse
Yes. This is dead. OP never followed up after he was told this did not work as claimed.

mrmazak said:
Yes. This is dead. OP never followed up after he was told this did not work as claimed.
Click to expand...
Click to collapse
Knew it was too good to be true

Question S21 Ultra [Exynos]: Building a custom kernel

Hello, I am trying to build and run a custom kernel on S21 Ultra Exynos (SM-G998B). Reason: support permissive SELinux policy.
I am running AUF6 firmware, downloaded AUF6 kernel source from Samsung, followed the included build instructions and with unmodified sources, ran included `build_kernel.sh `, and created a boot.img using AIK, and flashed the resulting .img file via TWRP.
Rebooting into system, the phone is stuck on displaying the boot logo. Reading /proc/last_kmsg through TWRP, logging stops right after 'Starting kernel...' message. At this point I am not sure what else I can do to resolve this. Please help.
P.S. my compiled Image size is 26M, while stock is 28M.
The tutorial I followed: https://pucarasec.wordpress.com/2020/06/16/debugging-the-samsung-android-kernel-part-2/
Another post with trying to build S21 kernel, with outcome, similar to mine: https://groups.google.com/g/android-platform/c/ljRkDbBE0lE/m/mr4MM0WGCAAJ

mzakharocsc said:
Hello, I am trying to build and run a custom kernel on S21 Ultra Exynos (SM-G998B). Reason: support permissive SELinux policy.
I am running AUF6 firmware, downloaded AUF6 kernel source from Samsung, followed the included build instructions and with unmodified sources, ran included `build_kernel.sh `, and created a boot.img using AIK, and flashed the resulting .img file via TWRP.
Rebooting into system, the phone is stuck on displaying the boot logo. Reading /proc/last_kmsg through TWRP, logging stops right after 'Starting kernel...' message. At this point I am not sure what else I can do to resolve this. Please help.
P.S. my compiled Image size is 26M, while stock is 28M.
The tutorial I followed: https://pucarasec.wordpress.com/2020/06/16/debugging-the-samsung-android-kernel-part-2/
Another post with trying to build S21 kernel, with outcome, similar to mine: https://groups.google.com/g/android-platform/c/ljRkDbBE0lE/m/mr4MM0WGCAAJ
Click to expand...
Click to collapse
I'm sure you know this already, but there's a magisk module that does that already.
If I was to build a kernel I would try and definitely build something that has smoother performance or slightly better battery life.

Keep up the efforts. It is a shame there are no custom kernels for the phone...

Burt Squirtz said:
I'm sure you know this already, but there's a magisk module that does that already.
Click to expand...
Click to collapse
If you are talking about this: https://github.com/evdenis/selinux_permissive , then having tried it it did not work. On their own XDA thread, they state 'The module will not work if your kernel compiled with always enforcing config, e.g., stock samsung kernels. It's not possible to enable permissive mode on such kernels'. Unless I am missing something here?

Ok. I managed to install a custom kernel. There is already one in development here: https://github.com/mohammad92/android_kernel_samsung_exynos2100
Here are the steps I took.
1. Downgraded firmware to 3AUDA.
2. I ran 'build_menu' script from the repository, and selected p3s target. Here, I ran into build errors, so I commented out 'export LLVM=1' from 'build_menu' script, and this produced a kernel image. While that matched original instructions from samsung kernel release, the result did not boot (same hang as before), so I put LLVM=1 back, and resolved build issues by installing clang on my host system. It seems like LLVM=1 is the trick here, as I now have a working custom kernel, and it is 'permissive'. Perfect. Attached is the zip file to be installed with TWRP.

mzakharocsc said:
Ok. I managed to install a custom kernel. There is already one in development here: https://github.com/mohammad92/android_kernel_samsung_exynos2100
Here are the steps I took.
1. Downgraded firmware to 3AUDA.
2. I ran 'build_menu' script from the repository, and selected p3s target. Here, I ran into build errors, so I commented out 'export LLVM=1' from 'build_menu' script, and this produced a kernel image. While that matched original instructions from samsung kernel release, the result did not boot (same hang as before), so I put LLVM=1 back, and resolved build issues by installing clang on my host system. It seems like LLVM=1 is the trick here, as I now have a working custom kernel, and it is 'permissive'. Perfect. Attached is the zip file to be installed with TWRP.
Click to expand...
Click to collapse
commenting that line will brake your image, we need llvm to make bootable kernel.

afaneh92 said:
commenting that line will brake your image, we need llvm to make bootable kernel.
Click to expand...
Click to collapse
Makes sense, however, this 'export LLVM=1' line is not present in the samsung's official build instructions that come with the kernel zip. Nor have I found any mention of this flag on any of the kernel building tutorials online and on this forum. Maybe I missed something, but this looks non-obvious for someone new to this.

mzakharocsc said:
Makes sense, however, this 'export LLVM=1' line is not present in the samsung's official build instructions that come with the kernel zip. Nor have I found any mention of this flag on any of the kernel building tutorials online and on this forum. Maybe I missed something, but this looks non-obvious for someone new to this.
Click to expand...
Click to collapse
By reading Makefile you can find it there.

afaneh92 said:
By reading Makefile you can find it there.
Click to expand...
Click to collapse
Yeah, I read the makefile. LLVM flag is supported there, but unset/unused by default, resulting in corrupt images. and you have to somehow know that you need to set it externally.

If someone build a good custom kernel wich improves battery and performance i will donate 100 usd

I want custom kernels too.
Would it be possible to make a bounty?
I'm interested in battery, hackability, booting time, stability and performance.

songoku1 said:
If someone build a good custom kernel wich improves battery and performance i will donate 100 usd
Click to expand...
Click to collapse
Are there some official XDA bounty program for this stuff?

timofonic said:
Are there some official XDA bounty program for this stuff?
Click to expand...
Click to collapse
Sadly no on my oneplus i use arter kernel and i absolutely lovibg it. Sadly for my s21u there isnt one :/

What's more important now is to stress samsung's opensource service to release the AUG4 kernel source

DaReDeViL said:
What's more important now is to stress samsung's opensource service to release the AUG4 kernel source
Click to expand...
Click to collapse
Already requested it.

interested in a custom kernel also, it's already a very good device but battery life needs to be better

afaneh92 said:
Already requested it.
Click to expand...
Click to collapse
Got it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

DaReDeViL said:
Got it
View attachment 5368845
Click to expand...
Click to collapse
I will rebase my kernel soon

Ok
DaReDeViL said:
Got it
View attachment 5368845
Click to expand...
Click to collapse
Hope we will see a custom kernel soon

Any news?

[RECOVERY] TWRP for lt02 (SM-T210(R)/SM-T211)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project Official
For SM-T210(R)/SM-T211 (lt02)
USE AT YOUR OWN RISK!
Please make sure to this thread if you like the port! ​
ISSUES
Temperature is not available because the kernel does not support it.
Google apps install does not work (Fixed in latest nightly release!)
DOWNLOADS
All nightly releases are on our build repository. DOWNLOAD
All standard releases are on the TWRP website. DOWNLOAD
LINKS
Source Code
Discord Server
CREDITS
@Jespert
@TriDiscord
@gr8nole
@ketut.kumajaya
@paziusss
@ruben15prd

Reserved -

Thanks for maintaining TWRP for this almost 9 year old tablet! It's about time it gets official support. Works perfectly on my SM-T2105.

Just as a heads up, any installers that check for the correct device before installing using the "assert(getprop("ro.product.device")" line in the install script may give an error since you have the product showing as "lt02" (as opposed to lt02wifi, lt023g, etc.) for this recovery. Won't likely be an issue unless someone gets a device-specific version of a source built rom working (Lineage, Omni, etc.). Most customized versions of stock-based roms won't have that line in the install script.

gr8nole said:
Just as a heads up, any installers that check for the correct device before installing using the "assert(getprop("ro.product.device")" line in the install script may give an error since you have the product showing as "lt02" (as opposed to lt02wifi, lt023g, etc.) for this recovery. Won't likely be an issue unless someone gets a device-specific version of a source built rom working (Lineage, Omni, etc.). Most customized versions of stock-based roms won't have that line in the install script.
Click to expand...
Click to collapse
We'll probably never get a custom ROM except for modified stock ones anyways lol.

throwaway019299292 said:
We'll probably never get a custom ROM except for modified stock ones anyways lol.
Click to expand...
Click to collapse
CM11 exist, there are plans to fix bugs.

throwaway019299292 said:
We'll probably never get a custom ROM except for modified stock ones anyways lol.
Click to expand...
Click to collapse
uhh, cyanogenmod 11 recieved its last update for this tablet 7 years ago, so it's been around for a damn long time

gr8nole said:
Just as a heads up, any installers that check for the correct device before installing using the "assert(getprop("ro.product.device")" line in the install script may give an error since you have the product showing as "lt02" (as opposed to lt02wifi, lt023g, etc.) for this recovery. Won't likely be an issue unless someone gets a device-specific version of a source built rom working (Lineage, Omni, etc.). Most customized versions of stock-based roms won't have that line in the install script.
Click to expand...
Click to collapse
ROMs should support the `TARGET_OTA_ASSERT_DEVICE` flag if they're building for multiple devices. Will remove the `lt02` from that, though. Let me know if you have any other codenames for the Tab 3 7.0

TriDiscord said:
ROMs should support the `TARGET_OTA_ASSERT_DEVICE` flag if they're building for multiple devices. Will remove the `lt02` from that, though. Let me know if you have any other codenames for the Tab 3 7.0
Click to expand...
Click to collapse
SM-T2105 shows up as lt02kidswifi in the device field and lt02kidswifiue in the product field on the Device Info HW app.

throwaway019299292 said:
SM-T2105 shows up as lt02kidswifi in the device field and lt02kidswifiue in the product field on the Device Info HW app.
Click to expand...
Click to collapse
This is the line as the final result:
TARGET_OTA_ASSERT_DEVICE := lt02wifi,lt02wifijpn,lt02wifizc,lt02wifizs,lt02wifiue,lt02kidswifi,lt02kidswifiub,lt02kidswifiue,lt02kidswifiww,lt02kidswifixw,lt02kidswifizc,lt02kidswifizh
Will merge when other changes are completed. Thanks!

This has inspired me to TRY to create a custom rom for the T210R.
I'm trying diligently to make one based on CM 14.1.
Anyone have any ideas, I'm more than happy to collaborate.
Thanks for the recovery!

CaptainBenSisko said:
This has inspired me to TRY to create a custom rom for the T210R.
I'm trying diligently to make one based on CM 14.1.
Anyone have any ideas, I'm more than happy to collaborate.
Thanks for the recovery!
Click to expand...
Click to collapse
After a month... I don't know what I've gotten myself into. This is a royal pain to try to build a rom for.

CaptainBenSisko said:
After a month... I don't know what I've gotten myself into. This is a royal pain to try to build a rom for.
Click to expand...
Click to collapse
Hehe, I understand. It takes so much time.

CaptainBenSisko said:
After a month... I don't know what I've gotten myself into. This is a royal pain to try to build a rom for.
Click to expand...
Click to collapse
Any GitHub sources? We can maybe try to help?

TriDiscord said:
Any GitHub sources? We can maybe try to help?
Click to expand...
Click to collapse
These are what I was working with, all credit to the OP's. (Especially gr8nole, he seems to have his hand in all things T210R)
GitHub - lt02-dev/android_device_samsung_lt02wifi: Device Tree for Galaxy Tab 3 7.0 Wifi (lt02wifi)
Device Tree for Galaxy Tab 3 7.0 Wifi (lt02wifi). Contribute to lt02-dev/android_device_samsung_lt02wifi development by creating an account on GitHub.
github.com
GitHub - gr8nole/android_vendor_samsung_lt02wifi: Proprietary files for lt02wifi
Proprietary files for lt02wifi. Contribute to gr8nole/android_vendor_samsung_lt02wifi development by creating an account on GitHub.
github.com
sm-t210r / android_kernel_samsung_lt02 · GitLab
GitLab.com
gitlab.com
Don't fall down the rabbit hole, but if you wanna give it a go, I'm more than happy to collab.

CaptainBenSisko said:
These are what I was working with, all credit to the OP's. (Especially gr8nole, he seems to have his hand in all things T210R)
GitHub - lt02-dev/android_device_samsung_lt02wifi: Device Tree for Galaxy Tab 3 7.0 Wifi (lt02wifi)
Device Tree for Galaxy Tab 3 7.0 Wifi (lt02wifi). Contribute to lt02-dev/android_device_samsung_lt02wifi development by creating an account on GitHub.
github.com
GitHub - gr8nole/android_vendor_samsung_lt02wifi: Proprietary files for lt02wifi
Proprietary files for lt02wifi. Contribute to gr8nole/android_vendor_samsung_lt02wifi development by creating an account on GitHub.
github.com
sm-t210r / android_kernel_samsung_lt02 · GitLab
GitLab.com
gitlab.com
Don't fall down the rabbit hole, but if you wanna give it a go, I'm more than happy to collab.
Click to expand...
Click to collapse
Those are very buggy sources for CyanogenMod 11. I doubt that 14.1 will work on this.

@CaptainBenSisko, @TriDiscord, I tried building 14.1 for T210R this month using
https://github.com/SamsungGalaxyTab3
but ran into the exact same problem and error messages that the previous person @sscsps was getting in this thread
https://forum.xda-developers.com/t/abandoned-not-working-lineageos-14-1-for-t211.3621818/
There's no boot animation and my last_kmsg shows the same problem.

retiredtab said:
@CaptainBenSisko, @TriDiscord, I tried building 14.1 for T210R this month using
https://github.com/SamsungGalaxyTab3
but ran into the exact same problem and error messages that the previous person @sscsps was getting in this thread
https://forum.xda-developers.com/t/abandoned-not-working-lineageos-14-1-for-t211.3621818/
There's no boot animation and my last_kmsg shows the same problem.
Click to expand...
Click to collapse
I'm just curious, has anyone tried MM yet?

I think I found a guy who got lollipop to work on the t210r but it was canceled

HackerMan195 said:
I think I found a guy who got lollipop to work on the t210r but it was canceled
Click to expand...
Click to collapse
Ooh! Could you share a link?