Related
Hey guys im having a bit of an issue when trying to flash the official FCO6 Stock rom through odin. I have v1.85 and 1.87 and both show the same thing. I have the victory pit file and the SPH-D700-FC09-8GB-REL.TAR.MD5 file both on my desktop but when my phone is plugged in and ready to go, and I click PDA on odin and go to desktop, it isn't their. The victory file shows up and I place that In it's correct place but the md5 does not. No matter where I put it? anyone have any suggestions so I can odin my phone?
try erasing the .md5 part at the end
Try the phone slot instead.
Sent from my GT-P7510 using Tapatalk 2
Hey guys I have this exact same problem right now. My phone is in a bootloop so I am trying to odin back to stock but the FC09 file will not show up. I have tried removing the .md5 as well but that does not work either. I have tried deleting and re-downloading 3 times. I know the file is there 100% and I know I am looking in the right folder 100%.
edit: this is odin 1.87 and I have tried the phone slot with the same results.
edit #2: I am sure someone else will run into this problem someday since two of us have. Apparently this is the only file you will ever unzip. I have it so ground into my head to never unzip anything I didn't think of that
danipoak said:
Hey guys I have this exact same problem right now. My phone is in a bootloop so I am trying to odin back to stock but the FC09 file will not show up. I have tried removing the .md5 as well but that does not work either. I have tried deleting and re-downloading 3 times. I know the file is there 100% and I know I am looking in the right folder 100%.
edit: this is odin 1.87 and I have tried the phone slot with the same results.
edit #2: I am sure someone else will run into this problem someday since two of us have. Apparently this is the only file you will ever unzip. I have it so ground into my head to never unzip anything I didn't think of that
Click to expand...
Click to collapse
Try the updated version of Odin. http://db.tt/OIEtTUxn
Hi all, I’m having some trouble with my SGS2. I’ve searched for the better part of several days and read a lot of threads with similar but slightly different issues and I haven’t seen any definite solutions so I want to ask the experts before I do something stupid. Sorry for the long post but I want to include as many details as I can so no one has to use their crystal ball to figure out what is going on.
The other day my Sprint (really it is through Ting but it is branded as Sprint) SGS2 would not wake up from sleep after charging all night. It was running a GB27 rooted, full restore stock ROM I flashed through Odin (downloaded via rwilco’s very nice site). The flashing was done over a month ago and I didn’t have any troubles until this. Pressing and holding the power button did nothing, so I removed the battery to restart the phone. It was stuck in a boot loop at the “Samsung Galaxy S2” boot screen. Removed the battery for over an hour, tried again, same thing. I can boot into Odin download mode by using power+vol down. I don’t have CWM so I can’t try any other recovery options.
I tried using Odin to reflash the same ROM--GB27, rooted, full restore. This is Odin v1.81 one-click from rwilco’s site. I made sure all Kies processes were killed and started the reflash process and it got stuck trying to write cache.img. I left it for well over an hour and it never progressed past this point. Usually I’d see the blue progress bar on the phone during the flash process but it never appeared. This is the log from odin:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> cache.img
The log stopped here and after an hour, I unplugged the phone. I can still get to odin download mode, but instead of the “Samsung Galaxy SII” boot screen, I just get the “Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.” I gather that a flag is set during the flash process, then is removed once the flash process completes successfully. Tried to flash again many times with different USB cable/port etc, but no luck.
The next step, I read through the FAQ on this forum and decided to try flashing EL29 via odin one-click (downloaded from here: http://www.rwilco12.com/downloads.p...-D710)/Stock ROMs/GB/EL29/Full Restore/Rooted). This used Odin v1.85. I left all options as the default and selected the PDA file but got these messages:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EL29_CL852097_ROOTED_PDA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.bin
<ID:0/003> NAND Write Start!!
However, it never seems to progress from here even after an hour. I never see any blue progress bar. Also tried again using different USB cable and port, but no luck.
My phone isn’t viewable from Kies.
I’m at a loss for what to do next. I’d try to flash more versions, but I don’t know enough about this emmc bug and don’t want to trigger it. Reading around, I see suggestions about repartitioning and flashing PIT files, but this seems risky. I am also looking if there is any danger flashing from jellybean to non-jellybean builds.
I read about flashing just the kernel, modem and ROM separately but which files should I use? I also read about flashing a CWM kernel so I can get into recovery mode but I’m still not certain which files I should be using. I will also admit I don’t know how to flash only a kernel through odin. It looks like you use the PDA box like what I did above, but I thought that was for full ROMs? Do you use the PDA box for both kernels and ROMs?
I did find this thread http://forum.xda-developers.com/showthread.php?t=2289007 which is very similar to my issue, but I’m not sure if I messed something up by trying to reflash the same ROM.
What should I try next?
Sorry for the simple questions but I want to learn! Thanks for the help!
Very interesting. Seems like there is some nastiness going around with jellybean and our phones. The emmc bug was initially ICS, don't know if it carried over, but due to the high number of phones crashing, there must be some form of corruption going on.
Sent from my SPH-D710 using xda premium
noobtoob said:
Very interesting. Seems like there is some nastiness going around with jellybean and our phones. The emmc bug was initially ICS, don't know if it carried over, but due to the high number of phones crashing, there must be some form of corruption going on.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Agreed. The fact that it happens unprovoked is particularly worrisome.
This is the exact type issue I tried moving and helping the other day. I an now at quite a loss. We could have you just try and Odin flash a kernel. Yes, you would just use the PDA button to select your .tar file. Put a ROM in your SD card, and clean/flash this way, but that proved unsuccessful least time as well.
Sent from my SPH-D710 using xda premium
noobtoob said:
This is the exact type issue I tried moving and helping the other day. I an now at quite a loss. We could have you just try and Odin flash a kernel. Yes, you would just use the PDA button to select your .tar file. Put a ROM in your SD card, and clean/flash this way, but that proved unsuccessful least time as well.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Thanks. I did find your post here on a similar thread and it was what made me post this... I wasn't sure if I could salvage it before getting to the point where I couldn't get into odin mode.
So you think flashing EL26 with CWM recovery would be my best option? I'm curious if when I tried to flash EL29 it didn't do anything since the previous flash had stalled... so maybe I avoided the scenario mentioned in your post above. From the log it still looks like it flashed recovery.bin though, so I don't know.
tanminivan said:
Thanks. I did find your post here on a similar thread and it was what made me post this... I wasn't sure if I could salvage it before getting to the point where I couldn't get into odin mode.
So you think flashing EL26 with CWM recovery would be my best option? I'm curious if when I tried to flash EL29 it didn't do anything since the previous flash had stalled... so maybe I avoided the scenario mentioned in your post above. From the log it still looks like it flashed recovery.bin though, so I don't know.
Click to expand...
Click to collapse
Well, at this point I don't know. I see this happening a lot now. I have been flashing exclusively through mobile Odin and roms that I had on my SD card except the other day when I tried the pit and tar files from that post. Seems more and more people are running into bricking all of a sudden a lot right now. I think sprint or Samsung need to get involved and do some phone replacement. I would take a poll and see how many people have bricked using just a stock ROM. It could have something to do with the hardware version of something in your phones. I am not anywhere smart enough to figure that stuff out, I can just offer advice and test things I know (or knew) to be safe ATM.
Sent from my SPH-D710 using xda premium
Are you able to flash a one-click ICS or GB ROM? Specifically FL24. My phone didn't like GB27 either (thankfully no bricking). I was able to flash EL26 with CWM by using the one-click twice. The first flash never seemed to work the first time, even though it said it was successful. Flashed several AOSP ROMs from there without issue.
bigj231 said:
Are you able to flash a one-click ICS or GB ROM? Specifically FL24. My phone didn't like GB27 either (thankfully no bricking). I was able to flash EL26 with CWM by using the one-click twice. The first flash never seemed to work the first time, even though it said it was successful. Flashed several AOSP ROMs from there without issue.
Click to expand...
Click to collapse
Flashing with one-click twice? Wouldn't that be a double-click?
I've tried using Odin non-one-click to flash EL26 w/ CWM but Odin just stalls at "NAND Write Start." But interestingly, it is incrementing the flash counter and "current binary" now reads "custom" where before it read "Samsung Official." So at least it's doing something. Time to search on how to get past these stalled flashes... from this thread it doesn't look particularly promising...
Just to provide an update to anyone who comes across this thread and has the same issue. I tried pretty much everything I could think of. I tried flashing all of the odin one-clicks I could get a hold of (GB/ICS/JB). I tried flashing tars. I tried flashing just kernels (GB/ICS/JB). I tried all kinds of recovery kernels, EL26 CWM etc. Of course I used all different versions of odin, different computers, different cables, different USB ports, etc.
I read the repartitioning thread (well at least quite a bit before people started asking the same questions over and over again). I downloaded the 92 different PIT files for the E4GT and tried flashing all of the different kinds of pit files... ones that moved the system partition, ones that moved data, ones that moved factoryFS, ones that shrank the UMS partition. Of each of those I tried different shift amounts...1GB, 3GB, 8GB, etc. I tried flashing with "repartition" unchecked (not sure what it really would do but it was suggested somewhere so I tried it).
Nothing worked. It'd always stall trying to write to the device. For flashing PIT files odin would start with "SET PARTITION" and just hang for over an hour and never progress. Still very strange that I could get into odin and usually on each attempted flash it would increase the flash counter. And strange as well that I was running rooted stock and this seemed to happen on its own.
The best I can figure is I'm really unlucky and have some bad blocks in memory at just the wrong spot to prevent the flashing process from completing.
Thanks for the update tan. Someone else has this very same issue. Looks like as of now there's no solution. That really sucks.
Sent from my SPH-D710 using xda premium
jdsingle76 said:
Thanks for the update tan. Someone else has this very same issue. Looks like as of now there's no solution. That really sucks.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I woke up this morning with the same issue. My phone was fine when I put it on the charger last night. This morning it was off, when I turned it on just samsung logo boot loop. I could not boot to recovery. I've tried to Odin a new recovery and a once-click full ROM. Odin stalls at recovery.bin either way.
wraith404 said:
I woke up this morning with the same issue. My phone was fine when I put it on the charger last night. This morning it was off, when I turned it on just samsung logo boot loop. I could not boot to recovery. I've tried to Odin a new recovery and a once-click full ROM. Odin stalls at recovery.bin either way.
Click to expand...
Click to collapse
Sorry to hear you have the same issue. You may read up on repartitioning and try that---you might have better luck than I did.
tanminivan said:
Sorry to hear you have the same issue. You may read up on repartitioning and try that---you might have better luck than I did.
Click to expand...
Click to collapse
I couldn't perform any of the standard repartitioning methods because recovery was not accessible (couldn't run the bad sector scan), nor was Odin working with any sort of TAR. I also reviewed the various PIT files, but based on your review of the same 100 odd files I was reviewing and finding that none of them seemed to relocate recovery addresses (we are stalling on recovery not sys or user), I threw in the towel and took it into a local Sprint repair store. The tech confirmed the issue, he was unable to factory flash it at all. His diagnosis was "something is seriously corrupted", but was very nice about it. He didn't even mention my dozen or so flash count showing in odin mode from my recovery attempts. Oh, and I told him flat out that I had tried to recover it via odin. I had the Insurion coverage, (drop/break/wet), not full TEP, but they were still able to order a replacement for $53. If you have TEP it might be a no charge replacement. He also noted aside that hes seen this a couple other times lately, not to read to much into that but it may be that the lemon memory modules Samsung pawned off on this device might be starting to just up and die instead of waiting to be overwritten wrong. I only say that because I haven't flashed a thing in months by Odin or recovery, and when mine died it was (or should have been) sleeping.
Thanks for the posts, they saved me the frustration of further investigating the PIT files, and got me into the repair shop quickly. I have a 5 day wait for the replacement, and my pregnant wife is due any time. I can't afford to be without a phone for long. I could have procrastinated for days without finding this research.
I'm up for upgrade in just like 2 weeks now, and this has me wondering if I should even chance another Samsung product. The HTC One is looking better and better, even though I'm not sure I can part with having an SD card and replaceable battery. Time to start looking around to see if the SG3 and Note2 have had all these EMMC issues. I want the SG4 but not if this is a running problem.
Note 2 doesnt.
Sent from my SPH-L900 using Tapatalk 2
wraith404 said:
Thanks for the posts, they saved me the frustration of further investigating the PIT files, and got me into the repair shop quickly. I have a 5 day wait for the replacement, and my pregnant wife is due any time. I can't afford to be without a phone for long. I could have procrastinated for days without finding this research.
I'm up for upgrade in just like 2 weeks now, and this has me wondering if I should even chance another Samsung product. The HTC One is looking better and better, even though I'm not sure I can part with having an SD card and replaceable battery. Time to start looking around to see if the SG3 and Note2 have had all these EMMC issues. I want the SG4 but not if this is a running problem.
Click to expand...
Click to collapse
Thank you, not a problem. Congrats on your upcoming baby!
Unfortunately I'm with Ting, so not am I only out of warranty and official repair options, but the full $500 unsubsidized cost of the phone as well. I'm optimistic, however. I purchased a Sprint SGS2 with a broken screen on ebay for around $50 and swapped the motherboard. Unfortunately it turns out the ESN had been flashed to another carrier so I'm trying to figure out how to flash it back...
I have the same feelings on whether my next phone will be a Samsung device as well. I guess time will tell how good the S4 is.
Hey guys, I have a Samsung Galaxy S3 for Tmobile SGH T999 and I had cyanogen on it until it crapped out and got hard bricked. AFter following these links, http://forum.xda-developers.com/showthread.php?t=1949687 and http://forum.xda-developers.com/showthread.php?t=2439367, I was able to unbrick my phone and get into boot recovery mode. However, when i try to flash the stock firmware in odin, I get an error (the error is shown in the attachment). Can anyone please help me? Sorry if im posting something wrong, I am new to this forum. Thank you!
After booting into download mode, take out the sdcard before flashing with Odin. Also if kies is on the computer, uninstall it.
DocHoliday77 said:
After booting into download mode, take out the sdcard before flashing with Odin. Also if kies is on the computer, uninstall it.
Click to expand...
Click to collapse
I tried this still doesnt work.
You said there was an error msg, but im not seeing it in the screenshot.
How exactly did you brick it though? Have you tried flashing MJC or NC2 firmware from Odin?
If you are still running MD5 or earlier, you could try flashing TWRP, then boot recovery and flash the recovery firmware package in the development section.
DocHoliday77 said:
You said there was an error msg, but im not seeing it in the screenshot.
How exactly did you brick it though? Have you tried flashing MJC or NC2 firmware from Odin?
If you are still running MD5 or earlier, you could try flashing TWRP, then boot recovery and flash the recovery firmware package in the development section.
Click to expand...
Click to collapse
Sorry i meant failure not error. I bricked it because my cyanogenmod was having problems and i tried to restore it, after i did it completely bricked. Sorry can you please elaborate what is TWRP, MJC or NC2 firmware, im dont have much knowledge about these kind of things. Thank you so much for helping me, it means alot to me and I will do my best to follow your directions.
Ok, ill explain better when I get to my computer. It'll be too much to try to type on this tiny device im using right now!
But for now, TWRP is a custom recovery, like CWM. You use it when flashing roms like CM.
MJC and NC2 are just the different firmware builds you can flash in Odin. We shorthand it by just using the last 3 letters of the build version. T999UVUENC2 is what im referring to when I say NC2.
Take a look at my firmware thread. Its stickied at the top of development. Linked in my sig too.
Let me know if this helps your understanding at all. Ill explain more in what to do shortly.
Thanks for that, it gave me a better understanding. I tried to install flash and this happens when i try to flash twrp or MJC on odin
Ahhh! PIT=Partition Information Table
Odin uses this to know the partition layout of the device so it knows where to flash each part of the firmware. It usually gets this directly from the device, but occasionally it becomes corrupted or lost.
There is a thread in the General section that has all our PIT files. Should be on the first page right now, maybe second. Download the correct one for your device. (My last post has a link to my repo with all PIT files)
Now try flashing your firmware again, do everything the same way, but this time check the repartition checkbox, and click the PIT button and select the .pit file you just downloaded. Now click start and it should work. We hope....!
DocHoliday77 said:
Ahhh! PIT=Partition Information Table
Odin uses this to know the partition layout of the device so it knows where to flash each part of the firmware. It usually gets this directly from the device, but occasionally it becomes corrupted or lost.
There is a thread in the General section that has all our PIT files. Should be on the first page right now, maybe second. Download the correct one for your device. (My last post has a link to my repo with all PIT files)
Now try flashing your firmware again, do everything the same way, but this time check the repartition checkbox, and click the PIT button and select the .pit file you just downloaded. Now click start and it should work. We hope....!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1848267 are you talking about this page for the PIT file? because when i clicked this link it doesnt work and it pops up as an unsafe page on my myWOT.
Ok so i found a PIT file for my phone and when i tried to flash with the odin v3.07 it got stuck on Leave CS. I looked up a solution for this and it was to use an older version of odin, v1.85. After i tried this I made more progress but it failed again.
ojhasha said:
http://forum.xda-developers.com/showthread.php?t=1848267 are you talking about this page for the PIT file? because when i clicked this link it doesnt work and it pops up as an unsafe page on my myWOT.
Click to expand...
Click to collapse
Yes that's the thread. Which did it say was unsafe? The thread itself, or my link in the post in that thread?
If its my link, it just goes to my folder on http://androidfilehost.com. its a file sharing site solely for android stuff from sites like xda. Its perfectly safe. If that's the one being flagged its probably because it has files you can download m
ojhasha said:
Ok so i found a PIT file for my phone and when i tried to flash with the odin v3.07 it got stuck on Leave CS. I looked up a solution for this and it was to use an older version of odin, v1.85. After i tried this I made more progress but it failed again.
Click to expand...
Click to collapse
Where did you get the pit? May be that its either a corrupt download or for the wrong device.
And did you try with Odin 3.09?
DocHoliday77 said:
Yes that's the thread. Which did it say was unsafe? The thread itself, or my link in the post in that thread?
If its my link, it just goes to my folder on http://androidfilehost.com. its a file sharing site solely for android stuff from sites like xda. Its perfectly safe. If that's the one being flagged its probably because it has files you can download m
Where did you get the pit? May be that its either a corrupt download or for the wrong device.
And did you try with Odin 3.09?
Click to expand...
Click to collapse
It was invisibleK's link that was unsafe. I used your 16GB Pit file in here, http://www.androidfilehost.com/?w=files&flid=6471 and i got the same result. I dont remember where i got the other pit. I got stuck on Leave CS on the odin 3.09 and when i click start it failed again with the repartition failed.
You are still removing the sdcard before flashing, right?
I have no idea if this could help, but theres a program here on xda called PIT magic. Maybe take a look in that thread to see if you find anything useful.
You can try flashing the PIT only, no firmware selected, but I dont know if this would work or not.
Only other thing I can think of is to try everything over again with the NC2 firmware.
Try that first, but you can also try flashing cwm or TWRP with odin. If we can get recovery on there we might be able to try other stuff with that.
DocHoliday77 said:
You are still removing the sdcard before flashing, right?
I have no idea if this could help, but theres a program here on xda called PIT magic. Maybe take a look in that thread to see if you find anything useful.
You can try flashing the PIT only, no firmware selected, but I dont know if this would work or not.
Only other thing I can think of is to try everything over again with the NC2 firmware.
Try that first, but you can also try flashing cwm or TWRP with odin. If we can get recovery on there we might be able to try other stuff with that.
Click to expand...
Click to collapse
sorry i didnt respond in a while, I was really busy with homework. I tried what you said and still no sign of success. I brought my phone to a repair shop and they said the motherboard is damaged and it needs to be replaced for 150$. I hope this guy is just bull****ting me, can anyone confirm? I really hope there is still light at the end of the tunnel right now.
Its hard to say. Motherboards do go bad, usually an issue with the memory. Its pretty rare, but it does happen, and the frequency has been increasing since these devices are starting to get a little old now.
But $150 for a replacement is, imo, a rip off. You can find used boards on ebay for under $100. If you csn use a screwdriver and can be gentle with the ribbon cables, its a super easy swap. Just check the videos to see.
DocHoliday77 said:
Its hard to say. Motherboards do go bad, usually an issue with the memory. Its pretty rare, but it does happen, and the frequency has been increasing since these devices are starting to get a little old now.
But $150 for a replacement is, imo, a rip off. You can find used boards on ebay for under $100. If you csn use a screwdriver and can be gentle with the ribbon cables, its a super easy swap. Just check the videos to see.
Click to expand...
Click to collapse
do you recommend me doing it? or are there more alternatives.
If the memory itself has gone bad, that's your best option. It is possible to change just the memory chip, but the part is probably hard to find and it requires a higher level of soldering skills.
There's a video of this, if I can find it again ill post the link.
Here's the video to the emmc replacement for international S3, should be similar but will require BGA soldering skills. https://www.youtube.com/watch?v=rOYo9AcUQQI
I thought about attempting to do this for my T999v, but a EMMC chip is about 35-50 bucks.
yellowonion said:
Here's the video to the emmc replacement for international S3, should be similar but will require BGA soldering skills. https://www.youtube.com/watch?v=rOYo9AcUQQI
I thought about attempting to do this for my T999v, but a EMMC chip is about 35-50 bucks.
Click to expand...
Click to collapse
did you have my symptoms? did you ever fix your phone? if so please share, i want to get my phone back in the cheapest way possible.
PS. I charged my phone today and the red led light showed up, that means my motherboard isnt broken right?
Not necessarily. It means there is a problem and requires special drivers and programs to fix, (or the debrick sd card). It basically just means the computer sees something is plugged in. If the memory has gone bad it could very well still give the red led and/or boot from the sd.
The only good way to verify the board (or memory) needs replacing would be to go to a second shop and ask them to attempt a jtag repair. If they tell you the same thing as the first shop, ask if they can be more specific about what happened when they attempted the jtag repair. At this point though, its a pretty good guess that the memory has gone bad.
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.
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.