[Sprint Samsung Galaxy S6] IAmTechFreq:
So, this is what i've done through out the past hours lol care to give any suggestions or ideas?

( i've read alot of info saying i have a Corrupt Partition or NAND or emmc and i might need to have a repair technician to replace it, but i'm not giving up just yet)

So, what i've done is ReDownload the stock tars as fresh with no corrupt or retry download issues most took 15 to 20 minutes.

most of the stock tars from these sources.

AFH - by Koop1955

Dec 24th 2015 - G920PVPU3BOL1_G920PSPT3BOL1_SPR

Mar 27, 2016 - G920PVPU3CPB6_G920PSPT3CPB6_SPR

April 28th, 2016 - G920PVPS3CPD2_G920PSPT3CPD2_G920PVPS3CPD2_HOME

Stock PD2 from the samfirm website and it's fast downloading tool

G920PVPS3CPD2_G920PSPT3CPD2_G920PVPS3CPD2_HOME.tar

I've also download your pit and another forums pit file aswell.

ZEROFLTE_USA_SPR and SPR_S6_G920P_32G_PIT

And for final tests....more forums resulted into these details.

As, i try to reboot into my own Recovery i can't even do that, it forces me straight to Download Mode, yet i can hardly flash anything.

So, i went off and Downloaded and Flash through Odin via AP

A Twrp Recovery - TWRP_G920P_MM_3.0.0-1_by_Lamlazy -

Lamlazy gave me a NAND WRITE Start after cache img and just was stuck from there which actually suprised me, while others just didn't try or got stuck at recoverying.img

The CF-Auto-Root-zerofltespr-zerofltespr-smg920p.tar - CF autoroot recovery img was just stuck again at that point, nothing on phone or odin.

So, i went to Sunderwears downloads, used - CF-Auto-Root-zeroflte-zerofltexx-smg920f.tar - and stuck like the other made no difference.

AS well as his recovery, just stuck no difference.

I went to his MM post for the flashable tar that he grabbed from the servers BEFORE it was out in public and downloaded most of it.

So i went ahead and tried to flash - ALL_SPT_G920PVPU3CPB6_G920PSPT3CPB6_CL7280193_QB8664149_REV02_user_low_ship.tar -

same thing happened no difference, stuck at Sboot.bin.

The TWRP and other Root method made no difference either.

So i went onto to Sac23s forum, tried flashing Both Recovery files, not at the same time obviously, restarting and trying the next - is just stuck on recovery img - no difference..

So i went back to Koops forum again, redownloaded OL1 , stuck on the sboot.bin

I tried just PIT solo and it flashes fine, the stock tar is stuck on recover img.

If i combine both PIT and that OL1 it just hangs on me....so no luck there no difference except PIT is flashing through.

Im pretty stumped at this point, i'm not sure what to really do lol

I've tried Kies, no game and SmartSwitch and no game same difference, i enter Model Numebr but i still require the Serial # which i can't grab and i'm screwed so i uninstalled it..

Wondering about my battery because i dont know if its going to die soon or not it was at 49+ percent before it forced itself to downloadmode. And then i thought why not flash the file 1 by 1 like a pit?

I've tried another Youtube video suggestion and forum for a Tar Tool for Odin. a.k.a No Boot.bin tutorial

So, i only used PD2's tar and extracted It from the SamFirm and i tried flashing 1 file at a time to see what works and what doesn't.

And here's my results.

So i try Just Cache

It's Detected at the top and highlighted but won't flash

..Restart...

Next i try JUST CM

IT, It flashes through no problem

...Restart...

Next i try Just MODEM, it won't flash it says get pit mapping, firmware update start, single downlaod then gets stuck afterwards..

..Restart...

Next i try JUST recovery, it won't flash say get pit for mapping aswell, firmware update start, single downlaod , gets stuck on recovery img

..Restart...

Last but not least i Try Just Sboot, it wont flash, get pit for mappying, firmware update start, single downlaod, gets stuck at sboot.bin

So now I'm ultimately stumped. Even stock firmware won't flash 1 by 1 and even, The custom recovery or original just doesn't like to,

The only thing i can think of trying is, different Cable, and USb port but i dont see how that would make a difference if it could just be the phone itself here. (possibly)