Hi,
The last update I have on my Pixel 3a was on October 5th. However, when I go to Google's pages, I see that there were OTA updates in November and December.
When I go to Settings/System/System Update, I can "check for updates", but I always get the message "your system is up to date".
I tried to restore Magisk images and uninstall Magisk, but there is nothing to do, the system is always indicated as up to date.
What should I do to update my phone ? Do you have an idea where the problem can come from?
Thanks in advance for your help.
N.B : Google Play system updates are ok and are dated December 1st. These are the security updates that haven't moved for the last 3 months.
Best way is to either sideload the OTA or flash the factory image. If you go the factory image route, make sure to remove the -w from the flash-all.bat file or it will wipe your phone. There are 2 threads in the Guides section that go into great detail on how to do this. You will have to re-root, again follow the directions in the 2 threads.
jawiler said:
Best way is to either sideload the OTA or flash the factory image. If you go the factory image route, make sure to remove the -w from the flash-all.bat file or it will wipe your phone. There are 2 threads in the Guides section that go into great detail on how to do this. You will have to re-root, again follow the directions in the 2 threads.
Click to expand...
Click to collapse
Thanks. Unfortunately, the "flash_all.bat" solution doesn't work for me. I tried it twice yesterday, the update works but when I restart the phone, it's still in the previous version (RP1A.201005.004).
And I still don't understand why it doesn't detect the new version...
weird, not sure what's happening then. sorry
Ok, I found another way with the OTA update via the recovery. That's solved
Related
So I was away from my computer when the January Security update came out so Im on the December update.
I would like to know can I just jump straight to the Feb update when its available or do I need to do Jan first then Feb?
im unlocked, rooted, ex kernel, google store phone. thanks.
You can just jump.
my phone is on the latest 8.1 april ota.
after the update the phone freezes when placing and recieving phone calls
is it possible to "downgrade" to the previous ota the one from march to test the phone app or will it break the phone
i googled the hell out of this but only found people flashing later releases and not previous ones
thanks
kidhudi said:
my phone is on the latest 8.1 april ota.
after the update the phone freezes when placing and recieving phone calls
is it possible to "downgrade" to the previous ota the one from march to test the phone app or will it break the phone
i googled the hell out of this but only found people flashing later releases and not previous ones
thanks
Click to expand...
Click to collapse
I think downgrading via OTA it's quite impossible.
You have to wipe and flash the full factory image.
damn it thats what i was afraid of.
thanks
kidhudi said:
damn it thats what i was afraid of.
thanks
Click to expand...
Click to collapse
You should've have to wipe. Just flash the full image but remove the -w from the flash all bat file. That saves data and settings. But backup to be sure.
TonikJDK said:
You should've have to wipe. Just flash the full image but remove the -w from the flash all bat file. That saves data and settings. But backup to be sure.
Click to expand...
Click to collapse
i got the verizon varient. it seems i cant oem unlock the device.
i searched all day and cant find a technique that works so flashing the stock image is a no go apparently.
life was so much easier with my nexus 6.
damn verizon.
kidhudi said:
i got the verizon varient. it seems i cant oem unlock the device.
i searched all day and cant find a technique that works so flashing the stock image is a no go apparently.
life was so much easier with my nexus 6.
damn verizon.
Click to expand...
Click to collapse
Time to start clearing data on the dialer related apps, or reset the phone. I am hopeful that will help you. If it was soley update related the forum would be blowing up with complaints.
Now did something go wrong with your update... I'll buy that.
i just assumed it was the april security update it started acting up around the same time. i thought maybe a crappy download
i already did a few factory resets. tried third party dialers. everything i could think of.
what really sucks is i am 3 months out of the 1 year google warranty. so i am pretty much screwed.
thanks for your help bro
i will try to sideload the latest ota.. if it is still jacked up then it is probably hardware related
what sucks is i am still paying it off and it is virtually unusable lol.. at least i can text
Hey guys,
So I've been out of the rooting/unlocking field for a while and kind of forget some of the basic rules.
So my Verizon Pixel was unlocked and rooted immediately after I got it.
It has NOT been updated in any way since then.
I am still on Android 7.1 and the November Security Patch. I figure its time to update now that oreo is out.
Heres the question:
Do I have to flash back to stock before updating? Or can I just flash the OTA update through TWRP? I figure I would have to reflash the recovery and root possibly I'm just not sure which way I should go about it. Also, would doing this wipe my data?
Any help would be greatly appreciated.
Thanks!
Bump
Po1soNNN said:
Bump
Click to expand...
Click to collapse
It would probably be easier to just flash the full factory image using the .bat script it comes packaged with. You could try removing the -w to retain data but I wouldn't count on it booting smoothly with the version jumps you're performing. If it doesn't work, just flash it again with the -w in place and you'll be good to go although you'll have to set everything up and you should make sure anything crucial is backed up somewhere.
Know that the "O" twrp and root flashing instructions are a little different from the Nougat days.
Hey all,
I've restored my girlfriends pixel using the original android 8 image. (It was using PureNexus before). However, she just got the update notification (september update?) but it doesn't do anything when she taps it. The phone should not be rooted, as I used the original clean factory image.
Any suggestions? I've looked at this thread https://forum.xda-developers.com/pixel/help/taking-september-security-update-rooted-t3672586 and so am prepared to download the latest update and remove the "-w" part, but shouldn't it allow her to take the update anyway? Am I going to have to always do this every time they release an update?
Thanks!
It should work, so long as you restored everything to stock - system, bootloader, recovery (dunno if radio matters).
If it's not working most likely there's something custom hanging around somewhere...
I believe it will also fail to update if the bootloader is unlocked. Not sure if you have a VZW device but that's how it works for them. I just update by flashing the full factory image, not an OTA file. Removing the -w will retain user data.
FernBch said:
I believe it will also fail to update if the bootloader is unlocked.
Click to expand...
Click to collapse
Nope, not true. I unlocked my bootloader (not a Verizon phone, bought it from Google), but I've have my phone 100% stock most of the time and I've taken many OTA updates. Including the recent Oreo Sept security update a couple of days ago.
jss2 said:
Nope, not true. I unlocked my bootloader (not a Verizon phone, bought it from Google), but I've have my phone 100% stock most of the time and I've taken many OTA updates. Including the recent Oreo Sept security update a couple of days ago.
Click to expand...
Click to collapse
I think that's the point they're trying to make. Its the Verizon version that is having the update problem if the bootloader is unlocked.
I am having the same issue (have a Verizon Pixel) but am on the ProjectFi network and can't update. I think I'll have to reset and lock the bootloader in order to get the update.
joeyfeffer said:
I think that's the point they're trying to make. Its the Verizon version that is having the update problem if the bootloader is unlocked.
I am having the same issue (have a Verizon Pixel) but am on the ProjectFi network and can't update. I think I'll have to reset and lock the bootloader in order to get the update.
Click to expand...
Click to collapse
Wait wait no. Just download the full image, edit the flashall bat file and remove the-w from it with a text editor. That will flash you back to stock and not wipe your data. Then reroot and so on.
Do not relock it, ever. If something goes wrong and you brick you are toast.
TonikJDK said:
Wait wait no. Just download the full image, edit the flashall bat file and remove the-w from it with a text editor. That will flash you back to stock and not wipe your data. Then reroot and so on.
Do not relock it, ever. If something goes wrong and you brick you are toast.
Click to expand...
Click to collapse
Oh gotcha gotcha.
Weird issue though I couldn't get update to the latest image. I was only able to flash the bootloader and radio. When I tried updating the image it said it couldn't find some of the files. Do I still need to keep the line as "fastboot -w update" when updating the image? won't the "-w" do the wipe?
Nevermind I figured it out. I guess I was inputting the wrong command.
https://www.essential.com/developer/current-builds
Also, just received it on my phone this very moment.
Downloading now! Came to post this exact thing.
UPDATE
Screen shot for those interested
changelog?
mookiexl said:
changelog?
Click to expand...
Click to collapse
Check the screenshot one post right before your!
Magisk install to inactive slot is supposedly fixed in the new version released a few days ago. Installing the OTA now. Will report back if it works.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
edit: hey it works
ziddey said:
Magisk install to inactive slot is supposedly fixed in the new version released a few days ago. Installing the OTA now. Will report back if it works.
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md
edit: hey it works
Click to expand...
Click to collapse
I'm stock rooted with elenentalX. Can I take the OTA now and just reroot and reflash after? Or do I need to unroot prior?
If I try to unroot by restoring images it says "Stock backup does not exist!"
sruel3216 said:
I'm stock rooted with elenentalX. Can I take the OTA now and just reroot and reflash after? Or do I need to unroot prior?
Click to expand...
Click to collapse
I believe you'd fail the OTA if you have an altered boot, but you can try.
oracleoftruth said:
If I try to unroot by restoring images it says "Stock backup does not exist!"
Click to expand...
Click to collapse
I dumped the old boot before rebooting just in case: https://drive.google.com/file/d/11MjB4kTOHuxbUyHe_kIwZ1d0wqp6-Nmf/view?usp=sharing
You can flash it to your boot slot while rooted, take the OTA, and then install magisk to the other slot before rebooting.
Drop a shell.
Determine current boot slot: getprop |grep boot.slot
Flash the boot: dd if=/path/to/boot_b.img of=/dev/block/by-name/boot_b (change to boot_a if that's your slot)
Of course, don't reboot since you'll lose root. Instead, you should now be able to take the OTA, and then use magisk to patch the other slot before rebooting.
Magisk should now have a backup for next time, so you can uninstall/ota/install in the future.
Nice...4 days in, and patched with the security update already.
ziddey said:
I believe you'd fail the OTA if you have an altered boot, but you can try.
Click to expand...
Click to collapse
Was curious cuz I was able to update the OTA on my pixel when rooted with custom kernel.
For some reason after I ran the magisk uninstaller and made sure to flash the stock boot image I still ran into problems updating via OTA and after sideloading the OTA for the Sept Update with success I found that TWRP would seem to freeze whenever it got to the main screen for some reason. I was able to use adb commands to reboot to bootloader and flash the stock kernel for the update and was able to boot normally. Just wondering if anybody else is having issues with TWRP freezing after installing the security update and yes I did remove fingerprint and lock screen security before booting into TWRP so I know its not something from that causing it to freeze.
Anyone try to Fastboot install the Sept update?
Tried 3 times and the screen was unresponsive every time after booting to setup
Finally went back to last months original P release and everything was as normal and updated from there...........
Just installed patch. Scrolling feels so much better, especially when scrolling slow.
gorm said:
Anyone try to Fastboot install the Sept update?
Tried 3 times and the screen was unresponsive every time after booting to setup
Finally went back to last months original P release and everything was as normal and updated from there...........
Click to expand...
Click to collapse
That's exactly what happened to me.. a user on /r/essential said they had the same issue; frustrating!
I'm going to be going back to 8.1 via fastboot, and then flashing 9.0 august, THEN fastbooting september, and if that doesn't work, I'm going to fastboot 9.0 august and then try OTA to
get my screen back.
Really weird stuff.
EDIT: Here's a supposed fix for those with the touchscreen issue - https://www.reddit.com/r/essential/comments/9d0lg3/for_anyone_having_trouble_with_touchscreen_not/
I don't know if we're allowed to link to reddit or not, but I'm doing that fix now.
Thanks!
my PH-1 is no longer recognizing my T-Mobile SIM.
i bought this used & my SIM worked fine up until OTA install. i've tried a different T-Mo SIM & it produces same Invalid SIM error.
the bootloader does show Variant = Sprint. i never did check the bootloader after I purchased it a little more than a month ago.
i'm currently reinstalling August 2018 Release via fastboot & see if that helps.
EDIT:
August 2018 Release resulted in no touch response & unable to progress through setup.
giving June 2018 Release (Oreo 8.1 ) a try via fastboot.
i just want a working phone back
jon_ybanez said:
my PH-1 is no longer recognizing my T-Mobile SIM.
i bought this used & my SIM worked fine up until OTA install. i've tried a different T-Mo SIM & it produces same Invalid SIM error.
the bootloader does show Variant = Sprint. i never did check the bootloader after I purchased it a little more than a month ago.
i'm currently reinstalling August 2018 Release via fastboot & see if that helps.
EDIT:
August 2018 Release resulted in no touch response & unable to progress through setup.
giving June 2018 Release (Oreo 8.1 ) a try via fastboot.
i just want a working phone back
Click to expand...
Click to collapse
Hey Jon,
Go ahead and take a look at my post I just made above yours. It might be able to help
Check the link out in the edit, I'm doing that process now to make sure I get my touchscreen back too.
Thanks!
beard805 said:
Hey Jon,
Go ahead and take a look at my post I just made above yours. It might be able to help
Check the link out in the edit, I'm doing that process now to make sure I get my touchscreen back too.
Thanks!
Click to expand...
Click to collapse
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance
jon_ybanez said:
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance
Click to expand...
Click to collapse
Sadly, I don't know much about the SIM side of the issue
Hope someone with more knowledge can chime in!
jon_ybanez said:
thanks for the info.
touchscreen works again but i still get an Invalid SIM message
i'm a bit lost on what to do next and would appreciate any guidance from yourself or anyone else in the community
thanks in advance
Click to expand...
Click to collapse
Are you rooted? Here are the unlocked modemst files: https://drive.google.com/file/d/1LQC-2QOC-PWX7vza-82tpwFrnUjaGZVq/view?usp=sharing
You can try to dd them:
Code:
dd if=/path/to/modemst1.img of=/dev/block/by-name/modemst1
dd if=/path/to/modemst2.img of=/dev/block/by-name/modemst2
Would be a good idea to backup your current images
from https://forum.xda-developers.com/essential-phone/how-to/discussion-brainstorm-sim-unlock-t3724135
Pixel 7 Pro Sideload OTA for January 2023 FAILED now phone Google image start and stops.
I followed exact instructions and OTA sideload failed. rebooted and now screen just flashes Google every 15 seconds or so. Not sure what to do!
Help!
Sorry I'm at work and don't have much time to help and maybe someone else will chime in. It's stuck in a bootloop. Try using the Pixel Flasher Tool to sideload the OTA or the image
Just flash.
Android Flash Tool
flash.android.com
jaseman said:
Pixel 7 Pro Sideload OTA for January 2023 FAILED now phone Google image start and stops.
I followed exact instructions and OTA sideload failed. rebooted and now screen just flashes Google every 15 seconds or so. Not sure what to do!
Help!
Click to expand...
Click to collapse
More information is needed like are you rooted did you download the correct OTA file what instructions did you follow where did you download the file from
I was able to "fix" my issue and redo the OTA successfully!
I had to use the button combo of Power-volume down to get to a place where I could choose the proper setting and get back to the screen where I could again choose sideload from ADB. This time it completed successfully. Not sure why it failed the first time.
WHEW!!!!!!!
I downloaded from the Google site for OTA files and I chose the proper file.
All is good now and everything appears to be OK.
Thanks to all who quickly responded to my concerns!!!!!!
Just use the web browser to update it if you're using an unlocked phone.
UltimateGamer83 said:
Just use the web browser to update it if you're using an unlocked phone.
Click to expand...
Click to collapse
Even though I was ultimately able to sideload the update using ADB (and all is good on day 2) I am curious as to how this can be accomplished using a web browser? Do you have detailed instructions for such a procedure? I do have an unlocked phone...always!
jaseman said:
Even though I was ultimately able to sideload the update using ADB (and all is good on day 2) I am curious as to how this can be accomplished using a web browser? Do you have detailed instructions for such a procedure? I do have an unlocked phone...always!
Click to expand...
Click to collapse
The Android Flash Tool is used through your web browser https://flash.android.com/welcome?continue=/devices?continue=%2Fcustom
If I am not mistaken this method will "wipe" your device?
That is not a desirable thing unless your phone is hosed.
jaseman said:
If I am not mistaken this method will "wipe" your device?
That is not a desirable thing unless your phone is hosed.
Click to expand...
Click to collapse
You just change the settings to uncheck the options for wipe, force flash partitions, and lock bootloader. I actually used Android Flash Tool to upgrade my phone the other day and it went fine. I just wanted to see how it worked. Going back to PixelFlasher since I want to keep root but yeah, pretty cool tool.