Hey guys,
Not much of a poster but it seems the retus guys are left out in discussions involving flashing our firmware...
I present the official nougat OTA I received for RETUS only. This has the January security patch (vanilla android yet we are still behind security patches...nice Lenovo...).
For those sideloading this and are still on MM, you'll just need to adb sideload the file. Keep in mind that I received my OTA update on a November security patch, so it may not mater at all which patch you have.
RETUS NOUGAT OTA (Mega link)
Preparation:
For those who rooted and caused a bunch of hell on your system partition, you can grab some stock unsigned firmware here and revert what you did. Fastboot flash the boot, sparsechunks (in order), recovery, and oem images (then reboot back to bootloader to choose recovery mode). You can now finally sideload it flawlessly without losing any data. If you need more information you can check out one the revert to stock firmware guides, I'm not going to post something repetitive.
Root options:
You want root? You have two options...first you obviously need TWRP.
flash a custom ROM
flash this gentleman's (tomparr) custom kernel over on his thread and then flash superSU or Magisk. You can flash both SuperSU and Magisk but you could also just flash Magisk which comes with it's own systemless root.
Revert?
You can reflash MM images but I suggest using something more autonomous like this flashing tool by core720 since there's a lot more commands involved to officially downgrade. There's also an edit of the downgrade bat script in the comments of the thread which I suggest to use instead.
Viper4Android!? Atmos!?
There are currently magisk modules that work (both arise and independent ones).
I am also on the Nov. security and got the notice today of the update being available and twice after what I believe it to be successful it boots back up and tells me there was an error and nothing was updated. So thanks I guess I have no choice but to try to side-load this. Would love to know why it failed to update after being downloaded though.
I am on July security patch and just got the prompt so don't think patch level matters
xantanion said:
I am on July security patch and just got the prompt so don't think patch level matters
Click to expand...
Click to collapse
Please let me know if yours updates, mine has failed four times today already.
Jimi Mack said:
Please let me know if yours updates, mine has failed four times today already.
Click to expand...
Click to collapse
Mine went flawlessly
Jimi Mack said:
I am also on the Nov. security and got the notice today of the update being available and twice after what I believe it to be successful it boots back up and tells me there was an error and nothing was updated. So thanks I guess I have no choice but to try to side-load this. Would love to know why it failed to update after being downloaded though.
Click to expand...
Click to collapse
Jimi Mack said:
Please let me know if yours updates, mine has failed four times today already.
Click to expand...
Click to collapse
I'm not sure where you're coming from, have you ever altered your system partition? If you sideload through recovery, you would be able to see the recovery log and see the error it shows each time rather than having the OTA handled through the OTA client.
DroneDoom said:
I'm not sure where you're coming from, have you ever altered your system partition? If you sideload through recovery, you would be able to see the recovery log and see the error it shows each time rather than having the OTA handled through the OTA client.
Click to expand...
Click to collapse
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
xantanion said:
Mine went flawlessly
Click to expand...
Click to collapse
You installed this downloaded OTA or did you get yours OTA? Thanks.
Jimi Mack said:
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
You installed this downloaded OTA or did you get yours OTA? Thanks.
Click to expand...
Click to collapse
Got my OTA today and had no issues. Just got the phone brand new yesterday as well
Jimi Mack said:
Tried booting into Recovery to see such logs, all I get is "No Command." I picked this phone up 2nd hand, I am going to assume system partition was altered as the unit was already unlocked but showing to be stock. I am best at this point maybe just installing TWRP and working with what roms are available.
---------- Post added at 07:12 PM ---------- Previous post was at 07:10 PM ----------
You installed this downloaded OTA or did you get yours OTA? Thanks.
Click to expand...
Click to collapse
To unlock the stock recovery menu, bring up that 'no command' instance again and hold the power button and double tap the vol+ while still holding the power button. It's tricky, you may need to press them both at once or just play around with it until you see the menu.
DroneDoom said:
To unlock the stock recovery menu, bring up that 'no command' instance again and hold the power button and double tap the vol+ while still holding the power button. It's tricky, you may need to press them both at once or just play around with it until you see the menu.
Click to expand...
Click to collapse
Thanks, I was able to get into it, but the sad part is I have no idea on what I am looking at, that might as well been a foreign language...lol. I saw several error logs, but as I said, no idea on what I was looking at. I did not know what to expect but was kind of hoping for a red lag or something that said "hey schmuck loot at this. "
Jimi Mack said:
Thanks, I was able to get into it, but the sad part is I have no idea on what I am looking at, that might as well been a foreign language...lol. I saw several error logs, but as I said, no idea on what I was looking at. I did not know what to expect but was kind of hoping for a red lag or something that said "hey schmuck loot at this. "
Click to expand...
Click to collapse
If you invested in some Z mods and want them working (battery packs work but there's no software indication of charge or anything) you may have to flash some stock images to get everything sorted out. If you don't care then by all means you can use a custom nougat rom, the MM modem and radios still work even on a nougat rom.
DroneDoom said:
If you invested in some Z mods and want them working (battery packs work but there's no software indication of charge or anything) you may have to flash some stock images to get everything sorted out. If you don't care then by all means you can use a custom nougat rom, the MM modem and radios still work even on a nougat rom.
Click to expand...
Click to collapse
Hopefully at sometime there is a stock N rom I can flash from TWRP on a MM base.
Or I can try side loading yours and hope that works.
Question: What is the differences in the two "unsigned firmware" in the 1st post?
Just got the update when I checked manually (Consumer Cellular RETUS Unlocked)
First impression: What an... interesting boot animation.
Jimi Mack said:
Hopefully at sometime there is a stock N rom I can flash from TWRP on a MM base.
Or I can try side loading yours and hope that works.
Question: What is the differences in the two "unsigned firmware" in the 1st post?
Click to expand...
Click to collapse
I think there may be a difference in security patches but they have the same build number so I'm not too sure.
holabola said:
Just got the update when I checked manually (Consumer Cellular RETUS Unlocked)
First impression: What an... interesting boot animation.
Click to expand...
Click to collapse
Yeah it is, it reminds me of the days when I had a Motorola razr lol.
For anyone that was wondering, the display size scaling works PERFECTLY.
I originally changed the DPI to make everything smaller, but it led to a lot of random issues with other apps (mainly involving the camera). The display size scaling mimics the effects of a DPI change right out of the box without all the issues and need for a computer (I wasn't rooted so)
Also, when I got the update, I was on the December 1st security patch.
DroneDoom said:
This has the January security patch (vanilla android yet we are still behind security patches...nice Lenovo...).
Click to expand...
Click to collapse
Yeah motoblur might look like stock android, but it is very different under the hood. This is also the first 32-bit nougat phone in existence, and certainly the first nougat phone on the snapdragon 625. This phone is also unique in that it has to work with all of the Moto mods (none of the aosp Roms in the "ROMs" section work with Moto mods, so this probably wasn't trivial to add). For such a unique phone, we got updated pretty quickly. We got nougat before the Axon 7 (advertised as "daydream compatible" for +6 months before updated to 7.0) and plenty of other phones. It's not a nexus or a Oneplus, but Moto did good considering this isn't a flagship (although to most of us, it is).
DroneDoom said:
Magisk
Click to expand...
Click to collapse
Just want to be clear, Magisk v11 will brick on nougat. V12 works perfectly. I've got a whole thread dedicated to Magisk on nougat and was finally able to pass safetynet using s3v3n's 3.0.1 build and the latest v12 Magisk. Did not flash supersu or ARISE.
xxBrun0xx said:
Yeah motoblur might look like stock android, but it is very different under the hood. This is also the first 32-bit nougat phone in existence, and certainly the first nougat phone on the snapdragon 625. This phone is also unique in that it has to work with all of the Moto mods (none of the aosp Roms in the "ROMs" section work with Moto mods, so this probably wasn't trivial to add). For such a unique phone, we got updated pretty quickly. We got nougat before the Axon 7 (advertised as "daydream compatible" for +6 months before updated to 7.0) and plenty of other phones. It's not a nexus or a Oneplus, but Moto did good considering this isn't a flagship (although to most of us, it is).
Just want to be clear, Magisk v11 will brick on nougat. V12 works perfectly. I've got a whole thread dedicated to Magisk on nougat and was finally able to pass safetynet using s3v3n's 3.0.1 build and the latest v12 Magisk. Did not flash supersu or ARISE.
Click to expand...
Click to collapse
Thanks for the feedback (fixed op), I noticed v11 doesn't patch the kernel correctly and the ROM tries to boot without it. I thought it was just me since I was playing around trying to change my cache partition to f2fs but I guess the kernel doesn't support that filesystem for cache (ROM boots but doesn't initialize).
S3v3n's ROM is based on firmware stock right? I tried magisk with V4A module but it doesn't work and Atmos somehow bricks stock but it doesn't brick on a ROM built from different source (works on xperience). I noticed today that the ARISE project has a magisk module for it's latest project so maybe there's a possibility for stock to have systemless V4A.
Question, when I am in Stock Recovery to side load the update, I ma getting this.. anyone know what Status 225 is?
Now send package you want to apply
to the device with "adb sideload ,filename>...
status 255
Installation aborted.
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
I think I may have found the issue, in Stock Recovery, is says :motorola/addison-retail/addison
but under ABOUT PHONE on the phone it states this is on a retus channel. Conflict of information, any suggestions?
Jimi Mack said:
Question, when I am in Stock Recovery to side load the update, I ma getting this.. anyone know what Status 225 is?
Now send package you want to apply
to the device with "adb sideload ,filename>...
status 255
Installation aborted.
---------- Post added at 01:05 PM ---------- Previous post was at 01:01 PM ----------
I think I may have found the issue, in Stock Recovery, is says :motorola/addison-retail/addison
but under ABOUT PHONE on the phone it states this is on a retus channel. Conflict of information, any suggestions?
Click to expand...
Click to collapse
Addison is our phone model's codename. For instance the Moto z variants are codenamed "griffin." They each have individual builds based on a region's network range and so they are codename as well...We are RETUS (retail US) which is the channel that we get our updates from so that each device will get specifically tuned update based on the region it represents. Reteu (Europe), retbr (Brazil) etc.
As for your 255 error, there is no specific documentation about this. It may be some incompatibility error or a failed sideload based on the same error # given in TWRP and CM recoveries.
DroneDoom said:
Addison is our phone model's codename. For instance the Moto z variants are codenamed "griffin." They each have individual builds based on a region's network range and so they are codename as well...We are RETUS (retail US) which is the channel that we get our updates from so that each device will get specifically tuned update based on the region it represents. Reteu (Europe), retbr (Brazil) etc.
As for your 255 error, there is no specific documentation about this. It may be some incompatibility error or a failed sideload based on the same error # given in TWRP and CM recoveries.
Click to expand...
Click to collapse
I thank you. I got the update to begin to load, it fails and aborts at 45% . It states something about content, lists my build number and give a code 755. I can not find out anything about this one either. I guess something is screwy with what is installed on my phone and what should be...
Related
Purpose of this thread:
This thread is about changes within factory images of newly released Android updates in comparison with the previously released Android update.
Latest Android version 8.1.0 (Oreo): OPM7.181205.001
This December update is most likely gonna be the last official security update from Google for the Nexus 5X (source: https://support.google.com/nexus/answer/4457705?hl=en)
Download-Link: https://dl.google.com/dl/android/aosp/bullhead-opm7.181205.001-factory-5f189d84.zip MD5: 05DEE954B6FD17B6B301A4D1C90B1B5EChangelog: https://source.android.com/security/bulletin/pixel/2018-12-01 Unchanged:
bootloader bhz32c
radio 2.6.42.5.03
Changed: (md5sum in brackets)
boot (438936FDD50D2C8D3FA8D7586624D670)
recovery (E55D287CBCF78DACEC618E538CE74014)
system (9DD438116FB86EDBF89876A728CC0AA8)
vendor (97C79E83F00AD006D77DA9C570A71BD7)
How to install it on rooted devices with custom recovery installed? Flashfire?
Δημοσιεύτηκε από Google Nexus 5X με Android 7.0 Nougat μέσω Tapatalk.
AFK269 said:
How to install it on rooted devices with custom recovery installed? Flashfire?
Δημοσιεύτηκε από Google Nexus 5X με Android 7.0 Nougat μέσω Tapatalk.
Click to expand...
Click to collapse
That has worked before. Still should work, I have not tried it though.
Sent from my Nexus 5X using Tapatalk
---------- Post added at 02:40 AM ---------- Previous post was at 02:39 AM ----------
Any idea what changes to the system?
Sent from my Nexus 5X using Tapatalk
Smoosh1 said:
userdata.img is the same (MD5: 808444c5b0a4cbfa1f2cbf38b6629b67)
cache.img is the same (MD5: 9aedd15ebf6bc07a38de5bcd705f516a)
Click to expand...
Click to collapse
I think you'll find userdata and cache won't change throughout the lifecycle of nougat. Through something like 14 MM updates they never changed (same MD5) until Nougat came (where they did change) and then through 2 releases they haven't changed.
AFK269 said:
How to install it on rooted devices with custom recovery installed? Flashfire?
Click to expand...
Click to collapse
I would recommend you follow Heisenberg's guide, section 9 "How To Update To A New Build Of The Stock ROM"
sfhub said:
I think you'll find userdata and cache won't change throughout the lifecycle of nougat. Through something like 14 MM updates they never changed (same MD5) until Nougat came (where they did change) and then through 2 releases they haven't changed.
Click to expand...
Click to collapse
You are right, they most likely won't change throughout the lifecycle of nougat. I just mentioned them for the sake of completeness.
Comparison of Android Updates
Do It A Your Own Risk. I am not responsible if you make a mistake.
I found this method on the Internet and I applied it to my phone right now:
(WITH THIS METHOD YOU WILL NOT LOSE ROOT, CUSTOM RECOVERY)
1.Download the ZIP.
2.Download FlashFire.
3.Open flashfire and accept for root access etc etc...
4.click "+" button and click to "flash firmware package" and find the ZIP.
5.Wait for a couple o seconds or 2mins, and then uncheck the "Recovery" (if you don't want to lose the custom recovery) and "Data" (maybe on your device will be already unchecked so keep it unchecked if you don't want to lose your data) and then I clicked the "ν" button.
6.Click "Flash". Your screen will be black for a minute and then you will see a progress bar at the bottom of your screen and log of FlashFire what installs on your device.
7.When it finish flashing, your device will be automatically reboot.
8.Wait a couple of minutes (approximately 3-6 mins).
9.Your device is running the latest Android Version with the latest Security patches and you have also root back....
Sent from my iPad using Tapatalk
AFK269 said:
I found this method on the Internet and I applied it to my phone right now
Click to expand...
Click to collapse
Strange that you didn't include a reference to where you got it on the Internet. Many times, they provide more detail than just the steps and took time create the content and test the procedure.
krelvinaz said:
Strange that you didn't include a reference to where you got it on the Internet. Many times, they provide more detail than just the steps and took time create the content and test the procedure.
Click to expand...
Click to collapse
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
Sent from my iPad using Tapatalk
AFK69 shared the typical img flashing instructions for FlashFire. I've been using it on my rooted devices for months. No issues.
Sent from my Nexus 9 using Tapatalk
Android November update NRD91N released
New Android security update NRD91N got released today.
What has changed? -> See updated OP
I'm sorry, but HERE the last one is still NPF10C, it's a different branch or I'm missing something?
EDIT: nevermind i'm dumb, the post is about the official factory image, mine is about devoloepr preview
AFK269 said:
http://nexus5.wonderhowto.com/how-t...thout-losing-root-no-computer-needed-0168428/
Click to expand...
Click to collapse
Only problem with FlashFire is CF himself says not to flash a bootloader or radios so when there a change there you either have to make a twrp flashable or use fastboot to get atw updated.. Has anyone used FF to flash bootloader? I'm curious....
Sent from my Nexus 5X using XDA Labs
SM210 said:
Only problem with FlashFire is CF himself says not to flash a bootloader or radios so when there a change there you either have to make a twrp flashable or use fastboot to get atw updated.. Has anyone used FF to flash bootloader? I'm curious....
Click to expand...
Click to collapse
Me too!! (Curious)
Sent from my Nexus 5X using XDA Labs
My build number changed to N5D91L after the November update, not NRD91N. How come?
In the past there were some different builds for different countries with a different radio.img. So where do you come from?
I live in the UK.
Edit: And my radio is still 2.6.33.2.14.
Hm...I've only found a lot of japanese sites (f.e. Y!Mobile (is that yahoo?) if I search for this build. Don't know if there is a coherence.
N5D91L is 7.0.0_r21 while NRD91N is 7.0.0_r15. Probably a quick hotfix on the unfixed dirtycow exploit + other fixes . Too lazy to check the real changes on git.
Since some of us is still waiting for the ota by phases and by the time we are getting it, google already roll out N5D91L. Thus the mysterious build update emerged. The others on NRD91N will get it or probably not, until December.
ThorSchwar said:
Hm...I've only found a lot of japanese sites (f.e. Y!Mobile (is that yahoo?) if I search for this build. Don't know if there is a coherence.
Click to expand...
Click to collapse
Nevermind, apparently it's a regular build - see: http://forum.xda-developers.com/nexus-5x/help/n5d91l-strange-android-build-t3500378
November OTA patch has new tag:
Just captured this from my 5X.
Source: google/bullhead/bullhead:7.0/NBD90W/3239497:user/release-keys
Target: google/bullhead/bullhead:7.0/N5D91L/3425233:user/release-keys
https://android.googleapis.com/packa...a1f18978ec.zip
So looks like the new build is not NRD91N but N5D91L.
OTA's and factory images have been posted for November security updare.
https://developers.google.com/android/ota
Three versions:
NDE63U Europe
NDE63V US, except Verizon
NDE63X Verizon
With the BIG warning on the page about be sure to backup all your Photos and Personal data before applying the Update, does this means that it will delete all your data for just applying an OTA update? I understand that for applying the Full Factory images but does it really wipes the data applying just the OTA updates?
Sorry, but this being my first Nexus/Google phone what I know for OTA updates was just a simple process that doesn't delete anything on the phone, and I just want to be sure how it is here before I proceed, thanks in advance.
erasat said:
With the BIG warning on the page about be sure to backup all your Photos and Personal data before applying the Update, does this means that it will delete all your data for just applying an OTA update? I understand that for applying the Full Factory images but does it really wipes the data applying just the OTA updates?
Sorry, but this being my first Nexus/Google phone what I know for OTA updates was just a simple process that doesn't delete anything on the phone, and I just want to be sure how it is here before I proceed, thanks in advance.
Click to expand...
Click to collapse
Best to back up your data, just to be safe. But I personally sideloaded "U" without any issue. Nothing lost.
cam30era said:
Best to back up your data, just to be safe. But I personally sideloaded "U" without any issue. Nothing lost.
Click to expand...
Click to collapse
Yeah, I understand the risks when updating anything so I always do a backup of the most important stuff just in case, but as you know it's not the same to have to do a Full backup/restore. I needed to be sure but if you did it and you are fine then with what I already have backed up I should be fine too, thanks.
I just restored to stock my L and then checked for updates before rooting.
It said I'm already up to date.
I'll try again in a little while before rooting.
But simply being "unlocked" might be what is preventing me from grabbing an update. Not sure.
CZ Eddie said:
I just restored to stock my L and then checked for updates before rooting.
It said I'm already up to date.
I'll try again in a little while before rooting.
But simply being "unlocked" might be what is preventing me from grabbing an update. Not sure.
Click to expand...
Click to collapse
You can download the update(s) from the Google dev site and adb sideload of fastboot flash the factory image (if your bootloader is unlocked). No need to wait for the OTA, if you don't want to...
Whats the difference between builds NDE63U, NDE63V and NDE63X?
Got a vzw pixel that BL unlocked. Safe to flash the 63X? I saw @jcase said vzw would not do an OTA that relocked your BL. Just wondering if anyone else flashed the 63X build.
armandocorti said:
Whats the difference between builds NDE63U, NDE63V and NDE63X?
Click to expand...
Click to collapse
U-> 11/1 sec patch
V-> 11/5 sec patch
X-> 11/6 sec patch
cam30era said:
U-> 11/1 sec patch
V-> 11/5 sec patch
X-> 11/6 sec patch
Click to expand...
Click to collapse
Not arguing, but how do you know this.
The previous three builds were all the for different phones.
It's natural to expect the new three builds (all dropped on the same day) are for three different phones, USA, Verizon and *something else*.
CZ Eddie said:
Not arguing, but how do you know this.
The previous three builds were all the for different phones.
It's natural to expect the new three builds (all dropped on the same day) are for three different phones, USA, Verizon and *something else*.
Click to expand...
Click to collapse
http://source.android.com/security/bulletin/2016-11-01.html
Was going to flash the factory image system but it looks like the process has changed.... More files and slot a and b.
Anyone know the proper way to manually flash the system.img?
cam30era said:
You can download the update(s) from the Google dev site and adb sideload of fastboot flash the factory image (if your bootloader is unlocked). No need to wait for the OTA, if you don't want to...
Click to expand...
Click to collapse
Yes, I realize I can typically install my own updates.
But as of right now, nobody truthfully knows which phone should have which build. P is so far looking Verizon Only.
Nobody I know of on Verizon has the H or L images.
So I'd rather be safe than sorry and let my phone CHOOSE it's update, and it did not so I mentioned that here to prevent others from restoring to stock and trying for an OTA
Anyways, it's just a payload.bin file. Not the same android image as the older files. I'm actually not sure how to install a payload.bin.
---------- Post added at 12:48 PM ---------- Previous post was at 12:46 PM ----------
cam30era said:
http://source.android.com/security/bulletin/2016-11-01.html
Click to expand...
Click to collapse
Yeah, I get that there are security patches.
But what I'm asking you is to tell us how you know those security patches correspond with the different builds.
I skimmed the page but didn't notice anything saying one way or the other.
CZ Eddie said:
Yes, I realize I can typically install my own updates.
But as of right now, nobody truthfully knows which phone should have which build. P is so far looking Verizon Only.
Nobody I know of on Verizon has the H or L images.
So I'd rather be safe than sorry and let my phone CHOOSE it's update, and it did not so I mentioned that here to prevent others from restoring to stock and trying for an OTA
Anyways, it's just a payload.bin file. Not the same android image as the older files. I'm actually not sure how to install a payload.bin.
Click to expand...
Click to collapse
My vzw pixel shipped with 63H.
jaxenroth said:
My vzw pixel shipped with 63H.
Click to expand...
Click to collapse
Then you're the only person on the board so far who has an H build on Verizon:
http://forum.xda-developers.com/pixel-xl/help/build-pixel-t3489990/page2
Could you please post in that thread to let others know?
I wonder if you got a non-Verizon phone.
CZ Eddie said:
[/COLOR]
Yeah, I get that there are security patches.
But what I'm asking you is to tell us how you know those security patches correspond with the different builds.
I skimmed the page but didn't notice anything saying one way or the other.
Click to expand...
Click to collapse
Valid question. @jcase has clearly stated that "X" would prevent VZW bootloader unlock. Regarding U and V, and which is 11/1 and which is 11/5, I don't know for sure. But it's clear from the Google dev link that each of the 3 builds include an incremental increase in patches.
"clearly stated that "X" would prevent VZW bootloader unlock."
Those durty basturds.
And that's why I didn't get a VZW phone.
<<----- VZW hater gets to hate on VZW yet again. :laugh:
JustusIV said:
Was going to flash the factory image system but it looks like the process has changed.... More files and slot a and b.
Anyone know the proper way to manually flash the system.img?
Click to expand...
Click to collapse
I guess i will do an adb sideload of the OTA.
I have never done it this way, but it looks like others have done this, and the boot-to-root still works.
with the newest radio being in the v .. i would speculate that its u world v north america and x verizon
corrected radio
Sent from my marlin using XDA Labs
CZ Eddie said:
Not arguing, but how do you know this.
The previous three builds were all the for different phones.
It's natural to expect the new three builds (all dropped on the same day) are for three different phones, USA, Verizon and *something else*.
Click to expand...
Click to collapse
"The previous U and V versions were a few days older and are simply there for legacy reasons."
Source > http://www.androidcentral.com/google-posts-latest-pixel-images-november-security-patch
I thought everyone would like to know that amazingly BLU has released a New software update for the BLU R1-HD tonight...
Update Information:
Version number: BLU_R0010UU_V8.3_GENERIC_6.0_20170414-2043
Version size: 333.47 MB
Release date: 2017-05-01
A new software update is available for your R1 HD!
This software update includes the Android Security Updates and several improvements including VoLTE for T-Mobile.
download link
ulises.rodriguez said:
I thought everyone would like to know that amazingly BLU has released a New software update for the BLU R1-HD tonight...
Update Information:
Version number: BLU_R0010UU_V8.3_GENERIC_6.0_20170414-2043
Version size: 333.47 MB
Release date: 2017-05-01
A new software update is available for your R1 HD!
This software update includes the Android Security Updates and several improvements including VoLTE for T-Mobile.
Click to expand...
Click to collapse
BLU_R0010UU_V8.3
drive.google.com/file/d/0B4hDCcrfeDwXQ21lQmIyNXlqOWs/view
Are you running the Prime firmware?
Could you share with us the patch level date?
I'm running OEM firmware, haven't seen any new updates arrive.
liviu_anc said:
BLU_R0010UU_V8.3
drive.google.com/file/d/0B4hDCcrfeDwXQ21lQmIyNXlqOWs/view
Click to expand...
Click to collapse
thank you. your link is no a link though. here i will make it a link.
i edited your quote section.
and copied here too so make it easier to find.
==>FULL-UNMOFIFIED-7.42-to-8.3_update
i will try to upload a copy without the preloader and u-boot.img's when i test it out
Modified _without being locked down version
==>Link
mblokker said:
Are you running the Prime firmware?
Could you share with us the patch level date?
I'm running OEM firmware, haven't seen any new updates arrive.
Click to expand...
Click to collapse
I am running the Prime firmware.
Android Security Patch Level date is:
April 5, 2017
.....
mrmazak said:
thank you. your link is no a link though. here i will make it a link.
i edited your quote section.
Click to expand...
Click to collapse
I'm new on xda and first 10 post I cannot post Link's
---------- Post added at 12:03 PM ---------- Previous post was at 11:59 AM ----------
I have a question I'm running a rooted room based on the official Amazon prime room and have TWRP recovery installed how can I make an update script from this to use it on TWRP recovery ?
ulises.rodriguez said:
I am running the Prime firmware.
Android Security Patch Level date is:
April 5, 2017
.....
Click to expand...
Click to collapse
One would then assume that the dirty-cow method will no longer work. It was supposed to have been patched as early as Nov security patch, so I guess new updates to V8 will have no root yet.
Maybe Chainfire's FlashFire could help? Search for eu.chainfire.flash in the Google Play Store.
***EDIT***
Sorry for the double redirect, but my original post was a rom and should be kept in the rom section
==>Link to ROM Thread
mrmazak said:
One would then assume that the dirty-cow method will no longer work. It was supposed to have been patched as early as Nov security patch, so I guess new updates to V8 will have no root yet.
Click to expand...
Click to collapse
Did we lose root access with any security updates pass November 2016?
Three apps I've noticed uninstalled and now incompatible: google+, goggles, and wolphram alpha. Can't see what the problem is. Any ideas?
sirrelevant said:
Three apps I've noticed uninstalled and now incompatible: google+, goggles, and wolphram alpha. Can't see what the problem is. Any ideas?
Click to expand...
Click to collapse
No idea, myself. Is that on the official or modified update?
mrmazak said:
No idea, myself. Is that on the official or modified update?
Click to expand...
Click to collapse
Official OTA. Phone's all stock.
Is there way to do install this new firmware 8.3 unmodified as sent from manufacturer thru OTA if my phone is already modified? Is Wireless Update app safe to do upgrade to 8.3?
Few month ago I used Dirty Cow on 6.6 to root and unlock bootloader, I then installed TWRP and from TWRP I installed modified 7.4.2 from vampireinfo thread, the one without preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img and without Amazon apps and adds.
Seeing this device is no longer supported I would like to revert to factory ROM to have up to date and working phone. I don care about SuperSu or rooted phone, this is useless.
ivarme said:
Is there way to do install this new firmware 8.3 unmodified as sent from manufacturer thru OTA if my phone is already modified? Is Wireless Update app safe to do upgrade to 8.3?
Few month ago I used Dirty Cow on 6.6 to root and unlock bootloader, I then installed TWRP and from TWRP I installed modified 7.4.2 from vampireinfo thread, the one without preloader_p6601.bin, lk.bin, logo.bin, secro.img, trustzone.bin, uboot.img and without Amazon apps and adds.
Seeing this device is no longer supported I would like to revert to factory ROM to have up to date and working phone. I don care about SuperSu or rooted phone, this is useless.
Click to expand...
Click to collapse
The only way to go back unmodified is to go back to locked bootloader, stock recovery, and stock rom first. It's an unchangeable path. Because going that way will change the preloader(take away sp flash tool as a means of unbricking)
And then if the update goes "side ways" could be a problem.
But possible if you want to.
Outline of what's needed- not realy a step by step tutorial.
1. Make sure sp flash tool is working.
If not working because of previous update, need to go forward in order to go back.
What I mean is, more modification ,by rolling back preloader.
2. Flash an oob (out of box) backup
3. Take official updates, and hope things do not brick.
OR
Wait a day or two, and the update will be made available to be flashed in twrp.
I have already made the system update work in v17, flashed in twrp, next will be test out the boot.img update, then change it from a patch update into a rom.
Your choice.
**UPDATE**
Full rom install complete
==>Link to post with modified V8
ulises.rodriguez said:
I am running the Prime firmware.
Android Security Patch Level date is:
April 5, 2017
.....
Click to expand...
Click to collapse
It's been updated to April 2017, that's good.
Sent from my Life Max using Tapatalk
Tracerlx said:
Did we lose root access with any security updates pass November 2016?
Click to expand...
Click to collapse
I don't think we lost root , it you have it already. But it you don't Already have root the security update pass the November date you loose the dirty-cow exploit. And without that the way we unlock bootloader is lost. And you need to be able to do that , to install recovery, etc, etc.
---------- Post added at 06:24 AM ---------- Previous post was at 06:18 AM ----------
liviu_anc said:
BLU_R0010UU_V8.3
drive.google.com/file/d/0B4hDCcrfeDwXQ21lQmIyNXlqOWs/view
Click to expand...
Click to collapse
What version were you on when you downloaded this update?
I need to match up system files in order to apply the patches.
The new files are OK but the updated ones need to be matched up.
mrmazak said:
I don't think we lost root , it you have it already. But it you don't Already have root the security update pass the November date you loose the dirty-cow exploit. And without that the way we unlock bootloader is lost. And you need to be able to do that , to install recovery, etc, etc.
---------- Post added at 06:24 AM ---------- Previous post was at 06:18 AM ----------
What version were you on when you downloaded this update?
I need to match up system files in order to apply the patches.
The new files are OK but the updated ones need to be matched up.
Click to expand...
Click to collapse
I'm on 7.4.2
liviu_anc said:
I'm on 7.4.2
Click to expand...
Click to collapse
What ever version people are on is the only patch that will work for that device you can't mix and match patches cause they simply won't apply.
The patches check the hashes and only applies to apps, and binaries that match.
While you could apply 7.4.2 to V17 only a small part would apply, basically not worth the effort.
Hopefully people using different versions captured their update and uploads it, would be nice to have version from every version that got an update.
vampirefo said:
What ever version people are on is the only patch that will work for that device you can't mix and match patches cause they simply won't apply.
The patches check the hashes and only applies to apps, and binaries that match.
While you could apply 7.4.2 to V17 only a small part would apply, basically not worth the effort.
Hopefully people using different versions captured their update and uploads it, would be nice to have version from every version that got an update.
Click to expand...
Click to collapse
Right.
I had to install v7.4.2 to apply patches. I tried to just apply patches to the boot.img on the ext-sd card (tried following an old apply-patch guide) but had trouble because the sha1 of the boot.img when it was not on the boot partition did not match. (Over my head this morning)
So I have the patch working and booting for 7.4.2 without the preloader change.
I would like to make it a rom.zip instead if a patch. As soon as I know how to do that will upload.
The new update has added this interesting privacy policy to the setup. And by default it is set to allow sharing data with Blu.
Looks to be a minor update, but at least they're still thinking about us
States EMUI version 5.0.1
Android version 7.0
Android security patch level August 5, 2017
So far, the main change I have noticed is the addition of a "Moving Picture" mode to the camera app, which is similar to the Live Photos you would find on iOS.
Also, it seems they have added an automatic video creation "Highlights" feature to the Gallery app, utilizing Quik video editor. Not sure if this was already included in previous versions.
peterchen1999 said:
Looks to be a minor update, but at least they're still thinking about us
States EMUI version 5.0.1
Android version 7.0
Android security patch level August 5, 2017
So far, the main change I have noticed is the addition of a "Moving Picture" mode to the camera app, which is similar to the Live Photos you would find on iOS.
Click to expand...
Click to collapse
Gr8 and battery life?
I guess they mentioned it in updates?
@PalakMi
We don't have to rebrand!!!
Sent from my Honor 8 using XDA Labs
---------- Post added at 05:14 PM ---------- Previous post was at 04:29 PM ----------
peterchen1999 said:
Looks to be a minor update, but at least they're still thinking about us
States EMUI version 5.0.1
Android version 7.0
Android security patch level August 5, 2017
So far, the main change I have noticed is the addition of a "Moving Picture" mode to the camera app, which is similar to the Live Photos you would find on iOS.
Click to expand...
Click to collapse
Can u share a screenshot of ur about page after the update please?
Sent from my Honor 8 using XDA Labs
ayush rao said:
@PalakMi
We don't have to rebrand!!!
Sent from my Honor 8 using XDA Labs
---------- Post added at 05:14 PM ---------- Previous post was at 04:29 PM ----------
Can u share a screenshot of ur about page after the update please?
Click to expand...
Click to collapse
Here you go.
peterchen1999 said:
Here you go.
Click to expand...
Click to collapse
Awesome. I can't wait for the update to reach my device!!!!
Sent from my Honor 8 using XDA Labs
I'm rooted and have TWRP installed. I tried updating and it said "zip failed to install" a few different times. I am curious on what I need to do to update, not necessarily just for this update but for future ones as well. Thanks
cant wait!!!
myphoneishaunted said:
I'm rooted and have TWRP installed. I tried updating and it said "zip failed to install" a few different times. I am curious on what I need to do to update, not necessarily just for this update but for future ones as well. Thanks
Click to expand...
Click to collapse
You need to be on stock and unrooted for the official update process to work.
myphoneishaunted said:
I'm rooted and have TWRP installed. I tried updating and it said "zip failed to install" a few different times. I am curious on what I need to do to update, not necessarily just for this update but for future ones as well. Thanks
Click to expand...
Click to collapse
unroot then do update
PS: My L04 still not get this update
blackbuffalo said:
unroot then do update
PS: My L04 still not get this update
Click to expand...
Click to collapse
Mine too. Might take another 1-2 weeks probably for every device to receive the OTA.
Sent from my Honor 8 using XDA Labs
Anyone with the 64gb version (L14) confirm the update as well? I haven't gotten it with my L14 yet.
mcvanger said:
Anyone with the 64gb version (L14) confirm the update as well? I haven't gotten it with my L14 yet.
Click to expand...
Click to collapse
Even me, an FRD-L04 user, didn't receive it. Once we receive the update u can expect it on ur phone within a week or two. That's what happened in the case of the B385 update.
Sent from my Honor 8 using XDA Labs
Got it last night. Currently using phone on first day of the update.
mcvanger said:
Anyone with the 64gb version (L14) confirm the update as well? I haven't gotten it with my L14 yet.
Click to expand...
Click to collapse
Got it last night on my L14.
dsEVOlve said:
Got it last night on my L14.
Click to expand...
Click to collapse
Thanks! Hopefully I get it soon. Any major changes? Heard there were some apps that were added.
Got this update notification on my FRD-L14 2 days ago and for some reason it keeps failing to install with error "failed to verify update package" i was initially rooted and had Magisk 14.0 installed. But i've reverted to stock recovery and boot image which i flashed using fastboot commands.. Can anyone help with the above or better still piont me in the thread on how to create a TWRP package so i can flash it.
I've even gone as far as flashing system.img from my backup B385 UPDATE.APP but still no luck.
I am using a FRD-L14 and currently on stock EMUI 7.0.
Thanks
nestojean said:
Got this update notification on my FRD-L14 2 days ago and for some reason it keeps failing to install with error "failed to verify update package" i was initially rooted and had Magisk 14.0 installed. But i've reverted to stock recovery and boot image which i flashed using fastboot commands.. Can anyone help with the above or better still piont me in the thread on how to create a TWRP package so i can flash it.
I've even gone as far as flashing system.img from my backup B385 UPDATE.APP but still no luck.
I am using a FRD-L14 and currently on stock EMUI 7.0.
Thanks
Click to expand...
Click to collapse
U have stock recovery and boot right? Flash the recovery and boot image of B385 and then from recovery factory reset ur phone. After that try and see if u can update ur device. Also if u wish to lock ur bootloader then hit download latest full package.
Sent from my Honor 8 using XDA Labs
dsEVOlve said:
Got it last night on my L14.
Click to expand...
Click to collapse
Well I got the phone about a week ago and just activated my new tmo sim card last night to get cell service on it so I'm probably not the best judge of whether any performance changes occurred. Based on the change log I wasn't expecting much though.
FYI I'm still completely stock, locked bootloader for now if that made any difference in the delivery of the update.
ayush rao said:
U have stock recovery and boot right? Flash the recovery and boot image of B385 and then from recovery factory reset ur phone. After that try and see if u can update ur device. Also if u wish to lock ur bootloader then hit download latest full package.
Click to expand...
Click to collapse
Thanks for the explanation. This is the route I had to take. I have FRD-L04. I was on B385 with TWRP and Magisk 14.0. Unrooting and flashing boot.img and recovery.img from 385 did not help to install the new update. I keep getting the same error of Package failed. No matter what I seemed to try nothing worked.
So, this sucks, but, I factory reset. Then RE-locked bootloader. Then, I had to download *latest full package* otherwise I still received same error. But, now I am on B388 and i'm going to try flashing TWRP and installing Magisk now.
Live photos seems interesting. Pretty excited about that.
Question to anyone who got the update, any changes in battery life?
Hello all - the Oreo beta is now officially over for all devices and unofficial beta devices may need to be manually migrated to the release branch:
Note: Your device will receive OTAs after this update.
Note: Please use Updato or SamMobile to acquire the latest firmware for your device if you use AT&T or Verizon, or use XAA for a clean, unlocked experience.
1. Use SamFirm to acquire the latest Oreo build for your device (if not AT&T or Verizon).
Enter SM-G950U/SM-G955U/SM-G955U1 depending on your model.
Enter your desired carrier code, or XAA for unlocked (common are TMO, SPR)
Select Auto, Check CRC32, and Decrypt Automatically.
Click Download
2. Once the download is done, extract the archive.
3. Use the patched Odin 3.13.1 from @realbbb. This is necessary for carrier-switching, including to unlocked/debranded/XAA.
4. It is safe to use HOME_CSC to preserve your data, but if you're switching to an unlocked build or switching carriers, you MUST use CSC (data will wipe).
5. You can also use CSC to wipe your data and get a fresh factory start.
Previous post:
Howdy - here's how to get Oreo!
OLD PROCESS FOR BETA 1-2 IS BELOW - Move on to Beta 4 below!
Credit to @norbarb for the leaked update!
Try at your own risk - this is for the brave
First, read this:
Code:
Since we don't have a flashable CSC for the unlocked firmware, your phone will be branded with whichever SIM you have inserted.
This means your unlocked S8+ will become a TMO S8+, for example. It all depends on the inserted SIM.
This is compatible with G955U/U1 and G950U/U1.
Warning: Back up your data! Your phone will be reset.
Step 1: Be on the AQGL baseband. Skip the below steps if you're already there.
You can do this by downloading your AQGL package and ODIN below. Extract the ZIP, open ODIN, and connect your phone in download mode.
Then, select (from the ZIP you just extracted) BL, AP, CP, and CSC (NOT home csc) in their respective slots. Don't change any other options. Select Start.
After this is done, your device will boot into recovery.
Tip: If you're getting verification errors in ADB, you likely don't have the latest version installed.
NEXT!
Step 2: Flash the Oreo update package:
Download the Oreo update package below.
Connect your phone to your computer while it is in recovery.
You must have ADB installed. Open command prompt or terminal.
Sideload the package by typing "adb sideload XXXXXX".
You may see multiple errors/warnings. Ignore them.
DO NOT touch or unplug the device until it reboots on its OWN!
Last step
Open your device, and perform a factory data reset. This is mandatory.
New! - Update your Google Play Services to v940. Thanks @Dudash
Code:
As always, anything you from XDA is done at your own risk! There's a chance that someone got something wrong, and you could mess up your device! Please - if you want to be safer, wait until a bunch of people have tried a given ROM/procedure/tool before you try yourself!
There's a bit too much instability for the moment in the update schedule. Once the correct build is confirmed as Beta 4, I'll update the OP to the new method.
Thanks for sticking around, guys!
dmezh
Click to expand...
Click to collapse
Downloads:
UPDATE: BETA 2 AVAILABLE
Currently S8+ Only. Do with it what you will, it was up only temporarily and mixed success is reported.
Credit, again, goes to @norbarb.
S8:
AQGL Baseband (XAS - don't use the old BST one!): https://goo.gl/TEbCLe
AQGL to Oreo: https://goo.gl/EFMwBf
S8+:
AQGL Baseband: https://androidfilehost.com/?fid=745425885120759463
AQGL to Oreo2: https://goo.gl/TvmsAU
AQGL to Oreo: https://goo.gl/iq3YJJ
Click to expand...
Click to collapse
PLEASE HIT THE THANKS BUTTON IF I HELPED YOU!
Hi all, here's the new process for beta build installation:
1. Install BQK5 (Nougat)
2. Install Oreo
That's all, and here's how:
[1.] Odin to BQK5. This will wipe your data. You must do this no matter what software you're currently on.
Select CSC_OYN, not HOME_CSC.
Important: This update contains bootloader 2, which means that you can no longer install any updates based on bootloader 1 (i.e., AQJC).
All new updates are based on B2, so you'll need to eventually do this anyway.
Link for S8+: https://drive.google.com/open?id=18CnyqnxlVpLj1qTdt1I5RIhTBi2Uy4xn (Thanks @xdanilva)
Link for S8: https://drive.google.com/file/d/1iDm5tzyzNiSUf07KjEY9E5sFlUjWUb31/view (Thanks @xdanilva)
[2.] Sideload or update-from-sd to Oreo using an update.zip:
S8+ current latest: ZQKS, considered a Beta 4 (Thanks samsung.firmware.science)
S8 current latest: ZQKS, considered a Beta 4 (Thanks samsung.firmware.science)
Click to expand...
Click to collapse
You're done!
Sorry for the S8 delay; I personally confirm everything on my own devices before publishing, and my access to the S8 is limited.
Thank you!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Great! Waiting for S8 , but one question im on AQH3 when s8 be on , i need to flash AQGL baseband?
Solitaryrex said:
Great! Waiting for S8 , but one question im on AQH3 when s8 be on , i need to flash AQGL baseband?
Click to expand...
Click to collapse
Yes, you must flash AQGL.
What is in this zip? System.img & csc?
---------- Post added at 06:06 AM ---------- Previous post was at 06:05 AM ----------
I am already on aqgl.
S8rooted&tooted said:
What is in this zip? System.img & csc?
---------- Post added at 06:06 AM ---------- Previous post was at 06:05 AM ----------
I am already on aqgl.
Click to expand...
Click to collapse
The Oreo zip is the official OTA zip.
Thank you. I will check it out. I got three s8. One is rooted. So I will 7zip it and see what it is. Then go from there. Thank you again. Very much appreciated.
Is this ok on F variant (international)?
dmezh said:
Yes, you must flash AQGL.
Click to expand...
Click to collapse
Great i see is already for download , i have a S8 i install the rom unlocked because from factory was verizon , any problem whit that? Thanks for ans mate
pogi.paul0119 said:
Is this ok on F variant (international)?
Click to expand...
Click to collapse
Definitely not! This is only for USA models, sorry
Solitaryrex said:
Great i see is already for download , i have a S8 i install the rom unlocked because from factory was verizon , any problem whit that? Thanks for ans mate
Click to expand...
Click to collapse
No, that shouldn't be a problem. The device will brand itself as Verizon upon first boot after the install.
dmezh said:
No, that shouldn't be a problem. The device will brand itself as Verizon upon first boot after the install.
Click to expand...
Click to collapse
Great thanks , i ask that because im from mexico im want to be sure i dont have any problems whit signal
That is a no go. It will not read in adb. Says loading then can not read.
---------- Post added at 08:44 AM ---------- Previous post was at 08:20 AM ----------
Update. Sideload didn't work. I got to go via apply from SD card. It is doing its thing now. Will let you know how it went.
Works like a charm. Excellent. Only thing I did different was apply via SD card. For some reason it wouldn't read it on my computer to push it adb. Said failed to read. So I installed it on a SD card and installed that way. It all checks out. All signed and certified.
Thank you for posting this but I have some noob's questions:
1) Will I still receive OTA updates?
2) What does changing the baseband does for me? Anything significant will change?
3) Can I go back to nougat if I want?
4) Upgrading to oreo like this shouldn't trip knox right? Because it official...
Thanks!
romhaja said:
Thank you for posting this but I have some noob's questions:
1) Will I still receive OTA updates?
2) What does changing the baseband does for me? Anything significant will change?
3) Can I go back to nougat if I want?
4) Upgrading to oreo like this shouldn't trip knox right? Because it official...
Thanks!
Click to expand...
Click to collapse
Question one, I checked for updates and it still says it can check for them. So I believe that is a yes.
2. Depends on your baseband you have and carrier. Aqgl is the lastest baseband for Sprint phones I know for sure. So the new one is the Oreo one being a completely different version.
3. Only way to revert is data reset. Wipe the whole phone and take it back to the way you got it.
4. Knox and all the stuff still works. Samsung pay and all that. So Knox doesn't get tripped.
I have found so far everything I use works fine or better than before. Substratum is working flawlessly along side samsung themes. I can't stand their keyboard so I ditched that. Camera is way better. Setting are more open with way more options. I don't see a downside. I turned off my other s8 that is rooted to use this as my daily driver.
romhaja said:
Thank you for posting this but I have some noob's questions:
1) Will I still receive OTA updates?
2) What does changing the baseband does for me? Anything significant will change?
3) Can I go back to nougat if I want?
4) Upgrading to oreo like this shouldn't trip knox right? Because it official...
Thanks!
Click to expand...
Click to collapse
S8rooted&tooted said:
Question one, I checked for updates and it still says it can check for them. So I believe that is a yes.
2. Depends on your baseband you have and carrier. Aqgl is the lastest baseband for Sprint phones I know for sure. So the new one is the Oreo one being a completely different version.
3. Only way to revert is data reset. Wipe the whole phone and take it back to the way you got it.
4. Knox and all the stuff still works. Samsung pay and all that. So Knox doesn't get tripped.
I have found so far everything I use works fine or better than before. Substratum is working flawlessly along side samsung themes. I can't stand their keyboard so I ditched that. Camera is way better. Setting are more open with way more options. I don't see a downside. I turned off my other s8 that is rooted to use this as my daily driver.
Click to expand...
Click to collapse
1) While it appears to "check for updates", you will not get updates. We all will have to wait for a developer to load the next version files for us, again.
3) A factory reset WILL NOT REVERT YOU TO NOUGAT. You will need to download and flash via Odin the appropriate .zip file.
---------- Post added at 06:59 AM ---------- Previous post was at 06:53 AM ----------
@dmezh,
Thanks for bringing this over from the AT&T thread. I've been on this for a couple of days now, an it has been flawless for me. Zero issues. It's my daily driver now.
And I want to emphasize to all users, the importance of your instructions regarding factory reset: on a major system update like this you have a big risk of system conflicts resulting in issues if you choose not to. It's a lot less work in the long run to just bite the bullet and do it now.
cam30era said:
And I want to emphasize to all users, the importance of your instructions regarding factory reset: on a major system update like this you have a big risk of system conflicts resulting in issues if you choose not to. It's a lot less work in the long run to just bite the bullet and do it now.
Click to expand...
Click to collapse
Thank you! Please, friends, save yourself the pain later on. Factory reset.
Hello, I am currently on Sprint, latest official version(which is august patch, AQGL), so I should flash straight from Odin the Unlocked firmware and then sideload Oreo OTA?
cam30era said:
1) While it appears to "check for updates", you will not get updates. We all will have to wait for a developer to load the next version files for us, again.
3) A factory reset WILL NOT REVERT YOU TO NOUGAT. You will need to download and flash via Odin the appropriate .zip file.
---------- Post added at 06:59 AM ---------- Previous post was at 06:53 AM ----------
@dmezh,
Thanks for bringing this over from the AT&T thread. I've been on this for a couple of days now, an it has been flawless for me. Zero issues. It's my daily driver now.
And I want to emphasize to all users, the importance of your instructions regarding factory reset: on a major system update like this you have a big risk of system conflicts resulting in issues if you choose not to. It's a lot less work in the long run to just bite the bullet and do it now.
Click to expand...
Click to collapse
Will I have to wait for every update or only beta updates?
romhaja said:
Will I have to wait for every update or only beta updates?
Click to expand...
Click to collapse
You won't get any updates unless you manually flash them, or revert back to stock.
---------- Post added at 02:06 PM ---------- Previous post was at 02:04 PM ----------
albannotosska said:
Hello, I am currently on Sprint, latest official version(which is august patch, AQGL), so I should flash straight from Odin the Unlocked firmware and then sideload Oreo OTA?
Click to expand...
Click to collapse
Since you are already on AQGL, you should be good to directly sideload the Oreo zip.