Develop Bugs

[Q] How do I unlock my Note 2 if my Android version is 4.1.2

I just want to unlock my Note 2 for now, I don't want to root it yet... but my Android version is 4.1.2 and when I try to follow the instructions but when I get to the part about ( perso SHA256 OFF ) and I do as it says and wait 30 seconds then hit back to return to the previous menu but I don't get the "4th" option ( NW Lock NV Data INITALLIZ ) Have tried to do a data reset but no good....

Tanamir said:
I just want to unlock my Note 2 for now, I don't want to root it yet... but my Android version is 4.1.2 and when I try to follow the instructions but when I get to the part about ( perso SHA256 OFF ) and I do as it says and wait 30 seconds then hit back to return to the previous menu but I don't get the "4th" option ( NW Lock NV Data INITALLIZ ) Have tried to do a data reset but no good....
Click to expand...
Click to collapse
Well you either root and flash the radio, flash an earlier stock firmware, call your provider or pay...

crixley said:
Well you either root and flash the radio, flash an earlier stock firmware, call your provider or pay...
Click to expand...
Click to collapse
Ya,
I'm on it... just found a link for stock roms for Canadian carriers and I am downloading all of them... I am a noob so the first thing I want to try is to revert to an earlier version ( 4.1.1 ) just to see if I can unlock the phone...
Trying to find what you want is difficult because the results you get depend on how you word the query... A lot of times so far I have had no results come back and so I had to re-word the question...

Tanamir said:
Ya,
I'm on it... just found a link for stock roms for Canadian carriers and I am downloading all of them... I am a noob so the first thing I want to try is to revert to an earlier version ( 4.1.1 ) just to see if I can unlock the phone...
Trying to find what you want is difficult because the results you get depend on how you word the query... A lot of times so far I have had no results come back and so I had to re-word the question...
Click to expand...
Click to collapse
Be very cautious, make sure you don't flash an international stock file

In your case (assuming your Note 2 did come from Rogers) simply flash the stock SGH-I317M 4.1.1 ROM with Odin. You might have to factory reset if you get crashes or force closes (this can be done from stock recovery) unlock, then flash the 4.1.2 ROM back with Odin.
Sent from my SGH-T889V using xda app-developers app

Tanamir said:
I just want to unlock my Note 2 for now, I don't want to root it yet... but my Android version is 4.1.2 and when I try to follow the instructions but when I get to the part about ( perso SHA256 OFF ) and I do as it says and wait 30 seconds then hit back to return to the previous menu but I don't get the "4th" option ( NW Lock NV Data INITALLIZ ) Have tried to do a data reset but no good....
Click to expand...
Click to collapse
I usually purchase my phones off contract so just call my provider (AT&T) and request the code, have never been denied.

RiPpeR_dUdE said:
I usually purchase my phones off contract so just call my provider (AT&T) and request the code, have never been denied.
Click to expand...
Click to collapse
It's different with Canadian carriers unfortunately

Unlike AT&T, Canadian carriers haven't been forced by law (or binding court settlement, as AT&T) into giving out unlock codes, even for phones bought outright or whose contract has been fulfilled.
So yeah, using the stock Odin images should keep the flash counter at 0 and be relatively straightforward.
The other method involves a custom recovery, such as TWRP.
Pros:
Much smaller download size. (Odin, TWRP - Odin-flashable version, two modem update zips all total under 75 MB, iirc. Two full stock images: over 2 GB.)
Takes care of custom recovery installation for later and makes rooting a piece of cake.
Cons:
Custom flash counter is triggered.
System status will probably show as modified.

Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

Darkshado said:
In your case (assuming your Note 2 did come from Rogers) simply flash the stock SGH-I317M 4.1.1 ROM with Odin. You might have to factory reset if you get crashes or force closes (this can be done from stock recovery) unlock, then flash the 4.1.2 ROM back with Odin.
Sent from my SGH-T889V using xda app-developers app
Click to expand...
Click to collapse
Got some question, if i'm running international stock rom base running on my AT&T Note 2 i can't unlock my phone? What if I provide just my IMEI number to unlocking company and unlock it, will still screw up my phone?
I have done this on my older phones (3phones Samsung Infuse 4g) and have success no problems at all unlocking them just providing IMEI number to unlocking company.

xxxSuperserieSxxx said:
Got some question, if i'm running international stock rom base running on my AT&T Note 2 i can't unlock my phone? What if I provide just my IMEI number to unlocking company and unlock it, will still screw up my phone?
I have done this on my older phones (3phones Samsung Infuse 4g) and have success no problems at all unlocking them just providing IMEI number to unlocking company.
Click to expand...
Click to collapse
hey SSxxx
note which build and modem you are using
flash a 4.1.1 modem
use the unlock method
flash back the modem you were on.
all in recovery
no need to odin

qkster said:
hey SSxxx
note which build and modem you are using
flash a 4.1.1 modem
use the unlock method
flash back the modem you were on.
all in recovery
no need to odin
Click to expand...
Click to collapse
Im running,
Rom: 4.1.2 stock rom international base
Baseband version: 1317UCAMA4
Thanks in andvanced bro will try that nice seeing you here...

I flash the irug I ball modem and the option option came up to unlock. No new to flash firmware. Go find the modem in the modem theead
Sent from that one guy with the cool phone

Darkshado said:
Unlike AT&T, Canadian carriers haven't been forced by law (or binding court settlement, as AT&T) into giving out unlock codes, even for phones bought outright or whose contract has been fulfilled.
So yeah, using the stock Odin images should keep the flash counter at 0 and be relatively straightforward.
The other method involves a custom recovery, such as TWRP.
Pros:
Much smaller download size. (Odin, TWRP - Odin-flashable version, two modem update zips all total under 75 MB, iirc. Two full stock images: over 2 GB.)
Takes care of custom recovery installation for later and makes rooting a piece of cake.
Cons:
Custom flash counter is triggered.
System status will probably show as modified.
Click to expand...
Click to collapse
Quick question...
How long is it supposed to take to flash the .md5 file?

It's been a while since I've had to flash with Odin, but I'd say a few minutes tops. If it's been sitting there for half an hour, something's not working. Ideally, it is just stuck as "establishing protocol for connection" or something like that and nothing has been written yet.
Make sure that Kies is properly and completely shut down as it will interfere with Odin. (I usually skip installing Kies altogether.)

Darkshado said:
It's been a while since I've had to flash with Odin, but I'd say a few minutes tops. If it's been sitting there for half an hour, something's not working. Ideally, it is just stuck as "establishing protocol for connection" or something like that and nothing has been written yet.
Make sure that Kies is properly and completely shut down as it will interfere with Odin. (I usually skip installing Kies altogether.)
Click to expand...
Click to collapse
So, how do I get out of the download on the phone? The phone is in download mode and has been for hours now.... It seems to me that Odin doesn't recognize the phone. The message box in Odin has messages in it... the last message says " <OSM> All threads completed. ( succeed 0 / failed 0 )
These are the instructions I have been using:
Extract the root66_xxx_I317MVLALJ2.tar.md5 from the .7z file you downloaded.
Use Odin, put phone into download mode [with phone off, hold vol. down + home + power ], connect to computer and open Odin.
once in odin click the PDA field and select the root66_xxx_I317MVLALJ2.tar.md5 you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let phone reboot.
If you have issues flashing with Odin please ensure you are using the microusb cable that came with the phone, users have had issues using other cables.
If you just want a stock, rooted phone with no custom recovery, no plans to flash custom roms, etc. then you can stop HERE.
This is what the message box says in Odin ( ver. 3.04 & 3.07 ) :
<OSM> Enter CS for md5..
<OSM> Check md5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> root66_RWC_I317MVLALJ2.tar.md5 is valid.
<OSM> Checking md5 finished successfully..l
<OSM> Leave CS..
<OSM> All threads completed ( succeed 0 / failed 0 )
The phone just sits in download mode and doesn't seem to do anything. I hit "Finish" in Odin then close the program. Then I shut down the phone and let it reboot and.... VOILA!!! Absolutely no change... The phone still has Android 4.1.2 installed...
Hmmmm, I must be doing something wrong... I just don't know what...

Tanamir, I find I almost always have to back up my pictures and anything else I want to keep, then do a clean wipe of the device ( factory reset ) before flashing anything using the odin and the cable method.
I also find I need to usually remove the external sd card when doing this too. hope that helps.

bwolmarans said:
Tanamir, I find I almost always have to back up my pictures and anything else I want to keep, then do a clean wipe of the device ( factory reset ) before flashing anything using the odin and the cable method.
I also find I need to usually remove the external sd card when doing this too. hope that helps.
Click to expand...
Click to collapse
I did remove everything of value to me that was on the phone before I did the factory reset but that was a couple of days ago... I did some video of my son today and took a few pics of him but that is no problem to download and then I will do another quick wipe and then try flashing again...
There is no MicroSD card in my unit since I did the original factory wipe and subsequent wipes and flashes return 0 results ( i.e.: I still have Android 4.1.2 installed). At this point I am left to ponder whether: a) I am a complete idiot and cant follow basic instructions, b) That there might be a problem with the phone in download mode and it is not responding to Odin, c) That there might be a problem with the ROM's I downloaded from another part of the XDA site...
Default [HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel]
This is a root injected FACTORY Stock I317 Odin Flashable Image. You flash this in Odin just as you would the completely stock ROM from samsung. I've simply injected the su binary and SuperSu app so you now have rooted stock image.
So if you want to keep your device stock yet have the functionality of root without tripping the counter or messing up OTA updates then this would be your best bet.
You can get ODIN here
and the drivers for the SGH-I317 so ODIN can detect your phone can be found at Samsung's site. Click on the Manuals & Downloads tab at the bottom and then on Software for the latest driver.
Instructions:
First, Download Image:
ATT Rom
January 2013 JB 4.1.2 New!
Mirror 1: root66_ATT_I317UCAMA4.7z
October 2012 JB 4.1.1
Mirror 1: root66_ATT_I317UCALJ2.7z
Mirror 2: root66_ATT_I317UCALJ2.7z
Image supplied by Kirbo20. Please thank him for his time in getting the stock image to me.
Bell Rom
January 2013 JB 4.1.2
Download: root66_BMC_I317MVLBMA3.7z
October 2012 JB 4.1.1
Mirror 1: root66_BMC_I317MVLALJ2.7z
Mirror 2: root66_BMC_I317MVLALJ2.7z
Telus Rom
January 2013 JB 4.1.2
Download: root66_TLS_I317MVLBMA3.7z
October 2012 JB 4.1.1
Mirror 1: root66_TLS_I317MVLALJ2.7z
Mirror 2: root66_TLS_I317MVLALJ2.7z
Rogers Rom
January 2013 JB 4.1.2
Download: root66_RWC_I317MVLBMA3.7z
October 2012 JB 4.1.1
Mirror 1: root66_RWC_I317MVLALJ2.7z
Mirror 2: root66_RWC_I317MVLALJ2.7z
Sasktel Rom
January 2013 JB 4.1.2
Download: root66_BWA_I317MVLBMA3.7z
October 2012 JB 4.1.1
Mirror 1: root66_BWA_I317MVLALJ2.7z
Mirror 2: root66_BWA_I317MVLALJ2.7z
Virgin Rom
January 2013 JB 4.1.2
Download: root66_VMC_I317MVLBMA3.7z
October 2012 JB 4.1.1
Mirror 1: root66_VMC_I317MVLALJ2.7z
Mirror 2: root66_VMC_I317MVLALJ2.7z
Second, Extract and Flash:
Extract the root66_xxx_I317MVLALJ2.tar.md5 from the .7z file you downloaded.
Use Odin, put phone into download mode [with phone off, hold vol. down + home + power ], connect to computer and open Odin.
once in odin click the PDA field and select the root66_xxx_I317MVLALJ2.tar.md5 you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let phone reboot.
If you have issues flashing with Odin please ensure you are using the microusb cable that came with the phone, users have had issues using other cables.
If you just want a stock, rooted phone with no custom recovery, no plans to flash custom roms, etc. then you can stop HERE.
Optional, Recovery (will trip counter):
It seems loading any custom recovery will trip the download mode flash counter. Loading a non stock recovery will also prevent you from successfully applying any OTA updates however here is a procedure for any who want a non-stock recovery:
Currently I see TWRP has support for this device so the instructions here will install that recovery.
Option 1: Download GooManager from the Play store. Once installed click the menu and select "Install OpenRecovery Script".
Option 2: Download the TWRP recovery image here. Copy it to the /sdcard of your phone.
Connect your phone to your computer and use adb
type adb shell
once in the shell run su
then
dd if=/sdcard/http://goo.im/devs/OpenRecovery/t0lteatt/openrecovery-twrp-2.4.4.0-t0lteatt.img of=/dev/block/mmcblk0p9
Alternate if unfamiliar with adb commands
Grab android terminal emulator from the play store and run the same commands starting with su and then the dd command.
De-Bloater
If you've made it this far with a stock, rooted phone with CWM or TWRP and you don't want to flash a custom rom (which will do its own de-bloating) you can check out my mrRobinson Note II De-Bloater to easily get rid of bloat system apps you no longer want to see. Simply flash in CWM or TWRP like anything else and you will be presented with a menu system to choose what to remove. If you are unsure it is safe to pick Minimal and still get a decent de-bloat.
Miscellaneous Files
CWM/TWRP Flashable OTA Update: I took the stock I317UCALK7 update.zip that was posted by reinbeau (thanks!) and simply made it flashable with a non-stock recovery preserving root through the process. I see nothing in here that would wipe data but did not test it myself.
Download: root66_OTA_I317_UCALJ2_to_UCALK7.zip
History:
I've injected root into other stock images and those threads have a lot of valuable information which could answer some questions that may arise here. If you have time to do some reading here are a few of the informative ones:
Samsung Galaxy S3 [ATT / Bell / Telus / Rogers / Sasktel ]
Samsung Galaxy S3 [TMO / Wind / Mobilicity]
Also did sprint and vzw but there isn't much there that won't be covered above.
FAQ
Does this remove bloatware?
A: No. It is same as stock, nothing is removed.
Does this use an unsecured boot.img
A: No. This flashes the stock boot.img in the ODIN image.
If my flash counter has been tripped, and I flash this and reset the counter, will it stay at 0.
A: Yes, as long as you don't then flash a non-stock recovery.
More to come...
The answer to my earlier question is A) I am an idiot...
I have had an AHA!!! moment when I realized that there was some critical info missing from what I needed to do... If you read the instructions above they say that you:
Use Odin, put phone into download mode [with phone off, hold vol. down + home + power ], connect to computer and open Odin.
once in odin click the PDA field and select the root66_xxx_I317MVLALJ2.tar.md5 you downloaded.
Leave Auto Reboot and F. Reset Time checked.
click start and
when done let phone reboot.
If you have issues flashing with Odin please ensure you are using the microusb cable that came with the phone, users have had issues using other cables.
This is wrong... I found that in order to work, Odin has to be running BEFORE you connect the phone in download mode so that Odin recognizes the phone, it didn't work for me the other way around.
Although I was able to get the phone to flash, and Odin gave the phone a pass... I closed Odin and disconnected the phone from the computer but something is wrong and the phone is stuck a the "Samsung" screen where the letters kind of glow blue every two seconds... maybe I disconnected the phone from the computer too early so I am going to try to reflash the phone again and I will leave the phone alone to see what happens...
Something is wrong and the phone won't go any further than the aforementioned Samsung screen... I haven't unplugged the phone from the USB cable yet but when I restart the phone it wants to download files from the computer and its a good thing that I installed the Samsung USB driver pkg, but it seems that I am missing something... The notice on the computer says that "Device driver software was not successfully installed" followed by please consult with your device manufacturer for assistance in getting this device installed: Samsung mobile MTP device X Failed.
Help.

Hello Tanamir,
Got your PM but I'd rather answer it here. There's a bit of a) in your situation
DO NOT cross-flash between Note 2 variants unless you know what you're doing.
Root doesn't matter for this, and you could just as well flash the unmodified Odin images (either from here or sammobile). But let's stick with the mrRobinson ROMs since you've already got them and they'll work. (I checked, and they do contain the modem image, which I wasn't entirely sure of at first.)
The "blue glow" Samsung screen is the boot animation, your phone is stuck there in what is called a boot loop. Most likely, something in the 4.1.1 ALJ2 ROM doesn't like the data from your previous 4.1.2 BMA3 installation. In this situation a factory reset from recovery should solve it. (Also known as "clearing user data", I forget the exact term used in the Samsung stock recovery.) To boot in recovery, with the phone powered off: volume up + home + power. You might need to hold it and see the Samsung text flash twice before releasing.
Good luck,
Darkshado

Darkshado said:
Hello Tanamir,
Got your PM but I'd rather answer it here. There's a bit of a) in your situation
DO NOT cross-flash between Note 2 variants unless you know what you're doing.
Root doesn't matter for this, and you could just as well flash the unmodified Odin images (either from here or sammobile). But let's stick with the mrRobinson ROMs since you've already got them and they'll work. (I checked, and they do contain the modem image, which I wasn't entirely sure of at first.)
The "blue glow" Samsung screen is the boot animation, your phone is stuck there in what is called a boot loop. Most likely, something in the 4.1.1 ALJ2 ROM doesn't like the data from your previous 4.1.2 BMA3 installation. In this situation a factory reset from recovery should solve it. (Also known as "clearing user data", I forget the exact term used in the Samsung stock recovery.) To boot in recovery, with the phone powered off: volume up + home + power. You might need to hold it and see the Samsung text flash twice before releasing.
Good luck,
Darkshado
Click to expand...
Click to collapse
Ya,
I'm a noob, but I try to figure out whats going on before I ask for help... Anyway, I was afraid you or someone else was gonna tell me I was eating Boot Loops... thanks, I've had quite enough... *BURP*... I kinda had that feeling, so I powered down the phone and went back into download mode and decided to try to go back to 4.1.2. But I didn't know about recovery so I decided to try to go back to Rogers 4.1.2 from MrRobinson ROM and it worked. I got the phone back but it is still locked to Rogers. Anyhow, what I wanted to try now that I am using this altered ROM (Oh yeah, I found this SuperSU icon in my apps folder...) was to try to go back to 4.1.1 now because of the 4.1.2 ROM that is now installed. ( They are both MrRobinson ROM's so they should be compatible, whereas before I was flashing back from a stock ROM to a modified one...) that is my thinking. As far as the recovery option goes, would that do me any good at this point? My phone is working, albeit now with an altered ROM and it is still locked to Rogers, although when I try to flash back this time I hope it works.... GOD, why am I reminded of "Back to the Future"?
Thanks for the info, talk atcha soon...
Tanamir

[Q] update to 4.4 from 4.3 +clean some bugs

Hi all my name is Blake and I'm a noob. (Sigh) thanks in advance for answering my stupid questions and being the awesome intelligent human bada$$es you are and helping teach me to better understand and operate my phone! So I rooted my phone a while back (4.3) or at least attempted it but I think Knox or something along those lines was preventing the process from completing so I had a friend help me out to complete the root so I'm still not 100% on how to do this. So I want to upgrade to 4.4 assuming it's better but more importantly my phone has a lot of quirks and bugs that annoy the living crap out of me and I won't waste u r time listing them unless you need me to and I'm hoping updating will solve some of them and if not I'll be back to forum surfing... anyways I'm rooted and need to know how to get to where I can get the ota update and then root it or however would be easiest to get the update and back to being rooted? I tried reading and understanding the existing threads but I'm still learning the terminology and i couldn't quite understand the ones i could find. Also this is probably a stupid question but is there an app or anything that will magically go through my phone and fix any stupid bugs and stuff!

Also to show my appreciation if u guys have like a YouTube channel i can like and subscribe to or anything i can do to show my appreciation I'd be glad to do so just send me a link thanks again you're my hero!

magikalbum said:
Also to show my appreciation if u guys have like a YouTube channel i can like and subscribe to or anything i can do to show my appreciation I'd be glad to do so just send me a link thanks again you're my hero!
Click to expand...
Click to collapse
I know you wanted a video I don't have all of the equipment to do so .. this is just a lot of words but simple easy steps.
Best possible solution for you if you really wanted the 4.4 update (nothing really has changed except the basic updates (firmware/modem)
... nothing noticeable except when you click on About Phone lol and you see 4.4.2 and the description of your system. That's really it.
But if you really want to give it a try the best solution for you is:
1 ALWAYS BACK UP YOUR PHONE!
This WILL BE UNROOTED BUT WILL GIVE THE OPTION TO BE ROOTED IF YOU WOULD LIKE
2 Download Odin if you haven't already and download the .tar file for 4.4.2 (the OTA Update)
When you extracted everything and opened Odin make sure Auto Reboot and F Reset Time is the ONLY ones checked.
3 Put the .tar file in PDA on Odin and put your phone in download mode (home, vol down, and power) when it comes up press vol up and it will show downloading .. it may show NOT RESPONDING give it a minute it usually will load up
Attach the usb cable from computer to phone once it registers it (will say added) click start. let it finish and you will have a complete wipe of 4.4.2 STOCK ROM --- UNROOTED!
FOLLOW THESE STEPS (COLOR MATCH) TO BE ROOTED ..... 4.4.2 ROOTED OR 4.3 ROOTED
-THIS IS THE START FOR BOTH --
1 Download your custom recovery (Philz or TWRP) ... I use Philz it's simple and and does everything for you to make sure it goes through.
2 Open Odin once more (same checked) turn your phone off wait for the vibration to indicate it is completely off then put it in download mode.
3 Place your recovery in PDA then attach phone and click start.
It will reboot just turn phone off and enter recovery mode (home, vol UP, and power). If the recovery doesn't show (sometimes it won't due to knox again) Then try again this way:
Phone off, place recovery in PDA, attach phone, and UNCLICK Auto-Reboot and push start. It will show downloading wait for Odin to show pass then boot in recovery from the screen you are on by just pushing home vol up and power. It should load that time.
Once it's loaded...
FOR 4.4.2 - ROOTED
3. Factory reset/clean to install new rom ...
DO NOT wipe cache just simply factory reset ..wait.. done ... clean to install new rom .. wait .. done.
If you do you will get a Status 7 or an error message.
4. Flash rom
5. Reboot
-It may ask you if you want to disable custom recovery make sure you hit NO!
You will need to update SU on playstore. And you should be good to go (had problems the first few times).
FOR 4.3 - ROOTED
DO NOT TRY FLASHING .TAR THROUGH ODIN. It will fail everytime because you can not downgrade firmware through it.
1. You will need to go back to stock unrooted with this HERE (MC2 Download only)
2 Make sure you have the MC2 Download -- or you will receive a Status 7 .. which means you don't have the right rom to update from.
3 Once you're on the MC2 firmware I believe it is the 4.2 version.
4 Turn off phone, enter recovery mode and flash this MC2 to Mk4 Rooted (NEED TO HAVE MC2 first!)
5 Reboot - if it asks to disable custom recovery make sure you press NO or it will unroot it at start up.
.

[Q] galaxy s3 I747 wont boot past Samsung Galaxy s3 Logo, Did i brick my phone???

I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!

baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app

baruchadi said:
I was trying to carrier unlock my phone, and to do that i tried to downgrade it 4.3 to 4.1.1, and only after i had pressed the button, i had noticed that this might brick my phone in a comment in one of the forums, this is what i did:
http://forum.xda-developers.com/showthread.php?t=2625461
after following this and trying to run odin with it, odin returned "FAIL", and due to my high level of stupidity at the time, i tried to use the original 4.1.1 as my PDA in odin right after, i didnt reboot or anything, just pressed start again with the other tar.md5 file....
so now i cannot go past the samsung galaxy s3 logo when booting. I CAN go into download mode though, but i have no clue what i am supposed to do afterwards
i have the Galaxy S 3 i747 (was 4.3 before the whole mess) at&t carrier, i am trying to unlock it because i am travelling and need a phone.
please help me fix it, i do not care about the warranty since i dont have it anymore anyways, as long as the phone is working
also, if possible, i also need to unlock it afterwards, any help is HIGHLY appreciated, thanks!
Click to expand...
Click to collapse
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.

KorGuy123 said:
Downgrading your boot loader from 4.3 is a guaranteed brick. I'm not sure if the brick will get you to the Samsung screen.
If you're already assuming its bricked reboot into recovery and do a full wipe. Restore a nandroid of something if you have one or try flashing a custom ROM. Because Odin failed maybe it never flashed the boot loader.
Worth a try
Sent from my SGH-I747M using XDA Free mobile app
Click to expand...
Click to collapse
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
Larry2999 said:
Welcome to the forum! Wished you'd come in much earlier though as you would have found you CANNOT downgrade from 4.3 to 4.1.1 to free unlock. Sorry, but once you are on 4.3, the surest way to unlock is to obtain the unlock code from the carrier or purchase one online. Sounds like you do have a soft brick. If your phone is still booting to the Samsung logo, then it's only a soft brick. Attempting to downgrade the 4.3 bootloader usually results in a hard brick so you may be in luck.
To fix this first, try to see if you can boot to recovery mode and do a hard wipe/factory reset. If you are able to boot to recovery (or download) mode then you have little to worry about. If the reset does not work, you can flash custom recovery via Odin and follow the instructions in the thread below to restore stock 4.3. Afraid, you have to revert to full stock 4.3 to get the phone back in working order and don't even think about 4.1.1.
http://forum.xda-developers.com/showthread.php?t=2658486
If you are not able to get to recovery, then you can see if you can boot from a debrick image following the instructions (on the first page) of the thread below ...
http://forum.xda-developers.com/showthread.php?t=2549068
Once your phone is working normally, you can request the unlock code from AT&T via the request form below. If eligible, they should provide this. Otherwise, you would have to buy one online ....
https://www.att.com/deviceunlock/client/en_US/
Let me know if you need any further help.
Click to expand...
Click to collapse
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!

baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
It's time to start reading. Before doing any flashing/modding, you should make sure you understand what you're doing and know the risks.
Now as for Odin, it's quite straight forward. Phone needs to be in download mode, you put the PDA file in Odin and flash (if it's a Odin one-click, just need to hit start). One thing is to not interrupt it! Especially if flashing bootloaders cause that will brick your phone. Also, don't downgrade bootloaders.
There are a few guides in the sticky, I suggest you take an hour or two reading them so things like that don't happen again (or that you know what to do if it does).
GL!

baruchadi said:
I tried wiping everything, i also wiped cache, still didn't boot, thanks though!
I am able to get to recovery, but the first link isn't very clear.... i am not really familiar with odin and all this other stuff... lol, i am now downloading the files it says to download in the first link though, can you maybe tell me in a quick list what exactly im supposed to do?
thanks!
Click to expand...
Click to collapse
Alright. If wipe/reset didn't work, you'll need to restore full stock 4.3 via custom recovery. Here's what we need to do....
1) Download the Odin flashable *.Tar file for custom recovery. I prefer TWRP because of the GUI so that's where I'm pointing you to ...
http://techerrata.com/file/twrp2/d2att/openrecovery-twrp-2.6.3.1-d2att.tar
2) Download the stock restore file for 4.3 from the thread below... If you are using TWRP, then the first link is the one you need
http://forum.xda-developers.com/showthread.php?t=2658486
3) Copy the stock restore zip file to a good quality (micro) SD card
4) I presume you have Odin already so you will use this to flash custom recovery to your phone. Run Odin.exe on your PC. If you are using Odin v.3.09 then you need the AP tab. For all other versions, use the PDA tab. Navigate to the custom recovery *.Tar file you downloaded earlier and place this in the PDA (or AP tab). Leave the default settings as is and do not check/uncheck any boxes other than the default settings.
5) Boot the phone to download mode via the 3-button combo (Volume Down/Home/Power). When you get to Odin (Download) mode, press volume up to continue. Connect the phone to your PC with a good quality micro USB cable. Wait until Odin has recognized the device then click on the Start button to start firmware installation (flashing). Wait for the flashing to end and the <Pass> message. Disconnect the phone from the PC and pull the battery to stop auto reboot.
6) Place the micro SD card with the stock restore zip in your phone. Replace the battery and boot to recovery mode. If you were successful with the firmware flashing above, it should boot you to custom recovery.
7) Select install from external card and navigate to the stock restore zip file. Select this file and swipe the screen to start firmware installation. Wait for installation to complete. Then clear your cache/dalvik and reboot to system.
This will hopefully do it.

[HELP!] Odin Firmware flash failed at hidden.img. Stuck in DL Mode. T700. Plz Help Me

Hi Everyone,
I am a new owner of a soft-bricked SM-T700. I am feeling very down and need some advice. I will be as thorough as I possibly can and I would truly, truly appreciate some help and advice from you kind folks. This is the first time I have had a bricked device out of my many Android devices.
My PLAN:
-Root
-Custom Recovery
-Nandroid Backup
-Backup EFS
-Flash stock western country firmware
What HAPPENED
Today I bought a wifi T700. I bought it in my hometown, which is China. Whenever I buy a new Android device in China my first action is to ensure it doesn't have any hardware/warranty issues. I then go about reflashing a western firmware so I can use Google services.
1) First I rooted using CF-Auto Root. That worked fine. I confirmed that I had root using an app called root checker.
2) I then attempted to flash TWRP recovery by following the instructions here: http://teamw.in/project/twrp2/238
- First I tried flashing the .tar file using Odin. As soon as I hit 'Start' Odin froze and I got the Windows error saying "Odin Downloader Has Stopped Working", asking to close the program. I close the program. I tried this several times then rebooted. It seemed as though the phone booted fine.
- I then tried using their own software, TWRP manager, here: http://jmzsoftware.com/twrp-manager-4. This app just crashed every time I booted it. I submitted an error log.
- I then tried using 'Flashify' as suggested by someone here on XDA. Once I did that it said flashed successfully and would I like to reboot. I said yes. This is when my troubles started.
3) Upon reboot it immediately booted into a sparse looking 'Download Mode' screen, all in English (the normal one on mine has some Chinese too) without the volume button options to reboot or continue. It just went straight into this screen.
After trying to reboot the phone using several power button holds and key combinations, it appears I am stuck in this screen, so I thought I had no chance of doing a NADROID backup as originally planned, so I decided to try my luck and flash the western firmware.
I tried to flash the version of the firmware provided here: http://forum.xda-developers.com/showthread.php?t=2798835
http://www.androidfilehost.com/?fid=23501681358556680
It got all the way through the install until it hit the hidden.img and then failed. I've attached a screen capture.
A few notes;
I have tried using two different USB cables (the one that came with it, and the one that came with my HTC One). I have tried several USB plugs, including the one in the back of my PC. I allowed Odin to do it's MD5 check and it said the file checks out.
I have tried using the Kies emergency Firmware recovery. Pffft! As it that was going to work. Damn Kies.
I sound like I've still got my sense of humor, but actually I am really cut up about this. It is so much money for a tablet and now it is useless unless I can get s firmware that will flash.
I don't have my stock Chinese firmware. That is T700ZCU1ANF4/T700CHN1ANF4/T700ZCU1ANF4/T700ZCU1ANF4 (CHN).
Questions:
Does anyone know where I could find the stock Chinese firmware to try flashing back to that?
Does anyone have the .PIT file and instructions on how to flash that, because I have read in other threads that it solves the hidden.img problem.
Does anyone know why this may have happened and have any alternative suggestions?
Could it have been the TWRP that actually caused this? The thread here indicates others aren't having trouble. Why would it have frozen for me?
I will try anything at this point. I am desperate.
Thanks so much in advance. Please come through XDA! Please come through Galaxy Tab S owners!!!!!!
-------------------------------------------
CLOSURE EDIT: I managed to flash Australian firmware, after reinstalling Kies, uninstalling and reinstalled the device drivers. I also made sure all Kies processes were killed before flashing with Odin.
For people in a similar situation I would urge them to have patience and keep trying to flash stock firmware.

Private Message UpInTheAir and see what he thinks.

Well let me start out by saying i have done some truely horrible things to my tablet in the proceas of porting CM 11. Bad kernels, messing up the partitions, you name it ive probably done it at this point.
I would try using heimdall. Flash one of the recoveries.. and try formatting your partitions.

The program crashing is when you should back off from trying to flash. Reassess what you did and what happened and if it's failing at a point flash the stock back before rebooting.
Continuing blindly was the problem. On something as expensive as a tablet never continue past a point where something goes wrong without reflashing back to stock and starting again.
As eousphoros said Use heimdall and flash a recovery.
Good luck.

eousphoros said:
Well let me start out by saying i have done some truely horrible things to my tablet in the proceas of porting CM 11. Bad kernels, messing up the partitions, you name it ive probably done it at this point.
I would try using heimdall. Flash one of the recoveries.. and try formatting your partitions.
Click to expand...
Click to collapse
Hi All,
Thanks for taking the time to reply.
You are certainly right that it is my fault and I should have stopped at some point and reassessed what was happening.
Can you please give me some more information about the steps you have offered? I am researching heimdall now, but if you could give some steps or advice that would be much appreciated.
It's probably going to be difficult because I assume we are in different timezones. I will persevere and try to get this worked out.

I have downloaded Heimdall and understand that it is an alternative to using Odin.
I currently have three questions about Heimdall.
1. Do I need to do the install drivers step if I have already installed the drivers for my device? Is this some step that actually replaces the current drivers with ones that are required for Heimdall to operate? I ask them because when I list USB devices, my tab is not shown up as Samsung Composite Device. It is actually shown as two separate entries, looking like generic USB entries.
2. Do I need to have a valid PIT file in order to run a custom Heimdall flash?
3. Which partition should I select if/when I run the Heimdall flash?
I'm dying a little inside every time I look at my tablet

Install heimdall
Download a recovery, I am going to pimp mine. http://forum.xda-developers.com/galaxy-tab-s/general/cwm-recovery-6-0-5-0-galaxy-tab-s-8-4-t2824099.
Run sudo ~/git/Heimdall/heimdall/heimdall flash --RECOVERY cwm6.0.5.0-2.img. Wait for it to complete, your tablet will reboot and will probably fail like it has been.
Hold down Power + Vol Down + Home button... wait for the "Press vol up to continue, press vol down to cancel"
Press vol down to cancel, then immediately hold down Power + Vol Up + Home button till you see the recovery screen pop up.
If you get the recovery screen your tablet can probably still be saved. Woo!
So then download http://forum.xda-developers.com/showthread.php?t=2798835 (Which i think you already have)
Unzip it, there will be a tar file. tar xvf T700....something.tar.md5 -C some_directory
You will get a bunch of img files. From those you should be able to finish the recovery and hopefully return full function to your device. (Which unless something is physically broken you will most likely be able to do.) Good Luck! And again this is all done at your own risk, please dont sue me.

eousphoros said:
Install heimdall
Download a recovery, I am going to pimp mine. http://forum.xda-developers.com/galaxy-tab-s/general/cwm-recovery-6-0-5-0-galaxy-tab-s-8-4-t2824099.
Run sudo ~/git/Heimdall/heimdall/heimdall flash --RECOVERY cwm6.0.5.0-2.img. Wait for it to complete, your tablet will reboot and will probably fail like it has been.
Hold down Power + Vol Down + Home button... wait for the "Press vol up to continue, press vol down to cancel"
Press vol down to cancel, then immediately hold down Power + Vol Up + Home button till you see the recovery screen pop up.
If you get the recovery screen your tablet can probably still be saved. Woo!
So then download http://forum.xda-developers.com/showthread.php?t=2798835 (Which i think you already have)
Unzip it, there will be a tar file. tar xvf T700....something.tar.md5 -C some_directory
You will get a bunch of img files. From those you should be able to finish the recovery and hopefully return full function to your device. (Which unless something is physically broken you will most likely be able to do.) Good Luck! And again this is all done at your own risk, please dont sue me.
Click to expand...
Click to collapse
First of all, let me just say that OH MY F#@$ING GOD I THINK THE NIGHTMARE IS OVER!!!! I managed to flash the Australian Firmware successfully. It has now booted fine, I have factory reset and I am in the process of setting up the device afresh.
Having said that, when I do come to reroot and install a custom recovery, I will definitely take a look at yours. Was this here 12 hours ago? I looked and couldn't find anything about CWM except for a short thread and an unofficial port. I have never tried TWRP before and I will avoid it like the plague in the future. I have NEVER had trouble with CWM.
When (if ever) I get the nerve up to give this another go, I will try your CWM.
Thanks again.
I am so relieved right now.....

And make a Nandroid first this time

Hey,
I had the exact same issue with my Galaxy Note 8, every time I tried to install European or custom Rom.
The only way to get the tab back was to flash with the Chinese firmware. You may find it easily on Baidu.
Since it happened also with a note 2 and note 3, I stopped buying Android device in China... Unless you can make sure that you buy a model coming from HK.

Hi everybody.
In order not to create another Thread I would like to leave a request for help in here while searching the answer myself.
I've messed up with SM-T700 and it is suffering a "near brick expirience" now. D:
I wanted to install the TWRP in order to backup the stock ROM before proceeding to anything else. So I put it in download mode. In Odin. 3.09 I put the TWRP under the AP section, the auto-reboot and f-reset were checked. (later I understood that I look at a different chrome tab and followed the instuction for auto-root flashing in via Odin instead of TWRP's. Stupid me) THen I proceeded with flashing and it was succesfull. After that I rebooted to recovery but it was not TWRP but stock. So I went to Download mode again and decided to repeat the procedure. Hower this time, and each time after that Odin stuck with the SetupConnection... The tab itself is stuck in Downloading Do not tur off target!! and does not react to any combinations of buttons.
Looking for a piece of advice here.
At least Odin is detecting the tab is a good sign right?
Attaching the photo and screenshot just in case.

ky3bmu4 said:
Hi everybody.
In order not to create another Thread I would like to leave a request for help in here while searching the answer myself.
I've messed up with SM-T700 and it is suffering a "near brick expirience" now. D:
I wanted to install the TWRP in order to backup the stock ROM before proceeding to anything else. So I put it in download mode. In Odin. 3.09 I put the TWRP under the AP section, the auto-reboot and f-reset were checked. (later I understood that I look at a different chrome tab and followed the instuction for auto-root flashing in via Odin instead of TWRP's. Stupid me) THen I proceeded with flashing and it was succesfull. After that I rebooted to recovery but it was not TWRP but stock. So I went to Download mode again and decided to repeat the procedure. Hower this time, and each time after that Odin stuck with the SetupConnection... The tab itself is stuck in Downloading Do not tur off target!! and does not react to any combinations of buttons.
Looking for a piece of advice here.
At least Odin is detecting the tab is a good sign right?
Attaching the photo and screenshot just in case.
Click to expand...
Click to collapse
Replying to myself: The tab began to respond to buttons so now I succesfully rebooted it and will continue with Rooting then recovery
Added: Rooted successful but the same problem as described above occured when I tryied to flash TWRP in Odin under PDA tab unchecked the auto-reboot

ky3bmu4 said:
Replying to myself: The tab began to respond to buttons so now I succesfully rebooted it and will continue with Rooting then recovery
Added: Rooted successful but the same problem as described above occured when I tryied to flash TWRP in Odin under PDA tab unchecked the auto-reboot
Click to expand...
Click to collapse
Yeah I've had a really bad experience with TWRP on this device. Try flashing a firmware from sammobile.com or elsewhere to at least get it up and running again. Try to do that as quickly as possible too, so you don't have to leave the device in download mode all night. I think that is what caused the battery swelling in my first device that I had to return.
I'm going to stick with CWM when I work up the courage to try again....

pierrotee said:
Yeah I've had a really bad experience with TWRP on this device. Try flashing a firmware from sammobile.com or elsewhere to at least get it up and running again. Try to do that as quickly as possible too, so you don't have to leave the device in download mode all night. I think that is what caused the battery swelling in my first device that I had to return.
I'm going to stick with CWM when I work up the courage to try again....
Click to expand...
Click to collapse
Hi thx for reply. Actually it managed to unstuck from Download mode in 10-15 minutes. It happened twice to me.

ky3bmu4 said:
Hi thx for reply. Actually it managed to unstuck from Download mode in 10-15 minutes. It happened twice to me.
Click to expand...
Click to collapse
Cool! So do you now have root and custom recovery?

pierrotee said:
Cool! So do you now have root and custom recovery?
Click to expand...
Click to collapse
Yeah))

TWRP installs OK via TWRP Manager
I installed TWRP Manager, selected 'klimtwifi' as the device, and it successfully installed TWRP 2.7.1.1 without a hitch.
From TWRP I then immediately performed a nandroid backup of everything but the caches to my microSD card and encountered no problems.
The last step was to enable writing to my microSD card by installing NextApp SDFix.

My SM-T700 is bricked as well and I tried to flash a custom recovery with Heimdall on Mac but it gave me the Error "Claiming Interface failed". Seems like you really need the pit.

Note 2 stuck at Start Up screen. Please help

My Galaxy Note 2 is stuck at the Start up screen screen. Where its an all black bg and simply says Samsung Galaxy Note II
I have tried using recovery mode, cleared cache, and reset to factory. Neither troubleshoot method worked.
I have tried numerous Odin autoroots. none work. Whenever I try to root it fails. Im guessing it might be because I dont have Dev Debug enable and I cant get into my phone to enable it. because of this issue
I have tried looking for TWRP .tar but every file I download the file is always a .img
The Model of the phone is a SGH-T889 (T-mobile Note II)
I am all out of ideas, and I dont know what to do. I have been search for answers for hours and everytime I think I found a solution it doesnt work.

What ROM was your phone on when this happened ?
Can you get int to download mode ? If yes try flashing stock ROM and see if it helps.

ciphercodes said:
What ROM was your phone on when this happened ?
Can you get int to download mode ? If yes try flashing stock ROM and see if it helps.
Click to expand...
Click to collapse
It was on the offical default rom. the phone was never modded, or rooted.
My niece downloads a bunch of kiddie games onto the phone, we constantly have to uninstall them. My thoughts and the T-mobile tech suspects that it the crash may have been caused my too many updates or a bad updated file most likely due to the games or game.
I can get the phone into download mode, and recovery mode.
In reovery mode I have 6 options
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cashe partition
apply update from cache
I have tried Apply update from cache, Wipe cache partition, then Wipe data.factory reset. I also attempted to put a CF auto root .md5 file and a KIES .md5 file which I believe is a stock firmware file on a SD card. to try to use the apply update from external storage option, but neither file showed up when I went into the option. So I guess I didnt have the right sort of file.
So recovery didnt work so I tried using Odin v3.07 and Odin v3.09 with CF auto root files for the SGH-T889, that didnt work, ecerytime I tried to apply it, It was always Fail within seconds. I tried other root files that are made for other versions of the Galaxt Note 2 like the GT-N1700 but those also simply failed.
I tried using what I believe to be stock frimware files with Odin. and those also Failed.
Im not exactly the best person with these. I learn mostly what I know from the internet and reading various forums, youtube videos, and other people experiences. I cannot find anyone who's problem has not yet been fixed through the above methods. so I really dont know where to go from here.
I think the reason I cant Flash from PC is because it might be possible USB Debugging is not enabled. Not sure if this is what is causing all the Fails in odin

BramaKnox said:
It was on the offical default rom. the phone was never modded, or rooted.
My niece downloads a bunch of kiddie games onto the phone, we constantly have to uninstall them. My thoughts and the T-mobile tech suspects that it the crash may have been caused my too many updates or a bad updated file most likely due to the games or game.
I can get the phone into download mode, and recovery mode.
In reovery mode I have 6 options
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cashe partition
apply update from cache
I have tried Apply update from cache, Wipe cache partition, then Wipe data.factory reset. I also attempted to put a CF auto root .md5 file and a KIES .md5 file which I believe is a stock firmware file on a SD card. to try to use the apply update from external storage option, but neither file showed up when I went into the option. So I guess I didnt have the right sort of file.
So recovery didnt work so I tried using Odin v3.07 and Odin v3.09 with CF auto root files for the SGH-T889, that didnt work, ecerytime I tried to apply it, It was always Fail within seconds. I tried other root files that are made for other versions of the Galaxt Note 2 like the GT-N1700 but those also simply failed.
I tried using what I believe to be stock frimware files with Odin. and those also Failed.
Im not exactly the best person with these. I learn mostly what I know from the internet and reading various forums, youtube videos, and other people experiences. I cannot find anyone who's problem has not yet been fixed through the above methods. so I really dont know where to go from here.
I think the reason I cant Flash from PC is because it might be possible USB Debugging is not enabled. Not sure if this is what is causing all the Fails in odin
Click to expand...
Click to collapse
Lets see if we can get this resolved.
1) Do you remember what version of Android the phone was on 4.3 or 4.1.2 ?
2) Put your phone in download mode then connect to your computer via usb. Start Odin in admin mode (right click and run as admin).
3) Now do you see ID:COM section turn blue ? Under message you can see "Added!". If you see this then phone is recognized by Odin.
4) If your phone was on 4.3 then download this most up to date firmware - from here http://www.sammobile.com/firmwares/download/22863/T889UVUCMK7_T889TMBCMK7_TMB/
5) Once downloaded, extract the file(use 7zip or winrar), once extracted you will see a file with .md5 extension.
6) Now going back to ODIN, click on PDA and then browse to this file which you just extracted.
7) This takes some time, once done you should see a message like "Checking MD5 finished successfully", "Leave CS".
8) You can leave Auto reboot and F-reset time checked.
9) Now click Start and let the process finish.
10) If everything goes fine you should see a green message "Pass"
Let me know how it goes.

I have the same problem as the OP (boots only up to Samsung logo with black bg) but it was not caused by niece downloading games but instead from trying to install jedi masterx2 rom.
I did what ciphercodes recommended and put phone in download mode and odin went through the motions of installing the stock os (in my case version 4.3) but after apparently installing the rom it again booted up to Samsung note II logo in black bg.
luckily I can install either Clockword mod recovery v6.0.4.3 or teamwin v2.8.6.0
The clockword mod recovery can read the external sd card (whereas funnily enough the teamwin can't) and I can attempt recovery from previous backups on cmr or to install a rom from zip file but neither of these work - reboots again to Samsung logo in black background after apparently installing the rom.
both teamwin and cwr mention that they can't mount system and that's probably why no rom is install either using cwr or odin so my guess is that I have to reformat the partitions cause probably efs file is corrupt but I don't know how to do that and I have done extensive search in google but have not found a solution
so ciphercodes if you or anyone reading this can help please reply to this message

ciphercodes said:
Lets see if we can get this resolved.
1) Do you remember what version of Android the phone was on 4.3 or 4.1.2 ?
2) Put your phone in download mode then connect to your computer via usb. Start Odin in admin mode (right click and run as admin).
3) Now do you see ID:COM section turn blue ? Under message you can see "Added!". If you see this then phone is recognized by Odin.
4) If your phone was on 4.3 then download this most up to date firmware - from here
5) Once downloaded, extract the file(use 7zip or winrar), once extracted you will see a file with .md5 extension.
6) Now going back to ODIN, click on PDA and then browse to this file which you just extracted.
7) This takes some time, once done you should see a message like "Checking MD5 finished successfully", "Leave CS".
8) You can leave Auto reboot and F-reset time checked.
9) Now click Start and let the process finish.
10) If everything goes fine you should see a green message "Pass"
Let me know how it goes.
Click to expand...
Click to collapse
I am uncertain of which version the phone was on. If you need I can call t-mobile and have them tell me which version it was on.
I did these steps. the file took a hour to download. and It still didn't work. I follow all steps down to the exact. and when I pressed start. within one second it said FAIL. just the other attempts I made.

BramaKnox said:
I am uncertain of which version the phone was on. If you need I can call t-mobile and have them tell me which version it was on.
I did these steps. the file took a hour to download. and It still didn't work. I follow all steps down to the exact. and when I pressed start. within one second it said FAIL. just the other attempts I made.
Click to expand...
Click to collapse
Unless your t889 Note II was sitting in a drawer and not being updated for the last year or so you probably have 4.3
When you go to download mode do you see "custom binary download: yes ..."
and do you see "knox warranty void:" ?
if so, your phone has been rooted.
but unlike your case, when I try to install stock rom through Odin, it goes through the motions of installing and gives message pass - that is that the stock rom has been installed, but unfortunately it has not installed any rom that my phone can read.

koyanishi said:
Unless your t889 Note II was sitting in a drawer and not being updated for the last year or so you probably have 4.3
When you go to download mode do you see "custom binary download: yes ..."
and do you see "knox warranty void:" ?
if so, your phone has been rooted.
but unlike your case, when I try to install stock rom through Odin, it goes through the motions of installing and gives message pass - that is that the stock rom has been installed, but unfortunately it has not installed any rom that my phone can read.
Click to expand...
Click to collapse
No it says
Product Name: SGH-T889
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Knox Warranty Void: 0
RP SWAEV: A2

BramaKnox said:
No it says
Product Name: SGH-T889
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Knox Warranty Void: 0
RP SWAEV: A2
Click to expand...
Click to collapse
Then you have an un rooted 4.3 rom because the 4.1.2 did not have knox

koyanishi said:
Then you have an un rooted 4.3 rom because the 4.1.2 did not have knox
Click to expand...
Click to collapse
Okay thank you, well then link ciphercodes gave me for the firmware was the right one. But still Failed. *Sigh*

BramaKnox said:
Okay thank you, well then link ciphercodes gave me for the firmware was the right one. But still Failed. *Sigh*
Click to expand...
Click to collapse
Since your phone is not rooted then I think that ciphercodes advice will not work as you can only install a stock rom that way only if your phone is first rooted.
Probably you should try to root your phone using instructions from this thread
http://forum.xda-developers.com/showthread.php?t=2562994
But this might not work for you as it could be that efs file is corrupted or something else as we both boot up to a black screen that only has Samsung logo

koyanishi said:
Since your phone is not rooted then I think that ciphercodes advice will not work as you can only install a stock rom that way only if your phone is first rooted.
Probably you should try to root your phone using instructions from this thread
http://forum.xda-developers.com/showthread.php?t=2562994
But this might not work for you as it could be that efs file is corrupted or something else as we both boot up to a black screen that only has Samsung logo
Click to expand...
Click to collapse
Yeah the chainfire root fail as well. I have tried every file for all the Galaxy II's including mines. none work. Always FAIL in Odin. I'm guessing there is just nothing I can do

BramaKnox said:
Yeah the chainfire root fail as well. I have tried every file for all the Galaxy II's including mines. none work. Always FAIL in Odin. I'm guessing there is just nothing I can do
Click to expand...
Click to collapse
Since your phone is not rooted you may be able to get it repaired under warranty. I think that Samsung warranty is only good for a year, but if you purchased your phone with a American Express gold card (I think other gold cards will also apply) your warranty is extended to double what the original was. So perhaps you have a chance to have your credit card pay for the repair.
Otherwise:
I am no expert but if you want to continue playing with your phone before you get expert advice you may want to play with the recovery mode. To enter recovery mode press volume up and home and power buttons at the same time. once you feel vibrate or after a while release the power button but continue to hold volume up and home buttons and then you will enter recovery mode. you may want to go to menu that says wipe data/factory reset and see if that works. It may be that it is like my phone and the system cannot be mounted in which case you will get that message. After you are through to get out of this menu remove the battery.
But please be aware that I am no expert and you are using this info at your own risk
but I think of doing something catastrophic using this advice in my non expert opinion is small.

koyanishi said:
Since your phone is not rooted you may be able to get it repaired under warranty. I think that Samsung warranty is only good for a year, but if you purchased your phone with a American Express gold card (I think other gold cards will also apply) your warranty is extended to double what the original was. So perhaps you have a chance to have your credit card pay for the repair.
Otherwise:
I am no expert but if you want to continue playing with your phone before you get expert advice you may want to play with the recovery mode. To enter recovery mode press volume up and home and power buttons at the same time. once you feel vibrate or after a while release the power button but continue to hold volume up and home buttons and then you will enter recovery mode. you may want to go to menu that says wipe data/factory reset and see if that works. It may be that it is like my phone and the system cannot be mounted in which case you will get that message. After you are through to get out of this menu remove the battery.
But please be aware that I am no expert and you are using this info at your own risk
but I think of doing something catastrophic using this advice in my non expert opinion is small.
Click to expand...
Click to collapse
Yeah the warranty is expired. and I have tried recovery mode. thats actually the first step before trying to apply a firmware. So recovery hasnt worked either. Guess I will just have to get a new phone. thank you all for oyu help tho. I apperciate it

I was just reading through the thread.. It doesnt seem like you tried flashing Tmobiles Stock 4.3 Firmware in download mode. If you tried to flash a 4.1.2 Firmware when the phone was already updated then I think thats where it failed. Try again but with the 4.3 Firmware through ODIN. After it finishes try rebooting it manually and/or if it doesnt boot again then go back into recovery and factory/data reset again...shouldnt hurt to try..

Double0EK said:
I was just reading through the thread.. It doesnt seem like you tried flashing Tmobiles Stock 4.3 Firmware in download mode. If you tried to flash a 4.1.2 Firmware when the phone was already updated then I think thats where it failed. Try again but with the 4.3 Firmware through ODIN. After it finishes try rebooting it manually and/or if it doesnt boot again then go back into recovery and factory/data reset again...shouldnt hurt to try..
Click to expand...
Click to collapse
From my knowledge the other person who first replied gave me 4.3 firmeware fild link. But in the chances of it could u provide me with a link to a 4.3 firmware u believe will work, because all the ones I found have not worked