I have a Samsung Galaxy S2 which I am using for 5.5 years. Some months ago, I upgraded my phone to Android 4.1 (Jelly Bean) (Using Kies). Officially, that is the last update for my phone. But I still want to upgrade via custom ROM.
The configuration of my phone:
Chipset: Exynos 4210 Dual
CPU: Dual-core 1.2 GHz Cortex-A9
GPU: Mali-400MP4
Internal: 16 GB storage, 1 GB RAM
Battery: Removable Li-Ion 1650 mAh battery
Display: 16M Colors, 4.3 inches Super AMOLED Plus capacitive touchscreen,
480 x 800 pixels, 5:3 ratio (~217 ppi density)
Which version of Android will run smooth in my phone ? Will upgrading slow down my phone?
Please help ! Thanks a lot.
Normally, the best performance is reached by stock ROM - there only are exceptions at Samsung.
In general, the newer the ROM, the more resources it needs. I think the best performance is possible with Android 4.4 KitKat. Marshmallow was faster than Lollipop in my experience, Nougat is slower than the both previously mentioned.
So if just the speed counts, try KitKat, if you also want a newer Android, go for Marshmallow. This is just my personal opinion.
i stay on Ehndroix , more fluid and good for games and battery without kernels. slim KK
https://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-ehndroix-14-5-22-smooth-stable-slim-t2662796
It depends on your needs.
I use my phone mostly for phoning (by mobile data or telegram), mailing, chatting and surfing. I did not install any g-apps. For me Android N is very smooth and reliable. I use [ROM][OFFICIAL][7.1.2][OTA][OMS][i9100]RESURRECTION REMIX[10/09/2017]: https://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-resurrection-remix-t3507366
BenjyTec said:
So if just the speed counts, try KitKat, if you also want a newer Android, go for Marshmallow. This is just my personal opinion.
Click to expand...
Click to collapse
Does anyone know if there are KitKat or Marshmallow ROMS available that are patched for the KRACK WiFi vulnerability?
Currently running LOS 14.1 on 7.1.2 and the latest nightly has been patched for KRACK, though performance is not as smooth as I had (Naively?) hoped
paragoneer said:
Does anyone know if there are KitKat or Marshmallow ROMS available that are patched for the KRACK WiFi vulnerability?
Currently running LOS 14.1 on 7.1.2 and the latest nightly has been patched for KRACK, though performance is not as smooth as I had (Naively?) hoped
Click to expand...
Click to collapse
go LOS 11 have stable for daily use and KRAK patches
Hi,
Upgrading your phone to the latest version might cause some instabiltity and performance issues, but it entirely depends on the rom and kernel that you'll flash. Most Kitkat based roms will do good, currently using this one and so far no issues at all.
Regards,
Thank you for the suggestion. I am currently using this custom Nougat-compatible kernel, what is the process to flash an older KitKat compatible kernel and ROM (I.e. going backwards from 7.1.2 to 4.4.4)
paragoneer said:
Thank you for the suggestion. I am currently using this custom Nougat-compatible kernel, what is the process to flash an older KitKat compatible kernel and ROM (I.e. going backwards from 7.1.2 to 4.4.4)
Click to expand...
Click to collapse
You can do a complete wipe then install, although I only tested this on LOS 11 so I don't know what result it will give on other ROMs...
You can also repartition your phone storage then install a Kitkat compatible recovery then install the ROM that you like.
I'm planning to test the downgrade using LOS 11, downgrading from LOS 14.1
How do I repartition the phone storage?
Do you have any suggestions for a KitKat compatible recovery and kernel?
Thanks
paragoneer said:
I'm planning to test the downgrade using LOS 11, downgrading from LOS 14.1
How do I repartition the phone storage?
Do you have any suggestions for a KitKat compatible recovery and kernel?
Thanks
Click to expand...
Click to collapse
You can repartition your phone by using lanchon's repit method but make a backup of your internal storage first. As for a Kitkat compatible kernel, you can flash Saber's DorimanX kernel for LOS14.1 and use TWRP recovery from the IsoRec thread.
You can also flash LOS11 without repartitioning, just make sure you have the latest recovery on your phone to avoid encountering problems.
I have the latest TWRP recovery. What would be the difference be in flashing LOS 11 without partitioning, as opposed to using lanchon's repit method before flashing?
paragoneer said:
I have the latest TWRP recovery. What would be the difference be in flashing LOS 11 without partitioning, as opposed to using lanchon's repit method before flashing?
Click to expand...
Click to collapse
There's no big difference really, it's just that some ROMs don't support different storage formats such as ext4/f2fs (and sometimes, the modded preload too)
If you have the latest TWRP recovery, you can flash LOS 11 right away - just don't forget to do a full wipe.
Just to clarify that I have correctly understood your instructions:
Flash Dorimanx kernel for 14.1
Flash LOS 11 ROM
Thank you kindly ^_^
paragoneer said:
Just to clarify that I have correctly understood your instructions:
Flash Dorimanx kernel for 14.1
Flash LOS 11 ROM
Thank you kindly ^_^
Click to expand...
Click to collapse
You don't need to flash DorimanX if you have the TWRP recovery, just flash away.
Hope you enjoy your new ROM!
Is a full wipe:
/system
/cache
/partition
and Dalvik?
Thanks!
paragoneer said:
Is a full wipe:
/system
/cache
/partition
and Dalvik?
Thanks!
Click to expand...
Click to collapse
/system
/data
/cache
/dalvik
Great, thank you. Will the device still be rooted after I flash the KitKat ROM? (I rooted it using LOS supersu addon)
paragoneer said:
Great, thank you. Will the device still be rooted after I flash the KitKat ROM? (I rooted it using LOS supersu addon)
Click to expand...
Click to collapse
Root is disabled by default in LOS 11, to activate it you need to go to:
Settings -> About Phone then tap the Build Number seven times
Once it's done, press the back button and select Developer Options, scroll down a bit and find the Root Access option, then select "Apps" or "Apps or ADB" (depends on you, there's not much of a difference anyway)
Thank you
Do you have any CPU governor suggestions (InteractiveX?) and frequency suggestions?
Related
So right now I'm running Task650s AOKP with Siyah Kernel, but an old version, thats still Android 4.0.4. In addition, I only have CWM 5. A lot of the KK ROM threads say that CWM 6 is required (and some JB ones imply the same thing, or tha I need JB bootloaders), but the one I want to flash (PACMan) doesn't have such a warning, but I'm still a bit apprehensive. Will I be fine if I just wipe, flash PACMan + GApps and reboot? Or is there an intermediary step I need like flashing a new kernel, and if so which one do I need?
Thanks guys
SupremeOverlord777 said:
So right now I'm running Task650s AOKP with Siyah Kernel, but an old version, thats still Android 4.0.4. In addition, I only have CWM 5. A lot of the KK ROM threads say that CWM 6 is required (and some JB ones imply the same thing, or tha I need JB bootloaders), but the one I want to flash (PACMan) doesn't have such a warning, but I'm still a bit apprehensive. Will I be fine if I just wipe, flash PACMan + GApps and reboot? Or is there an intermediary step I need like flashing a new kernel, and if so which one do I need?
Thanks guys
Click to expand...
Click to collapse
Well pacman isn't based on kitkat so I think you're good to go, the newest nightlies for that are still based on jellybean right? Or has it changed? I haven't downloaded one in a like two weeks.
SupremeOverlord777 said:
Will I be fine if I just wipe, flash PACMan + GApps and reboot?
Click to expand...
Click to collapse
Yes, you will be fine, as long as you install a JB kernel first (either STI or AJK 4.9 AOSP). I would suggest you install Milestone 1 (the download link is labeled PAC Release), instead of the nightly. Nightlies have a reputation for being finicky at times, so if you want stability you'd be better off sticking with known stable releases.
And don't forget to flash the gapps either, or you'll run into other problems.
SteveMurphy said:
Yes, you will be fine, as long as you install a JB kernel first (either STI or AJK 4.9 AOSP). I would suggest you install Milestone 1 (the download link is labeled PAC Release), instead of the nightly. Nightlies have a reputation for being finicky at times, so if you want stability you'd be better off sticking with known stable releases.
And don't forget to flash the gapps either, or you'll run into other problems.
Click to expand...
Click to collapse
Alright, sounds great. Thanks for the help, I'm downloading now.
Hello,
I want to install Android 4.4.4 on my good old S3, but I have some questions.
The phone is GT-I9300 with stock kernel 3.0.31 and baseband I9300XXUGNA8 -....... with stock Android 4.3
The smartphone is already root (Super Su 2.1) installed busy box 1.22.1 and I want to install this ROM CM-11-20140914-NIGHTLY-i9300 and Kernel boeffla-kernel-2.3a-CM11.0-i9300.CWM
I've changed the recovery (I have TWRP and CMR)
I want ask about:
1. Is it the good choice of the combination of ROM and kernel and are they compatible with my phone?
2 In my situation with the stock kernel and stock ROM what I have to install first? Kernel and then ROM or vice versa, because I don’t want to BRIC the phone.
3 If something goes wrong is there already an option for unbrick or not?
4.Can I used to change the ROM and Kernel, CyanogenMod Installer and Universal Kernel Flash applications or is better to do it manually in recovery. I see that Odin unable to install custom ROM. Am I right?
5 Is it possible and how I can make a backup of the kernel?
6 What is the connection between the baseband number and the compatibility with the kernel?
Thank you in advance for your advices and I know that all what I do is on my own risk.
I apologize for my English because is not good.
Best Regards
bmwpow said:
Hello,
I want to install Android 4.4.4 on my good old S3, but I have some questions.
The phone is GT-I9300 with stock kernel 3.0.31 and baseband I9300XXUGNA8 -....... with stock Android 4.3
The smartphone is already root (Super Su 2.1) installed busy box 1.22.1 and I want to install this ROM CM-11-20140914-NIGHTLY-i9300 and Kernel boeffla-kernel-2.3a-CM11.0-i9300.CWM
I've changed the recovery (I have TWRP and CMR)
I want ask about:
1. Is it the good choice of the combination of ROM and kernel and are they compatible with my phone?
2 In my situation with the stock kernel and stock ROM what I have to install first? Kernel and then ROM or vice versa, because I don’t want to BRIC the phone.
3 If something goes wrong is there already an option for unbrick or not?
4.Can I used to change the ROM and Kernel, CyanogenMod Installer and Universal Kernel Flash applications or is better to do it manually in recovery. I see that Odin unable to install custom ROM. Am I right?
5 Is it possible and how I can make a backup of the kernel?
6 What is the connection between the baseband number and the compatibility with the kernel?
Thank you in advance for your advices and I know that all what I do is on my own risk.
I apologize for my English because is not good.
Best Regards
Click to expand...
Click to collapse
1. Yes, i had both of them for awhile and it worked great for me, pretty good battery (i changed the governor and i/o scheduler though).
2. ROM then kernel, atleast ive always done that. If you flash rom second, the cm stock kernel will be installed and you will have to flash boeffla again.
3. Not too sure about unbricking, sorry. As far as i know, brick means pretty much useless/deadweight.
4. CM installer installs a snapshot for the installer and not the nightly you mentioned along with the cm stock kernel. I always flash manually via CWM recovery but that's my personal choice.
5. To backup the kernel, someone else will know but you could just make a nandroid backup of everything before flashing (recommended anyways).
6. I wouldnt know, sorry.
Hope i helped you, Good Luck!
Grimzee said:
1. Yes, i had both of them for awhile and it worked great for me, pretty good battery (i changed the governor and i/o scheduler though).
2. ROM then kernel, atleast ive always done that. If you flash rom second, the cm stock kernel will be installed and you will have to flash boeffla again.
3. Not too sure about unbricking, sorry. As far as i know, brick means pretty much useless/deadweight.
4. CM installer installs a snapshot for the installer and not the nightly you mentioned along with the cm stock kernel. I always flash manually via CWM recovery but that's my personal choice.
5. To backup the kernel, someone else will know but you could just make a nandroid backup of everything before flashing (recommended anyways).
6. I wouldnt know, sorry.
Hope i helped you, Good Luck!
Click to expand...
Click to collapse
Thank you. I've change ROM and the kernel and all it is work perfect
bmwpow said:
Thank you. I've change ROM and the kernel and all it is work perfect
Click to expand...
Click to collapse
You're welcome and glad to hear, enjoy cyanogenmod with boeffla
Just got given an i9100 today with a faulty USB port. A new one is coming in the mail, but ebay is slow.
It charges fine so it can be used, just no data connection over USB (connects and disconnects, cleaning the port did not help)
Currently on 4.1.2, i9100XXLS9
I can get files to it via SD card, is there any methods to root it or get TWRP on it that can be done before i fix the USB port?
Mussels84 said:
Just got given an i9100 today with a faulty USB port. A new one is coming in the mail, but ebay is slow.
It charges fine so it can be used, just no data connection over USB (connects and disconnects, cleaning the port did not help)
Currently on 4.1.2, i9100XXLS9
I can get files to it via SD card, is there any methods to root it or get TWRP on it that can be done before i fix the USB port?
Click to expand...
Click to collapse
Mobile Odin
noppy22 said:
Mobile Odin
Click to expand...
Click to collapse
looks like its working, its loaded a stock rom and has its many options. How do i add a custom recovery with it? I'm fuzzy on the S2, since it combined kernel + recovery.
Mussels84 said:
looks like its working, its loaded a stock rom and has its many options. How do i add a custom recovery with it? I'm fuzzy on the S2, since it combined kernel + recovery.
Click to expand...
Click to collapse
You could use any kernel in .tar format to load a custom recovery. Philz or siyah kernel are normally used to root the s2, but I think any will work.
Alternatively you could download philz kernel in .zip format. You just need to find the correct kernel for your firmware HERE.
This guide is one of many for basic info on rooting etc
i figured it out, got philz on there for now.
Thanks for the idea of mobile ODIN, i tried flashify. TWRP manager, Rash, and terminal commands and none of them worked... mobile ODIN did however.
Now i get to read up on the custom roms available for the S2
Any recommendations?
Mussels84 said:
Any recommendations?
Click to expand...
Click to collapse
Marshmallow is quite stable now on the S2, so is Lollipop. Any of the recent MM roms are pretty good. I've been running AICP, Oct M, and AOKP recently(MM) and no real major bugs. On lollipop, Oct OS is good and Mokee is still releasing new builds. There are others that are good as well; too many to list...
On kitkat I love Slimsaber by fusionjack(and GreekDragon has released newer builds). Kitkat is a bit more battery friendly than LP or MM.
Many many options
noppy22 said:
Marshmallow is quite stable now on the S2, so is Lollipop. Any of the recent MM roms are pretty good. I've been running AICP, Oct M, and AOKP recently(MM) and no real major bugs. On lollipop, Oct OS is good and Mokee is still releasing new builds. There are others that are good as well; too many to list...
On kitkat I love Slimsaber by fusionjack(and GreekDragon has released newer builds). Kitkat is a bit more battery friendly than LP or MM.
Many many options
Click to expand...
Click to collapse
due to messing around with recoveries and getting into a no-boot situation, i've used the recovery i had to flash dirty unicorns android 6.0.1
hopefully that works, and all is well. So frustrating when recovery + kernel are paired.
edit: DU included the latest TWRP. Bliss.
Mussels84 said:
due to messing around with recoveries and getting into a no-boot situation, i've used the recovery i had to flash dirty unicorns android 6.0.1
hopefully that works, and all is well. So frustrating when recovery + kernel are paired.
Click to expand...
Click to collapse
Well good news on that front. @Lanchon has done some very nice work for the S2 community and come up with a solution to the bundled recovery/kernel. Read up on "isorec" HERE. Basically on the newer MM roms and some later LP roms, the kernel supports this isolated recovery. Just flash the isorec recovery and you have a seperated recovery and kernel
noppy22 said:
Well good news on that front. @Lanchon has done some very nice work for the S2 community and come up with a solution to the bundled recovery/kernel. Read up on "isorec" HERE. Basically on the newer MM roms and some later LP roms, the kernel supports this isolated recovery. Just flash the isorec recovery and you have a seperated recovery and kernel
Click to expand...
Click to collapse
only thing left - repartitioning without ODIN.
found some very vague guides on that...
Mussels84 said:
only thing left - repartitioning without ODIN.
found some very vague guides on that...
Click to expand...
Click to collapse
My first recommendation is if you need a 6.0.1 rom, then wait until your usb port is fixed.
If you don't want to wait for that, then take your time and read the link I gave you over on the DU thread for Lanchons re-pit tool. There is a link near the start of that thread to github where you will find downloads for the tool and a more detailed guide. In the xda thread(the one I linked), there are posts from users that will make clear how to use the tool. Basically you need to rename the file to re-partition how you want your layout
If you are not too worried about android version, then maybe try LP or KK. You don't need to re-partition for these roms as long as you use a pico/minimal gapps package and you will get better battery performance.
noppy22 said:
My first recommendation is if you need a 6.0.1 rom, then wait until your usb port is fixed.
If you don't want to wait for that, then take your time and read the link I gave you over on the DU thread for Lanchons re-pit tool. There is a link near the start of that thread to github where you will find downloads for the tool and a more detailed guide. In the xda thread(the one I linked), there are posts from users that will make clear how to use the tool. Basically you need to rename the file to re-partition how you want your layout
If you are not too worried about android version, then maybe try LP or KK. You don't need to re-partition for these roms as long as you use a pico/minimal gapps package and you will get better battery performance.
Click to expand...
Click to collapse
What i've ran into as a hurdle, is the following:
The latest TWRP doesnt work with that tool, there are no older links on the TWRP website.
The Isolated recovery is now merged with TWRP, so there are no older links there either.
If i can find the recommended 2.8.7.0 i guess it would work.
https://www.androidfilehost.com/?fid=24369303960684130
Edit: That link i posted above was correct and worked to repartition.
Was wondering if its possible to flash to CM 11 from the Fire Nexus ROM I'm currently running. Or do I need to flash the Amazon OS again and then do it.
Would be much easier if I could do the first option but figurred I'd ask real quick since I couldn't seem to find a clear answer.
Thanks so much for any help! Bootloader is still locked so using safestrap. Fire Nexus ROM 4.4.4 (KitKat)
I enjoy this ROM too, its awesome but I've always been a sucker for CM. Thanks again!
Ripx88 said:
Was wondering if its possible to flash to CM 11 from the Fire Nexus ROM I'm currently running. Or do I need to flash the Amazon OS again and then do it.
Would be much easier if I could do the first option but figurred I'd ask real quick since I couldn't seem to find a clear answer.
Thanks so much for any help! Bootloader is still locked so using safestrap. Fire Nexus ROM 4.4.4 (KitKat)
I enjoy this ROM too, its awesome but I've always been a sucker for CM. Thanks again!
Click to expand...
Click to collapse
In general you can toggle between ROMs that share the same base version of Android. Note the system partition can not be wiped in Safestrap v4 (option is ignored) so outcomes can be problematic if you have made significant customizations. That said, it should work fine if your system is relatively clean. No need to return to FireOS.
Don't forget GAaps and SuperSU with CM11. Consult the CM11 OP for recommended versions.
Keep in mind Safestrap v4 best practices:
- no secondary slots; everything happens in the STOCK slot
- verify rom md5 before flashing any rom
- always keep a known good rom zip in \sdcard at all times
- never perform a 'factory reset' from the Amazon recovery menu (brick)
Hello, I was wondering which is the best kernel for Android N that gives out good customizability and battery life.
Currently using official LineageOS 14.1 (obviously) 20171011 Nightly + Saber's DorimanX Kernel v13.0b005.
Thanks!
You are currently using the latest and final version of the only custom LOS kernel available for the i9100. So you're choices are stick with it for a while or switch to the vanilla LOS kernel on your next update by just not flashing the DorimanX one.
You can still do some very basic tuning on the vanilla LOS kernel but it's pretty locked down, for stability reasons I suppose.
Apex Predator said:
You are currently using the latest and final version of the only custom LOS kernel available for the i9100. So you're choices are stick with it for a while or switch to the vanilla LOS kernel on your next update by just not flashing the DorimanX one.
You can still do some very basic tuning on the vanilla LOS kernel but it's pretty locked down, for stability reasons I suppose.
Click to expand...
Click to collapse
Thank you. I might be sticking with that for a while, as I also tried Skyline's kernel but I found that DorimanX is much more stable.
One more question, can I revert back to any CM12.1/13 ROM without doing any other specific work? (ex: repartitioning the device)
zereleith said:
Thank you. I might be sticking with that for a while, as I also tried Skyline's kernel but I found that DorimanX is much more stable.
One more question, can I revert back to any CM12.1/13 ROM without doing any other specific work? (ex: repartitioning the device)
Click to expand...
Click to collapse
if you already have the repartition and last Isorec only makes the wipes and install the new ROM with their gapps