Develop Bugs

Returning to stock from ICS w/root.

I tried searching for the answer but didn't find anything. Sorry if I missed a sticky on this!
Otherwise, just as thread states - need to return to stock before going to the sprint store. Everything is backed up but I can't seem to find the stock odin files to flash. I do NOT have CWM or a custom bootloader, just currently running FD26 ICS with root. A total wipe would be fine. This would be a return to stock sprint 2.3.x or whatever sprint has out now.
Thanks in advance!

You need this http://forum.xda-developers.com/showthread.php?p=21134991
After that, if you need to unroot, look for sfhub's auto root tool (think its in the development sticky) and run the unroot option.
Both together will achieve an out of the box state
Sent from my SPH-D710 using Tapatalk 2

The latest official kernel/modem is EL29. As you've already flashed a custom ROM, I know you're familiar with how to do it, but here is the thread with the download and instructions anyways =)
*note - this IS rooted, but sprint doesn't care if you root your phone--as long as kernal/ROM/modem are stock ^_~
http://forum.xda-developers.com/showthread.php?t=1433101

tkemack said:
You need this http://forum.xda-developers.com/showthread.php?p=21134991
After that, if you need to unroot, look for sfhub's auto root tool (think its in the development sticky) and run the unroot option.
Both together will achieve an out of the box state
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
I tried this method - using el29 restore - rooted but all I get is fail message. It hangs at "setup connection" as follows:
<ID:0/016> 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/016> Odin v.3 engine (ID:16)..
<ID:0/016> File analysis..
<ID:0/016> SetupConnection..
<ID:0/016>
<OSM> All threads completed. (succeed 0 / failed 1)
This is the result of pressing "start" in odin after getting a yellow com. All drivers are installed correctly as far as I know.
EDIT: I have now tried this from 2 computers, same result. Fail notice after setupconnection. Both times were using the stock cable that came with the phone.
EDIT 2: Using another aftermarket monoprice ferrite core cable made no difference. Continuing to get fail notice.

Just as an update I have now verified that the USB mode is set to AP, and I have all windows drivers installed correctly on both of my computers. Still unable to get a connection. In addition I have tried it in both usb debugging ON mode and OFF, with still no success. Anything I may still be doing wrong?

You are putting the phone into download mode first before plugging it into the computer right? Holding volume down and power buttons do this, hold them till you see the warning screen, then hit volume up to go into download mode.

lawr0155 said:
You are putting the phone into download mode first before plugging it into the computer right? Holding volume down and power buttons do this, hold them till you see the warning screen, then hit volume up to go into download mode.
Click to expand...
Click to collapse
Yes, absolutely. Odin gets a yellow com just fine too, it just doesn't setup the connection.

I'm not saying to do it but what about this idea? Somehow, with my thought, you have to get the modem back to EL29. You might (don't know haven't tried) be able to mobile Odin everything else. Make sure you get mobile Odin and the flashkernel d710 apk installed first. Just a suggestion....

Well can you not return to GB stock after running an ICS ROM using the odin method? I haven't seen any threads about it.

Give this a try...
http://forum.xda-developers.com/showthread.php?t=1678631
IMO the easiest way to get back to 100% Stock EL29 without root.

Drumrocker said:
Give this a try...
http://forum.xda-developers.com/showthread.php?t=1678631
IMO the easiest way to get back to 100% Stock EL29 without root.
Click to expand...
Click to collapse
File that is linked there is now gone
Man this is not going my way at all...

Okay, I got it flashing finally. For some reason my drivers were somehow in some way not correct. I opened kies and it it did the 6/6 (today's) update and then started updating my drivers. After that odin was finally able to start the flash setup. Who knows?
Well its working now.

If you aren't concerned with what version of stock you are on, you can also look on the EK02 ODIN OneClick thread. That ROM is pure stock and not rooted. If you can't use the OneClick, in the 2nd post there is a tar.md5 version.

[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] Sudden half death in Samsung N7100

I have rooted my phone. Working without any problem for past 1 year. Recently it started showing that the space was becoming limited .
Anyways, I didn't have time to look into it so I kind of nudged it off.
Well today someone called me and it got stuck, I couldn't accept/deny the call and my phone kept ringing in a loop (way longer than a phone should) so I pulled the battery. When I put the battery back in, my phone started up as a full white screen with black lines all over it (as if the screen was cracked.) Since then I have not been able to access anything except Odin (vol. down + home + power).
I cannot access CWM, do not ever see the samsung logo, only able to see this If I press down (to restart) the phone gets stuck.
Now I installed a few things such as the stock firmware, the pit file, the MD5 tar file for PDA. I went into Odin v1.85 and v3.0 on PC and tried flashing the stock firmware but that did not work out as it kept giving me
although i searched th forum but couldn't find the solution to it.
Please help

Did u tried flashing stock rom?nd wat bout chip?is it sane or insane?
Sent from my AweSoMe ☆♥Note2♥☆

Omg..everytime my apps are updating..its giving me the limited space notif. Should i be worried too? I have a sane chip btw.
And about ur phone..wat rom were u on?
Sent from my GT-N7100 using xda app-developers app

not responding to odin
mannyvinny said:
Did u tried flashing stock rom?nd wat bout chip?is it sane or insane?
Sent from my AweSoMe ☆♥Note2♥☆
Click to expand...
Click to collapse
only the stck rom was installed. i have never tried any custom ROM.
But now it is stuck on white lines. and only goes to odin mode (vol down+power+home). and not getting in restore mode (vol up+home+power).
i have tried flashing the original Stock ROM. Odin gave the following error
OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SGHT889V.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialization..
<ID:0/006> Get PIT for mapping..
<ID:0/006>
<ID:0/006> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)

Original board
naeem86 said:
Omg..everytime my apps are updating..its giving me the limited space notif. Should i be worried too? I have a sane chip btw.
And about ur phone..wat rom were u on?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
i was on stock ROM. And i don't know about the chip sane or insane. it is indian verssion of Note 2 (N7100).
now stuck at those white lines and not responding to even odin.
Guys please help to connect it to odin.

navdeepmasaun said:
i was on stock ROM. And i don't know about the chip sane or insane. it is indian verssion of Note 2 (N7100).
now stuck at those white lines and not responding to even odin.
Guys please help to connect it to odin.
Click to expand...
Click to collapse
<OSM> SGHT889V.tar.md5 ------ SGHT889V i don't think is really a n7100

Unless ur on tmobile note2 I think u chose wrong firmware.
Sent from my GT-N7100 using Tapatalk 4

original firmware
vash_h said:
Unless ur on tmobile note2 I think u chose wrong firmware.
Sent from my GT-N7100 using Tapatalk 4
Click to expand...
Click to collapse
i tried original Indian version of firmware of N7100, but same results
N7100XXDMG1_ODDDMG1_India_Android_4.1.2

Did you tick the repartition option in Odin? If yes, are you sure the ROM you are trying to flash needs that?
Sent from my GT-N7100 using xda app-developers app

@Nadeepmasaun
navdeepmasaun said:
i tried original Indian version of firmware of N7100, but same results
N7100XXDMG1_ODDDMG1_India_Android_4.1.2
Click to expand...
Click to collapse
"Bhai tera phone N7100 nahi Hai , thats why its giving you error , and Now you must look firmware for "T-mobile "
but were you bought This phone .? Gaffar Market
GT-n7100 is international and Tmobile is SGHT889V
Try to find Currect rom or Model Number :good:

djmax81 said:
"Bhai tera phone N7100 nahi Hai , thats why its giving you error , and Now you must look firmware for "T-mobile "
but were you bought This phone .? Gaffar Market
GT-n7100 is international and Tmobile is SGHT889V
Try to find Currect rom or Model Number :good:
Click to expand...
Click to collapse
Palika bazaar
Magar ye India me kaha available hai? @navdeepmasaun Go to settings-about device and check the 'Model Number'.. m sure its not N7100
Sent from my AweSoMe ?♥Note2♥?

Had something similar with my N2. First more and more random freezes until I tried to reflash complete stock to see if that solved the problem. I ended up with the same issue as you and I could only solve it by having the service point replace the main board. I know that earlier tests showed I had a problem MMC chip. The new mainboard test shows I have a sane chip. Good luck!
Sent from my GT-N7100 using xda app-developers app

model Number
mannyvinny said:
Palika bazaar
Magar ye India me kaha available hai? @navdeepmasaun Go to settings-about device and check the 'Model Number'.. m sure its not N7100
Sent from my AweSoMe ?♥Note2♥?
Click to expand...
Click to collapse
when it used to start at start-up logo it showed N7100. even in Settings it showed N7100. i bought it second hand year back.
problem is that it showed this syndrome when it was placed idle after a call. And suddenly stopped responding with white lines and only going in download mode and not letting me in recovery mode.
you guys are talking about flashing. Nothing has been flashed earlier, but although it was rooted.
ya after this problem, i tried to flash this one with Rom, without any success.
But now i have downloaded the original Stock rom also, and will try to update with that. and let you know about this.
i have given my phone to some local service center, lets see what they say.....

mannyvinny said:
Palika bazaar
Magar ye India me kaha available hai? @navdeepmasaun Go to settings-about device and check the 'Model Number'.. m sure its not N7100
Sent from my AweSoMe ?♥Note2♥?
Click to expand...
Click to collapse
+1 guess he probably ...bought it gray market n lagtaa hai Tmobile chipka diaa....coz most of the people get it to india even contract phones too illegally. at gaffar...to sell....
Nvr mind but it make me feel too its not n7100 ...not matter of brick or insane chip ...been using pc odin since ages
Sent from my GT-N7100 using XDA Premium 4 mobile app

alright
navdeepmasaun said:
when it used to start at start-up logo it showed N7100. even in Settings it showed N7100. i bought it second hand year back.
problem is that it showed this syndrome when it was placed idle after a call. And suddenly stopped responding with white lines and only going in download mode and not letting me in recovery mode.
you guys are talking about flashing. Nothing has been flashed earlier, but although it was rooted.
ya after this problem, i tried to flash this one with Rom, without any success.
But now i have downloaded the original Stock rom also, and will try to update with that. and let you know about this.
i have given my phone to some local service center, lets see what they say.....
Click to expand...
Click to collapse
hope for the best bro .!!!

djmax81 said:
+1 guess he probably ...bought it gray market n lagtaa hai Tmobile chipka diaa....coz most of the people get it to india even contract phones too illegally. at gaffar...to sell....
Nvr mind but it make me feel too its not n7100 ...not matter of brick or insane chip ...been using pc odin since ages
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
whether it is Tmobile or GT-N7100 doesn't matter. i want to know how to get it in restore mode or connect with odin.

have tried samsung latest drivers .?
navdeepmasaun said:
whether it is Tmobile or GT-N7100 doesn't matter. i want to know how to get it in restore mode or connect with odin.
Click to expand...
Click to collapse
did u update ... samsung usb drivers .?

How can i check it?

[Q] Help! Can't Unbrick TMO Note 2. Please help.

Team, my wife has a Note II that is stock all the way. She never accepted the OTA update to 4.3 and has been running 4.1.2 perfectly since last year. Three days ago, when she powered the phone on, it said "Firmware upgrade encountered an issue". The message said we had to go into Kies and try to recover. The phone will NOT enter stock recovery mode. It will go into download mode only.
I tried to use KIES, but Kies says the device version is not upgradeable. I took it to the store and they told me to come home and use Odin. So my wife decided since it couldn't be restored to her old phone we might as well update to 4.3 (booloader issues, I know !) I used Odin 3.07 using the MK7 version of 4.3 from last Dec, it took 10 minutes through modem, system etc. Then says FAIL. When I try to redo the Odin, it says PIT file missing or something like that.
Phone still won't work, and I have failed with Kies, local store, and Odin. I don't know what to do but she needs her phone. This phone bricked itself Sunday morning! Thank you in advance for any help. We don't need to buy a new phone. This one is only a year old.

hodgestl said:
Team, my wife has a Note II that is stock all the way. She never accepted the OTA update to 4.3 and has been running 4.1.2 perfectly since last year. Three days ago, when she powered the phone on, it said "Firmware upgrade encountered an issue". The message said we had to go into Kies and try to recover. The phone will NOT enter stock recovery mode. It will go into download mode only.
I tried to use KIES, but Kies says the device version is not upgradeable. I took it to the store and they told me to come home and use Odin. So my wife decided since it couldn't be restored to her old phone we might as well update to 4.3 (booloader issues, I know !) I used Odin 3.07 using the MK7 version of 4.3 from last Dec, it took 10 minutes through modem, system etc. Then says FAIL. When I try to redo the Odin, it says PIT file missing or something like that.
Phone still won't work, and I have failed with Kies, local store, and Odin. I don't know what to do but she needs her phone. This phone bricked itself Sunday morning! Thank you in advance for any help. We don't need to buy a new phone. This one is only a year old.
Click to expand...
Click to collapse
Flashing stock MK7 via odin should not have any issues. Can you double check the file you downloaded is indeed MK7 ?
Is the phone on 4.3 bootloader ? If download mode shows KNOX then yes it is.
You can also try to restore the phone using KIES emergency and then flash MK7 via odin.

ciphercodes said:
Flashing stock MK7 via odin should not have any issues. Can you double check the file you downloaded is indeed MK7 ?
Is the phone on 4.3 bootloader ? If download mode shows KNOX then yes it is.
You can also try to restore the phone using KIES emergency and then flash MK7 via odin.
Click to expand...
Click to collapse
Thanks for the reply. Download mode shows shows the following:
Odin mode
Product Name :
Custom Binary Download: No
Current Binary : Samsung Official
System Status: Custom (BTW, this said Normal before my Odin attempt)
The word KNOX does not appear anywhere on the Download mode screen.
Kies syas the current firmware is not upgradable. The phone will not actually connect in Kies. I try Emergency restore and put in model and S/N but its says can't upgrade. Kies won't connect to phone in normal mode.
Thanks for any possible ideas you can come up with.

hodgestl said:
Thanks for the reply. Download mode shows shows the following:
Odin mode
Product Name :
Custom Binary Download: No
Current Binary : Samsung Official
System Status: Custom (BTW, this said Normal before my Odin attempt)
The word KNOX does not appear anywhere on the Download mode screen.
Kies syas the current firmware is not upgradable. The phone will not actually connect in Kies. I try Emergency restore and put in model and S/N but its says can't upgrade. Kies won't connect to phone in normal mode.
Thanks for any possible ideas you can come up with.
Click to expand...
Click to collapse
If you can get into recovery and do a factory reset (format data and cache) then reboot and see if that will work. Make certain the SDcard is out of the phone when you format.

hodgestl said:
Thanks for the reply. Download mode shows shows the following:
Odin mode
Product Name :
Custom Binary Download: No
Current Binary : Samsung Official
System Status: Custom (BTW, this said Normal before my Odin attempt)
The word KNOX does not appear anywhere on the Download mode screen.
Kies syas the current firmware is not upgradable. The phone will not actually connect in Kies. I try Emergency restore and put in model and S/N but its says can't upgrade. Kies won't connect to phone in normal mode.
Thanks for any possible ideas you can come up with.
Click to expand...
Click to collapse
The phone is still on 4.1.2 bootloader. I would advise to flash stock T889UVBMD1 from sammobile.
Link: http://www.sammobile.com/firmwares/3/?download=15061
Or
If you want a rooted version you can flash MrRobinson's root 66 ROM.
Link: http://www.androidfilehost.com/?fid=23269279319200344

Coug76 said:
If you can get into recovery and do a factory reset (format data and cache) then reboot and see if that will work. Make certain the SDcard is out of the phone when you format.
Click to expand...
Click to collapse
Coug, thansk for the resposnse, but I can't get into recovery or just a boot up. Download (Odin) Mode is the only thing that is presently working.
Cipher, thank you also. Those are the two stock firmwares I have attempted. Nothing else.
I guess it may be hard-bricked, but I sure thought that was pretty rare.
Thanks again to you both for taking the time. If you have any more thoughts, I would sure be interested in hearing them. Thanks again.

hodgestl said:
Coug, thansk for the resposnse, but I can't get into recovery or just a boot up. Download (Odin) Mode is the only thing that is presently working.
Cipher, thank you also. Those are the two stock firmwares I have attempted. Nothing else.
I guess it may be hard-bricked, but I sure thought that was pretty rare.
Thanks again to you both for taking the time. If you have any more thoughts, I would sure be interested in hearing them. Thanks again.
Click to expand...
Click to collapse
Try giving the UVALJ1 root66 a try. I had a similar situation where I Odined that 2x and it reset my file system which had gotten corrupted. I was about to throw my hands up after flashing MB1 and another one as well. I figured that the original factory flash image would have the best chance of success.
Hastily spouted for your befuddlement

Coug76 said:
Try giving the UVALJ1 root66 a try. I had a similar situation where I Odined that 2x and it reset my file system which had gotten corrupted. I was about to throw my hands up after flashing MB1 and another one as well. I figured that the original factory flash image would have the best chance of success.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
Sounds like a good idea. I have tried Odin 3.07 and 3.09 on this effort up till now. Do you think I should look for an older copy of Odin too? Or just the older tar file from Mr. R?

hodgestl said:
Sounds like a good idea. I have tried Odin 3.07 and 3.09 on this effort up till now. Do you think I should look for an older copy of Odin too? Or just the older tar file from Mr. R?
Click to expand...
Click to collapse
I use 3.07. If that doesn't work give Heimdall a try. It *could* be a bit more stable.
Hastily spouted for your befuddlement

Here is the PIT file I had posted when my phone was still on 4.1.2.
Link: http://forum.xda-developers.com/showpost.php?p=48398405&postcount=205
Download the attached file and make sure to change file extension from .txt to .pit.
Start ODIN, click PIT and browse to this pit file.
Make sure the Re-Partition box is checked.
Then under PDA load your T889UVBMD1 tar.md5 file and click start.

ciphercodes said:
Here is the PIT file I had posted when my phone was still on 4.1.2.
Link: http://forum.xda-developers.com/showpost.php?p=48398405&postcount=205
Download the attached file and make sure to change file extension from .txt to .pit.
Start ODIN, click PIT and browse to this pit file.
Make sure the Re-Partition box is checked.
Then under PDA load your T889UVBMD1 tar.md5 file and click start.
Click to expand...
Click to collapse
Thank you. That PIT file should be exactly what I am looking for, since that is the message I am getting now. Just one last question, please. Shoukld I do the PIT file and then the TAR file in two separate Odin events? Or could I put the PIT in the Pit line and the TAR in the Pda line, click the re-partition box and do it as one Odin reflash?
I may try the PIT first, then come back and do the TAR second after the phone has repartitioned. I can't thank you enough.

Coug76 said:
I use 3.07. If that doesn't work give Heimdall a try. It *could* be a bit more stable.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
I will stay with Odin, I think. I have never used Heimdall, and am a little intimidated by trying something different. Of course I don't guess I can hurt the phone any further at this point ! haha.
Thanks again for everything. You have been a great help.

It's up to you, if you feel comfortable you can try with pit file first and then try the tar.md5 file. Glad to help, Ai hope the phone starts working again.
Sent from my SGH-T889 using XDA Free mobile app

hodgestl said:
I will stay with Odin, I think. I have never used Heimdall, and am a little intimidated by trying something different. Of course I don't guess I can hurt the phone any further at this point ! haha.
Thanks again for everything. You have been a great help.
Click to expand...
Click to collapse
We are a community. If my neighbor breaks his leg I'll mow his lawn for a while. If I need to replace my water heater he's there for me.
We've all been there before.
Hastily spouted for your befuddlement

Cipher, I think I am almost there. However, when I start Odin using the PIT file you provided, I have checked repartition, then entered the renamed TXT file with a PIT e4xtension. Odin starts normally, then says "Get PIT for Mapping" but it never continues. It doesn't fail, but it doesn't continue either. At the top of the Odin screen, in the area where it describes the current step, Odin says SET PARTITION, but never continues on past that point. I get no progress bar on either the PC screen or on the cell phone download screen. I think we are right on the edge of having this thing fixed but I am not quite there. Any ideas? Please?

hodgestl said:
Cipher, I think I am almost there. However, when I start Odin using the PIT file you provided, I have checked repartition, then entered the renamed TXT file with a PIT e4xtension. Odin starts normally, then says "Get PIT for Mapping" but it never continues. It doesn't fail, but it doesn't continue either. At the top of the Odin screen, in the area where it describes the current step, Odin says SET PARTITION, but never continues on past that point. I get no progress bar on either the PC screen or on the cell phone download screen. I think we are right on the edge of having this thing fixed but I am not quite there. Any ideas? Please?
Click to expand...
Click to collapse
Hi,
Does ODIN detect the device ? Does the ID:COM tab turns blue ?
You can try another PIT file posted by another user from here: http://forum.xda-developers.com/showpost.php?p=52860121&postcount=39

ciphercodes said:
Hi,
Does ODIN detect the device ? Does the ID:COM tab turns blue ?
You can try another PIT file posted by another user from here: http://forum.xda-developers.com/showpost.php?p=52860121&postcount=39
Click to expand...
Click to collapse
Yes, Odin is detecting the device just fine. The blue COM light comes on and gives me the com port number. Then in the running description, its says Added! which I have always taken to mean that Odin has successfullly connected to the device.
I leave the two check marks checked that are alerady there, then I also check the Re-Partition box. I add the PIT file from earlier (renamed with a PIT extension of course) to the PIT line.
When I click Start, Odin starts normally, finds the right instruxction, and above the blu com box, where it would say PASS at the very end, it syas SET PARTITION. The task descriptions in the lower left says Getting PIT file, and then ODIN stays there.
That lasted over 2 hours. I will try the new PIT file and see what happens this time. Thanks for the continued help and support. I really feel like we are just one tiny issue from getting this phone restored, but I can't quite get over the hump. I will let you know how I fare with the new PIT> Thanks again.

hodgestl said:
Yes, Odin is detecting the device just fine. The blue COM light comes on and gives me the com port number. Then in the running description, its says Added! which I have always taken to mean that Odin has successfullly connected to the device.
I leave the two check marks checked that are alerady there, then I also check the Re-Partition box. I add the PIT file from earlier (renamed with a PIT extension of course) to the PIT line.
When I click Start, Odin starts normally, finds the right instruxction, and above the blu com box, where it would say PASS at the very end, it syas SET PARTITION. The task descriptions in the lower left says Getting PIT file, and then ODIN stays there.
That lasted over 2 hours. I will try the new PIT file and see what happens this time. Thanks for the continued help and support. I really feel like we are just one tiny issue from getting this phone restored, but I can't quite get over the hump. I will let you know how I fare with the new PIT> Thanks again.
Click to expand...
Click to collapse
Try without checking the re-partition checkbox and see if it works. It should not take more then few seconds if you are only uploading the pit file.

ciphercodes said:
Try without checking the re-partition checkbox and see if it works. It should not take more then few seconds if you are only uploading the pit file.
Click to expand...
Click to collapse
Will do. Just gets stuck at "Get PIT for mapping.." I will try without the re-partition checked and report back. Thank you.

ciphercodes said:
Try without checking the re-partition checkbox and see if it works. It should not take more then few seconds if you are only uploading the pit file.
Click to expand...
Click to collapse
OK, when you select the PIT file using the Pit button, then Odin automatically checks the Re-Partition box. If you uncheck that box and try to proceed, I get the error message "No Binary is Selected." So it looks like I am kind of stuck. I have tried both of the PIT files. Both start normally, then get stuck (Permanently it appears) at the line "Get PIT for mapping.." I have tried just with the PIT only, and tried it with the ROM entered into the PDA button, and both give the same result.
I was very excited earlier today. I thought we (Really you) could save this phone. I feel like we are right on the edge, but the PIT load won't complete. Thanks for ideas.

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???