Related
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]
When the time comes for Verizon to push the Marshmallow update, do I take it? I would like to eventually root/rom my device.
Would this update potentially break any vulnerabilities in the bootloader that may be present in lollipop?
You should already know this answer...no do not take the update
Michaelmansour1997 said:
You should already know this answer...no do not take the update
Click to expand...
Click to collapse
That's what I figured, thanks!
We can't root the phone because the factory bootloader is locked, that has nothing to do with the OS version.
mjones73 said:
We can't root the phone because the factory bootloader is locked, that has nothing to do with the OS version.
Click to expand...
Click to collapse
So it may be possible if either Motorola or Verizon release a tool to unlock it?
It wouldn't need a vulnerability then, would it?
The reason why I ask is an update to the LG g3 (my friends device) broke the ability to root it (unfortunately he updated before it could be rooted), and I figured it was a common thing throughout Verizon devices.
I highly doubt Verizon or Motorola will unlock it. Someone will have to find an exploit, nothing has been reported so far. The updates for the G3 most likely updated the firmware on the phone and patched whatever exploit they were using to crack the bootloader. With no exploit on the DT2 yet, there's nothing to patch.
if you hope someone will find a exploit to root this phone, dont upgrade. root exploits are usually found on older firmware, so if plan to wait, dont upgrade.
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
I'm using the Amazon version of the g5 plus. Is it even possible to downgrade to nougat on this?
I'm gonna say no... bootloader can't be unlocked. But why would you want to? There are no real issues with Oreo...
jmindset said:
I'm using the Amazon version of the g5 plus. Is it even possible to downgrade to nougat on this?
Click to expand...
Click to collapse
Yes, you can downgrade to nougat but you should remove the bootloader and gpt codes , so your device won't hard brick.
acejavelin said:
I'm gonna say no... bootloader can't be unlocked. But why would you want to? There are no real issues with Oreo...
Click to expand...
Click to collapse
Well I just hate the fact that night mode was removed. Now when I use an app for blue light filter, it only works while using the phone. Not on the lockscreen not the pulldown notifications bar. An annoyance more than an actual issue but still...
riyan65 said:
Yes, you can downgrade to nougat but you should remove the bootloader and gpt codes , so your device won't hard brick.
Click to expand...
Click to collapse
Except if you do this, and happen to accept an OTA later it will hard brick if experience with previous Moto devices holds.
acejavelin said:
Except if you do this, and happen to accept an OTA later it will hard brick if experience with previous Moto devices holds.
Click to expand...
Click to collapse
I don't think so, as you are using the latest bootloader with old firmware, after if you update also it just going to update as normal happeneds. If you won't downgrade your bootloader it won't brick at all.yes by updating there could a soft brick chances,but that can be recoverable by fast boot.
riyan65 said:
I don't think so, as you are using the latest bootloader with old firmware, after if you update also it just going to update as normal happeneds. If you won't downgrade your bootloader it won't brick at all.yes by updating there could a soft brick chances,but that can be recoverable by fast boot.
Click to expand...
Click to collapse
I can tell you with 100% certainty that this can happen, and did on Moto G 2015 and Moto X Pure. If you upgraded, then downgraded by fastboot flashing and skipping bootloader and GPT, then you take an OTA update back to the higher version it would hardbrick... No boot, no bootloader, no fastboot... falls immediately into Qloader 9008 mode. It related to the partition table, which is in gpt.bin, and how it resizes it. I know it doesn't make sense, but it definitely happens.
You could always reflash the full factory to upgrade though, that worked... But that OTA was bad news on a device that was downgraded.
acejavelin said:
I can tell you with 100% certainty that this can happen, and did on Moto G 2015 and Moto X Pure. If you upgraded, then downgraded by fastboot flashing and skipping bootloader and GPT, then you take an OTA update back to the higher version it would hardbrick... No boot, no bootloader, no fastboot... falls immediately into Qloader 9008 mode. It related to the partition table, which is in gpt.bin, and how it resizes it. I know it doesn't make sense, but it definitely happens.
You could always reflash the full factory to upgrade though, that worked... But that OTA was bad news on a device that was downgraded.
Click to expand...
Click to collapse
It thought it was impossible to flash a stock room with a locked bootloader? I have the Amazon version of the Moto g5 plus. Am I missing something?
jmindset said:
It thought it was impossible to flash a stock room with a locked bootloader? I have the Amazon version of the Moto g5 plus. Am I missing something?
Click to expand...
Click to collapse
You can flash a stock ROM that is the same version or higher, in the same software channel, on a locked bootloader... you cannot downgrade or use a different software channel with a locked bootloader.
Sorry, we kind of got off on a bit of a tangent there.
acejavelin said:
You can flash a stock ROM that is the same version or higher, in the same software channel, on a locked bootloader... you cannot downgrade or use a different software channel with a locked bootloader.
Sorry, we kind of got off on a bit of a tangent there.
Click to expand...
Click to collapse
It's ok lol so basically I won't be able to downgrade? Knowing Motorola they won't bother responding to the complaints https://forums.lenovo.com/t5/Moto-G...-provided-in-moto-g5-plus/td-p/4222569/page/4
jmindset said:
It's ok lol so basically I won't be able to downgrade? Knowing Motorola they won't bother responding to the complaints https://forums.lenovo.com/t5/Moto-G...-provided-in-moto-g5-plus/td-p/4222569/page/4
Click to expand...
Click to collapse
Correct... You cannot downgrade without an unlocked bootloader, and you cannot unlock the bootloader on an Amazon device.
Moto is now owned by Lenovo, since this occurred they have shown little interest in enhancing or changing anything they release for a device over 6 months old. Unless there is tremendous outcry, meaning like 10's of thousands of people... We tried to petition them to continue update on the Moto G 2015 a while back (something that was stated initially in the devices release) and got about 25,000 signatures. Lenovo didn't even acknowledge it existed. So if you want a significant change in a device, you are going need to get a fairly LARGE outcry from customers, like 50k+ I am guessing, before they would even consider thinking about it, and that isn't likely to happen.
acejavelin said:
Correct... You cannot downgrade without an unlocked bootloader, and you cannot unlock the bootloader on an Amazon device.
Moto is now owned by Lenovo, since this occurred they have shown little interest in enhancing or changing anything they release for a device over 6 months old. Unless there is tremendous outcry, meaning like 10's of thousands of people... We tried to petition them to continue update on the Moto G 2015 a while back (something that was stated initially in the devices release) and got about 25,000 signatures. Lenovo didn't even acknowledge it existed. So if you want a significant change in a device, you are going need to get a fairly LARGE outcry from customers, like 50k+ I am guessing, before they would even consider thinking about it, and that isn't likely to happen.
Click to expand...
Click to collapse
Lol and for that exact reason, I will not purchase another Motorola device. So glad that the mid-range phone market is getting wider each year. I will purchase a Nokia 7.1 next. At least that phone will get guaranteed updates for the next few years.
Just adding to this thread, even if it were possible to downgrade the system to nougat, you would have problems with losing your IMEI. The fix would require root access, and again that's not possible on a locked bootloader.
We have a new G5 Plus (running stock Nougat) that is prompting for the OTA update to Oreo.
Question: Will the bootloader be unlockable after the update to Oreo?
I intend to unlock the bootloader, but sometimes the ability to unlock it is blocked after an update like this. Sometimes, unlocking the BL before an update blocks the update.
DECloyd said:
We have a new G5 Plus (running stock Nougat) that is prompting for the OTA update to Oreo.
Question: Will the bootloader be unlockable after the update to Oreo?
I intend to unlock the bootloader, but sometimes the ability to unlock it is blocked after an update like this. Sometimes, unlocking the BL before an update blocks the update.
Click to expand...
Click to collapse
You can unlock the bootloader in oreo also.
riyan65 said:
You can unlock the bootloader in oreo also.
Click to expand...
Click to collapse
Great! Thanks!
BTW, in your opinion, do you think that the G5 Plus will get updates past Oreo?
That might seem like an unrelated question, but I'm looking at the idea of adding some audio mods that require root and don't mind waiting until the official updates have settled down. Then I'll unlock, root, etc.
DECloyd said:
Great! Thanks!
BTW, in your opinion, do you think that the G5 Plus will get updates past Oreo?
That might seem like an unrelated question, but I'm looking at the idea of adding some audio mods that require root and don't mind waiting until the official updates have settled down. Then I'll unlock, root, etc.
Click to expand...
Click to collapse
Only via flashed custom ROMs will system software past Oreo exist on the G5 Plus. G series phones get slated for one major system update.
It would be better if you atleast get the unlock code while on nougat. There are issue in Oreo. Some people were having issues where the unlock data provided by the phone was said to be incomplete when pasti g it on Moto's site in order to get the unlock code.
debdeep98 said:
It would be better if you atleast get the unlock code while on nougat. There are issue in Oreo. Some people were having issues where the unlock data provided by the phone was said to be incomplete when pasti g it on Moto's site in order to get the unlock code.
Click to expand...
Click to collapse
Thanks! I will do that.
DECloyd said:
Thanks! I will do that.
Click to expand...
Click to collapse
It is done. Thank you!
DECloyd said:
It is done. Thank you!
Click to expand...
Click to collapse
Great:good: