[Galaxy Tab 3 10.1 Android Development] r2d23cpo:
[MENTION=4788780]Daniel-TAz00[/MENTION] First thanks. Nice work. But can you tell us if your "942MB" file is just the same

In particular it is VNC Linux on Android

Now I think [MENTION=5707708]Jacker31[/MENTION] is here for the fun of learning kernel compile and finding a way to implement "aircrack-ng/airmon-ng/airodump-ng" with TAB3 10.1 own Wifi and without Linux VNC. That is what I guess from his post.

Thanks goes to the Greatest creator [MENTION=4544860]osm0sis[/MENTION]. Last time he complains on me for saying it was another Kitchen. So NOOOO It is the best Kitchen in xda. I know all this nice applications get hidden on so many post. [MENTION=5864662]moonbutt74[/MENTION] was the one to point me to use AIK.

I will answer down

You see Jacker31 is trying to include the needed driver in a kernel. But that is only a step.

So, which modules Tab3 10.1 own wifi? If so you need to recall that first we need to modify our driver bcmdhd to allow promiscuous communication!

So I guess once you read this is going to be late, I was going you suggest to backup your own boot.img first! I do still you are a bit confuse it is not just ZIP!! see below

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

Yes, you see it is not just zip. In fact you need to make your own update.zip.

[MENTION=5707708]Jacker31[/MENTION]

1) So here is what you need to read. In this forum just search for "Edify", "updater script" and see how the script is build.

2) Please keep in mind that every device is different, in particular the partitions are in different places and in our case we are nor ARM but x86 or more technical we belong to the i686 family.

So if you unpack recovery.img an look inside the ramdiskfs you can find "/etc/recovery.fstab". By doing "cat /etc/recovery.fstab"

you will see

# mount point	fstype	device	[device2]
/config ext4 /dev/block/mmcblk0p3
/cache ext4 /dev/block/mmcblk0p6
/system ext4 /dev/block/mmcblk0p8
/data ext4 /dev/block/mmcblk0p9 length=-16384
/recovery emmc /dev/block/mmcblk0p11
/boot emmc /dev/block/mmcblk0p10
/external_sd vfat /dev/block/mmcblk1p1

This tells you that "boot" is at partition "/dev/block/mmcblk0p10" and "recovery" at "/dev/block/mmcblk0p11".

So a valid script to introduce your new boot.img may read

ui_print("+++++++++++++++++++++++");
ui_print(" Galaxy Tab 3 gt-p52xx ");
ui_print("+++++++++++++++++++++++");
#
ui_print("Flashing boot.img");
ui_print("+++++++++++++++++++++");
#
#
package_extract_file("[COLOR="Blue"]boot.img[/COLOR]", "[COLOR="Blue"]/dev/block/mmcblk0p10[/COLOR]");
#
ui_print("Done");
ui_print("+++++++++++++++++++++");

Now I am attaching a update.zip skeleton. The needed part is in "update.zip\META-INF\com\google\android". There you will find "update-binary" valid for our x86 device. Observe how it is about 521KB. The ARM one is just around 125KB! Easily to distinguish. This "update-binary" is the program that will interpret the Edify commands that are store in "updater-script". So the "updater-script" holds the instructions.

In it you will find also "update.zip\META-INF\com\android". With "metadata" holds signature information when signed. And "otacert" with in fact holds the signature for ota validation. This files are only required when the update.zip is signed!! But that another process meant for distribution that I am not going to explain. In general when we test we do not sign the updtate.zip instead we disable that in the recovery menu, so that recovery accepts update.zip packages that are not signed. So I had include those for you knowledge but you can delete them if you want.

So the last file is "update.zip\boot.img". This is the file you are going to substitute and that you want to program.

And yes making the package is as simple of zipping all. Here is the important detail. When you zip the file you need to be in the same directory as the boot.img file is. So that the update.zip created do not contain an extra folder. In other words, when you double click a good update.zip you find quickly boot.img and META-INF folder. No extra folders.

Now waitttttt. That is just for your general knowledge. If you do use this info it is at your own risk. It is easily to do something wrong and break the device.

Example, Make sure you have a FULL battery before doing any firmware programing. The Charging mechanism is in boot image. If you have a bad boot image programing, then your device will not charge and if you get out of juice then you end up with a nonchargeable devices. It will feel that the device is dead, since you only way to charge will be to open the device and charge the battery separately!!!