Develop Bugs

[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] 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!

P600 Bootlooping + Doesn't want to take anything from Odin

Hey All,
Sorry if this is a common issue, I've been script-kiddie hacking my android phones for a good bit now, but this one is perplexing me.
A friend bought a Galaxy Note 10.1 2014 Edition a few weeks ago, and asked me to take a look at it when he received it not working (friend of a friend kind of sale). I got my hands on it, and managed to get it to boot into a recovery (it honestly looked a little like CWM--just not as functional) as well as into Odin Mode.
I've used ADB, I've used fastboot, but I've never actually had to use Odin to my memory. That being said, Odin is relatively straight forward from what I see. I decided to take the route of trying to get the device back to stock, and found this thread:
http://forum.xda-developers.com/showthread.php?t=2618509
Seemed like a viable solution, but when loading the above .tar in Odin v3.09, and hitting start, this is the output:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P600UEUBMK1_P600XARBMK1_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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Can anyone provide a next step suggestion on what to try?

Siiig said:
Hey All,
Can anyone provide a next step suggestion on what to try?
Click to expand...
Click to collapse
What was the firmware version on the device when it crashed?

Hey Buhohitr,
I can't actually answer that question, as I mentioned up top, the device came into my life in its current state.
Would I be able to identify that based on the labels, or odin mode?

Siiig said:
Hey Buhohitr,
I can't actually answer that question, as I mentioned up top, the device came into my life in its current state.
Would I be able to identify that based on the labels, or odin mode?
Click to expand...
Click to collapse
download the latest firmware release for the US model.
https://mega.co.nz/#!H4hT1QQb!nidMcJhBQZiQvfz_fYLw4ZcS7bQIbJ-aURaD1WiaU0I
flash via Odin in the PDA / AP slot and see if that works

Siiig said:
Hey Buhohitr,
I can't actually answer that question, as I mentioned up top, the device came into my life in its current state.
Would I be able to identify that based on the labels, or odin mode?
Click to expand...
Click to collapse
Ok, the reason I asked because the firmware you tried to load is way outdated and if the current firmware version in your device is higher you won't able to downgrade, so the best bet is to flash the latest firmware as Brett_day suggested.

buhohitr said:
Ok, the reason I asked because the firmware you tried to load is way outdated and if the current firmware version in your device is higher you won't able to downgrade, so the best bet is to flash the latest firmware as Brett_day suggested.
Click to expand...
Click to collapse
Thanks guys!
Currently downloading the newest firmware at home--will try flashing it with Odin and report back!

Siiig said:
Thanks guys!
Currently downloading the newest firmware at home--will try flashing it with Odin and report back!
Click to expand...
Click to collapse
Very sad to report the exact same message out of Odin:
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> P600UEUCNI1_P600XARCNI1_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>
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1
Would someone else with a P600 be willing to tell me exactly what windows recognizes their device as when working in Odin?
This is what mine is showing:
{
"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"
}

Let take this slowly, one step at a time. Can you flash stock recovery with Odin and without boot up the device, boot directly into stock recovery? Let me know the results before proceed further.

buhohitr said:
Let take this slowly, one step at a time. Can you flash stock recovery with Odin and without boot up the device, boot directly into stock recovery? Let me know the results before proceed further.
Click to expand...
Click to collapse
I hate to do this Buhohitr, but where would I be able to find the stock recovery?

Siiig said:
I hate to do this Buhohitr, but where would I be able to find the stock recovery?
Click to expand...
Click to collapse
Not a problem, go here https://mega.co.nz/#!1BVWmLzZ!chJ9714Bxp7XbsZtAdMYHxhoOsExF9c9pUAcEDT3BHw download, unzip and you should see stockrecoverymj4.tar.md5, flash it with Odin, make sure auto reboot is unchecked. Once done flashing, don't let it boot up, boot back into stock recovery then wipe cache, davik cache and data, then flash latest stock rom.

Thanks
buhohitr said:
Not a problem, go here download, unzip and you should see stockrecoverymj4.tar.md5, flash it with Odin, make sure auto reboot is unchecked. Once done flashing, don't let it boot up, boot back into stock recovery then wipe cache, davik cache and data, then flash latest stock rom.
Click to expand...
Click to collapse
Thanks a lot, I was able to get working a P600 with your advice. Thanks a lot, mate. :good:

Sad to say, I didn't have the same luck.
Same error message about no PIT was found. It's actually identical to the log I posted before.
I wish I knew what happened to this poor thing.

Hey Guys,
I wanted to ask on here before I completely give up on this tablet, is it possible to re-flash the PIT partition on our tablets?
I remember reading in another thread the PIT needs to be signed by Samsung in order to flash, but I'm not sure if signed PITs are available.
If not, is there a particular part that might go bad on this device? Hard drive going dead kind of thing?

[Q] Soft bricked Note 2 I317m

Hi guys. I'm trying to fix this phone for my brother. He said he went to factory reset and wiped his phone.
{
"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"
}
(I put it in ADB mode to show more of the messages. I never flashed anything from ADB)
So it looked like he managed to wipe his systems so I downloaded Odin, installed the drivers and got the stock firmware from sammobile for his model. When I tried to flash it fails. I am not sure what I can do from here. Is the phone done? The previous forum threads were suggesting turning on USB debugging but the system isn't even on the device anymore for me to enable it.
I was thinking maybe I can flash it through recovery but I didn't find anything on google that said I could do that.
Code:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLUDNH2_I317MOYADNH2_I317MVLUDNH2_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks in advance. Any help would be greatly appreciated.

So I tried flashing a custom recovery both through Odin (get failed message) and through recovery (get cant mount /cache and /cache recovery)
So is this phone bricked?

any news? I have exactly same problem.

Same problem here, my friend's N7100 Hong Kong Version is dead just like this.
Stock 4.4.2 rom, not rooted, same message in recovery mode and Odin.
Please help!

Same here, stock recovery can't mount anything, ODIN mode can't flash anything, I think it is EMMC brick bug. N7105
Kicking myself for not copying a recent backup to external SD (it is on now inaccessible internal SD). Would be good if I could flash a decent recovery with some tools to try to get the internal SD card mounted, but I think nothing can be flashed at this point.

My SGH-i317M 16GB with Telus also suddenly failed to boot, and failed to flash using ODIN as well. After sent to several shops, including one which can perform JTAG flashing, confirmed that the eMMC is damaged.
This is not a simple software bug in eMMC, but a hardware failure, which requires to spend several hundred dollars in part and labour to replace the eMMC (embedded MMC 16GB NAND flash memory).
According to my weeks long research in the internet, this seems like a eMMC IC manufacturing problem on 16GB Note2 models in early release phones back in 2013, but not affecting 32GB model.
There are several users reporting that they used non-Samsung charger to charge the phone, including me, who use car charger. Poor quality charger somehow can shorten the life of the eMMC 16GB IC, and the phone will either slowly has storage corruption in this 16GB storage (which stores mount points /system, /data, /user). Unluckily this storage memory also stores the bootloader, recovery screen, charger percentage, Android OS, as well as user data + apps.
For me, it first reporting data issue by showing "I'm Lucky" button after booted up, which I though it resolved by factory reset without realize this is an early symptom of eMMC damage/failing. After 3 weeks, it stuck in boot screen, but manage to go to recovery screen, and neither Samsung Kies nor ODIN can write to the eMMC storage. This is later confirmed by a technician who has JTAG equipments/software that the eMMC is not writable at all, and needs to be replace.
The Android app that you can found on internet for the "fix" is actually a workaround, which will do a write test to identify bad block in eMMC storage which failed, and prevent the phone from using those areas to store any data. This app doesn't fix the hardware failure, which needs to be physically replaced. Theoretically, it can be replaced with 32GB eMMC IC but I don't find anyone posting the picture or model of the 32GB eMMC for SGH-i317M, as well as nothing for international model - i7100. If you are DOS users who used a floppy disk before, this is alike a dirty floppy disk with bad block, which the chkdsk utility can mark the FAT area for bad cluster to prevent DOS to write any data into those area. It is near impossible to repair the floppy disk to recover the bad cluster, unless replacing the disk.
For those who read this post early, and their phone is early release, and using the bad eMMC IC, I will advice to root it and install custom ROM which can boot from external fast microSD card, in addition of not using car charger and only use Samsung charger. This should prolong the time of eMMC lifespan
Hope this clarify for all users who has a failing eMMC chip, and be proactive about it

possible hard brick gt n7100

Hi everyone,
I ve been using a note 2 gt n7100 for 2 years .Since i ve got in my hands it was rooted with custom rom.Everything was fine,as i always was reading the instructions of every forum out there.
Its been a week that i ve installed a cyanogen build rom 6.01 ,my phone was working properly and i had no problem till yesterday that i ran out of battery and since then my phone is stuck at rom logo.
It cant even enter recovery mode ,only download mode .
In the download mode i can see my device name and my phone appears in ODIN.
But i cant write nor a stock rom,or bootloader or recovery even using pit files that i fould in the internet.
it is stuck oin download mode.
Can y give me any advice someone?
Is it hard brick?

what messages do you have in Odin?
it seems like SDS

yaro666 said:
what messages do you have in Odin?
it seems like SDS
Click to expand...
Click to collapse
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Rimotomos said:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try to take out sim & sd before flashing.

malyshbo said:
Try to take out sim & sd before flashing.
Click to expand...
Click to collapse
i already did.
i also tried to flash only pit file ,only recovery,only bootloader and always the same
I tried to flash all above again with pit file together but again fail
------
my samsung appears as gadger serial in devices.is this a problem?
{
"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"
}
I also tried HEIMDALL frontend and i get same fail about the pit file

seems your problem same as me bro. ran out of battery and cannot even enter recovery ( actually can but cannot go further such as flash rom or restore nandroid. ) dont panic. get another battery to test. i also panic when try anything but only download i can enter. at the end, i found my battery is totally dead after i try another battery. so buy new battery and phone back to normal.

fonblets said:
seems your problem same as me bro. ran out of battery and cannot even enter recovery ( actually can but cannot go further such as flash rom or restore nandroid. ) dont panic. get another battery to test. i also panic when try anything but only download i can enter. at the end, i found my battery is totally dead after i try another battery. so buy new battery and phone back to normal.
Click to expand...
Click to collapse
unfortunately,new battery didnt work