Develop Bugs

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

[RECOVERY][Galaxy Light T399] TWRP 2.7.1.0 Touch Recovery

Based on the latest version of TWRP's source code (Jul 16, 2014) & Galaxy Light's kernel (UANE4)
https://github.com/omnirom/android_bootable_recovery
Theme by z31s1g
{
"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"
}
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
Click to expand...
Click to collapse
HOW TO INSTALL
1- Download TWRP's file from the link below.
2- Download Odin 3.
3-Turn off your device and and boot into DOWNLOAD MODE by holding the Volume Down+Home+Power. Then Press Volume UP.
4-Run Odin and Make sure that only “Auto Reboot” option is selected.
5-Connect your device to your computer via a USB cable. (You should see “Added!” text at the message box of Odin GUI.)
6-Click the "PDA" OR "AP" (Odin v3.09) button and select TWRP's file (extension tar.md5).
7-Press the "Start" Button to begin the installation process.
8-Wait to see the "PASS!" message.
Click to expand...
Click to collapse
Download Link:
MOD EDIT: dev-host link removed, known for having mallware and other dirty redirects.
Special Thanks to:
TeamWin
@Dees_Troy
@z31s1g
@Modding.MyMind Theme's porter
anyone else ?

My script for porting the ui.xml is just about finished. Only one issue that I need to resolve and it will be ready. Will post it on my github in due time. Great work .

Modding.MyMind said:
My script for porting the ui.xml is just about finished. Only one issue that I need to resolve and it will be ready. Will post it on my github in due time. Great work .
Click to expand...
Click to collapse
Keep up your great work :good:

@[email protected] said:
Keep up your great work :good:
Click to expand...
Click to collapse
Make sure you read the README.md files on my repo for further details.
https://github.com/ModdingMyMind/TWRP_IMAGE_PORTER
Sent from my C525c using Tapatalk

t399n
will this work with the metro pcs t399n variant?

Yes
---------- Post added at 03:25 PM ---------- Previous post was at 03:24 PM ----------
tatico28 said:
will this work with the metro pcs t399n variant?
Click to expand...
Click to collapse
Yes

root t399n 4.4.2
what about a root method for t399n on 4.4.2?

Either twrp will do it for you, or download su.zip, simple google search will find it

tazmaniondvl said:
Either twrp will do it for you, or download su.zip, simple google search will find it
Click to expand...
Click to collapse
Thanks mate!

I can't mount the external SD card in recovery from the Galaxy Light.
Is that a known problem with TWRP for this device? Or is something funky on my phone?

I just got this phone metropcs about a week. Been tempted to install a custom recovery. Anything that I should know about?

i got a new metro galaxy light (sgh-t399) and it says its NK3, but veryone else seems to be on different kernels, i know on my galaxy s4, after they locked it down on kitkat with knox, itll just softbrick and no recovery willr emain if you try and odin/goo twrp...how can i get this thing AT LEAST rooted..towelroot didnt work.

I am starting to realize that. I think the bootloader is now locked
Kernel version
3.4.39-2903595
Fri Nov 7 10:51 KST 2014
That's probably what got updated. I got the phone in Oct. The days of android being open are over. I think Samsung is taking note from moto and LG. Those phone are notorious for having locked bootloaders.

<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> openrecovery-twrp-2.7.1.0-gardaltetmo.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..
Doesnt seem to work, tried different cables....how can i just get root...towelroot wont work....i dont care about recovery atm.

zak7 said:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> openrecovery-twrp-2.7.1.0-gardaltetmo.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..
Doesnt seem to work, tried different cables....how can i just get root...towelroot wont work....i dont care about recovery atm.
Click to expand...
Click to collapse
Did you boot your phone in download mode first. Won't work if it's not.

So, has anyone confirmed that this works on the latest version, after the most recent update? I am using a metro pcs version of this phone, and want it rooted... am on the latest kernal update.

DrGreenLeaf said:
So, has anyone confirmed that this works on the latest version, after the most recent update? I am using a metro pcs version of this phone, and want it rooted... am on the latest kernal update.
Click to expand...
Click to collapse
It works you need to use Odin version 3.9 as stated. It failed to flash with older versions. Once I flashed this one I rooted and manually installed mine I built.

Unjustified Dev said:
It works you need to use Odin version 3.9 as stated. It failed to flash with older versions. Once I flashed this one I rooted and manually installed mine I built.
Click to expand...
Click to collapse
Am pretty sure i have odin 3.0 i use a netbook to flash my phones, and the newer version of odin doesn't fit my screen. I am not able to move the control panel around to see the button to start the flash. I had to downgrade to version 3.0 then it fits on my screen.... i think i may be hosed... am gonna pick up an extra galaxy light tomorrow, then will start flashing. Thanks, may have more questions for you after tomorrow.

Unjustified Dev said:
It works you need to use Odin version 3.9 as stated. It failed to flash with older versions. Once I flashed this one I rooted and manually installed mine I built.
Click to expand...
Click to collapse
You mean 3.0, right? I just flashed your 2.8.1.0 and it's working fine.
DrGreenLeaf said:
Am pretty sure i have odin 3.0 i use a netbook to flash my phones, and the newer version of odin doesn't fit my screen. I am not able to move the control panel around to see the button to start the flash. I had to downgrade to version 3.0 then it fits on my screen.... i think i may be hosed... am gonna pick up an extra galaxy light tomorrow, then will start flashing. Thanks, may have more questions for you after tomorrow.
Click to expand...
Click to collapse
@M3gaBit3 thinks that the latest firmware update might have locked the bootloader. Downgrade to the previous version via Odin and you should be able to flash TWRP.

Planterz said:
You mean 3.0, right? I just flashed your 2.8.1.0 and it's working fine.
Click to expand...
Click to collapse
I was actually referring to my version of odin. But it's 1.85.
My issue is that I'm using my netbook to flash my phones. The control panel(window) for odin 3.9 or later doesn't fit my netbooks display.. i can't move it on my screen to get to all the buttons, i cant initiate the flash....

[Q] Soft bricked Note 2 I317m

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

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

any news? I have exactly same problem.

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

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

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