Greetings, I have a Project Fi Android One X4. Two days ago I went back to Project Fi Oreo stock after being rooted in order to receive the OTA. I received the January, February, and March security updates. But once I attempt to get the April one with 8.1, the system says I am up to date. I attempted to sideload the April OTA but got the message many get about not being able to mount. I know that these updates are not rolled out all at once, but I see many here in the forum already got it. Is there any way I can force the OTA? Thanks in advance for the help!
I'm pretty much in the same boat. I had to manually flash the full 8.0 firmware after being stuck on Dec security update. Received Jan, Feb and March updates OTA without a problem. Got notification that 8.1 April was available. Phone would download the OTA but fail halfway through the installation. Did this about a dozen times. Now phone says up to date but still on March 8.0.
Probably have to wait for the full firmware file to be released and manually flash again. Sucks. Never could get ADB sideload or update from SD card to work either.
jfalls63 said:
I'm pretty much in the same boat. I had to manually flash the full 8.0 firmware after being stuck on Dec security update. Received Jan, Feb and March updates OTA without a problem. Got notification that 8.1 April was available. Phone would download the OTA but fail halfway through the installation. Did this about a dozen times. Now phone says up to date but still on March 8.0.
Probably have to wait for the full firmware file to be released and manually flash again. Sucks. Never could get ADB sideload or update from SD card to work either.
Click to expand...
Click to collapse
Same issue for me. The ADB sideload/SD card problem doesn't make sense.
Same here. OTA update fails during step 3. Side loading doesn't work. I reflashed 8.0 and took all three security updates again just fine. Now I'm not even offered the OTA for 8.1.
I have a theory that it was pulled due to errors.
ptn107 said:
Same here. OTA update fails during step 3. Side loading doesn't work. I reflashed 8.0 and took all three security updates again just fine. Now I'm not even offered the OTA for 8.1.
I have a theory that it was pulled due to errors.
Click to expand...
Click to collapse
You think the 8.1 update was pulled due to errors? I was offered the update on my stock (locked and unrooted) Project Fi X4 a week ago, and my wife's got it on Friday (3 days ago). The update process was quick and went through without issues. The phones themselves seem to be operating normally.
rczrider said:
You think the 8.1 update was pulled due to errors? I was offered the update on my stock (locked and unrooted) Project Fi X4 a week ago, and my wife's got it on Friday (3 days ago). The update process was quick and went through without issues. The phones themselves seem to be operating normally.
Click to expand...
Click to collapse
Have you tried MTP or ADB (with lockscreen enabled), cause this would be the first confirmed case I've seen of it working properly on 8.1 update.
Thanks for all the responses! I see that I am not the only one with this issue. I think that like jfalls63 said, of we don't get the update in the coming days we will have to wait for the full firmware release. It is not convenient since I want to root and wanted to do it in 8.1, but there is not much we can do about it if we cannot find an alternative.
QWZR II said:
Have you tried MTP or ADB (with lockscreen enabled), cause this would be the first confirmed case I've seen of it working properly on 8.1 update.
Click to expand...
Click to collapse
You're right; I haven't had any reason to do either since the update and it wasn't until after I posted that I saw another thread mentioning this issue. Sure enough, same is true for me.
Still, the update was pushed to one of our phones only a couple of days ago, so if they pulled it, it's only been within the last 72 hours or so.
I'm experiencing a similar thing (https://forum.xda-developers.com/moto-x4/help/oreo-8-1-update-stuck-loop-t3788293), so this seems to be a prevalent problem.
When I have time, I'll go through the Moto forums and see if anyone has any helpful information.
I'm on Fi and I received the 8.1 update just fine. I haven't unlocked my bootloader yet to root it, but otherwise I'm on the gravy train. Once they release a full sized firmware I plan to reflash to get my space back, and then root.
The only solution i've found to get the OTA to work (verified by others as well as my self)
Reboot after each fail and try again - if you watch the screen the % complete will increase each time before fail, eventually ending in a successful upgrade! (At which time your phone is now more secure than ever - USB file transfer won't work with a lock screen pin/pattern/fingerprint.
So wonder why I have never gotten a single update pretty much since I got this phone 6 months ago. When i got it the first thing i did was unlock the bootloader and rooted it.
So I saw there was a June update of this year. Well I decided to go and look at my phone and oh look! June 1 update! yea from 2017. So when I do an update I get a "Check for update was not available at this time. Try again later"
I don't have any of the update apps blocked with Titanium either. Any help and\or ideas would be great.
On my Turbo it would still get updates, but fail because of TWRP at least and i would flash stock recovery just to update then flash twrp back on.
Thanks
Magisk Manager v16
Rooted
Unlocked
Recovery - TWRP 3.2.1-r16
Build: NPS26.116-45
Stock ROM
So the new november patch was rolled out and i decided to install it. I was kinda surprised it let me install it while my phone was already rooted in the first place, but as i thought the patch had gotten rid of the root. I tried to root the phone again using the Mi A2 Toolkit by Daha3ker
Link: https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
And now when it tries to reboot it gets stuck on the sliding colours right after the android one logo.
Any help would be much appreciated guys
thanks,
exoticpenguins
tool is outdated. Next time read the full guide. it says :Version 1.0.6 only tested September Update:
Matteo
Hey all,
Last night before going to bed, I was on the Dec patch. Magisk was installed because I was using my hotspot. I woke up this morning, unable to turn my hotspot on and when I checked Magisk, it was no longer installed. I went to my Android version and now see that I'm on security patch level March 5 2020. So, it seems as if my phone patched over night... I never had a warning that there was update or anything. Has this happened to anyone else?
Question: So, since I heard Magisk is having a hard time hiding root from certain apps, can I flash back to the Dec, Jan, or Feb patch without any issues? Or am I stuck on the March patch level now?
Question 2: What's the best way to make sure OTA's aren't auto-installed again?
ihuntinde said:
Hey all,
Last night before going to bed, I was on the Dec patch. Magisk was installed because I was using my hotspot. I woke up this morning, unable to turn my hotspot on and when I checked Magisk, it was no longer installed. I went to my Android version and now see that I'm on security patch level March 5 2020. So, it seems as if my phone patched over night... I never had a warning that there was update or anything. Has this happened to anyone else?
Question: So, since I heard Magisk is having a hard time hiding root from certain apps, can I flash back to the Dec, Jan, or Feb patch without any issues? Or am I stuck on the March patch level now?
Question 2: What's the best way to make sure OTA's aren't auto-installed again?
Click to expand...
Click to collapse
Magisk passing Safety Net (hiding root) is working (fixed).
Settings > System > Developer options > turn off Automatic updates.
I have a Pixel 5 and today I updated from redfin-2110-rq3a.211001.001-factory-23f4cec2 to redfin-2111-sp1a.211105.004-factory-749e8f9f (yes the Aus version).
All went well until I tried to root the device using Magisk - something I've done *many* times. The trouble is that after I flashed the patched boot.img, the device would not boot - it started to for a few seconds and then went back into fastboot mode.
I've tried a few times but always the same result.
And it seems that you cannot rollback to the October release - the flash-all.sh completes OK but the subsequent boot hangs.
BTW: I'm still using the canary channel, is this still necessary?
Help.
Was that an update from A11 to A12? If so you're gonna have to jump through some hoops...
Either way, this is very likely not a Magisk issue, but caused by some new verification stuff in Android 12, so the best place for you to find info/help is going to be in your device's forum.
Upgrade was from the October version, so, to the best of my knowledge, Android 12
Still, you're likely going to find the answer in the Pixel 5 forums...