Hey people. I'm seriously pulling my hair out for the last five days. I didn't want to post but you guys are my last hope. I'm not knew to rooting and have flashed many roms on my beloved s3 but this one is killing me.
I've read literally hundreds of threads and watched youtube videos on how to disable/remove this knox app and it's just causing so much grief.
Here's what I have and what i've tried.
Galaxy S3 D2att (on Bell In canada)
Currently running Stock 4.2.2 KOT49H.I747MVLUF0B1
Not rooted (This is my first issue as nothing I've tried will let me root)
Goal is to install Cyanide 5.1 rom or equivalent.
- I've tried uninstalling the knox app from with the app (Settings>About Uninstall) there is no about or uninstall option.
- Odin - Installed the latest openrecoverty-twrp-2.8.5.0 Although it appears to install fine, it won't allow me to mount anything and the console shows many errors in red.
-Samsung's default recovery - gives me an error. No Command with the dead android logo. This does mount the external and internal sd cards and I can flash items, but they all give errors.
_tried flashing a few De-samsungizer scripts, knox removal scripts, Latest SuperSU all unsuccessful. I get the following error.
E:footer is wrong
E: Signature verification failed
(no way to disable signature verification)
Tried un-installing the Knox package with different apps people say works including a few pay apps that I purchased and promptly refunded after they didn't work.
The phone boots up fine with stock so it's not bricked.
Any help would be greatly appreciated. I am unable to even downgrade to 4.1.1 as no recovery will allow me to flash a zip successfully.
:crying:
Flash an rom image that has Knox already removed that what I did I use this guide
http://forum.xda-developers.com/showthread.php?p=28019751
There is no need to disable Knox, root, or enable debugging to install a custom rom.
Use Odin to flash a custom recovery such as twrp or philz. Boot to custom recovery, do a full wipe, flash custom rom.
I have tried put the latest TWRP on via odin and although odin reports no errors, when I boot into recovery, twrp is unable to mount any internal or external sd cards. Gives errors so i am unable to flash any files via recovery.
Try Philz touch for the d2lte of twrp doesn't work.
You're flashing the latest twrp for the d2lte?
Im flashing the latest twrp for d2att. Im at work now . Will give philz twrp when i get home and report back.
Philz should work. After flashing recovery, you can wipe and flash a new rom.
If you want to remove Knox on your existing rom, flash supersu from recovery, reboot, open supersu, and let supersu disable Knox.
audit13 said:
Philz should work. After flashing recovery, you can wipe and flash a new rom.
If you want to remove Knox on your existing rom, flash supersu from recovery, reboot, open supersu, and let supersu disable Knox.
Click to expand...
Click to collapse
Hey Audit, thanks for your help.. Am I correct that I am getting the 'd2lte' version of Philz? This will work with my galaxy S3 on Bell (SGH-I747M)? Im just used to getting a d2att version of roms.
Development for the d2lte and d2att were unified under the d2lte moniker.
Anything designed for the d2lte should work on the d2can and d2att. If something is labelled specifically for a d2can or d2att, this leads me to believe the item is old. That being said, TWRP still uses the d2att labelling scheme for its recovery for the d2lte.
audit13 said:
Development for the d2lte and d2att were unified under the d2lte moniker.
Anything designed for the d2lte should work on the d2can and d2att. If something is labelled specifically for a d2can or d2att, this leads me to believe the item is old. That being said, TWRP still uses the d2att labelling scheme for its recovery for the d2lte.
Click to expand...
Click to collapse
Thanks.. I figured that labeling out after I sent my previous message and let me also say Major thanks for helping me out. Philz worked like a charm.. Was able to install Super SU and disable Knox. Not to decide with 5.1 rom I wanna install.
Related
Hello...anyone have stock kernel for ATT i927? Thanks.
2.3.6 upgrage is only on AT&T i believe..
and only available through OTA...
So if you are an AT & T Customer swtich back to AT&T Stock kernel and ROM and do an upgrade..
I just installed this kernel http://forum.xda-developers.com/attachment.php?attachmentid=806478&d=1323125030 and tried the update and it still didn't work. Is this the stock ATT kernel?
I think the problem lies in the recovery image. The update may be relying on the original recovery being intact (not ClockworkMod or any other). Thus, it may not be possible to update without having the original recovery in place. I have CWM recovery and the rooted kernel installed and cannot install the over-the-air updates. When I restart the phone after it's downloaded, my phone reboots into CWM and that's it. Rebooting into the OS afterwards gives me the message that the update failed.
While in recovery, I delved a bit into the filesystem using ADB and saw that the update files are there (this thread has a bit of what I'm talking about), but I don't think CWM knows what to do with them, therefore the update fails.
Are people without CWM having this problem? Furthermore, is there any way to return to the stock recovery if this is, in case, the problem?
Could you not use Odin and remove the CWM? Reflash a kernal without the CWM?
dudejb said:
Could you not use Odin and remove the CWM? Reflash a kernal without the CWM?
Click to expand...
Click to collapse
I never installed or used CWM. Is CWM something that gets installed with the rooted ROM? The only app I noticed installed with the rooted ROM was superuser and I deleted it. When I run AVG I still get the warning that my device is rooted, but when I type "su" in the emulator it says denied...is there something else I'm missing? Thanks.
CWM Recovery is what's installed if you have ever followed this guide. It's separate from the kernel and the ROM. On most phones, it's installed from ClockworkMod's ROM Manager, but we have to flash it via Odin. It replaces the stock recovery, but offers more features (such as the ability to flash ROMs from the phone itself, instead of having to use Odin on a PC, as well as allowing for full, or nandroid, backups of the phone).
I am ATT and I updated after I rooted with no problems. Some people reported that the update will fail if you're battery isn't mostly charged.
CWM won't be there unless you specifically installed it.
I would be interested in this too. I have been unable to get the update to go through after having flashed another ROM.
Hi everyone,
Has anyone been successful in getting any of the CWM recovery variants to work on the N7105T? Every version I can find listed for the N7105 (no dedicated N7105T version, from both XDA/Google/ROM manager) causes the phone phone to boot into the standard Samsung screen. However the screen then glitches by moving to the left and disappears all together.
Easily rectified by flashing TWRP recovery or stock recovery, but the issue is I'm attempting to install one of the Modem files for the N7105T after flashing an N7105 custom ROM. Without the modem file the custom ROMS also experience the same glitch mentioned above from CWM recovery. Unfortunately the modem.zip file I have on file cannot be found in the Download directory of the phone when using TWRP so I suspect I'll have to flash this using CWM.
Any thoughts? Or better yet, has anyone else successful loaded a custom N7105 ROM by flashing the ROM and then the modem.zip in CWM as above for the N7105T or by any other methods?
FYI;
Just flashed Phils modification of CWM which works successfully on the N7105T without the glitch. However the phone still cannot boot into a custom N7105 ROM successfully.
I tried to do the below to no avail;
Using Phils Recovery, flashed Paranoid Android & applicable GAPPS. After this I flashed the N7105T Telstra Modem using Phils Recovery. Rebooted phone and the phone turns on and screen 'glitches' as described earlier.
I also have the same problem
Note2-CWM-6.0.4.1-GT-N7105t
Jonnit said:
Hi everyone,
Has anyone been successful in getting any of the CWM recovery variants to work on the N7105T? Every version I can find listed for the N7105 (no dedicated N7105T version, from both XDA/Google/ROM manager) causes the phone phone to boot into the standard Samsung screen. However the screen then glitches by moving to the left and disappears all together.
Easily rectified by flashing TWRP recovery or stock recovery, but the issue is I'm attempting to install one of the Modem files for the N7105T after flashing an N7105 custom ROM. Without the modem file the custom ROMS also experience the same glitch mentioned above from CWM recovery. Unfortunately the modem.zip file I have on file cannot be found in the Download directory of the phone when using TWRP so I suspect I'll have to flash this using CWM.
Any thoughts? Or better yet, has anyone else successful loaded a custom N7105 ROM by flashing the ROM and then the modem.zip in CWM as above for the N7105T or by any other methods?
Click to expand...
Click to collapse
I'm using Note2-CWM-6.0.4.1-GT-N7105t and all is good. I have never updated to 4.3 officially, I rooted with odin, while on 4.1.1 and used this recovery and have been flashing for months. I now am trying to return to stock and update to 4.3. Just so I can use stock kernel in custom 4.3 roms ( Wifi won't work unles flash Agni or Devil kernels ). http://techbeasts.com/2013/08/22/how-to-root-install-cwm-recovery-on-samsung-galaxy-note-2/ - happy to help more.
---------- Post added at 08:58 PM ---------- Previous post was at 08:46 PM ----------
slysurfer said:
I'm using Note2-CWM-6.0.4.1-GT-N7105t and all is good. I have never updated to 4.3 officially, I rooted with odin, while on 4.1.1 and used this recovery and have been flashing for months. I now am trying to return to stock and update to 4.3. Just so I can use stock kernel in custom 4.3 roms ( Wifi won't work unles flash Agni or Devil kernels ). http://techbeasts.com/2013/08/22/how-to-root-install-cwm-recovery-on-samsung-galaxy-note-2/ - happy to help more.
Click to expand...
Click to collapse
Follow all steps. - http://androidxda.com/root-samsung-galaxy-note-2-n7100t.
Now I updated to stock telstra 4.3, using odin v3.09. Firmware from samsmobile. worked first go and many times since
Then I flashed philz recovery - ( philz_touch_6.15.4-t0lte.tar) with odin v1.85 - untick auto-reboot and once installed just hold vol up/home and power to get to philz recovery - Then to root, download and extract saferoot = http://forum.xda-developers.com/showthread.php?t=2565758 - it works on GT-N7105T ( just a N7105 really once you get a message on your phone about allowing USB ADB debugging / SU permision, all is good. I started the bat file again after i got the su message prior attempt and it completed. Then I updated supersu in play store then opened and updated binary in supersu and restarted phone. Just installed CWM and installed cm touch recovery app granted permissions, like on 4.1.2. phone is free now. will install roms tonight. any issues i will update this.
Tmobile Galaxy S4 (SGH-M919) Non-rooted
Problem:
The phone was working and then suddenly went into boot loop. The Samsung screen displays and right before it would goto the animation screen, it loops. I can get to download mode and the recovery OS.
What I've tried:
- First thought it was power button, sent it away to replace button but tech says it's not power button. The phone doesn't turn itself on when the battery is inserted. I can use the power button to turn on/off the phone fine.
- Cache wipe
- Factory reset
- Kies update/recovery
- Burn different firmware version (NB4, NH7, NK2, OH3)
- Tried just to burn NB4 twice consecutively without reboot (first time OK. when burn second time w/o reboot, the phone would display error saying the percentage completed is incorrect since it just finished 100%. Odin continues to burn to finish fine.)
Nothing seems to work. It still loops.
I am desperate. Please help! Thanks in advance.
Beocop
An update:
I tried CF Root and was able to get past he first Samsung screen, past the white TMobile screen, but it went back to boot loop again. Don't know what else to do. Any suggestions?
By burn do you mean you odin'd official stock rom? You cannot downgrade after 4.2.2 MDL so if you flashed OH3 then NB4 will not work anymore...just flash oh3 and root it. For root you can either flash recovery through odin then fash supersuBETA via recovery. Or (if you dont have a computer near you) use kingroot then push recovery through terminal emulator, then run remove kingroot app (google it) then flash supersu through recovery. Link to supersubeta: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
lordodin912 said:
By burn do you mean you odin'd official stock rom? You cannot downgrade after 4.2.2 MDL so if you flashed OH3 then NB4 will not work anymore...just flash oh3 and root it. For root you can either flash recovery through odin then fash supersuBETA via recovery. Or (if you dont have a computer near you) use kingroot then push recovery through terminal emulator, then run remove kingroot app (google it) then flash supersu through recovery. Link to supersubeta: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
I've tried flashing OH3 (twice) also. It still boot loops. Then I tried CF Root to see if it does anything. It flashes fine with no problem. It still boot loops.
I can get into download mode and recovery without problem. It just won't let me past the boot loop.
Try different versions of odin/usb cables and reflash. Or and this voids WARRANTY. Put TRWP on your phone and try a different kernel or OS.
lordodin912 said:
Try different versions of odin/usb cables and reflash. Or and this voids WARRANTY. Put TRWP on your phone and try a different kernel or OS.
Click to expand...
Click to collapse
update:
- I've tried different odin versions (3.07,3.09,3.10). I've tried different USB cables. There was no indication on any error during the flashing process.
- I can flash any stock ROM after NB4 (anything before NB4 => Odin fail). After flashing stock ROMS, it can never get past the Galaxy S4 screen. It just boot loop.
**** I tried to download the OH3 stock rom from Sammobile but I always get a corrupt file error in Winrar. Can someone verify if the OH3 ROM on Sammobile is error free?
- I've tried TWRP (2.6.0.0, 2.6.3.1, 2.8.4.0). I've used it to flash CM-12.1 and Darthstalker_S4_V3 ROMs.
- After flashing all the custom CM ROM, it got stuck with the pink screen.
- I get nothing from Darthstalker ROM, just blank.
I am so frustrated with this process. It seems that I am doing something wrong in my process to flash the ROMs. I am missing something.
Can you please list ALL the steps necessary to properly flash a ROM? Please list every single step that you would personally take, no matter how insignificant (remove battery, clear cache, settings, etc.). Just treat me like a 1st grader.
Thanks so much.
Another update...
- So far, I've tried to flash stock ROMS (NB4-OH3) with odin. None of the stock ROMs will boot fully. All stuck at Samsung logo and bootloops from there.
- The best, but not fully functional, solution I've found so far is from:
1- Flash stock rom NH7 (tried NB4,NH7 so far) with odin
2- Flash CF auto root (CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5) with odin
3- Flash CWM for recovery
4- boot into recovery, from CWM, install cm-11-20140110-SNAPSHOT-InstallerXNPQ02R-jfltetmo-signed.zip from sdcard1
5- From CWM, install gapps kk for 4.4.3 from sdcard1
6- Clear dalvik, format data + cache
It'll boot up fine. However, I get no sound (not from speaker or headphone). Google keyboard keeping turn on and off. The camera doesn't work. Video's cannot be played.
info "about phone":
Model: SGH-M919
Android version: 4.4.2
Baseband version: M9191UVUFNH7 (prob from CF auto root ?)
Kernel version: 3.4.0 cyanogenmod
Cyanogenmod version: 11.0-installer-XNPQ02R
Build date: 1/9/14
Build number: cm_jftetmo-userdebug4.4.2 KOT49H-installerXNPQ02R release-keys
Don't know what to do now. I've no idea why it won't take stock ROMs. I don't know why I am having problems in cyanogenmod. I freakin hate working on these phones.
Any ideas? suggestions? PLEASE!
Flash philz cwm touch recovery with your current recovery. Then use philz recovery to flash this rom: http://forum.xda-developers.com/galaxy-s4-tmobile/development/moving-please-post-t3009561.
Vicious89 said:
Flash philz cwm touch recovery with your current recovery. Then use philz recovery to flash this rom: http://forum.xda-developers.com/galaxy-s4-tmobile/development/moving-please-post-t3009561.
Click to expand...
Click to collapse
Update:
-OK. I tried using philz cwm and burned this ROM but went through the installation process and picking choices. However, it wouldn't even boot.
-I decided to open up the phone to verify I had a SGH-M919. The sticker underneath the battery indicated SGH-M919. The phone has been using and updating OTA with T-Mobile firmware, the latest being OH3 with stagefright fix.
-After I removed the motherboard, what I saw underneath was disturbing. There was one big stamping showing "I337", which is AT&T. Many other stampings on the chips also show I337.
-In download mode, the product name indicated "SGH-M919".
So the question is, do I have a I337 or M919 phone? Currently, I cannot flash or install any firmware that is not for M919. I tried flashing ATT stock rom (I337ATTFNB1) with odin but it failed, indicating many errors such as PIT. I tried installing CM 11 for ATT but it also failed indicating that I need jfltetmo (M919) version. Ever since the bootloop problem, I cannot get the phone to boot with stock M919 roms.
Hi all,
I am new here and I am having trouble with my Galaxy 3 SGH-I747 from at&t
I rooted the phone using KingoRoot and everything was fine.
I used the phone for about a week and decided to update from kitkat 4.4.2 to lolipop 5.0.
I have a micromax phone that is rooted and I didnt have any trouble updating it while it was rooted, so i figured it wouldnt be a problem but when I updated the s3 it said update failed at 94% and started rebooting and got stuck in an update loop.
I searched and searched and tried finding recovery options using odin but I cant find a 4.4.2 stock firmware, and cant find much information on recovering my device.
I am unable to boot in to recovery. I cant find a link for the SGH-I747 to philz recovery, the links all seem to be dead.
I can boot in to download mode.
I want to install a custom recovery via ODIN but i cant find one for my phone.
After I install the custom recovery, how will i know which stock OS my phone is currently at
I appreciate any advice you can give me, thanks.
Use TWRP for custom recovery. CWM and Philz haven't been updated in quite a while. You can get odin flashable tars from here.
Flashing TWRP should get you to working recovery, and you can find the rom zips you need to get back up and running in the development section here.
Unrooted stock will overwrite TWRP with stock recovery upon boot. Depending on how far your phone is getting into the booting process that might happen if you let odin auto-reboot. Your best bet is to uncheck auto-reboot in odin, so it won't restart on you automatically. Upon success remove the USB cable and pull battery. Replace battery and boot straight to recovery by holding home+vol up+power until you see tiny blue text in the upper left corner then releasing.
Thankyou! i was able to install the recovery by TWRP.
I just need to figure out what firmware to install and where I can get it... I was on kitkat, I tried to update to lollipop but it didnt work. My phone is bricked so I dont know how i would see the firmware version on it.
I really just want any kind of stable firmware that is rooted. Any ideas where I could find one? I'm trying to sift through the forums
Lots of ROMs are available here: http://forum.xda-developers.com/galaxy-s3-att/development
audit13 said:
Lots of ROMs are available here: http://forum.xda-developers.com/galaxy-s3-att/development
Click to expand...
Click to collapse
I appreciate all the help - It seemed really hard because I was finding roms and flashing with ODIN but it always failed TWRP is giving me results. I flashed slimkat and got my phone working again! the only problem is my sound is a bit junky, idk why.
I plan on trying out Octos - M, because I heard marshmallow OS has a lot better battery life among other things
If i upgrade to a custom marshmallow OS, is there any coming back to a former custom OS like 4.4.2? or is it a permanent upgrade?
Do you guys recommend any custom OS? I need something stable, that uses the resources efficiently.
Before flashing additional ROMs, make sure the phone is running the latest bootloader and modem.
To verify the installed bootloader and modem, install the Samsung Phone Info app from the Play store.
With a custom ROM, you can flash from one to another, usually without any issues as long as you perform a complete wipe (system, data, cache) before flashing a new ROM. If you are upgrading an existing custom ROM with a newer custom ROM (e.g. CM12.1 2016-01-01 nightly to CM12.1 2016-01-02 nightly), you can just flash the updated ROM over the existing ROM.
Recently I flashed through TWRP Resurrection Remix new 7.1.1 Nougat on my Tmobile Note3. Was working great. I had the newest twrp 3.0. I was looking at a custom ROM that said I would need CWM so I downloaded CWM from Google play and I ran it. I decided to back up through CWM and it rebooted my phone. My phone rebooted into recovery, and is stuck in recovery bootloop now. It keeps rebooting into recovery. I tried to fix by taking out battery for a long time but when I turn it on againit goes back to recovery in the loop. It can power into download mode. I don't know what to do in that mode though. Please help me. If I'm to use a computer to flash a different OS please include all links to find the downloads as well as the links for finding the usb drivers. Anyone know what I'm to do?
pax216 said:
Recently I flashed through TWRP Resurrection Remix new 7.1.1 Nougat on my Tmobile Note3. Was working great. I had the newest twrp 3.0. I was looking at a custom ROM that said I would need CWM so I downloaded CWM from Google play and I ran it. I decided to back up through CWM and it rebooted my phone. My phone rebooted into recovery, and is stuck in recovery bootloop now. It keeps rebooting into recovery. I tried to fix by taking out battery for a long time but when I turn it on againit goes back to recovery in the loop. It can power into download mode. I don't know what to do in that mode though. Please help me. If I'm to use a computer to flash a different OS please include all links to find the downloads as well as the links for finding the usb drivers. Anyone know what I'm to do?
Click to expand...
Click to collapse
Hello,
I will move your thread to the correct section, whereas experts there might be able to assist you.
Regards
Vatsal,
Forum Moderator.
pax216 said:
Recently I flashed through TWRP Resurrection Remix new 7.1.1 Nougat on my Tmobile Note3. Was working great. I had the newest twrp 3.0. I was looking at a custom ROM that said I would need CWM so I downloaded CWM from Google play and I ran it. I decided to back up through CWM and it rebooted my phone. My phone rebooted into recovery, and is stuck in recovery bootloop now. It keeps rebooting into recovery. I tried to fix by taking out battery for a long time but when I turn it on againit goes back to recovery in the loop. It can power into download mode. I don't know what to do in that mode though. Please help me. If I'm to use a computer to flash a different OS please include all links to find the downloads as well as the links for finding the usb drivers. Anyone know what I'm to do?
Click to expand...
Click to collapse
I find it odd that you would find a ROM that suggests CWM instead of TWRP, but the way I see it is you go back to Resurrection Remix or try to flash the new ROM you found with TWRP (2.8.7 is recommended)
You can download the .tar file for TWRP 2.8.7 here: https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar.html
For clearer instructions, you can visit this post: https://forum.xda-developers.com/showthread.php?t=2672393
These are instructions to flash back to stock, root and install TWRP 2.8.7
I suggest right after doing this, you flash the ROM you want, that will guarantee a "cleaner" installation of the ROM
Good luck!
ShaDisNX255 said:
I find it odd that you would find a ROM that suggests CWM instead of TWRP, but the way I see it is you go back to Resurrection Remix or try to flash the new ROM you found with TWRP (2.8.7 is recommended)
You can download the .tar file for TWRP 2.8.7 here: https://dl.twrp.me/hlte/twrp-2.8.7.0-hlte-4.4.img.tar.html
For clearer instructions, you can visit this post: https://forum.xda-developers.com/showthread.php?t=2672393
These are instructions to flash back to stock, root and install TWRP 2.8.7
I suggest right after doing this, you flash the ROM you want, that will guarantee a "cleaner" installation of the ROM
Good luck!
Click to expand...
Click to collapse
Thank you for your help. I did all the clear instructions from the thread. I couldn't get the CF auto root to stick. Also couldn't find a surfboard for TWRP 2.8.7, they only have 2.8.0 on the TWRP site, or TWRP 3.0. Ultimately I've got my original factory stock lollipop back. I'm no longer rooted. I had rooted before through KingRoot. I tried again and it says that I'm out on a list for root for my phone. So my phone works again. I guess I should be happy with that.
If you want to root, you could try flashing cfautoroot with Odin.
audit13 said:
If you want to root, you could try flashing cfautoroot with Odin.
Click to expand...
Click to collapse
I did try to flash CF auto root with Odin after I flashed back to the stock ROM. But it didn't work. It stayed stuck on the T mobile screen for a very long time. So I just gave up trying to root again and stayed with the stock ROM without root. Thanks. Maybe I'll try again and see if it'll work next time.
Flashing twrp with Odin and flashing supersu from twrp had always worked for me.
audit13 said:
Flashing twrp with Odin and flashing supersu from twrp had always worked for me.
Click to expand...
Click to collapse
Will that root my device?
Yes. When I want root with stock recovery, I use cfautoroot. When I want a custom recovery and root, I flash twrp and supersu.
audit13 said:
Yes. When I want root with stock recovery, I use cfautoroot. When I want a custom recovery and root, I flash twrp and supersu.
Click to expand...
Click to collapse
OK. Thanks. Also, which version of TWRP? I can't seem to find a download for 2.8.7.0, only for 2.8.0.0 and 3.0 on the official TWRP site. Also where can I find SuperSu? Do I flash SuperSU with TWRP once TWRP is on phone? I read somewhere that the best version for TWRP is 2.8.7.0, but I can't find it anywhere.
Twrp for T-Mobile note 3: https://dl.twrp.me/hltetmo/
Flash twrp using Odin. Olen Odin, do not check anything except f reset time. Flash twrp. When you see the word reset in the status window, remove USB cable from phone, remove battery, replace battery, use button combination to boot into recovery, connect to computer, copy supersu to phone memory, flash supersu from twrp.
Supersu: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
audit13 said:
Twrp for T-Mobile note 3: https://dl.twrp.me/hltetmo/
Flash twrp using Odin. Olen Odin, do not check anything except f reset time. Flash twrp. When you see the word reset in the status window, remove USB cable from phone, remove battery, replace battery, use button combination to boot into recovery, connect to computer, copy supersu to phone memory, flash supersu from twrp.
Supersu: https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703
Click to expand...
Click to collapse
OK. Thank you. I will get to this next time my friend is available with the computer.