ROM:00000000 load_index DCD 5
ROM:00000004 flash_partition_version DCD 3
ROM:00000008 image_source_pointer DCD 0
ROM:0000000C image_dest_pointer DCD 0x88E00000
ROM:00000010 image_size DCD 0x12BD90
ROM:00000014 code_size DCD 0x128C90
ROM:00000018 signature_addr DCD 0x88F28C90
revasm
revasm
/ sch-i535_ml1_mdk_comparison.md
Last active
January 4, 2016 05:09
Samsung Galaxy S III (Verizon) ML1-MDK disassembly comparison for Loki compatibility
revasm
/ sch-i535_43_to_41_rollback.md
Last active
January 4, 2016 04:39
Samsung Galaxy S III (Verizon) 4.3 OTA to 4.1 OTA rollback instructions
In December 2013, Verizon issued an over-the-air (OTA) update for the Samsung Galaxy S III. The 4.3 update, dubbed "ML1" by the XDA community, introduces Samsung KNOX, a sandboxed Android application environment aimed at business and government customers. Coinciding with the KNOX integration are several changes to the device boot loader firmware. Signing policies are now re-enforced on flashing procedures targeting the boot loader, recovery, and kernel partitions. Attempts to flash the device contents will supposedly trigger a newly exposed eFuse, permanently altering certain hardware circuit paths, thereby signaling expiration of the device's warranty.
Due to a desire by some individuals to downgrade to Android version 4.1, and a prevailing belief that this is now impossible, I will describe below steps on how to flash an older signed system ROM onto a 4.3-installed device.
Warning #1: Despite it being possible to downgrade the system and kernel to official version 4.1, it is not believed possible to d