Develop Bugs

[Q] Unable to boot totall soft brick

Hello fellow nexus users! So here is my problem. I have flashed newest paranoid rom with newest franco kernel. (oc. ~1500mhz)
Yesterday, while listening to music my phone just freezed.
Ok, so I took the battery off to reboot, but I got bootloop at google logo so I tried to turn the CWM recovery mode,
but unfortunately instead of CWM i saw some weird noise on the screen and a bootloop again.
Next thing I tried is the fastboot mode and the download mode. Both are working so I connected phone to Nexus Toolbox.
Phone gets detected so I tried to install CWM. After couple seconds I get this message" (status read failed (too many links))" .
Same thin happens when I choose to install stock rom by toolbox. The only thing that still works is re-locking bootloader.
Next thing I tried is ODIN.
I downloaded clean 4.1.1 for ODIN from some other threat but still no luck.. It stucks after...
<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> boot.img
<ID:0/003> NAND Write Start!!
I tried two different types of odin and two different laptops to be shure. The same result on both. Any idead what else I can do?
Btw. everytime I start to flash Gnex by Odin, some weird noise appears on the screen of my phone

why does everyone use odin? USE FASTBOOT.

Because the toolbox option doesnt work for me either . I tried it first couple times with no luck

regzpl said:
Because the toolbox option doesnt work for me either . I tried it first couple times with no luck
Click to expand...
Click to collapse
Use Fastboot without the toolbox, as it was meant to be used.

just tried the command "fastboot flash system system.img" by the fastboot cmd. Still getting the same answer in the fastboot "(status read failed (too many links))". I even changed the drivers once again and still the same...

you did download the correct image for your phone?
yakju = GSM
mysid = vzw
mysidspr = sprint

100% correct yakju from the official google site.
Also used the guide and drivers from your signature.

regzpl said:
[snip] Still getting the same answer in the fastboot "(status read failed (too many links))".
Click to expand...
Click to collapse
This usually means that you need to: a) change your USB cable AND/OR b) plug USB cable into a different port on your PC AND/OR c) use the latest version of fastboot.exe

efrant said:
This usually means that you need to: a) change your USB cable AND/OR b) plug USB cable into a different port on your PC AND/OR c) use the latest version of fastboot.exe
Click to expand...
Click to collapse
...or KEEP READING.

Today im gonna try a 3rd fresh PC with fresh drivers and a different cable maybe this will help because two of the laptops I tried had the same result with 3 different USB cables.
Tried Kies today in download mode and the phone is connecting for like 10 mins with no luck... It's kinda weird cos I used the same cable, drivers and laptop to flash the CWM and root the phone for the first time a while ago and everything worked as a charm and that why Im so consfused about it.
btw. do you have any idea how this could happen that both the rom and the CWM had died on my device without any reason ?

regzpl said:
Today im gonna try a 3rd fresh PC with fresh drivers and a different cable maybe this will help because two of the laptops I tried had the same result with 3 different USB cables.
Tried Kies today in download mode and the phone is connecting for like 10 mins with no luck... It's kinda weird cos I used the same cable, drivers and laptop to flash the CWM and root the phone for the first time a while ago and everything worked as a charm and that why Im so consfused about it.
btw. do you have any idea how this could happen that both the rom and the CWM had died on my device without any reason ?
Click to expand...
Click to collapse
Kies is not supported on the GNex.
As for your question, I have no idea why it would have died.
Follow the return to stock guide sticky in the General section.

In cases like this it's always best to attempt to return to full stock by flashing the original google stock image. Download the Galaxy nexus toolkit for your version. Download the google stock image for your version, put the google stock image in the appropriate folder then follow the instruction set in the toolkit. This has always rescued me many times while experimenting with my GNex. Hope it helps you too.

ezeuba said:
In cases like this it's always best to attempt to return to full stock by flashing the original google stock image. Download the Galaxy nexus toolkit for your version. Download the google stock image for your version, put the google stock image in the appropriate folder then follow the instruction set in the toolkit. This has always rescued me many times while experimenting with my GNex. Hope it helps you too.
Click to expand...
Click to collapse
Using a toolkit is NOT the best option to return to stock. (It hides too many things from you.) The best option to return to stock is to do it yourself using something like this or equivalent.

I forgot to mention that on my previous rom I had avast security mobile installed with the anti thef module for rooted devices. In one option It had the ability to block usb port in case of flashing different rom is it possible that this can block my device from flashing?

efrant said:
Using a toolkit is NOT the best option to return to stock. (It hides too many things from you.) The best option to return to stock is to do it yourself using something like this or equivalent.
Click to expand...
Click to collapse
Some options may be better than others in certain circumstances. The method in your post while very comprehensive may not be for the faint-hearted. The OP does not seem to be very techwise about stuff like this, hence I suggested the toolkit for him.

ezeuba said:
Some options may be better than others in certain circumstances. The method in your post while very comprehensive may not be for the faint-hearted. The OP does not seem to be very techwise about stuff like this, hence I suggested the toolkit for him.
Click to expand...
Click to collapse
do not ever suggest a toolkit.
efrant, myself and other help people on this forum who have problems. do you know how many threads get created with the title "HALP MY PHONE IS BROKE" and the first line in the body of the thread is "i used such and such toolkit and now my phone wont work"

regzpl said:
I forgot to mention that on my previous rom I had avast security mobile installed with the anti thef module for rooted devices. In one option It had the ability to block usb port in case of flashing different rom is it possible that this can block my device from flashing?
Click to expand...
Click to collapse
If you use a toolkit you would be able to determine if your phone is recognised by the computer while in fastboot mode, or not.

After couple tries of installing stock rom I managed to crack fastboot lol. Now instead of fastboot I got the phone next to a traingle and a monitor picture. What does that mean?

Zepius said:
do not ever suggest a toolkit.
efrant, myself and other help people on this forum who have problems. do you know how many threads get created with the title "HALP MY PHONE IS BROKE" and the first line in the body of the thread is "i used such and such toolkit and now my phone wont work"
Click to expand...
Click to collapse
I am no Android god, just a normal person trying to help someone in need with something that has always worked for me. Pushing your methods as the best does not add to the value, I'm sure there are so many who would swear by your contributions to the forum in general, likewise other folks contributions. I'm not here to remove anything from your skills and knowledge, just trying to help by suggesting something that has always worked for me. Thank you.
---------- Post added at 03:50 PM ---------- Previous post was at 03:49 PM ----------
regzpl said:
After couple tries of installing stock rom I managed to crack fastboot lol. Now instead of fastboot I got the phone next to a traingle and a monitor picture. What does that mean?
Click to expand...
Click to collapse
Odin is your only friend now dude...

<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CODE_I9250XWKL2_user_ICL53F_163640.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..
cant get any further than this in Odin...

[Q] Just bricked my phone on 4.3

UPDATE** Resolved problem.
Hey guys,
I accidentally bricked my tmobile GS4.. I can't seem to get it back and running again. I've been using Odin3 v1.85 and the tmobile 4.3 stock rom. I put it in download mode, click "PDA" and try to flash the stock rom and I get this error:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> M919UVUEMK2_M919TMBEMK2_M919UVUEMK2_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> sbl2.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!!
<ID:0/004> Added!!
<ID:0/004> Removed!!
I'm worried now that I won't be able to get it back up and running again and that I've just blown through my warranty because of that whole knox deal.
Please help!
BTW - I download the stock rom that was in this forum for tmobile another member posted stating it was 4.3. Due to my post count I can't link yet, but the file name is M919UVUEMK2_M919TMBEMK2_TMB.zip

Try a newer version of Odin. Try 3.07 or 3.09
Are you using the original cable?
☞ Sent from here☜???

I've had this issue where Odin will repeatedly say Added, Removed, and then Added again. However, that normally happens when I've inserted it into a pc for the first time. Perhaps Windows was installing drivers and caused Odin to redetect the device midway through flashing. @OP, is this the first time you plugged your GS4 in Download Mode on the computer

baseballfanz said:
Try a newer version of Odin. Try 3.07 or 3.09
Are you using the original cable?
I've tried Odin3 V3.07 as well. Maybe I'll try 3.09 too?
Yes, I'm using the original cable.
☞ Sent from here☜???
Click to expand...
Click to collapse
Vigz said:
I've had this issue where Odin will repeatedly say Added, Removed, and then Added again. However, that normally happens when I've inserted it into a pc for the first time. Perhaps Windows was installing drivers and caused Odin to redetect the device midway through flashing. @OP, is this the first time you plugged your GS4 in Download Mode on the computer
Click to expand...
Click to collapse
No, it is not the first time :/ I'm starting to really worry now that I won't have my phone working by tomorrow for work :s
I'm really hoping I can get this thing up and running again. I think it all happened when I tried to install a zip to root my phone via CWM recovery. It was an old one for 4.2.2 and I'm not sure if it caused my phone to brick because I forgot I did an OTA update to 4.3.
Thanks for the help so far guys, Please keep it coming.

Fixed
Well, I'm feeling pretty stupid right now.. it WAS the cable. I wiggled it around I guess and there must be a short in it because it made another connection on my PC.
I got a different cable and, boom, headshot. She works now.
Thanks for all your help guys!

Wicked White said:
Well, I'm feeling pretty stupid right now.. it WAS the cable. I wiggled it around I guess and there must be a short in it because it made another connection on my PC.
I got a different cable and, boom, headshot. She works now.
Thanks for all your help guys!
Click to expand...
Click to collapse
Samsung cables just suck. They've had issues since day one. If you ever have issues with kies or Odin always try a different cable first. 95% of the time it's the stupid cable at fault.
Sent from my SGH-M919 using Tapatalk

Wicked White said:
Well, I'm feeling pretty stupid right now.. it WAS the cable. I wiggled it around I guess and there must be a short in it because it made another connection on my PC.
I got a different cable and, boom, headshot. She works now.
Thanks for all your help guys!
Click to expand...
Click to collapse
Yeah, mine is really flimsy too. I try not to move the cable when it's plugged in because I'm too cheap of a bastard to get new ones. Hue.

Who has the best cables?
Sent from my GT-I9505G using xda app-developers app

Lmax579 said:
Who has the best cables?
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
AmazonBasics is a good brand.

I've been using the cable from a ridiculously priced charger I had to buy at the Best Buy kiosk at the Airport made by iGO. It's a lot thicker cable then most and the micro USB really snaps firmly into the phone.
Sent from my SGH-M919 using Tapatalk

Note 2 wont move from Samsung screen! :eek:

Hey guys! So this is a bit out of my area since I dont have a GN2 (I have a GS4) but my Godson has a Galaxy Note 2 from Rogers. So when he turns it on, it just stays on the Samsung Screen and doesn't go on. He hasn't rooted it and doesn't put custom Roms on it. Does anyone have any ideas? Would putting the original software through odin work?
Any help would be appreciated
Thanks guys

Maybe try a factory reset first? Phone off, then volume up + home + power to go into recovery, clear user data.

Darkshado said:
Maybe try a factory reset first? Phone off, then volume up + home + power to go into recovery, clear user data.
Click to expand...
Click to collapse
Thanks for the reply! Tried that and nothing
Any other suggestions?

Did you try a firmware upgrade/restore with samsung kies?

Cryingmoose said:
Did you try a firmware upgrade/restore with samsung kies?
Click to expand...
Click to collapse
Yup i just tried it and its a no go I wonder what happens to this thing... Its completly stock...he just woke up one morning and bam it was like this...
Any other suggestions?

Try flashing with Odin, but it's looking like a hardware failure

KillerX1911 said:
Yup i just tried it and its a no go I wonder what happens to this thing... Its completly stock...he just woke up one morning and bam it was like this...
Any other suggestions?
Click to expand...
Click to collapse
Yep odin flash the stock firmware or just the recovery.img will fix the issue
Cryingmoose said:
Try flashing with Odin, but it's looking like a hardware failure
Click to expand...
Click to collapse
Sent from my SCH-I605 using XDA Premium 4 mobile app

Watch out you don't void the warranty
lacoursiere18 said:
Yep odin flash the stock firmware or just the recovery.img will fix the issue
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If it has never been rooted, I would be careful that you don't try something that voids your warranty since the failure so far has nothing to do with flashing firmware based on what you wrote. Personally, I would just bring it to the nearest service center at this point.

RichMD said:
If it has never been rooted, I would be careful that you don't try something that voids your warranty since the failure so far has nothing to do with flashing firmware based on what you wrote. Personally, I would just bring it to the nearest service center at this point.
Click to expand...
Click to collapse
Odin flashing Stock firmware does not void warranty.. its the samething they will do at the store..

lacoursiere18 said:
Odin flashing Stock firmware does not void warranty.. its the samething they will do at the store..
Click to expand...
Click to collapse
OK, thanks for the info - I just figured anything beyond using KIES or OTA could void the warranty

Odin-ing the "wrong" thing could trigger Knox or the download counter, but so long as you stick to the same or newer unmodified firmware (from places like sammobile, free to register, search for SGH-I317M with Rogers listed as carrier.) for your proper model you won't have any issues.
If you haven't already, consider booting with no microSIM or microSD card in the phone, if only to eliminate any possibilities of one being defective and freezing the phone.
By the way, when you're saying stuck at the "Samsung screen" are you referring to the white text on black background, or to the animated logo (and boot sound) playing over and over?
But yeah, if there's any warranty left on that thing (and maybe a bit beyond depending on your province's consumer laws) I'd send it to a service centre.

Thank you everyone with your responses!
Yeah theres no warranty so no need to worry about that... its the galaxy Note 2 so its just over its period.
Darkshado said:
Odin-ing the "wrong" thing could trigger Knox or the download counter, but so long as you stick to the same or newer unmodified firmware (from places like sammobile, free to register, search for SGH-I317M with Rogers listed as carrier.) for your proper model you won't have any issues.
If you haven't already, consider booting with no microSIM or microSD card in the phone, if only to eliminate any possibilities of one being defective and freezing the phone.
By the way, when you're saying stuck at the "Samsung screen" are you referring to the white text on black background, or to the animated logo (and boot sound) playing over and over?
But yeah, if there's any warranty left on that thing (and maybe a bit beyond depending on your province's consumer laws) I'd send it to a service centre.
Click to expand...
Click to collapse
I really don't think he cares about the counter as long as its working lol because right now its a very expensive paper weight.
White text on black screen, no sound.
Where would I find the correct firmware for this rogers phone?
Thanks again guys you have been great!

Sammobile. I flashed bell 4.4 this morning with Odin 3.09 and had no issues
Sent from my SGH-I317M using XDA Free mobile app

OK so this is weird...so today out of the blue I do power home and up and it send me to downloading...please wait with the android staring at me. But it doesn't give me any options
So any other ideas

So back at her today, I downloaded kies 3, nothing, it didnt even recognize it. So I went back to normal old kies so at least I hear it connecting ( but it just goes around in circles saying connecting, so I guess it never connects).
I also download the new Odin (and tried the old Odin) and it connects if Kies is open but doesnt let me connect in Odin Mode... anyone think this is a driver problem? This is what Odin shows when I connect and try to put the firmware on
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I317MVLUDNF1_I317MOYADNF1_I317MVLUDNF1_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>
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)

You do have to install the official drivers from Samsung.
Also make sure to try Odin with kies uninstalled and using the official USB cable that came with the phone (I've personally see guides recommend this, not sure why, but I've gone along with it)
You can also try redownloading the image if it still doesn't work (happened to me once, wouldn't flash, deleted the file, got it again and then it worked)
Sent from my Nexus 7 using XDA Free mobile app

Funny all the weird voodoo some people do when it comes to flashing their phones... next thing someone's going to mention lucky socks or something.
Any good USB cable will do.
Kies tends to interfere with Odin, simply shutting it down (services included) will suffice.
The Kies install package contains up to date drivers for adb and download modes, and unless you extract that installer yourself (not that hard) you're not going to install the drivers without Kies.
Odin images ending in .tar.md5 have an MD5 hash appended at the end of the tarball and Odin uses that to check the file's integrity. It won't even flash if there's corruption, leaving your phone unharmed.
And last but not least, do not confuse download (volume down + home + power, or adb reboot download, or a USB "jig" with the proper resistive short) with recovery mode (volume up instead). Recovery mode often has options available, such as "clear user data" whereas download mode only displays information and requires a computer to flash.
Sent from my XT1045 using XDA Free mobile app

KillerX1911 said:
Hey guys! So this is a bit out of my area since I dont have a GN2 (I have a GS4) but my Godson has a Galaxy Note 2 from Rogers. So when he turns it on, it just stays on the Samsung Screen and doesn't go on. He hasn't rooted it and doesn't put custom Roms on it. Does anyone have any ideas? Would putting the original software through odin work?
Any help would be appreciated
Thanks guys
Click to expand...
Click to collapse
Follow this. http://forum.xda-developers.com/show....php?t=2618447 .
I followed sections all sections 1 threw 3. At section 2 the link for the I317UCUBMK6-TZ-PARAM.zip did not work. I used this link instead.
http://www56.zippyshare.com/v/16559598/file.html
At section 3 don't be alarmed when it says it's downloading the update but it doesn't show percentages. It is downloading. In fact for me it automatically downloaded the 4.4.2 update instead of 4.3. It skipped it and went straight to kitkat. It took some time but I have Official KItkat 4.4.2.
Hit Thanks
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app

Hmmm I've tried everything...still not connecting...I even used my G/F galaxy note 2 cable... So you guys are saying to install Kies, then shut it down because kies interferes with it? I cant believe its this difficult to reset this phone...I must be doing something wrong...I just dont know what
As I posted above...it says its connected then gives me an error...any other thoughts?
B

KillerX1911 said:
Hmmm I've tried everything...still not connecting...I even used my G/F galaxy note 2 cable... So you guys are saying to install Kies, then shut it down because kies interferes with it? I cant believe its this difficult to reset this phone...I must be doing something wrong...I just dont know what
As I posted above...it says its connected then gives me an error...any other thoughts?
B
Click to expand...
Click to collapse
Disclaimer: I am completely unfamiliar with the Note II. I know the Galaxy S II best.
Which version of Windows are you using?
You probably do not have a driver issue. In the Windows "Uninstall or Change a program" dialog (windows 7), you should see "Samsung USB Driver for Mobile Phones." If you have that, then you have the correct driver. Never the less, you might try uninstalling the driver on your pc, rebooting and then reinstalling the driver. You can get the driver from this thread, or you can download it directly from the Samsung website.
Also, you should not have Kies running when using Odin. You don't have to uninstall it, but it should not be running, and you should kill any Kies processes that are running, if any. Or, just reboot the PC and don't open Kies.
You are connecting with Odin. Odin recognizes the phone. So probably, the issue is one of: the connection between the phone and the PC or a firmware issue on the phone itself. The error message you posted suggests that you might need to flash the firmware with a pit file. However, if it were me, I would exhaust all the troubleshooting steps involving a connection problem first, before flashing with a pit file.
Connection problem: Use a USB port connected to the motherboard. Use different USB cables. Use different USB ports. Even use a different PC. Also, try the flash more than once. Some have reported that after multiple tries, they were able to get a successful flash.
Edit: Just ran across this while doing some reading. Your phone is the 317M I think, so you'll have to pm Zen Arcade for the correct PIT. This is just in case you need it.
By the way, helping folks get their phone working under difficult circumstances is what I like doing best. I'll keep an eye on this thread, but I usually only get on the forum once or twice a day.

T-mobile Galaxy S3 is Soft Bricked. Can only enter download mode. Please Help!!!

Please help!
I've tried going through all the forums as well as searching online but I'm unable to recover my phone. At this point, I'm not sure if my phone is soft bricked or if there is a power button failure, or both. I was initially having problems with the phone restarting by itself every so often. As time went on, the restarting problem became more frequent. Finally, it got stuck on the cyanogenmod loading screen.
I tried going into recovery mode to install a new version of cyanogenmod but a quarter of the way through the installation, the phone rebooting itself. Tried to install it again with the same results, this time the phone rebooting right after I began the install. Finally, I tried to wipe Dalvik Cache and data. Now, I'm unable to even get into recovery mode. I'm only able to get into download mode.
From download mode, I attempted to use Odins versions (1.85, 3.04, 3.07 & 3.09) to try to reinstall a stock mod. Unfortunately, I keep getting stuck on "nand write start!" No matter how long I wait, it stays there and I have to remove the battery from the phone to continue the process over again. It doesn't matter what firmware I try to install, or whether it be just trying to install twrp it always hangs on "nand write start!"
As a last resort, I attempted to use a pit file in addition to a stock rom. This time, I get the following error on my phone: "secure check fail : pit"
My phone displays the following when going through Odin and using the pit file:
Odin Mode
Product Name: SGH-T999
Custom Binary Download: Yes (3 counts)
Current Binary: Custom
System Status: Custom
QUALCOMM SECUREBOOT: ENABLE
SECURE CHECK FAIL : PIT
What does Qualcomm Secureboot: Enable mean? Could it be a hardware problem, motherboard, faulty power button causing this? Or software?
PLEASE HELP! Thanks so much in advance.

To check the power button, remove battery and pug it back in. If it tries to turn on by itself you have a faulty power switch.
Secureboot isnt anything to worry about. Its just there to prevent flashing of incompatible firmware.
It could be an issue with either the motherboard or USB port, or both, as well though.
Next time you try to flash with Odin, wait for it to finish. It may take a long time, but it will fail, and it may give us a clue to the cause when it does. I suggest starting the flash and walk away for 30-60 min.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
To check the power button, remove battery and pug it back in. If it tries to turn on by itself you have a faulty power switch.
Secureboot isnt anything to worry about. Its just there to prevent flashing of incompatible firmware.
It could be an issue with either the motherboard or USB port, or both, as well though.
Next time you try to flash with Odin, wait for it to finish. It may take a long time, but it will fail, and it may give us a clue to the cause when it does. I suggest starting the flash and walk away for 30-60 min.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I plugged in two different batteries and the phone didn't automatically turn on so maybe it's not a faulty power switch.
I also let Odin run for 80 minutes and it's still stuck on NAND Write Start!!
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVUEMJC_T999TMBEMJC_T999UVUEMJC_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> sbl2.mbn
<ID:0/005> NAND Write Start!!
Had to unplug the phone and restart it by removing the battery. After I try to boot it up the following message appears:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. " I am still able to get into download mode.
The previous attempt was using Odin 3.04. I attempted again using Odin 3.09 to flash TWRP onto the system only to get the same issue of being stuck at NAND Write Start. This time, I let it sit for an hour. File I used. C:\Users\xxx\Desktop\openrecovery-twrp-2.8.0.1-d2tmo.tar
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
Any clues???

Wow! Ok, I've never seen it take that long! Odin has always eventually failed out of the flash in my experience.
Do you have kies installed on your computer? If so, uninstall it. It interferes with Odin. Also, what windows version are you using?
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
Wow! Ok, I've never seen it take that long! Odin has always eventually failed out of the flash in my experience.
Do you have kies installed on your computer? If so, uninstall it. It interferes with Odin. Also, what windows version are you using?
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I don't have kies installed. I installed the samsung drivers directly. I'm running Windows 8.

Try different drivers and/or try running Odin as admin. Maybe compatibility mode would work too. Beyond that the only other thing I can think of would be to try a different computer.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
Try different drivers and/or try running Odin as admin. Maybe compatibility mode would work too. Beyond that the only other thing I can think of would be to try a different computer.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I used a different computer and had the same hanging problem.

Have you tried different USB cables? Different driver versions?
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
Have you tried different USB cables? Different driver versions?
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Go to SamMobile and get the newest stock image file: T999UVUENC2
MJC would not flash on my phone either when I thought I soft bricked. I also had the best luck with ODIN v3.04
Just load the image into PDA (don't use PIT file) and only check have "Auto-reboot" checked off. Let it run it's course. It does take a while so be patient.

You can download the firmware from my thread too. Will be faster than sammobile.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

If after doing all the above it still doesn't work, try a win 7 PC, some people have issues getting it to work with win 8

DocHoliday77 said:
Have you tried different USB cables? Different driver versions?
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
DocHoliday77 said:
You can download the firmware from my thread too. Will be faster than sammobile.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Thanks everyone for their suggestions. I'm without a phone and don't really have the money right now to purchase a new one. So, I've tried different USB cables as well as a Win 7 PC and it still hangs on NAND WRITE START!!
Where do I find the different driver versions that you are referring to? I just installed the Samsung Drivers from this thread using the installer:
http://forum.xda-developers.com/showthread.php?t=2688516

I have a bunch linked in my sig. The oldest I believe is the version that was released for the S3. The newest 1 or 2 were a major update for the Note 3 and S5. Anything in between were smaller updates to the first. Try the 2nd or 3rd from newest, then try the first couple after that is what I would do, but it's up to you which you want to give it a shot with.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
I have a bunch linked in my sig. The oldest I believe is the version that was released for the S3. The newest 1 or 2 were a major update for the Note 3 and S5. Anything in between were smaller updates to the first. Try the 2nd or 3rd from newest, then try the first couple after that is what I would do, but it's up to you which you want to give it a shot with.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
So I tried each of the drivers in your sig and none of them seemed to help. Does this sound like a motherboard failure? I do remember before when I was able to get into recovery that there was an error along the lines of can't mount sd card. I'm unable to get into recovery now to confirm

It certainly is possible.
When you installed the different drivers, did you go to device manager and verify they changed? Sometimes it won't unless you choose Update drivers in properties and browse to the new ones in program files.
Other than all of that, I'm not sure what else to tell you. It could be something faulty with the motherboard. Maybe the USB port itself is bad. Not sure if a good way to know for sure though. There may be some vids on YouTube that show how to test it.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
It certainly is possible.
When you installed the different drivers, did you go to device manager and verify they changed? Sometimes it won't unless you choose Update drivers in properties and browse to the new ones in program files.
Other than all of that, I'm not sure what else to tell you. It could be something faulty with the motherboard. Maybe the USB port itself is bad. Not sure if a good way to know for sure though. There may be some vids on YouTube that show how to test it.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
The phone still charges the battery. I get a battery charging icon on the phone when it's plugged in. If it was a faulty USB port would it still be able to charge and yet cause the problems I'm facing?

It could. And I'm not saying I believe its the USB port though. Just that its a possibility. It uses different pins for power and data, so if the data pins got damaged somehow it may still charge but not transfer anything. This usually happens with cables, but I have heard about it happening to the port too.
The only way I can think to test further would be to plug in a second S3 and see if it works. But it still might not tell you exactly what the issue is. Just that its not the computer or cable.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
It could. And I'm not saying I believe its the USB port though. Just that its a possibility. It uses different pins for power and data, so if the data pins got damaged somehow it may still charge but not transfer anything. This usually happens with cables, but I have heard about it happening to the port too.
The only way I can think to test further would be to plug in a second S3 and see if it works. But it still might not tell you exactly what the issue is. Just that its not the computer or cable.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
My roommate does have an S3. I should be able to borrow it to test. How do I go about testing it without potentially messing it up or rooting it? Is there a test file that I could use. I'm positive her phone would just be stock T-mobile.

Basically I would just plug it into the computer to see if it is detected by Odin. If it is we know the problem is definitely your device and not the computer or cable. Its still possible it could be any of them right now.
But if the good S3 also cannot connect, it means your device is most likely ok, and either the computer or cable is the problem.
Sent from my SAMSUNG-SGH-T999 using Tapatalk

DocHoliday77 said:
Basically I would just plug it into the computer to see if it is detected by Odin. If it is we know the problem is definitely your device and not the computer or cable. Its still possible it could be any of them right now.
But if the good S3 also cannot connect, it means your device is most likely ok, and either the computer or cable is the problem.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Okay, so I plugged in my roommates phone in Odin and it says Added!! When I unplug the usb cable it updates to Removed!! Thoughts???

Flash stock using odin alway get fail

Hi all
I have try many time to flash using ODIN a stock rom, but never success.
The Auto reboot and Reset Time is ticked
Im using Windows 10 with all Samsung driver installed
Note that i can use ODIN to flash TWRP 3.0 successfully
Here is result
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:1/003> Added!!
<ID:0/005> Odin engine v(ID:3.1100)..
<ID:1/003> Odin engine v(ID:3.1100)..
<ID:0/005> File analysis..
<ID:1/003> File analysis..
<ID:1/003> SetupConnection..
<ID:0/005> SetupConnection..
<ID:1/003> Initialzation..
<ID:1/003> Set PIT file..
<ID:1/003> DO NOT TURN OFF TARGET!!
<ID:1/003> FAIL!
<ID:1/003>
<ID:1/003> Re-Partition operation failed.
<ID:1/003> Removed!!
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 2)
Pls help

re-download the rom file, make sure you have a good internet connection and get the good download package.

yaibakt said:
re-download the rom file, make sure you have a good internet connection and get the good download package.
Click to expand...
Click to collapse
I think its not matter with downloading, i have downloaded 4 or 5 stock firmware from sammobile or androidhost, can extract it with winrar no problem.
Maybe becoz of windows 10? I dont have other windows now to try. Using odin 3.10.6, 3.10.7 same result...

Try a different USB cable. Sounds dumb but Odin can be like that sometimes. Also restart pc before trying.

I have try many ways, change PC, change Windows 10, 7 , change usb cab... have same result.
Maybe problem is my phone itself, something wrong with Rom, boot, recovery... Im still can install TWRP and custom Rom no problem

What options do you have set?

1619415 said:
What options do you have set?
Click to expand...
Click to collapse
I set as default, auto reboot and reset timer

Hahaha, so funny with my galaxy S6:
- With download mode show SM-920R4
- With Settings - About show 920P
- Plug into PC show as Galaxy S6 Edge
- Check EMEI info: T849 Galaxy Tab T-Mobile
I know some above just becoz of Cook ROM only, can change with difference ROM. For now, i still can install difference cook ROM from Sprint S6 by TWRP no problem, and phone work well. But no way to flash "stock ROM" becoz dont know what is original of the phone. I was bough it as 2nd hand.

quynh2v said:
Hahaha, so funny with my galaxy S6 . . . no way to flash "stock ROM" becoz dont know what is original [model] of the phone. I[t] was bough it as 2nd hand.
Click to expand...
Click to collapse
Seriously? The model number is (should be) printed on the bottom of your phone's back cover.
Sent from my SM-G920P using Tapatalk

tdhite said:
Seriously? The model number is (should be) printed on the bottom of your phone's back cover.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Model in back side is only Galaxy S6.
But, i just try to flash G920R4 stock rom by ODIN all is ok back to original, so my phone is realy Cellular S6. Now i can back to stock easy if custom Rom have trouble. I was paid 2 times for repair my phone allready, now will repair it by myself.

Bạn từ vietnam hả? Mình cũng bị trường hợp giống bạn. Máy mình chạy OF7. Bạn làm sao để fix lỗi vậy

quynh2v said:
Model in back side is only Galaxy S6.
But, i just try to flash G920R4 stock rom by ODIN all is ok back to original, so my phone is realy Cellular S6. Now i can back to stock easy if custom Rom have trouble. I was paid 2 times for repair my phone allready, now will repair it by myself.
Click to expand...
Click to collapse
Do u have a custom rom for G920R4? If u do can share a link. please.....

ur phone is imei spoofed ur imei has also changed with flashing the new rom...try matching from back also it wont match n the bill they gave u...its illegal to sell imei spoofed phone u could have the seller arrested