OTA in Unlocked Bootloader - Google Pixel 3a Questions & Answers

Hi, i have a Pixel 3A XL with Unlock Bootloader, no root, its possible receive OTA normally?
Regards

albertohds said:
Hi, i have a Pixel 3A XL with Unlock Bootloader, no root, its possible receive OTA normally?
Regards
Click to expand...
Click to collapse
Yeah you can ...
Even if you root your phone still you can get ota and applied on it easily

mayankparihar577 said:
Yeah you can ...
Even if you root your phone still you can get ota and applied on it easily
Click to expand...
Click to collapse
I've been wondering the same thing, do you have to do anything differently or just receive the Ota like normal? I've read in some cases people having to flash a modified zip to receive the update but I'm not sure if that was this device or not.

suckoos said:
I've been wondering the same thing, do you have to do anything differently or just receive the Ota like normal? I've read in some cases people having to flash a modified zip to receive the update but I'm not sure if that was this device or not.
Click to expand...
Click to collapse
You need to flash stock boot img. If you're on a custom kernel.

In theory you should be able to take an OTA update on an unlocked and rooted phone. However in real life it doesn't seem to work out that way very often. In the 8 months I've owned my Pixel 3a XL, I've been successful at taking an OTA update about three times.
You need to familiarize yourself with the "sideload" process of installing an OTA update for the times the normal process does not work. I've created a "How to" thread that talks about rooting as well as taking OTA updates and sideloading updates. It should have all the information you need. https://forum.xda-developers.com/pixel-3a/how-to/how-to-root-pixel-3a-preferred-t3938783

Related

Un-root & lock Galaxy Nexus?

Earlier I unlocked and rooted my Sprint Galaxy Nexus using GNextoolKit 7.9. I did not flash a different ROM. I have Android 4.0.4 L700.FG01.
Since the news is that Sprint is pushing JB out starting today, I would like to bring my phone back to stock and allow the OTA update.
I probably will not unlock again until a K version appears.
Is there a step-through to restore to stock using GNexToolKit 7.9? I am afraid I need pretty detailed guidance.
As far as I know you don't need to re-lock your Nexus to receive OTA updates, and I don't know if you need to unroot, but you might lose root after update anyway
OTA Updates
Ma7moud90 said:
As far as I know you don't need to re-lock your Nexus to receive OTA updates, and I don't know if you need to unroot, but you might lose root after update anyway
Click to expand...
Click to collapse
Agreed... some roms include stopping ota updates so it's not the unlocked bootloader that stops updates. You should get the update but you may lose root afterwords.
RJFrank33 said:
Agreed... some roms include stopping ota updates so it's not the unlocked bootloader that stops updates. You should get the update but you may lose root afterwords.
Click to expand...
Click to collapse
thanks for the replies. I will just sit tight and see what happens when Sprint gets around to me.
toolkit
GranPaSmurf said:
thanks for the replies. I will just sit tight and see what happens when Sprint gets around to me.
Click to expand...
Click to collapse
I have verizon galaxy nexus in our forums I believe their our 2 toolkits that someone made that relock and unroot a phone. I would bet under sprint section 1 for your phone to
thanks
tlawiv said:
I have verizon galaxy nexus in our forums I believe their our 2 toolkits that someone made that relock and unroot a phone. I would bet under sprint section 1 for your phone to
Click to expand...
Click to collapse
thanks, I will keep this info and refer back if I need to.

Root and still getting OTA updates theory

Hi XDA-Devvers,
In a topic (http://forum.xda-developers.com/showthread.php?t=1510719) I read about the following:
Nonverbose said:
Root won't stop an ota but an unlocked bootloader will. You can check in your boot screen if its still unlocked or if its relocked.
Click to expand...
Click to collapse
Doesn't that mean that we can root our tablet, lock the bootloader again (fastboot oem lock), install Voodoo OTA RootKeeper and once there's an OTA available, just backup the root with the Voodoo app and install it?
How awesome would that be :laugh:
Since I am not a pro in that kind of stuff: Can anyone confirm this theory might actually work for real?
fastboot oem lock is unavailable once you unlocked the bootloader.
Ah bummer. Can we relock the bootloader yet? IF we were able to relock the bootloader, it would work, wouldn't it?
TomONeill said:
Ah bummer. Can we relock the bootloader yet? IF we were able to relock the bootloader, it would work, wouldn't it?
Click to expand...
Click to collapse
No, as many informations -including bootloader version- are sent to check if a new OTA is available
alx5962 said:
No, as many informations -including bootloader version- are sent to check if a new OTA is available
Click to expand...
Click to collapse
Okay, thank you for replying. This makes the decision to root a little harder since I want to keep getting updates and for that you'll need ClockWork (and the people who are pushing the update to XDA)(Clockwork does have the nandroid backup though, which I want to have when rooting), which doesn't run very stable last time I read (I rooted before, but then I sent my tab back (heat problems) and got a new one. I flashed a beta ROM xd).
I thanked your post
Isn't it enough to have the original Kernel and ROM? Do you really need a locked bootloader to get OTA updates?
Has anyone tested the universal root method? See http://forum.xda-developers.com/showthread.php?t=1886460
As this doesn't effect the Kernel, OTA updates might work if rooting works with this method.
I've not tried it. I've read some people are bricking their tablets with the universal, and since the A700 is basically a brick waiting to happen, I think I'll pass on it for a while.

[Q] phone wont boot after 4.4 update PLEASE HELP

This morning i finally relented and installed the 4.4 update (kitkat?) on my droid razr maxx hd. now im stuck at the red M motorola splash screen thing. is there any way i can fix this? I went to verizon and they wouldent do anything for me. I need my phone for work every day so help is greatly appreciated. i also tried the power volume down to restore factory settings or whatever but it just goes to the M screen forever. the only thing that DOES come up from those menus is ap fast boot. not sure if thats helpful or not. PS im new to this stuff so noob friendly responses please!
Were you rooted at all? Did you modify your system in any way (froze or uninstalled stock apps)? If so, that's why.
Go here to get yourself back in shape:
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
f
i used a one click root method and always used voodoo ota rootkeeper other than that i havent changed anything else.
i will try this link and post back in a couple hours i have to go take care of a few things. thank you for the quick response.
KiraTheSavior said:
i used a one click root method and always used voodoo ota rootkeeper other than that i havent changed anything else
Click to expand...
Click to collapse
That's your issue. You can't do an OTA after you've rooted since the OTA does a verification to ensure the system isn't modified in any way.
Go to the link I posted in my previous reply to you to get yourself updated to Kit Kat and then unlock you bootloader if you haven't since the KK update put the bootloader exploit back in.
ok
iBolski said:
That's your issue. You can't do an OTA after you've rooted since the OTA does a verification to ensure the system isn't modified in any way.
Go to the link I posted in my previous reply to you to get yourself updated to Kit Kat and then unlock you bootloader if you haven't since the KK update put the bootloader exploit back in.
Click to expand...
Click to collapse
attempting it now. will post results.
it worked!
KiraTheSavior said:
attempting it now. will post results.
Click to expand...
Click to collapse
it worked im on kitkat and everythings great! thank you so much for the help! it was really easy with the step by step you linked. now i think ill try rooting and unlocking, if i mess it up i can always flash it like i just did and fix it right?
could you link me to the root/unlock tutorial for my phone? sorry im noob XD
Just to be sure, you didn't update to the latest soak that just came out, correct? You are on the previous Kit Kat OTA right?
If you haven't applied the latest soak (183.46.10.XT926), then you are golden and can unlock. ONLY apply the soak update AFTER you've unlocked your bootloader.
no
iBolski said:
Just to be sure, you didn't update to the latest soak that just came out, correct? You are on the previous Kit Kat OTA right?
If you haven't applied the latest soak (183.46.10.XT926), then you are golden and can unlock. ONLY apply the soak update AFTER you've unlocked your bootloader.
Click to expand...
Click to collapse
no my system information says 183.46.10 i dont know what a soak update is i just clicked install on that annoying install 4.4 update message ive had for weeks (which broke my phone) other than that i havent done anything. is my phone rootable?
KiraTheSavior said:
no my system information says 183.46.10 i dont know what a soak update is i just clicked install on that annoying install 4.4 update message ive had for weeks (which broke my phone) other than that i havent done anything. is my phone rootable?
Click to expand...
Click to collapse
You should have just ignored the update until after you unlocked the phone. The link I sent you to was meant to get you updated to KK before the 183.46.10 update. The previous KK update allowed you to unlock your bootloader. Now, that is no longer possible. There is no way to downgrade to a previous version. Once the ability to unlock has been patched, you cannot go back and try to unlock it.
You can still root the phone, though. Search for towelroot and you can install that and run it to root your device.
One thing you could try is once you've rooted, try running Motopocalypse to see if it will unlock your bootloader. Either it will or it won't. It won't hurt your phone in any way or brick it.
lame...
iBolski said:
It's rootable but it's not unlockable anymore. You have lost the ability to unlock the bootloader. There is no way to downgrade to a previous version. Once the ability to unlock has been patched, you cannot go back and try to unlock it.
Search for towelroot and you can install that and run it to root your device.
Click to expand...
Click to collapse
figures. thats me always a day late and a dollar short.
KiraTheSavior said:
figures. thats me always a day late and a dollar short.
Click to expand...
Click to collapse
WHOA! WHOA! WHOA! My bad. You should be okay to unlock!
Please go here and attempt it -> http://www.droidrzr.com/index.php/topic/46155-rootunlock-442-182183-razr-hdm-only/
Get Towelroot and run it. This should root your phone -> http://www.towelroot.com/
Next, get the motopocalypse apk from here -> http://forum.xda-developers.com/showpost.php?p=53428225&postcount=22
Install and run that on your phone. That should then unlock your bootloader.
So, you are fine. I completely brain farted that the soak test hasn't been sent to everyone. It is available to download and install, but don't do it yet.
PLEASE go and unlock your phone. I'm so sorry for the confusion.
Let me know how it goes!
hotspot
KiraTheSavior said:
figures. thats me always a day late and a dollar short.
Click to expand...
Click to collapse
is there a working exploit to make the mobile hotspot app work again? i always used the sqlite exploit to turn off subscription check but its still set to 0 on mine and the hotspot still wont work. im rooted by the way
?
KiraTheSavior said:
is there a working exploit to make the mobile hotspot app work again? i always used the sqlite exploit to turn off subscription check but its still set to 0 on mine and the hotspot still wont work. im rooted by the way
Click to expand...
Click to collapse
my system version says 183.46.10xt926 that link says its not unlockable. when i used the link in your original post to get my phone working again I automatically had this version. so i cant unlock right? ?_?
KiraTheSavior said:
my system version says 183.46.10xt926 that link says its not unlockable. when i used the link in your original post to get my phone working again I automatically had this version. so i cant unlock right? ?_?
Click to expand...
Click to collapse
No, that is the version you CAN unlock. At first, it was believed it couldn't happen, but someone discovered that Moto had accidentally added the bootloader unlock exploit back in with the KK release. It's the version after that, which hasn't been released yet but will be soon, that patches the exploit back up to no allow it. The zip file for it is available outside of the soak test so it hasn't been sent to you. What you took was the OTA you do want which does allow unlocking.
Please, go unlock your phone now before the OTA is released and then you'll be forever locked.
Go here to unlock it -> http://www.droidrzr.com/index.php/topic/46155-rootunlock-442-182183-razr-hdm-only/
Do it now before you do anything else. Do NOT apply the soak test OTA (which is available via a media fire link from SamuriHL) until you've unlocked your phone.
done
Rooted and unlocked. Very happy about it. But now what? What can I get with bootloader unlocked besides revert to jb?
I still need to get my WiFi tether app to work. I'm grandfathered into unlimited data so my phone is basically my internet. Are there any cool ROMs where the WiFi just works with no tricks or work a rounds?

Is there any way to install OTAs with an unlocked bootloader / root?

Sorry for making another thread so soon, but I've got new issues now. TL;DR, I'm just trying to get my Moto G7 Power to detect my sim card at *all* anymore. I've been told that installing an OTA will make the phone detect the sim card again, but... I can't re-lock my bootloader.
I've spent pretty much all day looking for ways to re-lock it, but not a single one has worked. I always get the same "Still waiting for signed boot.img" message, even when I try fixes that worked for others. At this point, I give up on trying to re-lock. I just rooted using a guide here and connected to WiFi.
The next best thing would be for me to find another way to install OTAs. I've heard Magisk used to be able to hide your bootloader status and let you do that, but can't anymore, so...
1. Is there a way for me to install official android updates manually? If so, how?
2. If there is, *where* do I find the updates?
T-Mobile [PCO29.114-54-2]
XT1955-5
Tsukomasi said:
Sorry for making another thread so soon, but I've got new issues now. TL;DR, I'm just trying to get my Moto G7 Power to detect my sim card at *all* anymore. I've been told that installing an OTA will make the phone detect the sim card again, but... I can't re-lock my bootloader.
I've spent pretty much all day looking for ways to re-lock it, but not a single one has worked. I always get the same "Still waiting for signed boot.img" message, even when I try fixes that worked for others. At this point, I give up on trying to re-lock. I just rooted using a guide here and connected to WiFi.
The next best thing would be for me to find another way to install OTAs. I've heard Magisk used to be able to hide your bootloader status and let you do that, but can't anymore, so...
1. Is there a way for me to install official android updates manually? If so, how?
2. If there is, *where* do I find the updates?
T-Mobile [PCO29.114-54-2]
XT1955-5
Click to expand...
Click to collapse
Retus one u need to flash do u have the bat file? Try flashing the modem non -hlos.bin in fastboot mode
You can install OTAs with unlocked bootloader, but you'll need to unroot your device first
Sorry for being 2 weeks late, but you look like you're in the exact same position I once was. Flashing an official update for my channel, available at https://mirrors.lolinet.com/firmware/moto/ocean/official/ was what solved it for me, for whatever reason. (my SIM also wasn't recognized at all, nor did I have any IMEIs outside of bootloader. Also, the option to enable OEM unlocking never became available to me, despite instantly being available when I solved it)
We're technically able to install OTAs with unlocked bootloaders? But for some reason mine throws up an error at step 3/6 every time, so I'm dependant on Lolinet to install them.
On relocking bootloader, you had to re-flash boot.img, run the command 3 times, re-flash and run the command again or something, I was also going to try that on one of my threads, but since I couldn't enable OEM unlocking.
Hyoretsu said:
Sorry for being 2 weeks late, but you look like you're in the exact same position I once was. Flashing an official update for my channel, available at https://mirrors.lolinet.com/firmware/moto/ocean/official/ was what solved it for me, for whatever reason. (my SIM also wasn't recognized at all, nor did I have any IMEIs outside of bootloader. Also, the option to enable OEM unlocking never became available to me, despite instantly being available when I solved it)
We're technically able to install OTAs with unlocked bootloaders? But for some reason mine throws up an error at step 3/6 every time, so I'm dependant on Lolinet to install them.
On relocking bootloader, you had to re-flash boot.img, run the command 3 times, re-flash and run the command again or something, I was also going to try that on one of my threads, but since I couldn't enable OEM unlocking.
Click to expand...
Click to collapse
Every OTA zip first verifies your entire system by checksums. Is there any modified partition the verifier fails and the update process ends with an error.
WoKoschekk said:
Every OTA zip first verifies your entire system by checksums. Is there any modified partition the verifier fails and the update process ends with an error.
Click to expand...
Click to collapse
Probably my Magisk then, but meh

Question Returning to stock ROM&closing the bootloader?

Hi, a little question. If I closed the bootloader and returned to the stock ROM with no root, will I receive OTA updates again? Also another question, I want to modify some files before I flash the rom like I want to remove samsung emoji and put ios emoji in their place, is it possible?
kingozilla said:
Hi, a little question. If I closed the bootloader and returned to the stock ROM with no root, will I receive OTA updates again?
Click to expand...
Click to collapse
I've heard people say that you do get OTA if you flash stock and re-lock your bootloader but never tested it myself.
kingozilla said:
Also another question, I want to modify some files before I flash the rom like I want to remove samsung emoji and put ios emoji in their place, is it possible?
Click to expand...
Click to collapse
No, any modification will be detected as custom and won't be able to be flashed with a locked bootloader.
You can receive OTA and update normally after locked bootloader
ShaDisNX255 said:
I've heard people say that you do get OTA if you flash stock and re-lock your bootloader but never tested it myself.
No, any modification will be detected as custom and won't be able to be flashed with a locked bootloader.
Click to expand...
Click to collapse
Ok thank you, I downloaded the stock rom and wont return to root in near future, because I strongly want the stability over apps - bank apps and phone, and I want encryption, and not anymore have more time for this. But how can I close the bootloader to receive OTA updates? Does installing it just normally through odin close it?
kingozilla said:
Ok thank you, I downloaded the stock rom and wont return to root in near future, because I strongly want the stability over apps - bank apps and phone, and I want encryption, and not anymore have more time for this. But how can I close the bootloader to receive OTA updates? Does installing it just normally through odin close it?
Click to expand...
Click to collapse
Make sure you are at stock. Boot into unlock mode again, do it the same like unlock, it will lock your bootloader. When stock boot up, enable Developer option, turn off allow OEM unlocking, reboot. Now you are able to receive OTA normally.

Categories

Resources