Database Develop

Stock recovery and upgrading Lollipop with future OTAs after rooting

Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!

LordGrahf said:
Hello everyone,
I'm back to a nexus 6 after a very short stint with a 6+.
A little background for my questions: This is the very first time that I rooted a phone. I'm rooting to only install these 3 apps:
adaway
titanium backup
greenify
I do not plan on using any custom ROMs or kernels.
I see from all the guides and tutorials that people also create a custom recovery whenever they root. I haven't done that yet and wasn't sure if I had to. I would like to maintain the stock recovery that I have currently so that I can go back to stock if I unRoot. My questions are:
1. Am I wrong in thinking that I can still use the stock recovery if I unRoot?
2. When a new OTA comes out and I flash it (since I'm rooted an no longer can install them automatically), will that also upgrade my still stock recovery properly?
3. Following up on the previous question, when I upgrade manually because I'm rooted, would that be a fresh install where I have to go in and configure things the way I like them again (system settings, apps and their settings, root the phone again, etc)?
Thanks in advance!
Click to expand...
Click to collapse
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.

Thank you sir!

obsanity said:
1. No, you're not wrong. Recovery will stay stock and can be used normally
2. You can't simply flash the new OTA. This will not work manually nor automatically.
3. All you need to do is not flash the user data image and you will not loose your data, settings etc. You will loose root however. See bellow.
Google posts android stock images for each device typically before OTA hits your phone. That's what you want to grab and use for the update. Just make sure you don't run the automatic scripts that come with those images because you need to avoid flashing user data image.
OTA zip file does you no good unless you get your system back to unmodified stock.
Click to expand...
Click to collapse
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.

I'm kinda curious myself. I had no idea root killed OTA's. Maybe I wouldn't have done that if I knew that. I'm very new to the Nexus device. It's my 1st. I unlocked the bootloader and rooted already.
Sent from Mark's Nexus 6

crowbarman said:
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?

I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!

LordGrahf said:
This is pretty scary. So you can unroot and GI back to stock and still can't update in anyway?
Click to expand...
Click to collapse
not sure what you mean by GI, but according to some others, after uninstalling root via SuperSU an OTA will still not install. This should not be the case unless the boot or recovery images are modified. Easily fixed by following the procedures above to fastboot the stock images on your phone.
kjnangre said:
I have always side-loaded OTAs, I have never flashed anything.
After installing an OTA, on the next reboot, Android takes some time to optimize all your apps. Does this also happen after flashing a new system image? Thanks!
Click to expand...
Click to collapse
Yes, it behaves exactly the same.

crowbarman said:
Based on the OP, it sounds like he has only rooted. Thus, the OTA will work fine. No need to flash image files.
Edit: I see that at least one other member has stated that an unroot still did not allow OTAs to function. That's a bit strange and unique. Not sure what root is modifying to prevent the OTA.
Click to expand...
Click to collapse
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.

obsanity said:
Root on Lollipop is not what it used to be. There are files that need to be modified in order to allow root. That's why this time OTA will fail if you are rooted.
Un-rooting however, will allow OTA as long as it is done properly and all traces are covered up and returned to stock. If it does fail after you have un-rooted, go back to the developer of that un-root method and let the know they missed something.
Here is the best way to un-root. Flash all of the old stock images besides user data image.
Click to expand...
Click to collapse
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.

crowbarman said:
That makes sense. Is there a manual root procedure or list of required modifications for root out there? I did some precursors searches but Came up empty. Can't tell what's missing in SuperSU unroot without those details.
Click to expand...
Click to collapse
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1

obsanity said:
Explanation from Chainfire:
https://plus.google.com/113517319477420052449/posts/S5zoKTzKUW1
Click to expand...
Click to collapse
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?

crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.

obsanity said:
That's the problem with Chainfire's work... he does not release source.
Again, best un-root method is to flash original images less user data.
Click to expand...
Click to collapse
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?

LordGrahf said:
Thanks for sharing this info. Its a bit concerning tbh. Is there a cleaner way to root other than using superSU?
Click to expand...
Click to collapse
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.

obsanity said:
I'm afraid not but Chainfire's is probably the cleanest possible. Koush was the one with an open source solution but he hasn't updated his to 5.0 yet.
Click to expand...
Click to collapse
There is an argument that publishing the method would allow Google to close it that much quicker, I suppose.

crowbarman said:
Thanks for this. A good read, but I'm surprised nobody has demanded more details than 'patched the policies in SELinux'. Not that I don't trust Chain fire (I do) , but who really knows what has been done to our phones?
Click to expand...
Click to collapse
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.

I assume that the encryption doesn't get in the way of being able to flash the images?
When I went from 5.0 to 5.0.1 on my old Nexus 5 all I did was flash the two new 5.0.1 images I extracted from the full factory image, then re-rooted. This is far cleaner than reverting back to the previous image then doing an OTA. I've not had to update my N6 yet so I don't know if my method will work still, but I hope it does.

Chainfire said:
The base changes and reasoning for those changes are actually documented on my website. Specific policy adjustments are present in plain text in the supolicy executable, as any hex editor will show you. Those who really wanted to know rather than whine about OSS, know.
By far most policy adjustments just drop audit log output for contexts that are already permissive, though.
All that information is still completely useless unless you understand SELinux in detail and how it's implemented on Android, though.
Click to expand...
Click to collapse
Thanks for the additional information.
I did spend a fair amount of time reading your documentation but failed to utilize a hex editor. I am not 'whining' about the lack of open source, rather, simply mildly surprised, but your website aptly describes the challenges with 5.0. Many are used to various root methods being available.
Your solution is fine with me.. I love your work.
Edit: I thought I'd add that the discussion has devolved from the OP, which was whether an OTA can be applied after uninstalling root. The answer was no, due to the unknowns about what still might be modified following the uninstall via SuperSU.

Temporary root to debloat? possible to unroot

I want to be as close to stock as possible. Is it possible to flash (with ODIN) 100% stock rom then root with unikernel and remove all the t-mobile apps and knox etc..then go back to stock kernel and unroot? how would I unroot?

anaveragehuman said:
Why would you want to unroot?
I would flash CF-Auto-Root from ODIN, do what I need to do, then open the SuperSU app, scroll down, and click Full Unroot.
Click to expand...
Click to collapse
I want to unroot because the phone is for my gf who knows nothing about technology, I don't want her to accidentally do anything to the phone if it's rooted lol. Does CF auto root work 100% for th S6 now? I always used unified kernel.

euklid said:
I want to unroot because the phone is for my gf who knows nothing about technology, I don't want her to accidentally do anything to the phone if it's rooted lol. Does CF auto root work 100% for th S6 now? I always used unified kernel.
Click to expand...
Click to collapse
my wife's phone is rooted and she wouldn't even know it if she seen it.
Women who don't know about root which is most in that casee could care less . As long as theyre facebook and cam works...lol .The only time they could do harm is Going to the extent of booting into twrp in which they would not even know the first thing about flashing a zip .
Root her phone debloat it and it's done.
Sent from my SM-G920T using XDA Free mobile app
---------- Post added at 09:52 AM ---------- Previous post was at 09:49 AM ----------
euklid said:
I want to unroot because the phone is for my gf who knows nothing about technology, I don't want her to accidentally do anything to the phone if it's rooted lol. Does CF auto root work 100% for th S6 now? I always used unified kernel.
Click to expand...
Click to collapse
5.0.2 was good for cf auto
Since 5.1.1 you cant downgrade and requires a rootable kernel and most people do it this way .
Just flash uni kernel v8 tar in Odin and reboot or flash twrp with Odin and then flash the unikenrel v8 zip before you reboot
Sent from my SM-G920T using XDA Free mobile app

androidddaaron said:
my wife's phone is rooted and she wouldn't even know it if she seen it.
Women who don't know about root which is most in that casee could care less . As long as theyre facebook and cam works...lol .
Click to expand...
Click to collapse
Exactly. +1

Don't do it, she'll hate you because stuff isn't going to work for her.
Just disable apps she doesn't want and leave stock with everything working.
Pp.

I'd be interested in this because I need to use an app for my work that checks for root and xposed framework. But I'd still like to use a ROM with enhancements like low battery camera etc and without all the useless apps.

MrManH said:
I'd be interested in this because I need to use an app for my work that checks for root and xposed framework. But I'd still like to use a ROM with enhancements like low battery camera etc and without all the useless apps.
Click to expand...
Click to collapse
There are root cloaking apps which are meant to hide that you have root access. I cannot speak as to their effectiveness but they are out there.
I told my employer that I wasn't unrooting my phone and that if somebody needed something so urgently as to pull me away from my personal time when I work 9-5:30 m-f that I didn't rhink it too much to ask that said individual(s) contact me personally. They actually came to agree with me.

cwhiatt said:
There are root cloaking apps which are meant to hide that you have root access. I cannot speak as to their effectiveness but they are out there.
I told my employer that I wasn't unrooting my phone and that if somebody needed something so urgently as to pull me away from my personal time when I work 9-5:30 m-f that I didn't rhink it too much to ask that said individual(s) contact me personally. They actually came to agree with me.
Click to expand...
Click to collapse
These don't work for the app I'm using, I looked into it. I have no use for root other than debloating the phone, and the built in features of custom roms (which I believe don't require root access).

MrManH said:
These don't work for the app I'm using, I looked into it. I have no use for root other than debloating the phone, and the built in features of custom roms (which I believe don't require root access).
Click to expand...
Click to collapse
If you use systemless root, delete /su/xbin_bind and then follow this thread's instructions http://forum.xda-developers.com/nexus-5x/general/passing-safetynet-root-t3307659 nothing will be able to detect root without requesting it [which you can deny] and you're golden.

Debloating ROM

Hi there
I would like to get started customising my ROM, for my OnePlus 3, but first i have a couple of questions. I am pretty new into this topic.
How do people get started customising ROMs? Are there any good tutorials? And in what points are most popular to start optimizing? Kernel, apps.. etc.?
I actually like the OxygenOS for the OnePlus 3, so i was actually thinking, my starting point would be OxygenOS. If i start tweeking and debloating, would i still be able to follow OTA updates? Or will they overrider my customised ROM?
What i am most interested in, is how to debloat my ROM, before i flash it. I am pretty OCD, with which apps should be installed, when i flash a new ROM to my phone, and my OCD freaks completely, if i have to uninstall apps, after they have been installed to a complete fresh install. So how do i remove fx Google Play Music, and all the other crapware i dont like?
If i remove OnePlus' music app, will this be installed when a new OTA update is installed?
I have read around the internet how to debloat ROMS, but it is very different, if it is a lollipop rom, or marshmallow. I have been able to extract the system.new.dat file, and see all apps, and remove them. The problem is, when i try to pack them, and flash them to the phone, it simply doesn't. Is there a complete guide, which works.
I can see there is a OxygenLite version, which is quite nice, but doesn't fit my needs exactly, why i want to make my own. Is this rom able to follow Oneplus OTA updates?
Hope someone can answer my questions. Thanks!

First you should root it. Then if you look through the OnePlus 3 forums, someone made a script that debloats your phone. As for OTA updates. You will still be able to update to the latest version with workarounds.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app

jdawgg21 said:
First you should root it. Then if you look through the OnePlus 3 forums, someone made a script that debloats your phone. As for OTA updates. You will still be able to update to the latest version with workarounds.
Click to expand...
Click to collapse
Thanks for your reply. My phone is already rooted, and twrp recovery is installed. Guess I can't use the stock recovery?
But I was actually more interested in knowing, how to extract the rom on my computer, and then debloat the stock rom, and then "compile" it back to its original system.new.dat form. I have searched the forum, but it only seems to work on lollipop.

Just erase undesired apps with a root file explorer or titanium backup then make an nandroid backup. If you want. .dat format you can use Lillopops howtos it hasn't change, it's just an imaget of a partition
http://forum.xda-developers.com/and.../how-to-conver-lollipop-dat-files-to-t2978952.
But it's too much a hassle for nothing, much esier to debloat and make an nadroid backup.

Striatum_bdr said:
Just erase undesired apps with a root file explorer or titanium backup then make an nandroid backup. If you want. .dat format you can use Lillopops howtos it hasn't change, it's just an imaget of a partition
http://forum.xda-developers.com/and...how-to-conver-lollipop-dat-files-to-t2978952.
But it's too much a hassle for nothing, much esier to debloat and make an nadroid backup.
Click to expand...
Click to collapse
Does rooting render the warranty void?

Devesh2094 said:
Does rooting render the warranty void?
Click to expand...
Click to collapse
I don't care generally.
I think it doesn't affect warranty but check on their website.
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk

Devesh2094 said:
Does rooting render the warranty void?
Click to expand...
Click to collapse
Unlike other oem, unlocking bootloader,rooting,installing custom roms and kernel doesn't void warranty.
still i recommend you that check TOS on their official website

Battery life really bad

The battery life that i am getting is just 7-8 hrs which i think is really really bad on the Note 5, the phone is just a month old.
Android OS is consuming the most of the battery please help me with the fix
Attached is the screenshot of the battery stats.

Yeah, the battery life of this device kind of sucks without any modifications. Don't worry, I was equally disappointed too - it's not just your device.
You should proceed to root your device if you are seriously wanting to do something about battery.
Once you're rooted, you may:
-Install ForceDoze, to force it to not wakeup anywhere near as much when the device is not being used.
-Install Greenify, to automagically freeze all unneeded apps (donate for system). This will speed up your phone, free memory and save battery.
-You can install and try L-Speed, which should help your battery out a lot when using an unoptimised Samsung firmware.
-And finally installing Xposed, which may require a little research. This will let you enable all of the modules provided by the above programs to give you deeper system integration. Ultimately saving you battery. Set Greenifies working mode from root to xposed in settings.
I can't help you out with a custom note 7 based ROM as they all seem to be broken in some way at this stage.

Turbine1991 said:
Yeah, the battery life of this device kind of sucks without any modifications. Don't worry, I was equally disappointed too - it's not just your device.
You should proceed to root your device if you are seriously wanting to do something about battery.
Once you're rooted, you may:
-Install ForceDoze, to force it to not wakeup anywhere near as much when the device is not being used.
-Install Greenify, to automagically freeze all unneeded apps (donate for system). This will speed up your phone, free memory and save battery.
-You can install and try L-Speed, which should help your battery out a lot when using an unoptimised Samsung firmware.
-And finally installing Xposed, which may require a little research. This will let you enable all of the modules provided by the above programs to give you deeper system integration. Ultimately saving you battery. Set Greenifies working mode from root to xposed in settings.
I can't help you out with a custom note 7 based ROM as they all seem to be broken in some way at this stage.
Click to expand...
Click to collapse
Thanks for your help BTW i will not be installing Xposed, but i will suerly do the L-speed, Greenify and ForceDoze. Any thing else that i should do to recover from this battery issue and be on stock as far as possible ?

You can use Agressive Doze in Greenify without root. It will help putting the phone in Doze mode much quicker. It looks like something is keeping the phone awake pretty much all the time.

jadebeer said:
You can use Agressive Doze in Greenify without root. It will help putting the phone in Doze mode much quicker. It looks like something is keeping the phone awake pretty much all the time.
Click to expand...
Click to collapse
this is after rooting and using all apps •

somyatiwari59 said:
this is after rooting and using all apps â?¢
Click to expand...
Click to collapse
Hi, if you have Knox tripped (0x1) then don't bother with software solutions... you need custom kernel either Sickness either SkyHigh. I have spend 2 months in research. First install latest TWRP and them install the new kernel. After that you will lose just 6% overnight instead of 50%.

angelfacekiller said:
Hi, if you have Knox tripped (0x1) then don't bother with software solutions... you need custom kernel either Sickness either SkyHigh. I have spend 2 months in research. First install latest TWRP and them install the new kernel. After that you will lose just 6% overnight instead of 50%.
Click to expand...
Click to collapse
Thanks bro for suggesting, can you leave link to the kernels ?, and after using custom kernels should i uninstall these Root Apps ? Or Unroot the device ?

Pls tell me how to root.I am a newbie at this.
Turbine1991 said:
You should proceed to root your device if you are seriously wanting to do something about battery.
Once you're rooted, you may:
-Install ForceDoze, to force it to not wakeup anywhere near as much when the device is not being used.
-Install Greenify, to automagically freeze all unneeded apps (donate for system). This will speed up your phone, free memory and save battery.
-You can install and try L-Speed, which should help your battery out a lot when using an unoptimised Samsung firmware.
-And finally installing Xposed, which may require a little research. This will let you enable all of the modules provided by the above programs to give you deeper system integration. Ultimately saving you battery. Set Greenifies working mode from root to xposed in settings.
I can't help you out with a custom note 7 based ROM as they all seem to be broken in some way at this stage.
Click to expand...
Click to collapse
pls tell me how to root the note 5.

t JaZzz said:
pls tell me how to root the note 5.
Click to expand...
Click to collapse
somyatiwari59 said:
Thanks bro for suggesting, can you leave link to the kernels ?, and after using custom kernels should i uninstall these Root Apps ? Or Unroot the device ?
Click to expand...
Click to collapse
First things first. We are talking about Marshmallow right???
Rooting is different than installing a custom kernel. Trust me, most of the people don't care about root but only to fix their phone.
IF you have a tripped knox don't go and install, or even worst buy, any applications promising to make battery last longer or 50% overnight to go down to 6%. They cannot...
I will tell you my use case and you will figure out what you want.
I have a Note 5 N9208 with tripped knox. Battery drains horribly losing 8-10% per hour. This is because of tripped knox and all software solutions (Greenify, Naptime, ForceDoze etc) are useless since you CANNOT put the processors to 0 frequency and the only way to solve it is with a customer kernel.
For my model I installed The Sickness kernel. For N920C Dr. Ketan has a kernel which might be good for other models too.
Steps:
Install TWRP from here . Select your model and install it with Odin in AP section.
Install kernel from Sickness for N9208 or arter97 for other models or DR. Ketan's kernel for N920C . It will be a .zip file containing a boot.img file somewhere. Copy the .zip file to a local folder on the mobile and after you boot into TWRP recovery select install and then flash the file.
After installation you are fixed BUT you MIGHT lose the functionality of keeping the WiFi passwords after reboot. THIS is the part where you need to be root.
If the kernel didn't installed SuperSU then install with TWRP SuperSU from here (Some kernels they don't inject SuperSU or installation is damaged). Install BuildProp editor from Google Play , give root permissions and search for 'storage'. Make parameter ro.secure.storage = false and save then reboot.
Unroot from superSU menu to regain access to banking applications. You might need to clear their cache and data if they have already identified the device as rooted.
Don't be afraid as the steps do not need to be executed all together and at once.
Flash TWRP and gain some familiarity with it. It's a nice recovery environment which you enter the same way like the official one. Check also what is the impact in your phone from changing the recovery.
Then copy all the files in you phone and install BuildProp too so you will have it ready. Also It would be nice to BUY and install Package Disabler pro. it is cheap and it will help you to get rid of the annoying messages regarding Unauthorized software etc.
After all these, you can discuss with many wise guys regarding Greenify and Forsedoze and blah blah on how to make your battery EVEN better.

angelfacekiller said:
First thing first. We are talking about Marshmallow right???
Rooting is different than installing a custom kernel. Trust me, most of the people don't care about root but only to fix their phone.
I will tell you my use case and you will figure out what you want.
I have a Note 5 N9208 with tripped knox. Battery drains horribly losing 8-10% per hour. This is because of tripped knox and all software solutions (Greenify, Naptime, ForceDoze etc) are useless since you CANNOT put the processors to 0 frequency and the only way to solve it is with a customer kernel.
For my model I installed The Sickness kernel. For N920C Dr. Ketan has a kernel which might be good for other models too.
Steps:
Install TWRP from here . Select your model and install it with Odin in AP section.
Install kernel from Sickness for N9208 or arter97 for other models or DR. Ketan's kernel for N920C . It will be a .zip file containing a boot.img file somewhere. Copy the .zip file to a local folder on the mobile and after you boot into TWRP recovery select install and then flash the file.
After installation you are fixed BUT you MIGHT lose the functionality of keeping the WiFi passwords after reboot. THIS is the part where you need to be root.
If the kernel didn't installed SuperSU then install with TWRP SuperSU from here (Some kernels they don't inject SuperSU or installation is damaged). Install BuildProp editor from Google Play , give root permissions and search for 'storage'. Make parameter ro.secure.storage = false and save then reboot.
Unroot from superSU menu to regain access to banking applications. You might need to clear their cache and data if they have already identified the device as rooted.
Don't be afraid as the steps do not need to be executed all together and at once.
Flash TWRP and gain some familiarity with it. It's a nice recovery environment which you enter the same way like the official one. Check also what is the impact in your phone from changing the recovery.
Then copy all the files in you phone and install BuildProp too so you will have it ready. Also It would be nice to BUY and install Package Disabler pro. it is cheap and it will help you to get rid of the annoying messages regarding Unauthorized software etc.
After all these, you can discuss with many wise guys regarding Greenify and Forsedoze and blah blah on how to make your battery EVEN better.
Click to expand...
Click to collapse
Thanks bro for helpming me out, i installed Arter Kernel and lets see how does it performs, BTW what else can we do to improve battery life i have uninstalled all root apications that i was using

somyatiwari59 said:
Thanks bro for helpming me out, i installed Arter Kernel and lets see how does it performs, BTW what else can we do to improve battery life i have uninstalled all root apications that i was using
Click to expand...
Click to collapse
There is no magic trick bro. Our phones have to light up 5.7 inches with high definition with 2 sim cards and 4G data coming and going all the time ...
ForceDoze works without root but needs to execute a commandline through ADB. To be honest I don't care since Doze fixed and I cannot measure performance.
From engineering point of view, I have to say that all these applications are nice when you don't use your phone.
If you talk too much or browse too much they are USELESS. If you saw my printscreen, I had a very good overnight behavior but during day I drained the phone since I was talking all day and I was not leaving the phone to rest...

angelfacekiller said:
There is no magic trick bro. Our phones have to light up 5.7 inches with high definition with 2 sim cards and 4G data coming and going all the time ...
ForceDoze works without root but needs to execute a commandline through ADB. To be honest I don't care since Doze fixed and I cannot measure performance.
From engineering point of view, I have to say that all these applications are nice when you don't use your phone.
If you talk too much or browse too much they are USELESS. If you saw my printscreen, I had a very good overnight behavior but during day I drained the phone since I was talking all day and I was not leaving the phone to rest...
Click to expand...
Click to collapse
My phone's standby time is affected thats my problem i drain 100% battery in one go i am ok with it, but the problem is with that standby drain and hence i posted here !!

somyatiwari59 said:
My phone's standby time is affected thats my problem i drain 100% battery in one go i am ok with it, but the problem is with that standby drain and hence i posted here !!
Click to expand...
Click to collapse
With ForceDoze you will be ok. It has complete instructions on how to install it without root. Try to do it after unrooting in order to show you the workaround method. However. It is not doing anything without the Doze patch that kernels are installing.

Thank you but....
angelfacekiller said:
First things first. We are talking about Marshmallow right???
Rooting is different than installing a custom kernel. Trust me, most of the people don't care about root but only to fix their phone.
IF you have a tripped knox don't go and install, or even worst buy, any applications promising to make battery last longer or 50% overnight to go down to 6%. They cannot...
I will tell you my use case and you will figure out what you want.
I have a Note 5 N9208 with tripped knox. Battery drains horribly losing 8-10% per hour. This is because of tripped knox and all software solutions (Greenify, Naptime, ForceDoze etc) are useless since you CANNOT put the processors to 0 frequency and the only way to solve it is with a customer kernel.
For my model I installed The Sickness kernel. For N920C Dr. Ketan has a kernel which might be good for other models too.
Steps:
Install TWRP from here . Select your model and install it with Odin in AP section.
Install kernel from Sickness for N9208 or arter97 for other models or DR. Ketan's kernel for N920C . It will be a .zip file containing a boot.img file somewhere. Copy the .zip file to a local folder on the mobile and after you boot into TWRP recovery select install and then flash the file.
After installation you are fixed BUT you MIGHT lose the functionality of keeping the WiFi passwords after reboot. THIS is the part where you need to be root.
If the kernel didn't installed SuperSU then install with TWRP SuperSU from here (Some kernels they don't inject SuperSU or installation is damaged). Install BuildProp editor from Google Play , give root permissions and search for 'storage'. Make parameter ro.secure.storage = false and save then reboot.
Unroot from superSU menu to regain access to banking applications. You might need to clear their cache and data if they have already identified the device as rooted.
Don't be afraid as the steps do not need to be executed all together and at once.
Flash TWRP and gain some familiarity with it. It's a nice recovery environment which you enter the same way like the official one. Check also what is the impact in your phone from changing the recovery.
Then copy all the files in you phone and install BuildProp too so you will have it ready. Also It would be nice to BUY and install Package Disabler pro. it is cheap and it will help you to get rid of the annoying messages regarding Unauthorized software etc.
After all these, you can discuss with many wise guys regarding Greenify and Forsedoze and blah blah on how to make your battery EVEN better.
Click to expand...
Click to collapse
First of all.Thank you sir but the problem is that my device is N920G.

t JaZzz said:
First of all.Thank you sir but the problem is that my device is N920G.
Click to expand...
Click to collapse
Then you can go to arter97 in section n920cig Also dr ketans should work too

I had a bootloop after flashin Twrp on N920C. Only solution was flashing from Odin the stock firmaware.
In the end, no custom recovery, knox tripped and no battery optimization...
I'd like to retry but I don't want to lose everything another time

alexross said:
I had a bootloop after flashin Twrp on N920C. Only solution was flashing from Odin the stock firmaware.
In the end, no custom recovery, knox tripped and no battery optimization...
I'd like to retry but I don't want to lose everything another time
Click to expand...
Click to collapse
You flashed twrp from the official site, for your model and it didn't work?

angelfacekiller said:
You flashed twrp from the official site, for your model and it didn't work?
Click to expand...
Click to collapse
yes, if I start in custom recovery I have twrp working but when I start the os I've a bootloop. Also I tried wiping cache and system but no luck, bootloop.

Try with stock firmware from smartswitch and then flash twrp. From what you said you are flashing an image not from samsung.

Resolved, i rooted first than I flashed the recovery. No more problems

Question Hide status bar time clock?

Anybody know how to hide status bar time? In previous android versions,there used to be an option to hide clock but can't find on android 12. BTW, unrooted OnePlus 10 Pro global edition. Thanks

You can use system UI for that

You can use system UI for that

dladz said:
You can use system UI for that
Click to expand...
Click to collapse
I tried to use it but was unable to provide the app necessary permissions. Currently, I am unrooted, adb command mentioned in the app for the required permissions did not work for me. I have been using this app for years but on rooted phones. I will try it again. Thanks
Update: There is another System ui tuner app by Bryan that worked just fine without any permissions

Gr8man001 said:
I tried to use it but was unable to provide the app necessary permissions. Currently, I am unrooted, adb command mentioned in the app for the required permissions did not work for me. I have been using this app for years but on rooted phones. I will try it again. Thanks
Update: There is another System ui tuner app by Bryan that worked just fine without any permissions
Click to expand...
Click to collapse
Yep you'll definitely need to provide them permissions or root.
Is adb working? Can you say adb devices and get a feedback code?
Also why not root? It's a OnePlus, the one phone you can root without repercussions.

I have always rooted my phones for the last 16 years and most likely will root this one too. But quite honestly, at least for my needs, benefits of root vs.complexity of rooting process, steps necessary for each upgrade is not there. Lack of official twrp, issues r/t Titanium backup, etc are not encouraging. That being said, the moment I see a good custom ROM for this phone, I know I will root again. Thanks

Gr8man001 said:
I have always rooted my phones for the last 16 years and most likely will root this one too. But quite honestly, at least for my needs, benefits of root vs.complexity of rooting process, steps necessary for each upgrade is not there. Lack of official twrp, issues r/t Titanium backup, etc are not encouraging. That being said, the moment I see a good custom ROM for this phone, I know I will root again. Thanks
Click to expand...
Click to collapse
Funny you should say that, so have I, and in all honesty you mustn't have seen the guide I made on rooting as it's extremely clear.
Plus as from the 8 pro on wards, you simply do not need twrp, period..it'd be nice to have MSM, but we already have fastboot enhance which is actually better as it doesn't relock the bootloader .
Titanium also hasn't worked correctly for a while, it has issues with restoration.
Swift back up works perfectly for those needs and it can back up to the cloud..
I'm not going to go into the benefits of rooting but just getting rid of ads is massive for me, I couldn't stomach a device which allowed them.
But you do you

ROMs are coming soon btw

Guide to updating, rooting, Magisk and fastboot enhance.
You don't need twrp
(Guide) Rooting, payload dumper, magisk_patched guides NE2213
Hi all, Thought i'd share a guide on how to get these boot images yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it without obtaining one yourself Please read the process before...
forum.xda-developers.com