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?

[WARNING] HARD Bricking After Upgrading/Downgrading Then Taking OTA

EDITED - an XT1095 owner on the 60.16 bootloader from a 5.1 soak bricked when he downgraded to 4.4.4 then took the 5.0 OTA. Several Brazilian XT1097 owners have done the same on the 60.14 or 60.16 bootloader.
THERE IS NO REASON TO DOWNGRADE TO 4.4.4 AFTER TAKING THE 5.1 SOAK IF THE 5.0 STOCK IMAGES ARE AVAILABLE FOR YOUR DEVICE!!!! Just flash the 5.0 stock images instead (system, kernel, modems, baseband, recovery - but not bootloader (motoboot) or partition table (gpt)).
Quite a few posters on the Q&A forum have hard bricked by taking the 5.1 soak, then downgrading to 4.4.4 then taking the 5.0 OTA. And unfortunately, the files that are necessary to restore their bootloaders are not available.
Obviously, taking an OTA after downgrading is dangerous. I would only flash the firmware myself or use Motorola Device Manager to upgrade if you have downgraded in the past.
Update - a poster on reddit is claiming that they did in fact take the brazilian 5.1 soak OTA, then downgraded to the chilean 4.4.4 then took the chilean 5.0 OTA without bricking. If this is true (and I have no way of knowing if it is true or not), what it could mean is that the OTA updater scripts are supposed to have checks in them that when your bootloader is not the right version, they prevent a brick.
From all that is posted on the Q&A forum, it looks like the Brazilian 5.0 OTA updater script did not have adequate checks in it to prevent bricking. IOW, human error in writing the brazilian 5.0 OTA updater script.
None of us can know which OTA updater script will be properly written and which ones will be defective until people start bricking. My advice is that you don't take the chance, because even if the chilean 5.0 OTA updater script was properly written, the brazilian one was not. Who knows what others were defective.
I would not take the chance myself (and I have MotoCare so it would only be $39 for me to get a new device if I brick) and don't see why anyone would. The Brazilians whose devices were bricked by the 5.0 OTA updater script are being denied warranty service for their devices due to having rooted in the past. They can tell they rooted in the past by the qe (root checker).
There is nothing to be gained by doing this and clearly at least one 5.0 OTA updater script does not prevent bricks if you have previously updated to the 5.1 soak.

I've flashed the the soak and down graded twice in the past couple of months. What is happening to cause hard bricks?

The bricks are caused when doing OTA after a downgrade. Not when flashing.
Sent from my XT1095

eqjunkie829 said:
I've flashed the the soak and down graded twice in the past couple of months. What is happening to cause hard bricks?
Click to expand...
Click to collapse
It happens when they downgrade to 4.4.4 then take the 5.0 OTA as stated in the OP.

AGISCI said:
The bricks are caused when doing OTA after a downgrade. Not when flashing.
Click to expand...
Click to collapse
Right, so I would never take an OTA after downgrading - I would only flash the firmware or use MDM (which is the same as flashing but has checks in it).

,,,

wolfu11 said:
There has to be a reason some of us can downgrade and take the OTA without issues.
Maybe part of the problem is people trying it with a modified software status ?
I've gone back and forth a few times on my 1095 and the one thing I notice is my software status always says official.
Click to expand...
Click to collapse
I responded in the other thread.
wolfu11 said:
There has to be a reason some of us can downgrade and take the OTA without issues.
Maybe part of the problem is people trying it with a modified software status ?
Click to expand...
Click to collapse
The issue is with taking the 5.1 soak, downgrading to 4.4.4 then taking the 5.0 OTA. The OTAs are supposed to fail if your system and recovery are not stock. I am sure the issue is taking the 5.0 update with the 5.1 bootloader and partition table - the OTA updater script does not adequately protect you from a hard brick when you have a higher version BL and PT than the system/recovery version you are running.
You simply cannot downgrade the bootloader despite what some people are saying here - it doesn't happen. Neither fastboot nor mfastboot will downgrade your bootloader. If people were on 5.0 system and then went back to 4.4.4 system and they are still on the 4.4.4 bootloader, then it is because they never successfully flashed the 5.0 bootloader. If they had successfully flashed the 5.0 bootloader, their bootloader would not flash back to the 4.4.4 bootloader using either fastboot or mfastboot.
What is going on with the OTAs that I have seen is that once you upgrade to 5.1 via the soak OTA, you flash back to 4.4.4, which will flash your system/kernel/ramdisk/modems/baseband/recovery back to 4.4.4 but not your bootloader or partition table. Then when they take the 5.0 OTA, which is a patch, the OTA updater script is trying to patch the 5.1 bootloader and partition table as if they were the 4.4.4. This should never happen - it is totally a Motorola mistake. The 5.0 updater script should detect that the person is on a different version bootloader and partition table than 4.4.4 and it should fail rather than hard brick the phone. But it doesn't.
It is infuriating that these people are hard bricking due to Motorola's bad coding and they are being denied warranty service due to having rooted. Root has nothing to do with it - the OTA updater scripts should be coded to fail if the person is on the wrong bootloader and partition table.
wolfu11 said:
The one thing I notice is my software status always says official.
Click to expand...
Click to collapse
Your qe however will show you have rooted in the past if you have ever rooted before.

[,,,

wolfu11 said:
Okay but when I've down graded before and after I sign into kitkat I get a message in the status bar saying to downgrade the firmware I click okay and it reboots. What is that downgrading?
Click to expand...
Click to collapse
Not the bootloader and partition table. I explained that in my other thread.

,,,

wolfu11 said:
That doesn't answer the question, which was what does it downgrade? Anyone know ?
Click to expand...
Click to collapse
Yeah, it does - I answered your question in my other thread multiple times. Just read the thread.

JulesJam said:
Yeah, it does - I answered your question in my other thread multiple times. Just read the thread.
Click to expand...
Click to collapse
Actually you didn't nor did anyone else, I'll just downgrade again and see what that Motorola firmware thing is all about.
No big deal since my phone doesn't seem to brick anyway.

wolfu11 said:
Actually you didn't nor did anyone else,
Click to expand...
Click to collapse
Yeah I did, but I am not repeating it b/c I am tired of spoonfeeding people who don't know basic things yet want to argue with me. You can read the thread or don't. No sweat off of my back either way.
wolfu11 said:
No big deal since my phone doesn't seem to brick anyway.
Click to expand...
Click to collapse
Because you aren't downgrading your BL or PT, lol!
Anyhow, please stop cluttering this thread. I suggest you read and learn what you are flashing then you will know. And please don't encourage other people to do dangerous things with their device when you don't even know what it is that you did with yours.

,,,

wolfu11 said:
Was just curious if you actually downgraded yourself
Click to expand...
Click to collapse
Why would I do something stupid?
wolfu11 said:
or was going by hearsay.
Click to expand...
Click to collapse
OK, you don't know what hearsay is. It is a rule of evidence. It has nothing at all to do with anything other than what is admissible evidence in a court of law. Completely irrelevant to anything being discussed here.
But if what you are trying to say is that I haven't done it myself so how could I possibly know - well I haven't thrown my body in front of a speeding train before but I know if I do, the chances are high I will die, lol! No, I don't have to brick my phone myself to know what could cause a brick.
I simply do not believe that all of the people on the Q&A forum who are begging for the blankflash files to be released are liars and/or making up false bricking stories out of boredom. I believe them when they say they bricked their devices and are desperate for some help.
wolfu11 said:
I won't clutter your thread any longer
Peace
Click to expand...
Click to collapse
Thanks.

JulesJam said:
Why would I do something stupid?
OK, you don't know what hearsay is. It is a rule of evidence. It has nothing at all to do with anything other than what is admissible evidence in a court of law. Completely irrelevant to anything being discussed here.
But if what you are trying to say is that I haven't done it myself so how could I possibly know - well I haven't thrown my body in front of a speeding train before but I know if I do, the chances are high I will die, lol! No, I don't have to brick my phone myself to know what could cause a brick.
I simply do not believe that all of the people on the Q&A forum who are begging for the blankflash files to be released are liars and/or making up false bricking stories out of boredom. I believe them when they say they bricked their devices and are desperate for some help.
Thanks.
Click to expand...
Click to collapse
That clears up a lot .
Thanks

FYI - a poster on reddit is claiming that they did in fact take the brazilian 5.1 soak OTA, then downgraded to the chilean 4.4.4 then took the chilean 5.0 OTA without bricking. If this is true (and I have no way of knowing if it is true or not), what it could mean is that the OTA updater scripts are supposed to have checks in them that when your bootloader is not the right version, they prevent a brick.
From all that is posted on the Q&A forum, it looks like the Brazilian 5.0 OTA updater script did not have adequate checks in it to prevent bricking. IOW, human error in writing the brazilian 5.0 OTA updater script.
None of us can know which OTA updater script will be properly written and which ones will be defective until people start bricking. My advice is that you don't take the chance, because even if the chilean 5.0 OTA updater script was properly written, the brazilian one was not. Who knows what others were defective.
I am not taking the chance myself (and I have MotoCare so it would only be $39 for me to get a new device if I brick) and don't see why anyone would. The Brazilians whose devices were bricked by the 5.0 OTA updater script are being denied warranty service for their devices due to having rooted in the past. They can tell they rooted in the past by the qe (root checker).
There is nothing to be gained by doing this and clearly at least one 5.0 OTA updater script does not prevent bricks if you have previously updated to the 5.1 soak.

Heads up peeps - the XT1095 5.1 soak OTA updater script does not have adequate checks in it to prevent a hard brick if you have downgraded and then attempt to upgrade again.
http://forum.xda-developers.com/showpost.php?p=60941697&postcount=132
So this is just like the Brazilian XT1097 5.0 OTA.

Please read the edit to the OP!!!

This happened to me and I'm so frocking pissed I didn't see this thread beforehand!! Does anyone know if a JTAG service could fix this or how Mich Motorola would charge to repair?

ASUS cancelled 2.19.40.18 OTA

guys
http://www.asus.com/zentalk/forum.php?mod=redirect&goto=findpost&ptid=14836&pid=107979
asus said they cancelled this update due to unstable update...
1st i dont know what is unstable in this version[same as previous and new bug of call screen animation
2nd lol which update came without new bugs?
3rd they removed after they heard about unlocking bootloader..something fishy right :laugh:

they will probably patch the unlock method with the next update, gonna unlock the bootloader before updating to next update.
Sent from my ASUS_Z008D using Tapatalk

luisoman2000 said:
they will probably patch the unlock method with the next update, gonna unlock the bootloader before updating to next update.
Sent from my ASUS_Z008D using Tapatalk
Click to expand...
Click to collapse
ya same here..but what they will do to unlocked phones/??

ansebovi said:
ya same here..but what they will do to unlocked phones/??
Click to expand...
Click to collapse
Maybe there just will be a check and it will abort if the BL is unlocked
But it should be easy to adapt these OTA updates to unlocked devices

ansebovi said:
ya same here..but what they will do to unlocked phones/??
Click to expand...
Click to collapse
Nothing they can do. As long as you don't flash an OTA or full stock build. They may have a way to patch it in their droidboot.

ansebovi said:
guys
3rd they removed after they heard about unlocking bootloader..something fishy right :laugh:
Click to expand...
Click to collapse
That was my first guess as well

TheSSJ said:
Maybe there just will be a check and it will abort if the BL is unlocked
But it should be easy to adapt these OTA updates to unlocked devices
Click to expand...
Click to collapse
no i am asking about bootloader[can they lock it somehow if we flash next ota]
Harfainx said:
Nothing they can do. As long as you don't flash an OTA or full stock build. They may have a way to patch it in their droidboot.
Click to expand...
Click to collapse
so how can we update from here after ??? need to modified by someone for flashing ???
jaysus145 said:
That was my first guess as well
Click to expand...
Click to collapse
ya my 1st thought too,, haha

ansebovi said:
so how can we update from here after ??? need to modified by someone for flashing ???
Click to expand...
Click to collapse
That's how it works with all custom work. Once you're off stock, you're going to have to wait for someone to post a safe update/install.
Rushing in and taking an OTA is a very common way of breaking your build. Like what we see with running an OTA while rooted. Any number of problems can come up.
They could patch any number of things that would give you a very bad day.
With the support we have here though, we'll probably have flashable, safe OTA zips within a few hours of an OTA being captured/downloaded.

Harfainx said:
That's how it works with all custom work. Once you're off stock, you're going to have to wait for someone to post a safe update/install.
Rushing in and taking an OTA is a very common way of breaking your build. Like what we see with running an OTA while rooted. Any number of problems can come up.
They could patch any number of things that would give you a very bad day.
With the support we have here though, we'll probably have flashable, safe OTA zips within a few hours of an OTA being captured/downloaded.
Click to expand...
Click to collapse
well i am from sony device..they release main update of android..and 1 bug fix,thats all...so we dont care..and no need to worry about relocking issues..
this is the first asus device...man they releasing update for every 10days..i thought we could apply just like that..but since they didnt gave unlocked bootloader tool ,i got these doubt..
and thanks for info..
so i must wait for zips which is modified for unlocked bootloader[if they trying to relock]

I honestly doubt they're going to find a way to relock it with an update, but who knows what voodoo they may come up with.
Either way, we'll grab the updates and get them ready to be flashed quickly. It's a simple process.

I highly doubt he will do anything regarding unlocking/locking bootloader. because:
1. last year they released their official tool to unlock zenfone 4,5,6 bootloader after 3-4 months of release.
2. This year when they launched the zf2 in US they hold contest and developer events via xda. Now xda is a place where no one keeps their bootloader locked. so they knew exactly where they are releasing and advertising the product.
So I dont think they would even bother about this bootloader . Maybe it is an unstable build in terms of their quality test.

Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.

joel.maxuel said:
Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.
Click to expand...
Click to collapse
Everthings here http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999

android is open source. and roms are not illegal. so why bother? i don't think asus is interested on ours bootloader plus, other zenfone's are already unlocked

joel.maxuel said:
Dang, and my 551 (2/16GB) is still in transit.
Was browsing the forum and this thread - has 2.19 been captured and saved somewhere else, or was everyone just downloading off ASUS servers for this OTA (when forced)?
I don't know if I would want 2.19 yet. Maybe to keep on my PC until the right time. That is, if 2.20 comes out and the BL hole is plugged, and those who were on 2.19 (and took advantage of the bootloader unlocking) still got the update successfully - if either of those two outcomes are false, I wouldn't use it.
Click to expand...
Click to collapse
Even if your phone gets here on a newer version (it won't), you could always downgrade everything and unlock from there. =)
Shakalaka has backups of everything going back to like version 2.12 or 2.13.

MatteXperiaU said:
android is open source. and roms are not illegal. so why bother? i don't think asus is interested on ours bootloader plus, other zenfone's are already unlocked
Click to expand...
Click to collapse
Problem is they can't support any ROM that isn't official on the zenfone. They'll pass you off. Like most manufacturers.

These are just official update links from Asus. Not backups. Asus can shut those down at any point. Not saying they will.
See here for pre-rooted ROM backups:
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590

one more doubt..
i think 2.17 is stable build from asus without the android os drinking the battery
now i have unlocked the bootloader ,can i reflash the 2.17[asking since it doesnt have the things which enabled to unlock bootloader] ...or once unlocked,we can do anything like other brands phone?

damian5000 said:
These are just official update links from Asus. Not backups. Asus can shut those down at any point. Not saying they will.
See here for pre-rooted ROM backups:
http://forum.xda-developers.com/zenfone2/orig-development/rom-pre-root-img-t3079590
Click to expand...
Click to collapse
I downloaded the appropriate OTA the other night, so if ASUS pulls the file, I still have it and can share it on Dropbox and/or Copy.
I get the phone today! So hopefully tonight I get the OTA up to 2.18 and then wait to see what upcoming 2.20 has to offer. If we can still unlock the BL with 2.20, I will let that OTA happen. Similarly if we find out that those who unlocked their bootloaders can't take the update (at that point I will cry a little, if there is no official way to unlock BL released with the update ).
If both scenarios above are false, then I will apply my downloaded 2.19, unlock the bootloader, then accept 2.20.
Best one could do eh?
---------- Post added at 07:24 ---------- Previous post was at 07:19 ----------
ansebovi said:
one more doubt..
i think 2.17 is stable build from asus without the android os drinking the battery
now i have unlocked the bootloader ,can i reflash the 2.17[asking since it doesnt have the things which enabled to unlock bootloader] ...or once unlocked,we can do anything like other brands phone?
Click to expand...
Click to collapse
I cannot imagine it would re-lock the bootloader. Should be able to downgrade, as long as you use the whole image and not just the OTA zip.
Now you got me wondering....

joel.maxuel said:
I cannot imagine it would re-lock the bootloader. Should be able to downgrade, as long as you use the whole image and not just the OTA zip.
Now you got me wondering....
Click to expand...
Click to collapse
no i didnt mean it will relock,..
but the unlocked needed some file right..it modifies something right? ...and it is not present in old things..so can old fw run on unlocked bootloader? [or would it get bootloop or damage bootloader]

Axon 7 Software Update - MR2

According to a Mod on Z-Community there should be an update being pushed out shortly. If anyone gets the update can provide the change log that would be appreciated. And if you do the update please let us know if the UI has changed. Still waiting on my axon 7, hopefully it ships tomorrow.

We need someone to capture this update before it's installed.
Always thank those who are helpful...and just ignore those who aren't.

I'll be curious if anyone with an unlocked bootloader can get this ota.

xxBrun0xx said:
I'll be curious if anyone with an unlocked bootloader can get this ota.
Click to expand...
Click to collapse
well if in case that is not possible if someone can capture the OTA i bet we can find a way how to apply the OTA with an unlock bootloader.

that would be great if someone can do that!!

DrakenFX said:
well if in case that is not possible if someone can capture the OTA i bet we can find a way how to apply the OTA with an unlock bootloader.
Click to expand...
Click to collapse
Yea, just create a flashable zip.
Sent from my ZTE A2017U using Tapatalk

shoman94 said:
Yea, just create a flashable zip.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
from b20_boot i when back to B20 Stock, so i may be able to capture that OTA wuhahaha , and if i can make a flashable zip i'll do it for everyone else.

DrakenFX said:
well if in case that is not possible if someone can capture the OTA i bet we can find a way how to apply the OTA with an unlock bootloader.
Click to expand...
Click to collapse
It should be possible to patch most everything -- however, if any of the partition hashes don't match, those partitions couldn't be patched. That would make minemeat out of the partition if you forced it, since they are updating blocks, and not direct files.

DrakenFX said:
from b20_boot i when back to B20 Stock, so i may be able to capture that OTA wuhahaha , and if i can make a flashable zip i'll do it for everyone else.
Click to expand...
Click to collapse
How did you go back? Can you please link me to the thread because I am stumped

bkores said:
How did you go back? Can you please link me to the thread because I am stumped
Click to expand...
Click to collapse
There's no thread , it was just me trying new things base on a user who started the idea a little while ago,

xxBrun0xx said:
I'll be curious if anyone with an unlocked bootloader can get this ota.
Click to expand...
Click to collapse
You will get the OTA. You just can't install it if your recovery is modified or is TWRP.
Sent from my ZTE A2017U using XDA-Developers mobile app

max1001 said:
You will get the OTA. You just can't install it if your recovery is modified or is TWRP.
Sent from my ZTE A2017U using XDA-Developers mobile app
Click to expand...
Click to collapse
No, the bootloader unlocking process changes more than just the recovery. It changes boot, system, and fastboot as well. So even if you reflash a stock recovery, if the OTA tries to patch any of those other partitions, it'll fail. This is why people have been clamouring ZTE to post full system images, so people who unlocked their BL can roll back to full stock in order to get OTAs.
Plus, we don't know if ZTE will use the IMEIs of people who officially submitted a bootloader unlock as exceptions to the OTA rollout.

xtermmin said:
Plus, we don't know if ZTE will use the IMEIs of people who officially submitted a bootloader unlock as exceptions to the OTA rollout.
Click to expand...
Click to collapse
They have to be using a list like that. Otherwise they wouldn't be able to roll out the bootloader unlock OTA to the right phones.
Which of course, is still silly -- they should have used the method others use where it's just baked into the OS and you have to request the appropriate code to provide during unlock. Then everyone would be on the same software load.

I am on my new stock phone I just picked up from Best Buy yesterday. I check the updates screen and it shows MiFavor 4.0 and my current version of B20. I haven't hit next yet but how would I capture the OTA?
I am t work with super slow wifi so I don't want to download anything here.

imp3r10 said:
I am on my new stock phone I just picked up from Best Buy yesterday. I check the updates screen and it shows MiFavor 4.0 and my current version of B20. I haven't hit next yet but how would I capture the OTA?
I am t work with super slow wifi so I don't want to download anything here.
Click to expand...
Click to collapse
B20 is the latest as of today. There's an update coming soon per ZTE. They didn't give us a date.
Sent from my ZTE A2017U using XDA-Developers mobile app

I guess by soon they didn't mean within a few days...Usually when companies say soon it's within 24 hrs.

According to the official forums, the MR2 update has been pushed back to next week.
Update:
Due to a few last minute software optimizations, the update will be pushed until mid to late next week.
Give your fingers a rest. We will update the community when the update goes live.
Click to expand...
Click to collapse
https://community.zteusa.com/thread/12287?start=210&tstart=0

I'm still on stock. How would I go about capturing the OTA when it's released next week?
Also, it looks like the bootloader unlock request form on the ZTE site is no longer available, but instead says: "The form AXON 7/Pro Bootloader Unlock Request is no longer accepting responses. Try contacting the owner of the form if you think this is a mistake."
That could mean something significant (free bootloader unlocks for everyone with no voiding of warranty!) or it could mean that they borked something on the backend (I think it was a Google form, so any number of things could have changed that caused the form to disappear).

rczrider said:
I'm still on stock. How would I go about capturing the OTA when it's released next week?
Also, it looks like the bootloader unlock request form on the ZTE site is no longer available, but instead says: "The form AXON 7/Pro Bootloader Unlock Request is no longer accepting responses. Try contacting the owner of the form if you think this is a mistake."
That could mean something significant (free bootloader unlocks for everyone with no voiding of warranty!) or it could mean that they borked something on the backend (I think it was a Google form, so any number of things could have changed that caused the form to disappear).
Click to expand...
Click to collapse
If you are running and adb logcat on your computer (or your phone) when you check for and/or download the OTA, the full link for the OTA should be in there somewhere. Or, to just save the file, after you download it but before you apply it, you can copy it off of the internal sd card partition. Getting the download location is better though, then people can download it directly for themselves.

rczrider said:
I'm still on stock. How would I go about capturing the OTA when it's released next week?
Also, it looks like the bootloader unlock request form on the ZTE site is no longer available, but instead says: "The form AXON 7/Pro Bootloader Unlock Request is no longer accepting responses. Try contacting the owner of the form if you think this is a mistake."
That could mean something significant (free bootloader unlocks for everyone with no voiding of warranty!) or it could mean that they borked something on the backend (I think it was a Google form, so any number of things could have changed that caused the form to disappear).
Click to expand...
Click to collapse
This is Coming from a ZTE-Employee which many of us know him from ZTE-Community
sshasan Employee 13 minutes ago
ZTE has not changed their opinion on unlocking the bootloader. The bootloader will still be unlockable.
I have temporarily stopped the form from accepting new requests for good reason.
1.) The process for unlocking the bootloader will be changing if all goes well with testing. (This includes stock image)
2.) There is a software update coming next week - Since stock images have not yet been released, instead of adding more customers to the mix of those who will not be able to update, I've decided to not let this happen.
Click to expand...
Click to collapse
so that is GREAT news and something else meaning Unlock Bootloader Request or process will be different

Coming from Nexus devices. Very confused about how the G5 Plus works

Please excuse my incompetence. I'm just very overwhelmed how how different things are from Nexus devices
For Nexus devices, there is a page that has stock images for every update. I can't seem to find such a page for the G5 Plus. At least not an official one. Too many outdated threads that link to outdated pages with dead download links, I can't actually find what the latest update is.
Even still, I tried to install this update https://www.getdroidtips.com/npns25-137-33-11-august-moto-g5-plus/ and I get an error in recovery saying:
E3002: Package expects build thumbprint of 7.0/NPNS25.137-33-11/11:user/release-keys or 7.0/NPNS25.137-33-5/5:user/release-keys; this device has 7.0/NPN25.137-33/35:user/release-keys.
E:Error in /sideload/package.zip
(Status 7)
Click to expand...
Click to collapse
I then tried to download this update https://www.getdroidtips.com/npns25-137-35-5-may-moto-g5-plus/ butthe download link was dead
Further, on Nexus devices, if I had a custom ROM, and there was an update to the ROM that required some updates from the official stock image, I would just flash the vendor, radio, and bootloader images extracted from the stock zip file. These update files seem to only be flashable in stock recovery. How would I be able to get these updates with a custom ROM an TWRP?
Sorry if all of this is obvious. Like I said, I'm just overwhelmed.

Yousie642 said:
Please excuse my incompetence. I'm just very overwhelmed how how different things are from Nexus devices
For Nexus devices, there is a page that has stock images for every update. I can't seem to find such a page for the G5 Plus. At least not an official one. Too many outdated threads that link to outdated pages with dead download links, I can't actually find what the latest update is.
Even still, I tried to install this update https://www.getdroidtips.com/npns25-137-33-11-august-moto-g5-plus/ and I get an error in recovery saying:
I then tried to download this update https://www.getdroidtips.com/npns25-137-35-5-may-moto-g5-plus/ butthe download link was dead
Further, on Nexus devices, if I had a custom ROM, and there was an update to the ROM that required some updates from the official stock image, I would just flash the vendor, radio, and bootloader images extracted from the stock zip file. These update files seem to only be flashable in stock recovery. How would I be able to get these updates with a custom ROM an TWRP?
Sorry if all of this is obvious. Like I said, I'm just overwhelmed.
Click to expand...
Click to collapse
Can you try the TWRP flashable builds from here?
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Or the fastboot ROM from here...
https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738

psychopac said:
Can you try the TWRP flashable builds from here?
https://forum.xda-developers.com/g5-plus/development/rom-twrp-flashable-stock-builds-t3675616
Or the fastboot ROM from here...
https://forum.xda-developers.com/g5-plus/how-to/stock-firmware-npn25-137-67-5-fastboot-t3694738
Click to expand...
Click to collapse
I'd actually seen the Fastboot thread already, but I guess in my frustration I misread the firmware version of the download in the OP as the one I was currently on, so I dismissed it as being outdated info. Silly me lol. Thanks!

Yousie642 said:
I'd actually seen the Fastboot thread already, but I guess in my frustration I misread the firmware version of the download in the OP as the one I was currently on, so I dismissed it as being outdated info. Silly me lol. Thanks!
Click to expand...
Click to collapse
From which nexus do you come?

GopalKaul said:
From which nexus do you come?
Click to expand...
Click to collapse
5x, as well as the 5 before that

Moto G5 is a pretty "plain jane" Android device, so is a Nexus device...
That is where the similarity ends, Moto/Lenovo does not provide ANY factory images and all the ones we have are leaked files, and they do not support anything after an unlock code has been issues (doesn't matter if you actually unlock it or not), and "relocking" does not return it to a true locked status like a Nexus device. Downgrading is very difficult and often requires some trickery to get accomplished, if at all.
No device is really like a Nexus as far as enthusiast support, except maybe a OnePlus.
How does this help? It doesn't... it's just some info.

Yousie642 said:
5x, as well as the 5 before that
Click to expand...
Click to collapse
On the 5..

acejavelin said:
Moto G5 is a pretty "plain jane" Android device, so is a Nexus device...
That is where the similarity ends, Moto/Lenovo does not provide ANY factory images and all the ones we have are leaked files, and they do not support anything after an unlock code has been issues (doesn't matter if you actually unlock it or not), and "relocking" does not return it to a true locked status like a Nexus device. Downgrading is very difficult and often requires some trickery to get accomplished, if at all.
No device is really like a Nexus as far as enthusiast support, except maybe a OnePlus.
How does this help? It doesn't... it's just some info.
Click to expand...
Click to collapse
I appreciate it nonetheless. Thanks! I'm actually a bit scared about the warranty now that I've unlocked it. I saw the message that popped up and mentioned it as I was getting my unlock code, but I was kinda mindlessly clicking "OK" through things and didn't realize what it actually said until it was too late :S

Yousie642 said:
I appreciate it nonetheless. Thanks! I'm actually a bit scared about the warranty now that I've unlocked it. I saw the message that popped up and mentioned it as I was getting my unlock code, but I was kinda mindlessly clicking "OK" through things and didn't realize what it actually said until it was too late :S
Click to expand...
Click to collapse
A G4 Play I have that's unlocked still gets updates. Haven't done anything with the G5+ yet.