Hey guys,
So I am a relative NOOB - I flashed my girlfriend last phone, ZTE Blade 2 and loaded a custom ROM made from a guy in Brazil that actually worked really well off the paltry 4GB storage it had. Eventually got it to read the 8GB SD card as internal memory - but this was 3 months ago and involved a lot of trial and error before figuring it out - thanks to XDA of course.
So I bought her a new S5 sealed form Korea - SM-G900A AT&T version.
Firmware version: 4.4.2.
I tried to run an OTA update to Lollipop and said it couldn't find anything
Then I realized it was rooted, and I thought maybe that is what is preventing the OTA update. So yesterday I unrooted the phone and loaded STOCK Samsung from:
http://forum.xda-developers.com/showthread.php?t=2785363
Ran the OTA update request, still nothing.
Thinking as its an AT&T phone it may not run the OTA update on my countries networks - South Africa.
Thinking 2 stratergies going forward:
1 - Download the OTA Lollipop 5.1.1 version and forcing it to update without rooting the phone.
As described here:
http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900a/
Problem is I don't trust other sites and had good experiences with XDA so if someone could provide me a link to a XDA thread that hosts an OTA Lollipop update I would appreciate it.
Install Lollipop OTA on AT&T Galaxy S5
Make sure your AT&T Galaxy S5 is 100% stock Android 4.4.4 KitKat firmware.
Now download the Lollipop OTA package: OTA_S5_5.0.zip | Mirror
Copy the OTA zip file to the external SD card of your phone.
Enable USB Debugging on your phone as precaution.
Now turn off your device and reboot into the stock recovery. To do so, hold the Volume Up+Home+Power keys together while the device is switched off. As soon as you see the Samsung logo, release the Power key and keep the other two keys pressed until you see the recovery menu.
Using the volume keys, scroll to apply update from external storage option and select it by pressing the Power key.AT&T-Galaxy-S5-stock-recovery
Navigate to the OTA update Zip package and select it.
Confirm installation when prompted.
When the file is flashed, go back to the main menu and select “reboot system now” option.
2 - Rooting the phone and upgrading the ROM to Lollipop.
As described below - problem is I don't want to void the warranty (could be void considering was rooted when received) nor brick the phone.
I prefer lower risk option UNLESS someone has a secure method of doing it? Any advice appreciated
Install Pre-Rooted Lollipop on AT&T Galaxy S5
If you want to enjoy root privilege on your AT&T Galaxy S5 running Android 5.0 Lollipop firmware, the following instructions would help you do that.
Warning!
You can use this method regardless of what firmware or build version your phone has. However, you must be rooted to be able to use the FireFlash app! Flashing the pre-rooted firmware provided below will not trip the KNOX Warranty Void flag. The procedure given below is considered risky. Follow it on your responsibility!
Preparations
To gain root access on your AT&T Galaxy S5 running KitKat, you can try Towelroot.
Enable USB Debugging on your Galaxy S5. This step has nothing to do with the method given below but it could be a lifesaver if anything goes wrong.
Install Chainfire’s FireFlash app on your AT&T Galaxy S5. Since this new app is only available for beta-testers currently, go to the Google+ page and join the Android-FlashFire community. You must be signed into Google+ using the same Gmail ID that you use on the Google Play Store. Having joined the community, click the Play Store link to download FireFlash Beta app.
Download the stock rooted Lollipop firmware for the AT&T S5: G900A_OC4_Stock_Rooted_ROM_wOA1_BL.zip (Note: The ROM is currently not available.)
-------------------------------------------------------------
Please advise on the best way going forward. I have about 3GB left on my data to play with so the next ROM I download I want to be my last.
Related
I have a Canadian Koodo Galaxy S4 (Model: SGH-i1337m) and I need help on how to update my phone to the official touchwiz android 5.0.
The phone was originally locked to Koodo, but I took it to a local phone store where they unlocked it for me. I now use the phone with another carrier (Rogers). I don't know the method they used to unlock it but after the process, my phone had become rooted and its device status was changed to "Custom". Also the Knox warranty counter became 0x1 after the unlock.
Right now the phone is on 4.4.2 and I'm unable to check for updates through the settings app as it gives me the message "Your device has been modified. Software updates are not available."
I don't really use root for anything on my phone except for xposed (which I can live without) and I need help updating this phone to 5.0. I don't mind losing my data but I really need to keep this phone unlocked. If anyone can help me out, it would be greatly appreciated.
rhwn said:
I have a Canadian Koodo Galaxy S4 (Model: SGH-i1337m) and I need help on how to update my phone to the official touchwiz android 5.0.
The phone was originally locked to Koodo, but I took it to a local phone store where they unlocked it for me. I now use the phone with another carrier (Rogers). I don't know the method they used to unlock it but after the process, my phone had become rooted and its device status was changed to "Custom". Also the Knox warranty counter became 0x1 after the unlock.
Right now the phone is on 4.4.2 and I'm unable to check for updates through the settings app as it gives me the message "Your device has been modified. Software updates are not available."
I don't really use root for anything on my phone except for xposed (which I can live without) and I need help updating this phone to 5.0. I don't mind losing my data but I really need to keep this phone unlocked. If anyone can help me out, it would be greatly appreciated.
Click to expand...
Click to collapse
Hi,
I have the same phone, Canadian variant, SGH-i337M. Koodo.
Do you have a custom recovery installed? If not, I would suggest using TWRP.
Download it here (I have TWRP too, and always used the dd install method several times without problem. Just MAKE SURE you have the exact command!):
https://twrp.me/devices/samsunggalaxys4canada.html
Once TWRP is installed, really important to make a Nandroid backup ("Backup" menu). Would suggest copying the backup to PC as well (Backup everything, including EFS). TWRP is not needed to flash Lollipop, but it's important to keep a backup.
Next, flashing Lollipop using Odin (Doing this, your SD card/internal memory will be untouched, but you will loose your apps, SMS and stuff. Back these up before if you want. Otherwise, everything would be also in the TWRP backup you've performed earlier). Go to Sammobile to grab the update:
Koodo: http://www.sammobile.com/firmwares/download/45758/I337MVLUGOC4_I337MOYAGOC4_KDO/
Rogers: http://www.sammobile.com/firmwares/download/45777/I337MVLUGOC4_I337MOYAGOC4_RWC/
It doesn't matter much which one you choose - Their content remains the same, but maybe the radio/modem would differ between carriers I think. I would suggest choosing the Rogers firmware (I know that Koodo include a "Koodo" app in their firmware, for instance).
Then follow the instruction closely (Make sure to use a genuine Samsung cable, and reliable USB connection):
Instructions
Extract (unzip) the firmware file
Download Odin v3.10.6
Extract Odin ZIP file
Open Odin v.3.10.6
Reboot Phone in Download Mode (press and hold Home + Power + Volume Down buttons)
Connect phone and wait until you get a blue sign in Odin
Add the firmware file to AP / PDA
Make sure re-partition is NOT ticked
Click the start button, sit back and wait few minutes
I did the same thing myself to update to Lollipop. Worked great. But word of warning, you will loose your root access, and will have to root again (Same method worked for me, while I had problem disabling Knox on Lollipop somehow. Returned back to KitKat with my Nandroid backup).
Also, on that same Lollipop ROM, I encoutered WiFi issue, WiFi wouldn't turn ON at all (What the hell). Still haven't figured out the problem. That's why I would suggest keeping a backup of KitKat, for sure.
Also, don't worry about your unlocked phone, it will remained unlocked without problem.
Good luck
Hey Guys, I'm brand new to these forums, and to this whole community so bare with me.
Basically I bought my T-Mobile Samsung Galaxy S5 phone around the time it came out, and I also had installed root on it via towelroot when Towel Root was first released. I did not update the phone at all for a long period of time and everything was working fine, until one day I was browsing under settings and accidentally tapped the "Software Update" button, then T-mobile auto-pushed an update onto my phone.
This update has caused the root on my phone to not work at all (Deemed useless) So I clicked SU and only a black screen popped up when I tried to open the app, so I uninstalled it, reinstalled it then got a message saying "There is no SU binary installed, and SuperSU Cannot install it. If you just upgraded to Android 4.3 you need to manually re-root your device" So I tried to re-root via towelroot method again. It seems the T-mobile update made my phone "Unsupported/Uncompatible" with TowelRoot's obsolete techniques, so now I'm in dire need of help.
My phone tried to push another t-mobile update (This time to upgrade to Lollipop) but it failed after attempting to install it after a reboot. So not only will my phone not update to Lollipop, but I'm not even rooted anymore and am unsure on how to get back rooted, or what to do next since I used rooting as a primary source to store apps on my SD Card. Kind of like i'm stuck in one spot? (Can't update your phone/can't root it the old method)
I'm brand new guys, Please can you break down to me what I should do, in order to obtain root again, and possibly be able to upgrade to Lollipop As well as prevent further pushed T-mobile updates? Here's some info if you need it
S5 Model Number: SM-G900T
Android Version:4.4.2
Kernel Version:3.4.0-262.. etc. (Tell me if you need the full kernel details)
Any help would be greatly appreciated! Thank YOU!
Flash this with ODIN
http://download.chainfire.eu/407/CF-Root1/CF-Auto-Root-kltetmo-kltetmo-smg900t.zip
(Will trip KNOX and void warranty)
Or flash a pre-June 2014 KK Kernel, root with Towelroot again, then flash back your current Kernel
Is this the only solution? And also is it the right one? o.o
Can anyone else please give me some feedback on the situation? I want to make sure I do this right, please just a little helps.
Bump
bump
*Detection* said:
Or flash a pre-June 2014 KK Kernel, root with Towelroot again, then flash back your current Kernel
Click to expand...
Click to collapse
Hey I did exactly what you said and it worked I got root back, but I was wondering how to flash back to my current kernel and keep Root?
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
I'm afraid I'm not familiar with Samsung devices, and because I purchased this from ebay, I don't know how to tell the exact state that the former user put it in (I expected they would return it to stock prior to selling).
It's currently a T-Mobile branded, SM-N900T, on 4.4.2, build is KOT49H, security software MDF v1.0 release 2. Kernel is 3.4.0-660648.
It is supposedly unlocked for carriers, though I have not attempted a SIM card use yet, until I can tell that what I have is a valid device and the IMEI is checked out.
Any thoughts on how to validate the IMEI, and sort out how to get my new phone up to date would be appreciated. As I stated, I expected the vendor would have returned it to stock, but that is clearly not the case, so I don't want to accidentally boot loop it by doing something I shouldn't. I have not owned a Samsung before, so I want to be careful on how it differs from my Nexus 7, Amaze 4g, and Droid X, as they're all obviously very different in the OS area.
Thank you for the help1
Download tbe stock 4.4.2 rom and use odin to install. Then you will get the OTA updates.
Sent from my SM-N900P using Tapatalk
There is no stock 5.1.1 for note 3, only cm12.1/ aosp. Latest is 5.0 and you can use odin to flash. Maybe it's rooted that's why you can't update.
bladebarrier said:
I just swapped from my Amaze 4g, to a used Note 3, and I'm a little lost as far as where I should start.
It says that it's on 4.4.2, and that I cannot update due to a modified system.
Basically, I would like to get updated to 5.1.1 (or as close as is official for the Note 3), and root it.
...
Thank you for the help1
Click to expand...
Click to collapse
Some apps to install from Play Store...
Phone INFO Samsung - this will tell you all about your phone and the firmware etc.
Root Checker Basic - tells you if you are rooted or not.
SuperSU - this is so valuable you should buy the Pro licence. Chainfire does some great work for our phones.
TWRP - I have the zip version on my extSDCard and an Odin version on PC in case I have to rebuild from a Stock firmware. CWN works OK but most ROM builds seem to be for TWRP I think and a backup from one will not work on the other.
I don't know your previous phone so you probably need Odin v3.09 - this sits on PC and lets you flash firmware to the phone. (connected by USB)
For which you need Samsung USB drivers so the PC will recognise the phone. Install on PC before connecting phone.
Then do some browsing and find the processes to root your phone and install the ROM you want. If you just want Stock and access to all your phone, you can root it after flashing the original v5.0 download (from Sammobile or similar site - note on Sammobile you need a free account to DL) and then install Custom recovery (if wanted - it WILL trip the Knox flag but that may not matter given it's 2nd hand and might already be tripped anyway)
Read, make SURE you understand what is being said BEFORE you do anything - ask if you don't.
Good luck...
N9005 Lollipop brick
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Thank you all for the info, especially the detailed info from Journyman16. I checked, and it is flagged as custom, which is fine, so I'm going to go ahead and try to return to mostly stock, update it, and root it.
Ok, everything went well. I had to do two attempts at rooting, but I think it's just one of those things where sometimes it doesn't restart into the process every time.
All seems good. I'm on 5.0, rooted, busyboxed, and smooth sailing.
Thank you all, again, for the tips. The Note 3 is running very well. Thank you to all of the devs that have made this process so refined. I've donated to you before, and did so again today. It's outstanding to have such well versed coders, on XDA, helping out the community.
mjmbirige said:
Hi All, just need a huge help here, a friend of mine has been using a N9005 which was auto restarting, she went online and downloaded this firmware...N900AUCUEOC1_N900AATTEOC1_N900AUCUEOC1_HOME.tar.md5....2.5GB in size...and flashed it, but the phone is stuck in boot loop even after recovery wiping data and cache, the phone can boot into download mode but re flashing the firmware always fails.....is there a solution for this.....please help
Click to expand...
Click to collapse
You have never learned not to ask in others posts? What does your problem has to do with this topic at all?
When you need help. Just click on Q&A then Create a new thread. How hard is it?
Hi all,
A couple quick questions here. I've done some reading up, but most of the information is more in depth than I need at the moment so I'm looking for some quick answers.
My SO has a Verizon S5, that has a locked bootloader, is not rooted, and is still on 5.0.
She swapped carriers a while back, so is no longer on the Verizon network. The IMEI is clean, and her Verizon account is fully paid, and everything on the phone works fine, aside from it being stuck on 5.0.
It will not update via the automated system, because I assume it's trying to reach out to straight talk for the update and gets a response that it's on the newest version.
I downloaded the Verizon OTA update file (approximately 1 gb) for 6.0.1. It's named update.zip to allow for automated updating.
Here are my questions:
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
Thank you very much for your assistance!
Hi bladebarrier, I actually just did the same thing a few weeks ago with a used S5 from Verizon going to Straight Talk.
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
I'm unsure if that would work, someone else may be able to answer as to that method, however I used the Odin tool v3.11.1, downloaded the PD1 image from here. There are some good video tutorials on YouTube and on writeups on this forum as well regarding how to flash the Marshmallow update using Odin.
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
No downsides that I've noticed and seems to have slightly better battery life.
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
You do not need root to flash it if using the Odin tool.
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
Yes, but it's always a good idea to make a backup of everything.
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
The only thing that the locked boot loader affects for now is the ability to flash custom ROMs. I was able to downgrade to 5.0 Lollipop which you can still root, even after upgrading, however I decided to just go back to Marshmallow and wait for an exploit to be found, if one ever is.
jesimpki89 said:
Hi bladebarrier, I actually just did the same thing a few weeks ago with a used S5 from Verizon going to Straight Talk.
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
I'm unsure if that would work, someone else may be able to answer as to that method, however I used the Odin tool v3.11.1, downloaded the PD1 image from here. There are some good video tutorials on YouTube and on writeups on this forum as well regarding how to flash the Marshmallow update using Odin.
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
No downsides that I've noticed and seems to have slightly better battery life.
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
You do not need root to flash it if using the Odin tool.
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
Yes, but it's always a good idea to make a backup of everything.
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
The only thing that the locked boot loader affects for now is the ability to flash custom ROMs. I was able to downgrade to 5.0 Lollipop which you can still root, even after upgrading, however I decided to just go back to Marshmallow and wait for an exploit to be found, if one ever is.
Click to expand...
Click to collapse
Thank you very much for your thorough response. It sounds like it will be a nice smooth flash, and I will use the full Odin version instead of the OTA file, to ensure it goes through comfortably.
Odin looked like it wanted to wipe the apps, so I ended up using the stock recovery/installer that's built in, and placing the OTA update file on the external SD card.
That worked like a charm. It took a bit, as expected, but all of the apps and info were ok after.
The only thing I can't sort out is why I can't find an option for the "Themes" setting in touch wiz. Any suggestions? I realize I could have her go to a third party launcher, like nova, but I have all of the theme options on my note 3, that's ported to MM note 5, and the theme option is still right there in the settings list, per normal. Maybe I'm just not seeing it, but I couldn't find an option on her S5 during 5.0, or now on 6.0.1. Is that something they never updated for the older phones?
Hi all,
Was recently in the 'States and broke my S8 - it's now the third mobile screen I've busted since Samsung brought in curved edges, never had any issues with the S2 or S5 - who ever thought tempering glass and curving it would be a good idea??
Anyway I had the opportunity to pickup a brand new Samsung Galaxy S8 Active and did a quick bit of research. I found the most compatible version with my carriers back home in AUS was the SM-G892A from AT&T. Picked up a brand new unlocked model, stupid me didn't connect it up to AT&T while I was there. I turned it on and played around with it on Wifi for the last few days of our trip and returned home to Melbourne.
Basically I now understand AT&T are a bunch of ***** and do not allow updates to be pushed even for unlocked devices overseas. Considering a lot of the updates are for security I'm very surprised by this.
Anyway so I've notcied a few tiny bugs here and there with apps/OS and figured updating my device/OS is the way to go and might resolve the issues. I guess the easiest way to get the info I need is to put the questions I have individually, as my mind tends to jump all over the place when I'm working a problem:
1. Is there any way to get my phone updated without rooting/flashing the phone?
2. If not, what is the best option for a S8 Active? Are there any firmware versions that will enable OTA updates so I don't need to keep flashing everytime new firmware is released? I have seen some posts about T-Mobile being able to be flashed over an AT&T model or even the G892U or maybe a custom firmware that allows this?
3. Will rooting/flashing interfere with any of the carrier settings etc? Don't want to upgrade it only to find it disables an LTE band or something?
4. I am an absolute noob at flashing, have never done it but am pretty tech savvy so if there is a step-by-step procedure I wil have no dramas following it. Saying that, I would rather not make the device worse than it is so I only want to follow tried & tested procedures if that makes sense, I don't want my device to be a lab-rat.
5. If there is no way to enable OTA internationally as per Question #2 when new firmware updates become available on XDA will flashing a new update delete personalisation/settings/files etc? Or will it retain them and update like a stock model performing a firmware upgrade would? If not, that would be a pain in the ass and time consuming to have to re-apply settings and reinstall apps every time and almost makes the idea of flashing unattractive.
6. I have baseband G892AUCU1AQG4 - taking into account Question #2 what is the best way to move forward? Considering Android 8.0 is available for the S8 Active and has been available for my model from AT&T since March 1st, 2018 apparently I'm hoping there might be some way to move towards that.
Hope someone might be able to help,
Thanks in advance
UPDATE 05/05/2019
Got some answers to my original questions...
1. Rooting/Flashing are different things - rooting allows custom firmware, flashing is the procedure to install custom or OEM firmware onto the device.
2. The best option for me I think is to just update to newer AT&T firmware so I get the updates and new software features as I'm not interested in custom firmware. I still do not know if it is possible to get OTA updates for this device directly from Samsung/Google.
3. As long as you are flashing from the same model firmware as in SM-G892A to SM-G892A should be no issues, however using SM-G892U might cause issues.
4. Once I wrapped my head around how baseband versions of firmware work and what is needed to get between bootloader versions flashing from SD Card or Odin (as I suspected) was very straightforward thanks to some of the guides out there. To make this easier for anyone facing the same issue I have written how I did this below.
5. Yes, flashing for AT&T will delete everything, it's an absolute PIA and that's why I will keep searching for a way to get OTA updates enabled if at all possible. However I believe Samsung SmartSwitch is pretty good for backing up and restoring so that might be a simple way forward.
6. See my latest post, I was 12 updates behind but able to skip 7 of them using my method.
I'm considering importing an S8 Active AT&T and have the same questions. How did you go?
secateurs said:
I'm considering importing an S8 Active AT&T and have the same questions. How did you go?
Click to expand...
Click to collapse
Sorry for the slow reply I've only just had the time to dive into this. Yes I have figured it out.
There are two ways, incrementally update by applying OTA updates via the SD card. However trying to find all of these can be a pain.
The other way you may have read about is to use Samsung's own 'Odin' flashing software.
Because I had the very first baseband version G892AUCU1AQG4 I was way behind. The fifth-last digit designates the bootloader version, you cannot jump from v1 to v3 for example. So what you can do is use a few OTA updates to jump you from v1 to the first v2, you can then use Odin to jump you all the way up and use another OTA to get you to the next bootloader version. Hope that makes sense?
So I was able to use x2 OTA updates to get from 1AQG4 to 1AQJ2, then I was able to do one more OTA to get from 1AQJ2-to-2AQK3. Now if I was to continue using the OTA method with the SD card, I would need to run the process x8 times. This presents 3 issues:
1. Time consuming, trying to find all the correct OTA updates.
2. Even when you do get all the correct OTA updates you then have to copy each on to the SD card waiting for the phone to update and then repeat the process.
3. Even if you can find a link for a required OTA update a lot of the links are dead.
However using Odin and the flash files I was able to skip these and go directly from 2AQK3 to 2BRF2, use one OTA update and then I was onto Bootloader v3 (which is the latest version). Here is how I compressed 12 updates do into 5, good luck..
1. 1AQG4-to-1AQJ2 OTA (SD CARD): dropbox.com/s/ikor71zt1ec0nyn/SS-G892AUCU1AQG4-to-S1AQJ2.zip?dl=0
2. 1AQJ2-to-2AQK3 OTA (SD CARD): dropbox.com/s/ott9fs9qunkvf9x/SS-G892AUCS1AQJ2-to-U2AQK3.zip?dl=0
3. 2AQK3-to-2BRF2 Odin Flash : androidfilehost.com/?fid=1322778262904016415
4. 2BRF2-to-3BRG1 OTA (SD CARD): androidfilehost.com/?fid=1322778262904016441
5. 3BRG1-to-3BRL1 Odin Flash: mega.nz/#!7M42VCAJ!-FKnhzwTZG0He1kb9FzHHaPX4Aanlnj4fpn0M61DzR4
Have the s8 active outside of America and desperately want to update it
Hey ,
I'm sorry to bring up this old thread but I didn't really understand the method you used sorry I'm really new to this thing, I have the s8 active Sm-g892A ( the att) model it's on the baseband version G892AUCS2ARB1 . If you could help me out a bit with this I would be really grateful, having Android 7.0 really makes me concerned as I've heard the security patches also won't update.
None2939 said:
Hey ,
I'm sorry to bring up this old thread but I didn't really understand the method you used sorry I'm really new to this thing, I have the s8 active Sm-g892A ( the att) model it's on the baseband version G892AUCS2ARB1 . If you could help me out a bit with this I would be really grateful, having Android 7.0 really makes me concerned as I've heard the security patches also won't update.
Click to expand...
Click to collapse
So you are on Bootloader v2 (5th character from the right). So you can skip straight to Step 3. Be warned all instructions below will result in all data on your device being wiped!
Using Odin to upgrade as directed on Step 3 & 5 or future upgrades (there is now v4 software appearing):
You need to download Odin (you don't need a modified/Comsy version).
You need to enable Developer Options on your Galaxy.
Once you have developer options you need to enable 'USB Debugging'.
You need to shutdown your Galaxy.
Connect your USB cabble to your PC.
Boot into Download mode by using the Power+Bixby+Volume Down combo. OR if that doesn't work Use the Power+Bixby+Volume Up and use the menu to get into Download Mode.
Open Odin on your PC, it should say 'Added' if it detects your Galaxy correctly. If it doesn't you may need to install some USB drivers (you can Google how to do this).
Once it says 'Added' you can add the files from Step 3 and flash but be warned it will wipe everything on your device.
For Step 4 OTA:
Very simply download the ZIP file and place the complete ZIP file on an SD Card (it should not be extracted must be complete ZIP archive). Place the SD Card in the Galaxy, power off and boot into Recovery Mode Power+Bixby+Volume Up. Then simply use the Volume Up/Down and Power keys to navigate through, 'Apply Update from SD Card', find your SD card and the ZIP file and allow the update to run.