Are there any clean & simple (i.e. non Samsung based) ROMs out there that support device & SD encryption?
I know CM11 doesn't... but I've not been able to find mention of it in any of the rom descriptions.
If none of the AOSP ones do, then what's the simplest Samsung based one, with encryption, but the least amount of Samsung bloatware?
A.
andybryant said:
Are there any clean & simple (i.e. non Samsung based) ROMs out there that support device & SD encryption?
I know CM11 doesn't... but I've not been able to find mention of it in any of the rom descriptions.
If none of the AOSP ones do, then what's the simplest Samsung based one, with encryption, but the least amount of Samsung bloatware?
A.
Click to expand...
Click to collapse
I think CM11 does, since I'm running a CM11 derived ROM and under settings -> security I have encryption.
Side note: you can remove bloatware from any ROM by yourself so pick any you like.
In stock-based roms, I suggest you give ArchiDroid V1.7.16 a try.
It has device encryption (as well as external SD encryption) and heavily debloated.
Make sure to read the OP, there are a lot of features you need to be aware of.
Related
I realize that one can run and install linux on an android device (which is running it's own kernel on top of android's kernel), so wouldn't it be just as possible to run a factory kernel on top of a modded kernel to regain access to device specific features that only the factory kernel can currently utilize (4g, 3d cameras, etc.)? As far as I understand, linux has access to those features and can interface with them (whether it can do anything with them is another topic, but...), so wouldn't this be a viable solution to make custom ICS, JellyBean, Cyanogenmod roms work 100% with each device? Sorry for the lack of specific technical mumbo-jumbo lingo, just a newbie brainstorming here.
Hello,
I came here desperate for answers that could solve my problem with "M-signature" not working on custom (not SAM-based) ROMs.
"M-signature" (aka "Mobile ID") is a way to connect to bank via phone (you get a special personal SIM card, you go to your e-banking site, enter your phone number, get a pop-up message on phone screen (see attached), enter PIN on the phone and voila - connected into e-bank).
This "M-signature" works on Stock Rom, also on Samsung based ROMs: null_ ROM v25, NeatROM EMC2, UltimaRom v11, but doesn't work with AOSP (Slim Bean, Dragon SlimBean), AOPK/CM (Pac-man), MIUI (_miui.polymorph_)...
Problem is I love Slim Bean or Pac-man and can't really get used to sam-based (they're ugly, i find them slower, battery not appealing, etc.) - could I find a way to make that "M-signature" work on AOSP/AOPK/CM ROMs??
Biggest thanks in advance.
Evaldino said:
Hello,
I came here desperate for answers that could solve my problem with "M-signature" not working on custom (not SAM-based) ROMs.
"M-signature" (aka "Mobile ID") is a way to connect to bank via phone (you get a special personal SIM card, you go to your e-banking site, enter your phone number, get a pop-up message on phone screen (see attached), enter PIN on the phone and voila - connected into e-bank).
This "M-signature" works on Stock Rom, also on Samsung based ROMs: null_ ROM v25, NeatROM EMC2, UltimaRom v11, but doesn't work with AOSP (Slim Bean, Dragon SlimBean), AOPK/CM (Pac-man), MIUI (_miui.polymorph_)...
Problem is I love Slim Bean or Pac-man and can't really get used to sam-based (they're ugly, i find them slower, battery not appealing, etc.) - could I find a way to make that "M-signature" work on AOSP/AOPK/CM ROMs??
Biggest thanks in advance.
Click to expand...
Click to collapse
It shouldn't act like that, android app should be compatible with everything running an android, not only samsung. Unless it's dedicated only to GT-I9300.
I know this won't solve your issue but there are plenty of samsung-based roms with really cool aosp themes, bunch of tweaks and really well made. I don't want to recommend my own work but take a look if you wish, perfect example of stock rom with non-stock look.
JustArchi said:
It shouldn't act like that, android app should be compatible with everything running an android, not only samsung. Unless it's dedicated only to GT-I9300.
I know this won't solve your issue but there are plenty of samsung-based roms with really cool aosp themes, bunch of tweaks and really well made. I don't want to recommend my own work but take a look if you wish, perfect example of stock rom with non-stock look.
Click to expand...
Click to collapse
Thnx JustArchi for answer (at least somebody wrote smth ).
That is not an app - it's a SIM card "feature" (a special, associated with my personal info (from my passport) SIM card which, I guess initiates those "pop-up messages").
It works this way: you go to www.example-mybank.com, enter there my ID and phone number, then (i guess) the special SIM card pushes a message "do you want to connect" (and shows control code to be sure it's your connection), enter your special PIN, and SIM card gives command to my bank "OK, let him in, it's really <Evaldino>" and the e-bank opens up for me
So, I guess it's something with "SIM services" (don't know how to call them - I'm a noob user), which work only on Stock or Sam-based ROMs, so perhaps CM/AOSP/MIUI lack a "module" or smth for these "SIM services" to work...
Also, this M-signature works on all smart devices (not only Samsung, not only Android, also on iOS, maybe even WinOS).
I see no other option as to try those SAM-based (though not really happy about that), so I'll definetely look into your ROM (I like 240DPI, circular battery, if only 4x4 pattern lock for locking screen), because for ex. on ReVolt (Sam-based, yes?) "m-signature" doesn't work (though I kind of liked this ROM)..
To be honest I'm surprised it works at all on a rooted device bearing in mind security etc....many banking apps/features won't work, especially with insecure kernel....I guess for a good reason...although not being particularly tech I wouldn't like to even attempt to explain why!
Please mind you that it may work on AOSP like the nexus builds but not work on CM based roms as they change ALOT of the AOSP code. That includes alot of the security protocols.
Wayne Tech S-III
slaphead20 said:
To be honest I'm surprised it works at all on a rooted device bearing in mind security etc....many banking apps/features won't work, especially with insecure kernel....I guess for a good reason...although not being particularly tech I wouldn't like to even attempt to explain why!
Click to expand...
Click to collapse
You have a point here.. didn'nt even think about that.. However, I'm not very "paranoid" and I don't think it's very insecure (to my little android security understanding)
zelendel said:
Please mind you that it may work on AOSP like the nexus builds but not work on CM based roms as they change ALOT of the AOSP code. That includes alot of the security protocols.
Click to expand...
Click to collapse
But I tried my beloved Slim Bean (AOSP based, right?) - not working.. maybe it's "too much changed" AOSP? What i9300 ROM is "purest" AOSP - I'll try?
Evaldino said:
You have a point here.. didn'nt even think about that.. However, I'm not very "paranoid" and I don't think it's very insecure (to my little android security understanding)
But I tried my beloved Slim Bean (AOSP based, right?) - not working.. maybe it's "too much changed" AOSP? What i9300 ROM is "purest" AOSP - I'll try?
Click to expand...
Click to collapse
There are no pure aosp roms for most devices. They all use something from CM. Be it kernel or some of the coding as aosp only supports the nexus line as a base. Everything else is a fork.
Wayne Tech S-III
So, how did you solved this problem, if you did? I wonder if this problem we are facing is only applicable in Lithuania as I can't even google some more sources on this issue...
valdelis said:
So, how did you solved this problem, if you did? I wonder if this problem we are facing is only applicable in Lithuania as I can't even google some more sources on this issue...
Click to expand...
Click to collapse
There is no way to solve it. It will not work on AOSP based roms.
zelendel said:
There is no way to solve it. It will not work on AOSP based roms.
Click to expand...
Click to collapse
Actually I just flashed this one [ROM][Mar 17] Jellybean 4.2.2 for Endeavoru AOSP Build [Kernel 3.1.10] [JDQ39] #19 and at last it works! Will try to use this ROM for some time to be sure everything works, but it at least the biggest problem is solved.
By the way, I forgot to mention in my first post, I'm on HTC One X (International version with Tegra), but hope there is a workaround for SIII too.
For Samsung Galaxy Mini there is AOSP ROM (http://forum.xda-developers.com/showthread.php?t=2413108)
Well thought I would pose the question as curious as to where to go next with our S2's
What are the advantages of the different versions of Android on the S2's and their sub versions??
What I mean by subversions is quite simple really 4.1.2 over say aosp 4.1.2?
We are on 4.1.2 Chameloen (me) 4.1.2 stock rooted(partner)
curios as to whether there's any point moving especially as kitkat onwards there no write to sd which is frigging STUPID!!!!
looking forward to your thoughts and opinions folks...
And thank you to all thoughs who take part..
regards
Lohtse
lohtse said:
Well thought I would pose the question as curious as to where to go next with our S2's
What are the advantages of the different versions of Android on the S2's and their sub versions??
What I mean by subversions is quite simple really 4.1.2 over say aosp 4.1.2?
We are on 4.1.2 Chameloen (me) 4.1.2 stock rooted(partner)
curios as to whether there's any point moving especially as kitkat onwards there no write to sd which is frigging STUPID!!!!
looking forward to your thoughts and opinions folks...
And thank you to all thoughs who take part..
regards
Lohtse
Click to expand...
Click to collapse
Hey,
Samsung doesn't officially release any changelogs, but if you prefer Samsung base roms, i recommend those with their latest base for security purposes and improved user interface (hopefully!)
There main difference between AOSP/AOKP and regular Samsung ROMs are that AOSP teams aren't part of Samsung.
AOSP aims to give people access to the latest of the Android world, as you can see that you can run lollipop on S2, without AOSP teams this wouldn't be even remotely possible as Samsung wants you to buy newer phones. So in that sense AOSP is a great tool.
But Samsung is the company that can ensure stability on their ROMs while AOSP still are nightly (beta) versions with lot of bugs, small maybe but lots.
AOSP/AOKP - Access
Samsung - Stability
If you refrain from using kitkat because of the sd card bug, don't worry. There are many apps and xposed modules that can fix the issue by granting full access to the external sd card.
WardenBerret said:
Hey,
Samsung doesn't officially release any changelogs, but if you prefer Samsung base roms, i recommend those with their latest base for security purposes and improved user interface (hopefully!)
There main difference between AOSP/AOKP and regular Samsung ROMs are that AOSP teams aren't part of Samsung.
AOSP aims to give people access to the latest of the Android world, as you can see that you can run lollipop on S2, without AOSP teams this wouldn't be even remotely possible as Samsung wants you to buy newer phones. So in that sense AOSP is a great tool.
But Samsung is the company that can ensure stability on their ROMs while AOSP still are nightly (beta) versions with lot of bugs, small maybe but lots.
AOSP/AOKP - Access
Samsung - Stability
If you refrain from using kitkat because of the sd card bug, don't worry. There are many apps and xposed modules that can fix the issue by granting full access to the external sd card.
Click to expand...
Click to collapse
Thank you for your reply very useful
but what are apps you have mentioned?
WardenBerret said:
Hey,
Samsung doesn't officially release any changelogs, but if you prefer Samsung base roms, i recommend those with their latest base for security purposes and improved user interface (hopefully!)
There main difference between AOSP/AOKP and regular Samsung ROMs are that AOSP teams aren't part of Samsung.
AOSP aims to give people access to the latest of the Android world, as you can see that you can run lollipop on S2, without AOSP teams this wouldn't be even remotely possible as Samsung wants you to buy newer phones. So in that sense AOSP is a great tool.
But Samsung is the company that can ensure stability on their ROMs while AOSP still are nightly (beta) versions with lot of bugs, small maybe but lots.
AOSP/AOKP - Access
Samsung - Stability
If you refrain from using kitkat because of the sd card bug, don't worry. There are many apps and xposed modules that can fix the issue by granting full access to the external sd card.
Click to expand...
Click to collapse
What sd card bug you are talking about? Are you talking about the music bug? Because I've never heard or a problem where there was some problems with external sd card mounting.
lohtse said:
Thank you for your reply very useful
but what are apps you have mentioned?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=nextapp.sdfix
I'm still on jellybean so i don't know even if it will show "This app is incompatible with all of your devices." if you have a kitkat rom, since its not official rom. Therefore the Xposed module is much more preferrable imo.
I can't offer any personal guarantees as whether it works or not.
gsstudios said:
What sd card bug you are talking about? Are you talking about the music bug? Because I've never heard or a problem where there was some problems with external sd card mounting.
Click to expand...
Click to collapse
The first kitkat builds had, for some strange reason, disallowed access to external sd cards, if any. Needless to say many people were not happy, and it wouldn't surprise me if the later builds removed this bug.
But if you have this bug, it basically means you can't use your external sdcard for anything unless you have root.
WardenBerret said:
https://play.google.com/store/apps/details?id=nextapp.sdfix
I'm still on jellybean so i don't know even if it will show "This app is incompatible with all of your devices." if you have a kitkat rom, since its not official rom. Therefore the Xposed module is much more preferrable imo.
I can't offer any personal guarantees as whether it works or not.
The first kitkat builds had, for some strange reason, disallowed access to external sd cards, if any. Needless to say many people were not happy, and it wouldn't surprise me if the later builds removed this bug.
But if you have this bug, it basically means you can't use your external sdcard for anything unless you have root.
Click to expand...
Click to collapse
thank you for the links... may give 5.0.2 or 4.4.x a try now....frigging stupid move not allowing write to sd etc in my opinion...... shame the community has to fix Googles screw ups!!
This is something I've always wanted for my G3, a vanilla ROM that's always up to date with the latest Android version, but without any "extras" and "features" seen in typical ROMs. I don't like having to deal with frequent ROM updates that add new features/create new problems. I just want a clean ROM that works like a Nexus device.
Why does this not exist?
(If it already exists I have not come across it yet)
DavM said:
This is something I've always wanted for my G3, a vanilla ROM that's always up to date with the latest Android version, but without any "extras" and "features" seen in typical ROMs. I don't like having to deal with frequent ROM updates that add new features/create new problems. I just want a clean ROM that works like a Nexus device.
Why does this not exist?
(If it already exists I have not come across it yet)
Click to expand...
Click to collapse
When you say vanilla I'm assuming you mean AOSP, in that case we do have cm12.1, but I don't know if that's what you mean when it comes to "frequent ROM updates"
But if you're asking as to why we don't have a stock 5.1 ROM, that would be because LG hasn't released a base for it yet
6NomoN6 said:
When you say vanilla I'm assuming you mean AOSP, in that case we do have cm12.1, but I don't know if that's what you mean when it comes to "frequent ROM updates"
But if you're asking as to why we don't have a stock 5.1 ROM, that would be because LG hasn't released a base for it yet
Click to expand...
Click to collapse
CM is not aosp based, it's cm based.
Yes, the argument could be made that everything starts with aosp, but AFAIK there is little true aosp left in cm, and mostly custom cm code.
As for the op,
You get what devs decide to build. Your question is borderline offensive.
DavM said:
This is something I've always wanted for my G3, a vanilla ROM that's always up to date with the latest Android version, but without any "extras" and "features" seen in typical ROMs. I don't like having to deal with frequent ROM updates that add new features/create new problems. I just want a clean ROM that works like a Nexus device.
Why does this not exist?
(If it already exists I have not come across it yet)
Click to expand...
Click to collapse
Well, you could always start a stock rom, root it, and use Titanium Backup to remove any feature you don't want and arrive to a "vanilla ROM". The ROM development is a hobby for the dev, so of course there are "frequent ROM updates". By the way, LG has not released the 5.1 yet, they are still on 5.0.1 (23c).
DavM said:
This is something I've always wanted for my G3, a vanilla ROM that's always up to date with the latest Android version, but without any "extras" and "features" seen in typical ROMs. I don't like having to deal with frequent ROM updates that add new features/create new problems. I just want a clean ROM that works like a Nexus device.
Why does this not exist?
(If it already exists I have not come across it yet)
Click to expand...
Click to collapse
Been using validus for days. Works great. No freezes. Don't use the features if you don't want em.
For all those who aren't yet ready to upgrade to Lollipop but would like to close this vulnerability on their device, I have built the latest CM11 i9100 source as of 9/1/15 (since CM11 nightlies for this device are no longer released for download). This build is unofficial but I have not modified it in any way**. It includes all StageFright fixes that the CM development team has implemented.
All required downloads are located here.
Works well as a daily driver with Lanchon's i777 Crossflash Kernel on my device.
Installation instructions can be found on CM's website or on Lanchon's kernel thread (above).
I recommend wiping cache/system/data prior to flashing (dirty flash with only a cache wipe did not work on my device when upgrading from the last public nightly).
Good luck!
** I did manually modify the updater-script to allow this ROM to be flashed on any device (because i9100 ROMs refuse to flash on the i777/S959G). Flashing this ROM on anything other than an i9100/i777/S959G WILL brick your device.
XDA:DevDB Information
CyanogenMod 11 [UNOFFICIAL] for i777 with Stagefright Fix, ROM for the AT&T Samsung Galaxy S II SGH-I777
Contributors
dimoochka
ROM OS Version: 4.4.x KitKat
Based On: CyanogenMod
Version Information
Status: Nightly
Created 2015-08-31
Last Updated 2015-08-31
Apparently the crossflash kernel is incompatible with this build (not sure why - was working ok on my device). A compatible version was rebuilt by Lanchon on 9/4/15 (can be found on his thread or in the download link in the first post).
Very considerate, and good of you to take the time to present this. Cheers, and build-on!
-Cyril
Stagefright bug still present
Flashed it yesterday.....all works fine.....except bug isn't fully patched
mmystere68 said:
Flashed it yesterday.....all works fine.....except bug isn't fully patched
Click to expand...
Click to collapse
I just started a rebuild. Will try to upload when it's finished tonight - maybe that vulnerability has been patched since the last time I built this (months ago).
mmystere68 said:
Flashed it yesterday.....all works fine.....except bug isn't fully patched
Click to expand...
Click to collapse
Rebuilt and uploaded. Give it a shot - I'm not sure if it'll work or if that bug is patched but it shouldn't hurt to try. Just make a backup first.
dimoochka said:
Rebuilt and uploaded. Give it a shot - I'm not sure if it'll work or if that bug is patched but it shouldn't hurt to try. Just make a backup first.
Click to expand...
Click to collapse
i just dirty flash it. right?
mmystere68 said:
i just dirty flash it. right?
Click to expand...
Click to collapse
If you're coming from a prior version of CM11 dirty flash should be fine.
Coming from omnirom 4.4.4 with TWRP, safe or no? There's a newer thread by Lanchon... my eMMC chip is VYL00M Firmware revision 19 (which can have superbrick bug?) ugh... Typically.... I softbrick my phone a few days til I sort things out when upgrading from GB>ICS>JB>kitkat (kitkat softbricked me)
All this partitioning stuff has me a bit sketched, but I hate how kitkat disabled USB mass storage (without me knowing or I wouldn't have upgraded) any custom ways around this with new roms?
ATT i777 here
Edgarhighmen said:
Coming from omnirom 4.4.4 with TWRP, safe or no? There's a newer thread by Lanchon... my eMMC chip is VYL00M Firmware revision 19 (which can have superbrick bug?) ugh... Typically.... I softbrick my phone a few days til I sort things out when upgrading from GB>ICS>JB>kitkat (kitkat softbricked me)
All this partitioning stuff has me a bit sketched, but I hate how kitkat disabled USB mass storage (without me knowing or I wouldn't have upgraded) any custom ways around this with new roms?
ATT i777 here
Click to expand...
Click to collapse
The official builds of CM11 and CM12.1 are safe to use with the i777. So are my unofficial builds (that don't include TWRP). Lanchon's kernels (with TWRP included) are safe to use as well. I highly recommend using one of Lanchon's modern kernels with whatever ROM you end up installing (they are basically stock kernels that contain bug fixes and are TRIM enabled). TRIM functionality is really essential to maintain good performance on this device (especially considering the i777 is now a few years old and runs a lot of current apps sluggishly).
I have an S959G (slight variation of the i777 - ROMs are interchangeable between these two models) with VYL00Mx19. I used @Lanchon's i777 kernels for years without a device superbrick. My understanding is that the superbrick bug basically occurred under one type of firmware TRIM command called Secure Erase. As far as I know, secure erase still remains bugged and dangerous, and for this reason is NOT used. Lanchon's TRIM kernels enable regular (unsecure) erase that is understood to be safe and still gives you the benefit of TRIM .
dimoochka said:
The official builds of CM11 and CM12.1 are safe to use with the i777. So are my unofficial builds (that don't include TWRP). Lanchon's kernels (with TWRP included) are safe to use as well. I highly recommend using one of Lanchon's modern kernels with whatever ROM you end up installing (they are basically stock kernels that contain bug fixes and are TRIM enabled). TRIM functionality is really essential to maintain good performance on this device (especially considering the i777 is now a few years old and runs a lot of current apps sluggishly).
I have an S959G (slight variation of the i777 - ROMs are interchangeable between these two models) with VYL00Mx19. I used @Lanchon's i777 kernels for years without a device superbrick. My understanding is that the superbrick bug basically occurred under one type of firmware TRIM command called Secure Erase. As far as I know, secure erase still remains bugged and dangerous, and for this reason is NOT used. Lanchon's TRIM kernels enable regular (unsecure) erase that is understood to be safe and still gives you the benefit of TRIM .
Click to expand...
Click to collapse
Thanks dimoochka, i'm probably going to give it a go this weekend.
Before I found this thread nothing worked; I tried 11,12 and 13 from other post and had weird things happen, 1st I lost my CWM 6.0.51 screen and was stuck with CM boot creen. 2nd E: failed to verify whole-file signature. 3rd it said I couldn't flash because I was on a i9100!? I think my device is possessed ... I have had issues with everything but cm-11-20150901-UNOFFICIAL-i9100 from your link, somehow this one worked! Thank you for posting this! I was about to buy a new phone :good:
Rhaegon said:
Before I found this thread nothing worked; I tried 11,12 and 13 from other post and had weird things happen, 1st I lost my CWM 6.0.51 screen and was stuck with CM boot creen. 2nd E: failed to verify whole-file signature. 3rd it said I couldn't flash because I was on a i9100!? I think my device is possessed ... I have had issues with everything but cm-11-20150901-UNOFFICIAL-i9100 from your link, somehow this one worked! Thank you for posting this! I was about to buy a new phone :good:
Click to expand...
Click to collapse
Glad this helped! Just so you're aware I haven't rebuilt this ROM for a good 9 months (and I am not even sure if the CM team is still patching old bugs in versions 11/12). If you're unable to get CM13 on the i777, I would definitely suggest buying a newer device for the sake of security. Nexus devices are basically the only option I'm aware of here since none of the other manufacturers actively maintain their ROMs. I retired my i777 in leiu of a Nexus 5X about 6 months ago.
Best of luck!