Database Info

Moto G (1st gen) OTA to Lollipop fails

Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks

Same problem here

Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.

A_Bunny said:
Have to install stock ROM again then update it via ota. Could also try flashing an ota update file via the official recovery of your phone.
Click to expand...
Click to collapse
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...

Ulverinho said:
Yep, my guess was the same. As per official recovery - I'll try adb sideload, but first time it couldn't find phone (all drivers installed and up-to-date).
http://forum.xda-developers.com/moto-g/help/driver-fastboot-falcon-s-t2820848
This error pops up - I can't find solution also...
Click to expand...
Click to collapse
Install the recovery with fastboot not adb.

A_Bunny said:
Install the recovery with fastboot not adb.
Click to expand...
Click to collapse
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.

Ulverinho said:
Well, I might misunderstood, but:
I have official recovery (fastboot is mode of it, I guess, when U press Power+volume key?)
I've read about adb sideload zip_name_of_OTA.zip
I don't know any other way to install OTA apart from let phone handle it OR adb sideload.
Click to expand...
Click to collapse
Just load it onto your phone before you flash it. Your ROM does work.

A_Bunny said:
Just load it onto your phone before you flash it. Your ROM does work.
Click to expand...
Click to collapse
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?

Ulverinho said:
Load ZIP of OTA on SD Card and install it from Recovery? Will it work?
Click to expand...
Click to collapse
It may work if it is the stock recovery.

A_Bunny said:
It may work if it is the stock recovery.
Click to expand...
Click to collapse
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.

Ulverinho said:
Got this, screenshot in attachment.
Fingerprints are wrong. In build.prop - I can see it's fine, fingerprint of current 4.4.4. - matches expected.
But as soon as update starts - it says that 4.4.2 is fingerprint of my OS. Bollocks.
Edited OTA zip, edited some metadata file...
Why it won't install on pretty clean phone - I can't understand...Previous installs of OTA went fine with root etc.
Click to expand...
Click to collapse
Well the only thing I would recommend would be to install the stock system though fastboot manualy.

Ulverinho said:
Hi folks, so, I received OTA update for my Moto G (XT1032).
Phone was rooted (I did unroot from SuperSU). Also, I've re-installed Stock recovery (to make sure) and wiped cache/dalvik.
But, update still fails.
I don't have much root-related soft (like Xposed etc) installed - so pretty sure this should not cause an issue.
But still, update fails.
Any ideas how to troubleshoot/make it work? Maybe installing OTA somehow from recovery (custom one, TWRP)?
Any comments - much appreciated. I guess I'm not alone in this, but still...
Thanks
Click to expand...
Click to collapse
i feel ya same thing here, than i tryed installing a stock lollipop from here via twrp witch ended up messing my phone with failing the procedure wondered around couldnt revert to stock since im a noob and didnt even backed up the rom,but at the and of the day thank god for the cm12.1 finally menaged to make my phone running again at least

Greetings, I have the same problem, it is the last screen that appears when you install the update, and then restarts it goes off the screen update error ...

To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.

fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yeah, that's the better way.
But I guess, I can install Stock 5.* straight away after wiping? Why bother about OTA, if there is ROM available?

fusionice said:
To anyone having issues:
1. Make sure you're on completely stock 4.4.4 (Refer to http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 and use only untouched 4.4.4 version for your phone if you have to reflash before continuing)
2. Make sure you're on stock recovery (Refer to http://forum.xda-developers.com/showthread.php?t=2649763)
*Uninstall XPOSED if using it
3. I personally let update run on its own after reverting everything to stock.
Click to expand...
Click to collapse
Yep.
The solution is backup data, restore stock last firmware using fastboot guide posted in this forum and not even update apps (cancel gmail registration and everything it asks when it first starts) ONLY update motorola update services so you can get the ota again an install it. If you have the ota downloaded you can flash it through recovery but using the last recovery version (.61) and of course last firmware version. If you guys flash it all through fastboot, it should install w/o any problems.

"system partition has unexpected contents" March 2016 OTA or Sideload Failed Error 7

"system partition has unexpected contents" March 2016 OTA or Sideload Failed Error 7
Hi,
My N5 is rooted and on factory images (6.0.1). I have reverted to stock recovery from twrp 3.0.0.0 because my system wouldn't accept Feb security updates.
After reverting to stock recovery, Feb updates worked fine.
March updates however continually fail with Error 7 (modified system partition?), either by system OTA or sideloading over adb / stock recovery.
I think, the last thing that I did was installed Wake Lock Detector, converted to a system app, this broke and couldn't be removed or converted back to a user app, so I had to force remove it via a convoluted system of Ti and other Root Uninstaller apps. Got rid of it in the end.
Anyway, this is the only thing I can think of that may be causing this Error 7, and I'm out of options. That's why I'm here.
The CM team seem to have some solutions to this issue. Anyone have any ideas for stock peeps?
Do I really need to unroot and reflash stock etc etc etc? I'd rather not.
Thanks, as ever, for the great support on XDA!

1. Check if the bootloader is hhz12k
2. Try use twrp 2.8.7.1 instead
3. Check adb version installed in your pc

I've gone back to pure stock...huge pain. Before I did this I reset to full stock, rooted and tested again...root broke the OTA and side load with error 7. Hence why I'm back unrooted and fully stock again. I want updates.

tedrogers61 said:
I've gone back to pure stock...huge pain. Before I did this I reset to full stock, rooted and tested again...root broke the OTA and side load with error 7. Hence why I'm back unrooted and fully stock again. I want updates.
Click to expand...
Click to collapse
Not many people replied to you as it has been said over and over and over. On marshmallow any change to system partition breaks the ability to apply OTAs. If you want the updates so bad, just download the new factory image and fastboot flash system.img. Then re-root. You wont lose data this way.

Thanks very much. I didn't know this and I swear I searched high and low...obviously not in the right areas. I ask a question on XDA when I feel I've googled the topic to death with no satisfactory outcome. So I can reflash a new system image over the top and all data remains intact? Good to know. Thank you.

tedrogers61 said:
Thanks very much. I didn't know this and I swear I searched high and low...obviously not in the right areas. I ask a question on XDA when I feel I've googled the topic to death with no satisfactory outcome. So I can reflash a new system image over the top and all data remains intact? Good to know. Thank you.
Click to expand...
Click to collapse
@tedrogers61: Make sure you only flash the system.img part - you have to do that manualy, dont use the .bat in the package.
Otherwise you WILL lose your data 100%, because the .bat file is flashing anything AND erase userdata+cache partition by default !
What you need to do :
1. Download factory image at https://developers.google.com/android/nexus/images#hammerhead
2. Use 7zip to unpack the .tgz, then again unzip the .tar, then unzip the image-hammerhead-mmb29v.zip (if you are using windows)
3. copy the system.img to a easy to find location (optional, just helps to find the system.img)
4. if you have USB Debug activated+USB cable + ADB installed (which i guess you have), connect your phone to USB, Phone runing normally and open a command prompt.
Enter these commands:
Code:
adb reboot bootloader
fastboot flash system <path-to-your-system.img>
On first command, the phone should reboot and display should show an android laying on his back
Next command should give you feedback in command prompt like "Erasing system"..."sending system"..."writing system".
The phone display should show similiar informations.
Thats it - you need to apply root after this.
You need to restart the phone manualy but as long as the command prompt shows OKAY and "finished. total time xyz seconds", everything worked fine.

Thank you @Warlord711, I worked out it was fastboot flash system system.img.
Testing this on my N5 right not which won't receive April OTA.
Might give this a go on my N5X later, which won't go past Feb OTA.
Is there a pattern here? Is there something wrong with my account which is preventing OTA's perhaps?

wangdaning said:
Not many people replied to you as it has been said over and over and over. On marshmallow any change to system partition breaks the ability to apply OTAs. If you want the updates so bad, just download the new factory image and fastboot flash system.img. Then re-root. You wont lose data this way.
Click to expand...
Click to collapse
Thank you very much.

tedrogers61 said:
Thank you @Warlord711, I worked out it was fastboot flash system system.img.
Testing this on my N5 right not which won't receive April OTA.
Might give this a go on my N5X later, which won't go past Feb OTA.
Is there a pattern here? Is there something wrong with my account which is preventing OTA's perhaps?
Click to expand...
Click to collapse
As mentioned, if anything is modified (root, custom recovery, etc) you will not be able to use OTA. Another problem, for people like me, cannot access google servers. Your google account is not linked to OTA, so it is not that. Doesn't really matter anyway, like you found, easy enough to just do it yourself. I live in China so have no choice anyway, haha, but it is simple. Personally, I do not use stock roms anyway, so don't really care.

Problem with reverting back to stock and take OTA!

Hi
I really need help to go stock on my device.
I unlocked my bootloader, flashed TWRP and Magisk on stock rom and installed the ViperU Magisk Module.
I also made a NANDROID of the stock ROM before, unfortunately there is no Recovery in it, since i had TWRP already installed.
Then an OTA (oktober 17 security patch) was available for my device and i startet the install process, but it didn't install.
TWRP open recovery would run not even 1 second then exit.
In order to get the OTA I restored stock recovery (which i had to extract from OTA, since i forgot to back it up) and started OTA.
--> Red Triangle!
Even after restoring stock NANDroid the OTA wouldn't install.
My mistake i think was that i didn't kept the stock system read only when i did the backup in twrp and swiped to allow modifications.
According to some threads here, even mounting the system r/w would break OTA functionality.
So since i also have no RUU for my device, i don't have the chance either to go back to stock. Maybe you did that mistake too.
The only way i can think of now, is to go temporary S-OFF, change CID and MID (to 401 international for example), flash Firmware and run the RUU for it.
But i'm not sure it'll still work after flashing the firmware.
Can anyone maybe confirm this way would work?
And is there an other way available?
Thanks!
Quick Specs:
-Unlocked Bootloader
-S-ON
-Firmware: 1.27.166.7
-CID: VODAP110
-MID: 2PZC10000

Nightmare
Quick Specs:
-Unlocked Bootloader
-S-ON
-Firmware: 1.27.166.7
-CID: VODAP110
-MID: 2PZC10000[/QUOTE said:
Hello, Have you looked at this list to see if you could take one from here?
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse

michaelbsheldon said:
Hello, Have you looked at this list to see if you could take one from here?
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit#gid=0
Click to expand...
Click to collapse
Hi
Yes, unfortunately there's nothing available for my device.

Does the phone boot into os?

You cannot take an OTA with TWRP. You need an untouched system image to take the OTA. Easiest way is to RUU to your current firmware. Let the system update.

schmeggy929 said:
You cannot take an OTA with TWRP. You need an untouched system image to take the OTA. Easiest way is to RUU to your current firmware. Let the system update.
Click to expand...
Click to collapse
Actually that's not true, TWRP appareantly has a open recovery which works with OTA.
Also the RUU doesn't have to match your Firmware.
What i did was following:
-Had TWRP and a running ROM, rootet with magisk
-Downloded a RUU for my MID (picked the 401 one for international unlocked, i think you can take any)
-Installed sunshine and went temp s-off
-Went into download mode and changed cid to a matching one (HTC__034 -> Europe for me, there are other compatibles)
-Renamed the RUU (2PZCIMG.zip) and put it in the root of my SD-Card
-Inserted the SD-Card and rebootet to download (there's an option in download mode for that)
-pressed volume up to start installation
-Done, phone reboots with stock system, stock recovery and right firmware
Also I installed TWRP right back and magisk and tried to take the OTA. It installed without problems through TWRP.
Afaik, it will work, but replace TWRP in the end, so you will have to reflash twrp after every OTA, or you just take the recovery out of the
OTA and flash it through SD-Card (you have to rename it).
So that's the way to go if you have to go stock and there's nothing in the collection for your version.
Hope this helps.
Edit: Please remember to keep TWRP in read only! you will still be able to flash zips like magisk for example.

Hey,
after you had flashed the 004 Ruu, did you change S-off back to S-On?

2eli0 said:
Hey,
after you had flashed the 004 Ruu, did you change S-off back to S-On?
Click to expand...
Click to collapse
since s-off is still temporary it will go back to s-on as soon as you boot into recovery or rom.
also, i flashed the 1.27.401.5 ruu, since i wanted to see if the update to 1.27.401.12 ota works with twrp and magisk installed.
it does, just remember to keep recovery read only!

What do you mean by "read only"? Is there a setting where I can do that?

2eli0 said:
What do you mean by "read only"? Is there a setting where I can do that?
Click to expand...
Click to collapse
If you take a bone stock phone (when you buy it for example, or after running a ruu), the first time you flash twrp and
boot into it, it will ask you if you want to keep the system in read only, in order not to break the OTA functionality.
But you won't be able to restore backups or install zip which changes system partition (Custom ROMs, xposed, etc.).
If you want to keep OTA functionality, you can keep it read only and still be able to flash zips like magisk and so on.
Once you swipe to allow modifications doe, there is no way back, so keep that in mind!
Mounting the system partition once in rw (read/write) will break OTA permanently.
If you ever decide that you want to modify the system partition anyway (going custom ROM) you can change the setting:
TWRP-->Mount-->"Mount system partition read only"-->uncheck it
Correct me if i'm wrong.

Nightmare[ITA said:
;75529278]If you take a bone stock phone (when you buy it for example, or after running a ruu), the first time you flash twrp and
boot into it, it will ask you if you want to keep the system in read only, in order not to break the OTA functionality.
But you won't be able to restore backups or install zip which changes system partition (Custom ROMs, xposed, etc.).
If you want to keep OTA functionality, you can keep it read only and still be able to flash zips like magisk and so on.
Once you swipe to allow modifications doe, there is no way back, so keep that in mind!
Mounting the system partition once in rw (read/write) will break OTA permanently.
If you ever decide that you want to modify the system partition anyway (going custom ROM) you can change the setting:
TWRP-->Mount-->"Mount system partition read only"-->uncheck it
Correct me if i'm wrong.
Click to expand...
Click to collapse
Ah ok, got it.
I would want to keep the OTA functionality, since I want to keep it stock with root privileges. That's all.
I won't try custom roms anytime soon. Thanks for the tip.
If I had known that before I flashed twrp I would have been able to update OTA now, right?

2eli0 said:
Ah ok, got it.
I would want to keep the OTA functionality, since I want to keep it stock with root privileges. That's all.
I won't try custom roms anytime soon. Thanks for the tip.
If I had known that before I flashed twrp I would have been able to update OTA now, right?
Click to expand...
Click to collapse
Pretty much, ya. I missed that part the first time too

Nightmare[ITA said:
;75529808]Pretty much, ya. I missed that part the first time too
Click to expand...
Click to collapse
Ahh, dang it. Well, I'd say we learn by mistakes.
Thanks for the hint.
I will try the version you tried. It's still downloading.
Btw. did the download take like ages for you?
During the day I get like 100-200 KB/s and sometimes even less. In the evening like 11 pm it's 3 MB/s...
My connection is fine.

2eli0 said:
Ahh, dang it. Well, I'd say we learn by mistakes.
Thanks for the hint.
I will try the version you tried. It's still downloading.
Btw. did the download take like ages for you?
During the day I get like 100-200 KB/s and sometimes even less. In the evening like 11 pm it's 3 MB/s...
My connection is fine.
Click to expand...
Click to collapse
Yes, over the last few months AFH has been extremely slow.

Ok I will state it in another way. The easiest way to take the OTA is on an Untouched System and Recovery Image lol. You can with TWRP however the firmware will not flash. Hence probably your problem. You do know there is an RUU for 2.33.166.6 for your carrier. https://www.htcdev.com/devcenter/downloads

I have already seen that, but its like 400 mb big, if I remember correctly, hence not the entire files, right?

schmeggy929 said:
Ok I will state it in another way. The easiest way to take the OTA is on an Untouched System and Recovery Image lol. You can with TWRP however the firmware will not flash. Hence probably your problem. You do know there is an RUU for 2.33.166.6 for your carrier. https://www.htcdev.com/devcenter/downloads
Click to expand...
Click to collapse
lol. That's the site i was searching for.
But since it's the source code, you would have to compile it first, right?
Anyway, are you sure? Cause from what i can see the firmware got updated too.
In fact, in this post under point 4. it states, that it's working.

The htcdev stuff is source only. No good. Also, once you flash twrp you can't take ota. You must be stock to take ota (s-off and bootloader remain untouched and do not matter for flashing, there is no need to s-on nor relock the bootloader ever).
To achieve stock just flash the same firmware you currently use as a zip from the external sdcard. The only things lost is root and twrp.

Nightmare[ITA] said:
lol. That's the site i was searching for.
But since it's the source code, you would have to compile it first, right?
Anyway, are you sure? Cause from what i can see the firmware got updated too.
In fact, in this post under point 4. it states, that it's working.
Click to expand...
Click to collapse
Yeah i guess you are right it is the source code. Even with TWRP stills seems like a lot of work to update. Ya'll need some custom ROMs installed. Flash signed firmware.zip, reflash TWRP and flash updated ROM. All done. If by chance you ever needed to return to stock, flash your system image backup. Ya'll make things so complicated when they really aren't. lol

Nightmare[ITA said:
]Actually that's not true, TWRP appareantly has a open recovery which works with OTA.
Also the RUU doesn't have to match your Firmware.
What i did was following:
-Had TWRP and a running ROM, rootet with magisk
-Downloded a RUU for my MID (picked the 401 one for international unlocked, i think you can take any)
-Installed sunshine and went temp s-off
-Went into download mode and changed cid to a matching one (HTC__034 -> Europe for me, there are other compatibles)
-Renamed the RUU (2PZCIMG.zip) and put it in the root of my SD-Card
-Inserted the SD-Card and rebootet to download (there's an option in download mode for that)
-pressed volume up to start installation
-Done, phone reboots with stock system, stock recovery and right firmware
Also I installed TWRP right back and magisk and tried to take the OTA. It installed without problems through TWRP.
Afaik, it will work, but replace TWRP in the end, so you will have to reflash twrp after every OTA, or you just take the recovery out of the
OTA and flash it through SD-Card (you have to rename it).
So that's the way to go if you have to go stock and there's nothing in the collection for your version.
Hope this helps.
Edit: Please remember to keep TWRP in read only! you will still be able to flash zips like magisk for example.
Click to expand...
Click to collapse
Well, I managed to do it exactly the way you did.
Everything worked just fine. I changed the CID to HTC__034 and flashed the ruu file updated to Oreo and flashed TWRP kept it at read only and rooted the phone.
Thanks for that :good:

OTA update with unlocked bootloader

I'll be switching to Project Fi soon from ATT. With the switch I'll lose my only reason for being rooted (wifi hotspot) since Fi offers hotspot for no extra charge. Am I able to install OTA updates with an unlocked bootloader if everything else is stock (ie. not rooted)?

geicogecko said:
I'll be switching to Project Fi soon from ATT. With the switch I'll lose my only reason for being rooted (wifi hotspot) since Fi offers hotspot for no extra charge. Am I able to install OTA updates with an unlocked bootloader if everything else is stock (ie. not rooted)?
Click to expand...
Click to collapse
I think you should be able to
Sent from my Pixel 2 XL using Tapatalk

You cannot take OTA updates normally with an unlocked bootloader. The phone will download the update, but the update will fail.
You CAN update manually using either OTA or factory images from here and following my guide here.
To sideload OTA images using either stock recovery or TWRP, follow the instructions here.

Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.

geicogecko said:
Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.
Click to expand...
Click to collapse
The nice thing about getting an OTA is that it installs in the background and a quick reboot to finish the update. Why not start fresh with a full wipe since you're changing carriers. It's not super difficult to get it set up again and now you have a clean install. I say that because I'm about to suggest you relock the bootloader and see how it runs. You obviously have the oem switch enabled so its really easy to go back and unlock if you so desire. Just a thought. I liked Project Fi when I had it but it didn't make financial sense in my case with a family plan. Good luck.

geicogecko said:
Excellent, thank you. I'd rather not wipe the phone so I guess I'll settle for sideloading OTAs. And it would be nice to be able to root later on if I decide I need to.
Click to expand...
Click to collapse
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.

socal87 said:
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.
Click to expand...
Click to collapse
Did you let it reboot on its own, or did you manually boot into TWRP, find the file and flash it that way?

k.s.deviate said:
Did you let it reboot on its own, or did you manually boot into TWRP, find the file and flash it that way?
Click to expand...
Click to collapse
I'm not sure I understand your question. I flashed the OTA file in recovery using TWRP. There is no way to flash things in recovery without rebooting...

socal87 said:
I'm not sure I understand your question. I flashed the OTA file in recovery using TWRP. There is no way to flash things in recovery without rebooting...
Click to expand...
Click to collapse
After the OTA downloaded, did you just reboot when it asked you to, or, did you manually boot into TWRP and find the OTA file to flash. OR, did you download the OTA from an third party and flash that way.

k.s.deviate said:
After the OTA downloaded, did you just reboot when it asked you to, or, did you manually boot into TWRP and find the OTA file to flash. OR, did you download the OTA from an third party and flash that way.
Click to expand...
Click to collapse
I downloaded the OTA directly from https://developers.google.com/android/ota, then rebooted into TWRP and flashed the zip.
I'm on stock software with the exception of Magisk and Flash kernel, so OTAs always fail. Thus, I have Automatic System Updates turned off in Developer Options.
Regardless of how you do it, the OTA will always overwrite /boot, so you'll lose custom kernel and recovery.

bobby janow said:
The nice thing about getting an OTA is that it installs in the background and a quick reboot to finish the update. Why not start fresh with a full wipe since you're changing carriers. It's not super difficult to get it set up again and now you have a clean install. I say that because I'm about to suggest you relock the bootloader and see how it runs. You obviously have the oem switch enabled so its really easy to go back and unlock if you so desire. Just a thought. I liked Project Fi when I had it but it didn't make financial sense in my case with a family plan. Good luck.
Click to expand...
Click to collapse
I may do this eventually. I want to see what having a non-rooted phone is like first. I haven't had a non-rooted phone in probably eight years. If I find out I really don't need root for anything, I may relock the bootloader.

socal87 said:
Just for ****s and giggles, I tried installing the OTA zip through TWRP. Worked like a charm.
Please note that if you do this, the kernel and recovery will revert to stock, so you'll have to boot TWRP via fastboot and reflash.
Click to expand...
Click to collapse
Wait... do you mean you actually flashed the downloaded, official OTA zip using TWRP over a rooted OS with no issues at all?... Interesting. Was that flashed OTA, a security patch only?
Sent from my Moto Z2 Play using XDA Labs

The Analog Kid said:
Wait... do you mean you actually flashed the downloaded, official OTA zip using TWRP over a rooted OS with no issues at all?... Interesting. Was that flashed OTA, a security patch only?
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
When the 9.0 update came out, I installed that via TWRP. Again, as noted, this will install it to both slots, and when it boots, it will boot via the other slot.
So, for instance, if you happen to be on slot A, and you install the OTA, it installs the stock kernel to slot B, and boots via that slot - stock kernel, no Magisk or TWRP. After it boots , when it is "Finishing update", it installs the stock kernel to slot A.
So, every time you flash an OTA, you need to let it boot, then reboot into bootloader, boot TWRP via fastboot, install TWRP, install kernel, and Magisk.

geicogecko said:
I may do this eventually. I want to see what having a non-rooted phone is like first. I haven't had a non-rooted phone in probably eight years. If I find out I really don't need root for anything, I may relock the bootloader.
Click to expand...
Click to collapse
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 10:31 PM ---------- Previous post was at 10:28 PM ----------
socal87 said:
When the 9.0 update came out, I installed that via TWRP. Again, as noted, this will install it to both slots, and when it boots, it will boot via the other slot.
So, for instance, if you happen to be on slot A, and you install the OTA, it installs the stock kernel to slot B, and boots via that slot - stock kernel, no Magisk or TWRP. After it boots , when it is "Finishing update", it installs the stock kernel to slot A.
So, every time you flash an OTA, you need to let it boot, then reboot into bootloader, boot TWRP via fastboot, install TWRP, install kernel, and Magisk.
Click to expand...
Click to collapse
... That's only if you want to preserve root, I guess? AND for Pixel devices, right?
Sent from my Moto Z2 Play using XDA Labs

The Analog Kid said:
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Sent from my Moto Z2 Play using XDA Labs
---------- Post added at 10:31 PM ---------- Previous post was at 10:28 PM ----------
... That's only if you want to preserve root, I guess? AND for Pixel devices, right?
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
Yes. If you're otherwise stock aside from an unlocked bootloader, you can sideload the OTA zip...or, copy it to internal storage, reboot to recovery, and install it that way.
If you want to keep TWRP, you'll have to boot the TWRP image after installing and rebooting, then flash TWRP. The OTA does not wipe data (obviously); it just returns everything in /boot and /system to stock.

The Analog Kid said:
So... How's the non-rooted phone experience going so far? Because I can't get fully used to the experience yet (I have this phone for a month now) and coming from... well, ALL of my previous devices rooted too (about an eight year span as well). Even though the phone in question (Z2 Play) runs very smooth and plain "force-close-less" (yeah, you know root) I still don't find myself quite at home without Xposed and it's useful modules, for example... Oreo is nice indeed but, on the other hand, I also have this little tiny bit temptation for Android 9... Sure, if it ever lands on my phone in less than a year! Quite a bet.
Click to expand...
Click to collapse
So I actually took the advice and relocked the bootloader. No issues. I think there was one app that I would've needed root for, but I can't remember what it was. I didn't use Xposed. I don't even know if it works on the Pixel. Like I said in the opening post, I only needed it to enable wifi hotspot, so others may notice it more.

Were you able to update with ota after relocking your boot loader? I tried it after and the update would install but stay at 0% then eventually fail. Any suggestions? Thanks.

ychongy13 said:
Were you able to update with ota after relocking your boot loader? I tried it after and the update would install but stay at 0% then eventually fail. Any suggestions? Thanks.
Click to expand...
Click to collapse
You should be able to install the latest OTA image using stock recovery:
https://developers.google.com/android/ota

Feb 2019 update now available

Hope by performance fixes they mean memory leak fix.

I have not seen os ram usage this low after boot in many months.

Did you have round corner?

yaral said:
Did you have round corner?
Click to expand...
Click to collapse
It squared it when I screenshot.

Anybody figure out how to turn off the rounded corners?

Anyone know what the modem sucurity patch is about? Kinda don't want to take it cuz of the sim lock issues awhile back.

enigma2446 said:
Anyone know what the modem sucurity patch is about? Kinda don't want to take it cuz of the sim lock issues awhile back.
Click to expand...
Click to collapse
no clue but i fastboot flashed the images because the OTA refused to work, but flashing the images worked. i'm still able to connect to ATT towers from my sprint sim unlocked PH-1.

TomTheGeek3 said:
no clue but i fastboot flashed the images because the OTA refused to work, but flashing the images worked. i'm still able to connect to ATT towers from my sprint sim unlocked PH-1.
Click to expand...
Click to collapse
Noob question here: When using fastboot to flash the update image, do you have to worry about the "slot A" vs "slot B" thing?? Can you provide a little more insight? I've been reading around the forum, and I'm a little worried about bricking my phone! (The bootloader on my phone is unlocked and I've rooted the phone, but I haven't flashed a third-party ROM. The OTA update feature gives me a "couldn't update" message.)

adiejg said:
Noob question here: When using fastboot to flash the update image, do you have to worry about the "slot A" vs "slot B" thing?? Can you provide a little more insight? I've been reading around the forum, and I'm a little worried about bricking my phone! (The bootloader on my phone is unlocked and I've rooted the phone, but I haven't flashed a third-party ROM. The OTA update feature gives me a "couldn't update" message.)
Click to expand...
Click to collapse
No you don't have to worry about it. The flash all file in the zip will do all the work for you. It wont take update via ota because you have to be on the stock boot.img. the stock boot img has the recovery built into the ramdisk there for if your rooted then there is no stock recovery to use for ota. Be cautious because flashing via fastboot will wipe the phone.

enigma2446 said:
No you don't have to worry about it. The flash all file in the zip will do all the work for you. It wont take update via ota because you have to be on the stock boot.img. the stock boot img has the recovery built into the ramdisk there for if your rooted then there is no stock recovery to use for ota. Be cautious because flashing via fastboot will wipe the phone.
Click to expand...
Click to collapse
If I edit the .bat file and remove "format userdata", that will prevent the wipe?

njsges said:
If I edit the .bat file and remove "format userdata", that will prevent the wipe?
Click to expand...
Click to collapse
It should without issues but always prepare for hickups.

Anyone else having issues when trying to update to the February release? I tried to sideload the OTA update and that kept giving me the error "adb sideload failed to read command: no error" and then I decided to follow Morphius's suggestion here to just unroot my device by flashing to stock bootloader in order to try to take the OTA update and that OTA keeps failing as well. Anyone else having this issue?

hssxda said:
Anyone else having issues when trying to update to the February release? I tried to sideload the OTA update and that kept giving me the error "adb sideload failed to read command: no error" and then I decided to follow Morphius's suggestion here to just unroot my device by flashing to stock bootloader in order to try to take the OTA update and that OTA keeps failing as well. Anyone else having this issue?
Click to expand...
Click to collapse
Are you rooted?

After three days running, memory Leak not fixed.. Bummer

enigma2446 said:
No you don't have to worry about it. The flash all file in the zip will do all the work for you. It wont take update via ota because you have to be on the stock boot.img. the stock boot img has the recovery built into the ramdisk there for if your rooted then there is no stock recovery to use for ota. Be cautious because flashing via fastboot will wipe the phone.
Click to expand...
Click to collapse
Again, a very noob question, (and I do apologize) but can I use something like Titanium Backup to make sure I can restore all my apps the way they were after I flash the update via fastboot? Reinstalling everything seems like a gigantic pain in the backside.

adiejg said:
Again, a very noob question, (and I do apologize) but can I use something like Titanium Backup to make sure I can restore all my apps the way they were after I flash the update via fastboot? Reinstalling everything seems like a gigantic pain in the backside.
Click to expand...
Click to collapse
Titanium Backup used to require root access. You probably need to be rooted before you update via fastboot and run the backup through Titanium Backup. Then you will need to copy your backup files to a computer because fastboot flashing will erase your phone data. Next apply the fastboot update, root again, copy your backup back to the phone and restore your backup.

enigma2446 said:
Are you rooted?
Click to expand...
Click to collapse
I was but I followed all the proper steps but for some reason this morning my computer wouldn't real the OTA zip file. I tried it tonight using a different USB port on my laptop and it is worked first time... so weird...

d14r1 said:
After three days running, memory Leak not fixed.. Bummer
Click to expand...
Click to collapse
I don't have memory leak anymore..
1.5gb ram not in usage.
The last time I restarted my phone was after the update.

I'm using my Essential 'phone in the UK having recently purchased it used. On the 7th I had a notice to say that an update was available. When I tried to install it it downloaded, but refused to install saying: Couldn't update... installation problem. As far as I know the 'phone is running the stock software but I noticed that no updates had been installed since October 2018. I unchecked 'allow bootloader unlocking' in case that was the issue, but still couldn't perform the update.
I went onto the Essential website and downloaded the OTA image to my iMac, then, following the guide, sideloaded the update on to the 'phone. This worked well and I now have an updated PH-1. I'll have to see if March's update now installs correctly or not.

so.... am i reading this right... and here is my thinking...
to keep root and still take the OTAs
- go to Essentials site and download the image zip
- (to keep root) copy boot.img to your device, patch it through magisk, then copy it back to your ota folder.
- open flashall.bat, comment the format userdata (to keep your data), change the boot.img line to patched_boot.img
- run flashall.bat
- profit