Related
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?
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]
Just read that LG is planning on monthly updates for security reasons....
http://phandroid.com/2015/08/06/lg-...ey-too-will-release-monthly-security-updates/
Wish I didn't unlock? Or are we going to have those patches here available?
They better should enable bootloader unlocking for everyone.
Then each LG user can flash his own ROM and solve security issues very quickly with the community.
Nice announcement, but the stagefrighter hole is gaping and gaping...
*justintime* said:
Just read that LG is planning on monthly updates for security reasons....
http://phandroid.com/2015/08/06/lg-...ey-too-will-release-monthly-security-updates/
Wish I didn't unlock? Or are we going to have those patches here available?
Click to expand...
Click to collapse
you have unlocked the bootloader, so you have a custom recovery and could of course install any rom .
Sure at the moment there are not a lot roms available, but the official ones are however posted...
beside that, i don't think that unlocking the bootloader (and rooting the phone) will disable the OTA feature...
alain57 said:
you have unlocked the bootloader, so you have a custom recovery and could of course install any rom .
Sure at the moment there are not a lot roms available, but the official ones are however posted...
beside that, i don't think that unlocking the bootloader (and rooting the phone) will disable the OTA feature...
Click to expand...
Click to collapse
Not? On HTC OTA updates were not possible...
Yes those custom roms.... Sigh... I think we will get them if a can choose another phone[emoji3]
Or... Use an app with built in protection for that issue?
*justintime* said:
Just read that LG is planning on monthly updates for security reasons....
http://phandroid.com/2015/08/06/lg-...ey-too-will-release-monthly-security-updates/
Wish I didn't unlock? Or are we going to have those patches here available?
Click to expand...
Click to collapse
As I read OTA won't work on a unlocked phone.
But you can get the KDZ and flash this - you will need to root again though...
Greetings
Medzinmann
*justintime* said:
Just read that LG is planning on monthly updates for security reasons....
http://phandroid.com/2015/08/06/lg-...ey-too-will-release-monthly-security-updates/
Wish I didn't unlock? Or are we going to have those patches here available?
Click to expand...
Click to collapse
You will still be able to receive the updates, unlocking the bootloader does not stop you receiving OTA updates.
Medizinmann said:
As I read OTA won't work on a unlocked phone.
But you can get the KDZ and flash this - you will need to root again though...
Greetings
Medzinmann
Click to expand...
Click to collapse
the bootloader itself does not change anything to the OTA process
but changing the recovery may block the OTA from working ... the phone may download the update but the custom recovery may not understand it :silly:
but most of the time, people find a way to create a flashable zip to make an update for custom recovery
alain57 said:
the bootloader itself does not change anything to the OTA process
but changing the recovery may block the OTA from working ... the phone may download the update but the custom recovery may not understand it :silly:
but most of the time, people find a way to create a flashable zip to make an update for custom recovery
Click to expand...
Click to collapse
I didn't try it myself, but people in the low effort root thread wrote it didn't work.
They got an error like "update not possible - suspicious root" or something.
http://forum.xda-developers.com/showthread.php?p=62250050
I will try today and see if it works.
I could download the OTA Update, if it works I will try this evening.
Greetings
Medzinmann
Medizinmann said:
I didn't try it myself, but people in the low effort root thread wrote it didn't work.
They got an error like "update not possible - suspicious root" or something.
http://forum.xda-developers.com/showthread.php?p=62250050
I will try today and see if it works.
I could download the OTA Update, if it works I will try this evening.
Greetings
Medzinmann
Click to expand...
Click to collapse
Yeah they couldn't OTA as they had rooted, not because they had unlocked their bootloader.
OTA are still made available to people with unlocked bootloaders, just not to people who have rooted. At the end of the day you can just find the KDZ and flash it to update or make an update zip to do it from custom recovery.
IIIIkoolaidIIII said:
Yeah they couldn't OTA as they had rooted, not because they had unlocked their bootloader.
OTA are still made available to people with unlocked bootloaders, just not to people who have rooted. At the end of the day you can just find the KDZ and flash it to update or make an update zip to do it from custom recovery.
Click to expand...
Click to collapse
That might be right, but as they said a simple unroot wouldn't work.
And BTW what is the point in unlocking the bootloader when you don't want to root?
I mean custom rom maybe but they are usually rooted as well for obvious reasons etc.
Greetings
Medzinmann
Medizinmann said:
That might be right, but as they said a simple unroot wouldn't work.
And BTW what is the point in unlocking the bootloader when you don't want to root?
I mean custom rom maybe but they are usually rooted as well for obvious reasons etc.
Greetings
Medzinmann
Click to expand...
Click to collapse
Unrooting via flashing a clean image worked fine for me, got OTA and then flashed new root.
IIIIkoolaidIIII said:
Unrooting via flashing a clean image worked fine for me, got OTA and then flashed new root.
Click to expand...
Click to collapse
As I said one could always get the most recent KDZ and flash this and reroot. A working OTA would make this just a little more convenient...that's all.
Greetings
Medzinmann
Just unroot, uninstall SuperSu and fire up LG Bridge. Install update. Flash root with twrp. Finish. Did that yesterday.
Sent from outer space using telepathy
does the new update fix stagefright?
On t-mobile it did.
Sent from my LG-H811 using XDA Free mobile app
Alright so I have a problem with the touch functionality of my phone. I have an LG G4 811 T-mobile variant. The new update is supposed to resolve that but I'm not sure how to update on a rooted device with twrp installed (update stagefrieght). I'm looking for a zip file and i have not managed to find it at all. Could someone help? Also if this is misplaced please devs move it or point me in the right direction to which my question can be answered.
---------- Post added at 02:25 AM ---------- Previous post was at 02:24 AM ----------
fpsq said:
Just unroot, uninstall SuperSu and fire up LG Bridge. Install update. Flash root with twrp. Finish. Did that yesterday.
Sent from outer space using telepathy
Click to expand...
Click to collapse
and this for sure worked with you?
Yes, it worked perfectly fine for my LG G4 H815 unlocked! Now on V10d-EUR-XX. Stagefright is fixed. ****ing sim issue (com.android.phone crashes, does NOT restart itself) remains. Support is worthless. Found a workaround myself.
LG lied about that updates. They never repaired these bugs and now it has About 50 stagefright etc vurnerabilities.
What updates you say? I'm still on V20D since January LoL LG is a joke.
Στάλθηκε από το LG-H815 μου χρησιμοποιώντας Tapatalk
*EDIT*
Disregard PSA, SunShine works on SU4TL-44 and SU4TL-49 now.
Just a PSA, after the new SU4TL-49 5.1 update SunShine will be unable to unlock the bootloader. If you are already unlocked, you are fine (dont relock it!).
If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.
jcase said:
Just a PSA, after the new SU4TL-49 5.1 update SunShine will be unable to unlock the bootloader. If you are already unlocked, you are fine (dont relock it!).
If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.
Click to expand...
Click to collapse
Where is this or what is this beta u speak of?
Sent from my XT1254 using XDA-Developers mobile app
hm,i only choose to update the offical mm...but thx to warning us
gangrenius said:
Where is this or what is this beta u speak of?
Sent from my XT1254 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's a soak test.
No! It's a OTA update. You should have it right now. Check for updates. I just installed it last night with no problems. I installed a stock rom. Ran the update, Then rooted again. Simple
@ChazzMatt is speaking of the Marshmallow soak test. @smooth781 is speaking of the Droid Turbo OTA that is still 5.1 (23.21.49.en.US). Both were mentioned in op.
jcase said:
If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.
Click to expand...
Click to collapse
gangrenius said:
Where is this or what is this beta u speak of?
Click to expand...
Click to collapse
ChazzMatt said:
It's a soak test.
Click to expand...
Click to collapse
smooth781 said:
No! It's a OTA update. You should have it right now. Check for updates. I just installed it last night with no problems. I installed a stock rom. Ran the update, Then rooted again. Simple
Click to expand...
Click to collapse
Please actually read the thread before replying. The op clearly mentioned the 6.0 beta and someone asked about it. I answered.
6.0 beta = the Marshmallow soak test.
The Marshmallow soak test is by invitation only and is not an OTA update. Emails went out several days ago.
One of the Quarks (XT1225) already has Marshmallow, and now the Verizon Droid Turbo is being tested for Marshmallow. Chop Chop action is removed in official Marshmallow ROM, or at least it was by the final soak test of the Brazil XT1225 Soak Test #3. It was still there in Soak Test #1.
It's also being removed from the Marshmallow custom ROMs (CM13 and Resurection Remix), at least until the CM dev figures out why Motorola removed it and if it's safe to put back.
Thanks to XDA devs, we've had Marshmallow for months now -- no thanks to Motorola.
ChazzMatt said:
It's also being removed from the Marshmallow custom ROMs (CM13 and Resurection Remix), at least until the CM dev figures out why Motorola removed it and if it's safe to put back.
Thanks to XDA devs, we've had Marshmallow for months now -- no thanks to Motorola.
Click to expand...
Click to collapse
Do you have any idea what the rationale is for removing it from CM, and therefore RR? Why would a feature like this be considered "unsafe?" I use it pretty regularly and if the next RR update implements this, I will not be updating.
@baybutcher27, what are your thoughts on this?
TheSt33v said:
Do you have any idea what the rationale is for removing it from CM, and therefore RR? Why would a feature like this be considered "unsafe?" I use it pretty regularly and if the next RR update implements this, I will not be updating.
@baybutcher27, what are your thoughts on this?
Click to expand...
Click to collapse
Motorola removed it from the Quark Marshmallow ROM, final soak test #3.
CM dev then removed it -- at least for now. Resurrection Remix is CM based.
Skrilax_CZ said:
The reason is proprietaries have been updated to soak #3 as well. It'll keep it disabled until I learn more about why it was disabled.
Click to expand...
Click to collapse
It may be added back in the future.
Wait, Would I be able to update? I've unlocked the bootloader, and am rooted on stock rom.
What would I need to do?
KOAO said:
Wait, Would I be able to update? I've unlocked the bootloader, and am rooted on stock rom.
What would I need to do?
Click to expand...
Click to collapse
I assume if your bootloader is unlocked and you are rooted that you have TWRP custom recovery. Pretty sure OTA would fail. But that's not a bad thing. You don't want to be the one to find out the OTA locks your bootloader permanently. (Probably wouldn't, since you are already unlocked, and having custom recovery will prevent the OTA from installing -- but still you don't want to be the one to find out this time Verizon did something very sneaky.)
If your bootloader is unlocked, you would manually flash the eventual official Marshmallow XT1254 update manually -- not taking it as an "OTA". There will be download links available here on XDA. And you would wait until others have done it first.
Or you would flash a custom Marshmallow ROM, again manually -- either one by @computerfreek274 which would be stock-based (not available yet) or a CM13-based ROM (CM13 or Resurrection Remix) or an AOSP-based ROM (Mokee).
We already have three custom Marshmallow ROMs for ALL Quarks -- CM13, Resurrection Remix, Mokee and Motorola recently finalized stock ROM for the other Quark, the XT1225.
As soon as Motorola/Verizon get their act together for the XT1254/XT1250, you will have a stock Marshmallow ROM available to flash for the XT1254 and @computerfreek274 will also release a "stock-based" ROM for people to flash -- if you want to stay with pure stock or stock-based.
My cell standby battery drain has taken a turn for the worse since updating the modem. It worked fine (comparatively) in the past. Anyone else have this issue? I'm going to flash back the old modem and see if it fixes things.
Edit: Yup, flashed back to 44 and it's back to normal.
drizzzzzz said:
My cell standby battery drain has taken a turn for the worse since updating the modem. It worked fine (comparatively) in the past. Anyone else have this issue? I'm going to flash back the old modem and see if it fixes things.
Edit: Yup, flashed back to 44 and it's back to normal.
Click to expand...
Click to collapse
Yeah, the OTA update was basically worthless -- just an excuse to prevent Sunshine from working to unlock the bootloader.
jcase said:
Just a PSA, after the new SU4TL-49 5.1 update SunShine will be unable to unlock the bootloader. If you are already unlocked, you are fine (dont relock it!).
If you take the 5.1-SU4TL-49 or 6.0 beta update prior to unlocking, then you are so out of luck.
Click to expand...
Click to collapse
i need relock the bootloader , my power botom is broke somebody knows how i can relock it , thanks
sorry for my bad english...
jorgkrkmo said:
i need relock the bootloader , my power botom is broke somebody knows how i can relock it , thanks
sorry for my bad english...
Click to expand...
Click to collapse
Don't lock it. Leave it unlocked, even if you send it in.
is there a chance sunshine will be updated to unlock the new version as well?
rhcreed said:
is there a chance sunshine will be updated to unlock the new version as well?
Click to expand...
Click to collapse
Theres a "chance" but a very slim one. The sunshine devs are not going to pour time and effort into it, but if they do find an exploit they will update it
rhcreed said:
is there a chance sunshine will be updated to unlock the new version as well?
Click to expand...
Click to collapse
The exploit they used has been closed.
Wynnded said:
The exploit they used has been closed.
Click to expand...
Click to collapse
can the phone be reverted to an unlock able version?
rhcreed said:
can the phone be reverted to an unlock able version?
Click to expand...
Click to collapse
No. Stock firmware with locked bootloader is not downgradeable.
People were told from the very beginning NOT to take the update unless your bootloader was unlocked first. Not just in this thread but several others.
Anyone who took the SU4TL-49 update with a locked bootloader does not care about unlocking their bootloader.
1) the Sunshine exploit has been available since November 2015. People have had six months to unlock their bootloaders! Why is it suddenly important now?
2) the Android SU4TL-49 update only showed up less than two weeks ago (early May 2016). It's the first firmware update since the exploit was released.
3) People were warned Android SU4TL-49 would close the Sunshine exploit. But even common sense would tell people that -- knowing control freak Verizon and their locked down bootloaders.
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