Develop Bugs

[Q] Serious problem with new Samsung Galaxy 3

I'm new to rooting and recently i attempted to root my Samsung galaxy S3 it using the Samsung galaxy S3 toolkit V5. My build was not listed so i selected build #1, I installed the drivers to my pc, went to rooting options, selected option #3 All In One, Enabled USB debugging ans started the process which opened up Odin and started doing its thing, but basically my phone was in Odin mode with the android figure which says downloading... Do not turn off target! but of course I thought it wasn't working and i had to unplug the USB and put it back in (I know I'm stupid Lol)
Now my phone will not boot at all, when i hold up volume power and home a battery image shows up and the phone shuts off again even though its plugged into my computer.
When i hold volume down power and home, this shows up: Warning! A custom os can cause critical problems in phone and installed applications
if you want to download a custom os press the volume up key, otherwhise press volume down to restart phone.
If i press voulume down it does not restart, it simply shuts off again.
If i press volume up it goes back to the downloading android even though it isnt downloading anything.
At the top left corner it says:
ODIN MODE
Product name: SGH-I747M
CUSTOM BINARY DOWNLOAD: Yes (3 counts)
CURRENT BINARY: Custom
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: ENABLE
My phone is not even detected on my computer or by the toolkit anymore, Im not sure if Odin detects it either.
I cant find any help regarding my specific problem and im starting to lose hope. Please help.

Bump

You can still get into Download mode so there is still hope. I'll provide a link I think you should check out. Remember to choose the proper carrier and follow the instructions to flash.
http://forum.xda-developers.com/showthread.php?t=1739426
[HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel]

Yes just go into Odin in down load mode and flash stock rom with root
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

blaker13 said:
Yes just go into Odin in down load mode and flash stock rom with root
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
you can go to downlload mode!! hello you arent a paperweight yet!!!
Use this vid to unbrick your phone-http://www.youtube.com/watch?v=ypmqJbZqOaU&feature=plcp
And a safe root
Root video-http://www.youtube.com/watch?v=XoEVDgjTTdg

jethro650 said:
You can still get into Download mode so there is still hope. I'll provide a link I think you should check out. Remember to choose the proper carrier and follow the instructions to flash.
http://forum.xda-developers.com/showthread.php?t=1739426
[HOWTO] [ROOT] No Tripping Flash Counter - [ATT / Bell / Telus / Rogers / Sasktel]
Click to expand...
Click to collapse
Thanks for the help so far, i used your method but the installation failed so I selected wipe the cache and reboot my phone and when it rebooted it stayed stuck at the blue light and Samsung logo. Now no matter what i do, when the phone restarts it stays stuck at that logo.
When i go back to Odin mode it it says there are now 5 custom binary downloads.

Did you also wipe data/factory reset along with clearing the cache/dalvik cache?

Down load stock firmware for your phone at Samsung.com and flash it in Odin. You can reset flash count with triangle away.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Ok i restored the entire phone and did the process again and it worked. Now i have this thing called superuser.
What excactly can i do now?

The Firestorm7 said:
Ok i restored the entire phone and did the process again and it worked. Now i have this thing called superuser.
What excactly can i do now?
Click to expand...
Click to collapse
Run marathons, leap tall buildings in a single bound.... JUST KIDDING!!!
What do you you WANT to do? You can now use any app labeled "root need". What you do with it is up to you, which is the great thing about android. :good:

Clock work mod problem, please help

Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.

Have you tried twrp?

athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium

athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
flash recovery again in odin but make sure the "auto reboot" box is NOT checked. once its done flashing, unplug it and remove the battery for a second. replace the battery and immediately hold down vol up+home+power. this should take you into cwm if it flashed correctly

this could happen when you didn't root it properly
anyways, if you are rooted(as you said), get twrp and see

+1 for twrp

athens71 said:
I still have root.
Click to expand...
Click to collapse
If you still have root, you might want to try installing CWM directly from your phone, using the dd terminal command to copy CWM into the right partition:
Download the latest CWM .img file from CWM's site: http://www.clockworkmod.com/rommanager
Put the file in your phone. For simplicity reason, I would suggest you put it in the root of your internal SD card. And because you will need to type the whole path+filename in the terminal in your phone, I would also suggest you rename the file to something simple, like cwm.img;
If you don't already have it, install Android Terminal Emulator;
Now, open the terminal emulator, and type the following commands:
Code:
su
dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p18
(That is, if you rename the CWM file to "cwm.img" and you actually put it in the root of your internal SD card. If you put it somewhere else or did not rename your file, you will need to adapt the "if=" part of the command.)
Profit.

athens71 said:
Galaxy S3 from at&t, i rooted my phone as soon as got it several months ago, I've flashed colockwordmode 3 times in the last day or so and i cannot make to work, i followed the steps exactly as described, Odin is showing the green pass, the binary cont is increasing every time I've tried but i can't get the phone to start in recovery mode by holding volume up, home and power! it just reboot and turns the phone on or it goes into the Samsung recovery mode (blue screen). Very frustrating!, anyone can please help.
BTW, when i rooted my phone i installed clockwordmode then and it worked fine, i had not has to use it since, I'm running the stock ROM i want to flash another ROM, before i do that i need to use clockworkmode and that's when i realized that it was not working anymore, then tried to flash it 3 times but no success. I still have root.
Click to expand...
Click to collapse
Just curious: are you trying to flash CWM via Odin? If so where did you get it from? Did you install a botched version of stock recovery maybe (or one that is from another model of S3)? Try TWRP from here http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1. It is at the bottom of the post and it is labeled "Odin Flashable TWRP Recovery" under Miscellaneous files. Download and install via Odin.
And if you are on Jelly Bean, your flash counter will increment in your dealings with custom recoveries and roms. You only option at this point (if you have root still) is to get Triangle Away and run it in order to reset the counter. However, even if you clear your flash counter, if you go back into recovery it will trip again.

drock212 said:
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
I'm still using stock ROM, i'd like to install a custom ROM but i'm reading that you have to have Clockworkmod to do a successful install.
When i check in the files of the phone (sd card) i can see the clockwordmod folder in there there but still can't get it to boot into cwm recovery, only the Samsung recovery and I've tried the volume up home and power button so many times but no success.
Why do you think it worked when i first rooted the phone and not now?
this is frustrating, thanks for the help.

aybarrap1 said:
Just curious: are you trying to flash CWM via Odin? If so where did you get it from? Did you install a botched version of stock recovery maybe (or one that is from another model of S3)? Try TWRP from here http://forum.xda-developers.com/showpost.php?p=28019751&postcount=1. It is at the bottom of the post and it is labeled "Odin Flashable TWRP Recovery" under Miscellaneous files. Download and install via Odin.
And if you are on Jelly Bean, your flash counter will increment in your dealings with custom recoveries and roms. You only option at this point (if you have root still) is to get Triangle Away and run it in order to reset the counter. However, even if you clear your flash counter, if you go back into recovery it will trip again.
Click to expand...
Click to collapse
Yes I've tried 3 times via Odin, i can't remember where i got the cmw file from, it's a tar file (clockworkmod.TAR), the part i don't understand is why when i first rooted the phone in August cwm worked, i used it to install the root and now after trying to install it again 3 times i can't get it to work.
I'm using the stock ROM, not jelly bean.
thanks for any help

xBeerdroiDx said:
flash recovery again in odin but make sure the "auto reboot" box is NOT checked. once its done flashing, unplug it and remove the battery for a second. replace the battery and immediately hold down vol up+home+power. this should take you into cwm if it flashed correctly
Click to expand...
Click to collapse
I've tried it with "auto reboot" check and without but still no luck. Like i said it reboots in the Samsung rm.

androidsavage23 said:
Have you tried twrp?
Click to expand...
Click to collapse
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Thank you

athens71 said:
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Thank you
Click to expand...
Click to collapse
Download goo manager app and open that. There will be an option to "install open recovery" in the menu. Voilà a superior recovery that's easier to use
You can even use it to boot into recovery or install the new update for it.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

athens71 said:
No i have not, i can't find where to get it for galaxy S3 at&t! would you know where i could find it?
Click to expand...
Click to collapse
Easiest way to install TWRP is using GooManager from the Play Store.
1. Open GooManager.
2. Press the menu key to open the contextual menu, and select Install OpenRecoveryScript.
3. The app will ask you to confirm you really want to install a new recovery image.
4. GooManager searches for the correct TWRP build for your device. Look at the Filename line, it should display openrecovery-twrp-2.4.1.0-d2att.img for AT&T or openrecovery-twrp-2.4.1.0-d2can.img for Rogers/Bell/Telus. Again, confirm the installation.
5. Wait for the download to begin. TWRP will install. Done.
If it does not work or if GooManager does not find the correct build for your device -- in this latter case, this should raise a flag for you, as you may not have a SGH-i747/SGH-i747M; double check your phone model --, you can always install TWRP manually. From TWRP website (http://www.teamw.in/project/twrp2), you can grab the IMG file to manually install from the terminal emulator, and a TAR file to install using ODIN.

athens71 said:
I've tried it with "auto reboot" check and without but still no luck. Like i said it reboots in the Samsung rm.
Click to expand...
Click to collapse
Did you try it exactly as i said to?

drock212 said:
This will happen until you load a custom rom I believe. Same thing happened to me then when I installed a rom it started being able to boot into cwm
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
So if that's the case (This will happen until you load a custom ROM) how can i back up my stuff before installing a new ROM? that's the reason i was trying to make cwm work so i could back my stuff.
Is there a different way to do a full back up?
thanks

xBeerdroiDx said:
Did you try it exactly as i said to?
Click to expand...
Click to collapse
Yes i did, when i tried to flash cmw 3 times yesterday, the description was exactly like yours.
thanks you

athens71 said:
Yes i did, when i tried to flash cmw 3 times yesterday, the description was exactly like yours.
thanks you
Click to expand...
Click to collapse
if you have root, download Rom Manager and install cwm from the menu.
i've also heard that, if rooted, you can erase /system/recovery-from-boot.p and /system/etc/install-recovery.sh (using ES File Explorer or Root Explorer) an that will make cwmstick. this is due to newer software versions overwriting your stock recovery on reboot.

xBeerdroiDx said:
if you have root, download Rom Manager and install cwm from the menu.
i've also heard that, if rooted, you can erase /system/recovery-from-boot.p and /system/etc/install-recovery.sh (using ES File Explorer or Root Explorer) an that will make cwmstick. this is due to newer software versions overwriting your stock recovery on reboot.
Click to expand...
Click to collapse
By installing cwm from the app store (ROM manger) will i get the same back up as i would with Odin install of cwm, in other words do i risk loosing my back up ROM using "ROM manager?"
thanks

athens71 said:
By installing cwm from the app store (ROM manger) will i get the same back up as i would with Odin install of cwm, in other words do i risk loosing my back up ROM using "ROM manager?"
thanks
Click to expand...
Click to collapse
you've created a backup already? if not, install cwm from ROM Manager, boot into cwm recovery and make your nandroid there. then you'll be all set to to try a new ROM

[Q] Rooting results in wrong recovery mode

I am in the middle of rooting my TMO GS3 with 4.1.2 and I am getting Android System Recovery instead of CWM recovery. What did I do wrong?

cybrguy1 said:
I am in the middle of rooting my TMO GS3 with 4.1.2 and I am getting Android System Recovery instead of CWM recovery. What did I do wrong?
Click to expand...
Click to collapse
What process did you try?
T-Mobile SGS III

re: sure way to root - success everytime
cybrguy1 said:
I am in the middle of rooting my TMO GS3 with 4.1.2 and I am getting Android System Recovery instead of CWM recovery. What did I do wrong?
Click to expand...
Click to collapse
There are dozens of ways to root your phone, some methods work better than others and some don't work at all.
Here is the way to root your phone with the T999 Jellybean 4.1.2 rom.
This method works all the time and every time, no more trial and errors.
Easy and sure way to have a fully rooted T999 Galaxy S3 - Here is s step by step guide:
Download the newest pre-rooted Samsung Galaxy S3 T999 Jellybean v4.1.2 rom: T999_UVDMD5
After downloading make a folder on your computer's desktop and unzip the
file using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download and extract Odin into the same folder you made containing the TAR file
Here is the link for Odin: http://d-h.st/Q14
Download ODIN which is required for flashing the stock rooted firmware (a windows app)
Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the Firmware you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache!
(It may seem to hang during boot, this is normal and you must be patient!!!)
Once it's rooted be sure to make a nandroid backup of the rom using cwm or twrp recovery.
Good Luck!

The above advice is irrelevant to the problem, way to read the OP. When you flash CWM with Odin, when you reboot your device, you need to drop to recovery before the device is allowed to boot. Do you understand? Flash CWM > boot straight into recovery. Once there you can exit. You will be prompted to disable some recovery crap. Do that.

mt3g said:
What process did you try?
T-Mobile SGS III
Click to expand...
Click to collapse
I've been following Max's galaxys3root.com video instructions. Used Odin 1.85, got the yellow COM indicator, ran the clockworkmod.tar, got the pass indicator and rebooted. Copied the CWM file to the phone. Can't seem to get into CWM recovery mode. Gives me Samsungs...

cybrguy1 said:
I've been following Max's galaxys3root.com video instructions. Used Odin 1.85, got the yellow COM indicator, ran the clockworkmod.tar, got the pass indicator and rebooted. Copied the CWM file to the phone. Can't seem to get into CWM recovery mode. Gives me Samsungs...
Click to expand...
Click to collapse
See my signature, too. Stop using files that are older than I am.

cybrguy1 said:
I've been following Max's galaxys3root.com video instructions. Used Odin 1.85, got the yellow COM indicator, ran the clockworkmod.tar, got the pass indicator and rebooted. Copied the CWM file to the phone. Can't seem to get into CWM recovery mode. Gives me Samsungs...
Click to expand...
Click to collapse
Do what aerowinder said.
T-Mobile SGS III

Aerowinder said:
See my signature, too. Stop using files that are older than I am.
Click to expand...
Click to collapse
OK, took your advice to heart and reflashed the newer (6.0.3.1) CWM, and I can now boot to it. Did an image.
Now, one of the main reasons I rooted the phone is so that I can add other programs to the MultiView feature. I most want Dolphin and my (stock) contact tool. Just dragging them to the tray doesn't get them there. I can imagine Dolphin may need to be reinstalled, but what would I need to do to get the built in contact tool to work with it?
Somehow I got the impression that rooting the phone would make everything available to MultiView...

You have to install the firmware with your recovery. Then it'll be available. Look in to the development section for the mod.
T-Mobile SGS III

mt3g said:
You have to install the firmware with your recovery. Then it'll be available. Look in to the development section for the mod.
T-Mobile SGS III
Click to expand...
Click to collapse
Sorry to be thick, but I don't know what you mean. I'm not sure what firmware you mean for me to install.

Rooting your device grants you permission to be able to do things. Not grant you things. You still need to flash a superuser root access .zip, a recovery doesn't grant root. I'm not on a PC so I'm not sure if what Aero pointed you towards also has the .zip you need included. Look in your app drawer and look for a superuser app. If its there then download this http://forum.xda-developers.com/showthread.php?t=2278022, And search how to flash a .zip in recovery. Make sure you read up a little more, and then ask questions before messing your phone up.
T-Mobile SGS III

Thanks, I do understand that rooting doesn't do anything but enable. I thought, though, that superuser was all I needed to enable most apps for multiview. I did flash SU when I rooted but mistakenly thought that would be enough for this feature.

There is an app that will grant the feature also, I don't use it but its out there. "multi window manager" that requires root so install it open it and follow instructions.

mt3g said:
There is an app that will grant the feature also, I don't use it but its out there. "multi window manager" that requires root so install it open it and follow instructions.
Click to expand...
Click to collapse
Thank You! That was exactly what I was looking for, and it works just fine.
https://play.google.com/store/apps/details?id=com.bjbinc.multiwindowmanager&hl=en

No worries. Forgot about the app for a few minutes glad I remembered lol.
T-Mobile SGS III

Rooting and flashing ROMS with T-Mobile Note 3 with KitKat

Ok. I have seen several people asking about rooting their T-Mobile Note 3. I am sure there have been posts on how to accomplish this feat. I am going to put out the steps that I took and mention a few other options and my thoughts on those. I hope to make this an all inclusive post for newbies. This method works whether you are on 4.3 or 4.4 BUT you will need to make sure the recovery and ROM you download is for the correct version of android you are using. To make this easier I am going to assume you are already on 4.4 Not everything will be clear but should be able to be easily understood. If there is something you don't understand ask and I am sure people will try to help. That or you can do a google search and probably find the answer a whole lot faster. If you did have a problem and found the solution please post it so others can use your information. I don't have the time at the moment to provide all the links but I will try to update this thread as much as I can.
I am NOT responsible for bricked devices, voided warranties or downloaded virus to your computer.
That being said rooting should be a relatively simple and easy process.
1. Download Odin 3.07 or 3.09 .zip file and install on your computer. (I have found no real difference in between the two when attempting root.) (No link provided just google it.)
2. Download the custom recovery of you choice. (I use and prefer twrp, but some people have had problems flashing ROMs and have had better luck with philz recovery) Below is the link for TWRP. If using 4.4 make sure to download the img.tar file for 2.7. There are other files but you want the one ending in img.tar! http://teamw.in/project/twrp2
3. Open Odin and connect your phone. You need to put your phone into download mode before connecting. Shut your phone off and then turn back on while holding volume down, power and home key. You will see a special screen pop up and a warning. Acknowledge the warning and the connect to the computer. If you don't get a blue bar on the left side of Odin after connecting your phone then you need to update your driver's (google search).
4. Place the .tar file that you downloaded into the PDA(3.07) or AP(3.09) section. Make sure the ONLY boxes on the left are Auto Reboot and F. Reset Time are checked (that should be the default settings)!!
5. Hit the start button. Be advised that Flashing a custom recovery WILL trip Knox.
6. You should the blue bar turn green and say "pass." You know have a custom recovery on your phone and you can disconnect your phone.
At this point you do not have root access, you just have a custom recovery. You now have a choice to make. Do you want your phone rooted or do you want to flash a custom ROM. If you want to flash a custom ROM jump to #8. If you just want root and plan on staying on stock go to #7.
7. Download the latest version of SuperSU file from http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip and flash from your custom recovery. when you restart your phone make sure you can open the SuperSU app. If you cannot go to the play store and reinstall it from there. Congrats!!
8. If you want a custom ROM you need to download the .zip file of that ROM. I would recommend placing it on your EXTERNAL sd card.
9. Go to your custom recovery. There are some things you are going to need to back up prior to Flashing the ROM.
a. Backup your stock ROM, This could save you from some major problems. Back up-system, data and boot-to your EXTERNAL sd card.
b. Backup you EFS files (this can be done via twrp, other wise you will need to do it another way-Google search)
10. Wipe the phone. You want to wipe Data, Cache and Dalvik
11. Flash you custom ROM. Almost every custom ROM comes rooted. You just need to read the info on that ROM
12. Your phone should reboot and you are done!!
Below is some Q&A and helpful tips.
If I upgrade to 4.4 from 4.3 to get a diffent ROM can I switch back? NO
What is "Bricked"? It is a phone that will not boot and only stays on a black screen. Soft Brick is where your phone constantly reboots without opening your ROM.
What is Knox? Google it
Will tripping Knox void my warranty? Probably
How do I get into the recovery? Shut your phone off and then restart while holding the volume up, power and home key. You have to let go as soon as you see the blue letters "Recovery Booting"
There are not that many ROMS for T-mobile can I use an international ROM? Yes! I currently run an international ROM but on most of them you do loose your wifi calling feature. You also need to download a custom T-Mobile Kernel and the Wifi/BT fix.
Should I use CF Auto root or Klingo? I personally don't like the idea of Klingo. Some of the things I have seen they appear to be a little fishy and with them rooting your phone they initially have access to EVERYTHING. CF auto root does not place a custom recovery. You CANNOT flash a custom ROM without a custom recovery. I did it my way because I wanted a custom ROM and just not root.
What about the De La Vega Method? I have no idea and it seemed more work that it was worth. I did not care about tripping Knox
Tips:
Some ROMS will delete your internal memory when flashing as will wiping your phone. That is why I strongly suggest placing the backups and ROMS on your external sd card.
Some ROMS come with an Auroma set up. You will automatically be directed into it when you flash from recovery.
If you are flashing an international ROM make sure that you flash the ROM, T-mobile Kernel and Wifi Fix before choosing the reboot option. If you don't have the t-mobile kernel prior to reboot you will go into a bootloop.
I hope this helps and I will add more and clarify this post in the next few days. I just hope this can help some of you new guys out a little bit and if you found it useful especially if you obtained root please hit the thanks meter.

OK, I deleted all the information here about all the errors I made so that this won't confuse anyone. To summarize my error, I thought I had purchased Android 4.4.2 and flashed the wrong versions. After flashing the correct version, 4.3, everything worked.
The SD-card is not visible in stock recovery and the ADB method won't work without first having root, so that leaves the Odin method.
The Odin method flashes TWRP recovery successfully and when I exited it asked me if I wanted to root the device. I chose 'yes' and it worked for a while then booted into the Android OS. In Android it booted normally, then after I did something which I did not think about and don't recall, a dialog advised me that the GUI portion of the root process still needed to be applied. I allowed it to proceed and now I am rooted with TWRP. I verified the root through ADB by creating a file in the root directory.
Frank

I will try to break this down for you.
1. You need to reflash twrp via Odin to make sure it works correctly since doing auto root.
2. That screen you saw is exactly what you wanted to see. As stated in the OP when you see that screen let go of the buttons and wait, twrp will open shortly. I get the same screen so don't worry. Once you get into twrp and if you need a tutorial on twrp I would suggest looking it up on YouTube.
3. If you reflash the stock ROM via Odin it should fix everything. I am not sure about the partition problem. I will get back if I get some more info.
I would not worry about trying to reflash stock. I would just reflash twrp, boot into recovery and then proceed as listed in the OP.

Frank Westlake said:
**************************************************************************
I found my problem. I think the box, or something, was mislabeled because "About" tells me I have Android 4.3, not 4.4.2. So I flashed the 4.3 version of TWRP and booted right into it. After another reboot to make sure it's stable I'll try rooting again.
Frank
Click to expand...
Click to collapse
Great. Yes, it did not work because 2.7 is written for the new bootloader in 4.4. Are you planning on staying stock jb or planning on flashing a ROM?
sm-n900t: Powered by X-Note V13

FFTony said:
Are you planning on staying stock jb or planning on flashing a ROM?
Click to expand...
Click to collapse
Stock. With root I'm able to customize everything right on the device about as much as the ROM builders. But there are things I cannot do on the device so I'll be keeping an eye on the ROMs to see if anything is attractive.
After I finished this update I refreshed this page and saw that you had been commenting. The screen you saw should be there was also there when I flashed the correct TWRP, and it did move on to TWRP as you said. I'm adding the following paragraph separately so that it's easier for people to find if they need it:
After I had flashed the wrong version of TWRP (4.4 instead of 4.3) it boot-looped to the "SEANDROID NOT ENFORCING" display. To get out of that boot-loop I held the Download Mode keys (HOME-POWER-VOLDOWN) until it rebooted into the first download mode screen, the warning which says you can press VOL-DOWN to boot normally. At that point press VOL-DOWN and it will boot normally. If you press VOL-UP and continue into Download Mode then you will still be in the boot-loop when you reset the device and you will need to reboot again into the Download Mode warning screen and press VOL-DOWN to boot normally.
Thank you very much for your help with this.
Frank

FFTony said:
What about the De La Vega Method? I have no idea and it seemed more work that it was worth.
Click to expand...
Click to collapse
Samsung explains about Root De La Vega here: Samsungknox.com/en/blog/about-root-de-la-vega

[Q] T-Mobile Note 2 (SGH-T889 on CM11) Unable to Boot into Recovery, Forgot GAPPS

Phone: T-mobile Samsung Galaxy Note 2 SGH-T889
1. Rooted phone using Zedomax instructions with CWM Recovery 6.
2. Afterwards, unable to boot into recovery.
3. Installed ROM Manager from Playstore, and used it to successfully boot into Recovery.
4. Flashed Nightly CM11 Rom from XDADevelopers site, but forgot to flash GAPPS.
5. Afterwards, booted into CM11 but phone model is listed as N7105 (or something like that). It is not listed as SGH-T889 anymore.
6. Unable to boot into Recovery using Vol Up + Power + Home. The Samsung logo flashed and scrolls vertically twice.
7. Tried installing the GAPPS APK files one at a time, but some files would not install and as a result I was unable to get any GAPPS working.
8. I would like to flash back to stock and have an image, but scared if I do, then I might get stuck if I am unable to boot into Recovery again.
What should I do to get GAPPS applications back on the phone?
What is the correct firmware file named?
Thanks for any help you provide.

cardinal35 said:
Phone: T-mobile Samsung Galaxy Note 2 SGH-T889
1. Rooted phone using Zedomax instructions with CWM Recovery 6.
2. Afterwards, unable to boot into recovery.
3. Installed ROM Manager from Playstore, and used it to successfully boot into Recovery.
4. Flashed Nightly CM11 Rom from XDADevelopers site, but forgot to flash GAPPS.
5. Afterwards, booted into CM11 but phone model is listed as N7105 (or something like that). It is not listed as SGH-T889 anymore.
6. Unable to boot into Recovery using Vol Up + Power + Home. The Samsung logo flashed and scrolls vertically twice.
7. Tried installing the GAPPS APK files one at a time, but some files would not install and as a result I was unable to get any GAPPS working.
8. I would like to flash back to stock and have an image, but scared if I do, then I might get stuck if I am unable to boot into Recovery again.
What should I do to get GAPPS applications back on the phone?
What is the correct firmware file named?
Thanks for any help you provide.
Click to expand...
Click to collapse
Can you post a link to what you used. That method doesn't sound familiar and might possibly be part of the problem.
The N7105 model is not unexpected. It is the model for the intl Note 2.
It can mess with stuff if you use auto installing software such as Goo Manager and *maybe* Rom Manager. It might try to install the wrong recovery based on your inaccurate build prop device ID.
Which version of bootloader are you running? If you had official 4.3 you have fewer options for going back to stock. If when you boot into download (home+vol down+power) you see the word "knox" anywhere you have the 4.3 bootloader.
Look in the Development stickies and check for root66 by MrRobinson. Install Odin on a PC, make certain your phone communicates with the computer, the factory reset it. Install the appropriate version of root66 (UVBMC1 if you are non Knox, UVUCMK7 if you are on the Knox bootloader) following the instructions in the thread.
This should get you back to stock.
Once you can breathe again (getting stuck like that sucks) only flash roms from around here until you become comfortable with the nuances of going elsewhere.
Hastily spouted for your befuddlement

Procedures used to root and clarification
Coug76 said:
Can you post a link to what you used. That method doesn't sound familiar and might possibly be part of the problem.
The N7105 model is not unexpected. It is the model for the intl Note 2.
It can mess with stuff if you use auto installing software such as Goo Manager and *maybe* Rom Manager. It might try to install the wrong recovery based on your inaccurate build prop device ID.
Which version of bootloader are you running? If you had official 4.3 you have fewer options for going back to stock. If when you boot into download (home+vol down+power) you see the word "knox" anywhere you have the 4.3 bootloader.
Look in the Development stickies and check for root66 by MrRobinson. Install Odin on a PC, make certain your phone communicates with the computer, the factory reset it. Install the appropriate version of root66 (UVBMC1 if you are non Knox, UVUCMK7 if you are on the Knox bootloader) following the instructions in the thread.
This should get you back to stock.
Once you can breathe again (getting stuck like that sucks) only flash roms from around here until you become comfortable with the nuances of going elsewhere.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
The link to the root method I used:
galaxynote2root dot com galaxy-note-2-root how-to-root-galaxy-note-2-easiest-method
I only used ROM manager when I was unable to boot into Recovery after using the above procedure. ROM manager was used only to boot into recovery when I was unable to boot into it using the Vol Up + Power + Home keys method. It has an option to boot into recovery.
If I use the root66 method, is there a chance that I may get a boot loop upon boot after flashing? I read that moving from CM roms to stock might require booting into recovery after flashing the stock firmware file. That being the case, then I was afraid after flashing the right file, I still would not be able to boot into recovery.
Is there a way to simply get the GAPPS installed without recovery? I tried adb and unzipping to use File Manager to install each individual apk...no luck. The CM 11 ROM seems to work just no google apps.
But it would be nice to get back to stock fully too. Am looking into the bootloader version and root66 instructions. Thank you for the direction to follow.

Root66 will get you to a rooted stock beginning place. It will start you out with a bone stock device including bootloader and recovery (if done properly).
At this point if you reset the flash counter via triangle away, unroot the device, and factory reset it looks warranty eligible (unless you have the Knox bootloader tripped).
The reason you would do this: somewhere along the line something got screwed up and starting fresh is in order. Back up your data and start over.
Once you have a stock device, use the resources available here to guide you step by step. Tool kits are all well and good. If you take the steps yourself carefully after learning what they do and why, the mystery of a tool kit is gone. You can be confident into what you put into your device.
I would download the most recent version of TWRP recovery from their website (2.7.0.1) and flash it in Odin while I was at it. Recovery Odin flashes just like the root66 files.
Hastily spouted for your befuddlement

cardinal35 said:
The link to the root method I used:
galaxynote2root dot com galaxy-note-2-root how-to-root-galaxy-note-2-easiest-method
I only used ROM manager when I was unable to boot into Recovery after using the above procedure. ROM manager was used only to boot into recovery when I was unable to boot into it using the Vol Up + Power + Home keys method. It has an option to boot into recovery.
If I use the root66 method, is there a chance that I may get a boot loop upon boot after flashing? I read that moving from CM roms to stock might require booting into recovery after flashing the stock firmware file. That being the case, then I was afraid after flashing the right file, I still would not be able to boot into recovery.
Is there a way to simply get the GAPPS installed without recovery? I tried adb and unzipping to use File Manager to install each individual apk...no luck. The CM 11 ROM seems to work just no google apps.
But it would be nice to get back to stock fully too. Am looking into the bootloader version and root66 instructions. Thank you for the direction to follow.
Click to expand...
Click to collapse
there are more files than just apks in a gapps package.

How do I know which version of boot loader is running? I am currently on CM 11 Nightly.
Then which root66 T-Mobile ROM should I flash using Odin? I did not understand the Mobilicity, Videotron, etc., ROMs.
Sent from my SPH-D710 using xda app-developers app

cardinal35 said:
How do I know which version of boot loader is running? I am currently on CM 11 Nightly.
Then which root66 T-Mobile ROM should I flash using Odin? I did not understand the Mobilicity, Videotron, etc., ROMs.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
to find out your bootloader version you need to boot into download mode. if you see the word knox on that screen you are on 4.3 bootloader. if you are on tmobile then you have no use for the other carriers roms (mobilicity etc)

Boot Loop after root66 UVBMD1
Coug76 said:
Can you post a link to what you used. That method doesn't sound familiar and might possibly be part of the problem.
The N7105 model is not unexpected. It is the model for the intl Note 2.
It can mess with stuff if you use auto installing software such as Goo Manager and *maybe* Rom Manager. It might try to install the wrong recovery based on your inaccurate build prop device ID.
Which version of bootloader are you running? If you had official 4.3 you have fewer options for going back to stock. If when you boot into download (home+vol down+power) you see the word "knox" anywhere you have the 4.3 bootloader.
Look in the Development stickies and check for root66 by MrRobinson. Install Odin on a PC, make certain your phone communicates with the computer, the factory reset it. Install the appropriate version of root66 (UVBMC1 if you are non Knox, UVUCMK7 if you are on the Knox bootloader) following the instructions in the thread.
This should get you back to stock.
Once you can breathe again (getting stuck like that sucks) only flash roms from around here until you become comfortable with the nuances of going elsewhere.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
1. Checked bootloader by going into Download Mode (Vol Down, Power, Home) and did not see Know anywhere.
2. I downloaded root66_TMO_T889UVBMD1.7z.
3. Installed using Odin after checking MD5 checksum.
Now the phone goes into a loop. It displays the Samsung logo, then goes to the T-Mobile Splash screen, then returns to Samsung logo...
Any ideas how I should proceed?

Solved!
cardinal35 said:
1. Checked bootloader by going into Download Mode (Vol Down, Power, Home) and did not see Know anywhere.
2. I downloaded root66_TMO_T889UVBMD1.7z.
3. Installed using Odin after checking MD5 checksum.
Now the phone goes into a loop. It displays the Samsung logo, then goes to the T-Mobile Splash screen, then returns to Samsung logo...
Any ideas how I should proceed?
Click to expand...
Click to collapse
Disregard last reply. I solved by:
1. Booting into Stock Recovery (Vol Up + Power + Home) and Factory Data Wipe/Reset.
2. Everything works on boot!
Thanks for all the help guys. What a relief...I will update if any problems are seen later.