i tried to restore my device to stock rom
downloaded N7100XXDLJ2_N7100OXADLJ2_OXA rom
went to download mode
started odin
got the tar file at pda
started to restore then stuck at this point
sboot.bin
then odin fails
here is the log
"
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDLJ2.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> cache.img
<ID:0/007> hidden.img
<ID:0/007> modem.bin
<ID:0/007> param.bin
<ID:0/007> recovery.img
<ID:0/007> sboot.bin
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
"
Samsung have black listed older bootloader (like 2012 released)
you can't flash that ROM (also not safe security wise) and chances are there some of also don't have SDS patched.
select some newer ROM
I don't recommend but if it is must to flash that ROM, use mobile odin (that won't flash bootloader)
i tried another new rom .. N7100XXDMC3_N7100OJVDMC1_EGY downloaded from Sammobile
and the same error
when it gets to sboot.bin i get fail and stop flashing
and the device stops at samsung logo and can't go in to use mobile odin too
is there any another way to solve this issue !!
Use pit file
First flash pit only
Then pit + rom
Sent from my GT-N7100 using xda premium
when i flash pit file the re-partition option got ticked .. do i un-tick it or leave it ticked ???
Yes you have to keep it selected (ticked)
Sent from my GT-N7100 using xda premium
still the same problem ... is there any way to bypass flashing sboot.bin ??
just thinking ... is there any way to erase any thing and every thing on the phone and start from the beginning .. flashing a boot loader then recovery then the room .. just thinking ... i guess it's a newbie question but had to try !!
What are the different potential reasons for Odin failing at the “sboot.bin” line? I’m flashing my Note 2 (GT-N7100) with the stock firmware (well, the one that had been listed at the top of the Recovery screen) using a brand-new Samsung-branded USB cable in Odin v3.09 and v3.11 and tried in each of my laptop’s four USB ports in turn, with nothing else connected to my laptop (not even a mouse) and no USB hub. I also tried using my brother’s laptop. I’ve included the full Odin log at the foot of my message as it’s different from the OP’s, going straight to sboot.bin and not reaching the other parts.
Only thing is prior to this I accidentally flashed a few incorrect stock ROMs before I found the right one listed in the Recovery screen. On each of these first four attempts with different ROMs I had received different failures in Odin, such as “system.img” and “boot.img” for two of them, and “sboot.bin” for the other two. None of them completed so I figured they can't have caused any damage but I'm certainly no expert.
Might flashing some incorrect stock ROMs have rendered it impossible to flash it with the right one once I found it, and cause it to fail at sboot.bin? Even if none of them completed?
My phone had been (and is) suffering the typical symptoms of being stuck on the boot screen, “E:failed to mount…” etc. message scroll in the Recovery screen, similar errors when wiping cache or doing factory reset while still in the Recovery screen etc. It meanwhile won't connect to Kies. When I try in Smart Switch it says it’s an unsupported device.
I'm a newbie who's learning the ropes Any help would be much appreciated!
<ID:0/023> 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/023> Odin engine v(ID:3.1101)..
<ID:0/023> File analysis..
<ID:0/023> SetupConnection..
<ID:0/023> Initialzation..
<ID:0/023> Get PIT for mapping..
<ID:0/023> Firmware update start..
<ID:0/023> SingleDownload.
<ID:0/023> sboot.bin
<ID:0/023> NAND Write Start!!
<ID:0/023> FAIL!
<ID:0/023>
<ID:0/023> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Sboot.bin is failing because the ROM is not for your phone, the bootloader in the phone is newer than the bootloader in the ROM, you need to use the original Samsung USB cable, or a different USB 2.0 port.
Hi audit13,
Thanks for your reply, I appreciate it
Can I presume that the ROM is correct if it appears listed at the top of the Recovery screen? There’s a small chance I might have tried flashing that ROM in the first few attempts before realising you could check correct ROM there but then none of my flashing attempts with this or other ROMs ever completed so I guess it must have been listed there all along.
And if it is the correct ROM would it therefore be the right bootloader within it?
It's the most recent ROM for O2 network phones in the UK that I could find on SamMobile (PDA: N7100XXUFNJ1; CSC: N7100O2UFNJ1). The phone was locked to O2 when I bought it second hand so I paid for it to be unlocked and it ran fine for over a year with a different network. Because it was unlocked those first few attempts had been with the newest ROMs for unlocked UK phones I could find on SamMobile but none of them worked in Odin. Back when the phone was still working fine it continued to show the O2 splash screen after the boot screen after being unlocked.
First thing to do is boot the phone into download mode and confirm the model number. If the phone model matches the ROM, try different USB cables and ports.
Hi audit13,
Thanks again
The Download screen confirms it's a GT-N7100. The values on the subsequent lines are "Samsung Official", "Official", "0" and "A2".
Each of my laptop's USB ports are 2.0. I've tried flashing using the original cable of another GT-N7100 (my first Note 2 which I got new on a contract and clumsily managed to smash early in its life) when connected to each of the four ports and then same again with a brand new genuine Samsung USB cable.
The original cable was frayed at the end where it meets the connector. Meanwhile the new Samsung cable has a slightly different micro connector on the front side with the USB symbol (as per attached photo, which is old cable on left/bottom and new cable on right/top). The seller I bought from had and still has a photo of the old style connector but I guess if I ordered another I would get the new style again since that is what they sent out last time, and probably other sellers too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before I chance ordering another cable is there any chance it could be the wrong ROM after all or a problem with the bootloader?
Since the phone was locked and subsequently unlocked, the latest firmware for the original carrier should work.
Do you see anything in download mode about "warranty bit"?
As a test of the internal memory, I suggest flashing the tar version of TWRP via Odin: https://dl.twrp.me/t03g/
Boot into TWRP and flash a CM ROM for the gt-n7100: https://download.cyanogenmod.org/?device=n7100
If the phone boots CM, you'll know that the internal memory chip is probably okay and something else is going wrong when flashing a stock ROM.
NOTE: flashing TWRP will trip the knox/warranty bit counter to 1 from 0 which voids the manufacturer's warranty.
Hi audit13,
Thanks very much for that.
Yes, currently have "KNOX WARRANTY VOID: 0" in Download screen.
I've been away from my own laptop tonight so will try this tomorrow and report back. Really like the idea of testing the memory to rule this in or out.
Hi audit13,
I downloaded the “twrp-3.0.1-0-t03g.img.tar” from the link, attached it under AP but got the following log with failure. I tried this in each USB port in Odin 3.11 and Odin 3.09.
<ID:0/023> Added!!
<ID:0/023> Odin engine v(ID:3.1101)..
<ID:0/023> File analysis..
<ID:0/023> SetupConnection..
<ID:0/023> Initialzation..
<ID:0/023> Get PIT for mapping..
<ID:0/023> Firmware update start..
<ID:0/023> SingleDownload.
<ID:0/023> recovery.img
<ID:0/023> NAND Write Start!!
<ID:0/023> FAIL!
<ID:0/023>
<ID:0/023> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Does that look like the memory is faulty then?
(I also tried the same with the “twrp-3.0.0-0-t03g.img.tar.md5” and the “twrp-3.0.2-0-t03g.img.tar.md5” on the offchance but Odin instead hug on Not Responding for 20+ minutes after selecting it under AP before I disconnected and pulled battery. I presume that’s because .md5 file extensions are for ROMs and .tar extensions are for CMs?)
The extension can be tar or tar.md5 when flashing in Odin.
Try Odin 3.07. If that doesn't work, it's possible that the memory chip is damaged or needs to be force flashed via jtag or a repair box.
Hi audit13,
Thanks so much for all your help
I’ve tried in Odin 3.07 and the same failures occurred.
I’ve looked into the JTAG method and think I’ll probably pass on that for this time but thanks for pointing it out. I can see potentially huge benefit of it for a pricey nearly new phone which is bricked whereas as it happens I have an option of donating its screen to my first Note 2 with broken digitizer. I’m glad to have given it a good shot at flashing it, and expanded my knowledge with your help.
Just out of interest, and because I’d like to ensure I don’t get another soft brick… The phone ran flawlessly for 12 months. It might be coincidence but shortly before the phone started going wrong I was staying at a hotel and needed to use the Wifi. I could only connect by ticking ‘Unknown Sources’ in my Settings under Security but forgot to untick it for about a week. About another week after that the phone suffered a slow decline of worsening problems. I started getting various errors, increasing in severity. At different times I had the following:
- downloaded iPlayer programmes disappeared
- occasional “Android is Upgrading” message when booting
- crashing and auto-resetting
- "Unfortunately [various apps] has stopped" message at random points when not even using whatever app it mentioned
- "Unfortunately Touchwiz Home has stopped" message whenever pressing Home, Back or Menu buttons)
- At times could only use touchscreen operations such as pull down notifications bar, open settings etc. but no use of Home, Back or Menu buttons
At various points in its decline I did factory resets in Settings but then the next problem would come along. I put it into Recovery mode and tried wiping cache partition and factory reset there as well but still no success. Then one day it lost its ability to boot.
That said you do see a few folk on forums with Note 2/3/4 etc whose phone suddenly stopped working, and no doubt other models (I’m a Note fanboy), with seemingly no indications of problems prior to that. Anyway, I’m probably digressing into another thread now.
Thanks again
Yes, I would agree that the phone is considered very "old" in the Android world. You cheapest fix may be to find a used Note 2 with a working motheboard and smashed screen. Swapping motherboards is very simple.
Ridil said:
still the same problem ... is there any way to bypass flashing sboot.bin ??
Click to expand...
Click to collapse
Unzip the rom, reselect all the .img and .bin files except zboot.bin and the bootloader file, rezip as tar and flash in odin
Related
I gave my sister a S2 for her account. rooted Jellybean installed. its been fine for the last 6 months or so.
now its stuck at the 4G logo screen or constantly reboots itself back to the 4G screen.
I tried holding vol up and power to "wipe" the device but it errors displaying this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Suggestions?
I THINK she may have tried to install some sort of update accidentally (something I specifically told her not to do) she says it said something about some update and then rebooted and swears she did not install one.
so I really have no clue what actually happened.
suggestions? what can I do to recover this bugger.?
I was able to get into download mode. so I want to odin in a rom.
WHAT do I odin in? I HAD jellybean installed but I have NO CLUE what "SHE" may have installed.
what is "safe" to odin over? step by step would be nice I have done quite a bit of flashing but always by "directions" never "on the fly" on my own
I AM NOT certain but I THINK this is what I had installed
http://forum.xda-developers.com/showthread.php?t=2191954
and is what I am downloading now.
suggestions? does this seem like the right procedure?
nerys71 said:
I gave my sister a S2 for her account. rooted Jellybean installed. its been fine for the last 6 months or so.
now its stuck at the 4G logo screen or constantly reboots itself back to the 4G screen.
I tried holding vol up and power to "wipe" the device but it errors displaying this
Suggestions?
I THINK she may have tried to install some sort of update accidentally (something I specifically told her not to do) she says it said something about some update and then rebooted and swears she did not install one.
so I really have no clue what actually happened.
suggestions? what can I do to recover this bugger.?
I was able to get into download mode. so I want to odin in a rom.
WHAT do I odin in? I HAD jellybean installed but I have NO CLUE what "SHE" may have installed.
what is "safe" to odin over? step by step would be nice I have done quite a bit of flashing but always by "directions" never "on the fly" on my own
I AM NOT certain but I THINK this is what I had installed
http://forum.xda-developers.com/showthread.php?t=2191954
and is what I am downloading now.
suggestions? does this seem like the right procedure?
Click to expand...
Click to collapse
That screenshot is due to her having stock android recovery, not custom recovery. The link you sent is good to Odin. Dave the tar to your computer, put computer in download mode, flash tar. Good luck...btw, you said s2, make sure it's epic 4g touch before you flash that sucker(sph-d710).
Sent from my SPH-D710BST using xda premium
Yes the SPRINT epic 4g touch D710.
so is that what happened? she installed some sort of update that whacked the recovery as well?
my concern was I know you have to do something "different" when going between ginger and jelly. my fear is she installed some ginger update?? (I have no idea what the "stock" firmware for this is
connection is slow right now downloading the 500mb file. Grrrr
anyway to flat out DISABLE updates ?
nerys71 said:
Yes the SPRINT epic 4g touch D710.
so is that what happened? she installed some sort of update that whacked the recovery as well?
my concern was I know you have to do something "different" when going between ginger and jelly. my fear is she installed some ginger update?? (I have no idea what the "stock" firmware for this is
connection is slow right now downloading the 500mb file. Grrrr
anyway to flat out DISABLE updates ?
Click to expand...
Click to collapse
Lol....I believe there is. I know there was for ICS. It was a zip called otakill I believe. Flashing that stock rom should be fine. And if she had custom recovery before, and ran an update, it flashed over the custom, that's what I would think . You have to partition between gb and jb custom roms, but that rom you are flashing should be fine. If you run into issues, let me know. Good luck.
Sent from my SPH-D710BST using xda premium
ok got the file downloaded. phone in download mode. open one click. plug in usb cable. got yellow box 0:[COM25]
click start and I get this and it just stops
<ID:0/025> 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/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> boot.bin
<ID:0/025> cache.img
I know its a big file but even if we assume usb 1.0 speeds it should be done by now. how do I know if its working or not? how long should it take?
You are flashing an entire jb stock ROM..it takes a little bit. I would give it awhile. And the last time I flashed a one click it didn't take the first time. If it doesn't take after a considerable amount of time, say 10 minutes, download the tar again, and try the new download. Sometimes you get a bad download, but pc Odin a Rom takes a bit, be patient
Sent from my SPH-D710BST using xda premium
its been sitting their since 0835 that is 40 minutes. Can't redownload right now will have to try later. I downloaded the self extracting which should alleviate "bad download" concerns since it should fail to extract if its a bad download.
will redownload later and see what happens.
nerys71 said:
its been sitting their since 0835 that is 40 minutes. Can't redownload right now will have to try later. I downloaded the self extracting which should alleviate "bad download" concerns since it should fail to extract if its a bad download.
will redownload later and see what happens.
Click to expand...
Click to collapse
Hmmm...that's odd. Maybe you need to start from scratch, stock unrooted, before you try to flash rooted. If it doesn't take next time, that's what I'd do. I know you're doing this anyway(hopefully), but make sure you read all of the OPs, watch the recommended videos, etc. Good luck man.
Sent from my SPH-D710BST using xda premium
no joy. downloaded the bone stock tar md5 file
odin 3 under pda
same thing. stops at cache.img
<ID:0/025> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710_GB27_1014481_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> boot.bin
<ID:0/025> NAND Write Start!!
<ID:0/025> cache.img
what do I do?
Try flashing a one click instead of a tar. And if that hangs up, try flashing just a custom recovery. If that takes, you can get into cwm and flash a zip version of the rom.
Sent from my SPH-D710 using xda premium
I was running jelly bean. what is the correct recovery to odin?
I already tried flashing a bone stock tar via odin (after trying the one click) same result. stalls at cache.img
uhhh these 500mb downloads are killing me hehe
which specific zip do you suggest? and which recovery tar ?
nerys71 said:
I was running jelly bean. what is the correct recovery to odin?
I already tried flashing a bone stock tar via odin (after trying the one click) same result. stalls at cache.img
uhhh these 500mb downloads are killing me hehe
which specific zip do you suggest? and which recovery tar ?
Click to expand...
Click to collapse
Dl a stock jb zip, gb27 will work. If it flashes in recovery, you won't have cwm, but that's ok, we'll cross that bridge when we get to it. And use stock el26 cwm tar by chris41g. If it flashes in Odin, it may reboot to Samsung logo, that's ok, just reboot to recovery.
Sent from my SPH-D710 using xda premium
ok I am grabbing this rom now
http://forum.xda-developers.com/showthread.php?t=2224230 (3 hours to download)
and using this CWM
http://forum.xda-developers.com/showthread.php?p=24987585
grabbing the GB08 modem from here
http://forum.xda-developers.com/showthread.php?t=1764210
and the agate63 source kernel from here
http://forum.xda-developers.com/showthread.php?t=1662295
I just tried to odin the StockCWM-EL26.tar.md5
stops at
<ID:0/017> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> StockCWM-EL26.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> zImage
<ID:0/017> NAND Write Start!!
Grrrrr now what ?
I tried re booting to recovery anyway thinking maybe it worked. no joy
says Firmware upgrade encountered an issue please select recovery mode in kies & try again
when I try to boot into recovery.
You're still able to get into download mode correct?
If you can get to download mode do the following:
Uninstall kies and Samsung drivers,Download ODIN 1.85 from here and install it (the newer versions have been known to fail flashes on occasion), plug your usb cable into pc not the phone, open ODIN and navigate to PDA (like you did before) and open, choose the GB27 tar file. Make sure that repartition is NOT checked, now connect your phone and wait for the com light to come on, once it lights up press start.
Now the reason I suggest this yet again is because you're trying to flash from ODIN v3+, Kies and Odin are known to conflict sometimes, and the repartition box will always cause issues without a pit file (these are dangerous to play with if you're not familiar with them)
It's unusual, but not unheard of, for a one click would fail. If all else fails, and this doesn't work for you, please post the exact model number under the battery of your device, so that we can determine if there are any discrepancies.
ok got 1.85 from your link. I do not have kies installed. I uninstalled the samsung drivers but now windows sits at install drivers and odin never see's the phone (of course I just removed the drivers that LET it see the phone ???) what was supposed to happen?
ahh interesting. unplugged it and plugged it in again and this time odin saw the phone (I guess it installed some sort of driver ??)
but no joy. same result.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> E4GT-EL29-directbootCWM-v3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
stops here.
Model number SPH-D710
Sprint Epic 4g Touch (S2)
nerys71 said:
ok got 1.85 from your link. I do not have kies installed. I uninstalled the samsung drivers but now windows sits at install drivers and odin never see's the phone (of course I just removed the drivers that LET it see the phone ???) what was supposed to happen?
ahh interesting. unplugged it and plugged it in again and this time odin saw the phone (I guess it installed some sort of driver ??)
but no joy. same result.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> E4GT-EL29-directbootCWM-v3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
stops here.
Model number SPH-D710
Sprint Epic 4g Touch (S2)
Click to expand...
Click to collapse
OK, do you happen to have another cable to try? Or perhaps another usb port on your pc?
Slithering from the nether regions of a twisted mind and tarnished soul
so far I have tried 4 pc's and 3 USB cables. never a change in results. 3 running xp 1 running windows 7
2 of these pc's have flashed this very phone in the past.
1 cable is my orange cable and the other 2 are stock samsung cable both good quality cables.
I can look for more cables but that does not seem to be the issue here.
dug up a 4th cable. no joy. no change.
nerys71 said:
so far I have tried 4 pc's and 3 USB cables. never a change in results. 3 running xp 1 running windows 7
2 of these pc's have flashed this very phone in the past.
1 cable is my orange cable and the other 2 are stock samsung cable both good quality cables.
I can look for more cables but that does not seem to be the issue here.
dug up a 4th cable. no joy. no change.
Click to expand...
Click to collapse
Man, what got flashed? LOL
OK, you're able to get to Odin mode, the PC recognized your device, but install fails as soon as it begins to write the images...
4 cables one of them should have worked if that was the issue, and several different pc's...
Reinstalling drivers didn't do anything...
Different version of Odin...
I assume you've verified md5?
Have you tried other downloads, or the same file?
Maybe try flashing say, FL24 with Odin, then the GB27. If FL24 flashes then you know its the GB27 thats failing. Where are you grabbing your download from?
Slithering from the nether regions of a twisted mind and tarnished soul
I posted the links in the other thread. I got them from here on xda forums threads.
I have tried a tar a one click a cwm and a direct boot cwm. md5 validated.
I will try an older kernel and see what happens.
nerys71 said:
I posted the links in the other thread. I got them from here on xda forums threads.
I have tried a tar a one click a cwm and a direct boot cwm. md5 validated.
I will try an older kernel and see what happens.
Click to expand...
Click to collapse
Try this link http://www.sxtpdevelopers.com/showthread.php?t=166 download that tar and try flashing it
Hey guys. After searching this and other forums and reading many threads I decided the best option would be for me to start my own for my personal situation. Here's the back story.
I put in a fully charged battery that I've used successfully for a few months. Phone appeared to successfully boot up then rebooted itself. Made it to swirling blue before rebooting again. This time, and every time after, it freezes at the Samsung Galaxy SIII screen. Phone won't go into recovery mode but will enter download mode.
I was running rooted ATT stock rom (not sure what version but I haven't done the last 2 OTA's for sure). Phone had been rooted for at least 6 months with no issues. No new apps or anything had been done to the phone recently. TWRP is on the phone however when trying to enter it it freezes on the Team Win screen and never fully enters recovery.
When trying go back to stock rom using Odin I get this message:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
. I'm using the firmware found here . I747UCALG1.
My phone also has a bad pin connection in the usb port (hence why I was changing out batteries)
It forms a connection but at times doesn't stay connected or any little manipulation could throw it off. I do know however that it's not losing connection with the computer when I get the failed message in Odin.
Any help or ideas? As of now I'm rocking a go phone but would rather get my S3 back.
Thanks
ETA: Top left corner in Download mode reads:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (2 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOM SECUREBOOT: ENABLED
I believe aboot.mbn is a the bootloader file. Does your phone have a 4.3 bootloader?
bbrou33 said:
Hey guys. After searching this and other forums and reading many threads I decided the best option would be for me to start my own for my personal situation. Here's the back story.
I put in a fully charged battery that I've used successfully for a few months. Phone appeared to successfully boot up then rebooted itself. Made it to swirling blue before rebooting again. This time, and every time after, it freezes at the Samsung Galaxy SIII screen. Phone won't go into recovery mode but will enter download mode.
I was running rooted ATT stock rom (not sure what version but I haven't done the last 2 OTA's for sure). Phone had been rooted for at least 6 months with no issues. No new apps or anything had been done to the phone recently. TWRP is on the phone however when trying to enter it it freezes on the Team Win screen and never fully enters recovery.
When trying go back to stock rom using Odin I get this message:
<ID:0/009> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCALG1_I747ATTALG1_I747UCALG1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> aboot.mbn
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
. I'm using the firmware found here . I747UCALG1.
My phone also has a bad pin connection in the usb port (hence why I was changing out batteries)
It forms a connection but at times doesn't stay connected or any little manipulation could throw it off. I do know however that it's not losing connection with the computer when I get the failed message in Odin.
Any help or ideas? As of now I'm rocking a go phone but would rather get my S3 back.
Thanks
ETA: Top left corner in Download mode reads:
ODIN MODE
PRODUCT NAME: SGH-I747
CUSTOM BINARY DOWNLOAD: YES (2 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
QUALCOM SECUREBOOT: ENABLED
Click to expand...
Click to collapse
Maybe it is the pin that's causing the problem or try flashing in Odin the DKL3 firmware in Odin
audit13 said:
I believe aboot.mbn is a the bootloader file. Does your phone have a 4.3 bootloader?
Click to expand...
Click to collapse
It shouldn't. I haven't done an OTA update since 4.1 I believe. The last 2 updates (most recent and October) I didn't do because my phone was rooted and didn't feel like dealing with it. So firmware hasn't been updated. However back in October, my phone automatically downloaded the OTA update and I accidentally installed it. In face I believe it did it again recently. Which after the installation, the phone wouldn't boot up because I was running the rooted firmware. I simply used TRWP to recover everything. As far as I know, phone firmware was never updated because I kept root, but I could very well be wrong.
britt21 said:
Maybe it is the pin that's causing the problem or try flashing in Odin the DKL3 firmware in Odin
Click to expand...
Click to collapse
The only ATT DKL3 firmware that I can find is in this thread. WinRar was failing to unpack the .7z file every time I tried. But I'll try again later when I get home
bbrou33 said:
It shouldn't. I haven't done an OTA update since 4.1 I believe. The last 2 updates (most recent and October) I didn't do because my phone was rooted and didn't feel like dealing with it. So firmware hasn't been updated. However back in October, my phone automatically downloaded the OTA update and I accidentally installed it. In face I believe it did it again recently. Which after the installation, the phone wouldn't boot up because I was running the rooted firmware. I simply used TRWP to recover everything. As far as I know, phone firmware was never updated because I kept root, but I could very well be wrong.
Click to expand...
Click to collapse
You can try different stock firmware from sammobile if you are sure you do not have the 4.3 bootloader.
Moderators, please delete my thread in Samsung Galaxy S III I9300, I9305
My phone: SPH-L710 Sprint Galaxy S3
This is what my ODIN says after trying to flash with stock ROM.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME.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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
This is what is on the top left corner in the DL mode.
"ODIN MODE
PRODUCT NAME: SPH-L710.
CUSTOM BINARY:Custom
SYSTEM STATUS:Custom
QUALCOM SECUREBOOT: ENABLE
Warranty Bit: 1
Bootloader AP SWAEV: 2
SW REV CHECK FAIL : Fused 2 > Binary 1"
Here's my story:
My phone was displaying "No error" in Google Play Store. So I factory reset my phone but it didn't resolve my problem. So I flashed a stock ROM and it failed. My device was 4.4.2 ROOTED before flashing a lower version. (Cannot remember the version number though.) Now it displays, "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." My phone, however, DOES go into Download mode but not the recovery mode. I tried to flash multiple times but ODIN kept on failing. I tried multiple USB cables, different USB ports, computers, and reinstalled USB drivers, etc. However ODIN keeps on failing. I tried to recover it through KIES but it will not detect my device. I am thinking about sending this into Mobiletechvideos.com but I heard some devices could not be restored because of EMMC failure. Do you think my device's emmc failed? (I spent 200 bucks on this and do not wanna buy another one )
Soooo..
Is there anything I can do before I send it into mobiletechvideos.com for 50 bucks?
I've tried this http://forum.xda-developers.com/show....php?t=1840030 but it didn't work because I couldn't find Sprint bootchain. Does anyone have one for Sprint?
I'm also trying to use this method http://forum.xda-developers.com/show....php?t=2369125 but do you think it will work? (I don't have a SD card so I can't try just yet.) It was meant for hardbricked people. But mine is not completely bricked. It turns on and goes into DL mode.
** I've just noticed some signs of hardbrick. WITHOUT my battery and I hook my phone up to my PC with a USB cable, it shows that Red LED light and vibrates. Doesn't turn on though. WITH the battery, it turns on and goes into DL mode. Is my phone hard bricked?**
SUMMARIZED QUESTIONS:
1) Is my phone hard bricked?
2) Do you think JTAG can fix my phone? My phone may be in Read only state. Wouldn't that prevent the JTAG method?
3) Will the SD card method work?
4) Does anyone have Sprint bootchain? (I think my phone might be at Read Only state)
5) What are some signs of EMMC failure? I would really hate it if my phone had EMMC failure -_-
6) Did my phone brick because my phone was rooted and I flashed unrooted Sprint Stock ROM?
PLEASE PLEASE help me. Donations will be considered! (Really, I'm desperate to get my phone fixed. T_T )
Thank you alot in advance. Please leave replies if you need more information.
sdw8253 said:
Moderators, please delete my thread in Samsung Galaxy S III I9300, I9305
My phone: SPH-L710 Sprint Galaxy S3
This is what my ODIN says after trying to flash with stock ROM.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME.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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
This is what is on the top left corner in the DL mode.
"ODIN MODE
PRODUCT NAME: SPH-L710.
CUSTOM BINARY:Custom
SYSTEM STATUS:Custom
QUALCOM SECUREBOOT: ENABLE
Warranty Bit: 1
Bootloader AP SWAEV: 2
SW REV CHECK FAIL : Fused 2 > Binary 1"
Here's my story:
My phone was displaying "No error" in Google Play Store. So I factory reset my phone but it didn't resolve my problem. So I flashed a stock ROM and it failed. My device was 4.4.2 ROOTED before flashing a lower version. (Cannot remember the version number though.) Now it displays, "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." My phone, however, DOES go into Download mode but not the recovery mode. I tried to flash multiple times but ODIN kept on failing. I tried multiple USB cables, different USB ports, computers, and reinstalled USB drivers, etc. However ODIN keeps on failing. I tried to recover it through KIES but it will not detect my device. I am thinking about sending this into Mobiletechvideos.com but I heard some devices could not be restored because of EMMC failure. Do you think my device's emmc failed? (I spent 200 bucks on this and do not wanna buy another one )
Soooo..
Is there anything I can do before I send it into mobiletechvideos.com for 50 bucks?
I've tried this http://forum.xda-developers.com/show....php?t=1840030 but it didn't work because I couldn't find Sprint bootchain. Does anyone have one for Sprint?
I'm also trying to use this method http://forum.xda-developers.com/show....php?t=2369125 but do you think it will work? (I don't have a SD card so I can't try just yet.) It was meant for hardbricked people. But mine is not completely bricked. It turns on and goes into DL mode.
** I've just noticed some signs of hardbrick. WITHOUT my battery and I hook my phone up to my PC with a USB cable, it shows that Red LED light and vibrates. Doesn't turn on though. WITH the battery, it turns on and goes into DL mode. Is my phone hard bricked?**
SUMMARIZED QUESTIONS:
1) Is my phone hard bricked?
2) Do you think JTAG can fix my phone? My phone may be in Read only state. Wouldn't that prevent the JTAG method?
3) Will the SD card method work?
4) Does anyone have Sprint bootchain? (I think my phone might be at Read Only state)
5) What are some signs of EMMC failure? I would really hate it if my phone had EMMC failure -_-
6) Did my phone brick because my phone was rooted and I flashed unrooted Sprint Stock ROM?
PLEASE PLEASE help me. Donations will be considered! (Really, I'm desperate to get my phone fixed. T_T )
Thank you alot in advance. Please leave replies if you need more information.
Click to expand...
Click to collapse
First thing, most of the time we moderators don't have time to go through every thread and post on XDA. Rather than asking us to delete a post in an obscure thread we may not see it would be helpful to us if you report it. I'm mobile right now so I can't do it but please report the other thread and make your request in the report.
Second, Odin isn't working because you're on a new bootloader. This one-click comes with the newest. Try flashing it. http://forum.xda-developers.com/showthread.php?t=2755793
Good luck!
If you were on KitKat 4.4.2 nd8 and tried to Odin the mk3 stock tar you've probably bricked your phone. Once on the nd8 boot loader and modem you cannot revert to an older version.
Many devs have bricked there phone with the new nd8 build.
I know I haven't answered all your w
Questions but I hope I've helped you understand what happened.
Luckily for you @rwilco12 has a solution for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FIXED!
I've been searching everywhere for a solution. Stupid Samsung and their Knox and their Kies (which fixes nothing)
I finally got it sorted!
1. Pull out the battery.
2. Reinsert the battery and force the phone into Download Mode. (Yes, I'm aware that the phone is unable to go anywhere else at this point; but when I fixed mine, I did it manually so that it displayed the Android droid logo, rather than the "Firmware upgrade encountered an issue..." message.
3. By now, you've probably tried every version under the sun. Try one more. It's an Odin package with the recovery image built-in. Assuming that you already have your Samsung drivers, download the executable from Step 3 of this guide: http://forum.xda-developers.com/showthread.php?t=2755793
4. Good luck! I'm just glad I finally fixed mine. Beware the OTA!
How do you force into download mode
badmojorayman said:
I've been searching everywhere for a solution. Stupid Samsung and their Knox and their Kies (which fixes nothing)
I finally got it sorted!
1. Pull out the battery.
2. Reinsert the battery and force the phone into Download Mode. (Yes, I'm aware that the phone is unable to go anywhere else at this point; but when I fixed mine, I did it manually so that it displayed the Android droid logo, rather than the "Firmware upgrade encountered an issue..." message.
3. By now, you've probably tried every version under the sun. Try one more. It's an Odin package with the recovery image built-in. Assuming that you already have your Samsung drivers, download the executable from Step 3 of this guide: http://forum.xda-developers.com/showthread.php?t=2755793
4. Good luck! I'm just glad I finally fixed mine. Beware the OTA!
Click to expand...
Click to collapse
sparks.calvin said:
How do you force into download mode
Click to expand...
Click to collapse
Press and hold down Volume down and Home button.
While holding both the above keys press and hold the power button, then you will see the disclaimer.
Let go of all the buttons and press Volume up to accept the disclaimer.
The phone goes directly into ODIN/Download mode right after this. You will see a green droid which indicates you’re in ODIN/Download mode.
sdw8253 said:
SUMMARIZED QUESTIONS:
1) Is my phone hard bricked?
2) Do you think JTAG can fix my phone? My phone may be in Read only state. Wouldn't that prevent the JTAG method?
3) Will the SD card method work?
4) Does anyone have Sprint bootchain? (I think my phone might be at Read Only state)
5) What are some signs of EMMC failure? I would really hate it if my phone had EMMC failure -_-
6) Did my phone brick because my phone was rooted and I flashed unrooted Sprint Stock ROM?
PLEASE PLEASE help me. Donations will be considered! (Really, I'm desperate to get my phone fixed. T_T )
Thank you alot in advance. Please leave replies if you need more information.
Click to expand...
Click to collapse
did you get it unbricked?
and answer to Question 6 like others have said it bricked cause you flashed MK3 or another older bootloader rom when you had ND8 if you notice on basically every sprint/boost/virgin post they state you can't go to a lower bootloader when on ND8 where did you hear you could flash a lower stock rom?
6th_Hokage said:
did you get it unbricked?
and answer to Question 6 like others have said it bricked cause you flashed MK3 or another older bootloader rom when you had ND8 if you notice on basically every sprint/boost/virgin post they state you can't go to a lower bootloader when on ND8 where did you hear you could flash a lower stock rom?
Click to expand...
Click to collapse
Yes. I got it unbricked ^_^
I flashed a new PIT file and it was unbricked!
I didn't hear that I could flash a lower stock ROM. I didn't know it was going to be bricked if I flashed with a lower stock rom.
sdw8253 said:
Yes. I got it unbricked ^_^
I flashed a new PIT file and it was unbricked!
I didn't hear that I could flash a lower stock ROM. I didn't know it was going to be bricked if I flashed with a lower stock rom.
Click to expand...
Click to collapse
ohhh okay well that's good; you got it sorted out
Hey yall,
Neighbor's kid handed me his Sprint galaxy s3 today and asked if I could fix it. It's not working at all right now. I'd like to think I know a thing or two about technology but I know jack about Android...I use the other brand of phones. Anyway, lots of searches led me here to ask for help.
Far as I can tell it's a Spring LPH-710 Samsung Galaxy S3. When I turn it on it has the firmware upgrade encountered an issue screen and it doesn't do anything else. I can't get VOLUP+HOME+POWER to work (recovery mode I think) but download mode works with VOLDOWN+HOME+POWER.
I went and downloaded the Kies program from samsung but it fails to load the software. here's the error message; CAN'T POST LINKS! arrrgggg. It says "Failed to upgrade firmware due to an unexpected error. Do you want to run firmware emergency recovery now?" It then says I should enter some recovery code from another PC which I don't have.
It also has some small red text on the phone screen after I saw the Kies error message. It says SW REV CHECK FAIL : Fused 2 > Binary 1. That makes no sense to me but it's red and Kies error out so I'm going to assume that's not good.
I don't have a recovery key to use and the kid tells me he never backed it up to a computer before. I've read Odin is the preferred method to use for stock recovery but I don't know what files to download and use. Apparently, people are pretty unhappy with Kies...kinda like iTunes I guess. Why can't the Kies software wipe and reload the phone? Am I doing something wrong?
The device malfunctioned or had an error when he tried doing an update / flash. And if Kies is malfunctioning you can try PC Odin.
Download Sammy drivers of device, download the stock .tar image of the sprint s3 ( L710VPUDND8 ), download Odin v3.07
- At PC. Open Odin in admin mode. Click PDA and select the .tar image file and let that load and leave everything else alone in the program.
- On device press vol dn + home + power to get into download mode, press vol up to continue.
- Plug in device and let driver installation be completed. If a box in Odin ( on PC ) doesn't show a COM:##, replug device or try different ports and cables.
- Once you have that all set up click start and leave it to flash. It takes roughly 15 minutes to flash the whole thing or lesser.
If all else fails tell him to bring it in for servicing.
Posted via XDA Mobile
Thanks for the reply Sparks. I downloaded Odin 3.07, uninstall Kies and rebooted the PC. When I loaded the .md5 file, I then plugged in the phone and saw it look for drivers. The phone shows up on COM3. Below is what I see after I press start. Doesn't look good to me! Did I get the right file?
I've read that attepting to alter the operating system will void the warranty. Would this line on the download screen indicate he tried to do that? Current Binary: Custom. He said the contract is up in March so I'd hate for him to get screwed over by this.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUDND8_L710SPRDND8_L710VPUDND8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
That's the right file. Says md5 is valid.
Binary custom and/or warranty bit 1 means he already tried to flash something and it ticked the counters so he's out of luck getting it repaired.
Go download the Galaxy S3 Samsung drivers through the official site and install them, reboot pc and try the method again in a different USB PORT ( Preferebly 2.0 slots ) some ports and different cables can be iffy at times.
Posted via XDA Mobile Free
Hi, I've searched hi and low for help, but can't find anything that seem to apply to my phone or case. I have a Canadian Mobilicity S3 model SGH-T999V that just bricked itself. Everything is official other than I unlocked it to switch to Wind: Binary Count = 0.
The Story: Last week (Tuesday Sep 22nd 2015) The phone restarted a few times for no apparent reason, then the next day errors about missing files started to pop up to the point that I had to reset the phone to be able to use it. Start fresh all good for a week, then one restart yesterday (Sep 30) and this morning I have a screen that says: "Device Memory Damaged - the data partition has been corrupted.you need to reset your device to factory defaults.this will erase all your date. (reset device button)" I press the button nothing happens, so I take out the battery, leave it while at work, then try again: same thing - I try to reboot into recovery but fail: I get a down android with an open belly cover and a red triangle picture for a bit and the phone reboots back to the damaged memory screen. I can get into the download mode, but Odin doesn't see the phone.
Any advice on how to proceed from here would be greatly appreciated.
I've used Odin before on my Nexus S, but that was many moons ago, it's dead now...
Thanks in advance.
Can you get into download mode? If you can, yet flashing the stock ROM from sammobile.com and flash it using Odin.
Thanks for the reply.
Odin doesn't see the phone and I don't remember exactly how to use it either, but I know it's very model specific, as to files and ROMs to download and install, hence the advise seeking. I guess I'm hoping someone in the know can tell me "follow the instructions for such [more popular] model #, that will work on the 999"...
The T999v is a very popular model in Canada as it was used by Wind and Videotron.
Are you able to boot the phone into download mode? The Samsung drivers are installed? Are you using a Win7 machine?
Yes it boots into Download mode but not into recovery. I have Kies installed along with the drivers, could reinstall that just in case. Running Windows 10 Pro Preview, in the process of upgrading to the final release.
I recommend grabbing the latest firmware from sammobile.com for the phone and flash it in Odin 3.07 with the phone in download mode. I would not bother with Kies.
I've updated my build of Windows 10, that may have been one of my problems, now Odin reacts to the phone but fails:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999VVLUFNH2_T999VYVLFNH2_T999VVLUFNH2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Phone says in red: "Secure Check Fail: aboot
So much for that! guess it's fried at the hardware level.
I'm thinking you are suffering from a hardware failure as stated by the message you mentioned before. It has happened to others and I can't recall anyone having much success in restoring functionality.
If you want to try again though, uninstall kies from your computer as it interferes with Odin. There is also a newer version of Odin, but I doubt that would make much difference on the S3.
If you are unable to get it working again and want a relatively cheap fix, search ebay for a used motherboard or a device that has a broken screen but otherwise works. Then swap out the board.
Sent from my SGH-T999 using Tapatalk
The update is failing because the ROM you are flashing has a bootloader that is older than the version currently installed on the phone as verified by the following stop error in Odin:
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
I have a feeling DocHoliday77 is probably right, I've bought a new phone from my provider for 9$ (Alcatel onetouch Pop D3) and posted a wanted ad for broken S3 ... not ready to completely give up on the S3 just yet, but neither do I have high hopes.
Getting rid of Kies
The firmware is the most recent for the SGH-T999V on sammobile.com - I can try without the V maybe
Only T999V firmware will work on the T999V.
If you are selling it and it has a good working display you should be able to get a decent amount for it still. Not sure how much they are going for these days but it's always been the most expensive and in demand part for the device.