[INFO][T31x] KitKat for Tab 3 8.0

Search This thread

ketut.kumajaya

Recognized Developer
Apr 28, 2011
4,935
14,132
Bekasi
KitKat update for Tab 3 8.0

T310:
http://www.sammobile.com/firmwares/1/?page=1&model=SM-T310&pcode=0#firmware
http://samsung-updates.com/device/?id=SM-T310
T311:
http://www.sammobile.com/firmwares/1/?page=1&model=SM-T311&pcode=0#firmware
http://samsung-updates.com/device/?id=SM-T311
T315:
http://www.sammobile.com/firmwares/1/?page=1&model=SM-T315&pcode=0#firmware
http://samsung-updates.com/device/?id=SM-T315


Kernel cmdline from KitKat bootloader:
console=ram loglevel=4 sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c [email protected] [email protected] [email protected] s3cfb.bootloaderfb=0x5ec00000 lcdtype=2049 consoleblank=0 lpj=3981312 vmalloc=176m oops=panic pmic_info=67 cordon=00000000000000000000000000000000 connie=SM-T311_OPEN_EUR_00000000000000000000000000000000 androidboot.emmc_checksum=3 androidboot.odin_download=1 androidboot.bootloader=T311XXXXXXX androidboot.selinux=enforcing androidboot.warranty_bit=0 androidboot.sec_atd.tty=/dev/ttySAC2 androidboot.serialno=0000000000000000 snd_soc_core.pmdown_time=1000

Kernel cmdline from JellyBean bootloader:
console=ram loglevel=4 sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c [email protected] s3cfb.bootloaderfb=0x5ec00000 lcdtype=2049 consoleblank=0 lpcharge=0 lpj=3981312 vmalloc=176m oops=panic pmic_info=67 cordon=00000000000000000000000000000000 connie=SM-T311_OPEN_EUR_00000000000000000000000000000000 androidboot.emmc_checksum=3 androidboot.odin_download=1 androidboot.bootloader=T311XXXXXXX androidboot.serialno=0000000000000000 snd_soc_core.pmdown_time=1000

Boot to LPM from KitKat bootloader:
In low power mode (LPM, low power charging), "androidboot.mode=charger" string added to kernel cmdline, with this string the init process will trigger "charger" action group in init.rc and init.<platform>.rc.

Boot to LPM from JellyBean bootloader:
In LPM, "lpcharge=1" string added to kernel cmdline, kernel parse this string and via a sysfs tell the init process to load lpm.rc

JellyBean/CM based ROM/kernel with KitKat bootloader:
No "lpcharge=1" string from the bootloader in LPM, no command from the kernel to load lpm.rc, kernel patch needed. Even with patched kernel, with "androidboot.mode=charger" in kernel cmdline, the init process avoid "early-fs" and "boot" actions group in lpm.rc, playlpm service not get started. Patch to lpm.rc needed.

KitKat based ROM/kernel with JellyBean bootloader:
No "androidboot.mode=charger" string from the bootloader in LPM, "charger" action group in init.rc and init.<platform>.rc not get triggered, lpm service not get started. Even with patched kernel, in KitKat the init process not aware to lpm.rc anymore. Kernel cmdline or init.rc hijacking before the init process started needed.

Root:
For me, the easiest method is flash NEXT kernel for T31x using Heimdall on a Linux host. Boot your device to download mode, connect it to your computer, and then run Heimdall.
Code:
sudo heimdall flash --BOOT boot.img
Install SuperSU from Play Store. KNOX popup disabler included in the latest SuperSU or manually using "pm disable com.sec.knox.seandroid" command as root.

User apps permission to write external SD card fix included in NEXT kernel as a patch, auto merged on boot if necessary.

Unofficial recovery:
As above, flash PhilZ Touch recovery for T31x using Heimdall.
Code:
sudo heimdall flash --RECOVERY recovery.img

FUSION package from NEXT kernel thread more friendly for Windows user. NEXT kernel, PhilZ Touch recovery, and needed blobs in one Odin flashable package.

More info later.

FOLLOW THIS INSTRUCTION AT YOUR OWN RISK!
 
Last edited:

ketut.kumajaya

Recognized Developer
Apr 28, 2011
4,935
14,132
Bekasi
No significant update, I have to fix my wife's washing machine first. No spare part but Zelio smart relay :laugh:

If you need FBD programming to control your washing machine, just ask me ;) Or maybe you want to control you home appliances wirelessly :D

attachment.php
 
Last edited:
  • Like
Reactions: duttyend

ketut.kumajaya

Recognized Developer
Apr 28, 2011
4,935
14,132
Bekasi
After create a Nandroid backup of my CM 11 ROM (1st ROM), without a reset, I accidentally "downgrade" it to Samsung 4.4.2 T311XXUBNHA XSE via Odin :laugh: :laugh: :laugh: A complete flash including modem and bootloader. Lost my SMS but no problem so far, no single FC, no random reboot but my CM 11 theme not applicable :laugh: :laugh: :laugh: My device status back to official, so our device unofficial status not permanently written. I'll flash NEXT kernel later.
 
Last edited:

ketut.kumajaya

Recognized Developer
Apr 28, 2011
4,935
14,132
Bekasi
Unfortunately NEXT 2.6.1 fail to root this stock ROM :( Immediately found the source of problem, I have to mount /system rw on boot https://github.com/kumajaya/android...ot.img/boot.img-ramdisk/sbin/fstab.sh#L56-L60 I also experienced a sudden reboot once after NEXT kernel installed :crying: No reboot so far after I disabled zswap.
No sudden reboot so far, even with zswap enabled, NEXT kernel 2.7. This NEXT version completely disable SELinux on Samsung 4.4.2 ROM.
 
  • Like
Reactions: reswin and gr8nole

manu12345

Member
Jun 25, 2014
12
0
Help

I have tried updating through odin but odin is not detecting the tab what i do how can i update it and i am running 4.2 and it is rooted it has TWRP so any idea how can i do it and will my files and app will format ???
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    KitKat update for Tab 3 8.0

    T310:
    http://www.sammobile.com/firmwares/1/?page=1&model=SM-T310&pcode=0#firmware
    http://samsung-updates.com/device/?id=SM-T310
    T311:
    http://www.sammobile.com/firmwares/1/?page=1&model=SM-T311&pcode=0#firmware
    http://samsung-updates.com/device/?id=SM-T311
    T315:
    http://www.sammobile.com/firmwares/1/?page=1&model=SM-T315&pcode=0#firmware
    http://samsung-updates.com/device/?id=SM-T315


    Kernel cmdline from KitKat bootloader:
    console=ram loglevel=4 sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c [email protected] [email protected] [email protected] s3cfb.bootloaderfb=0x5ec00000 lcdtype=2049 consoleblank=0 lpj=3981312 vmalloc=176m oops=panic pmic_info=67 cordon=00000000000000000000000000000000 connie=SM-T311_OPEN_EUR_00000000000000000000000000000000 androidboot.emmc_checksum=3 androidboot.odin_download=1 androidboot.bootloader=T311XXXXXXX androidboot.selinux=enforcing androidboot.warranty_bit=0 androidboot.sec_atd.tty=/dev/ttySAC2 androidboot.serialno=0000000000000000 snd_soc_core.pmdown_time=1000

    Kernel cmdline from JellyBean bootloader:
    console=ram loglevel=4 sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c [email protected] s3cfb.bootloaderfb=0x5ec00000 lcdtype=2049 consoleblank=0 lpcharge=0 lpj=3981312 vmalloc=176m oops=panic pmic_info=67 cordon=00000000000000000000000000000000 connie=SM-T311_OPEN_EUR_00000000000000000000000000000000 androidboot.emmc_checksum=3 androidboot.odin_download=1 androidboot.bootloader=T311XXXXXXX androidboot.serialno=0000000000000000 snd_soc_core.pmdown_time=1000

    Boot to LPM from KitKat bootloader:
    In low power mode (LPM, low power charging), "androidboot.mode=charger" string added to kernel cmdline, with this string the init process will trigger "charger" action group in init.rc and init.<platform>.rc.

    Boot to LPM from JellyBean bootloader:
    In LPM, "lpcharge=1" string added to kernel cmdline, kernel parse this string and via a sysfs tell the init process to load lpm.rc

    JellyBean/CM based ROM/kernel with KitKat bootloader:
    No "lpcharge=1" string from the bootloader in LPM, no command from the kernel to load lpm.rc, kernel patch needed. Even with patched kernel, with "androidboot.mode=charger" in kernel cmdline, the init process avoid "early-fs" and "boot" actions group in lpm.rc, playlpm service not get started. Patch to lpm.rc needed.

    KitKat based ROM/kernel with JellyBean bootloader:
    No "androidboot.mode=charger" string from the bootloader in LPM, "charger" action group in init.rc and init.<platform>.rc not get triggered, lpm service not get started. Even with patched kernel, in KitKat the init process not aware to lpm.rc anymore. Kernel cmdline or init.rc hijacking before the init process started needed.

    Root:
    For me, the easiest method is flash NEXT kernel for T31x using Heimdall on a Linux host. Boot your device to download mode, connect it to your computer, and then run Heimdall.
    Code:
    sudo heimdall flash --BOOT boot.img
    Install SuperSU from Play Store. KNOX popup disabler included in the latest SuperSU or manually using "pm disable com.sec.knox.seandroid" command as root.

    User apps permission to write external SD card fix included in NEXT kernel as a patch, auto merged on boot if necessary.

    Unofficial recovery:
    As above, flash PhilZ Touch recovery for T31x using Heimdall.
    Code:
    sudo heimdall flash --RECOVERY recovery.img

    FUSION package from NEXT kernel thread more friendly for Windows user. NEXT kernel, PhilZ Touch recovery, and needed blobs in one Odin flashable package.

    More info later.

    FOLLOW THIS INSTRUCTION AT YOUR OWN RISK!
    2
    Unfortunately NEXT 2.6.1 fail to root this stock ROM :( Immediately found the source of problem, I have to mount /system rw on boot https://github.com/kumajaya/android...ot.img/boot.img-ramdisk/sbin/fstab.sh#L56-L60 I also experienced a sudden reboot once after NEXT kernel installed :crying: No reboot so far after I disabled zswap.
    No sudden reboot so far, even with zswap enabled, NEXT kernel 2.7. This NEXT version completely disable SELinux on Samsung 4.4.2 ROM.
    1
    No significant update, I have to fix my wife's washing machine first. No spare part but Zelio smart relay :laugh:

    If you need FBD programming to control your washing machine, just ask me ;) Or maybe you want to control you home appliances wirelessly :D

    attachment.php
    1
    Thanks for yours donation @gr8nole :good: I'm still going in this Tab 3 community for some time, you are one of the reason, still satisfied with T311 is another reason.