Hello all,
So just recently I was having problems with my current firmware of Marshmallow 6.0 and I was thinking it's about time to upgrade to one of the latest firmwares available to XT1575. I'm always getting the update notification for Nougat 7.0 and I somehow accidentally chose the option to download the firmware and install it. As of now, I am stuck with my phone trying to update itself to Nougat 7.0. If you're wondering, yes my phone is rooted using Magisk. I am clueless of what to do now. Any help would be greatly appreciated.
NoHoesNick said:
Hello all,
So just recently I was having problems with my current firmware of Marshmallow 6.0 and I was thinking it's about time to upgrade to one of the latest firmwares available to XT1575. I'm always getting the update notification for Nougat 7.0 and I somehow accidentally chose the option to download the firmware and install it. As of now, I am stuck with my phone trying to update itself to Nougat 7.0. If you're wondering, yes my phone is rooted using Magisk. I am clueless of what to do now. Any help would be greatly appreciated.
Click to expand...
Click to collapse
After several reboots, I received the update failed notification. Problem has solved itself.
Related
Is it a good idea to update latest firmware? I just got a notification recently saying that there is an update. So I heard about Samsung took some precautions to prevent rooting with new firmware. I am not planning to root my device soon but was just wondering, is there any disadvantage of updating to latest firmware?
Hi Everyone,
So I originally installed Oreo via OTA from Nougat but started to experience sluggishness and performance issues. I decided to manually flash the Oreo 6P image from the Google site to start from a clean state and hopefully resolve my device's performance issues. So I unlocked the boot loader, flashed the latest build OPR6.170623.017 which includes the September security patch and relocked the boot loader without any issues. This is where it got kind of weird, after the initial boot and device setup I got an OTA notification for Android 8.0 Oreo thats 991.4 MB in size. This looks to be the full 8.0 OTA upgrade but I'm not sure why I'm getting this notification after I just manually flashed the latest version. I've double checked the build number and security patch date in the settings menu and they all match the latest image I flashed from the Google site. Had anyone ever encountered this before or know what's going on? Why would I get an OTA after manually flashing the latest build? Any guidance would be appreciated.
Thanks
TechnicallyImpaired said:
Hi Everyone,
So I originally installed Oreo via OTA from Nougat but started to experience sluggishness and performance issues. I decided to manually flash the Oreo 6P image from the Google site to start from a clean state and hopefully resolve my device's performance issues. So I unlocked the boot loader, flashed the latest build OPR6.170623.017 which includes the September security patch and relocked the boot loader without any issues. This is where it got kind of weird, after the initial boot and device setup I got an OTA notification for Android 8.0 Oreo thats 991.4 MB in size. This looks to be the full 8.0 OTA upgrade but I'm not sure why I'm getting this notification after I just manually flashed the latest version. I've double checked the build number and security patch date in the settings menu and they all match the latest image I flashed from the Google site. Had anyone ever encountered this before or know what's going on? Why would I get an OTA after manually flashing the latest build? Any guidance would be appreciated.
Thanks
Click to expand...
Click to collapse
Nevermind, figured it out. Mods, please delete this.
TechnicallyImpaired said:
Nevermind, figured it out. Mods, please delete this.
Click to expand...
Click to collapse
Would you maybe elaborate how you fixed this issue? I'm experiencing exactly the same thing right now..
Leviathius said:
Would you maybe elaborate how you fixed this issue? I'm experiencing exactly the same thing right now..
Click to expand...
Click to collapse
Ver .017 is the latest factory image but that is not the latest version. The full OTA is ver .019, which is technically the latest version. There is no factory image for it at the moment. Just an ota package. Hence the notice to download and install again
Sent from my Nexus 6P using Tapatalk
Ok so I rooted my Verizon phone 2 years ago and I'm still running 6.0.1 with G935VVRU2APE1, the security patch level is from June 1, 2016, yes I'm wayyy behind. I'd like to go to Nougat or Oreo if possible with a fresh start/data wipe. Not concerned with root atm.
Where do I start? I've read through a lot of forum pages but no one has a build as old as mine it seems. According to updato.com/firmware-archive-select-model?q=SM-G935v (can't post proper link) the latest build for 6.0.1 is G935VVRU4API3. Can I go from APE1 to API3 without issue following "{GUIDE} Flashing the SM-935U firmware onto your Verizon S7 Edge and Rooting" or does it have to be a certain prior version?
From there will an OTA update or an official stock odin file get me to Nougat/Oreo? Thank you in advance!
I did upgrade my 6.0.1 V to 7.0 U. From there I got the OTA updates/upgrades to Oreo. You can get them faster if you use SmartSwitch on PC and phone.
SoNic67 said:
I did upgrade my 6.0.1 V to 7.0 U. From there I got the OTA updates/upgrades to Oreo. You can get them faster if you use SmartSwitch on PC and phone.
Click to expand...
Click to collapse
Thanks for the reply. So do I go from my current build to the latest 6.0.1 (API3) or just go straight to the latest 7.0?
I would say you have to go to an official one first, using Odin.
Hi all,
First time poster, long time lurker.
I have recently purchased the galaxy s8 the other day, I was expecting for it to come with the Android default version 7.0 Nougat, however, it came with Oreo 8.0.
The baseband version of the phone is G950FXXU4CRI1, and the fifth last character indicates it is running Bootloader 4.
I heard it is impossible downgrade since the current available 7.0 Nougat roms from SamMobile are Bootloader 1.
I would like to clarify is that true?
If so, what happens If I force the downgrade with a different Baseband version?
If I am unable, are there any alternative ways to downgrade to 7.0 using an official samsung rom?
Any help would be appreciated.
Thank you
you are meddling in things that will error out in odin and or lose your IMEI.
anti rollback stops you from doing this fused binary device such and such version
So basically, my friend has been on nougat 7.1.1 for like a year now. Even though the update has been out for so long, it doesn't show up when I search for it through system updates. When I recently downgraded to nougat, I immediately got notified that the oreo update was available. So why doesn't it show up for him? Also if I were to download the update and install it manually, his data would be safe right? I wouldn't have to make a backup since it's just another OTA right?
What version is your friend's axon7? I once got a chinese version that was flashed with global rom, and it will never get any update untill you flash the original rom.
YoungAll said:
What version is your friend's axon7? I once got a chinese version that was flashed with global rom, and it will never get any update untill you flash the original rom.
Click to expand...
Click to collapse
Nah he bought an A2017G spanking new. He shouldn't have this problem. Also funny story, I recently rooted my phone and installed magisk and LOS 15.1. Somehow its model is now A2017U. Any explanation?
I second that question. Got one second-hand two weeks ago with Nougat 7.1.1. No updates popping up, when I let it search for them.
I have same problem. Android 7.1.1 A2017GV1.2.0B05 and no update find...