The ENG kernel used for root is great in a sense that it has aided in giving us root access, but it is nowhere near as refined as the factory kernel. @psouza4 has done a TON to make this kernel awesome, but there are a lot of people who have reverted back to stock because of the limitations.
I'm considering making an insanely debloated ROM that will hopefully run on the factory PE1 kernel. Root access would be needed to do the initial install with FlashFire, but afterwards there would be no root access. This might be what a few of you guys are looking for, a blazing fast ROM that runs forever on a charge, without getting hot. Once the ROM is flashed, there will be NO ability to modify unless the ENG kernel is flashed and rooted again. This ROM would NOT be for anyone interested in running Xposed framework in anyway.
If there is enough interest, I'll start working on something FAST!
Definitely interested in this
Extremely interested.
Could you throw in a modified hosts file for ad blocking? Or, should I mod it first then unroot? Also, would bypassing the checks for tethering be an option before going back to original kernel?
Illogi.xbone said:
Could you throw in a modified hosts file for ad blocking? Or, should I mod it first then unroot? Also, would bypassing the checks for tethering be an option before going back to original kernel?
Click to expand...
Click to collapse
I'm hoping to include some mods like this. I believe I'll be able to modify the host file, but you would not be able to update the hosts once the ROM is installed.
CVertigo1 said:
I'm hoping to include some mods like this. I believe I'll be able to modify the host file, but you would not be able to update the hosts once the ROM is installed.
Click to expand...
Click to collapse
Great! I was thinking of trying something along this route. I will make a flashfire backup of internal first then could give it a go.
I'll keep you posted when I have something worthy of flashing.
Wont future updates just re-bloat the rom?
CVertigo1 said:
I'll keep you posted when I have something worthy of flashing.
Click to expand...
Click to collapse
Thank you! Mostly root for adaway anyways lol
freak69ize said:
Wont future updates just re-bloat the rom?
Click to expand...
Click to collapse
The ROM would prevent future updates, so all updates would be done via re-root and flash.
CVertigo1 said:
The ROM would prevent future updates, so all updates would be done via re-root and flash.
Click to expand...
Click to collapse
Yeah.. very interested then... as long as you keep theme store in it
Awesome
This is exactly what I was looking for! I'd be eternally grateful if you did it.
I would love to see something like this!
My question is, since I can always at least disable bloat, can I make some changes (provisioning for tethering, modified hosts file) then unroot and reflash stock kernel?
The only reason I wanted root is for viper4android/audio mods. Would an unrooted rom be able to include that?
Sent from my SM-G930V using Tapatalk
fronc01 said:
The only reason I wanted root is for viper4android/audio mods. Would an unrooted rom be able to include that?
Sent from my SM-G930V using Tapatalk
Click to expand...
Click to collapse
That's an interesting question. Some optimizations like that could be added. But that app wouldn't work since it requires root privileges.
Sent from my SM-G930V using XDA-Developers mobile app
This will be great. An insanely debloated stock VZR 935U ROM with non-provisioned tethering, HD calling, and VVM is all that that's needed to make this the ultimate phone. Everything else that's need for full VZW functionality can be installed from the Play Store.
However, how would you go back to the stock kernel after installing this ROM? Just by flashing the stock AP in Odin?
I'd be stoked if this phone had stock mm status bar icons that's the only thing I've honestly really used root for and it still doesn't say LTE but instead the ugly 4G icon.. I'd even be alright with Verizons icon if it wasn't persistent on WiFi but then they're still ics looking signal bars. My s7 runs rather warm and battery drain rather sucks with the eng. Kernel starting to think it's not quite worth being able to themeish my status bar. I'd be interested in a debloated stock rom with HD calling if you can throw in the status bar that's icing on the cake.
Sorry for not checking the thread lately. I'm still trying to figure out how to make this work. I have some ideas, but nothing concrete yet.
This isn't going to work. DM-Verity checks will cause the phone not to boot once the original kernel is flashed back. If there is even a byte changed in the system partition it will make the hash invalid and cause the DM-Verity check to fail. The only debloating you can possibly do is simply disabling packages. (In the event of not wanting the Engineering kernel/root.)
Related
I have never run a stock OS rooted. Always AOKP or CM. What should we do now?
-How to we protect it to make sure VZW doesn't somehow patch it?
-Tethering without Foxfi now possible. See below.
-SuperSu info - see below.
-What will we need to do about updates?
-What else?
Read below. I'm adding helpful info as it is collected.
GeoHot (and others), you are the man (men). Thanks guys. All bounty pledgers, pay up!
If you need to root your S5, go here. Donate as well! http://towelroot.com/
** No, Root does not allow us to unlock the bootloader. They are entirely different. I personally have not heard of anyone working on that. Most knowledgeable people I have heard say it would require a leak of the keys from Verizon. **
***Below are apps and/or tweaks (not obvious ones) known to work by me or someone else that has tested***
-Xposed Framework
----X Tether (Free tethering)!
----Wanam Xposed - Free tethering option does NOT work for me. Others report it does.
-Super SU 2.0 in Play store now works. Link below no longer needed.
----use this version http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
mkitchin said:
I have never run a stock OS rooted. Always AOKP or CM. What should we do now?
-How to we protect it to make sure VZW doesn't somehow patch it?
-I assume we can enable native tethering without FoxFi?
-I know there is some chatter about SuperSu. It fails to update. Need a new version from Chainfire?
-What will we need to do about updates?
-What else?
GeoHot (and others), you are the man (men). Thanks guys. All bounty pledgers, pay up!
Click to expand...
Click to collapse
Did you install SU before or after rooting? Or had that problem, stupid me in the antisapation of having root I installed SU last night and after rooting just now could not for the life of me get it to update SU, after multiple reboots I finally uninstalled it after clearing the cache and app settings in app manager, rebooted then reinstalled, then ran root checker, it failed then it asked for root, granted, rechecked, and it passed!
mkitchin said:
I have never run a stock OS rooted. Always AOKP or CM. What should we do now?
-How to we protect it to make sure VZW doesn't somehow patch it?
-I assume we can enable native tethering without FoxFi?
-I know there is some chatter about SuperSu. It fails to update. Need a new version from Chainfire?
-What will we need to do about updates?
-What else?
GeoHot (and others), you are the man (men). Thanks guys. All bounty pledgers, pay up!
Click to expand...
Click to collapse
logically, you should avoid any vzw updates. SU may fail, but it still works. try running a rooted app. it will ask you to grant permission. I just removed over 12 apps that vzw forced on my phone.
Sent from my SM-G900V using Tapatalk
GlitchMob said:
logically, you should avoid any vzw updates. SU may fail, but it still works. try running a rooted app. it will ask you to grant permission. I just removed over 12 apps that vzw forced on my phone.
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
can you share what was safe to remove so far without messing up any framework dependencies?
Sent from my SM-G900V using Tapatalk
chainfire needs to update app before well b able to update it.. it still has root and works so be patient.. we cant keep vzw/samsung from patching it on future devices but it will take them a bit of time so id imagine later updates and newer phones yet to come out would be patched.. now we enjoy root until someone down the road (hopefully) gets us custom recovery for custom roms but lets not jump the gun here, we just got root so let the devs enjoy that feat lol
Sent from my SM-G900V using XDA Premium HD app
Disable OTA
elliwigy said:
chainfire needs to update app before well b able to update it.. it still has root and works so be patient.. we cant keep vzw/samsung from patching it on future devices but it will take them a bit of time so id imagine later updates and newer phones yet to come out would be patched.. now we enjoy root until someone down the road (hopefully) gets us custom recovery for custom roms but lets not jump the gun here, we just got root so let the devs enjoy that feat lol
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
Rename SDM.apk and SDM.odex. to .bak files and VZW can't use the OTA updater anymore. The software updater in settings will be gone too. You will need a file explorer like fx and the root add on for this, it's free.
EDIT: SDM.apk is in the system/app driectory.
Safestrap is next: you'll be able to run custom ROMs but not custom kernels, so TW builds but not AOSP (unless the S5 GPE is built on a TW kernel, as the original 4.2.2 S4 GPE ROM was). I wouldn't actually delete any APKs from your device; just freeze them with Titanium.
Backwardsblade said:
can you share what was safe to remove so far without messing up any framework dependencies?
Sent from my SM-G900V using Tapatalk
Click to expand...
Click to collapse
Sure, but I cannot guarantee you won't have any issues. I managed to remove a decent amount of bloat apps and rebooted successfully. I will list them below.
- Google +
- Google Books
- Google Play Music
- Audible
- VZW protection
- Messaging +
- Amazon
- Kindle
- Amazon Appstore
- IMDB
- VZW ringtones
- VZW protection and support
- Isis Wallet
and a few more that I cannot remember. I hope this helps.
---------- Post added at 07:28 PM ---------- Previous post was at 07:28 PM ----------
s44 said:
Safestrap is next: you'll be able to run custom ROMs but not custom kernels, so TW builds but not AOSP (unless the S5 GPE is built on a TW kernel, as the original 4.2.2 S4 GPE ROM was). I wouldn't actually delete any APKs from your device; just freeze them with Titanium.
Click to expand...
Click to collapse
Wouldn't the bootloader need to be unlocked first?
GlitchMob said:
Sure, but I cannot guarantee you won't have any issues. I managed to remove a decent amount of bloat apps and rebooted successfully. I will list them below.
- Google +
- Google Books
- Google Play Music
- Audible
- VZW protection
- Messaging +
- Amazon
- Kindle
- Amazon Appstore
- IMDB
- VZW ringtones
- VZW protection and support
- Isis Wallet
and a few more that I cannot remember. I hope this helps.
---------- Post added at 07:28 PM ---------- Previous post was at 07:28 PM ----------
Wouldn't the bootloader need to be unlocked first?
Click to expand...
Click to collapse
no.. safestrap doesnt change or effect bootloader which is why youd only be able to install roms compatible with the locked bootloader
Sent from my SM-G900V using XDA Premium HD app
elliwigy said:
chainfire needs to update app before well b able to update it.. it still has root and works so be patient.. we cant keep vzw/samsung from patching it on future devices but it will take them a bit of time so id imagine later updates and newer phones yet to come out would be patched.. now we enjoy root until someone down the road (hopefully) gets us custom recovery for custom roms but lets not jump the gun here, we just got root so let the devs enjoy that feat lol
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
He already updated SU HERE: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
---------- Post added at 12:31 PM ---------- Previous post was at 12:30 PM ----------
elliwigy said:
chainfire needs to update app before well b able to update it.. it still has root and works so be patient.. we cant keep vzw/samsung from patching it on future devices but it will take them a bit of time so id imagine later updates and newer phones yet to come out would be patched.. now we enjoy root until someone down the road (hopefully) gets us custom recovery for custom roms but lets not jump the gun here, we just got root so let the devs enjoy that feat lol
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
mkitchin said:
I have never run a stock OS rooted. Always AOKP or CM. What should we do now?
-How to we protect it to make sure VZW doesn't somehow patch it?
-I assume we can enable native tethering without FoxFi?
-I know there is some chatter about SuperSu. It fails to update. Need a new version from Chainfire?
-What will we need to do about updates?
-What else?
GeoHot (and others), you are the man (men). Thanks guys. All bounty pledgers, pay up!
Click to expand...
Click to collapse
SU updated here: http://download.chainfire.eu/447/SuperSU/UPDATE-SuperSU-v1.99r4.zip
elliwigy said:
no.. safestrap doesnt change or effect bootloader which is why youd only be able to install roms compatible with the locked bootloader
Sent from my SM-G900V using XDA Premium HD app
Click to expand...
Click to collapse
Would love to see safe strap soon!
Two of the more useful features (I believe) are:
1) native tethering -- http://forum.xda-developers.com/showthread.php?t=2768837
2) download booster -- http://forum.xda-developers.com/showthread.php?t=2719582
There's no concept of recovery, so it would involve uploading the files via adb or some other means and running the scripts via terminal emulator/adb
(1) involves replacing framework-res.apk with the packaged copy -- last time I tried to attempt something like that with a live filesystem I ended up with a bootloop I couldn't resolve and had to reflash the stock ODIN, which I don't want to do at this time.
You can also enable the hidden menus via the phone dialer after root -- change /efs/carrier/HiddenMenu to ON
vacaloca said:
Two of the more useful features (I believe) are:
1) native tethering -- http://forum.xda-developers.com/showthread.php?t=2768837
2) download booster -- http://forum.xda-developers.com/showthread.php?t=2719582
There's no concept of recovery, so it would involve uploading the files via adb or some other means and running the scripts via terminal emulator/adb
(1) involves replacing framework-res.apk with the packaged copy -- last time I tried to attempt something like that with a live filesystem I ended up with a bootloop I couldn't resolve and had to reflash the stock ODIN, which I don't want to do at this time.
You can also enable the hidden menus via the phone dialer after root -- change /efs/carrier/HiddenMenu to ON
Click to expand...
Click to collapse
The custom recovery from this thread: http://forum.xda-developers.com/showthread.php?t=2746586 won't work on ours?
Droid_Evo_8 said:
The custom recovery from this thread: http://forum.xda-developers.com/showthread.php?t=2746586 won't work on ours?
Click to expand...
Click to collapse
Bootloader is still locked on the consumer edition. Cannot flash a recovery.
vacaloca said:
Bootloader is still locked on the consumer edition. Cannot flash a recovery.
Click to expand...
Click to collapse
Gotcha. Too bad, I'm not good on replacing those framework stuff in other for me to have the native tethering and download booster to work.
vacaloca said:
Two of the more useful features (I believe) are:
1) native tethering -- http://forum.xda-developers.com/showthread.php?t=2768837
2) download booster -- http://forum.xda-developers.com/showthread.php?t=2719582
There's no concept of recovery, so it would involve uploading the files via adb or some other means and running the scripts via terminal emulator/adb
(1) involves replacing framework-res.apk with the packaged copy -- last time I tried to attempt something like that with a live filesystem I ended up with a bootloop I couldn't resolve and had to reflash the stock ODIN, which I don't want to do at this time.
You can also enable the hidden menus via the phone dialer after root -- change /efs/carrier/HiddenMenu to ON
Click to expand...
Click to collapse
Have you personally tried the dl booster on the S5?
GlitchMob said:
Have you personally tried the dl booster on the S5?
Click to expand...
Click to collapse
I have not. From the updater script on the 2.1 ODEX zip file on that thread it's replacing these files:
/system/framework/services.jar
/system/framework/services.odex
/system/priv-app/SecSettings.apk
/system/priv-app/SecSettings.odex
I briefly looked through the thread and I don't believe the author of the mod specifically mentioned what the changes he did are. I'd prefer getting the original files from my own phone, extracting/decompiling the contents, making the relevant changes, packaging them back up and replacing them on the phone (after making backups). I'm also lazy, so i'll probably leave that to someone else.
vacaloca said:
I have not. From the updater script on the 2.1 ODEX zip file on that thread it's replacing these files:
/system/framework/services.jar
/system/framework/services.odex
/system/priv-app/SecSettings.apk
/system/priv-app/SecSettings.odex
I briefly looked through the thread and I don't believe the author of the mod specifically mentioned what the changes he did are. I'd prefer getting the original files from my own phone, extracting/decompiling the contents, making the relevant changes, packaging them back up and replacing them on the phone (after making backups). I'm also lazy, so i'll probably leave that to someone else.
Click to expand...
Click to collapse
lol same here. I'll wait till I hear more from people who actually try it.
mkitchin said:
I have never run a stock OS rooted. Always AOKP or CM. What should we do now?
-How to we protect it to make sure VZW doesn't somehow patch it?
-I assume we can enable native tethering without FoxFi?
-I know there is some chatter about SuperSu. It fails to update. Need a new version from Chainfire?
-What will we need to do about updates?
-What else?
GeoHot (and others), you are the man (men). Thanks guys. All bounty pledgers, pay up!
Click to expand...
Click to collapse
Does anyone have a good method for enabling the native hotspot app for free? On my old Motorola RAZR all I had to do was flip the entitlement check with a sql editor. Obviously it's not that easy anymore...
ryanpm939 said:
Does anyone have a good method for enabling the native hotspot app for free? On my old Motorola RAZR all I had to do was flip the entitlement check with a sql editor. Obviously it's not that easy anymore...
Click to expand...
Click to collapse
Apparently xposed framework with X Tether module will do it, according to some replies on the thread I linked to above in post #12.
Edit: Here is the native way to do it:
http://forum.xda-developers.com/showthread.php?t=2759119
Hi all,
I have a corporate T-mobile S4 device for work and I can put a custom ROM on it as long as the OS is not rooted. I am looking for a AOSP 4.4.4 / GPE ROM that I can use that is not rooted.
Every Rom thread i look at, the ROM comes pre-rooted with SU. This wlll not work for me.
Any help is much appreciated.
RNB
Wrong section, but I figured I could help you http://forum.xda-developers.com/showthread.php?t=2397511
I think this is what you're looking for!
Me Gusta!
SuperSU will let you remove root, option in the app for it. So if the rom comes with that it's easily unrootable
Me Gusta said:
I think this is what you're looking for!
Click to expand...
Click to collapse
Looks like what I am looking for. Will test it tomorrow.
dave106 said:
SuperSU will let you remove root, option in the app for it. So if the rom comes with that it's easily unrootable
Click to expand...
Click to collapse
Removing the root using SuperSU doesnt return all the files and permissions back to normal. The root check performed by the MDM app checks a lot of things. More details available here
https://jira.cyanogenmod.org/browse/CYAN-4012
rnb89 said:
Looks like what I am looking for. Will test it tomorrow.
Removing the root using SuperSU doesnt return all the files and permissions back to normal. The root check performed by the MDM app checks a lot of things. More details available here
https://jira.cyanogenmod.org/browse/CYAN-4012
Click to expand...
Click to collapse
Maybe RootCloak will help?
Hi there, I'm no new to development, but haven't played with a phone in a while.
Can someone please tell me what the disadvantages of rooting the Nexus 6p are?
My plan is to get root access only to use specific apps (eg greenify) but not to install a new ROM, i.e. I'll stay with stock.
Does this affect:
-Applicability of OTA updates from Google
-ability to use the fingerprint reader
-warranty claims
-speed/stability of the device?
Thanks in advance!
qwertyuiop89 said:
Hi there, I'm no new to development, but haven't played with a phone in a while.
Can someone please tell me what the disadvantages of rooting the Nexus 6p are?
My plan is to get root access only to use specific apps (eg greenify) but not to install a new ROM, i.e. I'll stay with stock.
Does this affect:
-Applicability of OTA updates from Google
-ability to use the fingerprint reader
-warranty claims
-speed/stability of the device?
Thanks in advance!
Click to expand...
Click to collapse
-OTA are not possible when rooted. You have to flash back stock boot.img and recovery.img to accept an OTA.
-It does not interfere with Nexus Imprint (Fingerprint reader.)
-Does not affect speed or stability
-Warranty is not affected because you can flash stock imgs and relock bootloader.
You can take OTA's if you do the systemless-root. I believe you would have to flash the recovery back to stock, though.
I think you have to flash boot as well since it's modified.
the biggest disadvantage is your device become instantly awesome, so if you are used to being annoyed about the stock OS missing features this is hard to deal with
But honestly the best thing about owning a nexus is you can root and easily go back to stock if you change your mind. The flash images are also easily available for updates (even before the OTA is out). So play with it, and worst case you can always restore back to stock.
currently my only disadvantage to me is loosing android pay...
yea i know i can make it work if i delete /su/xbin... but i feel like its there for a reason and i shouldnt be deleting it.
chaco81 said:
currently my only disadvantage to me is loosing android pay...
yea i know i can make it work if i delete /su/xbin... but i feel like its there for a reason and i shouldnt be deleting it.
Click to expand...
Click to collapse
Supersu 2.61 does systemless root ootb. No need to delete anything. Systemless root will just work and Android Pay will just work.
83097markcynt said:
Supersu 2.61 does systemless root ootb. No need to delete anything. Systemless root will just work and Android Pay will just work.
Click to expand...
Click to collapse
i have been using systemless root since v 2.61... im using 2.66 now
and android pay didnt work, and even wont pass safetynet test
delete the /su/xbin folder and it passes safetynet and android pay works...
so yes, for me it sucks that i have delete that to make AP to work... which is why for now i am giving up AP since i dont feel comfortable deleting xbin and breaking stuff
Mine passes safetynet test and is just systemless with nothing deleted. No Android Pay in the UK to test it with though.
Not being awesome.
Not living in the exciting XDA fast lane!
Can I use Xposed with systemless root?
Thanks for the replies everyone - that was very helpful. I've gone ahead and installed three sustemless root, and installed xposed too, leaving the rom itself untouched as stock.
However, my system is disappointingly buggy. Apps keep crashing. Is this common? I thought this was supposed to be a stable/safe thing to do!
dimiboy said:
Can I use Xposed with systemless root?
Click to expand...
Click to collapse
Yes mate you can works perfectly well
Sent from my Nexus 6P using Tapatalk
qwertyuiop89 said:
Thanks for the replies everyone - that was very helpful. I've gone ahead and installed three sustemless root, and installed xposed too, leaving the rom itself untouched as stock.
However, my system is disappointingly buggy. Apps keep crashing. Is this common? I thought this was supposed to be a stable/safe thing to do!
Click to expand...
Click to collapse
lol this seems to happen when you root and install Xposed or pretty much modify anything. Usually I see a decrease in stability and battery life but an increase in performance, and you get to play with new features early.
I'm contemplating rooting just to use the new launcher.
qwertyuiop89 said:
Thanks for the replies everyone - that was very helpful. I've gone ahead and installed three sustemless root, and installed xposed too, leaving the rom itself untouched as stock.
However, my system is disappointingly buggy. Apps keep crashing. Is this common? I thought this was supposed to be a stable/safe thing to do!
Click to expand...
Click to collapse
You have a couple of things going on.
First root IS as safe as you let it be. If you haven't installed any root applications it should not be any more buggy than stock.
You have installed Xposed. You have not mentioned what modules you have.
I don't have any issues you describe but I don't have a lot of modules installed.
I am stock with Xposed and root.
None
Sent from my angler using XDA Labs
Is it possible to "un-root" a phone without having to flash firmware? For example I'd like to use Samsung Pay which won't work because of a root check BUT would like to keep the debloated and optimized U ROM along with the non-provisioned WIFI-tethering, VVM, etc. that I originally rooted for. So is this possible? I understand that I will still be on the eng. boot kernel but that's fine.
GeoFX said:
Is it possible to "un-root" a phone without having to flash firmware? For example I'd like to use Samsung Pay which won't work because of a root check BUT would like to keep the debloated and optimized U ROM along with the non-provisioned WIFI-tethering, VVM, etc. that I originally rooted for. So is this possible? I understand that I will still be on the eng. boot kernel but that's fine.
Click to expand...
Click to collapse
You can try the unroot option in the SU app but I doubt it will work because the files are pushed to the system by ADB. I could be wrong though.
This is one thing I have been curious about as well. I just want to make a few changes to files that require root, then remove root to keep my Samsung Pay working but the changes still saved in place. I feel like someone has tried it, I just haven't ran across the post yet...
I'd like to keep the U firmware while having all of the Verizon essentials but without root. Even optimized with all battery savings, I'm getting heat just using chrome and having more battery drainage than when I was unrooted. I read it's something dealing with the eng.boot since it's not made for daily use.
So would it be possible just to factory reset U firmware and have the necessary Verizon apps to install afterwards? I'm guessing root isn't that beneficial for me at this point if it just drains my battery since I usually would have 3 hours of SOT by 50%, and now it's only 2 hours by 50%.
GigaSPX said:
So would it be possible just to factory reset U firmware and have the necessary Verizon apps to install afterwards? I'm guessing root isn't that beneficial for me at this point if it just drains my battery since I usually would have 3 hours of SOT by 50%, and now it's only 2 hours by 50%.
Click to expand...
Click to collapse
You can install most of the Verizon apps through the Play Store except for VVM, which requires you to write into /system and thus requires root and thus the eng. kernel. Also you won't be be able to patch the HD Calling feature without root as well. IF you need these features, then the eng. kernel is a must have in order to obtain root to install.
If not, you're good to go. I'm sure there's probably something else I'm missing.
GeoFX said:
You can install most of the Verizon apps through the Play Store except for VVM, which requires you to write into /system and thus requires root and thus the eng. kernel. Also you won't be be able to patch the HD Calling feature without root as well. IF you need these features, then the eng. kernel is a must have in order to obtain root to install.
If not, you're good to go. I'm sure there's probably something else I'm missing.
Click to expand...
Click to collapse
Then it would already be pretty great to simply get a debloated stock Verizon firmware. Because I was amazed at how much free space I had for internal storage once I flashed the U firmware and the v15 debloat fix zip. If I could go all of that without the battery drainage that I'm pretty sure is coming from root itself.
GigaSPX said:
Then it would already be pretty great to simply get a debloated stock Verizon firmware. Because I was amazed at how much free space I had for internal storage once I flashed the U firmware and the v15 debloat fix zip. If I could go all of that without the battery drainage that I'm pretty sure is coming from root itself.
Click to expand...
Click to collapse
Your battery drainage is due to the engineering kernel, not necessarily from root. It is not an optimized kernel at all. When I was rooted, the phone was 6 degrees C warmer at idle than stock and would lag. This is with all the V15 fixes from the S7 thread. And heat kills battery life.
I'm sure someone could do this. I'm from the verizon flat s7 forums and a person is suggesting getting on the rooted firmware then from that installing a debloated stock rom from there without root but with various cooked in optimizations. It's not out yet but I'm waiting to see what comes of it. Root hasn't settled enough for me to run it all the time just yet.
Sent from my SM-G930V using XDA-Developers mobile app
JediDru said:
I'm sure someone could do this. I'm from the verizon flat s7 forums and a person is suggesting getting on the rooted firmware then from that installing a debloated stock rom from there without root but with various cooked in optimizations. It's not out yet but I'm waiting to see what comes of it. Root hasn't settled enough for me to run it all the time just yet.
Sent from my SM-G930V using XDA-Developers mobile app
Click to expand...
Click to collapse
That's actually perfect, when possible. :0
Could you not just apply the fixes and unroot or flashing will remove these?
Sent from my SM-G935V using Tapatalk
Hey guys, I have been out of the android world for a couple of years, I would appreciate some guidance.
I I'm currently living in US
T-mobil
Model number: SM-G935T
Android version: 6.0.1
Updated right now
So my question is, since I don't have any backup or anything, can someone provide me with the steps to get me started? Like what post to root it on this specific carrier and how everything? please
Thanks
Arturofm2 said:
Hey guys, I have been out of the android world for a couple of years, I would appreciate some guidance.
I I'm currently living in US
T-mobil
Model number: SM-G935T
Android version: 6.0.1
Updated right now
So my question is, since I don't have any backup or anything, can someone provide me with the steps to get me started? Like what post to root it on this specific carrier and how everything? please
Thanks
Click to expand...
Click to collapse
Of course we can get your started but see
But first you must answer us these question three.
Why do you want root?
Do you have a computer? (This is a must for root.)
Are you ready to be disappointed?
https://forum.xda-developers.com/tmobile-s7-edge/how-to/how-to-root-s7-edge-t3410470
follow this (use odin to flash rooted kernel) ......you should search before posting things like this.....google is your friend bro.
GOOD LUCK - BTW use flash fire app in play store to make backups and flash roms
Okay okay.
A quick glance at T-Mobile Samsung Galaxy S7 Edge Guides, News, & Discussion would have led you to the "How to root the S7 EDGE" thread.
I'd take a look in there if I were you.
Binary100100 said:
Of course we can get your started but see
But first you must answer us these question three.
Why do you want root?
Do you have a computer? (This is a must for root.)
Are you ready to be disappointed?
Click to expand...
Click to collapse
Well while I was waiting I just rooted it. So what do you think that would be the next step towards installing a rom? To answer your survey questions :laugh: :
1- Because a phone without being rooted is like a bird without wins.
2- I do
3- Oh well... tell me more
Arturofm2 said:
Well while I was waiting I just rooted it. So what do you think that would be the next step towards installing a rom? To answer your survey questions :laugh: :
1- Because a phone without being rooted is like a bird without wins.
2- I do
3- Oh well... tell me more
EDIT: I just checked and the root didn't go through... even though ODIN said it was successful
Click to expand...
Click to collapse
Well then.
Rooting the phone (as I'm sure you had already found out) was fairly easy.
BUT... since we do not have an unlocked bootloader then we cannot have any custom recovery. Which means we can only (for now) use adb and Fireflash to flash any custom firmwares. And while we're on the subject of that... there is only one custom rom. Well... technically there are two but only one for you since you updated to the latest firmware.
Echoe ROM which was updated (ummm...) September 9th (not including the Verizon version which might work but with no promises)
Tekxv2 which was updated back in July. Unfortunately, that is flashed by adb (computer required) and only supports G935TUVS3APD8 which is... pretty old.
Things that you may notice with root.
Battery life may be shorter.
Strange icons on your status bar.
Might start to have random reboots for absolutely no reason.
Can't use Samsung Pay and some other apps.
Phone might be laggy.
Phone might feel hot.
Some of those can be resolved by flashing the only custom rom that we have (Echoe ROM... which is a rather nice rom) but it's not "there" yet.
Or you can use the guide in my signature to resolve issues like the lag and the strange icons. Yet even after the "fix" you might still experience both again from time to time.
You might even have the IMS force close issue which I used to get about once a month. It would piss me off because no sooner that you click the button, it'll pop up again and you don't have time to do anything. You're pretty much forced to reflash stock, wipe, re-root, restore a latest backup... which can take hours and is rather inconvenient if it happens to you while you're at work like it always seemed to happen for me.
SO...
All in all... root is okay. It's better than nothing I suppose. But until we get more developer support for this phone then in my opinion it's kinda pointless in my opinion.
Too many drawbacks. I eventually unrooted two weeks ago and I love my phone now. I'm using the heck out of Samsung Pay especially since their promotions are pretty nice right now! Plus a few members are testing the Nouget update which probably won't be getting root at all since rooting requires an engineering kernel which we don't have and might not get. Or an unlocked bootloader which we've pretty much given up on.
A lot of members that are testing the Nouget beta firmware are extremely satisfied with it so if we can't root Nouget then having a rooted S7 will probably fade away as more people update to Android 7+. That's where I see this going anyway.
Binary100100 said:
What you wrote above
Click to expand...
Click to collapse
So for what I understood the dev support for this phone is very limited... I know the issues I may encounter, I had them with the galaxy note. but any way... If something I'll unroot it but I want to try it out Thank for you time. I've rooted it.
EDIT: Damn... I really don't like the visual style of Echoe... is that one the only one I can flash??
Binary100100 said:
Well then.
Rooting the phone (as I'm sure you had already found out) was fairly easy.
BUT... since we do not have an unlocked bootloader then we cannot have any custom recovery. Which means we can only (for now) use adb and Fireflash to flash any custom firmwares. And while we're on the subject of that... there is only one custom rom. Well... technically there are two but only one for you since you updated to the latest firmware.
Echoe ROM which was updated (ummm...) September 9th (not including the Verizon version which might work but with no promises)
Tekxv2 which was updated back in July. Unfortunately, that is flashed by adb (computer required) and only supports G935TUVS3APD8 which is... pretty old.
Things that you may notice with root.
Battery life may be shorter.
Strange icons on your status bar.
Might start to have random reboots for absolutely no reason.
Can't use Samsung Pay and some other apps.
Phone might be laggy.
Phone might feel hot.
Some of those can be resolved by flashing the only custom rom that we have (Echoe ROM... which is a rather nice rom) but it's not "there" yet.
Or you can use the guide in my signature to resolve issues like the lag and the strange icons. Yet even after the "fix" you might still experience both again from time to time.
You might even have the IMS force close issue which I used to get about once a month. It would piss me off because no sooner that you click the button, it'll pop up again and you don't have time to do anything. You're pretty much forced to reflash stock, wipe, re-root, restore a latest backup... which can take hours and is rather inconvenient if it happens to you while you're at work like it always seemed to happen for me.
SO...
All in all... root is okay. It's better than nothing I suppose. But until we get more developer support for this phone then in my opinion it's kinda pointless in my opinion.
Too many drawbacks. I eventually unrooted two weeks ago and I love my phone now. I'm using the heck out of Samsung Pay especially since their promotions are pretty nice right now! Plus a few members are testing the Nouget update which probably won't be getting root at all since rooting requires an engineering kernel which we don't have and might not get. Or an unlocked bootloader which we've pretty much given up on.
A lot of members that are testing the Nouget beta firmware are extremely satisfied with it so if we can't root Nouget then having a rooted S7 will probably fade away as more people update to Android 7+. That's where I see this going anyway.
Click to expand...
Click to collapse
How are you doing with the ads? Like youtube, pandora, spotify? I just installed xposed and the phone feels very hot, and If I unroot it (which I'm thinking to do) I won't be able to get things without ads (I know about vpns and browsers). Also how can I install teaks for apps? Installing apks from pages that promise you this and you have to log in is very untruthful. Any suggestions to all this?
Arturofm2 said:
How are you doing with the ads? Like youtube, pandora, spotify? I just installed xposed and the phone feels very hot, and If I unroot it (which I'm thinking to do) I won't be able to get things without ads (I know about vpns and browsers). Also how can I install teaks for apps? Installing apks from pages that promise you this and you have to log in is very untruthful. Any suggestions to all this?
Click to expand...
Click to collapse
I just put up with them.
In all reality, I don't use my phone for the purposes that require my viewing of ads to begin with.
Sure when I was rooted I had adblocker. But honestly, I had completely forgotten all about that benefit of being rooted until now.
I suppose if you absolutely need to be rid of ads then by all means, retain root. However ads don't effect my daily use one bit.
Binary100100 said:
I just put up with them.
In all reality, I don't use my phone for the purposes that require my viewing of ads to begin with.
Sure when I was rooted I had adblocker. But honestly, I had completely forgotten all about that benefit of being rooted until now.
I suppose if you absolutely need to be rid of ads then by all means, retain root. However ads don't effect my daily use one bit.
Click to expand...
Click to collapse
Could you help me unroot it? I was following a guide here to unroot it and downloaded the firmware but when I click flash, it didn't work, I'm having travel reverting it, can you help me? The model is: SM-G935T
Arturofm2 said:
Could you help me unroot it? I was following a guide here to unroot it and downloaded the firmware but when I click flash, it didn't work, I'm having travel reverting it, can you help me? The model is: SM-G935T
Click to expand...
Click to collapse
I just flash the appropriate firmware that you had prior to rooting with ODIN.
Never had any issues. Which "guide" are you referring to?
Binary100100 said:
I just flash the appropriate firmware that you had prior to rooting with ODIN.
Never had any issues. Which "guide" are you referring to?
Click to expand...
Click to collapse
bro now I'm friking out, I followed this guide and when I click in flash it says Fail. I followed it step by step, I don't don't what's going on and when I reset the phone it says custom and doesn't even load, so tmobil would know that I rooted it...
fff.... can you give me the link, guide, whatever you used to revert it?
Arturofm2 said:
bro now I'm friking out, I followed this guide and when I click in flash it says Fail. I followed it step by step, I don't don't what's going on and when I reset the phone it says custom and doesn't even load, so tmobil would know that I rooted it...
fff.... can you give me the link, guide, whatever you used to revert it?
Click to expand...
Click to collapse
You're probably trying to flash a firmware with a V3 bootloader over G935TTMB4APK1.
If you were seriously following that (outdated) guide step by step then you tried flashing TMB_G935TUVU3APG1.zip over a PK1 firmware. Yeah... that doesn't work.
Download the latest firmware from sammmobile.
https://www.sammobile.com/firmwares/database/SM-G935T/
Try it again.
IF that doesn't work... try using Smart Switch.
I haven't done it before but I think it's the Emergency Software Recovery and Initialization.
forum.xda-developers.com/tmobile-s7-edge/how-to/odin-apk1-tmobile-tmbg935ttmb4apk1-t3494724
Odin this to return to stock firmware.
Binary100100 said:
You're probably trying to flash a firmware with a V3 bootloader over G935TTMB4APK1.
If you were seriously following that (outdated) guide step by step then you tried flashing TMB_G935TUVU3APG1.zip over a PK1 firmware. Yeah... that doesn't work.
Download the latest firmware from sammobile.
https://www.sammobile.com/firmwares/database/SM-G935T/
Try it again.
IF that doesn't work... try using Smart Switch.
I haven't done it before but I think it's the Emergency Software Recovery and Initialization.
Click to expand...
Click to collapse
You have no idea the help you gave me. I went to sammobil before but since it said that the download speed was too slow, I didn't do it through that page. Now I did it and it's working fine thanks bro.
But when I start it, it says: custom in the log in, how can I totally put it original?
tduquefjc said:
forum.xda-developers.com/tmobile-s7-edge/how-to/odin-apk1-tmobile-tmbg935ttmb4apk1-t3494724
Odin this to return to stock firmware.
Click to expand...
Click to collapse
If I want to remove everything and just leave it plain how it comes from factory when you buy it, do I just flash the AP file?
Arturofm2 said:
You have no idea the help you gave me. I went to sammobil before but since it said that the download speed was too slow, I kept it. Now I did it and it's working fine thanks bro.
But when I start it, it says: custom in the log in, how can I totally put it original?
Click to expand...
Click to collapse
Arturofm2 said:
If I want to remove everything and just leave it plain how it comes from factory when you buy it, do I just flash the AP file?
Click to expand...
Click to collapse
You should flash everything.
BL= Bootloader (which should be V4 since you updated to the latest firmware already. Anything less than V4 will fail.)
AP= Is for System, Cache, kernel, etc.
CP= Is for modems
CSC is for your HOME_CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 file.
Important! If you use the CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 (doesn't have the word "HOME" in the name) then it'll wipe your phone!
If your phone still says "CUSTOM" on it then make sure that reboot and check again. If it still says custom then make sure that you don't still have the engineering kernel. Re-flash the AP files again if so. It shouldn't though if it's 100% stock. Also note if you saw the unlocked padlock on the S7 Edge splash screen (before the bootanimation).
Good luck and happy New Year.
Binary100100 said:
You should flash everything.
BL= Bootloader (which should be V4 since you updated to the latest firmware already. Anything less than V4 will fail.)
AP= Is for System, Cache, kernel, etc.
CP= Is for modems
CSC is for your HOME_CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 file.
Important! If you use the CSC_TMB_G935TTMB4APK1_CL9507190_QB11413830_REV02_user_low_ship_MULTI_CERT.tar.md5 (doesn't have the word "HOME" in the name) then it'll wipe your phone!
If your phone still says "CUSTOM" on it then make sure that reboot and check again. If it still says custom then make sure that you don't still have the engineering kernel. Re-flash the AP files again if so. It shouldn't though if it's 100% stock. Also note if you saw the unlocked padlock on the S7 Edge splash screen (before the bootanimation).
Good luck and happy New Year.
Click to expand...
Click to collapse
Perfect! All I did was reboot it, and the unlocked padlock went away, thank you very much for all your help! Happy new year!