G930V (S7) will not boot no matter what. [SOLVED, BATTERY ISSUE]

[Mnky313]

I have a co-worker's S7 that randomly decided it was only going to boot to the blue 'no command' screen (not actually into recovery, just that screen followed by a reboot over and over).

Info:
It's a G930V (completely stock, no root, stock firmware)
It's on Binary 10 (only allows A firmware, if you don't know what this is it basically means I can only ODIN firmware with A as it's 5th to last character)
It's bootloader locked and FRP lock is on (though he knows the password so this isn't important)

Things I have tried: Result
Factory Reset from Maintenance Boot: bootloop of 'recovery booting' followed by a black screen
flashing CSF2 via ODIN (BL/AP/CP/CSC): 'recovery booting' followed by blue 'installing system update' followed usually by 'Error' with a percent bar or just bootlooping the 'installing system update' screen
flashing CSF2 and HEROQLTE_VZW PIT file via ODIN (with and without NAND ERASE): sometimes boots to Samsung logo animation and reboots or the same recovery bootloop
flashing Latest Unlocked (G930U) firmware: same as CSF2 flash
Samsung Smartswitch: 'Device not supported'
Verizon software assistant thing: 'UNSUPPORT dev_type' (this happens when using older ODIN because it can't read oreo's lz4 compression)

It could be a battery issue, I wil try an S6 battery later (they should* be compatible and if not I have an S7 in the mail anway)
other than that, Im out of ideas because it's a locked bootloader and stuck on the latest binary which only has 1 firmware supported....

I can sometimes press random key combos to get it to go to recovery but reseting in there doesn't change anything
The phone also locks up a lot (sometimes in recovery, sometimes on boot screen, sometimes even in ODIN mode start screen)
I have seen the dreaded 'grey circle with lightning bolt' screen a few times (that's why I think it might be battery)
The 'Encryption Failed' screen has only shown up once and it was frozen (after rebooting it went back to bootlooping) 

Edit: just had it say:
SECURE CHECK FAIL : Loaded PIT
ERROR: Device have invalid pit

Edit Final:
IT WAS A BATTERY ISSUE, I tested a S6 battery I had and it works fine once I reflashed Stock VZW firmware, see comment for image.

 

Edited October 9, 2019 by Mnky313
battery issue

[SlayerOfHellWyrm]

From my experience, it's basically bricked. PIT's basically the partition table, and that's dead/corrupted. Secure Check shouldn't be failing,  so something else is also bad on the phone.  When secure check fails, it's supposed to load the PIT to see if it's changed location, or something's been modded. Could be the system storage is failing due to the phone's age/bad luck.  I've never been able to recover from this.

[Mnky313]

26 minutes ago, SlayerOfHellWyrm said:

From my experience, it's basically bricked. PIT's basically the partition table, and that's dead/corrupted. Secure Check shouldn't be failing,  so something else is also bad on the phone.  When secure check fails, it's supposed to load the PIT to see if it's changed location, or something's been modded. Could be the system storage is failing due to the phone's age/bad luck.  I've never been able to recover from this.

I thought so too, but I tested an S6 battery in it and boom! booted right up once I wiped NAND and repartitioned/flashed VZW firmware!