Database Info

[Q] Rooting a new droid ultra 4.4?

Ok, so I have been scouring the interwebs for 4 hours now, and I am getting 100 conflicting stories. I am not sure if I can post youtube links, but one says That I can use Kingo (didn't work for me) another was from FrenchGrape100 Neither worked for me, downloaded everything they said, did it all OTA. If anyone has any information, please reply.
Thank you in advance!
~Kevin D.

Okay, here's a TL;DR on the Droid lineup root situation. Essentially, you're out of luck at this point. No root for you! (Or for me, or for a lot of other annoyed users out there. You're not alone.)
Let me reiterate: if you currently have a brand new Droid running 4.4, no root is possible at the moment.
That being said, you're probably getting mixed accounts of this because of the following. Droid Maxx/Ultra/Mini sounds a lot like the Moto X--and they're very similar phones. However, the Moto X DOES have root on 4.4. It's a complicated process that involves downgrading to 4.2, installing a backdoor, and upgrading again to 4.4, then using the backdoor to regain root access. However, as the Droid Maxx/Ultra/Mini have locked bootloaders, it is not possible to downgrade after accepting the OTA upgrade to KitKat 4.4, and most new phones in the lineup are being shipped out with 4.4 already installed.
The first inkling of possible root was when noted dev and exploit-master jcase mentioned, tangentially and on twitter, that he HAD found an exploit for our phones. However, the exploit is not suitable for casual user usage, and still doesn't unlock write protection on the phone, making it essentially useless. Oh, and as a result of the locked write protection, root would be lost any time you restarted the phone. Jcase will be revealing the exploit at the blackhat conference this coming August as a teaching tool, but don't expect it to turn into anything we'll be seeing a solution out of.
The next glimmer of hope came a few weeks ago; remember how I said we couldn't downgrade because of our locked bootloaders? Some Motorola employee started selling bootloader unlock codes for the Droid lineup. You could send the guy 40 bucks and your IMEI number and he'd send you back a device-specific code to unlock your bootloader. Which through an even more complicated process, does eventually allow for root. However, as of about 2ish (?) weeks, the guy selling the codes has stopped; it seems like he/she/them/it/whatever no longer has access to the database containing the unlock codes. A few lucky people got codes before that happened--the process seemed sketchy, and those of us like myself who hesitated are now left with locked down phones.
So yeah, at various points, it's been possible to get root--which, when trying to read up on this stuff, makes it a tad hard to follow.
No root now, though, not if you're already on KitKat 4.4.
Sorry for the disappointment. Keep your ear to the ground in case someone offering codes pops up again and is legit--but I wouldn't hope too hard.

I am one among those few lucky people who got code and unlocked the BL and enjoying root now in 4.4.
@Jumnhy
However, the Moto X DOES have root on 4.4. It's a complicated process that involves downgrading to 4.2, installing a backdoor, and upgrading again to 4.4, then using the backdoor to regain root access. However, as the Droid Maxx/Ultra/Mini have locked bootloaders, it is not possible to downgrade after accepting the OTA upgrade to KitKat 4.4,
Click to expand...
Click to collapse
I want to add only one extra info to make things more clear. Actually BigRed's Moto X is also coming with locked / encrypted BootLoaders like DroidMini/Maxx/Ultra, but since its 4.4 update came first and without signature verification / check and hence downgrading was possible in its case. But in 4.4 of Droid series, the mistake was corrected and downgrade was IMPOSSIBLE.
So Droid users with 4.4 and NO root has to live without root in the future, unless any wonder occurs (like the earlier code purchase).
Moral of the Story:
If you want root access in Droid or other BigRed's phones, buy their Dev edition in future.

Good clarification. Missed that point myself!

This is really disheartening. I had one Droid Maxx back before the update and like an idiot, I updated without researching first. Now I got my insurance to replace the phone hoping that they'd send me one which hasn't been updated yet and instead they sent me one with 4.4 pre-installed. So I started researching and I thought it was possible because I saw a thread where an XDA user... Einstein something or other... said he got the downgrade to work. I think I'm just going to sell the phone and either try to buy one without the update or get a different phone.

ThunderWulf said:
This is really disheartening. I had one Droid Maxx back before the update and like an idiot, I updated without researching first.
Click to expand...
Click to collapse
my dear thunder, you are not alone.... i miss tethering my internet....

nerdyplayer said:
my dear thunder, you are not alone.... i miss tethering my internet....
Click to expand...
Click to collapse
Tethering does not require root. Now if you want wireless hotspot no frills then yes you need root.
You could use easy tether pro to tether just fine without root. But if you wanted to share that connection with more devices the first one would have to remain on. You can bridge the connection to your wireless card and share it.
Sent from my Nexus 7 using Tapatalk

kanagadeepan said:
I am one among those few lucky people who got code and unlocked the BL and enjoying root now in 4.4.
@JumnhyI want to add only one extra info to make things more clear. Actually BigRed's Moto X is also coming with locked / encrypted BootLoaders like DroidMini/Maxx/Ultra, but since its 4.4 update came first and without signature verification / check and hence downgrading was possible in its case. But in 4.4 of Droid series, the mistake was corrected and downgrade was IMPOSSIBLE.
So Droid users with 4.4 and NO root has to live without root in the future, unless any wonder occurs (like the earlier code purchase).
Moral of the Story:
If you want root access in Droid or other BigRed's phones, buy their Dev edition in future.
Click to expand...
Click to collapse
Do you mind sort of breaking down the process you did once you got the code and how the code was styled. Alpha-numeric? 10 digits? Things like that. I am considering that since there is a code and method for unlocking the device in an offline setting, that could be bruteforced using strong hardware GPU. (Which I tend to have these days thanks to virtual currencies.)
I am going to run on the assumption Motorola won't lock out a user for multiple incorrect attempts but who knows.

netuoso said:
Do you mind sort of breaking down the process you did once you got the code and how the code was styled. Alpha-numeric? 10 digits? Things like that. I am considering that since there is a code and method for unlocking the device in an offline setting, that could be bruteforced using strong hardware GPU. (Which I tend to have these days thanks to virtual currencies.)
I am going to run on the assumption Motorola won't lock out a user for multiple incorrect attempts but who knows.
Click to expand...
Click to collapse
It's a 20 digit Alpha numeric code. You enter the code in fastboot mode using the command fastboot oem unlock <code> Since there are 36^20 possible combinations good luck bruteforcing THAT

I think the BL unlock is no longer available from what I have been reading. If anyone has had success lately please correct me.
Sent from my DROID MAXX using Tapatalk

BladeRunner said:
It's a 20 digit Alpha numeric code. You enter the code in fastboot mode using the command fastboot oem unlock <code> Since there are 36^20 possible combinations good luck bruteforcing THAT
Click to expand...
Click to collapse
I know that this question is rhetorical, as reverse engineering this is probably not possible, but is it full alphabet, or only the hex characters a-f for the alpha characters? That's a smaller alphabet. (Also, if it is upper and lower case letters, that's at least a 62 character alphabet, so 62^20. If they are just hex digits, that's "just" 16^20.)

doogald said:
I know that this question is rhetorical, as reverse engineering this is probably not possible, but is it full alphabet, or only the hex characters a-f for the alpha characters? That's a smaller alphabet. (Also, if it is upper and lower case letters, that's at least a 62 character alphabet, so 62^20. If they are just hex digits, that's "just" 16^20.)
Click to expand...
Click to collapse
full alphabet and I have only seen upper case letters

unlock code
an21281 said:
I think the BL unlock is no longer available from what I have been reading. If anyone has had success lately please correct me.
Sent from my DROID MAXX using Tapatalk
Click to expand...
Click to collapse
I just tried to purchase the code. Be guy says no more 2013 codes. Only 2014 production

JarMagic said:
I just tried to purchase the code. Be guy says no more 2013 codes. Only 2014 production
Click to expand...
Click to collapse
Very interesting...

JarMagic said:
I just tried to purchase the code. Be guy says no more 2013 codes. Only 2014 production
Click to expand...
Click to collapse
Some late '13 are getting it anyway...

Should I Unlock my Bootloader?

I don't know how this'll go.......
So all my past android phones I have rooted + installed recoveries and what not. Originally I did this because I heard of a way to increase the battery life of my HTC Incredible via rooting. Afterwards I found myself rooting my Inc2, DNA, Inc4G, and my One M8. This time I did it so I can get the latest versions of Android/HTC Sense (until Google finally made a good looking UI w. 5.0).
Today (technically yesterday at this point) I bought the Pixel in hopes of finally being able to receive consistent android updates. That being said, the idea of being able to get consistent and relatively quick android updates was the whole point of me unlocking + rooting my phone.
I guess the question remains: Should I continue running unlocked with the Pixel, or will the updates from Google be enough?

dkris2020 said:
I guess the question remains: Should I continue running unlocked with the Pixel, or will the updates from Google be enough?
Click to expand...
Click to collapse
I like custom recoveries like TWRP because you can make nandroid backups. The downside of unlocking your bootloader is that Android Pay won't work and if someone gets ahold of your phone, like a thief, if the phone is unlocked then they can flash it and it will circumvent any protection on the device.
I like root because you can use apps that require root, like some Ad blockers and Titanium Backup, and because I can remove system apps I don't want on my phone.
It all depends on what you want to do with your phone.

Unless someone has a reason for unlocking the device, generally I don't see the point. There are some things that I want to do with my phone, which are easier to do unlocked, so personally I specifically wanted an unlockable phone. Depending on how much you've read about the Pixel, here are some things you may or may not know.
- Unlocking the device will wipe it, so if you decide later that you want to unlock it will wipe the phone.
- An unlocked stock device can still use the standard OTA updates.
- Some SuperSU users may be able to unroot and then use the standard OTA updates, and some rooted users have reported their phones automatically updating.
- After I started using root my phone fails to install the OTA updates, so I'd guess one of the checked areas on my phone has changed due to the root apps I've used.
- If the OTA notification shows up and the update will not install, with the stock ROM it's possible to burn through a lot of cellular data. When I didn't update my phone this month, it used about 1 GB before I shut off cellular data.
- Items like a computer, TWRP, or FlashFire are the sorts of alternate update routes for the stock ROM if a rooted phone cannot use the standard OTA.

alluringreality said:
some rooted users have reported their phones automatically updating..
Click to expand...
Click to collapse
Isn't there a way to disable the automatic updates?

LoliSmith said:
Isn't there a way to disable the automatic updates?
Click to expand...
Click to collapse
You can disable them in developer options. I've had my phone since early November (turned off system updates the day I got it) and have never been notified that an update is available. However, some have reported that they had system updates disabled in developer options and they still get notified an update is available. It seems to be hit and miss so I can't say for sure it would work for you or not.

Just addressing OPs concerns, unlocking your phone shouldn't have any impact on updates from Google. You can still get them, OTA or otherwise.
The only downside I'd say, are warranty related (unlocking the bootloader will void the warranty on Verizon models), and security. Google has pretty much decided that having an unlocked bootloader is not secure enough for Android pay, so you'll be without that (However, you can still use loaded gift cards/loyalty program cards. It's just credit/debit cards that won't work).

robocuff said:
You can disable them in developer options. I've had my phone since early November (turned off system updates the day I got it) and have never been notified that an update is available. However, some have reported that they had system updates disabled in developer options and they still get notified an update is available. It seems to be hit and miss so I can't say for sure it would work for you or not.
Click to expand...
Click to collapse
On my motorola phones, there was an app that you could freeze using titanium back up. I wonder if there is anything like that with the pixel?
---------- Post added at 12:28 PM ---------- Previous post was at 12:23 PM ----------
Soccerdude588 said:
The only downside I'd say, are warranty related (unlocking the bootloader will void the warranty on Verizon models),
Click to expand...
Click to collapse
First, that assumes that Google has a record of you unlocking your bootloader, which they may since jcase is saying that the phones have to communicate with the Google servers to unlock the bootloader.
Second, there is a federal law on this and the way it works in this situation is that if unlocking your bootloader is not related to the warranty claim, Google can't deny your claim. For instance, if the charging port fails that is entirely a hardware issue unrelated to unlocking your bootloader. Google must honor the warranty for that.
If you were to brick your device flashing, that would be different but Google would have to have some proof that you not only unlocked your bootloader but that it was the unlocked bootloader that resulted in a bricked phone.

robocuff said:
I've had my phone since early November (turned off system updates the day I got it) and have never been notified that an update is available.
Click to expand...
Click to collapse
Are you manually updating your device, or are you running months behind the current release? The reason I ask is that the OTA notices on my phone have been delayed my days or weeks from the initial release, but I think they have showed up eventually when I've stayed on a prior version and the developer option has been shut off.
LoliSmith said:
On my motorola phones, there was an app that you could freeze using titanium back up. I wonder if there is anything like that with the pixel?
Click to expand...
Click to collapse
I was hoping the following link might work similar to the Razr updater, but unfortunately the change kept my phone awake and didn't allow deep sleep both times I tried it. The update notification can be shut off by long pressing it, which I think shows up as a notification block. Due to the cellular data drain, my current plan is to try FlashFire for updates, and if that doesn't work well I'll probably try a ROM to avoid OTA updates.
https://www.androidexplained.com/pixel-hide-ota-notification/

alluringreality said:
Are you manually updating your device, or are you running months behind the current release? The reason I ask is that the OTA notices on my phone have been delayed my days or weeks from the initial release, but I think they have showed up eventually when I've stayed on a prior version and the developer option has been shut off.
Click to expand...
Click to collapse
I've been manually updating it. Usually within a week or so of the release. However, I skipped the January update all together and never got a notification about it. Maybe I got lucky. Don't know.

Thanks for the input guys.
So a lot of the stuff you guys are saying are things that I have had prior experience with so the actual process of unlocking I have no issues with. If unlocking the Pixel is anything like the Moto X Pure (which it should cause Google) it shouldn't be too much of a hassle.
That said I am with Verizon and I can say that in all of my years of owning rooted/unlocked HTC phones I only ever needed to use my warranty for hardware based claims. Like I said the main reason I unlocked/rooted was to get updated ROMs that Verizon/HTC wouldn't push out to the phone. I think I'll more than likely unlock it but I probably won't root unless I need to.

That's pretty much where I am. I did root, but a recent OTA update that I accidentally took unrooted me. Keeping the bootloader unlocked at least leaves that option available.

LG Q7+ Update Avaiable

So this morning I woke up to a security update message from T-Mobile. So if your interested they are rolling out a security update this morning. Now I'm actually with Metro Pcs but I recently flashed my device with the T-Mobile variant since it has less bloat ware and just ain't garbage as Metro's firmware. So being that Metro is part of the T-Mobile network I'm assuming you will be receiving it as well.
Now as for anyone ever hoping to require root you might want to block this update as I have just done. As you can see from the picture attached they are not giving you an option as in these updates make it harder and harder for someone to find an exploit or a (back door) as many say to aquire root. As as since it has been mentioned that these devices if and do receive the Android Pie 9.0 update it wouldn't be until late 2019 so til then I'm going to keep exploring and working on finding a way to root this device. For noobies, YES I ALREADY HAVE READ THE ANDROID TECH ARTICLES AND YOU TUBE VIDEOS. The switch in developer options will not unlock bootloader and LG does not have these devices on their list of phones even capable to be unlocked. So til then it's back to the grind.
~~~~FUN IS ILLEGAL

Paranoid "security" is purely meant to stifle open source community activity, nothing else (Maybe someone would need this if worked as CIA/MOSAD spy )

Hey, Funisillegal to turn off the automatic update just the toggle in developer options is enough right?

FullAccessForAll said:
Hey, Funisillegal to turn off the automatic update just the toggle in developer options is enough right?
Click to expand...
Click to collapse
No it's not brotha it will still force update just like clicking the unlock bootloader doesn't unlock bootloader

Funisillegal said:
No it's not brotha it will still force update just like clicking the unlock bootloader doesn't unlock bootloader
Click to expand...
Click to collapse
So how do you turn off automatic updates?

And isnt't enough simply to switch updates off from Android regular settings?
Settings->System->About Phone->Security updates (or somehow similar, watching just on my Polish menu)

Funisillegal said:
So this morning I woke up to a security update message from T-Mobile. So if your interested they are rolling out a security update this morning. Now I'm actually with Metro Pcs but I recently flashed my device with the T-Mobile variant since it has less bloat ware and just ain't garbage as Metro's firmware. So being that Metro is part of the T-Mobile network I'm assuming you will be receiving it as well.
Now as for anyone ever hoping to require root you might want to block this update as I have just done. As you can see from the picture attached they are not giving you an option as in these updates make it harder and harder for someone to find an exploit or a (back door) as many say to aquire root. As as since it has been mentioned that these devices if and do receive the Android Pie 9.0 update it wouldn't be until late 2019 so til then I'm going to keep exploring and working on finding a way to root this device. For noobies, YES I ALREADY HAVE READ THE ANDROID TECH ARTICLES AND YOU TUBE VIDEOS. The switch in developer options will not unlock bootloader and LG does not have these devices on their list of phones even capable to be unlocked. So til then it's back to the grind.
~~~~FUN IS ILLEGAL
Click to expand...
Click to collapse
Is anyone even working on a root for this device? Doesn't seem like it, I have one of these phones sealed in box never opened for the off chance someone picks up the charge and needs a stock firmware to toy around with given the phone was BOGO when I picked it up for my DIGITS line.

So far relying on ISLAND and IceBox, and it yields nice results.
Lg has equiped system with many quite useful and convenient features.
Not needed applications are just frozen.
However waiting for brealing from such utilities as KingoRoot.
So far disabled automatic updates hopefully making would-be exploits available for future versions of KingoRoot.View attachment 4747486

Anyone have an order in?

Anyone have an order in?

I'm very interested in it. I have a moto G4 as a back up phone. It is a non carrier specific and I find it very snappy without all the bloat. But the camera is pretty poor compared to my LG-V20 with GCAM app. Plus the V20 has the Quad DAC which gives quite nice sounding music with wired headphones, and it is rooted with Dolby Atmos for great sounding Bluetooth music. That being said, the Moto does have a head phone jack and I am sure there will be enhancements to help that in addition to Dolby or Viper add-ons. Miss my old note 4 which is what this would be like except with a 48MPX camera. And lots more memory, faster processor, and better, bigger screen. Plus a price that reflects the old days.

Wow, the phone is out and no one has one. Every phone I have bought in the past lots of people pre-ordered. I don't know if this is telling us something or the Wuhan virus is affecting sales. Just found this on the best buy website: "The phone isn't bad for the price, however Motorola has locked the device and doesn't allow the use of Wifi calling even if your carrier does." Deal breaker for me. On T-Mobile which I use for wifi calling. I travel a lot internationally and need wifi calling from the hotels I stay at. I guess I could use skype.

I received mine already.

androiddiego said:
Wow, the phone is out and no one has one. Every phone I have bought in the past lots of people pre-ordered. I don't know if this is telling us something or the Wuhan virus is affecting sales. Just found this on the best buy website: "The phone isn't bad for the price, however Motorola has locked the device and doesn't allow the use of Wifi calling even if your carrier does." Deal breaker for me. On T-Mobile which I use for wifi calling. I travel a lot internationally and need wifi calling from the hotels I stay at. I guess I could use skype.
Click to expand...
Click to collapse
I do not have one but have seen a similar criticism on BestBuy site about being locked and Wifi calling.. Motorola responded: The phone does support WiFi calling for carriers that choose to certify it. (For example, T-Mobile and Sprint.) It is not "locked" by Motorola.

rhuskjr said:
I do not have one but have seen a similar criticism on BestBuy site about being locked and Wifi calling.. Motorola responded: The phone does support WiFi calling for carriers that choose to certify it. (For example, T-Mobile and Sprint.) It is not "locked" by Motorola.
Click to expand...
Click to collapse
Interesting. I wonder if you have to get it at t-mobile along with all their bloatware. I'll call them and see what they say.
Called the local TMO and they know nothing.

I have it on t mobile. Got it from best buy. It works fine with wifi calling. No special setup necessary.

huge manatee said:
I have it on t mobile. Got it from best buy. It works fine with wifi calling. No special setup necessary.
Click to expand...
Click to collapse
Thanks!

I pre-ordered it from Best Buy, received it on release day, and I love it. I'm on Sprint and VoLTE and Wifi calling work fine on this phone, and it's the first phone I've owned that supports it (my previous Moto G5S Plus didn't).
Most people who buy phones these days don't come to XDA. I used to be a rooting/ROMing maniac, but I unrooted my previous phone (Moto G5S Plus) to get the stock Oreo update since all the 3rd party ROMs only half worked (at best) for me, and I didn't even re-root after that. I don't plan on rooting the Stylus at all.

I picked one up today after bricking my previous phone earlier in the morning. Curiously, wifi calling is not enabled on Google Fi as yet, even though they're now selling the phone too.

Just ordered one of these. Looking forward to see what development we can do for this. Rooting it shouldn't be too difficult right?

talkingmonkeys said:
Just ordered one of these. Looking forward to see what development we can do for this. Rooting it shouldn't be too difficult right?
Click to expand...
Click to collapse
Moto G Power is already rooted. Probably the same process for this phone.

androiddiego said:
Moto G Power is already rooted. Probably the same process for this phone.
Click to expand...
Click to collapse
I'm going to look into it and get prepared for my phone to get here over the weekend

what does the boot animation look like? guys?

talkingmonkeys said:
I'm going to look into it and get prepared for my phone to get here over the weekend
Click to expand...
Click to collapse
Hey all, I have had the Stylus for about a week now. I'm enjoying the phone overall. I previously had a G7 Power that I rooted following previous instructions. I did look at the instructions for the new G Power and it seems the method is the same. I tried it out on the Stylus and t seems to have worked. I am able to use Titanium back-up and Root Explorer to view the root of the device. The only thing that seems odd to me is that I cannot edit the build prop or change the name of any file in the root directory of the phone. Like I said, everything else seems to be working ok, just not sure what the issue is.
Perhaps someone with more knowledge will find a solution, but I just wanted to add what I've experienced so far with this phone.

CCivale said:
Hey all, I have had the Stylus for about a week now. I'm enjoying the phone overall. I previously had a G7 Power that I rooted following previous instructions. I did look at the instructions for the new G Power and it seems the method is the same. I tried it out on the Stylus and t seems to have worked. I am able to use Titanium back-up and Root Explorer to view the root of the device. The only thing that seems odd to me is that I cannot edit the build prop or change the name of any file in the root directory of the phone. Like I said, everything else seems to be working ok, just not sure what the issue is.
Perhaps someone with more knowledge will find a solution, but I just wanted to add what I've experienced so far with this phone.
Click to expand...
Click to collapse
What firmware did you use? I just got mine. Trying to make sure I have everything I need to root mine. I just want to be sure that there aren't major problems from doing it that we can't reverse. If you share exactly what you did different and some links I'll see what I can do to help.
@mingkee has been doing a lot for these new Motorola devices. Maybe he has some advice that might help us?

talkingmonkeys said:
What firmware did you use? I just got mine. Trying to make sure I have everything I need to root mine. I just want to be sure that there aren't major problems from doing it that we can't reverse. If you share exactly what you did different and some links I'll see what I can do to help.
@mingkee has been doing a lot for these new Motorola devices. Maybe he has some advice that might help us?
Click to expand...
Click to collapse
This is where I was able to grab the firmware:
https://mirrors.lolinet.com/firmware/moto/sofiap/
I just patched the boot.img from the link above with Magisk and then fastboot flashed it to my phone, same method as the Power.
I did ask over in the G Power forum and I believe he was the one that gave me some advice regarding "fastbootd". However, it didn't seem to work. Right now I'm good with the access I have. Though it may help to figure it out in the long run.

Just make sure ROM matches build number
Download ROM and get boot.img out
Transfer to the phone and let Magisk patch it
After that, send the patched_boot back to host PC
Make sure your PC has latest ADB so it can support fastbootd
Access fastbootd in bootloader by using "fastboot reboot fastboot"
Flash patched_boot in fastbootd using "fastboot flash patched_boot.img"
Please be advised using "fastboot -w" can wipe your phone

CCivale said:
This is where I was able to grab the firmware:
https://mirrors.lolinet.com/firmware/moto/sofiap/
I just patched the boot.img from the link above with Magisk and then fastboot flashed it to my phone, same method as the Power.
I did ask over in the G Power forum and I believe he was the one that gave me some advice regarding "fastbootd". However, it didn't seem to work. Right now I'm good with the access I have. Though it may help to figure it out in the long run.
Click to expand...
Click to collapse
Which build.prop did you edit? Dug through the system files looking for the apps to post and discovered another one in the product folder. Perhaps it doesn't use the one in the main folder. Some apps are hidden in there too

talkingmonkeys said:
Which build.prop did you edit? Dug through the system files looking for the apps to post and discovered another one in the product folder. Perhaps it doesn't use the one in the main folder. Some apps are hidden in there too
Click to expand...
Click to collapse
You know, I did not realize there were two. I was in the product folder because i was looking for the media folder and found it there. Then I must have been trying the build prop in the product folder. Huh.
Sent from my moto g stylus using Tapatalk

December update, OTA

Is anyone else still waiting for the December update to be available for OTA download? Google Pixel 3, unlocked, not rooted, not happy. Never waited this long before.

Is it a Verizon phone? Verizon updates are supposed to roll out this week. The update for non-Verizon phones was available last Monday.
I don't get OTA updates on my rooted phone because of root. I don't know if just being unlocked prevents OTA. You can always download the factory image and manually update. The images are at https://developers.google.com/android/images.

Thank you forI use Verizon, but it's not a Verizon phone. My updates come from Google, and always on the second or third day. This length of time is unique.

Fat fingers! 1st sentence intended to be "Thank you for the response".

BlackKeys said:
Thank you forI use Verizon, but it's not a Verizon phone. My updates come from Google, and always on the second or third day. This length of time is unique.
Click to expand...
Click to collapse
In that case, you will have to apply the update manually. The factory image is at the URL I gave previously. Edit flash-all.bat/sh to remove the -w from the last line in the file so the phone is not wiped.
You could also apply just the OTA manually. The OTA images are at https://developers.google.com/android/ota. I have not done that - I use the factory image method.

Thank you for your response. While manually installing this, or any other update is always an option, I was more concerned with why an alternative should have been needed at all. Nothing on my phone has been changed and previous monthly updates have always been available in a timely manner. I had also hoped to hear from others whether this problem was widespread.
My phone received the December update an hour ago, so my "problem" has disappeared. My concern has not. I would still like to know what changed, but cannot justify continuing this thread. Thank you for your suggestions.
I may need more help marking this thread "resolved".

BlackKeys said:
Thank you for your response. While manually installing this, or any other update is always an option, I was more concerned with why an alternative should have been needed at all. Nothing on my phone has been changed and previous monthly updates have always been available in a timely manner. I had also hoped to hear from others whether this problem was widespread.
My phone received the December update an hour ago, so my "problem" has disappeared. My concern has not. I would still like to know what changed, but cannot justify continuing this thread. Thank you for your suggestions.
I may need more help marking this thread "resolved".
Click to expand...
Click to collapse
You can search for update errors in logcat. See https://forum.xda-developers.com/t/tutorial-how-to-logcat.1726238/ on how to get a logcat. If you did the manual "Check for update" look in the log at the time you did the check. Logs are kept for quite a while, so the info should still be available.

I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this

paradox923 said:
I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this
Click to expand...
Click to collapse
I also have a google store pixel, but with a Verizon SIM. I had the same question, but finally decided on the non-verizon update. I believe the Verizon update is only for Verizon branded phones, with the added Verizon software. I have no Verizon software.
I have had no problems with the non-verizon update.

paradox923 said:
I am having a major brain block. I have a google store pixel 3 unlocked rooted. I am on Verizon, do I download the Verizon or non-verizon update. Thanks in advance, like i said, my brain is literally broken on this
Click to expand...
Click to collapse
dcarvil said:
I also have a google store pixel, but with a Verizon SIM. I had the same question, but finally decided on the non-verizon update. I believe the Verizon update is only for Verizon branded phones, with the added Verizon software. I have no Verizon software.
I have had no problems with the non-verizon update.
Click to expand...
Click to collapse
Sorry, I didn't see this sooner. You take the Verizon update if you are on Verizon. They contain different radio/network code for Verizon. It won't add bloat and it won't lock your bootloader.
This has always happened on the Pixels. A carrier will get a separate update for a month or two before the changes are merged into the same path and there is only one again. Been happening since the OG Pixel.
I doubt you will have any major problems using the other one. Maybe you won't get as strong a signal, or switch towers quite as fast as the VZ version. It will be something minor like that.

TonikJDK said:
Sorry, I didn't see this sooner. You take the Verizon update if you are on Verizon. They contain different radio/network code for Verizon. It won't add bloat and it won't lock your bootloader.
This has always happened on the Pixels. A carrier will get a separate update for a month or two before the changes are merged into the same path and there is only one again. Been happening since the OG Pixel.
I doubt you will have any major problems using the other one. Maybe you won't get as strong a signal, or switch towers quite as fast as the VZ version. It will be something minor like that.
Click to expand...
Click to collapse
Thanks for the info. I installed the January Verizon update today, and now I have a new Verizon app on my phone - com.verizon.obdm_permissions. Do you have any idea what that is for, and if it is necessary? I've disabled it for now.
I do not have the com.verizon.obdm app installed, so don't know why I'd need the permissions app.

dcarvil said:
Thanks for the info. I installed the January Verizon update today, and now I have a new Verizon app on my phone - com.verizon.obdm_permissions. Do you have any idea what that is for, and if it is necessary? I've disabled it for now.
I do not have the com.verizon.obdm app installed, so don't know why I'd need the permissions app.
Click to expand...
Click to collapse
That has always been there, very sure of that. A lot of us went done that rabbit hole with the Pixel 1 or 2. We never new for sure what it did, but I remember freezing it and had all kinds of connection problems.
Other carriers have those types of things too. They are built into the image and go live when the phone sees what carrier it is on.