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?
Just read that LG is planning on monthly updates for security reasons....
http://phandroid.com/2015/08/06/lg-...ey-too-will-release-monthly-security-updates/
Wish I didn't unlock? Or are we going to have those patches here available?
They better should enable bootloader unlocking for everyone.
Then each LG user can flash his own ROM and solve security issues very quickly with the community.
Nice announcement, but the stagefrighter hole is gaping and gaping...
*justintime* said:
Just read that LG is planning on monthly updates for security reasons....
http://phandroid.com/2015/08/06/lg-...ey-too-will-release-monthly-security-updates/
Wish I didn't unlock? Or are we going to have those patches here available?
Click to expand...
Click to collapse
you have unlocked the bootloader, so you have a custom recovery and could of course install any rom .
Sure at the moment there are not a lot roms available, but the official ones are however posted...
beside that, i don't think that unlocking the bootloader (and rooting the phone) will disable the OTA feature...
alain57 said:
you have unlocked the bootloader, so you have a custom recovery and could of course install any rom .
Sure at the moment there are not a lot roms available, but the official ones are however posted...
beside that, i don't think that unlocking the bootloader (and rooting the phone) will disable the OTA feature...
Click to expand...
Click to collapse
Not? On HTC OTA updates were not possible...
Yes those custom roms.... Sigh... I think we will get them if a can choose another phone[emoji3]
Or... Use an app with built in protection for that issue?
*justintime* said:
Just read that LG is planning on monthly updates for security reasons....
http://phandroid.com/2015/08/06/lg-...ey-too-will-release-monthly-security-updates/
Wish I didn't unlock? Or are we going to have those patches here available?
Click to expand...
Click to collapse
As I read OTA won't work on a unlocked phone.
But you can get the KDZ and flash this - you will need to root again though...
Greetings
Medzinmann
*justintime* said:
Just read that LG is planning on monthly updates for security reasons....
http://phandroid.com/2015/08/06/lg-...ey-too-will-release-monthly-security-updates/
Wish I didn't unlock? Or are we going to have those patches here available?
Click to expand...
Click to collapse
You will still be able to receive the updates, unlocking the bootloader does not stop you receiving OTA updates.
Medizinmann said:
As I read OTA won't work on a unlocked phone.
But you can get the KDZ and flash this - you will need to root again though...
Greetings
Medzinmann
Click to expand...
Click to collapse
the bootloader itself does not change anything to the OTA process
but changing the recovery may block the OTA from working ... the phone may download the update but the custom recovery may not understand it :silly:
but most of the time, people find a way to create a flashable zip to make an update for custom recovery
alain57 said:
the bootloader itself does not change anything to the OTA process
but changing the recovery may block the OTA from working ... the phone may download the update but the custom recovery may not understand it :silly:
but most of the time, people find a way to create a flashable zip to make an update for custom recovery
Click to expand...
Click to collapse
I didn't try it myself, but people in the low effort root thread wrote it didn't work.
They got an error like "update not possible - suspicious root" or something.
http://forum.xda-developers.com/showthread.php?p=62250050
I will try today and see if it works.
I could download the OTA Update, if it works I will try this evening.
Greetings
Medzinmann
Medizinmann said:
I didn't try it myself, but people in the low effort root thread wrote it didn't work.
They got an error like "update not possible - suspicious root" or something.
http://forum.xda-developers.com/showthread.php?p=62250050
I will try today and see if it works.
I could download the OTA Update, if it works I will try this evening.
Greetings
Medzinmann
Click to expand...
Click to collapse
Yeah they couldn't OTA as they had rooted, not because they had unlocked their bootloader.
OTA are still made available to people with unlocked bootloaders, just not to people who have rooted. At the end of the day you can just find the KDZ and flash it to update or make an update zip to do it from custom recovery.
IIIIkoolaidIIII said:
Yeah they couldn't OTA as they had rooted, not because they had unlocked their bootloader.
OTA are still made available to people with unlocked bootloaders, just not to people who have rooted. At the end of the day you can just find the KDZ and flash it to update or make an update zip to do it from custom recovery.
Click to expand...
Click to collapse
That might be right, but as they said a simple unroot wouldn't work.
And BTW what is the point in unlocking the bootloader when you don't want to root?
I mean custom rom maybe but they are usually rooted as well for obvious reasons etc.
Greetings
Medzinmann
Medizinmann said:
That might be right, but as they said a simple unroot wouldn't work.
And BTW what is the point in unlocking the bootloader when you don't want to root?
I mean custom rom maybe but they are usually rooted as well for obvious reasons etc.
Greetings
Medzinmann
Click to expand...
Click to collapse
Unrooting via flashing a clean image worked fine for me, got OTA and then flashed new root.
IIIIkoolaidIIII said:
Unrooting via flashing a clean image worked fine for me, got OTA and then flashed new root.
Click to expand...
Click to collapse
As I said one could always get the most recent KDZ and flash this and reroot. A working OTA would make this just a little more convenient...that's all.
Greetings
Medzinmann
Just unroot, uninstall SuperSu and fire up LG Bridge. Install update. Flash root with twrp. Finish. Did that yesterday.
Sent from outer space using telepathy
does the new update fix stagefright?
On t-mobile it did.
Sent from my LG-H811 using XDA Free mobile app
Alright so I have a problem with the touch functionality of my phone. I have an LG G4 811 T-mobile variant. The new update is supposed to resolve that but I'm not sure how to update on a rooted device with twrp installed (update stagefrieght). I'm looking for a zip file and i have not managed to find it at all. Could someone help? Also if this is misplaced please devs move it or point me in the right direction to which my question can be answered.
---------- Post added at 02:25 AM ---------- Previous post was at 02:24 AM ----------
fpsq said:
Just unroot, uninstall SuperSu and fire up LG Bridge. Install update. Flash root with twrp. Finish. Did that yesterday.
Sent from outer space using telepathy
Click to expand...
Click to collapse
and this for sure worked with you?
Yes, it worked perfectly fine for my LG G4 H815 unlocked! Now on V10d-EUR-XX. Stagefright is fixed. ****ing sim issue (com.android.phone crashes, does NOT restart itself) remains. Support is worthless. Found a workaround myself.
LG lied about that updates. They never repaired these bugs and now it has About 50 stagefright etc vurnerabilities.
What updates you say? I'm still on V20D since January LoL LG is a joke.
Στάλθηκε από το LG-H815 μου χρησιμοποιώντας Tapatalk
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.
Hey guys. Noob question alert. I'm still running the android august update on my 6P. Why am I not getting the latest October/November update? Thanks in advance.
Rooted? Unlocked BL? if so, that is why.
pickupman66 said:
Rooted? Unlocked BL? if so, that is why.
Click to expand...
Click to collapse
Nope. No root and locked bootloader.
Same problem here. Stuck on October security update
In my experience they're kinda random but you'll get them eventually. This is why I prefer to flash the updates manually as soon as they come out. Plus, if an OTA messes up your phone and you have a locked bootloader, your options are very limited I'm fixing the issue. An unlocked BL for me is more of a safety net than anything else.
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