Related
so i start using my xoom today, which is the wifi version, rooted on 3.2, and the box pops up and tells me there is another system update. this struck me as odd, because i never saw anything about another system update on xda or xoomforums or anywhere els. could this be an error? or is there really another update? and if there is an update, what are the new features?
thanks
Did you accept and install the update? If so, check your OS build number. The current version is HTJ85B.
alex94kumar said:
so i start using my xoom today, which is the wifi version, rooted on 3.2, and the box pops up and tells me there is another system update. this struck me as odd, because i never saw anything about another system update on xda or xoomforums or anywhere els. could this be an error? or is there really another update? and if there is an update, what are the new features?
thanks
Click to expand...
Click to collapse
If you are rooted on HC3.2, I'm not sure why you would get notification of the update, but that's the latest, and likely to be the last of the Honeycomb version.
okantomi said:
If you are rooted on HC3.2, I'm not sure why you would get notification of the update, but that's the latest, and likely to be the last of the Honeycomb version.
Click to expand...
Click to collapse
I hope there's a 3.2.1 version to be honest - 1 because it's a cool number sequence! lol - and 2 because I want them to push the support non-us keyboard layouts to devices (which moto said would put in their 3.1 update), including support for dorvak layout
Lothaen said:
I hope there's a 3.2.1 version to be honest - 1 because it's a cool number sequence! lol - and 2 because I want them to push the support non-us keyboard layouts to devices (which moto said would put in their 3.1 update), including support for dorvak layout
Click to expand...
Click to collapse
I hope so too, for your sake. It is a cool number sequence!
okantomi said:
I hope so too, for your sake. It is a cool number sequence!
Click to expand...
Click to collapse
we already had 2.3.4
I had the same thing fist time I booted to 3.2. I suspect it's just the ota 3.2 which was already downloaded to your Xoom and it's got a bit confused because it's not installed that download. Anyway, I rejected the update and it's not popped back up since.
burden010 said:
I had the same thing fist time I booted to 3.2. I suspect it's just the ota 3.2 which was already downloaded to your Xoom and it's got a bit confused because it's not installed that download. Anyway, I rejected the update and it's not popped back up since.
Click to expand...
Click to collapse
I'd have installed it if it were me... or at least got the update.zip if possible.
you never know - could be a 3.2.1...
Lothaen said:
I'd have installed it if it were me... or at least got the update.zip if possible.
you never know - could be a 3.2.1...
Click to expand...
Click to collapse
Hehe, would be good if it was but nah, it's just the ota update that I'd been putting off and had been downloaded prior to me flashing a 3.2 ROM.
burden010 said:
Hehe, would be good if it was but nah, it's just the ota update that I'd been putting off and had been downloaded prior to me flashing a 3.2 ROM.
Click to expand...
Click to collapse
Good reason for putting off the ota update!
C_K
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]
Hi all,
Hopefully I am asking in the right place here - it is my first question regarding the Moto X Style.
I got my phone at the end of last week. I decided to unlock the bootloader right from the off as it requires a full wipe. I see that people are seeing the Marshmallow update rolling out in Europe. My question is two fold really.
Firstly, should I receive the OTA update with an unlocked bootloader? Based on what I have read, it looks to me like I should get the update.
Secondly, what "decides" if the update is available to a given phone? When I check for a software update I get the message that the phone is up to date. I'm happy to wait a while but I am also curious how the update rolls out.
Just for extra info, the phone reports as an "XT1572" and the system version says "23.21.18.clark_reteu.reteu.en.EU reteu"
Thanks for any pointers
Just sideload the zip from this thread:
http://forum.xda-developers.com/showthread.php?p=64248551
kadopt said:
Just sideload the zip from this thread:
http://forum.xda-developers.com/showthread.php?p=64248551
Click to expand...
Click to collapse
Thanks for that, I had seen and I will use the sideload method if I don't see the OTA update soon.
My curiosity is more about the mechanics of the OTA method and why my phone does not see an update when I tell it to go and check vs others already seeing it.
user7743 said:
Thanks for that, I had seen and I will use the sideload method if I don't see the OTA update soon.
My curiosity is more about the mechanics of the OTA method and why my phone does not see an update when I tell it to go and check vs others already seeing it.
Click to expand...
Click to collapse
My device is a retfr and didn't receive the update while other users had it, so I just sideloaded it. The update seems to be universal for all eu devices.
user7743 said:
Thanks for that, I had seen and I will use the sideload method if I don't see the OTA update soon.
My curiosity is more about the mechanics of the OTA method and why my phone does not see an update when I tell it to go and check vs others already seeing it.
Click to expand...
Click to collapse
Usually the rollouts are sent on batches and not all at once. I'm not sure if the criteria they use.
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
Hello, two short questions
What's the latest official firmware for XT1642 and where to download?
I only found old ones.
If I relock Bootloader to get the latest OTA, am I be able to reopen it again?
Do I need my e-mail address I used for the first code or can I make a new one?
Thanks
I think you dont' need to relock the bootloader for OTA. I find old firmware too and i didn't test it.
The lock/unlock state of your bootloader isn't relevant to OTA updates, you just need stock recovery and an unmodified system partition.
acejavelin said:
The lock/unlock state of your bootloader isn't relevant to OTA updates, you just need stock recovery and an unmodified system partition.
Click to expand...
Click to collapse
When I got the phone I got an OTA with MJP24.139-63, but when I flashed MJP24.139-48 it always says "Your system is up to date".
I thought this was because of the unlocked bootloader.
I checked immediately after flashing stock firmware, I didn't modify it but still got no OTA.
HE4VYCR0WN said:
When I got the phone I got an OTA with MJP24.139-63, but when I flashed MJP24.139-48 it always says "Your system is up to date".
I thought this was because of the unlocked bootloader.
I checked immediately after flashing stock firmware, I didn't modify it but still got no OTA.
Click to expand...
Click to collapse
It is not because of the unlocked bootloader... I can't tell you exactly why it said that but I can say that isn't the cause.
Remember if you downgraded you are in a mixed state... Not every "piece" can be downgraded, I would bet when you flashed a couple of the parts it said 'Pre-flash validation failed' or something like that, meaning that partition was older and could not be downgraded, typically the bootloader and gpt.bin which is the partition table. That could be the issue, or it could be something else, it's hard to say. There has been some rumor that if the update server has handed out a specific OTA package to certain device for some reason it may not offer it to it to that device again under some conditions.
I don't understand why lenovo don't give us the last full firmware for our device... Sadly i didn't make a backup before flashing kernel and recovery.
titou4488 said:
I don't understand why lenovo don't give us the last full firmware for our device... Sadly i didn't make a backup before flashing kernel and recovery.
Click to expand...
Click to collapse
Have you requested it? You can contact Moto support and ask for it, that's how we got such a large collection for the Moto G 2015, a few people request each firmware image and we share. It can take a couple of days to a few months but Moto usually comes through.
acejavelin said:
Have you requested it? You can contact Moto support and ask for it, that's how we got such a large collection for the Moto G 2015, a few people request each firmware image and we share. It can take a couple of days to a few months but Moto usually comes through.
Click to expand...
Click to collapse
I asked for it just seconds ago, I will keep you up to date when I hear something new.
Thanks for your help.
HE4VYCR0WN said:
When I got the phone I got an OTA with MJP24.139-63, but when I flashed MJP24.139-48 it always says "Your system is up to date".
I thought this was because of the unlocked bootloader.
I checked immediately after flashing stock firmware, I didn't modify it but still got no OTA.
Click to expand...
Click to collapse
its because MJP24.139-63 is the latest .MJP24.139-63 is the the previous update. you need to be on MJP24.139-63 to get the android N upgrade.
zain st said:
its because MJP24.139-63 is the latest .MJP24.139-63 is the the previous update. you need to be on MJP24.139-63 to get the android N upgrade.
Click to expand...
Click to collapse
But he can't have MJP24.139-63 because he doesn't have the OTA update.
Motorola doesn't want to give us the last full firmware. I asked them.
Moto/Lenovo replied to my E-Mail and won't provide assistance in anyway.
Which firmware did you flash? maybe an older firmware will work. I found this: XT1621-XT1622-XT1642_ATHENE_MPJ24.139-23.4_cid50_subsidy-DEFAULT_CFC.xml.zip
HE4VYCR0WN said:
Moto/Lenovo replied to my E-Mail and won't provide assistance in anyway.
Click to expand...
Click to collapse
You can find everything in Guides section: http://forum.xda-developers.com/moto-g4-plus/how-to/index-moto-g4-plus-factory-firmware-t3409033