Related
hi all. Maybe is a stupid questions but I want to know if I root my phone do I will get any official update? (see attachment)
No, you wont be able to get the over-the-air updates anymore if you root.
However, if you flash a custom rom like cyanogenmod the devs usualy incorporate the ota update into their roms. So either way you'd still get the patches
so that mean in order to get the updates over-the-air, i have to role back to unroot nandroid backup, do the updates, than root again.. is that correct?
I thought I read in a recent thread that if you rooted, but kept the stock Tom
You would still get OTA update. Can anyone clarify?
if you have stock bootloader and stock rom but are rooted you will still receive OTA updates, if you flash amons boodloader, and custom roms you will not receive updates.
just remeber that once you update you will lose root and will have to re-apply the root, when it has been released. for that update!
No i mean flash a custom rom (like cyanogenmod) and each time there is an OTA update cyanogen will patch it to his rom. So pretty much flash a custom rom and keep it updated because they will include any OTA updates that are out already
r8zer said:
if you have stock bootloader and stock rom but are rooted you will still receive OTA updates, if you flash amons boodloader, and custom roms you will not receive updates.
just remeber that once you update you will lose root and will have to re-apply the root, when it has been released. for that update!
Click to expand...
Click to collapse
ok, so, can you give me one root information, in order to keep my updates over the air, please?
what do you mean give you one root information, if u unlock bootloader, via fastboot, then use pauls root over at modaco, u will still have stock boot loader and custom rom, all root does is give u superuser, as long as you do not flash a custom recovery or custom rom you will be fine.
r8zer said:
what do you mean give you one root information, if u unlock bootloader, via fastboot, then use pauls root over at modaco, u will still have stock boot loader and custom rom, all root does is give u superuser, as long as you do not flash a custom recovery or custom rom you will be fine.
Click to expand...
Click to collapse
take a look at my fist post: I unlock bootloader via fastboot, I applied root but I did not used Paul root, and also I don't have a custom rom. I have the attachment on top of the page..... everybody get me confused.... can somebody clarified me?
all you show in top post is a pic of the update 1, ERE 27 which to date is the newest one google has released,
right, u got stock bootloader and stock rom, but u r rooted u will still get OTA updates as only custom roms block OTA updates!.
r8zer said:
all you show in top post is a pic of the update 1, ERE 27 which to date is the newest one google has released,
right, u got stock bootloader and stock rom, but u r rooted u will still get OTA updates as only custom roms block OTA updates!.
Click to expand...
Click to collapse
which means 'm still able to get OTA updates, correct?
This conversation was very frustrating to read.
Yes you will get OTA updates, but you will get the same updates much sooner by using Cyanogen's ROM.
I have no idea what motivation you would have to root your N1 and void the warranty if you are just going to get OTA updates and not take advantage of any of the benefits that root enables... (The most desirable of which is a custom recovery allowing the application of a custom ROM)
Diceman4 said:
This conversation was very frustrating to read.
Yes you will get OTA updates, but you will get the same updates much sooner by using Cyanogen's ROM.
I have no idea what motivation you would have to root your N1 and void the warranty if you are just going to get OTA updates and not take advantage of any of the benefits that root enables... (The most desirable of which is a custom recovery allowing the application of a custom ROM)
Click to expand...
Click to collapse
I feel sorry if these conversation it becomes frustrating, but look my reason:
1. no warranty, in my country is not available yet, it sales on black market
2. before to root, I did not made a nandroid backup, I done after root
3. I'm running Alpha 10 Desire Rom for N1, and I want to make sure if I'm going to roll back to my nandroid backup, I will be able to get OTA updates
one more time I do apologize.
Android 5.0 (Lollipop) Bootloader and KitKat Compatibility
Everyone wants Lollipop, however it is worth considering some of the possible consequences of upgrading via OTA update.
Flashable zip of Android 5.0.2 'Soak Test' now available and boots with KitKat Bootloader: http://forum.xda-developers.com/moto-g/development/rom-retail-brazil-lollipop-soak-test-t2998793
Downgrading to KitKat also possible even with Lollipop Bootloader.
Bootloader:
A new Bootloader (BL) will almost certainly be is included in the OTA update. It is also very likely no KitKat Kernel, stock or custom will be able to boot properly with the 5.0 BL. Perhaps the Kernel DEVs can find a workaround.
Root: (DONE)
It may take some time to gain root access on Lollipop as on other devices this has required a custom Kernel. A custom kernel itself may require kernel sources to be released - something that has taken weeks / months in the past.
Chainfire releases Android 5.0 Root for Moto G (2013) (All Models)
In addition; apps that use root access in KitKat, require further development to have functional root access in Lollipop.
Xposed Framework:
Developer has said he will wait for CyanogenMod based on Lollipop before properly starting development of an ART version of Xposed. CM12 may take a few weeks to release. Expect to do without Xposed for at least a month, probably longer since root is also required (see above.) Related: Alternatives to popular Xposed Modules
Custom Recovery:
This has not been an issue before, but it is always possible a new Bootloader could break compatibility with existing Custom Recoveries. Obviously, you would not be able to restore a CWM / TWRP backup without a functional custom recovery; but even then, it is unlikely you will [not] be able to boot your KitKat backup. CWM unaffected, TWRP not fully supported yet.
Custom ROMs:
This is another area that could be affected by a new Bootloader. It is unknown if existing custom ROMs will require new Kernels / system changes in order to work with the new BL - something that could take days, weeks or months. CyanogenMod 12 (Lollipop) for Moto G (Falcon) now available and does not appear to require a new BL.
Performance:
Currently the performance difference between KitKat and Lollipop is unknown. If the first release of Lollipop for Moto G has performance issues, you may be unable to revert back to stock KitKat.Possible solution:
Wait for a flashable zip [NOT OTA Update zip] of Stock Moto G Lollipop ROM - this would mean your Bootloader remains at it's current version and potentially allowing you to change 'back and forth' between Stock KitKat and Stock Lollipop. However, it is currently unknown if the newer BL is a requirement for Android 5.0 Kernels. Flashable zip of Android 5.0.2 'Soak Test' now available and boots with KitKat Bootloader.
That is what I thought, since something like that happened because of the upgrade from JB to KK. Taking all of this into account, I'm not sure to upgrade immediately when the OTA comes out, maybe I'll try to still alive waiting for reviews from someone who dares to OTA right then.
You can be pretty sure it'll bring a bootloader update too because of all the fundamental changes lollipop brings in almost all areas of the OS. Major relase, as was gingerbread -> ICS.
It's pretty safe to say that once you upgrade, it won't be easy to downgrade, if at all possible... Many changes are in the security area and everything is getting tightened up a lot... Loads of tempting things we'll get in this upgrade, yes, but we'll have to give up much of what we're used to (in terms of rooting/etc), at least for a little while. I'll also wait until the dust settles a bit and it's clearer on where we stand with the upgrade once it gets released.
nice info
lost101 said:
Android 5.0 Bootloader and KitKat Compatibility
Everyone wants Lollipop, however it is worth considering some of the possible consequences of upgrading via OTA update.
Bootloader:
A new Bootloader (BL) will almost certainly be included in the OTA update. It is also very likely no KitKat Kernel, stock or custom will be able to boot properly with the 5.0 BL. Perhaps the kernel DEVs can find a workaround.
Root:
It may take some time to gain root access on Lolipop as on other devices this has required a custom Kernel. A custom kernel itself may require kernel sources to be released - something that has taken weeks / months in the past.
Custom Recovery:
This has not been an issue before, but it is always possible a new Bootloader could break compatibility with existing Custom Recoveries.
Performance:
Currently the performance difference between KitKat and Lollipop is unknown. If the first release of Lollipop has performance issues on Moto G, you may be unable to revert back to stock KitKat.
Alternative solution:
Wait for a flashable zip of Stock Moto G Lollipop ROM - this would mean your Bootloader remains at it's current version and potentially allowing you to change between Stock KitKat and Stock Lollipop. However, it is currently unknown if the newer BL is a requirement for Android 5.0 Kernels.
Click to expand...
Click to collapse
UUUUUUHHHHHHHH iam afraight. a little. who needs bootloaders. i dont.
juanchotazo99 said:
You can be pretty sure it'll bring a bootloader update too because of all the fundamental changes lollipop brings in almost all areas of the OS. Major relase, as was gingerbread -> ICS.
It's pretty safe to say that once you upgrade, it won't be easy to downgrade, if at all possible... Many changes are in the security area and everything is getting tightened up a lot... Loads of tempting things we'll get in this upgrade, yes, but we'll have to give up much of what we're used to (in terms of rooting/etc), at least for a little while. I'll also wait until the dust settles a bit and it's clearer on where we stand with the upgrade once it gets released.
Click to expand...
Click to collapse
Will you be able to wait when you see that little notification saying there's a new system update awaiting you?? I'll eat my nails until then!
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
I don't think so....
Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
Bootloader doesn't matter. Root doesn't matter. What does matter is the software on your phone that checks for OTA updates. As long as that is functioning; you will get the notification.
You can ignore the update notification and will not be forced to install it.
Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:
As always, very informative thread @lost101.
lost101 said:
Bootloader doesn't matter. Root doesn't matter. What does matter is the software on your phone that checks for OTA updates. As long as that is functioning; you will get the notification.
You can ignore the update notification and will not be forced to install it.
Click to expand...
Click to collapse
MarckozZ said:
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:
Click to expand...
Click to collapse
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.
Drift0r said:
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.
Click to expand...
Click to collapse
You need stock recovery and rid of xposedand any modules
MarckozZ said:
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:
Click to expand...
Click to collapse
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.
Is stock recovery and stock firmware same? If not how do i get stock recovery back?
S0bes said:
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.
Click to expand...
Click to collapse
How about if you are using Adaway?
I know this will change something to the file hosts.
Do you need to get this original hosts file as well?
Drift0r said:
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.
Click to expand...
Click to collapse
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
S0bes said:
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.
Click to expand...
Click to collapse
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:
MarckozZ said:
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:
Click to expand...
Click to collapse
Almost always it is enough to flash only system img files without erasing userdara. It should rewrite system block so it becames stock
MarckozZ said:
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:
Click to expand...
Click to collapse
How do I restore it to 4.4.3? Im currently downloading this file to flash via mfastboot RET-EU-SS_4.4.3_KXB21.14-L1.31_cid7_CFC_1FF.xml.zip from this guide. http://forum.xda-developers.com/showthread.php?t=2542219 would this work?
my phone moto g 4g lte - xt1039
Drift0r said:
How do I restore it to 4.4.3? Im currently downloading this file to flash via mfastboot RET-EU-SS_4.4.3_KXB21.14-L1.31_cid7_CFC_1FF.xml.zip from this guide. http://forum.xda-developers.com/showthread.php?t=2542219 would this work?
my phone moto g 4g lte - xt1039
Click to expand...
Click to collapse
You can try the guide I've done with some help from other users here at XDA...
http://forum.xda-developers.com/moto-g/general/guide-restore-moto-firmware-gpe-t2914884
Finally ! Straight from Google DEVS
"razor" for Nexus 7 [2013] (Wi-Fi) 5.1.1 (LMY47V)
Thank You
Just flashed it. I wasn't having any issues, but I hope it fixes problems for others.
just lou said:
Just flashed it. I wasn't having any issues, but I hope it fixes problems for others.
Click to expand...
Click to collapse
Can you check if the bootloader is still 04.05 or it changed?
I heard, it is the same
idCyber said:
Can you check if the bootloader is still 04.05 or it changed?
Click to expand...
Click to collapse
Its 4.05 bootloader still. Somehow in the zip its called bootloader-flo-flo-04.05.img
There's a new kernel, some changes in the source. Its compiled March 21
Not much else changed
Has any one got the ota yet ?
@Vkk187
ofc not.
Flash the stock image with NRT and check "dirty flash" and that will not delete your apps and data.
Yet to unlock my BL ...I know it's simple . Will do it some day [emoji18]
AonI updated to 5.1 rooted stock via TWRP a couple weeks ago.
Today I just got this update notification for 5.1
Is today's notification for 5.1.1? Because it only says 5.1
Do we have a rooted stock file we can flash in TWRP?
ymDroid said:
Do we have a rooted stock file we can flash in TWRP?
Click to expand...
Click to collapse
http://forum.xda-developers.com/nex...my47v-root-t3098137/post60479181#post60479181
I just got the 5.1 update. It shows 5.1.1 as the Android version.
Sent from my BN Nook HD using XDA Free mobile app
I just completely flash-all every time a new build comes out as I do not know how to side load using NRT or TWRP (am I wasting my time on doing it this way). If someone could please explain to me how to side load I would be forever grateful. I have searched and cannot find clear instructions or walk through on side loading
Having read wugfresh page,it says Since lollipop,its hard to sideload OTA now. I myself try it last night with my rooted stock recovery,it fails to install the OTA from google,even if file has been downloaded automatically. Its harder to get OTA install smoothly nowadays especially if you on lollipop. No choice had full flash without wipe. And reroot again.
Sent from my Nexus 7
ksloh1 said:
Having read wugfresh page,it says Since lollipop,its hard to sideload OTA now. I myself try it last night with my rooted stock recovery,it fails to install the OTA from google,even if file has been downloaded automatically. Its harder to get OTA install smoothly nowadays especially if you on lollipop. No choice had full flash without wipe. And reroot again.
Sent from my Nexus 7
Click to expand...
Click to collapse
Actually, it's just as easy sideloading as it's always been. The difference is that you can't sideload an OTA (or receive one in any way) if you've done any kind of alterations to the system. This includes rooting and/or flashing custom recoveries and kernels. Even if you unroot there are still residue alterations in your system, meaning you'll have to do a full system flash anyway.
It's worth mentioning that unlocking your bootloader does not prevent installing an OTA.
How is this version running compare to the 5.0?
Jaylex31 said:
How is this version running compare to the 5.0?
Click to expand...
Click to collapse
Any versions of Android on the Nexus 7 2013 ran fine for me.
Just wanted to let you guys know that the 5.1 OTA is rolling out as we speak. My girl's got a German Moto X, and received the OTA today!
She's now on 222.21.15.ghost_row.Retail.en.DE. The build number is LPA23.12-15.
And here I am waiting for it with my Dutch Retail.en.EU version..
tommert38 said:
Just wanted to let you guys know that the 5.1 OTA is rolling out as we speak. My girl's got a German Moto X, and received the OTA today!
She's now on 222.21.15.ghost_row.Retail.en.DE. The build number is LPA23.12-15.
And here I am waiting for it with my Dutch Retail.en.EU version..
Click to expand...
Click to collapse
Can you look to list of languages? Has this OTA Ukrainian language (Українська)?
Unfortunately it doesn't include Ukrainian localization.
Anyone knows where to get this Ota in a rsd lite flashable form?
When we got OTA zip file, then we do RSD one )
---------- Post added at 11:49 PM ---------- Previous post was at 11:43 PM ----------
tommert38 said:
She's now on 222.21.15.ghost_row.Retail.en.DE. The build number is LPA23.12-15
Click to expand...
Click to collapse
Any possibility to get OTA zip?
johnrangoo said:
Anyone knows where to get this Ota in a rsd lite flashable form?
Click to expand...
Click to collapse
you can't flash the OTA via RSDLite.
Someone could try updating via Motorola Device Manager on their PC, and see if an FXZ/SBF comes down that can be captured.
Or if someone who is rooted can download, but not apply the OTA, they can grab the OTA ZIP file from their /cache folder... then you could follow the Side Load instructions from -> http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
That being said.. if this is a SOAK being performed, it shouldn't be long until it starts being pushed to all users of that model. Of course it will come in waves, so once the official push to that model comes, it may take up to a week until it hits all phones.
And anyone who takes part in the MFN tests would be violating the NDA they signed to take part, if they leak the file. Moto got the links to prior leaks removed, so it stands to reason they might do the same for other leaks.
KidJoe said:
you can't flash the OTA via RSDLite.
Someone could try updating via Motorola Device Manager on their PC, and see if an FXZ/SBF comes down that can be captured.
Or if someone who is rooted can download, but not apply the OTA, they can grab the OTA ZIP file from their /cache folder... then you could follow the Side Load instructions from -> http://forum.xda-developers.com/moto-x/general/ref-return-to-stock-recovery-rooted-t3027079
That being said.. if this is a SOAK being performed, it shouldn't be long until it starts being pushed to all users of that model. Of course it will come in waves, so once the official push to that model comes, it may take up to a week until it hits all phones.
And anyone who takes part in the MFN tests would be violating the NDA they signed to take part, if they leak the file. Moto got the links to prior leaks removed, so it stands to reason they might do the same for other leaks.
Click to expand...
Click to collapse
You should flash full FW by RSD, not OTA.
md07 said:
You should flash full FW by RSD, not OTA.
Click to expand...
Click to collapse
Which is what I said...
I think maybe you should have quoted @johnrangoo who asked the question...
KidJoe said:
Which is what I said...
I think maybe you should have quoted @johnrangoo who asked the question...
Click to expand...
Click to collapse
I stay tuned.. because I have a German Retail Moto X.. the ota zip is flashable via stock recovery.. right?
I have a question.. there is a safe way to downgrade to stock kitkat (just in case)?
bart.found said:
I stay tuned.. because I have a German Retail Moto X.. the ota zip is flashable via stock recovery.. right?
I have a question.. there is a safe way to downgrade to stock kitkat (just in case)?
Click to expand...
Click to collapse
Yes, the OTA zip must be flashed from Stock Recovery. And there are also some other conditions. See -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425
As for downgrade... It is always suggested to never downgrade. If you downgrade, you risk bricking. see -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
KidJoe said:
Yes, the OTA zip must be flashed from Stock Recovery. And there are also some other conditions. See -> http://forum.xda-developers.com/moto-x/general/faq-how-to-prepare-ota-update-carriers-t3126425
As for downgrade... It is always suggested to never downgrade. If you downgrade, you risk bricking. see -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202
Click to expand...
Click to collapse
OMG it's a huge amount of informations!! If I understood, even if I have a retail version with unlockable bootloader, it is impossible to revert to a stock old version without the risk of a (hard)brick!!! :S
Does exist, at least, a stock rom flashable through custom recovery on newer bootloader versions? Or, alternatively, custom ROMs that are able to properly use the particular hardware of this device (without losing all its smart features?)
Thanks for the reply... I'll read it more carefully later
bart.found said:
...If I understood, even if I have a retail version with unlockable bootloader, it is impossible to revert to a stock old version without the risk of a (hard)brick!!! :S
Click to expand...
Click to collapse
Correct.
bart.found said:
Does exist, at least, a stock rom flashable through custom recovery on newer bootloader versions? Or, alternatively, custom ROMs that are able to properly use the particular hardware of this device (without losing all its smart features?)
Thanks for the reply... I'll read it more carefully later
Click to expand...
Click to collapse
As of yet, for Lollipop. No. What exists are "backups" of LEAKED test versions of Lollipop for other models and carriers. (Brazil XT1058 for example)
When the OTA finally pushes, you'll need to be stock, and on stock recovery to apply it.. OR wait for someone to create something like a "backup" which you can restore in TWRP, or a custom rom version BASED on the stock rom.
Keep in mind, that unless you apply the stock OTA which is pushed by your carrier/motorola, you might miss parts that get updated. In other words, the TWRP BACKUPS of the leaked test versions only include the /System partition. It does not include the partition table file, the bootloader, the modems, etc. and the other parts that are updated by the OTA.
KidJoe said:
Correct.
As of yet, for Lollipop. No. What exists are "backups" of LEAKED test versions of Lollipop for other models and carriers. (Brazil XT1058 for example)
When the OTA finally pushes, you'll need to be stock, and on stock recovery to apply it.. OR wait for someone to create something like a "backup" which you can restore in TWRP, or a custom rom version BASED on the stock rom.
Keep in mind, that unless you apply the stock OTA which is pushed by your carrier/motorola, you might miss parts that get updated. In other words, the TWRP BACKUPS of the leaked test versions only include the /System partition. It does not include the partition table file, the bootloader, the modems, etc. and the other parts that are updated by the OTA.
Click to expand...
Click to collapse
My phone is stock unrooted with locked bootloader in this moment.. I think I'll wait for OTA or, at most, sideload the correct OTA for my model and flash it through stock recovery.
My question was if exist a stock KitKat firmware flashable through custom recovery over Lollipop bootloader!! Just in case I'd like to revert without losing any feature!
Thank you!
bart.found said:
My phone is stock unrooted with locked bootloader in this moment.. I think I'll wait for OTA or, at most, sideload the correct OTA for my model and flash it through stock recovery.
My question was if exist a stock KitKat firmware flashable through custom recovery over Lollipop bootloader!! Just in case I'd like to revert without losing any feature!
Thank you!
Click to expand...
Click to collapse
Why take OTA if you can just install a TWRP-backup of Lollipop... only then u can downgrade without the risk of bricking your device.
bart.found said:
My phone is stock unrooted with locked bootloader in this moment.. I think I'll wait for OTA or, at most, sideload the correct OTA for my model and flash it through stock recovery.
My question was if exist a stock KitKat firmware flashable through custom recovery over Lollipop bootloader!! Just in case I'd like to revert without losing any feature!
Thank you!
Click to expand...
Click to collapse
If you are LOCKED BOOTLOADER, you can't run a custom recovery on the 2013 X. So that question is No, you can't.
And as for downgrading, Please DO NOT!! Instead, Read that entire thread, trust me, it explains why I say that.
KidJoe said:
If you are LOCKED BOOTLOADER, you can't run a custom recovery on the 2013 X. So that question is No, you can't.
And as for downgrading, Please DO NOT!! Instead, Read that entire thread, trust me, it explains why I say that.
Click to expand...
Click to collapse
I finally read everything!!!
What I understand:
1) NEVER downgrade your bootloader or your stock firmware! If you don't want to brick immediately or later XD
What I didn't understand:
1) I have a German retail moto x xt1052.. can I unlock my bootloader, root and flash custom recovery/firmware? I suppose yes, even if my device isn't listed on motorola official page (can I use sunshine or other methods?)
2) Does any custom ROM, able to use all moto x features like touchless control or lift to wake etc, exist? Because I noticed that most custom ROMs aren't able to use that features (probably due to the lack of binaries), at least on lollipop.. I don't know if CM11 or slimkat or other AOSP based or stock based rom can properly use that damn X8 processor!
Thank you.. and sorry for bothering you so much, but I don't really want to damage my device!!!
bart.found said:
I finally read everything!!!
What I understand:
1) NEVER downgrade your bootloader or your stock firmware! If you don't want to brick immediately or later XD
Click to expand...
Click to collapse
Correct.
bart.found said:
What I didn't understand:
1) I have a German retail moto x xt1052.. can I unlock my bootloader, root and flash custom recovery/firmware? I suppose yes, even if my device isn't listed on motorola official page (can I use sunshine or other methods?)
2) Does any custom ROM, able to use all moto x features like touchless control or lift to wake etc, exist? Because I noticed that most custom ROMs aren't able to use that features (probably due to the lack of binaries), at least on lollipop.. I don't know if CM11 or slimkat or other AOSP based or stock based rom can properly use that damn X8 processor!
Thank you.. and sorry for bothering you so much, but I don't really want to damage my device!!!
Click to expand...
Click to collapse
1. The XT1052 could get its bootloader unlock code direct from Moto. After unlocking the bootloader you can flash customer recovery, root, and/or flash a 3rd party custom rom.
2. Any custom rom built on TOP of Moto's stock rom, could still retain those stock moto features. AOSP based roms, CM11/12 based roms, etc. will not include the stock moto features. However they may include 3rd party apps which mimic those features, but might not work as well.
Does 5.1 include hebrew language support as in 4.4.4?
amarguli said:
Does 5.1 include hebrew language support as in 4.4.4?
Click to expand...
Click to collapse
If the stock Moto rom for your carrier/model X includes it, then yes, 5.1 update should include it as well.
I want to have 4.4.4 back instead of the ota given 5.1 update. Is there a nearly unmodified xt1052 stock 4.4.4 flashable with trwp?
I have a US XT1687 on LineageOS (2017-09-19 build), and I would like to flash the latest stock firmware (which I believe is the April NPNS25.137-93-10 update), while also continuing to receive future OTA updates
The fastboot stock firmware thread was closed.
I found these files https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ but I don't see the 93-10 update.
Can I flash the 93-4 update from that site via fastboot and then get the 93-10 update via OTA?
Thanks!
I believe it depends on what bootloader version you were on before. If you were on 93-4 or earlier, then theoretically you should be fine. If you were on the 93-10 version of the bootloader and attempted to flash to the 93-4 stock rom, and then take an OTA from there, you are very likely going to hard-brick your device.
There are a lot of active threads about flashing back to stock and losing IMEI and enhanced LTE, so I wouldn't risk it. Out of curiosity why would you want to flash back to stock Nougat? IMO the camera is worse and you're rolling back to an older OS.
dunderball said:
I believe it depends on what bootloader version you were on before. If you were on 93-4 or earlier, then theoretically you should be fine. If you were on the 93-10 version of the bootloader and attempted to flash to the 93-4 stock rom, and then take an OTA from there, you are very likely going to hard-brick your device.
There are a lot of active threads about flashing back to stock and losing IMEI and enhanced LTE, so I wouldn't risk it. Out of curiosity why would you want to flash back to stock Nougat? IMO the camera is worse and you're rolling back to an older OS.
Click to expand...
Click to collapse
I'm actually still on Nougat. The last time I flashed a new ROM was back in September (the LineageOS build I'm using is from 2017-09-19). So my bootloader is likely whatever the latest one was around that time.
From what I read, it seemed like people were losing their IMEI and VoLTE after flashing 8.1 custom ROMs, which I haven't done, so I figured I was safe. Maybe I'm misunderstanding?
Yousie642 said:
I'm actually still on Nougat. The last time I flashed a new ROM was back in September (the LineageOS build I'm using is from 2017-09-19). So my bootloader is likely whatever the latest one was around that time.
From what I read, it seemed like people were losing their IMEI and VoLTE after flashing 8.1 custom ROMs, which I haven't done, so I figured I was safe. Maybe I'm misunderstanding?
Click to expand...
Click to collapse
Ah I wasn't aware that you were on a nougat version of LOS. I would still back up all partitions just in case.
dunderball said:
Ah I wasn't aware that you were on a nougat version of LOS. I would still back up all partitions just in case.
Click to expand...
Click to collapse
Is that different from doing a NAND backup in TWRP?
Yousie642 said:
Is that different from doing a NAND backup in TWRP?
Click to expand...
Click to collapse
Nope it's the same.
Yousie642 said:
I have a US XT1687 on LineageOS (2017-09-19 build), and I would like to flash the latest stock firmware (which I believe is the April NPNS25.137-93-10 update), while also continuing to receive future OTA updates
The fastboot stock firmware thread was closed.
I found these files https://mirrors.lolinet.com/firmware/moto/potter/official/RETAIL/ but I don't see the 93-10 update.
Can I flash the 93-4 update from that site via fastboot and then get the 93-10 update via OTA?
Thanks!
Click to expand...
Click to collapse
Here's a mirror of the 93-10 firmware, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud but not everyone was able to download it from there.
If you changed to a custom rom in September 2017 you should have been on August security patch which is the firmware NPNS25.137-33-11.
But you should be good to go with 93-10.
As written above make sure to have a full nandroid, especially of EFS.
Sent from my Moto G5 Plus using XDA Labs
dunderball said:
Nope it's the same.
Click to expand...
Click to collapse
Wolfcity said:
Here's a mirror of the 93-10 firmware, it can be found in this thread.
https://drive.google.com/file/d/16Bfp3nVfvKMURAeKagOaOImX-lvJrYBF/view?usp=drivesdk
The source is the Motorola secure cloud but not everyone was able to download it from there.
If you changed to a custom rom in September 2017 you should have been on August security patch which is the firmware NPNS25.137-33-11.
But you should be good to go with 93-10.
As written above make sure to have a full nandroid, especially of EFS.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
Thanks dudes! I actually found my old adb folder and saw I had the files for NPN25.137-83 extracted there, so I'm pretty sure that's what I'm on. Seems like it still won't be an issue though.
What I am worried about now is losing VoLTE if I ever decide to go back to a custom ROM. Though, from what I understand, as long as I have an EFS backup, I can fix it. Is that right?
Yep you should be fine. I didn't have issues when going from stock to custom. Still -- I'd try out an Oreo rom before jumping back to stock.
dunderball said:
Yep you should be fine. I didn't have issues when going from stock to custom. Still -- I'd try out an Oreo rom before jumping back to stock.
Click to expand...
Click to collapse
Y'know, it didn't actually occur to me, and this may be a silly question, but now I'm wondering if there's actually any need to run a stock firmware update before going to newer custom ROMs? The reason I ask is because this was a thing with my Nexus 5x. Newer LineageOS builds sometimes needed a bootloader and radio update.