Related
EDITED - an XT1095 owner on the 60.16 bootloader from a 5.1 soak bricked when he downgraded to 4.4.4 then took the 5.0 OTA. Several Brazilian XT1097 owners have done the same on the 60.14 or 60.16 bootloader.
THERE IS NO REASON TO DOWNGRADE TO 4.4.4 AFTER TAKING THE 5.1 SOAK IF THE 5.0 STOCK IMAGES ARE AVAILABLE FOR YOUR DEVICE!!!! Just flash the 5.0 stock images instead (system, kernel, modems, baseband, recovery - but not bootloader (motoboot) or partition table (gpt)).
Quite a few posters on the Q&A forum have hard bricked by taking the 5.1 soak, then downgrading to 4.4.4 then taking the 5.0 OTA. And unfortunately, the files that are necessary to restore their bootloaders are not available.
Obviously, taking an OTA after downgrading is dangerous. I would only flash the firmware myself or use Motorola Device Manager to upgrade if you have downgraded in the past.
Update - a poster on reddit is claiming that they did in fact take the brazilian 5.1 soak OTA, then downgraded to the chilean 4.4.4 then took the chilean 5.0 OTA without bricking. If this is true (and I have no way of knowing if it is true or not), what it could mean is that the OTA updater scripts are supposed to have checks in them that when your bootloader is not the right version, they prevent a brick.
From all that is posted on the Q&A forum, it looks like the Brazilian 5.0 OTA updater script did not have adequate checks in it to prevent bricking. IOW, human error in writing the brazilian 5.0 OTA updater script.
None of us can know which OTA updater script will be properly written and which ones will be defective until people start bricking. My advice is that you don't take the chance, because even if the chilean 5.0 OTA updater script was properly written, the brazilian one was not. Who knows what others were defective.
I would not take the chance myself (and I have MotoCare so it would only be $39 for me to get a new device if I brick) and don't see why anyone would. The Brazilians whose devices were bricked by the 5.0 OTA updater script are being denied warranty service for their devices due to having rooted in the past. They can tell they rooted in the past by the qe (root checker).
There is nothing to be gained by doing this and clearly at least one 5.0 OTA updater script does not prevent bricks if you have previously updated to the 5.1 soak.
I've flashed the the soak and down graded twice in the past couple of months. What is happening to cause hard bricks?
The bricks are caused when doing OTA after a downgrade. Not when flashing.
Sent from my XT1095
eqjunkie829 said:
I've flashed the the soak and down graded twice in the past couple of months. What is happening to cause hard bricks?
Click to expand...
Click to collapse
It happens when they downgrade to 4.4.4 then take the 5.0 OTA as stated in the OP.
AGISCI said:
The bricks are caused when doing OTA after a downgrade. Not when flashing.
Click to expand...
Click to collapse
Right, so I would never take an OTA after downgrading - I would only flash the firmware or use MDM (which is the same as flashing but has checks in it).
,,,
wolfu11 said:
There has to be a reason some of us can downgrade and take the OTA without issues.
Maybe part of the problem is people trying it with a modified software status ?
I've gone back and forth a few times on my 1095 and the one thing I notice is my software status always says official.
Click to expand...
Click to collapse
I responded in the other thread.
wolfu11 said:
There has to be a reason some of us can downgrade and take the OTA without issues.
Maybe part of the problem is people trying it with a modified software status ?
Click to expand...
Click to collapse
The issue is with taking the 5.1 soak, downgrading to 4.4.4 then taking the 5.0 OTA. The OTAs are supposed to fail if your system and recovery are not stock. I am sure the issue is taking the 5.0 update with the 5.1 bootloader and partition table - the OTA updater script does not adequately protect you from a hard brick when you have a higher version BL and PT than the system/recovery version you are running.
You simply cannot downgrade the bootloader despite what some people are saying here - it doesn't happen. Neither fastboot nor mfastboot will downgrade your bootloader. If people were on 5.0 system and then went back to 4.4.4 system and they are still on the 4.4.4 bootloader, then it is because they never successfully flashed the 5.0 bootloader. If they had successfully flashed the 5.0 bootloader, their bootloader would not flash back to the 4.4.4 bootloader using either fastboot or mfastboot.
What is going on with the OTAs that I have seen is that once you upgrade to 5.1 via the soak OTA, you flash back to 4.4.4, which will flash your system/kernel/ramdisk/modems/baseband/recovery back to 4.4.4 but not your bootloader or partition table. Then when they take the 5.0 OTA, which is a patch, the OTA updater script is trying to patch the 5.1 bootloader and partition table as if they were the 4.4.4. This should never happen - it is totally a Motorola mistake. The 5.0 updater script should detect that the person is on a different version bootloader and partition table than 4.4.4 and it should fail rather than hard brick the phone. But it doesn't.
It is infuriating that these people are hard bricking due to Motorola's bad coding and they are being denied warranty service due to having rooted. Root has nothing to do with it - the OTA updater scripts should be coded to fail if the person is on the wrong bootloader and partition table.
wolfu11 said:
The one thing I notice is my software status always says official.
Click to expand...
Click to collapse
Your qe however will show you have rooted in the past if you have ever rooted before.
[,,,
wolfu11 said:
Okay but when I've down graded before and after I sign into kitkat I get a message in the status bar saying to downgrade the firmware I click okay and it reboots. What is that downgrading?
Click to expand...
Click to collapse
Not the bootloader and partition table. I explained that in my other thread.
,,,
wolfu11 said:
That doesn't answer the question, which was what does it downgrade? Anyone know ?
Click to expand...
Click to collapse
Yeah, it does - I answered your question in my other thread multiple times. Just read the thread.
JulesJam said:
Yeah, it does - I answered your question in my other thread multiple times. Just read the thread.
Click to expand...
Click to collapse
Actually you didn't nor did anyone else, I'll just downgrade again and see what that Motorola firmware thing is all about.
No big deal since my phone doesn't seem to brick anyway.
wolfu11 said:
Actually you didn't nor did anyone else,
Click to expand...
Click to collapse
Yeah I did, but I am not repeating it b/c I am tired of spoonfeeding people who don't know basic things yet want to argue with me. You can read the thread or don't. No sweat off of my back either way.
wolfu11 said:
No big deal since my phone doesn't seem to brick anyway.
Click to expand...
Click to collapse
Because you aren't downgrading your BL or PT, lol!
Anyhow, please stop cluttering this thread. I suggest you read and learn what you are flashing then you will know. And please don't encourage other people to do dangerous things with their device when you don't even know what it is that you did with yours.
,,,
wolfu11 said:
Was just curious if you actually downgraded yourself
Click to expand...
Click to collapse
Why would I do something stupid?
wolfu11 said:
or was going by hearsay.
Click to expand...
Click to collapse
OK, you don't know what hearsay is. It is a rule of evidence. It has nothing at all to do with anything other than what is admissible evidence in a court of law. Completely irrelevant to anything being discussed here.
But if what you are trying to say is that I haven't done it myself so how could I possibly know - well I haven't thrown my body in front of a speeding train before but I know if I do, the chances are high I will die, lol! No, I don't have to brick my phone myself to know what could cause a brick.
I simply do not believe that all of the people on the Q&A forum who are begging for the blankflash files to be released are liars and/or making up false bricking stories out of boredom. I believe them when they say they bricked their devices and are desperate for some help.
wolfu11 said:
I won't clutter your thread any longer
Peace
Click to expand...
Click to collapse
Thanks.
JulesJam said:
Why would I do something stupid?
OK, you don't know what hearsay is. It is a rule of evidence. It has nothing at all to do with anything other than what is admissible evidence in a court of law. Completely irrelevant to anything being discussed here.
But if what you are trying to say is that I haven't done it myself so how could I possibly know - well I haven't thrown my body in front of a speeding train before but I know if I do, the chances are high I will die, lol! No, I don't have to brick my phone myself to know what could cause a brick.
I simply do not believe that all of the people on the Q&A forum who are begging for the blankflash files to be released are liars and/or making up false bricking stories out of boredom. I believe them when they say they bricked their devices and are desperate for some help.
Thanks.
Click to expand...
Click to collapse
That clears up a lot .
Thanks
FYI - a poster on reddit is claiming that they did in fact take the brazilian 5.1 soak OTA, then downgraded to the chilean 4.4.4 then took the chilean 5.0 OTA without bricking. If this is true (and I have no way of knowing if it is true or not), what it could mean is that the OTA updater scripts are supposed to have checks in them that when your bootloader is not the right version, they prevent a brick.
From all that is posted on the Q&A forum, it looks like the Brazilian 5.0 OTA updater script did not have adequate checks in it to prevent bricking. IOW, human error in writing the brazilian 5.0 OTA updater script.
None of us can know which OTA updater script will be properly written and which ones will be defective until people start bricking. My advice is that you don't take the chance, because even if the chilean 5.0 OTA updater script was properly written, the brazilian one was not. Who knows what others were defective.
I am not taking the chance myself (and I have MotoCare so it would only be $39 for me to get a new device if I brick) and don't see why anyone would. The Brazilians whose devices were bricked by the 5.0 OTA updater script are being denied warranty service for their devices due to having rooted in the past. They can tell they rooted in the past by the qe (root checker).
There is nothing to be gained by doing this and clearly at least one 5.0 OTA updater script does not prevent bricks if you have previously updated to the 5.1 soak.
Heads up peeps - the XT1095 5.1 soak OTA updater script does not have adequate checks in it to prevent a hard brick if you have downgraded and then attempt to upgrade again.
http://forum.xda-developers.com/showpost.php?p=60941697&postcount=132
So this is just like the Brazilian XT1097 5.0 OTA.
Please read the edit to the OP!!!
This happened to me and I'm so frocking pissed I didn't see this thread beforehand!! Does anyone know if a JTAG service could fix this or how Mich Motorola would charge to repair?
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]
*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.
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
I'm using the Amazon version of the g5 plus. Is it even possible to downgrade to nougat on this?
I'm gonna say no... bootloader can't be unlocked. But why would you want to? There are no real issues with Oreo...
jmindset said:
I'm using the Amazon version of the g5 plus. Is it even possible to downgrade to nougat on this?
Click to expand...
Click to collapse
Yes, you can downgrade to nougat but you should remove the bootloader and gpt codes , so your device won't hard brick.
acejavelin said:
I'm gonna say no... bootloader can't be unlocked. But why would you want to? There are no real issues with Oreo...
Click to expand...
Click to collapse
Well I just hate the fact that night mode was removed. Now when I use an app for blue light filter, it only works while using the phone. Not on the lockscreen not the pulldown notifications bar. An annoyance more than an actual issue but still...
riyan65 said:
Yes, you can downgrade to nougat but you should remove the bootloader and gpt codes , so your device won't hard brick.
Click to expand...
Click to collapse
Except if you do this, and happen to accept an OTA later it will hard brick if experience with previous Moto devices holds.
acejavelin said:
Except if you do this, and happen to accept an OTA later it will hard brick if experience with previous Moto devices holds.
Click to expand...
Click to collapse
I don't think so, as you are using the latest bootloader with old firmware, after if you update also it just going to update as normal happeneds. If you won't downgrade your bootloader it won't brick at all.yes by updating there could a soft brick chances,but that can be recoverable by fast boot.
riyan65 said:
I don't think so, as you are using the latest bootloader with old firmware, after if you update also it just going to update as normal happeneds. If you won't downgrade your bootloader it won't brick at all.yes by updating there could a soft brick chances,but that can be recoverable by fast boot.
Click to expand...
Click to collapse
I can tell you with 100% certainty that this can happen, and did on Moto G 2015 and Moto X Pure. If you upgraded, then downgraded by fastboot flashing and skipping bootloader and GPT, then you take an OTA update back to the higher version it would hardbrick... No boot, no bootloader, no fastboot... falls immediately into Qloader 9008 mode. It related to the partition table, which is in gpt.bin, and how it resizes it. I know it doesn't make sense, but it definitely happens.
You could always reflash the full factory to upgrade though, that worked... But that OTA was bad news on a device that was downgraded.
acejavelin said:
I can tell you with 100% certainty that this can happen, and did on Moto G 2015 and Moto X Pure. If you upgraded, then downgraded by fastboot flashing and skipping bootloader and GPT, then you take an OTA update back to the higher version it would hardbrick... No boot, no bootloader, no fastboot... falls immediately into Qloader 9008 mode. It related to the partition table, which is in gpt.bin, and how it resizes it. I know it doesn't make sense, but it definitely happens.
You could always reflash the full factory to upgrade though, that worked... But that OTA was bad news on a device that was downgraded.
Click to expand...
Click to collapse
It thought it was impossible to flash a stock room with a locked bootloader? I have the Amazon version of the Moto g5 plus. Am I missing something?
jmindset said:
It thought it was impossible to flash a stock room with a locked bootloader? I have the Amazon version of the Moto g5 plus. Am I missing something?
Click to expand...
Click to collapse
You can flash a stock ROM that is the same version or higher, in the same software channel, on a locked bootloader... you cannot downgrade or use a different software channel with a locked bootloader.
Sorry, we kind of got off on a bit of a tangent there.
acejavelin said:
You can flash a stock ROM that is the same version or higher, in the same software channel, on a locked bootloader... you cannot downgrade or use a different software channel with a locked bootloader.
Sorry, we kind of got off on a bit of a tangent there.
Click to expand...
Click to collapse
It's ok lol so basically I won't be able to downgrade? Knowing Motorola they won't bother responding to the complaints https://forums.lenovo.com/t5/Moto-G...-provided-in-moto-g5-plus/td-p/4222569/page/4
jmindset said:
It's ok lol so basically I won't be able to downgrade? Knowing Motorola they won't bother responding to the complaints https://forums.lenovo.com/t5/Moto-G...-provided-in-moto-g5-plus/td-p/4222569/page/4
Click to expand...
Click to collapse
Correct... You cannot downgrade without an unlocked bootloader, and you cannot unlock the bootloader on an Amazon device.
Moto is now owned by Lenovo, since this occurred they have shown little interest in enhancing or changing anything they release for a device over 6 months old. Unless there is tremendous outcry, meaning like 10's of thousands of people... We tried to petition them to continue update on the Moto G 2015 a while back (something that was stated initially in the devices release) and got about 25,000 signatures. Lenovo didn't even acknowledge it existed. So if you want a significant change in a device, you are going need to get a fairly LARGE outcry from customers, like 50k+ I am guessing, before they would even consider thinking about it, and that isn't likely to happen.
acejavelin said:
Correct... You cannot downgrade without an unlocked bootloader, and you cannot unlock the bootloader on an Amazon device.
Moto is now owned by Lenovo, since this occurred they have shown little interest in enhancing or changing anything they release for a device over 6 months old. Unless there is tremendous outcry, meaning like 10's of thousands of people... We tried to petition them to continue update on the Moto G 2015 a while back (something that was stated initially in the devices release) and got about 25,000 signatures. Lenovo didn't even acknowledge it existed. So if you want a significant change in a device, you are going need to get a fairly LARGE outcry from customers, like 50k+ I am guessing, before they would even consider thinking about it, and that isn't likely to happen.
Click to expand...
Click to collapse
Lol and for that exact reason, I will not purchase another Motorola device. So glad that the mid-range phone market is getting wider each year. I will purchase a Nokia 7.1 next. At least that phone will get guaranteed updates for the next few years.
Just adding to this thread, even if it were possible to downgrade the system to nougat, you would have problems with losing your IMEI. The fix would require root access, and again that's not possible on a locked bootloader.