Related
I am unrooted and on stock 4.4.
I have tried installing the 4.4.2 OTA 3 times, failing every time on 20-30%.
Then I tried to go to recovery mode and wiping cache partition, and after that I immediately got another OTA 4.4.2, but that also failed.
I have no idea why this is happening, and what my options are.
Do anyone know about this problem, if it is with my phone or a general problem, and how to fix it, or get 4.4.2 some other way.
did you install any mods, kernels, change any files? if so its been documented all over the forums.
No, the only thing I've done that might be causing a problem (I've just now learned), is that I had Google Keep deactivated, which apparently is a no-no since it's a system app.
I've re-activated it now and waiting until I get another OTA, then trying again.
danielvago said:
No, the only thing I've done that might be causing a problem (I've just now learned), is that I had Google Keep deactivated, which apparently is a no-no since it's a system app.
I've re-activated it now and waiting until I get another OTA, then trying again.
Click to expand...
Click to collapse
It didn't work. I have no idea what to do, can I sideload the APK?
Something similar happened to me to my wife's Nexus 5. Not even manually down loading the OTA file and flashing it using CWM worked properly (it flashed all right, but the phone became unstable after). So in the end, I downloaded the factory image for 4.4.2 and did a flash-all. Detailed instructions for doing that are available here: http://forum.xda-developers.com/showthread.php?t=2513701. It seems to run fine now. If you would like to preserve your data, unzip all of the factory image file and flash one component at a time, skipping userdata.img (as doing so wipes your data).
danielvago said:
It didn't work. I have no idea what to do, can I sideload the APK?
Click to expand...
Click to collapse
I've never had a problem flashing an update because system apps were disabled. Deleted yes, disabled no. If you were at one time rooted and deleted Keep from system/app sideloading it will not install it in the system, it will be installed as a user app. Also, if you put Keep back in system/app it needs to be both the apk and the odex files or it will fail again anyway. If you delete anything from the system you need to save those files somewhere because that will affect being able to do updates. Instead of deleting a file I would just rename it by adding the number 1 at the end of the name (Keep.apk1). At this point you would need to be rooted to replace anything in the system. Or you could use adb to flash the system image. Anyway... all this is conjecture on my part because it's not very clear if you have EVER been rooted or not and what exactly you mean by "deactivated," then asking if sideloading would work. If you "Disabled" Keep you don't need to sideload it because it's still there inside system/app. The update does not care if you have system app updates installed or not as long as the original is in system/app.
---------- Post added at 04:33 AM ---------- Previous post was at 04:24 AM ----------
Theory said:
Something similar happened to me to my wife's Nexus 5. Not even manually down loading the OTA file and flashing it using CWM worked properly (it flashed all right, but the phone became unstable after). So in the end, I downloaded the factory image for 4.4.2 and did a flash-all. Detailed instructions for doing that are available here: http://forum.xda-developers.com/showthread.php?t=2513701. It seems to run fine now. If you would like to preserve your data, unzip all of the factory image file and flash one component at a time, skipping userdata.img (as doing so wipes your data).
Click to expand...
Click to collapse
I believe you can open the flash-all script and delete the -w part and it will not flash the userdata image. I have a new original version of the 2012 N7 I'm going to try that with here in a minute to update to 4.4.2 but like you mention doing each image separately works great.
wantabe said:
I've never had a problem flashing an update because system apps were disabled. Deleted yes, disabled no. If you were at one time rooted and deleted Keep from system/app sideloading it will not install it in the system, it will be installed as a user app. Also, if you put Keep back in system/app it needs to be both the apk and the odex files or it will fail again anyway. If you delete anything from the system you need to save those files somewhere because that will affect being able to do updates. Instead of deleting a file I would just rename it by adding the number 1 at the end of the name (Keep.apk1). At this point you would need to be rooted to replace anything in the system. Or you could use adb to flash the system image. Anyway... all this is conjecture on my part because it's not very clear if you have EVER been rooted or not and what exactly you mean by "deactivated," then asking if sideloading would work. If you "Disabled" Keep you don't need to sideload it because it's still there inside system/app. The update does not care if you have system app updates installed or not as long as the original is in system/app.
---------- Post added at 04:33 AM ---------- Previous post was at 04:24 AM ----------
I believe you can open the flash-all script and delete the -w part and it will not flash the userdata image. I have a new original version of the 2012 N7 I'm going to try that with here in a minute to update to 4.4.2 but like you mention doing each image separately works great.
Click to expand...
Click to collapse
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
danielvago said:
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
Click to expand...
Click to collapse
What is the error when the OTA fails?
Adblockers usually require root, which in turn edits the hosts file, so that could be the culprit. I'd go the factory image way and edit the flash-all.bat using Notepad++ before running it to remove the -w flag so you don't lose your data
try incremental install
danielvago said:
I am unrooted and on stock 4.4.
I have tried installing the 4.4.2 OTA 3 times, failing every time on 20-30%.
Then I tried to go to recovery mode and wiping cache partition, and after that I immediately got another OTA 4.4.2, but that also failed.
I have no idea why this is happening, and what my options are.
Do anyone know about this problem, if it is with my phone or a general problem, and how to fix it, or get 4.4.2 some other way.
Click to expand...
Click to collapse
try sideloading 4.4.1 first. .and then sideload 4.4.2 after that. see if that works.
EddyOS said:
Adblockers usually require root, which in turn edits the hosts file, so that could be the culprit. I'd go the factory image way and edit the flash-all.bat using Notepad++ before running it to remove the -w flag so you don't lose your data
Click to expand...
Click to collapse
I just updated a new 2012 N7 from 4.1 to 4.4.2 and I couldn't get removing the -w flag to work. I think the script needs more editing than just removing the -w part. Something new I had never tried before which I actually don't personally have much use for because it still flashes the stock recovery over a custom recovery if you are using one. Anyway.. flashing the bootloader and radio separately and then flashing the update zip with "fastboot update image-hammerhead-kot49h.zip" would be a little bit of a shortcut versus flashing ALL of the images and you don't lose data.
Never had an issue myself, but I always prefer to flash each image manually one at a time
EddyOS said:
Never had an issue myself, but I always prefer to flash each image manually one at a time
Click to expand...
Click to collapse
I've always flashed each image separately also, I was just being lazy and experimenting. Removing the -w from the .bat and/or the .sh wouldn't work for me.
---------- Post added at 10:33 AM ---------- Previous post was at 10:27 AM ----------
danielvago said:
Sorry for not being clear, I have never rooted, un-locked, flashed anything, etc. I am using the phone very stock-y, not messing with anything.
It boggles me, that I can have such a problem, when I am going completely stock.
The most "extreme" things I've done is install an adblock apk and flashplayer 11.1 apk, that Dolphin browser suggested.
I don't know if the only solution is to do a factory reset, which I hate doing, since it took so very long to set everything up the way I wanted it.
I've read of other people having this problem, and no solution, and some have tried a factory reset but that didn't fix it.
Click to expand...
Click to collapse
If you don't want to try a factory reset (can't blame you) you're probably going to need to use adb. If you don't have it setup this is a good video showing how to setup adb.
wantabe said:
If you don't want to try a factory reset (can't blame you) you're probably going to need to use adb. If you don't have it setup this is a good video showing how to setup adb.
Click to expand...
Click to collapse
Thanks a lot.
I followed his steps and got it to show me the phones serial number when I wrote "adb devices" in cmd, in SDK -> platform-tools but... now what?
The guide just stops, and I don't know what to do.
I've done everything in this other guide ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ), but when I get to "adb sideload kk.zip" it just says "adb is not recognized as an internal or external command, operable command or batch file" and I'm stuck again.
What to do?
danielvago said:
Thanks a lot.
I followed his steps and got it to show me the phones serial number when I wrote "adb devices" in cmd, in SDK -> platform-tools but... now what?
The guide just stops, and I don't know what to do.
I've done everything in this other guide ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ), but when I get to "adb sideload kk.zip" it just says "adb is not recognized as an internal or external command, operable command or batch file" and I'm stuck again.
What to do?
Click to expand...
Click to collapse
Your path to adb isn't correct. Put the zip file in the same folder as adb
jd1639 said:
Your path to adb isn't correct. Put the zip file in the same folder as adb
Click to expand...
Click to collapse
Thanks, that was it, got it to begin.
Unfortunately it didn't work, it gave me an error about 30-35% through (like the normal OTA).
It says:
"/system/framework/framework-res.apk" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
From this link ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ) I chose:
"Nexus 5
Android 4.4 to 4.4.2 OTA update"
as I am on 4.4.
danielvago said:
Thanks, that was it, got it to begin.
Unfortunately it didn't work, it gave me an error about 30-35% through (like the normal OTA).
It says:
"/system/framework/framework-res.apk" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
From this link ( http://www.androidbeat.com/2013/12/...-4-4-2-kitkat-update-nexus-4-nexus-5-nexus-7/ ) I chose:
"Nexus 5
Android 4.4 to 4.4.2 OTA update"
as I am on 4.4.
Click to expand...
Click to collapse
You're going to have to flash the system and boot image in fastboot in order for the update to work. You modified something
jd1639 said:
You're going to have to flash the system and boot image in fastboot in order for the update to work. You modified something
Click to expand...
Click to collapse
I am unrooted and locked, I have no idea how I modified something, or what, or how, I have kept it really stock.
What does it mean to flash the system and boot image? Can I do it without rooting, unlocking and/or factory resetting?
danielvago said:
I am unrooted and locked, I have no idea how I modified something, or what, or how, I have kept it really stock.
What does it mean to flash the system and boot image? Can I do it without rooting, unlocking and/or factory resetting?
Click to expand...
Click to collapse
Ok, so you're doing an adb sideload while in recovery?
jd1639 said:
Ok, so you're doing an adb sideload while in recovery?
Click to expand...
Click to collapse
Yes.
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.
Hello. I recently tried to use Magisk Manager to root my phone using a step by step walk through. It worked, everything was great, I finally was able to get my mobile data to turn off automatically when I connected to Wi-Fi. Goal achieved. Hooray. But then a new update came out for the Pixel 2 XL, I believe what is called OTA? See how new I am, it's pathetic. Anyway, I can't get the OTA installed because I have Magisk. I found a good walk through to how to fix it github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips BUT when I go to uninstall Magisk and restore images, it says "stock backup does not exist". Guys. I'm in over my head and I don't know what to do to fix it. Can any one explain in simple language, maybe with pictures, so my idiot self can understand, how do I get a stock back up, and get Magisk to recognize it, so that I can proceed to install the OTA? Thank you so much for any advice,and your patience for dealing with me.
Megin said:
Hello. I recently tried to use Magisk Manager to root my phone using a step by step walk through. It worked, everything was great, I finally was able to get my mobile data to turn off automatically when I connected to Wi-Fi. Goal achieved. Hooray. But then a new update came out for the Pixel 2 XL, I believe what is called OTA? See how new I am, it's pathetic. Anyway, I can't get the OTA installed because I have Magisk. I found a good walk through to how to fix it github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips BUT when I go to uninstall Magisk and restore images, it says "stock backup does not exist". Guys. I'm in over my head and I don't know what to do to fix it. Can any one explain in simple language, maybe with pictures, so my idiot self can understand, how do I get a stock back up, and get Magisk to recognize it, so that I can proceed to install the OTA? Thank you so much for any advice,and your patience for dealing with me.
Click to expand...
Click to collapse
Search the forum, there are a lot of walk through threads.
You won't remove anything, IE Magik.
Download the Factory Image, OTA will not work.
You'll remove "-w" from one file to not wipe data.
Flash update.
Reroot with Magisk.
If you have problems finding the links or threads, I can link them.
Sent from my Pixel 2 using Tapatalk
What diesel said, it isn't really that hard ?.
Nathanchanche made a really good guide for us. Take your time to read it really well and you should be able to solve your problem.
https://forum.xda-developers.com/pixel-2/how-to/guide-unlock-flash-root-pixel-2-walleye-t3702417
In my experience, if rooted, don't use OTAs. Stick with factory images if possible.
Like other responses, it's best to use the guides on XDA. I usually do the following when an update is available:
- Download factory image
- Edit batch file (if you're using Windows) to remove the -w option so I don't lose my data
- Boot into bootloader (power off phone, then hold down power and volume down until you get to the bootloader)
- Run batch file (I have had issues on occasion with this). If you get an error, try using a different USB cable
- After factory image is installed, let phone reboot.
- After rebooting and device is fully ready to go, reboot back to bootloader.
- Install latest TWRP (follow instructions on their website...the steps they have works perfectly)
- After TWRP is installed, reboot phone back to bootloader and then go to the 'recovery' option. Make sure TWRP is working correctly and you can decrypt your data (that is, if you have a security password)
- After decrypted, you should be able to access your data where you've downloaded Magisk. You can then install Magisk.
- After install, reboot phone and you should be rooted.
These steps work for me, but I'm a bit anal when it comes to updates and rooting.
pgarlinski said:
In my experience, if rooted, don't use OTAs. Stick with factory images if possible.
Like other responses, it's best to use the guides on XDA. I usually do the following when an update is available:
- Download factory image
- Edit batch file (if you're using Windows) to remove the -w option so I don't lose my data
- Boot into bootloader (power off phone, then hold down power and volume down until you get to the bootloader)
- Run batch file (I have had issues on occasion with this). If you get an error, try using a different USB cable
- After factory image is installed, let phone reboot.
- After rebooting and device is fully ready to go, reboot back to bootloader.
- Install latest TWRP (follow instructions on their website...the steps they have works perfectly)
- After TWRP is installed, reboot phone back to bootloader and then go to the 'recovery' option. Make sure TWRP is working correctly and you can decrypt your data (that is, if you have a security password)
- After decrypted, you should be able to access your data where you've downloaded Magisk. You can then install Magisk.
- After install, reboot phone and you should be rooted.
These steps work for me, but I'm a bit anal when it comes to updates and rooting.
Click to expand...
Click to collapse
Ok what am I doing wrong here? prntscr.com/iqefpd
Megin said:
Ok what am I doing wrong here? prntscr.com/iqefpd
Click to expand...
Click to collapse
You need to install fastboot. Download plataform tools from the Android SDK and try again.
Megin said:
Ok what am I doing wrong here? prntscr.com/iqefpd
Click to expand...
Click to collapse
Follow the full tutorial in my signature, it will cover all the steps in detail.
Megin said:
Ok what am I doing wrong here? prntscr.com/iqefpd
Click to expand...
Click to collapse
As said previously you need fastboot.exe. Download from https://dl.google.com/android/repository/platform-tools-latest-windows.zip.
Extract everything to folder that contains your extracted image. If the fastboot.exe is still not recognized:
one option is to modify flash-all.bat line: PATH=%PATH%;"%SYSTEMROOT%\System32"; to PATH=%PATH%;"%SYSTEMROOT%\System32";"%cd%"
Telperion said:
Follow the full tutorial in my signature, it will cover all the steps in detail.
Click to expand...
Click to collapse
Worked!! Thanks
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
So for some reason the February update doesn't show up for my in system updates.
To update manually, is it better to download the ota from Google's site and flash that or the newest firmware and flash system?
G5-User7080 said:
So for some reason the February update doesn't show up for my in system updates.
To update manually, is it better to download the ota from Google's site and flash that or the newest firmware and flash system?
Click to expand...
Click to collapse
The safest way to update is by sideloading the OTA.
I assume your bootloader is not unlocked; if I am correct, flashing the factory image is not an option.
V0latyle said:
The safest way to update is by sideloading the OTA.
I assume your bootloader is not unlocked; if I am correct, flashing the factory image is not an option.
Click to expand...
Click to collapse
Ah sorry for the lack of details.
I'm unlocked and rooted and pass safetynet / play attestation with safetynet-fix-mod by DisplaX
I found your guide about updating etc in the Pixel 6 forum, and since I didn't know if I could just take feb 06 OTA or if I had to flash all previous ones too I just went with the factory image method.
I updated with the same version as I'm running to see if it would offer me to OTA then et voila it does
After I finished updating and did fastboot boot magisk-patched-boot-image.img it did offer me to OTA even tho I failed safety-net / play attestation (probably since I didnt do magisk direct install yet and was just booting the rooted image)
Which made me wonder,.. are you supposed to uninstall magisk before you even click on "system update"?
I thought you just check for updates first and when it shows one you then uninstall magisk.
G5-User7080 said:
Ah sorry for the lack of details.
I'm unlocked and rooted and pass safetynet / play attestation with safetynet-fix-mod by DisplaX
I found your guide about updating etc in the Pixel 6 forum, and since I didn't know if I could just take feb 06 OTA or if I had to flash all previous ones too I just went with the factory image method.
Click to expand...
Click to collapse
Current updates have all the updates and fixes from previous releases
G5-User7080 said:
I updated with the same version as I'm running to see if it would offer me to OTA then et voila it does
After I finished updating and did fastboot boot magisk-patched-boot-image.img it did offer me to OTA even tho I failed safety-net / play attestation (probably since I didnt do magisk direct install yet and was just booting the rooted image)
Which made me wonder,.. are you supposed to uninstall magisk before you even click on "system update"?
I thought you just check for updates first and when it shows one you then uninstall magisk.
Click to expand...
Click to collapse
Automatic OTA is troublesome when rooted. You don't need to perform a complete uninstall in Magisk; just restore images before you take the update, and make sure that you go back into Magisk and patch the inactive slot before you reboot.
V0latyle said:
Current updates have all the updates and fixes from previous releases
Automatic OTA is troublesome when rooted. You don't need to perform a complete uninstall in Magisk; just restore images before you take the update, and make sure that you go back into Magisk and patch the inactive slot before you reboot.
Click to expand...
Click to collapse
yes, that restore original images thing is what I meant, I'm just sticking to the OTA guide from Magisk, thats why I booted the patched boot img and then direct installed through magisk too instead of just flashing it.
Just since I've never done an OTA update before Idk if it shows that updates are available with magisk installed.
Like, if the "restore images" before OTA refers to before I even click on Settings -> System update to check if theres an upate available or if I can like let it download first and then restore it before installation or smth.
It did show it for me now but that was directly after rebooting from updating with factory images, booting rooted boot image but it was before I even direct installed root through magisk.
@V0latyle
mhh alright... I'm never doing OTA's again.
restored original boot.img through magisk, let the ota do its thine, instead of restart I went to magisk again and did "install to inactive slot" then reboot from magisk.
Except that it just showed "This device is corrupted" and when I pressed continue I was staring at a google logo and nothing happened.
So in the end I had to use android flash tool and wipe my phone cause normal fastboot firmware install didn't work.
Now its working and rooted again but the "This device is corrupted" message doesn't go away.
I even relocked the bootloader through android flash tool before I unlocked it and rooted like normal, but it's still there.
Is that like an addition from the last update? Now whenever I reboot there are 2 screens I have to click away,.. the normal unlocked warning and the corrupted screen.
G5-User7080 said:
@V0latyle
mhh alright... I'm never doing OTA's again.
restored original boot.img through magisk, let the ota do its thine, instead of restart I went to magisk again and did "install to inactive slot" then reboot from magisk.
Except that it just showed "This device is corrupted" and when I pressed continue I was staring at a google logo and nothing happened.
So in the end I had to use android flash tool and wipe my phone cause normal fastboot firmware install didn't work.
Click to expand...
Click to collapse
Shouldn't have had to do that. If this happens just reflash the boot image using ADB. If that doesn't work...
G5-User7080 said:
Now its working and rooted again but the "This device is corrupted" message doesn't go away.
Click to expand...
Click to collapse
Try sideloading the OTA. It appears that the "patch inactive slot" method in Magisk isn't working for everyone. Nothing is actually corrupt, the OTA update engine just isn't happy about something. Either way, wiping data shouldn't be necessary.
G5-User7080 said:
I even relocked the bootloader through android flash tool before I unlocked it and rooted like normal, but it's still there.
Click to expand...
Click to collapse
Don't EVER do this unless everything is 100% stock and the device has been fully wiped.
G5-User7080 said:
Is that like an addition from the last update? Now whenever I reboot there are 2 screens I have to click away,.. the normal unlocked warning and the corrupted screen.
Click to expand...
Click to collapse
Nope, both screens are part of the Android Boot Flow.
Since the inactive slot method didn't work, I suggest sideloading the OTA in the future. Do not interrupt the process or attempt to flash anything. Let the update complete normally and boot; you won't have root. Assuming you already have a Magisk patched boot image handy (it doesn't have to be current), you can then reboot to bootloader and live boot the patched image, then perform Direct Install in Magisk.
V0latyle said:
Shouldn't have had to do that. If this happens just reflash the boot image using ADB. If that doesn't work...
Click to expand...
Click to collapse
welp.. I tried flashing matching (so newest) boot, didnt work
V0latyle said:
Try sideloading the OTA. It appears that the "patch inactive slot" method in Magisk isn't working for everyone. Nothing is actually corrupt, the OTA update engine just isn't happy about something. Either way, wiping data shouldn't be necessary.
Click to expand...
Click to collapse
you mean now? like after im factory reset & rooted I should sideload the same OTA again which I'm on right now?
V0latyle said:
Don't EVER do this unless everything is 100% stock and the device has been fully wiped.
Click to expand...
Click to collapse
Isn't that what android flash tool does?
wiping my device and install stock?
either way I wasnt running a custom rom and of course I don't relock it after I'm rooted.
V0latyle said:
Since the inactive slot method didn't work, I suggest sideloading the OTA in the future. Do not interrupt the process or attempt to flash anything. Let the update complete normally and boot; you won't have root. Assuming you already have a Magisk patched boot image handy (it doesn't have to be current), you can then reboot to bootloader and live boot the patched image, then perform Direct Install in Magisk.
Click to expand...
Click to collapse
So right now I should leave everything as is including the corrupted message, right?
Then when the next OTA comes I do nothing, keep root, no uninstall or restore through magisk, and I just download the newest OTA from google, and do the fastboot sideload thing?
It'll work even though my boot.img is rooted?
And then the OTA will remove root, I live boot my existing (eventually outdated) magisk patchet boot.img, then direct install as usual?
V0latyle said:
Nothing is actually corrupt, the OTA update engine just isn't happy about something.
Click to expand...
Click to collapse
This is slightly frustrating,... thanks for telling my my device is corrupted and making me think its actually bricked... nice going google.
I'm gonna have so much fun doing all the device settings again, cause for some reason restoring google backup doesn't do that.
How would I not hate OTA's after this lol
G5-User7080 said:
welp.. I tried flashing matching (so newest) boot, didnt work
you mean now? like after im factory reset & rooted I should sideload the same OTA again which I'm on right now?
Click to expand...
Click to collapse
Yes. Sorry if it's confusing. The OTA update process can be a bit...sensitive.
G5-User7080 said:
Isn't that what android flash tool does?
wiping my device and install stock?
Click to expand...
Click to collapse
Yes, but only if Wipe device is checked
G5-User7080 said:
So right now I should leave everything as is including the corrupted message, right?
Click to expand...
Click to collapse
Just sideload the OTA. It won't wipe anything and it can't possibly hurt anything.
G5-User7080 said:
Then when the next OTA comes I do nothing, keep root, no uninstall or restore through magisk, and I just download the newest OTA from google, and do the fastboot sideload thing?
It'll work even though my boot.img is rooted?
Click to expand...
Click to collapse
Yes - when you update via system, it checks images for integrity before updating. Sideloading the OTA skips this and just overwrites the images. Doesn't affect user data.
G5-User7080 said:
And then the OTA will remove root, I live boot my existing (eventually outdated) magisk patchet boot.img, then direct install as usual?
Click to expand...
Click to collapse
Yep.
G5-User7080 said:
This is slightly frustrating,... thanks for telling my my device is corrupted and making me think its actually bricked... nice going google.
I'm gonna have so much fun doing all the device settings again, cause for some reason restoring google backup doesn't do that.
How would I not hate OTA's after this lol
Click to expand...
Click to collapse
I can definitely understand the frustration. Suggestion: before you go nuclear next time and wipe your data, post here and see if someone might have a solution. I have a strong suspicion that simply sideloading the OTA would have cleared the corrupted message, you wouldn't have had to wipe data, and you could have just re-rooted. As the great Hitchhiker's Guide to the Galaxy tells us, "Don't Panic!"
Sideloading went without issue, message still there though, but at this point idec anymore, thanks for the help!
V0latyle said:
Just sideload the OTA. It won't wipe anything and it can't possibly hurt anything.
Click to expand...
Click to collapse
G5-User7080 said:
Sideloading went without issue, message still there though, but at this point idec anymore, thanks for the help!
Click to expand...
Click to collapse
The corrupt message is?
Hmm. Sideload again. Reason being is the OTA always installs to the inactive slot, then switches to that slot. If you install the OTA twice, it installs to both slots. Example: you're on slot A. Install OTA -> slot B becomes active, Slot A hasn't been updated. Install OTA again, -> Slot A becomes active.
Just to make sure - you're using Magisk 25.2, yes?
Latest release, yes.
No worky, was on slot a before, so it did ota and switched to b, b wasnt rooted, I rooted it through magisk, did the ota again, so it switched back to a, rebooted, a wasnt rooted as expected and the message was still there.
just to confirm that it actually switched and didnt like ota 2 times without switching, I switched back to b and it was rooted.
Can only guess it only works if the ota actually installs anything, i mean im already on february 5th on both slots.
So I'll try again next month.
G5-User7080 said:
Latest release, yes.
No worky, was on slot a before, so it did ota and switched to b, b wasnt rooted, I rooted it through magisk, did the ota again, so it switched back to a, rebooted, a wasnt rooted as expected and the message was still there.
just to confirm that it actually switched and didnt like ota 2 times without switching, I switched back to b and it was rooted.
Can only guess it only works if the ota actually installs anything, i mean im already on february 5th on both slots.
So I'll try again next month.
Click to expand...
Click to collapse
The message should disappear when you update the OS next month.
G5-User7080 said:
So for some reason the February update doesn't show up for my in system updates.
To update manually, is it better to download the ota from Google's site and flash that or the newest firmware and flash system?
Click to expand...
Click to collapse
what works best for me (!) is downloading the whole factory image, extracting boot.img, patching it using magisk, transferring it back to the pc, and there editing flash-all.bat so it doesn’t wipe data (!) and adding one line to flash the new boot.img directly at the end. reboot to bootloader, run flash-all, done.
Just use PixelFlasher. It will take care of everything, including Magisk patching the boot image. Makes updates using the factory images painless, takes about 5 minutes total.
G5-User7080 said:
hi, umm so this isn't really something for any thread, I just have some questions.
Is it possible to force a full factory flash?
Cause I assume running flash-all.bat from the factory image or using android flash tool does not do that, as it only uses the fastboot update command.
Well, Idk what exactly fastboot update does, but from my old phone I remember that the script to flash stock contains a lot of flash commands for every partition, e.g. fastboot flash boot, fastboot flash system, etc.
So maybe that warning would go away after actually flashing the entire rom over it.
Also while data was wiped at least 2 times, there are three apps that I accidentally disabled a few days ago, and or some reason I couldnt re-enable them, and the weird thing is they are still disabled..
Then for some reason when I restored the google backup after the wipe it didn't apply my settings and only downloaded my apps.
And now I found another thing, sometimes my screen doesnt turn off after the set timeout, only when charging tho, but stay awake in dev settings isnt on..
Additionally the battery level is inconsistent and suddenly jumps up or down a few percent, but the kernel reported level (measured with ACCA) stays consistent, so its not really an issue.
I'll try resetting all app permissions and if that doesnt work all settings i guess, but I really have no clue what mightve caused this.
Especially since none of those happened before wipe / OTA and I only re-installed my apps, loaded their settings from backups and clicked through the settings app.
No new modules or any root quirks.
I'm glad its just my phone, I only really use it for social media and and umm music ig so its not really that much work to set up again, only really annoying thing is to click through everything in settings cause theres no way to back that up meh.
Click to expand...
Click to collapse
@G5-User7080 I'm bringing this to public as discussed in PM.
Yes, you can force a full factory flash. Yes, the flash-all script and the Android Flash Tool both do this - they flash bootloader, radio, and all OS partitions. If you want to be really thorough, you can check the "Force flash all partitions" checkbox, this also requires a data wipe.
I'm not sure why system apps would remain disabled following a data wipe.
The Google One backup isn't able to back up everything. It cannot back up application data, and it does not back up all system settings.
Regarding the screen, I've noticed the opposite with my Pixel 5. I have "Stay Awake" turned off, but despite having my screen timeout set for 1 minute, it turns off and locks after about 15 seconds.
Battery...Not sure what to tell you.
Consumer electronics are cantankerous beasts indeed and fraught with gremlins.
V0latyle said:
@G5-User7080 I'm bringing this to public as discussed in PM.
Yes, you can force a full factory flash. Yes, the flash-all script and the Android Flash Tool both do this - they flash bootloader, radio, and all OS partitions. If you want to be really thorough, you can check the "Force flash all partitions" checkbox, this also requires a data wipe.
I'm not sure why system apps would remain disabled following a data wipe.
The Google One backup isn't able to back up everything. It cannot back up application data, and it does not back up all system settings.
Regarding the screen, I've noticed the opposite with my Pixel 5. I have "Stay Awake" turned off, but despite having my screen timeout set for 1 minute, it turns off and locks after about 15 seconds.
Battery...Not sure what to tell you.
Consumer electronics are cantankerous beasts indeed and fraught with gremlins.
Click to expand...
Click to collapse
I couldnt think of any other way that some apps retain their disabled state, as well as why would the corrupted message stay even after full stock / full OTA on both slots.
Only thing I can think of is that fastboot update does not overwrite partitions that are already the same version.
Do you think enforcing all partitions flash would get rid of the corrupted warning as well?
As for the google one backup,.. it said it would restore settings, even if its not all of them,.. i dont think it restored any.
sound, display, permissions, gestures, gboard, etc, was all different.
G5-User7080 said:
I couldnt think of any other way that some apps retain their disabled state, as well as why would the corrupted message stay even after full stock / full OTA on both slots.
Only thing I can think of is that fastboot update does not overwrite partitions that are already the same version.
Click to expand...
Click to collapse
Pretty sure it does. I could be wrong.
G5-User7080 said:
Do you think enforcing all partitions flash would get rid of the corrupted warning as well?
Click to expand...
Click to collapse
In theory, yes. Google hasn't exactly released any in depth documentation for the Android Flash Tool. Note that force flashing all partitions will include a data wipe but it's worth a try
G5-User7080 said:
As for the google one backup,.. it said it would restore settings, even if its not all of them,.. i dont think it restored any.
sound, display, permissions, gestures, gboard, etc, was all different.
Click to expand...
Click to collapse
Only thing I can think of is you might have selected a backup that was incomplete or something. Google One takes "snapshots" every once in a while, including after you've signed into Google on your device.
Otherwise, the backup just didn't restore completely?
G5-User7080 said:
Only thing I can think of is that fastboot update does not overwrite partitions that are already the same version.
Click to expand...
Click to collapse
Fastboot does but I don't think Android Flash Tool does unless you select "Force Flash Partitions".
I'm pretty sure the information part of "Force Flash Partitions" says "Flash all partitions that are part of the build even if they are up to date (e.g. bootloader, radio) as well as force a wipe".
At least this language leaves me to believe that that Android Flash Tool won't overwrite partitions that are already up-to-date unless you select "Force Flash Partitions".