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] "Firmware upgrade encountered an issue ....."

Hi there ... yes I've done something wrong and would like to try to fix it without going to Vodafail to get them to berate me.
I was trying to install PhilZ Touch recovery but was having trouble with Odin (1.85, and 3.07 I was trying) and finally gave up and just wanted to make a normal boot but the dreaded firmware message has come up.
I've had a quick search & read and it seems that I need to flash (with Odin) a new stock ROM.
It's getting late here so I'm not going to try anything more without a lot of advice and reading.
So any suggestions please?
I'm in Australia with Vodafone, phone is about two or three months old. i9505.

Cam you get into download mode? Turn it off then press home, power and volume down at the same time, if you can download a stock firmware for your device this can be found at Sam mobile. Then flash it with Odin. Always use the latest version.
Sent from my GT-I9500 using Tapatalk 4 Beta

BillzillaAus said:
Hi there ... yes I've done something wrong and would like to try to fix it without going to Vodafail to get them to berate me.
I was trying to install PhilZ Touch recovery but was having trouble with Odin (1.85, and 3.07 I was trying) and finally gave up and just wanted to make a normal boot but the dreaded firmware message has come up.
I've had a quick search & read and it seems that I need to flash (with Odin) a new stock ROM.
It's getting late here so I'm not going to try anything more without a lot of advice and reading.
So any suggestions please?
I'm in Australia with Vodafone, phone is about two or three months old.
Click to expand...
Click to collapse
Hi,
Stock firmwares are HERE
Try ODIN 3.04 as well

Thanks guys, I'm downloading http://www.hotfile.com/dl/227186782/ebf4c32/I9505XXUBMEA_I9505XSABME4_XSA.zip.html now and will try it when it's finished.
And yes the phone will go into download mode okay.
I also had a think about it last night and I'm not against putting a different ROM into it, any suggestions?

Okay trying to flash that rom with Odin failed.
Where do I go from here please? Like I mentioned, I'm more than happy to try a custom rom.

Hmmmm just tried flashing CWM recovery ..... that failed as well.
Help!!

Know its probably a stupid question but did you root the phone before trying to install Phillz recovery?
If not, try CF-Autoroot, then try Phillz recovery. If you can't get these flashed you may have corrupted your partition table. Here's a link to the PIT file you need - http://forum.xda-developers.com/showthread.php?t=2265477 (Make sure you get the right one or you can say bye bye to your toy- I believe you should have an I9505)
Read this, then go and try again....
Cheers.... :good:

ultramag69 said:
Know its probably a stupid question but did you root the phone before trying to install Phillz recovery?
If not, try CF-Autoroot, then try Phillz recovery. If you can't get these flashed you may have corrupted your partition table. Here's a link to the PIT file you need - http://forum.xda-developers.com/showthread.php?t=2265477 (Make sure you get the right one or you can say bye bye to your toy- I believe you should have an I9505)
Read this, then go and try again....
Cheers.... :good:
Click to expand...
Click to collapse
Yep I flashed CF-Autoroot a couple of months ago without too many problems, I'll try it again.
Which version of Odin should be best to use?

Ah! Flashing the pit file thingy did it, THANKS!!!

BillzillaAus said:
Ah! Flashing the pit file thingy did it, THANKS!!!
Click to expand...
Click to collapse
No problem, just remember though that flashing the pit file is no small thing... If that stuffs up or you have a corrupt pit file you can actually hard brick your device... It really is the final step before giving it back to Samsung to fix...
Glad it all worked out and cheers....:good:

Yes I'll try to not need to do that again!

[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.

Rooting phone with emmc error and PIT partition error.

So my Note 4 (N910G) has been running like total arse for about a year now with really slow response time to screen presses, the mmc fail on boot problem and random reboots. Ive been using wake lock and that at least keeps the phone working but its SLOOOOOOW.
So I decided to root it and then try out some roms to see if I could improve its performance. Anyway when I tried to install CF-Auto-Root in Odin I got the 'There is no PIT partition" error. I then found (i think) a PIT file and tried to install that but couldn't get it to work.. odin seemed to freeze up and do nothing. I then tried to do a factory reset from the OS .. and everything seemed to work.. but then I rebooted, got a mmc error.. and then the next time I booted there was no factory reset, everything was as I left it.
Anyway... im wondering if im wasting my time trying to root/rom my phone while im getting constant mmc errors? I saw the hardware fix and im going to give that a try.. but yeah im at a loss as to what my next steps should be.
Any guidance would be great.

https://forum.xda-developers.com/note-4/help/100-fix-galaxy-note-4-emmc-error-random-t3859448
If you've seen the mmc_read failed error then a new ROM wouldn't make a difference other than stressing the emmc even more by installing it.

Big Elf said:
https://forum.xda-developers.com/note-4/help/100-fix-galaxy-note-4-emmc-error-random-t3859448
If you've seen the mmc_read failed error then a new ROM wouldn't make a difference other than stressing the emmc even more by installing it.
Click to expand...
Click to collapse
Bugger. I saw that hardware fix and im going to give it a shot. Assuming it works would it still be dangerous/pointless to change roms?

No, I'd assume that the 'fix' means the emmc is reliable enough to cope with increased disk activity. Only way to be sure is to try it though.
EDIT: After rereading your comments in your original post. You need to load both the PIT files AND the stock ROM into Odin before running. You can't install the PIT file on its own.

Yeah I loaded the stock rom and the pit file.. But Odin just seemed to hang

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