Develop Bugs

Boot loop frozen ??

I gave my sister a S2 for her account. rooted Jellybean installed. its been fine for the last 6 months or so.
now its stuck at the 4G logo screen or constantly reboots itself back to the 4G screen.
I tried holding vol up and power to "wipe" the device but it errors displaying this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Suggestions?
I THINK she may have tried to install some sort of update accidentally (something I specifically told her not to do) she says it said something about some update and then rebooted and swears she did not install one.
so I really have no clue what actually happened.
suggestions? what can I do to recover this bugger.?
I was able to get into download mode. so I want to odin in a rom.
WHAT do I odin in? I HAD jellybean installed but I have NO CLUE what "SHE" may have installed.
what is "safe" to odin over? step by step would be nice I have done quite a bit of flashing but always by "directions" never "on the fly" on my own
I AM NOT certain but I THINK this is what I had installed
http://forum.xda-developers.com/showthread.php?t=2191954
and is what I am downloading now.
suggestions? does this seem like the right procedure?

nerys71 said:
I gave my sister a S2 for her account. rooted Jellybean installed. its been fine for the last 6 months or so.
now its stuck at the 4G logo screen or constantly reboots itself back to the 4G screen.
I tried holding vol up and power to "wipe" the device but it errors displaying this
Suggestions?
I THINK she may have tried to install some sort of update accidentally (something I specifically told her not to do) she says it said something about some update and then rebooted and swears she did not install one.
so I really have no clue what actually happened.
suggestions? what can I do to recover this bugger.?
I was able to get into download mode. so I want to odin in a rom.
WHAT do I odin in? I HAD jellybean installed but I have NO CLUE what "SHE" may have installed.
what is "safe" to odin over? step by step would be nice I have done quite a bit of flashing but always by "directions" never "on the fly" on my own
I AM NOT certain but I THINK this is what I had installed
http://forum.xda-developers.com/showthread.php?t=2191954
and is what I am downloading now.
suggestions? does this seem like the right procedure?
Click to expand...
Click to collapse
That screenshot is due to her having stock android recovery, not custom recovery. The link you sent is good to Odin. Dave the tar to your computer, put computer in download mode, flash tar. Good luck...btw, you said s2, make sure it's epic 4g touch before you flash that sucker(sph-d710).
Sent from my SPH-D710BST using xda premium

Yes the SPRINT epic 4g touch D710.
so is that what happened? she installed some sort of update that whacked the recovery as well?
my concern was I know you have to do something "different" when going between ginger and jelly. my fear is she installed some ginger update?? (I have no idea what the "stock" firmware for this is
connection is slow right now downloading the 500mb file. Grrrr
anyway to flat out DISABLE updates ?

nerys71 said:
Yes the SPRINT epic 4g touch D710.
so is that what happened? she installed some sort of update that whacked the recovery as well?
my concern was I know you have to do something "different" when going between ginger and jelly. my fear is she installed some ginger update?? (I have no idea what the "stock" firmware for this is
connection is slow right now downloading the 500mb file. Grrrr
anyway to flat out DISABLE updates ?
Click to expand...
Click to collapse
Lol....I believe there is. I know there was for ICS. It was a zip called otakill I believe. Flashing that stock rom should be fine. And if she had custom recovery before, and ran an update, it flashed over the custom, that's what I would think . You have to partition between gb and jb custom roms, but that rom you are flashing should be fine. If you run into issues, let me know. Good luck.
Sent from my SPH-D710BST using xda premium

ok got the file downloaded. phone in download mode. open one click. plug in usb cable. got yellow box 0:[COM25]
click start and I get this and it just stops
<ID:0/025> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> boot.bin
<ID:0/025> cache.img
I know its a big file but even if we assume usb 1.0 speeds it should be done by now. how do I know if its working or not? how long should it take?

You are flashing an entire jb stock ROM..it takes a little bit. I would give it awhile. And the last time I flashed a one click it didn't take the first time. If it doesn't take after a considerable amount of time, say 10 minutes, download the tar again, and try the new download. Sometimes you get a bad download, but pc Odin a Rom takes a bit, be patient
Sent from my SPH-D710BST using xda premium

its been sitting their since 0835 that is 40 minutes. Can't redownload right now will have to try later. I downloaded the self extracting which should alleviate "bad download" concerns since it should fail to extract if its a bad download.
will redownload later and see what happens.

nerys71 said:
its been sitting their since 0835 that is 40 minutes. Can't redownload right now will have to try later. I downloaded the self extracting which should alleviate "bad download" concerns since it should fail to extract if its a bad download.
will redownload later and see what happens.
Click to expand...
Click to collapse
Hmmm...that's odd. Maybe you need to start from scratch, stock unrooted, before you try to flash rooted. If it doesn't take next time, that's what I'd do. I know you're doing this anyway(hopefully), but make sure you read all of the OPs, watch the recommended videos, etc. Good luck man.
Sent from my SPH-D710BST using xda premium

no joy. downloaded the bone stock tar md5 file
odin 3 under pda
same thing. stops at cache.img
<ID:0/025> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SPH-D710_GB27_1014481_Stock_Restore.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/025> Odin v.3 engine (ID:25)..
<ID:0/025> File analysis..
<ID:0/025> SetupConnection..
<ID:0/025> Initialzation..
<ID:0/025> Get PIT for mapping..
<ID:0/025> Firmware update start..
<ID:0/025> boot.bin
<ID:0/025> NAND Write Start!!
<ID:0/025> cache.img
what do I do?

Try flashing a one click instead of a tar. And if that hangs up, try flashing just a custom recovery. If that takes, you can get into cwm and flash a zip version of the rom.
Sent from my SPH-D710 using xda premium

I was running jelly bean. what is the correct recovery to odin?
I already tried flashing a bone stock tar via odin (after trying the one click) same result. stalls at cache.img
uhhh these 500mb downloads are killing me hehe
which specific zip do you suggest? and which recovery tar ?

nerys71 said:
I was running jelly bean. what is the correct recovery to odin?
I already tried flashing a bone stock tar via odin (after trying the one click) same result. stalls at cache.img
uhhh these 500mb downloads are killing me hehe
which specific zip do you suggest? and which recovery tar ?
Click to expand...
Click to collapse
Dl a stock jb zip, gb27 will work. If it flashes in recovery, you won't have cwm, but that's ok, we'll cross that bridge when we get to it. And use stock el26 cwm tar by chris41g. If it flashes in Odin, it may reboot to Samsung logo, that's ok, just reboot to recovery.
Sent from my SPH-D710 using xda premium

ok I am grabbing this rom now
http://forum.xda-developers.com/showthread.php?t=2224230 (3 hours to download)
and using this CWM
http://forum.xda-developers.com/showthread.php?p=24987585
grabbing the GB08 modem from here
http://forum.xda-developers.com/showthread.php?t=1764210
and the agate63 source kernel from here
http://forum.xda-developers.com/showthread.php?t=1662295
I just tried to odin the StockCWM-EL26.tar.md5
stops at
<ID:0/017> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> StockCWM-EL26.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> zImage
<ID:0/017> NAND Write Start!!
Grrrrr now what ?
I tried re booting to recovery anyway thinking maybe it worked. no joy
says Firmware upgrade encountered an issue please select recovery mode in kies & try again
when I try to boot into recovery.

You're still able to get into download mode correct?
If you can get to download mode do the following:
Uninstall kies and Samsung drivers,Download ODIN 1.85 from here and install it (the newer versions have been known to fail flashes on occasion), plug your usb cable into pc not the phone, open ODIN and navigate to PDA (like you did before) and open, choose the GB27 tar file. Make sure that repartition is NOT checked, now connect your phone and wait for the com light to come on, once it lights up press start.
Now the reason I suggest this yet again is because you're trying to flash from ODIN v3+, Kies and Odin are known to conflict sometimes, and the repartition box will always cause issues without a pit file (these are dangerous to play with if you're not familiar with them)
It's unusual, but not unheard of, for a one click would fail. If all else fails, and this doesn't work for you, please post the exact model number under the battery of your device, so that we can determine if there are any discrepancies.

ok got 1.85 from your link. I do not have kies installed. I uninstalled the samsung drivers but now windows sits at install drivers and odin never see's the phone (of course I just removed the drivers that LET it see the phone ???) what was supposed to happen?
ahh interesting. unplugged it and plugged it in again and this time odin saw the phone (I guess it installed some sort of driver ??)
but no joy. same result.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> E4GT-EL29-directbootCWM-v3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
stops here.
Model number SPH-D710
Sprint Epic 4g Touch (S2)

nerys71 said:
ok got 1.85 from your link. I do not have kies installed. I uninstalled the samsung drivers but now windows sits at install drivers and odin never see's the phone (of course I just removed the drivers that LET it see the phone ???) what was supposed to happen?
ahh interesting. unplugged it and plugged it in again and this time odin saw the phone (I guess it installed some sort of driver ??)
but no joy. same result.
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> E4GT-EL29-directbootCWM-v3.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
stops here.
Model number SPH-D710
Sprint Epic 4g Touch (S2)
Click to expand...
Click to collapse
OK, do you happen to have another cable to try? Or perhaps another usb port on your pc?
Slithering from the nether regions of a twisted mind and tarnished soul

so far I have tried 4 pc's and 3 USB cables. never a change in results. 3 running xp 1 running windows 7
2 of these pc's have flashed this very phone in the past.
1 cable is my orange cable and the other 2 are stock samsung cable both good quality cables.
I can look for more cables but that does not seem to be the issue here.
dug up a 4th cable. no joy. no change.

nerys71 said:
so far I have tried 4 pc's and 3 USB cables. never a change in results. 3 running xp 1 running windows 7
2 of these pc's have flashed this very phone in the past.
1 cable is my orange cable and the other 2 are stock samsung cable both good quality cables.
I can look for more cables but that does not seem to be the issue here.
dug up a 4th cable. no joy. no change.
Click to expand...
Click to collapse
Man, what got flashed? LOL
OK, you're able to get to Odin mode, the PC recognized your device, but install fails as soon as it begins to write the images...
4 cables one of them should have worked if that was the issue, and several different pc's...
Reinstalling drivers didn't do anything...
Different version of Odin...
I assume you've verified md5?
Have you tried other downloads, or the same file?
Maybe try flashing say, FL24 with Odin, then the GB27. If FL24 flashes then you know its the GB27 thats failing. Where are you grabbing your download from?
Slithering from the nether regions of a twisted mind and tarnished soul

I posted the links in the other thread. I got them from here on xda forums threads.
I have tried a tar a one click a cwm and a direct boot cwm. md5 validated.
I will try an older kernel and see what happens.

nerys71 said:
I posted the links in the other thread. I got them from here on xda forums threads.
I have tried a tar a one click a cwm and a direct boot cwm. md5 validated.
I will try an older kernel and see what happens.
Click to expand...
Click to collapse
Try this link http://www.sxtpdevelopers.com/showthread.php?t=166 download that tar and try flashing it

Can't boot into recovery mode... Bricked?

I've got a sprint GS3 that is rooted and has the clockwork recovery mod on it, but was otherwise running stock OS. It had been acting up, hanging, that kind of thing so I decided to go ahead and accept the download new software prompt I've had for the last year or so. When it went to the bootimage(?) menu it asked if I wanted to install this untrusted image. That gave me pause, so I selected no. The little android icon got a red X-ish thing on it's chest and it rebooted. And sat at the samsung galaxy s3 screen for about a half an hour. I pulled the power and it kept going between hanging at that screen, or hanging at random points (app 6, 8, 9, 11) of an "upgrading android" screen I have never seen before. I tried going into the recovery mode but when I follow the instructions (up vol, home and power, when it vibrates for power release the power button) but that doesn't work at all. It just sits there. I'm 100% certain it's not a button/physical issue. I decided to try the download option and can get to a screen that warns me about custom rom. I've tried both installing (let it go for over an hour, gave up) and hitting cancel, to no avail. Before I take this as a sign from the android gods that it's time to go get a GS5, does anyone have any ideas/advice? TIA.

You tried to install an OTA over your rooted ROM. that is the only thing wrong. This is a sign from the Android Gods that you need to read more. Either reinstall your custom recovery and flash a ROM or download the tar of the Android version you want (ND8, MK3, MD4, etc) and run that through Odin. Either one will fix your 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"
}

bilgerryan said:
You tried to install an OTA over your rooted ROM. that is the only thing wrong. This is a sign from the Android Gods that you need to read more. Either reinstall your custom recovery and flash a ROM or download the tar of the Android version you want (ND8, MK3, MD4, etc) and run that through Odin. Either one will fix your problem
Click to expand...
Click to collapse
By fix the problem, I assume that I'm going to lose anything that was on the phone (not much, most is backed up via various utilities)? If so, I think I may go the path of least resistance and just get a new phone.

OK, found this which seems to indicate I may be able to salvage data. Thanks for pointing me in the correct direction. :good:

I've got a followup question, if you don't mind. I've followed the instructions in the referenced article and Odin is reporting the following:
<ID:0/008> 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/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> sbl2.mbn
<ID:0/008> NAND Write Start!!
I went to lunch, so I don't know how long it's been on the NAND Write Start!! but it's going on about 2.5 hours from when I clicked start and the process started going. The top left box is white and outputs SBL2. Should I continue to wait or start thinking something is broken/hung at this point? TIA!

Just updating the thread in case I can (a) solve the problem and (b) folks find it useful.
I have tried Odin 3.07, 1.87 and 1.83 to no success. They all seem to fail in about the same way, either at sbl2.mbn or at NAND Write Start!!. Waiting anywhere from 10-30 minutes doesn't seem to change anything. I've tried different cables and USB ports. I don't have another computer to try. Currently researching whether I should try to include the PIT file and if doing so will result in data loss.

wnoonan said:
By fix the problem, I assume that I'm going to lose anything that was on the phone (not much, most is backed up via various utilities)? If so, I think I may go the path of least resistance and just get a new phone.
Click to expand...
Click to collapse
Well if that's the easier option, send me the S3 lol.

bilgerryan said:
Well if that's the easier option, send me the S3 lol.
Click to expand...
Click to collapse
Well, at some point you cut your losses. At this point I've spent the better part of 7 hours trying to get the phone recovered in some fashion. Multiple versions of Odin. Multiple USB cables. Multiple USB ports. Currently installing the Samsung USB drivers on another PC to try it all from there. I'll admit it, I'm not a cell phone developer (I'm a data center guy, want to know how to setup DFI, why you use FabricPath, what ACI is, why you use a pVC, how to setup OTV, etc. I'm your guy). I don't know the in's and outs of what a PIT file is, what it means when the phone just sits there at NAND Write Start!! and does nothing, and I can't seem to find an answer. Every article I can find seems to indicate I'm doing exactly what I'm supposed to be doing, but nothing works. I'm certainly open to ideas, but so far I'm not getting anywhere really.

And FWIW, I just fired up Odin3 v1.85 up on a totally different PC, with yet another totally different USB cable (so I'm not 0 for 2 on PC's, 0 for 3 on cables) and it's the same result. Starts the firmware update, sbl2.mbn goes, the next message is NAND Write Start!! but no progress is made and in the top left box, it's simply white with "SBL2". Clearly something isn't write, but just as clearly I'd be danged if I can figure out what it is.

bilgerryan, a question if you don't mind. You said "Either reinstall your custom recovery and flash a ROM or download the tar of the Android version you want (ND8, MK3, MD4, etc) and run that through Odin." I have to confess, I have no idea what ND8, MK3, MD4, etc are, but at the QBKing77 link he mentioned a TAR file at a hotfile.com location, but that link appears to be dead. So I subsequently (after doing more reading in more threads) went here to grab what I presume is a valid TAR file, which I then extracted into a MD5 file. Odin seems to find it to be valid, but again it never seems to update. Any ideas? TIA!

OK. If anyone else happens to run across this thread, here are the things I attempted:
cf auto root chainfire - didn't work. It actually seemed like it was trying to copy, but would stop about halfway and never finish.
Tried the following ROM's. None of them would get past the NAND Write Start:
L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME.tar.md5
KIES_HOME_L710VPBMD4_L710SPRBMD4_1130792_REV03_user_low_ship.tar.md5
L710VPUCMK3_L710SPRCMK3_L710VPUCMK3_HOME.tar.md5
L710VPUCND8_L710SPRCND8_L710VPUCND8_HOME.tar.md5
Tried multiple PC's, cables, ports, you name it.
Currently the phone won't even power on anymore. Not sure if the battery is just dead (tried another old battery, same result) or if the phone is just outright dead.
If this happens to you and you can figure out how to recover, you're a better man than I. Near as I can tell it's pretty much a total loss when this happens.
HTH.

[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

No Pit partition Problem

Hi every one any help will be greatlly apreciated. First what happened we'll shut down and stuck at Galaxy Note II Screen and restarting itself until it stops frozen at the Galaxy Note II Screen. Was working fine for a couple months after my last flash froze some times but battery pull fixed it before. Now I can not get into CWM Recovery So I tried flashing factory rom with Odin I get this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.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)
Tried mutiple times tried F.Reset Time checked. Any Ideas guy's. wife's phone have to get it working if you know what I meen. Thank's for any help. Hope the nands not corupt. Had a International S3 I9300 with that problem. Would like to save this and not shell out the money for a MBoard.

kennethcolman said:
Hi every one any help will be greatlly apreciated. First what happened we'll shut down and stuck at Galaxy Note II Screen and restarting itself until it stops frozen at the Galaxy Note II Screen. Was working fine for a couple months after my last flash froze some times but battery pull fixed it before. Now I can not get into CWM Recovery So I tried flashing factory rom with Odin I get this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.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)
Tried mutiple times tried F.Reset Time checked. Any Ideas guy's. wife's phone have to get it working if you know what I meen. Thank's for any help. Hope the nands not corupt. Had a International S3 I9300 with that problem. Would like to save this and not shell out the money for a MBoard.
Click to expand...
Click to collapse
in download mode does it say n7100 in product code?
what you need to do if you will be using a pit file is use a factory emergency rom. sadly most the links are down.
i have a MJ9 Emergency rom from india which is 4.3. i will try upload it when i get home in 8 to 9 hours to mega.nz if that is ok.
what i have done is replaced the MJ9 bootloader with MJ5 in that firmware.
if you can't wait, you need a firmware that has BL,AP, CP and CSC all split so you can put them in all the boxes. if i get a chance at lunch i might try find a pre uploaded link for you. just remain calm and don't start flashing stuff randomly

I have searched and searched online and cant seem to nail down a solution to this issue.
My Download Screen displays:
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
I hope that my Note II is not bricked. I have tried 100's of times with stock, custom recovery's, CWM, I get some kind of error no matter what I do.
my Sammy just doesn't want to work with me.
I hope that we can put together a solution.

El_Nino9 said:
in download mode does it say n7100 in product code?
what you need to do if you will be using a pit file is use a factory emergency rom. sadly most the links are down.
i have a MJ9 Emergency rom from india which is 4.3. i will try upload it when i get home in 8 to 9 hours to mega.nz if that is ok.
what i have done is replaced the MJ9 bootloader with MJ5 in that firmware.
if you can't wait, you need a firmware that has BL,AP, CP and CSC all split so you can put them in all the boxes. if i get a chance at lunch i might try find a pre uploaded link for you. just remain calm and don't start flashing stuff randomly
Click to expand...
Click to collapse
Thanks I am very patient. Oh and yes it says GT-N7100 in product code under warranty bit: 1 binary:yes status: custom under binary download: Yes (6 counts)

Teckin said:
I have searched and searched online and cant seem to nail down a solution to this issue.
My Download Screen displays:
ODIN MODE
PRODUCT NAME: GT-N7100
CUSTOM BINARY DOWNLOAD: NO
CURRENT BINARY: SAMSUNG OFFICIAL
SYSTEM STATUS: CUSTOM
I hope that my Note II is not bricked. I have tried 100's of times with stock, custom recovery's, CWM, I get some kind of error no matter what I do.
my Sammy just doesn't want to work with me.
I hope that we can put together a solution.
Click to expand...
Click to collapse
kennethcolman said:
Thanks I am very patient. Oh and yes it says GT-N7100 in product code under warranty bit: 1 binary:yes status: custom under binary download: Yes (6 counts)
Click to expand...
Click to collapse
to both you guys:- what bootloader are you on/were you on? Kenneth I think you've taken your bootloader above MJ5 as you say your warranty bit is 1. you can't downgrade bootloader at all! flashing the MJ5 bootloader with the file I've uploaded won't help. you will only get FAIL in odin. you need to tell me which bootloader you've been to so I can try arrange a package for you if I can.
Teckin, I need you to answer the above too

El_Nino9 said:
to both you guys:- what bootloader are you on/were you on? Kenneth I think you've taken your bootloader above MJ5 as you say your warranty bit is 1. you can't downgrade bootloader at all! flashing the MJ5 bootloader with the file I've uploaded won't help. you will only get FAIL in odin. you need to tell me which bootloader you've been to so I can try arrange a package for you if I can.
Teckin, I need you to answer the above too
Click to expand...
Click to collapse
First off thanks for your help. Here's the deal I had this installed: DN3_v3.2_by_E-Team_(Vegeta_Edition) Thats a Jelly Bean for the past 2 month's so what ever bootloader works with that is what it had. I was tying to flash an OEM KK: BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar I figured we'll since I have this problem let me flash DN5 but in oder to do this I would have to upgrade my bootloader KK that's why I flashed this BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.tar Now I say again The problem was not a result of flashing. My wife was using Skype while on the DN3 and it froze she pushed the wake button once or twice it went black and then gave the reboot logo that I mentioned above. So then I proceeded to try to flash to fix and upgrade in the process. And it gave me the odin results above No PIT Partition

https://mega.co.nz/#!5ZlXFbrR!GoNuuuDwKrp3QG8X7p4eV5v5ViOZR51kXgTtcptkGBo
here's the file I've uploaded.
you may well still have taken the device to MJ5 only.
flash all files in here at the same time using odin. let me know how you get on?
I find this method works best for me:
phone is off, load odin, load all the files in, pit, bl, ap, cp, csc no messing around with any ticking other boxes. AP will probably cuase odin to crash for a few seconds when loading just let it do its thing.
then put phone into download mode( I put battery in hold down, menu and power) if the drivers have been installed using that port previous it finds the device in odin instantly and i start the process.
If your flash is successful but doesn't load rom, your data might need to be wiped. i mean if your device is has been stuck on a Samsung screen for 10 minutes after odin said everythings fine don't panic. take battery out, go into recovery (volume up+menu+power) and then wipe data. it should now load the rom.

El_Nino9 said:
https://mega.co.nz/#!5ZlXFbrR!GoNuuuDwKrp3QG8X7p4eV5v5ViOZR51kXgTtcptkGBo
here's the file I've uploaded.
you may well still have taken the device to MJ5 only.
flash all files in here at the same time using odin. let me know how you get on?
I find this method works best for me:
phone is off, load odin, load all the files in, pit, bl, ap, cp, csc no messing around with any ticking other boxes. AP will probably cuase odin to crash for a few seconds when loading just let it do its thing.
then put phone into download mode( I put battery in hold down, menu and power) if the drivers have been installed using that port previous it finds the device in odin instantly and i start the process.
If your flash is successful but doesn't load rom, your data might need to be wiped. i mean if your device is has been stuck on a Samsung screen for 10 minutes after odin said everythings fine don't panic. take battery out, go into recovery (volume up+menu+power) and then wipe data. it should now load the rom.
Click to expand...
Click to collapse
Thanks but no prize.
Download and tried it Failed
Odin Said this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N7100XXUEMJ5_1903221_REV04_user_low_ship.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_N7100DDEMJ9_REV08_CL1423182.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_ODD_N7100ODDEMK1_2099172_REV04_user_low_ship.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_N7100XXUEMK4_2099172_REV04_user_low_ship.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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Do you think I should check erase nand I won't do it till some body who I trust tells me I should don't want things worse.

Ok so here is the deal on my GT-N7100. I bought it this way, but have not been able to flash it back to stock to start from scratch. so to answer your question, I have NO CLUE.
Seller told me that It would only boot into dl screen with usb...So I thought hmm I can re-flash it with stock software and move forward from that point.
Thank you all for the suggestions!

Teckin said:
Ok so here is the deal on my GT-N7100. I bought it this way, but have not been able to flash it back to stock to start from scratch. so to answer your question, I have NO CLUE.
Seller told me that It would only boot into dl screen with usb...So I thought hmm I can re-flash it with stock software and move forward from that point.
Thank you all for the suggestions!
Click to expand...
Click to collapse
you can try the above files if you want.
kennethcolman said:
Thanks but no prize.
Download and tried it Failed
Odin Said this:
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Do you think I should check erase nand I won't do it till some body who I trust tells me I should don't want things worse.
Click to expand...
Click to collapse
don't click erase.
mate i think you've flashed a new bootloader than MJ5 hence why it fails at that stage.
i am checking to see if i can get hold of a kitkat rom for you that's split to so you can flash pit.
i have never tried it with kitkat mate. plus i don't use odin to flash anymore. i use my octoplus box so files are in a .oct format
Sorry for delay in replying.
again i think youhave a newer bootlaoder if it shows warranty bit.

El_Nino9 said:
you can try the above files if you want.
don't click erase.
mate i think you've flashed a new bootloader than MJ5 hence why it fails at that stage.
i am checking to see if i can get hold of a kitkat rom for you that's split to so you can flash pit.
i have never tried it with kitkat mate. plus i don't use odin to flash anymore. i use my octoplus box so files are in a .oct format
Sorry for delay in replying.
again i think youhave a newer bootlaoder if it shows warranty bit.
Click to expand...
Click to collapse
I have a buddy who has a box would that be the safest rout?

kennethcolman said:
I have a buddy who has a box would that be the safest rout?
Click to expand...
Click to collapse
i dont think it makes a difference to be honest as i think it just uses the same type of way to push it.
i have a silly question to ask you.
what happens if you flash http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7100//philz_touch_6.41.6-n7100.tar.md5
in ap only without pit ofcourse.
does odin allow you to do this?

El_Nino9 said:
i dont think it makes a difference to be honest as i think it just uses the same type of way to push it.
i have a silly question to ask you.
what happens if you flash http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n7100//philz_touch_6.41.6-n7100.tar.md5
in ap only without pit ofcourse.
does odin allow you to do this?
Click to expand...
Click to collapse
I believe I tried that same thing happened. Fail no pit partition

kennethcolman said:
I believe I tried that same thing happened. Fail no pit partition
Click to expand...
Click to collapse
what box has your mate got?
check this thread out if he has a z3x (wish i had got that instead of octoplus)
http://forum.xda-developers.com/galaxy-s3/general/samsung-s3-i9300-note2-n7100-i9500-s4-t2647558
i have found PIT_N7100XXUENA1_N7100OJVENA1_N7100XXUENA3_Taiwan_Android_4.3
which includes all the files an oct file. if your mate has another box he might be able to find something similar along the lines?

I tried that file as well. Still same issue. I did talk with a guy that does jtag services and he advised me that it's either the eMMC or motherboard issue. He wants to sell me a eMMC Flash service for $75.00. What do you guys think I should do....
---------- Post added at 10:32 PM ---------- Previous post was at 09:51 PM ----------
El_Nino9 said:
i dont think it makes a difference to be honest as i think it just uses the same type of way to push it.
i have a silly question to ask you.
what happens if you flash "goo.im/devs/philz_touch/CWM_Advanced_Edition/n7100//philz_touch_6.41.6-n7100.tar.md5"
in ap only without pit ofcourse.
does odin allow you to do this?
Click to expand...
Click to collapse
I will try this as well..

Did try that last file as well still no go...
Thank you all for your efforts.

El_Nino9 said:
what box has your mate got?
check this thread out if he has a z3x (wish i had got that instead of octoplus)
http://forum.xda-developers.com/galaxy-s3/general/samsung-s3-i9300-note2-n7100-i9500-s4-t2647558
i have found PIT_N7100XXUENA1_N7100OJVENA1_N7100XXUENA3_Taiwan_Android_4.3
which includes all the files an oct file. if your mate has another box he might be able to find something similar along the lines?
Click to expand...
Click to collapse
We're you able to find the KK files for the N7100 odin flashable? and a little off topic here but I have been dabbling with the idea of unlocking cells. I live in the Dominican Republic and cells here are mostly GSM wondering if you we're to purchase 3 box's to do the widest range of phones which 3 would you buy and from where? Sorry everybody for the off topic.

El_Nino9 said:
what box has your mate got?
check this thread out if he has a z3x (wish i had got that instead of octoplus)
http://forum.xda-developers.com/galaxy-s3/general/samsung-s3-i9300-note2-n7100-i9500-s4-t2647558
i have found PIT_N7100XXUENA1_N7100OJVENA1_N7100XXUENA3_Taiwan_Android_4.3
which includes all the files an oct file. if your mate has another box he might be able to find something similar along the lines?
Click to expand...
Click to collapse
I beleve I figured out why the Rescue Firmware you sent me didn't work. What I need is Android 4.3 MK9 Bootloader and Do you have this and if so can you upload it to me mega would be fine. Thanks Just like the other just MK9 Based with pit and etc. Thanks for all your earlier help I am pretty sure this wil work.

kennethcolman said:
I beleve I figured out why the Rescue Firmware you sent me didn't work. What I need is Android 4.3 MK9 Bootloader and Do you have this and if so can you upload it to me mega would be fine. Thanks Just like the other just MK9 Based with pit and etc. Thanks for all your earlier help I am pretty sure this wil work.
Click to expand...
Click to collapse
sorry for the lack of activity. deadlines for work have kept me away from here.
i have a MK4. i will send it to you now. i will hunt for MK9 in the mean time if MK4 fails. plus i'll answer your other question about boxes in few minutes.

Teckin said:
I tried that file as well. Still same issue. I did talk with a guy that does jtag services and he advised me that it's either the eMMC or motherboard issue. He wants to sell me a eMMC Flash service for $75.00. What do you guys think I should do....
---------- Post added at 10:32 PM ---------- Previous post was at 09:51 PM ----------
I will try this as well..
Click to expand...
Click to collapse
that's note a bad price for the service i'd say. they have to use a rework station to pull the emmc off and then reball the new one on. however i'd suggest you try flashing a new firmware on first. i will try to dig a new firmware out for you to try but if they keep failing then the only route is emmc and make sure they load a firmware below 4.3 knox free if you want custom roms again

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?