If you haven't heard of Dirty Cow you should look it up.
There thread is dedicated to rooting the GS7 / GS7E with Dirty Cow
Additional Goals:
Root without Tripp Knox
Working Verizon Hotpsot App
Unlock Bootloader
Receive future Android Updates
Fix all Bug fixes
Anyone can confirm???? New s7 edge and ready to blaze gigs!!!!
Don't listen to this fool. Look at his name.
I don't trust this guy either but this is an actual thing with code written for Android devices already. Any developer who complies it into an apk will have the next kingroot on their hands. Except for truly all Android devices
This will not work for our devices. Even if you do manage to gain root, you won't be able to do much. Any changes to the /system partition will be overwritten on reboot. Dm-verity won't allow those changes.
The current root method is going to be the only option until we are able to unlock the bootloader. That may never happen.
TLDR; Use the current engineering kernel.
Sent from my SM-G935U using Tapatalk
Dameon87 said:
This will not work for our devices. Even if you do manage to gain root, you won't be able to do much. Any changes to the /system partition will be overwritten on reboot. Dm-verity won't allow those changes.
The current root method is going to be the only option until we are able to unlock the bootloader. That may never happen.
TLDR; Use the current engineering kernel.
Click to expand...
Click to collapse
Honestly, I feel like a tethered root would be better than what we have currently. The engineering kernel is pretty terrible after about a week of use. It lags terribly even when maxed out and set to performance in the kernel settings. Maybe someone will at least look into an alternative root.
jal3223 said:
Honestly, I feel like a tethered root would be better than what we have currently. The engineering kernel is pretty terrible after about a week of use. It lags terribly even when maxed out and set to performance in the kernel settings. Maybe someone will at least look into an alternative root.
Click to expand...
Click to collapse
I'm not really sure you understand the implications in such a method. We have dm-verity checks that check the checksum of data on the /system partition. If even one bit is changed, the hash becomes invalid and various things can happen. The Note4 had such a method before, and while it was something... It had tons of issues with reboots, and losing root at random. It became so frustrating that it was honestly not worth the time invested. These problems with exacerbated by changes to the /system partition. So things like xposed and the like were highly hit or miss.
With the amount of issues likely to be caused, the engineering kernel is the best bet until a bootloader unlock is achieved. (if it ever is.) Truthfully a 'tethered' half functional root would be a waste of time. We have the engineering kernel, and while it is far from perfect... It works. And with the right tweaks and time, it can be stable as a daily driver.
Dameon87 said:
With the amount of issues likely to be caused, the engineering kernel is the best bet until a bootloader unlock is achieved. (if it ever is.) Truthfully a 'tethered' half functional root would be a waste of time. We have the engineering kernel, and while it is far from perfect... It works. And with the right tweaks and time, it can be stable as a daily driver.
Click to expand...
Click to collapse
You argue how the engineering kernel is better, and that a tethered root would be a waste of time. But the same could be argued both ways. A tethered boot has the aforementioned problems, and the engineering kernel have the obvious problems of horrible battery life, stability, etc.
So at the end of the day, they're both shotty, half baked, and far less than ideal ways to get root. But who's to say one crappy method is crappier than another crappy method. I'll take what I can get, and due to the fact my S7 Edge hasn't been rooted for months due to how sh*t the engineering kernel is, I wouldn't mind a another root method, reguardless.
FoxyDrew said:
You argue how the engineering kernel is better, and that a tethered root would be a waste of time. But the same could be argued both ways. A tethered boot has the aforementioned problems, and the engineering kernel have the obvious problems of horrible battery life, stability, etc.
So at the end of the day, they're both shotty, half baked, and far less than ideal ways to get root. But who's to say one crappy method is crappier than another crappy method. I'll take what I can get, and due to the fact my S7 Edge hasn't been rooted for months due to how sh*t the engineering kernel is, I wouldn't mind a another root method, reguardless.
Click to expand...
Click to collapse
So you logic is to trade a stable-enough solution for a lesser one that has more implications, will noticeably impact performance. (Because of various methods that have to be used to keep root active.) I'm not sure I follow that at all. And anyone who has actually dealt with a Samsung 'tethered root' will tell you the same thing. The dm-verity check makes things hell. That check is -not- enabled with the Engineering kernel. There were issues with root being lost if you even remove a file from the /system partition (Which by the way, respawns on reboot, so no changes will ever stick. Every change you make... Installing xposed, etc etc.... is wiped -every- time you reboot. There is no saving states.)
In any regard, I've done my homework.. I've messed with the solutions before, and I have developer insight into the former. It's not a feasible solution when we have an engineering kernel. It may not be optimal, but with time and effort it works just fine. And battery life, as well as other things can nearly be mimicked to a T with that kernel over stock.
Dameon87 said:
So you logic is to trade a stable-enough solution for a lesser one that has more implications, will noticeably impact performance. (Because of various methods that have to be used to keep root active.) I'm not sure I follow that at all. And anyone who has actually dealt with a Samsung 'tethered root' will tell you the same thing. The dm-verity check makes things hell. That check is -not- enabled with the Engineering kernel. There were issues with root being lost if you even remove a file from the /system partition (Which by the way, respawns on reboot, so no changes will ever stick. Every change you make... Installing xposed, etc etc.... is wiped -every- time you reboot. There is no saving states.)
In any regard, I've done my homework.. I've messed with the solutions before, and I have developer insight into the former. It's not a feasible solution when we have an engineering kernel. It may not be optimal, but with time and effort it works just fine. And battery life, as well as other things can nearly be mimicked to a T with that kernel over stock.
Click to expand...
Click to collapse
Do you have any advice on making the engineering kernel more optimized?
The v15 fixes here, greenify, amplify, l speed, and gov tuner help a lot! Personally, not the same as stock life, but close... that's the trade off
Sent from my SM-G930U using XDA-Developers mobile app
The first week of rooted u firmware is rough after that with only kernel adiutor my battery life if that of stock unrooted u firmware with only 15 fixes. Only rom I've used that I would say is capable of this is the playstore pi3.
Cant we use dirty cow and change the /system of a combination firmware as dm-verity check is disabled by default, then some how engineer a way to flash the bootloader that would accept a modded twrp recovery or similar..?
Related
I sent my Galaxy S Vibrant through the dishwasher, which didn't turn out particularly well, and the insurance company sent me this G2X as a replacement.
Pleasantly surprised that wifi tethering works out of the box. That was the big point of rooting the Samsung and upgrading first to Bionic (which was awesome) and then to CM7 (which was a big wad of bugs).
Any particular advantage to rooting? LG seems to be much better than Samsung as keeping up with the joneses.
rooting
I recently got my G2x and after following the instructions for installing nvflash and CM recovery I began flashing many different ROMs. I had never done it before and instantly became an addict. My girlfriend who got hers on the same day kept hers stock. Her camera seems to be brighter, mine is faster with a lot less bloat. I did overclock my CPU which so far seems to work well with this phone.
Bloat
yelvington said:
I sent my Galaxy S Vibrant through the dishwasher, which didn't turn out particularly well, and the insurance company sent me this G2X as a replacement.
Pleasantly surprised that wifi tethering works out of the box. That was the big point of rooting the Samsung and upgrading first to Bionic (which was awesome) and then to CM7 (which was a big wad of bugs).
Any particular advantage to rooting? LG seems to be much better than Samsung as keeping up with the joneses.
Click to expand...
Click to collapse
It is worth rooting if for no other reason than to get all the bloat off. Try tsugi rom. It is super stable and lightning fast.
Just the ordinary stuff:
-adfree
-UV kernels
-set CPU
-battery calibration
Those alone are worth the root.
bloat
After having it overnight I can see the advantage of rooting to clean some of the autostart junk out of /system. A couple of times I've had it essentially lock up and the list of processes shown by ATK (when I can get to run) is insane.
Rooting isn't really required or hardly used. I DO use root explorer to make system changes and rom Manager if you crack flash.
But everyday stuff... Maybe titanium backup but I never used it either. Best to restore apps manually.
Most phones require root to install clockwork mod recovery. With Tegra devices you only need to nvflash which doesn't require root. Once you have a custom recovery you can flash roms and custom stuff without root.
So root isn't really important on the G2x unless you want to use a root required app.
-sent from temp HTC Rezound waiting for Galaxy Nexus
I have my phone rooted and tight now only need root for two purposes: 1. I use App Quarantine to freeze unwanted system apps, and 2. I use SetCPU to underclock while the screen's off to save on battery use.
Subtle but important for my phone at least. It all depends on what you use your phone for. Rooting the G2x is pretty easy so it's simple enough to have it if you need it.
Got mine rooted and on CM7. Yes it depends on what you use it for and prefer. I like the custom options that CM7 provide like gestures and specific sound settings etc. In general you do get more freedom to do things and personalize, at the risk of messing it up if you are not careful.
yelvington said:
After having it overnight I can see the advantage of rooting to clean some of the autostart junk out of /system. A couple of times I've had it essentially lock up and the list of processes shown by ATK (when I can get to run) is insane.
Click to expand...
Click to collapse
Why are you using Advanced Task Killer?
Rooting can bring many nice things.
Such as better battery life, better phone performance, opening your phone up for countless customization options.
And a great benefit: no more waiting months and months for new firmware from T-Mobile, get the latest and greatest right away.
And that's just what iI know, I'm sure.there's many other ways.
Sent from my LG-P999 using xda premium
Last night I finally mustered the courage to unlock my bootloader, root and flash Franco (which sounds dirty...), mostly for the improved battery life. I installed Greenify and Titanium, and I'm intrigued by Xposed, so I'll probably give that a go...but now what? What are the essential things I should do with my rooted Nexus 5?
My only "parameters" are that I want to stick with stock ROM (unless someone can make a compelling argument otherwise) and that I want to optimize battery life without compromising performance.
Your insights are much appreciated!
Backup and read. We can't advise any more than that.
Other than tibu, the only thing I use root for is an ad blocker, adaway is good.
I started my Nexus 5 with Cataclysm ROM, very close to stock with added features. No updates nightly like others, stays pretty much with Google stock yet the customization is what I needed. I'd check it out to see if it fits your needs. I also flashed the bionic optimization mods since I run ART but dalvik/bionic mods exist since Xposed currently isn't supported on ART (testing to see if any benefits as of now). Franco is good choice for kernel, waiting to see once r33 is released since very good chance of code change and WAY better battery as stated by the beta testers (minus current beta tester reboots and the memory issue). Mostly, since sticking near stock, the combinations of all these are all I personally needed. Make sure of nandroid before flashing since something may happen but I have not run into any issues yet.
+1 what he said ^^
Sent from my Nexus 5 using Tapatalk
install some system applications - for battery stats, CPU app(if you didn't buy franco's app), wakelock detector. If you are searching to get best battery life without losing performance, you will need to try different kernels (no need to remove and re flash ROM, just flash kernel zip files throught recovery). Essentially, you can try multi ROM feature (there is a thread about it), and try different ROM/kernel combinations, without losing/restoring your data, to find what is best for you. hope this helps
Anyone feel like lollipop runs slower after you root it?
Root access has ABSOLUTELY NOTHING to do with ANYTHING AT ALL other than having root access.
Lethargy said:
Root access has ABSOLUTELY NOTHING to do with ANYTHING AT ALL other than having root access.
Click to expand...
Click to collapse
you are absolutely right but
for root access the kernel is changed permissive maybe that "may" be buggy
bhavstech said:
you are absolutely right but
for root access the kernel is changed permissive maybe that "may" be buggy
Click to expand...
Click to collapse
It modifies the ramdisk. Extremely unlikely that it affects the performance at all.
So no. What I said still stands.
I would like to argue otherwise. Upon unrooting my phone, it has started to perform much better, quite noticeable as well. Same kernel, same apps. Been running for some time now and it's a lot better.
Definitely something there though...
VisionNN said:
I would like to argue otherwise. Upon unrooting my phone, it has started to perform much better, quite noticeable as well. Same kernel, same apps. Been running for some time now and it's a lot better.
Definitely something there though...
Click to expand...
Click to collapse
No. Without actual evidence, we can only say that its placebo or coincidence.
Root access does NOT affect anything at all other than having root access. Even with a modified kernel ramdisk.
VisionNN said:
Anyone feel like lollipop runs slower after you root it?
Click to expand...
Click to collapse
Maybe you already have affected by this.
I assume you using with your phone more than 1 day, and start to feel lag. And then you feel it more responsive because you need to reboot to unroot, right?
And what @Lethargy said is true.
I think that could actually be a reason. Checking my ram, was running pretty high, but i understand lollipop needs more resources. Seems to be running fine right now, but will definitely check that out in more detail when i get a chance.
Hi.
It's been 2 months that I have used my one plus one and I still have the original/vanilla build 22R.
Now I'm curious is it worth to update to the newer versions? I have heard so much bad feedback regarding battery life and other bugs.
What are the pro's and con's?
Right now I'm enjoying 3 days battery life, 5h screen time. But microphone gain for videos is bad also for sound recording. WiFi and the antenna for RF seems to be buggy and not working properly.
Thanks in advance,
Zekenka
Sent from my One using XDA Free mobile app
Just update. Updates are good. Don't listen too much the blaming people cause a lot of them just confuse themselves by doing tests right after the update.
I agree with the previous poster, update your phone, don't worry about the negative Nellies, it's usually user error anyway.
Transmitted via Bacon
Make sure you do the updates in order, or just flash the complete 44s ROM that you can find also (use search, stock rooted 44s).
Personally I would just flash the complete ROM and skip the incrementals lol
ek69 said:
Make sure you do the updates in order, or just flash the complete 44s ROM that you can find also (use search, stock rooted 44s).
Personally I would just flash the complete ROM and skip the incrementals lol
Click to expand...
Click to collapse
What about the battery life etc? I have heard like terrible stories(ofcourse myabe their nellies) but i kinda like the long one right now and I doubt there will be possibility to rollback unless i unlock my bootloader and install TWRP/CWM .
Battery life is good for me and others I've seen. It is possible to go back to old versions but like you said it requires unlocked boot loader and custom recovery probably. Why don't u want to unlock it?
Most battery problems are caused by wake locks. There's a thread in general by timmaaa called play services battery fix if you have issues. If your phone works good as is and don't care about upgrading then don't lol it's not a requirement. If you have bugs then it's probably fixed in the upgrades. Just don't blame us if you do upgrade though
ek69 said:
Battery life is good for me and others I've seen. It is possible to go back to old versions but like you said it requires unlocked boot loader and custom recovery probably. Why don't u want to unlock it?
Most battery problems are caused by wake locks. There's a thread in general by timmaaa called play services battery fix if you have issues. If your phone works good as is and don't care about upgrading then don't lol it's not a requirement. If you have bugs then it's probably fixed in the upgrades. Just don't blame us if you do upgrade though
Click to expand...
Click to collapse
Would unlocking bootloader cause any stuff related to wakelocks? Right now It is perfect 0 drain over night and no terrible wakelocks,
I remember with daily SGS2 build there were terrible wakelocks with up to 20% drain over night
Unlocking bootloader won't do that. Updating or flashing ROM might, no guarantees. My experience is good with latest update, some others have problems most I would say don't. It's your phone and your choice what to do with it lol.
Just update, dont ask to much. Phone is working great on 44S. You will see when you update, battery life is great for me.
I've been catching wind of people mentioning different versions of the mk2000 kernel working best for them on Oreo. In my personal experience flashing mk2000 v2.0. Works quite well for me. I member reading someone saying that a beta version of the 2.2 worked good for them. But for the life of me can't find where I read that. I want to say it was beta 14. In my experience 2.1 and 2.2 have been very unreliable. I even tried the 2.2 build2 by Phenix using the Clang compiler.
In my experience my phone has never run better while using V2.0 on Oreo. Even compared to Nougat. However I probably wasn't flashing it right.
I know next to nothing about android. I just recently learned you are supposed to flash magisk after flashing the kernel. I have only done this procedure in the specific versions listed above.
The LG V20 is my first smartphone. And I must say it has been quite a nightmare. The only redeeming factor is that after two years of using it. I've figured out how to make it sound decent.
I digress... What versions of the kernel have worked best for you? Can you go around flashing away different versions without messing things up?
Good luck!
I've been using the stable 2.2 "re-upload" version for my VS995 on AO oreo for a while now. It is the one that has given me the least issues. Wish I had more info for you, but honestly it was just a LOT of trial and error to find what worked for me... Don't know why and I'm done trying to figure it out
All I can say is good luck. None of them are perfect for me. This version has the occasional crash of an app in the background but that seems to be it, even after many months of heavy use. So if you mean "has the least bugs" when you say "working best" then that is my answer.
The version I am talking about is located here by the way:
https://androidfilehost.com/?w=files&flid=297449
Just make backups and try them all out... why not, ya know?
Not sure what issues you guys have been having my phone has been great.
Qron said:
Right now I'm using mk2000 2.2 beta 34 kernel and it gives me a way smoother experience than 2.2 or 2.1 stable. It's paired with 20b TWN by reza_xdv.
Click to expand...
Click to collapse
This was the post i was looking for. Flashed the kernel and Magisk. The phone really cooks! In a good way. Performance wise and heat wise lol. Only under load. I feel like I have a good phone finely. It's only been 3 years. Now if I can only get my spell check to work.
@xSodxManx. Thanks a lot for the heads up on this one. I'll look into it.
You can also check version compiled by Phoenix591
https://androidfilehost.com/?fid=6006931924117931114
I guess I'm back to 2.0. My alarm service crashed and I was late for work. First time ever. I'm not 100% sure it was the kernel but I'm almost positive as my phone started exhibiting strange behavior pryor to the battery swap. I even rebooted before going to sleep. I was charging a new Perfine 10000mAh battery. I have read reviews that it made some customers phone unstable. I understand how important clean power is in any electrical system. In phones the battery seems to be the only component in the powersupply that delivers a clean voltage. It's entirely possible that the balancing system in the new battery screwed things up on the first charge.
Qron said:
You can also check version compiled by Phoenix591
https://androidfilehost.com/?fid=6006931924117931114
Click to expand...
Click to collapse
I haven't had much luck with that. I didn't like the way the phone booted. Then I got a kernel panic and jumped ship.
I'm still struggling with this. However I think I have discovered something. I cannot find any sort of installation instruction from the official MK2000 thread. I originally made the assumption that clearing Dalvik cache and cash in TWRP was sufficient enough. However it seems that that doesn't clear the app cache that can be found in system Settings.
After having issues trying the other MK2000 versions, I decided to revert back to 2.0. After doing so the system still ran like crap, until I cleared the cache in system settings. I have now achieved system stability and performance I was only able to achieve through a factory reset.
The complete [installation / upgrade / downgrade] procedure is as follows.
1. Flash kernel zip.
2. Flash magisk NOT version 2.2
3. Clear Dalvik cache / Cashe in TWRP
4. Clear app cache in system settings.
For now I'm sticking with 2.0. However perhaps when I get board I will try the other mentioned versions.
I am particularly interested in the mysterious Stendro re-upload. It did give interesting results.
I've put my V20 through some grueling real world tests. Testing the following Kernel versions:
MK2000 V2.0
MK2000 V2.2 Beta 34
MK2000 V2.2 PHXCLANG2-rebuild
MK2000 V2.2 Stendro re-upload
Stock Kernel
I was running the following programs for the test:
Google maps (driving directions)
Google assistant
USB Audio player pro (FLAC player, with dedicated audio driver)
Flud (torrent software)
Messages (sms)
Contacts
I set all cores to performance in Kernel Auditor
In a nutshell I can see no difference between reliability between the MK2000 versions. I would recommend using ether the Beta34 or the PHXCLANG. I find they both lag in different ways but equally so. During the testing I did run into some issues where the music would stop playing or the navigation stoped. Aside from noticing the second screen getting killed. I believe this is all due to the LMK not the Kernel, which sounds like a bad idea to me but what do I know.
Then I went back to the stock kernel. Oh boy! I forgot how slow this phone can be. It brought back feelings of nostalgia. To a time when I was afraid to root my first android smartphone. And utterly completely frustrated and disappointed with it. My dispatcher called me 2 times in a row and a friend shortly after. My phone never even displayed the answer screen.
I had heard rumors that there were problems with the MK2000 kernel. I remember the words "crashing in the background". I would like to be informed of the issues it may possess.
During my initial test of the stock kernel. I ran into the issue where the music stoped. However when going back to the app, instead of the app being reset to the state it was when first opened. The app was paused precisely where the music stoped. Also I think the DAC sounds better on stock. It could be because my ears got a chance to rest over the weekend. These seem to be the only differences thus far. I'm going to continue testing stock kernel and see if I notice anything different.
It's been a couple days running the stock kernel and I have to say it's been quite an interesting experience. I had to uninstall Google or revert back to the original version. And after doing so voice input and Google Assistant have been working better than ever. I still believe the DAC sounds better. I recall being amazed with if the difference between MK 2000 nougat and MK 2000 Oreo.
I'm starting to believe that you have to do a factory reset after flashing the kernel. So I feel all of these this testing is almost for nothing. And would also explain why different users are getting different results. I am getting a lot of bugs with apps such as titanium backup. Where are the app list doesn't load. And I had an issue where LG music service was disabled and I couldn't enable it. The LG music app is apparently the only way to select a ringtone or notification sound. Which I'm very upset about. I was able to fix it by installing an APK.
I've been on A-O_VS995_20C_1.3.1.zip with VS995_v2.2-mk2000.zip for a LONG time. Used to have some heat issues intermittently... Afer i installed Greenify my heat issues have gone away... phone is snappy, stable, and battery has been really good.
Flash order:
Clean (wipe cache, dalvic, system) 3 times minimum.
Flash rom
Flash kernel
Flash magisk
Reboot.
Use the correct version of TWRP.
( no issues as mentioned two above.)
Not exactly what you asked for, but apparently a promising kernel is almost out that you might be interested in trying out: https://forum.xda-developers.com/v20/development/bounty-kernel-h990ds-stock-oreo-t3952667
EDIT: disclaimer, I haven't tried it myself yet, and would love to hear from people when it comes to fruition
the clang variant is superior in performance