Tab 3 8 official kikat update (T310) + root instrucions

[faria]

No, this is for T315 model (LTE). This is not the same as T311 (3G).

Anyway thanks for your reply!

HA, my mistake, Samsung and their numbering system makes me dizzy

 

[faria]

here, running latest cm build to date:

Well its official, custom kernels are supported!:laugh:
the only thing we cant change is the bootloader, but at this stage who cares!

Many thanks.

 

[faria]

Here is an unexpected suprise...
If you happen to flash cf-auto-root after flashing a custom recovery the device reverts back to official status:good:

Clearly samsung did not want their developers to waste much time in the firmware

 

[HavokbyName]

just wanted to clarify an earlier post i made, going back to 4.2 is possible if you have a backup of it in twrp or other recovery, i just restored a 4.2 system & boot image and everything works as normal, even goes back to 4.2 kernel, at least there is minimal issue with this release, full knox would have been a real headache

 

[smanq]

Here is an unexpected suprise...
If you happen to flash cf-auto-root after flashing a custom recovery the device reverts back to official status:good:

Clearly samsung did not want their developers to waste much time in the firmware

I'll try to recap for clarifying:
1. We can flash the stock 4.4.2 ROM through Odin
2. Now we can flash a custom recovery (TWRP_T31x_r3.tar)
3. We can finally flash cf-auto-root.
With this 3 steps we will have a TAB3 8.0 with stock 4.4.2, rooted, with custom recovery and official knox status, right?

 

[ketut.kumajaya]

Please give me KitKat "cat /proc/cmdline" output. Though I have experience making WiFi only ROM working on 3G device, for now I will patiently wait for Samsung release.

 

[ketut.kumajaya]

just wanted to clarify an earlier post i made, going back to 4.2 is possible if you have a backup of it in twrp or other recovery, i just restored a 4.2 system & boot image and everything works as normal, even goes back to 4.2 kernel, at least there is minimal issue with this release, full knox would have been a real headache

One possible minimal issue is offline charging will always reboot to normal mode.

 

[HavokbyName]

One possible minimal issue is offline charging will always reboot to normal mode.

yeah...

attempting to charge whilst device is powered down using old 4.2 with new bootloader results in a grey battery icon center screen with a static circle, static icon & screen never goes off, not so good, guess that's one issue just found using older release with new bootloader, so offline charging isn't so friendly

same goes for custom rom, just checked with cm11

with stock 4.4, it has no such issue, not surprising, offline charging acts normally with green battery filling up & loading animation, 5 dots

---

@ketut.kumajaya

here's kitkat "cat /proc/cmdline" output

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=540b54ba3baeca9400db9ee8ca8a55ca connie=SM-T310_OPEN_EUR_7de22521b2ab8773703e844dacabe390 androidboot.emmc_checksum=3 androidboot.odin_download=1 androidboot.bootloader=T310XXUBNE9 androidboot.selinux=enforcing androidboot.warranty_bit=0 androidboot.sec_atd.tty=/dev/ttySAC2 androidboot.serialno=000000000000000 snd_soc_core.pmdown_time=1000

 

[faria]

I'll try to recap for clarifying:
1. We can flash the stock 4.4.2 ROM through Odin
2. Now we can flash a custom recovery (TWRP_T31x_r3.tar)
3. We can finally flash cf-auto-root.
With this 3 steps we will have a TAB3 8.0 with stock 4.4.2, rooted, with custom recovery and official knox status, right?

Yes, but the custom recovery gets replaced by the one from cf-root that seems to be a officiant one.

 

[faria]

just wanted to clarify an earlier post i made, going back to 4.2 is possible if you have a backup of it in twrp or other recovery, i just restored a 4.2 system & boot image and everything works as normal, even goes back to 4.2 kernel, at least there is minimal issue with this release, full knox would have been a real headache

In that case then should be possible to downgrade to official 4.2 by simply removing the bootloader partition from the .tar file.

This is a 5 minute job in Linux with the right commands.

 

[thebestiam]

Can I manual update with this to kitkat??

Sent from my SM-T310 using XDA Free mobile app

 

[faria]

Can I manual update with this to kitkat??

Sent from my SM-T310 using XDA Free mobile app

Yes.

 

[faria]

New fetures

Anyone interested on this in their tablet?:laugh::laugh::laugh:
Ported Quick connect and s finder on tab 3 8.
Samsung actually did not include the feature in the kitkat update , in a device that actually has the hardware for it! Up yours SAMSUNG!

 

[Smokey Mc Pot]

Anyone interested on this in their tablet?:laugh::laugh::laugh:
Ported Quick connect and s finder on tab 3 8.
Samsung actually did not include the feature in the kitkat update , in a device that actually has the hardware for it! Up yours SAMSUNG!

Nice one!
Can you share the download links ?

Sent from my SM-T310 using Tapatalk

 

[faria]

Nice one!
Can you share the download links ?

Sent from my SM-T310 using Tapatalk

I'm still working on it, s finder is crashing, will upload a soon as I can.

 

[ketut.kumajaya]

@HavokbyName I found:
New entry:
[email protected]
[email protected]
androidboot.selinux=enforcing
androidboot.warranty_bit=0
androidboot.sec_atd.tty=/dev/ttySAC2

Missing entry:
lpcharge=0

lpcharge mean low power charging. Why no androidboot.mode there? CM kernel still compatible to the old bootloader https://github.com/kumajaya/android...mmit/97e454051b3364deafcc47a0e76a3a4fae29c356 but for the new bootloader, maybe init process need to be changed.

 

[HavokbyName]

@HavokbyName I found:
New entry:
[email protected]
[email protected]
androidboot.selinux=enforcing
androidboot.warranty_bit=0
androidboot.sec_atd.tty=/dev/ttySAC2

Missing entry:
lpcharge=0

lpcharge mean low power charging. Why no androidboot.mode there? CM kernel still compatible to the old bootloader https://github.com/kumajaya/android...mmit/97e454051b3364deafcc47a0e76a3a4fae29c356 but for the new bootloader, maybe init process need to be changed.

not sure, don't know much about this stuff, that was the full output from that file, are these related to the new bootloader or kernel?

 

[thebestiam]

Thanks for replying, By updating from Stock 4.2.2 to 4.4.2, Will i be able to keep ALL my data or it will reset the tablet?

 

[smanq]

Thanks for replying, By updating from Stock 4.2.2 to 4.4.2, Will i be able to keep ALL my data or it will reset the tablet?

Flashed stock 4.4.2 ROM (Odin) and I haven't lost my data and settings.

 

[thebestiam]

Flashed stock 4.4.2 ROM (Odin) and I haven't lost my data and settings.

Thanks , Was it rooted or anything?