Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
goja said:
Hello,
Is there a way to make SuperSU/SuperUser less slow? I mean, on a virgin rom it's already not so fast, but after you install your apps, it can takes minutes before the pop-up asking for root rights comes, if it comes..!! So is there a way to "fix" that? It's a pain, having to reboot sometimes cause of that!
Thanks.
Click to expand...
Click to collapse
Set it to automatically grant permissions and turn notifications off, but remember that this is very insecure way so don't install any untrusted apps.
I've thought of that, but i'm not sure it would help : If it waits, let's say 2minutes, for showing pop-up asking for rights, then it would also wait 2minutes before automatically allowing apps...
2 minutes?? It should show immediately, so there is something wrong in your rom. Try to wipe cache and dalvik cache and fix permissions.
Man, this is not in MY ROM, this is in ANY roms... Seems that the more apps installed (=the more process running) the slower it'll be!
I agree. I have the same problem. I'm running CM13 (Marshmallow) on my old S3 i9300, and I flashed SuperSu (beta) for it. It work well, but its slow to grant permissions even when its meant to do so automatically. I've set it to start at boot, but this hasnt done much. Any fixes??
Same problem also here with every rom that I used it. Root in cm roms is almost instant.
same here on a custom cm12.1 rom
What the heck are you guys talking about? 2 minutes?! That is just plain wrong. I won't say impossible, cause you obviously have problems, but I have never seen that behavior you're talking about, and that is absolutely not caused by SuperSU or Superuser. Even my 7 years old HTC HD2 asks for, or grants root in 2 seconds max. Tell your developers to fix their ROMs.
Sent from my HTC One M9 using Tapatalk
Can it be that "Clean Master" or some other memory management software is pushing SuperSU back. Try uninstalling any memory management software.
never had issue having to wait for 2min either and ive rooted almost 50 diffrent phone from ics to lollipop to my current headache oppo mirror 5 still superSU still doing its job
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum¡*
Ur thread will b moved immediately.
BatDroid said:
check if any other app stopping it.
I always update su binary, set the access to grant and delete su app.
Its d fastest way.
Read rules before posting questions on development forum�?�¡*
Ur thread will b moved immediately.
Click to expand...
Click to collapse
â?¦
I don't even know how to process this ?¦ try my way first¦
I'd bet anything the speed will be just as fast¦ and i forgot to mention, i always enable full logging? so full logging, no lag?vs no nothing, no app, security etc
loogielv said:
I can confirm this is a real problem, but can also confirm it goes away with tweaking.
On aosp, it's important to disable the native su in dev options.
In anything else, for instance touch wiz, I have learned that system less root is evil, and mount separate name spaces is the devil.
Now, when installing prerooted rom, kernels etc, it's imperative to get your supersu set up prior to installing your root apps...or it will hit the fan....well..that's dramatic. It'll act oddly and you'll never realize what's causing things to be weird.
First and foremost, uncheck mount separate blah blah and reboot. Then, attempt to install supersu to system. If it fails after reboot, twice, then you must return the check mark to mount name spaces and reboot.
Once rebooted, try the "cleanup for reinstallation" and if that succeeds in allowing you to update/reinstall from play store, try to uncheck the mount name spaces again...then attempt the system install again...should work this time...
EDIT the point of all this is to test the app and the connection with the binary. If the app can't control the binary stuff, you'll probably be seeing lag. By doing all the options and checks that tweak the binary, you will have a good supersu environment, and the lag will disappear.
When you finally get supersu to do the things with its binary without crashing, you'll notice no more lag.
Further more, disabling notifications is an ABSOLUTE MUST. From @Chainfire himself, he suggests turning off notifications to get rid of overhead, and he states that logging does not effect it much, and after HUNDREDS of man hours tweaking and fiddling with supersu in every arena, from system less, to autoroot, I could not agree more.
Throw the man some love, respect, and donations, because he's at the front of the pack, hacking the infinite combinations of phones, to couriers, to software, to user intelligence.
His app is rock solid. The billions of other x factors are to blame
2nd edit mount name spaces will cause all sorts of odd things, so I disable that always, as well as notifications.
It's important to note, you'll always have delay for root requests in the first few minutes after boot, as certain things like scripts and even supersu itself might be denying for the first few minutes.
Enabling supersu at boot might help, actually it will help, but I've never needed it after configuring my root environment properly.
When everything fails, I Uninstaller root completely, and either reflash supersu, or my prerooted kernel of choice
3rd edit. Sigh, sorry. I notice my environment is in need of tweaking nearly 100% of the time when I flash a prerooted kernel, then a prerooted rom. Even flashing the kernel again, as is sometimes required for a rom not tailored for my device, will cause things to get out of wack which I notice instantly, when I got supersu lag
Click to expand...
Click to collapse
As he said i have dissabled notifications and worked, Thanks Man
I've had this problem on a Samsung Galaxy J7 (2016). It was because I disabled the encryption of /data. For details on how to solve it see here. I think there are probably other factors that can cause this, so this solution is probably not for everyone. But I would recommend checking your adb logcat to figure out if something is going on in the background that should not.
Since I installed SuperSu 2.79 on my klte on RR (los, android 7.1.1) the device started lagging, not a lot but enough to be annoying.
Related
I've just tried to download my first rented movie on Google's Play Videos. I got the error that many have gotten for a long time "won't install on rooted device." I know that the OTARootKeeper exists for truly rooted devices, but my Nook isn't really "rooted," right?!? because it's still the original NT, just booted with Team B's SD Card CM7 most recent release.
My question is, should i used OTARootKeeper to allow me to download rented videos or is there a better way to handle this "bump in the road" of not being able to download a rented moving?
I am a noobie, however I've done lots of looking on line as well as searching forums and reading about past people's challenges with Google Play (Market).
As a final note, I do want to download b/c I want to watch on a plane flight vs stream through YouTube or watch live streaming.
Thank you for your help in advance!
To address the first part of your premise, your device is rooted.
Root means "root access" i.e. you have access to the root directory of the device. What you and many others think it means is "stock rom rooted" but this is a misinterpretation of the meaning "rooted." Your device is running CM7 which happens to be a "rooted" rom. In fact, the official Cyanogenmod team has decided to make future rom releases "not rooted" on upon initial flashing, though root access can be gained by toggling it in developer settings. I have even come across "unrooted" custom roms, meaning that they are custom versions of android, but much like many manufacturer ones, root access is not enabled "out of the box."
Now as to using Google Videos, I believe voodoo rootkeeper does not work for this purpose anymore. I think there is an app called "Super SU" that allows it, but I don't remember the exact setting you need to toggle to enable it. I'll report back after I test on my tablet.
Edit: So this is the app you want to use. In it, go to settings and toggle "Enable Superuser." You should then be able to use Google Movies. When you're done, just go back to SuperSU and toggle that setting again.
error --
Thank you so much first for the Rooted clarification and second for the SuperSU install information. Once I download from SuperSU and open it, I get the following error from SuperSU and am not sure what to do about it..."There is no SU binary installed, and SuperSU cannot install it. This is a problem!" Help please!
I am having the same issue on my Nook Color. I've tried SuperSU but it fails on the binary installation. When I try using Voodoo I get an SU Protected error.
Am I missing something? This process is usually brainless and I really would like to rent a movie through Google Play to watch on my trip.
Any help on temporarily circumventing the root issue would be greatly appreciated. Is this a CM7 issue?
Sent from my NookColor using XDA
still needing help - pretty please!
EDITED: I'm wondering if a solution from another post may work for this challenge. Some people have had trouble downloading certain apps so they edited the build.prop to remove any "Nook Tablet" and replaced it with "XOOM" and said from that point they didn't have any trouble downloading. Unfortunately I'm not quite enough of an expert to know how to edit the build.prop on my device, so I'm wondering if someone can help me figure it out. cheers!
Cubanluke88 said:
To address the first part of your premise, your device is rooted.
Root means "root access" i.e. you have access to the root directory of the device. What you and many others think it means is "stock rom rooted" but this is a misinterpretation of the meaning "rooted." Your device is running CM7 which happens to be a "rooted" rom. In fact, the official Cyanogenmod team has decided to make future rom releases "not rooted" on upon initial flashing, though root access can be gained by toggling it in developer settings. I have even come across "unrooted" custom roms, meaning that they are custom versions of android, but much like many manufacturer ones, root access is not enabled "out of the box."
Now as to using Google Videos, I believe voodoo rootkeeper does not work for this purpose anymore. I think there is an app called "Super SU" that allows it, but I don't remember the exact setting you need to toggle to enable it. I'll report back after I test on my tablet.
Edit: So this is the app you want to use. In it, go to settings and toggle "Enable Superuser." You should then be able to use Google Movies. When you're done, just go back to SuperSU and toggle that setting again.
Click to expand...
Click to collapse
Thank you so much first for the Rooted clarification and second for the SuperSU install information. Once I download from SuperSU and open it, I get the following error from SuperSU and am not sure what to do about it..."There is no SU binary installed, and SuperSU cannot install it. This is a problem!" Help please!
Hi All,
i have an issue - i installed custom ROM, custom kernel, all is working except root.
I have two root apps - superuser (standard) and one from ROM supersu. One came with ROM, and i flashed another (standard) just after flash (not sure why really)
So - I have two supersusers - bot don't have root... irony
Any suggestion how to fix that? Also, how should i delete superuser (standard) from system/app folder (without root apparently)?
Thanks all!
"This app cannot be uninstalled if it was installed with your ROM or root. If there is no uninstall option, it's because you placed it in /system/app, not me. It is impossible for an app to be installed in /system/app by the Play store. In fact, the entire /system partition is read only at runtime. The only way for an app to be placed in /system/app is via a rooting process (which usually installs Superuser), or by remounting the system partition as read/write and manually putting it there."
this is from the play store page. I guess you could try using root explorer to delete it but don't know if it will work
The more important question is why don't you have root? You have two root apps installed on a custom ROM. You should be able to run SuperSU and let it update the su binary. Then you can use ROM Toolbox or TB to remove Superuser.
Posted using Tapatalk 2
That is a strange problem. Never had that issue. Some custom come with supersu already installed and don't require you to install super user from the market. In fact it dont make sense to download standard unless you have standard from Rom and want to add supersu for better root access. Try to reflash Rom first and see if that works. Don't install standard. If that don't work try another Rom.
Jsparta26 said:
That is a strange problem. Never had that issue. Some custom come with supersu already installed and don't require you to install super user from the market. In fact it dont make sense to download standard unless you have standard from Rom and want to add supersu for better root access. Try to reflash Rom first and see if that works. Don't install standard. If that don't work try another Rom.
Click to expand...
Click to collapse
That's already been suggested in the ROM thread on another site, but he seems to be trying to get around it without reinstalling the ROM. He said over there that he doesn't know why he installed SuperUser since the ROM came with another su app and neither do I. He should just go ahead and reflash the ROM.
For some reason this guy seems to want to do things differently from standard practices and then ask for help when it doesn't work. His latest post in the other thread was asking if he could flash the ROM after removing the kernel (boot.img)!
I'm not sure where he comes up with these ideas but he seems to be off doing his own thing even though he is new at this stuff. I'm not suggesting that you don't help him, but wanted you to be aware that he may be creating problems for himself.
ramjet73
Thanks for the heads up. Your right, it don't make sense to try something different if what we suggest to somebody has been a better and usually a full proof way of fixing a problem. But like you said if he wants to add to his own problems that's on him. Let's make this clear to him too since he is new. Nobody on this site or other sites are responsible if you blow up your device, your gf leaves you, or you burn down your house and get fired. :highfive:
So I used the ACS/Shabbypenguin root method (do a Google search, I can't post links...) and followed the directions exactly. Well almost exactly, I knew of some issues so this is what I did...
First I downloaded Superuser & Superuser Elite (I previously paid for it on a different phone).
Then I downloaded the drivers and Odin and both kernals.
I installed the drivers and put my phone into development mode.
Next, I turned off my phone then turned it back on in download mode and flashed the pre-rooted kernal as per the instructions there.
Finally, I went through the process again to flash in the stock kernal.
Now the other users had issues with USB connection and the phone not being recognised, the answer to that was on page 11 of the above linked thread (editing the vold.fstab file). I did this (using ES Root Explorer) as per the instructions and restarted.
Things seemed fine for half a day. Now my phone randomly restarts, but not always randomly. I can perform specific actions to cause it to freeze and reboot (example, simply opening the vold.fstab file does this EVERY TIME, but I was able to copy/paste it to the SD card and then open and edit it and even copy/paste it back, all using ES root explorer, and no crash/reboot unless I open it specifically and yes, that's with having the system mounted as R/W).
Another thing I noticed since rooting, and it still has maintained the rooted status, is that any time my phone restarts or I restart it, I open the system tray and this stupid "tip" toast message comes up that, prior to rooting, only came up once. Now, it comes up only once after a restart but resets every time.
I tried to sign up for the ACS forums but for some reason, I've not gotten a single registration e-mail from them and messaged half their admin with no response (the fact that the site has no cancel account and no re-send activation option troubles me enough as it is and in my opinion, should be internationally illegal).
Anyway, that's the issue, I need to resolve these random restarts, which may or may not be caused by this vold.fstab file.
Also, I connect now (before when I did the fix, it worked), the computer doesn't recognise the phone so I can't even re-flash using Odin, but the phone works (until randomly restarting which is a pain...), so I am at a loss as to what the actual cause was and since nothing I change sticks when it restarts, I have no idea what the deal is.
Some more information...
Nothing I change sticks. I have programs that I uninstalled, but they still show up in the system tray after a reboot (if I click it, it says that the program is not installed, but it still shows up).
I tried swapping back the original build.prop - didn't stick.
I tried factory data reset - didn't do anything.
I tried a restore in BusyboxPro (stericon or something is the dev) - restored but there were some "errors".
Tried temporarily unrooting (Superuser Elite) - nothing.
I read about a power button issue - my power button is fine.
There is something wrong specifically with the OS in some way that certain actions cause it to freeze and restart. I have a game, "Deathworm" that I can play with no issues or freezes. I can do a few things but:
if I get on the mobile browser, sometimes it will freeze and reboot.
if I run AppManagerPro III, sometimes it crashes when calculating the cache size (always when it gets to 70/125 or whatever the total is, but always at 70 if it DOES crash).
Now I went into task manager and went through and cleared all the app data individually app per app. Before when I tried to do this (before restoring in Busybox, before restoring the original build.prop, etc), it would crash when I went into the downloaded tab of the thing to clear the cache. This time it didn't crash on me.
Other root stuff I have installed which was working before the random rebooting issue:
Script manager (free) and V6 supercharger (also unsupercharging wouldn't stick, which I tried before restoring the build.prop manually)
SuperUserElite
App Manager Pro III
SD Maid Pro
ES File Explorer (free version I think)
BusyBox Pro
SU Update Fixer
Screenshot It
After everything I just did, it seems to (for the moment) be working again, I am just waiting to see if it crashes again. So far I have opened and closed App Manager Pro III a few times and it calculated cache sizes with no crash. Right now, SD Maid Pro hasn't crashed yet open, hide certain tabs (clearing the data so I had to reset those options), close, reopen, scanned with system clean and app clean and actually did the app clean, so far no crashes (my phone would normally have crashed by now), cleared databases and no crash.
Also while I was in there, two programs I uninstalled via the system tray (menu button, edit, uninstall) that kept coming back were a buld.prop editor and some wonkey game (Fall down) or something, anyway those were in the downloaded section of task manager and I uninstalled them through there. Maybe that did it?
And no... still freeze, reboot and not saving any changes.
So far I've also tried uninstalling practically everything I installed and those changes aren't persisting (the uninstalled apps remain uninstalled, but reappear in the system tray or on the home screen if I had an icon there for it).
No changes I make to anything persist except things I save or copy to the SD card.
Tried factory reset again, still didn't stick.
So apparently SOME others have this issue without rooting, I can't tell, there's not a ton of reviews that I can find beyond "F*** STRAIGHT TALK CUSTOMER SERVICE THIS PHONE IS CRAP".
I hate to keep bumping this, but every time I have an issue, I am highly detailed in things and I NEVER EVER have EVER gotten a response EVER on this site, EVERRRRRRRRRRRRRR.
I really really really don't want to waste another ~$200 for nothing.
I would appreciate even a response of "yeah I have this problem too".
I don't want this to die like all the other threads I started...
Does anyone even have a clue as to where I can begin attempting to troubleshoot this on my own then?
What tools should I look into or what logs in what folders?
I know this post is very outdated but there may still be someone tinkering with these older phones still as I am.
Over the past few days I have been trying to get this Straight Talk Samsung Galaxy Proclaim rooted and working just for something to do.
I'm not one to ask for help to often so I end up doing a lot of reading and a lot of trial / error.
In my reading I have seen quite a few posts / comments around the net stating not to use the Shabbypenguin root method
as it is very buggy and unstable.... I can not tell you from experience so please do not quote me. I ended up using the TeamProlusion
root method and all has went very well other than a few minor problems I need to work out.
In all honesty I'm not real sure what I may post or may not.... ( Yes I need to REread the rules for sure ) but I
will leave this link for anyone that may be in need... Mods / Admins please feel free to edit this post if this is not permitted and
please accept my apologies.
Please google androidarea51
(This is a thread @POWerSUrgeSW3 and I will be maintaining and checking regularly, so if you have any questions feel free to ask. We will always try to post a root method for the latest firmware version once we figure it out, so expect us to be updating this thread as firmware updates roll in)
Nougat Root Method SM G930P QG1 (Latest):
(Start from a CLEAN ODIN INSTALL of Nougat. If you need Nougat, go here: http://updato.com/firmware-archive-select-model?record=2C3C1C6245EF11E7963AFA163EE8F90B .
1. Go through initial activation process; Turn WiFi on and let the phone register through WiFi; log into Google and Samsung accounts if desired
2. For WiFi Calling to work, click on Sprint Zone, this will load a bunch of Sprint software. This will also load the WiFi Calling APK needed for later. The rest of the unused Sprint software can be debloated after rooting the phone.
3. Test WiFi Calling, to ensure it connects through your Wireless connection.
4. Disable AlwaysOnDisplay under the Display under Settings. This can be enabled again after the rooting process is completed.
5. Go into System updates; disable ‘Download updates automatically’.
6. Next, go back into Settings -> About Device -> Click build number 7 times to unlock developer options.
7. Under Developer Options, enable OEM unlock, and USB debugging; turn off Auto update system and verify apps over ADB
8. Go into ‘Lock screen and security’ -> other security settings -> turn auto update off
9. If a PIN has been entered for security: Lock screen and security -> Secure startup -> Do not require – Otherwise root will not be active on startup after going through the process.
10. Install Adhell
11. Diisable these packages:
- com.android.sharedstoragebackup
- Chameleon
- Security policy updates
- SecurityLogAgents
- Samsung DM Phone Interface
- Samsung DM Service
12. Download these apps for later use:
-L Speed
-Kernel Adiutor
-BuildProp Editor
13. Turn off WiFi for the rest of the rooting process. This will ensure that any remembered WiFi passwords are saved and not erased.
14. Use Odin again to flash the engineering boot image from here: https://www.androidfilehost.com/?fid=745425885120714389 . (It goes in the AP Slot).
15. Once it reboots, download this file: https://www.androidfilehost.com/?fid=889764386195909311 . Thanks to @jrkruse for this.
Extract and run the root file.
Opt for root with tweaks, or press 2. Follow the prompt, it's fairly simple.
17. Go into BuildProp Editor, and set these values:
Set ro.cdma.default_numeric to 310120
Set ro.cdma.default_alpha to Sprint
Set ro.build.characteristics to Sprint
18. Reboot.
19. If you don't want updates to download/install, uninstall these packages:
com.sec.android.soagent
com.wssyncmldm
com.samsung.sdm
Then, remove the update file from data/fota.
20. You should have a fully functional phone now.
Thanks to:
@POWerSUrgeSW3 for helping me root nougat and for his PL6 root method (which this was based off of).
@colormedroid for his initial APE1 root method
@paul2112 for the hotspot bypass.
@JUSMEJOSE for the nougat engineering image and su.
@Chainfire for SuperSU and the other tools that have been very useful in different rooting applications
Huge thanks to @jrkruse for the modded root.bat!
@ Everyone who has contributed in one way or another to all of these different applications!
Hit thanks if I helped and enjoy a rooted nougat!
P.S: PL6 root method is located here: https://forum.xda-developers.com/sp...hmallow-pl6-marshmallow-t3573135/post71434273 .
Q&A + General troubleshooting section:
Q. Is there a hotspot bypass?
A. Yes there is, find it here: https://forum.xda-developers.com/sprint-s7-edge/how-to/hotspot-bypass-nougat-ok-t3563446 .
Q. My phone is lagging, how do I fix it?
A. For maximum performance do this:
Use the settings for L Speed as follows:
- Set the profile to performance.
- Under virtual memory, set OOM Killer to default, cache reclaiming to doubled, and cache allocation to large.
- Set the ram manager to multitasking.
- Set seeder and fstrim to run on boot.
Use the settings for Kernel Adiutor as follows:
Set both cpu governors to performance and to apply on boot.
Turn core control off and temperature throttle on under thermal.
Set the GPU governor to performance.
Debloat, first freezing and then uninstalling to ensure system stability.
SM G930U QF3 Nougat Root:
1. First, download the Universal QF3 firmware from here: http://updato.com/firmware-archive-select-model?record=8AE0CC7C625711E7963AFA163EE8F90B and flash it via Odin.
2. Completely finish activating and finish initial setup.
3. Update PRL and Profile.
4. Then enable USB debugging under developer settings and turn off verify apps via ADB.
5. Go into other security settings from lock screen and security settings, click security policy updates and turn auto updates off.
6. Turn off auto update system in developer options.
7. Disable the following packages via adhell (Knox needs to be activated in order to disable packages).
-Chameleon
-Sprint OMADM
-Sprint OMADM Phone Interface
-MDMApp
-SecurityLogAgent
-Security Policy Updates
-Security Storage
8. Flash the modified boot image via Odin, you can find it here: https://www.androidfilehost.com/?fid=457095661767149794 .
And grab Odin from here:
https://www.androidfilehost.com/?fid=673368273298965444
9. Go into connections, mobile networks, and delete the Wholesales OTA APN. Click the remaining one and edit as follows:
Name: Set it as whatever, I named mine Sprint LTE/MMS/Hotspot.
APN: n.ispsn
MMSC: http://mms.sprintpcs.com
Multimedia message proxy: 68.28.31.7
Multimedia message port: 80
MCC: 310
MNC: 000
APN Type: default,supl,mms,dun,fota
APN/APN ROAMING PROTOCOL: IPV4/IPV6
Bearer: Unspecified, LTE, eHRPD.
Click save.
Activate it (make sure the dot is filled in).
10. Run the root.bat file. (GET IT HERE: https://www.androidfilehost.com/?fid=889764386195909311 ).
(Here's how:
1. Download the file
2. Extract it.
3. Shift click and open a command/ powershell window there.
4. Type root.bat
5. Hit enter
6. Follow the command prompt.
)
11. Download and install Kernel Adiutor, and set the CPU governors to ondemand. Turn core control off, and turn VDD Restriction on. Set your GPU to simple_ondemand.
12. If you want hotspot do this:
Download and install Termux
Type "su", press enter and allow root access.
Type "settings put global tether_dun_required 0" and press enter.
Type "settings put global tether_dun_apn "APNDUN,n.ispsn,,,,,,http://mms.sprintpcs.com,68.28.31.7,80,310,120,,default,dun,mms,supl"
Turn off mobile data.
Turn on hotspot and it should work just fine.
13. Install L Speed and set your settings as such:
Go into Virtual Memory: Set cache reclaiming as Doubled.
Go into Ram Manager: Set Ram Manager as Multitasking.
Set Cleaner to run on boot.
Set FStrim to run on boot and set the FStrim scheduler to 60 Minutes.
Go into main tweaks, and set boost scheduler to 60 Minutes.
14. I'd recommend using a custom launcher (I use nova launcher with animations set to the fastest speed).
15. I'd also recommend debloating via Titanium Backup. After you remove the apps you don't want just reboot to get rid of the "This (insert app here) has crashed" message pop ups.
16.Change the animation speeds to .5 via developer options.
Enjoy your blazing fast rooted S7 with full activation and hotspot.
Thanks to @jtash01 for the activation settings for the firmware, and @paul2112 for hotspot.
YMNDLZ said:
Q&A + General troubleshooting section:
Q. Is there a hotspot bypass?
A. Yes there is, find it here: https://forum.xda-developers.com/sprint-s7-edge/how-to/hotspot-bypass-nougat-ok-t3563446 .
Click to expand...
Click to collapse
If you put this in for 5b, you should get phone and tether data simultaneously.
Code:
"APNDUN,n.ispsn,,,,,,,,,310,120,,default,mms,dun"
Otherwise, you get one or the other. Still have to do the data cycle though. Can you use sqlite for this to edit the apn?
Sent from my SM-G930P using XDA-Developers Legacy app
lvpre said:
If you put this in for 5b, you should get phone and tether data simultaneously.
Otherwise, you get one or the other. Still have to do the data cycle though. Can you use sqlite for this to edit the apn?
Click to expand...
Click to collapse
Nope, you need to use the hotspot bypass in the Q&A section.
YMNDLZ said:
Nope, you need to use the hotspot bypass in the Q&A section.
Click to expand...
Click to collapse
Ok. Not rooted, but have hotspot. Had to add something to his code to have tether data and phone data at the same time; otherwise, if I was tethering my phone data wouldn't work.
I know that method worked on mm root. Just asking.
Sent from my SM-G930P using XDA-Developers Legacy app
Currently getting a 404 error on your google drive links.
vunuts said:
Currently getting a 404 error on your google drive links.
Click to expand...
Click to collapse
Will be updated asap.
Much appreciated man. Just wanna give this method a shot and get it working!
Thank you guys so much for cracking at it and giving us this process.
vunuts said:
Much appreciated man. Just wanna give this method a shot and get it working!
Thank you guys so much for cracking at it and giving us this process.
Click to expand...
Click to collapse
Links fixed.
Outstanding job!
Rooted and everything works. Followed all instructions, everything is working, data, text, voice. currently debloating and gonna mess with some more stuff and run through my normal daily functions just to make sure it all works. If I have any issues, I shall let y'all know.
vunuts said:
Outstanding job!
Rooted and everything works. Followed all instructions, everything is working, data, text, voice. currently debloating and gonna mess with some more stuff and run through my normal daily functions just to make sure it all works. If I have any issues, I shall let y'all know.
Click to expand...
Click to collapse
Sweet! We took a good couple of days to fine tune the method before we released it, glad to know it works!
My SM-G930P / PL6 Firmware Root Instructions (Updated 07/25/2017)
UPDATED 07/25/2017
It has come to my attention some of the links listed here are outdated. All of the Google Drive links are to my my account. These are the files I collected for this process. If there are any other links that are not working, please let me know by PM.
We are keeping these instructions just because there has still been interest shown for Marshmellow.
Extra THANKS to @YMNDLZ for the continued support, and allowing me to help out where I can!
Disclaimer: This is the process I used, which I put together after a weeks’ worth of messing around and rebuilding my phone over and over. This is not the first time I have messed around doing this sort of stuff. If you are inexperienced, not sure what root/Odin/flashing is, I highly recommend keeping your phone the way it is and be happy. I take no responsibility for any damage that might come from following my process. THIS WILL VOID YOUR WARRANTY if you take your phone into Sprint and try to get it serviced. Your phone will be running an engineering version of the kernel for your phone, letting you obtain root. In addition, your battery life and performance is going to probably be different from before, and it will be up to you to tweak the kernel and other system settings to fix that.
Recommend starting over from scratch. If you already have your phone setup, I know it is not the best to start over from scratch. Nevertheless, I have tried doing this from a phone already setup, configured, and tweaked. Even though it is not rooted, something seems to screw up the process and things will not work. I had issues with MMS and hotspot not working. When I rebuilt the phone from scratch, everything seemed to work fine.
NOTE: My instructions were done using a Windows 10 Pro 64-bit computer. If you have another OS, you are kind of on your own.
ALSO TO NOTE: When I got my S7 (Not Edge), I switched to a new plan from Sprint. My plan now provides HotSpot with my contract. If yours does not, results may vary then. I am unable to test all different configurations of plans with this process.
What May Not Work: I have tested everything I could think of on my phone.
Any application that checks for Root/Custom device software (because I do not know them all). Applications like Samsung/Android Pay. In addition, snapchat, though if this is installed and logged into before the Engineering Boot image is installed, Snapchat should continue working after phone is rooted. There are some work arounds depending on the app being installed, consult the Internet before rooting. You have to make the decision whether you can accept not using the app once rooted.
WiFi Calling. I think this is because I forgot to set it up before I rooted the phone. I did not even think about it until days after I had my phone setup. Because I did not use this feature on the G930U/PL2 firmware, did not think about it. But when I came back to the PL6 firmware, I did know it was working because I was messing around with it before I rebuilt the phone another 4-5 times.
First, download the firmware from one of the usual sites:
http://updato.com/firmware-archive-select-model
http://www.sammobile.com/firmwares
http://www.sammobile.com/firmwares
Then download and extract everything from this ZIP: https://drive.google.com/drive/folders/0Bz6QOPY0cm2lblk3TUo5ZjdlanM?usp=sharing
This gives us the modified Odin we will need later, as well as the bootloader we will need.
Grab this SuperSU ZIP:
Chainfire direct link: https://download.chainfire.eu/970/SuperSU/SuperSU-v2.76-S7QC.zip
As a backup, here's my link: https://drive.google.com/drive/folders/0Bz6QOPY0cm2lcWxtOFptRzVFLXM?usp=sharing
Also grab the V15 FIX ZIP:
https://drive.google.com/drive/folders/0Bz6QOPY0cm2lUGRCSW01WHlLRHM?usp=sharing
If you don’t have the Android SDK already installed, I found this to give us the needed ADB/Fastboot options we need. You can download from this page, scroll to the bottom (linking to give them credit):
http://www.androidpolice.com/2017/0...ble-without-full-sdk-android-studio-download/
Extract the SuperSU ZIP and the ADB/Fastboot zip into the same directory for later. I recommend putting them in c:\S7files as this will make life easier in the future.
With all that done, open the Modified Odin and load the different parts of the Firmware into the associated Odin slots. Whatever the file name starts with is the slot it goes in. BL_, AP_, CP_,CSC_... now there is an extra “HOME_CSC_) file, we will not be using this and don’t worry about it. This file is if the original service settings were to be kept after flashing. As this could cause issues, I recommend not using it. If you do, you may have different results.
With all that done, your phone should be ready to start as if it was just turned on out-of-the-box. Let the phone go through its process and reboot to “install updates”. Then, it seems, Sprint is installing its software, reboots, and then loads up to the “Welcome” screen. Go through the whole process. Make sure the phone activates, which will cause a reboot and I think flashing of your SIM card (that is the image that comes up and looks like anyway). Then you can finish the activation process and log into your Google account/restore apps on your phone.
Once the launcher loads, any apps you wanted to restore is done, time to start the actual rooting process. Enable ‘USB debugging’ under ‘Developer Options’ and turn off verify apps via ADB. If you do not know how to get Developer Options to show under Settings… Google It (and might be a first sign this is not for you if you’re new to the process)
Next, while in Settings, go into ‘Lock screen and security’, scroll to the bottom to ‘Other Security Settings’, click ‘Security policy updates’ and turn auto updates off.
This next part requires purchasing Package Disabler Pro. If there is another way that you know, please try to report back. However, I bought he app and it does the job. This app will be used to disable services on a non-rooted device. The following services will need to be disabled:
(Knox needs to be activated in order for Package Disabler Pro to verify it's license)
Chameleon
Security policy updates
SecurityLogAgents
(The next ones I did from a lot of late night reading, sorry I forget where I found these)
Samsung DM Phone Interface
Samsung DM Service
CMHProvider
com.samsung.dcmservice
Now we are going to flash the Engineering Boot Image file. Again, if you are not sure how to use, or what Odin does… stop here! Run Odin, and flash the Engineering Boot image, I used the AP slot. Then under ‘options’ disable ‘F. Reset Time’.
Once rebooted, the phone is running the engineering kernel now. This is what is going to allow us to root. However, until we are rooted and do some tweaking, battery is going to drain a lot faster than expected. This is due to the kernel not being efficient with the processor/system resources. Your phone will get warm, because of the above reasons. Don’t worry, once rooted everything can be tweaked to fix this.
At this point, LTE will not be working. Also after every reboot your phone will not remember any WiFi networks it was connected to do not worry it will get those fixed down the road.
Now we are going to go through the actual root process on the phone. Connect phone to a computer via USB cable. If the phone asks to allow/deny access, ALLOW. Open up Command Prompt as an administrator on attached computer. Move to the directory c:\S7Files that we created earlier. This should be where the root.bat, SuperSU, and ADB/Fastboot files are located. Once inside this directory simply run the root.bat file.
This will execute a bunch of commands to be run on the phone; phone should reboot at least once (or twice – cannot remember). Once the phone boots up and loads “normal”, SuperSU will be loaded. I kept the phone awake while the files were being transferred over to the phone. On a few times doing this, when the phone went to sleep the process seemed to “hang” until the phone was “woken up”.
Of course we have, an older version of SuperSU is installed, but do not worry about it now. We are going to finish the process, and then update SuperSU last. That just seemed to have the best/smooth/stable results for me.
Please note, you have SuperSU access to the phone. Now you can screw it up, even possibly hardware brick the thing if you do not know what you are doing. Again, I caution if you are not comfortable with knowing what root really does or how it can affect your phone, reflash your phone back to factory using Odin NOW.
Copy the S7_or_S7Edge_Fixes_V15.zip file to your phone storage. Download ‘[root] FlashFire’ by Chainfire (In Google Play) and flash the fixes zip. This will reboot the phone a couple of times; you will see the FlashFire logo at the top and then a bunch of scripts being executed.
Download BuildProp Editor, and change the following values (use the search function at the top is easiest method):
ro.securestorage.support to false. (This fixes the phone forgetting WiFi networks on reboot)
Set ro.cdma.default_numeric to 310120
Ro.cdma.default_alpha to Sprint
Ro.build.characteristics to Sprint
Reboot the phone to apply changed.
Now another app that costs money, but this seemed to work for me over the other method mentioned by @YMNDLZ in his rooting tutorial to get HotSpot working. (found here https://forum.xda-developers.com/showpost.php?p=71118378&postcount=1021 )
Install SQLite Editor. Click on “files” tab, and navigate to:
/data/data/com.android.providers.telephony/database/telephony.db
Select ‘carriers’ and scroll down to the bottom. On my phone, it was lines 30 and 31, ‘APN2 LTE internet’ and ‘APN2 EHRPD internet’ respectively. Select each one, click the edit button at the top (looks like a pencil) and scroll down to the ‘type’ line. It should read: default,mms
click the line and add ‘dun’ to the end. The line should now read: default,mms,dun
No spaces between the words and the commas.
At this point everything should be working. If you go into the Mobile Networks and check out the Access Point Names, there should be a bunch of names listed. I have 8. LTE should be working, HotSpot, and WiFi should remember all of the names. The phone should be fully functional now, with root access, just runs hot and kills the battery. We will deal with that next. Here is the apps I used, L Speed, and Kernel Auditor. Now @YMNDLZ has his own setting recommendations for L Speed, check out the post referred to earlier for screen shots. @swick1981 also has a thread with recommendations, found here https://forum.xda-developers.com/ve...guide-to-fix-s7-lag-root-s7-variants-t3441715 . I started with both of their recommendations, one at a time, and tweaked things, as I wanted. Personally, I found that my phone still felt warm, like it the processor was still working harder than it needed to. Therefore, I hanged my settings. I suggest reading, research, testing. Figure out what works best for you. This for me seems still fast, battery lasts all day, and phone does not get hot at all. I do think I still have a bit of a nasty battery drain on LTE networks compared to when my phone was not rooted, but I am surviving with it.
L Speed: I left everything default. When the app loads and you are at the profile screen, I changed the Profile, IO Tweaks, and LNET options all to the Balance profile for each. After I changed each one, I exited the program and loaded it again. I did this because sometimes I noticed the app would not acknowledge changes to profiles. I have screen shots of my settings at the bottom of this thread. To experiment, I recommend using the BACKUP feature, and saving different options. That way you can go back to an exact configuration to try different settings without having to manually reprogram them each time.
Kernel Auditor: All I am currently using this app for is to change the CPU Governor to INTERACTIVE for all the cores. I like it because it has thermal options, if that is a concern down the road. As well as has options for the GPU. Among a bunch of other options, I doubt I will touch. However, I have a feeling maybe the GPU needs to be adjusted to help save some battery life as well… sometime I will tackle later.
Note: that on reboot or booting phone from powered off state, the stock options for the kernel are used. Therefore, my phone usually sucks about 4% battery and gets warm everytime. Then when the scripts run for L Speed and Kernel Auditor, things “regulate” themselves and the phone settles down. For the rest of the time until I reboot my phone again, it stays cool for the most part. Even with the screen on a lot and/or using LTE/WiFi/Voice.
I have heard that the stock launcher seems to cause lag. I did not notice that really myself, but in the event, it was causing the phone to work harder… I switched. I have been a huge Nova Launcher fan; use to use it a lot on my S3 and S5. I also have the PRIME version. I installed that and tweaked it, and am actually a lot happier with that personally. Again, it is another app that can require root access for some features, why I stopped using it when I first moved to my S7.
I would also recommend debloating via an App Remover program. Personally, I like Titanium Backup, you can freeze apps you’re not sure about… or even back them up to restore later if needed. Remember removing some apps may cause error messages to pop up, rebooting should fix that. IF not, undo whatever you did (IE unfreeze or restore the app. @YMNDLZ has a screen shot of the apps that can be removed, found here https://forum.xda-developers.com/showpost.php?p=71119004&postcount=1024. Know what you use and do not use. I have a Samsung Galaxy S2 watch, so I kept a lot of the Samsung apps (except the Pay stuff), I use Gmail, etc. Nevertheless, it’s a good reference.
Or if you want you can try running this debloat script: https://drive.google.com/drive/folders/0Bz6QOPY0cm2lTXBWWHVNN1o0SXc?usp=sharing
Personally I think it removes more than I want, but if new to this rooting process it's woth a try to see if it works out for you.
EmergencyManagerSerivce seemed to come up as not responding on a few of the times I experimented rebuilding my phone for this process. If that happens, just go to the service and wipe the cache for it. Reboot, and that should take care of the issue.
Last thing I did, trying to figure out why the EmergencyManagerService was not working, I re-enabled the following in Package Disable Pro:
Samsung DM Phone Interface
Samsung DM Service
CMHProvider
My phone seems to still be working fine with them enabled.
How to Update SuperSU: If anyone has tried updating SuperSU from the PLAY store, it updates fine. But then the binaries need updated, and that's where we run into the problem. The update process always fail, and because of the locked bootloader we can't restart in TWRP or a custom recovery to install the update. My process is pretty easy, and so far seems to work every time (I should know I've done it about 11 times over the past couple of weeks). The current newest version is v2.79 (December 14, 2016) as of writing this post.
NOTE: This will remove root access from your phone temporarily, and then all apps that require root will have to be granted access again. So yes until this is done we're back to the stock kernel settings and your phone may get a little warm again/battery will die a bit faster than normal again.
Open up SuperSU app on your phone, go to the SETTINGS tab scroll all the way down. On my phone "Reinstall" will now be the first thing listed when scrolled all the way down to the bottom of SETTINGS, it's the first item inside of the "CLEANUP" section. If it's not for you, scroll back up until you see it.
DO NOT CLICK FULL UNROOT!!!!
This will unroot your phone. I have not done this, but potentially you would have to rebuild the phone from scratch.
When "Reinstall" is clicked, SuperSU will give a little informational box. Read it, it pretty much gives you the instructions you need. Click "Continue" and the process is started. For me I usually have to restart my phone manually. When the phone restarts, simply go to the Google PLAY story and download the newest version of SuperSU. Once downloaded, open up SuperSU. There should be no notification to update (as you're on the newest binaries). Go back and tweak your settings if needed, install Pro if you bought it, and go through all your apps that need root to grant it.
Other SuperSU method/Other apps that try to do certain mods on reboot: I know that there is a version on @Chainfire website to download and install the SuperSU updates through FlashFire. This isn't the only situation that that will cause issues, but be aware that this will probably soft brick the phone and it will not boot. If you see the picture below, keep reading for a fix.
{
"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"
}
'custom binary blocked by SECURE BOOT (boot.img)'
Scary message huh? No matter if you reboot your phone, try clearing the cache in Recovery, nothing will get it to go away. First time I saw it, I ended up rebuilding my phone last time because I figured all was lost... praying something didn't "lock" in the firmware to cause me to have to actually call Sprint! This time I was messing around with 'Magisk Manager', because I ran into more apps that wouldn't install on a rooted device). Was trying to figure out a work around and flashed something and BOOM on reboot.
Fix When I read the message again this time, and saw the 'boot.img'... it stuck out in my head. I figured I would try using our modified Odin and re-upload the engineering boot.img file again. That was the fix for me! After that, phone rebooted and loaded back into the launcher like normal. So far everything seems to be working fine, my L Speed and Kernel Auditor scripts ran at bootup just like I had normally rebooted my phone.
I can't promise this is the overall fix for everything. But if you happen to be messing with your phone, like I do, and get this... hopefully this will be a quick fix and get the phone back up and running.
I have not reinstalled XPOSED yet, maybe down the road I’ll mess with it. Trying not to add too many variables while figuring out a few of the other things. However, I did test the process and it works.
Framework ZIP to be installed using Flashfire: https://www.androidfilehost.com/?fid=529152257862685343
XPOSED APK installer: https://drive.google.com/drive/folders/0Bz6QOPY0cm2lLUVuVnBlalRHbWM?usp=sharing
@colormedroid also posted up an FQA post in this thread that may be helpful to anyone having issues, found here https://forum.xda-developers.com/showpost.php?p=67595435&postcount=2
The End
That is my notes on everything I did to get the Sprint PL6 firmware rooted and functional with Voice, LTE, MMS, and Hotspot. I enjoy the phone, and I am SOOOOO happy to have root again. Just for stupid stuff like access NTFS partitions on thumb drives, I connect to my phone, Adaway, Titanium Backup, and just general apps to let me use MY phone MY way.
Again, these are the instructions I followed for what I did. I think I wrote down all the steps, if I missed anything or something is not clear, PM me! I am always here to help when and where I can. If there is an edit to be made, I will make it. There is a bunch of people to thank here, if I forget anyone let me know! If this process helps you, think about giving everyone involved a THANKS for their contribution/hardwork! Samsung is really making life hard for us now after they made it so easy with the S5.
@colormedroid and everyone in the OP of the thread here! This is where I met @YMNDLZ and got really into figuring out the rooting process for The SM-G930P phone.
@YMNDLZ who has put up with my insane posts throughout this thread trying to figure this out. Plus responding to a few PMs with questions
@@bodyshop who suggested the SQLite Editor part for the Hotspot.
@swick1981 for the thread on S7 lag.
The other random threads I read through and picked up bits here and there, and forgot to bookmark.
My wife, for putting up with this crap and my sleepless nights messing with my phone.
I think you should hyperlink on the OP to the PL6 instructions since they are on the 2nd page of the thread.
Great write up guys. This will help many since the other threads have outdated links and zips and instructions...
One thing I wanted to know, do you know where the Update.zip is located on marshmallow so it can be deleted?
I've noticed if the Nougat update was deleted you no longer get the notice to reboot and install it. I'm sure it won't pop up after following instructions, but it can't hurt to delete it completely.
I also froze both packages (com.sec.android.soagent and com.wssyncmldm) in Titanium Backup. Had to search for them and 2 Software update files appeared. I Don't know if it makes a difference but I got that part from the other thread that you posted the link to your instructions in.
bodyshop said:
I think you should hyperlink on the OP to the PL6 instructions since they are on the 2nd page of the thread.
Great write up guys. This will help many since the other threads have outdated links and zips and instructions...
One thing I wanted to know, do you know where the Update.zip is located on marshmallow so it can be deleted?
I've noticed if the Nougat update was deleted you no longer get the notice to reboot and install it. I'm sure it won't pop up after following instructions, but it can't hurt to delete it completely.
I also froze both packages (com.sec.android.soagent and com.wssyncmldm) in Titanium Backup. Had to search for them and 2 Software update files appeared. I Don't know if it makes a difference but I got that part from the other thread that you posted the link to your instructions in.
Click to expand...
Click to collapse
I'll hyperlink the PL6 method in the OP, thanks for the suggestion. The update file is located under data/fota by the way.
YMNDLZ said:
I'll hyperlink the PL6 method in the OP, thanks for the suggestion. The update file is located under data/fota by the way.
Click to expand...
Click to collapse
Thanks...
The superSU still said it needs to update binaries. on 2.79 for me but its still working. On PL6 Sprint
bodyshop said:
The superSU still said it needs to update binaries. on 2.79 for me but its still working. On PL6 Sprint
Click to expand...
Click to collapse
When it asks to update binaries click ok, it'll fail the update and ask you to reboot. After you reboot it'll quit asking you to update.
Does this work for the nougat update from sprint or only the universal firmware?
outerdepth said:
Does this work for the nougat update from sprint or only the universal firmware ROM?
Click to expand...
Click to collapse
Sprint...
QAA and PL6 are Sprint. PL2 is Universal
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
New!: Spacesung Oreo Debloat ScriptNotes:
1. Flash in recovery after the first boot.
2. Wipe dalvik cache ONLY! (Oreo cleans up data from removed apps automagically after rebooting.)
3. Profit!
*If you want to modify what's removed, simply open the updater-script with a text editor (preferably Notepad++) and add or remove the # sign. All apps in the stock Oreo system are listed in alphabetical order. This script should be safe to flash as is. Touchwiz, Theme store, Google play, and Samsung keyboard, are not removed by default. No files will be added to your OS either.
Ex.
delete_recursive("/system/app/AmazonMP3"); ← This would be deleted. #delete_recursive("/system/app/AmazonMP3"); ← This would be ignored.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
J727P
Spaceminer said:
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
Click to expand...
Click to collapse
One question did you add any kernel tweaks to your build ? An why can't I find any system tweaks ? Sorry two Questions !!
peter couniaz said:
One question did you add any kernel tweaks to your build ? An why can't I find any system tweaks ? Sorry two Questions !!
Click to expand...
Click to collapse
There are no kernel tweaks. I have been trying to build a custom kernel from source for this, however, ubuntu/virtualbox are not playing nice with my hardware. (Ubuntu stops using my CPU completely after ~10min.) This is just a very bare bones stock Rom, with Trebuchet as a launcher. There are no special system tweaks added to it. Regarding that topic, I am working on tethering, it has been very difficult though. Samsung's smali files are a huge mess to work with. I can get the "you are not subscribed to this service" notification to stop, but tethering still won't start. Are you missing any options that would normally be available on stock? If so, I would definitely like to fix that ASAP.
J727P
Spaceminer said:
There are no kernel tweaks. I have been trying to build a custom kernel from source for this, however, ubuntu/virtualbox are not playing nice with my hardware. (Ubuntu stops using my CPU completely after ~10min.) This is just a very bare bones stock Rom, with Trebuchet as a launcher. There are no special system tweaks added to it. Regarding that topic, I am working on tethering, it has been very difficult though. Samsung's smali files are a huge mess to work with. I can get the "you are not subscribed to this service" notification to stop, but tethering still won't start. Are you missing any options that would normally be available on stock? If so, I would definitely like to fix that ASAP.
Click to expand...
Click to collapse
Thank you for getting back to me an good luck with your build on a custom kernel for this phone we can really use one !! Thanks again !
Spaceminer said:
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
Click to expand...
Click to collapse
Downloaded and installed nicely. Tried to switch superuser with magisk but no go, need stock boot image but all in all a good clean debloated Rom. You should include a keyboard though, your link did not work so I downloaded one on my PC and transferred to internal sd and installed. If you can get magisk instead of superuser, you will have a winner !
Sent from my SM-J727P using Tapatalk
J727P
Spaceminer said:
SpacesungGalaxy J727P
(J727PVPU3ARC2)Disclaimer:
I am not responsible for what you do with your device. If you decide to flash this software then you are accepting any risks involved. Including, but not limited to; bricking your device, missing alarms, missing calls, loss of your job, repossession of your car, and maybe even spilt milk.
About:
This is very much a personal project that I felt others would appreciate. I enjoy retro gaming very much, and as some of you may know, emulation is very CPU intensive. Hence the reason for making Spacesung. My goal was a stock rom that was lag free, debloated, and buttery smooth for gaming. I believe I have achieved this, and so, I give this to the you, to enjoy, use, modify, and share at your discretion.
Features
•Deodexed
•Debloated- I have removed all unnecessary Samsung, Google, and Amazon apps.
•Removed all Amazon symlinks. (Libs are next.)
•Deknoxed- Note: Some leftovers may be present. If you find any please let me know.
•Rooted- SuperSu is included.
•Up to 10gb+ of internal storage is available. This number will change depending on what you install afterwards, and what you have already stored on your internal SD.
Instructions:
1. Download the ROM from here.
2. Download GoogleKeyboard. You will need this after installation because the Samsung keyboard has been removed.
3. Make sure both files are on your internal, or external storage. Either is fine.
4. Reboot to recovery and wipe, data, system, cache, & dalvik cache.
5. Install Spacesung.
6. Reboot and wait. SuperSU will cause it to boot loop once. This is just root sinking it's teeth into the system. Don't interrupt it. After the aforementioned loop, it'll take about ~5-8min to start up. This only applies to the very first boot. Afterwards it only takes ~10 seconds to startup.
7. Skip all the setup steps that require typing. This can be done after you install GoogleKeyboard.
8. Enjoy!
Special notes:
*Google play, and Google services are still installed. You can disable both if you want to. You must disable it as a device administrator under the security options first, or it will be grayed out.
*Syncing will not work, since it has also been removed.
*Device encryption and secure storage shouldn't work either.
*Chrome is still installed. It can also disabled. There is no way to remove it yet, as the 7.0 framework uses it for webview. I'm still searching for a workaround to save more space.
*Anything not listed, should be working perfectly. If something is broken, let me know. And please remember, that anything already listed is not a bug, it is intentional. If you have any issues with 3rd party apps, I will try to help you, though I make no promises.
*As always, anything that I make is free to use for other projects, public or personal, without my permission. No need to ask me, just do it! Credit is always appreciated, though not required.
Click to expand...
Click to collapse
You may want to try this Build I Built on TomeGJ7p's WIFI BUILD it's a good one I THINK YOU WILL LIKE IT !
https://mega.nz/#!aUlU3CiD!QERLRerFDA8497aKopbqZqZh-ZSTVfZ9GhfQQy2mBrs
PS if you like it you can use it to Build on you have mine an tomeGJ7p's Blessing !!
Spaceminer said:
There are no kernel tweaks. I have been trying to build a custom kernel from source for this, however, ubuntu/virtualbox are not playing nice with my hardware. (Ubuntu stops using my CPU completely after ~10min.) This is just a very bare bones stock Rom, with Trebuchet as a launcher. There are no special system tweaks added to it. Regarding that topic, I am working on tethering, it has been very difficult though. Samsung's smali files are a huge mess to work with. I can get the "you are not subscribed to this service" notification to stop, but tethering still won't start. Are you missing any options that would normally be available on stock? If so, I would definitely like to fix that ASAP.
Click to expand...
Click to collapse
This ROM is totally debloated. I went back and tried it again, very smooth, very fast but Contacts would not sync so I could not call anyone. Google account would not sync so no play store apk update from old account.Samsung account missing so no way for me to bring certain apks and utilities from stock ROM. Bare-bones android op. But I will keep it on my sd card.
PS
I just remembered those system apks that are missing that I need, I could have installed thru Titanium Bkup! [emoji846]
Sent from my SM-J727P using Tapatalk
is there anyway you can upload a copy with sync enabled and would it be possible to also use a modified or even stock touchwiz launcher?? and Magisk... If I could have sync magisk and touchwiz Id run this as my daily driver
JeepinxJosh said:
is there anyway you can upload a copy with sync enabled and would it be possible to also use a modified or even stock touchwiz launcher?? and Magisk... If I could have sync magisk and touchwiz Id run this as my daily driver
Click to expand...
Click to collapse
You can flash gapps for sync, I don't have the sync apps on hand or I would attach them. I've flashed pico without issue. I forget which one(s) has the sync apps, it's possible that all of them do. Magisk can be installed fairly easily. Grab Magisk v16. Open SuperSU, look in settings and choose full unroot. Select yes when asked to restore the stock boot image, and no to recovery. As soon as it reboots, hold Vol↑+Home to catch TWRP, then flash Magisk. As for Touchwiz, try installing the one in the attachments below. If it gives you any problems, let me know. If I update anything I will definitely be using Magisk, and I'll keep these options in mind for separate builds in the future.
Spaceminer said:
You can flash gapps for sync, I don't have the sync apps on hand or I would attach them. I've flashed pico without issue. I forget which one(s) has the sync apps, it's possible that all of them do. Magisk can be installed fairly easily. Grab Magisk v16. Open SuperSU, look in settings and choose full unroot. Select yes when asked to restore the stock boot image, and no to recovery. As soon as it reboots, hold Vol↑+Home to catch TWRP, then flash Magisk. As for Touchwiz, try installing the one in the attachments below. If it gives you any problems, let me know. If I update anything I will definitely be using Magisk, and I'll keep these options in mind for separate builds in the future.
Click to expand...
Click to collapse
Thanks man
I used this rom as the base for my gaming phone and then stripped it down to only system framework apps. If the latter were removed it would crash the phone. Anything I removed to get to that point, had minimal impact on space (fifty or so megs) and bootup times compared to a fully loaded phone (5 seconds). Spaceminer did an excellent job on this.
Video here of bootup comparison between two Galaxy J7 Perx, one with the Spacesung rom:
https://www.youtube.com/watch?time_continue=2&v=z9bcqwLVIAA
Is the Oreo stock ROM a battery chugger?
It's just me or anybody have experienced less stamina from their battery with the Oreo stock ROM even with all the de-bloat applied. Compared to the latest ARG2 Nougat it's almost halves the lifetime of the battery, even when on standby it consume a lot more.
ct760ster said:
It's just me or anybody have experienced less stamina from their battery with the Oreo stock ROM even with all the de-bloat applied. Compared to the latest ARG2 Nougat it's almost halves the lifetime of the battery, even when on standby it consume a lot more.
Click to expand...
Click to collapse
Have you tried turning off all the scanning features? Also in the dev options, the switch that keeps mobile data always on, is enabled by default. It's normally off in Nougat. Turning that off should help tremendously.
That being said, I do think Oreo is a battery hog, and I don't think there's any performance gain over Nougat. My best benchmarks with this phone are running Nougat (ARG2), debloated. My battery gives me 51-52hrs on Nougat, with 17-18hrs of that being screen on time. I plan on running Oreo this week to get a good comparison between them.