Database Users

Revert to stock and root without reboots.

Hello, I have had a few people ask about how I reverted back to stock and managed to root without having reboots so here is an outline including links.
First you will need to use ODIN to go back to the original stock firmware.
Stock Odin for P907A can found here: http://forum.xda-developers.com/galaxy-note-pro-12/general/sm-p907a-att-version-news-t2850564/page1
Stock ODIN for the P900 can be found here: http://forum.xda-developers.com/showthread.php?t=2724895
For those who don't know how to use ODIN, here is a nce guide for you: http://androidcentral.us/2014/02/how-to-flash-firmware-using-odin-samsung-devices/
Now the next thing you need to do is root using TowelRoot, but DO NOT install SuperSU yet! After rooting use the debloat script in this thread (You run it from your device using terminal, I used the terminal function in ROM Toolbox): http://forum.xda-developers.com/showthread.php?t=2797540
I only used the option to disable KNOX and the updater along with the option to disable the startup sound.
Once you have successfully done those things, you may now install SuperSU. It will no longer ask you about KNOX, because it is properly disabled and will not cause you any reboots. My Note Pro has been rock solid stable and lightning fast after doing this.
NOTE: You will not be able to update to new firmwares after this.
Thanks to:
najoor
torreon91
Please make sure you hit thanks in these guys' threads for their hard work!
EDIT: If Jellybean comes out for our tablet I would not update unless the trade off was worth it to you. Or obviously if an exploit for the jellybean update were found then you would want to. If you did want to update, you could re-enable the updater by using the enbloat script that was with the debloat script.

Thank you for your help. Now I will be able to use my tablet more frequently

dragunbayne said:
Hello, I have had a few people ask about how I reverted back to stock and managed to root without having reboots so here is an outline including links.
First you will need to use ODIN to go back to the original stock firmware.
Odin for P907A can found here: http://forum.xda-developers.com/galaxy-note-pro-12/general/sm-p907a-att-version-news-t2850564/page1
For those who don't know how to use ODIN, here is a nce guide for you: http://androidcentral.us/2014/02/how-to-flash-firmware-using-odin-samsung-devices/
Now the next thing you need to do is root using TowelRoot, but DO NOT install SuperSU yet! After rooting use the debloat script in this thread (You run it from your device using terminal, I used the terminal function in ROM Toolbox): http://forum.xda-developers.com/showthread.php?t=2797540
I only used the option to disable KNOX and the updater along with the option to disable the startup sound.
Once you have successfully done those things, you may now install SuperSU. It will no longer ask you about KNOX, because it is properly disabled and will not cause you any reboots. My Note Pro has been rock solid stable and lightning fast after doing this.
NOTE: You will not be able to update to new firmwares after this.
Thanks to:
najoor
torreon91
Please make sure you hit thanks in these guys' threads for their hard work!
Click to expand...
Click to collapse
EDIT: If Jellybean comes out for our tablet I would not update unless the trade off was worth it to you. Or obviously if an exploit for the jellybean update were found then you would want to. If you did want to update, you could re-enable the updater by using the enbloat script that was with the debloat script.

dragunbayne said:
Hello, I have had a few people ask about how I reverted back to stock and managed to root without having reboots so here is an outline including links.
First you will need to use ODIN to go back to the original stock firmware.
Odin for P907A can found here: http://forum.xda-developers.com/galaxy-note-pro-12/general/sm-p907a-att-version-news-t2850564/page1
For those who don't know how to use ODIN, here is a nce guide for you: http://androidcentral.us/2014/02/how-to-flash-firmware-using-odin-samsung-devices/
Now the next thing you need to do is root using TowelRoot, but DO NOT install SuperSU yet! After rooting use the debloat script in this thread (You run it from your device using terminal, I used the terminal function in ROM Toolbox): http://forum.xda-developers.com/showthread.php?t=2797540
I only used the option to disable KNOX and the updater along with the option to disable the startup sound.
Once you have successfully done those things, you may now install SuperSU. It will no longer ask you about KNOX, because it is properly disabled and will not cause you any reboots. My Note Pro has been rock solid stable and lightning fast after doing this.
NOTE: You will not be able to update to new firmwares after this.
Thanks to:
najoor
torreon91
Please make sure you hit thanks in these guys' threads for their hard work!
EDIT: If Jellybean comes out for our tablet I would not update unless the trade off was worth it to you. Or obviously if an exploit for the jellybean update were found then you would want to. If you did want to update, you could re-enable the updater by using the enbloat script that was with the debloat script.
Click to expand...
Click to collapse
Is there a way to do this, but for the SMP-900 version the first link with the odin files state that they are only for the SM-P907 version? I have reverted back to stock but my tablet reboots qute often and with school starting it would be great to avoid that while taking notes. Thanks!

acaldrn2 said:
Is there a way to do this, but for the SMP-900 version the first link with the odin files state that they are only for the SM-P907 version? I have reverted back to stock but my tablet reboots qute often and with school starting it would be great to avoid that while taking notes. Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2724895
I will add it to the main post also.

5.1.1 [DOK2] Setup [Debloated & Systemless Root] [Viper4Android][Bettery Battery]

5.1.1 [DOK2] Setup [Debloated & Systemless Root] [Viper4Android][Bettery Battery]
I have seen a few people having issues with the DOK2 update and were looking for a step by step process of how to upgrade to the new firmware and optimize it to get goo performance. this thread will guide you through that process as well as link to the appropriate threads to download and get the needed files/add ons.
*****This process will wipe your phones internal storage and give you a clean install of the new firmware.
Step 1: Download the DOK2 firmware to your PC
There are a few places you can get this from:
Sammobile: N910T Firmware
Or XDA thread: Stock TW Firmware/Bootloader/Modem N910TUVU2DOK2 UNMODIFIED Mirror
(You will need the entire firmware not just the modem and baseband)
Step 2: Download ODIN to you computer
From ODIN DOWNLOAD: ODIN 3.10.7
Step 3: Odin Flash new firmware.
The download from Sammobile or Mega should be a .zip file. you will need to unzip that file to find the .tar file which is what you will use for ODIN flashing the firmware.
If you need help using Odin to flash the firmware check out this post on Android Central: Help Thread
After you have completed the Odin Flash the phone should reboot and come to the setup screen with your new firmware.
Step 4: Odin Flash TWRP
Download TWRP to your computer: TWRP Downloads
Specifically you want this file: twrp-2.8.7.0-trltetmo.img.tar
Use Odin to flash TWRP recovery onto your device.
If you get lost you can check this tutorial: ODIN Help
Step 5: Reboot your device and setup
Once you have rebooted go ahead and set up your device. we will worry abou debloating and getting root after your device is setup.
Step 6: make a backup in TWRP
Once your device is setup make a TWRP backup of your setting
Step 7: Getting Root
*****Update: New SuperSu 2.64 beta. Works even better with Samsung phones. *******
You will need the latest SuperSU beta from the below thread.
SuperSU Beta Systemless Root
Newest version is 2.64
You will then boot into TWRP and flash that zip in recovery. This will give you "Systemless Root"
Systemless root allows you to use the stock kernel with SE LINUX enforcing, but still be able to use root apps. However this is not complete root. Some root apps that need to modify the system will not work. this is just a BETA root and is not final yet. check back to that thread for updates as they come out.
Once you have flashed the SuperSU zip reboot your device and verify your root apps are working.
Step 8: DeBloating TW.
There are 2 options for debloating TW.
Option #1: V3.90 Debloater V3.90 DeBloater
This option works on both rooted and unrooted devices. It really is a program that uases ADB to allow you to FREEZE system apps. This will not allow you to completely delete the application with Systemless Root.
The OP has a TON of detail and walks through this process of how to uses his program.
Option #2: [Script]Touchwiz De-Bloating Script and Gapps ~ 222 Apps
http://forum.xda-developers.com/not...pt-touchwiz-bloating-script-222-apps-t3258537
This Option removes 222 applications. It is a simple download and flash in recovery process.
****HOWEVER This will remove some functionality of the device READ the list of application before you flash to make sure there are not any that you use. The OP also has instructions on how to modify the script if you want some application to not be removed.
Step 9 Viper4Android on Systemless root.
Download the Viper4 Andriod/Beat installer
Viper4Android w/ Beat Audio
Flash the installer zip in TWRP and reboot your device
Download BusyBox Installer
BusyBox by Stephen (Stericson)
Install BusyBox
Reboot
install Viper$Android Drivers
Reboot
Download both the Viper4Android SU policy fixes
1.) ViPER4Android-supolicy.zip
2.) XM_V4A_Fix_by_androidexpert35.zip
Reboot into TWRP and flahs both of these. you can flash them at the same time just to them in the order above. [1 then 2]
Reboot the device and enjoy V4a.
******Also the Beat portion of the zip is a bit wonky sometimes. I have not yet been able to get it to opperate effectively, so you may want to disable it or freeze it with Titanium backup.
Disclaimer: NONE of these zips are mine. I am posting download links from my mega, because I pulled these files from 3 different threads and only one was from an OP. the main Viper4Android /beats install zip comes from here : [SUPER MOD][4.3+/6.0][ v6.2 ] XTREMEMusic™ THE SOUND THAT YOU'VE NEVER HEARD!
*************************************************************************************************************************************************************************
With this setup I have easily gotten more than a days worth of usage. I average about 5.5 hours of SOT and 24 hrs between charges. Normally I plug in around 20 hours with about 40% battery left.
*****These are all items developed by other XDA USERS. Please provide the thanks on their respective threads as well.

Thanks for taking the time for this write up. I don't have much experience with the new systemless root. I was wondering since the steps you mentioned above doesn't require any pre-rooted steps if there is any way of getting root without triggering Knox. I know in the past you can do this with Android 4.x, however since I'm currently on the latest boatloader there is no going back. I understand many don't care about Knox, but since my replacement and having Knox intact, I'd thought it might be worth my while since systemless root seems to be the future for new Android releases. Also I've been running stock for the last few months and the experience has been pretty good, though I miss some of the conveniences of having root.

James62370 said:
Thanks for taking the time for this write up. I don't have much experience with the new systemless root. I was wondering since the steps you mentioned above doesn't require any pre-rooted steps if there is anyway off getting root without triggering Knox. I know in the past you can do this with Android 4.x, however since I'm currently on the latest boatloader there is no going back. I understand many don't care about Knox, but since my replacement and having Knox intact, I'd thought it might be worth my while since systemless root seems to be the future for new Android releases. Also I've been running stock for the last few months and the experience has been pretty good, though I miss some of the conveniences of having root.
Click to expand...
Click to collapse
This method is for root only. It requires installing TWRP which is a custom recovery. That means you will have to unlock the bootloader to be able to use this method. Once you unlock the bootloader (by Odin flashing TWRP) you have already tripped Knox. Knox is no big deal from what I have heard though. I have not heard of anyone getting denied a new phone because it was tripped.
The two main reasons to use this method are:
1.) It keeps the system intact, which allows you to use apps that check for root. (eg. Android Pay, Some Bank Apps etc)
2.) It allows you to use the stock kernel from 5.1.1. Currently the only way to get root on 5.1.1 and up is to install a custom kernel. Which is fine, and there are two really great option available with Emotion and Beast Mode, but I find the stock kernel gets me the best battery life and is the most stable.
ALSO this will be the way root is done going forward. 6.0.1 has a bunch of system file locks that prevent much of the system tinkering from happening. Chainfire (dev who built SuperSU) has a nice right up about the system partition on XDA right now explaining why some of the system tweaks we were used to will not be possible in the future. so at the very least this is good practice for getting ready for the Marshmallow update.

ShrekOpher said:
Step 8: DeBloating TW.
There are 2 options for debloating TW.
Option #1: V3.90 Debloater [http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294]
This option works on both rooted and unrooted devices. It really is a program that uases ADB to allow you to FREEZE system apps. This will not allow you to completely delete the application with Systemless Root.
The OP has a TON of detail and walks through this process of how to uses his program.
Option #2: [Script]Touchwiz De-Bloating Script and Gapps ~ 222 Apps [http://forum.xda-developers.com/not...t-touchwiz-bloating-script-222-apps-t3258537]
This Option removes 222 applications. It is a simple download and flash in recoevery process.
****HOWEVER This will remove some functionality of the device READ the list of application before you flash to make sure there are not any that you use. The OP also has instructions on how to modify the script if you want some application to not be removed.
Click to expand...
Click to collapse
Witch option is the easier? :silly:

Avide said:
Witch option is the easier? :silly:
Click to expand...
Click to collapse
Option #2 is WAY easier as long as you don't want to modify the script. You just download it to you phone boot into recovery and flash it. Then reboot. Takes 5 min.

ShrekOpher said:
This method is for root only. It requires installing TWRP which is a custom recovery. That means you will have to unlock the bootloader to be able to use this method. Once you unlock the bootloader (by Odin flashing TWRP) you have already tripped Knox. Knox is no big deal from what I have heard though. I have not heard of anyone getting denied a new phone because it was tripped.
Click to expand...
Click to collapse
Appreciate your reply. I was under the impression that the boatloader is already unlocked which is why we can flash a recovery without jumping through too many hoops. I know that a custom recovery trips Knox, but if there's a way to install the latest supersu through a utility such as flashfire or mobile odin, Knox won't be tripped.
I'm not really worried about warranty, just curious to see if it's possible to retain the integrity. Unfortunately both those options I mention requires the device to already be rooted which defeats what I'm trying to accomplish.
Hopefully someone will be able to figure something out in the near future.

Is it possible to use xposed with this?

So Shrek you've made the total move over?
I am holding off, althoguh i dunno for how long , because i need darker theme colors. do you know of any options?

masri1987 said:
So Shrek you've made the total move over?
I am holding off, althoguh i dunno for how long , because i need darker theme colors. do you know of any options?
Click to expand...
Click to collapse
Unless there is a feature in 5.1.1 that you MUST have, I would wait. I don't find anything to be significantly better on 5.1.1 vs. 4.4.4, but the battery life is much worse.

chodaboy19 said:
Unless there is a feature in 5.1.1 that you MUST have, I would wait. I don't find anything to be significantly better on 5.1.1 vs. 4.4.4, but the battery life is much worse.
Click to expand...
Click to collapse
Well i'm on 5.0.1 right now pop rocks, so yeah i probably will wait since there isn't a particular feature... i'm using the DOK2 modem on COD6 rom right now.

Is there a list of apps you should disable via the debloater specific to the tmobile note4?

masri1987 said:
So Shrek you've made the total move over?
I am holding off, althoguh i dunno for how long , because i need darker theme colors. do you know of any options?
Click to expand...
Click to collapse
There is no dark theme option as of right now, really it's the only thing i miss.

Will Rickards said:
Is there a list of apps you should disable via the debloater specific to the tmobile note4?
Click to expand...
Click to collapse
The list of apps on the "Debloater Script" (Option #2) thread is a great reference.

I tried everything exactly as indicated by this great guide, but I am still getting very poor battery life. I give up, I don't know what else to do.
I have googled and tried all sorts of suggestions from others with the same problem to no avail. Google Play Services and 5.1.1 have made my phone a useless POS. I guess it's time for a new phone. LOL

chodaboy19 said:
I tried everything exactly as indicated by this great guide, but I am still getting very poor battery life. I give up, I don't know what else to do.
I have googled and tried all sorts of suggestions from others with the same problem to no avail. Google Play Services and 5.1.1 have made my phone a useless POS. I guess it's time for a new phone. LOL
Click to expand...
Click to collapse
Do you ever use power saving mode? If you are in the stock kernel it can help a bunch. The phone operates just fine on it, if you are going to play a game or something you just turn it back off, but while your phone is in your pocket or laying around idle it keeps those background running Google services in check.
I'm normally getting about 6 hrs of SOT and about 24 hrs between charges. Below is where I'm at so far today. With about 2.5 hrs of SOT.

ShrekOpher said:
Do you ever use power saving mode? If you are in the stock kernel it can help a bunch. The phone operates just fine on it, if you are going to play a game or something you just turn it back off, but while your phone is in your pocket or laying around idle it keeps those background running Google services in check.
I'm normally getting about 6 hrs of SOT and about 24 hrs between charges. Below is where I'm at so far today. With about 2.5 hrs of SOT.
Click to expand...
Click to collapse
I think I found the culprit after 2 days of googling and countless wasted hours. My specific problem was that Media process was running all the time which in turn was causing Google Play Services to run at all times.
The Media process includes 2 packages: Media Storage and Download Manager. Together they perform scanning and indexing of media files on the internal SD and external SD.
I came across this page:
http://geeknizer.com/fix-android-media-server-scanner-sdcard-cpu-battery-drain/
I did step #3 which states that having more than 1,000 files in a folder makes this process crap out. I reformatted my microSD card, then I copied back all the files to the microSD. Then finally I deleted most of the pictures so that no one folder had more than 400 images.
I rebooted my phone and it started to behave normally. The Media Process only ran for 5minutes and stopped. Google Play Services ran for 2min and stopped. I have been through 1 charge already and got 5hrs or so of screen time with heavy use, I was installing apps, configuring accounts, freezing apps with Titanium backup, etc.
Overall, it seems like I have a happy ending to my story, BUT I will post a followup if the phone craps out again.
EDIT:
How do you get it to show the time on battery?
Mine doesn't have that information:

Does anyone have any interest in me adding how to set up Viper4Android on Systemless root to this thread? Just curious if I should go through the trouble.

There is a new version of SuperSU 2.64:
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
Changelog:
20.12.2015 - v2.64 - BETA
- (systemless) Detect more boot image partition names
- (systemless) Blank partitions before writing to them
- (systemless) Ask to restore boot and recovery images on full unroot
- (systemless) Implement "uninstall competing superuser apps"
- (systemless) Samsung: prevent "KERNEL IS NOT SEANDROID ENFORCING" warning
- (systemless) Cleanup system install properly if present, fixes a number of possible bootloops
- ZIP: 6.0+: Detect firmwares that can reload sepolicy from /data and use system-based root on these ("allow init kernel:security { load_policy }")
- supolicy: Additional SELinux patches for M (reduced logging only)
- Update translations

ShrekOpher said:
The list of apps on the "Debloater Script" (Option #2) thread is a great reference.
Click to expand...
Click to collapse
Link to script isn't working. ..have another?
Sent from my SM-N910T3 using Tapatalk

AlexanderBlaQ said:
Link to script isn't working. ..have another?
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Should be working now. Thanks for the heads up.

Xposed for Samsung Galaxy J3

Hey! So recently I got a Samsung Galaxy J3 and was wondering if it was possible to get Xposed on it? Flashing a Zip is not an option, by the way.

Hey man, I'm right there with you, I want to know as well. I hope this thread gets more attention! I got this phone recently myself and am so far very sad at the lack of ability to do things with it root-wise, such as getting root to frickin stick and getting things like Xposed installed (with-out boot looping your device....).

Hi,
If you're on 5.0.x, flash Xposed by arter97.
If you're on 5.1.x, flash Xposed by wanam.
Find both on Xposed General thread.
Sent from my ASUS_Z00AD

krasCGQ said:
Hi,
If you're on 5.0.x, flash Xposed by arter97.
If you're on 5.1.x, flash Xposed by wanam.
Find both on Xposed General thread.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
The problem is that I don't have custom recovery either, and I'm not yet experienced enough to know how to flash something like xposed without it, without bootlooping. I actually already have the xposed you're talking about, wanam is what I need since im on 5.1, so if someone guides me on how to flash it or at least points me in the right direction, maybe that'd help.
Also as a side question, somewhat related to this, anyone know what I should do about custom recovery? There are models close to mine but not the exact same that are covered by TWRP or CWMR, but I've been very strongly advised against such a course of action.

darknaio said:
The problem is that I don't have custom recovery either, and I'm not yet experienced enough to know how to flash something like xposed without it, without bootlooping. I actually already have the xposed you're talking about, wanam is what I need since im on 5.1, so if someone guides me on how to flash it or at least points me in the right direction, maybe that'd help.
Also as a side question, somewhat related to this, anyone know what I should do about custom recovery? There are models close to mine but not the exact same that are covered by TWRP or CWMR, but I've been very strongly advised against such a course of action.
Click to expand...
Click to collapse
I'd recommend TWRP, actually. If your device doesn't have a custom recovery developed, it could be a pain. Just hoping if someone could develop it one for your device.
Sent from my ASUS_Z00AD

krasCGQ said:
I'd recommend TWRP, actually. If your device doesn't have a custom recovery developed, it could be a pain. Just hoping if someone could develop it one for your device.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
I would agree with you, as I had TWRP on my last phone and liked it quite a bit. I just don't know which phone's TWRP to try and how to try and flash it on there. Do I do it through Odin? Theres (if I recall correctly) a TWRP for the Samsung Galaxy J2 and J5, on either side of my J3 (Which it's so odd that the newer phone came out with a "series" number in the middle like that). Which would you suggest I do, J2 or J5, or neither?

darknaio said:
Hey man, I'm right there with you, I want to know as well. I hope this thread gets more attention! I got this phone recently myself and am so far very sad at the lack of ability to do things with it root-wise, such as getting root to frickin stick and getting things like Xposed installed (with-out boot looping your device....).
Click to expand...
Click to collapse
Me being dumb, I tried manually installing the required files for Xposed a few weeks ago and it bricked immediately. So I had to get a replacement. I'm not sure if it's because I did it wrong but based on that I don't think we'll ever be able to install Xposed which really sucks. Coming from my previous phone which had a lot of tweaks from xposed it just feels weird using a normal phone.

darknaio said:
am so far very sad at the lack of ability to do things with it root-wise, such as getting root to frickin stick
Click to expand...
Click to collapse
I know what you mean. Every time I restart my phone I have to re-root it if I want to do something with it. Luckily I don't really need root on this phone. Mainly because of the lack of things you can do with it. Hoping to see something come out of this though

EqiiKxDude said:
Me being dumb, I tried manually installing the required files for Xposed a few weeks ago and it bricked immediately. So I had to get a replacement. I'm not sure if it's because I did it wrong but based on that I don't think we'll ever be able to install Xposed which really sucks. Coming from my previous phone which had a lot of tweaks from xposed it just feels weird using a normal phone.
Click to expand...
Click to collapse
I know exactly what you both mean. My previous crappy phone had loads of things from xposed on there that I missed. However the good news I guess is since I don't need certain UI tweaks because I'm satisfied with what this phone comes with I'm not missing out on too much. And thus far every time I get bootloop I just use Odin to flash a copy of the original firmware and somehow it doesn't reset everything so I can still keep trying without losing all my apps. Just haven't found anything that sticks. Maybe one of us should try a custom recovery from a different Samsung Galaxy J Series like the 2 or 5.

darknaio said:
I know exactly what you both mean. My previous crappy phone had loads of things from xposed on there that I missed. However the good news I guess is since I don't need certain UI tweaks because I'm satisfied with what this phone comes with I'm not missing out on too much. And thus far every time I get bootloop I just use Odin to flash a copy of the original firmware and somehow it doesn't reset everything so I can still keep trying without losing all my apps. Just haven't found anything that sticks. Maybe one of us should try a custom recovery from a different Samsung Galaxy J Series like the 2 or 5.
Click to expand...
Click to collapse
Yeah I mainly used Xposed on my previous phone to make it look more like Lollipop but since this phone comes with it I don't need it as much. And I didn't know you were able to unbrick this phone? I would have saved about $40 if I knew that ? well then yeah we should probably try one of them. I think we should go with the newest one though

Thats what I was thinking, but I don't know which J series came out before the J3 this year or I'd try that one. And yep, luckily able to unbrick it thanks to Odin. Actually unbricked it from even worse than a boot loop, I accidentally destroyed my recovery somehow so I couldn't even boot into that and do a factory reset, but thankfully Odin's separate from the recovery so it still worked. End of the day if you can at least get your phone recognized by your computer and can flash something onto it, flashing stock = unbrick (usually).

I own the J3 also. Have gained temp root via king root so I could debloat the system. We need a cf auto root option. Our device is 5.1.1 and I think the kernel has to be modified for true root. Then development can start. As for xposed,you need full root for that to work properly. I suggest to you all to get a copy of the device firmware,install odin on pc so you can reinstall firmware if you decide to use temp root and end up boot looped after debloating to much or making other potentially harmful changes.

Curtis1973 said:
I own the J3 also. Have gained temp root via king root so I could debloat the system. We need a cf auto root option. Our device is 5.1.1 and I think the kernel has to be modified for true root. Then development can start. As for xposed,you need full root for that to work properly. I suggest to you all to get a copy of the device firmware,install odin on pc so you can reinstall firmware if you decide to use temp root and end up boot looped after debloating to much or making other potentially harmful changes.
Click to expand...
Click to collapse
I have the same thing, temp root that's lost when I reboot. I've already had to go the Odin route with the original firmware so I've got my backup covered. I'm also working with the dev behind Super Sume and he thinks he has the issue resolved, if not he's going to teamview with me to try and get past this. If we manage to solve the problem I'll post the results and subsequent steps here. Hopefully this will lead to root sticking through reboot. If so then at minimum may be able to solve -some- of the problems. Though I don't know if this will fix Xposed not working, as it always caused me to boot-loop in the past (only solved by going into TWRP and rebooting from there) and even if root sticks the only way to flash Xposed according to current theories is to do so from custom recovery, which I haven't found one for this device yet.
Have you been able to get a custom recovery on your J3? If so that would be the other key part to solving a lot of these problems. If I get the Super Sume to work and someone else can manage to get a custom recovery working, maybe that'll be the start of this device's support here =D.

No but I believe by repacking an edited firnware you can add xposed that way.

Curtis1973 said:
No but I believe by repacking an edited firnware you can add xposed that way.
Click to expand...
Click to collapse
Unfortunately I wouldn't know the first thing about editing a firmware, much less be able to add Xposed lol. Could that be a way to manually add custom recovery? Or are we still dependent on someone making a version compatible with this phone?

will need a custom recovery built for the device. with proper root you could then use flashify to install it to the device. root opens the door for everything. temp root will never get much except ability to debloat the device.
---------- Post added at 08:17 AM ---------- Previous post was at 08:15 AM ----------
i reached out to chainfire in hopes of cf auto root for the j3. but have not heard back. but does not mean i wont. will see. otherwise i will keep on trying what i can.

Quick question. Has anyone updated their J3 yet? I keep getting a notification for a Software update, is it safe?

EqiiKxDude said:
Quick question. Has anyone updated their J3 yet? I keep getting a notification for a Software update, is it safe?
Click to expand...
Click to collapse
Ive been seeing that too and ignoring/swiping it away. Not sure what it is though.

my system is edited so im not getting update pushes. probably nothing significant.

Curtis1973 said:
my system is edited so im not getting update pushes. probably nothing significant.
Click to expand...
Click to collapse
Your J3 is modified? Temp root, or something else?

New T-Mobile Firmware Out. --> G930TUVU4PK1

This update brings us up to November security patch.

I assume this is rootable via Odin bootloader swap. Does this update finally enable vulkan?
And how is battery life?
Thanks ahead of time

So far it does seem like it was the stated update to enable 256QAM and 64QAM. But for me only the upload speeds have increased, up to Just over 50Mbps. The speeds in general have been varying from 30Mbps-150Mbps dependent on site, but Just days ago I would be roughly 80Mbps almost everywhere I went, up to about 130Mbps

thowersome said:
I assume this is rootable via Odin bootloader swap. Does this update finally enable vulkan?
And how is battery life?
Thanks ahead of time
Click to expand...
Click to collapse
Vulkans been enabled since the September patch update APIA

I assumed it was but it doesn't seem to be picked up by the apps. For example dolphin emu doesn't pick it up

G930TUVU4APK1_CL9507190_QB11413802_REV02_user_low_ ship_MULTI_CERT.rar
Here are the Odin files:
G930TUVU4APK1_CL9507190_QB11413802_REV02_user_low_ship_MULTI_CERT.rar

After updating to this pdanet force closes about 1 minute after connecting it. Seems there's some new system service that is force closing it. Really low move there tmo
---------- Post added at 10:27 PM ---------- Previous post was at 10:17 PM ----------
If anyone can grab the update files and figure out if there's a new service they introduced maybe I can disable it in package Disabler pro. I really need pdanet to work

Okay now the burning question
... does root work??

KillerClaw321 said:
Okay now the burning question
... does root work??
Click to expand...
Click to collapse
That's what I want to know as I updated and now can't get root access...

CWBPHT said:
That's what I want to know as I updated and now can't get root access...
Click to expand...
Click to collapse
Meaning you flashed the kernel, and used the root.bat but supersu doesnt work?
---------- Post added at 04:38 PM ---------- Previous post was at 04:37 PM ----------
esjames said:
This update brings us up to November security patch.
Click to expand...
Click to collapse
Can you root? Or did you try?

KillerClaw321 said:
Meaning you flashed the kernel, and used the root.bat but supersu doesnt work?
---------- Post added at 04:38 PM ---------- Previous post was at 04:37 PM ----------
Can you root? Or did you try?
Click to expand...
Click to collapse
I followed the root guide here - http://forum.xda-developers.com/tmobile-galaxy-s7/how-to/root-files-t-mobile-s7-t3488067
I got the boot file flashed and rebooted, but when I run root.bat it just sits there saying waiting-for-device and a security warning pops up on my phone. I have USB debugging enabled and no boot unlock requirement. I had root, then lost it with a previous build and decided to flash stock then update and try again. I'm at my wits end as to what is going on.
Edit - Also, when I type adb devices there are no devices attached, yet I have access to my sd card and phone folders through windows...

CWBPHT said:
I followed the root guide here - http://forum.xda-developers.com/tmobile-galaxy-s7/how-to/root-files-t-mobile-s7-t3488067
I got the boot file flashed and rebooted, but when I run root.bat it just sits there saying waiting-for-device and a security warning pops up on my phone. I have USB debugging enabled and no boot unlock requirement. I had root, then lost it with a previous build and decided to flash stock then update and try again. I'm at my wits end as to what is going on.
Click to expand...
Click to collapse
Then run the cmd as admin

KillerClaw321 said:
Then run the cmd as admin
Click to expand...
Click to collapse
No dice, its still just sitting there and nothing is showing up with adb devices. I've tried switching usb ports, i'm currently trying to reinstall the adb drivers... I'm on windows 7 btw. Is it possible to downgrade the firmware?

CWBPHT said:
No dice, its still just sitting there and nothing is showing up with adb devices. I've tried switching usb ports, i'm currently trying to reinstall the adb drivers... I'm on windows 7 btw. Is it possible to downgrade the firmware?
Click to expand...
Click to collapse
I know it was possible to go from PG1 to PD8, idk about PIA-PG1 or PK1-PG1 ...

KillerClaw321 said:
I know it was possible to go from PG1 to PD8, idk about PIA-PG1 or PK1-PG1 ...
Click to expand...
Click to collapse
I just tried and it wouldn't work through Odin. Getting really frustrated. Something i've read is that the Samsung Galaxy S7 drivers in the Device Manager can interfere with proper ADB functionality. Should I try removing those drivers?
Edit - Just uninstalled the adb drivers and reinstalled using the Android SDK usb drivers and it worked. I've successfully run the root bat, now I'm in a boot loop which I'm trying to fix with another factory reset. We shall see.

CWBPHT said:
I just tried and it wouldn't work through Odin. Getting really frustrated. Something i've read is that the Samsung Galaxy S7 drivers in the Device Manager can interfere with proper ADB functionality. Should I try removing those drivers?
Edit - Just uninstalled the adb drivers and reinstalled using the Android SDK usb drivers and it worked. I've successfully run the root bat, now I'm in a boot loop which I'm trying to fix with another factory reset. We shall see.
Click to expand...
Click to collapse
Oh yes after root you will see a bootloop, but its fine. A factory reset will fixthe issues... just let us know if when you setup the phone you have root.

m52 power! said:
After updating to this pdanet force closes about 1 minute after connecting it. Seems there's some new system service that is force closing it. Really low move there tmo
---------- Post added at 10:27 PM ---------- Previous post was at 10:17 PM ----------
If anyone can grab the update files and figure out if there's a new service they introduced maybe I can disable it in package Disabler pro. I really need pdanet to work
Click to expand...
Click to collapse
If anyone else can confirm that? You could then send a message to the PDANet app team and maybe they'll work in a workaround of some sort.

KillerClaw321 said:
Oh yes after root you will see a bootloop, but its fine. A factory reset will fixthe issues... just let us know if when you setup the phone you have root.
Click to expand...
Click to collapse
Got it up and running and even debloated it, got xposed on there, and I'm working on the tuning guide here - http://forum.xda-developers.com/ver...uide-fine-tuning-performance-battery-t3417804
The only minor annoyance I have as of right now is the phone keeps giving me a "health update" telling me that I have to update Samsung +, but thankfully it stopped giving me the stupid security warnings.
Thanks for the help!

Does this update help with any slowdowns from the Eng Boot root? Even when i set govs to interactive it still lags quite a bit. I'm currently on PG1.

joachim123 said:
Does this update help with any slowdowns from the Eng Boot root? Even when i set govs to interactive it still lags quite a bit. I'm currently on PG1.
Click to expand...
Click to collapse
I've not had any lag problems, but I did optimize a bunch of apps from running in the background, which always helps with battery life.

Delete

Delete

Craz Basics said:
I just rooted my galaxy s7 edge on 6.0.1, and it downloaded the nougat update (OTA). I havn't installed it yet, but I was wondering if I use flashfire, will I still have root and xposed? I'm highly doubting xposed but what about root?
Thanks,
Gavin
Click to expand...
Click to collapse
You wont have root or xposed.

Ah, figures. Thanks a ton for the reply though, I thought nobody was going to.

Craz Basics said:
Ah, figures. Thanks a ton for the reply though, I thought nobody was going to.
Click to expand...
Click to collapse
Yea, sadly xposed is not released for nougat yet, so nobody has that.

Ummmm you can root on 7.0 dude. Just update it to 7.0 and then just follow the directions in this thread https://forum.xda-developers.com/verizon-s7-edge/how-to/root-method-nougat-t3566978
I can confirm that it is safe to use and works having done it myself, however as for xposed I don't think it's out yet for 7.0 bt I could be misinformed.

TheSproker said:
Yea, sadly xposed is not released for nougat yet, so nobody has that.
Click to expand...
Click to collapse
Do you think it will come out soon?

This is the last I heard on it in January
https://www.google.com/amp/s/www.xd...he-situation-regarding-xposed-for-nougat/amp/

gurnsey101 said:
Ummmm you can root on 7.0 dude. Just update it to 7.0 and then just follow the directions in this thread https://forum.xda-developers.com/verizon-s7-edge/how-to/root-method-nougat-t3566978
I can confirm that it is safe to use and works having done it myself, however as for xposed I don't think it's out yet for 7.0 bt I could be misinformed.
Click to expand...
Click to collapse
I am aware, thanks for the reply. I am rooted as well on 7.0 now. How do you deal with the lag? I have the kernel Aduitor app (Sorry, I don't know how to spell it lmao) and both my governors are set to performance. This kills my battery but any other one is a bit too laggy for me. I do have greenify to help me out on standby which is what killed my battery before root.

gurnsey101 said:
This is the last I heard on it in January
https://www.google.com/amp/s/www.xd...he-situation-regarding-xposed-for-nougat/amp/
Click to expand...
Click to collapse
Will check out, thanks!

All good theres a reason i didnt take part in spelling bees haha and Well I set mine to conservative for the kernal aduitor app and make surr you hit the "apply on boot" option on the top and restart your phone (I didn't notice it at first) and it seemed to fix most of the lag as for the battery I flashed debloat script https://forum.xda-developers.com/galaxy-s7/themes/mod-extreme-debloater-s7-root-req-t3335703
either that or try this custom rom that I can confirm works as well and has no lag just follow the instructions carefully
://forum.xda-developers.com/verizon-s7-edge/development/rom-t3603231

gurnsey101 said:
All good theres a reason i didnt take part in spelling bees haha and Well I set mine to conservative for the kernal aduitor app and make surr you hit the "apply on boot" option on the top and restart your phone (I didn't notice it at first) and it seemed to fix most of the lag as for the battery I flashed debloat script https://forum.xda-developers.com/galaxy-s7/themes/mod-extreme-debloater-s7-root-req-t3335703
either that or try this custom rom that I can confirm works as well and has no lag just follow the instructions carefully
://forum.xda-developers.com/verizon-s7-edge/development/rom-t3603231
Click to expand...
Click to collapse
Conservative? That will be hella laggy lol. I have had the "apply on boot" option selected. And the debloat script, would just disabling the bloat work? Because that's what I have done. And I have a qualcomm s7 edge :/
so I don't have a custom recovery and no unlocked bootloader. So I don't think I can flash any ROMs. I did find a T-mobile ROM, but no AT&T (mine).
Edit: I did put it on conservative. Seems okay, just had to get passed startup

Yeah conservative is what I am on and no lag haha and no the debloat script removes things entirely from the system and yes you can flash the rom i linked even on locked bootloader that one is safe to flash just use flashfire and follow the instructions I use a Verizon s7 edge so it's all good you can flash it just make sure you follow the directions to the letter and dont panic if the reboot takes like 10 mins or so it will take a few for it to reboot after flashing

gurnsey101 said:
Yeah conservative is what I am on and no lag haha and no the debloat script removes things entirely from the system and yes you can flash the rom i linked even on locked bootloader that one is safe to flash just use flashfire and follow the instructions I use a Verizon s7 edge so it's all good
Click to expand...
Click to collapse
Is debloat safe?
Also, do I just download the zip and flash in flashfire? As well what version do I download, there are two files

Yes debloating is completely safe as long as you don't unstall key components (the one I linked is safe) all it does is pretty much run an adb command to unstall useless apps like all the google and Samsung apps that we never use that tend to take up space and ram

gurnsey101 said:
Yes debloating is completely safe as long as you don't unstall key components (the one I linked is safe) all it does is pretty much run an adb command to unstall useless apps like all the google and Samsung apps that we never use that tend to take up space and ram
Click to expand...
Click to collapse
Okay, which one do I use? I won't have Wi-Fi soon so I downloaded both, so I can just pick one.

Yes use flashfire. Flashfire is your love flashfire is your life haha and bt first go into super su and go into settings click on "enable su during boot" then use the flash zip OTA option and the make sure you chose the mount/system option and I use the Clean_S7_160319_Ultra one however I will advise you to look through the script first to see what is uninstalled first just to make sure so you can make backups bc I am not sure what exactly you use

I need you help asap! I ran a script (I found one that wasn't on the link you sent me, stupid me) and now it keeps saying "IMS Service has stopped" laterally every 2 seconds. Any help please?

Did you use the S7Edge DeepDebloatV2? Or something like that?? Haha yeah don't use that uninstall ims for now or reflash with Odin

gurnsey101 said:
Did you use the S7Edge DeepDebloatV2? Or something like that?? Haha yeah don't use that uninstall ims for now or reflash with Odin
Click to expand...
Click to collapse
Ahh. Yeah I refreshed in odin. Then I did your debloat, and worked like a charm, Thanks! I forgot to sign into Snapchat before rerooting Smh, this is not my day lol. Would you happen to know any way to get on with root?

Hmmmm ic well you could try hiding the root with rootcloak in the playstore bt if I had to guess it searches for super su and the su folder soooo my guess would be to maybe go into super su and uninstall the root and super su (or reflash everything with odin to make sure all root is wiped) and then log in then root it after