TA Partition and flashing history. topic

Did anyone noticed that in the TA partition it is stored every firmware flash that the device took?

For example in my TA backup took when i rooted the .534 to flash the rooted 4.4 i have:

Quote:

ÿÿ« ç Áéø;ÿÿÿÿNEW_VERSION: erased_user_data:true, variant:user, s1boot_version:1270-3115 S1_Boot_MSM8974_LA1.0_56-A, cdf_version:1276-4321_R2A, fs_version:EURO-LTE_14.1.G.1.518, sw_version:1274-8313_14.1.G.1.518 NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1270-3115 S1_Boot_MSM8974_LA1.0_56-A, cdf_version:1276-4321_R2A, fs_version:EURO-LTE_14.1.G.1.534, sw_version:1274-8313_14.1.G.1.534 NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1270-3115 S1_Boot_MSM8974_LA1.04_15, cdf_version:1276-4321_R1B, fs_version:EURO-LTE_14.2.A.1.136, sw_version:1274-8313_14.2.A.1.136 NEW_VERSION: erased_user_data:false, variant:user, s1boot_version:1270-3115 S1_Boot_MSM8974_Rhine1.2_LA1.04_12, cdf_version:1276-5833_R5C, fs_version:EURO-LTE_14.3.A.0.681, sw_version:1274-8313_14.3.A.0.681 NEW_VERSION: erased_user_data:true, variant:user, s1boot_version:1270-3115 S1_Boot_MSM8974_LA1.0_67, cdf_version:1276-4314_R2A, fs_version:EURO-LTE_14.1.G.1.534, sw_version:1274-8313_14.1.G.1.534

This means that if i unlock the device and then restore ta for warranty purposes sony will see all history of flashed software along the phone's life, in this case that i flashed another region's firmware.

[Q] [WHATSAPP] Unable to recover message history: Corrupt Database topic

Hello,

Whatsapp problem! I want to copy my chat history from my Samsung Galaxy S1 (2.3.6) to my new Nexus 5 (4.4.2).

I copied my entire Whatsapp folder to my Nexus 5 (/sdcard/Whatsapp/) and then installed Whatsapp. It asked me if I would like to recover my history chat messages. After clicking yes it started recovering but after 10-20 seconds it shuts down and an error message comes forward saying that Whatsapp had stopped working. I tried it multiple times.

When looking in my System Log file it says that it has something to do with SQLite. These are some lines in the Log file concerning Whatsapp:

1. "E/DefaultDatabaseErrorHandler (3784): Corruption reported by sqlite on database: /data/data/com.whatsapp/databasesmsgstore.db"


2. "E/AndroidRuntime (3784): java.lang.AssertionError: android.database.sqlite.SQLiteDatabaseCorruptExcep tion: Database disk image is malformed (code 11), SQLiteConnection.java,-2"


3. "E/SQLiteLog (3784): (14) cannot open file at line 30191 of [00bb9c9ce4]"


4. "E/SQLiteDatabase (3784): Failed to open database '/data/data/com.whatsapp/databases/msgstore.db' "


5. "E/SQLiteDatabaseException: unknown error (code 14): Could not open database"


6. "I/sqlite_db_corrupt (3784): /data/data.com.whatsapp/databases/msgstore.db"

:confused:
Can someone tell me how to fix this problem or how to find what the error causes in my database file? :crying:

NOTE: I added screenshots of System Log

Attached Files

sqlitecorrupt.zip - [Click for QR Code] (2.60 MB)

[Q] [WHATSAPP] Unable to recover message history: Corrupt Database topic

Hello,

Whatsapp problem! I want to copy my chat history from my Samsung Galaxy S1 (2.3.6) to my new Nexus 5 (4.4.2).

I copied my entire Whatsapp folder to my Nexus 5 (/sdcard/Whatsapp/) and then installed Whatsapp. It asked me if I would like to recover my history chat messages. After clicking yes it started recovering but after 10-20 seconds it shuts down and an error message comes forward saying that Whatsapp had stopped working. I tried it multiple times.

When looking in my System Log file it says that it has something to do with SQLite. These are some lines in the Log file concerning Whatsapp:

1. "E/DefaultDatabaseErrorHandler (3784): Corruption reported by sqlite on database: /data/data/com.whatsapp/databasesmsgstore.db"


2. "E/AndroidRuntime (3784): java.lang.AssertionError: android.database.sqlite.SQLiteDatabaseCorruptExcep tion: Database disk image is malformed (code 11), SQLiteConnection.java,-2"


3. "E/SQLiteLog (3784): (14) cannot open file at line 30191 of [00bb9c9ce4]"


4. "E/SQLiteDatabase (3784): Failed to open database '/data/data/com.whatsapp/databases/msgstore.db' "


5. "E/SQLiteDatabaseException: unknown error (code 14): Could not open database"


6. "I/sqlite_db_corrupt (3784): /data/data.com.whatsapp/databases/msgstore.db"

:confused:
Can someone tell me how to fix this problem or how to find what the error causes in my database file? :crying:

NOTE: I added screenshots of System Log

[Q] Installed apps history? topic

hi! we can clean some apps that we dont use going to playstore/myapss/all.

but if you try remove an app from the list (not the 1st app preferably), and install again that app you will notice the position on the list is the same. So its impossible delete apps history, google always remember what apps you have ever installed with your account?

[History] How the Droid was Rooted topic

Originally written by Evan Charlton, however his site is down and I'm preserving this here for "history"

Quote:

Posted: Monday, Dec 14 2009 How Droid Was Rooted As you may (or may not) know, the Verizon Droid was recently rooted. That is to say that the average user can get root/superuser access on the device. Here's how it was pulled off: In Android, updates must be signed by a known private key in order for the phone to install them. The recovery image checks these updates and installs (or does not install) these binaries. In Android 2.0, this code was rewritten for some reason. Here's what a certain portion of the vulnerable file (now fixed) looks like: int i; for (i = 4; i < eocd_size-3; ++i) { if (eocd[i ] == 0x50 && eocd[i+1] == 0x4b && eocd[i+2] == 0x05 && eocd[i+1] == 0x06) { // if the sequence b appears anywhere after // the real one, minzip will find the later (wrong) one, // which could be exploitable. Fail verification if // this sequence occurs anywhere after the real one. LOGE("EOCD marker occurs after start of EOCD\n"); fclose(f); return VERIFY_FAILURE; } } It's important to know what happens with verification. First, the zip's signing key is verified. This is located at the beginning of the file. Next, the file is read from the end backwards until it finds a certain series of bytes, known as EOCD (end-of-central-directory). The author correctly noted that you could get around this by sticking two .zips together--the first one would have the correct signature and the second one would be the one applied, and they put in a check for it. However, they made a crucial typo in this line of code: if (eocd[i ] == 0x50 && eocd[i+1] == 0x4b && eocd[i+2] == 0x05 && eocd[i+1] == 0x06) { If you still don't see it, look at the offsets. Here is why the check fails: if(foo == 1 && foo == 2) { // there's an exploit! // note that the above condition is never true } With that discovered, all that had to happen was getting a signed zip from Verizon and then stick a payload zip on the end (it's a tiny bit more difficult than that, but that's the general idea). Just to clarify: I can claim no credit for this hack. Zinx created the magical zip (but wants it to be known that he did not find the exploit).

Proper link for the fixed file : http://androidxref.com/2.1/xref/boot...ery/verifier.c

[Discuss] Lets tell a History topic

Lets play this game. You just can folow the history with 3 words.
I will start!

Long time Ago