Can we update phone's software via ota even after unlocking the boot loader and installing custom recovery
Nooooooooooooooooo
No, Not even in your dreams,
From what I've learned from my own Issue
http://forum.xda-developers.com/moto-x/moto-x-qa/totally-screwed-updating-rooted-x-4-4-4-t2896292
Never update phone's software via ota, while you are on Custom Recovery.
Patel21 is correct, you can't with a custom recovery.
You need stock recovery to take the OTA, then you can reinstall a custom recovery
m.ryuu said:
Can we update phone's software via ota even after unlocking the boot loader and installing custom recovery
Click to expand...
Click to collapse
Yes you can as long as you flash back to stock recovery before accepting the OTA. Once done, flash custom recovery and root if lost.
m.ryuu said:
Can we update phone's software via ota even after unlocking the boot loader and installing custom recovery
Click to expand...
Click to collapse
OTA will not install when you have a custom recovery on your phone. Instead you'll be stuck in a bootloop if you have tried to install an OTA with a custom recovery.
Rather than my retyping everything... Please see -> http://mark.cdmaforums.com/MotoX-OTA.html
I've flashed ota updates via custom recovery, you just have to know what you're doing. Also, the Moto boot loader won't relock as far as I know after an update. It doesn't on the Dev edition, not sure about unlocked retail or devices that have been unlocked with sunshine.
Sent from my Moto X
Since all unlocked devices are the same as the dev edition....the same would be true.
KJ said:
Since all unlocked devices are the same as the dev edition....the same would be true.
Click to expand...
Click to collapse
The only thing I want sure of was sunshine. If you unlocked via a code, then yes, all of them act the same.
Sent from my Moto X
imnuts said:
I've flashed ota updates via custom recovery, you just have to know what you're doing. Also, the Moto boot loader won't relock as far as I know after an update. It doesn't on the Dev edition, not sure about unlocked retail or devices that have been unlocked with sunshine.
Sent from my Moto X
Click to expand...
Click to collapse
I don't completely understand how Sunshine works, so I can't say for sure, however based on reading the thread, my understanding is it wont relock.
But if you unlock via mfastboot oem unlock {YourUniqueCode} your bootloader will not relock itself. This holds true for developer and non-developer alike.
Someone pls post a Link to stock recovery
m.ryuu said:
Someone pls post a Link to stock recovery
Click to expand...
Click to collapse
It's in the sbf for your phone/carrier/version.
4.4.4 version Asia retail not there
m.ryuu said:
4.4.4 version Asia retail not there
Click to expand...
Click to collapse
Have you checked -> http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=25 too?
Is it possible to get custom roms on xperia play r800i locked boot loader. Running gin2kat android 2.3.7.
Related
I have rooted every phone i've had and for some reason the MOTO X is confusing me! The phone is a bone stock developers Ed. 4.2.2 pre camera.
I am confused as to which jcase method to use or if there is another option.
I am guessing PwnMyMoto 1.4.3 verizon. but i'm not sure.
Any help would be fantastic.
Thanks,
J
ejason said:
I have rooted every phone i've had and for some reason the MOTO X is confusing me! The phone is a bone stock developers Ed. 4.2.2 pre camera.
I am confused as to which jcase method to use or if there is another option.
I am guessing PwnMyMoto 1.4.3 verizon. but i'm not sure.
Any help would be fantastic.
Thanks,
J
Click to expand...
Click to collapse
PwnMyMoto and jcase's methods are for locked bootloaders. You first need to unlock your bootloader. Then you need to decide if you want to take the OTA to 4.4 or not because once you upgrade to 4.2.2 post-camera, you can never downgrade to 4.2.2 pre-camera without bricking your device.
If you want to upgrade to 4.4, here are the instructions to unlock and gain root:
[STEP-BY-STEP INSTRUCTIONS] Unlocking and Rooting a Dev Ed Moto X Running Kit Kat
I have read of others who kept the 4.2.2 bootloader and other partitions and just selectively flashed those partitions they wanted as each new upgrade's sbf firmware was released. I don't know what advantages there are to doing that.
ejason said:
I have rooted every phone i've had and for some reason the MOTO X is confusing me! The phone is a bone stock developers Ed. 4.2.2 pre camera.
I am confused as to which jcase method to use or if there is another option.
I am guessing PwnMyMoto 1.4.3 verizon. but i'm not sure.
Any help would be fantastic.
Thanks,
J
Click to expand...
Click to collapse
It's a Developer Edition. Take all the updates available (4.2.2 camera update, 4.4 and now 4.4.2). Get the unlock code from Motorola and unlock your bootloader. Once that is done, flash twrp recovery and then install root via twrp.
Very simple on Dev Editions just because you can unlock the bootloader and flash an alternate recovery (twrp, cwm, etc..).
I agree. Unlock your bootloader (Doesn't void warranty on Developer Edition), flash TWRP recovery, then boot to TWRP and install/flash SuperSU. And it doesn't matter what ROM version you're running. (there is a TWRP for 4.2.2 and one for 4.4/4.4.2).
As mentioned, the bootloader included in the android versions can prevent you from downgrading the rom version. (i.e. bootloader in 4.4.2 prevents you from downgrading to any previous ROM). Why would you want to downgrade? If you have a locked bootloader, you'd want to downgrade to be able to use the root processes needed when you have a locked bootloader. But if you have an unlocked bootloader, because you can flash an alternate recovery (not possible with locked bootloader) and root no matter what ROM version you have installed, the only reason to downgrade would be if you encounter a bug you can't deal with that isn't present in the older roms.
because 4.4.2 fixes the exchange and bluetooth issues, and doesn't introduce anything new, its suggested you update to 4.4.2 if you have an unlocked boot loader (4.4.2 isn't rootable on locked bootloaders and may not be, so its recommended that those with locked bootloaders who want to root stick with 4.4).
KidJoe said:
I agree. Unlock your bootloader (Doesn't void warranty on Developer Edition), flash TWRP recovery, then boot to TWRP and install/flash SuperSU. And it doesn't matter what ROM version you're running. (there is a TWRP for 4.2.2 and one for 4.4/4.4.2).
I didn't know there was a different TWRP for 4.2.2.
As mentioned, the bootloader included in the android versions can prevent you from downgrading the rom version. (i.e. bootloader in 4.4.2 prevents you from downgrading to any previous ROM). Why would you want to downgrade? If you have a locked bootloader, you'd want to downgrade to be able to use the root processes needed when you have a locked bootloader. But if you have an unlocked bootloader, because you can flash an alternate recovery (not possible with locked bootloader) and root no matter what ROM version you have installed, the only reason to downgrade would be if you encounter a bug you can't deal with that isn't present in the older roms.
because 4.4.2 fixes the exchange and bluetooth issues, and doesn't introduce anything new, its suggested you update to 4.4.2 if you have an unlocked boot loader (4.4.2 isn't rootable on locked bootloaders and may not be, so its recommended that those with locked bootloaders who want to root stick with 4.4).
Click to expand...
Click to collapse
From what i have read 4.4.2 isn't rootable at all. Even if you have an unlocked bootloader. Is that correct?
Great info, thanks.
I thought that the Verizon DE already had an unlocked bootloader? Or is it like an HTC where i have to go the the MOTOROLA webite and get a code?
I did something like that for an HTC ONE i have on straight talk. I unlocked the bootloader from the HTC website, then installed TWRP, and then rooted and its running a 4.4.2 ROM that is great.
ejason said:
From what i have read 4.4.2 isn't rootable at all. Even if you have an unlocked bootloader. Is that correct?
Click to expand...
Click to collapse
Incorrect. You can do whatever you want with the DE, regardless of what version of Android you're on.
Sent from my Moto X
ejason said:
I thought that the Verizon DE already had an unlocked bootloader? Or is it like an HTC where i have to go the the MOTOROLA webite and get a code?
Click to expand...
Click to collapse
There are directions on a 1 page pamphlet that came with your VZW DE on how to unlock the bootloader.
Sent from my Dev Edition Moto X
ejason said:
I thought that the Verizon DE already had an unlocked bootloader? Or is it like an HTC where i have to go the the MOTOROLA webite and get a code?
Click to expand...
Click to collapse
It is all in that step-by-step link I gave you above.
Ok, so i have my phone unlocked, updated to 4.4 and for some reason i can not flash the TWRP.
I get the error (bootloader) variable not supported!
Any ideas.
I have tried both mfastboot and fastboot and i get nothing.
I also moved all files into another folder and CD into that folder and still the same error.
Can i install the TWRP with goo manager?
ejason said:
Ok, so i have my phone unlocked, updated to 4.4 and for some reason i can not flash the TWRP.
I get the error (bootloader) variable not supported!
Any ideas.
I have tried both mfastboot and fastboot and i get nothing.
I also moved all files into another folder and CD into that folder and still the same error.
Can i install the TWRP with goo manager?
Click to expand...
Click to collapse
did it finish flashing? mine says that when i flash a recovery also, but it flashes.
after you flash it dont reboot, just go into recovery (volume down to move the selection, volume up to execute)
then select reboot system, and it will ask if you want to root.
ejason said:
ok, so i have my phone unlocked, updated to 4.4 and for some reason i can not flash the twrp.
I get the error (bootloader) variable not supported!
Any ideas.
I have tried both mfastboot and fastboot and i get nothing.
I also moved all files into another folder and cd into that folder and still the same error.
Can i install the twrp with goo manager?
Click to expand...
Click to collapse
ok, thanks for everyones hellp. Done and done..
I haven't don it yet getting all the info I need before hand.
1) After I unlock the bootloader will I be able to flash the most recent update for 4.4.4 or will I just be able to unfreeze the OTA and still keep root?
2) If I loose root since I now have an unlocked bootloader I'm just a SuperSU flash away from root, right?
3) Since I'm still on 4.4.2 will I have any issues if I need to flash back to it?
Anything else I might have missed that is important either from mistakes or just general knowledge I missed would be appreciated. Thanks and Good Night everybody!
Icon000 said:
I haven't don it yet getting all the info I need before hand.
1) After I unlock the bootloader will I be able to flash the most recent update for 4.4.4 or will I just be able to unfreeze the OTA and still keep root?
Click to expand...
Click to collapse
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
2) If I loose root since I now have an unlocked bootloader I'm just a SuperSU flash away from root, right?
Click to expand...
Click to collapse
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
3) Since I'm still on 4.4.2 will I have any issues if I need to flash back to it?
Click to expand...
Click to collapse
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.
tcrews said:
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.
Click to expand...
Click to collapse
Great explanation! :good:
tcrews said:
After you unlock the bootloader, treat your device like a developer edition. I would just flash the full 4.4.4 image files for your device to bring it up to the latest version without worry of it failing because of modifications you may have made to the system (root, etc..).
With an unlocked bootloader you can flash an alternate recovery like CWM or TWRP. These recoveries will allow you to flash SuperSU to gain root.
Just like every other Motorola device (developer or not), you can not flash backwards. If you move to 4.4.4 you can NOT go back to 4.4.2.
Click to expand...
Click to collapse
Why do you recommend flashing 4.4.4 over accepting the OTA? I still want to be able to use the additions originally provided by Motorola. I didn't seen a rom built on Moto Stock. Did I miss it?
Flash the stock 4.4.4 ROM that is for your device.
What's better...4.4.2 with patches to make it 4.4.4 (via an OTA) or just the full 4.4.4 (via the full 4.4.4 install) without the need for patching to make it 4.4.4?
Oh well...it looks like there isn't a FULL 4.4.4 for AT&T Moto X released yet....just 4.4.2. Flash the full 4.4.2 then take the OTA update to 4.4.4 and then flash TWRP to get root.
AT&T 4.4.2
http://sbf.droid-developers.org/download.php?device=0&file=849
You can just flash the system.img from the download with mfastboot to revert any changes you did (root, etc..) so that the OTA can be installed successfully. You'll just want to get fully updated before flashing an alternative recovery like TWRP.
I have unlocked bootloader, flashed Custom Recovery TWRP to my Moto G2 XT1068 and rooted on 4.4.4 stock, while waiting for the official lollipop updates.
So does this break the OTA, and if so how to enable it again?!
Yes you don't get official Lollipop OTA if you unlock your bootloader. For getting official OTA you have to unroot ur phone and relock the bootloader
sumit227 said:
Yes you don't get official Lollipop OTA if you unlock your bootloader. For getting official OTA you have to unroot ur phone and relock the bootloader
Click to expand...
Click to collapse
Okay, understood. thanks mate
And a few threads along the road you will read:Just do a full unroot and reflash stock recovery,unlocked bootloader is no problem for capturing OTA.
I don't know.....
Sent from my XT1068 using XDA Free mobile app
Rooting didnt affect OTA with my old moto g upgrading from 4.4.2 to 4.4.4 and probably wont affect the new moto g too
epivitor said:
Rooting didnt affect OTA with my old moto g upgrading from 4.4.2 to 4.4.4 and probably wont affect the new moto g too
Click to expand...
Click to collapse
No. You will receive ota but you can't install it. For root to work, /system has to be modified. The OTA-package will recognize this and refuses to install.
sumit227 said:
Yes you don't get official Lollipop OTA if you unlock your bootloader. For getting official OTA you have to unroot ur phone and relock the bootloader
Click to expand...
Click to collapse
Also not true. OTA does not require a relock. Only unroot and stock-recovery is required.
Wolfcity said:
And a few threads along the road you will read:Just do a full unroot and reflash stock recovery,unlocked bootloader is no problem for capturing OTA.
I don't know.....
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
Yes, because it is a fact.
doppelhelix said:
Also not true. OTA does not require a relock. Only unroot and stock-recovery is required.
Click to expand...
Click to collapse
Wolfcity said:
And a few threads along the road you will read:Just do a full unroot and reflash stock recovery,unlocked bootloader is no problem for capturing OTA.
I don't know.....
Click to expand...
Click to collapse
Oh my bad sorry, for OTA we don't need to relock I think relock is for regain the warranty correct me if I'm wrong.
Thanks for the answers guys.
Now why the heck i can't relock the bootloader whatever i do?! did anyone successfully relocked the bootloader before, and if so. how?!
i've followed all the guides around and it always give me errors and i can't flash rom!!
and in fact isnt really any useful to relock it?!
solly84 said:
it always give me errors and i can't flash rom!!
Click to expand...
Click to collapse
That's a bit vague. Please post exactly the output on your screen.
doppelhelix said:
That's a bit vague. Please post exactly the output on your screen.
Click to expand...
Click to collapse
sure!
seems like i cant relock my bootloader, whenever i do all the sequence of flashing the stock rom without the "oem lock begin" everything goes smoothly and i can restore to stock image.
as soon as i put "oem lock begin" i got a error in boot.img:
bootloader preflash validation failed
bootloader invalid signed image
and it doesn't continue...
solly84 said:
bootloader preflash validation failed
bootloader invalid signed image
Click to expand...
Click to collapse
Maybe the rom currently installed and the rom you try to flash and lock are not the same. Or, at one point you installed a rom that had a version above your current one. There are some partitions that can't be downgraded, like gpt and motoboot (which is the bootloader). Subsequently the lock will fail. Anyway, locking the bootloader is absolutely not necessary. There is no benefit in doing so.
doppelhelix said:
Maybe the rom currently installed and the rom you try to flash and lock are not the same. Or, at one point you installed a rom that had a version above your current one. There are some partitions that can't be downgraded, like gpt and motoboot (which is the bootloader). Subsequently the lock will fail. Anyway, locking the bootloader is absolutely not necessary. There is no benefit in doing so.
Click to expand...
Click to collapse
Yeah, i had tried a lot of Roms, so maybe that is why. And now i am on Custom Lollipop Rom (Titan)...
but eventually as you said, its not necessary, so i will just forget about it.
Thanks man.
Hello everyone, I'm new here, my nexus 6 is on stock 5.0.1 and waiting for update to 5.1, here are my concerns.
1. How can I root my phone without unlock boot loader or flash a twrp recovery( I Know if I got a twrp recovery, I can not get OTA).
2. If I need unlock boot loader in order to root, could this affect ota?
3. If I rooted my phone, can I get ota in the future?
Thanks.
Dennypalace said:
Hello everyone, I'm new here, my nexus 6 is on stock 5.0.1 and waiting for update to 5.1, here are my concerns.
1. How can I root my phone without unlock boot loader or flash a twrp recovery( I Know if I got a twrp recovery, I can not get OTA).
2. If I need unlock boot loader in order to root, could this affect ota?
3. If I rooted my phone, can I get ota in the future?
Thanks.
Click to expand...
Click to collapse
1. You can't 2. No can be unlocked and still do the ota 3. YES!
nms247 said:
1. You can't 2. No can be unlocked and still do the ota 3. YES!
Click to expand...
Click to collapse
Thanks. So this means if I want to root my phone, I will have to unlock boot loader. And is there anything I can do if I want to update through OTA after I rooted and unlocked my phone?
Dennypalace said:
Thanks. So this means if I want to root my phone, I will have to unlock boot loader. And is there anything I can do if I want to update through OTA after I rooted and unlocked my phone?
Click to expand...
Click to collapse
As long as you flash the stock recovery before an ota you'll be fine
Actually any system modification including root on Lollipop will prevent an OTA so in answer to question 3, no.
Basically need to flash stock system.img, recovery.img and stock boot (if you changed the kernel).
At least thats what I'm about to do.
y2whisper said:
Basically need to flash stock system.img, recovery.img and stock boot (if you changed the kernel).
At least thats what I'm about to do.
Click to expand...
Click to collapse
Correct. That's exactly what I did, and it worked.
rootSU said:
Actually any system modification including root on Lollipop will prevent an OTA so in answer to question 3, no.
Click to expand...
Click to collapse
Weird as I took the OTA while rooted.
Still working on it on my end. Drivers aren't installed for add sideboard trying to figure it out
Hi I got a bit excited and unlocked bootloader and root and have twrp now but now I want to flash an ota to 5.1 bit it seems I can't is this correct?
Or someone shed some light on the process I have the European xt1092
I presume I have to go back fully stock and just flash in stock recovery while unroofed and still have bootloader unlocked
gavin-phelan said:
Hi I got a bit excited and unlocked bootloader and root and have twrp now but now I want to flash an ota to 5.1 bit it seems I can't is this correct?
Or someone shed some light on the process I have the European xt1092
I presume I have to go back fully stock and just flash in stock recovery while unroofed and still have bootloader unlocked
Click to expand...
Click to collapse
Yep.OTA means no system modification,AFAIK.
gavin-phelan said:
Hi I got a bit excited and unlocked bootloader and root and have twrp now but now I want to flash an ota to 5.1 bit it seems I can't is this correct?
Or someone shed some light on the process I have the European xt1092
I presume I have to go back fully stock and just flash in stock recovery while unroofed and still have bootloader unlocked
Click to expand...
Click to collapse
I had to go completely stock to flash the ota and my boot loader is still unlocked