<ID:0/006> Added!! <ID:0/006> Odin engine v(ID:3.1301).. <ID:0/006> File analysis.. <ID:0/006> Total Binary size: 35 M <ID:0/006> SetupConnection.. <ID:0/006> Initialzation.. <ID:0/006> Get PIT for mapping.. <ID:0/006> Firmware update start.. <ID:0/006> NAND Write Start!! <ID:0/006> SingleDownload. <ID:0/006> recovery.img <ID:0/006> RQT_CLOSE !! <ID:0/006> <ID:0/006> Complete(Write) operation failed. <OSM> All threads completed. (succeed 0 / failed 1) <ID:0/006> Removed!!
Android 9 Baseband version: A530FXXUECTH1 Kernel version: - 4.4.111-19323942 - #1 Mon Aug 3 15:36:52 KST 2020 Build number: PPR1.180610.011.A530FXXUECTH2 Security patch level: August 1,2020 Security software verion: - ASKS v3.1.1 Rlease 20200120 - ADP v3.0 Releasae 20191001 - SMR Aug-2020 Release 1
I'm not 100% sure, it might boot but you probably will find some bugs that could happen due to different kernels and device tree.
#include <std_disclaimer.h> /* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about doing this to your device * YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. */
No problem, he was saying to check build.prop to see if there was some strange prop enabled (like Knox Zygote one). Anyway me and @salimskiy find out it's Magisk/SuperSU related and not some kinda of anti-root protection (it's related to systemless root method, in particular the patch of "init" file in ramdisk). I'm gonna report the issue to topjohnwu in afternoon and see if the dev can fix it