Database Users

Accidentally deleted my System folder SGH-M919

Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.

titaniums4 said:
Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
Click to expand...
Click to collapse
I managed to fix this! WOW was this such a headache!
after a long time researching, I found out the 4.4.2 update has some sort of updated bootloader that will not let you install older firmware. So I downloaded the 4.4.2 stock rom from www sammobile com
After you download that, i ran it with odin 1.09 and it installed.
My phone went into some weird loop where the samsung logo would come out for 1 second then my phone would vibrate every 2 seconds and not turn on... great another wall...
After more research i found out it could have been a power button issue, luckily it wasnt this, someone had mentioned that if you go into download mode and hold down the power button until your phone reboots you can get out of this "glitch". So this got me out of the glitch and my s4 started up normally!
Right now I am back to stock, I hope this helps out anyone who encounters something similar!

titaniums4 said:
Hello, I accidentally deleted my systems folder. I was trying to overwrite one file but apparently it deleted my entire system folder, now I cannot use recovery. If I try to go into recovery mode i get "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried downloading Kies and updating it through that but I then get the error "the device's version cannot be updated." I have updated KIES to the newest firmware and still get the error.
I have tried adb pushing but my device is unrecognized and does not fully connect to my computer (Kies will just be stuck at "Connecting...")
I have tried installing a stock rom back with odin (ran as administrator), but odin gives me the error:
Initialzation..
Get PIT for mapping..
Firmware update start..
sbl2.mbn
NAND Write Start!!
sbl3.mbn
rpm.mbn
aboot.mbn
FAIL! (Auth)
All threads completed. (succeed 0 / failed 1)
So it seems I have tried pretty much everything so far with no avail, may someone please help me? I am really stressed out and confused at all these errors.
Click to expand...
Click to collapse
I think u should download new firmware from sammobile (because sometimes some firmware corrupted) and try different pc for reflash stock...
Sent from my GT-I9500 using XDA Premium 4 mobile app

fleming.patel said:
I think u should download new firmware from sammobile (because sometimes some firmware corrupted) and try different pc for reflash stock...
Sent from my GT-I9500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thanks for the reply, however i already fixed this!

titaniums4 said:
I managed to fix this! WOW was this such a headache!
after a long time researching, I found out the 4.4.2 update has some sort of updated bootloader that will not let you install older firmware. So I downloaded the 4.4.2 stock rom from www sammobile com
After you download that, i ran it with odin 1.09 and it installed.
My phone went into some weird loop where the samsung logo would come out for 1 second then my phone would vibrate every 2 seconds and not turn on... great another wall...
After more research i found out it could have been a power button issue, luckily it wasn't this, someone had mentioned that if you go into download mode and hold down the power button until your phone reboots you can get out of this "glitch". So this got me out of the glitch and my s4 started up normally!
Right now I am back to stock, I hope this helps out anyone who encounters something similar!
Click to expand...
Click to collapse
Hey I am also in a similar difficulty. > http://forum.xda-developers.com/galaxy-s4/help/help-firmware-upgrade-encountered-issue-t2821045
Basically read this above, and tell me what you think I should do. One thing I forgot to add is that when I try to flash a Official Firmware via ODIN, my S4 doesn't really do anything then ODIN would say FAILED, and it would have no affect on my S4 because it just stays on the firmware upgrade encountered an issue part.

I337UCUFNC1 for Odin?

Hello guys... I was given a phone that I can keep and use if I fix it, but this phone is stuck on the open padlock/custom logo just stays there (if I try to go to recovery it says AT&T found unauthorized software). I fixed that by flashing stock NC1 Recovery but that only eliminated the unauthorized software message. I have read every thread and tried everything... Even flashed NC1 Modem and Kernel also since I found them... Only thing I have yet to try is flash a full I337UCUFNC1 via Odin but cant find it (At least not free). It seems this phone will only take NC1 stuff. Any help on getting the full I337UCUFNC1 Rom for Odin will be appreciated. I have the zip version but that does not work form DL mode...
More info:
Galaxy S4 i337
Binary: Official
System Status: Custom
Knox void: 0x1
CSB-Config-LSB: 0x30
Write protection: Enabled
eMMC Burst Mode: Enabled

You can Odin flash NB1. That will work even on NC1.
More info http://forum.xda-developers.com/showthread.php?t=2616221

Phone disconnects and reconnects by itself at about 98% of the process. Tried on 2 diff pc's. Going crazy... LOL.

Apexseal said:
Phone disconnects and reconnects by itself at about 98% of the process. Tried on 2 diff pc's. Going crazy... LOL.
Click to expand...
Click to collapse
Try a different cable and try different usb ports. Odin can be finicky
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Try a different cable and try different usb ports. Odin can be finicky
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Two brand new original cables, brand new usb/charging connector (Tried connector in another i337 and works fine), all usb ports tried on both pc's. It starts flashing then after a while I hear the usb disconnect and reconnect sound and Fail. I can flash nc1 modem, kernel and recovery all day without problems that gets me out of the Kies screen but no recovery either It gets stuck at the "Custom" logo with the "Recovery booting" on top left. if I flash a custom recovery i get the AT&T unauthorized software message. I'm writing this thread because I read and read and read and can't find a solution. Tried Odin 1.85, 3.07 and 3.09 all with same results. I was thinking maybe if I flash a full NC1 rom for Odin I can get it to work since all NC1 stuff flashes ok.

Apexseal said:
Two brand new original cables, brand new usb/charging connector (Tried connector in another i337 and works fine), all usb ports tried on both pc's. It starts flashing then after a while I hear the usb disconnect and reconnect sound and Fail. I can flash nc1 modem, kernel and recovery all day without problems that gets me out of the Kies screen but no recovery either It gets stuck at the "Custom" logo with the "Recovery booting" on top left. if I flash a custom recovery i get the AT&T unauthorized software message. I'm writing this thread because I read and read and read and can't find a solution. Tried Odin 1.85, 3.07 and 3.09 all with same results. I was thinking maybe if I flash a full NC1 rom for Odin I can get it to work since all NC1 stuff flashes ok.
Click to expand...
Click to collapse
There is no nc1 tar file. Nb1 should work. Try downloading it again
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
There is no nc1 tar file. Nb1 should work. Try downloading it again
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Downloaded from 3 diff places...

The only way I can get the progress bar to reach at least 98% is if I discharge the phone by briefly connecting the battery backwards (1-2 seconds). I have tried the NB1 file from different places all with the same result. Is there any way to convert the NC1 flash for TWRP recovery to .tar?

Apexseal said:
The only way I can get the progress bar to reach at least 98% is if I discharge the phone by briefly connecting the battery backwards (1-2 seconds). I have tried the NB1 file from different places all with the same result. Is there any way to convert the NC1 flash for TWRP recovery to .tar?
Click to expand...
Click to collapse
I think you have a hardware issue, bad emmc. You're doing everything right
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
I think you have a hardware issue, bad emmc. You're doing everything right
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Frustrating... Is there an unbrick sd card image for i337??? I'm willing to try anything now... I just dont care anymore... LOL
<OSM> Leave CS..
<ID:0/046> Odin v.3 engine (ID:46)..
<ID:0/046> File analysis..
<ID:0/046> SetupConnection..
<ID:0/046> Initialzation..
<ID:0/046> Set PIT file..
<ID:0/046> DO NOT TURN OFF TARGET!!
<ID:0/046> Get PIT for mapping..
<ID:0/046> Firmware update start..
<ID:0/046> SingleDownload.
<ID:0/046> sbl1.mbn
<ID:0/046> NAND Write Start!!
<ID:0/046> sbl2.mbn
<ID:0/046> sbl3.mbn
<ID:0/046> rpm.mbn
<ID:0/046> aboot.mbn
<ID:0/046> tz.mbn
<ID:0/046> boot.img
<ID:0/046> recovery.img
<ID:0/046> persdata.img.ext4
<ID:0/046> system.img.ext4
<ID:0/046> __XmitData_Write
<ID:0/046> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/046> Removed!!
<ID:0/046> Added!!

Ok... I was able to do a full flash "Pass" in Odin... BUT still stuck on Custom Logo. I Used JFLTE_USA_ATT_16G.pit and AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_C ERT.tar.md5. Recovery also not working.

179
Seems I can flash MK2 all day long but nothing... Stuck at Custom logo and no recovery... If emmc is bad would it do a full flash at all? Did 2 full flashes with MK2 but everything else that I try to flash fails...

MK2 still does not make it boot but... Any ideas why I can flash MK2 ROM and not NB1 ROM???

I extracted system.img.ext4 from NB1 rom then converted to .tar using cygwin, all the bars loaded in odin but right at the point where it is supposed to reboot it failed. Should I try flashing with z3x?

[Q] G900i DVU1ANE2 bootloader required

Hi all,
I've searched for ages and couldn't find the DVU1ANE2 bootloader for my G900i. I have the firmware that I've downloaded from here:
http://www.sammobile.com/firmwares/download/30740/G900IDVU1ANE2_G900ITNZ1ANF1_TNZ.zip/
I know the bootloader is a tar.md5 file that contains the following files:
aboot.mbn
rpm.mbn
sbl1.mbn
sdi.mbn
tz.mbn
I've tried building my own .md5 file but it didn't work and I don't want to risk bricking my phone either. All the bootloaders I've found are for different firmware versions. If I supply the files, could someone build it for me?

anyone?

I'm almost certain you can flash that via odin without the bootloader because it comes in the package. But if you really want to be sure
http://forum.xda-developers.com/showpost.php?p=52210611

Latest Firmware for Galaxy Note 4 (N910TUVS2EQB1 AND N910T3) New N910TUVU2EQC1

This is the latest firmware for Tmobile Galaxy Note 4. Flash it at your own risk
I am not responsible if your phone blowup or sing the national anthem.
Samsung Galaxy USB Driver
New N910TUVU2EQC1
MDSUM: f86917e3e1763e9fb59bba6ca642fb22
How to root this:
1. Odin TWRP "uncheck auto reboot in odin" pull battery out put back in.
2. Boot to TWRP by holding Volume up Power and Home key together.
3. Flash SuperSu or flash this by PVSGH rooted rom
Enjoy
"Install Xposed Framework"
Install this first as apk XposedInstaller_3.1.1.apk
Go this this thread and flash xposed framework
I install this Qb1 stock RomControl. you guys can try it
For SM-N910T
MDSUM: 0b38870b792e37de28d1c6de721f5543
Odin 3.1.1
TWRP 3.0.2.0
Use this guide for root HERE
MDSUM: 29358c76fd6de55c086eb67bb1bff418
New firmware for SM-N910T3 (N910T3UVS3EQB1) Download HERE

Thanks for sharing, is the bootloader locked? are we able to downgrade? Thanks1

The-Accountant said:
Thanks for sharing, is the bootloader locked? are we able to downgrade? Thanks1
Click to expand...
Click to collapse
I have N910t and its not lock. I don't know about t3. You can use the guide posted by Deexii HERE just find the latest supersu if you will. Its has a good battery life. Always full wipe after and before odin. Good luck

boot loader and modem parted out
I've parted out the bootloader (BL) and modem (CP) for this firmware for those who don't wanna update their system: https://www.androidfilehost.com/?w=files&flid=158710
I've not flashed these yet myself, but did the same thing for EPK2 and had no issues flashing them. I'll probably get to updating my 910t this weekend and comment here if I have any issues.

Screenshots
I know I'm kinda late but I thought I would throw up some screenshots of the description of the update for anyone interested.

I have t3 and I can i use the BL and CP from T build rather than the T3. thanks

I have a n910t and update it for odin but on startup it stays on the T-mobile screen. any ideas
**Forget it and start 10 minutes the first start

razholio said:
I've parted out the bootloader (BL) and modem (CP) for this firmware for those who don't wanna update their system: https://www.androidfilehost.com/?w=files&flid=158710
I've not flashed these yet myself, but did the same thing for EPK2 and had no issues flashing them. I'll probably get to updating my 910t this weekend and comment here if I have any issues.
Click to expand...
Click to collapse
Just tried the modem alone not HLOS and not the bl stuff and it seems to work okay w/cm14. LTE works and a call went through anyway. Thx for doing this I hate having to download 2 gigs just to get like 100K of files.. I'll probably update the bl and such soon..
(updated via heimdall not odin fwiw)

razholio said:
I've parted out the bootloader (BL) and modem (CP) for this firmware for those who don't wanna update their system: https://www.androidfilehost.com/?w=files&flid=158710
I've not flashed these yet myself, but did the same thing for EPK2 and had no issues flashing them. I'll probably get to updating my 910t this weekend and comment here if I have any issues.
Click to expand...
Click to collapse
I've since flashed bq1 bl&cp and everything is working fine, though I'm on emotion 14.1 which hsbadr keeps updated with the latest proprietary blobs.

razholio said:
I've since flashed bq1 bl&cp and everything is working fine, though I'm on emotion 14.1 which hsbadr keeps updated with the latest proprietary blobs.
Click to expand...
Click to collapse
Cool. I'll give it a try in the next day or two and report back.
Update: Got impatient.. Tried the rest:
$ sudo heimdall flash --ABOOT aboot.mbn --APNHLOS NON-HLOS.bin --RPM rpm.mbn --SBL1 sbl1.mbn --DBI sdi.mbn --TZ tz.mbn
....
Uploading ABOOT
100%
ABOOT upload successful
Uploading APNHLOS
100%
APNHLOS upload successful
Uploading RPM
100%
RPM upload successful
Uploading SBL1
100%
SBL1 upload successful
Uploading DBI
100%
DBI upload successful
Uploading TZ
100%
TZ upload successful
Ending session...
It auto-rebooted. SEEMS to be working, but it's been about 30 seconds of testing
BTW, for anyone reading this who wants to also flash to modem, just add --MODEM modem.bin to the list of files above.
I see Baseband version N910TUVS2EQB1 listed in About Phone so that's good too.
(also-- I notice that it unfortunately didn't fix the timezone thing-- I still have to manually set it to keep it from jumping back to GMT)
Also, quick question-- I notice that NON-HLOS seems to always be grouped with modem.bin-- although I flash the modem as a standalone by itself (and used an older one for months alone) and it never had an issue.. is there a reason those two are treated as a group? I think (but am not 100%) that the NON-HLOS stuff contains the key stuff in /vendor. It's been a while tho since I did it so maybe it's muddled in my brain
Edit: Also, for the record, I'm using the Heimdall from here: link... No wait, actually that's gone. I pushed my working Heimdall source to here. It may be fixed better upstream but this works on Note 4 for me.

Thanks for the upload. Much faster than Sammobile's download.

Thank you for posting the ROM, I appreciate it.

Anybody has the md5sum for the sammobile firmware?

rajil.s said:
Anybody has the md5sum for the sammobile firmware?
Click to expand...
Click to collapse
Look again @ the first page

Installing this gives me 2 phone shortcuts and 2 broken Knox container apps? What is this

fattire said:
Also, quick question-- I notice that NON-HLOS seems to always be grouped with modem.bin-- although I flash the modem as a standalone by itself (and used an older one for months alone) and it never had an issue.. is there a reason those two are treated as a group? I think (but am not 100%) that the NON-HLOS stuff contains the key stuff in /vendor. It's been a while tho since I did it so maybe it's muddled in my brain
Edit: Also, for the record, I'm using the Heimdall from here: [email protected]:SaburoJiro/Heimdall.git... No wait, actually that's gone. I pushed my working Heimdall source to here. It may be fixed better upstream but this works on Note 4 for me.
Click to expand...
Click to collapse
Wish I had something intelligent to say on NON-HLOS, but I suspec the components of CP and BL are grouped together because of possible interdependencies, not that they necessarily have to break when out of sync, but the possibility exists. I've worked on build systems, and that's how I would define build artifact units.
Thanks for the heimdal links. I'd prefer not to ever have to fire up my aging winxp VM, but in the past, my heimdal attempts have always failed to identify my samsung products. I'll give this one a try.

Uh is anyone else's phone shortcut missing from the lockscreen?

I can't get this to flash, I have an N910T. Odin does recognize my phone, it shows the blue indicator. I'm using the AP box in Odin. The blue bar moves a bit, then stops cold. I checked the MD5, it matches what OP posted.
Samsung USB driver v1.5.45.0 (downloaded from Samsung's website)
Odin v3.11
Odin log:
<ID:0/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've also tried different cables, different USB ports, no go. I bought this phone brand new in factory-sealed box from a reputable seller on Amazon. I'm pretty sure it's not a fake/clone.
Please help, I don't want to be stuck with a brick that I've only had for less than 24 hrs!

AnonVendetta said:
I can't get this to flash, I have an N910T. Odin does recognize my phone, it shows the blue indicator. I'm using the AP box in Odin. The blue bar moves a bit, then stops cold. I checked the MD5, it matches what OP posted.
Samsung USB driver v1.5.45.0 (downloaded from Samsung's website)
Odin v3.11
Odin log:
<ID:0/005> Odin engine v(ID:3.1101)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl1.mbn
<ID:0/005> rpm.mbn
<ID:0/005> tz.mbn
<ID:0/005> sdi.mbn
<ID:0/005> NON-HLOS.bin
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've also tried different cables, different USB ports, no go. I bought this phone brand new in factory-sealed box from a reputable seller on Amazon. I'm pretty sure it's not a fake/clone.
Please help, I don't want to be stuck with a brick that I've only had for less than 24 hrs!
Click to expand...
Click to collapse
Download this and unzip use Odin N910TUVS2EQB1_N910TTMB2EQB1_TMB-v6.0.1.zip

@gmenik6: Thanks, but I got the issue fixed without your zip. I got my file from SamMobile, the only source I really trust. It had the same MD5 as what OP posted.
I had to use a cable from my LG v10, it looks like all my other cables are shot. I'm just surprised that the cable that came with this new phone couldnt cut it, but it charges fine. The ROM flashed and booted fine. But now I'm running LineageOS.
Thanks again!

SGH-M919: No PIT Partition, Unable to boot to recovery. pls Help

Hello All,
My Device is S4 SGH M919(T-Mobile USA), Not Rooted and have been running on Lineage OS 17.1 + TWRP recovery for several months until recently when the phone started to randomly shut off mic or reboot or crash often. nandroid backup used to be my savior. In an attempt to resolve the issue, I tried to reformat the phone, install different Lineage OS versions 17.1 and 18.1 which didn't improve my situation. I then switched to Lineage recovery(which I now regret was a bad move!) which not only improvised my situation but I lost ability to perform nandroid backups since then. I have been trying to revert to TWRP recovery but am facing the several issues which are listed below. My phone is very unstable now; it boots sometimes, crashes often and most times it gets stuck trying to enter recovery. i am able to get into download mode.
Issues:
Missing/Corrupted PIT Partition
Unable to boot to Recovery
Frequent crash
Troubleshooting Attempts Performed:
Flash PIT partition file using ODIN
<ID:0/003> Added!!​<ID:0/003> Odin engine v(ID:3.1401).​<ID:0/003> File analysis..​<ID:0/003> Total Binary size: 0 M​<ID:0/003> SetupConnection..​<ID:0/003> Initialzation..​<ID:0/003> Set PIT file..​<ID:0/003> DO NOT TURN OFF TARGET!!​<ID:0/003>​<ID:0/003> Re-Partition operation failed.​<OSM> All threads completed. (succeed 0 / failed 1)​
Flash stock android via ODIN with/without PIT partition file
<ID:0/003> Odin engine v(ID:3.1401)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 2616 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Flash TWRP recovery using ODIN
<ID:0/003> Added!!​<ID:0/003> Odin engine v(ID:3.1401)..​<ID:0/003> File analysis..​<ID:0/003> Total Binary size: 8 M​<ID:0/003> SetupConnection..​<ID:0/003> Initialzation..​<ID:0/003> Get PIT for mapping..​<ID:0/003>​<ID:0/003> There is no PIT partition.​<OSM> All threads completed. (succeed 0 / failed 1)​
Flash TWRP recovery + PIT file using ODIN
<ID:0/003> Added!!​<ID:0/003> Odin engine v(ID:3.1303)..​<ID:0/003> File analysis..​<ID:0/003> Total Binary size: 8 M​<ID:0/003> SetupConnection..​<ID:0/003> Initialzation..​<ID:0/003> Set PIT file..​<ID:0/003> DO NOT TURN OFF TARGET!!​<ID:0/003>​<ID:0/003> Re-Partition operation failed.​<OSM> All threads completed. (succeed 0 / failed 1)​
Checking PIT Partition using Heimdall
heimdall print-pit
Heimdall v1.4.2
Copyright (c) 2010-2017 Benjamin Dobell, Glass Echidna
Glass Echidna
This software is provided free of charge. Copying and redistribution is
encouraged.
if you appreciate this software and you would like to support future
development please consider donating:
Donate | Glass Echidna
initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Initialising protocol...
Protocol initialisation successful.
Beginning session...
Some devices may take up to 2 minutes to respond.
Please be patient!
Session begun.
Downloading device's PIT file...
ERROR: Failed to receive PIT file size!
ERROR: Failed to download PIT file!
Ending session...
Rebooting device...
Releasing device interface...
Things already verified
Connecting to PC USB Port with original quality USB cable; Tried changing USB cable and the port
Installed required samsung USB drivers
tried with multiple ODIN versions which all used to work in the past
How to recover from here?
May be I am not using the correct PIT file? I tried and couldn't find many so far.
Assuming there is no physical damage to the board inside, what additional steps I could try to get back to recovery mode? I look forward for your expert suggestion/next steps here.
Thank You!

Tried taking this to a Samsung service center but as expected they denied looking into this citing the phone is too old, is no longer being supported and better buy a new phone.
I am still wondering if I can revive this phone so that I can use this to continue experimenting with custom ROM.. Any options still worth trying to revive this phone?