I try to install Oreo Beta 2 and it says older time stamp and degrade is unavailable. I researched a bit and found that I need to flash back to older firmware. I downloaded it from the STOCK thread but I couldn't sideload it. It says footer is wrong, sig verf failed and other stuffs. Im currently on the lastest firmware
Have you updated to the latest firmware with January security update if so that's why
r8dooo said:
Have you updated to the latest firmware with January security update if so that's why
Click to expand...
Click to collapse
Yes, I have.
So there is no way to do it now?
You should be able to downgrade if your bootloader is unlocked.
loctuantran said:
Yes, I have.
So there is no way to do it now?
Click to expand...
Click to collapse
I updated to latest security patch for January and unlocked bootloader and flashed to Oreo beta 2 no issues. Essential.com and do it step by step and should have no issues.
Related
As Verizon users know a new OTA was pushed yesterday 02/16/17 the update is safe to take if you have a unlocked bootloader you will need to reflash TWRP and root you will lose both after updating
Haven't seen a new OTA on Verizon.
@Shiftydogit, build no. anything?
I'm guessing it is not showing on anyone who manually upgraded with the latest Google OTA files. Not sure about the regular Google update files, but probably checks the system version ether way for 7.1.1, NOF26V and the latest (February) security version.
sliding_billy said:
I'm guessing it is not showing on anyone who manually upgraded with the latest Google OTA files. Not sure about the regular Google update files, but probably checks the system version ether way for 7.1.1, NOF26V and the latest (February) security version.
Click to expand...
Click to collapse
Its all determined by the IMEI and ICCID. The images from Google and VZW are now identical. I got the OTA push and Im on the latest Google OTAs. They simply don't roll out OTAs to everyone at the same time .
Newer than February security patch 7.1.1 NOF26V? What's the build number? I'm 100% stock on NOF26V and can't pull an OTA at this time.
Shiftydogit said:
As Verizon users know a new OTA was pushed yesterday 02/16/17 the update is safe to take if you have a unlocked bootloader you will need to reflash TWRP and root you will lose both after updating
Click to expand...
Click to collapse
Have you rerooted? Idk if I have much reason to, since I rooted mostly for tethering, but I'm curious about the reliability in that
Soccerdude588 said:
Have you rerooted? Idk if I have much reason to, since I rooted mostly for tethering, but I'm curious about the reliability in that
Click to expand...
Click to collapse
Not at the moment been to lazy to reflash TWRP lol
farfromovin said:
Newer than February security patch 7.1.1 NOF26V? What's the build number? I'm 100% stock on NOF26V and can't pull an OTA at this time.
Click to expand...
Click to collapse
NOF26V is the newest OTA. NOF26W is for Rogers. NOF26V was pushed a few weeks ago and includes the February Security patches. I'm assuming those getting it on 2/17 were either late, or part of the 7.1.2 beta program.
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
Since 7.0 came to the s7, I have been keeping up with the monthly updates the carriers push out but for the past couple of months I've been getting some terrible kernel wake locks and I've tried everything possible to prevent them but I can't find a solution. So my thought was downgrading to an earlier 7.0 where I didn't have that problem.
Now my question is: Has the bootloader been updated prior to the first 7.0 monthly update (march)? Because I've heard once the bootloader has been updated you can't go downgrade to an earlier bootloader and I've experienced a soft brick on my s7 edge while tried to downgrade to an earlier version of marshmallow and someone told me it was because of an update to the bootloader. The firmware i'm on now is G935W8VLU2BQH1 and I want to go down to G935W8VLU2BQB6 which is the first nougat update (march)
orlans21 said:
Since 7.0 came to the s7, I have been keeping up with the monthly updates the carriers push out but for the past couple of months I've been getting some terrible kernel wake locks and I've tried everything possible to prevent them but I can't find a solution. So my thought was downgrading to an earlier 7.0 where I didn't have that problem.
Now my question is: Has the bootloader been updated prior to the first 7.0 monthly update (march)? Because I've heard once the bootloader has been updated you can't go downgrade to an earlier bootloader and I've experienced a soft brick on my s7 edge while tried to downgrade to an earlier version of marshmallow and someone told me it was because of an update to the bootloader. The firmware i'm on now is G935W8VLU2BQH1 and I want to go down to G935W8VLU2BQB6 which is the first nougat update (march)
Click to expand...
Click to collapse
Just download rom from sammobile, you will have all the files for downgrading.
MS420 said:
Just download rom from sammobile, you will have all the files for downgrading.
Click to expand...
Click to collapse
I did that back in December while on 6.0.1 and odin failed then when rebooting I got a software error message
orlans21 said:
I did that back in December while on 6.0.1 and odin failed then when rebooting I got a software error message
Click to expand...
Click to collapse
Well, I downgraded from 7.0 to 6.0 but with twrp, so maybe it's not possible via odin, but I flashed many times nougat via odin, from april to february security patch, it always worked..
MS420 said:
Well, I downgraded from 7.0 to 6.0 but with twrp, so maybe it's not possible via odin, but I flashed many times nougat via odin, from april to february security patch, it always worked..
Click to expand...
Click to collapse
So then it's possible. As long as Samsung didn't update the bootloader between March and August then I should be good. Did you include BL in Odin when you downgraded to an earlier security patch?
orlans21 said:
So then it's possible. As long as Samsung didn't update the bootloader between March and August then I should be good. Did you include BL in Odin when you downgraded to an earlier security patch?
Click to expand...
Click to collapse
Yes.
MS420 said:
Yes.
Click to expand...
Click to collapse
Then they haven't updated it so far. When I wanted to go from 6.0.1 November security patch back to February security patch it failed and the phone went into a softbrick
orlans21 said:
Then they haven't updated it so far. When I wanted to go from 6.0.1 November security patch back to February security patch it failed and the phone went into a softbrick
Click to expand...
Click to collapse
Well, if you have custom recovery, you can downgrade to 6.0.1 very easy..
MS420 said:
Well, if you have custom recovery, you can downgrade to 6.0.1 very easy..
Click to expand...
Click to collapse
I've chosen not to root this phone so I just have stock recovery
Hi guys,
I have received an OTA update for android nougat. I was rooted and have xposed framework. So I have flashed stock firmware so that system status is changed to Official. I have received OTA updates after flashing till January 2017 security patch. After this update, even if i manually check for update, it just says "Your device's software is up to date".
Not able to get OTA for nougat when everyone else in India are receiving it. I received update for the same device when I had root and Xposed. Please help. Currently I'm on stock firmware without root & xposed.
Update:
Received the OTA update again. sharing the link here. Just extracted it from /data partition. Its unmodified.
Nougat OTA Link: https://drive.google.com/file/d/0B6DJKZBTXr7MNGlmUmtmLVJ4aUk/view?usp=sharing
same issue with me, I received update of security patch 1 january 2017, now it says up to date, installed stock in last week. anyone help :__:
May be we'll get it in a couple of days!
Sudarshan Q700S said:
same issue with me, I received update of security patch 1 january 2017, now it says up to date, installed stock in last week. anyone help :__:
Click to expand...
Click to collapse
I think Motorola is restricting a device to download the update more than once for now, as everyone are trying to get the update. Let me know if you get the update again. Will do the same if I get it.
Lord of Hell said:
I think Motorola is restricting a device to download the update more than once for now, as everyone are trying to get the update. Let me know if you get the update again. Will do the same if I get it.
Click to expand...
Click to collapse
I havent downloaded it once even. I still don't get the update. Complete stock since purchase. No modding done
swaggy123 said:
I havent downloaded it once even. I still don't get the update. Complete stock since purchase. No modding done
Click to expand...
Click to collapse
I have downloaded it once, but not able to find it in the cache partition. Then flashed stock firmware and no more update notification for Nougat. Even I'm wondering what really is happening.
Maybe Motorola might be pushing the update randomly. I see that many others are reporting the same issue at XDA. I hope we would get the update in a couple of days.
Lord of Hell said:
I think Motorola is restricting a device to download the update more than once for now, as everyone are trying to get the update. Let me know if you get the update again. Will do the same if I get it.
Click to expand...
Click to collapse
Sure I'll tell you if i got it
Can you got update notification
Yes, I did get an update notification
nitingarje24 said:
Can you got update notification
Click to expand...
Click to collapse
I have downloaded it and its around 764MB. I have flashed the stock firmware and tried to update it, but my device got updates till Jan 2017 security patch only, nougat update didn't appear second time! Still waiting for the update
Lord of Hell said:
I have downloaded it and its around 764MB. I have flashed the stock firmware and tried to update it, but my device got updates till Jan 2017 security patch only, nougat update didn't appear second time! Still waiting for the update
Click to expand...
Click to collapse
Hey,
I did the same. I used RR ROM almost a month than re-flashed the stock one.
I got the 7.1.1.
What is the build number?
when you got 7.1.1
[email protected] said:
Hey,
I did the same. I used RR ROM almost a month than re-flashed the stock one.
I got the 7.1.1.
What is the build number?
Click to expand...
Click to collapse
These are the current stock ROM details.
Lord of Hell said:
These are the current stock ROM details.
Click to expand...
Click to collapse
Seems you are using the right version of marshmallow.
What i did was:-
1. Downloaded the ROM from https://github.com/motoxplay/stock. Indian version 5.1.1 (XT1562).
2. Flashed it.
3. Now the ROM was automatically updated to 6.0.1 then 7.1.1.
Just try to download and flash the ROM from here. https://github.com/motoxplay/stock
after flashing 5.1.1 it said device up to date.not working now its Lollipop.
tell me when you got nougat update because after 4 oct 2017 didn't get notification of ota
Tried it few days back, didn't work!
[email protected] said:
Seems you are using the right version of marshmallow.
What i did was:-
1. Downloaded the ROM from https://github.com/motoxplay/stock. Indian version 5.1.1 (XT1562).
2. Flashed it.
3. Now the ROM was automatically updated to 6.0.1 then 7.1.1.
Just try to download and flash the ROM from here. https://github.com/motoxplay/stock
Click to expand...
Click to collapse
I have already tried this method. Flashed Indian Official Lollipop firmware and it received OTA updates till Jan 2017 security patch. No more update after that! When did you receive the notification?
I think Motorola has rolled back the OTA due to battery drain and other issues few people reported. Fingers crossed!
when you got nougat update please provide date if you remember
4th Oct
nitingarje24 said:
when you got nougat update please provide date if you remember
Click to expand...
Click to collapse
I got the update on 4th Oct. Tried it again on 5th, it disappeared!
When did you get the update?
Lord of Hell said:
I have already tried this method. Flashed Indian Official Lollipop firmware and it received OTA updates till Jan 2017 security patch. No more update after that! When did you receive the notification?
I think Motorola has rolled back the OTA due to battery drain and other issues few people reported. Fingers crossed!
Click to expand...
Click to collapse
May be they rolled back the update due to issues.
I got the update on 3rd October 2017.
I don't have any issues but yes Nougat battery is not as much effective than MM.
But its not draining like other people reporting.
---------- Post added at 08:19 AM ---------- Previous post was at 08:15 AM ----------
nitingarje24 said:
after flashing 5.1.1 it said device up to date.not working now its Lollipop.
tell me when you got nougat update because after 4 oct 2017 didn't get notification of ota
Click to expand...
Click to collapse
Kindly select based on region.
Updates will come based on combination of country & IEMI number.
If you are not from India and flashed the Indian version then it don't update further.
So make sure while flashing the ROM.
After flash check, should have stock recovery and ROM than only you will get the same.
Guys! I have received the OTA update today again. Not sure where to capture the OTA. Last time I didn't find it in Cache partition. This time I was able to pull the OTA zip file from data partition. Will upload it this evening if anyone wants the OTA zip file.
yes
thanks
Hi, thanks for reading. My S8+ G955F stopped finding updates after 2018 July's security patch, when I try to search for updates manually it says that the device is up to date already (its 2019 April's 20th today).
I never flashed a custom ROM, it's 100% stock and Knox is intact.
I wonder if there is a way to just update with Samsung official tooling or just flash with TWRP the OneUI Pie official ROM without having to go through every update to date manually (there must be dozens of them).
I attached my current build and firmware below.
Thanks for reading and have a great day.
xRaevyn said:
Hi, thanks for reading. My S8+ G955F stopped finding updates after 2018 July's security patch, when I try to search for updates manually it says that the device is up to date already (its 2019 April's 20th today).
I never flashed a custom ROM, it's 100% stock and Knox is intact.
I wonder if there is a way to just update with Samsung official tooling or just flash with TWRP the OneUI Pie official ROM without having to go through every update to date manually (there must be dozens of them).
I attached my current build and firmware below.
Thanks for reading and have a great day.
Click to expand...
Click to collapse
You could try first Samsung's Smart Switch to see if that will update your phone.
If not the other way would be to download your firmware and flash with Odin.
spawnlives said:
You could try first Samsung's Smart Switch to see if that will update your phone.
If not the other way would be to download your firmware and flash with Odin.
Click to expand...
Click to collapse
having the same issue . do you need to go update by update if you decide to install by odin? or can you just pick the last version and install it?
zoiden said:
having the same issue . do you need to go update by update if you decide to install by odin? or can you just pick the last version and install it?
Click to expand...
Click to collapse
No you don't need to do incremental updates
Just update to the version you want