Database Users

Please Help. Can't get past white Samsung Vibrant Screen.

I followed the instructions from here ( http://forum.xda-developers.com/showthread.php?t=743769 ) up until flashing the actual zip and forgot I put the zip on my external sdcard rather than "internal" sdcard. Now my phone won't get past the initial white Samsung Vibrant screen. Also, I can only get into stock recovery. After clicking "reinstall packages" it just reboots and brings me back to stock recovery. Please help. Thank you.

You will need to flash back to stock then you will have access to your phone again.. you will have to start over to flash that rom. after you flash back to stock using odin
use this thread
http://forum.xda-developers.com/showthread.php?t=734475
You will need the right windows drivers so Odin will see your phone pick them up here.
Windows 64bit
Windows 32bit
Directions posted by setzer715
1. Put your phone in download mode by plugging it in and then holding Vol Up+Down and Power. As SOON as the screen goes black release power but NOT Vol Up+Down.
2. Launch Odin
3. Unplug your phone.
4. Load the pit and pda files into odin.
5. Plug your phone back in. You should now see one of the small blocks turn yellow and show you the com port. If not, something is wrong with your drivers.
6. Click start. If it flashes, great. If it hangs at File analasys then repeat 1-5.
6a. If Odin hangs at cache.rfs then move on to 6b.
6b. Unplug your phone (Odin will say it was removed) and remove the battery. DO NOT SHUT DOWN ODIN!!!!!!
6c. Put the battery back in and plug it back into your computer and put it back into download mode using step 1.
6d. Press start on Odin and it should now flash.
Also if you continue to hang at cache.rfs I found that if you delete s1_odin_20100512.pit then copy a new copy of the file over to your odin directory it seems to work fine after that.

Damn it.Thanks....

vol dn+up should get you to the stock recovery util right? the yellow and blue one?
edit: nvm, scare is over lol

On step 6d, where it says to press start again on odin, odin does not let me do this. The start, reset, pit, pda, etc... buttons are grey and will not let me press them. Help!
EDIT: also gives me a message in the upper left corner that says "CACHE" if that helps (in the far upper left box above where the yellow COM3 thing was.

bumpbumpbump

$iMoney said:
On step 6d, where it says to press start again on odin, odin does not let me do this. The start, reset, pit, pda, etc... buttons are grey and will not let me press them. Help!
EDIT: also gives me a message in the upper left corner that says "CACHE" if that helps (in the far upper left box above where the yellow COM3 thing was.
Click to expand...
Click to collapse
You need to delete your s1_odin_20100512.pit file and then extract a new copy to the odin folder then flash again. happened to me and that is all I did to fix it. step 6d did not work for me has well.

Hmmmm it's still not working. Would it help if i made a video showing what i'm doing then you can look it over and tell me if I'm doing something incorrectly? Also maybe I should be more clear. There is no way for me to start the flash again after removing my device as per step 6 without having to completely restart odin, thus restarting the process.

Update: Still not working. Really need a fix for this. Is there another way to un-brick my phone?

EDIT: To clarify, my problem was getting stuck as Cache.rfs and never going past that. I did try the previous steps listed in this article, as well as trying to reinstall all drivers and even using different Odin copies from other threads (even though they were all the same Odin 3). No .pit file seemed to work for me. Also, I'd like to point out that I have this issue with my netbook, but my work computer where I've done all my Odin flashing before did not have this issue, and I could use the .pit files perfectly fine.
First off, I'm not anyone special (I guess depends on the meaning of special), I don't dev... I play around. That's all. So take this all with a grain of salt.
I had the same issue, and have spent all night trying to fix it. Just now I didn't use the .pit file at all. Just the .tar in the PDA slot. Immediately went through and reflashed everything and I am fully up and running.
I can't guarantee that I don't have some kind of issues now but I am now back at my home screen and the phone seems to be operating fine.
The files I used are as follows:
Stock 2.1 firmware for the Vibrant: http://forum.xda-developers.com/showthread.php?t=739091
Samsung studio 7 (seemed to get Odin to recognize the phone without having to disconnect and reconnect, thought it might have something to do with the issue, though not sure): http://www.4shared.com/file/117435710/3d286573/Samsung_PC_Studio_72249.html
And the Samsung USB Drivers: http://forum.xda-developers.com/showthread.php?t=728929
Now, if a real dev can tell us what happens when you don't use the .pit file, we can know if there is any longterm repercussion from this. Short term though, working like a dream. I hope this helps, because being stuck without a working Vibrant sucks!

ODIN is a pain but I've found a way to get it work pretty consistently for me. Whenever you flash a ROM or back to stock, always make sure you enable USB debugging, and have adb working on your computer.
Open up your command console, plug in your device, open up ODIN, and type "adb reboot download". ODIN should recognize your phone when it restarts and a COM will light up.
From my experience, ODIN recognizes the devices better this way and hasn't hung for me so far (granted it's only 3 times). When I was booting into download manually and then plugging in the USB, it would hang at cache.rfs. If you don't have USB debugging enabled, then only thing you can do is keep retrying over and over. Took me like 15 tries once before it finally ran.

Can't thank you guys enough. Phone is back to normal! As soon as I didn't use the pit file it worked like a charm.

hey...i'm in the same situation as you...i can't get it to work...i'm trying to do just the tar file right now but it still hangs on cache.rfs how long did you have to wait?

$iMoney said:
Can't thank you guys enough. Phone is back to normal! As soon as I didn't use the pit file it worked like a charm.
Click to expand...
Click to collapse
which firmware did you use? did you use the true stck 2.1 firmware?

tq745 said:
hey...i'm in the same situation as you...i can't get it to work...i'm trying to do just the tar file right now but it still hangs on cache.rfs how long did you have to wait?
Click to expand...
Click to collapse
It should go right away. If it's hanging at cache.rfs, then it's not working. I really think its a drivers issue with ODIN. Just keep restarting your phone and ODIN and retrying.

I used the tar file that is linked to from the second post on this thread. I didn't even download what you linked me to, I just didn't use the pit file, like you told me and it worked with the files I already had.

My phone will absolutely not go into download mode. Is this a sign of some other problem or am i just out of luck?

ahhduy said:
My phone will absolutely not go into download mode. Is this a sign of some other problem or am i just out of luck?
Click to expand...
Click to collapse
how are you trying to get into download mode?

skater4690 said:
how are you trying to get into download mode?
Click to expand...
Click to collapse
Holding down + power when turning on, tried other varients like volume up instead of down, usb connected or usb not connected etc.

ahhduy said:
Holding down + power when turning on, tried other varients like volume up instead of down, usb connected or usb not connected etc.
Click to expand...
Click to collapse
ok try this...
1)plug into a usb with power
2)wait for the battery to show up
3)hold power and both volume buttons
4)wait for the vibrant screen to flash twice it will go once then seem like it turns off but then pops up agian
5)after it turns off the second time release the power button but still hold the volume buttons and you should be in download mode now
REMEMBER TO HAVE THE USB PLUGGED INTO THE COMPUTER AND YOUR PHONE!!!

did lag fix now stuck on black screen!

ok..im new to the galaxy and android phones .. i bought the phone rooted..not sure all what it had but i was running i believe a different rom on the phone, 2.1 update 1 i believe, it had rom manager and clockwork recovery on it, anyway .. i tried doing the lag fix and now the phone just turns on and stays on black screen.. keys at the bottom stay lit up also.. i can get into recovery but not really seeing anything in there that is helping.. can i factory reset or something from this recovery screen? like i said im not real familiar with these phones but im good with directions so if someone can explain how to fix this that would be great! thanks!

Hi, did you try using odin to flash back to stock?
the files you need to flash are in this thread
forum.xda-developers.com/showthread.php?t=734475
Also make sure you have samsung drivers installed on your computer. Which can be located here forum.xda-developers.com/showthread.php?t=728929
A stable version of odin is in this thread
forum.xda-developers.com/showthread.php?t=790026
steps
1. you will need to download odin..open it
2.Make sure your phone is off. connect your phone via usb and get into download mode(hold the volume keys+power when screen turns black let go of power button) now you should see a yellow triangle with android icon
3.to make sure your comp recognizes the phone.. pull out usb and put it back into the phone.
4. look at the first link i posted and flash the files accordingly and you should be good to go.

ok..i will try it. unfortunately i use my phone to tether so now im back on my blackberry which is SLOW.. odin is saying like 4hrs to download..loL!

I had the same issue. It sounds like you didn't install a BusyBox version that has extfs support built in. I could swear that the lag fix option I pulled down was supposed to have it, but it didn't. If you made a nandroid backup before you tried this, you should be able to get into recovery and restore. If not, you'll have to get to download mode and Odin flash back to stock.
If your phone is hardware locked, with the state your phone is in, you SHOULD be able to do an "adb reboot download" or "adb reboot recovery" to get into those modes.

Touch Wiz update messed tab up please help!

ok so here is what happened i have a stock US retail wifi only 16gb tab no clockwork recovery or none of that , im kind of a noob when it comes to that stuff, so today i received the update cool i downloaded it but it didn't install the first time for some reason. The it said a previous update was sucessfully downloaded but did not install do i wish to instal so i clicked yest and it said tab is about to reboot, clicked ok and it took me to this black and grey screen like the boot screen only with a loadbar and it zoomed to 100 percent. then i got the original samsung galaxy boot logo and the noise but no animation then the screen goes to this nasty screen with alot of colorful lines and dots everywhere and i cant see anything looks terrible.
Heres what i can do i can go into the bootloader by pressing power and volume. and i already tried to do a restore/wipe but didnt help, i can also plug it in to the computer and use the sd card and put and remove files from tab. im wondering if i can somehow get the update put it in the tab and install from there and see if it works or if i can get stock honeycomb and try to see if that works because they guy at samsung was clueless he didnt get the fact that i cant use the OS and said i need to get it serviced when i know its a software problem.

exact same thing happened to me! keep me posted

I've just got absolutely the same problem. I have a stock wifi 32gb version.

If you can get to your bootloader and sdcard still then why don't you just install CWM and try flashing the stock 3.1 OTA?
All the files you need and instructions are here: http://forum.xda-developers.com/showthread.php?t=1171089
Once you're done flash the stock recovery back and try the update again, or just wait for one of the devs to release a flashable zip.

sorry if im mistaken but dont i need to be able to use the tab and install something from the market place to be able to install CWM thats what im getting from what i read?

I can't even get my bootloader. Holy f**k am I pissed. Does anyone have any ideas??

Ok. So I installed the Samsung Kies software. It recognizes the device and shows that the update is available. However, it says that the battery should be fully charged. So now I am waiting for the full charge to proceed.
Hope the Kies helps.

I'll try that too. ahh

tonyurquiza said:
sorry if im mistaken but dont i need to be able to use the tab and install something from the market place to be able to install CWM thats what im getting from what i read?
Click to expand...
Click to collapse
No.
Go to the thread I linked, download the files, watch the youtube video.
1. Install the GT-p7510_USB_Driver if you haven't already
2. Start Odin - untick the auto reboot option
3. Click PDA and choose recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5
4. Power up your tab and get it into download mode (power down + vol down, then vol up)
5. connect the tab to your PC, one of the boxes in odin should highlight yellow and say com 4 or whatever.
6. press start and it'll flash CWM to your tab
7. wait till it's done, it should only take a few seconds and the boxes will turn green.
8. power down your tab and unplug it from your pc
9. boot into CWM, (power down + vol down, vol down to select CWM, vol up to enter.
10. flash hc-3.1_ota-full_sam_tab_10.1.zip
11. do a factory wipe in CWM and wipe davlik just to be safe
12. reboot, and hopefully you'll be back to stock 3.1
From here you can do whatever you want.

Connect it to a PC and there's a firmware recovery on KIES. Hope that works!
Sent from my GT-P7510 using XDA Premium App

lordwinkevin said:
there's a firmware recovery on KIES
Click to expand...
Click to collapse
it didn't work for me. There were no devices in the list to recover.

I'm going to try it once my kies is finished updating. I really hope this works.

haha well first and formost i want to thank everyone for thier input. I did alot of searching online i tried KIES samsung tech support was useless. So i found the instructions on how to put clockwork on a locked bootloader got it on there and flashes the stock rom and it worked my tab is now back! only problem now is i tried to update again and only go the minor update and it doesnt find the big one lol but cant complain ill just wait lol thanks again. and to others who had the same problem dont deal with KIES to recover its useless unless you were using the program to update. I suggest getting CWM and flashing stock since thats what worked for me?

tonyurquiza said:
haha well first and formost i want to thank everyone for thier input. I did alot of searching online i tried KIES samsung tech support was useless. So i found the instructions on how to put clockwork on a locked bootloader got it on there and flashes the stock rom and it worked my tab is now back! only problem now is i tried to update again and only go the minor update and it doesnt find the big one lol but cant complain ill just wait lol thanks again. and to others who had the same problem dont deal with KIES to recover its useless unless you were using the program to update. I suggest getting CWM and flashing stock since thats what worked for me?
Click to expand...
Click to collapse
Glad to hear it worked.
Since you now have CWM, just download the flashable zip from here: http://forum.xda-developers.com/showthread.php?t=1198921
Make sure you do a factory reset in CWM after you flash this, otherwise you'll bootloop.

hoodoomagic said:
No.
Go to the thread I linked, download the files, watch the youtube video.
1. Install the GT-p7510_USB_Driver if you haven't already
2. Start Odin - untick the auto reboot option
3. Click PDA and choose recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5
4. Power up your tab and get it into download mode (power down + vol down, then vol up)
5. connect the tab to your PC, one of the boxes in odin should highlight yellow and say com 4 or whatever.
6. press start and it'll flash CWM to your tab
7. wait till it's done, it should only take a few seconds and the boxes will turn green.
8. power down your tab and unplug it from your pc
9. boot into CWM, (power down + vol down, vol down to select CWM, vol up to enter.
10. flash hc-3.1_ota-full_sam_tab_10.1.zip
11. do a factory wipe in CWM and wipe davlik just to be safe
12. reboot, and hopefully you'll be back to stock 3.1
From here you can do whatever you want.
Click to expand...
Click to collapse
How would i get hc-3.1_ota-full_sam_tab_10.1.zip on my tab to flash via CWM if I can't get the tab to boot?

tonyurquiza said:
ok so here is what happened i have a stock US retail wifi only 16gb tab no clockwork recovery or none of that , im kind of a noob when it comes to that stuff, so today i received the update cool i downloaded it but it didn't install the first time for some reason. The it said a previous update was sucessfully downloaded but did not install do i wish to instal so i clicked yest and it said tab is about to reboot, clicked ok and it took me to this black and grey screen like the boot screen only with a loadbar and it zoomed to 100 percent. then i got the original samsung galaxy boot logo and the noise but no animation then the screen goes to this nasty screen with alot of colorful lines and dots everywhere and i cant see anything looks terrible.
Heres what i can do i can go into the bootloader by pressing power and volume. and i already tried to do a restore/wipe but didnt help, i can also plug it in to the computer and use the sd card and put and remove files from tab. im wondering if i can somehow get the update put it in the tab and install from there and see if it works or if i can get stock honeycomb and try to see if that works because they guy at samsung was clueless he didnt get the fact that i cant use the OS and said i need to get it serviced when i know its a software problem.
Click to expand...
Click to collapse
Mine did exactly this too, by the way....

I would go this way:
http://forum.xda-developers.com/showthread.php?t=1167250
/Doc

* deleted *

Thank you DocRambone, flashing that via Odin got me up and running.
Then I flashed CWM as per earlier post and then flashed the Stock UEKMB + root ROM and I guess I am good to go.

Ok guys. This is my report. I used the Kies to update. The firmware was updated successfully and now the tablet works perfectly!
So this is easier and less painful method than using CWM described above =)) (but thanks to hoodoomagic for the description anyway)
Hope this will help somebody.

Updating to 4.3 error, no command, is my phone dead? :(

I literally just got the 4.3 OTA update. Phone was fully charged... like 98%. I went ahead and let it update. It rebooted, and it got about 75% into updating and then the icon switched to the sideways android with the red caution symbol and said "Error". I let it sit there for awhile hoping it would do something. It didn't, so I held down power to reboot. It rebooted to the same icon, but now says "No command". I did the vol up/power to get into the wipe/reboot options. I went ahead and rebooted. Every single time... I see the Google logo for like a min, then to the sad android logo w/ "No command". Now I can't even get that far, the indicator light flashes red. I've read that indicates a totally drained battery. Not sure how it can go from full charged to fully drained in a matter of minutes. However on the issue of the error and no command, is my device dead? I've never rooted it or used custom roms. I got the N4 for the pure vanilla stock experience, so I never felt rooting was needed. Any advice? Should I just call Google and request replacement?

I would try a few things first before calling Google. Sometimes the battery doesn't show its correct percentage, it's pretty common on my N4 as far as I can tell. Maybe you've just run out of battery. Let it charge for half an hour or so and then try it again.
If you can't boot to system after that, turn off your phone, press and hold volume down and power buttons at the same time for a few seconds until it boots to bootloader. If you can't boot to bootloader after doing this let it charge for more time, an hour or two.
Sometimes, after the battery has run dry completely it is really hard to turn the phone on (I've even seen this behavior on my 7 years old Nokia). One question, does a charging animation shows up when you plug your phone?

Mercado_Negro said:
I would try a few things first before calling Google. Sometimes the battery doesn't show its correct percentage, it's pretty common on my N4 as far as I can tell. Maybe you've just run out of battery. Let it charge for half an hour or so and then try it again.
If you can't boot to system after that, turn off your phone, press and hold volume down and power buttons at the same time for a few seconds until it boots to bootloader. If you can't boot to bootloader after doing this let it charge for more time, an hour or two.
Sometimes, after the battery has run dry completely it is really hard to turn the phone on (I've even seen this behavior on my 7 years old Nokia). One question, does a charging animation shows up when you plug your phone?
Click to expand...
Click to collapse
It's been charging now for a little over an hour. No animation or indication the battery may be drained other than the red indicator light when I try to go to into the boot loader. Still can't do anything. If I power it on, I see Google logo for awhile, then sad Android icon and "no command". If I try to go into bootloader, just red indicator light and black screen. All while plugged in.
I just don't understand how it went from fully charged to drained in minutes. It was plugged in for hours today. In fact I initiated the OTA update only about 20-30 min after taking it off the charger.

Unplug your device, press and hold the power and volume down buttons for a few seconds until it boots to the bootloader. Now plug your phone again and let it charge.

Mercado_Negro said:
Unplug your device, press and hold the power and volume down buttons for a few seconds until it boots to the bootloader. Now plug your phone again and let it charge.
Click to expand...
Click to collapse
Alright, it's now been charging for 3 hours. I did what you just suggested. All that happens is I see a white Google logo for about 10 seconds, then it goes black. I think the device is off at this point. Stupid question I'm sure... I can't dock my phone to my computer to get any of my data at the "no command" screen can I? It needs to be fully booted, right?

Get into recovery, wipe cache, then it "should" boot.

ksilver89 said:
Get into recovery, wipe cache, then it "should" boot.
Click to expand...
Click to collapse
Like I said above, I'm not able to. I hold down power + vol up and it just shows white Google logo then goes black.

Well hmmm. I just did power + vol down for the hell of it, and I have a menu. Selected "recovery mod" and it just went straight to the sad Android icon with "No command".
I'm not sure what to make of all the stuff I see on this menu...
https://dl.dropboxusercontent.com/u/28754710/20130730_100302.jpg

Here is a short video of what I get from that menu when trying to go into recovery...
https://dl.dropboxusercontent.com/u/28754710/20130730_100936.mp4

For the sake of simplicity, learn how to use Fastboot. You should find more than enough information in the General section.
All you need to do is run this command in bootloader mode.
Code:
fastboot format cache
Edit:
Just saw the video, press vol up + power together in the recovery to access the menu.

ksilver89 said:
For the sake of simplicity, learn how to use Fastboot. You should find more than enough information in the General section.
All you need to do is run this command in bootloader mode.
Code:
fastboot format cache
Edit:
Just saw the video, press vol up + power together in the recovery to access the menu.
Click to expand...
Click to collapse
Again... like I said before vol up + power does nothing. I can take a video if you like.
Disregard the above. Got it into recovery. I guess my pushing was off or something. I took the rigid case off and made it easier to press the vol button. Let's see what happens now.

Alright. Got into recovery, did a wipe data/factory reset, still no dice. This time it rebooted several times, Google white logo each time, then finally a sad Android icon with "No command". Guessing next step is to download it and try updating via ADB?... or just say screw it and call Google and initiate a replacement?

Alright, it is screwed. Long guide here: http://forum.xda-developers.com/showthread.php?t=2010312
Short guide:
1. You need basically 3 things, the factory image, fastboot, and nexus 4 drivers
2. Download and setup all of them.
3. Extract the factory image tgz file TWICE until you see a folder.
4. Place "fastboot" into that folder.
5. Unlock your bootloader, shift + right click inside the folder, Open command window here. Run "fastboot oem unlock" and read the agreement (it's screwed anyway), select Yes if agree.
6. Once unlocked, run "flash-all".
7. Go running around your house for 10 mins.
Warning: This operation will wipe everything in your phone, if there's any crucial data, edit flash-all.bat to remove "-w" flag, and remove userdata.img in the occam zip.
Edit:
Or probably you can just get a toolkit...

ksilver89 said:
Alright, it is screwed. Long guide here: http://forum.xda-developers.com/showthread.php?t=2010312
Short guide:
1. You need basically 3 things, the factory image, fastboot, and nexus 4 drivers
2. Download and setup all of them.
3. Extract the factory image tgz file TWICE until you see a folder.
4. Place "fastboot" into that folder.
5. Unlock your bootloader, shift + right click inside the folder, Open command window here. Run "fastboot oem unlock" and read the agreement (it's screwed anyway), select Yes if agree.
6. Once unlocked, run "flash-all".
7. Go running around your house for 10 mins.
Warning: This operation will wipe everything in your phone, if there's any crucial data, edit flash-all.bat to remove "-w" flag, and remove userdata.img in the occam zip.
Edit:
Or probably you can just get a toolkit...
Click to expand...
Click to collapse
Thanks for your help. I appreciate it. I'm probably going to give this a try, couldn't get any worse. I think all data is gone anyhow when I did the factory reset option in the recovery, right? I did just call Google, they said I could get a replacement no problem, but that will probably take a week.

pixelbat said:
Thanks for your help. I appreciate it. I'm probably going to give this a try, couldn't get any worse. I think all data is gone anyhow when I did the factory reset option in the recovery, right? I did just call Google, they said I could get a replacement no problem, but that will probably take a week.
Click to expand...
Click to collapse
Yes, what he suggested should get you up and running again (if not, then yes your phone needs a replacement). I saw the video and the image. I'm pretty sure your system was wiped somehow and that's why you can't boot to it anymore. If what he suggested fails I can walk you through the steps to flash each factory image separately.

What would you do if the nexus 4 drivers wont install?
I have similar problem, I got the 4.3 update ota and it crashed half way through and now it gets stuck on the X logo. I was trying to follow a guide (http://forum.xda-developers.com/showthread.php?t=2010312) to install 4.3 back onto the device but failed at the first hurdle, when plugin the phone in it fails on the driver software installation - mtp usb device failed.
Is there any other way to do it?

pixelbat said:
Thanks for your help. I appreciate it. I'm probably going to give this a try, couldn't get any worse. I think all data is gone anyhow when I did the factory reset option in the recovery, right? I did just call Google, they said I could get a replacement no problem, but that will probably take a week.
Click to expand...
Click to collapse
unplug your phone. reboot into bootloader (vol down + power) but don't plug it in
downloaded the file posted in this topic from the google website.
http://forum.xda-developers.com/showthread.php?p=44088784
once you download it, extract it to a folder
then open up flash_all.bat in notepad, and it will say -w near the end. remove that (leaving it would wipe all of your data) and save the file
then run it, it will say waiting for device. plug your phone in and it will start updating

flipfamous said:
What would you do if the nexus 4 drivers wont install?
I have similar problem, I got the 4.3 update ota and it crashed half way through and now it gets stuck on the X logo. I was trying to follow a guide (http://forum.xda-developers.com/showthread.php?t=2010312) to install 4.3 back onto the device but failed at the first hurdle, when plugin the phone in it fails on the driver software installation - mtp usb device failed.
Is there any other way to do it?
Click to expand...
Click to collapse
Which driver did you try to install? Naked Drivers 0.72? What OS (Win8, Win7, etc)?
Plug your device in, go to control panel, click on Device Manager, scan for hardware changes or select the device with a yellow exclamation mark. Click on "Update driver" and search for the drivers in your PC (where you downloaded them). That should work.

Just Boot from a ubuntu live cd, install fastboot with apt-get and get started
Gesendet von meinem Nexus 4 mit Tapatalk 4 Beta

N910TUVS2EPK2 - got it rooted!

Happy, happy, happy! Since I got it to work, thought I'd share.
~ caveat emptor, not responsible if this doesn't work for you ~
First off, I followed this very helpful post from DeeXii:
https://forum.xda-developers.com/note-4-tmobile/general/recovery-n910t-t3-marshmallow-pe3-guide-t3406870
I had flashed the N910TUVS2EPK2 stock from Odin after screwing up my phone doing other crap. In any case, after doing that, I obviously wanted root again! Note that this wasn't immediate - I flashed to this a couple months ago, so have been fully setup with gmail, and other account settings. So, the above link gave the best overall, simple step-through, with handy download links. It worked, and even better didn't lose any of my settings. (but, no guarantees, make sure you've backed up!)
Additional details that would be helpful:
- make sure you run Odin as Administrator.
- Odin: click the button next to AP, and then go select the twrp archive you downloaded
- Power off phone, hold boot into download mode (power, home, volume down at same time). click volume up when it says so.
- connect to Odin. you need to see the square just below ID:COM turn blue.
- Click Start to flash the twrp.
- IMPORTANT: after it flashes, the phone will auto-restart. *Quickly* pull out battery before it boots, otherwise it will put back stock recovery on you. (this happened to me - I had waited until it had fully booted, then powered down, then brought it up in recovery mode, and it wasn't twrp! - so remember, pull out battery right after it cycles after flashing)
- Put battery back in, and then boot into recovery by holding power-home-volume up simultaneously. If you end up seeing the nice pretty twrp squares, then this worked. It is interesting that there is also a message here stating that the kernel may very well write back the custom recovery. So, can't say if this will be permanent or not, but at least you can now flash the supersu. (subsequent reboot into recovery still seems to have twrp, so groovy!)
- (presuming you had already put the supersu on the sd card or internal memory - I used the systemless supersu), click install, select it and flash.
- just for kicks (not sure if this was needed or not), after flashing I saw an option to wipe cache/dalchik, so I did that too.
- rebooted (it took awhile, had to 'optimize' all the apps, etc.) - and I'm rooted!
If anyone has been trouble with specifically the N910TUVS2EPK2 build, then I hope this helps.

Thanks man, had the same issue. I figured it might be something to do with booting int OS. Sure enough with 6.0.1 EPK2 rom you MUST load into boot recovery right after flashing TWRP as you stated.
Something went wrong with my OTA update of EPK2 and it started to bootloop( 2 vibrates upon restart and then random amount of bootloops, and then random, soon-coming freeze upon loading in OS and continuing boot-looping) sometime after the update. I erased most of the old stuff via TWRP reinstalled EPK2 bootloader separately and then flashed EPK2 rom and it seems to be OK so far (knock on wood). We'll see hopefully it's not hardware issues like many people were reporting with bootlooping.

Can't you just uncheck the Odin option to reboot instead of the frantic battery pull?
Just wondering, as I'm going to do this later- thanks!
Steven.RN
Followup: Yep. Slip over to the options tab in Odin and uncheck "auto reboot". After Odin flashes TWRP, (the bar is all the way across the download screen, and the Odin Log says "succcess") go ahead, disconnect the phone from USB. Do your battery pull, replace battery. Close up the phone, then hit Volume up, home, and power at the same time- Bang! TWRP screen.
Further note: first time I did this flash, it didn't work, it just stopped in it's tracks. Then I realized I had to enable "developer mode" by clicking on the build number in the "About phone" sections in settings 5 times, going into Developer mode (the new option will present itself in the menu on settings), then: enable OEM unlock and USB debugging. Odin will flash TWRP just fine after that. (Duh on me!)

planetjeff said:
Happy, happy, happy! Since I got it to work, thought I'd share.
~ caveat emptor, not responsible if this doesn't work for you ~
First off, I followed this very helpful post from DeeXii:
https://forum.xda-developers.com/note-4-tmobile/general/recovery-n910t-t3-marshmallow-pe3-guide-t3406870
I had flashed the N910TUVS2EPK2 stock from Odin after screwing up my phone doing other crap. In any case, after doing that, I obviously wanted root again! Note that this wasn't immediate - I flashed to this a couple months ago, so have been fully setup with gmail, and other account settings. So, the above link gave the best overall, simple step-through, with handy download links. It worked, and even better didn't lose any of my settings. (but, no guarantees, make sure you've backed up!)
Additional details that would be helpful:
- make sure you run Odin as Administrator.
- Odin: click the button next to AP, and then go select the twrp archive you downloaded
- Power off phone, hold boot into download mode (power, home, volume down at same time). click volume up when it says so.
- connect to Odin. you need to see the square just below ID:COM turn blue.
- Click Start to flash the twrp.
- IMPORTANT: after it flashes, the phone will auto-restart. *Quickly* pull out battery before it boots, otherwise it will put back stock recovery on you. (this happened to me - I had waited until it had fully booted, then powered down, then brought it up in recovery mode, and it wasn't twrp! - so remember, pull out battery right after it cycles after flashing)
- Put battery back in, and then boot into recovery by holding power-home-volume up simultaneously. If you end up seeing the nice pretty twrp squares, then this worked. It is interesting that there is also a message here stating that the kernel may very well write back the custom recovery. So, can't say if this will be permanent or not, but at least you can now flash the supersu. (subsequent reboot into recovery still seems to have twrp, so groovy!)
- (presuming you had already put the supersu on the sd card or internal memory - I used the systemless supersu), click install, select it and flash.
- just for kicks (not sure if this was needed or not), after flashing I saw an option to wipe cache/dalchik, so I did that too.
- rebooted (it took awhile, had to 'optimize' all the apps, etc.) - and I'm rooted!
If anyone has been trouble with specifically the N910TUVS2EPK2 build, then I hope this helps.
Click to expand...
Click to collapse
thanks for the info, might give it a shot tonight. you have a link to the software update so i can load it with odin?

Thanks for the post. Where can I find the stock N910TUVS2EPK2 ROM?

Charlie Rock said:
Thanks for the post. Where can I find the stock N910TUVS2EPK2 ROM?
Click to expand...
Click to collapse
sammobile.com
Sent from my SM-N910T using Tapatalk