[Q] [XT1068] [Stock 4.4.4] Does Rooting and custom recovery break the OTA?! - G 2014 Q&A, Help & Troubleshooting

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.

Related

Update for unlocked bootloader

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.

Error on update

Updating from 5.0 to 5.0.1 I got a message that said "error" during the reboot and install phase. I had to manually shut down the phone and reboot. After the reboot, I noticed that there was no update available and my phone is still on 5.0. I've only unlocked the bootloader and does with CF. No custom recovery or rom.
Sent from my Nexus 6 using XDA Free mobile app
You used CF so if you rooted it wont work.
As stated in the other threads, you cannot update if you have root. You need to unroot. The update notification will eventually pop up again,
Hand76 said:
You used CF so if you rooted it wont work.
Click to expand...
Click to collapse
PaisanNYC said:
As stated in the other threads, you cannot update if you have root. You need to unroot. The update notification will eventually pop up again,
Click to expand...
Click to collapse
Ah okay I didn't realize that. Thanks for the info!
Sent from my Nexus 6 using XDA Free mobile app
I'm not rooted, I just have decrypted and I get the error.
Aston Martin said:
I'm not rooted, I just have decrypted and I get the error.
Click to expand...
Click to collapse
Same issue - any change to the kernel or system files is going to cause this issue. You need to be completely stock (having the bootloader unlocked is not an issue)
n00b question: I have mine unlocked and rooted; how should I go about getting this update?
TheLegendary87 said:
n00b question: I have mine unlocked and rooted; how should I go about getting this update?
Click to expand...
Click to collapse
Unroot relock boot loader which will while everything again and apply update
ryuken11221 said:
Unroot relock boot loader which will while everything again and apply update
Click to expand...
Click to collapse
Did you mean "...which will wipe everything again..." ? If so, that's really not what I wanted to hear, haha.
TheLegendary87 said:
Did you mean "...which will wipe everything again..." ? If so, that's really not what I wanted to hear, haha.
Click to expand...
Click to collapse
yeah lol i know its hard to hear
ryuken11221 said:
yeah lol i know its hard to hear
Click to expand...
Click to collapse
Found this thread which walks you through the update process without having to wipe your data. Worked perfectly.
TheLegendary87 said:
n00b question: I have mine unlocked and rooted; how should I go about getting this update?
Click to expand...
Click to collapse
You need to get stock before taking any OTA (bootloader being unlocked doesn't cause any issues with update). You can either download factory images for 5.0 and flash those (skip userdata.img if you don't want to lose data), and then take OTA, OR, do it the easier way - download factory images for 5.0.1 and flash those (skip userdata.img to avoid losing data)
ryuken11221 said:
Unroot relock boot loader which will while everything again and apply update
Click to expand...
Click to collapse
huh? why relock bootloader? And that's not going to fix the issue with the modified system files
jj14 said:
You need to get stock before taking any OTA (bootloader being unlocked doesn't cause any issues with update). You can either download factory images for 5.0 and flash those (skip userdata.img if you don't want to lose data), and then take OTA, OR, do it the easier way - download factory images for 5.0.1 and flash those (skip userdata.img to avoid losing data)
Click to expand...
Click to collapse
Exactly what I did following the guidence in this thread: http://forum.xda-developers.com/nexus-6/help/help-5-01-wipe-t2970924

[Q] Upgrading from 5.0>5.1

Is it okay to flash the newest image (LMY74I) coming from LMY47O? I won't do any harm in skipping 5.0.1 will I?
Fastboot or recovery? Stock or custom rom? Best to fastboot the updated bootloader and radio if you are updating via custom recovery. I run stock and fastboot bootloader, radio, and system. Boot into recovery and then reboot. Before it reboots you will be prompted to install root. I use this updating method to keep my apps and settings.
mymusicathome said:
Fastboot or recovery? Stock or custom rom? Best to fastboot the updated bootloader and radio if you are updating via custom recovery. I run stock and fastboot bootloader, radio, and system. Boot into recovery and then reboot. Before it reboots you will be prompted to install root. I use this updating method to keep my apps and settings.
Click to expand...
Click to collapse
That didn't answer my question. I'm wondering if I can skip 5.0.1 stock and go straight to 5.1 still stock.
Forerunner326 said:
That didn't answer my question. I'm wondering if I can skip 5.0.1 stock and go straight to 5.1 still stock.
Click to expand...
Click to collapse
He couldn't answer your question because you were too vague. And still are.. What method are you using (now we know you're stock)? And will you be remaining unrooted?
rootSU said:
He couldn't answer your question because you were too vague. And still are.. What method are you using (now we know you're stock)? And will you be remaining unrooted?
Click to expand...
Click to collapse
Unrooted, stock, 5.0 LMY47O to 5.1 LMY47I still stock and unrooted. I am sorry for the confusion.
Forerunner326 said:
Unrooted, stock, 5.0 LMY47O to 5.1 LMY47I still stock and unrooted. I am sorry for the confusion.
Click to expand...
Click to collapse
If you're planning on unlocking the bootloader and flashing the full factory image then yes I that should be fine. Just a word of caution, relocking the bootloader has left some people in a bad place so do ensure if you just relock, that your phone is fully working and booting before hand.
rootSU said:
If you're planning on unlocking the bootloader and flashing the full factory image then yes I that should be fine. Just a word of caution, relocking the bootloader has left some people in a bad place so do ensure if you just relock, that your phone is fully working and booting before hand.
Click to expand...
Click to collapse
Is this because oem unlocking was unchecked for those people?
rootSU said:
If you're planning on unlocking the bootloader and flashing the full factory image then yes I that should be fine. Just a word of caution, relocking the bootloader has left some people in a bad place so do ensure if you just relock, that your phone is fully working and booting before hand.
Click to expand...
Click to collapse
Even if the device is rooted, all it will do is cause root to be lost correct?
Forerunner326 said:
Is this because oem unlocking was unchecked for those people?
Click to expand...
Click to collapse
See this post on relocking instructions:
http://forum.xda-developers.com/showthread.php?p=59699095
Forerunner326 said:
Even if the device is rooted, all it will do is cause root to be lost correct?
Click to expand...
Click to collapse
Yes but if its rooted, you'll never get OTA, so there's no point flashing the entire factory image.
If you flash the entire factory image and dont root, you'll get ota in future.
Though, I'm guessing g you'll be impatient anyway so its will be irrelevant. In which case since you'll probably just want to flash yourself and be rooted, why bother flashing the entire factory image? You dont need to flash recovery or bootloader... Just flash radio, system and boot.
rootSU said:
Yes but if its rooted, you'll never get OTA, so there's no point flashing the entire factory image.
If you flash the entire factory image and dont root, you'll get ota in future.
Though, I'm guessing g you'll be impatient anyway so its will be irrelevant. In which case since you'll probably just want to flash yourself and be rooted, why bother flashing the entire factory image? You dont need to flash recovery or bootloader... Just flash radio, system and boot.
Click to expand...
Click to collapse
so if you are rooted on 5.0 stock and unlocked bootloader and no custom recoveries. How do you install the 5.1 update without losing everything?
theDXT said:
so if you are rooted on 5.0 stock and unlocked bootloader and no custom recoveries. How do you install the 5.1 update without losing everything?
Click to expand...
Click to collapse
Flash everything from the factory image except the userdata.img

[Q] Downgrade system image

I know it can be done, as long as you don't OTA after. If I were to downgrade to 4.4.4 or 5.0.2 with 5.1 bootloader, would that offer a software method to root and unlock or no?
Edit: Welp, I answered my own question... I can't even flash anything because of sig checks.
darknessrise1234 said:
I know it can be done, as long as you don't OTA after. If I were to downgrade to 4.4.4 or 5.0.2 with 5.1 bootloader, would that offer a software method to root and unlock or no?
Edit: Welp, I answered my own question... I can't even flash anything because of sig checks.
Click to expand...
Click to collapse
I am looking for a downgrade without removing the bootloader . just that there's no way .
Maliktor said:
I am looking for a downgrade without removing the bootloader . just that there's no way .
Click to expand...
Click to collapse
The bootloader can not be downgraded. That would cause a brick. I'm looking for a way to downgrade the system/boot images to 4.4.4 so I could root to get an unlock on the bootloader via sunshine.
darknessrise1234 said:
The bootloader can not be downgraded. That would cause a brick. I'm looking for a way to downgrade the system/boot images to 4.4.4 so I could root to get an unlock on the bootloader via sunshine.
Click to expand...
Click to collapse
You can at least try using Kingroot to root the device for now, and wait till Sunshine is compatible with Lollipop.
With "mofo" you can flash firmwares to the phone on a locked bootloader, I wonder if there is a way to flash just system.img using mofo. Maybe ask that at their thread.
eksasol said:
You can at least try using Kingroot to root the device for now, and wait till Sunshine is compatible with Lollipop.
With "mofo" you can flash firmwares to the phone on a locked bootloader, I wonder if there is a way to flash just system.img using mofo. Maybe ask that at their thread.
Click to expand...
Click to collapse
Mofo does not work with 5.1 bootloader and kingroot does not work with 5.1. Sunshine is updated to unlock so long as you have root but I cannot find root method for 5.1.
Edit: Okay, so I'm seeing that some people HAVE downgraded their system image but eventually had a brick from OTA flashing BL. How do you downgrade the system image? If I can get to 4.4.4, I can root and unlock and go back to 5.1.

[HELP] Moto X XT1058 AT&T fully bricked! I can't do anything!

So, as the title says, I had a Moto X XT1058 from AT&T.
I updated a long time ago to Lollipop and the phone worked perfectly fine until yesterday, when suddenly shutted down and when I restarted, got stuck on M logo.
I restarted to bootloader(?) pressing power off and vol down buttons.
The version that shows me is 30.BE
The device wasn't unlocked or rooted, because I was happy with the stock ROM, so it says Device is LOCKED ans Status Code 0.
I tried every option on this menu and everyone says (in red):
"No valid PIV block in SP for system
piv validation failed (system)
Boot up failed"
I tryed with abd, fastboot, mfastboot and RSDLite to flash gpt.bin and motoboot.img and every time I do it I get a error, and the operation fails.
For what I've read in tooooooo many posts, it's probably death, but I resist to this idea, so I came here to ask for advice.
THE PHONE IS NOT IN WARRANTY ANY MORE.
Thanks in advance and sorry for my english (not my native language).
why dont you try twrp recovery ?
just flash it
fadyrox said:
why dont you try twrp recovery ?
just flash it
Click to expand...
Click to collapse
Can I do it if my phone isn't rooted? The bootloader it's locked!
Flash full stock att 5.1 rom, it will be fine.
Salik Iqbal said:
Flash full stock att 5.1 rom, it will be fine.
Click to expand...
Click to collapse
Flashing via fastboot mode will be okay !
do search here you will get details !
fadyrox said:
Flashing via fastboot mode will be okay !
do search here you will get details !
Click to expand...
Click to collapse
But I never flashed any ROM on this phone. I got Lollipop from a OTA update. My phone was stock. Never rooted, never unlock bootloader. I didn't find any tutorial to do it with this characteristics.
And it's an AT&T xt1058
MatiCepe said:
But I never flashed any ROM on this phone. I got Lollipop from a OTA update. My phone was stock. Never rooted, never unlock bootloader. I didn't find any tutorial to do it with this characteristics.
And it's an AT&T xt1058
Click to expand...
Click to collapse
first you need to unlock your bootloader .. otherwise you wont be able to recover your device
Please do a search regarding unlocking bootloader !
fadyrox said:
first you need to unlock your bootloader .. otherwise you wont be able to recover your device
Please do a search regarding unlocking bootloader !
Click to expand...
Click to collapse
The bootloader of the XT1058 from AT&T is'nt unlockable.... That's the big trouble. I've read that it can be done if it's no 4.2.2, but not if the version is newer.
MatiCepe said:
The bootloader of the XT1058 from AT&T is'nt unlockable.... That's the big trouble. I've read that it can be done if it's no 4.2.2, but not if the version is newer.
Click to expand...
Click to collapse
Download rsd lite for windows, get latest stock rom for att, reboot your phone into fastboot, flash stock rom and you are done.
Salik Iqbal said:
Download rsd lite for windows, get latest stock rom for att, reboot your phone into fastboot, flash stock rom and you are done.
Click to expand...
Click to collapse
I searched and the lastone is ATT_XT1058_5.1.0_LPA23.12-21.7_cid1_CFC.xml.zip. I try to flash it on my phone via RSD and the process showsme this error:
Failed flashing process. 4/18 flash motoboot "motoboot.img" -> Phone returned FAIL.
MatiCepe said:
I searched and the lastone is ATT_XT1058_5.1.0_LPA23.12-21.7_cid1_CFC.xml.zip. I try to flash it on my phone via RSD and the process showsme this error:
Failed flashing process. 4/18 flash motoboot "motoboot.img" -> Phone returned FAIL.
Click to expand...
Click to collapse
Is your phone is charge enough? Search 5.1.1 att xml zip
can anybody give a solution for this problem because i am also with a xt1058 at&t, The device wasn't unlocked or rooted and the version that shows me is 30.BE too
sorry my english
What's up with your device any screen shot?
Hi, i have the same problem, my device is locked by AT&T and i cant flash the firmware< i have a unlock code from the AT&T company, how I can introdce that code manually? Thanks!
Thank you
H3c4rtr1 said:
Hi, i have the same problem, my device is locked by AT&T and i cant flash the firmware< i have a unlock code from the AT&T company, how I can introdce that code manually? Thanks!
Click to expand...
Click to collapse
You can help how you got the code, give details.
Thank you

Categories

Resources