Develop Bugs

GNex Bricked - Tried Fastboot/ODIN/OMAP

I am pretty new to flashing and rooting android phones. I have a GNex 4.1.1 JB Stock ROM. It was stuck in a boot loop somehow and I wasn't able to fix it by factory reset. Someone told me to unlock and root the phone to install a new stock ROM.
I unlocked using the Wuz toolkit. But rooting wasnt possible because I couldnt push files through ADB. Then I tried doing an ODIN flash using this method (http://forum.xda-developers.com/showthread.php?t=1827685). But I got stuck at NAND Write Start.
Now I have a Phone <-> Yellow Triangle with Exclamation <-> Computer. Which I believe is download mode for Samsung.
Then I tried an OMAP Flash using this method (http://forum.gsmhosting.com/vbb/archive/t-1465412.html). I was successful installing the OMAP drivers and running the bat file. However I am still have the phone/yellow/triangle/Computer logo on my screen.
I tried to do an ODIN flash again but still stuck at NAND Write Start.
I already tried to do this:
1.) Repartiion using the PIT file [ODIN]
2.) Then OMAP flash
3.) Then Flash PDA file using ODIN.
I also tried it by swapping steps 1 & 2 but no progress.Can someone tell me the exact sequence of steps or any advice what to do now?

First of all, let me list your mistakes before I help you out:
Mistake #1: You used a toolkit. By doing so, you skipped over the entire learning part of unlocking and flashing your device, so you have no idea what went wrong or what you did.
Mistake #2: You used Odin when you didn't have to. You can mess up your device with Odin, while it is next to impossible to do so using fastboot. We have a Nexus device, i.e. a device with an unlockable bootloader and the ability to use fastboot. In my opinion, Odin should only be used as a last resort.
Mistake #3: You did not read enough before you decided to fix your bootloop. There are a bunch of stickies in the General and Q&A sections. Did you read any of them?
Now, on to fixing your issue.
Go to the Dev section and find the IMM76D Odin file in a thread started by Chainfire.
Follow the instructions in that thread to flash the complete package. Odin should be able to flash your device even though you are on the screen you currently see. Do not use a JB Odin package, use an ICS package.
Sent from my Galaxy Nexus using Tapatalk 2

I read a few articles and i know it wasnt enough. I posted a thread on android central and a senior wrote down some steps and i followed that. But going for odin and omap was totally my experiment.
I links to the imm76d image do not work any more. File not found error. There were no other sources i could find. Do you have another link to the file?
Sent from my cm_tenderloin using Tapatalk 2

shravanm18 said:
[snip]
I links to the imm76d image do not work any more. File not found error. There were no other sources i could find. Do you have another link to the file?
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
I can't remember if I have them on my PC (I'm not near it at the moment) -- if i do, i will upload them tomorrow. But in any case, you should be able to find links somewhere via a Google search, no?
Sent from my Galaxy Nexus using Tapatalk 2

Worse comes to worse I have the Odin files too if you guys need them. I've used so many times to save my ass
Sent from my Galaxy Nexus using XDA Premium HD app

efrant said:
I can't remember if I have them on my PC (I'm not near it at the moment) -- if i do, i will upload them tomorrow. But in any case, you should be able to find links somewhere via a Google search, no?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I have my stock rooted files in a twrp backup. I'm unclear how that works they Odin but I'll pm you the dropbox link.
EDIT guess it would be if great importance to know if you are Sprint or not..
And i meant to quote the guy needing them. Oops

JediNinjafication said:
I have my stock rooted files in a twrp backup. I'm unclear how that works they Odin but I'll pm you the dropbox link.
EDIT guess it would be if great importance to know if you are Sprint or not..
And i meant to quote the guy needing them. Oops
Click to expand...
Click to collapse
I just looked at the thread I was referring to earlier, and someone already had posted another link to the files. The OP did not read the entire thread.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
I just looked at the thread I was referring to earlier, and someone already had posted another link to the files. The OP did not read the entire thread.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Isn't that what got him into this in first place?

JediNinjafication said:
Isn't that what got him into this in first place?
Click to expand...
Click to collapse
He cannot load a recovery if he has no fastboot access. His only option now is Odin.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
He cannot load a recovery if he has no fastboot access. His only option now is Odin.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
at least Odin is easy enough

I downloaded the image and tried an odin flash but seems to be stuck at nand write start. I also see that this process does not have a pit to repartition. I had previously tried to re partition it using the pit file given in the jb stock rom odin image. Can i use the same one here?
Sent from my cm_tenderloin using Tapatalk 2

I downloaded the image and tried an odin flash but seems to be stuck at nand write start. I also see that this process does not have a pit to repartition. I had previously tried to re partition it using the pit file given in the jb stock rom odin image. Can i use the same one here?

shravanm18 said:
I downloaded the image and tried an odin flash but seems to be stuck at nand write start. I also see that this process does not have a pit to repartition. I had previously tried to re partition it using the pit file given in the jb stock rom odin image. Can i use the same one here?
Sent from my cm_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
You shouldn't need the .pit file. That's what probably messed things up in the first place.
If Odin is not working, I guess you can try Omap flash and then Odin. Note that if you try omap flash, and then Odin still doesn't work, I don't think you have any other option besides sending it in for repair.
Sent from my Galaxy Nexus using Tapatalk 2

I tried the OMAP Flash. It executes perfectly in the command window but my phone still shows the "connect phone to PC" picture with yellow excalmation. After that I tried ODIN flash the IMM76D tar file but I am still stuck at NAND Write flash. What I want to know is that what are the reason for getting stuck at NAND write flash and what should have happened to my phone after OMAP Flash was complete?
Furthermore I was also thinking if using a USB jig would help me get back into fastboot.

shravanm18 said:
I tried the OMAP Flash. It executes perfectly in the command window but my phone still shows the "connect phone to PC" picture with yellow excalmation. After that I tried ODIN flash the IMM76D tar file but I am still stuck at NAND Write flash. What I want to know is that what are the reason for getting stuck at NAND write flash and what should have happened to my phone after OMAP Flash was complete?
Furthermore I was also thinking if using a USB jig would help me get back into fastboot.
Click to expand...
Click to collapse
After OMAP Flash, you should still see the "connect phone to PC" picture with yellow exclamation, but now Odin should have worked. Not sure why it gets stuck on NAND write flash. Maybe try un-checking the F. Reset Time option. Someone about a week ago said that it worked for him.

Need PIT file for Galaxy S3 repartition

I've run into quite the problem with my AT&T Galaxy S3. It seems my file system has structure has changed and my internal sd card has been wiped. If I try to install a new ROM via CWM, I get the file choices, 0, legacy & obb...none of which have my rom in it.
I have tried to flash a new ROM via ODIN but it always gets stuck at the aboot.xxx portion of the flashing process (attempting to flash the stock room...just using pda in ODIN). I searched other forums and they suggested finding a firmware with PIT file so that I can repartition the S3.
All the firmwares I have downloaded contain a single file that goes in the PDA part of ODIN. Does anyone have any links to firmware zips that contain the PIT file? My phone doesn't boot past the Samsung bootscreen.
Any help is appreciated. Thank you.

Sir, I understand your need but this type of thread is not for the Development Section...moved to the Q&A.
Thank You.

Here this is what your looking for
http://forum.xda-developers.com/showthread.php?p=30547929
Its at the bottom of the post
Sent from my SGH-I747M using xda premium

thatsupnow said:
Here this is what your looking for
http://forum.xda-developers.com/showthread.php?p=30547929
Its at the bottom of the post
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
You are a life saver good sir! Thank you! It worked perfectly

?
chizzwhizz said:
You are a life saver good sir! Thank you! It worked perfectly
Click to expand...
Click to collapse
How exactly did you fix it? I am having a strange issue, where the phone will not boot and in recovery everything fails to mount ex: "e: cannot mount \cache" and so on. I've flashed a few different stock restores with no avail, and I think that the partitions are jacked.

Corrupt SD
amawatts88 said:
How exactly did you fix it? I am having a strange issue, where the phone will not boot and in recovery everything fails to mount ex: "e: cannot mount \cache" and so on. I've flashed a few different stock restores with no avail, and I think that the partitions are jacked.
Click to expand...
Click to collapse
Check this link out
Link: http://forum.xda-developers.com/showthread.php?t=2369125
Link: http://forum.xda-developers.com/showthread.php?t=2422893&page=2

Need pit file. Phone bricked.

So my phone just stopped working after two days of rooting. I decided to un root it and revert it back to stock with Odin. I downloaded the right file for my phone SGH-M919 but when I tried to flash it. I got there is no pit partition. I tried then using kies and that failed. So I googled s4 pit file and got to a thread that had it. But stupid me thinking that i9505 pit file is the same for my phone because Wikipedia said it was the quad core version which the tmobile is. So now i have a new error for flash.
Please help thank you

The stock tar or md5 file from Sammobile.com has the pit mappings in it.
Sent from my SGH-M919 using Tapatalk 2

elesbb said:
The stock tar or md5 file from Sammobile.com has the pit mappings in it.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
So all I would need is that .tar and it would automatically fix the issue? Or do I have to extract the pit and use it another way? I've never had to deal with this myself but some one else is having the same problem and I'm trying to find the answer for the both of us really, I don't want to be blind if this were to happen to myself so I want to find what I need to correct it before it becomes a problem later.

Flash the stock .tar like the man said...
Sent from my SGH-M919 using xda app-developers app

Orical said:
So all I would need is that .tar and it would automatically fix the issue? Or do I have to extract the pit and use it another way? I've never had to deal with this myself but some one else is having the same problem and I'm trying to find the answer for the both of us really, I don't want to be blind if this were to happen to myself so I want to find what I need to correct it before it becomes a problem later.
Click to expand...
Click to collapse
Just use tar file place it in pda not pit section of odin . Click start after reboot you are back to stock.
Sent from my SGH-M919 using Tapatalk 2

richardlibeau said:
Just use tar file place it in pda not pit section of odin . Click start after reboot you are back to stock.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Sounds simple, I've been helping some one from here out a little and either he doesn't understand what he's doing or there's something else wrong that he doesn't know he did in the mean time but that's pretty simple for a fix. He's been "from what I gather" doing that same thing but when it starts it just hangs at the check in Odin. I told him it takes a few minutes before it actually shows progress but he's waited over an hour so maybe he did something to the partitions that's all I can think of that would cause this to happen but it's hard trying to figure out the problem when you don't have the device in hand.
Thanks for responding I'll send him the link to the thread.

Orical said:
Sounds simple, I've been helping some one from here out a little and either he doesn't understand what he's doing or there's something else wrong that he doesn't know he did in the mean time but that's pretty simple for a fix. He's been "from what I gather" doing that same thing but when it starts it just hangs at the check in Odin. I told him it takes a few minutes before it actually shows progress but he's waited over an hour so maybe he did something to the partitions that's all I can think of that would cause this to happen but it's hard trying to figure out the problem when you don't have the device in hand.
Thanks for responding I'll send him the link to the thread.
Click to expand...
Click to collapse
If it's hanging at the "check" in Odin, it's not even began to write things to the device. The "check" part is checking the tar file. So it may have just been an incomplete download of the tar file.
Sent from my SGH-M919 using Tapatalk 2

elesbb said:
If it's hanging at the "check" in Odin, it's not even began to write things to the device. The "check" part is checking the tar file. So it may have just been an incomplete download of the tar file.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
That's what I thought too, it works for me so he must have flashed something he shouldn't have.
Sent from my SGH-M919 using xda premium

Same problem as above but still getting pit error
I have the same problem as the guy above. I tried to unroot and soft bricked my phone. Kies hasnt worked neither has anything I've read. I've tried the stock tar and modified tar file from this post ( http://forum.xda-developers.com/showthread.php?t=2258628) but still havent had much success. The tar check passes so I'm assuming the files are valid and I'm uploading the file in the PDA slot in Odin 3.07. But when the program runs it gets to (check pit mapping) then it says (device removed) then (device addded) then i get a failed message. Anyone have any ideas?
I'm using Galaxy S4 SGH-M919
Win 7 Home 64bit

So many variables, try original Odin 1.85, try a different USB cable and USB port on PC.
Pp.
sent from my P5113 using TouchPal mind control keyboard. (Beta)

Same problem. Nothing is working. I am using the SGH-M919 pit file, but still, Odin throws errors. "Re-partition operation failed"... I tried everything nothing wants to work so far. Any ideas?

Try using an original Samsung USB cable.

[GUIDE] How to Unbrick your AT&T S4 I337 OTA UCUAMF3

With me not reading about Samsung latest OTA locked bootloader , I rooted my phone, installed TWRP and updated SU, them I am stuck at a soft brick at the download mod, I have tried every possible way with ODIN to no luck, I always kept booting to the damn download mod, then accidentally I was able to flash this pit file to bypass the stuck download mod and was able to boot normally
All you need is ODIN and the attached pit file,
1. Download attached file and unzip it
2. Run ODIN
3. Click on pit
4. Loacate the unziped SGS-I337_16GB.pit file and load it
5. Click start, phone will reboot when when compelete
6. Done
Thought to share my findings
Good Luck Don't forget to Hit the Thanks Button

This is interesting. Is the PIT file you linked a "signed" PIT file?
The reason I am asking is because the PIT file listed in this thread...
http://forum.xda-developers.com/showthread.php?t=2323019&highlight=pit
...appears to not be signed and I think people had trouble flashing it through ODIN because it was not signed.
The size of the PIT file in the thread I linked and the PIT file in your post is different so it definitely appears to be a different PIT file.
Where did you get the PIT file from in your post? Was it pulled from a device running MF3 firmware?
Also, people should be aware both PIT files are for 16GB phones. It says so in the file name, but it's worth an extra mention just the same.
Thank, and it will be interesting to find out more information about this.

wait so, this will just fix the fact u tried to flash the recovery on mf3.. u weren't able to downgrade to amdl were u ?

scott14719 said:
This is interesting. Is the PIT file you linked a "signed" PIT file?
The reason I am asking is because the PIT file listed in this thread...
http://forum.xda-developers.com/showthread.php?t=2323019&highlight=pit
...appears to not be signed and I think people had trouble flashing it through ODIN because it was not signed.
The size of the PIT file in the thread I linked and the PIT file in your post is different so it definitely appears to be a different PIT file.
Where did you get the PIT file from in your post? Was it pulled from a device running MF3 firmware?
Also, people should be aware both PIT files are for 16GB phones. It says so in the file name, but it's worth an extra mention just the same.
Thank, and it will be interesting to find out more information about this.
Click to expand...
Click to collapse
The pit is indeed signed, and it should work for both 16GB and 32GB according to the original information
Yes It is the same file
Sent from my GT-N7105 using xda app-developers app

iB4STiD said:
wait so, this will just fix the fact u tried to flash the recovery on mf3.. u weren't able to downgrade to amdl were u ?
Click to expand...
Click to collapse
I didn't try, but I don't see why not, dude, this could be a work around
Thanks
Sent from my GT-N7105 using xda app-developers app

nkhater said:
The pit is indeed signed, and it should work for both 16GB and 32GB according to the original information
Yes It is the same file
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
Can you tell me where the original information came from (a link)?

scott14719 said:
Can you tell me where the original information came from (a link)?
Click to expand...
Click to collapse
Prob his phone...they are simple to pull from your phone, at least with heimdall. Ive been able to pull my pit with heimdall and use it in odin successfully
His is the exact same size of the pit I pulled from my device which confirms my theory on obtaining it
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

mg2195 said:
Prob his phone...they are simple to pull from your phone, at least with heimdall. Ive been able to pull my pit with heimdall and use it in odin successfully
His is the exact same size of the pit I pulled from my device which confirms my theory on obtaining it
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
The reason i am asking is because I think people have tried to use the PIT file (the one I linked above) with ODIN, and although ODIN reported it as successfully flashing, it actually did not flash. Of course, the PIT file I linked above couldn't have been from MF3 (it wasn't released at the time of that post), but I was wondering if it was a signing issue with the PIT file that kept it from actually flashing, and if not, what would be the difference between the PIT file posted by the OP and the PIT file that is in the thread I linked (other than being pulled from different firmwares)?
It is my understanding (I might be wrong here), that flashing a PIT file via ODIN to a phone would erase all partition information including ROM, KERNEL, and boot partitions. Without this information (in this case a MF3 TAR file) being flashed through ODIN directly after a successful PIT file flash, how could the phone successfully boot back up into MF3? And we all know an ODIN flashable MF3 TAR does not yet exist.

scott14719 said:
The reason i am asking is because I think people have tried to use the PIT file (the one I linked above) with ODIN, and although ODIN reported it as successfully flashing, it actually did not flash. Of course, the PIT file I linked above couldn't have been from MF3 (it wasn't released at the time of that post), but I was wondering if it was a signing issue with the PIT file that kept it from actually flashing, and if not, what would be the difference between the PIT file posted by the OP and the PIT file that is in the thread I linked (other than being pulled from different firmwares)?
Click to expand...
Click to collapse
You know...im not sure. I mean...even with new firmwares shouldnt it be the same? Unless they changed the partitions around in mf3...than again...the one I pulled from my phone was from mdl and mine is the same exact size as his...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

mg2195 said:
You know...im not sure. I mean...even with new firmwares shouldnt it be the same? Unless they changed the partitions around in mf3...than again...the one I pulled from my phone was from mdl and mine is the same exact size as his...
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
Click to expand...
Click to collapse
I added some Ninja edit info to my last post...

nkhater said:
I didn't try, but I don't see why not, dude, this could be a work around
Thanks
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
i say fire up odin and try to downgrade to amdl :good:

iB4STiD said:
i say fire up odin and try to downgrade to amdl :good:
Click to expand...
Click to collapse
As much as I would like to see it work, I don't think it would be a good idea.
A. If the OP was on MF3, how did he even attempt to install TWRP as was stated?
B. (I mentioned this in one of my lasts posts in this thread) If the PIT fil actually has flashed successfully, how would any information (other than partition information) remain on his phone? Wouldn't the PIT file wipe it completely...requiring the OP to immediately flash a firmware TAR file...which does not exist yet for MF3?
Something either is very right with this (a breakthrough) or is very wrong with this.

scott14719 said:
As much as I would like to see it work, I don't think it would be a good idea.
A. If the OP was on MF3, how did he even attempt to install TWRP as was stated?
B. (I mentioned this in one of my lasts posts in this thread) If the PIT fil actually has flashed successfully, how would any information (other than partition information) remain on his phone? Wouldn't the PIT file wipe it completely...requiring the OP to immediately flash a firmware TAR file...which does not exist yet for MF3?
Something either is very right with this (a breakthrough) or is very wrong with this.
Click to expand...
Click to collapse
see, im hoping very right.. I would love to see people get around the sammy bs.. so im trying to be positive (for once) Im confused how this would work myself.. but hey stranger things have happened.. :good:

iB4STiD said:
see, im hoping very right.. I would love to see people get around the sammy bs.. so im trying to be positive (for once) Im confused how this would work myself.. but hey stranger things have happened.. :good:
Click to expand...
Click to collapse
I am theorizing (just a theory) that the PIT file actually did not flash through ODIN. It reported as flashing correctly (successful), but as others have experienced, it was a false positive and didn't really flash. I am guessing the OP's phone started to work because of the method ODIN used to reboot the phone somehow bypassed the bootloop caused by trying to put TWRP onto MF3. I have seen a couple of recent posts where people were able to boot their phones by somehow getting into recovery and canceling a certain operation out ( I'm not sure which), causing the phone (that was in a previous bootloop) to start booting correctly.
I hope it is a break through as well, but I am leaning towards my explanation (or one close to it) as the reason for the OP's success.

scott14719 said:
I am theorizing (just a theory) that the PIT file actually did not flash through ODIN. It reported as flashing correctly (successful), but as others have experienced, it was a false positive and didn't really flash. I am guessing the OP's phone started to work because of the method ODIN used to reboot the phone somehow bypassed the bootloop caused by trying to put TWRP onto MF3. I have seen a couple of recent posts where people were able to boot their phones by somehow getting into recovery and canceling a certain operation out ( I'm not sure which), causing the phone (that was in a previous bootloop) to start booting correctly.
I hope it is a break through as well, but I am leaning towards my explanation (or one close to it) as the reason for the OP's success.
Click to expand...
Click to collapse
ya, wiping cache in stock recovery, will kick the phone out of bootloop

iB4STiD said:
ya, wiping cache in stock recovery, will kick the phone out of bootloop
Click to expand...
Click to collapse
And here is another example of someone getting out of a bootloop through Download (ODIN) mode:
http://forum.xda-developers.com/showpost.php?p=44433724&postcount=11
Possibly, Odin triggered a similar reaction.
Actually, the original thread i pulled that post out of sounds very similar to what happened to the OP in this post.
Take a look at the OP of this post to see what I mean:
http://forum.xda-developers.com/showthread.php?t=2398336
So, I think my theory is correct. The PIT file never actually flashed, it was the interaction between ODIN and D/L mode that overcame the bootloop.
But hey, feel free to keep messing around with the PIT file because you never know...

I wonder where op went...
Sent from my SGH-I337 using xda premium

orlandoxpolice said:
I wonder where op went...
Sent from my SGH-I337 using xda premium
Click to expand...
Click to collapse
OP was sleeping and just woke up will reply shortly
Sent from my GT-N7105 using xda app-developers app

scott14719 said:
It is my understanding (I might be wrong here), that flashing a PIT file via ODIN to a phone would erase all partition information including ROM, KERNEL, and boot partitions. Without this information (in this case a MF3 TAR file) being flashed through ODIN directly after a successful PIT file flash, how could the phone successfully boot back up into MF3? And we all know an ODIN flashable MF3 TAR does not yet exist.
Click to expand...
Click to collapse
Sorry if this off topic but what's stopping someone from wiping the bootloader partition and flashing the MDL firmware?
I'm not sure if this would be done via a PIT file, ADB script or some other method but in general isn't this the path of last resistance for achieving root/bootloader access?

scott14719 said:
Can you tell me where the original information came from (a link)?
Click to expand...
Click to collapse
Here is the link
http://forum.xda-developers.com/showthread.php?t=2323019&highlight=pit

Pit Configuration

Long story short, directly after installing Swap Internal Sdcard to External Sdcard my phone rebooted into recovery mode saying that it could not mount /Data & /Cache. This was on Cyanogenmod 10.2 (latest nightly) and I was an idiot and tried to start over and failed at repartitioning my ROM. Does anyone have a ROM configuration directory tree for a PIT configuration so I can recovery my phone?
Model is: SPH-l900
Recovery: TWRP
This is my last resort D:
======Update======== 10/09/2013
I've done a lot of research, pretty much summed up my options. Since I do not have a PIT configuration for my SPH-l900 I can either buy a hardware / software combo to repair my phone, throw my phone away, or risk taking it to a sprint store.
Also what device would I use to repair my phone? JTAG / RIFFTag? or ???
And also no one can make a PIT file for the SPH-L900 (16GB) ?
I have

Just odin back to a stock rooted LJC rom and it will automagically repartition your phone back the way it needs to be.
Sent from my note 2 ya bish!

d12unk13astard said:
Just odin back to a stock rooted LJC rom and it will automagically repartition your phone back the way it needs to be.
Sent from my note 2 ya bish!
Click to expand...
Click to collapse
Last I researched and tried you cannot just Odin back without a .PIT configuration file with a corrupted ROM (EMMC). Does anyone have a .PIT configuration file for the SPH-L900?

Can you get into odin download mode by holding volume down and power? If so im 99.9% sure its an easy fix. Or you can try your luck finding a .pit configuration...
Sent from my note 2 ya bish!

d12unk13astard said:
Can you get into odin download mode by holding volume down and power? If so im 99.9% sure its an easy fix. Or you can try your luck finding a .pit configuration...
Sent from my note 2 ya bish!
Click to expand...
Click to collapse
I have the PIT file somewhere.... just need to find it.
*Edit* Attached. Use this and MC2 and you should be all set.

garwynn said:
I have the PIT file somewhere.... just need to find it.
*Edit* Attached. Use this and MC2 and you should be all set.
Click to expand...
Click to collapse
Thank you so much, I was hesitant to PM you directly and thought someone else might have the proper .PIT file...
Did you just create it yourself using Pit Magic or how did you get that .PIT configuration? If you don't mind me asking.
d12unk13astard said:
Can you get into odin download mode by holding volume down and power? If so im 99.9% sure its an easy fix. Or you can try your luck finding a .pit configuration...
Sent from my note 2 ya bish!
Click to expand...
Click to collapse
I was looking for a .PIT configuration file because my ROM (EMMC) was corrupted, from my experience Odin only works with regular Custom OS .tar installs if you only have a working ROM (EMMC). I had to repartition my phone first... And I did look lol, I couldn't find a working .PIT file for my phone sadly and on top of that I tried to create my own but failed it hard. I guess it was a great learning experience because sprint looked at my phone and just said that they would replace my old one, and since I've had it for about a year they just let me keep the old one

Guy_with_an_Axe said:
Thank you so much, I was hesitant to PM you directly and thought someone else might have the proper .PIT file...
Did you just create it yourself using Pit Magic or how did you get that .PIT configuration? If you don't mind me asking.
I was looking for a .PIT configuration file because my ROM (EMMC) was corrupted, from my experience Odin only works with regular Custom OS .tar installs if you only have a working ROM (EMMC). I had to repartition my phone first... And I did look lol, I couldn't find a working .PIT file for my phone sadly and on top of that I tried to create my own but failed it hard. I guess it was a great learning experience because sprint looked at my phone and just said that they would replace my old one, and since I've had it for about a year they just let me keep the old one
Click to expand...
Click to collapse
This one I got from a Heimdall pull.
Sent from my SPH-L900 using Tapatalk

garwynn said:
This one I got from a Heimdall pull.
Sent from my SPH-L900 using Tapatalk
Click to expand...
Click to collapse
Thanks again, I think I'll do that from now on lol

garwynn said:
I have the PIT file somewhere.... just need to find it.
*Edit* Attached. Use this and MC2 and you should be all set.
Click to expand...
Click to collapse
So if I have MC2 firmware and use your MC2 pit file this repartition the phone and restore firmware. so what do i click on in odin too run both files. Thanks

tommyjoesanders said:
So if I have MC2 firmware and use your MC2 pit file this repartition the phone and restore firmware. so what do i click on in odin too run both files. Thanks
Click to expand...
Click to collapse
Pit goes in pit slot, tar in pda.
Sent from my LG-LS980 using Tapatalk

garwynn said:
Pit goes in pit slot, tar in pda.
I have same problem and tried to do things as your guy have shown: get the t0lte.zip and MC2 but the pit re-partition is failed after all just seconds after hit the start. Tried to do with several USBs but no help.
What should I do next? I can get my phone into ODIN download mode but could not flash the any stock ROM. I got the message :There is no PIT partition and if I attach file t0tle.pit and check the re-partition box then I got the message second after hit the start button : Re-Partition operation failed.
Click to expand...
Click to collapse

abbuyacc said:
garwynn said:
Pit goes in pit slot, tar in pda.
I have same problem and tried to do things as your guy have shown: get the t0lte.zip and MC2 but the pit re-partition is failed after all just seconds after hit the start. Tried to do with several USBs but no help.
What should I do next? I can get my phone into ODIN download mode but could not flash the any stock ROM. I got the message :There is no PIT partition and if I attach file t0tle.pit and check the re-partition box then I got the message second after hit the start button : Re-Partition operation failed.
Click to expand...
Click to collapse
You should not need to repartition. I don't believe they changed to go to 4.3. What happens if you do just the tarball?
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse

garwynn said:
abbuyacc said:
You should not need to repartition. I don't believe they changed to go to 4.3. What happens if you do just the tarball?
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Could not do anything, and sorry what do you meant when saying "do just the tarball"?
Click to expand...
Click to collapse

abbuyacc said:
Could not do anything, and sorry what do you meant when saying "do just the tarball"?
Click to expand...
Click to collapse
My meaning is try flashing the tar file only. Don't add the pit file or check repartition.
Sent from my LG-LS980 using Tapatalk

garwynn said:
My meaning is try flashing the tar file only. Don't add the pit file or check repartition.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
OH, OK... if so then I got the message something like there is no pit file. The phone if I don't do anything but just hit the power button it will come to a blank screen with nothing in it and you cannot control anything even power button and you will need to take the battery out in order to turn the phone off but I also mentioned that I can get into the Odin download mode and when you do the tarball (your term) you will get the message that said no pit file.

Did this end up working out for you? I've downloaded MC2 (4.1.2?) and another version (4.4 I think) and everything I try keeps telling me I need a PIT file. My phone is soft bricked where it'll go into download mode, but trying to go into recovery or booting it normally and it'll turn into a Poltergeist screeen and won't do anything - http://forum.xda-developers.com/note-2-sprint/help/odd-semi-brick-t3082102

garwynn said:
I have the PIT file somewhere.... just need to find it.
*Edit* Attached. Use this and MC2 and you should be all set.
Click to expand...
Click to collapse
I've tried literally everything possible....Cannot get anything to flash in Odin or Philz Recovery....Is there any other way to try to reset internal memory?

New logic board and now the phone is good as new, thanks eBay

kchannel9 said:
New logic board and now the phone is good as new, thanks
I am in the same boat.
Woke up this morning and phone is on "Galaxy Note 2" screen. Does not even get past the Sprint and Samsung boot anims. Try to boot into TWRP to send some commands and disable Xposed, I did some playing with Xposed last night but when I went to sleep, I had done multiple restarts and tests w/ Xposed modules and all was sound. Put it on the charger and slept. Until this morning!
Not able to send and ADB commands to phone during boot.
I can get into dl mode with Odin but so far the recovery files I've tried to flashed have returned either FAILED or NO PIT PARTITION error.
Kchannel9.. so you got a new motherboard. Were you ever able to recover any of your data off your old motherboard?
Click to expand...
Click to collapse

Nope.