Related
Removed as inappropriate!
Please close this thread!
I thought that the new unlock tool on the website is made for the 4.2.1 ROM? Maybe that is why it asks you to update...
joelalmeidaptg said:
I thought that the new unlock tool on the website is made for the 4.2.1 ROM? Maybe that is why it asks you to update...
Click to expand...
Click to collapse
The new unlock v8 is for 4.2 but as stated I used v7 which covers 4.0 and 4.1.
It didn't ask to update it just started updating without confirmation from me and that is the reason for the post.
It was totally on automatic and I had no control or say in the matter. In the past you have always had a choice to decline the updates and once unlocked you could not receive updates - this is something entirely new from Asus.
Thanks for the reply as it confirms I can't properly explain the situation.
Well clearly it downloaded the 4.2 update and put it on the cache partition, ready to install next time you rebooted. Which it did.
Case closed. What is the fuss about?
Once you are unlocked you will not get a OTA network update but if you have unlocked after it downloaded it then it will install.
sbdags said:
Well clearly it downloaded the 4.2 update and put it on the cache partition, ready to install next time you rebooted. Which it did.
Case closed. What is the fuss about?
Once you are unlocked you will not get a OTA network update but if you have unlocked after it downloaded it then it will install.
Click to expand...
Click to collapse
No fuss, just info!
Have you ever received an update after unlocking a tablet or received an update that you did not confirm acceptance?
I haven't not nor have I heard of anyone else doing so.
The point of this being that motherboards remanfactured now will update you from ICS 4.0.3 to JB 4.2.1 without confirmation.
This means no chance to install nvflash as you will be on JB without choice if you are not very careful.
If you respond yes I'll remove the info and asked that this thread be closed.
tobdaryl said:
No fuss, just info!
Have you ever received an update after unlocking a tablet or received an update that you did not confirm acceptance?
I haven't not nor have I heard of anyone else doing so.
The point of this being that motherboards remanfactured now will update you from ICS 4.0.3 to JB 4.2.1 without confirmation.
This means no chance to install nvflash as you will be on JB without choice if you are not very careful.
If you respond yes I'll remove the info and asked that this thread be closed be closed.
Click to expand...
Click to collapse
I have had an update I didn't accept and it installed yes. Sat there and watched it install a firmware update after a reboot. I didn't even notice it had downloaded. I think they force 3 goes at denying the update then force it don't they?
Also you have to understand that the firmware contains firmware updates for the keyboard, screen and camera. They are sitting there in /system/etc/firmware waiting to install and will install themselves if you reboot and don't have the latest version......
tobdaryl said:
Removed as inappropriate!
Please close this thread!
Click to expand...
Click to collapse
I have removed the info and asked for the thread to be closed.
Just for info the update was 4.2.1 not camera etc.
Hey, I rooted my Lg g2, and I see that there is an update for srpint G2's to get to kitkat, however I am on jellybean. I am not seeing an update for kitkat, and when I manually check it says I am up to date? is this because I rooted, or?
eddytheyeti2 said:
Hey, I rooted my Lg g2, and I see that there is an update for srpint G2's to get to kitkat, however I am on jellybean. I am not seeing an update for kitkat, and when I manually check it says I am up to date? is this because I rooted, or?
Click to expand...
Click to collapse
No it isn't because you have root. I wouldn't accept the OTA though. There isn't a native root process for KitKat as of yet. We just have the sneaky pants ninja workaround at the moment bc of the new KitKat security shenanigans. OTAs are sometimes pushed out in waves. When the AT&T OTA pushed I didn't get it until 2 days after it was initially pushed. I'd just keep checking. If you get the "Device is up to date. You can check again in 24 hrs" message you can get around that by going into date and time and manually changing your date to tomorrow and it lets you check again right away.
Also you might want to edit your post title. Spring G2
EDIT: Actually I just found out ioroot25 roots KitKat without the downgrade workaround. Yay XDA devs!!!
BreakingVZW said:
No it isn't because you have root. I wouldn't accept the OTA though. There isn't a native root process for KitKat as of yet. We just have the sneaky pants ninja workaround at the moment bc of the new KitKat security shenanigans. OTAs are sometimes pushed out in waves. When the AT&T OTA pushed I didn't get it until 2 days after it was initially pushed. I'd just keep checking. If you get the "Device is up to date. You can check again in 24 hrs" message you can get around that by going into date and time and manually changing your date to tomorrow and it lets you check again right away.
Also you might want to edit your post title. Spring G2
EDIT: Actually I just found out ioroot25 roots KitKat without the downgrade workaround. Yay XDA devs!!!
Click to expand...
Click to collapse
Thanks for the info! however, still no update available
eddytheyeti2 said:
Thanks for the info! however, still no update available
Click to expand...
Click to collapse
you can always try either a)contacting your company and asking them to push the ota or b)depending on which device you have there are roms/kdz/tots to flash kk if you don't want to wait http://forum.xda-developers.com/showthread.php?t=2705259
Just received lollipop via OTA. Check system for updates people!
qwerty12601 said:
Just received lollipop via OTA. Check system for updates people!
Click to expand...
Click to collapse
http://motorola-blog.blogspot.nl/2014/11/its-time-to-unwrap-android-5-lollipop.html
qwerty12601 said:
Just received lollipop via OTA. Check system for updates people!
Click to expand...
Click to collapse
I saw Motorola's blog post, but my device doesn't have anything available yet. As a matter of fact, I still don't even have the updated Google Calendar 5.0. I'd rather see the Play Store offer it than install the APK manually. Not sure when that will happen.
Keep checking. I have 2 on hand. One received it immediately, the other kept saying your device is up to date. Checked a short while later and it was there
Any word on if this official OTA will be pushed to those of us running the leaked .5 Lollipop build? Or will we still need to downgrade to stock 4.4.4 to receive the update? Thanks!
paul_jones said:
Any word on if this official OTA will be pushed to those of us running the leaked .5 Lollipop build? Or will we still need to downgrade to stock 4.4.4 to receive the update? Thanks!
Click to expand...
Click to collapse
This is what I want to know too. I know it just started rolling out, but does anyone know yet?
You have no choice but to downgrade back to 4.4.4 using the images Moto released yesterday. Instructions are available throughout the threads here. There is not going to be a .5 lollipop to the final version. Nothing will come OTA to your device. I took the time last night to flash back.
paul_jones said:
Any word on if this official OTA will be pushed to those of us running the leaked .5 Lollipop build? Or will we still need to downgrade to stock 4.4.4 to receive the update? Thanks!
Click to expand...
Click to collapse
tebower said:
You have no choice but to downgrade back to 4.4.4 using the images Moto released yesterday. Instructions are available throughout the threads here. There is not going to be a .5 lollipop to the final version. Nothing will come OTA to your device. I took the time last night to flash back.
Click to expand...
Click to collapse
Sigh. Thanks a lot for the answer, guess I'll have to flash back to stock this afternoon when I get home!
tebower said:
You have no choice but to downgrade back to 4.4.4 using the images Moto released yesterday. Instructions are available throughout the threads here. There is not going to be a .5 lollipop to the final version. Nothing will come OTA to your device. I took the time last night to flash back.
Click to expand...
Click to collapse
Is that actually confirmed by Motorola? Seems odd they would offer a soak test and then tell all the testers to go back to 4.4.4 (which is far more challenging) to get the official update.
crawlgsx said:
Is that actually confirmed by Motorola? Seems odd they would offer a soak test and then tell all the testers to go back to 4.4.4 (which is far more challenging) to get the official update.
Click to expand...
Click to collapse
there is a delta-ota but that hasn't been leaked
whats the version number?
So is it a soak test or official lollipop? Either way very jelly vzw user here
edwardgtxy said:
whats the version number?
Click to expand...
Click to collapse
22.11.6.en.US
Yes, the update for the soak test users was only sent to them and no one has captured or released it.
crawlgsx said:
Is that actually confirmed by Motorola? Seems odd they would offer a soak test and then tell all the testers to go back to 4.4.4 (which is far more challenging) to get the official update.
Click to expand...
Click to collapse
Still no update. Does it matter if you are using wi-fi vs mobile data?
tebower said:
Yes, the update for the soak test users was only sent to them and no one has captured or released it.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=56583716
What are you taking about?
That is the full update for 4.4.4 to the final version of lollipop. That's not a .5 to .6 update.
kcustom11 said:
http://forum.xda-developers.com/showthread.php?p=56583716
What are you taking about?
Click to expand...
Click to collapse
How much time for branded devices? I have an att dev.
I still have no update yet... Does the official OTA affected by the "root issue"? Also i'm curious if i will see OTA on my device if it's rooted?
If you carefully read my OP here, you'll understand the situation if you're on the .5 or .6 builds
http://forum.xda-developers.com/showthread.php?t=2937074
Sent from my Moto X Pure Edition using Tapatalk
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]
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