Database Users

Can flash firmware but cannot access Recovery

I'm new here so please bear with me. I've been reading up on these forums and other places all over the internet. Currently, I'm not sure what the problem is with my device. I can boot into download mode but never in recovery.
First off, I got this phone from someone else and it was bricked when I got it. I've tried flashing and I've got the "Fused 3: Binary 2" when trying to flash different stock files. If I'm correct, this means the last person should have tried to upgrade it to the latest Kitkat firmware. I've been using Odin 3.07, 3.09, and even 1.85 to see if the flash is just bad in one version or the others. However, each version will flash the latest firmware that Sammobile give me just fine (or at least appears so).
I've even tried flashing a pit file (HLTE_USA_VZW_32G.pit) but that really does nothing. If I flash the pit file and then flash the firmware alone 2 time back to back... it will show its attempting to go into recovery ONCE but fail and go into a never ending bootloop. Sometimes after a flash it will even bootloop trying to go into recovery automatically.
I haven't read anyone who has had it happen like this and I'm not sure if I'm in a soft-brick or in a weird hard-brick. Any suggestions?

LeveeWasDry said:
I'm new here so please bear with me. I've been reading up on these forums and other places all over the internet. Currently, I'm not sure what the problem is with my device. I can boot into download mode but never in recovery.
First off, I got this phone from someone else and it was bricked when I got it. I've tried flashing and I've got the "Fused 3: Binary 2" when trying to flash different stock files. If I'm correct, this means the last person should have tried to upgrade it to the latest Kitkat firmware. I've been using Odin 3.07, 3.09, and even 1.85 to see if the flash is just bad in one version or the others. However, each version will flash the latest firmware that Sammobile give me just fine (or at least appears so).
I've even tried flashing a pit file (HLTE_USA_VZW_32G.pit) but that really does nothing. If I flash the pit file and then flash the firmware alone 2 time back to back... it will show its attempting to go into recovery ONCE but fail and go into a never ending bootloop. Sometimes after a flash it will even bootloop trying to go into recovery automatically.
I haven't read anyone who has had it happen like this and I'm not sure if I'm in a soft-brick or in a weird hard-brick. Any suggestions?
Click to expand...
Click to collapse
the fact you can get into download modes shows you're not hard brick. Make sure you are downloading the correct firmware, since I don't know what you were running the safest approach would be to download NC4 Firmware, pit file, and use odin 3.10. Now flash the pit file, then flash the firmware in the PDA/PA spot. Restart you phone, on boot up hold home and I believe the down power button to get into recovery, select factory restore, and restart.

Yeah, definitely check which firmware you have. Make sure it's for the N900V. The leaked nc2 came with either missing or broken recovery, so don't odin that. Verify the md5 code after you download both the pit and the tar.md5. I'm pretty sure odin does this, but check just in case.

LeftyGR said:
Yeah, definitely check which firmware you have. Make sure it's for the N900V. The leaked nc2 came with either missing or broken recovery, so don't odin that. Verify the md5 code after you download both the pit and the tar.md5. I'm pretty sure odin does this, but check just in case.
Click to expand...
Click to collapse
I'm pretty sure my phone needs N900VVRUCNC4_N900VVZWCNC4_N900VVRUCNC4_HOME.tar because its the only one that successfully flashed in Odin. I have a new theory that may have something to do with it. My phone battery is completely dead so maybe that is a failsafe for recovery mode? I know people say the battery needs to be a certain % charged before doing any flashing. Perhaps its due to the fact it won't boot into recovery proper until the battery is at a certain charge? I sort of think it could be the case.
Since it won't charge due to boot loop... I had to do a bad flash and reproduce the results I got a day ago. I did a bad flash that won't send the device into a bootloop and rather straight into a charge state. I'm going to get the battery to 100% and try a flash with the above firmware again. Perhaps recovery will actually work with the battery at 100%. I will keep update with the results.

Battery is at 100% now but it still will not boot into recovery. I flash the .pit file and then the firmware file stated above. I try different combinations all to no fix. I'm still stuck in a bootloop.
I don't understand really. The phone seems to be soft-bricked obviously... so there is a way to salvage... I just can't seem to get it to work. Any thoughts on what I can try from here?

LeveeWasDry said:
Battery is at 100% now but it still will not boot into recovery. I flash the .pit file and then the firmware file stated above. I try different combinations all to no fix. I'm still stuck in a bootloop.
I don't understand really. The phone seems to be soft-bricked obviously... so there is a way to salvage... I just can't seem to get it to work. Any thoughts on what I can try from here?
Click to expand...
Click to collapse
LeveeWasDry said:
Battery is at 100% now but it still will not boot into recovery. I flash the .pit file and then the firmware file stated above. I try different combinations all to no fix. I'm still stuck in a bootloop.
I don't understand really. The phone seems to be soft-bricked obviously... so there is a way to salvage... I just can't seem to get it to work. Any thoughts on what I can try from here?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2755970
Have you tried this link ? Contains the working recovery to flash.

mjh68 said:
http://forum.xda-developers.com/showthread.php?t=2755970
Have you tried this link ? Contains the working recovery to flash.
Click to expand...
Click to collapse
the link provided above will fix your phone. Follow the steps exactly and you will be good to go.

Since I cannot start my phone, I can't root it under "Steps for Retail Edition" I have to skip straight to step 10 and flashing that files does not work.Unified_KK_Firmware_RE.tar So, am I screwed or what else is there to do?

LeveeWasDry said:
Since I cannot start my phone, I can't root it under "Steps for Retail Edition" I have to skip straight to step 10 and flashing that files does not work.Unified_KK_Firmware_RE.tar So, am I screwed or what else is there to do?
Click to expand...
Click to collapse
The Unified_kk is not the full firmware. It's only the radio, recovery, etc.
But to verify from a previous post, you tried the full firmware for nc4?
When you boot to download mode, in the upper left corner there is some info and codes. What are they on your phone?

LeftyGR said:
The Unified_kk is not the full firmware. It's only the radio, recovery, etc.
But to verify from a previous post, you tried the full firmware for nc4?
When you boot to download mode, in the upper left corner there is some info and codes. What are they on your phone?
Click to expand...
Click to collapse
Yes. I've tried the full firmware for NC4 and it just bootloops. This is what the download page tells me.
ODIN MODE
PRODUCT NAME: SM-N900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A3, P1
WRITE PROTECTION: Enable
UDC START

LeveeWasDry said:
Yes. I've tried the full firmware for NC4 and it just bootloops. This is what the download page tells me.
ODIN MODE
PRODUCT NAME: SM-N900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T1, R1, A3, P1
WRITE PROTECTION: Enable
UDC START
Click to expand...
Click to collapse
Ok. Everything seems right to me. It's definitely not you!
What info did you get from the previous owner? When you bought it did they tell you it was bricked and what they did to brick it?

LeftyGR said:
Ok. Everything seems right to me. It's definitely not you!
What info did you get from the previous owner? When you bought it did they tell you it was bricked and what they did to brick it?
Click to expand...
Click to collapse
I was told nothing really. They just told me that it boot looped and it was stuck on the "Firmware Upgrade has Encountered an Issue" screen. It was more so a gamble really. The phone looks impeccable so it seems to be rather new. Maybe the owner had flashed it before and tool the OTA, soft-bricking it... I don't know. I just know that its last flash was 4.4 KK because it wouldn't let me downgrade firmware.

I'm not quite sure what else you could look at doing here. You seem to be doing everything right, but not getting the right results.
The following is an option:
Seems to me that the previous owner did something "unofficial" that caused this. If it was something official, it would've easily been accepted as a replacement via warranty situation. But instead, they got rid of it!
---------- Post added at 07:33 AM ---------- Previous post was at 07:26 AM ----------
Actually, there is one more thing you can try. You should never do this because there is too high a risk of bricking if you do something wrong. But you are already pretty bricked, so what else have you got to lose?
http://forum.xda-developers.com/showthread.php?t=2610757
Go check this out, and nand erase all during the odin flash.

[Q] Note 3 (N900) wont turn on, recovery not accessible, RP SWREV: A4

Galaxy Note 3 N900 ​
Im not new to Odin nor rooting or even customized Roms, but this time i ran out of solutions.
I have galaxy note 3 SM-N900, it was running on 4.4.2 and i have made some modification through Xposed Installer, it is rooted as well.
it was stable and i used it without any new modification for 2 months. but yesterday its battery ran out and i didn't charge it for 5 hours after it was dead.
after recharging it, it refused to boot, it stuck on the Samsung first screen when it turns on, then it does nothing, take into consideration that the battery is charged (i have tested it on another phone).
i tired entering the recovery mode but with no luck, recovery page is not accessible. And i have noticed a weird thing that when it was turned off and plugged to the charger i usually see the big battery picture show a motion that its charging but now it shows only a picture of an empty batter without any motion.
its now showing on the download mode page "RP SWREV: A4" i have searched all the forms and the websites and i couldn't find what is the meaning of it. (picture attached)
I used odin to flash a new stock rom but it always stops on "<ID:0/011> Initialzation.." and sticks on this stage forever.
also Knox warranty was void!
Your help and support are really appreciated.

Guys please I need your help!
If any has passed through the same situation or has any idea why my phone is stuck to boot logo please let me know,
i have a useless brand new Note 3 now
your support is really appreciated.

Avenech said:
If any has passed through the same situation or has any idea why my phone is stuck to boot logo please let me know,
i have a useless brand new Note 3 now
your support is really appreciated.
Click to expand...
Click to collapse
Find the correct stock ROM for your device and the PIT file to match it, then flash it via ODIN and you should be OK. Since you can get to the Boot loader it's most definitely fixable.

radicalisto said:
Find the correct stock ROM for your device and the PIT file to match it, then flash it via ODIN and you should be OK. Since you can get to the Boot loader it's most definitely fixable.
Click to expand...
Click to collapse
I Tried flashing stock Rom with the PIT file that i found on other XDA Thread, but Odin was stuck on <ID:0/011> Initialzation.." as before!
any suggestions?
can you give me a different PIT file?

Avenech said:
I Tried flashing stock Rom with the PIT file that i found on other XDA Thread, but Odin was stuck on <ID:0/011> Initialzation.." as before!
any suggestions?
can you give me a different PIT file?
Click to expand...
Click to collapse
ODIN won't show the Device Name or Model, and regarding the phone issue, I could have helped you if I have the device, and even I don't know what could be the Solution, I guess you tried almost everything to fix it.
Hope you can fix it.

Bricked S5 SM-G900F, cannot boot to recovery

Firstly my thanks to all the experts here - I'm a complete noob, yet I've managed to use the threads here to install a custom ROM on an old Sony Experia and more recently my Galaxy S3.
However, my S5 is sick and I'm stuck. Sorry to start yet another thread on this topic, but they mostly suggest things I've tried and in any case my head is spinning with it all so I'm starting afresh.
History: I was using the S5 as normal (RealCalc, IIRC - nothing exotic) and it became a bit non-responsive, so I restarted the phone. It hung at the 'Samsung Galaxy S5 powered by Android' screen. Tried again, same; took the battery out and tried again, same.
After much Googling and searching here, here's what I've tried:
Used Odin (various versions) to flash a recovery (can't remember which one). It appeared to work but on booting into recovery (power, home, vol-up), it hung at the 'recovery booting' screen.
Used Odin to flash a TWRP recovery. This gave me 'recovery booting (blue), recovery is not seandroid enforcing (red), set warranty bit: recovery (yellow) but still hung.
Eventually, after several attempted flashes, it booted into TWRP; the first thing I thought I should do was take a backup. It was late at night, so I left it backing up to the SD card (connected to USB power). In the morning, the screen was saying that the backup had completed ok, but the phone was completely frozen. Since then, it's never got past the initial boot screen
I also tried Odin to flash a stock ROM obtained from SamMobile. This failed right at the end (FAIL! (Ext4)).
I found a PIT file for the 900F, and with this and the stock ROM, got Odin to a PASS at the end. However, it still hangs on reboot.
The only thing that seems to work reliably is getting into download mode and flashing with Odin, but it never boots after that. I've tried other variations of the above but foolishly I didn't take notes and in any case they all had the same result.
Completely stuck. Would very much appreciate any suggestions.

Did you try flashing custom ROM?
thickymcthick said:
Firstly my thanks to all the experts here - I'm a complete noob, yet I've managed to use the threads here to install a custom ROM on an old Sony Experia and more recently my Galaxy S3.
However, my S5 is sick and I'm stuck. Sorry to start yet another thread on this topic, but they mostly suggest things I've tried and in any case my head is spinning with it all so I'm starting afresh.
History: I was using the S5 as normal (RealCalc, IIRC - nothing exotic) and it became a bit non-responsive, so I restarted the phone. It hung at the 'Samsung Galaxy S5 powered by Android' screen. Tried again, same; took the battery out and tried again, same.
After much Googling and searching here, here's what I've tried:
Used Odin (various versions) to flash a recovery (can't remember which one). It appeared to work but on booting into recovery (power, home, vol-up), it hung at the 'recovery booting' screen.
Used Odin to flash a TWRP recovery. This gave me 'recovery booting (blue), recovery is not seandroid enforcing (red), set warranty bit: recovery (yellow) but still hung.
Eventually, after several attempted flashes, it booted into TWRP; the first thing I thought I should do was take a backup. It was late at night, so I left it backing up to the SD card (connected to USB power). In the morning, the screen was saying that the backup had completed ok, but the phone was completely frozen. Since then, it's never got past the initial boot screen
I also tried Odin to flash a stock ROM obtained from SamMobile. This failed right at the end (FAIL! (Ext4)).
I found a PIT file for the 900F, and with this and the stock ROM, got Odin to a PASS at the end. However, it still hangs on reboot.
The only thing that seems to work reliably is getting into download mode and flashing with Odin, but it never boots after that. I've tried other variations of the above but foolishly I didn't take notes and in any case they all had the same result.
Completely stuck. Would very much appreciate any suggestions.
Click to expand...
Click to collapse

androidtweaker1 said:
Did you try flashing custom ROM?
Click to expand...
Click to collapse
No, I did download a CyanogenMod one, but I can't install it from recovery, as I can't get into any recovery now.
Are there any custom ROMs that can be flashed from Odin?

did you try to remove and format your extSD (possibly partly corrupted) and reinsert and flash again? Or change to other extSD?

Perru said:
did you try to remove and format your extSD (possibly partly corrupted) and reinsert and flash again? Or change to other extSD?
Click to expand...
Click to collapse
Well, I removed the card completely and reflashed with Odin. No difference.
I can't flash from a ROM on the SD card because I can't successfully boot into recovery.

I suppose, you already tried to flash twrp-2.8.7.0-klte directly from here: https://dl.twrp.me/klte
and latest stock rom for G900F and your country directly from here: http://www.sammobile.com/firmwares/database/SM-G900F/
via ODIN 3.10.7 from here: http://forum.xda-developers.com/showthread.php?t=2711451?

Perru said:
I suppose, you already tried to flash twrp-2.8.7.0-klte directly from here: https://dl.twrp.me/klte
and latest stock rom for G900F and your country directly from here: http://www.sammobile.com/firmwares/database/SM-G900F/
via ODIN 3.10.7 from here: http://forum.xda-developers.com/showthread.php?t=2711451?
Click to expand...
Click to collapse
I have, yes.
And earlier stock ROMs, and with earlier ODINs too, in various combinations.
Every time, the flash appears to work but it then hangs, booting into recovery. I get the blue 'recovery booting' line at the top, on the Samsung initial boot screen.

thickymcthick said:
Firstly my thanks to all the experts here - I'm a complete noob, yet I've managed to use the threads here to install a custom ROM on an old Sony Experia and more recently my Galaxy S3.
However, my S5 is sick and I'm stuck. Sorry to start yet another thread on this topic, but they mostly suggest things I've tried and in any case my head is spinning with it all so I'm starting afresh.
History: I was using the S5 as normal (RealCalc, IIRC - nothing exotic) and it became a bit non-responsive, so I restarted the phone. It hung at the 'Samsung Galaxy S5 powered by Android' screen. Tried again, same; took the battery out and tried again, same.
After much Googling and searching here, here's what I've tried:
Used Odin (various versions) to flash a recovery (can't remember which one). It appeared to work but on booting into recovery (power, home, vol-up), it hung at the 'recovery booting' screen.
Used Odin to flash a TWRP recovery. This gave me 'recovery booting (blue), recovery is not seandroid enforcing (red), set warranty bit: recovery (yellow) but still hung.
Eventually, after several attempted flashes, it booted into TWRP; the first thing I thought I should do was take a backup. It was late at night, so I left it backing up to the SD card (connected to USB power). In the morning, the screen was saying that the backup had completed ok, but the phone was completely frozen. Since then, it's never got past the initial boot screen
I also tried Odin to flash a stock ROM obtained from SamMobile. This failed right at the end (FAIL! (Ext4)).
I found a PIT file for the 900F, and with this and the stock ROM, got Odin to a PASS at the end. However, it still hangs on reboot.
The only thing that seems to work reliably is getting into download mode and flashing with Odin, but it never boots after that. I've tried other variations of the above but foolishly I didn't take notes and in any case they all had the same result.
Completely stuck. Would very much appreciate any suggestions.
Click to expand...
Click to collapse
What s u model number
---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------
R u now able go to download mode.

tharik816 said:
What s u model number
Click to expand...
Click to collapse
SM-G900F, as in the thread title. Is this what you meant?
R u now able go to download mode.
Click to expand...
Click to collapse
No, nothing's changed since I last tried.

https://youtu.be/m1eRM-kSNNs
---------- Post added at 11:30 PM ---------- Previous post was at 11:22 PM ----------
Try this ...http://www.gsmindia.in/forum/samsun...fix-samsung-galaxy-s5-sm-g900f-dead-boot.html

tharik816 said:
https://youtu.be/m1eRM-kSNNs
Click to expand...
Click to collapse
This video just shows starting up in download mode. Not sure how this helps. I can do this, flash a stock rom or recovery with ODIN, which appears to work (get PASS at the end).
Then on reboot to recovery, it just hangs at the Recovery booting message.

http://www.gsmindia.in/forum/samsun...fix-samsung-galaxy-s5-sm-g900f-dead-boot.html
---------- Post added at 11:35 PM ---------- Previous post was at 11:34 PM ----------
thickymcthick said:
This video just shows starting up in download mode. Not sure how this helps. I can do this, flash a stock rom or recovery with ODIN, which appears to work (get PASS at the end).
Then on reboot to recovery, it just hangs at the Recovery booting message.
Click to expand...
Click to collapse
download mode working or not

tharik816 said:
http://www.gsmindia.in/forum/samsun...fix-samsung-galaxy-s5-sm-g900f-dead-boot.html
---------- Post added at 11:35 PM ---------- Previous post was at 11:34 PM ----------
download mode working or not
Click to expand...
Click to collapse
Appears to be, as I've said. It's the reboot to recovery after flashing that hangs.
I don't have access to a working G900F, unfortunately.

Well, it turned out to be hardware. Needed a replacement board, seems fine now. Thanks for the various suggestions, but none of them worked.

thickymcthick said:
Well, it turned out to be hardware. Needed a replacement board, seems fine now. Thanks for the various suggestions, but none of them worked.
Click to expand...
Click to collapse
wow you have an identical problem with my device. Did you go to samsung service center or a unofficial service center? and may i know how much you spend to fix that? i'm afraid it'd be expensive for a student. thanks before.

firareza said:
wow you have an identical problem with my device. Did you go to samsung service center or a unofficial service center? and may i know how much you spend to fix that? i'm afraid it'd be expensive for a student. thanks before.
Click to expand...
Click to collapse
I took it to a local (I live near London, England) Samsung authorised service centre and they replaced the board.
It cost me GBP 169... :crying:
Worse still, it turned out that it had a 2-year warranty, not the one year one that I thought it had. If I hadn't tried to reinstall Android, thereby tripping the Knox counter, it would have cost me precisely nothing...
An expensive mistake there - check your warranty carefully.

thickymcthick said:
I took it to a local (I live near London, England) Samsung authorised service centre and they replaced the board.
It cost me GBP 169... :crying:
Worse still, it turned out that it had a 2-year warranty, not the one year one that I thought it had. If I hadn't tried to reinstall Android, thereby tripping the Knox counter, it would have cost me precisely nothing...
An expensive mistake there - check your warranty carefully.
Click to expand...
Click to collapse
My warranty isn't valid since i bought a mint condition second-handed G900F from SG. I'm Indonesian. My knox is 0x1 today when i tried to fix that using boot.tar (i didn't know if it'd make my knox avoid! desperately tried every possibilities. Ended up sobbing to see that 0x1).
I thought the problem is on the software, not the hardware. So i'm bit shocked reading your statement that you replace the board. Hope the local service center near the city helps. Thanks for the info!

firareza said:
...So i'm bit shocked reading your statement that you replace the board.
Click to expand...
Click to collapse
Well the thing is, flashing a new Recovery and booting into recovery mode isn't difficult - I've done it several times with other phones, and it's a straightforward procedure.
So the fact that the phone wouldn't boot to Recovery was (in retrospect at least) a bit of an indication that all wasn't well with the hardware. I wasn't messing with the phone when it failed initially, either - I was just using it.
Booting to the stock recovery was the first test I did on the repaired phone, and it worked fine. I'll be leaving the ROM as stock, though, till the warranty runs out.
A bit strange for the board to just stop working though - I've looked after the phone very carefully since new.
Is it common with the S5, does anyone know?

thickymcthick said:
Well the thing is, flashing a new Recovery and booting into recovery mode isn't difficult - I've done it several times with other phones, and it's a straightforward procedure.
So the fact that the phone wouldn't boot to Recovery was (in retrospect at least) a bit of an indication that all wasn't well with the hardware. I wasn't messing with the phone when it failed initially, either - I was just using it.
Booting to the stock recovery was the first test I did on the repaired phone, and it worked fine. I'll be leaving the ROM as stock, though, till the warranty runs out.
A bit strange for the board to just stop working though - I've looked after the phone very carefully since new.
Is it common with the S5, does anyone know?
Click to expand...
Click to collapse
Were you able to resolve the issue?

@mike_sausage said:
Were you able to resolve the issue?
Click to expand...
Click to collapse
Er, did you read my earlier posts? #14 and later.

900V stuck in bootloop after FW upgrade

My Father-in-law tried updating the firmware on my wife's SM-G900V and now it's stuck in a boot loop. I am able to get it into download mode and recovery (I've cleaned the cache and factory reset it dozens of times), and I have been able to flash the latest marshmallow and lollipop images using Odin (passes with no issues), but it's still stuck in the boot loop.
When I get home from work tonight my plan is to try some of the "debricking" and or "rooting" guides I've found on this site:
https://forum.xda-developers.com/ve...images-hardbrick-recovery-plan-t3387010/page1
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Should one of these do the trick, or will I be wasting my time and should be trying something else? Thanks in advance for your advice/help!

RetroRider said:
My Father-in-law tried updating the firmware on my wife's SM-G900V and now it's stuck in a boot loop. I am able to get it into download mode and recovery (I've cleaned the cache and factory reset it dozens of times), and I have been able to flash the latest marshmallow and lollipop images using Odin (passes with no issues), but it's still stuck in the boot loop.
When I get home from work tonight my plan is to try some of the "debricking" and or "rooting" guides I've found on this site:
https://forum.xda-developers.com/ve...images-hardbrick-recovery-plan-t3387010/page1
https://forum.xda-developers.com/ve.../testers-required-easier-root-method-t3561529
Should one of these do the trick, or will I be wasting my time and should be trying something else? Thanks in advance for your advice/help!
Click to expand...
Click to collapse
I have not tried the first method so I cannot say if it will work for a stock debrick. If you are going to use that, make sure the phone is on a PB1/PD1 firmware.
The second one is rooting the phone. I have usedthis one with both CIDs and have had no issues. Since the phone wont boot, you might not be able to locate the CID, so please read the following thread before starting:
https://forum.xda-developers.com/verizon-galaxy-s5/help/to-id-cid-15-loading-app-t3756413
UPDATE: Also, Here is a link to a firmware with the pit file:
https://forum.xda-developers.com/ve...rmware-pit-verizon-samsung-galaxy-s5-t3757416
You may want to try that first before doing the other ones. Having a pit file during the firmware install sometimes helps to fix it.
Try it, see if it works, if you have any more issues, let me know.
Good Luck!

Thanks for the quick reply!
I updated the pit file and didn't get any errors from Odin. I think the issue I'm stuck with is I don't know what original firmware was on here, so I randomly pick on of the many available ones (like I mentioned previously, I've tried Lollipop and Marshmallow). This time I tried this one:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar
The phone actually boots up and I hear the music of it booting up, but the screen doesn't come one. I can still get to recovery and download mode (but I can't see what I'm doing). Is this a matter of just working my way through the list of firmwares until I find the one that works?
Thanks again

RetroRider said:
Thanks for the quick reply!
I updated the pit file and didn't get any errors from Odin. I think the issue I'm stuck with is I don't know what original firmware was on here, so I randomly pick on of the many available ones (like I mentioned previously, I've tried Lollipop and Marshmallow). This time I tried this one:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar
The phone actually boots up and I hear the music of it booting up, but the screen doesn't come one. I can still get to recovery and download mode (but I can't see what I'm doing). Is this a matter of just working my way through the list of firmwares until I find the one that works?
Thanks again
Click to expand...
Click to collapse
Do you see the "Samsung Galaxy S5" logo when it first boots up? It sounds like the screen went bad.

Fear_The_Fluff said:
Do you see the "Samsung Galaxy S5" logo when it first boots up? It sounds like the screen went bad.
Click to expand...
Click to collapse
It depends on which firmware I flash it with.....usually I get the logo as it's in the bootloop. The only change was when I used that PB1 firmware and it actually booted, minus the screen....

RetroRider said:
It depends on which firmware I flash it with.....usually I get the logo as it's in the bootloop. The only change was when I used that PB1 firmware and it actually booted, minus the screen....
Click to expand...
Click to collapse
Try going into Download/Odin Mode and (first grab some binoculars LOL!) take a look at the top (small letter) information and (you may want to write it down) see what the device information states there.
It just seems as though you may have a specific variant of the S5 that may have been unlocked and flashed to the one you believe that you have...
... OR you are correct with the Variant but, are trying to flash the wrong Firmware Version (one of the previous releases) and the device is preventing it.
I think that it may be the first assumption but, I could be wrong...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

Fear_The_Fluff said:
Do you see the "Samsung Galaxy S5" logo when it first boots up? It sounds like the screen went bad.
Click to expand...
Click to collapse
Ibuprophen said:
Try going into Download/Odin Mode and (first grab some binoculars LOL!) take a look at the top (small letter) information and (you may want to write it down) see what the device information states there.
It just seems as though you may have a specific variant of the S5 that may have been unlocked and flashed to the one you believe that you have...
... OR you are correct with the Variant but, are trying to flash the wrong Firmware Version (one of the previous releases) and the device is preventing it.
I think that it may be the first assumption but, I could be wrong...
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Click to expand...
Click to collapse
here's what I see when I go into download mode:
ODIN MODE
PRODUCT NAME: SM-G900V
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
REACTIVATION LOCK: OFF
QUALCOMM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1, T2, R1, A2, P1
SECURE DOWNLOAD : ENABLE
UDC START
Is there anything there that tells me what version of firmware I should be using?

RetroRider said:
Is there anything there that tells me what version of firmware I should be using?
Click to expand...
Click to collapse
Product name is correct.
I'd flash this one: https://androidfilehost.com/?fid=818070582850486654
It's the latest firmware with full-wipe.
The first boot should take 12-15 min.
If the phone does not boot within 20 min. it will mean a hardware problem.

bricked sm-t580

i have the T580 32GB of a friend here, that does not work at the moment (and maybe never again ) - the problem is that on startup it only gives this message in red letter :
could not do normal boot invalid kernel length
Click to expand...
Click to collapse
the only thing i can do is get into download mode - but i fail when i try to install a stock rom via odin - after NAND Write Start!! it times out and gives me a fail.
i already tried a 3 different odin versions and adroid 6.0, 7.0 and 8.01 Stock Rom for SM-T580 but no luck so far.
another problem is my friend does not know what the android version he was on before that hapend - and the tablet has Samsung FRP on.
maybe some of the experts here have an advice what i can try otherwise this tab a is really bricked - furthermore i wonder how this could happen as my friend swears he did not try to put twrp or anything else onto the tablet ....

Have you tried flashing TWRP using ODIN? (AP Slot)

i do not know if flashing twrp is a good idea as i do not know if oem unlock is enabled - and as it does not boot up i cannot switch it on in developer options

ilovebytes said:
i do not know if flashing twrp is a good idea as i do not know if oem unlock is enabled - and as it does not boot up i cannot switch it on in developer options
Click to expand...
Click to collapse
Wouldn't it simply fail if OEM unlocking was disabled? I don't know honestly. I'd try it if no other solutions come up.

ilovebytes said:
i have the T580 32GB of a friend here, that does not work at the moment (and maybe never again ) - the problem is that on startup it only gives this message in red letter :
the only thing i can do is get into download mode - but i fail when i try to install a stock rom via odin - after NAND Write Start!! it times out and gives me a fail.
i already tried a 3 different odin versions and adroid 6.0, 7.0 and 8.01 Stock Rom for SM-T580 but no luck so far.
another problem is my friend does not know what the android version he was on before that hapend - and the tablet has Samsung FRP on.
maybe some of the experts here have an advice what i can try otherwise this tab a is really bricked - furthermore i wonder how this could happen as my friend swears he did not try to put twrp or anything else onto the tablet ....
Click to expand...
Click to collapse
I think you are going about it wrong. Instead of booting to download mode, try booting to recovery mode via Home, Vol Up and Power and then selecting Factory Reset. This is always necessary before you can use download to flash a ROM via Odin and it might make using Odin unnecessary.

of course i tried to get into receovery mode but the problem is i can't - when i do home, vol up and power absolutely nothing happens, i only get into download mode
edit: i believe FRP is the Problem this prevents odin from writing the files to the tablet - as it allways times out with :
Complete(Write) operation failed.
Click to expand...
Click to collapse
what i do not really understand is why FRP does not let odin flash an original samsung firmware ?

[QUOTE what i do not really understand is why FRP does not let odin flash an original samsung firmware ?[/QUOTE]
This sounds more like a binary issue. I have reason to believe you are what's called an FRP Binary Lock. Recovery is usually inaccessable or re-routed and you cannot "seem" to use Odin3 but in fact you can. This issue you apparently are having sounds oddly like some issues I've had on these devices and is often a result of bad Rooting or invalid firmware being installed. This overloads the binaries and puts the device in a locked mode with symptoms of an inaccessible Recovery a difficult to use Odin3 or a bootloop. Most of the time I hear of a notification somewhere of an FRP lock. If this is the situation you are in here is a link to a page of mine that will give you the files to helpfully solve your issue. Let me know if that works or not.
https://forum.xda-developers.com/general/help/custom-binary-blocked-frp-lock-2019-t3979661

Casper Young said:
If this is the situation you are in here is a link to a page of mine that will give you the files to helpfully solve your issue. Let me know if that works or not.
https://forum.xda-developers.com/general/help/custom-binary-blocked-frp-lock-2019-t3979661
Click to expand...
Click to collapse
it sounds like i am in the same situation and i tried your files but it does not let me download them through odin - i also wrote you a pm maybe you find the time to answer me.
i really wonder how this could happen as my friend swears he did never try to flash anything onto the tab, and i really believe him as he absolutely knows nothing about flashing or where to get a firmware and not even how to get into dl mode ....

ilovebytes said:
it sounds like i am in the same situation and i tried your files but it does not let me download them through odin - i also wrote you a pm maybe you find the time to answer me.
i really wonder how this could happen as my friend swears he did never try to flash anything onto the tab, and i really believe him as he absolutely knows nothing about flashing or where to get a firmware and not even how to get into dl mode ....
Click to expand...
Click to collapse
The situation I was suspecting is a "Custom Binaries are Blocked by FRP Lock" to which you would have seen a notification of it in one of 4 ways. Your situation is somewhat similar because you cannot access Recovey and although Download Mode is accessable it appears useless. Your device is not Bricked. A bricked device is unusable in any way and these days most devices can be restored.
You do seem to be having some difficulties that are usually common with binary issues. You can in fact use Odin3 but how is the question. Usually one can flash in the Stock firmware and that returns the device to normal. When it becomes impossible to flash in stock firmware or anything else it seems, to my experiance has always been a Binary issue. I will provide a link to the 4File Official firmware. And instructions for you to properly use it for your needs.
SM-T580 Official Stock Firmware 4Files
https://drive.google.com/open?id=1zvhwUfSRW44V1ZwEsHLRvlh-T0M79ks9
I'll assume you know something about using Odin3. Unzip the file to your desktop. There are 4 files but you'll only use 3 of them. You can use the patched version of Odin3.13B or you can use Odin3.14. Place the files in their respective places. BL, and AP are easy enough to see where they go. Now there is a file labeled CSC and one labeled HOME CSC. You will only use one of them. The CSC file returns your app data to factory settings (it erases everything). The Home CSC file keeps the app data. So it's your choice which one you choose. These are Official Firmware Files so you should be able to flash them in. Should that not work for you my most likely answer would be that your binaries are the issue and that is why you can't as of yet use Odin sucessfully. Does Odin even try to initiate a flash then stalls or does it do nothing altogether?
There are two different Binary files for the SM-T580 that I have. I would suggest using the Binary 4 FRP first. f I recall correctly the Odin3.13B patched version was made for this. Place the file in the AP section and try flashing it. You should get a few gears on the screen turning if it applied, or maybe not. If that fails use the U4 Binary Unlock file. It is only after you flash in the binary files that you can then install the Stock Firmware. It is the overloaded binaries that prevent the use of Odin as you may be experiancing. I am also including the Knox cleaner in case you need to reset it.
SM-T580 Binary files:
Binary 4 FRP Unlock
https://drive.google.com/open?id=1iXrZR2E7m6Ai5InAw8u3lzeLhb3ThRo5
U4 Binaries. This is two files. Flash one at a time using the AP section. They are labeled 1rst or 2nd
1. https://drive.google.com/open?id=1rX_luP_0W4ygdloIr2Gr9TCSfqFyaTK-
2. https://drive.google.com/open?id=1xsw4GVYtNMJhiMXV2cR2jaJvToG_n6Pi
Knox Cleaner: Also flashed in using the AP section of Odin3
https://drive.google.com/open?id=1EolYe9auY9jslYSpSgHoon_YB00D2noV
Good Luck and let me know if this helps or not.

lewmur said:
I think you are going about it wrong. Instead of booting to download mode, try booting to recovery mode via Home, Vol Up and Power and then selecting Factory Reset. This is always necessary before you can use download to flash a ROM via Odin and it might make using Odin unnecessary.
Click to expand...
Click to collapse
Only if they could get into Recovery they may be able to reset it.
I have never once needed to go to Recovery to do "anything" before using Odin3 to flash.
The only time I've had to go there (repetedly) and reset was when trying to get past FRP Google Account Protection. Sometimes it takes out the page I want to get to and I need to reset it to get to it again. This is "not" always neccesary before flashing a ROM which rewrites the device programing.

sorry for double post

@Casper Young
thanks for your help so far, i am gonna try your suggestions on weekend when i have a bit more spare time - hope i can get the tab running again