Develop Bugs

[Q] updating stops at modem

Been flashing with EVO4G, now switching to Epic..
I bought this phone off ebay with cracked screen, since I had a screen laying around I swapped it out and worked fine. First update to GB27 went sour (it was on FI03), stopped without fail on modem.bin, unplugged and got failure, plugged back in and tried again, getting that "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." screen. Using the SPH-D710_GB27_1014481_Rooted_Restore, opened Odin and tried again, clicking start and watching progress this time it went fine and updated, woohoo.
Well, trying to flash this to boost, and couldnt get the msl regardless of what I tried, so saw a post to go back to EL29 and get it then back up, that worked going back, but coming up to gb27 didnt, back to the modem.bin stop, unplugged, plugged turn off, open Odin try again, nada, same thing stop at modem.bin for about 30 minutes, unplugged it.
I think I re-flashed the EL29 as it was stuck in lala land, then shut it down for the night er, early morning. I saw this recent post about stoppage at data, so could this be the same? Though I can still use it with EL29 installed.
Thanks

gellybelly said:
Been flashing with EVO4G, now switching to Epic..
I bought this phone off ebay with cracked screen, since I had a screen laying around I swapped it out and worked fine. First update to GB27 went sour (it was on FI03), stopped without fail on modem.bin, unplugged and got failure, plugged back in and tried again, getting that "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." screen. Using the SPH-D710_GB27_1014481_Rooted_Restore, opened Odin and tried again, clicking start and watching progress this time it went fine and updated, woohoo.
Well, trying to flash this to boost, and couldnt get the msl regardless of what I tried, so saw a post to go back to EL29 and get it then back up, that worked going back, but coming up to gb27 didnt, back to the modem.bin stop, unplugged, plugged turn off, open Odin try again, nada, same thing stop at modem.bin for about 30 minutes, unplugged it.
I think I re-flashed the EL29 as it was stuck in lala land, then shut it down for the night er, early morning. I saw this recent post about stoppage at data, so could this be the same? Though I can still use it with EL29 installed.
Thanks
Click to expand...
Click to collapse
Have you tried installing the modem via a .zip instead of Odin? If not give that a try.

crawrj said:
Have you tried installing the modem via a .zip instead of Odin? If not give that a try.
Click to expand...
Click to collapse
Not too familiar with the Epic, so if you can... which one? Imma noob at that part lol, still trying to figure out modems, ok read the wiki now I know.
If I am updating to gb27 which modem do I try and install? I only see it go to FH23... oh wait, think I can figure that out, open the tar file and extract the modem.bin file from there, but...
you saying I could install the gb27 modem before full update, thru zip?

gellybelly said:
Not too familiar with the Epic, so if you can... which one? Imma noob at that part lol, still trying to figure out modems, ok read the wiki now I know.
If I am updating to gb27 which modem do I try and install? I only see it go to FH23... oh wait, think I can figure that out, open the tar file and extract the modem.bin file from there, but...
you saying I could install the gb27 modem before full update, thru zip?
Click to expand...
Click to collapse
Just to see if the modem will install fine from the zip. You need a custom recovery to install it. Not sure what you have on there now. Modem is here. http://www.rwilco12.com/downloads.p...g Galaxy S2 (Sprint) (SPH-D710)/Modems/JB/ZIP
If it installs correctly from the zip try the Odin file again. I would verify the MD5 also to make sure it isn't corrupt in any way. If it still hangs on Modem, and Modem takes a while sometimes so make sure you are giving it plenty of time, use 7zip to delete the modem out of the tar and try again.

crawrj said:
Just to see if the modem will install fine from the zip. You need a custom recovery to install it. Not sure what you have on there now. Modem is here. http://www.rwilco12.com/downloads.p...g Galaxy S2 (Sprint) (SPH-D710)/Modems/JB/ZIP
If it installs correctly from the zip try the Odin file again. I would verify the MD5 also to make sure it isn't corrupt in any way. If it still hangs on Modem, and Modem takes a while sometimes so make sure you are giving it plenty of time, use 7zip to delete the modem out of the tar and try again.
Click to expand...
Click to collapse
ok, I believe this is rooted but doesnt have the custom recovery, I tried looking for one, er actually have two but wasnt sure if I could install them so didnt, have: CM9_FF11_Agats_Recovery and FE22_Agats_Repack_ACS, if can use them which one?

You would want this one http://garwynn.rainmotorsports.net/D710SPR/GB27/SXTP_Agat_GB27-v0.1.0.tar

crawrj said:
You would want this one http://garwynn.rainmotorsports.net/D710SPR/GB27/SXTP_Agat_GB27-v0.1.0.tar
Click to expand...
Click to collapse
ok got it, installed custom recovery, get yellow triangle, no prob ... install from zip, modem.zip:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
guess not

gellybelly said:
ok got it, installed custom recovery, get yellow triangle, no prob ... install from zip, modem.zip:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
guess not
Click to expand...
Click to collapse
But when you install EL29 everything installs? That is very odd. Try going back to EL29 and verify that your modem shows up as EL29.

gellybelly said:
ok got it, installed custom recovery, get yellow triangle, no prob ... install from zip, modem.zip:
Finding update package...
Opening update package...
Installing update...
Installation aborted.
guess not
Click to expand...
Click to collapse
hold on wrong one, lol sorry, pulled the one from the rooted restore....
install from zip gb27.zip
finding...
opening...
installing...
SPH-D710 GB27 JB Modem
visit....
Flashing GB27 Modem
script aborted (no error message) E:Error in /sdcard/GB27.zip
(status 7)
Installation aborted
ok now what

gellybelly said:
hold on wrong one, lol sorry, pulled the one from the rooted restore....
install from zip gb27.zip
finding...
opening...
installing...
SPH-D710 GB27 JB Modem
visit....
Flashing GB27 Modem
script aborted (no error message) E:Error in /sdcard/GB27.zip
(status 7)
Installation aborted
ok now what
Click to expand...
Click to collapse
See my post above yours.

crawrj said:
See my post above yours.
Click to expand...
Click to collapse
go back to EL29?
how do I verify that the modem is from el29, errrr wait:
<ID:0/011> 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/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> recovery.bin
<ID:0/011> NAND Write Start!!
<ID:0/011> hidden.img
<ID:0/011> boot.bin
<ID:0/011> Sbl.bin
<ID:0/011> param.lfs
<ID:0/011> cache.img
<ID:0/011> zImage
<ID:0/011> factoryfs.img
<ID:0/011> data.img
<ID:0/011> modem.bin
seems to be stuck, 5 min now....update: 15 min now, about to unplug it.....

gellybelly said:
go back to EL29?
how do I verify that the modem is from el29, errrr wait:
<ID:0/011> 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/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> recovery.bin
<ID:0/011> NAND Write Start!!
<ID:0/011> hidden.img
<ID:0/011> boot.bin
<ID:0/011> Sbl.bin
<ID:0/011> param.lfs
<ID:0/011> cache.img
<ID:0/011> zImage
<ID:0/011> factoryfs.img
<ID:0/011> data.img
<ID:0/011> modem.bin
seems to be stuck, 5 min now....update: 15 min now, about to unplug it.....
Click to expand...
Click to collapse
So after it fails will the device boot?

crawrj said:
So after it fails will the device boot?
Click to expand...
Click to collapse
No, I unplugged it, pulled battery, power on and gives me the Cell phone....Triangle...PC icons with it saying:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."

Have you added the pit file manually even though it's included in the packs?
I would take the FL24 low ship tar, the pit, make sure re-partitioning is checked in Odin and flash that way.
Seems to be more and more of these threads over then past few months.. Wonder what's going on..
There's another current thread where the flash hangs at data.img and Garwynn believes it was the triggered emmc bug. The above was his suggestion as well.

MoHoGalore said:
Have you added the pit file manually even though it's included in the packs?
I would take the FL24 low ship tar, the pit, make sure re-partitioning is checked in Odin and flash that way.
Seems to be more and more of these threads over then past few months.. Wonder what's going on..
There's another current thread where the flash hangs at data.img and Garwynn believes it was the triggered emmc bug. The above was his suggestion as well.
Click to expand...
Click to collapse
hmm havent added any PIT files, not sure what they are.....lol
have the FI03 low tar trying to update to it, hanging on modem also, oops now failed:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> D710_CODE_SPH-D710.FI03_CL1083465_REV02_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/011> Added!!
<ID:0/011> Odin v.3 engine (ID:11)..
<ID:0/011> File analysis..
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Get PIT for mapping..
<ID:0/011> Firmware update start..
<ID:0/011> boot.bin
<ID:0/011> NAND Write Start!!
<ID:0/011> cache.img
<ID:0/011> data.img
<ID:0/011> factoryfs.img
<ID:0/011> hidden.img
<ID:0/011> modem.bin
<ID:0/011> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
yeah I read that post, and was going to add to it but opened new thread, so not sure if my case the same

gellybelly said:
hmm havent added any PIT files, not sure what they are.....lol
have the FI03 low tar trying to update to it, hanging on modem also, oops now failed:
yeah I read that post, and was going to add to it but opened new thread, so not sure if my case the same
Click to expand...
Click to collapse
Go find the 09/26 9/16 pit, add the pit file in the pit section, with a low ship tar in the pda section, check re-partition in odin and try.
If you cant find the pit, I'll link in about 5 mins
:edit: My fault, it's 9/16.. anyway, here is the zip for the pit in this thread - http://forum.xda-developers.com/showthread.php?p=17608657

MoHoGalore said:
Go find the 09/26 pit, with a low ship tar, check re-partition in odin and try.
If you cant find the pit, I'll link in about 5 mins
:edit: My fault, it's 9/16.. anyway, here is the zip for the pit in this thread - http://forum.xda-developers.com/showthread.php?p=17608657
Click to expand...
Click to collapse
lol I was googling and this time google wasnt being friendly
ok I got it downloaded, how do I install, nevermind figured it out PIT in Odin, alright its doing something....

If this fails, maybe try Crawrj's bad flash recovery technique?
What do think Crawrj? (didn't mean to step on your toes here either, btw)
gellybelly said:
lol I was googling and this time google wasnt being friendly
ok I got it downloaded, how do I install, nevermind figured it out PIT in Odin, alright its doing something....
Click to expand...
Click to collapse
Yeah, I edited my post just after you replied..
Go find the 9/16 pit, add the pit file in the pit section, with a low ship tar in the pda section, check re-partition in odin and try.

MoHoGalore said:
If this fails, maybe try Crawrj's bad flash recovery technique?
What do think Crawrj? (didn't mean to step on your toes here either, btw)
Click to expand...
Click to collapse
No way man, we are all here to help. Would never think that. I doubt that will help but couldn't hurt. Since the tar is getting past everything except the modem. And you can't DD the modem on our phone. I would definitely try your other suggestion with the pit. If that doesn't work????
Seems like something is horribly wrong with the phone.

crawrj said:
No way man, we are all here to help. Would never think that. I doubt that will help but couldn't hurt. Since the tar is getting past everything except the modem. And you can't DD the modem on our phone. I would definitely try your other suggestion with the pit. If that doesn't work????
Seems like something is horribly wrong with the phone.
Click to expand...
Click to collapse
hmmm well seems to be the latter, crap
{
"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"
}

Boot loop frozen ??

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

[Q] sboot.bin fail to restore via odin

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

[Q] Odin will not flash Galaxy S3

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

[Q] Flashing back to stock image failing (on 4.4.2)

Okay, I was trying to flash back to original stock image which included all the bloatware and crap like that. Reason for going back was due to some mistake I made removing stuff I possibly shouldn't have (short sighted of me I know) and as a result got error 491 on google play and other stuff when I update. Removing the account to get rid of 491 doesn't work. So I figured flashing back to original stock would work.
I'm on AT&T with the Samsung Galaxy S3 (SGH-I747) on 4.4.2 downgrading to 4.1.1 and then will upgrade from that point on.
The Android system recovery says this is a KOT49H.I747UCUFNE4
I loaded up Odin 3.09, got I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 loaded in AP and hit go. Then I run into this:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.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> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
{
"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"
}
On the phone, it says "SW REV CHECK FAIL : Fused 3 > Binary 0".
Currently I'm downloading 4.3 which is taking it's precious time. However I'm not too confident that this might work. Reason being is http://www.androidayos.com/samsung-galaxy-s3-stock-firmware/ says that it won't work. So I've been trying to figure out how to completely restore back to a 100% default stock image of 4.4.2 undoing the stuff I've done.
Alternatively, I'm out of ideas and really like to get my phone fixed.
Any help or suggestions would be appreciated.

I was able to figure it out. I got 4.3 from here https://www.mediafire.com/folder/w5czcxvufdiaw/I747UCUEMJB_ATTEMJB_4.3 which now is flashing the phone. Guess I kind of overreacted.

Kaitian said:
I was able to figure it out. I got 4.3 from here https://www.mediafire.com/folder/w5czcxvufdiaw/I747UCUEMJB_ATTEMJB_4.3 which now is flashing the phone. Guess I kind of overreacted.
Click to expand...
Click to collapse
Okay, I'm banging my head now which I'm trying to figure out what the heck to do at this point. I'm getting no cell reception which I have "Baseband version Unknown" on the phone. Kies doesn't even do squat for me and acts like I'm fine by saying "This device's version cannot be updated." What's strange is that the phone info is on 4.3 but Kies says "Android Version : 4.1.1 / Baseband Version : I747UCDLK3" which is odd. Does that mean the bootloader is still on 4.1.1 when I need it on 4.3? If so, I've tried using the BL in the above link and it gave me failed.
Suggestions?

Once updated to 4.4.2, you cannot downgrade, ever. Luckily Odin sees this, or you'd be hard bricked right now. I will link to the modem you need to flash in a minute.
As for your other problems, factory resetting will probably help there. Otherwise flash the stock NE4 rom from enewman17 in the development section.
---------- Post added at 03:44 AM ---------- Previous post was at 03:41 AM ----------
Here is the NE4 modem. It should take care of the baseband unknown and no signal.
Before flashing though, verify your bootloader version. Open Terminal Emulator and enter this.
getprop ro.bootloader
If it says anything but NE4, do not flash it!
http://forum.xda-developers.com/showthread.php?p=53627484

DocHoliday77 said:
Once updated to 4.4.2, you cannot downgrade, ever. Luckily Odin sees this, or you'd be hard bricked right now. I will link to the modem you need to flash in a minute.
As for your other problems, factory resetting will probably help there. Otherwise flash the stock NE4 rom from enewman17 in the development section.
---------- Post added at 03:44 AM ---------- Previous post was at 03:41 AM ----------
Here is the NE4 modem. It should take care of the baseband unknown and no signal.
Before flashing though, verify your bootloader version. Open Terminal Emulator and enter this.
getprop ro.bootloader
If it says anything but NE4, do not flash it!
http://forum.xda-developers.com/showthread.php?p=53627484
Click to expand...
Click to collapse
However I don't even know how to update to 4.4.2 from 4.3 with no OTA access. I'll let you know regarding the bootloader in a bit.

Lucky me I guess. It says I747UCUFNE4 on the emulator. However with it still being on 4.3, I don't even know what to do with going from 4.3 to 4.4.2 with no cell access? If I try software update, it says "DM initialization is not ready. Check network or SIM card."

Yes, I was able to push 4.4.2 OTA update with this zip file located here http://forum.xda-developers.com/showthread.php?t=2789917 through TWRP. Now everything is working.

Right on! Glad to hear you fixed it!