Using custom ROMs without sacrificing security. - General Questions and Answers

I was always a fan of customizing and hacking around systems. I like to have root, I like to be in control of my device.
I do not like google or proprietary (especially Chinese but not only) firmware/os. One is spyware the other almost certainly also is.
However, using a custom ROM comes with other issues. One of them is possibility that the maintainer packaged malware. This ofc depends on your trust for the author, or if you use a fully open-source ROM your own ability to verify the code. This is not an issue for me here, but it is a big issue in general where custom ROMs come in, which most just ignore.
What I am talking about is the security of devices.I haven't messed around a lot with custom ROMs etc for some time as I had other things on my mind, but I see the only things that changed, changed for the worse. Virtually everywhere you need an unlocked bootloader. Once you do that you cannot re-lock it with custom recovery or system image. From what I've seen there is not even attempts to try and override the bootloader itself, probably because vendors veryify those with additional unchangable keys.
Are there any devices / vendors that allow for custom OS with a locked bootloader?
I would like to be protected against evil-maid attacks as well as prank-wiping, or tbh in the case of theft I'd love to see the hardware unusable. I know that this is not even Android developers fault, as the documentation clearly states ( https://source.android.com/security/verifiedboot/boot-flow ) mechanisms for running custom code on locked devices using "custom user set root of trust" which I assume to be "overridden" keys for validating partition signatures. But even a modded bootloader would be enough, an unlocked but password protected bootloader.. One can dream.
Or is using custom software on Android always a complete security disaster?

Related

Is there any secure custom roms or os?

I wish to know if there are any custom roms or os'es that wouldn't touch my data using background processes that doesn't ask for permission to do so. Because these apps are either pre-installed or installed by me (which ask for permissions up front)? Or at least that I would be able grant app permissions when it needs them? It's like a real time permission request service.
Thanks.
I don't understand your question very well but I think you'll need an AOSP 6.0 ROM like the one made by Flashhhh beacuse AOSP is the most secure beacuse just Google modifies it and the developer (Flashhhh in our case). You can't make it 100 % secure beacuse you need to encrypt the partition and lock the bootloader. Encryption slows the device like hell and locking the bootloader with costum software cannot by made except if some of the great develoeprs of the falcon can reprogram the bootloader and the other low level bootloaders. Hardware encryption isn't supported on falcon I don't know why beacuse my Lumia 435 has encryption enabled via settings as you can see here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And yes the device is as fast as with the option disabled ! So hardware encryption is supported on Snapdragon 200 and our device has Snapdragon 400. I don't know why but that's the life...I am also interested in a secure OS with encryption that can run on our Moto G without performance loss.
I was really looking forward to cyanogen-mod, because it was looked as safe. But after I've read their DISCLAIMER stating "Modifying or replacing your device's software may void your device's warranty, lead to data loss, hair loss, financial loss, privacy loss, security breaches, or other damage, and therefore must be done entirely at your own risk. No one affiliated with the CyanogenMod project is responsible for your actions. Good luck." I changed my mind. I am paranoid about my privacy and security therefore this disclaimer put all my excitement and hopes to find privacy and security in their custom rom down. On the other had they're stating the things that could happen to my phone through the use of their custom rom, which I am thankful for their honesty and precautions. I was looking for official carbon rom, because of it's flexibility in customization and some other useful features, but sadly they don't support our device so yet again I was let down. Even if there is ports of it. Yet again my paranoia for privacy and security appears to be in action and I just can't help it when It come to it. It's my need and I believe it is everyone's need that sadly seems to be not met... even my keyboard sends data through background services... The more I see what android does the more I want to switch back to windows phone... it was easy to use, simple, and at least secure. I loved the thing that you could use one app for text messaging and social network messaging and I found it really handy feature. Android is highly customizable, but not as secure as WP. Also did everyone else noticed that Android version names are alphabetically ordered which could mean that they have plans up front for Z? Ohhh and google is in alphabet now...
Was WP really more secure or did you simply don't know what it did in the background?
Concerning your question: to find a "perfect" system might by impossible. However, you should not completely give up on Cyanogenmod (or on custom roms in general). You do get the possibility to manage permissions and you get root. The latter you can use to uninstall system-apps you dont like or to set up a firewall for apps and services you dont trust (for instance your keyboard). As a further step you could try if a Google-free device would work for you (i.e. not flash gapps after rom). That might be less convenient in some aspects but you would get rid of the no. 1 risk for privacy. And dont worry too much about the disclaimer! Sure, flashing a custom rom can turn your device into electronic scrap and things like root are risky anyway, the crucial point is that stuff needs to be handled the correct way. With enough information acquired in the first place the risks arent too big
Hwyl.Fawr said:
Was WP really more secure or did you simply don't know what it did in the background?
Concerning your question: to find a "perfect" system might by impossible. However, you should not completely give up on Cyanogenmod (or on custom roms in general). You do get the possibility to manage permissions and you get root. The latter you can use to uninstall system-apps you dont like or to set up a firewall for apps and services you dont trust (for instance your keyboard). As a further step you could try if a Google-free device would work for you (i.e. not flash gapps after rom). That might be less convenient in some aspects but you would get rid of the no. 1 risk for privacy. And dont worry too much about the disclaimer! Sure, flashing a custom rom can turn your device into electronic scrap and things like root are risky anyway, the crucial point is that stuff needs to be handled the correct way. With enough information acquired in the first place the risks arent too big
Click to expand...
Click to collapse
Well yes WP doesn't have such feature as seeing what backgroung processes are active, what they're doing which should be a concern, but I think there are some devices that doesn't support multi-tasking which probably deals with the issue. Well the cyanogen mod does offer that security and frees you from app permission chains, but I don't want to rush on flashing it.
What about ubuntu os? They provide tutorial to port it for your own device which I am really interested in. But is there any advantages over cyanogen mod in terms of user privacy and security? Should I consider porting it myself or flashing a port made by community?
This ROM was created with privacy in mind: (Read the first post carefully and follow the instructions)
http://forum.xda-developers.com/moto-g/4g-development/rom-identity-crisis-6-lte-extreme-t3328861​
It will boot on Falcon; if after flashing the ROM, you immediately flash the Stock 6.0 Kernel available here:
http://forum.xda-developers.com/showthread.php?t=2649763​
lost101 said:
This ROM was created with privacy in mind: (Read the first post carefully and follow the instructions)
http://forum.xda-developers.com/moto-g/4g-development/rom-identity-crisis-6-lte-extreme-t3328861​
It will boot on Falcon; if after flashing the ROM, you immediately flash the Stock 6.0 Kernel available here:
http://forum.xda-developers.com/showthread.php?t=2649763​
Click to expand...
Click to collapse
Is it only for LTE version?
Thank you for your time spent on developing this rom for the community. I will flash it straight away.
zgodig said:
Is it only for LTE version?
Thank you for your time spent on developing this rom for the community. I will flash it straight away.
Click to expand...
Click to collapse
As I said, the ROM will boot and work fine on your phone if you flash the Falcon kernel. @minimale_ldz created this ROM based on my previous work.
lost101 said:
As I said, the ROM will boot and work fine on your phone if you flash the Falcon kernel. @minimale_ldz created this ROM based on my previous work.
Click to expand...
Click to collapse
This is madness.
Also
lost101 said:
This ROM was created with privacy in mind: (Read the first post carefully and follow the instructions)
http://forum.xda-developers.com/moto-g/4g-development/rom-identity-crisis-6-lte-extreme-t3328861​
It will boot on Falcon; if after flashing the ROM, you immediately flash the Stock 6.0 Kernel available here:
http://forum.xda-developers.com/showthread.php?t=2649763​
Click to expand...
Click to collapse
Okay. The rom looks good and seems to offer what I need, but that bug when you dim your brightness and flickering occurs can be annoying, since I like to dim it as much as possible, to save my battery from draining. I guess I will have to keep on using the stock rom till port of your rom will be fixed.
zgodig said:
Okay. The rom looks good and seems to offer what I need, but that bug when you dim your brightness and flickering occurs can be annoying, since I like to dim it as much as possible, to save my battery from draining. I guess I will have to keep on using the stock rom till port of your rom will be fixed.
Click to expand...
Click to collapse
There's also Lollipop version of this rom available, and it doesn't flicker. Installing the rom itself, however, won't be enough - even removing GApps doesn't prevent Google and from collecting "anonymous" data as there are still some leaks through kernel and modem debug settings. They can be blocked by firewall (like AFWall+). You may also want to install Network Log to see all the traffic. XPosed Xprivacy module is also very helpful in restricting internet, network, location, sensors, etc. access to the apps. You can also disable location services and bluetooth (and other things) with Servicely for extra protection and battery life.
All of it will give you SOME protection as obviously your carrier will have a lot of data about your device and this can't be avoided as long as you use its phone services.
minimale_ldz said:
There's also Lollipop version of this rom available, and it doesn't flicker. Installing the rom itself, however, won't be enough - even removing GApps doesn't prevent Google and from collecting "anonymous" data as there are still some leaks through kernel and modem debug settings. They can be blocked by firewall (like AFWall+). You may also want to install Network Log to see all the traffic. XPosed Xprivacy module is also very helpful in restricting internet, network, location, sensors, etc. access to the apps. You can also disable location services and bluetooth (and other things) with Servicely for extra protection and battery life.
All of it will give you SOME protection as obviously your carrier will have a lot of data about your device and this can't be avoided as long as you use its phone services.
Click to expand...
Click to collapse
I think that I should wait for the marshmallow patch. Because I wouldn't have to use the apps you have mentioned in order to protect myself. I've read that you recommend these apps to use on marshmallow too. Which one would you recommend? Lollipop ir marshmallow? From the things you have mentioned it made me an impression that there has to be done more on lollipop to protect yourself as much as possible, than on marshmallow. Besides I suspect that marshmallow is more advanced than lollipop. Anyways an expert opinion is allways worth to concider. A big thank you xda developers for your hard work and time put in developing all of the software available for us. You're the best!
zgodig said:
I think that I should wait for the marshmallow patch. Because I wouldn't have to use the apps you have mentioned in order to protect myself. I've read that you recommend these apps to use on marshmallow too. Which one would you recommend? Lollipop ir marshmallow? From the things you have mentioned it made me an impression that there has to be done more on lollipop to protect yourself as much as possible, than on marshmallow. Besides I suspect that marshmallow is more advanced than lollipop. Anyways an expert opinion is allways worth to concider. A big thank you xda developers for your hard work and time put in developing all of the software available for us. You're the best!
Click to expand...
Click to collapse
Well, I don't consider myself an expert - just spent some time reading security and privacy related stuff in the web and used some of the information to help myself. Please also mind all the things I mentioned (firewall, XPrivacy, etc.) don't come with Marshmallow and need to be installed and set up anyway so it doesn't make much difference if you use Lollipop or MM version. The biggest privacy-related changes that come with MM are built-in permissions manager (which is good but insufficient) and more up to date security patch. And I think that is it, so it's up to you if you want to wait. The thing with Android updates is that they bring new stuff that OEM and carriers need to implement and optimize, so I wouldn't say that Marshmallow is better in every aspect than Lollipo. I was using 5.1.1 for a few months on Moto G and was very happy - I'm using 6.0.1 on Moto X Play now, and see some annoying bugs that came with it. Interesting thing is they only appeared after removing GApps from the rom. So again - it's up to you.
The other fact is that the more you protect yourself from intrusive Google services the more new privacy and security issues appear. For example - if you use stock rom there's no need to unlock bootloader nor using custom recovery which are actually negatively affecting your privacy. You can access all the system and data in TWRP, so your privacy is pretty much none in case someone steals your phone. Good practice is not to keep too much private stuff on it, because there's always a risk someone can get it - one way or another.
minimale_ldz said:
There's also Lollipop version of this rom available, and it doesn't flicker. Installing the rom itself, however, won't be enough - even removing GApps doesn't prevent Google and from collecting "anonymous" data as there are still some leaks through kernel and modem debug settings. They can be blocked by firewall (like AFWall+). You may also want to install Network Log to see all the traffic. XPosed Xprivacy module is also very helpful in restricting internet, network, location, sensors, etc. access to the apps. You can also disable location services and bluetooth (and other things) with Servicely for extra protection and battery life.
All of it will give you SOME protection as obviously your carrier will have a lot of data about your device and this can't be avoided as long as you use its phone services.
Click to expand...
Click to collapse
minimale_ldz said:
Well, I don't consider myself an expert - just spent some time reading security and privacy related stuff in the web and used some of the information to help myself. Please also mind all the things I mentioned (firewall, XPrivacy, etc.) don't come with Marshmallow and need to be installed and set up anyway so it doesn't make much difference if you use Lollipop or MM version. The biggest privacy-related changes that come with MM are built-in permissions manager (which is good but insufficient) and more up to date security patch. And I think that is it, so it's up to you if you want to wait. The thing with Android updates is that they bring new stuff that OEM and carriers need to implement and optimize, so I wouldn't say that Marshmallow is better in every aspect than Lollipo. I was using 5.1.1 for a few months on Moto G and was very happy - I'm using 6.0.1 on Moto X Play now, and see some annoying bugs that came with it. Interesting thing is they only appeared after removing GApps from the rom. So again - it's up to you.
The other fact is that the more you protect yourself from intrusive Google services the more new privacy and security issues appear. For example - if you use stock rom there's no need to unlock bootloader nor using custom recovery which are actually negatively affecting your privacy. You can access all the system and data in TWRP, so your privacy is pretty much none in case someone steals your phone. Good practice is not to keep too much private stuff on it, because there's always a risk someone can get it - one way or another.
Click to expand...
Click to collapse
If you're not an expert then you're not far from it, because I don't think it's easy to do the things you did.
Is it possible to re-flash stoch recovery and re-lock bootloader after flashing one your roms to improve security, or are they essential to make rom work?
zgodig said:
If you're not an expert then you're not far from it, because I don't think it's easy to do the things you did.
Is it possible to re-flash stoch recovery and re-lock bootloader after flashing one your roms to improve security, or are they essential to make rom work?
Click to expand...
Click to collapse
As far as I know relocking bootloader will fail if installed system is not original, but I'd ask @lost101 as he's got much more expertise in Motorola issues.
minimale_ldz said:
You can access all the system and data in TWRP, so your privacy is pretty much none in case someone steals your phone.
Click to expand...
Click to collapse
Using encryption helps in this case. Just remember that when you get your phone back, don't trust it anymore.
zgodig said:
Is it possible to re-flash stoch recovery and re-lock bootloader after flashing one your roms to improve security, or are they essential to make rom work?
Click to expand...
Click to collapse
Originally Falcon (and Peregrine I suspect) did not support Factory Reset Protection (FRP) - this may have changed for those with locked Bootloaders who updated to Lollipop via official OTA Update. Even with FRP, all you are doing is stopping someone who stole / found your phone from accessing your data. Obviously you must unlock Bootloader to gain real control over your data by flashing a ROM just as those created by @minimale_ldz. Once Bootloader is unlocked, it's permanent. So-called 'relocking' is purely superficial and can be simply undone by anyone with fastboot access.
So the answer is no, flashing Stock Recovery and 'relocking' Bootloader does absolutely nothing for you in terms of security.
Newer phones such as Moto G (3rd Gen) support FRP out of the box. But again, you are at the mercy of Google and Motorola when it comes to privacy as long as the Bootloader remains locked. You cannot root, nor install a custom ROM.
I fear ultimately you must examine your own psychological / egoic need for control and privacy, as the world outside your mind is unlikely to deliver what you seek.
lost101 said:
Originally Falcon (and Peregrine I suspect) did not support Factory Reset Protection (FRP) - this may have changed for those with locked Bootloaders who updated to Lollipop via official OTA Update. Even with FRP, all you are doing is stopping someone who stole / found your phone from accessing your data. Obviously you must unlock Bootloader to gain real control over your data by flashing a ROM just as those created by @minimale_ldz. Once Bootloader is unlocked, it's permanent. So-called 'relocking' is purely superficial and can be simply undone by anyone with fastboot access.
So the answer is no, flashing Stock Recovery and 'relocking' Bootloader does absolutely nothing for you in terms of security.
Newer phones such as Moto G (3rd Gen) support FRP out of the box. But again, you are at the mercy of Google and Motorola when it comes to privacy as long as the Bootloader remains locked. You cannot root, nor install a custom ROM.
I fear ultimately you must examine your own psychological / egoic need for control and privacy, as the world outside your mind is unlikely to deliver what you seek.
Click to expand...
Click to collapse
Is it possible to make or do something that no one would be able to enter recovery mode without password or at least pin code?
_that said:
Using encryption helps in this case. Just remember that when you get your phone back, don't trust it anymore.
Click to expand...
Click to collapse
So encrypting the phone would help to protect data. In case of loost or stolen phone, the person would only be able to delete my data through recovery mode?
And what do you mean that after I'd get my phone back I shouldn't trust it?

Can ported TWRP Recovery versions ( or any ported stuff ) contain virus?

hi everyone.
recently, I installed a custom twrp version that is ported to my device.
i used to be skeptical about this but now that i know what spywares can do with your privacy I started to really worry about "ported" recoveries.
i was just wondering if there was a way they could fit a virus into a ported twrp for example?
3CORSA3 said:
hi everyone.
recently, I installed a custom twrp version that is ported to my device.
i used to be skeptical about this but now that i know what spywares can do with your privacy I started to really worry about "ported" recoveries.
i was just wondering if there was a way they could fit a virus into a ported twrp for example?
Click to expand...
Click to collapse
Yes No Maybe.
It all depends on the source of the file and who made this PORT.
If the person is trustworthy, nothing to fear. Of course, it also depends on whether that person has the TWRP file base as trustworthy.
TeamWin folks generally don't do any nonsense. But any malicious person with knowledge can put a malicious script in the TWRP or any option desired by the user can lead to a bad action.
As you can see, the doubts will be great even if someone with a mind for crack does that. There is usually nothing to worry about if you have the stock ROM files.
In addition, most actions are done by the user himself and not by applications (malicious or not).
The best way to know is to test the functionality of TWRP and if you notice something different to what it was thought of or behaving strangely, then stay tuned. If you are knowledgeable and know how to use TWRP then you will know how to differentiate what is good or what is bad.
Another way is to place the ported TWRP file for a developer or person with experience to analyze if there is any different script that causes something bad.
3CORSA3 said:
hi everyone.
recently, I installed a custom twrp version that is ported to my device.
i used to be skeptical about this but now that i know what spywares can do with your privacy I started to really worry about "ported" recoveries.
i was just wondering if there was a way they could fit a virus into a ported twrp for example?
Click to expand...
Click to collapse
Yes one can fit a virus in anything. You can take a precaution of scanning any file you download with an antivirus. Though no antivirus can be truly accurate, there still are chances. Giving a link to an antivirus if you want
https://www.google.com/url?sa=t&source=web&rct=j&url=https://play.google.com/store/apps/details%3Fid%3Dcom.protectstar.antispy%26hl%3Den%26gl%3DUS%26referrer%3Dutm_source%253Dgoogle%2526utm_medium%253Dorganic%2526utm_term%253Dprotectstar%26pcampaignid%3DAPPU_1_wzKvYOuJA4HT-QaivL6gDQ&ved=2ahUKEwir98KClenwAhWBad4KHSKeD9QQ8oQBMA96BAgjEAE&usg=AOvVaw37khVQ1DKzplbVrZ44uuzg
My POV: As long as Android OS didn't get tampered ( e.g. bootloader unlocked, rooted, dm-verity disabled, etc.pp ) noone must fear his/her device can get infected with malware ( viruses included ).
BTW:
Malware like viruses are known to perform repeated tasks that can take up resources on your devices. Signs of malware may show up in these ways.
Phone is too slow.
Apps take longer to load.
The battery drains faster than expected.
There is an abundance of pop-up ads.
Phone has apps you don’t remember downloading.
Unexplained data usage occurs.
Higher phone bills arrive.

Security-related arguments for root and custom rom usage...

Exodus, a popular, albeit closed-source, crypto wallet app recently stopped working on my device. After a few days of back-and-forth troubleshooting via support, they somehow realized that my device is both rooted and running a custom, open source, community-supported ROM. They told me this was no longer allowed because it is far less secure than running the proprietary ROM. I countered with both personal testimony (back when I had a Blu phone, and a year later they got kicked off Amazon due to spyware streaming customer data out without consent) and common fact that OEM ROMs are almost always packed full of bloatware and spyware. I countered that installing a reputable open source ROM with only those apps I want and need is better. I argued that root gives me the ability to use AFWall to block outbound access to apps that I don't want having having access to the Internet without my permission. I could have argue that continuing to use a 1-2 year old phone that no longer receives security updates when I could use an open source ROM that does is better. I also provided a few public articles showing how frequently apps from the Play Store and other "OEM" stores are caught abusing their users' trust and performing malicious action. My point was that it's not correct to just automatically assume that having root and using a non-OEM ROM is less secure. That's a falsehood. But that said, I am interested to know what the XDA community thinks about that. And if the XDA community has any facts about custom, open source, community-supported ROMs being more secure than OEM ROMs, I am interested to further arm myself. And of course, I am completely willing to be instructed by the XDA community that indeed Exodus is right and using a custom ROM and having a rooted phone is completely, inherently, automatically more insecure than using an OEM ROM full of bloatware and spyware, not having root so that any rag-tag app can stream data back to home base, and falling behind with security patches because the vendor is either too slow to release or decides my device is no longer worth supporting.
You can't blame them for not troubleshooting unknown firmware. You changed the playing field.
Less mainstream use and support* is one of the disadvantages of custom roms and rooting.
I run stock and use other methods to kill bloatware. Zero brick risk, little down time and they run well.
I'm not saying don't root etc... but you knew the job was dangerous when you took it.
*this can have potentially far reaching and multifaceted implication$
@blackhawk I'm pretty sure it wasn't broken on my phone. One day I opened the app and it said I needed to update to continue using it. So I thought maybe the app just had failed to automatically update from the Play Store. But shortly thereafter I found it wouldn't update. That led to opening support ticket with them which eventually led to them saying it no longer works on rooted devices. Their argument was that they were attempting to protect me. My rebuttal was that I don't want their protection, I want my freedom back. They should focus on making their app as secure as possible and then, if they discover I am running it on a rooted phone, then give me a warning box and force me to accept it but don't just take away my freedom.
The irony of their stance is that they still provide the Linux program. And who doesn't have root access on their Linux computer? Or their Mac or Windows computer, for that matter? I can completely understand if they don't wish to troubleshoot the installation of the Debian package or even the use of the zip on every Linux version out there. I wouldn't either! But that's completely different than saying, "Oh, you have root access to your Linux/Mac/Windows computer? We can't let you use our program anymore." That makes zero sense, and it's the same nonsensical argument they are making for rooted Android phones.
I run stock N10+'s because they're easier to troubleshoot, maintain and it doesn't trip the Knox efuse. I have to add a package disabler and do some optimizing but it's child's play for me to do it at this point.
Unfortunately if you root you're going to have to suck it up and do the work needed to optimize it.
Same thing I do with stock but with more tools at your disposal... after the learning curve.
It's this learning curve, the chance of bricking and the damage that can be inadvertently done to the OS with no access restrictions are some of the downsides. Rooting takes time to learn and perfect. With unlimited power, blah, blah, blah.
I rather just do basic infrequent troubleshooting and have fun... my current load is over 1.5 yo, still fast and stable.
I don't update the firmware because that breaks things. No updates needed once you optimize it and find any needed work arounds... it's good to go. Anything from Pie up is pretty secure; they have some vulnerabilities but in practice this isn't an issue... unless you do something stupid.

Difference Between Custom ROM vs Stock ROM

Android operating system is very popular Operating system for mobile among all the operating systems. Android
operating system based on Linux, developed by Android, Inc in 2015 later google purchase android and
took over its development. The android operating system is open source and free. All the Codes release on an
open-source Apache License which means anyone can build Customizable Os by downloading the full
source code. Not only the Rom of a smartphone, but the processor of a smartphone have also a vital role.
If you are using an Android smartphone, then at least once for a while you will have updated the version of Android.Or if you want to update the android version then you will find there are two ways to do that.And we’ll discuss about these two methods one by one.And in the end you will be able to understand which one is right for you.
-What is a Stock Rom?​Stock ROM is an operating system developed by manufacturer itself when we purchase a mobile.But, in stock rom the manufacturers limits the function and feature of the phone or tablet for our
safety purposes.A Stock ROM basically based on the Android platform and its open source. Any developer can
easily access the code and edit it, recompile it, and re-release it, this is called CUSTOM ROM.
-What is Custom ROM ??​
In simple word,Its the modified version of stock rom.Custom ROMs are usually made by third-party developers which consist lots of customization.It can be used by other phones which can unlock extra feature also
increase performance and battery life at the same time.When some of the manufacturer company
stopped providing updates for certain devices which means you cannot get any further updates but at that time with the help
of custom ROM we can update our phones to next android version .
Advantages of Stock ROM​Security – Security is the key reason why people prefer STOCK ROM over Custom ROM. Each stock ROM is developed by reputed companies so there is no chance for any kind of malware to attack
our device because some devices come with Locked Bootloader. Due to which you have to unlock the Bootloader in order to install Custom ROM.That is why your mobile is much safer due to security.
Warranty– As long as you are in the STOCK ROM, your mobile will have a warranty.That’s why most of the users shift to the STOCK ROM after the warranty void.And stick with STOCK ROM for that purpose.This is one of the
reasons why users don’t use custom ROM over Stock ROM.
However, even after unlocking the mobile bootloader, many manufacturing companies offer warranties, although.
-Disadvantages of Stock ROM​
-Performance
Manufacturers limit the device, as the device may overheat when it reaches its limit. Due to which you have to face problems from sometime during heavy task. Like multiple task or playing games, etc.
-Less Space Many unwanted apps come pre-installed in stock ROM. Which we cannot easily remove or uninstall, because these are system apps Which very quickly fills our mobile storage. It
is the most unliked part of Stock ROM.
-Updates -Most irritating part of Stock ROM is that you need to wait a long for your manufacturer to send
the update to get new and exciting features in your device. Also after sometime manufacturer, stops
sending the update. In that case, you are stuck on the same android version with old features.
-Advantages of Custom ROM​
-Customizable
Android Custom ROMs are highly customizable. It is very easy to install different custom ROMs nowadays. You can
easily customize the looks of the system ui and also enhance the performance of the system at the same time.
-Better Performance and Battery life
On Custom ROM you can customize your device as you want which
means there will be no unwanted app like Stock ROM.Custom ROMs allow you to turn off background processes that consume a lot of RAM and battery and internet data. With custom ROMs, you
can find a ROM customized to your unique device. That means better performance, greater battery life.
-Frequently updates
How many of you still didn’t get the android 10 updates?? isn’t frustrating ,how do you feel when you find out that there is a new Android version available for your mobile but your manufacturing company has stopped giving updates and because of this the demand for Custom ROMs has increased tremendously.And using custom ROM we get the opportunity to use the features of the new Android System.
-Disadvantages of Custom ROM​
Like the Advantages, Custom ROMs have many disadvantages that many of you may not know about, here are some.
-Void Warranty
If you use a custom ROM during the warranty period, in most cases your mobile warranty will be void,but in some cases the process is
reversible.This means you will be able to return to the STOCK ROM and your mobile phone will have a warranty again if your device isn’t bricked .
Most of the time to install Custom ROM you need to have root installed on your mobile or have bootloader unlocked.
While unlocking devices or rooting most phones is easy, some phones require a complicated step to
install Custom ROM.Due to which many times our phone may be dead or our data may be lost
-Loss of data
To install a custom ROM, we have to wipe cache and format the data, many cases data on storage often deleted. You will be lost your saved settings and other
apps data also. Also formatting data and wipe cache cause you to lose contacts, messages, call logs, and apps backup and important documents etc etc.
-BUGS
Most of the custom ROMs are ported from other ROM, so if you want to use those features on your phone, you may have to face bugs sometimes.
Custom ROMs are complied by the developer not tested by any authority or genuine manufacturers. So,
it might contain some Bugs in it. If you are planning to install a Custom ROM then ready for face bugs.
-Security
As we know android is based on Linux and Linux is virus-free. In order to install a Custom ROM, we need
to unlock the phone bootloader or root our device this is the first step. Manufacturer locked our device,
for this reason, no third party app can affect our phone. But our device might get infected by malware if
the device is unlocked or rooted.Also, Many times we can’t use banking related app on our phone because of its root.
This Isn't any promotion topic,i covered all the points here but if you appreciate my work visit the link
xxxxxx
Mod Edit: Link removed
Thank you so much for this, left a like

What's really at stake if rooting an older phone?

My phone is 5 years old, and hasn't had any OTA updates in years and its got no warranty. Apparently my older version of Android 8, isn't recognized as much and I'm starting to encounter more and more Play store apps that want a newer version of android and refuse to load. Hence I had to learn how to sideload stuff which is really annoying.
After a quick google search I learned you can root your phone and there is an Android 11 image called Lineage OS 18.1 ... which sounds pretty sweet. BUT after additional searches, I'm reading so many cons about rooting a phone. If bricking it isn't a concern, and I don't have a warrantee to void. What's at risk? I was probably going to buy a new phone anyways but now I'm intregued with this rooting process and wondiering if it might buy me time on a older phone that still works amazingly well. Why replace it if it still works, it just needs new software.
Questions: If I install Lineage OS 18.1 successfully...
Will the Play Store and Apps continue to update, or will I stop receiving notifications regarding available updates? Or am I forever stuck with sideloading?
If I don't install G Apps is this bad? I don't use stock Google Apps, I've opted to use the Microsoft equivalent like Outlook for email and calendar... or do I still need to install Google Apps to gain the ability to layer Microsoft products on top?
Why is there so much negative talk about malware infection with rooted phones? If I'm not downloading and installing apps constantly, the risk would still be no more threatening than it is now correct?
Are there any apps that would realize the phone is rooted and refuse to run? Some searches told me that security apps may not like a rooted phone. Does rooting it affect Microsoft Authenticator app?
Lastly, if I only want to pick and choose specific G Apps - can you install only the ones you need? or do they come all bundled together?
Thanks in advance,
What's really at stake if rooting an older phone?​
Click to expand...
Click to collapse
Ii is easy to answer:
Pro: Complete Control Over Your Device​
One of the most significant benefits of rooting your Android device is the ability to have complete control over it. You can remove any pre-installed apps that you don’t need, customize the look and feel of your device, and control every aspect of its performance. With rooting, the possibilities are endless, and you can make your device truly your own.
Con: Risk of Bricking Your Device​One of the most significant risks of rooting your Android device is the potential to brick it. Bricking is when your device becomes completely unusable due to a software malfunction. If you’re not careful, you can render your device useless. However, if you follow the instructions carefully and take the proper precautions, you can minimize the risk of bricking your device.
Speed up older Android hardware with a custom ROM​
Click to expand...
Click to collapse
Installing a custom ROM ( or a 3rd-party OS ) allows your device to live a second life, provided you can stomach the somewhat lengthy process. Custom ROMs become especially useful once your smartphone’s manufacturer stops delivering software and feature updates. Most ROMs are also based on vanilla Android ( AOSP ), which means you get a lighter and faster experience than default manufacturer skins.
Having said that, it’s worth noting that custom ROMs are completely unofficial. Some work perfectly, while others may exhibit bugs and instability - you’ll need to do some due diligence for your specific device model. But don’t worry, here is a guide on how to install Lineage OS, one of the most popular custom ROMs.

Categories

Resources