Related
Hi there,
So my new OPO came with a build of CM11S which doesn't appear to have any OTA updates, or the OTA function has been disabled. I have heard about this new CO12 update (YNG1TAS2I3) which is supposed to fix the touchscreen issues once and for all, and I would like to move up to this latest official build. I would like to keep all of my data partition intact if it can be done because without root, there doesn't seem to be any way of backing up data/apps. I am not rooted so I only have the original stock recovery.
I just want to point out that I don't have any touchscreen issues on this OPO, my first One had these issues and I sent it back and was given a replacement. With this 2nd OPO, I wanted to stay away from lollipop until the issue was fixed in a new update, which seems to have happened now.
My question is, which official build should I flash/install?, and which would be the best method to do this? (without rooting ) I was thinking, flash the latest CM11S and see if the OTA updates will take me up to the latest build
Im currently on CM11.0-XNF9XBS28K - Build No. KTU84Q.
Thanks
See section 8 of my guide here:
http://forum.xda-developers.com/showthread.php?t=2839471
Your guide says that i need an unlocked bootloader for step 8. And to unlock boot my bootloader, means the data will be wiped. Can I use the stock recovery to just flash the update zip? Or will that also wipe my data?
donk165 said:
Your guide says that i need an unlocked bootloader for step 8. And to unlock boot my bootloader, means the data will be wiped. Can I use the stock recovery to just flash the update zip? Or will that also wipe my data?
Click to expand...
Click to collapse
You can use stock recovery to flash an update zip. But you really should unlock your bootloader anyway, you're gonna need it unlocked just in case something goes wrong in future, it's best to do it now while you can actually backup your data.
Heisenberg said:
You can use stock recovery to flash an update zip. But you really should unlock your bootloader anyway, you're gonna need it unlocked just in case something goes wrong in future, it's best to do it now while you can actually backup your data.
Click to expand...
Click to collapse
Okay, well how can I back my data up from here? I know your guide says I should do the unlock when I first get the phone, but I've already been using the phone for about 3-4 weeks.
Back on my first OPO, when I was being told to do the display patches, I tried omegavesko's Simple ADB Backup and when it came to restoring, it didn't really work properly, many things got missed despite it being a "full backup". I assumed because I'm upgrading from Kitkat to Lollipop, I can just apply the update and my data will be kept intact?
donk165 said:
Okay, well how can I back my data up from here? I know your guide says I should do the unlock when I first get the phone, but I've already been using the phone for about 3-4 weeks.
Back on my first OPO, when I was being told to do the display patches, I tried omegavesko's Simple ADB Backup and when it came to restoring, it didn't really work properly, many things got missed despite it being a "full backup". I assumed because I'm upgrading from Kitkat to Lollipop, I can just apply the update and my data will be kept intact?
Click to expand...
Click to collapse
Just copy any important personal data (images, music, etc) from your internal storage to your PC. You can't do anything about your apps though unfortunately. The update won't wipe any of your data.
Heisenberg said:
Just copy any important personal data (images, music, etc) from your internal storage to your PC. You can't do anything about your apps though unfortunately. The update won't wipe any of your data.
Click to expand...
Click to collapse
Okay, I have taken all of my needed files, did SMS and call log backups and I'm ready to unlock the bootloader, so do i just do step 1 of your guide then straight to step 8? I was gonna fastboot the latest CM11 build and then after that should I wait for OTA or just do another fastboot session but this time use the CO12 build?
Just installed all the USB and fastboot drivers now.
Edit: Its all done now, I unlocked the bootloader, then I used the fastboot version of cm-11.0-XNPH05Q and did all the fastboot commands to give me the latest CM11, then i was prompted with a pre-requisite update before CO12, then after I got the update to cm-12.0-YNG1TAS17L. After those, I didn't get an OTA to the newest CO12, so then finally I downloaded and applied the incremental OTA from YNG1TAS17L to YNG1TAS2I3 and installed that through CM stock recovery.
donk165 said:
Okay, I have taken all of my needed files, did SMS and call log backups and I'm ready to unlock the bootloader, so do i just do step 1 of your guide then straight to step 8? I was gonna fastboot the latest CM11 build and then after that should I wait for OTA or just do another fastboot session but this time use the CO12 build?
Just installed all the USB and fastboot drivers now.
Edit: Its all done now, I unlocked the bootloader, then I used the fastboot version of cm-11.0-XNPH05Q and did all the fastboot commands to give me the latest CM11, then i was prompted with a pre-requisite update before CO12, then after I got the update to cm-12.0-YNG1TAS17L. After those, I didn't get an OTA to the newest CO12, so then finally I downloaded and applied the incremental OTA from YNG1TAS17L to YNG1TAS2I3 and installed that through CM stock recovery.
Click to expand...
Click to collapse
Cool, so you're all good?
Heisenberg said:
Cool, so you're all good?
Click to expand...
Click to collapse
Yeah man, all good now, thank you for pointing me in the right direction. That CM11 I started on was weird having no OTA updates, and I was very wary after CO12 on my first OPO and then getting touchscreen problems. I'm glad this new build is out with the fixes. Hopefully I'll never see those issues on this phone now.
Has anyone flashed the new 8.1 developer image? Is it possible to root and get TWRP on there?
Horgar said:
Has anyone flashed the new 8.1 developer image? Is it possible to root and get TWRP on there?
Click to expand...
Click to collapse
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.
mannunikhil said:
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.
Click to expand...
Click to collapse
Yes I tried with TWRP 3.1.1.1 and supersu 2.82 SR5 plus suhide 1.09. and got the same thing TWRP would not decrypt at password entry. Had to go back to 8.0. Have you managed to get root and recovery?
Horgar said:
Yes I tried with TWRP 3.1.1.1 and supersu 2.82 SR5 plus suhide 1.09. and got the same thing TWRP would not decrypt at password entry. Had to go back to 8.0. Have you managed to get root and recovery?
Click to expand...
Click to collapse
I'm not bothered with twrp recovery so did not flash the zip, but like I said I booted into twrp.img, flashed supersu and suhide and that's it. All working for me including SafetyNet. I used USB OTG for this process.
I did the same as the poster above.
just curious;
but how is Android 8.1? ?
I've found 8.0 to not be as good on battery life as 7.x.x, although I think I have mostly worked that out on my custom kernel...
any other notable goodies?
(ps: I don't care for the pixel launcher or the ambient services stuff..)
mannunikhil said:
I booted trwp 3.1.1-1 and flashed SuperSU 2.82 SR3 + Suhide 1.09. Oreo feels more sweeter in 8.1 DP1.
Edit: Decrypt failed at recovery so performed above via OTG. Just thought you should know.
Click to expand...
Click to collapse
I flashed factory image and I have error.
Myo Thu Htet said:
I flashed factory image and I have error.
Click to expand...
Click to collapse
Move the entire folder to a drive other than C drive. I think that might fix it.
NoobInToto said:
Move the entire folder to a drive other than C drive. I think that might fix it.
Click to expand...
Click to collapse
I did. But the error exit
Myo Thu Htet said:
I did. But the error exit
Click to expand...
Click to collapse
Sweet. Now you can't flash using factory images
And I can't flash using ADB sideload and inbuilt ota system.
Great.
Edit: @Myo Thu Htet
I checked google+ page of android beta program. Seems those update has issues.
NoobInToto said:
Sweet. Now you can't flash using factory images
And I can't flash using ADB sideload and inbuilt ota system.
Great.
Edit: @Myo Thu Htet
I checked google+ page of android beta program. Seems those update has issues.
Click to expand...
Click to collapse
I did all u did ?
Yes I checked G+
Only few can install.
Myo Thu Htet said:
I flashed factory image and I have error.
Click to expand...
Click to collapse
There could be few things that is causing to stuck, you can try below points in order make it work
1) check if downloaded factory image is not corrupt - see if you can extract all files from that zip, and/or download it again.
2) Disable any antivirus/firewall in your PC which monitors the behavior of files and try again.
3) Run cmd as Administrator and then run flash-all.bat
If none of above works then try and flash each file manually, follow my guide from below link this has worked 99% times
https://forum.xda-developers.com/showpost.php?p=73699257&postcount=5
mannunikhil said:
There could be few things that is causing to stuck, you can try below points in order make it work
1) check if downloaded factory image is not corrupt - see if you can extract all files from that zip, and/or download it again.
2) Disable any antivirus/firewall in your PC which monitors the behavior of files and try again.
3) Run cmd as Administrator and then run flash-all.bat
If none of above works then try and flash each file manually, follow my guide from below link this has worked 99% times
https://forum.xda-developers.com/showpost.php?p=73699257&postcount=5
Click to expand...
Click to collapse
Nope. It looks like Google's fault this time.
NoobInToto said:
Nope. It looks like Google's fault this time.
Click to expand...
Click to collapse
Just to test your theory (and came out wrong), I sideload'ed 8.1 OTA over my previous 8.1. This time it was successful without an error, attached images - one of it not clear as taken it from laptop camera just right now.
It seems like a file system issue when sideload'ing over 8.0.0 - a android developer shall confirm.
In short, both OTA and factory images from google are totally fine, concern is something else.
mannunikhil said:
Just to test your theory (and came out wrong), I sideload'ed 8.1 OTA over my previous 8.1. This time it was successful without an error, attached images - one of it not clear as taken it from laptop camera just right now.
It seems like a file system issue when sideload'ing over 8.0.0 - a android developer shall confirm.
In short, both OTA and factory images from google are totally fine, concern is something else.
Click to expand...
Click to collapse
It wouldn't be a fair test.
The update fails when sideloading 8.1 over a 8.0 system.
Edit: let me try the few things you suggested to test your suggestions . However I am not too optimistic.
@mannunikhil as I was extracting the ota, I realised I shouldn't bother with it. Google itself has taken down the ota from their site...
NoobInToto said:
It wouldn't be a fair test.
The update fails when sideloading 8.1 over a 8.0 system.
Edit: let me try the few things you suggested to test your suggestions . However I am not too optimistic.
@mannunikhil as I was extracting the ota, I realised I shouldn't bother with it. Google itself has taken down the ota from their site...
Click to expand...
Click to collapse
Mine was the fair test just to check if OTA zips are corrupt or not. I provided suggestions for factory image not for OTA, no point in extracting the OTA anyway. And if you had gone through all the threads you would see I mentioned I had similar issue sideload'ing OTA over 8.0.0, so that means we are sailing in same boat. OTAs had compatibility issue with 8.0.0, glad google listened and taken them off.
I still have little lag in app drawer hoping that would be fixed too in republished OTA.
Just signed up for Android beta program and got the 8.1 update for my project fi carrier unlocked Google pixel XL. The update seems to be running smoothly and everything is working so far on my device... I didn't have any issues with installation it installed just fine... Can't wait for Nov security patch supposed to be a good network feature in there in Dev settings.
I am not sure if this may help anyone trying to look at why the issues are present when trying to install:
Android 8.1 beta OTA upgrade on OG Pixel
I, just like many of you, have been experiencing OTA "installation problem" when trying to upgrade to the 8.1 beta. After reviewing comments and what worked for who, I decided to give this a shot and it worked. I am not sure if this will work for other devices (nexus or XLs) and keep in mind that you WILL lose all your data stored on the device, so back up prior to this method.
1. Be sure you are enrolled in the beta program.
2. Wait for the OTA to notify you that it's available.
3. Select "Download and Install".
4. After it has done its duty, DO NOT select "Restart and Install"
5. Go to "Factory Reset" and pull the trigger.
6. Your phone will factory reset, stating it's wiping everything, then it will install the update successfully.
NOTE: this is what worked for me. I'm unsure if it will solve all the "Installation problem" reports which have been made.
It's weird cause when I tried to factory reset, then download and install, it didn't work. Yet, downloading but NOT installing, then factory resetting worked.
After doing this I posted it here: https://plus.google.com/+ChristopherLeeMurray/posts/KDCZXbfAxLJ
You don’t need to sign up to the beta program. Just go to the Google website and download the latest 8.1 factory image. That's what I did and had no problem with flashing it. You can also delete the - w and keep your data. It's getting past the TWRP password to decrypt that I cant do. So can't flash root or recovery. Anyone managed this?
I'd prefer to be in the beta program since I'm a Android apps beta tester. I beta test everything and when it was installing it said on the screen that it's a beta version of the original software version of 8.1 which is what I believe is on Googles page and mine may have errors and defects.. the beta program gets different software than what Google usually posts. Different features and such which isn't in the official version which makes it a beta version.
Thanks to user @NinjaBoyLao for the heads up... seems a new update is appearing on Moto X Pure, anybody else seeing it?
https://mobilesupport.lenovo.com/us/en/solution/MS124799
Screenshot attached.
EDIT: A see a few MXPE users in this thread have seen an update today as well.
Just checked and I'm now downloading the 8 MB update.
Yes I got it. It's just the Oct security update. It takes care of the wifi issue.
acejavelin said:
Thanks to user @NinjaBoyLao for the heads up... seems a new update is appearing on Moto X Pure, anybody else seeing it?
https://mobilesupport.lenovo.com/us/en/solution/MS124799
Screenshot attached.
EDIT: A see a few MXPE users in this thread have seen an update today as well.
Click to expand...
Click to collapse
Just got the notification here. I'm currently on 22 (Verizon). I'm rooted w/xposed so I can't take it without a full fastboot flash, but I downloaded it and extracted it. It's about 8mb. For other users, this is if you are on stock -22 and want to sideload the -25 ota from -22. I cannot confirm if this will work if you are on -23.
Blur_Version.25.11.22.clark_retus.retus.en.US: https://mega.nz/#!GR4yha5B!WT97ryQRKD8V0EkefLj6WHwUdTs3boMJea0D3e4ZSGY
autosurgeon said:
Yes I got it. It's just the Oct security update. It takes care of the wifi issue.
Click to expand...
Click to collapse
what wifi issue?
I'm rooted with just magisk and TWRP in my recovery partition, should I attempt to take this and/or capture it to verify the other capture?
jaysus145 said:
what wifi issue?
Click to expand...
Click to collapse
Pretty sure the user means the WiFi Vulnerability KRACK... https://www.krackattacks.com/
jaysus145 said:
what wifi issue?
Click to expand...
Click to collapse
KRACK is the issue it primarily addresses.
Can confirm, I just received the notification as well, USA on AT&T, no root but unlocked bootloader. I flashed to 25.200-22 manually.
I'm not sure how I should proceed if I plan on getting root and possibly lock bootloader again.
i did the update and my phone don't get out of the twrp screen. what i need to do now?
You cannot take updates if you are not completely stock. Yeesh it amazes me how few people root and fiddle without any idea what they are doing.
Got an update today. I returned to stock a while back to get nougat. I've had battery issues since even after factory reset. But I digress. Got this update today. I'm on Sprint.
Once we install this. Will there be any harm going back to .22? Have to say at least they are still pushing some updates out.
StankFiss said:
Once we install this. Will there be any harm going back to .22? Have to say at least they are still pushing some updates out.
Click to expand...
Click to collapse
Same rules apply as always... Downgrading is questionable at best, this seems to be a boot image update only though, since it is merely 8MB, so it should be possible to downgrade successfully but I don't think anyone has tried yet.
I received the update notification just now. Unfortunately I have TWRP and rooted with Magisk. I guess I'll have to wait for an OTA flashable zip.
annoyingduck said:
Just got the notification here. I'm currently on 22 (Verizon). I'm rooted w/xposed so I can't take it without a full fastboot flash, but I downloaded it and extracted it. It's about 8mb. For other users, this is if you are on stock -22 and want to sideload the -25 ota from -22. I cannot confirm if this will work if you are on -23.
Blur_Version.25.11.22.clark_retus.retus.en.US: https://mega.nz/#!GR4yha5B!WT97ryQRKD8V0EkefLj6WHwUdTs3boMJea0D3e4ZSGY
Click to expand...
Click to collapse
If I remember correctly, I can't just flash this via TWRP, correct? What are the fastboot flash commands for these files, or will I be better off waiting for someone to just upload a TWRP flashable version?
Thanks!
Just got an alert this morning. Not going to take it. Will wait for flashable file.
On Verizon and running .22 . Got the update message for 25.201.1. My phone has TWRP, SU root, a new logo.bin and Xposed.
I will be waiting for a flashable zip file. Any volunteers?
I wonder if there is any .23 goodness in this update such as newer radios for BT.
slicetwo said:
If I remember correctly, I can't just flash this via TWRP, correct? What are the fastboot flash commands for these files, or will I be better off waiting for someone to just upload a TWRP flashable version?
Thanks!
Click to expand...
Click to collapse
No TWRP. The file I provided is the actual OTA zip from Motorola. It will only apply from the stock recovery (side load) if you are on the -22 build unmodified. If your just stock with systemless root and left TWRP in read only mode, you could simply unroot, fastboot flash the stock recovery and then take the OTA. You would also have to fastboot flash any other modified partitions too from the -22 firmware (like if you changed the logo.bin). However, if your like me and are using the official N xposed or have allowed modifications in TWRP, you would need a full flash of the stock -22 firmware. In this case you could simply omit the bootloader lock, and data wipe commands and "dirty flash" the -22 firmware, take the OTA, and then re-root.
Note: I haven't had the time to do this yet. I cannot confirm if root/Xposed are working correctly on this -25 OTA, but I see no reason it wouldn't. I'm hoping I'll have time later to do it. I honestly don't care if there is some sort of failure, I'll be rocking a Pixel 2 soon. So I will be the guinea pig.
annoyingduck said:
No TWRP. The file I provided is the actual OTA zip from Motorola. It will only apply from the stock recovery (side load) if you are on the -22 build unmodified. If your just stock with systemless root and left TWRP in read only mode, you could simply unroot, fastboot flash the stock recovery and then take the OTA. You would also have to fastboot flash any other modified partitions too from the -22 firmware (like if you changed the logo.bin). However, if your like me and are using the official N xposed or have allowed modifications in TWRP, you would need a full flash of the stock -22 firmware. In this case you could simply omit the bootloader lock, and data wipe commands and "dirty flash" the -22 firmware, take the OTA, and then re-root.
Note: I haven't had the time to do this yet. I cannot confirm if root/Xposed are working correctly on this -25 OTA, but I see no reason it wouldn't. I'm hoping I'll have time later to do it. I honestly don't care if there is some sort of failure, I'll be rocking a Pixel 2 soon. So I will be the guinea pig.
Click to expand...
Click to collapse
Yeah... that's to much damn work. Haha. I am running Xposed and such. I'll just wait to see if someone makes a flashable file.
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
When will the update madness with our phone ends???
Downloading right now...has anyone installed it yet?
liquor said:
When will the update madness with our phone ends???
Downloading right now...has anyone installed it yet?
Click to expand...
Click to collapse
When will it end? Probably August 2020 as Essential has promised 2 years of OS updates and 3 of security updates like the Pixel. Android Q would be the last OS update, followed by a year of security updates. And August because the phone launched late August. It might get support through September. All assuming nothing happens to Essential before then.
Installed the zip from Essential, haven't had much time to see if any differences that are noticeable.
OTA Zip
Fastboot zip
Anybody else getting "Couldn't Update" message after reverting back to May update from Q Beta?
goofball2k said:
Installed the zip from Essential, haven't had much time to see if any differences that are noticeable.
OTA Zip
Fastboot zip
Click to expand...
Click to collapse
Do you apply those OTA.zips like you would for any ROM? Or do you wipe dalvik, system, and data then flash the OTA.zip. I wanted to ask before I winded up in some crazy ****. I went ahead and backed up my phone.
jxcorex28 said:
Do you apply those OTA.zips like you would for any ROM? Or do you wipe dalvik, system, and data then flash the OTA.zip. I wanted to ask before I winded up in some crazy ****. I went ahead and backed up my phone.
Click to expand...
Click to collapse
I have TWRP installed. This is my way of doing the update.
Ensure the OTA zip and TWRP zip (optional, you can choose to install TWRP your own way) and Magisk zip (optional, only if you want to be rooted) are on the phone storage
Reboot to TWRP recovery
Select Install, then install the OTA zip file and then the TWRP recovery zip.
Reboot to system, or if you wish to have Magisk installed, flash the Magisk zip file.
knochnkopf said:
Anybody else getting "Couldn't Update" message after reverting back to May update from Q Beta?
Click to expand...
Click to collapse
Yeah, have the exact same problem.
After disliking Android Q Beta (had issues with calls) I flashed Android 9 May update (fastboot). Now the June update won't install
cjscholten said:
Yeah, have the exact same problem.
After disliking Android Q Beta (had issues with calls) I flashed Android 9 May update (fastboot). Now the June update won't install
Click to expand...
Click to collapse
I had no issues installing the June OTA through TWRP after going back to stock May ROM from the Q Beta.
I would recommend you to back up again and start with the stock fastboot June ROM.
Good luck.
Sent from my PH-1 using XDA Labs
cjscholten said:
Yeah, have the exact same problem.
After disliking Android Q Beta (had issues with calls) I flashed Android 9 May update (fastboot). Now the June update won't install
Click to expand...
Click to collapse
Have you contacted Essential about the issue? I sent them a message yesterday with my device info and the process I used to flash back to the May 2019 update. Haven't heard from them yet. Seems like an odd problem. Only thing I can think of is maybe it has something to do with a scripting error in the batch file used to flash back to stock. I also went into my bootloader to verify that was locked so it should for all intents and purposes behave as a stock device. I have no root or custom recovery installed.
---------- Post added at 09:46 AM ---------- Previous post was at 09:22 AM ----------
Anybody know if flashing the OTA file from the Essential website vs the FastBoot file will completely wipe my device or just install over the top like a normal OTA? Only reason I ask is the OTA download is 330MB but the OTA file from the website is over 1GB. I really don't want to wipe my device AGAIN after just doing it less than a month ago.
Update: Flashed OTA zip from stock recovery without loss of data. They should really make that clearer on their website because it says flashing OTA "may" result in loss of data.
knochnkopf said:
Have you contacted Essential about the issue? I sent them a message yesterday with my device info and the process I used to flash back to the May 2019 update. Haven't heard from them yet. Seems like an odd problem. Only thing I can think of is maybe it has something to do with a scripting error in the batch file used to flash back to stock. I also went into my bootloader to verify that was locked so it should for all intents and purposes behave as a stock device. I have no root or custom recovery installed.
---------- Post added at 09:46 AM ---------- Previous post was at 09:22 AM ----------
Anybody know if flashing the OTA file from the Essential website vs the FastBoot file will completely wipe my device or just install over the top like a normal OTA? Only reason I ask is the OTA download is 330MB but the OTA file from the website is over 1GB. I really don't want to wipe my device AGAIN after just doing it less than a month ago.
Click to expand...
Click to collapse
I flashed the OTA via TWRP and retained all app's and the data without any problems.
Sent from my PH-1 using XDA Labs
The new update broke fastboot for me. Anyone else having issues with it? The update was taken OTA and runs fine, but I can't flash boot images or twrp anymore. Just gets a can't be read error.
Jz5678910 said:
The new update broke fastboot for me. Anyone else having issues with it? The update was taken OTA and runs fine, but I can't flash boot images or twrp anymore. Just gets a can't be read error.
Click to expand...
Click to collapse
There's a fastboot zip linked in the previous page. Not sure if it'll help but maybe.
Essential PH-1, /e/ 0.6-n ROM, microG (NoGapps), XDA Legacy
marcdw said:
There's a fastboot zip linked in the previous page. Not sure if it'll help but maybe.
Essential PH-1, /e/ 0.6-n ROM, microG (NoGapps), XDA Legacy
Click to expand...
Click to collapse
Actually I did try that, but I can't flash it due to fastboot not working unfortunately. It seems like one of my slots is corrupted.
Jz5678910 said:
The new update broke fastboot for me. Anyone else having issues with it? The update was taken OTA and runs fine, but I can't flash boot images or twrp anymore. Just gets a can't be read error.
Click to expand...
Click to collapse
I don't use TWRP, but I was able to successfully flash Magisk-patched boot image after the latest update, so fastboot seems to be working just fine for me...