I'll ask here... If I buy a new Pixel phone (4, 4a, etc..) that ships with A10, and I unlock the bootloader and root it, is there a setting to turn off automatic system updates from Google, either A10 or A11beta?
Are Pixels like similar AOSP-like phones (OnePlus) in that the latest full ROM can be flashed manually, re- rooted, etc..?
Yes. You can turn off automatic updates in the developer options. But usually once you root your Pixel it breaks updates. You probably won't be able to update at all through the native settings. You'll have to flash the update manually it do the magisk trick.
Perfect, thanks. I prefer manual updating anyway. If there is serious bug that becomes evident, then I wait for the patched update.
Related
Hi all,
A couple quick questions here. I've done some reading up, but most of the information is more in depth than I need at the moment so I'm looking for some quick answers.
My SO has a Verizon S5, that has a locked bootloader, is not rooted, and is still on 5.0.
She swapped carriers a while back, so is no longer on the Verizon network. The IMEI is clean, and her Verizon account is fully paid, and everything on the phone works fine, aside from it being stuck on 5.0.
It will not update via the automated system, because I assume it's trying to reach out to straight talk for the update and gets a response that it's on the newest version.
I downloaded the Verizon OTA update file (approximately 1 gb) for 6.0.1. It's named update.zip to allow for automated updating.
Here are my questions:
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
Thank you very much for your assistance!
Hi bladebarrier, I actually just did the same thing a few weeks ago with a used S5 from Verizon going to Straight Talk.
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
I'm unsure if that would work, someone else may be able to answer as to that method, however I used the Odin tool v3.11.1, downloaded the PD1 image from here. There are some good video tutorials on YouTube and on writeups on this forum as well regarding how to flash the Marshmallow update using Odin.
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
No downsides that I've noticed and seems to have slightly better battery life.
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
You do not need root to flash it if using the Odin tool.
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
Yes, but it's always a good idea to make a backup of everything.
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
The only thing that the locked boot loader affects for now is the ability to flash custom ROMs. I was able to downgrade to 5.0 Lollipop which you can still root, even after upgrading, however I decided to just go back to Marshmallow and wait for an exploit to be found, if one ever is.
jesimpki89 said:
Hi bladebarrier, I actually just did the same thing a few weeks ago with a used S5 from Verizon going to Straight Talk.
1. Would it be ok to just slap the update file on her phone and let it auto-update using the built in software?
I'm unsure if that would work, someone else may be able to answer as to that method, however I used the Odin tool v3.11.1, downloaded the PD1 image from here. There are some good video tutorials on YouTube and on writeups on this forum as well regarding how to flash the Marshmallow update using Odin.
2. Are there any major downsides to updating to marshmallow, considering it's an official release on the correct version of that phone?
No downsides that I've noticed and seems to have slightly better battery life.
3. Will root be needed prior (I'm assuming not) for using the OTA update file?
You do not need root to flash it if using the Odin tool.
4. Will her information stay intact; email accounts, contacts, apps, samsung account, etc?
Yes, but it's always a good idea to make a backup of everything.
5. While root would be nice for locking down some of the bloatware after, it isn't a deal breaker, simplicity is the key here as she is not an advanced user, but would updating via the OTA file remove all possibilities of rooting the device after (it seems to be the impression I get, as her bootloader is locked)?
The only thing that the locked boot loader affects for now is the ability to flash custom ROMs. I was able to downgrade to 5.0 Lollipop which you can still root, even after upgrading, however I decided to just go back to Marshmallow and wait for an exploit to be found, if one ever is.
Click to expand...
Click to collapse
Thank you very much for your thorough response. It sounds like it will be a nice smooth flash, and I will use the full Odin version instead of the OTA file, to ensure it goes through comfortably.
Odin looked like it wanted to wipe the apps, so I ended up using the stock recovery/installer that's built in, and placing the OTA update file on the external SD card.
That worked like a charm. It took a bit, as expected, but all of the apps and info were ok after.
The only thing I can't sort out is why I can't find an option for the "Themes" setting in touch wiz. Any suggestions? I realize I could have her go to a third party launcher, like nova, but I have all of the theme options on my note 3, that's ported to MM note 5, and the theme option is still right there in the settings list, per normal. Maybe I'm just not seeing it, but I couldn't find an option on her S5 during 5.0, or now on 6.0.1. Is that something they never updated for the older phones?
Hello - I have the prime edition of the Moto but used rootjunkie's RSDLite method to put the non-Amazon version on (build number MPJ24.139-49)
My channel is still set to "amz" and the bootloader is locked. Today I started receiving a message about OTA to the new version of MPJ24.139-64.
Is it safe to install (I've seen others having issues but it looked like they have an unlocked bootloader)? How do I know if this is the Motorola version or the Amazon version (I do not want the ads back)?
I am in the same situation too. I have a locked bootloader and flashed the retail version using RSDLite. I'm on build number MPJ24.139-49. The software channel on my phone is "amz". This evening I also got a message about the OTA update to build MPJ24.139-64. Has anyone in this situation done the update?
bfridman said:
Hello - I have the prime edition of the Moto but used rootjunkie's RSDLite method to put the non-Amazon version on (build number MPJ24.139-49)
My channel is still set to "amz" and the bootloader is locked. Today I started receiving a message about OTA to the new version of MPJ24.139-64.
Is it safe to install (I've seen others having issues but it looked like they have an unlocked bootloader)? How do I know if this is the Motorola version or the Amazon version (I do not want the ads back)?
Click to expand...
Click to collapse
I was in the same situation, updated and got the ads and Amazon apps back. Tryed to remove them and my Moto was stuck in fastboot mode until I managed to fix it. If you don't want the ads back don't update
Caxref said:
I was in the same situation, updated and got the ads and Amazon apps back. Tryed to remove them and my Moto was stuck in fastboot mode until I managed to fix it. If you don't want the ads back don't update
Click to expand...
Click to collapse
Yeah, I can confirm the update puts back all of the Amazon stuff back on the phone. I was looking for a way to get back into the Amazon apps anyways so that I could get the future updates.
Caxref said:
I was in the same situation, updated and got the ads and Amazon apps back. Tryed to remove them and my Moto was stuck in fastboot mode until I managed to fix it. If you don't want the ads back don't update
Click to expand...
Click to collapse
How did you apply the update, get rid of them and get back to normal? I've unlocked the bootloader and installed the systemless root, which I want to keep but I also don't want to skip security updates.
ansong said:
How did you apply the update, get rid of them and get back to normal? I've unlocked the bootloader and installed the systemless root, which I want to keep but I also don't want to skip security updates.
Click to expand...
Click to collapse
Right now I'm stuck with the ads, I couldn't find any way to remove them with this update yet.
Caxref said:
Right now I'm stuck with the ads, I couldn't find any way to remove them with this update yet.
Click to expand...
Click to collapse
I guess I'll hold off then. Thanks.
What are the options moving forward?
1) Is it possible to disable the device from continuously prompting to update? I went to Google Play Services and disabled notifications but that does not stop the system from prompting open the system update app and asking if I would like to update.
2) Can i install the non-Amazon version of the 64 ROM (I'm having difficulty understanding if this works on other threads)? If so, would that stop the device from hounding for system update (until the next release)?
bfridman said:
What are the options moving forward?
1) Is it possible to disable the device from continuously prompting to update? I went to Google Play Services and disabled notifications but that does not stop the system from prompting open the system update app and asking if I would like to update.
2) Can i install the non-Amazon version of the 64 ROM (I'm having difficulty understanding if this works on other threads)? If so, would that stop the device from hounding for system update (until the next release)?
Click to expand...
Click to collapse
Same problem here. Have turned of notifications in Motorola Update services but it has not stopped them. Tried renaming the Motorola OTA update app in / system but unable to due to no root. Do not want the ads but i don't want to be hounded to update either. I guess i will wait another week to see if they stop but if they don't i may take the update and then complain to Amazon about the ads being very intrusive and bright in dim lighting
I know you can't disable motorola update services but what about just blocking all notifications in the app settings for Motorola update services.
I just blocked moto notifications and will see if it works. If it does I'll report back.
Can I update to the non-prime 64 without any expected issues?
While blocking notifications did not work I was able to force disable the moto update does. This has to be done every time after reboot.
Has anyone successfully loaded the non-amazon 64 IMG on a locked Amazon xt1625?
You have to flash a blank but valid oem.img to block updates.
fastboot flash oem oem.img
I'm sure that the rootjunky website has it somewhere...
I want to ask a few things, I'm trying to get this phone all working on the latest things and I can't seem to find concrete answers for why its not working when searching around.
So the first issue is that I'm stuck on 7.0. I enrolled in the beta program and all, but it starts to try to download the update and then suddenly kicks off and goes 'you are up to date' even though I've still only got 7.0. What does that mean? I'm not sure what I'm doing wrong.
Second, I really, really want to use the google assistant. If I do this OTA update will I be unable to root the phone. If I root the phone, can I update to the final release of 7.1 when it comes out in december? And, as I am unfamiliar with this sort of thing, if I change the build.prop to be of a Pixel so I can use google assistant, will that adversely affect anything else on the phone?
Do I even use the OTA update method when I root the phone with TWRP or do I now have to flash things manually?
Hi Guys,
I did not receive OTA for Oreo on my Android One and had to reset my phone to get the OTA update. After that once I installed Nougat Fastboot Rom and it was on August 2017 patch and wasnt receiving OTA again so I flashed Oreo Fastboot Current Rom and later locked the bootloader through fastboot oem lock command. I thought it was only me who is not getting the latest January Patch. Following are my questions:
1. Are we going to get Oreo 8.1 or any patch for january? I am not a beta tester.
2. How do I know if my phone is still receiving OTA?
Bugs encountered, please let me know if any one has the similar bugs.
1. Sudden crash of google chrome, android web view or some other apps like ventura wealth etc.
2. Camera doesnt start sometimes.
3. Battery Drain.
4. Phone rings but there is no caller id when phone is locked.
5. Multiple Contacts for various apps can be seen in native contact apps which makes it difficult to select the required contact.
6. No Fingerprint Gesture control.
7. Mi Remote not able to put shortcuts on desktop and no option to grant permission too.
8. No Flash Notification.
Please let me know something useful.
I have got Nougat Rom of December patch. Is it wise to use that?
So I just flashed Nougat December patch official fast boot rom.
I am not being shown any ota for oreo or for any thing.
Is this normal.
rajputz said:
So I just flashed Nougat December patch official fast boot rom.
I am not being shown any ota for oreo or for any thing.
Is this normal.
Click to expand...
Click to collapse
Yeah, I did a fastboot flash last night. Just got the update. Just wait.
The update rolls out in batches so you just have to wait your turn
KalolParty said:
Yeah, I did a fastboot flash last night. Just got the update. Just wait.
The update rolls out in batches so you just have to wait your turn
Click to expand...
Click to collapse
What you mean is that as soon as I put official fastboot rom, I wont immediately get the OTA. I will have to wait. For eg. I am trying with August Patched Official Tissot rom now.
rajputz said:
What you mean is that as soon as I put official fastboot rom, I wont immediately get the OTA. I will have to wait. For eg. I am trying with August Patched Official Tissot rom now.
Click to expand...
Click to collapse
Stay with the December update since you'll only get OTA if you're on December update.
Just be patient. It may take a day or two or even a week but you'll get it.
Installing a fastboot ROM helps improve your chances but doesn't guarantee anything
Hy,
December Update out now.
Greets
got it too, can't see any fixes though. on the plus side they dont seem to have broken anything either. can call this a "win" i guess
Wondering if people stuck on September version can finally update without resetting data.
Please let us know if you're in this group.
laviniu_c said:
got it too, can't see any fixes though. on the plus side they dont seem to have broken anything either. can call this a "win" i guess
Click to expand...
Click to collapse
I would say the same. Can't expect anything better than this from these system updates.
until when mi a2 will receive updates? will this be the last?
Mi A1 was released with August 2017 security patch and received its last update on August 2020, something similar should happen for Mi A2 too.
birdflesh said:
Mi A1 was released with August 2017 security patch and received its last update on August 2020, something similar should happen for Mi A2 too.
Click to expand...
Click to collapse
thanks for the info! Mi A2 security patches until Aug 2021 (Mi A2 release August 2018)
Since that update my battery drains way faster.
Since that update my battery drains way faster.
+1
I'm still in the September update.
Has anyone with the bootloader unlocked updated their phone? If yes, what were your steps to update it?
ota should work with an unlocked bl, IF you have not changed the system. unlocking means you could change it, it doesnt in itself deny ota updates
salmonthefish said:
I'm still in the September update.
Has anyone with the bootloader unlocked updated their phone? If yes, what were your steps to update it?
Click to expand...
Click to collapse
I´m also waiting for anyone that reported that made the update. I have Setember Update with bootloader unlocked because of camera2api, i don´t made any system changes, and i get all the updates until september without problemes. After that i get Bootloop on October and don´t update anymore. If anyone upgrade from setember with sucess please report.
ki69 said:
because of camera2api
Click to expand...
Click to collapse
you answered your own question. if you've unlocked AND made ANY changes to the system ota can bootloop ofcourse.
With unlocked bootloader factory reset is needed once and only once when updating from any version < 11.0.15.0 (October patch) to any version >=11.0.15.0 regardless of update method (OTA or fastboot reflashing). I suspect that Xiaomy made breaking changes to /vendor and/or other system partitions in 11.0.15.0.
So if you want to fastboot flash 11.0.19.0 over 11.0.14.0 or 11.0.5.0 you will need to make factory reset or just flash with "flash_all.bat/sh".
I've seen reports here that factory reset was also required on fully stock phones when receiving 11.0.15.0 October OTA, and I am really sorry for those users, as they had no chance to update with full recovery of user data.
Those having unlocked bootloader can make full recovery of user data after reset using TWRP backup of /data partition, guide is here:
October 2020 Security Update now available
October Security Update just released today.
forum.xda-developers.com
Aerobatic said:
With unlocked bootloader factory reset is needed once and only once when updating from any version < 11.0.15.0 (October patch) to any version >=11.0.15.0 regardless of update method (OTA or fastboot reflashing). I suspect that Xiaomy made breaking changes to /vendor and/or other system partitions in 11.0.15.0.
So if you want to fastboot flash 11.0.19.0 over 11.0.14.0 or 11.0.5.0 you will need to make factory reset or just flash with "flash_all.bat/sh".
I've seen reports here that factory reset was also required on fully stock phones when receiving 11.0.15.0 October OTA, and I am really sorry for those users, as they had no chance to update with full recovery of user data.
Those having unlocked bootloader can make full recovery of user data after reset using TWRP backup of /data partition, guide is here:
October 2020 Security Update now available
October Security Update just released today.
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you.
A question, if i unlock the bootloader afterwards will the same issue pop up again?
salmonthefish said:
A question, if i unlock the bootloader afterwards will the same issue pop up again?
Click to expand...
Click to collapse
I believe neither Xiaomi nor Google can answer this question.
Anyway,
1) right now factory reset for unlocked MiA2 is needed only once when updating from any previous ROM version to any currently available ROM version >= 11.0.15.0;
2) having unlocked phone one is sure that his data can be restored in any future mishap;
3) unfortunately unlocked phone prevents usage of most of banking apps unless Magisk + Riru + edXposed installed with MagishHide On and GooglePlayServices in Blocked List (SafetyNet issue).
So everyone decides himself whether to
a) keep phone untampered (with risk of loosing data with next OTA bootloop),
b) or unblock phone and then stay with updating stock (spending some time to get root, make SafetyNet passable, remove annoying settings suggestions, customize UI, etc.) ,
c) or unblock phone and then revert to Android 9 10.0.17.0 (disabling updates),
d) or unblock phone and then escape to a Custom ROM.
I personally prefer option (b) since my first Android gadgets (never bought a phone/tablet which had problems with rooting).
19Gerhard85 said:
Since that update my battery drains way faster.
Click to expand...
Click to collapse
19Gerhard85
after updating "Google Find my Device" app battery holds like before all ok now but i never use that app not even logged in calendar app also updated at same time but i don't thin it was calendar