Green_Laser
Well-known member
Good you tried from recovery.
Reason why I was asking about which rom you were on was because could be the custom rom you're on already had the proper configuration to block OTAs.
The developer who posted the OTA killer, Santod, he makes killer custom roms, though on his latest, he did not include the files that block future OTAs, mainly due to him assuming that there wouldn't be any more of them from Verizon, can't blame him. So some of us on his roms could have been affected otherwise, however due to his patch, some of us were lucky as I was to flash this and stop anything to be pushed onto the custom roms we're running.
So more than likely, could be your device is aborting the flash of this patch because it is different rom that does not need this patch.
Although I am no expert in this field, I may be wrong too, just my opinion/perspective on this.
Sent from my ADR6400L using Android Central Forums
Reason why I was asking about which rom you were on was because could be the custom rom you're on already had the proper configuration to block OTAs.
The developer who posted the OTA killer, Santod, he makes killer custom roms, though on his latest, he did not include the files that block future OTAs, mainly due to him assuming that there wouldn't be any more of them from Verizon, can't blame him. So some of us on his roms could have been affected otherwise, however due to his patch, some of us were lucky as I was to flash this and stop anything to be pushed onto the custom roms we're running.
So more than likely, could be your device is aborting the flash of this patch because it is different rom that does not need this patch.
Although I am no expert in this field, I may be wrong too, just my opinion/perspective on this.
Sent from my ADR6400L using Android Central Forums