[ROM][4.4.2][TW] 100% stock 4.4.2 kitkat P5210 [Deodexed+Rooted build also available] - Galaxy Tab 3 10.1 Android Development

This is a 100% stock flashable zip of the recently released 4.4.2 firmware for the P5210. As it is 100% stock, it is fully bloated, odexed, and non-rooted. If you wish to attain root you can do so by flashing superSU-2.02 zip from chainfire. As of right now, no other root method appears to be working, including towelroot.
Download link below.
A deodexed + rooted build is also available. The deodexed / rooted build also has unsecure boot, courtesy of @moonbutt74
NOTE: if you flash the deodexed version and have problems with root, flash UPDATE-SuperSU-v2.02.zip from here. I don't anticipate any root problems, but just in case, this will fix it.
100% stock: STOCK-4.4.2-P5210(fixed).zip
deodexed + rooted: STOCK-ROOTED-DEODEXED-4.4.2-P5210(fixed).zip
Anyone may feel free to use this as a base for their ROM. I only ask that you give me credit.

---

finally
Now how sweet is this? Will flash it asap... (nasty CWM backup takes forever)

---

Restl3ss said:
This is a 100% stock flashable zip of the recently released 4.4.2 firmware for the P5210. As it is 100% stock, it is fully bloated, odexed, and non-rooted. If you wish to attain root you can do so by flashing superSU-1.9.4 zip from chainfire. As of right now, no other root method appears to be working, including towelroot.
Download link below.
A deodexed + rooted build will be ready soon, I'm just trying to iron out the kinks with the deodex script (about 10 apks seem to be fighting me)
Download: 100% stock P5210 4.4.2
Click to expand...
Click to collapse
I flashed this on top of Pimpdroid, and now I can use google now launcher in stock rom. Let me just imagine for a second that I achieved something impossible. And this is super fast! In a word, I am very happy.

---

I have a little problem when i try to install the kitkat update from samsung i get this error at the screenshot
{
"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"
}
[/IMG]
and when i try to flash your stock kitkat in twrp i get this: this is for the device santos10wifi your device is santos103g
but i am 100% sure i have the p5210

---

damian312 said:
I have a little problem when i try to install the kitkat update from samsung i get this error at the screenshot
[/IMG]
and when i try to flash your stock kitkat in twrp i get this: this is for the device santos10wifi your device is santos103g
but i am 100% sure i have the p5210
Click to expand...
Click to collapse
have the same error!

---

Try flashing with philz recovery instead of twrp, i find it works a LOT better

---

Restl3ss said:
Try flashing with philz recovery instead of twrp, i find it works a LOT better
Click to expand...
Click to collapse
Ok which version do i need and how do i install it because i can not flash it through twrp?

---

Can you flash (odin ) back to 4.2.2 after flashing this?

---

damian312 said:
Ok which version do i need and how do i install it because i can not flash it through twrp?
Click to expand...
Click to collapse
get philz from this thread. once you have it up, wipe data, cache, dalvik cache, system, and boot. Flash zip (should install fine). reboot. enjoy.

---

firestorm942 said:
Can you flash (odin ) back to 4.2.2 after flashing this?
Click to expand...
Click to collapse
don't know, haven't tried. Probably can, this isn't like the galaxy S family of phones with e-fuses

---

Actually, wait. I seem to be having problems with philz. Getting stuck on splash screen, had to Odin. hmm

---

Restl3ss said:
Actually, wait. I seem to be having problems with philz. Getting stuck on splash screen, had to Odin. hmm
Click to expand...
Click to collapse
if i try to flash philz it keep saying my device is santos103g and not santos10wifi
i have 100% sure gt-p5210 it is on the back of the tablet

---

damian312 said:
if i try to flash philz it keep saying my device is santos103g and not santos10wifi
i have 100% sure gt-p5210 it is on the back of the tablet
Click to expand...
Click to collapse
That's an extremely weird glitch. Try odining back to 4.2.2 and start over. Maybe try a different region firmware

---

Happening to me to...

---

Can't wait for the rooted build! I wonder though, since it is based on the Canadian release, will it contain the same language pack as the European devices?

---

VIRGIN KLM said:
Can't wait for the rooted build! I wonder though, since it is based on the Canadian release, will it contain the same language pack as the European devices?
Click to expand...
Click to collapse
Rooted / deodexed build will be up in about 15 minutes, it's uploading right now and at about 84%
Took enough work, this thing did NOT want to be deodexed. Took about 6 hours.
edit: it's up. enjoy

---

damian312 said:
if i try to flash philz it keep saying my device is santos103g and not santos10wifi
i have 100% sure gt-p5210 it is on the back of the tablet
Click to expand...
Click to collapse
Restl3ss said:
That's an extremely weird glitch. Try odining back to 4.2.2 and start over. Maybe try a different region firmware
Click to expand...
Click to collapse
firestorm942 said:
Happening to me to...
Click to expand...
Click to collapse
Then there is a missmatch between your recovery device name and the device name in the zip. I think your recovery is made with device name santos103g. and that doesn't work with a recovery script that searches for santos10wifi. So manually change name in the update-script to search for santos103g and u are good or the maker of the recovery needs to make a fix Or u flashed a recovery that works, but for another device

---

Hazou said:
Then there is a missmatch between your recovery device name and the device name in the zip. I think your recovery is made with device name santos103g. and that doesn't work with a recovery script that searches for santos10wifi. So manually change name in the update-script to search for santos103g and u are good or the maker of the recovery needs to make a fix Or u flashed a recovery that works, but for another device
Click to expand...
Click to collapse
i don't have enough knowledge to fix that
would you fix the recovery if i upload it?

---

Same issue runing CAG-mans latest ROM
The "update-script" contains the following:
assert(getprop("ro.product.device") == "santos10wifi" || getprop("ro.build.product") == "santos10wifi" || abort("This package is for \"santos10wifi\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("");
ui_print("+++++++++++++++++++++");
ui_print(" TWRP v-2.7.1.0 ");
ui_print("+++++++++++++++++++++");
ui_print("Galaxy Tab 3 gt-p5210");
ui_print("+++++++++++++++++++++");
#
ui_print("Flashing");
ui_print("+++++++++++++++++++++");
#
#
package_extract_file("recovery.img", "/dev/block/mmcblk0p11");
#
ui_print("Done");
ui_print("+++++++++++++++++++++");
EDIT: Did a full stock reflash in odin, then flashed TWRP 2.7 (the oen misslabled 2.6.3.0) in Odin.
Still same error when flashing TWRP-v2710-gtP-5210.zip in recovery.
Same issiu when trying to flash the PhilzAdvCWM.6_55_0-gtP-5210.zip in recovery
EDIT: Found an old CWM 6.0.2.8 and flashed it in Odin, From there I was able to flash the PhilzAdvCWM.6_55_0-gtP-5210.zip and it booted fine and from there the TWRP was flashable to.
EDIT: And now stuck on Sammy logo

---

on recovery and vendor
hey all,
my instructions to install recovery are clear. again, you must dd write cwm as it is not a flashable zip.
AFTER you have done that then you can flash philz or twrp because they are flashable zips.
this is a re-worked system/vendor directory http://d-h.st/kSw
to address samsung's strange use of symlinks in vendor/lib
the rom hangs at boot because after copy/rebuild to a flashable zip the symlinks in vendor directory get broken
this is not a flashable zip.
instructions extract the contents and drop them into your rom.zip. you should all be familiar with the android
directory structure. when prompted to overwrite, do so.
m