Develop Bugs

[Q][ASAP]Is this a soft brick or a hard brick?

Ok, I have spent a really long time figuring out where to post this, but I still can't figure it out. Please forgive me if this is the improper place.
Please mind that I have looked at similar hard vs soft brick threads, and tried all of the advice given, but nothing has worked yet.
To start, I have a Samsung Galaxy S II from Sprint. The Epic 4G Touch, Model SPH-D710. I am on a MacBook Pro running 10.7.5 OSX. Recently, I followed the steps as listed by h tt p:// epic4gtouchroot .com /epic-4g-touch-root/ how-to-root-epic-4g-touch-on-mac-or-linux/
The Terminal went through the entire process and said it was successful. I thought 'Wow! That was easy!' However, upon rebooting my phone, it never booted past the splash screen which showed "Samsung Galaxy SII GT-I9100" with a yellow triangle at the bottom. At this point I could access Download mode, Recovery mode, this splash screen, and the charging battery that is shown when it is charging and powered off.
I was so confused so I spent about 3 hours on xda looking for an answer. Next, I downloaded Odin and packaged it for Mac. Then I downloaded the Samsung drivers just in case, and the stock ROM for my particular phone. I went through and tried to use Odin. Much to my dismay, Odin would not recognize my phone at all.
So then, I downloaded a .zip file containing the Official Samsung ROM, and put it on my internal sdcard. Under ClockworkMod, I wiped cache, dalvik cache, and wiped all user data. Then, I applied the .zip file using the option in CWM, and it said that it was successful. However, upon rebooting, it went back to the same screen with the yellow triangle.
Next, I downloaded the CF root, and tried to apply it the same way through CWM. Again a fail. However, now upon rebooting to splash screen, it would progressively turn from a black/gray screen to a white screen. Once it got to the white screen, it stopped and stayed there for about an hour. Then it died.
I tried to boot to Download mode but it says that the battery is too low. So now I am trying to charge it. However, it tries to load the charging battery icon that is normally shown when charging a powered off phone, and flashes to black. From this black screen it again slowly turns gray then white. Once it reaches the white screen, it turns back to the charging icon, and starts the stupid cycle over again. Its been doing that for the past 30 minutes.
UPDATE: My battery is not charging AT ALL. Whether plugged in to computer or wall it continues the cycle.
UPDATE 2: I made a video so that you can see what the phone actually does. I still can't post links, so please remove the spaces. http :// youtu .be /4LW60EknFWw

Remove the battery first, then try charging it. After, get windows onto your Mac or borrow a friend's, and use the windows Odin to get back to stock.
Sent from my SAMSUNG-SGH-I747 using xda premium

christykientzler said:
Ok, I have spent a really long time figuring out where to post this, but I still can't figure it out. Please forgive me if this is the improper place.
Please mind that I have looked at similar hard vs soft brick threads, and tried all of the advice given, but nothing has worked yet.
To start, I have a Samsung Galaxy S II from Sprint. The Epic 4G Touch, Model SPH-D710.
<snip>
Click to expand...
Click to collapse
You're in the wrong forum. This is currently posted in the i9100 forums. You want the Epic 4G Touch forum.
EDIT to add:
To clarify - the Epic 4G Touch is a CDMA phone, and the GT-I9100 is a GSM phone which doesn't even work on Sprint's network.
So according to this:
christykientzler said:
Recently, I followed the steps as listed by http://epic4gtouchroot.com/epic-4g-touch-root/how-to-root-epic-4g-touch-on-mac-or-linux/
The Terminal went through the entire process and said it was successful. I thought 'Wow! That was easy!' However, upon rebooting my phone, it never booted past the splash screen which showed "Samsung Galaxy SII GT-I9100" with a yellow triangle at the bottom. At this point I could access Download mode, Recovery mode, this splash screen, and the charging battery that is shown when it is charging and powered off.
Click to expand...
Click to collapse
You apparently flashed something for the GT-I9100 onto your Epic 4G Touch SPH-D710. If you actually did follow the steps at http://epic4gtouchroot.com/epic-4g-touch-root/how-to-root-epic-4g-touch-on-mac-or-linux/ properly, this should not have happened. What exactly did you download and flash? Because if you followed steps for an Epic 4G Touch, then you would not have downloaded and flashed something that would alter your bootscreen to read GT-I9100.
You MIGHT have been at a recoverable spot at this point, until:
christykientzler said:
So then, I downloaded a .zip file containing the Official Samsung ROM, and put it on my internal sdcard. Under ClockworkMod, I wiped cache, dalvik cache, and wiped all user data. Then, I applied the .zip file using the option in CWM, and it said that it was successful. However, upon rebooting, it went back to the same screen with the yellow triangle.
Next, I downloaded the CF root, and tried to apply it the same way through CWM. Again a fail. However, now upon rebooting to splash screen, it would progressively turn from a black/gray screen to a white screen. Once it got to the white screen, it stopped and stayed there for about an hour. Then it died.
Click to expand...
Click to collapse
By my count, that's you flashing 3 things meant for an GT-I9100 to an SPH-D710.
You're probably out of luck at this point, but again, check in the Epic 4G Touch forum. Maybe someone there can help you, but I wouldn't hold my breath. You might have some luck trying to get a warranty exchange at a Sprint store, if they can't get your phone to boot and see exactly how bad you buggered it. But I wouldn't hold my breath on this, either.

Oh my goodness...
ctomgee said:
You're in the wrong forum. This is currently posted in the i9100 forums. You want the Epic 4G Touch forum.
EDIT to add:
To clarify - the Epic 4G Touch is a CDMA phone, and the GT-I9100 is a GSM phone which doesn't even work on Sprint's network.
So according to this:
You apparently flashed something for the GT-I9100 onto your Epic 4G Touch SPH-D710. If you actually did follow the steps at http://epic4gtouchroot.com/epic-4g-touch-root/how-to-root-epic-4g-touch-on-mac-or-linux/ properly, this should not have happened. What exactly did you download and flash? Because if you followed steps for an Epic 4G Touch, then you would not have downloaded and flashed something that would alter your bootscreen to read GT-I9100.
You MIGHT have been at a recoverable spot at this point, until:
By my count, that's you flashing 3 things meant for an GT-I9100 to an SPH-D710.
You're probably out of luck at this point, but again, check in the Epic 4G Touch forum. Maybe someone there can help you, but I wouldn't hold my breath. You might have some luck trying to get a warranty exchange at a Sprint store, if they can't get your phone to boot and see exactly how bad you buggered it. But I wouldn't hold my breath on this, either.
Click to expand...
Click to collapse
Oh my goodness... I knew I really had screwed the pooch on this one D:
Thanks for letting me know that I really am in a world of trouble. I had thought that GT-I9100 was a type of SPH-D710.
Also I apologize for the incorrect post location. Again, I hadn't understood the difference.
Do you think if I could charge up the battery, and get it into download mode with a jig, I might be able to use OneClick UnBrick? Or some other method?

christykientzler said:
Oh my goodness... I knew I really had screwed the pooch on this one D:
Thanks for letting me know that I really am in a world of trouble. I had thought that GT-I9100 was a type of SPH-D710.
Also I apologize for the incorrect post location. Again, I hadn't understood the difference.
Do you think if I could charge up the battery, and get it into download mode with a jig, I might be able to use OneClick UnBrick? Or some other method?
Click to expand...
Click to collapse
I have no idea. The two phones are different enough that any advice I give you would be invalid.
My suggestion about going to the Epic 4G Touch forum to ask for help there still stands. You're much more likely to find helpful advice and valid files for your particular device there. Do not use any more guides or download any more files from the I9100 forums.
That said, it looks like you may have tried either flashing a GT-I9100 bootloader or .pit file to your phone, which REALLY would have screwed the pooch, yes. If you can't get help in the Epic 4G Touch forums, I'd just take it to a Sprint store and tell them that a Kies update screwed your phone up.

TLDR
There is no such thing as a "Soft" or "Hard" brick, Your device is either bricked or it isnt, simple as that.
If you can get into download or recovery and use them your device is not bricked.

Will do
ctomgee said:
I have no idea. The two phones are different enough that any advice I give you would be invalid.
My suggestion about going to the Epic 4G Touch forum to ask for help there still stands. You're much more likely to find helpful advice and valid files for your particular device there. Do not use any more guides or download any more files from the I9100 forums.
That said, it looks like you may have tried either flashing a GT-I9100 bootloader or .pit file to your phone, which REALLY would have screwed the pooch, yes. If you can't get help in the Epic 4G Touch forums, I'd just take it to a Sprint store and tell them that a Kies update screwed your phone up.
Click to expand...
Click to collapse
Ok :good: Will do. I was wondering what I'd tell them if I went to a Sprint store Thanks again.

TheATHEiST said:
TLDR
There is no such thing as a "Soft" or "Hard" brick, Your device is either bricked or it isnt, simple as that.
If you can get into download or recovery and use them your device is not bricked.
Click to expand...
Click to collapse
Lol?
Softbrick is corrupted system files which result in a bootloop.
Hardbrick is a dead phone that can be fixed with a Jtag or M/B replacement...
Sent from my GT-I9100

Again, there is no such thing as a "soft brick". There is just "bricked" and the term is used too loosely by n00bs.
If you can simply re-flash a rom your device is not bricked at all.
"Soft brick" is just a n00b term that is used because they think their device is bricked if they can't get it to boot.
Your device is only "bricked" if all you can do is JTAG or mobo replace.
Sent from my GT-I9100 using xda premium

ctomgee said:
I have no idea. The two phones are different enough that any advice I give you would be invalid.
My suggestion about going to the Epic 4G Touch forum to ask for help there still stands. You're much more likely to find helpful advice and valid files for your particular device there. Do not use any more guides or download any more files from the I9100 forums.
That said, it looks like you may have tried either flashing a GT-I9100 bootloader or .pit file to your phone, which REALLY would have screwed the pooch, yes. If you can't get help in the Epic 4G Touch forums, I'd just take it to a Sprint store and tell them that a Kies update screwed your phone up.
Click to expand...
Click to collapse
boki9999 said:
Lol?
Softbrick is corrupted system files which result in a bootloop.
Hardbrick is a dead phone that can be fixed with a Jtag or M/B replacement...
Sent from my GT-I9100
Click to expand...
Click to collapse
Is there a one-stop resource for "Jtag or M/B replacement"? I'm having trouble searching forums for some reason, otherwise I would look for it myself.

You need to get it into download mode and then reflash a ROM appropriate for your device. Your phone isn't bricked - but if you fail to get it working again and have to resign to using it purely as a surface to sniff your cocaine off, then you have only yourself to blame.

postfatal said:
You need to get it into download mode and then reflash a ROM appropriate for your device.
Click to expand...
Click to collapse
Thank you, will do.
postfatal said:
Your phone isn't bricked - but if you fail to get it working again and have to resign to using it purely as a surface to sniff your cocaine off, then you have only yourself to blame.
Click to expand...
Click to collapse
LMAO, that's true. I don't blame anyone but myself for my mistakes.

If you hadnt understood the difference then why did you decide one day to go I to your phone and per form operations that are completely unknown to you? Do you ipen up your cars engines and place honda parts into your ford Fiesta?
Sent from my SGH-T889 using Tapatalk 2

Curiousity killed the cat...
ssCISengineer said:
If you hadnt understood the difference then why did you decide one day to go I to your phone and per form operations that are completely unknown to you? Do you ipen up your cars engines and place honda parts into your ford Fiesta?
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
Because I am curious. This is where it often times gets me, but I like to learn new things by doing. In my eyes it's usually worth the risk. I will admit this was a stupid mistake, but I have certainly learned a lot about rooting in the process

Wow. So, hopefully by now you are in the correct forum. And hopefully have downloaded the appropriate Odin tar file to restore your phone properly. Get that at the dev section of E4GT. Charge that battery in a different phone if you have to. Get into Odin mode and run Odin from a PC (Heimdall for macs?), if the PC does not recognize your phone, its probably the cable. If Odin starts but then fails half way through, its probably the cable. BTW, check out SFHubs Odin-one clicks for your phone, probably the easiest way to restore a clean, new rom.
And in the future, be more curious before you act. Read read read.
Good luck.

Thank you
Dr. Fed said:
Wow. So, hopefully by now you are in the correct forum. And hopefully have downloaded the appropriate Odin tar file to restore your phone properly. Get that at the dev section of E4GT. Charge that battery in a different phone if you have to. Get into Odin mode and run Odin from a PC (Heimdall for macs?), if the PC does not recognize your phone, its probably the cable. If Odin starts but then fails half way through, its probably the cable. BTW, check out SFHubs Odin-one clicks for your phone, probably the easiest way to restore a clean, new rom.
And in the future, be more curious before you act. Read read read.
Good luck.
Click to expand...
Click to collapse
Yes I got to the correct forum.I still don't know which file to download. Nobody has bothered to point me in the right direction. Considering what I did to it last time with what I thought was the correct file, any direction would be appreciated. :/ I'll definitely ask in the E4GT forums. I'm currently working on getting a charged up battery, but I won't be able to do so until next Friday. I've looked into OneClick UnBrick. When I get the charged battery, I will definitely use a more reliable cord. XP I will definitely research more next time. In fact I might not mess with it at all!
Thank you for your help!

christykientzler said:
Yes I got to the correct forum.I still don't know which file to download. Nobody has bothered to point me in the right direction. Considering what I did to it last time with what I thought was the correct file, any direction would be appreciated. :/ I'll definitely ask in the E4GT forums. I'm currently working on getting a charged up battery, but I won't be able to do so until next Friday. I've looked into OneClick UnBrick. When I get the charged battery, I will definitely use a more reliable cord. XP I will definitely research more next time. In fact I might not mess with it at all!
Thank you for your help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1903252
If you can get into Odin mode (on a PC preferably) , download one of these files. I recommend the latest official ICS build. Read the op carefully. That will return you back to stock. All your data is gone,, but hopefully you've always backed up your contacts to Google. The play store will have your app history.

Wait what..?
Dr. Fed said:
http://forum.xda-developers.com/showthread.php?t=1903252
If you can get into Odin mode (on a PC preferably) , download one of these files. I recommend the latest official ICS build. Read the op carefully. That will return you back to stock. All your data is gone,, but hopefully you've always backed up your contacts to Google. The play store will have your app history.
Click to expand...
Click to collapse
I see that the latest is FI27. The three files shown are OneClick.exe, a zip file, and an unrooted TAR file. From those I'm assuming that OneClick.exe is a windows application that goes in and puts your phone back to the ICS build with one click? This method would be the simplest, except for the fact I have a Mac. Would the time taken to repackage it be worth it or would one of the other two options be better? And the zip file. Would I be able to put that on my internal SD card and flash it through CWM? Or would I unzip it and flash through heimdall. As for the TAR file, I am unfamiliar with this, and am not sure how this file would be utilised.
The last time I tried to understand a concept on my own, I ended up with a bricked phone so please forgive me for asking so many questions, I just don't want to mess it up a second time.
As for the data, yes it is gone. DX Yes I backed up contacts *phew*. I had a feeling going into this that I should back up something.

christykientzler said:
I see that the latest is FI27. The three files shown are OneClick.exe, a zip file, and an unrooted TAR file. From those I'm assuming that OneClick.exe is a windows application that goes in and puts your phone back to the ICS build with one click? This method would be the simplest, except for the fact I have a Mac. Would the time taken to repackage it be worth it or would one of the other two options be better? And the zip file. Would I be able to put that on my internal SD card and flash it through CWM? Or would I unzip it and flash through heimdall. As for the TAR file, I am unfamiliar with this, and am not sure how this file would be utilised.
The last time I tried to understand a concept on my own, I ended up with a bricked phone so please forgive me for asking so many questions, I just don't want to mess it up a second time.
As for the data, yes it is gone. DX Yes I backed up contacts *phew*. I had a feeling going into this that I should back up something.
Click to expand...
Click to collapse
The one clicks are full "images" flashed through Odin. I recommend this because a one click will reflash your stock rom, modem, and recovery partition. This is what you need to do to repair your phone. If you try to flash something in recovery, it will repair your rom but not necessarily your modem/radio/firmware, and this could be a problem. I'm not sure exactly what you flashed before, so I think its best if you fix it all with a One Click.
As far as using a Mac goes, I am not sure. I'll look into it, you should too. Odin used to be only for PCs, Heimdall for Macs. Maybe its changed now?
---------- Post added at 08:30 PM ---------- Previous post was at 08:19 PM ----------
You must have some schmo friend that will let you borrow his or her PC laptop for 10 minutes. Install Odin , install the proper drivers. Go into Odin mode, connect phone, once recognized... click.
Look up QBKing77 on YouTube, search on YouTube "QBking77 Epic 4g Touch" and you will see instructional videos with appropriate download links.

Why have you lot continued to answer this thread ? It's in the wrong place. More to the point, why hasn't anyone asked mods to move it to Epic 4G Q&A ? (Which I've just done)

[Q] Samsung galaxy SIII hard bricked will not boot but ODIN can recognize it

Samsung galaxy SIII hard bricked will not boot no power, but ODIN 1.85 can recognize it, (not the new Odins), when I try to re-flash it with Odin I get stuck at setupConnection..
any help? can I use the small USB mod

If you don't mind me asking, how you brick your phone?
Sent from my SGH-T999 using xda app-developers app

i have the same problem i used the Odin3 v1.85 and installed CF-Root-SGS3-v6.4 zip but it failed. so then i tried to reboot it and said firmware update encountered an issue and something else. then i looked up how to unbrick and the post said to downloaded the zip CF-Insecure-SGS3_XX_NEE_ALE8-v1.2 and used Odin to install now i got nothing but a black screen buy it will go into download mode and Odin read it

You're not hard bricked if Odin can read your phone. Reboot your computer then reconnect and flash a stock rom to be safe.

chubby1_8888 said:
i have the same problem i used the Odin3 v1.85 and installed CF-Root-SGS3-v6.4 zip but it failed. so then i tried to reboot it and said firmware update encountered an issue and something else. then i looked up how to unbrick and the post said to downloaded the zip CF-Insecure-SGS3_XX_NEE_ALE8-v1.2 and used Odin to install now i got nothing but a black screen buy it will go into download mode and Odin read it
Click to expand...
Click to collapse
If I'm not wrong ODIN uses TAR files and not ZIP files. Try unziping and see if there is a TAR file if there is then thats what you have to use in ODIN.

Same as OP's phone
Sprint s3 flash pacman JB and google apps the went to reboot recovery ask to reflash su yes phone powered off and no coming back on Odin does detect it on com05 when I plug it in but anything I try to do just says waiting on connection, will not go into recovery or download modes. is there anything I can do to fix it? kies or anything? and I edited the updater scripts to be able to flash pacman because every rom I tried would fail with error 7............ please help

Kevinreid1 said:
Sprint s3 flash pacman JB and google apps the went to reboot recovery ask to reflash su yes phone powered off and no coming back on Odin does detect it on com05 when I plug it in but anything I try to do just says waiting on connection, will not go into recovery or download modes. is there anything I can do to fix it? kies or anything? and I edited the updater scripts to be able to flash pacman because every rom I tried would fail with error 7............ please help
Click to expand...
Click to collapse
Do you get a message when you plug it into your computer? Does the red LED turn on? Editing the scripts is dangerous if you don't know what you are doing!

serio22 said:
Do you get a message when you plug it into your computer? Does the red LED turn on? Editing the scripts is dangerous if you don't know what you are doing!
Click to expand...
Click to collapse
followed the guides about it just removed from top to quotes dealing with checking versions of device.

Kevinreid1 said:
followed the guides about it just removed from top to quotes dealing with checking versions of device.
Click to expand...
Click to collapse
I'm not saying that was the problem or that you did it wrong, but maybe the ROM was forced to flash and was truly not compatible or was corrupt, bricks are highly likely to occur in this case

serio22 said:
I'm not saying that was the problem or that you did it wrong, but maybe the ROM was forced to flash and was truly not compatible or was corrupt, bricks are highly likely to occur in this case
Click to expand...
Click to collapse
The roms I have downloaded are supposed to be for Sprint s3 I was running stock JB 4.3 if that makes any difference, any help on what to do know, thinking of trying the unbrick mmc card trick .... idk what else to do... thanks : ) and something went wrong somewhere for sure... lol I also found out my exact model number if that helps. SPH-L710MBBSPR again thanks for you responses..

Ok, a few things I noticed....
1. You are using a very old version of Odin. I recommend only using 3.07 or 3.09.
2. The COM port box is yellow, which probably was trying to caution you about something.
3. You have a Sprint model S3. This is the T-Mobile S3 forum.
4. You have a Sprint S3, but were trying to flash old T999 firmware! This simply will not work, and if it were to flash, insta-brick!
What you need to do is start using the Sprint forums. Only flash items you find in those forums, and nothing else. While some of our roms might flash and boot on yours, they will never function very well. This is one of the things the asserts in an updater script are intended to protect against.
Finally, just a bit of posting advice. Please use proper punctuation. Small mistakes are ok, but posting with no punctuation at all just makes it difficult for people to read, and many will just close the thread and move to the next without bothering to help.
---------- Post added at 02:28 AM ---------- Previous post was at 02:25 AM ----------
Oops! Just realized the pic in the op wasn't yours! But still, theyre all good points you should check before flashing. Also make sure kies is uninstalled or disabled on your computer.
But most importantly, you need to be in the Sprint forums. We can help a bit here, but you need to ONLY use stuff from your devices forum. And a lot of it we simply may not be familiar with.
Good luck!

DocHoliday77 said:
Ok, a few things I noticed....
1. You are using a very old version of Odin. I recommend only using 3.07 or 3.09.
2. The COM port box is yellow, which probably was trying to caution you about something.
3. You have a Sprint model S3. This is the T-Mobile S3 forum.
4. You have a Sprint S3, but were trying to flash old T999 firmware! This simply will not work, and if it were to flash, insta-brick!
What you need to do is start using the Sprint forums. Only flash items you find in those forums, and nothing else. While some of our roms might flash and boot on yours, they will never function very well. This is one of the things the asserts in an updater script are intended to protect against.
Finally, just a bit of posting advice. Please use proper punctuation. Small mistakes are ok, but posting with no punctuation at all just makes it difficult for people to read, and many will just close the thread and move to the next without bothering to help.
---------- Post added at 02:28 AM ---------- Previous post was at 02:25 AM ----------
Oops! Just realized the pic in the op wasn't yours! But still, theyre all good points you should check before flashing. Also make sure kies is uninstalled or disabled on your computer.
But most importantly, you need to be in the Sprint forums. We can help a bit here, but you need to ONLY use stuff from your devices forum. And a lot of it we simply may not be familiar with.
Good luck!
Click to expand...
Click to collapse
Thank you.. I knew I was in the wrong forum and that is why I said my s3 was a Sprint device... My problem however was the same exact problem. I got it fixed with file from another forum, while follow info from yet another forum, the file that worked for me was HomefixSprint_S3_L710.img the debrick_sph_l710.img would not work for me. I used win32diskimager and burned .img file to class 10 32gb card, stuck it in went in to download mode and used odin to write firmware file... Anyway back up any running.. I didn't download any t-mobile roms or anything that wasn't for the Sprint S3, what I did do was try and load an older JB rom that was under V4.3, it wasn't that long ago when a person could flash any android version one wished, it looks like Samsung is getting as bad as Apple you can move up but not back. Any tips on how to safely downgrade? Anyway thanks for taking the time to respond. : ) Cause no one has in the Sprint S3 forum yet.

Kevinreid1 said:
it wasn't that long ago when a person could flash any android version one wished, it looks like Samsung is getting as bad as Apple you can move up but not back. Any tips on how to safely downgrade?
Click to expand...
Click to collapse
No, Samsung is not turning into apple, there is a reason you cannot downgrade from a Knox bootloader. And to downgrade, with this device we can just flash an older ROM and it will work, maybe its different with the Sprint variant? Try to search in their forums if you haven't already

[Q] Boot Loop/Stock firmware/I seriously need help PLEASE!!!!

Hello all *waves*
This is my very first post although I have used this site countless times. I'm just going to jump right to it because I seriously need some help!
I am trying to fix my SGH-M919 (Tmobile S4) that just suddenly stopped working one day. I have tried EVERYTHING! Kies, custom roms, Odin but my phone still will not load past the Samsung logo. It will boot into recovery (TWRP) and Download mode. I know that using Kies is the quick fix but (LUCKY ME...not) my phone is one of the few phones tmobile/Samsung sent out with no S/N on the sticker under the battery. Since I cant get into my phone I cant get the S/N and I do not have the box anymore.
I have tried using the many sgh-m919 Stock Rom files online, including this site, but nothing is working. When I spend hours downloading them and begin to use them in odin, Odin doesn't load the file for me to flash.
I know I am using Odin correctly because I have done it successfully countless times in the past. I have also tried EVERY download file out there, but I can't find a good one that I can flash in Odin. I have also tried all of the guides on this site several times so please don't redirect me to them, because I have seriously and correctly tried them all. If you have any suggestion please let me know. I can't afford the 161.00 Samsung is requiring or the 175 warranty fee tmobile is charging. PLEASE HELP.
And if some has a good copy of the Stock Rom for SGH-M919 that they would be willing to email me I would FOREVER be greatful!
also my sdcard and battery are not the issue.... tried that too
Thanks,
Nikki

Were there any symptoms or anything you may have done out of the ordinary that might or might not have caused the problem? By saying that odin will not load files, is there an error message or what exactly do you mean by that? And what version odin are you using?

serio22 said:
Were there any symptoms or anything you may have done out of the ordinary that might or might not have caused the problem? By saying that odin will not load files, is there an error message or what exactly do you mean by that? And what version odin are you using?
Click to expand...
Click to collapse
I don't know if its something I have done wrong or not. I followed all of the instructions to the letter. I think (but am not sure) that I don't have a usable copy of the Stock Firmware.
I am using v3.10 but I have tried them all.
When I click on AP in Odin, then click on the file I am sent back to Odin, but the file (and filename) doesn't appear in the AP box like normal.

The stock firmware files take a while for odin to validate md5 check I think. Select your firmware file in Odin's selector, then wait a few mins for bit to process before giving up. This time lag surprised me first time I flashed stock firmware. Big file means longer wait!
Sent from my SGH-M919 using Tapatalk

Frankenscript said:
The stock firmware files take a while for odin to validate md5 check I think. Select your firmware file in Odin's selector, then wait a few mins for bit to process before giving up. This time lag surprised me first time I flashed stock firmware. Big file means longer wait!
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
The longest I have waited has been an hour, do you think that I should still wait longer?

Try different version of odin. Even if the file was bad, it would say something

Try a different pc.
Pp.

**SOLVED** Any/All ODIN flashes FAIL!

SOLVED: see post #5 & #8
I've been trying to root my T807T and everyone with one on the forums here has reported that all T805 stuff works just fine on it.
I have installed USB drivers, USB Debugging set to on. Been using Odin 3.07 as well as 3.09.
I tried multiple USB ports and two computers and a whole lot of different wires (including original ones).
I disabled my Anti-virus and do not have Kies installed.
I am not a newbie to flashing and have been rooting Samsungs since the first Galaxy S Vibrant all those years ago. I have never seen anything like this.
Everything I try to flash in Odin comes up with FAIL! after about halfway through flashing. I can restart my tablet and everything works fine, but this is making it impossible to root.
FAIL occurs right after "NAND Write"
Any/all help is very much appreciated. If anyone is NYC local and can give it a shot, that'd be great.
Thanks everyone.

I would suggest taking a look at this thread. http://forum.xda-developers.com/showthread.php?p=54393309
Install kies and reinstall drivers with kies probably would help?

DUHAsianSKILLZ said:
I would suggest taking a look at this thread. http://forum.xda-developers.com/showthread.php?p=54393309
Install kies and reinstall drivers with kies probably would help?
Click to expand...
Click to collapse
I've read that thread before, not the same issue. But thanks for the heads up nevertheless

postulio said:
I've read that thread before, not the same issue. But thanks for the heads up nevertheless
Click to expand...
Click to collapse
I would uninstall the drivers and try to install the drivers from kies. Other than that, Im not sure why it wouldnt work.

I have been digging a lot on the issue. Of course I haven't been able to find a whole lot other then it appears 95 percent of these nand write issues are with samsung devices. Make sure that in settings>general>security reactivation lock is OFF. Also try removing your SIM card and the SD card if you have one. Then proceed to flash. We have the exact same model, firmware, build, etc etc. I can't think of a logical reason why it won't work. I'd be inclined to believe it's a communication issue between tablet and computer at this point. Completely stumped on this one however I will keep digging for you.

DUHAsianSKILLZ said:
I would uninstall the drivers and try to install the drivers from kies. Other than that, Im not sure why it wouldnt work.
Click to expand...
Click to collapse
no go.

postulio said:
no go.
Click to expand...
Click to collapse
Does your tar have .md5 at the end of the filename? I think it should fail earlier if this is the problem but maybe its not being properly verified? Its just a shot in the dark but try removing the .md5 if its there and just flash the straight .tar file. Or retry download maybe you got a corrupt copy.
Sent from my Nexus 7 using XDA Free mobile app

Ripx88 said:
I have been digging a lot on the issue. Of course I haven't been able to find a whole lot other then it appears 95 percent of these nand write issues are with samsung devices. Make sure that in settings>general>security reactivation lock is OFF. Also try removing your SIM card and the SD card if you have one. Then proceed to flash. We have the exact same model, firmware, build, etc etc. I can't think of a logical reason why it won't work. I'd be inclined to believe it's a communication issue between tablet and computer at this point. Completely stumped on this one however I will keep digging for you.
Click to expand...
Click to collapse
HAHAHAHA BINGO!!!!
woooo!
cfautoroot: BAM! worked first try.
everybody dance.
Thank you very much for this genius tidbit. I must've enabled it the first day I got the tablet and forgot all about it as It's never been an option on any of my other devices.
Huge thanks to both of you guys for bending over backwards trying to find a solution as to why the flashing wasn't working. Now we know.
Pretty clever of Samsung to hide an Odin flash lockout switch within the actual OS (as opposed to recovery).

s3 ?bricked? STUCK/LOOP ON DOWNLOAD MODE ONLY

i have my friends phone and he's galaxy s3 is stuck on download mode and its looping there everytime
it happened out of nowhere, he wasn't playing around with it it just happened
now its stuck on downloading and wont go to recovery for me to initialize the device through kies or smartswitch
NO ACCESS TO RECOVERY MODE AT ALLL
i tried numerous ways to retrieve the phone into working condition but no success at all
thru odin i get the pit error and when i place a pit to repartititon with the stock tar file or the cwm recovery tar i failed
it says complete write operation failed and it takes a long time to set up connection with the device before showing me the fail
its a tmobile sgh-t999 prob 16 gb
any genius here got any ideas?

What firmware build was on the device and what build did you try to flash using Odin?
Did you try different versions of odin?
Different driver versions?
Different USB cable?
Different USB port?
If kies is installed on the computer, get rid of it. It interferes with Odin.
If none of that helps it may be a hardware failure.
Sent from my SGH-T999 using Tapatalk

The same thing has happened to my wife's phone and I have done almost the same steps to fix it with similar results.

If you tried everything I mentioned and are sure you weren't flashing an older firmware build (only after 4.3), then theres a good chance it's a hardware failure, probably with the memory.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
If you tried everything I mentioned and are sure you weren't flashing an older firmware build (only after 4.3), then theres a good chance it's a hardware failure, probably with the memory.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
OK, uninstalled Kies and tried to flash T999UVUEOH1_T999TMBEOH1_TMB rom with odin again and got there is no pit partition error. Would post some pictures of the boot screen and a screenshot of the odin program but need 10 posts. Well not sure what version was on phone before all this happened.) Also the ODIN bootloader screen says SYSTEM STATUS: NONE Warrenty Bit: 0 BOOTLOADER AP S?AEV: 1 among other things...forgot to mention I used ODIN v3.10.6 because v3.10.7 gave me a win32 error when I tried to run it on my Windows XP PC.

Here's my suggestion to at least get the phone running a ROM:
download Odin 3.07 from here: https://www.google.ca/url?sa=t&rct=...5QWImOPDJboTA_V3D5S9eA&bvm=bv.107763241,d.dmo
download the tar version of TWRP 2.8.6.0 from here: https://dl.twrp.me/d2tmo/
download the latest cm12.1 for the phone from here and save it to a micro SD card: https://download.cyanogenmod.org/?device=d2tmo&type=nightly
place the micro SD card into the phone;
boot the phone into download mode;
open Odin 3.07 and uncheck everything except f. reset time;
click on PDA and browse to the tar TWRP file and select it;
connect the phone and it should show up as a com port in Odin;
flash TWRP;
when you see the word RESET in the status window, remove the USB cable, remove the battery, replace the battery, use the button combination to get into recovery which should now be TWRP;
perform a full wipe of system, data, and cache;
flash CM12.1 from the micro SD card;
reboot the phone.
Hopefully, the above steps will get the phone booted so you can confirm the installed bootloader and modem.

Followed your guide step by step but flash failed in odin Get Pit for mapping..
There is no PIT partition.
All threads completed. (succeed 0 / failed 1):crying: BTW thank for all your help.

You got the pit error flashing twrp in Odin? Any other errors? What model number is shown at the top of the screen when the phone is in download mode?

The only times I've encountered this type of behavior it turned out to be a hardware failure (memory). If that is indeed the case here, I'm afraid there won't be much you can do for it. Don't get me wrong, I'm not saying you should just give up, but you should probably at least start looking at other options.
The main reasons I believe this to be the case are
1. It just died while nothing was being done (not being used)
2. Pit errors indicate either the partition table has been corrupted, or the partitions themselves have. Because it cannot detect any system (SYSTEM STATUS: NONE), it's more likely to be the partitions them selves, not the partition information table (pit).
Something else that doesn't look good, (but that I've never seen before) is the S?AEV. It should be SWREV. (Software Revision). It may mean nothing, but I've never seen it before so I thought I'd point it out.
As I said, I'm not saying you should give up yet. I've been wrong before and I'd hope to be again in this case. But I wouldn't put too much more time and effort into it as I've never seen one of these types of failures restored. They are pretty rare, but they do happen.
My best suggestion at this point is to start looking into replacing either the motherboard or the device. Motherboards can be found for reasonable prices, but you do have to be careful when buying one. (Let us know if you want to do this and we'll give you some tips on what to look for).
I'm sorry that this happened and that there doesn't seem to be much I can do to help. If you had any important data (pics or whatever), there's a small chance it can still be recovered. Don't get your hopes up too much for it, but using ADB while in download mode MIGHT allow you to copy your stuff to the computer. I can't remember if this can be done from download mode though, and if the data partition is also hosed you'd be out of luck there anyway.
If i think of anything else you can try, I'll certainly let you know. Audit13 might have a few ideas you can try too. As I said though, you should also start looking into other options. Let us know what you want to do and we'll continue to help as best as we can!
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
The only times I've encountered this type of behavior it turned out to be a hardware failure (memory). If that is indeed the case here, I'm afraid there won't be much you can do for it. Don't get me wrong, I'm not saying you should just give up, but you should probably at least start looking at other options.
The main reasons I believe this to be the case are
1. It just died while nothing was being done (not being used)
2. Pit errors indicate either the partition table has been corrupted, or the partitions themselves have. Because it cannot detect any system (SYSTEM STATUS: NONE), it's more likely to be the partitions them selves, not the partition information table (pit).
Something else that doesn't look good, (but that I've never seen before) is the S?AEV. It should be SWREV. (Software Revision). It may mean nothing, but I've never seen it before so I thought I'd point it out.
As I said, I'm not saying you should give up yet. I've been wrong before and I'd hope to be again in this case. But I wouldn't put too much more time and effort into it as I've never seen one of these types of failures restored. They are pretty rare, but they do happen.
My best suggestion at this point is to start looking into replacing either the motherboard or the device. Motherboards can be found for reasonable prices, but you do have to be careful when buying one. (Let us know if you want to do this and we'll give you some tips on what to look for).
I'm sorry that this happened and that there doesn't seem to be much I can do to help. If you had any important data (pics or whatever), there's a small chance it can still be recovered. Don't get your hopes up too much for it, but using ADB while in download mode MIGHT allow you to copy your stuff to the computer. I can't remember if this can be done from download mode though, and if the data partition is also hosed you'd be out of luck there anyway.
If i think of anything else you can try, I'll certainly let you know. Audit13 might have a few ideas you can try too. As I said though, you should also start looking into other options. Let us know what you want to do and we'll continue to help as best as we can!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Wow, thanks Doc for replying. I was hopeful for a better result. BTW it does say SWREV I just couldn't quite make out the W at the time so I put ? to indicate that. I do have a little experience working on these phones (replaced the entire LCD/screen and USB port on my Note2) The model of the phone is listed as SGH-T999 in ODIN mode and it is a T-mobile phone. How much is motherboard and what should I look for as far as part number?

Found this with a quick ebay search: http://m.ebay.com/itm/Samsung-Galax...Board-Motherboard-s3-/221940485670?nav=SEARCH
I searched for "galaxy s3 T999 motherboard". That one is 68.50 obo.
It's been a while since I've looked, and it looks like there's a lot fewer of them available now. (Used to get tons of results).
You can also look for an I747 (AT&T) board. The I747 and T999 are fully compatible. No other models will fit into the case. (The T999V and I747M would probably also work. I'm not sure about the T999L or T999N models though. I'm guessing they would, but really have no idea for sure.)
Some terms to search for would be: Galaxy S3 T999 motherboard, I747 motherboard, mainboard, etc.
Also search for the same models with broken screens. Many times people sell these cheap and everything inside works perfectly. Might be cheaper too.
Watch out for certain words and phrases in the listing though. Some sellers will try a little wordplay to make it sound better than it is. If i find an example, I'll post it. Stuff like cracked screen won't power on can be changed to sound like it's only the screen won't come on, when it's really the whole device. Either ask for clarification, or move on.
I like the ones that are very specific, like cracked screen, but does appear to boot up and gives boot sounds.
Ask the seller for the imei number and check it yourself on swappa. I'd also call t-mobile and verify with them.
I hope that helps. Feel free to ask if you're wondering about a specific listing or anything else.
Oh and if buying from an eBay store, make sure they've got very good ratings. Individual people often won't have many ratings, but can sometimes be more trustworthy and more willing to give specifics. Sometimes....
You can also check places like Swappa and Craigslist.
Sent from my SGH-T999 using Tapatalk

The simplest way to get a replacement motherboard would be to look in the used market for a t999 that has smashed or defective screen with working internals.
If it is not too expensive, a jtag repair centre may be able to force flash a rom.