Develop Bugs

[Kernel] Insecure/Rooted, CWM-Flashable MVLALH1 [ADB][init.d][Custom Bootanimation]

Hey everyone,
This is a modified stock kernel based on the Canadian stock kernel MVLALH1 and is ONLY compatible with stock-based ICS roms from the i747m. I haven't seen this around so I decided to make it myself for all to use and assist in development and was contacted to make this for all you Canadian folks without much dev help. The root application of choice is Chainfire's SuperSU. Remember that the first boot takes longer than usual after you clear the cache.
Features:
•Insecure rooted kernel
•init.d script support
•ADB support
•Custom bootanimation.zip support
Instructions:
1.Download the recovery-flashable zip to your phone's SD card
2.Flash in recovery
3.Wipe cache and dalvik cache
4.Reboot and enjoy
Standard disclaimer: I am not responsible for anything bad that happens to your phone. I have personally tested this on my own AT&T SGS3 and it works great for me.
Special thanks to NunHugger for his infinite wisdom in helping me figure out how to get custom boot animations working and letting me borrow his updater script. Also thanks to dsixda for the amazing Android Kitchen. Thanks again neuropass for your donation. Always appreciated, never necessary.
Download:
From here
Or, alternatively, directly from this thread
Kernel Source: http://opensource.samsung.com

Secondary Odin Instructions
This is the modified kernel made flashable in ODIN ONLY. Do not flash this in recovery as it will not work. Flashing with ODIN will increase your flash counter so if you use it, make sure to use Triangle Away to set your counter back to zero. Flashing using Mobile ODIN will NOT increase your flash counter, however.
Download:
ODIN-Flashable Kernel
Mirror
Checksum: 5a100e185ab55f69bb42bd84852a6bd9

stratatak7 said:
This is the modified kernel made flashable in ODIN ONLY. Do not flash this in recovery as it will not work. Flashing with ODIN will increase your flash counter so if you use it, make sure to use Triangle Away to set your counter back to zero. Flashing using Mobile ODIN will NOT increase your flash counter, however.
Download:
ODIN-Flashable Kernel
Mirror
Checksum: 5a100e185ab55f69bb42bd84852a6bd9
Click to expand...
Click to collapse
Awsome thanks..

Fantastic. Thanks again.

You're welcome! I haven't tested it yet but I didn't change any of my processes. Just trying to help out the friends up north.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

stratatak7 said:
This is the modified kernel made flashable in ODIN ONLY. Do not flash this in recovery as it will not work. Flashing with ODIN will increase your flash counter so if you use it, make sure to use Triangle Away to set your counter back to zero. Flashing using Mobile ODIN will NOT increase your flash counter, however.
Download:
ODIN-Flashable Kernel
Mirror
Checksum: 5a100e185ab55f69bb42bd84852a6bd9
Click to expand...
Click to collapse
First of all, thanks for the kernel! Only one problem I got. I flashed this through Odin but it seems my device is still not rooted. what do I do next?
I tried installing the already rooted Samsung firmware but the install just hangs and soft bricks my S3 so I reverted back to stock and trying to root in a different way.
Any help? Please?

islandboy_2000 said:
First of all, thanks for the kernel! Only one problem I got. I flashed this through Odin but it seems my device is still not rooted. what do I do next?
I tried installing the already rooted Samsung firmware but the install just hangs and soft bricks my S3 so I reverted back to stock and trying to root in a different way.
Any help? Please?
Click to expand...
Click to collapse
I apologize I should be more clear. The insecure kernel allows you to actually root but does not actually root the device. The next step in the process is for you to flash supersu or superuser (preferably in recovery. Go to chainfires supersu thread and it will provide you with the correct packages to flash. I believe that is one method of doing it. By insecuring a kernel it just allows you to root. You'll need to include su binaries but the cwm packages on chainfires thread should take care of that. Let me know if you're still having issues and I'll take a more personal look into it.
Secondary: I know for sure if you download the qcom toolkit it will quide you through rooting without issues at all. Then you can simply flash this kernel overtop and you should still be able to keep root.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

stratatak7 said:
I apologize I should be more clear. The insecure kernel allows you to actually root but does not actually root the device. The next step in the process is for you to flash supersu or superuser (preferably in recovery. Go to chainfires supersu thread and it will provide you with the correct packages to flash. I believe that is one method of doing it. By insecuring a kernel it just allows you to root. You'll need to include su binaries but the cwm packages on chainfires thread should take care of that. Let me know if you're still having issues and I'll take a more personal look into it.
Secondary: I know for sure if you download the qcom toolkit it will quide you through rooting without issues at all. Then you can simply flash this kernel overtop and you should still be able to keep root.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks a bunch for clearing that up! I will let you know once I'm succesful. Cheers! :good::laugh:

[GUIDE] Root T999 (variants) on android 4.3 AND remove knox

WARNING: Following any of these instructions WILL void your warranty,
and could possibly cause irreparable harm to your device (i.e. bricked)
If you do Not understand these risks, stop here and do Not proceed.
If you do Not know how to use Odin, stop here and do Not proceed.
This guide is ONLY for SGH-T999 variants that are ALREADY RUNNING android 4.3
If you do Not have a SGH-T999 variant, stop here and do Not proceed.
If you are Not currently running android 4.3, stop here and do Not proceed.
I am not responsible for anything that happens to your device. YOU chose to follow this guide.
I have the SGH-T999V (samsung galaxy S3, canada, Videotron)
I flashed the full 4.3 firmware from samsung-updates.com as soon as it became available ... and then I tried to root it the usual ways
However knox prevented the superSu app from running, and it closed immediately, and obviously root was Not available to any app
This method will obtain ROOT and REMOVE the knox garbage
note ... altho it is optional to remove knox, I have Not tested without removing knox and do Not know if root will work using this method (guide) with knox still installed !
I did NOT create this method ... I simply found it, read thru user comments, and used it
FULL CREDIT goes to
@upndwn4par for the method ... the thread is here
@Kaito95 for the Knox Removal script ... the thread is here
@Dees_Troy for the TWRP recovery
@Chainfire for SuperSu
as you can see, this method was for the AT&T, Rogers, Bell, Telus Samsung Galaxy S3 ... I747 variants, I believe
So here is how I achieved a successful root on 4.3 using the above method, with adjustments for our T999 variant
Using Method #2
1. Download required files
a) download Odin 3.07 to your PC​
b) download the latest TWRP recovery for your device, in TAR format, to your PC
click on your device here
scroll down on your device page to the section called Download - Odin Flashable Tar
below that, click on the Select the latest .tar file from here link
scroll to the bottom of the files and click on the latest TAR version
note to d2tmo users ... thanks to @Perseus71 it has been noted that 2.6 versions may have issues on your device, and it is recommended that you choose the 2.5.0.0 TAR version
example: Mine looks like this: openrecovery-twrp-2.6.3.0-d2can.tar
note to T999V users ... both d2can and d2tmo work for our device ... I personally use d2can​
c) download SuperSu 1.65 zip to your DEVICE​
c) download Knox Removal zip to your DEVICE​
2. Reboot into Download mode ... VolumeDOWN + Power + Home
Run Odin
make sure that re-partition is NOT checked!
click the PDA button and point to the TWRP recovery TAR file that you downloaded above
connect your device to the computer ... wait briefly
the COMM port in top left box should turn blue
click Start
when it is done, PASSED, and phone has rebooted, disconnect device
3. Reboot into Recovery mode ... VolumeUP + Power + Home
Flash (install) the Knox Remover zip
Flash (install) the SuperSu zip ... it is version 1.65, current is 1.80, so it will prompt us to update later :good:
Reboot System
4. Update SuperSu from the Play Store
5. Open SuperSu
it should prompt that it needs to update the binary
accept and let it update the binary the Normal way
6. Reboot
7. Enjoy rooted 4.3, knox-free :laugh: :good:
​
thanks again to @Perseus71 for noting that it is possible that the default Enforcing mode of SElinux may cause issues with the ability and/or performance of some root apps despite being granted root permission
if you are experiencing similar issues, he recommends that you check out the SELINUX Status Changer app.
[I have Not personally tested this app]

reserved
in case

You may also wish to mention the SELINUX Status Changer. Here's the Thread.
With it enabled, root won't be stable.
Ahem. First ?
EDIT - TWRP 2.6.x.x has trouble remounting and formatting /Data. You may wish to reccomend version 2.5.0.0

Perseus71 said:
You may also wish to mention the SELINUX Status Changer. Here's the Thread.
With it enabled, root won't be stable.
Ahem. First ?
EDIT - TWRP 2.6.x.x has trouble remounting and formatting /Data. You may wish to reccomend version 2.5.0.0
Click to expand...
Click to collapse
hi and thanks for your input
I just looked at that SELINUX Status Changer thread and will keep an eye on it ... but for now I won't add it cuz:
the dev says it is pre-alpha version
Mine is Enforcing and root seems stable and hasn't had any problems, yet ... 4 days so far
SElinux is here to stay, and there's a big difference between proper (Google) implementation and samching implementation ... root blocked by samching, but not by standard android enforcing #BAM
congrats on being first, lol
what kind of things are you referring to when you say that root won't be stable?
what is your device d2 id?
I haven't had any problems with twrp 2.6.3 for d2can
THAT is something I WILL add, for your specific device
any particular reason you're recommending all the way back to 2.5 instead of just earlier 2.6 version?

cLogic said:
what kind of things are you referring to when you say that root won't be stable?
what is your device d2 id?
I haven't had any problems with twrp 2.6.3 for d2can
THAT is something I WILL add, for your specific device
any particular reason you're recommending all the way back to 2.5 instead of just earlier 2.6 version?
Click to expand...
Click to collapse
I have D2TMO AKA SGH-T999. Yes this is specific to my variant. I tested all the 2.6.x versions to establish that the /Data Problem exists in all these versions.
As to Root, well, Certain apps such as Nandroid Manager, and other apps have difficulty performing Root operation despite SuperSU granting it. @Aerowinder has a lot of stories. May I suggest you please visit the D2TMO Leaked 4.3 Rom thread in development for more details ?

Perseus71 said:
I have D2TMO AKA SGH-T999. Yes this is specific to my variant. I tested all the 2.6.x versions to establish that the /Data Problem exists in all these versions.
As to Root, well, Certain apps such as Nandroid Manager, and other apps have difficulty performing Root operation despite SuperSU granting it. @Aerowinder has a lot of stories. May I suggest you please visit the D2TMO Leaked 4.3 Rom thread in development for more details ?
Click to expand...
Click to collapse
fair enough ... thanks again for your input ... OP updated

Did this to the letter and soft bricked as soon as I flashed the mod zip in twrp. Stuck on pulsing samsung logo.
Had to reflash. Tried twice just to be sure.
(T999) (root, 4.3 stock)

trepoman said:
Did this to the letter and soft bricked as soon as I flashed the mod zip in twrp. Stuck on pulsing samsung logo.
Had to reflash. Tried twice just to be sure.
(T999) (root, 4.3 stock)
Click to expand...
Click to collapse
what do you mean ... bricked as soon as you flashed mod zip? you mean the knox removal script?
not sure how that's even possible
if you see the pulsing logo, then you rebooted
your T999 is rooted?
meaning it was before, or everything was fine after you did it twice?

cLogic said:
what do you mean ... bricked as soon as you flashed mod zip? you mean the knox removal script?
not sure how that's even possible
if you see the pulsing logo, then you rebooted
your T999 is rooted?
meaning it was before, or everything was fine after you did it twice?
Click to expand...
Click to collapse
The native tether mod. Knox remover worked fine.
Phone is rooted, stock 4.3.
Flashed tether mod in twrp recovery, which succeed but phone would not boot past the pulsing Samsung afterwards (10 minutes of pulsing, never booted past that) nor would it boot to recovery. I could get to boot loader luckily. I pulled the battery and tried again, same thing. Flashed stock 4.3 in Odin to get phone alive, tried flashing tether mod again, exact same result and same solution. HTH.
So close to clicking buy now on a nexus 5...

trepoman said:
The native tether mod. Knox remover worked fine.
Phone is rooted, stock 4.3.
Flashed tether mod in twrp recovery, which succeed but phone would not boot past the pulsing Samsung afterwards (10 minutes of pulsing, never booted past that) nor would it boot to recovery. I could get to boot loader luckily. I pulled the battery and tried again, same thing. Flashed stock 4.3 in Odin to get phone alive, tried flashing tether mod again, exact same result and same solution. HTH.
So close to clicking buy now on a nexus 5...
Click to expand...
Click to collapse
ummm .. not sure what this tether mod is that you are talking about, but it's not part of this guide, lol
this guide simply flashes the knox removal script (to delete knox files) and superSu (to root)

cLogic said:
ummm .. not sure what this tether mod is that you are talking about, but it's not part of this guide, lol
this guide simply flashes the knox removal script (to delete knox files) and superSu (to root)
Click to expand...
Click to collapse
Confounded facts. Always kicking my ass.
This is what happens when I stay up too late and try to do too many things. Linked from another thread and had too many tabs open.
Delete.

Thanks for the post. Sadly, no dice for me. I was directed to this post after creating my own. I've really held off asking for help, but only conclusion I can come to is I got one of those phones that just flat out won't root. Tried everything I can think of. Samsung Galaxy s3, SGH-T999v, 4.3, Wind (Canada). The Odin steps worked, when I boot into recovery, just get the stock android recover menu (original issue I've been having). Nothing seems to work in the slightest.

So I followed this to the letter and it all went well. Except, while the device seems to be rooted, SuperSU seems to be granting permissions to apps, Root Check Pro reports the device is rooted... I still can't use any apps that require root access. GameCIH doesn't work. ROM Manager doesn't work. Nothing wants to work.
Why is this happening? Because every step seemed to go flawlessly. Also, I have no idea how to put it back to stock if I wanted to try and start over lol.
[EDIT]
Oh yeah. Pertinent information. Samsung Galaxy S3 T999V through Mobilicity (Canada) running 4.3.
Used the 2.5 tar rather than the 2.6.
Also set SElinux to permissive.

ksec said:
Thanks for the post. Sadly, no dice for me. I was directed to this post after creating my own. I've really held off asking for help, but only conclusion I can come to is I got one of those phones that just flat out won't root. Tried everything I can think of. Samsung Galaxy s3, SGH-T999v, 4.3, Wind (Canada). The Odin steps worked, when I boot into recovery, just get the stock android recover menu (original issue I've been having). Nothing seems to work in the slightest.
Click to expand...
Click to collapse
are you sure you're running stock 4.3 ? baseband MK5 ?
re-do the Odin steps, except uncheck the auto reboot option .. so that it stops after successfully pushing the recovery tar
unplug the phone from the pc .. it should still be in download mode
pull the battery
then put it back in
boot into recovery immediately
if you see the TWRP recovery, great!, complete the guide and you'll be knox free and rooted
if that worked then there are two files that you seem to still have that are putting stock recovery back on normal boot .. post results here and I'll find them for you

Ergonyx said:
So I followed this to the letter and it all went well. Except, while the device seems to be rooted, SuperSU seems to be granting permissions to apps, Root Check Pro reports the device is rooted... I still can't use any apps that require root access. GameCIH doesn't work. ROM Manager doesn't work. Nothing wants to work.
Why is this happening? Because every step seemed to go flawlessly. Also, I have no idea how to put it back to stock if I wanted to try and start over lol.
[EDIT]
Oh yeah. Pertinent information. Samsung Galaxy S3 T999V through Mobilicity (Canada) running 4.3.
Used the 2.5 tar rather than the 2.6.
Also set SElinux to permissive.
Click to expand...
Click to collapse
did you go into superSu and update it's binary?
what do you mean, exactly, by apps won't work ?
do they run? you said they are being granted permission.
how were they installed?
we're they restored using Titanium?
the 2.5 TWRP was recommended for tmobile users.. we are T999V, can use d2can 2.6.3.0 or d2tmo 2.6.3.1

cLogic said:
did you go into superSu and update it's binary?
what do you mean, exactly, by apps won't work ?
do they run? you said they are being granted permission.
how were they installed?
we're they restored using Titanium?
the 2.5 TWRP was recommended for tmobile users.. we are T999V, can use d2can 2.6.3.0 or d2tmo 2.6.3.1
Click to expand...
Click to collapse
I updated the the SuperSU binary.
The apps will open but when it attempts to do anything requiring root access it is denied or fails.
SuperSU and Knox were installed through the TWRP recovery boot thing as the guide specified. Other things were either installed from the app store or downloaded APK files. I didn't have Titanium at the time I attempted rooting my phone. Wasn't mentioned in the guide so I never got it. I have the basic version now from the play store now. As I'm sure you can tell, I've never rooted my device before. Always had a friend do it for me.
Should I just restore to a stock install (not sure how to do this) and then try again? Especially now that I know the 2.5 warning was specifically for T-Mobile users? Or can I just put the 2.6X version on my phone and try again? lol

it's working
@ cLogic
Thanks a lot man, thanks to you I successfully root my sgh-t999v (stock android 4.3)

I've managed to use GooManager from the Google Play store to install latest TWRP and to flash the 4.3 mod.

Having issues when trying this. I followed all the steps and received no errors. But when the SuperSu ap tries to open on my phone it crashes, the ap only phone is stable.
I have Tomo G3 4.3 Stock rom
Flashed the TW 2.5.0.0 version
Rebooted into the touch recovery
Ran Knox removal
Ran SuperSu
Booted
Knox is not in my list off apps
SuperSu does show
Cant not open supersu, updating binarys does not work since the app crashes.
(Edit)--> Redid the whole process but did not let the phone reboot during the TW flash and the Zip installs. Seemed to of fixed the issue. (Edit)
Thanks added

I flashed Stock 4.3 via Odin before coming across this guide and now my device seems to be stuck at the boot screen. My question is, if I haven't completely booted, can I reflash using the modified version of 4.3 (root, deodexed, knox removed)? Do I have any other options right now?

T999V-Wind Mobile-TWRP problem

I've tried 2.7.1 and 2.7.0 of TWRP for both Tmo and the Canada version they have, they all install fine, but when I try and do anything, it can't mount any partitions, so I can't wipe or install anything. I am rooted with the root66 of the latest Wind firmware.
Any other wind users know a good working TWRP ?

getochkn said:
I've tried 2.7.1 and 2.7.0 of TWRP for both Tmo and the Canada version they have, they all install fine, but when I try and do anything, it can't mount any partitions, so I can't wipe or install anything. I am rooted with the root66 of the latest Wind firmware.
Any other wind users know a good working TWRP ?
Click to expand...
Click to collapse
Are you running a custom rom and/or kernel? Im wondering if this may have something to do with selinux. If not using one already, try flashing an insecure custom kernel. You might also want to try flashing CWM, just to see if it has the same issue.

DocHoliday77 said:
Are you running a custom rom and/or kernel? Im wondering if this may have something to do with selinux. If not using one already, try flashing an insecure custom kernel. You might also want to try flashing CWM, just to see if it has the same issue.
Click to expand...
Click to collapse
Thanks for the reply.
I'm not sure, I'm only running stock+root from the root66 package for the MK5 ROM for my phone from Wind in Canada. I tried installing CWM and it ran the first time, tried clearing cache to see if it had any permission/mount errors, and it froze, pulled the battery and wouldn't boot anymore. Had to reflash root66 package to get my phone to even boot. Rootchecker says I'm rooted fine, SU gives permissions to everything fine, busybox is fine. Donwload mode shows security bit disabled, so the root66 disabled knox. Not sure what to do try next.
EDIT
Installed CWM from ROM-Manager, and it worked, installed liewise ROM and it's working fine. I unno. lol.

getochkn said:
Thanks for the reply.
I'm not sure, I'm only running stock+root from the root66 package for the MK5 ROM for my phone from Wind in Canada. I tried installing CWM and it ran the first time, tried clearing cache to see if it had any permission/mount errors, and it froze, pulled the battery and wouldn't boot anymore. Had to reflash root66 package to get my phone to even boot. Rootchecker says I'm rooted fine, SU gives permissions to everything fine, busybox is fine. Donwload mode shows security bit disabled, so the root66 disabled knox. Not sure what to do try next.
EDIT
Installed CWM from ROM-Manager, and it worked, installed liewise ROM and it's working fine. I unno. lol.
Click to expand...
Click to collapse
Sorry that caused you so much trouble. When you are booted into recovery though, whether or not the rom is rooted makes no difference. What is important here is if the kernel is secure or insecure. I am still fairly certain selinux was causing you your problems with mounting though. If you are running any rom based on my Sprint ND8 port (such as likewise), you shouldn't have anymore problems (if I am correct about it being selinux of course). The kernel included has selinux disabled. Glad you got it working though.
Just curious, what do you mean by download mode shows security bit disabled? I think you might mean selinux? The warranty bit, which is often referred to as the knox counter cannot be disabled and is actually separate from Knox itself. Removing knox is something done only in the rom, not the kernel, and has no effect on what is shown in download mode. Also, selinux is not knox, they are two different technologies. Just fyi for future reference.

getochkn said:
I've tried 2.7.1 and 2.7.0 of TWRP for both Tmo and the Canada version they have, they all install fine, but when I try and do anything, it can't mount any partitions, so I can't wipe or install anything. I am rooted with the root66 of the latest Wind firmware.
Any other wind users know a good working TWRP ?
Click to expand...
Click to collapse
how i did my wind s3 is
Unified_Android_Toolkit_v1.2.8 seemed to work for me

DocHoliday77 said:
Sorry that caused you so much trouble. When you are booted into recovery though, whether or not the rom is rooted makes no difference. What is important here is if the kernel is secure or insecure. I am still fairly certain selinux was causing you your problems with mounting though. If you are running any rom based on my Sprint ND8 port (such as likewise), you shouldn't have anymore problems (if I am correct about it being selinux of course). The kernel included has selinux disabled. Glad you got it working though.
Just curious, what do you mean by download mode shows security bit disabled? I think you might mean selinux? The warranty bit, which is often referred to as the knox counter cannot be disabled and is actually separate from Knox itself. Removing knox is something done only in the rom, not the kernel, and has no effect on what is shown in download mode. Also, selinux is not knox, they are two different technologies. Just fyi for future reference.
Click to expand...
Click to collapse
Ah. Maybe I was looking at the QualcomSecureboot or something
Either way, all is good. Not sure why TWRP gave problems or CWM did via Odin. I'm using likewise rom, which is based off your sprint so shouldn't have any more problems now anyways. Not a stranger to flashing Samsung phones, just my first newer samsung flash with this whole knox/selinus thing and all that. My old sammy S 4G was flashed hundreds of times while I worked on ROMs'. lol.

Rickyfk said:
how i did my wind s3 is
Unified_Android_Toolkit_v1.2.8 seemed to work for me
Click to expand...
Click to collapse
Be careful with that! I always advise against using it because it is very rarely updated, the op does not provide any support for it, and it has bricked several devices.

yes i forgot that in my post i always back ups of everything before i do anything.
i have also fixed bricked devices befor also but ya you have to be carful tho.
DocHoliday77 said:
Be careful with that! I always advise against using it because it is very rarely updated, the op does not provide any support for it, and it has bricked several devices.
Click to expand...
Click to collapse

i have the same problem
getochkn said:
I've tried 2.7.1 and 2.7.0 of TWRP for both Tmo and the Canada version they have, they all install fine, but when I try and do anything, it can't mount any partitions, so I can't wipe or install anything. I am rooted with the root66 of the latest Wind firmware.
Any other wind users know a good working TWRP ?
Click to expand...
Click to collapse
my phone is wind T999V, rom is original JB 4.3.
i use root66 rom. i want to downgrade, i want to use twrp to copy system, but , all is no no no , sad.:crying:

welcome2you said:
my phone is wind T999V, rom is original JB 4.3.
i use root66 rom. i want to downgrade, i want to use twrp to copy system, but , all is no no no , sad.:crying:
Click to expand...
Click to collapse
Not sure what you mean there, sorry. But you cannot downgrade your firmware, but you can flash an older rom from TWRP.

DocHoliday77 said:
Not sure what you mean there, sorry. But you cannot downgrade your firmware, but you can flash an older rom from TWRP.
Click to expand...
Click to collapse
i want to use twrp,but cannot find partition, i want to downgrade to 4.1 ,then i can unlock my phone , but i have no way to finish it.

welcome2you said:
i want to use twrp,but cannot find partition, i want to downgrade to 4.1 ,then i can unlock my phone , but i have no way to finish it.
Click to expand...
Click to collapse
How are you trying to install TWRP? There are several ways to do so. Odin, recovery, Goo.Im app..... You can get the twrp files from my sig if you want to try those. No guarantee you will be able to unlock when flashing the 4.1.1 modem, let us know if it works for you.

I had tried TWRP through Odin flashable and also Goo Manager. I tried 2.7.0 and 2.7.1, both Tmo and Can version, and none could mount anything . CWM through Rom Manager works great though.
I know, from my experience working on ROM's and getting the first Heimdall flashable package to upgrade the Galaxy S 4G from Wind, that the Wind models of phones are slightly different than the Tmo versions. It took me a dev a while to find the right files, lots of soft bricking ,etc, to figure out the minute difference to allow Heimdall to flash a package, and even then, Heimdall could never flash a modem to the 4G-Wind Variant. I even tried working with the Heimdall dev to find out why, and never could. Modems would flash from CWM or TWRP, but not from the PC, even though Tmo firmwares and ROM's worked, so maybe the Wind phone is slightly different in partition layout that CWM can adapt for, but TWRP can't. Maybe I'll contact the TWRP team and see if I can help them figure out why, although now I'm working a lot more than I was and don't have a lot of time to flash my phone 100 times and brick it and flash again like in the older days.

getochkn said:
I had tried TWRP through Odin flashable and also Goo Manager. I tried 2.7.0 and 2.7.1, both Tmo and Can version, and none could mount anything . CWM through Rom Manager works great though.
I know, from my experience working on ROM's and getting the first Heimdall flashable package to upgrade the Galaxy S 4G from Wind, that the Wind models of phones are slightly different than the Tmo versions. It took me a dev a while to find the right files, lots of soft bricking ,etc, to figure out the minute difference to allow Heimdall to flash a package, and even then, Heimdall could never flash a modem to the 4G-Wind Variant. I even tried working with the Heimdall dev to find out why, and never could. Modems would flash from CWM or TWRP, but not from the PC, even though Tmo firmwares and ROM's worked, so maybe the Wind phone is slightly different in partition layout that CWM can adapt for, but TWRP can't. Maybe I'll contact the TWRP team and see if I can help them figure out why, although now I'm working a lot more than I was and don't have a lot of time to flash my phone 100 times and brick it and flash again like in the older days.
Click to expand...
Click to collapse
As far as partition layout goes, all of the T999 and I747 variants are the same. I believe the Sprint and Verizon ones are as well, but am not 100% confident in that. You said you tried the d2can and d2tmo versions, but what about d2lte? Everyone should be just using d2lte now as ALL the S3 models have been consolidated into that one. Where did you download it from btw? You can get it from the link in my sig. I know for sure it works. (I think I still need to add 2.7.0.1 though. But 2.7.0.0 is there.)

DocHoliday77 said:
As far as partition layout goes, all of the T999 and I747 variants are the same. I believe the Sprint and Verizon ones are as well, but am not 100% confident in that. You said you tried the d2can and d2tmo versions, but what about d2lte? Everyone should be just using d2lte now as ALL the S3 models have been consolidated into that one. Where did you download it from btw? You can get it from the link in my sig. I know for sure it works. (I think I still need to add 2.7.0.1 though. But 2.7.0.0 is there.)
Click to expand...
Click to collapse
I looked in your sig but don't see a D2LTE TWRP, only the 2.7.0 TMO one, which I downloaded from the official TWRP site, as well as 2.7.1 and neither worked. I also tried installing from Goo Manager. Maybe I'll try yours since it is a CWM flashable zip as opposed to an odin tarball and I have CWM working

getochkn said:
I looked in your sig but don't see a D2LTE TWRP, only the 2.7.0 TMO one, which I downloaded from the official TWRP site, as well as 2.7.1 and neither worked. I also tried installing from Goo Manager. Maybe I'll try yours since it is a CWM flashable zip as opposed to an odin tarball and I have CWM working
Click to expand...
Click to collapse
Ill have to double check that later. Been a while since I've flashed recovery. I know I am using the one in my repo though, so it should work fine whether its d2tmo or d2lte

Trying to ROOT. Freekin KNOX (Warranty void: 1 ) Help!

I have a Samsung Galaxy s6 on Sprint, running Android 5.1.1 and build OFE.
I've successfully rooted before but i'm still a noob in training lol
What I have done:
Developer options: Enabled / turned on USB debugging / unlocked autoloader
Used:
dot tech dot org / how-to-root-all-galaxy-s6-models-and-install-twrp-recovery-guide
(using all the files from the link)
FOLLOWED TO THE LETTER
I left odin on autoreboot, maybe that was the problem.
I saw in the 1st video that you should hold down the volume up/power/home immediately after hitting start in ODIN.
This was my second attempt, KNOX was already reading 1 warranty void and 0 x 0304 or something.
I read that if you get to 0 x 1 it bricks your phone so that you can't save it yourself. not sure if that's true.
I'm afraid to go further because I don't want to have a knox brick which I don't think I can recover from.
I would have to go to sprint and deal with those buttholes and I'm a national truck driver. I have no time for that.
Is there a way to kill knox? for good!?
I'm thinking of using ping pong root, any thoughts?

Ping Pong Root does not work on 5.1.1, so that won't help.
There is an excellent guide with links located here: http://forum.xda-developers.com/sprint-galaxy-s6/general/how-to-to-100-stock-root-t3075448
Since you are already on 5.1.1, you can skip to step two. Flash a kernel to enable root through ODIN, then flash TWRP and you are good to go.

koop1955 said:
Ping Pong Root does not work on 5.1.1, so that won't help.
There is an excellent guide with links located here: http://forum.xda-developers.com/sprint-galaxy-s6/general/how-to-to-100-stock-root-t3075448
Since you are already on 5.1.1, you can skip to step two. Flash a kernel to enable root through ODIN, then flash TWRP and you are good to go.
Click to expand...
Click to collapse
One more thing if you can help? I want to install xtrestolite deodexed mod edition 1.2 after flashing the kernel and twrp recovery. Is this compatible? Thanks

"Kernel is not seandroid enforcing". It got stuck for about 20 minutes there telling me to hook up to smartswitch but I reflashed the kernel and it restarted. wheeew!!! So why is this kernel not flashing properly? What is this warning message? PLEASE HELP GUYS!!!

djscottallen said:
"Kernel is not seandroid enforcing". It got stuck for about 20 minutes there telling me to hook up to smartswitch but I reflashed the kernel and it restarted. wheeew!!! So why is this kernel not flashing properly? What is this warning message? PLEASE HELP GUYS!!!
Click to expand...
Click to collapse
Warning message is normal. Nothing to worry about there.

djscottallen said:
One more thing if you can help? I want to install xtrestolite deodexed mod edition 1.2 after flashing the kernel and twrp recovery. Is this compatible? Thanks
Click to expand...
Click to collapse
Nope, that ROM doesn't support the G920P.
I am running the Twisted Project ROM (http://forum.xda-developers.com/sprint-galaxy-s6/development/rom-twisted-project-6-v1-7-17-t3159117) which I recommend if you like a minimal approach.
The other "hot" ROM for our phones is the Ramified ROM (found here: http://forum.xda-developers.com/spr...ment/ram9200-ofe-rom-thread-v3-5-1-1-t3173417) which is also excellent. Be sure to follow directions and flash the recommended kernel after flashing the ROM. (Set TWRP to flash ROM, flash kernel and reboot.)
Just to educate you a bit, the Twisted Project ROM was written for our phones, so that you don't need to flash a kernel after. Of course, you can if you want to.
The Ramified ROM was written for the Edge. Flashing a kernel (this is the recommended one: http://forum.xda-developers.com/sprint-galaxy-s6/development/kernel-unikernel-v5-t3166295) is needed to make it work correctly.
Have fun, dude!

koop1955 said:
Nope, that ROM doesn't support the G920P.
I am running the Twisted Project ROM (http://forum.xda-developers.com/sprint-galaxy-s6/development/rom-twisted-project-6-v1-7-17-t3159117) which I recommend if you like a minimal approach.
The other "hot" ROM for our phones is the Ramified ROM (found here: http://forum.xda-developers.com/spr...ment/ram9200-ofe-rom-thread-v3-5-1-1-t3173417) which is also excellent. Be sure to follow directions and flash the recommended kernel after flashing the ROM. (Set TWRP to flash ROM, flash kernel and reboot.)
Just to educate you a bit, the Twisted Project ROM was written for our phones, so that you don't need to flash a kernel after. Of course, you can if you want to.
The Ramified ROM was written for the Edge. Flashing a kernel (this is the recommended one: http://forum.xda-developers.com/sprint-galaxy-s6/development/kernel-unikernel-v5-t3166295) is needed to make it work correctly.
Have fun, dude!
Click to expand...
Click to collapse
I think that's why I'm running into problems? I'm trying to get native hotspot to work on twisted ROM and it's not working. I flashed a custom kernel first, then rooted, then flashed the twisted ROM, in that order. Any suggestions?

Sorry, I found my answer and can't delete my post! So... sorry for bumping this thread.

Want to root Friends Note 4, a few questions.

Hello,
I want to root my friends sprint note 4 (lolipop i believe). I was looking at this guide http://galaxynote4root.com/galaxy-note-4-root/how-to-root-galaxy-note-4note-edge-on-android-5-1-1/ and it seems straightforward. A little different than what I had to do with my phone becuase I had to unlock the bootloader and then flash the recovery and supersu. (I've never used odin) Does this mean the bootloader is already unlocked by default since all I have to do is install the recovery and then the kernel?
I'm a little confused, once I get the recovery, can I flash roms to it? Do I have to change the kernel again if I want to install a ROM? I don't plan on putting a custom ROM on his phone but I want reflash the stock rom or a debloated stock rom because he said even after a factory reset it was buggy (if you can link me to a proper stock rom that supports xposed I would be grateful).
And I also want xposed to work, is there a specific xposed version I should install?
And also, if I do flash something, is this method correct?
Backup data
factory reset
flash
clear cache
restore data
reboot
or do I restore the data later?

The thread and video are dated. A few key elementary facts are still relevant but as a whole, just not up to date. I wouldn't trust it and it lends to repeated help threads in this forum. If one read the OPs and threads of current ROMs in development and recent help threads, maybe less questions and help would be needed.
He omits current ROMs, didn't mention where the reactivation lock is for TW Android ROMs: Settings/Security/Reactivation lock (should be disabled). He doesn't mention Chainfire Auto root for Note 4 has been updated for 5.1 and will be key again for marshmallow (but that's only needed for rooting stock Odex). He also didn't tell you how to get to those old ROMs on his site. Some think you just Odin an old update but not so. That requires a 5.1 kernel matched with current bootloader rather than Odin downgrade.
The bootloader, while not locked to block root, is considered unlocked but actually is now security locked to block older security stock tars with lower security bootloaders. It's actually unknown until confirmed what tar you can downgrade to. It won't be KitKat or OB7 and some just after that. From OK1 update, I'm only aware that you can downgrade from OK1 to OJ6 and if you flash the MM leaked tar, you can still downgrade to OK1.
Kernels should be kept in zip form because backing up a kernel in TWRP doesn't backup /system/lib/modules to restore and some custom kernels modify or add modules which may not work restored boot.img And restoring stock kernel on a rooted phone would cause a boot loop. So to restore that, you'd need to full un-root in SuperSU to avoid the boot loop there as well as restore the stock /system/lib/modules.
Root methods: unless you're using the full un-root or wiping everything but extSdCard (particularly user data and internal memory), you don't fully remove systemless root. Flashing a ROM or SuperSU with system based SuperSU over systemless root without the wipes would break things like root. Not seeing the SuperSU app or loss of ability to add new apps to superuser would be impacted but also a boot loop is possible if but patching stock kernel su.img to boot.
The basic principal is that to flash the custom deodexed ROM you need for Xposed, just make sure you're on the right update, Odin TWRP and follow the OP closely. If wiping internal memory is suggested by OP, I'd suggest that. To keep things simple, I backup and wipe everything but extSdCard for ports or where Xposed or systemless SuperSU is used. I typically do the same for stock tar updates as well.
As to recommended ROMs, I'd suggest any deodexed OK1 ROM for Xposed. tx_dbs_tx has a variety of OK1 ROMs. Freeza has one with Xposed integrated with Xposed modules in system. If Note 5 Moar port is a good fit, I'd recommend trying without Xposed until you determine the minimum of Xposed mods you're lacking so you're not overlapping features and you're getting to know the stability of it, first.
Rooting a friend's phone? IMO, you should be very sure and confident before proceeding and advise rather than do all the work and take the risks yourself. Use the correct USB driver, not just one that works. Setup his computer to root and sustain that phone.
Sent from my SM-N910P using Tapatalk

How is it dated exactly? I thought 5.1 is highest OTA for Note 4? Do OTA security patches change how things work now? I wouldn't know about security patches since I have a moto x 2013, we are left in the dust.
This is the ROM I am looking at http://forum.xda-developers.com/note-4-sprint/development/rom-t3271966
I'm still a little confused about the bootloader, right now my friend is on Sprint 5.1 lolipop. Is there a way to check the bootloader version? Can I not use Odin to install TWRP? And I'm not sure about the modem/kernel stuff, I didn't have to deal with it on my 2013 moto x. The website links to these kernels https://www.mediafire.com/folder/naq9dih44fndv/SM-N915P. Can I flash the latest kernel that was uploaded in January? The ROM contains root so I know I'm not supposed to flash superSU by itself, also obviously not to take any OTA's. I know that I'm supposed to install the wanam version of xposed that is optimized for samsung phones.

rapiollymega said:
How is it dated exactly? I thought 5.1 is highest OTA for Note 4?
Click to expand...
Click to collapse
I answered that in detail.
rapiollymega said:
Do OTA security patches change how things work now?
Click to expand...
Click to collapse
No; it's the bootloader and updates that did that.
rapiollymega said:
This is the ROM I am looking at http://forum.xda-developers.com/note-4-sprint/development/rom-t3271966
Click to expand...
Click to collapse
Good choice.
rapiollymega said:
I'm still a little confused about the bootloader, right now my friend is on Sprint 5.1 lolipop. Is there a way to check the bootloader version?
Click to expand...
Click to collapse
Answered. Use Phone Info from Google Play or Galaxy Tools.
rapiollymega said:
Can I not use Odin to install TWRP? And I'm not sure about the modem/kernel stuff, I didn't have to deal with it on my 2013 moto x. The website links to these kernels https://www.mediafire.com/folder/naq9dih44fndv/SM-N915P. Can I flash the latest kernel that was uploaded in January? The ROM contains root so I know I'm not supposed to flash superSU by itself, also obviously not to take any OTA's. I know that I'm supposed to install the wanam version of xposed that is optimized for samsung phones.
Click to expand...
Click to collapse
Answered. Make sure you're updated, use Odin to flash TWRP and follow OP closely. I wouldn't concern myself with the kernels listed outside this forum. SuperSU and kernel are in those ROMs; they're pre-rooted. If you want an updated kernel, I'd recommend freeza Beastmode kernel from this forum.
Edit: don't use a Galaxy Edge ROM, kernel or recovery on a Note 4 or vice versa. To be clear, this is the Sprint Note 4 forum. SM-N910P not SM-N915P.
Edit 2: When flashing TWRP, verify the reactivation lock is unchecked in Settings/Security. Use latest Odin, uncheck only the auto reboot option. Once it flashes and you confirm 0 failed, pull USB and battery for 30 seconds. Reinstall battery and be sure to reboot directly into recovery. Skip steps and it may not stick.
Sent from my SM-N910P using Tapatalk

samep said:
Answered. Make sure you're updated, use Odin to flash TWRP and follow OP closely. I wouldn't concern myself with the kernels listed outside this forum. SuperSU and kernel are in those ROMs; they're pre-rooted. If you want an updated kernel, I'd recommend freeza Beastmode kernel from this forum.
Edit: don't use a Galaxy Edge ROM, kernel or recovery on a Note 4 or vice versa. To be clear, this is the Sprint Note 4 forum. SM-N910P not SM-N915P.
Edit 2: When flashing TWRP, verify the reactivation lock is unchecked in Settings/Security. Use latest Odin, uncheck only the auto reboot option. Once it flashes and you confirm 0 failed, pull USB and battery for 30 seconds. Reinstall battery and be sure to reboot directly into recovery. Skip steps and it may not stick.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Sorry if I'm not understanding some of your post since I'm not that experienced with android or the post is kind of worded ambiguously. For TWRP, should I use 3.0 or 2.8.7?
is now security locked to block older security stock tars with lower security bootloaders. It's actually unknown until confirmed what tar you can downgrade to. It won't be KitKat or OB7 and some just after that. From OK1 update, I'm only aware that you can downgrade from OK1 to OJ6 and if you flash the MM leaked tar, you can still downgrade to OK1.
Click to expand...
Click to collapse
I'm not sure what you mean here. Looking at youtube videos, people just flash TWRP with Odin. Should I just try to put TWRP in? I understand the part about either removing the battery or trying to instant go into recovery.
So the ROM I'm looking at already has a kernel? So all I need to do it flash the zip? And then install xposed? Is it recommended to restore data or should I boot first once and then restore data. Also on a side question: For data restoring, is there a way to only specifically restore apps from a data backup? Thanks for the help.

rapiollymega said:
Sorry if I'm not understanding some of your post since I'm not that experienced with android or the post is kind of worded ambiguously. For TWRP, should I use 3.0 or 2.8.7?
I'm not sure what you mean here. Looking at youtube videos, people just flash TWRP with Odin. Should I just try to put TWRP in? I understand the part about either removing the battery or trying to instant go into recovery.
So the ROM I'm looking at already has a kernel? So all I need to do it flash the zip? And then install xposed? Is it recommended to restore data or should I boot first once and then restore data. Also on a side question: For data restoring, is there a way to only specifically restore apps from a data backup? Thanks for the help.
Click to expand...
Click to collapse
It's the INTERNET that's ambiguous towards Touchwiz Android 5.1 There has been a few updates and each changed the way we do things. So when you say you're on Android 5.1, I say you need to be on the latest 5.1 update to have the greatest compatibility with the ROM you're choosing to flash.
Yes. You use Odin to install TWRP when rooting from full stock un-root to custom pre-rooted ROM. Perhaps my direction to Odin TWRP was ambiguous? Flash this in Odin AP slot with auto reboot unchecked- use the other option defaults from latest Odin:
https://dl.twrp.me/trltespr/twrp-3.0.0-0-trltespr.img.tar.html
http://forum.xda-developers.com/showpost.php?p=51767811&postcount=1
I would restore data after installing Xposed. Keep in mind that these installation boots of custom ROM and Xposed take time. The less apps and data, the shorter the boot times will be. Plus the ROM will have more time to stabilize. After you've verified the last three of the bootloader and modem matches OK1, you can proceed with TWRP, then install ROM per the 1st post and immediate posts from OP. When you get to the Wi-Fi connection in setup wizard, make sure you have radio signal before connecting Wi-Fi. Make sure everything is stable and functional before Xposed installation.
Again, about the long boot times on installation. Best to keep case off the phone and ventilate phone with not too cool or ambient air. This will speed the process and possibly prevent component failure.
When your ready for Xposed, you need the Wanam unofficial Xposed framework.
http://forum.xda-developers.com/showpost.php?p=62377731&postcount=1
You'll need sdk22 arm for Lollipop, not 64 bit Exynos or MM.
Currently it's the one labeled: xposed-v80.0-sdk22-arm-custom-build-by-wanam-20160211.zip
Grab the uninstaller too, just in case. You shouldn't need it but be prepared.
Edit: be sure to get the deodexed version of that ROM. Makes things easier for Xposed and Xposed compatibility when adding system applications, if that applies to anytime later.
Sent from my SM-N910P using Tapatalk

Thanks for all the help, did it over the weekend and everything went smoothly. Well except for one part before installing the new ROM, I deleted everything in data/system and forgot that the zip was In the internal storage instead of the sd card . And for whatever reason the PC usb connection wasn't working in TWRP so I had to use a flash drive and otg cable to put the zip ROM back in the phone.