SGH-M919: No PIT Partition, Unable to boot to recovery. pls Help - Galaxy S 4 Q&A, Help & Troubleshooting

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?

Related

Odin Complete(Write) operation failed

I followed the instructions on (youtube DOT com SLASH watch?v=SpHZ2n9lTcs) this YouTube video to install CyanogenMod on my AT&T Galaxy S4. I flashed the CWM using Recovery Tools, then when it rebooted it wouldn't boot into recover (it would say "System software not authrized by AT&T") so I downloaded Odin and tried flashing it from there but I get the following messages:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone screen is the Download mode page with the message at the top
start[224,1440]
secure magiccode check fail : recovery
Could someone please help me complete the installation or at least revert back to stock? I can't use my phone at all now
leaf68 said:
I followed the instructions on (youtube DOT com SLASH watch?v=SpHZ2n9lTcs) this YouTube video to install CyanogenMod on my AT&T Galaxy S4. I flashed the CWM using Recovery Tools, then when it rebooted it wouldn't boot into recover (it would say "System software not authrized by AT&T") so I downloaded Odin and tried flashing it from there but I get the following messages:
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone screen is the Download mode page with the message at the top
start[224,1440]
secure magiccode check fail : recovery
Could someone please help me complete the installation or at least revert back to stock? I can't use my phone at all now
Click to expand...
Click to collapse
@leaf68 I'm guessing that u are on either MF3 or MK2,since u bricked trying to flash CWM recovery.Try flashing these via ODIN MF3.tar or u can follow my latest MK2.tar.Check post#2 for guide on how to.....GOODLUCK......:good::good:
ted77usa said:
@leaf68 I'm guessing that u are on either MF3 or MK2,since u bricked trying to flash CWM recovery.Try flashing these via ODIN MF3.tar or u can follow my latest MK2.tar.Check post#2 for guide on how to.....GOODLUCK......:good::good:
Click to expand...
Click to collapse
Thank you very much for your response. Right before you posted this, I plugged my phone into my laptop and despite doing this multiple dozen times, it actually booted out of nowhere. Thanks again and I'll hold on to the files in case I need them in the future
yes!
Finally got personal!
It was my USB cable that changed with the Moto X and now worked (S4 Cable sucks anyway!)
Who have some problem there are several possibilities! Do the following.
Test all kinds of Odin, but before connecting first add the file;
If you get caught try to install a recovery may be the "philz_touch_6.44.8-jflte.tar.md5" or "openrecovery-TWRP-2.7.1.0-jfltexx.tar";
If you do not give change the USB port of your PC;
If it persists, replace the USB cable;
That's what I did and it worked guys because of USB CABLE! kkkkkk
have the same problem bro is your phone ok now what did you do?
diogomitsuda said:
Finally got personal!
It was my USB cable that changed with the Moto X and now worked (S4 Cable sucks anyway!)
Who have some problem there are several possibilities! Do the following.
Test all kinds of Odin, but before connecting first add the file;
If you get caught try to install a recovery may be the "philz_touch_6.44.8-jflte.tar.md5" or "openrecovery-TWRP-2.7.1.0-jfltexx.tar";
If you do not give change the USB port of your PC;
If it persists, replace the USB cable;
That's what I did and it worked guys because of USB CABLE! kkkkkk
Click to expand...
Click to collapse
I can vouch. It's the cable and the port. Try switching ports between failed flashes. I guarantee you it will eventually work. It's really sensitive.

Noob messed up. Flashed wrong version and now won't flash correct version

I don't know if I made a minor mistake or a major mistake. I was trying to flash U Firmware and downloaded and tried to flash G935UUEU2APEH_CL8086184_QB9638174_REV02_user_low_ship_MULTI_CERT. I can't tell you for sure what it said because the post I was reading said if it fails, it's no big deal, try again a few times. After a few failed attempts, I realized there were tons of different versions.
I finally downloaded what I believe is the the correct one, G935VVRU4API3_CL8875708_QB11198937_REV02_user_low_ship_MULTI_CERT, but when I went to flash it, in red at the top it says
volume size is too big 1152000 < 1369600
Odin : invalid ext4 image
and in Odin, the end says
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there any fixing this or am I royally screwed? When I restart the phone, a blue screen comes up and says
Software Update Failed
Your device didn't update successfully. Use the Verizon Software Repair Assistant on a computer to repair your device and complete the update. (I don't have a Verizon Software Repair Assistant).
I'll be honest, at this point I just want a functioning phone! haha Thanks for your help!
re: messed up phone
bmccartney2004 said:
I don't know if I made a minor mistake or a major mistake. I was trying to flash U Firmware and downloaded and tried to flash G935UUEU2APEH_CL8086184_QB9638174_REV02_user_low_ship_MULTI_CERT. I can't tell you for sure what it said because the post I was reading said if it fails, it's no big deal, try again a few times. After a few failed attempts, I realized there were tons of different versions.
I finally downloaded what I believe is the the correct one, G935VVRU4API3_CL8875708_QB11198937_REV02_user_low_ship_MULTI_CERT, but when I went to flash it, in red at the top it says
volume size is too big 1152000 < 1369600
Odin : invalid ext4 image
and in Odin, the end says
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Ext4)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is there any fixing this or am I royally screwed? When I restart the phone, a blue screen comes up and says
Software Update Failed
Your device didn't update successfully. Use the Verizon Software Repair Assistant on a computer to repair your device and complete the update. (I don't have a Verizon Software Repair Assistant).
I'll be honest, at this point I just want a functioning phone! haha Thanks for your help!
Click to expand...
Click to collapse
You need to use Odin3 to flash the proper official samsung
firmware for your s7 or s7 edge phone model.
You can find and download the firmware from http://sammobile.com
After successfully flashing the phone using Odin3 your phone will be
just like new.
The mistake you made is a very small one, flashing the official firmware
takes less than 15 minutes.
Good luck, have a great day!
.
This happened to me on my galaxy tab s2, same error in Odin and same result. Good news is it is fixable. I have no idea why the error happened, I just tried a different firmware, and the second one worked.

Unable to flash anything on Samsung Galaxy S4 GT-I9515

Evening fellas!
I hope i can get some help over because i am freaking out!
Let me start with what i wanted to achieve. I wanted to go and use Stuff on my phone which wasnt usable due to the SafetyNet API, because i got a custom firmware and root Access. I tried to flash Magisk but it doesnt worked, neither did my SuperSU proberly.
My idea was to unroot and then simply flash the stock firmware via Odin on my phone. 1st couple of tries it didnt work. However, it also didnt affect my phone at all. So i then went into my recovery (TWRP) and did factory reset. Just to clean things up. I tried again to flash and yeah, he actually did it! Just with the minor exception that the flasing failed like 3% before its completion and now i got basiclly a white brick. I ve tried numerous times to flash that firmware again, get some other firmware running - I also tried to flash the Stock Rom completly (which also was able to start the flashing just before it failed in the middle).
I dont find any help on the internet, or at least not help that helps me in my specific situation. I honestly dont know what to do else... I do appreciate any help!
Please help me xda-users, you re my last hope!
Did you try using the original USB cable? Tried different USB ports?
audit13 said:
Did you try using the original USB cable? Tried different USB ports?
Click to expand...
Click to collapse
Yes, i just did. I ve used several USB Ports of my Computer (Haven't tried another computer yet, but that will come too). I also used two different cables. One Original and one third-party cable from amazon, which worked just fine for normal file copying and moving, on the S4 before its brick and the Samsung Grand Prime as well (as i use that in the mean time).
As from yesterday at some random points i was still able to get to flash something for just a second or so, the only messages i get from odin today are these:
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> FAIL! (DeviceInfo)
<OSM> All threads completed. (succeed 0 / failed 1)
I dont find any helpful information on that error message either, which is the worst part of it all.
Is Odin assigning a COM port to the phone?
audit13 said:
Is Odin assigning a COM port to the phone?
Click to expand...
Click to collapse
Yes, everything is detected. Odin is detecting the Samsung Grand Prime just as well as the Galaxy S4. I've also tried different version of Odin. v3.12.3 and v3.13.1. They both give me the same output.
During the initalization phase, Odin is trying to communicate with the phone and is not able to do so.
What about Odin 3.07 with Win7?
Thread moved to Help & Troubleshooting.
audit13 said:
During the initalization phase, Odin is trying to communicate with the phone and is not able to do so.
What about Odin 3.07 with Win7?
Click to expand...
Click to collapse
I ve been using Windows 7 all the time, but now i also tried it with Odin v3.07 and look there: It actually worked! I was able to flash the Stock Firmware, i downloaded days ago, on the phone.
But i still have some problems. As i had the stock firmware running everything seemed to work just fine. At first some google processes repeatedly stopped all the time, but i got that fixed after a factory reset. But i wasnt able to get any google Service running even though i was logged in successfully. It seemed like it was working, but i got fooled. So i tried to flash the whole stock rom and thats where the fun begins all over again.
With using Odin v3.07 i set the files for the Bootlader(BL), PDA(AP),Phone(CP) and CSC but it wont work. Here's the Odin log:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
vM44tze said:
I ve been using Windows 7 all the time, but now i also tried it with Odin v3.07 and look there: It actually worked! I was able to flash the Stock Firmware, i downloaded days ago, on the phone.
But i still have some problems. As i had the stock firmware running everything seemed to work just fine. At first some google processes repeatedly stopped all the time, but i got that fixed after a factory reset. But i wasnt able to get any google Service running even though i was logged in successfully. It seemed like it was working, but i got fooled. So i tried to flash the whole stock rom and thats where the fun begins all over again.
With using Odin v3.07 i set the files for the Bootlader(BL), PDA(AP),Phone(CP) and CSC but it wont work. Here's the Odin log:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Set PIT file..
<ID:0/007> DO NOT TURN OFF TARGET!!
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Okay, i don't know whats wrong now - but now i cant even flash back the stock firmware that worked before with odin v3.07. Odin now says:
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
EDIT: Its not even being detected anymore.
There is no need to split the tar.md5 into 4 parts. In Odin 3.07, you can flash it as a single file in PDA.
You're flashing the latest stock ROM? Is it possible the USB port on the phone is damaged?

Problem flashing stock rom - All threads completed. (succeed 0 / failed 1)

I have an unlocked Samsung S8 (SM-G950U) and I'm unable to get Odin to flash a stock rom to it. I'm able to boot it and the current software is:
AP: G950USQS7DTB3
CP: G950USQU7DTF4
CSC G950UOYN7DTB3
When I boot into download mode, it reads: CARRIER: TMB
At this point I'm thinking this isn't an issue of Odin not being able to communicate with the phone. Odin sees it and lists the COM port as expected. I've tried multiple USB cables, USB ports (2.0), uninstalling/reinstalling Samsung drivers, tried from another PC, etc.
Here's a sample log:
<ID:0/005> Odin engine v(ID:3.1401)..
<ID:0/005> File analysis..
<ID:0/005> Total Binary size: 4685 M
<ID:0/005> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
I've tried multiple firmware versions from updato and sammobile including TMB and others but they've all failed like this. I'm not sure what else to do at this point to get it back to current firmware level.
Any input or assistance you may be able to offer would be greatly appreciated.
Hi, i'm having the same issue with a Samsung S8 (SM-G950U). Did you find a solution?
I'm Having same issue with SM-G9500

SM-T510 recovery:Error validating footer.

My tablet is currently stuck in download mode where every time i try to cancel it, it just reboots back into download mode with the error "recovery:Error validating footer. (6)", "VBMETA T510XXU5CVG2, 54266617A" This occurred while i was messing around trying to root the tablet after i had attempted to flash TWRP to the device (ver: https://twrp.me/samsung/samsunggalaxytaba101wifi2016.html). I believe this is 2016 tab firmware and my tab is a 2019 which may be the reason its bricked, however i have attempted to flash 2 versions of what i believe to be the correct firmware, one from frija and one from samfw, with both failing in odin hanging on SetupConnection. At one point i was able to restart the tablet after these flashes with the error "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software." After which i was able to flash the samfw firmware in a flash that only took 3 seconds to complete without the usual file logs.
logs:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1401)..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
This allowed me to clear the error but it is back to being stuck on downloading loop.
The bootloader was unlocked prior to this issue and i believe i was on a fresh unmodified boot.img prior to TWRP flash. I have not been able to find any information that has worked in helping me fix this issue.
Product Link: https://www.amazon.com/gp/product/B07Q3T1YJS/
Frija Version: T510XXU5CVG2/T510OXM5CVG2/T510XXU5CVG2
Frija Filename: SM-T510_1_20220725192041_c4u4t0y6d6_fac.zip.enc4
samfw file: https://samfw.com/firmware/SM-T510/XAR/T510XXU5CVG2
I would appreciate any help or advice anyone can give thanks!

Categories

Resources