The only S5 Kitkat ROMs I've found either haven't been updated in over a year, or many users are reporting severe bugs like no camera support, or severe battery drain issues.
I'm just trying to get an app called Winulator running so I can play Starcraft: Broodwar on android, but it isn't working and one user said that is because Lolipop broke it (I'm on 5.1.1 atm). The app is no longer supported so I don't think it will ever run properly on 5.x. If anyone knows of a way to emulate 4.x for just 1 app maybe that would be the best shortcut for me overall here.
Barring that, could someone please recommend a guide to installing a lightweight, power-user-oriented ROM that is 4.x or older and has excellent battery life? I was going to try the official 4.4.4 VanirAOSP release but there are too many reports of poor battery performance in the last 2 pages of that thread for my liking.
I think the first thing I need to do is unlock the bootloader, and I've yet to find a definite answer on the best method of doing this from FOL1 (12/15). It seems I will need Odin on my PC and I have it. I've also started backing up all the data from my phone by manually copying/pasting to my PC.
I guess once everything is finally backed up (it's taking FOREVER, explorer literally been calculating time to copy for 10 minutes now just on the phone/android folder), then I will try and flash the official 4.4.2 VanirAOSP ROM since that one doesn't have any reports of battery issues and possibly only the camera and a few things won't work.
BTW, is there a step specially to unlock the FOL1 bootloader that I am missing, or can I just flash that ROM with Odin straight up? I found a comment stating NOT to flash 5.1.1 with Odin or I'd be stuck on Lollipop until some new bootloader-unlock method comes out. The 5.1.1 I'm running wasn't flashed with odin it was sent OTA and I've never rooted or had custom rom/bootloader, so I should be good on that I guess?
I am actually about to dive into this, if no one has any suggestions for me: http://forum.xda-developers.com/showthread.php?t=2752995
So I'll just pick one at random then? Thanks for the help...
You haven't even listed your model S5 or the ROM it's running now
And of course KK hasn't been updated in over a year, Lollipop and Marshmallow are released, they're not going to keep updating KK when a newer version of Android is released
Related
Hey guys I have not seen this in the Q&A section and I want to make sure I do it right.
I only recently rooted my Nexus 7, been running stock but decided I wanted to have Multi Windows like I have on my Note 4. I have not decided on a ROM as I was looking for the best one so I am still running Stock Rooted 5.0.2 I saw Omni ROM and I think that this would be the best ROM to attempt this as I tried the Xposed method and of course got the boot loop.
I see that currently on OmniROM.com that this device is still running on KK 4.4.4 according to the nightlies. I assume I would need to find a KK stock ROM and flash it on to my Nexus to downgrade back to KK in order to install this ROM, or will this install with TWRP even though I'm running Lollipop?
If so does someone have a quick link to the Stock KK files? I used Wug's Nexus Root Toolkit to root my device as I did not feel like going through the same hassel as when I rooted my Droid RAZR so I would just tell that to use those files instead.
I am always flashing ROMs on my Note 4 but I have never gone backwards and I think it was possible to install KK ROM once you upgrade to lolly but not use a lolly ROM if your still on KK.
Soulforged666 said:
Hey guys I have not seen this in the Q&A section and I want to make sure I do it right.
I only recently rooted my Nexus 7, been running stock but decided I wanted to have Multi Windows like I have on my Note 4. I have not decided on a ROM as I was looking for the best one so I am still running Stock Rooted 5.0.2 I saw Omni ROM and I think that this would be the best ROM to attempt this as I tried the Xposed method and of course got the boot loop.
I see that currently on OmniROM.com that this device is still running on KK 4.4.4 according to the nightlies. I assume I would need to find a KK stock ROM and flash it on to my Nexus to downgrade back to KK in order to install this ROM, or will this install with TWRP even though I'm running Lollipop?
If so does someone have a quick link to the Stock KK files? I used Wug's Nexus Root Toolkit to root my device as I did not feel like going through the same hassel as when I rooted my Droid RAZR so I would just tell that to use those files instead.
I am always flashing ROMs on my Note 4 but I have never gone backwards and I think it was possible to install KK ROM once you upgrade to lolly but not use a lolly ROM if your still on KK.
Click to expand...
Click to collapse
I don't think anyone has done a compatibility check to see what happens if you run a 4.4 build on a device with 5.x bootloaders. It might work, it might do weird things (usually with sensors/wifi)
Multiwindow never got merged, if you want it you'll have to build for yourself and cherrypick it. There were some remaining issues with the patch we never had time to fix, we got too busy with other stuff, and xplodwild wants to rewrite the whole thing after finding a better way to implement it.
Hello,
It's been almost a little over a year since I was last really into android customization. Since it's been so long it has become clear to me that my phone is outdated in many ways. I'm still running OxygenOS 2.2.1 with Android 5.1.1. I've been wanting to update up to Android N (7.x.x) for a long time now, but haven't seen any real stable roms or haven't really had the time to look for one. Now I've finally found my self with free time and ready upgrade my rom. I've just faced couple of problems, I can't really find what should I do when upgrading from 5.1.1 to 7.x.x since no-one is really doing that anymore. I remember reading sometime back that if you dont have the right firmwares you'll brick ur phone, and I wouldn't really want to go through that hassle at the moment. Is it still a thing or should it be just fine for me to flash a new rom just on top of this? (Ofc with clearing memory etc) Other question that is in my mind is that is there any critical bugs in Android N roms? It's bit unclear to me since there are such many roms that have their status as work in progress or beta etc, but some roms have status as stable. Are there any roms that I should clearly avoid? Im not new to this so I don't really need any deep info how to do everything etc, just a bit of a oversight on how things are going atm.
Thanks.
first of all is ur device rooted?? If yes then install the latest twrp recovery...then take a backup.. and flash any nougat rom which u like...If at all u would need Volte support then u l have to flash the 3.5.7 firmware..or else the 3.1.0 firmware works fine with most of the nougat roms..some nougat roms i would recommend are AICP, Resurrection Remix and AOSP extended .... In my suggestion u should probably first upgrade the Oxygen Os on ur device through official updates via OTA atleast upto the 3.5.6 firmware
there's no need to update until 3.5.6, unless you aren't going to plan staying with OOS [the only "stable" firmware which provides you VoLTE working, but it's still M-based and not N].
as @mhd athiq said, unlock your bootloader [just in case you still haven't done it before] then update your TWRP recovery to the latest version.
then flash the incrementals OTAs until OOS 3.1.x and you are good to go to flash any custom ROM which is N-based.
to avoid any mistake, please make a EFS backup via terminal [just to have a backup of your modems] and save the files to a safe location.
I don't have a specific ROM to suggest to you, but in my experience I have found the CAF/AOSP-based ones to be the ones with the best battery backup and less bugs then LOS-based ones.
I have used happily for a few months CypherOS version 3.5.1 [not the latest one, I find it quite unstable as the developers tried to implement OMS].
sidenote:
flashing N-based custom ROMs upon OOS 3.5.6 firmwares gives random reboots and unstable network in many cases/scenarios.
so don't update to that OOS version unless you have a mandatory VoLTE feature required [but you'll have to live with random reboots and poor network stability].
I recently bought a used Lenovo A6000+. Using it for the first few hours did not reveal any major flaws. However, shortly afterwards I realized that the Phone used to switch off by itself when left unattended.
After verifying that my assumption is true, I proceeded to flashing the stock Lollipop ROM. I did so because I thought the problem was due to a flaw in the firmware. Plus, the 'About Phone' section in the Settings app showed clearly that my phone is a Lenovo A6000, with 8GB internal storage and 1GB RAM, while CPU-Z said that there is 16GB internal and 2GB of RAM, which tells that it is an A6000+.
The Lollipop ROM is worse than what I had anticipated. It lags like hell on the device, and is filled top to bottom with bloatware. Plus, the problem didn't get rectified even a bit. Worst, it started switching off even more regularly, and it wouldn't start unless I took out the battery and put it back in again.
If someone has devised a way of getting past this problem, be kind enough to mention it below.
@techfreak13, I don't know what's causing this issue but I can tell you that the stock Lollipop was a nightmare. Either you stay with stock KitKat or you can flash any of the other various ROMs available for this device. But, do note, that if you want to move from Lollipop (or Marshmallow or Nougat) based to KitKat based ROMs or vice versa, you'll first need to flash the stock ROM only. Then only you can flash the custom ROMs. Also different versions of TWRP are needed to work with the Kitakt and the other Lollipop/+ ROMs. TWRP 2.8.6 no image is for Kitkat while the latest verion 3.1.0 can be used for Lollipop+ Android versions. Since there is no unified thread for all the mods and roms. You'll have to dig deep into the forums to get the links. Good Luck to you. I hope you'll be able to solve the problem.
I've been running Cloudy G2.2 for a year an a half. It's given the phone enough legs to mostly make it through 2017. However, about every other week I have to restore my latest backup when Bluetooth stops working because it saw too many devices. This wouldn't be terrible if it wasn't for Authy refusing to sync my newer 2-Factor auth accounts. I think I've convinced myself that the G6 (US997) is my next phone, but now is a silly time to buy as the price should drop like a rock as the next wave of flagships come out.
I'm hoping to make it another couple months and was wondering anyone's experiences moving from Cloudy G2.2 (or other ROMs) to the latest lineage? From what I've read, it's very stable. However, I'm on Kit Kat bootloader, so it doesn't seem like this will be a straightforward process. I was hoping to get some experiences from people who made the same move before starting.
I currently have:
LG G2 D800
Root using stumproot (I think, it's been a while) with supersu installed
TWRP 2.7.0.0 installed by autorec
Cloudy G2.2 KOT49I
So, after some research, I set off to install LineageOS. In hindsight, this might have been a bad idea since it specifically only mentions the D802 in the title. However, it listed links for D800 builds, though they were crossed out.
I updated TWRP to this version by Blastagator and that was painless. I then wiped the phone, made a fresh backup and flashed the latest nightly of LineageOS, and the latest GApps (Mini) for 7.1. That was disappointing since I got the quick "LG logo" followed by a blank screen, that I later found was mentioned in the same Lineage post. Should've read farther.
I think the issue is that I'm on the wrong bootloader. I thought I was on KitKat which the post requires, but in order to enter recovery, I have to press enter three times (rather than using volume buttons to navigate), which indicates I'm on JellyBean bootloader.
So, this is the scary step that I was hoping to avoid. My big fear is that I run Linux on my desktop, so I can't use the LG Flash Tool. As long as I can keep a working recovery, I have backups, so I'm fairly safe. Following the Blastagator bootloader post, I'm not really sure how you go back and forth between bootloaders so easily as it suggests. Is that really as simple as loading the zip file on the phone and installing it in TWRP?
Is there a safer way to handle this?
From my experience, it is that easy. Simply install the zip file and you have loaded a new boot loader. Also, I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid. However it's not stable and I am considering looking for something else more stable but fast like crDroid.
ernie young said:
I was in the same boat as you with Cloudy rom and moved to Nougat with crDroid
Click to expand...
Click to collapse
When you updated your bootloader, were you still able to run the Cloudy ROM before you switched to crDroid? Once I flash the KitKat bootloader, am I only able to use the Nougat ROMs? My big concern is that there might be something a bit off with my bootloader, so I won't be able to get back to TWRP.
I think there's something a bit off with my bootloader as is, because about a year ago I flashed back to stock Jellybean, and took all the OTA updates. However, when the phone tried to take the KitKat update, it softbricked, and could only be recovered using the LG Update Tool, which I don't have access to anymore. Because of this, I'm a little worried that just dropping on the Blastagator KitKat bootloader may have some atypical issues.
i m using it for a while. u know, on Los you won't be able to use lg features such as qslide, qmemo, plug&pop, knockcode etc. Only worth it if you want your phone to look a little bit fresher and lighter or you need a newer android version for some reason. Else, don't take the risk if you can't use flashtool. You can consider installing another kitkat rom. There are lots and they are nice :]
S YILDIRIM said:
or you need a newer android version for some reason.
Click to expand...
Click to collapse
My primary issue is that KitKat (or whatever Cloudy G2.2 is?) has the old Android bluetooth bug where once it sees too many devices, it stops connecting to anything. I have to make sure to turn off my phone if I go somewhere like an airport, and have been having to restore my clean Cloudy backup about once a month. It's getting pretty frustrating. On the other hand, I'm hoping to upgrade to an LG G6 (US997) in a month or two when the V30 release pushes down on prices. So, if it's a case of potentially hard-bricking my G2 at the worst possible time, I should hold off flashing.
I think you need hybrid bootstack for android 7.
WORF84 said:
I think you need hybrid bootstack for android 7.
Click to expand...
Click to collapse
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.
superlou23 said:
That makes sense, but will I not be able to use my Cloudy 2.2 backup after that? It says that the hybrid bootstack will only boot CM 12.1, CM13, and LP stock roms.
Click to expand...
Click to collapse
These questions if this works with that or that are easier to answer for yourself by reading what goes with what.
Just Google LG G2 bootstack and you can probably find the ones you need for any available rom.
I use hybrid on Marshmallow 6.0.1 but I tried Nougat 7.1.2 too, it works.
I turned on my Note 2014 10.1 today for the first time in, apparently, over a year. And it still had over 90% battery charge on it after all that time. Impressive. It has root access and I'm running version 5.1.1 of Android on it. But I figure there's a newer stable version out by now that I could update the device to. But which one is the most stable, good on battery usage and performance, and with the best features?
Also, I've never used a custom modded ROM before, and I don't have any particular interest in doing abnormal things. So, unless they would offer some performance / power / security / feature or usability advantage, I probably don't need one.
Which ROM would you install to a Note 2014 P605 today?
One ROM I've looked at is this port of Android 6.0.1 - reported to be stable and good for daily use:
https://forum.xda-developers.com/galaxy-note-10-2014/development/rom-android-6-marshmallow-t3254901
I notice there are ROMs of Android 7 and 8, but I don't know if any of them very stable, with good performance, issue-free.
I'd love to know too.. Also is there a ROM that enables smooth playback of h265 videos?
Thanks
Nothing is as stable as a stock rom. And instead of the basic AOSP 6 you can as well stay with Touchwiz 5.0.
Or install LOS14/16/17, all several generations ahead.
My P605 is running rock solid with LOS 14.1 Nougat by @davidmueller13.
Unless you definitely need the s-pen functions (which can be bought as an app afaik) I recommend switching to a new ROM to get newer safety patch levels.
And David's best supported rom is the old Los 14.1.
I'm torn in between going back from Los16 and waiting for an update to the Los17(alpha) from early this year.
S-Pen works in third-party and Samsung apps available in Playstore and you can use it system- wide instead of your finger. Not more.
i need help i can't find the OEM option in the developer mode in my samsung 10.1 2014 i tried fastboot method and i was stuck on waiting for any device i need to be able to install twrp i have tried odin with no success . any suggestion pls
You can't unlock the bootloader?
That's not possible with some P605s with provider branding.
One major hurdle when attaching the device to a pc can be overcome by invoking Fastboot at power - on and then attaching the phone, instead of establishing an ADB connection which will require a reboot into Fastboot mode later on.
Good evening. I am completely new to modded rom installations. Is there perhaps a step by step guide on hoe to install the LOS Roms to my device?
Thanks