I know AT&T does not update the S5 anymore (went end of life), but is there a way to install Nougat on the device?
I also know the bootloader is locked which makes this difficult since we can't use TWRP.
What I don't know is if there's a way to get Nougat anyway.
Not on our current kernel and bootloader. There is talk of a new exploit in the download mode that may allow us to run an unsigned kernel, almost like a tethered jailbreak, but it is still in the testing phases.
Related
Hi all, I was wondering if it would be less of a hassle to keep my BL unlocked Moto X stock until Lollipop OTA comes out OR if it might actually be harder to install recovery, root, etc when 5.0 is on the phone? IIRC KK made some changes that caused hassles on rooting, recovery install for some phones. I have Dev Edition, thanks
Although lollipop is making it difficult to root, you would still be able to unlock your BL on lollipop. Since it appears you don't have a need to root right now, I would just wait until lollipop. The reason to wait is if you install a recovery or freeze apps, you won't be able to install OTA until you restore stock recovery etc.
As long as you have an unlocked / unlockable BL, you will always be able to install a custom recovery / root.
PsychoKilla666 said:
Hi all, I was wondering if it would be less of a hassle to keep my BL unlocked Moto X stock until Lollipop OTA comes out OR if it might actually be harder to install recovery, root, etc when 5.0 is on the phone? IIRC KK made some changes that caused hassles on rooting, recovery install for some phones. I have Dev Edition, thanks
Click to expand...
Click to collapse
it depends.
With an unlocked bootloader we should continue to be able to flash a custom recovery, and custom rom.
However, there are several unknowns right now, including when will we see Lollipop for the X? Which variant of the 2013 X (Dev vs ATT vs VZW vs Sprint, etc) will get it first? When will soak tests start? When will the carriers finally push it, etc?
Then we don't know how hard or easy it will be to root. At first a custom kernel was needed to root Lollipop, but now it seems Chainfire has found away around that http://www.androidpolice.com/2014/1...w-to-root-lollipop-without-a-modified-kernel/ Until we see L on a 2013 X, we wont know for sure.
In any case, its always less hassle to keep your phone STOCK if you want to take an OTA. The OTA's need stock recovery on the phone in order to install. Also, diverting from stock can mean changes which will cause the OTA's pre-flash validation checks to fail, and the OTA to not install.
US Cellular is STILL on 4.4.2 lol 5.0 seems a hundred miles away still. Glad I'm unlocked, rooted and stock (Xposed Gravitybox) best combo IMHO.
Recently purchased an AT&T XT1097. It was on Android 4.4.4 which I temp rooted with Kingroot and then bootloader unlocked using Sunshine. I'd like to upgrade to 5.1 so I haven't bothered yet with rooting or installing a recovery. Frankly, I'm a wee bit confused by the information I've found in numerous threads on this and other sites simply because it seems the AT&T and Verizon versions of the Moto X 2014 are problematic to work with.
Does having my bootloader unlocked at this point mean that any root method will work on the device? I believe flashing should be a non issue at this point (because the bootloader is unlocked) but will it also allow me to downgrade to 4.4.4 or 5.0.2 if I am not pleased with 5.1? Is using TWRP a good idea or would it be best to manually flash images thru fastboot (which I couldn't do without clear instructions)?
On a related note my device initially reported an available OTA system update but since unlocking via Sunshine I haven't had the notification return. MDM also doesn't see an available update. Is this due to Sunshine or left over vestiges of Kingroot despite having done a FDR?
Further update...
With no replies to my questions I've taken it upon myself to try a few things. Figured out that MDM will not see an available update unless the device can connect with AT&T via wifi at which point it tells me that an update is already in progress because the OTA is downloading to the device. I would prefer to download and flash the full image via MDM but it is refusing to do so. I'm assuming that this may be because the update the phone wants to install is now considered an interim update (5.0.2) and the full image has been pulled from Motorola's or AT&T's servers.
I have been able to successfully root 4.4.4 but have since removed it in the expectation of updating the device shortly. I have also been able to boot a TWRP image in the hopes of doing a backup before making any significant changes but the device becomes unresponsive to touch commands at the write protect warning screen. Any ideas???
Hi,
This is a very basic question, but I haven't been able to find the answer in one place.
I have a new Galaxy S6 Edge G925A on AT&T, baseband version G925AUCU1AOE2. I don't want to take the OTA update because apparently then the bootloader will be locked and can't be rolled back. I'd like to root the phone and not lose any features but I'd also like to be able to flash a ROM based on the most current version of Android available (and continue to upgrade in the future). Right now I only know enough about rooting, bootloader, baseband, kernels, custom recovery, ROMs, Android, KNOX, radios, modems, fingerprint scanners, Samsung Pay . . . to be dangerous. Every search I've done over the past couple days seems to teach me something while also confusing me a little bit more.
What I'm wondering is - if I root my AOE2, am I then able to flash a custom ROM based on 5.1.1 (or later) versions of Android without losing any other features (Samsung Pay, fingerprint scanner, etc.) and without locking myself to a certain version of Android? If so, what steps would I have to take (e.g., 1) root, 2) install a custom recovery, 3) flash a later kernel, 4) flash ROM, etc.)? Thanks in advance, and sorry if this question is answered elsewhere already!
monkton said:
Hi,
This is a very basic question, but I haven't been able to find the answer in one place.
I have a new Galaxy S6 Edge G925A on AT&T, baseband version G925AUCU1AOE2. I don't want to take the OTA update because apparently then the bootloader will be locked and can't be rolled back. I'd like to root the phone and not lose any features but I'd also like to be able to flash a ROM based on the most current version of Android available (and continue to upgrade in the future). Right now I only know enough about rooting, bootloader, baseband, kernels, custom recovery, ROMs, Android, KNOX, radios, modems, fingerprint scanners, Samsung Pay . . . to be dangerous. Every search I've done over the past couple days seems to teach me something while also confusing me a little bit more.
What I'm wondering is - if I root my AOE2, am I then able to flash a custom ROM based on 5.1.1 (or later) versions of Android without losing any other features (Samsung Pay, fingerprint scanner, etc.) and without locking myself to a certain version of Android? If so, what steps would I have to take (e.g., 1) root, 2) install a custom recovery, 3) flash a later kernel, 4) flash ROM, etc.)? Thanks in advance, and sorry if this question is answered elsewhere already!
Click to expand...
Click to collapse
Simple answer is no.
Sent from my SAMSUNG-SM-G920A using Tapatalk
So - if I want to have the latest version of Android possible on this phone does that mean I can't also be rooted (or be using a custom ROM)?
dandrumheller said:
Simple answer is no.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Click to expand...
Click to collapse
monkton said:
So - if I want to have the latest version of Android possible on this phone does that mean I can't also be rooted (or be using a custom ROM)?
Click to expand...
Click to collapse
Correct. Since you are still on OE2, your choices are as follows:
1) root with ping pong and go to
A) custom 5.0.2 ROM, keeping root
B) stock OF3, keeping oe2 bootloader and recovery via odin/flashfire, keeping root
C) stock OF4, keeping oe2 bootloader and recovery via odin/flashfire, keeping root
2) don't root, update to full stock OF3/OF4/5.1.1 (I forget the build number), lose the ability to root, lose the ability to roll back. Possible that this will never be rooted.
Sent from my SAMSUNG-SM-G920A using Tapatalk
Dang. Thanks for confirming. They're sons of *****es. Why do they need both an early contract termination fee AND to lock down the phones so you can't get full enjoyment out of the hardware you're committing to a 2-year contract to get?
My phone is reporting the following
Android Version = 5.1.1
Baseband version = G920AUCU1AOE2
Though my phone has the 5.1.1 update but my baseband didn't get updated does still mean I'm SOL for a future root?
Is there any option that someone working on that?
I love this phone - I got it for about one month
Maybe Samsung? You cannot install custom firmware to this phone.
Dear @mulp, I am very sorry to tell you this but the Samsung Galaxy S6 Active cannot be upgraded past Android 7.0.1 Nougat, you cannot upgrade it using a Custom ROM such as CyanogenMod or Lineage OS. The reason is because the Active is an AT&T exclusive phone and as such, the bootloader cannot be unlocked. Even as of now (2018), no developer has been able to exploit and hack the locked down bootloader. If you try and exploit the bootloader by flashing TWRP, your KNOX counter can be triggered to 0x1 (believe me, I tried, I failed). The only way to root the device is to flash a combination file but even though, you cannot flash a custom ROM. Sorry about that, but that is AT&T for you.
Gold_Danny04
Hey Guys! I write to know that how can I update my moto x 2nd gen. from lollipop to marshmallow without opening its bootloader or root because I think these two options are not safe and somehow will damage my device. By the way its a verizon variant xt1096. So guys please help me, will be very grateful
Sapper Morton said:
You could update to MM without unlocking the bootloader, unfortunately the XT1096 ( Verizon ) didn't ever received the Stock MM Firmware, so no lucky to you mate.
Flashing Stock firmware from other variants with locked bootloader could become a nightmare very quickly, so I don't recommend doing that.
If you want a phone that is more or less secure, you better be staying on locked state on Lollipop.
Unlocked bootloader + partition encryption is a reasonable security measure for smartphones, but yet is vulnerable to injection of custom binaries due to the unlocked state.
On daily use, you will hardly ever be vulnerable, however you could be exploited if you become a specific target.
Other than that I recommend buying a new phone that supports security updates officially, for a least to the next 2-3 years.
You know your daily life and your priorities, you can decide for yourself.
Click to expand...
Click to collapse
Thanks for the advice! I really appreciate your thoughts. Well you said that I can update to marshmallow by flashing other variants firmware without opening my device's bootloader. So how can really do that? By the way I have already tried updating through recovery mode, but it didn't work. So is there any other way to update my device.
I have the Verizon model too, and same situation. Phone still works fine, but I couldn't tolerate being 4 major Android versions behind. Eventually, I bite the bullet, unlocked the boot loader (since device is well out of warranty anyway), flashed a Oreo-based Linage OS ROM, which really brought new life into the phone. Some minor issues here and there but nothing huge. You should be okay if you know what you're doing and backup your stock configuration properly.
Sapper Morton said:
You could flash other variants firmware, however the stock MM doesn't support CDMA, only GSM.
With locked bootloader you will only get your XT1096 to work on non-verizon carriers, or partially work on verizon, since they don't use CDMA exclusively anymore.
There was a modded stock MM OS in the past, made to work on verizon network, unfortunately, you need an unlocked bootloader to flash it.
In case you should consider unlocking your bootloader, I recommend flashing the LineageOS 14.1, Android 7.1.2.
Any AOSP ROM, based on CM13, Android 6.0.1, should support CDMA and GSM from the source.
In which case, the Lineage 14.1 supports it, and it has the latest security patches, as I said before, using /data encryption on a unlocked state, is a reasonable security measure you should consider, that way, anyone that may get hands on your device will be unable to read the data, being naive.
Click to expand...
Click to collapse
Thanks once again for your time! Actually I am not on CDMA, I'm using GSM network. So how can update to marshmallow now and I prefer stock marshmallow rather than custom or any other roms. So please guide me in that.