THIS IS FOR QUALCOMM SM-G935P
I saw that the original root thread was missing a few information on the first and second post, so I decided to still offer the same information, while making the entire root process easy to follow along. All work goes to those at the Samsung G935P Root Forum and @colormedroid .
The Files Needed Are:
Odin by Princecosmy: ODIN
G935A: Galaxy S7 Edge
SuperSU: SuperSU Root
Minimal ADB and Fastboot: XDA Forums
You will also need Package Disabler Pro for Samsung: Package Disabler Pro (Samsung) $0.99
I know it costs money, but it is worth it, especially on future devices that support Samsung Admin while waiting for root.
Make sure all files above are downloaded and ready to be accessed.
These steps are best done on a factory reset (can be found in FAQ #3) on PF2 update.
Step By Step Instructions
1. After downloading Package Disabler Pro and getting it set up, you'll need to disable three packages: samsung dm phone interface, samsung dm service, and securityLogAgent.
2. Turn off your phone and boot into Download/Bootloader mode by pressing and holding the Vol Down+Home+Power after your phone is off.
3. Plug Phone into Flash the G935A.TAR in ODIN under AP and your device should restart by itself.
4. Your phone should boot straight into Android. Most likely you will have no LTE. Do not worry, that is normal. Continue onto step 5.
5. Copy the files from SuperSU to the location of your Minimal ADB and Fastboot folder on the computer (Default is "C:\Program Files (x86)\Minimal ADB and Fastboot")then after you enable USB debugging in the Developer Options menu on your phone (If you don't have Developer Options in Settings, go to About Phone, and tap on Build Number 7 Times), Run the Root.Bat file from your Minimal ADB and Fastboot Folder.
6. Open Build.Prop with BuildProp Editor and change the following settings
ro.cdma.default_numeric=310000
Change the value to 310120
ro.cdma.default_alpha=Chameleon
Change "Chameleon" to Sprint
Edit*ro.build.characteristics=Chameleon
Change "Chameleon" to Sprint
After a reboot, you should be good to go and have LTE.
Any other questions, feel free to post to the thread and myself and other helpful members of the community can help!
FAQ
1. Download and install BusyBox on Rails and get it set up. After that's set up, open up SuperSU, go to settings, and under Security check Enable SU during boot. Next, download Kernel Toolkit and under CPU set the Big Cores Maximum Frequency to 2150 Mhz. Don't forget to apply to boot from the side menu.
2. I'm stuck on the LTE splash screen. What do I do?
A: Press and hold the Volume Down + Power button down until your phone restarts. You may have to Factory Reset your device if it stays stuck on the splash screen. Get the files from FAQ #3 to successfully reset. If you wish to Re-Root, activate device beforehand by doing the Device Setup or by going into Settings - Activate Device. After Activated, follow the step by step guide.
3. I'd like to unroot and return to factory stock. How would I go about this?
A: Download the factory firmware from HERE and extract the file. Once Extracted, open ODIN and load each file in their appropriate space (BL file to BL, AP file to AP, CP file to CP, and CSC file to CSC). Make sure your phone is in download/bootloader mode by holding the Vol Down+Home+Power after the phone is off. Click Start once in download/bootloader mode and you should be back to stock once your phone reboots.
4. My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Use BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Once the edit is saved correctly, restart your phone.
Credit goes out to: @guaneet for this fix
More answers to FAQ's to come.
Thanks, this guide is a bit clearer for beginners like me
EDIT: I can't seem to find the Minimal ADB and Fastboot Folder, where is it? (solved)
EDIT2: Where do I find the root.bat file in my phone? (solved, I had to run it from the computer not the phone)
This doesn't trip Knox right? So if I root and decide to go back stock, Samsung pay should work right?
JG96EVO said:
This doesn't trip Knox right? So if I root and decide to go back stock, Samsung pay should work right?
Click to expand...
Click to collapse
Correct. It requires to be on unchanged software. When going on complete factory reset using ODIN, it reverts any and all software changes made.
That changing the thing to sprint an the numbers to 310120 does not work for me when i do that i get no data wel 3g an it comes in an out then goes to roaming..an i cant change apns an there r no sprint apns as well...not sure if anyone els is having that
donbudafuko said:
That changing the thing to sprint an the numbers to 310120 does not work for me when i do that i get no data wel 3g an it comes in an out then goes to roaming..an i cant change apns an there r no sprint apns as well...not sure if anyone els is having that
Click to expand...
Click to collapse
Did you let the phone set up once before rooting? Did you also go into mobile networks and change roaming settings to home only?
Edit: The setup to bring your phone to Sprint did work because Sprint does not allow (unless with MSL) editing of APNs. I also made an edit that changes ro.build.characteristics=Chameleon in Build.Prop to ro.build.characteristics=Sprint. Hopefully that helps as well.
So let me throw out some errors that happened with me with the solvencies so no one has to feel like an idiot like me...
1. If Odin throws an error on your pit it will look like its good to go. It is not. Let your phone setup and then reodin
2. After initializing the 3 you disabled, go to settings, activate device. Let it activate but do NOT press done or ok or restart or a winky face emoticon or anything... But the home button and disable that same three again. Reboot. If your device keeps trying to be crazy, pick yourself up and try again.
3. For the bad file... Enable USB debugging, install the and drivers and the such then... Plug your phone into your computer and agree to the popup on your phone. After you agree (You have to be down with MTP, you know me) run the bad file on your computer. It'll say stuff and take a couple of minutes. Let it run. After reboot, reboot again. Root achieved.
Thanks so much for your clarification OP, I would've loved to use this post when I did mine lol
NOTE: Your mileage may vary... I did the buildprop change from Chameleon and the 31000 change and it negated my service. I went and changed it back, restarted, re-enabled the 3, activated the device, homed out, re-disabled the 3 and restarted. My LTE is back up and running
4. My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Use BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Even after making these changes and verifying, my WiFi credentials and still being erased.
Hardcorp said:
4. My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Use BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Even after making these changes and verifying, my WiFi credentials and still being erased.
Click to expand...
Click to collapse
Verify your edit stuck. Make sure there is not any extra "space" in line or end of that line. Reboot.
xyameax said:
Did you let the phone set up once before rooting? Did you also go into mobile networks and change roaming settings to home only?
Edit: The setup to bring your phone to Sprint did work because Sprint does not allow (unless with MSL) editing of APNs. I also made an edit that changes ro.build.characteristics=Chameleon in Build.Prop to ro.build.characteristics=Sprint. Hopefully that helps as well.
Click to expand...
Click to collapse
Tryed that still the samething..really doesnt mayter thimo i have data an call service as is so um goid just wanting to let everyine els know it might not work
LeftyGR said:
Verify your edit stuck. Make sure there is not any extra "space" in line or end of that line. Reboot.
Click to expand...
Click to collapse
After the next reboot they started to stick.
why can i not update su? without updating i cannot use buildprop editor... i even tried downgrading from pf2 to pe1.... no luck. phone also says custom on boot.
Are there still issues with lag and battery drain after root?
wojo797 said:
why can i not update su? without updating i cannot use buildprop editor... i even tried downgrading from pf2 to pe1.... no luck. phone also says custom on boot.
Click to expand...
Click to collapse
Updating supersu has had mixed results. Some have no problem, but it has been suggested by chainfire himself to not update it.
ch0de said:
Are there still issues with lag and battery drain after root?
Click to expand...
Click to collapse
If you follow the Kernal Auditor step, it helps with the lag and battery drain. It is because the phone is in performance mode first upon root, and so the phone throttles on heat. Setting it to Interactive brings down heat and ultimately lag and brings back battery life.
wojo797 said:
why can i not update su? without updating i cannot use buildprop editor... i even tried downgrading from pf2 to pe1.... no luck. phone also says custom on boot.
Click to expand...
Click to collapse
Are you on the Qualcomm or Exynos device? Are you sure you're G935P? I ask to try again one more time and make sure SU is installed on your phone. It may take a while for the prompt to open as well, but give it time.
xyameax said:
If you follow the Kernal Auditor step, it helps with the lag and battery drain. It is because the phone is in performance mode first upon root, and so the phone throttles on heat. Setting it to Interactive brings down heat and ultimately lag and brings back battery life.
Click to expand...
Click to collapse
Just to clarify, and I apologize for my ignorance..
When you say "helps" with battery drain and lag, does that mean it fixes the issue and it preforms at "stock", or does that mean its better then doing nothing but still more lag and battery/heat the unrooted stock ?
As per XDA forum rules, duplicating threads is not allowed. There is nothing wrong with making your contribution to the existing thread. Please continue there:
SM-G935P Root
THREAD CLOSED
Related
So you want to keep (knox) warranty and still use root?
Well there is RDLV and the "forbidden" Tool for that, BUT you will still have SELinux on enforcing mode, which means you don't have full control even with root. While technically most things still do work, they might work a lil different or need a different approach.
Lets collect our findings here...
---
First of all, remounting system with apps like solid explorer does not seem to work.
A workaround for this is to run the following command in terminal or through quick terminal etc:
Code:
/system/bin/mount -o rw,remount /dev/block/mmcblk0p2 /system
This command gets through where other methods fail. Once you have mounted the system writable like this, you can go back to your root explorer app to delete things etc on system partition. Solid explorer gives me error messages still when I delete apps from /system/app/, but they still disappear / get deleted.
---
This also brings me to my next workaround:
To delete system apps and not just freeze them with Titanium, you need to remount system like above and then delete the apks from the /system/app/ directory. A reboot should then remove everything else related to that app afaik. (like the /data/data/ of the app etc.)
Titanium on the other hand gives me an error when I try to delete a system app, even after remounting system to rw.
---
If you want to edit things from your system partition, like build.prop etc. Copy them to your sd first and edit them there. Then mount system rw, and create a backup of the file you are editing. (make a copy and just append "_bak" or smth to the file name) And finally copy the sd file over the corresponding file in system. Make sure you check permissions before and after you copied everything and edit them if they do not match up.
---
My final Tip for now:
I noticed that most root methods on SELinux (this includes RDLV and the forbidden one) use install-recovery.sh to start su as a system daemon which handles all the su requests. (as far as I understood it at least).
Well we can also use this file (or create an install-recovery-2.sh in /etc/ which gets called by the first one by default when you got the root) to run init.d scripts or other stuff.
I don't have tested it yet but I will put the code below once it works...
Code:
tbd
..
hopefully we find a way to turn off this selinux enforcing mode while keeping knox warranty at some point.. - xposed framework might be the answer but not sure - in theory its able to overwrite all methods used by apps. (but I guess selinux above xposed still in system rights and therefore cannot be affected by it?)
And another one:
Don't like this big n clunky user interface? The DPI for the Note 3 is set to 480, thats for old people! If you have want things a bit more refined and more "space" on the screen, edit your build.prop (like I mentioned above) and set the "ro.sf.lcd_density" value down.
I used 360 instead of 480 and that seems perfect to me. It looks like 240 DPI used to look on the Note 1. - You could try 320 or 400 as well.
If you want to set the dpi of individual apps, install xposed and the app settings module. (I would still set browser to 360 or even 320 dpi, 400 is just too much - the adress bar is so damn huge still)
Glad to see you still at it homie. Kingoapp is great. "Google kingoapp" anyone needing help. Just don't post any links please.
Sent from Heaven.
dallastx said:
Glad to see you still at it homie. Kingoapp is great. "Google kingoapp" anyone needing help. Just don't post any links please.
Sent from Heaven.
Click to expand...
Click to collapse
Definitely try out at least the dpi change to 360 or 400, that one is golden =). (nothing special but still..)
--
so far I haven't found anything that does not work at least with a workaround. Some apps do not work as supposed, but thats because they havent adapted yet to the new environment as far as I can tell. And yea, you cannot edit the selinux stuff or turn it off (at least not easy) but thats it. What I did not yet try, which is for risk-friendly people only anyway, is to mess with the efs folder. (you can change your devices mac there, good for privacy concerns hehe). Could be that selinux blocks that one as well, but other than that most things work alright. Just no custom recovery yet, but this could maybe be made possible through the install-recovery.sh file, telling it to start up a custom recovery but not actually flashing it hard onto the device.
Reboot apps I can't get to work. You know the apps that restart phone, bootloader etc... Even through the side 4 button mod. I can only reboot through factory restart. Pressing the power button and using the default restart button.
Sent from Heaven.
---------- Post added at 06:50 PM ---------- Previous post was at 06:49 PM ----------
Yea I always do DPI changes for Gmail , browser, settings, and few other apps
Sent from Heaven.
aww yea youre right - I havent got any app to reboot the phone yet, only the normal reboot through the stock power menu works for me. Didnt try terminal yet.
Maybe not "reboot" but "shutdown -r now"
dallastx said:
Reboot apps I can't get to work. You know the apps that restart phone, bootloader etc... Even through the side 4 button mod. I can only reboot through factory restart. Pressing the power button and using the default restart button.
Click to expand...
Click to collapse
The 4 way reboot menu from Wanam's xposed module works fine for me if you wanted to check that out.
I got one. Enter download mode by powering off. Then hold volume_down+home+power then press volume_up when promtped. Ok now this is what blows my mind. Everyone says pull battery to exit. I did this and the center off my screen looked messed up for about 8 seconds and I thought there must be a better way. Guess what to exit just hold power by itself for about 10 secs and you reboot out of download mode. Great easy way to check counter and no longer have to remove case, battery, etc.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
TheAvatar said:
The 4 way reboot menu from Wanam's xposed module works fine for me if you wanted to check that out.
Click to expand...
Click to collapse
Yea i tried it but didnt work... It may of been conflicting with other apps. But what root method are you using?
---------- Post added at 07:16 PM ---------- Previous post was at 07:11 PM ----------
JohnnyRebel said:
I got one. Enter download mode by powering off. Then hold volume_down+home+power then press volume_up when promtped. Ok now this is what blows my mind. Everyone says pull battery to exit. I did this and the center off my screen looked messed up for about 8 seconds and I thought there must be a better way. Guess what to exit just hold power by itself for about 10 secs and you reboot out of download mode. Great easy way to check counter and no longer have to remove case, battery, etc.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yea i have always got out of download mode on Note 3 by just holding power button.
---------- Post added at 07:20 PM ---------- Previous post was at 07:16 PM ----------
zroice said:
And another one:
Don't like this big n clunky user interface? The DPI for the Note 3 is set to 480, thats for old people! If you have want things a bit more refined and more "space" on the screen, edit your build.prop (like I mentioned above) and set the "ro.sf.lcd_density" value down.
I used 360 instead of 480 and that seems perfect to me. It looks like 240 DPI used to look on the Note 1. - You could try 320 or 400 as well.
If you want to set the dpi of individual apps, install xposed and the app settings module. (I would still set browser to 360 or even 320 dpi, 400 is just too much - the adress bar is so damn huge still)
Click to expand...
Click to collapse
Only reason i wouldn't change the DPI for everything because some apps will look crazy. Then you will have apps also like the play store that may not work correctly.
JohnnyRebel said:
I got one. Enter download mode by powering off. Then hold volume_down+home+power then press volume_up when promtped. Ok now this is what blows my mind. Everyone says pull battery to exit. I did this and the center off my screen looked messed up for about 8 seconds and I thought there must be a better way. Guess what to exit just hold power by itself for about 10 secs and you reboot out of download mode. Great easy way to check counter and no longer have to remove case, battery, etc.
Sent from my SM-N900W8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
good finding! (lol i couldve came up with this myself lol - holding power long enough always does a forced reboot).
I noticed too that when you pull the battery that sometimes you get lines on the screen - really scary, thought I messed up my device but after like 10 seconds or so they disappeared. But definitely something you want to avoid!
Holding down power to exit the download mode instead of pulling battery from now on.
I use Rootr Browser Pro... I can delete things out of the system partition and write into the system partition (after setting it for root privelege in settings and supersu) however I can''t just overwrite files.... The file I wish to overwrite must 1st be deleted or renamed,usually with .bak. Haven't had to use terminal.
Another handy tip, in the CSC folder, rename the customer.xls to customer.xls.bak and then a new option will be available in the settings/device/lock screen menu to add app shortcuts to the lock screen
if you add this code to the others.xml file AFTER <FeatureSet> and BEFORE </FeatureSet>
<CscFeature_Sip_UseSymbolInCMKey>true</CscFeature_Sip_UseSymbolInCMKey>
<CscFeature_Sip_EnableSymbolInSecondary>en_GB;en_U S;de;fr;es;it</CscFeature_Sip_EnableSymbolInSecondary>
You will then enable sub symbols on the default keyboard.
Works a dream...
TheAvatar said:
The 4 way reboot menu from Wanam's xposed module works fine for me if you wanted to check that out.
Click to expand...
Click to collapse
wait a minute - the 4 way reboot does work for you? Are you on Knox 0x0 still? And SELinux status enforcing? For me no "reboot" apps seem to work. They all just try to reboot (and SELinux denies it then most likely)
---
one other problem occured: when using xprivacy and deinstalling an app the system locks up. Can someone confirm this?
Why do people insist on DELETING apps from system? Just use pm disable, sheesh.
khaytsus said:
Why do people insist on DELETING apps from system? Just use pm disable, sheesh.
Click to expand...
Click to collapse
The xprivacy lockup also happens with user apps deinstallation. Just want to make sure its not me or my setup but xprivacy thats causing this. I turned it off and it works, turn it on, device hangs on deinstallations.
zroice said:
And another one:
Don't like this big n clunky user interface? The DPI for the Note 3 is set to 480, thats for old people! If you have want things a bit more refined and more "space" on the screen, edit your build.prop (like I mentioned above) and set the "ro.sf.lcd_density" value down.
I used 360 instead of 480 and that seems perfect to me. It looks like 240 DPI used to look on the Note 1. - You could try 320 or 400 as well.
If you want to set the dpi of individual apps, install xposed and the app settings module. (I would still set browser to 360 or even 320 dpi, 400 is just too much - the adress bar is so damn huge still)
Click to expand...
Click to collapse
Yeah, thanks for the tip. I used xpose app setting to set my nova launcher to be about 400. I will try modify the build.prop then.
Ok so what i did to quickly update to mj4 since it is now live. "you will lose root and everything on internal storage so back it up"
Be sure make COPY of backup of your titanium folder if use NOVA be sure to do a backup of your current layout. Copy these folders to your EXTsd. Remove card afterwards.
I was rooted so i kept getting "Cant up dated Modded system". Even unrooting i cant getting Modded system. I use almost the same root method as OP uses called kingoapp "cant provide links so google is your friend"
Anyhow.. i wanted to make sure i didnt trip KNOX and grew impatient for an update.zip. I didnt want to flash anything through ODIN, so i figured would use Kies.
Kies will see your phone as already updated. At the top of the app if you click tools then "firmware and initialization" Kies will override whatever is on your phone and update to mI5. This will take about 30 min but much quicker then trying to download the entire stock firmware from hotfile.
Once your phone is up go ahead and go to to settings on you phone and system update. Update will run and restart your phone. You are now on the latest firmware mj4.
Reroot and reinstall SD card. You are now rooted on latest update.
Notes - I tried everything to try to trick system to thinking its not modded including unrooting. Nothing worked reasoning i resorted to flashing through Kies.
dallastx said:
Ok so what i did to quickly update to mj4 since it is now live. "you will lose root and everything on internal storage so back it up"
....
Click to expand...
Click to collapse
Ohh theres an update? Well I bought a 2nd note today - couldnt resist it was 500€ only (they usually go for about 550 here). And mine had some display issues... gonna sell the first one and keep second - screen is better. Anyway, I got to redo everything now and restore the "old one" to stock.
To restore stock safely I would always suggest using Kies and doing a forced firmware update like dallas described. I read that flashing the same firmware twice with odin can already trip knox. (at least if you were tempering with the system)
But note that this will most likely update the bootloader of your phone as well.
---
Now I got the old bootloader on my new and still branded n3 - can someone explain what the difference actually is to the new bootloader? I mean both don't allow SELinux permissive, and both can be rooted (at least with the "tool")?
On S4 etc I understand that new firmware version introduced knox, and that there was firmware out without knox, but if you upgraded once you couldnt go back. But there are no knox free firmwares for the n3 are there? (I mean stock ones)
zroice said:
Ohh theres an update? Well I bought a 2nd note today - couldnt resist it was 500€ only (they usually go for about 550 here). And mine had some display issues... gonna sell the first one and keep second - screen is better. Anyway, I got to redo everything now and restore the "old one" to stock.
To restore stock safely I would always suggest using Kies and doing a forced firmware update like dallas described. I read that flashing the same firmware twice with odin can already trip knox. (at least if you were tempering with the system)
But note that this will most likely update the bootloader of your phone as well.
---
Now I got the old bootloader on my new and still branded n3 - can someone explain what the difference actually is to the new bootloader? I mean both don't allow SELinux permissive, and both can be rooted (at least with the "tool")?
On S4 etc I understand that new firmware version introduced knox, and that there was firmware out without knox, but if you upgraded once you couldnt go back. But there are no knox free firmwares for the n3 are there? (I mean stock ones)
Click to expand...
Click to collapse
Yea go ahead and do all your updates then root. I think the update may me just for Sprint N900p.
so there is still no way to get rid of "enforcing selinux" without tripping knox counter?
need this only to get my OTG cable to USB OBD working, seems SELinux is blocking serial usb communication :/
zroice said:
wait a minute - the 4 way reboot does work for you? Are you on Knox 0x0 still? And SELinux status enforcing? For me no "reboot" apps seem to work. They all just try to reboot (and SELinux denies it then most likely)
Click to expand...
Click to collapse
Sorry for the late reply. I was Knox 0x0, used Root De La Vega, installed xposed framework then grabbed wanam from the play store. Just had to enable it and it was all good.
Below, not only will you find step by step instructions on how to root your device but also a FAQ section in post #2 that will guide you through the problems most of us encountered in the beginning. It is highly recommended that you read through all of it. Basic knowledge of ADB is required and if you don't have it then you should definitely read the FAQ section for ADB set up. Make sure you have all the files downloaded.
Update 10/25/2016: Attached at the end of this thread is a modified debloat script for knox removal and a few other apps. This will make your root experience a heck of a lot smoother than before. Just flash the zip using FlashFire without changing any settings. You may notice a reboot or two. There are few bloatware apps that will still be there (amazon shopping, amazon videos, amazon photos, etc) that you'll have to remove manually. Happy flashing and don't forget to hit that Thanks button down below!
Disclaimer:
This root method is NOT for beginners. It is NOT easy. If you don't get it then DON'T do it. Especially if you're worried about voiding the warranty and blah blah blah. Simply put, don't do it if you don't have the slightest idea of what you're doing. I'm tired of complaints. This guide is not for the faint of heart. Do this at your own risk!
Package Disabler Pro is required to get this rooting method working. Yes, it costs money ($.99) but it's the way I acheived this work around at the moment.
Be prepared to lose data (LTE) connection but don't be scared as it's an easy fix.
Make sure you don't have Secure startup set up before you start the process. Having this set up causes issues.
Must have ADB set up and installed system-wide.
This root method should be used with PE1 firmware for both the GS7 and the GS7 Edge. Although this root method might work with the latest firmware, users have been reporting issues dealing with APN's on the newest update. Look at post 2 FAQ's returning to stock for flashing PE1 firmware through Odin.
Do not update to PJ2 if you want to keep service with your root. Phone calls and text messages won't come through after rooting on PJ2.
Files you will need:
Odin by Princecomsy: http://www.filedropper.com/princecomsyodin
G935A: http://www.filedropper.com/samsungg935xqcrootedboot (S7 Edge)
G930A: http://d-h.st/o3hm (S7)
SuperSU: https://download.chainfire.eu/970/SuperSU/SuperSU-v2.76-S7QC.zip
Click on the BLUE "download" links. Extract everything into a folder easy to locate.
Here we go:
After downloading and getting set up Package Disabler Pro, you'll need to disable the following three packages:
samsung dm phone interface
samsung dm service
securityLogAgent.
Use the search box to easily find these packages.
Power off your device and boot into download/bootloader mode by pressing and holding the volume down, home, and the power button. Press volume up to get into bootloader.
Open PrinceComsy odin and flash the engineer boot.img by clicking AP and navigating to the file for your model. Click start and your device should reboot by itself.
Enable developer options by going to Settings>About Device and tapping Build Number till it shows Developer mode has been turned on. You will now have Developer options under the settings menu.
Enable USB debugging in the Developer options settings.
Extract the SuperSU zip and run the root.bat file. Your phone will reboot if the script is successfully ran.
Next, we'll get LTE data back:
Method A: BuildProp Editor (easiest method)
Open Build.Prop with BuildProp Editor and change the following settings:
ro.cdma.default_numeric=310000 to 310120
ro.cdma.default_alpha=Chameleon to Sprint
ro.build.characteristics=Chameleon to Sprint
Make sure you grant root permissions when it asks. You may have to try this twice. Reboot and LTE should stick.
Method B: Manual activation (also if you're not able to make any calls)
Enable the three packages disabled in step 1. Go into the phone dialer and type in ##72786# and your phone should reboot and begin the activation process. After the 5th retry, it will manually activate itself. It should say "writing to device". Don't click done yet. Press the home button and disable the three packages once again. Reboot.
Alternatively, after renabling the three packages and dialing ##72786#, you can go into Settings>Activate this device and manually try to activate it yourself. It still must say "writing to device". Don't click done. Disable the packages once again. Reboot. Voice and LTE should stick.
Download S7_or_S7Edge_Fixes_V15.zip to your internal or external storage and install install FlashFire from the playstore.
Open FlashFire and let it acquire root access. Click the + button at the bottom right corner then click on Flash ZIP or OTA. Navigate and select the S7_or_S7Edge_Fixes_V15.zip. file. Leave the options alone and click the check in the top right. Scroll down to the bottom and click flash. Your phone will reboot and flash the zip. This can take a while.
Go to Settings>Lock screen and security>Other security settings>Security policy updates and turn off "Automatic updates" and "Wi-Fi only". Reboot. This seems to be the culprit of the 7 day soft brick.
Open back up Package Disabler Pro and search for "software update". Disable both packages (com.sec.android.soagent and com.wssyncmldm)
Enjoy your rooted device with minimal to almost no lag.
???
Profit.
As always, be sure to donate to the people who actually helped achieved root: @Princecosmy, @br3w3r, and @Chainfire
For the bounty donate to [email protected] PayPal
Shout out to @psouza4, @izzibew26, @mhill1986, @LeftyGR, @Soooperstar, and to all of you who are contributing in making this root method easier everyday. Thanks for the feedback.
Originally, it started getting interesting at post #185:
http://forum.xda-developers.com/att-galaxy-s7/how-to/bounty-att-s7-root-exploit-t3341274/page4
I'm also keeping track of the Sprint Galaxy S7 (SM-G930P) version:
http://forum.xda-developers.com/sprint-galaxy-s7/how-to/sm-g930p-root-t3410604
FAQ's:
My WiFi credentials keep on getting erased after a reboot. What gives?
A: This seems to be an issue across all the QC S7 variants. Here's what I did to fix it. Download BuildProp Editor and change: ro.securestorage.support=true to ro.securestorage.support=false
Credit goes out to: @guaneet for this fix
Can I install Xposed?
A: Yep. Here's how to do it:
fnztakedown said:
Alright. Here is a DB link of the two files I had installed to get xposed working. To flash this you will need flashfire.
Process is simple. Download both files and install the apk.
Open flashfire> select flash new file> find the xposed zip, flash. Give it a solid 5-7 minutes during boot up.
Ensure you do not have any major packages disabled and ensure you have BACKED UP YOUR ROM VIA FLASHFIRE. Please be aware, this was successful for me on the 935T and I do have random reboots at time. I cannot confirm this is the cause yet. I would also suggest finding the uninstall zip in the event you have issues you can flashfire back.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://www.dropbox.com/sh/0yabdfx6ao69dpd/AAAnu-9Jv8W9stjjuG1Nq5jba?dl=0
Click to expand...
Click to collapse
Credit goes out to: @fnztakedown for these instructions
I'm having issues with ADB. Any help?
A: Easiest way to install ADB and its subsequent drivers would be to get it from here:
http://forum.xda-developers.com/showthread.php?t=2588979
It's SO easy to install and it takes most if not all of the hassle out of it.
Credit to @Snoop05 for this easy ADB installer.
How do I enable USB debugging?
A: Go to Settings>About device and tap Build number until it shows Developer options has been enabled.
I'm stuck on the LTE splash screen. What do I do?
A: Press and hold the Volume Down + Power button down until your phone restarts. If you keep on getting stuck at the LTE splash screen you may have to factory reset your device. As soon as your phone restart quickly press the volume up + home + power button and let it boot into recovery. Wipe data/factory reset and cache partition.
I'd like to unroot and return to factory stock. How would I go about this?
A: Head on over to @psouza4's post HERE and follow his steps in the return to stock section. The steps are easy and he's posted mostly all the firmware.
[*]Does this method trip Knox?
A: No, it doesn't. And flashing back to stock will allow Knox to work again, as long as you didn't flash files from other sources (there are some that will trip Knox, so be careful).
[*]Does Samsung Pay work?
A: No, sorry. They can detect the rooted boot environment through a driver, so you can't even hide root from the app using RootCloak.
[*]Does Android Pay work?
A: It does, but you have to make a change that disables root and then reboot your phone. You can toggle this back/forth without flashing, but you either get root or Android Pay at any one time.
[*]What happens if I brick my phone?
A: As long as there are stock images to flash back to, it's almost impossible to do this no matter how badly the process goes. Check that we have stock images; if we do, then we can always flash them over the device using the unroot method in this guide. That practically guarantees a return-to-stock experience for a phone as long as it doesn't have any serious physical damage preventing it from powering on.
[*]I installed the ADB system-wide on my Windows computer/laptop, but I see "'adb' is not recognized as an internal or external command, operable program or batch file".
A: Your user profile path can't contain a space. That means if your Windows user is 'Somebody Nice' and thus your Windows user path is 'C:\Users\Somebody Nice', the install will fail. You can create another user on your computer (if prompted for a Microsoft login, choose to make only a local account) and enter a short, single-word name for your user. Sign into and use that user profile instead. Also, the path where you extract the SuperSU package can't contain a space, so try extracting them to somewhere simple like perhaps C:\S7Root.
More answers to FAQ's to come.
PF2 will not activate for me.
mrboost said:
PF2 will not activate for me.
Click to expand...
Click to collapse
Like to make calls and what not? Try going into the dialer and type ##72786#
I sure miss root. I read Samsung will be releasing factory unlocked phones that support all US Carriers however that doesn't necessarily the bootloader will be unlocked.
Awesome. Cant wait.
Sent from my SM-G935P using XDA-Developers mobile app
mrboost said:
PF2 will not activate for me.
Click to expand...
Click to collapse
Got mine finally activated by going through the system settings and clicking "Activate Device". Alternatively, after the 5th retry, this will automatically happen.
any update on what does and doesnt work? i have a PF2 s7 edge and im anxious to use this but wont if it breaks my samsung pay or gear 2 usability
rhyme187 said:
any update on what does and doesnt work? i have a PF2 s7 edge and im anxious to use this but wont if it breaks my samsung pay or gear 2 usability
Click to expand...
Click to collapse
Breaks Sam Pay. Root will always break it.
LeftyGR said:
Breaks Sam Pay. Root will always break it.
Click to expand...
Click to collapse
This is correct.
Sorry, I've been away and just got back to my computer. So far it seems that I am having issues activating the device after flashing the engineer boot.img through odin. It seems that after the 5th retry it will activate and write to device but will then restart and the whole activation process will start back over. I'm trying to see if I can use disabler pro to stop the reactivation process and I'll see where it goes from there.
My S7 is unlocked and with the activation problem, I feel I already know the answer, shouldn't affect me, right?
Since it's a matter of punching in APN info
TehPirate_ said:
My S7 is unlocked and with the activation problem, I feel I already know the answer, shouldn't affect me, right?
Since it's a matter of punching in APN info
Click to expand...
Click to collapse
Try it and let us know. And if it works, let us know the APN info would you?
I figured it was something to do with the APN info too but when I hit up my friend about the APN info (who isn't rooted) he told me the information was grayed out so I couldn't get a hold of the info.
My S7 edge SM-G935v is working great But running very HOT!!! Any Fixes?
colormedroid said:
Try it and let us know. And if it works, let us know the APN info would you?
I figured it was something to do with the APN info too but when I hit up my friend about the APN info (who isn't rooted) he told me the information was grayed out so I couldn't get a hold of the info.
Click to expand...
Click to collapse
Well the APN info would be for Cricket. Wouldn't be relevant.
melona380 said:
My S7 edge SM-G935v is working great But running very HOT!!! Any Fixes?
Click to expand...
Click to collapse
Unfortunately no, I only have the G935P and mine does not run hot after doing the above mentioned. Good luck to you and let us know if you figure anything out.
TehPirate_ said:
Well the APN info would be for Cricket. Wouldn't be relevant.
Click to expand...
Click to collapse
True! Thanks anyways! I was just hoping that ppl wouldn't have to spend money on package disable pro and it thus it would be a free solution.
Still getting reboots. It connects to LTE and does fine for a few minutes. Then it'll reboot randomly. I disabled the DM service as suggested. I also disabled System Update and Software Update. Thoughts?
EDIT: Also, it says Samsung in the top left corner and not Sprint. Just an observation.
sirslipzalot said:
Still getting reboots. It connects to LTE and does fine for a few minutes. Then it'll reboot randomly. I disabled the DM service as suggested. I also disabled System Update and Software Update. Thoughts?
EDIT: Also, it says Samsung in the top left corner and not Sprint. Just an observation.
Click to expand...
Click to collapse
What software version are you on? Did you disable the DM service AFTER your phone was activated? And just to make sure, your phone is the Sprint version?
colormedroid said:
What software version are you on? Did you disable the DM service AFTER your phone was activated? And just to make sure, your phone is the Sprint version?
Click to expand...
Click to collapse
I'm on PD3. I did disable DM AFTER activation. And yes, I'm on the G935P.
sirslipzalot said:
I'm on PD3. I did disable DM AFTER activation. And yes, I'm on the G935P.
Click to expand...
Click to collapse
Hmm.... I had issues with it rebooting on me randomly too at the beginning. It wasn't until I got home and after a few wipes that I didn't notice it afterwards. Might want to try a wipe or two and try it again.
Sent from my SM-G935P using Tapatalk
I take no credit other than compiling info and making a guide. All credit goes to http://forum.xda-developers.com/member.php?u=4911585 (br3w3r, Chainfire and Princecomsy)
http://forum.xda-developers.com/att-...-root-t3410403
Also credits to Mastajeff for originally making the guide for T-Mobile.
First off download these files: http://d-h.st/PK3q
Extract them to whatever folder you want, there will be 5 files in there.
Folder named: "su" contains the SuperSU and thing needed to root the phone
ADB Setup EXE called: "adb-setup-1.4.3.exe" Needed to install ADB and the Drivers
Special patched Odin that skips the SHA 225 called: Odin PrinceComsy.exe (Mainly for AT&T)
.ini file named: "Odin3.ini"
Last, file, named: "Samsung_G935x_QC_Rooted_BOOT.TAR", this is the engBoot for the phone.
NOTE: Some users have experienced endless boot loop; this seems to be caused by using a package disabler that disabled certain services.
If you used one and end up getting an endless boot loop try wiping the cache and factory reset the phone.
I suggest you backup your phone before doing this, just in case something happens.
Install ADB by running adb-setup-1.4.3.exe
Make sure to put your phone into downloading mode (Power off--- Hold Down arrow + Home + Power button)
Open up Odin and click AP and mount Samsung_G935x_QC_Rooted_BOOT.TAR
Once restarted put the phone into USB debugging mode (Need Developer options for this)
To get developer mode, go to "About" then tap "build number" about 6 or 7 times
Go back to settings and you should now see developer options, turn on USB debugging
Now back on your PC, Move the folder named "su" into your ADB folder (Default Path: C:\adb)
Run CMD by either Win + R and typing cmd or from the control panel.
Once CMD is open type this
Code:
cd C:\adb\su
or whatever your path to your "su" folder.
After that type root.bat
Wait for the CMD to finish and then your phone should restart
Once your phone has finally restarted you will notice that SuperSU was installed and root should be working, download root checker to find out for yourself.
If your CMD just says starting Daemon and doesn't proceed any further than that, then you forgot to make sure USB debugging was turned on.
If everything went well you will see the CMD was able to push SuperSU.
You can now install Xposed via Flashfire. Unfortunately, TWRP does not work on this method, so, DO NOT TRY, there is a chance that you can Brick your phone from doing that.
NOTE: DO NOT UPDATE THE SU BINARY!
Fix for wifi bug on restart: http://forum.xda-developers.com/tmo...ticky-root-t3327399/post67592828#post67592828
Thanks 2swizzle for mentioning this.
If you want to fix the lag/slowness download any CPU or Kernel Editor or changer.
This one works fine: https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor&hl=en
To fix the lag
Open up the APP
Go into the CPU settings
Set CPU Governor to ondemand
Apply on boot
Thanks to orgulloso4202 I have found a way to fix the battery drain and help with Youtube and the CPU.
L Speed seems work fine and my battery no longer drains when using the recommended Profile.
Interesting. First Sammy I've seen that Knox is intact but Samsung Pay won't work.
Have been searching a bit after rooting mine, don't suppose anyone has word on how to or if you can install TWRP or Xposed?
AlphaD1 said:
Have been searching a bit after rooting mine, don't suppose anyone has word on how to or if you can install TWRP or Xposed?
Click to expand...
Click to collapse
Got Xposed with flashfire but sadly it left me in a boot loop on the verizon logo, think I need to start over.
If we can get the bootloader unlocked it will be fun times indeed!
Going to try this soon.
Don't care if my phone blows up, it's the 4th here in the U-S-A!
Besides my trusty Nexus 6 and even Note 5 are ready for duty!
Xposed would be nice, I do miss those features.
Layer support even just to change up the statusbar.
Themes have done a nice job to blackout the device.
Root, center clock and some battery icon customizations and I'm all set for sure.
Perhaps the horrid standby time will be fixed.
Because as of late this phone has lead to high frustration to the point where I want to see how good it skips across the lake! But when I think of how much I paid for it, well I keep it in my pocket!
TWRP doesnt work, but you can install Xposed from flashfire.
Argyrus said:
TWRP doesnt work, but you can install Xposed from flashfire.
Click to expand...
Click to collapse
So with Xposed working, that means battery saving apps like Greenify and Amplify work now for our devices?
GigaSPX said:
So with Xposed working, that means battery saving apps like Greenify and Amplify work now for our devices?
Click to expand...
Click to collapse
Not 100% sure.
I haven't really installed it on my phone. I only know Xposed work due to the countless others that tried it; however, I don't see why those should not work.
Xposed is working fine and you guys need to install a kennel app and change the engboot settings to ondemand, that's why it lags and slow
2swizzle said:
Xposed is working fine and you guys need to install a kennel app and change the engboot settings to ondemand, that's why it lags and slow
Click to expand...
Click to collapse
Root gives performance issues??
GigaSPX said:
Root gives performance issues??
Click to expand...
Click to collapse
Negative. The eng kernel has shown some lag and performance slowdowns for some people but can be remedied by changing the governor.
Sent from my SM-G935V using Tapatalk
MisterSprinkles said:
Negative. The eng kernel has shown some lag and performance slowdowns for some people but can be remedied by changing the governor.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Which governer do you recommend we use for optimal performance?
zachchen1996 said:
Which governer do you recommend we use for optimal performance?
Click to expand...
Click to collapse
Would seem the consensus is on-demand.
Sent from my SM-G935V using Tapatalk
Am I missing the download files for Verizon or are they not posted here
Can anyone report that they are suffering overheating issues after rooting even after a FDR? Thanks!
shawnten said:
Am I missing the download files for Verizon or are they not posted here
Click to expand...
Click to collapse
They are posted here: http://forum.xda-developers.com/tmobile-s7-edge/how-to/how-to-root-s7-edge-t3410470
I guess maybe I should make a thread here with all the download links and some other links that fix things.
Thread updated!
Added links and more stuff.
farfromovin said:
Interesting. First Sammy I've seen that Knox is intact but Samsung Pay won't work.
Click to expand...
Click to collapse
If you try opening the app you will get a message saying: "Access denied. Unauthorized modifications have been made to your device."
I am guessing that the app has some other type of security that checks if phone has been modded.
Anyone tried to unroot? Does Samsung Pay work if you revert NB to stock?
Sent from my SM-T320 using Tapatalk
How do we install xposed with flashfire?
Alright. So here it is. OnionRoot. ver 1.0.0
How does it work?
Same as default root with modifications of fixing the lag after you root.
This is early and it takes about a minute after you boot for OnionRoot (app) to fix the lag. DON'T WORRY, I am still trying to find a way to run the onion_root.sh script when the device is booting. It will be updated to fix this but it does what it is so far intended to do, remove lag.
Steps?
RECOMMENDED! Restore to stock firmware AP,CP,CSC,BL! Android 6.0.1
1. Put device into download mode
2. Flash Samsung_G935x_QC_Rooted_BOOT with Odin PrinceComsy.exe in AP
3. You device will lag like aids, I know. This is due to the fact that you flashed a version of the boot for samsung engineers. Go to settings and enable developers options and enable USB debuggging. You should know this by now.
4. Open your device. It should be at the homescreen. Now run part1_rooting.bat
5. Your device should be rebooting. After its done, open it and go to the homescreen again and run part2_after_rooted.bat
6. After running part2_after_rooted.bat your device will reboot again. It will install busy box for you and onionroot. Open busybox first and grant SU access. wait for all packages to download and install to /system/xbin
7. Open OnionRoot and tap manually lag out. This will ask you for root access, grant SU access. Tap it again just to be sure it ran the CPU governor script and give it about 30 seconds. Manually lag out doesnt lag your device, I know how it sounds, it actually switches your CPU governor to ondemand in order to make it run better without lagging like crap.
Now you should be good to go! Every time you reboot your device, OnionRoot will take a minute to execute the script to remove lag without having you to do anything! I am working on a MUCH better way of executing the script. I need to find out a way to execute the onion_root.sh script before the device boots up completely. If you have any ideas, let me know! Any suggestions on what to add, I am reading and listening. I am always looking for better ways to improve this root tool and make it fix performance without downloading so many apps and running them to make sure your device runs smoothly and not kill your battery.
P.S. I am open to ANY suggestions to make this better, we can make this open source too if you'd like
(edit) Should I also add a little fix to remove the notification pop up that says : "Security notice" Unauthorized actions have been detected blah blah ?
Thank you.
-SentoDev_ aka silentwind827
Download OnionRoot.rar
I'm all for development, but why make another thread when you have one other one about this tool?
Thanks, I performed all of your steps and it works well for me. I needed to perform a clean wipe, so I'm glad you posted this at the right time. The only issue now is to make OnionRoot autmatically start after boot up.
StrumerJohn said:
I'm all for development, but why make another thread when you have one other one about this tool?
Click to expand...
Click to collapse
I'm kinda new to xda and how posting works
Can you do this from APK1?
S7 SM-G930T Root Deleting Apps on Restart
Hi SilentJoe,
I had a rooted Samsung S7 that worked perfectly until I restart or power cycle. When I restart it will come back showing several user installed apps as "not installed" but with the icons still there. Then the power cycle started deleting the Google app and Play Store app. I ended up having to reload stock rom and reset and am trying to determine if there is a stable root available for the SM-G930T? Let me know if you are having any luck with your method listed in this post?
Here's My Config:
Phone - Samsung T-Mobile S7 SM-G930T
Baseband - G930TUVU3APG1
Android - 6.0.1
Root Used - Samsung_G930x_QC_Rooted_BOOT.TAR
Root Patches - S7_or_S7Edge_Fixes_V15.zip (MD5 hash F15CD9BDC35382A8F48FFBEDBB1BCDF0)
SperSu - V.2.79
Any feedback would be greatly appreciated. Thanks in advance for all of your efforts!
-Todd
Thanks,
-Todd
cogancorp said:
Hi SilentJoe,
I had a rooted Samsung S7 that worked perfectly until I restart or power cycle. When I restart it will come back showing several user installed apps as "not installed" but with the icons still there. Then the power cycle started deleting the Google app and Play Store app. I ended up having to reload stock rom and reset and am trying to determine if there is a stable root available for the SM-G930T? Let me know if you are having any luck with your method listed in this post?
Here's My Config:
Phone - Samsung T-Mobile S7 SM-G930T
Baseband - G930TUVU3APG1
Android - 6.0.1
Root Used - Samsung_G930x_QC_Rooted_BOOT.TAR
Root Patches - S7_or_S7Edge_Fixes_V15.zip (MD5 hash F15CD9BDC35382A8F48FFBEDBB1BCDF0)
SperSu - V.2.79
Any feedback would be greatly appreciated. Thanks in advance for all of your efforts!
-Todd
Thanks,
-Todd
Click to expand...
Click to collapse
This was developed for S7 Edge, not the regular S7. Also are you saying that you did this when you rooted with my tool?
uniphase said:
Thanks, I performed all of your steps and it works well for me. I needed to perform a clean wipe, so I'm glad you posted this at the right time. The only issue now is to make OnionRoot autmatically start after boot up.
Click to expand...
Click to collapse
OnionRoot does start to run its script at start up, but it doesn't do it while booting. It activates the script after your device has completed booted. Try it, boot you device (if you rooted with OnionRoot) and youll see a toast message popup saying "Lagged Out". This means it removed the lag and should make your device run smoothly. I am working on ideas how to make the script run while the device is in booting stages and completely remove lag due to the flash with odin of eng_boot.tar. Thanks.
S7 SM-G930T Root Deleting Apps on Restart
No, I did not use your tools or method. The previous method I used listed as S7 or S7 edge. Do you recommend trying your method? Has it been stable? Thanks for your reply. -Todd
silentwind827 said:
This was developed for S7 Edge, not the regular S7. Also are you saying that you did this when you rooted with my tool?
Click to expand...
Click to collapse
Gotta go get my laptop from home. Gonna do this at work.... Can't wait. Thanks
Sent from my SM-G935T using XDA-Developers Legacy app
cogancorp said:
No, I did not use your tools or method. The previous method I used listed as S7 or S7 edge. Do you recommend trying your method? Has it been stable? Thanks for your reply. -Todd
Click to expand...
Click to collapse
Follow these intructions and let me know if it worked. NOTE: you should restore EVERYTHING before rooting in order to make sure you didnt leave any data behind and have a fresh stock rom before rooting. Dont forget to wipe partitions and factory reset in recovery!
cogancorp said:
No, I did not use your tools or method. The previous method I used listed as S7 or S7 edge. Do you recommend trying your method? Has it been stable? Thanks for your reply. -Todd
Click to expand...
Click to collapse
Follow these instructions and let me know if it worked. NOTE: you should restore EVERYTHING before rooting in order to make sure you didnt leave any data behind and have a fresh stock rom before rooting. Dont forget to wipe partitions and factory reset in recovery!
Got it. I will let you know how it goes. Thank you again! -Todd
silentwind827 said:
Alright. So here it is. OnionRoot. ver 1.0.0
How does it work?
Same as default root with modifications of fixing the lag after you root.
This is early and it takes about a minute after you boot for OnionRoot (app) to fix the lag. DON'T WORRY, I am still trying to find a way to run the onion_root.sh script when the device is booting. It will be updated to fix this but it does what it is so far intended to do, remove lag.
Steps?
RECOMMENDED! Restore to stock firmware AP,CP,CSC,BL! Android 6.0.1
1. Put device into download mode
2. Flash Samsung_G935x_QC_Rooted_BOOT with Odin PrinceComsy.exe in AP
3. You device will lag like aids, I know. This is due to the fact that you flashed a version of the boot for samsung engineers. Go to settings and enable developers options and enable USB debuggging. You should know this by now.
4. Open your device. It should be at the homescreen. Now run part1_rooting.bat
5. Your device should be rebooting. After its done, open it and go to the homescreen again and run part2_after_rooted.bat
6. After running part2_after_rooted.bat your device will reboot again. It will install busy box for you and onionroot. Open busybox first and grant SU access. wait for all packages to download and install to /system/xbin
7. Open OnionRoot and tap manually lag out. This will ask you for root access, grant SU access. Tap it again just to be sure it ran the CPU governor script and give it about 30 seconds. Manually lag out doesnt lag your device, I know how it sounds, it actually switches your CPU governor to ondemand in order to make it run better without lagging like crap.
Now you should be good to go! Every time you reboot your device, OnionRoot will take a minute to execute the script to remove lag without having you to do anything! I am working on a MUCH better way of executing the script. I need to find out a way to execute the onion_root.sh script before the device boots up completely. If you have any ideas, let me know! Any suggestions on what to add, I am reading and listening. I am always looking for better ways to improve this root tool and make it fix performance without downloading so many apps and running them to make sure your device runs smoothly and not kill your battery.
P.S. I am open to ANY suggestions to make this better, we can make this open source too if you'd like
(edit) Should I also add a little fix to remove the notification pop up that says : "Security notice" Unauthorized actions have been detected blah blah ?
Thank you.
-SentoDev_ aka silentwind827
Download OnionRoot.rar
Click to expand...
Click to collapse
I think I will try to fix the ENGBOOT.tar kernel files so the device doesn't lag that much and drain the battery or might just move on to trying to figure out a possibility of unlocking bootloader which is highly unlikely.
Iomo said:
Can you do this from APK1?
Click to expand...
Click to collapse
What do you mean? Its possible but useless you'd still need to flash ENGBOOT.tar with pc on odin
Easy install. Snappy so far.
Is it okay to update SuperSU via playstore?
Can't Continue, Phone Not "Properly Rooted"
Hi i followed the steps but after getting to the busy-box app it says root isn't properly installed i re-did this about 2 times and still the same message.
silentwind827 said:
OnionRoot does start to run its script at start up, but it doesn't do it while booting. It activates the script after your device has completed booted. Try it, boot you device (if you rooted with OnionRoot) and youll see a toast message popup saying "Lagged Out". This means it removed the lag and should make your device run smoothly. I am working on ideas how to make the script run while the device is in booting stages and completely remove lag due to the flash with odin of eng_boot.tar. Thanks.
Click to expand...
Click to collapse
Something that may work is creating a /system/su.d folder and placing the script in with 7xx permissions.
I have Engineering Root for latest 7.0
OK so after reading a bunch on rooting the different firmwares I went ahead and gave the root a shot on our 935P running PK1. It was successfully rooted and runs with no lag whatsoever, no reboots, and LTE is working as well as voice and MMS. I did not make any of the needed files I just found them on XDA and put them to use. Please make sure you thank the devs for this would not be possible without them. Here are the steps I took:
1. Download the following items on your Windows PC:
A. ADB
B. Odin found at http://www.filedropper.com/princecomsyodin
C. Stock PK1 TAR
D. The engineer boot.img from the thread labeled root 10/25 found at http://www.filedropper.com/samsungg935xqcrootedboot
E. The SU install package from same thread found at https://download.chainfire.eu/970/SuperSU/SuperSU-v2.76-S7QC.zip
2. With phone in DL mode use Odin to flash all 5 items of stock PK1 TAR. Let phone boot up and activate on the network.
3. Download Package Disabler from Play store and use it to disable the following items:
A. Bootagent
B. Carrier Setup Wizzard
C. Chameleon
D. Com.android.carrierconfig
E. MobileInstaller
F. SAE
G. Samsung DM Phone Interface
H. Samsung DM service
I. Setup Wizzard
J. securityLogAgent
4. Power off phone and start in DL mode
5. After installing ADB open up Odin and click AP and select the engineer boot.img file
6. With phone in DL mode connect to PC and flash boot.img through Odin (once complete phone will boot up)
7. Once phone boots up run the Root.bat script. After a successful run the phone will reboot and SuperSU will be installed.
8. Download build.prod editor from Playstore
9. Use build.prop editor to change the following 3 items:
A. ro.cdma.default_alpha from chameleon to sprint
B. ro.cdma.default_numeric from 310000 to 310120
C. ro.build.characteristics from Chameleon to Sprint
10. GoTo settings, security, other security settings and turn off automatic updates.
11. Reboot
12. Install Wireless Tether Router from Playstore
13. After install open and set desired broadcast name and password DO NOT change anything else.
14. Turn your phone's Wifi on
15. Hit Enable Wifi Router and grant SU permission when asked.
Your 935P on PK1 is now rooted with working LTE, voice, MMS, and hotspot.
thank you very much for your help. i confirm that this solution works on PL6 stock and everything like you said is working. This is what i did.
i followed everything you listed except 3 things.
1) i needed stockfile for PL6 and when unzipped i used 4 files . for the csc file i used home, so it preserves data.
2) for part I i didn't know which wizard setup, lol so i disabled both.
3) i also added securityLogAgent. to the disabled list, because i kept getting that notification that if u click it. it reboots and gets rid of root.
thank you once again, and once again this is working on PL6, just make sure u download PL6 stock
going totry this on pl6 today. wish me luck. any more tips for trying this on pl6? what "home" file did you use?
stebomurkn420 said:
going totry this on pl6 today. wish me luck. any more tips for trying this on pl6? what "home" file did you use?
Click to expand...
Click to collapse
Did you try this?
This worked flawlessly for me thanks
Sent from my SM-G935P using Tapatalk
hotrodssnova said:
Did you try this?
Click to expand...
Click to collapse
i sure did... it does work... there are a few minor snags i ran into but nothing i couldnt figure out. This method is definitely not for noobs. lol. not saying you are just proceed with caution.
With the update so close, im on the fence.
hotrodssnova said:
With the update so close, im on the fence.
Click to expand...
Click to collapse
What update are you referring to? I'm assuming 7.0? Any idea when it's coming out?
I got the update yesterday.
Could you link which package disabler you used? Some of them have been removing some of the packages that you can disable (im guessing from pressure from samsung).
Also, what did you do to get no lag?
Thanks!
stebomurkn420 said:
going totry this on pl6 today. wish me luck. any more tips for trying this on pl6? what "home" file did you use?
Click to expand...
Click to collapse
How'd it go? Looking to do this on PL6.
Hey guys. Im having some problems with this method because of ADB.
I flash the boot.img but once I run root.bat it goes though everything fine until I get to the line "adb install -r SuperSU-v2.76.apk" an error appears from adb saying "Error could not access the package manager. Is the system running?"
Ive tried making it the specific path. ex: "adb install -r /sdcard/Download/SuperSU-v2.76.apk" and stuff like it. (Im also not sure if its installing the apk from the file on the phone or the folder on my PC.
Any help would be appreciated. Running PK1 S7 Edge Sprint.
on top of this my phone just vibrates and lands at the Sprint LTE screen while it doesnt do anything. This is probably the problem. But I have the same version as #1 so whats the problem?
Goongydin said:
OK so after reading a bunch on rooting the different firmwares I went ahead and gave the root a shot on our 935P running PK1. It was successfully rooted and runs with no lag whatsoever, no reboots, and LTE is working as well as voice and MMS. I did not make any of the needed files I just found them on XDA and put them to use. Please make sure you thank the devs for this would not be possible without them. Here are the steps I took:
1. Download the following items on your Windows PC:
A. ADB
B. Odin found at http://www.filedropper.com/princecomsyodin
C. Stock PK1 TAR
D. The engineer boot.img from the thread labeled root 10/25 found at http://www.filedropper.com/samsungg935xqcrootedboot
E. The SU install package from same thread found at https://download.chainfire.eu/970/SuperSU/SuperSU-v2.76-S7QC.zip
2. With phone in DL mode use Odin to flash all 5 items of stock PK1 TAR. Let phone boot up and activate on the network.
3. Download Package Disabler from Play store and use it to disable the following items:
A. Bootagent
B. Carrier Setup Wizzard
C. Chameleon
D. Com.android.carrierconfig
E. MobileInstaller
F. SAE
G. Samsung DM Phone Interface
H. Samsung DM service
I. Setup Wizzard
J. securityLogAgent
4. Power off phone and start in DL mode
5. After installing ADB open up Odin and click AP and select the engineer boot.img file
6. With phone in DL mode connect to PC and flash boot.img through Odin (once complete phone will boot up)
7. Once phone boots up run the Root.bat script. After a successful run the phone will reboot and SuperSU will be installed.
8. Download build.prod editor from Playstore
9. Use build.prop editor to change the following 3 items:
A. ro.cdma.default_alpha from chameleon to sprint
B. ro.cdma.default_numeric from 310000 to 310120
C. ro.build.characteristics from Chameleon to Sprint
10. GoTo settings, security, other security settings and turn off automatic updates.
11. Reboot
12. Install Wireless Tether Router from Playstore
13. After install open and set desired broadcast name and password DO NOT change anything else.
14. Turn your phone's Wifi on
15. Hit Enable Wifi Router and grant SU permission when asked.
Your 935P on PK1 is now rooted with working LTE, voice, MMS, and hotspot.
Click to expand...
Click to collapse
Hello, i am currently running PJ2 on my samsung edge, do you think i should use the root method for pj2 or take the update to pk1 and then root?thanks in advanced
razzrmaxx said:
Hello, i am currently running PJ2 on my samsung edge, do you think i should use the root method for pj2 or take the update to pk1 and then root?thanks in advanced
Click to expand...
Click to collapse
I can confirm pk1 method works. Not sure about root on pj2.
After obtaining root from the OP I downloaded the current stable SuperSU 2.79 flashable zip. I flashed it from FlashFire. I received a security warning. Custom binary blocked by SECURE BOOT (boot.img). I then flashed the OP engineer boot.img in ODIN. this fixed the update binary issue, woot, and rebooted again fine.
I also got this to work on the third try on pj2. The first two were one hundred percent my mistake as both times I missed something very plainly stated in the OP. I would say to anyone experiencing difficulties to read over the threads where the OP files originate. That's what allowed my bone head to see what I was doing wrong. I can't believe I finally have root and hotspot! Thank you for all the hard work folks!
Oh man. Do you even know how much you helped me out. I have succesfully rooted 7.0 on my s7 edge. Will post tutorial soon, much credit to you sir you are awesome.
Edit:https://forum.xda-developers.com/sprint-s7-edge/how-to/sm-g935p-spr-root-nougat-7-0-data-t3568780
I can confirm this works 100% on PK1. Thank you so much
Any of you have any tips on fixing the lag? I love root but might go back due to lag and battery drain