Database Users

[Early Warning] DO NOT TAKE OTAs after upgrading to Lollipop

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?

[Question] Android N OTA notification?

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.

Sideloading

Hey guys I recently sideloaded the latest oreo beta version on my s8 and now I am wondering if when the oficial oreo 8.0 comes out I will be able to get it OTA or will I have to use Odin to go back to BQL1 and then do the OTA update? I am obviously not part of the samsung beta program.

alek305 said:
Hey guys I recently sideloaded the latest oreo beta version on my s8 and now I am wondering if when the oficial oreo 8.0 comes out I will be able to get it OTA or will I have to use Odin to go back to BQL1 and then do the OTA update? I am obviously not part of the samsung beta program.
Click to expand...
Click to collapse
I believe you'll have to sideload the latest version ,

Joshua Mr PC Repair said:
I believe you'll have to sideload the latest version ,
Click to expand...
Click to collapse
Got it but will I have to use Odin, or updating throught the sd card will be enough?

alek305 said:
Hey guys I recently sideloaded the latest oreo beta version on my s8 and now I am wondering if when the oficial oreo 8.0 comes out I will be able to get it OTA or will I have to use Odin to go back to BQL1 and then do the OTA update? I am obviously not part of the samsung beta program.
Click to expand...
Click to collapse
Did you wipe your device after updating? I didn't do it, and so far it's working fine.

hemp_invader said:
Did you wipe your device after updating? I didn't do it, and so far it's working fine.
Click to expand...
Click to collapse
Mine is working fine too, and no, it didn't got wiped. I was just wondering if after the oficial Oreo release comes out I can just do the OTA but i guess I will just figure it out when it comes out. (Is probably going to be a while)

alek305 said:
Mine is working fine too, and no, it didn't got wiped. I was just wondering if after the oficial Oreo release comes out I can just do the OTA but i guess I will just figure it out when it comes out. (Is probably going to be a while)
Click to expand...
Click to collapse
Theoretically, we are strongly advised to wipe out everything and start from scratch. However, I would rather do it once Oreo is out.
I couldn't help noticing an error occurred during the installation process, some SYSTEM folder or partition that couldn't be mounted due to ACCESS DENIED. Perhaps this is something related with having the device encrypted?

hemp_invader said:
Theoretically, we are strongly advised to wipe out everything and start from scratch. However, I would rather do it once Oreo is out.
I couldn't help noticing an error occurred during the installation process, some SYSTEM folder or partition that couldn't be mounted due to ACCESS DENIED. Perhaps this is something related with having the device encrypted?
Click to expand...
Click to collapse
Yes I remember I saw the error as well, but everything seems working fine so far. I have T mobile and I know that the release of Oreo is going to take a while because they are not even in the testing phase yet.
Do you think we're going to need to flash back to BQL1 and then Oreo? Btw which Baseband version you have installed? I got ZRA6

alek305 said:
Yes I remember I saw the error as well, but everything seems working fine so far. I have T mobile and I know that the release of Oreo is going to take a while because they are not even in the testing phase yet.
Do you think we're going to need to flash back to BQL1 and then Oreo? Btw which Baseband version you have installed? I got ZRA6
Click to expand...
Click to collapse
I have ZRA5, which comes from the leaked build shared a couple of days ago. It has January 2018 security patch and build date is 01/09/2018 22:49:09.
Are you sure you have ZRA6? Perhaps you have different build from a different source. If that is so, where did you get it?
Thanks!

hemp_invader said:
I have ZRA5, which comes from the leaked build shared a couple of days ago. It has January 2018 security patch and build date is 01/09/2018 22:49:09.
Are you sure you have ZRA6? Perhaps you have different build from a different source. If that is so, where did you get it?
Thanks!
Click to expand...
Click to collapse
Yes I am positive I have ZRA6 I got it from: https://samsung.firmware.science
I came across this website looking for ways to update to Oreo. I understand that all the firmware versions he has in the website are officially released by Samsung (including the Betas), the only downside is that he does not specify which software is which, you have to know the baseband versions you are installing.

alek305 said:
Yes I am positive I have ZRA6 I got it from: https://samsung.firmware.science
I came across this website looking for ways to update to Oreo. I understand that all the firmware versions he has in the website are officially released by Samsung (including the Betas), the only downside is that he does not specify which software is which, you have to know the baseband versions you are installing.
Click to expand...
Click to collapse
That site only featured the build intended for the Snapdragon variant of the S8, also known as 950U. If you installed that build on your 950F I'm surprised you haven't bricked it.

hemp_invader said:
That site only featured the build intended for the Snapdragon variant of the S8, also known as 950U. If you installed that build on your 950F I'm surprised you haven't bricked it.
Click to expand...
Click to collapse
Thats the thing, my phone is 950U not 950F sorry I did not specify that little detail. Thats why I was able to install throught the sd card with no trouble at all.

Downgrade from Pie to Oreo

I've been trying to downgrade from the latest pie release but I always get the same error due to how Samsung has blocked bootloader downgrades. Is there anyway around this or am I stuck on Pie?

Sterben Pistole said:
I've been trying to downgrade from the latest pie release but I always get the same error due to how Samsung has blocked bootloader downgrades. Is there anyway around this or am I stuck on Pie?
Click to expand...
Click to collapse
You are probably stucked because you upgraded to the latest bootloader:
After updating bootloader to U5/S5 (as in case of G95xFXXU5DSFB) it will not be possible to downgrade it again to any U2/S2/U3/S3/U4/S4 version
Click to expand...
Click to collapse
Here's a workaround:
Backup your present baseband on TWRP, flash ALEXNDR Oreo's ROM then restore your baseband, otherwise you won't have mobile signal and your IMEI will be unknown.

So in theory the only way to downgrade to Oreo or less, is having the bootloader unlocked with TWRP right? if not, you're stuck

No Bootloader downgrade. Not possible.

Sterben Pistole said:
I've been trying to downgrade from the latest pie release but I always get the same error due to how Samsung has blocked bootloader downgrades. Is there anyway around this or am I stuck on Pie?
Click to expand...
Click to collapse
Why would you want to downgrade anyways?

cantenna said:
Why would you want to downgrade anyways?
Click to expand...
Click to collapse
I can't speak for the OP but for me it is more battery friendly, has better perfomance, allow me to debloat more apps than PIE and has better mod/theme support and looks better (didn't like Pie UI).

nemesisexsp said:
Backup your present baseband on TWRP, flash ALEXNDR Oreo's ROM then restore your baseband, otherwise you won't have mobile signal and your IMEI will be unknown.
Click to expand...
Click to collapse
Quick question for you @nemesisexsp as you seem to know what you're talking about.
I'm in the same boat as OP. attached is my SOFTWARE INFORMATION section with my baseband and whatever. Slightly different to what you've posted on your screenshot.
Can you suggest which files I should use from the ALEXANDR Oreo Mod selection? also, just the ROM, or do i need to do something with the BL files also?
I'm rooted (with TWRP), so that shouldn't be any issue.

tim455 said:
Quick question for you @nemesisexsp as you seem to know what you're talking about.
I'm in the same boat as OP. attached is my SOFTWARE INFORMATION section with my baseband and whatever. Slightly different to what you've posted on your screenshot.
Can you suggest which files I should use from the ALEXANDR Oreo Mod selection? also, just the ROM, or do i need to do something with the BL files also?
I'm rooted (with TWRP), so that shouldn't be any issue.
Click to expand...
Click to collapse
I suggest you flash the last Oreo ROM available for the S8 model (SM-G950F/FD). After you flash it you can boot normally in the ROM and see if your mobile signal is fine, if it isn't just restore your PIE baseband on TWRP.
Here's the original post in _alexndr thread where you can find the ROM link:
https://forum.xda-developers.com/showpost.php?p=75646352&postcount=2

nemesisexsp said:
I suggest you flash the last Oreo ROM available for the S8 model (SM-G950F/FD). After you flash it you can boot normally in the ROM and see if your mobile signal is fine, if it isn't just restore your PIE baseband on TWRP.
Here's the original post in _alexndr thread where you can find the ROM link:
https://forum.xda-developers.com/showpost.php?p=75646352&postcount=2
Click to expand...
Click to collapse
Thanks for the quick response.
I made backups via TWRP just incase, but it looks like everything worked. [see image]
Thank you
It's also got me thinking...
-could you install other custom roms that are Oreo-based?
-What makes Alexndr's rom special?
-Is it technically possible to install stock oreo?

tim455 said:
Thanks for the quick response.
I made backups via TWRP just incase, but it looks like everything worked. [see image]
Thank you
It's also got me thinking...
-could you install other custom roms that are Oreo-based?
-What makes Alexndr's rom special?
-Is it technically possible to install stock oreo?
Click to expand...
Click to collapse
I think you can install other ROMs. I just suggested _alexndr because it's as close to stock as possible as the OP was trying to flash via Odin. But i believe that we can't install older firmware via Odin due to the updated bootloader.

nemesisexsp said:
I think you can install other ROMs. I just suggested _alexndr because it's as close to stock as possible as the OP was trying to flash via Odin. But i believe that we can't install older firmware via Odin due to the updated bootloader.
Click to expand...
Click to collapse
Yes, many thanks.
I was trying to get as stock as possible but only found a NOTE8-to-S8 rom and nothing else stock-y. This seems perfect.

cantenna said:
Why would you want to downgrade anyways?
Click to expand...
Click to collapse
Because Pie is absolute trash on the S8 Active. Battery life went way down hill, constantly stutters like the CPU is loaded or it is thermal throttling, notification screen blanks preventing you from see any in the bar. Tapping notification doesn't always open. They ruined the camera UI. Control via bluetooth doesn't work anymore(forget the name but used to when I started my car it would automatically open Pandora and play. Instead now I have to unlock the phone and open Pandora manually".
I only wouldn't be surprised if it come out later that Samsung pulled and able and deliberately crippled devices to encourage upgrades. Joke's on them because my upgrade will be a different brand.

Robborboy said:
Because Pie is absolute trash on the S8 Active. Battery life went way down hill, constantly stutters like the CPU is loaded or it is thermal throttling, notification screen blanks preventing you from see any in the bar. Tapping notification doesn't always open. They ruined the camera UI. Control via bluetooth doesn't work anymore(forget the name but used to when I started my car it would automatically open Pandora and play. Instead now I have to unlock the phone and open Pandora manually".
I only wouldn't be surprised if it come out later that Samsung pulled and able and deliberately crippled devices to encourage upgrades. Joke's on them because my upgrade will be a different brand.
Click to expand...
Click to collapse
Sounds like you got a snapdragon USA?

cantenna said:
Sounds like you got a snapdragon USA?
Click to expand...
Click to collapse
Yepperoni

Robborboy said:
Yepperoni
Click to expand...
Click to collapse
A dev just mad project treble available fo S8+ Exynos which is pretty much what I think your ultimately after.

cantenna said:
A dev just mad project treble available fo S8+ Exynos which is pretty much what I think your ultimately after.
Click to expand...
Click to collapse
Unfortunately the S8 Active did not come in an exynos version AFAIK.

@nemesisexsp wondering, have you noticed much battery diff between Oreo and Pie?

T-Mobile on Open Beta not receiving Android 10 OTA

I have tried to manually flash the Android 10 Beta to my OnePlus 6T using Local Upgrade but after the phone reboots, I get a "Build Version does not match Hardware version" error and I have to reset my device using MSMDownloadTool. I've always received the Open Beta updates OTA but this new one I am not. Just food for thought: do you think OnePlus is purposely not sending the update OTA to T-Mobile Variants running the International ROM? I've attempted on both the bootloader unlocked method, and the method without needing to unlock the bootloader.

bigmikey307 said:
I have tried to manually flash the Android 10 Beta to my OnePlus 6T using Local Upgrade but after the phone reboots, I get a "Build Version does not match Hardware version" error and I have to reset my device using MSMDownloadTool. I've always received the Open Beta updates OTA but this new one I am not. Just food for thought: do you think OnePlus is purposely not sending the update OTA to T-Mobile Variants running the International ROM? I've attempted on both the bootloader unlocked method, and the method without needing to unlock the bootloader.
Click to expand...
Click to collapse
Yes, T-Mobile is excluded from this beta until now. We found a way to flash the ROM but it has some issues that need to be fixed.

bigmikey307 said:
I have tried to manually flash the Android 10 Beta to my OnePlus 6T using Local Upgrade but after the phone reboots, I get a "Build Version does not match Hardware version" error and I have to reset my device using MSMDownloadTool. I've always received the Open Beta updates OTA but this new one I am not. Just food for thought: do you think OnePlus is purposely not sending the update OTA to T-Mobile Variants running the International ROM? I've attempted on both the bootloader unlocked method, and the method without needing to unlock the bootloader.
Click to expand...
Click to collapse
For what it's worth, Android 10 Beta showed up via OTA on my TMobile 6T running international ROM. Was excited and installed it...same result as for you...won't boot and shows the same message.

OTA's have never worked, just fyi.

Dark Nightmare said:
OTA's have never worked, just fyi.
Click to expand...
Click to collapse
I have had no problem with OTA's on my tmobile 6t running the international beta. I have taken 6-8 of them with no issues.

I've gone from each beta to 17 since i switched to international with no issues. Android 10 does partitions different amongst other things and that's why it doesn't work via OTA.

Scott said:
Yes, T-Mobile is excluded from this beta until now. We found a way to flash the ROM but it has some issues that need to be fixed.
Click to expand...
Click to collapse
Could you post a link to how we can flash the ROM?

Dark Nightmare said:
OTA's have never worked, just fyi.
Click to expand...
Click to collapse
They've always worked for me, you must've not read the original post. And I just received the Android 10 OTA but I'm not gonna install it bc apparently it'll still brick the phone.

bigmikey307 said:
They've always worked for me, you must've not read the original post. And I just received the Android 10 OTA but I'm not gonna install it bc apparently it'll still brick the phone.
Click to expand...
Click to collapse
Same here. All Android 9 OTA updates worked fine for me. That's why I didn't really think twice to hit INSTALL when the Android 10 OTA showed up. I was on the BETA channel, btw, which I am sure you are too.

The notification is driving me crazy.

You can not install Android 10 open beta on a T-Mobile variant OnePlus6T. It will not boot. You will HW/SW mismatch. Even if you've converted it to International
There is no OTA for Android 10, you have to download it from the Oxygen Updater app and then Local Upgrade.
But as I mentioned earlier, IF you have a T-Mobile converted 6T it WILL NOT WORK. you will brick.

GeorgeSRL said:
You can not install Android 10 open beta on a T-Mobile variant OnePlus6T. It will not boot. You will HW/SW mismatch. Even if you've converted it to International
There is no OTA for Android 10, you have to download it from the Oxygen Updater app and then Local Upgrade.
But as I mentioned earlier, IF you have a T-Mobile converted 6T it WILL NOT WORK. you will brick.
Click to expand...
Click to collapse
You can by using the fastboot OB1 mentioned here in these forums, but it's still far from stable. Best to wait for the stable Android 10 from OnePlus. It may be another month though before we see it.
Sent from my ONEPLUS A6013 using Tapatalk

GeorgeSRL said:
You can not install Android 10 open beta on a T-Mobile variant OnePlus6T. It will not boot. You will HW/SW mismatch. Even if you've converted it to International
There is no OTA for Android 10, you have to download it from the Oxygen Updater app and then Local Upgrade.
But as I mentioned earlier, IF you have a T-Mobile converted 6T it WILL NOT WORK. you will brick.
Click to expand...
Click to collapse
No OTA? Oh ok..
Don't install the OTA of you're TMobile, as everyone has said, it will soft brick your device

Fortunately I have the Oneplus 6T International Purple variant. I wanted to be able to use 2 SIMS just in case I need a phone for work I'll just install a second SIM.