[Galaxy Tab 3 10.1 Android Development] dale_para_bajo:
First I am no Real Developer. So read an test what I say.

In fact this may be a known issue for real developers.

This belongs to GT-P5210

I found my self installing various Zip files in recovery mod that Failed!

After carefully study various ZIP files that work and comparing them with the ZIP files that does not, I found that the ones that work have the "update-binary" with size of 322,688 bytes and the ones that fail have only 194,636!

Tis is for those of you like me that are starting to learn how to develop.

Get an update file that work in P5210: For example go and get

http://roms.bindroid.com/downloads/viewcategory/11-stock

and download the file : no_bloatware_stock_rom.zip

Now using 7zip or any other compressor, go ahead and decompress the file. You will see the following folders: META-INF\com\google\android

Inside android there is a binary called: update-binary

that I understand interprets the commands inside the script called: updater-script

Is this update-binary the one I am talking about. This is 322,688 bytes!

- - - - - - - - - - - - - - - - - - - - -

Now lest download a zip file that does not work in our P5210.

I been studying a way to back up our partitions. So I been reading on:

Online Nandroid / Nandroid Backup without re-booting

http://xdaforums.com/showthread.php?t=1620255

At the bottom of the first post is the link to the program. This program is install on a rooted device via zip file on recovery mode.

Here is a direct link for "onandroidv9.20.zip" so you to follow me.

http://xdaforums.com/attachment.php?attachmentid=2389865&d=1384355365

Try to install using TWRP by saving the file onandroidv9.20.zip on your Internal memory using the PC.

In TWRP then you will do Install and then search /emmc for onandroidv9.20.zip. Select the file and install.

You will see:

Updating partition details...
Installing '/emmc/onandroidv9.20.zip' ...
Check for MD5 file ...
Skip MD5 check: no MD5 file found.
[COLOR="Red"]E:Error executing updater binary in zip '/emmc/onandroidv9.20./onandroidv9.20.zip'
Error flashing zip '/emmc/onandroidv9.20./onandroidv9.20.zip'[/COLOR]
Injecting TWRP into boot Image...
TWRP Injection complete.
Updating partition details...
[COLOR="Red"]FAILED[/COLOR]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

So then I thought this has to be with the issue our P5210 is x86. And for sure my friend DutchDanny compiled that "update-binary" special for us.

So since this files have no signature I decide to copy the "update-binary" from the DutchDanny Files and replace the one inside onandroidv9.20.zip and I rename this modified file onandroidv9.20x86.zip

Then I try to install it in TWRP and guess what!!!! Yes it install without any issue.

So this "update-binary" that I saw first on DutchDanny files is been copied on all roms that we see posted here. So this is known to our real developers.

But I thought it should be shown, so that we can force the Failing Zip Files to work in P5210.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Now Here is an Interesting Thing.......

Our GT-P5210 is x86. Not : armeabi or armeabi-v7a nor mips!!!!!

But most of all application in the market are armeabi or armeabi-v7a. They do not have a x86 version.

But when you are running Android normally yesssssss all apks work fine. So how is that possible?

Some people has claim that there are a secondary armeabi processor inside or x86 device. Others think there is emulation!! I do not know.

But I know I had side load many apks really old at the beginning of Android when there was no x86 and they most all work. A few exceptions.

For example MXPlayer requires a special MXPlayer Code Pack. And if you look inside MXPlayer apk that there is a folder "lib" that have sub folders "x86, armeabi or armeabi-v7a and mips". With the applicable libraries that for sure are compiled for each different processor.

If you go into MX Player Codec (x86).apk in lib you will see only "Lib\x86" as expected. It is to be used only in x86.

What I a saying, It is possible that our P5210 have some sort of way of ruining armeabi code while ruining normally. But there are things that require true x86 code like some libraries. This only while you are ruining normally the OS. And I expect that when in Recovery this does not apply making many zip designed for armeabi to fail.

I hope this is useful for you.

Edited:

Correction: There is no second CPU but in fact allmost all apps run under Java Dalvik and libraries via emulation ( houdini library) please see below.