Of course no one knows for sure (or is telling at least) when the update will happen, but I'm wondering if there is anything special I could/should do to be ready for it. My phone is completely stock in terms of not being rooted etc. The only things I've done were to replace touch wiz with Apex launcher and then use package disabler pro to disable a bunch of stuff (including touch wiz) that I'm not using.
1. Will having verizon, samsung, and many other things disabled cause any problems with the updat when it comes?
2. To be safe, should I re-enable all the disabled built in apps and set touch wiz back to the default launcher before allowing the update just to be safe?
No need for any of that, as long as your device indicates it's official in the settings then you should receive the OTA when ever it comes.
I think you need to convert default settings on disabler package.
Related
Hello
I don't have much experience with custom ROMs, I've tinkered with my Samsung Tab 2, but I still have a few questions.
First of all, I have a stock M7, and as far as I understand HTC won't update this device to Android 6.0 Marshmallow. So I decided when custom 6.0 ROMs get stable enough - I'd like to dive in and try this side of Android I haven't yet experienced. I plan on sticking with my M7 for at least a year or two, as I cannot justify buying a new flagship phone for what I consider to be a slight upgrade, I'm very happy with my M7.
#1 Dumping my current ROM
My M7 still has a 1+ year warranty, and due to the camera purple tint issue, I'd like to have a full backup of my phone (ROM, kernel, baseband etc) if I was forced to go through the warranty process. Is it possible to dump a sort of RUU-type file? The CW field on my phone has the carrier embeded into it, and I cannot find a RUU that exactly matches it, so I'm afraid it could void my warranty if they checked it.
#2 Custom ROM updates
I've found apps in the Play store that claim to provide OTA updates for certain custom ROMs, but I don't understand how this works. Are there no OTA updates for custom ROMs? My Samsung Tab 2 has CM11 installed, and I've never received a notification or anything that an update was ready. I really don't want to keep flashing ROMs and constantly backing up/restoring my data on my phone. The reason I didn't switch to custom ROMs earlier was this issue. I had an iPhone a long time ago, and updating to a new iOS version meant wiping the phone because I always used to jailbreak it because it was locked to a different carrier. That's a pain, and I don't want that. Is this an issue for specific ROMs? Do certain custom ROM developers provide this feature? If there is no "official" OTA support, is there a way to just update and not reflash a new ROM version?
#3 Custom ROM selection
This sort of ties in to my 2nd question. I want to have an almost OEM type experience with updates and so on. As far as I understand, Cyanogenmod would be the way to go, but I didn't really like it on my Samsung Tab 2 - I had battery drain issues, I didn't really like the UI, but I could live with it by using a different launcher, using apps to tweak the UI and so on. But what would be the ROM to use, in order to have an "OEM" experience?
#4 Kernels
I've wanted the double-tap to wake feature on my phone since (if I remember correctly) the M8 launched and had this feature. As far as I understand, I'd need to use a custom kernel in order to have this feature. Does that mean that I have to choose a specific ROM, or can I use any ROM with any kernel? Also ... updates? If I update my ROM - will the kernel be updated, do I have to update the kernel when updating the ROM?
Want to make the phone faster and less harrasment will help me ftom slamming the phone to the floor from rage
I already disabled animations as it didnt help anything and atopped the phone from beibg lethargic
If i root the phone will this allow me to disable htc services and apps from running or to remove them? Dont care to install any other rom. I have looked through the roms here previously and people had comnebts with issues so not going from a crap os to another problematic rom. Just want to slim down the htc crap inside to make it zippy
Most important is the constant harrasment for updates and notifications like me doing a print screen updating a software and such. I went to eat i took a dump i killed an ant. Tired of these stupid notifications tellibg ne what i did. Its unnecessary
Sorry part rant part asking for help thank you
rocketman122 said:
Want to make the phone faster and less harrasment will help me ftom slamming the phone to the floor from rage
I already disabled animations as it didnt help anything and atopped the phone from beibg lethargic
If i root the phone will this allow me to disable htc services and apps from running or to remove them? Dont care to install any other rom. I have looked through the roms here previously and people had comnebts with issues so not going from a crap os to another problematic rom. Just want to slim down the htc crap inside to make it zippy
Most important is the constant harrasment for updates and notifications like me doing a print screen updating a software and such. I went to eat i took a dump i killed an ant. Tired of these stupid notifications tellibg ne what i did. Its unnecessary
Sorry part rant part asking for help thank you
Click to expand...
Click to collapse
You can uninstall apps on a rooted phone, but if you run stock ROM you will get notifications about firmware updates if you are not on the newest firmware
No way at all (configuration or an app to diable) to disable those stupid notifications like print screen or download finished or system update available whatsoever?
I downloaded an app called diableservice from play store and seems it can disable those things. No?
rocketman122 said:
No way at all (configuration or an app to diable) to disable those stupid notifications like print screen or download finished or system update available whatsoever?
I downloaded an app called diableservice from play store and seems it can disable those things. No?
Click to expand...
Click to collapse
Why not flashing a rom that allow you to remove the HTC bloatware you doesn't want at the installation? InsertCoin for example offer this option. You can always remove the bloatware yourself from your stock rom using root, but you won't be able to install ota updates anymore after that which is why I propose you to go for a custom rom (since the only benefit of a stock rom, imo, is ota updates).
And don't forget that all bloatware installed on the /system partition must be removed when booted in a custom recovery. If you want to remove them when booted in the OS, you'll also need a custom kernel since the stock one will revert any changes made in the /system partion
It took me a long time but I have finally gotten things settled down and working adequately on my new 405QA with Android 9, root w/Magisk, etc. I read here <https://www.theandroidsoul.com/lg-v40-update/> and elsewhere there may be an Android 10 coming. While for some that may be great news, for me it isn't. I need to rest and recover from the migration from my old Samsung Note 3 with 4.4.2!
So the question is: how do I 100% avoid any new Android OS updates from being (a) downloaded and (b) installed? In developer options, I have turned OFF "automatic system updates". But I fear this is not enough.
On my old Samsung, rooted with SuperSu, this alone seemed to prevent OS updates. But somehow I wonder if using Magisk and all will make preventing updates a bit different. What is the best way to handle this?
Thanks!
So, what you have done already is enough. Also, for a number of carriers you only get OTA if you are with the original firmware so if you cross-flashed your phone to unlocked US kdz, it is unlikely you would get any OTA updates even if you didn't disable in developer options. Any further options, you'd need to be rooted (which you are), disable/freeze both 'Software Update' apps and 'Fota Update' app. Titanium Backup is the best to freeze these.
Android# said:
So, what you have done already is enough. Also, for a number of carriers you only get OTA if you are with the original firmware so if you cross-flashed your phone to unlocked US kdz, it is unlikely you would get any OTA updates even if you didn't disable in developer options. Any further options, you'd need to be rooted (which you are), disable/freeze both 'Software Update' apps and 'Fota Update' app. Titanium Backup is the best to freeze these.
Click to expand...
Click to collapse
Thanks. Have not cross-flashed but I have used Magisk debloat to deal with fota and software updater. I feel better/safer now. Cheers
Hey there guys,
I just received my s21 ultra (G998B) and planning to root it. I had a few questions since I’m new to this and wanted some clarifications:
1) If I root the phone can I update it OTA through the settings or do I have to update it by another method? Will I lose root/data/apps if I do that?
2) If I lose root when updating it, can I just root again and be all set? Or do I have to follow another procedure for that?
3) I am planning to debloat a few apps and services that I won’t be using, if I update the system/software will the stuff that I debloated come back and will I have to do the debloat again?
Thank you for all the help.
paul_cherma said:
Hey there guys,
I just received my s21 ultra (G998B) and planning to root it. I had a few questions since I’m new to this and wanted some clarifications:
1) If I root the phone can I update it OTA through the settings or do I have to update it by another method? Will I lose root/data/apps if I do that?
2) If I lose root when updating it, can I just root again and be all set? Or do I have to follow another procedure for that?
3) I am planning to debloat a few apps and services that I won’t be using, if I update the system/software will the stuff that I debloated come back and will I have to do the debloat again?
Thank you for all the help.
Click to expand...
Click to collapse
1- Probably not usually the root or recovery will block OTA updates from installing, even if they download.
2- If you lose root, you can USUALLY re-root assuming the same root method wasnt patched. If it was patched, a new root method (though probably still through magisk) will be needed. If this is the case, its up to the dev to find that method, you might be without root for a while.
3-if you debloat, and receive an OTA, your will probably need to de-bloat again, thought I havent personally had experience with this.
Why are you rooting? Just to de-bloat? If so, root isn't really necessary...
As someone who's been in the rooting stage for many years, i can answer your questions.
1. You can not update your phone through OTA updates after rooting the device, as the device was modified in an unauthorized way. And since you own a galaxy phone, the e-fuse within the motherboard will blow and knox will be permanently blown. You can no longer use samsung pay, google pay, and any other app that uses the safetynet api, even after you unroot the device.
2. You will lose root every time you update. You will need ODIN on your PC in order to properly update your firmware and to re-root your device by following the procedure again that you used to root your device, unless samsung patched the method you used to root your device. You can always check what bootloader version you're on within the firmware. For example, on the galaxy S8, the firmware version is N950U1UES5CRG9. The 5th to last number of the firmware will tell you. In this case, N950U1UES5CRG9 is the 5th bootloader version. Keep this in mind once samsung starts to update your phone often.
3. You will have to debloat again from scratch. In order to fully update your device through ODIN, you need to download the full firmware file containing an AP (Firmware), BL (Bootloader) , CP (Modem), and CSC (Carrier File) and manually flash them.
Do keep in mind, it is possible to soft brick or even hard brick your device, so back up your data frequently if you decide to tinker with your device.
Thank you for the detailed answer. I just updated my software to the latest official one by Samsung (April 1st security patch) but I am not rooted yet. I guess I could live with the fact that I can root the phone now and stay on this software version/security patch until I upgrade, since I would have to go through a lot of hassle to set-up the phone the way I wanted. But the main reason why I want to get the official updates is because of the camera improvements that Samsung does, since the main reason of me getting this phone is the camera. And there are some root-required tweaks that I absolutely need such as Viper, and some xposed tweaks also. I like the Stock ROM of Samsung, it really has come a long way at least imo throughout the years, as I have been a Samsung user since day 1 but:
Would it be a good idea to install a custom ROM then? I am reading the description of a few custom ROMs and it seems like I can “retain everything” by simply dirty flashing the ROM and following the dev’s instructions on how to retain root whenever the developer updates it. Is that a better route to take you think? I can keep my device rooted, and still get the updates through a custom ROM.
paul_cherma said:
Thank you for the detailed answer. I just updated my software to the latest official one by Samsung (April 1st security patch) but I am not rooted yet. I guess I could live with the fact that I can root the phone now and stay on this software version/security patch until I upgrade, since I would have to go through a lot of hassle to set-up the phone the way I wanted. But the main reason why I want to get the official updates is because of the camera improvements that Samsung does, since the main reason of me getting this phone is the camera. And there are some root-required tweaks that I absolutely need such as Viper, and some xposed tweaks also. I like the Stock ROM of Samsung, it really has come a long way at least imo throughout the years, as I have been a Samsung user since day 1 but:
Would it be a good idea to install a custom ROM then? I am reading the description of a few custom ROMs and it seems like I can “retain everything” by simply dirty flashing the ROM and following the dev’s instructions on how to retain root whenever the developer updates it. Is that a better route to take you think? I can keep my device rooted, and still get the updates through a custom ROM.
Click to expand...
Click to collapse
That really varies depending on the custom rom you go for. Usually when you dirty flash a rom, you would need to re root your device, but some (not all) roms are persistent with root after system updates. Do keep in mind if you switch to a custom rom, your system might be more buggy and crash more often. One thing i will say though is that xposed is outdated. The last android version xposed officially supported was either 8 or 9. When it has to come down to certain mods you'd wish to have with root, take that into consideration too, as it might make your device really unstable if it's too outdated or if there's a buggy port available. I've dealt with that issue too many times on my phones.
HighOnLinux said:
That really varies depending on the custom rom you go for. Usually when you dirty flash a rom, you would need to re root your device, but some (not all) roms are persistent with root after system updates. Do keep in mind if you switch to a custom rom, your system might be more buggy and crash more often. One thing i will say though is that xposed is outdated. The last android version xposed officially supported was either 8 or 9. When it has to come down to certain mods you'd wish to have with root, take that into consideration too, as it might make your device really unstable if it's too outdated or if there's a buggy port available. I've dealt with that issue too many times on my phones.
Click to expand...
Click to collapse
if xposed is outdated, what is the new thing the comunity is migrating to? All the privacy, security, and customizability tools available through xposed must go somewhere, right?
Twodordan said:
if xposed is outdated, what is the new thing the comunity is migrating to? All the privacy, security, and customizability tools available through xposed must go somewhere, right?
Click to expand...
Click to collapse
There's buggy ports thats flashable on magisk. While you still can get xposed, it'll be an unofficial version, and more likely to run into issues within your rom and daily use into your device.
HighOnLinux said:
There's buggy ports thats flashable on magisk. While you still can get xposed, it'll be an unofficial version, and more likely to run into issues within your rom and daily use into your device.
Click to expand...
Click to collapse
I mean xprivacy on xposed was the must have killer feature for any android device to turn your device into anything other than a privacy nightmare. If we can't do that any more we are f'd.
[EDIT] Looks like the new version of xprivacy, xprivacyLua is still supported for android 11, with magisk and EdXposed or LSPosed:
[CLOSED][APP][XPOSED][6.0+] XPrivacyLua - Android privacy manager [UNSUPPORTED]
XPrivacyLua Really simple to use privacy manager for Android 6.0 Marshmallow and later (successor of XPrivacy). Revoking Android permissions from apps often let apps crash or malfunction. XPrivacyLua solves this by feeding apps fake data...
forum.xda-developers.com
XPrivacyLua/README.md at master · M66B/XPrivacyLua
Really simple to use privacy manager for Android 6.0 Marshmallow and later - XPrivacyLua/README.md at master · M66B/XPrivacyLua
github.com
As I understand it, the pixel dialer now has a call recording capability built in, but its only enabled on a per country basis. Even though its legal to do single party recording in my jurisdiction, its not enabled. I had the same issue with my old one plus 7t, but I was able to force it via some automatable adb magic. Is there any way to do this for the Pixel 7?
possible only after root.
How? Please elaborate. Thanks
How to root P7
How to unlock the bootloader and root the Google Pixel 7 or Pixel 7 Pro with Magisk
Planning to root your Google Pixel 7 or Pixel 7 Pro? Here's how to unlock the bootloader and root the latest 2022 Pixel phones with Magisk!
www.xda-developers.com
GoogleDialerMod-Magisk
GitHub - jacopotediosi/GoogleDialerMod-Magisk: A deprecated module to tweak Google Dialer (Phone by Google) Android application to enable hidden features like call recording. Use https://github.com/jacopotediosi/GoogleDialerMod instead.
A deprecated module to tweak Google Dialer (Phone by Google) Android application to enable hidden features like call recording. Use https://github.com/jacopotediosi/GoogleDialerMod instead. - GitHu...
github.com
is it possible to root the phone, make the change to the db, then undo the changes (i.e. I'd rather not have my phone be rootable in general), also somewhat (small) worried about things breaking because of security checks after rooting. And it be nice to be able to use OTA upgrades.
No, it's not possible.
After unrooting, the bootloader must be locked, which will wipe data
efkosk said:
No, it's not possible.
After unrooting, the bootloader must be locked, which will wipe data
Click to expand...
Click to collapse
so the only way to do it in a way that could be preserved while maintaining the ability to do OTAs and the like would be if an user accessible exploit was discovered that enabled users to modify the sqlite db and that the OTAs don't overwrite said db? (big assumption, dont know if its true).
i.e. thinking creatively.for pixel 6
1) install the original firmware - i.e. from https://developers.google.com/android/images
2) somehow make use of dirty pipe to gain root, make the changes directly with sqlite, reboot, and phone will still be locked no longer rootable, but changes should persist in db.
and as phone was never unlocked, OTAs should work?
though, even if this is all true, doesn't help pixel 7 users (today). Also doesn't help if db gets overwritten fully (which even if small OTAs dont, I'd imagine, that the android 12-13 upgrade might have?, but again, assumption).
"somehow make use of dirty pipe to gain root" is comical. Do it like this somehow, but I don't know how.. :- D
No need to worry about root.
OTA works, you just have to use pixelflasher for that. It's not a problem and everything works perfectly.