Related
If you've upgraded to the new Lollipop 5.0.1 update (N910VVRU1BOAF) for Verizon Samsung Galaxy Note 4 (N910V):
MAKE SURE YOU NEVER TAKE ANY OTA
unless/until
IT IS CONFIRMED THAT IT IS SAFE TO UPGRADE/DOWNGRADE
or
A dev has made a SAFE UPGRADE via Odin or recovery-flashable .ZIP​
One of the main advantages of this update is that you can use ODIN to go back to KK 4.4.4 at anytime, since the bootloader isn't incremented.
For Retail Edition: This is very important if you want to gain ROOT access when available & keep it over OTAs then.
For Developer Edition: Some of you have taken the OTA & restored his aboot backup via Odin. This was fine ONLY for this update. However, if the bootloader is incremented with any coming OTA, it'll block your unlocked bootloader for good & you'll end up with a Retail Edition. Moreover, if you were able to restore your aboot over an incremented bootloader using ADB/dd/etc utilizing ROOT access, you'll most likely HARD BRICK your device since the other critical partitions (TZ, SBL, ... etc) can break boot sequence due to failure in signature verification or version check.
Do we know if the updates will automatically install after a period of time?
I'm still on 4.4.4 NJ5, and the dialog pops up periodically. I am running without using the "no OTA" script at the moment. Has anyone experienced the phone update by itself after a while?
^^^I'm not sure, but I've been postponing mine since the Ota was pushed.
Hibby- said:
Do we know if the updates will automatically install after a period of time?
I'm still on 4.4.4 NJ5, and the dialog pops up periodically. I am running without using the "no OTA" script at the moment. Has anyone experienced the phone update by itself after a while?
Click to expand...
Click to collapse
droidx2.3.3 said:
^^^I'm not sure, but I've been postponing mine since the Ota was pushed.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
It's recommended to disable the OTA & manually update whenever you wish, if it's safe.
When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"
itspeat said:
When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"
Click to expand...
Click to collapse
I believe your looking for "SDM"
rhilway said:
I believe your looking for "SDM"
Click to expand...
Click to collapse
You are correct.
Manually updating
hsbadr said:
It's recommended to disable the OTA & manually update whenever you wish, if it's safe.
Click to expand...
Click to collapse
Know where I can grab the 5.01 firmware? I've already debloated / disabled OTA's, etc.
Also, I'm going to want to flash it through Odin, right? I'm on the retail edition (N910V)
Much Appreciated
Nameless crowd face said:
Know where I can grab the 5.01 firmware? I've already debloated / disabled OTA's, etc.
Also, I'm going to want to flash it through Odin, right? I'm on the retail edition (N910V)
Much Appreciated
Click to expand...
Click to collapse
For Retail Edition, follow instructions here to flash N910VVRU1BOAF_FullFirmware.tar.md5.7z!
So if if I upgraded to Lollipop can I still downgrade back to Kit Kat?
hsbadr said:
For Retail Edition, follow instructions here to flash N910VVRU1BOAF_FullFirmware.tar.md5.7z!
Click to expand...
Click to collapse
Thank you again man
samhainww said:
So if if I upgraded to Lollipop can I still downgrade back to Kit Kat?
Click to expand...
Click to collapse
I did last night, just use Odin to flash the NJ5 firmware, when it tries to boot the first time it will bootloop. Pull the battery, replace the battery and boot to recovery (vol up+home+power) then wipe data. The phone will boot to the setup wizard for KK.
I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Sent from my SM-N910V using Tapatalk
starbuckk said:
I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Sent from my SM-N910V using Tapatalk
Click to expand...
Click to collapse
From what I understand, its been confirmed that you can downgrade back to KK from 5.01. However, any updates thereafter (esp. OTA's through your carrier) have the potential to take away that ability to downgrade. A good example of this is the situation that happend with Verizon's Galaxy S4. The Update after MDK locked both the bootloader and the ability to downgrade back to MDK. No one was able to figure out how to downgrade back to MDK and only those fortunate enough not to have taken the update after mdk could flash custom roms that weren't touchwiz based (ie aosp). Since we don't know what the future holds for root on this device, its wise to keep all of your avenues open.
starbuckk said:
I'm a bit confused about this thread. What would the next update lock that isn't already locked? As I understand, the hope of rooting now is looking quite dim.
Not sure I care much since the SD card limitation has been addressed. That was the only reason I rooted my last phone.
Click to expand...
Click to collapse
Nameless crowd face said:
From what I understand, its been confirmed that you can downgrade back to KK from 5.01. However, any updates thereafter (esp. OTA's through your carrier) have the potential to take away that ability to downgrade. A good example of this is the situation that happend with Verizon's Galaxy S4. The Update after MDK locked both the bootloader and the ability to downgrade back to MDK. No one was able to figure out how to downgrade back to MDK and only those fortunate enough not to have taken the update after mdk could flash custom roms that weren't touchwiz based (ie aosp). Since we don't know what the future holds for root on this device, its wise to keep all of your avenues open.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
+1
Another example, some Note 3 users fall into the trap of 4.4.4 OTA update & with no option to downgrade, they lost root, custom TW ROMs, and almost everything. Now, they're waiting with Note 4 users for a root method to rejoin the party while Note 3 on 4.4.2 can be rooted using TowelRoot.
Which tool?
itspeat said:
When blocking/disabling packages, which is the one that stops OTA. I've used the debloat tool for lollipop but just want to ensure that I've blocked it since I don't see any packages titled specifically as "OTA"
Click to expand...
Click to collapse
All of the debloat tools that I find require root, which are you using?
There's a script that someone wrote to disable Ota and debloat. It doesn't need root. Sacher around on here for it
So would it be a bad idea to update just using the software update in the phones settings menu? Or should I do it by running odin? What actual difference does this make? Will this cause me issues once we do have a root method for this device?
As of now it makes no difference.
Stupid question, but how do you turn off automatic OTA on lollipop?
So i unrooted my 6p yesterday and then locked my bootloader today, how long will it take for the notification for an update to pop up?
Im running 6.0.1 with Build Number MTC20F
I am in the UK, my provider is Vodafone, if that makes a difference.
I havent upgraded to android N yet, but from reading, you need to be enrolled in the Android Beta program to get the OTA as of now. Also the bootloader being locked or unlocked shouldn't make a difference.
DeathGrind said:
I havent upgraded to android N yet, but from reading, you need to be enrolled in the Android Beta program to get the OTA as of now. Also the bootloader being locked or unlocked shouldn't make a difference.
Click to expand...
Click to collapse
Cheers, I keep hearing about people getting the update, and all sources keep saying different things, one site says its released and 6p users can get it and another will say its still rolling out. Same goes for the bootloader, one site says it makes a difference and the other will say it doesn't. Guess ill have to wait. Again, cheers.
So, I just went through and made my phone stock MTC20F, but bootloader is still unlocked, enrolled for the beta program at https://www.google.com/android/beta?u=0, and check system updates and instantly got the update to download. So i can confirm that your bootloader doesn't matter and you need to be enrolled.
sid.parmar said:
So i unrooted my 6p yesterday and then locked my bootloader today, how long will it take for the notification for an update to pop up?
Im running 6.0.1 with Build Number MTC20F
I am in the UK, my provider is Vodafone, if that makes a difference.
Click to expand...
Click to collapse
You don't need to re-lock the bootloader or unroot to accept the OTA. You just need to flash stock recovery.
dratsablive said:
You don't need to re-lock the bootloader or unroot to accept the OTA. You just need to flash stock recovery.
Click to expand...
Click to collapse
So ur saying that you can accept the OTA while rooted? Will this work with dp5 rooted with encryption and just revert to stock recovery? (BC right now I'm on the newest twrp)
Sent from my Nexus 6P using XDA-Developers mobile app
ArmStrongDickPunch said:
So ur saying that you can accept the OTA while rooted? Will this work with dp5 rooted with encryption and just revert to stock recovery? (BC right now I'm on the newest twrp)
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
If your system is modified, then the OTA won't work. This works with a systemless root.
Want to change my build from Verizon NBD91V to N4F26O for all other carriers. Any easy way to do it? Can I side load an OTA or do I have to side load a factory image and lose all my stuff? Any other way to do it? I'm stuck on 7.0 and would like to update to 7.1.1. or 7.1.2.
Thanks
Sent from my Nexus 6P using Tapatalk
Yes, you can easily flash between builds/carriers with no ill effects. Download the full Google stock image (not OTA) and do it manually with flash-all.bat (first edit this file in Notepad to remove the -w (wipe) switch so as to not lose your userdata) or you can install and use a toolkit like NRT or Skipsoft found here on XDA to automate the process. Google has released a few images specific to Verizon that included a modified radio, but that radio also works well on all networks. Current radio version is v03.79 for Verizon and v03.78 for all others.
You could always flash a custom rom.
So I flashed a stock image, will I still get OTA updates? Haven't gotten Feb. Update yet.
Sent from my Nexus 6P using Tapatalk
08BlackWRX said:
So I flashed a stock image, will I still get OTA updates? Haven't gotten Feb. Update yet.
Click to expand...
Click to collapse
If you did flash stock, and remained completely stock (ie. not rooted, no custom recovery or kernel) you should get regular OTA security updates. Your OP says you wanted to flash N4F26O which is the February update. March updates are coming out this week, so I would just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
v12xke said:
If you did flash stock, and remained completely stock (ie. not rooted, no custom recovery or kernel) you should get regular OTA security updates. Your OP says you wanted to flash N4F26O which is the February update. March updates are coming out this week, so I would just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
Click to expand...
Click to collapse
I'm actually on N4F26J, I couldn't get N4F26O to work with the Nexus Toolkit for some reason. And yes I'm completely stock otherwise.
Sent from my Nexus 6P using Tapatalk
08BlackWRX said:
I'm actually on N4F26J, I couldn't get N4F26O to work with the Nexus Toolkit for some reason. And yes I'm completely stock otherwise.
Click to expand...
Click to collapse
The only way I know of to try to force an OTA is to swap a SIM from a different carrier into your phone, let it connect (carrier shows in notification). Try to update in settings>>about phone. Then swap your SIM back in. If this doesn't work (it did for me) then.... March updates are coming out this week, so just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
v12xke said:
The only way I know of to try to force an OTA is to swap a SIM from a different carrier into your phone, let it connect (carrier shows in notification). Try to update in settings>>about phone. Then swap your SIM back in. If this doesn't work (it did for me) then.... March updates are coming out this week, so just wait to receive a March OTA. If you get tired of waiting, then side load the March OTA when it is posted.
Click to expand...
Click to collapse
Good to know, thanks.
Sent from my Nexus 6P using Tapatalk
08BlackWRX said:
Good to know, thanks.
Click to expand...
Click to collapse
Boom!
Hello, im on 8.1. dp2, and still didnt get official update with december security patch...can i manually sideload OTA from december over dp2 ??
Thanks??
scrin378 said:
Hello, im on 8.1. dp2, and still didnt get official update with december security patch...can i manually sideload OTA from december over dp2 ??
Thanks??
Click to expand...
Click to collapse
No, ADB sideload will fail. 8.1 DP2 is on a newer branch than December 8.1 stable. You could install via fastboot or wait until Google pushes the OTA for preview users.
Sent from my Nexus 5X using Tapatalk
Opt out beta tester
mr.joshuanice said:
Opt out beta tester
Click to expand...
Click to collapse
I think @mr.joshuanice is right. Opt out from the beta program.
And then, among all methods to install the update I would recommend to flash the factory image so that you can start from a very clean environment.
I can't provide link here on XDA right now because I'm a too young XDA member (not so young in the real-life however, )
By the way, look for android factory images in google and you will find download link as well as instruction for flashing.
luk.giak said:
I think @mr.joshuanice is right. Opt out from the beta program.
And then, among all methods to install the update I would recommend to flash the factory image so that you can start from a very clean environment.
I can't provide link here on XDA right now because I'm a too young XDA member (not so young in the real-life however, )
By the way, look for android factory images in google and you will find download link as well as instruction for flashing.
Click to expand...
Click to collapse
I know that option for beta program...but i dont want to lose my data..
It looks that i will wait for OTA from Google
Thanks...
scrin378 said:
I know that option for beta program...but i dont want to lose my data..
It looks that i will wait for OTA from Google
Thanks...
Click to expand...
Click to collapse
Did you get the OTA yet?
My phone is still on the November patch as well. I'm getting a little impatient here...
whpsnp said:
Did you get the OTA yet?
My phone is still on the November patch as well. I'm getting a little impatient here...
Click to expand...
Click to collapse
No, i opt out from beta program, and then i get official version..i lose my data, but nothing special, most of pics, docs, etc...is on the cloud storage ..so no big deal for me.. good luck with patience
whpsnp said:
Did you get the OTA yet?
My phone is still on the November patch as well. I'm getting a little impatient here...
Click to expand...
Click to collapse
Factory images with January security patches are out since yesterday. Why don't you flash it?
Another option is to use the FULL OTA update. This method does not require to unlock the bootloader and, consequently, to wipe all your data.
If I were you I would go for the factory image with a clean flash
luk.giak said:
Factory images with January security patches are out since yesterday. Why don't you flash it?
Another option is to use the FULL OTA update. This method does not require to unlock the bootloader and, consequently, to wipe all your data.
If I were you I would go for the factory image with a clean flash
Click to expand...
Click to collapse
I thought I needed to have an unlocked bootloader.
By full OTA you mean sideload via adb?
whpsnp said:
I thought I needed to have an unlocked bootloader.
By full OTA you mean sideload via adb?
Click to expand...
Click to collapse
Yes the full OTA is installed via adb sideload. And it does not need an unlocked bootloader.
Look for "full ota Android O" in Google and you will find the page and the instructions.
luk.giak said:
Yes the full OTA is installed via adb sideload. And it does not need an unlocked bootloader.
Look for "full ota Android O" in Google and you will find the page and the instructions.
Click to expand...
Click to collapse
Awesome! I've done it before so it should be fairly easy.
Now I know what I'll do Friday night ?
whpsnp said:
Awesome! I've done it before so it should be fairly easy.
Now I know what I'll do Friday night ?
Click to expand...
Click to collapse
:good:
I had the OTA to 8.1 notification. I rebooted my phone and now it's gone and it shows as I'm being up to date. I want it back!
Sent from my Nexus 6P using Tapatalk
OT
As a side note for all people who do not want to unlock the bootloader. Please consider at least to:
* activate developer options (tapping 7 times on the build number under phone information)
* enter developer options and activate 1) Debug USB and 2) Enable OEM Unlock
As you probably know, the nexus 6p is subject to the bootloop of death. It is hardware based and, when it happens, the only way to give a second life to the Nexus 6p is to flash a special boot.img (or kernel) that enable only 4 cores (over 8). You can perform this procedure only if you can unlock the bootloader. Hence, only if you have previously enabled the two options above (debug USB and Enable OEM Unlock).
---------- Post added at 07:17 PM ---------- Previous post was at 07:05 PM ----------
Ulver said:
I had the OTA to 8.1 notification. I rebooted my phone and now it's gone and it shows as I'm being up to date. I want it back!
Click to expand...
Click to collapse
Google is really messing up with OTAs. You should consider to manually flash a factory image or to adb sideload a full OTA (available on the official website).
Same situation for me, i get ota 8.1 ~ 10 December then 8.1 dp2 ota. And for now no ota I am still on security update from November...
One question, if im rooted, can i flash full OTA with flashfire??
sideload the DP2 to Final ota (Dec patch).
Then unenroll your device from beta, you will get an update (Jan patch)
https://android.googleapis.com/pack.../105818de493dde2bb290a13474a367f78ac6122f.zip
https://www.google.com/android/beta
Factory image direct link: http://storage.googleapis.com/androiddevelopers/shareables/preview/factory/taimen-ppp2.180412.013-factory-546fdc1f.zip
Cool beans!
Suggest new title: Android Beta Program now open.
DP2 has not been made available yet.
PhoenixPath said:
Suggest new title: Android Beta Program now open.
DP2 has not been made available yet.
Click to expand...
Click to collapse
Redditors are reportedly getting the OTA as we speak.
snowrelyt said:
Redditors are reportedly getting the OTA as we speak.
Click to expand...
Click to collapse
Within the last few minutes, yes. (After the Android P presentation was completed)
I am getting it now myself. Had no idea how quick they'd release it, so suggested playing it safe. Doesn't matter much now, I suppose.
Can we get Ota on rooted/unlocked bootloader? I know we can't install Ota on a rooted phone with custom recovery, but I haven't even gotten monthly security updates ever since I rooted my pixel. I enrolled in the beta as soon as it was announced but will i get an Ota since my phone is rooted?
...
Yasharkhan said:
Can we get Ota on rooted/unlocked bootloader? I know we can't install Ota on a rooted phone with custom recovery, but I haven't even gotten monthly security updates ever since I rooted my pixel. I enrolled in the beta as soon as it was announced but will i get an Ota since my phone is rooted?
Click to expand...
Click to collapse
I just got my OTA notification on my unlocked/rooted Pixel 2XL.
Yasharkhan said:
Can we get Ota on rooted/unlocked bootloader? I know we can't install Ota on a rooted phone with custom recovery, but I haven't even gotten monthly security updates ever since I rooted my pixel. I enrolled in the beta as soon as it was announced but will i get an Ota since my phone is rooted?
Click to expand...
Click to collapse
Same as me.im on dp1 with root..need a guide how to install dp2 from here
So dumb question but where does this OTA download to on the phone? I would like to grab a copy of it after it finishes downloading.
mprziv said:
I just got my OTA notification on my unlocked/rooted Pixel 2XL.
Click to expand...
Click to collapse
Did you install it?
The Beta OTA is coming to DP1 or is coming to Android Oreo? Whoever has received can they confirm.
gettinwicked said:
Did you install it?
Click to expand...
Click to collapse
I got the notification and currently downloading it right now
Does anyone know how to clear any rootless navbar customizations? Essentially clearing it back to stock, but without factory resetting. I thought I reset it through Custom Navbar but now my Navbar keeps defaulting back to the old 3 buttons (the new gesture navbar won't stay)
Edit: under Settings>System>Gestures you can turn on the gesture-based navigation.
I have unlocked bootloader but installed full May factory image without rooting. Have notification about Android P beta update but stuck on downloading OTA... Could I install it on the unlocked bootloader?
Phelicks said:
I have unlocked bootloader but installed full May factory image without rooting. Have notification about Android P beta update but stuck on downloading OTA... Could I install it on the unlocked bootloader?
Click to expand...
Click to collapse
It just takes some time
fiffan86 said:
I got the notification and currently downloading it right now
Click to expand...
Click to collapse
Let us know how it goes! Like, do you lose root/custom recovery, anything like that. I'm waiting to install mine until I know the correct way to do it being rooted/custom recovery.
Thanks in advance!
Factory image is live but there is an error when downloading
https://developer.android.com/preview/download
Phelicks said:
Factory image is live but there is an error when downloading
https://developer.android.com/preview/download
Click to expand...
Click to collapse
Thanks, added the link to the op
Phelicks said:
Factory image is live but there is an error when downloading
https://developer.android.com/preview/download
Click to expand...
Click to collapse
Yep i also get an error