A
AC Question
Water damage lead to custom message at boot and other strange problems
Yesterday I took my Active to the pool. It was submerged for no more than 10 minutes in maybe 5 inches of water. Afterwards it was working normally but this morning, when I plugged it in to charge, the splash screen had a "Custom" message along with an image of an unlocked lock. I can only imagine this is referring to the bootloader, which I haven't even touched. This phone is non-rooted, an obviously stock ROM.
Now, it has the following messages on the screen:
_____________________________________
FACTORY MODE
PRODUCT NAME: SM-G870A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECURE BOOT: ENABLE (CSB)
AP SWREV: S1, T1, A1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START
[picture of android dude}
Downloading...
Do not turn off target!!
_____________________________________
My only theory is that the water damage somehow blew the fuse that gets triggered when the bootloader is unlocked. I could be wrong though.
Does anyone know what is going on?
Any help is appreciated.
Yesterday I took my Active to the pool. It was submerged for no more than 10 minutes in maybe 5 inches of water. Afterwards it was working normally but this morning, when I plugged it in to charge, the splash screen had a "Custom" message along with an image of an unlocked lock. I can only imagine this is referring to the bootloader, which I haven't even touched. This phone is non-rooted, an obviously stock ROM.
Now, it has the following messages on the screen:
_____________________________________
FACTORY MODE
PRODUCT NAME: SM-G870A
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
REACTIVATION LOCK(KK): OFF
KNOX WARRANTY VOID: 0x0
QUALCOMM SECURE BOOT: ENABLE (CSB)
AP SWREV: S1, T1, A1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START
[picture of android dude}
Downloading...
Do not turn off target!!
_____________________________________
My only theory is that the water damage somehow blew the fuse that gets triggered when the bootloader is unlocked. I could be wrong though.
Does anyone know what is going on?
Any help is appreciated.