Develop Bugs

[Q] Phone stuck after flashing stock rooted

OK--1st post EVER in a forum, so I feel like I'm gonna get layed into,
but here goes:
Just got Epic Touch two days ago and felt I needed root so I downloaded
and used the EL29 Odin one-click method of flashing the stock rooted ROM.
This was yesterday. No problems. Took 15 minutes. I installed some apps,
then I installed ROM Manager And tried to use it to install CW, but I'm not sure if that was successful, as I tried to do a couple of NAND backups from within the GUI
of ROM Manager and failed both times, going to the stock android recovery screen.
I think I pulled the battery both times.
Then I installed Widget Locker, was playing around with that for a bit, took
a photo and tried to attach it to a text response, then the phone locked while
I was sending that. Pulled battery, wont get past Samsung startup screen.
Looked around a bit, decided to try and reflash using the one-click method.
I get:
<ID:0/006> 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/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> recovery.bin
every time. BTW, I cannot access anything with VolUP+power buttons.
I've tried different combos of that, always Samsung boot screen hang.
I can get into Odin, and Odin sees my device. but never has the device indicated
that anything is happening. No progress bar.
Also, I have tried the two USB cables that i have in all the ports of my computer,
but I do not have another handy.
So I poked around and found this:
http://forum.xda-developers.com/showthread.php?t=1492771
which suggested I individually flash ROM, kernel, and modem.
none of that has worked, either.
Flashing the modem does get a green progress bar(in Odin, not on the device),
but then it hangs at--
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> modem.bin
<ID:0/006> NAND Write Start!!
<ID:0/006> Transmission Complete..
<ID:0/006> Now Writing.. Please wait about 2 minutes
flashing kernel yields:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710.EL29_CL852097_KERNEL_PDA.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> zImage
<ID:0/006> NAND Write Start!!
...and a hang.
So....... haven't foud anything else adressing this. Lotta stuff out there about
careless ICS/CWM brickers, but I didn't do anything fancy, did I?
Just stock rooted, 5 hours of use and blammo.
Thanks for the assistance.

Are you using Kies or the full Samsung driver suite? Also, have you tried (with the phone still unplugged) running the one-click odin on the pc, getting into odin mode on the phone and THEN plugging the phone in?
Edit: If you need them, the samsung drivers are here:
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe
Please remove kies prior to installing them. In any case, you should probably uninstall what you have now and install the driver suite if it's still not working, then reboot the pc and try again. Sometimes the drivers aren't working correctly and require a reinstall.

I was gonna suggest a pc reboot as well, often times that helps when Odin hangs on me.
Once you get recovered I'd suggest not using cwm manager to install a custom recovery, instead get one from these forums which is specifically for the epic touch.
The original epic had a method of reaching download mode with the battery removed, not sure if that's an option here maybe someone can give the procedure.
Sent from my SPH-D710 using XDA

I think what Rocket meant to say is not use Rom Manager any more.
Sent from my SPH-D710 using XDA

RE:
>> Are you using Kies or the full Samsung driver suite? Also, have you tried (with the phone still unplugged) running the one-click odin on the pc, getting into odin mode on the phone and THEN plugging the phone in?<<<<
I have BOTH installed...but Kies I only installed midway (i.e. this morning)
through troubleshooting. nonetheless i will uninstall/reboot/reinstall/reboot
with these guys. Which is better?
And YES, EVERY time i've tried something with either EL29 oneclick or 1.85 regular Odin, I have always started Odin first, and then plugged the phone in.
If I plug the phone in before putting it in download mode, it just displays an empty battery charging icon, and cannot be turned off except by removing battery.
RE:
>>>>I was gonna suggest a pc reboot as well, often times that helps when Odin hangs on me.
Once you get recovered I'd suggest not using cwm manager to install a custom recovery, instead get one from these forums which is specifically for the epic touch.
The original epic had a method of reaching download mode with the battery removed, not sure if that's an option here maybe someone can give the procedure. <<<<<<<<<<
I HAVE rebooted, several times, though perhaps the driver/drivers are an issue.
I have to go out of town tonight so I'll try some more tomorrow and repost.
Pep talk, though: If it goes into download mode, there's a 99.9 percent chance that I can recover it, right?
Thanks for the replies.

iguai said:
I HAVE rebooted, several times, though perhaps the driver/drivers are an issue.
I have to go out of town tonight so I'll try some more tomorrow and repost.
Pep talk, though: If it goes into download mode, there's a 99.9 percent chance that I can recover it, right?
Click to expand...
Click to collapse
It sounds like you're ok but Kies needs to go, it conflicts with the regular drivers and causes issues using odin. Goood luck and let us know how it goes.

make sure the samsung drivers are on you PC/Laptop. make sure your computer sees your phone. I have read that sometimes trying different USB ports and cables can be helpful as well when using Odin. hope this helps.

OK--- uninstalled Kies and reinstalled Samsung drivers and restarted and such.
Tried oneclick and still getting stuck at recovery bin.
Tried all three usb ports.

iguai said:
OK--- uninstalled Kies and reinstalled Samsung drivers and restarted and such.
Tried oneclick and still getting stuck at recovery bin.
Tried all three usb ports.
Click to expand...
Click to collapse
You're likely bricked. Sorry. Rom Manager has been bad for almost all Samsung phones.
Sent from my SPH-D710 using XDA

Allow your phone to charge for SEVERAL hours.
Follow this guide to the letter: http://forum.xda-developers.com/showthread.php?t=1274337
Flash this rom which has root: http://forum.xda-developers.com/showthread.php?t=1703406
If you follow this correctly and your phone does not boot. You are bricked.
Sounds like somehow you reversed the modem or rom and flashed them between the phone and pda (which I hope you didn't because you are bricked if you did... but its good in away because you can take it back and say look what I woke to...).
Let us know if it works...
Edit- and if it does boot, don't ever try to install cwm with rom manager on this phone.

No dice. I am, however, going to give it one more try on a friends computer this evening. That's my last throw though, I think, unless I get some fresh inspiration.
I'll report back tomorrow.

OK---I gave it everything, and no dice.
This phone was bricked.
I believe using ROMManager to try and install CWM f'd some things,
and perhaps when I was trying to do individual flashes
in Odin I flashed a modem in PDA.
Thanks for all responses.

Tried everything and nothing
So I wasn't trying anything crazy with my phone, left it charging, and went to check the time and it was off, tried turning it on and nothing.
I was running CM10 Beta 2... so I went into recovery mode, tried to run do wipe factory reset, wipe dalvik, wipe cache, flash the CM10 again, and it was getting stuck.
Mounted usb on pc and tried to save some files to flash the full tar through odin, in the middle of that copy it failed, so I tried to odin the tar anyway and it was getting stucked.
Tried flashing modem separately - stuck on Wait 2 mintues...
Tried flashing kernel separately - stuck on NAND Write Start!!
Tried flashing rom - stuck
Tried flashing pit file - stuck
Tried one click - stuck
The thing is that I can't just say to samsung service that I didn't do anything to the phone, because when you try to boot in recovery it shows CWM 6..., but only one line, it doesn't really load cwm.
So even if I use a usb jig to reset odin counter, they'll notice I had done some stuff to the phone, even when I wasn't really doing anything when it crashed.
Any new way to fix the phone? I don't have insurance or anything, so I might be pretty much screwed
Anything else I could do? Thank you very much!

[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"
}

[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

Another Soft Brick...

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.

Odin Fails with eMMC write fail error.

Hello everyone.
I just purchased a Sprint Note 4 (SM-n910P) that has Android 5.1.1 currently installed. While I know there is no current chainfire autoroot for this version of android, I was planning on downloading to 5.0.1 using the ROM file from SamMobile that I downloaded. So I enabled developer mode, enabled USB debugging, and used Odin to flash and downgrade to 5.0.1. I used vol down, Power, and Home to go into the Odin Mode on the phone, plugged it into a Windows 10 PC using Odin 3.10.6. Odin recognizes the com port and I load up the correct .tar.md5 file. I press start and immediately receive a FAIL inside of Odin. This is on the Odin screen:
<OSM> N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.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> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
While on the phone I receive the following:
SW REV CHECK FAIL : [about]Fused 4 > Binary 3
[1] eMMC write fail: ABOUT
Can anyone tell me what I am doing wrong? I am experienced at rooting and flashing roms on my HTC Evo 4G and my Note 2 which I've had for a combined 5+ years. I've tried Odin 3.07, 3.10, older Samsung USB Cable, newer USB cable. I have Kies installed with the latest USB drivers installed.
Is this an issue with my computer or with the phone itself? After it fails numerous times I'm able to reboot the phone back into the normal settings and continue using it as if nothing happened. CAN I downgrade this to 4.4.4 through 5.0.1 if I choose too? Or does 5.1.1 somehow magically prevent all of that from happening? Advice? Comments? Suggestions??
Thanks!

Downgrade !
bawalker said:
Hello everyone.
I just purchased a Sprint Note 4 (SM-n910P) that has Android 5.1.1 currently installed. While I know there is no current chainfire autoroot for this version of android, I was planning on downloading to 5.0.1 using the ROM file from SamMobile that I downloaded. So I enabled developer mode, enabled USB debugging, and used Odin to flash and downgrade to 5.0.1. I used vol down, Power, and Home to go into the Odin Mode on the phone, plugged it into a Windows 10 PC using Odin 3.10.6. Odin recognizes the com port and I load up the correct .tar.md5 file. I press start and immediately receive a FAIL inside of Odin. This is on the Odin screen:
<OSM> N910PVPU3BOF5_N910PSPT3BOF5_N910PVPU3BOF5_HOME.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> aboot.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> sbl1.mbn
<ID:0/007> rpm.mbn
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
While on the phone I receive the following:
SW REV CHECK FAIL : [about]Fused 4 > Binary 3
[1] eMMC write fail: ABOUT
Can anyone tell me what I am doing wrong? I am experienced at rooting and flashing roms on my HTC Evo 4G and my Note 2 which I've had for a combined 5+ years. I've tried Odin 3.07, 3.10, older Samsung USB Cable, newer USB cable. I have Kies installed with the latest USB drivers installed.
Is this an issue with my computer or with the phone itself? After it fails numerous times I'm able to reboot the phone back into the normal settings and continue using it as if nothing happened. CAN I downgrade this to 4.4.4 through 5.0.1 if I choose too? Or does 5.1.1 somehow magically prevent all of that from happening? Advice? Comments? Suggestions??
Thanks!
Click to expand...
Click to collapse
You cant downgrade when on android 5.1.1 og5, seems to be the trending thing nowadays, so if your on 5.1.1 your stuck, we have root, roms, and xposed is working. Good luck on your quest!

Iceburn1 said:
You cant downgrade when on android 5.1.1 og5, seems to be the trending thing nowadays, so if your on 5.1.1 your stuck, we have root, roms, and xposed is working. Good luck on your quest!
Click to expand...
Click to collapse
Well that just totally sucks. I was hoping to get down to 5.0.1 to use chainfire root. The Beastmode root kernel patch seems to have slowness and lag issues introduced after installing that kernel patch which I really wanted to avoid.
I used to do roms and such back earlier on in my smart phone days, but I've found Stock to be best, even with touchwhiz. When I root I just want root access, maybe twrp, but even that's not a requirement as the only things I use are wifi tether when on job sites and titanium backup to freeze things like knox, remove bloatware, etc. That's all I ever use root for. So I'm kinda bummed right now over not downgrading. What is Samsung thinking?!

@bawalker,
You'll need to use the correct root method found in post below. Also, refer to OP of that thread to understand the reasons; OG5 update blocked root at kernel level. And bootloader blocks downgrade to lower versions.
http://forum.xda-developers.com/showthread.php?p=62241991
Flash TWRP then try the Beastmode kernel and SuperSU zip in recovery with cache and dalvik-cache wipe. If it doesn't boot, you may need the OG5 stock tar and start over.
Sent from my SM-N910P using Tapatalk

samep said:
@bawalker,
You'll need to use the correct root method found in post below. Also, refer to OP of that thread to understand the reasons; OG5 update blocked root at kernel level. And bootloader blocks downgrade to lower versions.
http://forum.xda-developers.com/showthread.php?p=62241991
Flash TWRP then try the Beastmode kernel and SuperSU zip in recovery with cache and dalvik-cache wipe. If it doesn't boot, you may need the OG5 stock tar and start over.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks for that link, I read that last night in passing. I've also still be reading that those who do this root method and after adding the line to the bottom of the build.prop file still experience lag and in some cases, some complained it was severe. If I'm going to have performance issues with a phone I use for my business every day then I'm hesitant of even doing it. Esp after seeing that using Odin to put a 5.1.1 tar.md5 rom back on isn't working right.

Kernel+Rom
bawalker said:
Thanks for that link, I read that last night in passing. I've also still be reading that those who do this root method and after adding the line to the bottom of the build.prop file still experience lag and in some cases, some complained it was severe. If I'm going to have performance issues with a phone I use for my business every day then I'm hesitant of even doing it. Esp after seeing that using Odin to put a 5.1.1 tar.md5 rom back on isn't working right.
Click to expand...
Click to collapse
Im using stock rom Hybrid 3.0...http://forum.xda-developers.com/note-4-sprint/development/rom-t2956667....with emotion kernel.....http://emotroid.com/touchwiz-kernel/, use app called Synapse to control kernel, link is below emotion kernel to playstore. You said you liked stock, and this will give you that and the emotion kernel is great, no lag for me at all, use synapse to fine tune it.

I have n910f , i try to flash it but always get odin fails
Any solution to repair it

hbs131415 said:
I have n910f , i try to flash it but always get odin fails
Any solution to repair it
Click to expand...
Click to collapse
Lots of reasons for Odin to fail. Some can be easily remedied but others aren't so easy. Could you post the full Odin log and include the screenshot of phone display or describe fully as the OP did in post 1?
Sent from my SM-N910P using Tapatalk

samep said:
Lots of reasons for Odin to fail. Some can be easily remedied but others aren't so easy. Could you post the full Odin log and include the screenshot of phone display or describe fully as the OP did in post 1?
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
<ID:0/028> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N910FXXU1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_N910FXXU1ANK4_REV00_CL_1795169.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_N910FOXA1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT_.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N910FXXU1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/028> Odin engine v(ID:3.1005)..
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Set PIT file..
<ID:0/028> DO NOT TURN OFF TARGET!!
<ID:0/028> Get PIT for mapping..
<ID:0/028> Firmware update start..
<ID:0/028> SingleDownload.
<ID:0/028> aboot.mbn
<ID:0/028> NAND Write Start!!
<ID:0/028> sbl1.mbn
<ID:0/028> rpm.mbn
<ID:0/028> tz.mbn
<ID:0/028> sdi.mbn
<ID:0/028> NON-HLOS.bin
<ID:0/028> boot.img
<ID:0/028> FAIL! (Write)
<ID:0/028>
<ID:0/028> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

hbs131415 said:
<ID:0/028> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N910FXXU1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CP_N910FXXU1ANK4_REV00_CL_1795169.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CSC_OXA_N910FOXA1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT_.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> AP_N910FXXU1ANK4_CL3311829_QB3005660_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/028> Odin engine v(ID:3.1005)..
<ID:0/028> File analysis..
<ID:0/028> SetupConnection..
<ID:0/028> Initialzation..
<ID:0/028> Set PIT file..
<ID:0/028> DO NOT TURN OFF TARGET!!
<ID:0/028> Get PIT for mapping..
<ID:0/028> Firmware update start..
<ID:0/028> SingleDownload.
<ID:0/028> aboot.mbn
<ID:0/028> NAND Write Start!!
<ID:0/028> sbl1.mbn
<ID:0/028> rpm.mbn
<ID:0/028> tz.mbn
<ID:0/028> sdi.mbn
<ID:0/028> NON-HLOS.bin
<ID:0/028> boot.img
<ID:0/028> FAIL! (Write)
<ID:0/028>
<ID:0/028> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
And what does your phone display indicate when you get this failure?
Just an observation, I think you're trying to Odin KitKat which may not be possible in Odin if you've updated to Lollipop 5.1 Other 5.0 stock tars attempted may also get blocked to downgrade of bootloader as well like my SM-N910P will. My phone won't get as far as yours did when Odin of KitKat or Android 5.0 stock tar is attempted so that may not be the issue; maybe you haven't had that phone upgraded beyond beyond Android 5.0 yet?
If you had updated to Android 5.1 or higher, you might consider trying a newer stock tar, 5.1 or higher.
They're may be a more logical reason given on your screen at time of failure.
Sent from my SM-N910P using Tapatalk

here the message in the phone
here screenshoot

samep said:
@bawalker,
You'll need to use the correct root method found in post below. Also, refer to OP of that thread to understand the reasons; OG5 update blocked root at kernel level. And bootloader blocks downgrade to lower versions.
http://forum.xda-developers.com/showthread.php?p=62241991
Flash TWRP then try the Beastmode kernel and SuperSU zip in recovery with cache and dalvik-cache wipe. If it doesn't boot, you may need the OG5 stock tar and start over.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Out of curiosity? Keep getting conflicting. Does this device have a bad hostory of emmc failures. I got one doing it. But this things seems to have loads of weird issues. I will get some logs together tonight when i get. Home. Im goi. To try to flash latest mm firmware tonight. When i try to start up anything other than dl mode. I get the connect to kies. The fiwmware update went wrong select emency recovery. Kies 3 doesnt work for this device or it says it dont. And i get a side by side configuration error when installing older odin. Got windows 10

hbs131415 said:
here the message in the phone
here screenshoot
Click to expand...
Click to collapse
That's not good but I'm still not sure if you can flash that KitKat stock tar or not.
If you've had updates greater than Android 5.0 on that phone, I'd suggest not trying to flash that anymore. If that applies, try the latest stock tar.
The eMMC write error could be component failure but I'm thinking it could also be refusing to downgrade the bootloader to a less secure one which would apply if the phone is currently on a higher bootloader. Could you get the bootloader version by running this app?
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
You can use Galaxy Tools if you have that. Of course that requires the phone to be booted. If you can post, a screenshot.
Something to consider: it's risky so do only after determining the proper stock tar fails even using Odin default settings. So If you continue to have the eMMC write error, the PIT can be found on Sammobile in the Note 4 PIT thread (posted at bottom of this post). In order to determine if flashing error or component failure, power down, pull battery for a minute or more, and first try the suggested tar with Odin defaults. If it fails with eMMC write error again, you can try to flash with repartition and PIT with "nand erase all" and stock tar loaded, all at same time. Important: Always have the right PIT loaded with repartition option checked. Don't forget the battery pull prior to download mode.
If the last step fails, you most likely have the a component failure. If it's just a boot issue, nand erase all sometimes causes that: try factory reset in stock recovery, pull battery and flash the tar again with Odin defaults.
Before beginning, first determine which stock tar to flash. I'd recommend latest if your bootloader is Android 5.1 or higher. The Sprint version started getting the updated bootloader before Android 5.1, so only the initial Lollipop release had the less secure bootloader.
Find PIT here:
http://www.sammobile.com/forum/showthread.php?p=137840
You can find recommended safe versions of Odin here:
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
Sent from my SM-N910P using Tapatalk
---------- Post added at 11:10 AM ---------- Previous post was at 10:46 AM ----------
TheMadScientist420 said:
Out of curiosity? Keep getting conflicting. Does this device have a bad hostory of emmc failures. I got one doing it. But this things seems to have loads of weird issues. I will get some logs together tonight when i get. Home. Im goi. To try to flash latest mm firmware tonight. When i try to start up anything other than dl mode. I get the connect to kies. The fiwmware update went wrong select emency recovery. Kies 3 doesnt work for this device or it says it dont. And i get a side by side configuration error when installing older odin. Got windows 10
Click to expand...
Click to collapse
Maybe my reply above helps you?
IMO, the Note 4 does a lot of eMMC failures. Not scientific or statistical data comparisons but I'm seeing recommendations to get TEP (insurance) in close circles on my Sprint version, especially if sluggishness starts or trying to hold out until 2017 phones are available for upgrade.
Having the phone boot to download mode is an indicator of eMMC hardware failure. Some time ago, Samsung had an ongoing to-do list that included flash errors on Odin and OTA. I have a theory that it may discovered by updating phone but may just be hardware failure.
The suggested flash with PIT and repartition and nand erase all with stock tar loaded in AP slot is only a troubleshooting step to eliminate the possibility of a bad flash or update causing the initial error. It's been proven redundant many times and some feel attempting more flashes only worsens the severity. But it is ultimately severe failure at some point so use with appropriate caution. The many eMMC failures makes me weary of updates. Time to consider TEP; $0 deductible for hardware failure without losing an upgrade on line, if available.
Main board replacement or eMMC replacement is another alternative. The local uBreakItiFixIt quoted me $10 labor to replace main board with one that I'd have to obtain myself. I've seen certified used ones on eBay and Amazon.
Hopefully mine lasts. I plan to keep it but planning to upgrade my line in 2017.
Sent from my SM-N910P using Tapatalk

samep said:
That's not good but I'm still not sure if you can flash that KitKat stock tar or not.
If you've had updates greater than Android 5.0 on that phone, I'd suggest not trying to flash that anymore. If that applies, try the latest stock tar.
The eMMC write error could be component failure but I'm thinking it could also be refusing to downgrade the bootloader to a less secure one which would apply if the phone is currently on a higher bootloader. Could you get the bootloader version by running this app?
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo
You can use Galaxy Tools if you have that. Of course that requires the phone to be booted. If you can post, a screenshot.
Something to consider: it's risky so do only after determining the proper stock tar fails even using Odin default settings. So If you continue to have the eMMC write error, the PIT can be found on Sammobile in the Note 4 PIT thread (posted at bottom of this post). In order to determine if flashing error or component failure, power down, pull battery for a minute or more, and first try the suggested tar with Odin defaults. If it fails with eMMC write error again, you can try to flash with repartition and PIT with "nand erase all" and stock tar loaded, all at same time. Important: Always have the right PIT loaded with repartition option checked. Don't forget the battery pull prior to download mode.
If the last step fails, you most likely have the a component failure. If it's just a boot issue, nand erase all sometimes causes that: try factory reset in stock recovery, pull battery and flash the tar again with Odin defaults.
Before beginning, first determine which stock tar to flash. I'd recommend latest if your bootloader is Android 5.1 or higher. The Sprint version started getting the updated bootloader before Android 5.1, so only the initial Lollipop release had the less secure bootloader.
Find PIT here:
http://www.sammobile.com/forum/showthread.php?p=137840
You can find recommended safe versions of Odin here:
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
Sent from my SM-N910P using Tapatalk
---------- Post added at 11:10 AM ---------- Previous post was at 10:46 AM ----------
Maybe my reply above helps you?
IMO, the Note 4 does a lot of eMMC failures. Not scientific or statistical data comparisons but I'm seeing recommendations to get TEP (insurance) in close circles on my Sprint version, especially if sluggishness starts or trying to hold out until 2017 phones are available for upgrade.
Having the phone boot to download mode is an indicator of eMMC hardware failure. Some time ago, Samsung had an ongoing to-do list that included flash errors on Odin and OTA. I have a theory that it may discovered by updating phone but may just be hardware failure.
The suggested flash with PIT and repartition and nand erase all with stock tar loaded in AP slot is only a troubleshooting step to eliminate the possibility of a bad flash or update causing the initial error. It's been proven redundant many times and some feel attempting more flashes only worsens the severity. But it is ultimately severe failure at some point so use with appropriate caution. The many eMMC failures makes me weary of updates. Time to consider TEP; $0 deductible for hardware failure without losing an upgrade on line, if available.
Main board replacement or eMMC replacement is another alternative. The local uBreakItiFixIt quoted me $10 labor to replace main board with one that I'd have to obtain myself. I've seen certified used ones on eBay and Amazon.
Hopefully mine lasts. I plan to keep it but planning to upgrade my line in 2017.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you good sir. Both posts clarify well. Sometimes mine stips about where last posters is. Sometimes it flashes 1/4 of the system before failing. I obtained this device stuck in qloader mode and outa nowhere decided to work. I flashed a few files and all was great. Im thinking. Im flashing a older bl on the newer one hopefully. If not im not out nothing. Not a sprint customer so no innsurance.

TheMadScientist420 said:
Thank you good sir. Both posts clarify well. Sometimes mine stips about where last posters is. Sometimes it flashes 1/4 of the system before failing. I obtained this device stuck in qloader mode and outa nowhere decided to work. I flashed a few files and all was great. Im thinking. Im flashing a older bl on the newer one hopefully. If not im not out nothing. Not a sprint customer so no innsurance.
Click to expand...
Click to collapse
Makes me wonder if the issue with eMMC is cold solder joints?
I used to work in a manufacturing facility. It's rare to happen but unless tight solder wave standards are in place, failures could be more frequent. It happens with even the tightest standards.
Reflow the solder is the fix but have to be careful not to overheat or short electrodes.
Sent from my SM-N910P using Tapatalk

samep said:
Makes me wonder if the issue with eMMC is cold solder joints?
I used to work in a manufacturing facility. It's rare to happen but unless tight solder wave standards are in place, failures could be more frequent. It happens with even the tightest standards.
Reflow the solder is the fix but have to be careful not to overheat or short electrodes.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Same issue as lgg4 but with cores on the prossessor.
Mine keeps failing as a flash write failure makes it to system flashing then fails

TheMadScientist420 said:
Same issue as lgg4 but with cores on the prossessor.
Mine keeps failing as a flash write failure makes it to system flashing then fails
Click to expand...
Click to collapse
You get the eMMC write error each time?
If not, have you tried different USB cables and ports? Different Odin versions? I've seen some users revert to 3.10.6 or 3.10.7 for flash issues. You do have Samsung driver from Samsung support installed, right? Windows 10 doesn't seem to require run as administrator to flash successfully but you might try with and without it just in case.
I forgot to mention earlier that KIES may not work for rooted phones. There may be exceptions for users that started using it before they rooted but I get that inquiry for serial number that cannot doesn't satisfy the inquiry with valid number. I've seen the emergency recovery but never attempted to use it so I don't know if KIES is partially functional or not.
Sent from my SM-N910P using Tapatalk

samep said:
You get the eMMC write error each time?
If not, have you tried different USB cables and ports? Different Odin versions? I've seen some users revert to 3.10.6 or 3.10.7 for flash issues. You do have Samsung driver from Samsung support installed, right? Windows 10 doesn't seem to require run as administrator to flash successfully but you might try with and without it just in case.
I forgot to mention earlier that KIES may not work for rooted phones. There may be exceptions for users that started using it before they rooted but I get that inquiry for serial number that cannot doesn't satisfy the inquiry with valid number. I've seen the emergency recovery but never attempted to use it so I don't know if KIES is partially functional or not.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Mine just says flash write failure. Cant flash twrp cant mount. Tried a factory wipe in fact recovery. Failed cannot mount system. Exception error.
Odin said something while trying to flash twrp. Alongs the lines of no pit for mapping. When i flashed pit ot passes. It acts like the partition table is messed up

TheMadScientist420 said:
Mine just says flash write failure. Cant flash twrp cant mount. Tried a factory wipe in fact recovery. Failed cannot mount system. Exception error.
Odin said something while trying to flash twrp. Alongs the lines of no pit for mapping. When i flashed pit ot passes. It acts like the partition table is messed up
Click to expand...
Click to collapse
Did you try loading the PIT from Sammobile and a recent tar with options repartition and nand erase all? If the tar doesn't include PIT, you might consider PC1 stock tar from the stock tar thread in general forum. Check the md5 against zip before extracting the tar.md5
If you can reach recovery, factory reset. Then power down and pull battery prior to Odin.
Have you tried any of this with a new battery? Historically, from what you describe, you may have been on borrowed time with the functionality you had. All the above is a long shot because typically, updates should happen without error. If you can't flash and boot without error; that just isn't normal if you've taken the appropriate steps to ensure success. Sorry if that's the case.
Sent from my SM-N910P using Tapatalk

samep said:
Did you try loading the PIT from Sammobile and a recent tar with options repartition and nand erase all? If the tar doesn't include PIT, you might consider PC1 stock tar from the stock tar thread in general forum. Check the md5 against zip before extracting the tar.md5
If you can reach recovery, factory reset. Then power down and pull battery prior to Odin.
Have you tried any of this with a new battery? Historically, from what you describe, you may have been on borrowed time with the functionality you had. All the above is a long shot because typically, updates should happen without error. If you can't flash and boot without error; that just isn't normal if you've taken the appropriate steps to ensure success. Sorry if that's the case.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I have tried most of that. This thing does have a weird battery issue. Its no loss to me. I got this thing cheap the other day. I keep getting failed to repartition errors. Which seems to come back to the fail to mount system.
I hate to buy a battery. I dont buy cheappies. Due to high failure quality rateS.
I used the pit from samobiles.
Even factory recovery will wip cache. But thats when i get the failed to mount system
new update so i flashed the developer firmware minus the system and data parts. so basicly modem and other partitions included in boot and that takes every time now it litrely fails when i try to flash something to the system partition. when i flash twrp i get failure says no pit for mapping.
even the pit files is failing says there is no pit partition
id say im donr now just saw a mmc read fail on device in dl mode