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] Odin will not flash Galaxy S3

Moderators, please delete my thread in Samsung Galaxy S III I9300, I9305
My phone: SPH-L710 Sprint Galaxy S3
This is what my ODIN says after trying to flash with stock ROM.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
This is what is on the top left corner in the DL mode.
"ODIN MODE
PRODUCT NAME: SPH-L710.
CUSTOM BINARY:Custom
SYSTEM STATUS:Custom
QUALCOM SECUREBOOT: ENABLE
Warranty Bit: 1
Bootloader AP SWAEV: 2
SW REV CHECK FAIL : Fused 2 > Binary 1"
Here's my story:
My phone was displaying "No error" in Google Play Store. So I factory reset my phone but it didn't resolve my problem. So I flashed a stock ROM and it failed. My device was 4.4.2 ROOTED before flashing a lower version. (Cannot remember the version number though.) Now it displays, "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." My phone, however, DOES go into Download mode but not the recovery mode. I tried to flash multiple times but ODIN kept on failing. I tried multiple USB cables, different USB ports, computers, and reinstalled USB drivers, etc. However ODIN keeps on failing. I tried to recover it through KIES but it will not detect my device. I am thinking about sending this into Mobiletechvideos.com but I heard some devices could not be restored because of EMMC failure. Do you think my device's emmc failed? (I spent 200 bucks on this and do not wanna buy another one )
Soooo..
Is there anything I can do before I send it into mobiletechvideos.com for 50 bucks?
I've tried this http://forum.xda-developers.com/show....php?t=1840030 but it didn't work because I couldn't find Sprint bootchain. Does anyone have one for Sprint?
I'm also trying to use this method http://forum.xda-developers.com/show....php?t=2369125 but do you think it will work? (I don't have a SD card so I can't try just yet.) It was meant for hardbricked people. But mine is not completely bricked. It turns on and goes into DL mode.
** I've just noticed some signs of hardbrick. WITHOUT my battery and I hook my phone up to my PC with a USB cable, it shows that Red LED light and vibrates. Doesn't turn on though. WITH the battery, it turns on and goes into DL mode. Is my phone hard bricked?**
SUMMARIZED QUESTIONS:
1) Is my phone hard bricked?
2) Do you think JTAG can fix my phone? My phone may be in Read only state. Wouldn't that prevent the JTAG method?
3) Will the SD card method work?
4) Does anyone have Sprint bootchain? (I think my phone might be at Read Only state)
5) What are some signs of EMMC failure? I would really hate it if my phone had EMMC failure -_-
6) Did my phone brick because my phone was rooted and I flashed unrooted Sprint Stock ROM?
PLEASE PLEASE help me. Donations will be considered! (Really, I'm desperate to get my phone fixed. T_T )
Thank you alot in advance. Please leave replies if you need more information.

sdw8253 said:
Moderators, please delete my thread in Samsung Galaxy S III I9300, I9305
My phone: SPH-L710 Sprint Galaxy S3
This is what my ODIN says after trying to flash with stock ROM.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
This is what is on the top left corner in the DL mode.
"ODIN MODE
PRODUCT NAME: SPH-L710.
CUSTOM BINARY:Custom
SYSTEM STATUS:Custom
QUALCOM SECUREBOOT: ENABLE
Warranty Bit: 1
Bootloader AP SWAEV: 2
SW REV CHECK FAIL : Fused 2 > Binary 1"
Here's my story:
My phone was displaying "No error" in Google Play Store. So I factory reset my phone but it didn't resolve my problem. So I flashed a stock ROM and it failed. My device was 4.4.2 ROOTED before flashing a lower version. (Cannot remember the version number though.) Now it displays, "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again." My phone, however, DOES go into Download mode but not the recovery mode. I tried to flash multiple times but ODIN kept on failing. I tried multiple USB cables, different USB ports, computers, and reinstalled USB drivers, etc. However ODIN keeps on failing. I tried to recover it through KIES but it will not detect my device. I am thinking about sending this into Mobiletechvideos.com but I heard some devices could not be restored because of EMMC failure. Do you think my device's emmc failed? (I spent 200 bucks on this and do not wanna buy another one )
Soooo..
Is there anything I can do before I send it into mobiletechvideos.com for 50 bucks?
I've tried this http://forum.xda-developers.com/show....php?t=1840030 but it didn't work because I couldn't find Sprint bootchain. Does anyone have one for Sprint?
I'm also trying to use this method http://forum.xda-developers.com/show....php?t=2369125 but do you think it will work? (I don't have a SD card so I can't try just yet.) It was meant for hardbricked people. But mine is not completely bricked. It turns on and goes into DL mode.
** I've just noticed some signs of hardbrick. WITHOUT my battery and I hook my phone up to my PC with a USB cable, it shows that Red LED light and vibrates. Doesn't turn on though. WITH the battery, it turns on and goes into DL mode. Is my phone hard bricked?**
SUMMARIZED QUESTIONS:
1) Is my phone hard bricked?
2) Do you think JTAG can fix my phone? My phone may be in Read only state. Wouldn't that prevent the JTAG method?
3) Will the SD card method work?
4) Does anyone have Sprint bootchain? (I think my phone might be at Read Only state)
5) What are some signs of EMMC failure? I would really hate it if my phone had EMMC failure -_-
6) Did my phone brick because my phone was rooted and I flashed unrooted Sprint Stock ROM?
PLEASE PLEASE help me. Donations will be considered! (Really, I'm desperate to get my phone fixed. T_T )
Thank you alot in advance. Please leave replies if you need more information.
Click to expand...
Click to collapse
First thing, most of the time we moderators don't have time to go through every thread and post on XDA. Rather than asking us to delete a post in an obscure thread we may not see it would be helpful to us if you report it. I'm mobile right now so I can't do it but please report the other thread and make your request in the report.
Second, Odin isn't working because you're on a new bootloader. This one-click comes with the newest. Try flashing it. http://forum.xda-developers.com/showthread.php?t=2755793
Good luck!

If you were on KitKat 4.4.2 nd8 and tried to Odin the mk3 stock tar you've probably bricked your phone. Once on the nd8 boot loader and modem you cannot revert to an older version.
Many devs have bricked there phone with the new nd8 build.
I know I haven't answered all your w
Questions but I hope I've helped you understand what happened.
Luckily for you @rwilco12 has a solution for you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

FIXED!
I've been searching everywhere for a solution. Stupid Samsung and their Knox and their Kies (which fixes nothing)
I finally got it sorted!
1. Pull out the battery.
2. Reinsert the battery and force the phone into Download Mode. (Yes, I'm aware that the phone is unable to go anywhere else at this point; but when I fixed mine, I did it manually so that it displayed the Android droid logo, rather than the "Firmware upgrade encountered an issue..." message.
3. By now, you've probably tried every version under the sun. Try one more. It's an Odin package with the recovery image built-in. Assuming that you already have your Samsung drivers, download the executable from Step 3 of this guide: http://forum.xda-developers.com/showthread.php?t=2755793
4. Good luck! I'm just glad I finally fixed mine. Beware the OTA!

How do you force into download mode
badmojorayman said:
I've been searching everywhere for a solution. Stupid Samsung and their Knox and their Kies (which fixes nothing)
I finally got it sorted!
1. Pull out the battery.
2. Reinsert the battery and force the phone into Download Mode. (Yes, I'm aware that the phone is unable to go anywhere else at this point; but when I fixed mine, I did it manually so that it displayed the Android droid logo, rather than the "Firmware upgrade encountered an issue..." message.
3. By now, you've probably tried every version under the sun. Try one more. It's an Odin package with the recovery image built-in. Assuming that you already have your Samsung drivers, download the executable from Step 3 of this guide: http://forum.xda-developers.com/showthread.php?t=2755793
4. Good luck! I'm just glad I finally fixed mine. Beware the OTA!
Click to expand...
Click to collapse

sparks.calvin said:
How do you force into download mode
Click to expand...
Click to collapse
Press and hold down Volume down and Home button.
While holding both the above keys press and hold the power button, then you will see the disclaimer.
Let go of all the buttons and press Volume up to accept the disclaimer.
The phone goes directly into ODIN/Download mode right after this. You will see a green droid which indicates you’re in ODIN/Download mode.

sdw8253 said:
SUMMARIZED QUESTIONS:
1) Is my phone hard bricked?
2) Do you think JTAG can fix my phone? My phone may be in Read only state. Wouldn't that prevent the JTAG method?
3) Will the SD card method work?
4) Does anyone have Sprint bootchain? (I think my phone might be at Read Only state)
5) What are some signs of EMMC failure? I would really hate it if my phone had EMMC failure -_-
6) Did my phone brick because my phone was rooted and I flashed unrooted Sprint Stock ROM?
PLEASE PLEASE help me. Donations will be considered! (Really, I'm desperate to get my phone fixed. T_T )
Thank you alot in advance. Please leave replies if you need more information.
Click to expand...
Click to collapse
did you get it unbricked?
and answer to Question 6 like others have said it bricked cause you flashed MK3 or another older bootloader rom when you had ND8 if you notice on basically every sprint/boost/virgin post they state you can't go to a lower bootloader when on ND8 where did you hear you could flash a lower stock rom?

6th_Hokage said:
did you get it unbricked?
and answer to Question 6 like others have said it bricked cause you flashed MK3 or another older bootloader rom when you had ND8 if you notice on basically every sprint/boost/virgin post they state you can't go to a lower bootloader when on ND8 where did you hear you could flash a lower stock rom?
Click to expand...
Click to collapse
Yes. I got it unbricked ^_^
I flashed a new PIT file and it was unbricked!
I didn't hear that I could flash a lower stock ROM. I didn't know it was going to be bricked if I flashed with a lower stock rom.

sdw8253 said:
Yes. I got it unbricked ^_^
I flashed a new PIT file and it was unbricked!
I didn't hear that I could flash a lower stock ROM. I didn't know it was going to be bricked if I flashed with a lower stock rom.
Click to expand...
Click to collapse
ohhh okay well that's good; you got it sorted out

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

Okay, I was trying to flash back to original stock image which included all the bloatware and crap like that. Reason for going back was due to some mistake I made removing stuff I possibly shouldn't have (short sighted of me I know) and as a result got error 491 on google play and other stuff when I update. Removing the account to get rid of 491 doesn't work. So I figured flashing back to original stock would work.
I'm on AT&T with the Samsung Galaxy S3 (SGH-I747) on 4.4.2 downgrading to 4.1.1 and then will upgrade from that point on.
The Android system recovery says this is a KOT49H.I747UCUFNE4
I loaded up Odin 3.09, got I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 loaded in AP and hit go. Then I run into this:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I747UCDLK3_I747ATTDLK3_I747UCDLK3_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On the phone, it says "SW REV CHECK FAIL : Fused 3 > Binary 0".
Currently I'm downloading 4.3 which is taking it's precious time. However I'm not too confident that this might work. Reason being is http://www.androidayos.com/samsung-galaxy-s3-stock-firmware/ says that it won't work. So I've been trying to figure out how to completely restore back to a 100% default stock image of 4.4.2 undoing the stuff I've done.
Alternatively, I'm out of ideas and really like to get my phone fixed.
Any help or suggestions would be appreciated.

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

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

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

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

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

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

Right on! Glad to hear you fixed it!

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?

SM-T210R Bricked; Odin won't work

Hello, I hope you are having a good day,
I have a SM-T210R (Galaxy Tab 3 WiFi) that is bricked. It was not leaving the "Galaxy Tab 3" screen at boot-up and I determined that it was bricked. I looked at other forums on fixing a bricked tablet with the stock ROM and they didn't work AFTER I attempted to use Odin when it disconnected. At first, it seemed like it was working in Odin, but it said that my device had disconnected in the middle of the operation. The message that it now displays after it turns on, says that there was an error in updating and that it needs to be updated with Kies (I have tried both the recovery and updating it. The connection screen on it just appears and disappears and it doesn't recognize the device in recovery.) Now, if it even gets to this point, I keep getting to "Write NAND start" and then it tells me that there was a write error. Is there any way that I could possibly fix my device? I am using Odin3 v1.85 and I have tried other versions too, but this was the recommended one. I also have to uninstall the device and disconnect it every time I try. The
It is an old device and there is not much point to fixing it. It would be nice if I could fix it, but I understand if it can't be fixed.
Thank you.
EDITED

freonman said:
Hello, I hope you are having a good day,
I have a SM-T210R (Galaxy Tab 3 WiFi) that is bricked. I looked at other forums on this topic and they didn't work AFTER I attempted to use Odin. At first, it seemed like it was working in Odin, but it said that my device had disconnected. Because of this, I keep getting to "Write NAND start" and then a write error. Is there any way that I could possibly fix my device? I am using Odin3 v1.85.
It is an old device and there is not much point to fixing it. It would be nice if I could fix it, but I understand if it can't be fixed.
Thank you.
Click to expand...
Click to collapse
Odin can be finicky. I suggest trying a different USB cable. Post back and let me know. Also, not sure what your initial problem was, but I did quite a bit of work on the 210R and quite a few people still tinker with them. We should be able to get you going as long as the hardware is still working properly.
Sent from my LM-Q720 using Tapatalk

RealWelder said:
Odin can be finicky. I suggest trying a different USB cable. Post back and let me know. Also, not sure what your initial problem was, but I did quite a bit of work on the 210R and quite a few people still tinker with them. We should be able to get you going as long as the hardware is still working properly.
Click to expand...
Click to collapse
I have now tried multiple cables and computer ports and it did the same thing. Now, it says there is no PIT partition. I found one online and it does nothing.

I have something for you to try I just have to find it. In my time creating a custom ROM for this device I bricked it a bunch of times. I was always able to get it back though. One of the times it bricked it did exactly as you were describing. The kies software doesn't do anything anymore, but when the tab is on that screen ODIN will work. One of the times I bricked it, it was due to shrinking the system partition. When the partition was the incorrect size, stock ROM files would fail. I made a fix for it that saved me twice and might save you... But I have to see if I still have it. I think it's on my Google drive, though.
Sent from my LM-Q720 using Tapatalk

RealWelder said:
I have something for you to try I just have to find it. In my time creating a custom ROM for this device I bricked it a bunch of times. I was always able to get it back though. One of the times it bricked it did exactly as you were describing. The kies software doesn't do anything anymore, but when the tab is on that screen ODIN will work. One of the times I bricked it, it was due to shrinking the system partition. When the partition was the incorrect size, stock ROM files would fail. I made a fix for it that saved me twice and might save you... But I have to see if I still have it. I think it's on my Google drive, though.
Click to expand...
Click to collapse
Thank you. I wish you luck!

I can't find the file I was looking for, but I think if you flash TWRP through Odin and then boot into TWRP we can fix it. I'll link the TWRP to try flashing with Odin.
TWRP
https://drive.google.com/file/d/11EI-n_P47W6L8JM1-9wQWKv_tQq9A15V/view?usp=drivesdk
Report back and we'll keep going down the rabbit hole until we hit wonderland. If it successfully flashes TWRP you will have to hold vol+, power, and home until it goes off and into recovery.
Sent from my LM-Q720 using Tapatalk

RealWelder said:
I can't find the file I was looking for, but I think if you flash TWRP through Odin and then boot into TWRP we can fix it. I'll link the TWRP to try flashing with Odin.
TWRP
https://drive.google.com/file/d/11EI-n_P47W6L8JM1-9wQWKv_tQq9A15V/view?usp=drivesdk
Report back and we'll keep going down the rabbit hole until we hit wonderland. If it successfully flashes TWRP you will have to hold vol-, power, and home until it goes off and into recovery.
Sent from my LM-Q720 using Tapatalk
Click to expand...
Click to collapse
I have to tell you, it now boots in ODIN mode every time, with this message; "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". Also, I tried the file in the BOOTLOADER and the PDA section and neither worked. Is there something I'm missing?
(This is the try in BOOTLOADER)
<ID:0/004> Added!!
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Can't open the specified file. (Line: 1992)
<OSM> All threads completed. (succeed 0 / failed 1)

freonman said:
I have to tell you, it now boots in ODIN mode every time, with this message; "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.". Also, I tried the file in the BOOTLOADER and the PDA section and neither worked. Is there something I'm missing?
Click to expand...
Click to collapse
NVM had that backwards. I'm thinking of what to try next.
Sent from my LM-Q720 using Tapatalk

RealWelder said:
I'm not sure if this will actually help or not, but PDA was a slot in older versions of Odin. On the newer versions it is AP. Which version are you using? Maybe a newer version will pass.
Sent from my LM-Q720 using Tapatalk
Click to expand...
Click to collapse
I tried a newer version as well. ODIN3 V.1.85 is what I was recommended for KitKat.

What does it do when you have it powered off and use the button combination to try to get to recovery? (vol+, home, and power) Does it still just load to Odin? Also if you don't use any buttons and it goes into Odin, I think the drivers don't work right. Try using vol-, home, and power. It will still go into download mode, but it might allow Odin to see it correctly.
Sent from my LM-Q720 using Tapatalk

<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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)

RealWelder said:
What does it do when you have it powered off and use the button combination to try to get to recovery? (vol+, home, and power) Does it still just load to Odin? Also if you don't use any buttons and it goes into Odin, I think the drivers don't work right. Try using vol-, home, and power. It will still go into download mode, but it might allow Odin to see it correctly.
Sent from my LM-Q720 using Tapatalk
Click to expand...
Click to collapse
It does the same "Firmware upgrade encounter an issue..." thing, whether or not I hold the ODIN mode buttons down. But, I got a new thing;
<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> recovery.img
<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)
It almost looked like it had worked. Do you have any ideas yet?

freonman said:
It does the same "Firmware upgrade encounter an issue..." thing, whether or not I hold the ODIN mode buttons down. But, I got a new thing;
Odin v.3 engine (ID:4)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
SingleDownload.
recovery.img
NAND Write Start!!
FAIL!
Complete(Write) operation failed.
All threads completed. (succeed 0 / failed 1)
It almost looked like it had worked. Do you have any ideas yet?
Click to expand...
Click to collapse
That does look like it almost worked. If we could get to TWRP or even get a rooted shell we could manually flash. Do you have adb and everything setup on your PC? If so try adb shell. If adb doesn't work I'd keep trying to flash the stock firmware and the TWRP back and forth. I feel like if I had it in front of me I could figure it out. Don't give up on it.
Also does it just have stock recovery?
Sent from my LM-Q720 using Tapatalk

RealWelder said:
That does look like it almost worked. If we could get to TWRP or even get a rooted shell we could manually flash. Do you have adb and everything setup on your PC? If so try adb shell. If adb doesn't work I'd keep trying to flash the stock firmware and the TWRP back and forth. I feel like if I had it in front of me I could figure it out. Don't give up on it.
Also does it just have stock recovery?
Sent from my LM-Q720 using Tapatalk
Click to expand...
Click to collapse
I have ADB setup on my computer, but there are no "List of devices attached".
And yes, it does have the stock recovery.

Picture for visualization
{
"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"
}

freonman said:
I have ADB setup on my computer, but there are no "List of devices attached".
And yes, it does have the stock recovery.
Click to expand...
Click to collapse
I just had thought. Which firmware are you trying to flash? This device originally came with JB but got a KK upgrade. When it did the bootloader also got updated. You might try flashing stock 4.2 and see if it will pass. If it does then you can upgrade to 4.4. A few people ran into issues flashing my ROM because they were still on the old bootloader.
Also, I'll link my ROM's thread and you can post your issue there also. There's quite a few people that follow my thread and they might be able to help. I haven't messed with the device in 2 years and I forget a lot of the intimate details.
https://forum.xda-developers.com/galaxy-tab-3/development-7/rom-release-t210r-t3510449/amp/
Sent from my LM-Q720 using Tapatalk

RealWelder said:
I just had thought. Which firmware are you trying to flash? This device originally came with JB but got a KK upgrade. When it did the bootloader also got updated. You might try flashing stock 4.2 and see if it will pass. If it does then you can upgrade to 4.4. A few people ran into issues flashing my ROM because they were still on the old bootloader.
Also, I'll link my ROM's thread and you can post your issue there also. There's quite a few people that follow my thread and they might be able to help. I haven't messed with the device in 2 years and I forget a lot of the intimate details.
https://forum.xda-developers.com/galaxy-tab-3/development-7/rom-release-t210r-t3510449/amp/
Sent from my LM-Q720 using Tapatalk
Click to expand...
Click to collapse
I can't find a JB tar.md5 file for it. I tried to convert a .img file that was JB to tar.md5, and that didn't work. It did the same exact thing as the TWRP and the KK tar.md5.