Develop Bugs

[Q] What does this mean ?

I have recently purchased my Nexus it was working fine but i got this screen yesterday while booting. I tired to connect it to my PC but no luck all it does is tells me that the drivers failed to install. I called up google, they didn't know how to help me. They told me to take it back to the place i bought it. I tried looking for this type of error no luck.
Can someone help me out with this please ? Thanks.
{
"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"
}

You're missing the kernel and/or recovery. What did you try to flash that failed?

sorry never seen that particular screen. Besides rebooting what have you done to the phone? mods? etc....

Xleogun said:
I have recently purchased my Nexus it was working fine but i got this screen yesterday while booting. I tired to connect it to my PC but no luck all it does is tells me that the drivers failed to install. I called up google, they didn't know how to help me. They told me to take it back to the place i bought it. I tried looking for this type of error no luck.
Can someone help me out with this please ? Thanks.
View attachment 1170297
Click to expand...
Click to collapse
That screen means your bootloader got corrupt somehow. You need to re-flash your device to stock using Odin. Assuming you have a GSM device, see this thread for details. Note that since your bootloader is corrupt, you can't boot into "odin mode", but Odin will download the images to your device if you are booted to the screen you are currently showing.

efrant said:
That screen means your bootloader got corrupt somehow. You need to re-flash your device to stock using Odin. Assuming you have a GSM device, see this thread for details. Note that since your bootloader is corrupt, you can't boot into "odin mode", but Odin will download the images to your device if you are booted to the screen you are currently showing.
Click to expand...
Click to collapse
Thank you for your quick response i will read up on this try it out.

efrant said:
That screen means your bootloader got corrupt somehow. You need to re-flash your device to stock using Odin. Assuming you have a GSM device, see this thread for details. Note that since your bootloader is corrupt, you can't boot into "odin mode", but Odin will download the images to your device if you are booted to the screen you are currently showing.
Click to expand...
Click to collapse
It's not the bootloader, it's the kernel and/or recovery. I had the same screen on my Charge with a failed flash of the kernel, same with a failed recovery flash. I would also recommend using fastboot over Odin as it is generally "safer".

imnuts said:
It's not the bootloader, it's the kernel and/or recovery. I had the same screen on my Charge with a failed flash of the kernel, same with a failed recovery flash. I would also recommend using fastboot over Odin as it is generally "safer".
Click to expand...
Click to collapse
Not sure about the Charge, but I have tried wiping my kernel and recovery previously, and have never seen that screen. From other users experiences on the Galaxy Nexus, that screen appears when the bootloader is corrupt, so the phone cannot load up anything.
As for your recommendation to use fastboot (instead of Odin), how can you use fastboot when you can't boot into fastboot mode?

efrant said:
Not sure about the Charge, but I have tried wiping my kernel and recovery previously, and have never seen that screen. From other users experiences on the Galaxy Nexus, that screen appears when the bootloader is corrupt, so the phone cannot load up anything.
As for your recommendation to use fastboot (instead of Odin), how can you use fastboot when you can't boot into fastboot mode?
Click to expand...
Click to collapse
Wiping the kernel or recovery is different then a failed flash of kernel or recovery. Wiping recovery just writes '0's to the partition in all likelihood. As far as the phone knows, it was successfully flashed, even if it doesn't boot.
As for not getting into bootloader mode, if you can't boot due to a corrupted bootloader, how are you booting into download mode? The phone is still booting, just to a different system. I would guess that if you can access download mode, you can access bootloader mode. Hold both volume keys while turning on the phone and you should get to bootloader mode where you can use fastboot. Volume down plus power is download mode.
EDIT: I've also seen users on the Stratosphere, Continuum, and Fascinate (all Samsung phones) that had a failed Odin flash (usually recovery, sometimes kernel) and when the phone restarted, that was the screen it was left on.

imnuts said:
Wiping the kernel or recovery is different then a failed flash of kernel or recovery. Wiping recovery just writes '0's to the partition in all likelihood. As far as the phone knows, it was successfully flashed, even if it doesn't boot.
Click to expand...
Click to collapse
Well, I disagree with that - I do not think the device knows the difference from a bunch of zeros or half a kernel flash.
imnuts said:
As for not getting into bootloader mode, if you can't boot due to a corrupted bootloader, how are you booting into download mode? The phone is still booting, just to a different system. I would guess that if you can access download mode, you can access bootloader mode. Hold both volume keys while turning on the phone and you should get to bootloader mode where you can use fastboot. Volume down plus power is download mode.
Click to expand...
Click to collapse
But that's the whole point: on a GNex, if you see that screen, you can't boot into download mode or into the bootloader. You can only boot into that particular screen. However, Odin still pushes the files to your device when in that screen.
If you're right and he can still boot into the bootloader, then I agree, he should use fastboot over Odin. But I don't think he can.
Sent from my Galaxy Nexus using Tapatalk 2

Xleogun said:
I have recently purchased my Nexus it was working fine but i got this screen yesterday while booting. I tired to connect it to my PC but no luck all it does is tells me that the drivers failed to install. I called up google, they didn't know how to help me. They told me to take it back to the place i bought it. I tried looking for this type of error no luck.
Can someone help me out with this please ? Thanks.
View attachment 1170297
Click to expand...
Click to collapse
If you take out the battery, put it back in, and hold volume +, volume -, and power, what does your phone do?

jordancrockett said:
If you take out the battery, put it back in, and hold volume +, volume -, and power, what does your phone do?
Click to expand...
Click to collapse
nothing it doesn't go into recovery.

Xleogun said:
nothing it doesn't go into recovery.
Click to expand...
Click to collapse
As I had figured, your bootloader is corrupt - when that happens, that is the only screen you will see. You need to use Odin to re-download the stock images to your devices.

efrant said:
As I had figured, your bootloader is corrupt - when that happens, that is the only screen you will see. You need to use Odin to re-download the stock images to your devices.
Click to expand...
Click to collapse
Thanks, any idea where i would find the stock images ?
I did follow instructions on this thread [http://forum.xda-developers.com/showthread.php?t=1586807 but now it's showing a blank screen.
it showed my this message after the process was completed.
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/007> Added!!
<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> bootloader.img
<ID:0/007> NAND Write Start!!
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img
<ID:0/007> userdata.img
<ID:0/007> radio.img
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/007> Removed!!

Xleogun said:
Thanks, any idea where i would find the stock images ?
I did follow instructions on this thread [http://forum.xda-developers.com/showthread.php?t=1586807 but now it's showing a blank screen.
it showed my this message after the process was completed.
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/007> Added!!
<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> bootloader.img
<ID:0/007> NAND Write Start!!
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img
<ID:0/007> userdata.img
<ID:0/007> radio.img
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/007> Removed!!
Click to expand...
Click to collapse
Based on what you posted, that was a successful Odin flash. Are you saying when you reboot, you don't see anything at all anymore?
The files you flashed were the stock images.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Based on what you posted, that was a successful Odin flash. Are you saying when you reboot, you don't see anything at all anymore?
The files you flashed were the stock images.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
yeah just blank and when I plug the device into my PC it told me drivers failed to install.
hmm okay. yeah I used stock IMM76D ROM.
Maybe i bricked it...

Xleogun said:
yeah just blank and when I plug the device into my PC it told me drivers failed to install.
hmm okay. yeah I used stock IMM76D ROM.
Maybe i bricked it...
Click to expand...
Click to collapse
Strange. I have never seen that before after a successful Odin flash.
Regardless, you have one other option before I would consider it bricked: OMAP Flash. I don't have the thread handy, but search for OMAPFlash_tuna.zip
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
Strange. I have never seen that before after a successful Odin flash.
Regardless, you have one other option before I would consider it bricked: OMAP Flash. I don't have the thread handy, but search for OMAPFlash_tuna.zip
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I found the download link to it.
I tried finding a guide to follow but i don't see any posted.

Xleogun said:
I found the download link to it.
I tried finding a guide to follow but i don't see any posted.
Click to expand...
Click to collapse
I believe the instructions are included in a text file within the zip.

imnuts said:
It's not the bootloader, it's the kernel and/or recovery. I had the same screen on my Charge with a failed flash of the kernel, same with a failed recovery flash. I would also recommend using fastboot over Odin as it is generally "safer".
Click to expand...
Click to collapse
I borked a kernel flash last night and didn't get that screen. I got as far as the boot animation then it just stays there. I just pushed the kernel through fastboot to get out

[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

N7100 stuck on Samsung Screen

Please please can someone help?
I'll start at the beginning; I have a galaxy note 2 (n7100) in the UK, unlocked for use on any network. I have had this phone from new.
I rooted the phone about a year ago and installed twrp recovery I also installed a script that would allow me to swap the internal memory with the external memory.
Everything has been fine for about 8 months and then the other day I went to switch on my phone and it froze on the screen where I put my pin number in, I didn’t think much about it and turned the phone off & on, but now it just sits at the “Samsung galaxy note 2” screen.
I have booted into twrp and that is telling me there is “No Operating system installed”, it also will not allow me to browse the external SD card.
I have tried to reflash the stock rom using ODIN and everything appears to work and I get the “PASS” sign up, but the phone refuses to boot!!
Also when I boot into twrp it asks me to enter a password, I have never set a password so I'm baffled as to what this is?
And one last thing is that when I plug the phone into the charger with the phone switched off, the battery symbol appears on the screen but it just has a little circle in the battery and doesn’t show the battery charging animation.
I have just tried to flash a PIT file and now can no longer get into TWRP recovery, it seems to be going from bad to worse.
Please can someone help?
Pete

peter7769 said:
Please please can someone help?
I'll start at the beginning; I have a galaxy note 2 (n7100) in the UK, unlocked for use on any network. I have had this phone from new.
I rooted the phone about a year ago and installed twrp recovery I also installed a script that would allow me to swap the internal memory with the external memory.
Everything has been fine for about 8 months and then the other day I went to switch on my phone and it froze on the screen where I put my pin number in, I didn’t think much about it and turned the phone off & on, but now it just sits at the “Samsung galaxy note 2” screen.
I have booted into twrp and that is telling me there is “No Operating system installed”, it also will not allow me to browse the external SD card.
I have tried to reflash the stock rom using ODIN and everything appears to work and I get the “PASS” sign up, but the phone refuses to boot!!
Also when I boot into twrp it asks me to enter a password, I have never set a password so I'm baffled as to what this is?
And one last thing is that when I plug the phone into the charger with the phone switched off, the battery symbol appears on the screen but it just has a little circle in the battery and doesn’t show the battery charging animation.
I have just tried to flash a PIT file and now can no longer get into TWRP recovery, it seems to be going from bad to worse.
Please can someone help?
Pete
Click to expand...
Click to collapse
why did you use a pit file? anyway. if you flashed stock with odin there souldn't have been remained any TWRP.
reflash without pit file. after that boot in stock recovery and wipw data/factory reset. phone should boot up.
if all fails, (jope not) use this http://forum.xda-developers.com/showthread.php?t=2088809

mariosraptor said:
why did you use a pit file? anyway. if you flashed stock with odin there souldn't have been remained any TWRP.
reflash without pit file. after that boot in stock recovery and wipw data/factory reset. phone should boot up.
if all fails, (jope not) use this http://forum.xda-developers.com/showthread.php?t=2088809
Click to expand...
Click to collapse
i used pit file as last resort, i have tried everything else, i was thinking the same as you in that if i flashed custom rom then it should be custom recovery, ODIN says passed when its finished but something is obviously going wrong somewhere.
Thanks
Pete
i have tried the link you suggested but the phone wont connect with Kies, i have all the drivers installed but still wont connect

Well even though ODIN says its flashing and passed its not working, i have just tried for the 3rd time flashing a stock ROM, it said it had passed but its still booting into TWRP, and i cant do anything from within TWRP, firstly it ask for my password, if i press cancel then it goes to the main screen, but that's it.
if i look in the log file it just keeps saying
E: unable to find partition size for boot
E: unable to find partition size for recovery
etc
also
Unable to mount /efs
Unable to mount /cache
Unable to mount /system
etc

peter7769 said:
Well even though ODIN says its flashing and passed its not working, i have just tried for the 3rd time flashing a stock ROM, it said it had passed but its still booting into TWRP, and i cant do anything from within TWRP, firstly it ask for my password, if i press cancel then it goes to the main screen, but that's it.
if i look in the log file it just keeps saying
E: unable to find partition size for boot
E: unable to find partition size for recovery
etc
also
Unable to mount /efs
Unable to mount /cache
Unable to mount /system
etc
Click to expand...
Click to collapse
try this rescue firmware. also close all kies running apps from task manager prior to opening ODIN
http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5

mariosraptor said:
try this rescue firmware. also close all kies running apps from task manager prior to opening ODIN
http://forum.xda-developers.com/showpost.php?p=32273406&postcount=5
Click to expand...
Click to collapse
Thanks, but the hotfile links are dead
i managed to find a link further on, d/l and tried it but still no joy im afraid, ODIN said it had all passed but nothing was written to the phone!!

peter7769 said:
Thanks, but the hotfile links are dead
Click to expand...
Click to collapse
https://www.4shared.com/zip/814t0y9A/N7100XXDLJ2_OXA_FACTORY.html

mariosraptor said:
https://www.4shared.com/zip/814t0y9A/N7100XXDLJ2_OXA_FACTORY.html
Click to expand...
Click to collapse
Thanks, but as you can see from my post above it didn't work :crying:

what do you mean? this is from 4shared not hotfile

mariosraptor said:
what do you mean? this is from 4shared not hotfile
Click to expand...
Click to collapse
no we are getting crossed wires, your original link sent me to download a rescue package from Hotfile, this no longer works.
but i managed to find another link further in the post that did work, i downloaded that and tried it but still had no success.
i have now downloaded your file from 4shared, and when i try and add all the various parts into Odin and click start, i get a message saying "Failed", this happens almost instantly.
any suggestions?
Pete

peter7769 said:
no we are getting crossed wires, your original link sent me to download a rescue package from Hotfile, this no longer works.
but i managed to find another link further in the post that did work, i downloaded that and tried it but still had no success.
i have now downloaded your file from 4shared, and when i try and add all the various parts into Odin and click start, i get a message saying "Failed", this happens almost instantly.
any suggestions?
Pete
Click to expand...
Click to collapse
first, are you closing any Kies remaining tasks from task manager?
second. what does it say when you are in donload mode? write all here

mariosraptor said:
first, are you closing any Kies remaining tasks from task manager?
second. what does it say when you are in donload mode? write all here
Click to expand...
Click to collapse
Hi
i have unistalled KIES as the phone wouldnt connect, no matter what usb port i tried, but i have kept the samsung drivers.
When i go into download mode i get this..
ODIN MODE
PRODUCT NAME - GT-N7100
CUSTOM BINARY DOWNLOAD: YES (2 COUNTS)
CURRENT BINARY:CUSTOM
SYSTEM STATUS:CUSTOM
like i said before it seems like nothing is being written to the phone, i even tried to flash the latest version of TWRP to the phone via ODIN, it passed but when i booted into recovery it still showed the old version number within TWRP
Pete

peter7769 said:
Hi
i have unistalled KIES as the phone wouldnt connect, no matter what usb port i tried, but i have kept the samsung drivers.
When i go into download mode i get this..
ODIN MODE
PRODUCT NAME - GT-N7100
CUSTOM BINARY DOWNLOAD: YES (2 COUNTS)
CURRENT BINARY:CUSTOM
SYSTEM STATUS:CUSTOM
like i said before it seems like nothing is being written to the phone, i even tried to flash the latest version of TWRP to the phone via ODIN, it passed but when i booted into recovery it still showed the old version number within TWRP
Pete
Click to expand...
Click to collapse
1. Try to flash the stock firmware.
2. If it bootloops, try to access recovery.
3. If didn't work, try to flash custom recovery such as philz touch
4. Try factory reset, wipe cache and dalvik cache.
Let us know if it works

iamjerbergerber said:
1. Try to flash the stock firmware.
2. If it bootloops, try to access recovery.
3. If didn't work, try to flash custom recovery such as philz touch
4. Try factory reset, wipe cache and dalvik cache.
Let us know if it works
Click to expand...
Click to collapse
Have you even read what he wrote? He did all those things but despite Odin reporting success, nothing in the phone was altered.
@peter7769 - what Odin version are you using? Is it started as Administrator? What is the driver version that is reported in Device Manager when you connect the phone? Can you uninstall Kies and try again to flash Samsung firmware (not custom one)?

mat9v said:
Have you even read what he wrote? He did all those things but despite Odin reporting success, nothing in the phone was altered.
@peter7769 - what Odin version are you using? Is it started as Administrator? What is the driver version that is reported in Device Manager when you connect the phone? Can you uninstall Kies and try again to flash Samsung firmware (not custom one)?
Click to expand...
Click to collapse
Thanks, like you said i have tried everything that iamjerbergerber suggested and nothing works,
i have tried using ODIN 3.07 & 3.09 as admin, what am are looking for in the device manager?, i can only see SAMSUNG Mobile USB CDC Composite Device listed under USB controllers, and SAMSUNG Mobile USB Modem listed under modems.
i have already tried the stock firmware which i got from SAMmobile but still no joy, i have been reading up that people said something has happened to the read/write permissions and that is why nothing is being flashed to the phone, though i cant understand why ODIN reports a PASS, as soon as i flash and go into TWRP is firstly asks for my password (never set one!) and then tells me no operating system installed.
Pete

Also i do get failed messages on ODIN when i try to flash anything but the PDA & PIT File Boxes.
Just trying to give you as much info as i can.
Pete

Just flashed stock firmware, all passed but same result
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7100XXDMB2_N7100OXXDMB2_N7100XXDLK7_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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> tz.img
<ID:0/003> system.img
<ID:0/003> boot.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> recovery.img
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

peter7769 said:
Thanks, like you said i have tried everything that iamjerbergerber suggested and nothing works,
i have tried using ODIN 3.07 & 3.09 as admin, what am are looking for in the device manager?, i can only see SAMSUNG Mobile USB CDC Composite Device listed under USB controllers, and SAMSUNG Mobile USB Modem listed under modems.
i have already tried the stock firmware which i got from SAMmobile but still no joy, i have been reading up that people said something has happened to the read/write permissions and that is why nothing is being flashed to the phone, though i cant understand why ODIN reports a PASS, as soon as i flash and go into TWRP is firstly asks for my password (never set one!) and then tells me no operating system installed.
Pete
Click to expand...
Click to collapse
What driver version are you using? This one (look at included screenshot)?
{
"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"
}
From the listing you provided, the Odin behaves well. What happens after it reboots the system (Auto reboot and F.reset time are enabled, yes?)
Does the first window at the top print PASS! on green color with time underneath?
As I understand you tried to flash recovery with Odin? Could you try Philz recovery flashable from Odin, can be downloaded from HERE
You know, this message from TWRP stating that it can't locate partitions may mean you flashed an invalid PIT file...
Attached is a PIT file I have used in times of 4.1.2 firmware flash when I hosed my system.
Also PIT can be flashed ONLY with full system flash or you may loose EFS (along with IMEI) and that would be a disaster without correct backup.

mat9v said:
What driver version are you using? This one (look at included screenshot)?
View attachment 2601488
From the listing you provided, the Odin behaves well. What happens after it reboots the system (Auto reboot and F.reset time are enabled, yes?)
Does the first window at the top print PASS! on green color with time underneath?
As I understand you tried to flash recovery with Odin? Could you try Philz recovery flashable from Odin, can be downloaded from HERE
You know, this message from TWRP stating that it can't locate partitions may mean you flashed an invalid PIT file...
Attached is a PIT file I have used in times of 4.1.2 firmware flash when I hosed my system.
Also PIT can be flashed ONLY with full system flash or you may loose EFS (along with IMEI) and that would be a disaster without correct backup.
Click to expand...
Click to collapse
Thanks again for the help so far, firstly yes auto reboot is enabled and the other one, when the phone reboots it just sticks on the Samsung GT-N7100 screen and doesn't move, yes the window is green with PASS on it, although i cant recall seeing a time.
as for the driver it says driver date 02/01/2014 and version 2.11.7.0
i will try the pit file and philz recovery in a while as im just updating some stuff on the pc.
i will report back with the results.
Pete

Hi
one question i forgot to ask, when i flash the pit file do i have a tick in the Re-partition box, or should i leave it blank?
Thanks again
Pete

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