Database Users

Need help on unfamiliar error screen. Image provided.

Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
UPDATE <21_03_2015><16_54_09_524>____________________________________________________________
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.

3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app

Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?

intervall said:
I think that this error appears when a ROM isn't flashed properly to the device. So a possible solution might be a factory reset in recovery and a clean ROM flash with Odin. You just need to download a ROM for your device model - SM-N9005 from sammobile or samsung-updates.
Click to expand...
Click to collapse
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
st3chn0 said:
Download an official firmware from sammobile and use odin to flash. It's all on their site
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
3XTR3M1ST said:
Just got the Note3 from a online seller who seems to be legit but when the phone was received via the mail, it didn't work as expected.
I've had some experience with android ROMs and rooting but those are mostly for the other phones, this is the first Samsung phone i got. Could you guys help and advise what to do to resolve this error?
I've actually downloaded Kies3 and use the emergency recover thing, but most of the times it couldn't detect the phone connection.
And on the rare occasion that it does detect something, it says that the model is incompatible with Kies3. Tried it with the old Kies too, but didn't work as well!
Click to expand...
Click to collapse
3XTR3M1ST said:
Is Odin a entirely different piece of software to kies?
Also would you this to be soft brick and reason to demand for compensation from the seller?
Click to expand...
Click to collapse
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.

1. If its possible for him to return to the seller then yes but he can't to samsung. Due to knox being tripped. If he does its just basically a 50/50 chance
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
3. Using odin to flash any official firmware. Is not bad advice.
Sent from my SM-N9005 using XDA Free mobile app

celderic said:
Yes this appears when a rom isn't flashed properly, Or the user has manually soft bricked the device.
I wouldn't take this advice as you bought a phone that is soft bricked with knox tripped (0x1)
try and return it before you attempt to fix it.
It looks like your knox is 0x1 and the system status is 'custom' but i can't really tell as the quality of the pictures isn't good enough.
This means that the phone has been used before and rooted, then a wrong flash or simply just deleting a few system files so it doesn't boot to get that screen to show up instead.
If there is nothing wrong with the hardware, Odin should fix this easily.. but i wouldn't trust it as your imei could of been changed.. many things could of been tampered with.
Also you mention that kies doesn't detect the phone properly, only sometimes. This could be your pc but it is likely a hardware problem with the phone judging by how you recieved it with knox tripped (0x1).
As it has been sold in this condition i can only assume that it has been tampered with. Why else would the seller sell a soft bricked device ?
Was it advertised as new or used?
Return it and get your money back as soon as possible is all i can suggest, good luck.
Click to expand...
Click to collapse
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/

Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone

st3chn0 said:
2. This nothing to do with soft brick. Such thing as a soft brick doesn't really exist.
Click to expand...
Click to collapse
This is a softbrick, if the hardware is fine then you should be able to fix it in 10mins by flashing a stock rom, but as the seller has sold it in this state then i assume it is softbricked for a reason so you can't test the device for example.
cryostasis25 said:
Flashing firmwate from sammobile will not trigger knox so as suggested earlier download and flash a firmware for your phone
Click to expand...
Click to collapse
But his knox is already tripped.. he bought a phone with knox 0x1 that's why i suggested returning it.
3XTR3M1ST said:
The seller is not responding to my questions, so I think the next best bet to attempt and fix it myself. Am I right to think that flashing an official firmware is the best option? What could go wrong if the imei have been changed?
Also, you just got me curious about the knox thing. Where do you suggest I look at for a comprehensive elaboration of the error codes?
http://postimg.org/image/rorg1p21n/
Click to expand...
Click to collapse
If the seller is not responding, then it points to them tampering with the device before selling it. Where did you buy it from, i would ring your bank as soon as possible.
Download the latest n9005 rom from sammobile and flash it through odin if you want to try and fix it, shouldn't really matter what csc as your knox is already tripped anyway so you can't recieve OTA updates or warranty from samsung anymore, mine is a BTU device but i have used many XEO roms.
If the phone isn't connecting to the computer properly like you say, then it's probably best to leave it. As this could result in the connection failing when it is flashing the bootloader or something. But if it works fine, then there should be no problems.
Here is something you could try, start up odin (i use v3.09), close all processes relating to kies, boot the device into download mode, that screen you provided pictures of. Plug the phone in and wait a few minutes to check the connection is stable, move the cable around to make sure the socket and cable are okay. You will see it come up on the top left in odin after windows has installed the drivers.
If this all works fine then flashing a stock rom should fix the device if the hardware is okay.

Just a quick question. From what site did you buy the phone and how did you pay for the phone?
Sent from my SM-N9005 using XDA Free mobile app

Where is a reliable source to download the official firmwares? I cant find it on the samsung site.
Tried http://www.samsungupdate.com/how-to/download-firmware but the file sizes are different on either filehost mirrors and it seems shady.

www.sammobile.com/firmwares/

I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Before flashing
first_flash_no_pit
first_boot_after_first_flash
Second_flash_no_pit
3rd_flash_with_pit

3XTR3M1ST said:
I just tried flashing lollipop from http://forum.xda-developers.com/galaxy-note-3/general/finally-official-5-0-firmware-galaxy-t3029557
It didn't work, with and without the PIT file.
Click to expand...
Click to collapse
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.

sirobelec said:
1. Try flashing the new bootloader and modem first: http://forum.xda-developers.com/galaxy-note-3/general/odin-flashable-lollipop-bootloader-t3058101
2. If flashing modem and bootloader succeeded, try flashing the whole firmware again.
From what I learned from this http://forum.xda-developers.com/showthread.php?p=47287747#post47287747 thread, "invalid ext4 image" errors occur when bootloader is wrong.
Actually, do you have any info with what firmware was this phone last? I think I might have encountered another thread (don't remember it, though) which says that these exact problems occur when trying to upgrade from Jelly Bean 4.3 to Lollipop directly.
Click to expand...
Click to collapse
Thanks for the suggestion. I'll give it a try after a little more research.
I have no idea what the phone was before, or what the seller did to it since he's just not responding anymore.

So I tried flashing the new bootloader as suggested, it seem to have worked to some extent, but then I screw it up again by pulling out the cable before seeing "PASS!". What now?
http://forum.xda-developers.com/showpost.php?p=59616074&postcount=16 said:
iketil said:
Hi the file size should be 58 041 KB
From what I can see from you ODIN log, ODIN has "done its thing"
If you did not uncheck the auto reboot tab, the phone should now be rebooting.
And bootloader and Modem should be updated when its booted up.
Are you still stuck at the "Samsung GALAXY Note3 SM-9005" screen ?
Click to expand...
Click to collapse
I'm still stuck on the "Samsung GALAXY Note3 SM-9005" screen. However I do think that the "hlte_lollipop_bootloader_modem.tar.md5" has "done its thing". I was previously unable to get to the recovery, but I was able to get to this <3e>recovery after flashing.
Also managed to see some logs of "i'm not sure what it is" before the phone went blank. I presume its due to battery going flat.
Later, I tried putting TWRP on it. Starting with "twrp-2.8.3.0-hlte-4.3.img.tar". But being a novice odin user I mistakenly unpluged the phone when odin is showing "RESET!". Then I tried going into recovery using VOLUP+HOME+POWER, and got this screen instead. I'm not sure if removing the phone before "PASS!" in odin could have caused this? Subsequently I tried flashing "twrp-2.7.0.3-hlte-4.3.img.tar" and
"twrp-2.7.2.0-hlte-4.3.img.tar", which resulted in the same error screen about SEANDROID.
I also noticed it increased my KNOX counter?
This is before and after.
Next I tried flashing ""hlte_lollipop_bootloader_modem.tar.md5" again hoping it would fix it. It didnt work. Silly me, this flash does not have a recovery image in it does it?
Anyway, now I dont have a working recover and is still stuck on the "Samsung GALAXY Note3 SM-9005". Thankfully odin mode still work. What should I do next? Please see this thread below for a little background to my problem. Thank you.
http://forum.xda-developers.com/galaxy-note-3/general/help-unfamiliar-error-screen-image-t3059227
Click to expand...
Click to collapse

HORRY SHET!!
I think my phone is asian! I just flashed the latest taiwan firmware released (N9005ZSUGOC3_N9005OZSGOC3_BRI) after flashing the new bootloader and everything works now!
I'm not sure what actually made it work since this is the first taiwan firmware I tried (its all XEO and BOB previously), but big thanks to everyone who helped!

Start Up Fail while installing rom

Ok guys I just recently rooted my first phone. All was well until I tried to install my first ROM. It seemed to be going fine until I got a Screen that said "start up fail" and in small red text at the top it said "Custom Binary Blocked By Secure Boot (Boot. img)" Here is a picture of the screen: http://imgur.com/a/DQ62P
Here is the link to the ROM: http://forum.xda-developers.com/verizon-s7-edge/development/stang5litre-edition-5-0-s7e-t3450208
Any Ideas on what I can do to fix this?

Dizzy.Dylan said:
Ok guys I just recently rooted my first phone. All was well until I tried to install my first ROM. It seemed to be going fine until I got a Screen that said "start up fail" and in small red text at the top it said "Custom Binary Blocked By Secure Boot (Boot. img)" Here is a picture of the screen: http://imgur.com/a/DQ62P
Here is the link to the ROM: http://forum.xda-developers.com/verizon-s7-edge/development/stang5litre-edition-5-0-s7e-t3450208
Any Ideas on what I can do to fix this?
Click to expand...
Click to collapse
Anyone got any ideas on what to do?

Dizzy.Dylan said:
Anyone got any ideas on what to do?
Click to expand...
Click to collapse
I had a similar occurrence while using FlashFire when I accidentally hit the EverRoot option. You'll have to put it into download mode and ODIN a stock ROM onto it. Then ROOT and upgrade as usual being careful not to hit the EverRoot. Hope it helps.

otterdad said:
I had a similar occurrence while using FlashFire when I accidentally hit the EverRoot option. You'll have to put it into download mode and ODIN a stock ROM onto it. Then ROOT and upgrade as usual being careful not to hit the EverRoot. Hope it helps.
Click to expand...
Click to collapse
I never hit EverRoot and I've tried it twice now and still havent gotten it to work Could it be something to do with the firmware?

Hey man, sorry to hear about this, I'm not exactly sure your problem, but I guess I would start by re-flashing the ENG Boot for your device (via Odin) - assuming that's the root method you used (you can find it here if you haven't got it elsewhere) Otherwise you could flash your device's stock firmware via Odin and then you could try following this guide here for rooting, and retry everything, which is what I would recommend.
I used that guide for my brother's SM-G935V and it has worked "flawlessly", I haven't tried installing a ROM on it yet but it should work as long as the ROM itself works, - I say "flawlessly" because there are a few issues with rooting this phone, but you can easily work around all of them.
I would recommend explaining and detailing your problem as much as you possibly can, in this post and in future posts, so that you can get as much help as possible.. if you need any clarification on anything, let me know, and be careful, for your first phone experimenting ,there's a lot of sh** that can go wrong! Keep in mind that you can fix most problems by flashing your stock firmware with Odin if all else fails.
Best of luck to you, let me know how it goes.

Phone stuck in bootloop after device reset and installing stock rom

The phone of my girlfriend has been stuck in a bootloop for a few days. It happened while she watched a video. Apparently at the same time she got a message that her phone ran out of space. Then it crashed and has been stuck in the loop since then. Her phone is not rooted. She did restore the device to default settings using recovery mode. This didn't do anything however.
I've tried using ODIN 3.12.3 to flash the newest rom from sammobile since her carrier is T-Mobile. I followed a guide from adnroid central since I never had done anything like this before. It all worked as far as ODIN goes but is still stuck in the bootloop. I'd link the guide but I need 10 posts before I can include outside links.
I'm not sure what the next step would be. If I should try an older ODIN version or use a different stock rom. Before the whole incident her android version was 6.0.1 I believe. Also in the download mode the product name is SMG-900T.
I hope someone can point me in the right direction on what to do. Thank you!

beerbat123 said:
The phone of my girlfriend has been stuck in a bootloop for a few days. It happened while she watched a video. Apparently at the same time she got a message that her phone ran out of space. Then it crashed and has been stuck in the loop since then. Her phone is not rooted. She did restore the device to default settings using recovery mode. This didn't do anything however.
I've tried using ODIN 3.12.3 to flash the newest rom from sammobile since her carrier is T-Mobile. I followed a guide from adnroid central since I never had done anything like this before. It all worked as far as ODIN goes but is still stuck in the bootloop. I'd link the guide but I need 10 posts before I can include outside links.
I'm not sure what the next step would be. If I should try an older ODIN version or use a different stock rom. Before the whole incident her android version was 6.0.1 I believe. Also in the download mode the product name is SMG-900T.
I hope someone can point me in the right direction on what to do. Thank you!
Click to expand...
Click to collapse
Have you tried flashing the marshmallow boot loader in odin?

RomBetaTester said:
Have you tried flashing the marshmallow boot loader in odin?
Click to expand...
Click to collapse
I'm not sure what you mean since I'm quite new to anything android. Would this be what you are talking about? I know it says only for S5 G900F and I have the G900T but would the overall process be the same?
Thank you for the reply though!

beerbat123 said:
I'm not sure what you mean since I'm quite new to anything android. Would this be what you are talking about? I know it says only for S5 G900F and I have the G900T but would the overall process be the same?
Thank you for the reply though!
Click to expand...
Click to collapse
Google search for marshmallow bootloader and flash it through Odin. I am very good with android. I can fix your problem. Is there anyway you could direct message me?

Galaxy S8 bricked - Stuck in boot loop after flashing twrp

Hey there everyone,
I wanted to root my s8 (sm-950f) and when I flashed twrp my phone initially got stuck in Samsung logo. After managing to shut it down I tried to go to recovery mode to wipe everything and perform a factory reset but I can not do it. All that happens is I get to s8 screen and it reads in red on top left of the screen "Only official released binaries are allowed to be flashed" and it keeps resetting itself. I can access download mode but that's it, I can't do anything else. Currently downloading a stock firmware to try and flash it but with the free downloads it's taking its time. Any help appreciated, I really want to unbrick my phone
note: It shows FRP and OEM lock to be off in download mode, i dont even know if i'll even be able to flash a new fw. Do I just have a very expensive brick in my hands now?

nekropok said:
Hey there everyone,
I wanted to root my s8 (sm-950f) and when I flashed twrp my phone initially got stuck in Samsung logo. After managing to shut it down I tried to go to recovery mode to wipe everything and perform a factory reset but I can not do it. All that happens is I get to s8 screen and it reads in red on top left of the screen "Only official released binaries are allowed to be flashed" and it keeps resetting itself. I can access download mode but that's it, I can't do anything else. Currently downloading a stock firmware to try and flash it but with the free downloads it's taking its time. Any help appreciated, I really want to unbrick my phone
Click to expand...
Click to collapse
This must be a international S8... Did you activate oem unlock in developer settings before flashing twrp
([emoji3590]09-09-18[emoji3590])

I'm not sure if it's international, it's most likely a Turkish version.
And yeah to your question

nekropok said:
I'm not sure if it's international, it's most likely a Turkish version.
And yeah to your question
Click to expand...
Click to collapse
But you know for a fact that there's a twrp version for your device.... Not good to do these expensive phones like that without officially having all the facts
([emoji3590]09-09-18[emoji3590])

Well it's too late for that now, I need actual solutions. I also tried smart switch - it doesn't recognize the phone

nekropok said:
Well it's too late for that now, I need actual solutions. I also tried smart switch - it doesn't recognize the phone
Click to expand...
Click to collapse
On the xda thread for your device there aren't no stock roms uploaded to Android host for fast download so you can flash in Odin and start the process of twrp again or just leave it alone you have a S8 it's good money
([emoji3590]09-09-18[emoji3590])

WHEW. Flashing a stock firmware seems to have fixed the issue. Mods can lock the thread.

nekropok said:
WHEW. Flashing a stock firmware seems to have fixed the issue. Mods can lock the thread.
Click to expand...
Click to collapse
You going to give up on twrp
([emoji3590]09-09-18[emoji3590])

I do want to root, but I don't want to approach it without knowing all my facts, do you have any suggestions for guides for Android 9.0?

nekropok said:
I do want to root, but I don't want to approach it without knowing all my facts, do you have any suggestions for guides for Android 9.0?
Click to expand...
Click to collapse
Just look in your device forum everything Is there however your device is a international cause it ends in with the F so twrp does work for your device..... You just need to find the specific one for your model once you have twrp you can install a android 9 custom rom
([emoji3590]09-09-18[emoji3590])

I had same issue as you and was pointed towards this thread may be of some use to you?
https://forum.xda-developers.com/sa...w-to/guide-root-install-twrp-samsung-t3747535

Problem on my S8
PoochyX said:
This must be a international S8... Did you activate oem unlock in developer settings before flashing twrp
([emoji3590]09-09-18[emoji3590])
Click to expand...
Click to collapse
Sorry but I have a serious problem. I have activated oem and debug usb on developer option, but I can't install TWRP. I have tried with odin, prince cosmy odin, odin patched but FAIL everywhere, please help me, I just want twrp and i want to install a custom rom. thanks in advance everyone. If is a problem answer me here, you can send me a pvt message. I tried it from 3 days with the same FAILS :_(

I had this problem too a year ago but wasn't able to reflash the official firmware, but when I went to Samsung they fixed it for free even though Knox was already tripped

FabiusMod said:
Sorry but I have a serious problem. I have activated oem and debug usb on developer option, but I can't install TWRP. I have tried with odin, prince cosmy odin, odin patched but FAIL everywhere, please help me, I just want twrp and i want to install a custom rom. thanks in advance everyone. If is a problem answer me here, you can send me a pvt message. I tried it from 3 days with the same FAILS :_(
Click to expand...
Click to collapse
are you able to flash the stock firmware on it and get it to boot without TWRP installed?

I am with a stock rom now, The device works fine.

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