[Galaxy Tab 3 General] r2d23cpo:
IMPORTANT This is in fact real risky, if you do not have the skill to recover from a failure PLEASE DO NOT USE THE FOLLOWING FILES. As always you and only you are responsible for what you introduce to your device. You been warned.

You need to be rooted.

Please backup everything before you do anything.

I use TWRP usually, I guess any of the others can backup your original own boot.img

I suggest you make a copy of your own boot.img. Remember once you introduce a new boot.img for test the only way to go back is to reestablish your own original.

To make an image that can be use by zip update or Odin you need to make a copy first. I use the following command in terminal or "adb shell"

dd if=/dev/block/mmcblk0p10 of=/sdcard/boot.img bs=4096

You will end up with a file in your internal sdcard called "boot.img". Quickly copy the file in to your PC and I even suggest you zip the file. Ziping a file give you some protection. It when open it will tell you if the file is corrupted!.

For those of you that get in trouble I will place the following boot.img for 4.2.2 & 4.4.2 in zip update packages. To my best understanding they are the correct. At least I use the 4.2.2 with no trouble.

Stock_P5210_4.2.2_boot.img.zip 7.6 MB

h__ps://mega.co.nz/#!qFsUDSQZ!8nfzmySNCqFqlUJ0HQyhb2dWjQK6pObPTZDnQDUMGT4

Stock_P5210_4.4.2_boot.img.zip 16.0 MB

h__ps://mega.co.nz/#!ic1GjLSa!qEVgD-mUwADDI26K0gq_5c1dVNKf0YBX5tbTw5noFBY

And the following is the test image I am using. Please make note

IT DOES NOT WORK AS INTENDED YET

. It is posted just for the one that may have the knowledge and can help. Or for those that just want to open the Image and look at the files or what I am doing. If you installed the screen will show only the Samsung Galaxy TAB3. But you can do "adb shell".

alien-kexecboot-022.zip 16.0 MB

h__ps://mega.co.nz/#!3MM0CJJC!7dgUptI8NGQbHUjijW2kEZjv7LJq88q_VbGTeUdlDww

Ahaaaaa. To have adb you may need need to have your google driver modified and installed. Please check if it work first. Mine did not work.

The drives is with your sdk instalation. In my case that I have 64Bit driver is at sdk folder

C:\Users\<username>\AppData\Local\Android\android-sdk\extras\google\usb_driver\android_winusb.inf

So first make a copy of the driver android_winusb.inf to android_winusb.inf.bck

Then open android_winusb.inf and you need to add what is in blue. If you see we are placing the same info in to places. One for 32bit system and the other for 64 bit.

I have place the labels [Google.NTx86] & [Google.NTamd64] and you can see the **** clearly meaning a lot of data. You can place the info in after [Google.NTx86] & the other after [Google.NTamd64]. I did at the end of each section. Here is my example.

[Google.NTx86]

***

[COLOR="Blue"];Galaxy Tab3 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0224
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0224&MI_01[/COLOR]

[Google.NTamd64]

and

[Google.NTamd64]

***

[COLOR="Blue"]
;Galaxy Tab3 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0224
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_0224&MI_01[/COLOR]

[USB_Install]

To install you place your device in recovery TWRP, I guess CWM and Philss have this too but I have not tested.

hock the cable to the pc

Then you need to go to Device Manager in your PC and look for the USB driver that have no install correctly. In fact you PC may been looking for the driver.

Well you go to the usb device and request a "Update Driver" or "Install Driver" then you point to your modded file

C:\Users\<username>\AppData\Local\Android\android-sdk\extras\google\usb_driver\android_winusb.inf.

After that you should be able to work in adb shell in recovery.