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.

Samsung s3 4.2.2 update issue

Hi,
I was trying to update my phone to the newest version 4.2.2 and i got stuck during the process. I have downloaded the 4.2.2 firmware as well as ODIN and followed the steps of how to update it to the newest Jelly Bean update, So first i turned off the phone and did the download mode, then i opened odin and pressed PDA and chose the md5 file .. just like a couple seconds later it said on the odin ( All process filed ) and showed a failed red board on the top. So now my phone says : ( firmware upgrade encountered an issue. please select recovery mode in Kies and try again ) ... I tried all the possibilities to fix the phone; even tried to do a hard mode (recovery mode by clicking the Home + Up volume + power buttons on the same time) and it actually brings me back to the yellow triangle.
My phone seems to be in Bricked mode, could anyone tell me how to unbrick my phone ?
Please it would be very nice if someone tries to help me fix this annoying issue AS SOON AS POSSIBLE !!
Thanks.

1) Stop flashing firmware that isn't for your phone.
2) See step 1.
3) See dev forum for proper files (http://forum.xda-developers.com/showthread.php?t=1949687). Only if you have an SGH-T999.
4) See step 1 again.
5) If you can't access download mode, you are bricked. Can't fix without JTAG.
6) See step 1 again.
7) Step 1 is really important. Look at it again.

Aerowinder said:
1) Stop flashing firmware that isn't for your phone.
2) See step 1.
3) See dev forum for proper files (http://forum.xda-developers.com/showthread.php?t=1949687). Only if you have an SGH-T999.
4) See step 1 again.
5) If you can't access download mode, you are bricked. Can't fix without JTAG.
6) See step 1 again.
7) Step 1 is really important. Look at it again.
Click to expand...
Click to collapse
Can we get a sticky!?!?!

Aerowinder said:
1) Stop flashing firmware that isn't for your phone.
2) See step 1.
3) See dev forum for proper files (http://forum.xda-developers.com/showthread.php?t=1949687). Only if you have an SGH-T999.
4) See step 1 again.
5) If you can't access download mode, you are bricked. Can't fix without JTAG.
6) See step 1 again.
7) Step 1 is really important. Look at it again.
Click to expand...
Click to collapse
Thanks so much for your help. First of all my phone is a canadian phone from Windmobile, and it ends with V .. but there are a sever stuff for 999v, which one should i download though ?
i have downloaded this one ( Wind VLDLL1
Version: 4.1.1 JB
Date: Dec, 01, 2012
PDA: T999VVLDLL1
CSC: T999VYVLDLL1 ) is that okay ?

If you are on Wind, and have an SGH-T999. Then yes, that's the correct one. But if you can't get download mode, you are screwed.

Aerowinder said:
1) Stop flashing firmware that isn't for your phone.
2) See step 1.
3) See dev forum for proper files (http://forum.xda-developers.com/showthread.php?t=1949687). Only if you have an SGH-T999.
4) See step 1 again.
5) If you can't access download mode, you are bricked. Can't fix without JTAG.
6) See step 1 again.
7) Step 1 is really important. Look at it again.
Click to expand...
Click to collapse
Which step is step one though ? you mean downloading the official firmware or "How to root no tripping flash counter " ??? please help ?

Aerowinder said:
If you are on Wind, and have an SGH-T999. Then yes, that's the correct one. But if you can't get download mode, you are screwed.
Click to expand...
Click to collapse
I could do download mode and get there, but when i open the odin app on windows and start the process via PDA and click start after a while it will show on the phone in red color : ( Unsupported dev_type )

Aerowinder said:
If you are on Wind, and have an SGH-T999. Then yes, that's the correct one. But if you can't get download mode, you are screwed.
Click to expand...
Click to collapse
So i have downloaded the firmware and used it via odin (PDA) and it said it failed :
( <OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> KIES_HOME_T999VVLDLL1_T999VYVLDLL1_CL616748_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Can't open the serial(COM) port.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Help please !!

This is just not working correctly, i have also downloaded ( root66_GLW_T999VVLDLL1.tar.md5 ) and it keep saying failed. is there any other ways to unlock this issue ??? PLEASE HELP

Links to what you flashed first of all to start this stuff, and then we can possibly help you. There is no 4.2.2 leak for our phone or your t999v. Sooo it should be bricked. If you can get into download mode, state so.. if not than you are bricked and are wasting your time.

mt3g said:
Links to what you flashed first of all to start this stuff, and then we can possibly help you. There is no 4.2.2 leak for our phone or your t999v. Sooo it should be bricked. If you can get into download mode, state so.. if not than you are bricked and are wasting your time.
Click to expand...
Click to collapse
Thankfully is working again now ... i think i had to install Samsung USB drivers ...
Do you think if i could try again using the 4.2.2 firmware and if a problem occur, will redo the first step since i havent lost any of my files.

numberone1 said:
Thankfully is working again now ... i think i had to install Samsung USB drivers ...
Do you think if i could try again using the 4.2.2 firmware and if a problem occur, will redo the first step since i havent lost any of my files.
Click to expand...
Click to collapse
Can you read? If so, please read the post you quoted from mt3g.
Sent from my SGH-T999 using xda premium

numberone1 said:
Thankfully is working again now ... i think i had to install Samsung USB drivers ...
Do you think if i could try again using the 4.2.2 firmware and if a problem occur, will redo the first step since i havent lost any of my files.
Click to expand...
Click to collapse
We don't have an official 4.2.2 firmware. If you got it from Sam mobile it it ONLY for the international version of the sgs3. You're lucky you didn't brick your phone.
Sent from my SGH-T999 using xda app-developers app

[Q] Tmobile Galaxy S 2 not going beyon Boot screen

One fine day all of a sudden my SGH T989 ( Tmobile version of Galaxy S2) turned off and when I tried to turn it on it went in to the boot load loop and was not going beyond the Boot loaded screen which shows blue progress bar. Then I tried emergency firmware recovery option of the KIES but the progress bar on the recover dialog was getting stuck at 0 % for long time without any movement. Tried it multiple times by disabling the anti virus on my laptop , connected to different USB ports but same result. I couldn't get into the recover mode on my phone by pressing the Volume down+Power + Home button. The download mode option was also not working with by pressing both Volume Up+Down and Power button. But I could get in the Download mode by Pressing both volume up+down and then connecting the USB cable.
After KIES now the progress bar on boot load screen reaches almost 100% but after few seconds the screen turns completely black ( appears that the device is turned off) and it no longer goes in to the boot load loop.
After that I tried recovery thru ODIN by using the t898 Stock ROM, but it also doesn't work. It shows ABOOT on the first box on the screen and in the log it shows Nand Write Start !! and doesn't do anything beyond that point. I tried ODIN version 3.09, 3.07, 3.04 and 1.83 but same result every time.
Note: My phone is having Android version 4.1.2/ Software T989UVMC6 (Tmobile official Jelly Beans version) and is still factory locked.
Then I tried the CMW recovery file for T989 using ODIN 1.83 but no luck it get stuck at aboot.md and nothing happens.
I have latest version of KIES on my laptop.
While going thru some other post I read something about repartition but I couldn't find the proper instructions and PIT files for my phone.
Would appreciate guidance/advise to fix this issue.
My phone is out of warranty from both the carrier and Samsung. Samsung is asking to pay $70 for fixing the phone.
But I want to give it a try before sending it to samsung.

try this thread http://forum.xda-developers.com/showthread.php?t=1414341
make sure you end all kies processes- use ics in thread and go from there...hope this helps

Fasted12 said:
try this thread http://forum.xda-developers.com/showthread.php?t=1414341
make sure you end all kies processes- use ics in thread and go from there...hope this helps
Click to expand...
Click to collapse
All download links provided on the thread given by you are broken. I could find ODIN 1.85 from some other sites but am having hard time finding the stock rom 4.0.3 that is mentioned in the thread. All hotfile.com links are not working.
Please let me know if there is a legitimate link available for download. Can I use the Jelly Beans recovery file?
I tried it with ODIN 3.09, 3.07 and 1.83 but it didn't work.

nikson1906 said:
All download links provided on the thread given by you are broken. I could find ODIN 1.85 from some other sites but am having hard time finding the stock rom 4.0.3 that is mentioned in the thread. All hotfile.com links are not working.
Please let me know if there is a legitimate link available for download. Can I use the Jelly Beans recovery file?
I tried it with ODIN 3.09, 3.07 and 1.83 but it didn't work.
Click to expand...
Click to collapse
you can use the 4.1.2 tar file, needs to be odin 1.85 for this. forgot about hotfile,
try this link http://forum.xda-developers.com/showthread.php?t=2226886&page=9 (look on last page)
these are everywhere on xda, you have to look through the comments since hotfile went down
---------- Post added at 09:24 AM ---------- Previous post was at 09:05 AM ----------
http://forum.xda-developers.com/showthread.php?t=1374868
this link is working-- ive had better luck flashing to ics when soft bricked. mine accepts radio better and then i flash custom rom after root,

Fasted12 said:
you can use the 4.1.2 tar file, needs to be odin 1.85 for this. forgot about hotfile,
try this link http://forum.xda-developers.com/showthread.php?t=2226886&page=9 (look on last page)
these are everywhere on xda, you have to look through the comments since hotfile went down
---------- Post added at 09:24 AM ---------- Previous post was at 09:05 AM ----------
http://forum.xda-developers.com/showthread.php?t=1374868
this link is working-- ive had better luck flashing to ics when soft bricked. mine accepts radio better and then i flash custom rom after root,
Click to expand...
Click to collapse
I tried 4.1.2 tar file ( downloaded from Samsung-Update.com) yesterday with ODIN 1.85 but still same result. It get stuck at Nand Write Start !!
I'll try with ICS rom from the links provided by you but I doubt it will work. Do I need to repartition using PIT file. I read in few other threads that guys had same problem and after using the PIT they could fix their phone. I searched for PIT file for Tmobile Galaxy S 2 (T989) but couldn't find. I see that there a PIT file available with ODIN 1.85 which I downloaded, but am not sure if that is the correct one for my phone.

You can try, be careful, a lot of hard bricks come from trying to repartition. What windows do you use, and end Kies process if running.
Sent from my SGH-T989 using xda app-developers app

Fasted12 said:
You can try, be careful, a lot of hard bricks come from trying to repartition. What windows do you use, and end Kies process if running.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I am using Windows 7. I checked in task manager and made sure no process that starts with the name KIES or has samsung in description is not running. Is there any specific service/process that I need to kill before starting the ODIN?
Any other thoughts, like if I need to disable the anti virus completely which might be restricting ODIN and KIES to write to the COM port?
I downloaded a utility for monitoring the serial port while ODIN was running but once I get the NAND Write Start !! I don't see any activity on the port.
I tried the PIT file that came along with ODIN 1.85 and T989 stock Rom together ( I kept the Re-Partition checked.), but again it got stuck at...
<ID:0/05> Set PIT file..
<ID:0/05> DO NOT TURN OFF TARGET!!
Still same issue, no change in the Device status..

nikson1906 said:
I am using Windows 7. I checked in task manager and made sure no process that starts with the name KIES or has samsung in description is not running. Is there any specific service/process that I need to kill before starting the ODIN?
Any other thoughts, like if I need to disable the anti virus completely which might be restricting ODIN and KIES to write to the COM port?
I downloaded a utility for monitoring the serial port while ODIN was running but once I get the NAND Write Start !! I don't see any activity on the port.
I tried the PIT file that came along with ODIN 1.85 and T989 stock Rom together ( I kept the Re-Partition checked.), but again it got stuck at...
<ID:0/05> Set PIT file..
<ID:0/05> DO NOT TURN OFF TARGET!!
Still same issue, no change in the Device status..
Click to expand...
Click to collapse
only thing i ever check is auto reboot, only value i use is PDA-thats where the .tar file goes. uncheck re-partition.

Fasted12 said:
only thing i ever check is auto reboot, only value i use is PDA-thats where the .tar file goes. uncheck re-partition.
Click to expand...
Click to collapse
Re-partition I checked only when I used the PIT file.
any other thoughts like, if I need to flash ?

nikson1906 said:
Re-partition I checked only when I used the PIT file.
any other thoughts like, if I need to flash ?
Click to expand...
Click to collapse
pit files are related to the size of repartition, thats not what you need. if your phone will still go to download mode but will not boot, you should follow the guide i posted in the first reply , especially step 2, i have recovered many with that guide. sometimes i had to use gingerbread rom first to get files that were missing to upgrade.

Fasted12 said:
pit files are related to the size of repartition, thats not what you need. if your phone will still go to download mode but will not boot, you should follow the guide i posted in the first reply , especially step 2, i have recovered many with that guide. sometimes i had to use gingerbread rom first to get files that were missing to upgrade.
Click to expand...
Click to collapse
I have already tried steps as per the guide but no luck. I can try gingerbread if the ROM is available. finding ICS rom itself was very difficult. Let me know if you have the link for Gingerbread ROM

So I tried the gingerbread and ICS roms as well. Also tried flashing the kernels and various versions of ODIN including 1.3,1.83,1.85,3.07,3.09 but same result. It get either stuck at Nand Write Start !! for ROM upgrade or Boot.img for Kernel flash.
Tried disabling McAfee's firewall and Active Protections, made sure none of the KIES services are running, tried stock ROMs for Gingerbread, ICS and JB.
Tried KIES as well as ODIN.
KIES get stuck at 0% in the Firmware update step after completing all the required file downloads, decryption etc.
Tried all 3 USB ports on my Laptop.
I can get into download mode only by holding Vol up+Down button and then connecting the USB cable.
Holding Vol up+ down and pressing the power button ( releasing on first vibration) doesn't work.
I couldn't get into the recovery mode by pressing the vol up and power button.
If I power ON the device it completes the boot load screen ( blue progress bar) and after few seconds the screen turns black. Pressing the power button again doesn't do anything.
Gone thru many thread but no luck so far.
Need help !!

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