Database Users

[Resolved via warranty] Phone bricked overnight and Re-Partition operation failed

Hello everyone,
Upon waking up this morning, I found that my phone was stuck on the (very first) Samsung logo. Before going to sleep, I was already booted and everything was stable.
I attempted to enter CWM recovery, but it would not work. It would continue to show the Samsung logo.
Entering download mode, I see the following -
Product name:
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Custom
This is strange, and pretty wrong. My product name is empty, custom binary download is "No" instead of at least "3" (I never have used TriangleAway), and I wasn't using an official Samsung ROM before the problem.
The very first thing I tried was flashing the Siyah .tar file. I get this:
"<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> boot.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed."
If I attempt to flash a full, multi-part .tar.md5 file in PDA, ODIN v3.04 shows a "There is no PIT partition." error and fails. Re-partition is not ticked.
Therefore, I've tried to flash each of the following, with re-partition ticked:
GT-I9300_mx_20120220.pit
GT-I9300_mx_20120322.pit
GT-I9300_mx_20120329.pit
Each of them fail with a "Re-Partition operation failed." error.
If I try to flash a .pit file and the full .tar.md5, I get the same "Re-Partition operation failed." error. The same happens when I try to flash the .pit and Siyah at the same time.
Once a flash fails, I need to turn my phone off and on into download mode again, or else ODIN will stop on "<ID:0/004> SetupConnection.." and not continue for every type of flashing attempt.
The same thing happens for both ODIN v1.85 and v3.04, I've taken my battery in and out, I've tried this on two different computers, I've used every USB port, my Samsung drivers are up to date and Kies it not running in the background.
I've searched Google and XDA for hours, and I'm pretty sure the the problem I need to resolve is the "Re-Partition operation failed." error. However, almost no one on the internet has ever had this error.
The absolute very last abnormal thing I did with my phone was use the app "GetRIL" app as recommended on page 857 of the Siyah thread. The process said it succeeded, but the RIL didn't match the Baseband in the end. My phone was completely functional after, and I don't think the app even asked for root privileges at any point, so I'm not sure if it could have been capable of causing an issue this dire.
Is there anything I can do? I just can't imagine how my phone could have broken itself overnight while charging...
Any help would be greatly appreciated.

Go back to CWM and do a full wipe.
If that doesn't work I would suggest you find the nearest service centre.

Kangburra said:
Go back to CWM and do a full wipe.
If that doesn't work I would suggest you find the nearest service centre.
Click to expand...
Click to collapse
CWM is completely inaccessible!
I'll try a service centre after I've tried absolutely everything with this phone... I don't think I'm covered by warranty after rooting (Although they maybe won't be able to tell given how messed up the download mode seems to be right now)

Same problem here!
I have exactly the same problem! I've tried everything and I couldn't fix it.
People that are genius at this stuff:
PLEASE HELP! I am going crazy about this and I don't think that here in Argentina somebody can offer a solution!:crying:

nicoroldan1 said:
I have exactly the same problem! I've tried everything and I couldn't fix it.
People that are genius at this stuff:
PLEASE HELP! I am going crazy about this and I don't think that here in Argentina somebody can offer a solution!:crying:
Click to expand...
Click to collapse
If you can't get to recovery then you must return to Samsung.

Kangburra said:
If you can't get to recovery then you must return to Samsung.
Click to expand...
Click to collapse
The international model has international warranty? I bought this phone abroad (in the US) and i'm from Argentina, the warranty will cover the repair?

nicoroldan1 said:
The international model has international warranty? I bought this phone abroad (in the US) and i'm from Argentina, the warranty will cover the repair?
Click to expand...
Click to collapse
I don't know, it would depend on your terms of warranty.
If you are stuck you could try to unbrick it yourself.

Mine woke up to the exact same thing. Sadly I don't have a solution for you, this happened 1 week after being bought so I just had it replaced. I had not modified it in any way nor I tried any repair on my own (no reason to).
Sorry for your phone bro... id still try sending it to Samsung, if it's that screwed maybe they won't try to figure what happened.
Sent from my GT-I9300 using XDA Premium App

I dont think you need to flash use a pit file at all tbh. Try getting a fresh stock image from sammobile.com and flash the tar file without clicking the re-partition box. I use to use .pit files all the time with the galaxy s and sii but for i9300 i've never had to. hope this helps

kart_y_26 said:
I dont think you need to flash use a pit file at all tbh. Try getting a fresh stock image from sammobile.com and flash the tar file without clicking the re-partition box. I use to use .pit files all the time with the galaxy s and sii but for i9300 i've never had to. hope this helps
Click to expand...
Click to collapse
It's not working, even with an enormous 1.59gb tar which matches my country and carrier... Same old "<ID:0/003> There is no PIT partition." error.
If I use ODIN v3.07 I get a freeze on "<ID:0/003> Get PIT for mapping.." when attempting to flash the .pit. I've also tried flashing mx.pit.
I've even tried moving every file directly onto the root of C:\, but nothing is changing.
It's surprising that my phone could get so bricked by itself. :silly:

I would suppose the nand chips are damaged for whatever reasons, which makes a trip to the service center inevitable.

aegixnova said:
It's not working, even with an enormous 1.59gb tar which matches my country and carrier... Same old "<ID:0/003> There is no PIT partition." error.
If I use ODIN v3.07 I get a freeze on "<ID:0/003> Get PIT for mapping.." when attempting to flash the .pit. I've also tried flashing mx.pit.
I've even tried moving every file directly onto the root of C:\, but nothing is changing.
It's surprising that my phone could get so bricked by itself. :silly:
Click to expand...
Click to collapse
I know. It is strange. Actually after posting in this thread i was reading around in the q&a section and one of the users was told by the service centers that its a motherboard issue. The tar file that you downloaded. Is it ics or jb? Just asking cause because ics might be a safer bet to try and restore.
Sent from my GT-I9300 using xda app-developers app

kart_y_26 said:
I know. It is strange. Actually after posting in this thread i was reading around in the q&a section and one of the users was told by the service centers that its a motherboard issue. The tar file that you downloaded. Is it ics or jb? Just asking cause because ics might be a safer bet to try and restore.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
It's a stock ICS taken from sammobile.
I've tried running ODIN v3.07 on my 32bit Windows 8 tablet, and my 64bit Windows 8 notebook across both 1.5.4 as well as 1.5.5 Samsung drivers, in both XP compatibility mode and default. Nothing.
Windows updates the drivers after my phone enters download mode, so I've tried flashing both before and after the driver download and installation. Same result.
I haven't tried running ODIN v3.07 on my Windows 7 computer (But I have for v3.04), so I'll give it a go later. I think I know what the result will be

I've given up, and will contact Samsung to get the phone repaired by them. I'll edit this post or bump the thread later with details of how the warranty was handled. I'm hoping that the end result will be favorable for me.
Thanks for the help, everyone. :good:

Same thing happend to me :/ Tried to flash PIT partition via odin again and it failed! Official service center voided my warranty. My phone is now at the unofficial service and i am waiting if it can be unbricked! He said if the phone gets to DL mode it should be OK!

Good luck buddy
Sent from my GT-I9300 using xda premium

I took my phone to an unofficial phone repair shop, 'Fonebiz'.
They replaced the entire phone circuit board within the hour, and Samsung was billed due to my phone still being under warranty. I don't know whether they were unknowledgeable of warranty checking procedures, uncaring of warranty procedures, or simply could not tell due to the extent of the phone's brokenness. Needless to say, I lost the contents of my internal SD, but thankfully most things were backed up.
Either way, I recommend unofficial repair centres which can be funded by Samsung, and my few days without the phone really let me appreciate the quality of the product and service I received.
I'm guessing that the problem was either a pure hardware fault, or Siyah kernel's dual-booting functionality messing up how partitions can be flashed to the phone. I'm not placing blame on anything, however.
I'm very pleased with both Samsung and the end result. :good:
I wish the very best of luck to everyone. This seems to be one of the few ways these solid phones can be bricked, and it's heartening to see that it can be resolved under warranty.

hey,
thanks for making this thread.
it is indeed devastating to find that other people experience my same problem and how they needed to replace the phone
i did nothing to my phone, no root, original firmware.
maybe dropped it once or twice but it worked fine afterwards for plenty of time.
last night i went to bed after putting it to charge as i usually do, while it was on and perfectly working.
this morning it was showing the s3 logo (weird thing is that the led was flashing as if the phone was still on and notifying about new emails)
then everything happens as in the OP
- no stock recovery abailable - reboot loop showing only the logo and nothing else
- normal boot stuck only showing the logo
- people haven't been mentioning this but: with the phone completely off, if i connect the charger it shows the battery empty with just the "in progress" circle and nothing else happens..
- download mode accessible but no "product name", and the unseen before "system status: custom"?
- what does that mean? anybod with a working s3 can tell us what they have in download mode? much appreciated
- all the while firmware is "samsung official" and custom binary is "no"
1. are people certain i cannot bring this back to life?
2. can anybody suggest a way to maybe retrieve at least some of my data?
3. warranty is a little tricky - bought on ebay.... anybody claim warranty in this situation? or have any pointers how to go about it?
4. if not, anybody know a repair shop it the UK that would handle it the way it was mentioned here? i.e. replace the motherboard and bill samsung since still in warranty?
thanks all for help in my time of despair

DorinAlex said:
4. if not, anybody know a repair shop it the UK that would handle it the way it was mentioned here? i.e. replace the motherboard and bill samsung since still in warranty?
thanks all for help in my time of despair
Click to expand...
Click to collapse
http://www.freesamsungrepairs.com/

[Q] Bricked i9505

This morning I was attempting to update the firmware on my i9505.
I downloaded and extracted the .tar.md5 file and opened Odin in administrator mode.
Stupidly I then added the downloaded file as Phone and not PDA and pressed start in Odin. Unsurprisingly it failed.
I downloaded and tried other firmware (as Phone) before I realised my error.
When I boot the phone "normally" I get the failed firmware update message and have tried Kies but it can't connect to the phone.
Download mode does work, but when I try with the firmware (stock and pre-rooted) as PDA it always fails.
Can someone please help to recover my phone? I'm feeling pretty stupid just now

floydart said:
This morning I was attempting to update the firmware on my i9505.
I downloaded and extracted the .tar.md5 file and opened Odin in administrator mode.
Stupidly I then added the downloaded file as Phone and not PDA and pressed start in Odin. Unsurprisingly it failed.
I downloaded and tried other firmware (as Phone) before I realised my error.
When I boot the phone "normally" I get the failed firmware update message and have tried Kies but it can't connect to the phone.
Download mode does work, but when I try with the firmware (stock and pre-rooted) as PDA it always fails.
Can someone please help to recover my phone? I'm feeling pretty stupid just now
Click to expand...
Click to collapse
do you have custom recovery that you can boot into it?

samersh72 said:
do you have custom recovery that you can boot into it?
Click to expand...
Click to collapse
djembey sent me a couple of files and a ROM passed in Odin.
I don't think it's loading though as it's stuck on the SAMSUNG logo (and has been for about 15 mins) ....

floydart said:
djembey sent me a couple of files and a ROM passed in Odin.
I don't think it's loading though as it's stuck on the SAMSUNG logo (and has been for about 15 mins) ....
Click to expand...
Click to collapse
remove battery then insert it, boot into recovery, wipe cache and data, reboot

samersh72 said:
remove battery then insert it, boot into recovery, wipe cache and data, reboot
Click to expand...
Click to collapse
I rebooted to recovery and did a wipe data then a wipe cache. Recovery crashed and the phone rebooted.
This time the boot sound played completely and my phone is back to initial setup screen - thank you :good:

floydart said:
I rebooted to recovery and did a wipe data then a wipe cache. Recovery crashed and the phone rebooted.
This time the boot sound played completely and my phone is back to initial setup screen - thank you :good:
Click to expand...
Click to collapse
Did you feel the adrenalin flowing? I thought I bricked mine earlier. We had a mini power cut half way through flashing and it booted up with "Connect to Kies to do emergency firmware upgrade" or something like that. lol
Felt the cheeks of my bum twitch a bit there. lol
Managed to reflash one of the few stock ROMS I have to hand.

artnada said:
Did you feel the adrenalin flowing? I thought I bricked mine earlier. We had a mini power cut half way through flashing and it booted up with "Connect to Kies to do emergency firmware upgrade" or something like that. lol
Felt the cheeks of my bum twitch a bit there. lol
Managed to reflash one of the few stock ROMS I have to hand.
Click to expand...
Click to collapse
Aye, you could say that
I would say that I won't try flashing again after 3 or 4 hours sleep, but knowing me I probably will ....

S4 bricked after freeze during unmount internal sdcard
Dear friends. I need your help!
I did the actualization on my S4 i9500 (I9500XXUAMDK with root) and after this, I was trying to put more space in my SDcard (editing vold fstab files). During this process, appeared a message on phone about one error in sdcard and it suggested me to unmount the sdcard to try solve the problem. So, when I click yes, the phone froze and then I turned it off, but now it dont pass to Sangung Logo and the phone just go in recovery mode. In recovery mode I tryied clear/mount/unmount some file, but return with error to mount any directories.
I think the phone have the files or some partition corrupted!!! I can access it through ODIN and adb shell as well. There is (in adb commands) a command to fix the partition? How can I do?
I can access the phone in ODIN, and I tried to re-install the original FW. It did well (OK for update), but the phone cant finish the instalation after, because it cant mount anything. And returns to recovery mode with many messages about it cant mount directories.
Every thing I try to do, the phones (in recovery mode) returns "cant mount... or error to mount". I as said, I cant clear cache, format /sdcard or other directory or reset to factory data as well (because I think, the system cant mount any directories).
Somebody had this problem or could help me to solve it, please!!!
Tks in advance!
Barros

rgbarros said:
Dear friends. I need your help!
I did the actualization on my S4 i9500 (I9500XXUAMDK with root) and after this, I was trying to put more space in my SDcard (editing vold fstab files). During this process, appeared a message on phone about one error in sdcard and it suggested me to unmount the sdcard to try solve the problem. So, when I click yes, the phone froze and then I turned it off, but now it dont pass to Sangung Logo and the phone just go in recovery mode. In recovery mode I tryied clear/mount/unmount some file, but return with error to mount any directories.
I think the phone have the files or some partition corrupted!!! I can access it through ODIN and adb shell as well. There is (in adb commands) a command to fix the partition? How can I do?
I can access the phone in ODIN, and I tried to re-install the original FW. It did well (OK for update), but the phone cant finish the instalation after, because it cant mount anything. And returns to recovery mode with many messages about it cant mount directories.
Every thing I try to do, the phones (in recovery mode) returns "cant mount... or error to mount". I as said, I cant clear cache, format /sdcard or other directory or reset to factory data as well (because I think, the system cant mount any directories).
Somebody had this problem or could help me to solve it, please!!!
Tks in advance!
Barros
Click to expand...
Click to collapse
Why on Earth would you mess around with stuff like that? I hope you get help here, and next time just flash it and don't mess around. Perhaps get an external SDCard to solve your "space" problem.

artnada said:
Why on Earth would you mess around with stuff like that? I hope you get help here, and next time just flash it and don't mess around. Perhaps get an external SDCard to solve your "space" problem.
Click to expand...
Click to collapse
hehehe... I agree totally with you. But, it wasnt brick because there is some mistake in vold.fstab edition (I suppose). My fault is to accept unmout sugestion in the phone message.
But, it has a soft brick now. I got the access thought adb and odin and I'm trying to find a valid pit to rebuild the partition, that I think is corrupted now (I cant mount anything there. I can access it, but not change anything there).
I found a post here that there is a pit file. I cant ask there because I dont have enough privileges to post in development topic. The links are http://forum.xda-developers.com/showthread.php?t=2217777 and http://forum.xda-developers.com/showthread.php?t=2214865
I´d like to know if this pit (the second link has a file attached), is a valid pit. If yes, I could fix the phone!!!
Tks

rgbarros said:
hehehe... I agree totally with you. But, it wasnt brick because there is some mistake in vold.fstab edition (I suppose). My fault is to accept unmout sugestion in the phone message.
But, it has a soft brick now. I got the access thought adb and odin and I'm trying to find a valid pit to rebuild the partition, that I think is corrupted now (I cant mount anything there. I can access it, but not change anything there).
I found a post here that there is a pit file. I cant ask there because I dont have enough privileges to post in development topic. The links are http://forum.xda-developers.com/showthread.php?t=2217777 and http://forum.xda-developers.com/showthread.php?t=2214865
I´d like to know if this pit (the second link has a file attached), is a valid pit. If yes, I could fix the phone!!!
Tks
Click to expand...
Click to collapse
i think it is the right pit file for I9500 "Adonis.pit"

samersh72 said:
i think it is the right pit file for I9500 "Adonis.pit"
Click to expand...
Click to collapse
+1
@rgbarros: That is for I9500. Do not try it for I9505

stress nsitylf
samersh72 said:
i think it is the right pit file for I9500 "Adonis.pit"
Click to expand...
Click to collapse
Tks samersh72. I'll try it and I'll give the feedback after. :fingers-crossed:

demlasjr said:
+1
@rgbarros: That is for I9500. Do not try it for I9505
Click to expand...
Click to collapse
Tks demlasjr. My phone is a i9500 (not the ...905).
I run the adonis.pit on pit magic and it generated a analisys report (attached). Before I put it to run on ODIN, you (or somebody) could give a feedback about the entry memory below:
----------------------------------------------------------
Entry Memory Address: 0x754
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 12
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 196.608
Block Count: 16.384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CDMA-RADIO
Flash FileName: modem_cdma.bin
FOTA FileName:
My doubt is about the Partition Name CDMA-RADIO. Is this correct for a i9500 S4? I just really confirm and just to avoid to brick totally my phone, because when I run this pit through ODIN, or fix it or break it (no more chances to revive it)!!!
Tks very much!!!

I've seen that you have the 9500 later, but the forum was down and I couldn't edit my post. On that thread is a discussion about it. Somebody days that may be from 9502. I just seen the art you posted there, try adding this info too, including the pit magic report. Kinda hard to get confirmation and a trustful pit yet.
Sent from my GT-I9300 using Tapatalk 2

demlasjr said:
I've seen that you have the 9500 later, but the forum was down and I couldn't edit my post. On that thread is a discussion about it. Somebody days that may be from 9502. I just seen the art you posted there, try adding this info too, including the pit magic report. Kinda hard to get confirmation and a trustful pit yet.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Dear demlasjr, the forum was down and I forgot to attach the pit magic report when the forum goes up. Im attaching the files now (magic pit report and the adonis.pit that I got in other topic about S4 forum).
If you (or somebody) could help me to analyse it and give us a feedback if this pit is a valid pit for samsung S4 i9500, I will thank a lot!!!
Ps.: I´m trying to solve the problem too, looking for a way to mount the files through adb shell, because I got access my phone with this way and I can see all the files inside there. I just cant to mount any drive yet. Is it possible the problem be only a vold.fstab file corruption or missed? And in this case, is only to solve this file (vold.fstab) to revive my phone?
Or there is a some command in adb shell that could repair the structure files (like scandisk for dos?). I'm newbie on linux and I'm trying to use fsck command, but it returns a error message (fsck: not found). I dont know if I'm putting a correct/complete command to scan and repair the system/drives/files (or if there is a error)...
So, I´m trying to solve it using 3 differents ways of thinking (finding a valid pit, edit/restore vold.fstab and find a correct adb command line to scan and repair eventually corrupt files/directories) and if I solve the problem, I'll be happy to post a tuto here to help some other guys in the future.
Until there, Im working to find a solution.
Tks for help me!!!

nothing worse than this feeling. I remember when I did this to my S2, felt a cold sweat instantly... :crying:

crimptool said:
nothing worse than this feeling. I remember when I did this to my S2, felt a cold sweat instantly... :crying:
Click to expand...
Click to collapse
I agree totally with you my friend!!! I put it down in the first day I bought it... Its terrible!!! hehehe I put other phones down too, but how the others were olds phones (more then 6 months in the market), always I found the cfw or pit's to revive...
S4 is a newest phone, so, there is not a consistent or many topics/files/cfw tested yet. I´m looking for 3 full days about this and I found a lot of topics in how to root/unroot the phone, but not yet about pits, commands, etc...
The problem is that phone has a corruption files inside (my first diagnostic) and this is avoid to flash any firmware there until I fix this problem.
I´m trying to keep calm to avoid to worst the situation. I can access the phone yet, so I see a light in the end of tunnel yet!!!
But, the feeling is terrible!!! hahaha

Until Odia or GSMCN came back to you, we can't help you my friend. Only them can confirm the .pit file comparing the one already published with his phone's pit file.
One question....what if you try Emergency recover in KIES. Connect your phone to pc, open KIES, open emergency recover and insert your phone serial number. I read that people messed some times with the partitions and KIES saved their phone. It will not hurt to try, KIES is a putty compared with the repartitioning.

demlasjr said:
Until Odia or GSMCN came back to you, we can't help you my friend. Only them can confirm the .pit file comparing the one already published with his phone's pit file.
One question....what if you try Emergency recover in KIES. Connect your phone to pc, open KIES, open emergency recover and insert your phone serial number. I read that people messed some times with the partitions and KIES saved their phone. It will not hurt to try, KIES is a putty compared with the repartitioning.
Click to expand...
Click to collapse
I tried to connect it in KIES, but KIES didnt recognizes the phone. I'll try once again!!! I think I really discovered what the problem is, reported by adb parted command in /dev/block/mmcblk0: "error: Both the primary and backup GPT tables are corrupt. Try making a fresh table, and using Parted´s rescue feature to recover partitions"
So, probably when the phone froze during unmounting sdcard, the partitions were corrupted. I'm really thinking to use the adonis.pit, due I think there is no other manner to solve the problem.
I'm waiting any reply from Odia, to see if him can help me. Otherwise, I'll cross fingers and press "enter", to see what happen!!!
My friend, tks for all!!! After I´ll post the results!!! :fingers-crossed:

[Q] Changing CSC with Know 0x0 + update parts of the firmware

Hello!
I post here since I have many question mostly related to the CSC which seems to lock everything up right now. BIG Thanks to the XDA community which is the most expert about Android on the web!
I have a French Note 3 4G already rooted with URDLV without tripping Knox.
Please, I want to :
- upgrade my firmware (from MI7 to ... ??? I have Mobile Odin already)
- be able to change the CSC to find a ROM more adapted to my local network (Thailand). I lost the connection many times because of that.
WATCH OUT! There is only the exynos version in Thailand so I don't know which ROM (Malaysia, Vietnam ??) would be the best.
My CSC is N9005BOGBMI3_BOG. I have currently the MI7 version (AP : N9005XXUBMI7). I froze Knox with Titanium.
So, how..
- can I change of ROM without tripping KNOX ?
- can I install CRMW without tripping KNOX ?
- update my phone without tripping KNOX ?
- change my modem/RILS without tripping....... KNOX!?
- can I send a insulting email to Samsung in order to clearly express what I think about their new policy!!
I already downloaded this ROM (BOG-N9005XXUDMJ7-20131121184400) can I flash it and how ?
Thank you very very much and merry Xmas!!

Nemorensis32 said:
...
So, how..
- can I change of ROM without tripping KNOX ?
- can I install CRMW without tripping KNOX ?
- update my phone without tripping KNOX ?
- change my modem/RILS without tripping....... KNOX!?
- can I send a insulting email to Samsung in order to clearly express what I think about their new policy!!
I already downloaded this ROM (BOG-N9005XXUDMJ7-20131121184400) can I flash it and how ?
...
Click to expand...
Click to collapse
0) Backup your current EFS! Is your phone unlocked? Did you have any problems as a result of EU region-lock? Also note that changing the CSC will not make any change in how the modem works, so no change in signal quality.
1) Flash that MJ7 with Mobile Odin PRO - read details in the specific thread that explains how you can use MOP to upgrade and keep root (and knox 0x0). MJ7 will improve and fix a lot of things.
2) No, at this point ANY kernel or recovery that is not signed my Samsung WILL trip Knox
3) You keep updating using MOP
4) Modem will be updated automatically when you do 1) and 3)
5) You can, but I doubt it will make any difference.

xclub_101 said:
0) Backup your current EFS! Is your phone unlocked? Did you have any problems as a result of EU region-lock? Also note that changing the CSC will not make any change in how the modem works, so no change in signal quality.
1) Flash that MJ7 with Mobile Odin PRO - read details in the specific thread that explains how you can use MOP to upgrade and keep root (and knox 0x0). MJ7 will improve and fix a lot of things.
2) No, at this point ANY kernel or recovery that is not signed my Samsung WILL trip Knox
3) You keep updating using MOP
4) Modem will be updated automatically when you do 1) and 3)
5) You can, but I doubt it will make any difference.
Click to expand...
Click to collapse
Thanks for your answer ! However, a little precision please . The ROM you told to flash doesn't have the same original CSC than I had. Is it possible to do that ?
Other thing, I was talking about changing my modem/RIL in order to get a better hook where I live (each modem are customed in order to work as well as possible with each local related network).
And just now, I use an app called EFS to backup my EFS and then my NVRAM. I lost my connexion.... Not SIM inserted it says!! :'( :'(

Nemorensis32 said:
Thanks for your answer ! However, a little precision please . The ROM you told to flash doesn't have the same original CSC than I had. Is it possible to do that ?
Other thing, I was talking about changing my modem/RIL in order to get a better hook where I live (each modem are customed in order to work as well as possible with each local related network).
And just now, I use an app called EFS to backup my EFS and then my NVRAM. I lost my connexion.... Not SIM inserted it says!! :'( :'(
Click to expand...
Click to collapse
The second/newer ROM that you listed had the same region/carrier as the 1st that you listed (and which I assumed it was the original one) = BOG (which I believe is a French carrier). Of course the newer one is not the same version, it is a newer one for that same region/carrier. Of course all assuming that I understood correctly and that your initial CSC region/carrier was BOG.
The change in modem is more carrier-specific than region-specific, in the very first step I would recommend avoiding that, see first how the new BOG modem does under your current conditions.
Hmm, the EFS backup is just a read and should not result in such problems - the app probably tried to do something like unmounting the partition. Just fully reboot the phone and as long as no destructive write was done to that partition things should be back to your previous state (and assuming that the app indeed unmounted the EFS partition then it is very likely it also made a good backup).

xclub_101 said:
The second/newer ROM that you listed had the same region/carrier as the 1st that you listed (and which I assumed it was the original one) = BOG (which I believe is a French carrier). Of course the newer one is not the same version, it is a newer one for that same region/carrier. Of course all assuming that I understood correctly and that your initial CSC region/carrier was BOG.
The change in modem is more carrier-specific than region-specific, in the very first step I would recommend avoiding that, see first how the new BOG modem does under your current conditions.
Hmm, the EFS backup is just a read and should not result in such problems - the app probably tried to do something like unmounting the partition. Just fully reboot the phone and as long as no destructive write was done to that partition things should be back to your previous state (and assuming that the app indeed unmounted the EFS partition then it is very likely it also made a good backup).
Click to expand...
Click to collapse
Now I'm confused.
You talk about BOG as a carrier when I talk about CSC. Indeed, this is the same CARRIER but it seems to not be the same CSC since it didn't appeared in sammobile web while I search for all ROMs based on this CSC.
About the IMEI, my main problem now. I just reflashed a ROM modified by VEGA. It still bootloops !!!
I heard on that topic that we could wipe our EFS partition since the phone is able to rebuild it itself but I doubt about my own understanding here.. Maybe I could use in ODIN the option "Phone EFS clear" ?? http://forum.xda-developers.com/showthread.php?t=2471421
Please, I would really appreciate some help here!!
EDIT : Here is the damn software with what I bricked my phone. Maybe the comments can help you or anyone willing to save my all new phone. That's Xmas ... lol
https://play.google.com/store/apps/details?id=nl.boris.efs

Nemorensis32 said:
Now I'm confused.
You talk about BOG as a carrier when I talk about CSC. Indeed, this is the same CARRIER but it seems to not be the same CSC since it didn't appeared in sammobile web while I search for all ROMs based on this CSC.
About the IMEI, my main problem now. I just reflashed a ROM modified by VEGA. It still bootloops !!!
I heard on that topic that we could wipe our EFS partition since the phone is able to rebuild it itself but I doubt about my own understanding here.. Maybe I could use in ODIN the option "Phone EFS clear" ?? http://forum.xda-developers.com/showthread.php?t=2471421
Please, I would really appreciate some help here!!
EDIT : Here is the damn software with what I bricked my phone. Maybe the comments can help you or anyone willing to save my all new phone. That's Xmas ... lol
https://play.google.com/store/apps/details?id=nl.boris.efs
Click to expand...
Click to collapse
You should have not used a program that was not specifically reported to work on Note 3, even more so with a program that does not seem to have so great feedback (there are a number of other ways to backup your EFS, searching for those around would have helped).
1) what is your current Odin status?
2) try to go to Samsung recovery, wipe data and cache from there, then go to download mode and try to write again the URDLV version that previously worked.

xclub_101 said:
You should have not used a program that was not specifically reported to work on Note 3, even more so with a program that does not seem to have so great feedback (there are a number of other ways to backup your EFS, searching for those around would have helped).
1) what is your current Odin status?
2) try to go to Samsung recovery, wipe data and cache from there, then go to download mode and try to write again the URDLV version that previously worked.
Click to expand...
Click to collapse
Today I am sick. It made me probably sloppy on that one.. Yesterday I spent one day to root my phone without doing a mistake and without disturbing anyone on any forum. I handled it.
Concerning Odin, in Odin mode on the mobile I have everything good. I managed to reflash my Vega ROM from yesterday but I still get bootloops.
I have one line of code (still in Odin mode on my n9005 ) : RP SWREV S1, T1, R1, A1, P1
On my PC, Odin worked obviously fine. No error and the status is <ID:0/004> Added!!
Do I really have to flash a stock ROM ? I really fear to lose my root and reduce the possibilities of fixing my phone. Yesterday, since the tuto for URDLV didn't work, I packed a TAR with a mix of my original files and the modified files and it worked fine.
I try to wipe now... :'(
Thanks

I get bootloops during the setup of the "first launch". ....
"the system process doesn't respond. Do you want to quit ?"
PS: I installed the VEGA repacked with the original files missing to make a complete ROM.

Nemorensis32 said:
...
Concerning Odin, in Odin mode on the mobile I have everything good. I managed to reflash my Vega ROM from yesterday but I still get bootloops.
I have one line of code (still in Odin mode on my n9005 ) : RP SWREV S1, T1, R1, A1, P1
On my PC, Odin worked obviously fine. No error and the status is <ID:0/004> Added!!
Do I really have to flash a stock ROM ? I really fear to lose my root and reduce the possibilities of fixing my phone. Yesterday, since the tuto for URDLV didn't work, I packed a TAR with a mix of my original files and the modified files and it worked fine.
I try to wipe now... :'(
Thanks
Click to expand...
Click to collapse
It is still good great that the EFS program did not trigger knox! (but of course there still is the major question about what the program did).
I never said to write stock, I said the URDLV ROM, the one generated by Universal Root De La Vega and which worked OK for you previously.
The point was that wiping before Odin might fix some of the bootloops.
That being said the OLD original stock ROM, the same one that came inside your phone (and which you should have used as base for your original URDLV) should not create any knox problem. You will lose root but you should be able to gain it back by repeating the exact sequence from URDLV. And when stuff like this is happening wipe before Odin just to be certain.

xclub_101 said:
It is still good great that the EFS program did not trigger knox! (but of course there still is the major question about what the program did).
I never said to write stock, I said the URDLV ROM, the one generated by Universal Root De La Vega and which worked OK for you previously.
The point was that wiping before Odin might fix some of the bootloops.
That being said the OLD original stock ROM, the same one that came inside your phone (and which you should have used as base for your original URDLV) should not create any knox problem. You will lose root but you should be able to gain it back by repeating the exact sequence from URDLV. And when stuff like this is happening wipe before Odin just to be certain.
Click to expand...
Click to collapse
I CAN'T get it back since I have a constant bootloop. I can't copy the URDLV files on my internal SD . The phone reboots ! Anyway, my computer doesn"t detect my phone either. Never.
On the buggy software I used, you have two options . One for EFS and one for NVRAM. I press both of them with one reboot each. Maybe it is the NVRAM which is buggy ?
I hate that developper who put his warning at the END of the presentation of his software.... (my fault too... )

Nemorensis32 said:
I CAN'T get it back since I have a constant bootloop. I can't copy the URDLV files on my internal SD . The phone reboots ! Anyway, my computer doesn"t detect my phone either. Never.
On the buggy software I used, you have two options . One for EFS and one for NVRAM. I press both of them with one reboot each. Maybe it is the NVRAM which is buggy ?
I hate that developper who put his warning at the END of the presentation of his software.... (my fault too... )
Click to expand...
Click to collapse
Let me get a better idea of what is happening:
- you went to recovery and wiped data and cache
- you went to download mode and from Odin you wrote the URDLV-generated tar.md5
- you restarted and you got bootloops?

xclub_101 said:
Let me get a better idea of what is happening:
- you went to recovery and wiped data and cache
- you went to download mode and from Odin you wrote the URDLV-generated tar.md5
- you restarted and you got bootloops?
Click to expand...
Click to collapse
No, I have bootloops since I pressed the two options in "Efs by BORIS.X.1" app. First, the option "EFS backup" (I got a reboot but I thought it was normal), secondly, "NVRAM backup" (I got a second reboot). Since then, my phone keep rebooting. I reflashed with my former VEGA ROM, Then I did the wiped everything and flashed again. Always with Odin. I kept all that time to have bootloops and (I forgot to repeat it!) no connexion/no data.
Hope it's clear enough now..
Btw, I don't manage to use EFS pro. It can't find my phone (and my computer neither..)
What happened!! :/
(I have to go to a short meeting/dinner right now. I'll be right back) . I don't see any solution on internet yet.
Thank you so much for helping me.

ok. I'm back.
Any solution ?

ok. I'm back.
Any solution ?

Nemorensis32 said:
ok. I'm back.
Any solution ?
Click to expand...
Click to collapse
At this point I have no idea what that EFS program did
Also I wonder if you had Reactivation lock ON - but I assume you did not.
The only other that I can think of is to:
- wipe again everything in recovery
- write in Odin the original Samsung ROM that you had on the phone; ideally this should revert things to something close to your original state (but that is not 100% certain - the original ROM might not be "full wipe" and certain partitions might be left with some content).

Ok. Thanks. Il will wait for someone else. Or maybe open a new topic. Merry christmas.

[Q] DOWNLOAD mode N9005 - 4.4.2 - UDC START?

I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??

I have the same problem with a N9005 I guess it was Hong Kong version for the kanjis in the back, but is stuck in odin mode with the UDC START line

UDC Start info.
Ok gent's little more knowledge about "udc start" I am guessing that the problem became clear as you installed 4.4.2 KK.
So did I and came across UDC Start the second time I booted into download mode.
As I played around i became aware that the "UDC Start" mode locks the download loader to certain criteria. This would be 4.4.2 KK,
so anything under 4.4.2 will get a MASSIVE RED FAIL. That including the CWR/TWRP recoveries and ROOT files.
So just to specify, yes phone is now locked/bricked to 4.4.2 KK software only.
Therefore I would please like some help to get the udc start away!? If anyone can help.
If I shared some light to the darkness please say thanks.:good:

Try this out:
Worked for me on a Hong Kong 16GB N9005 which was stuck on the 'Samsung Galaxy Note 3' screen after getting a 'Invalid: ext4 image' or 'Repartioning failed' errors while installing 4.4.2 OFFICIAL (Single File ROM) via Odin.
Binary: Custom
Knox: 0x1
Method:​
In Odin mode
1. Flash the latest cf-autoroot (Kitkat support) [http://download.chainfire.eu/352/CF-...x-smn9005.zip]
2. Flash the Chenglu's latest CWM - 6.0.4.6 (the one that supports KitKat) http://forum.xda-developers.com/show....php?t=2454079
Download Sweet Rom and place it in ExtSDcard (http://forum.xda-developers.com/show....php?t=2487425)
I tried external sd-card with various format and could not install the ROM. After format my SD Card to FAT32, the ROM can be installed.
On Device
1. Boot in to Recovery mode by Volume up + Home + Power
2. Wipe Factory reset / Dalvik Cache
3. Format /System (under "mount and storage" menu) [IMPORTANT STEP]
4. Install Rom from SD Card
5. Say your prayer. You'll need it. (The installation could take sometimes. If the device screen shows Samsung boot animation, you're half way there)

How is that going to take away the udc start?

I have UDC Start in Odin/Download mode... It hasn't affected my flashing of custom ROMs nor Stock, everyone on KK has it.

Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.

FdeKlerk said:
Ok, but why if i try to install a previous version of TW rom 4.3 i get a massive fail?
But all the rest works?
Thanx in regards.
Click to expand...
Click to collapse
Because you are locked into the new Bootloader (NA6) and it's unable to downgrade

So I am guessing there is no way to downgrade the boot-loader without unlocking it?

FdeKlerk said:
So I am guessing there is no way to downgrade the boot-loader without unlocking it?
Click to expand...
Click to collapse
There's no way full stop. Samsung have blocked downgrades within the bootloader itself.

Wow now that's some sort of a problem.
My 4.4.2 works but i love xposed modules to make everything transparent and as of yet kitkat does not support that.
And now i a stuck on 4.4.2..
But thanx for the assist.:good:

Same Problem with E330s
ManuH8 said:
I'm installing the new firmware but i had an issue with odin...
I flashed again 4.4.2 but in download mode, the last line you can see " UDC START" in colour red... Is this normal? I think the phone works good, but i don't know why put on this...
Anyone have this new line??
Click to expand...
Click to collapse
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.

summan971 said:
Hi. I have a unrooted SHV-E330 (I9506 to some) I was running the unrooted firmware and updating with Kies up until yesterday when the update to came up. I ran it as with every other update however on self rebooting the phone now goes to ODIN MODE (in red) and UDC Start (in red) i'm a root virgin and was happy with the phone running as it was AnTU TU score 36118 with the Korean bloatware running in the background. From what I have picked up after 4.3 firmware update to 4.4.2 there is no going back. I tired to root with earlier versions of firmware but get fail every time. I Picked up a zip SKT-E330SKSUCNA7 wich goes as far as checking the MD5 file successfully in Odin 3 v3.09. everywhere I look on the web it states the com box should be yellow however mine is blue.
After MD5 successful I get leave CS. I click start I get 'Get PIT for mapping. There id no PIT partion followed by a red box and the'FAIL!' box with 'all threads completed Failed 1.
I have never rooted a phone and a buff mentioned that I will not regret it. I figure thart i'm doing something wrong as there was no PIT file with the firmware.
On first trying a firmware recovery in Kies because the phone is stuck In ODIN MODE it will not recognise the phone even though the USB drivers are installed.
If their is a person out there that could talk me through rooting trough the stuck ODIN MODE I would appreciate contact.
I gather that I have no choice but to try ODIN MODE on phone as that's where the phone is stuck. Removing battery etc has been tried to death.
Click to expand...
Click to collapse
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.

[COLOR=[/COLOR]
feralfire said:
your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 're-partition' box in odin while flashing. Though i don't really think it will help, because your single file rom most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
Ps- you are in the wrong forums.
Click to expand...
Click to collapse
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...

Thanks for caring XDA developers - i fixed it
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
Hey thanks for the response the same day I managed to fix the problem a hour ago after 24 hours of banging my head on a wall.
I uninstalled all software including Odin remembering that ODIN MODE was the only option. most of the Boot Operating system was in Korean.
I followed a you tube guide from another root and noticed that although ODIN MODE and UDC start are new (according to other forums) that the other information insinuated that the screen I was looking at was also the download mode.
I reinstalled Kies and rather than asking me for the emergency recovery code it reset and was asking for the Model and serial number. After which it stated it could not recover the device only reinstall the stock firmware. I selected OK. the phone came back to life and reinstalled all data from cloud.
now on 4.4.2 and still thinking about rooting
however I must warn anyone that comes across the unlocker website that states its mod allows for E330S root. that clockwork mod does not cater for E330S.

ultramag69 said:
[COLOR=[/COLOR]
do not tick re-partition without having a pit file, you will get a brick.
Feralfire, you just broke the first law of flashing with ODIN... If you don't know what to do then don't say anything...
Click to expand...
Click to collapse
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.

FeralFire said:
Au contraire, I have done a lot of research on pit file and played around a lot. Check out my threads.
If you tick re-partition without having a pit, it just gives you an error. Maybe in the olden days, it might have been an issue (I haven't always been a Samsung guy), but definitely not now.
Click to expand...
Click to collapse
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...

ultramag69 said:
If so, then make sure they know which version of ODIN to use as this is the fastest way to kill a phone I know...
Right from the very first this was a cardinal sin but then you didn't have a phone anymore or much sympathy either... But to tell a noob to do this was in effect saying "put your phone in front of a steamroller, it'll be ok after its gone over it a couple of times"...
Click to expand...
Click to collapse
He was using 3.09. Don't overcomplicate things.
But anyway, I apologize for making people put their phones in front of 20 ton vehicles.

re Pit File
FeralFire said:
Your phone does not have a pit file on it. Odin downloads the pit file from the phone to make sure that all the partitions are correctly flashed.
Try ticking the 'Re-partition' box in odin while flashing. Though I don't really think it will help, because your single file ROM most probably does not contain the pit.
Your best bet is to find somebody else with the same model as you, and get a pit from them.
PS- You are in the wrong forums.
Click to expand...
Click to collapse
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!

summan971 said:
I found this KS01LTE_KOR_SKT_32G.pit and ran it in Odin running download mode and it worked. It appears there are several Korean versions of the right ROM and unless the right rom is used flash in odin does not work.
I'm starting to sound like i know what i'm talking about!
Click to expand...
Click to collapse
The different ROMs must have different pits. That would explain why only some specific ones work.
Anyway, congratulations.

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