Database Info

[FXZ][OTA] Moto E LTE Retail US Recovery Flashable Fastboot (Unlocked Bootloader)

*removed*

use it, install perfectly working on twrp.
this is my new rom daily rom , more fluid than aosp.
all working fine with my module xposed
thank you for your work

pixiebob said:
use it, install perfectly working on twrp.
this is my new rom daily rom , more fluid than aosp.
all working fine with my module xposed
thank you for your work
Click to expand...
Click to collapse
Do you have the US Retail version XT1527?
I'm interested to know whether this works on other moto e lte variants.
I updated the fxz to exclude the bootloader to prevent any potential bricks; so anyone with an unlocked bootloader can flash this and still be able to flash back to any 5.0.2 build without any issues.
Just be sure to have the fxz for your device standing by before trying.
Also renamed the other files, adding the prefix "surnia" to the title to avoid any potential confusion...

Q9Nap said:
Do you have the US Retail version XT1527?
I'm interested to know whether this works on other moto e lte variants.
Click to expand...
Click to collapse
my version is XT1524, europe retail LTE

Fastboot file now includes only logo, boot, and system.
Radio and bootloader can be installed using separate flashable zips.
It is recommended to flash radio and bootloader only on devices for which they were intended; logo, boot, and system are safe to flash on any unlocked hardware.

best rom is this stock 5.1 so far, more fluide and battery life
i like stock kernel, cpu is more able to stay at low frequencies, phone more able to stay cool.in CM/aosp it's not the case

Sadly, this phone doesn't have much development, but this is what I've been looking for, I think.
What I understand is that this works like any ROM, right? I can have a backup of my current ROM and flash this and if anything goes wrong I restore and that's it? This doesn't mess with the radio, recovery nor bootloader, so it doesn't matter that my phone is a Retla one with CID 12, as the ROM doesn't mess with that. I make several questions as I bricked my last phone by trying to flash 5.1 firmware with the bootloader unlocked, so I want to be careful. After all, if something goes really wrong, I'll always be able to flash stock firmware.

This is the best ROM I've used (XT1527) so far. I had to wipe the data and let google restore most of my apps to stop Gapps crashes, but it was worth it. I didn't install the radio, bootloader, or recovery zips and am having no problems at all. Re-rooting was easy and Xposed and its modules are working well. All the minor problems I had with AOSP are gone. This is my daily driver.

rster said:
This is the best ROM I've used (XT1527) so far. I had to wipe the data and let google restore most of my apps to stop Gapps crashes, but it was worth it. I didn't install the radio, bootloader, or recovery zips and am having no problems at all. Re-rooting was easy and Xposed and its modules are working well. All the minor problems I had with AOSP are gone. This is my daily driver.
Click to expand...
Click to collapse
What's your phone model? What do you mean, when you say you let Google restore your apps?

My phone is the Moto E 2015 LTE Retail US (XT1527). I'm using the google backup/reset in settings and it appears that it backs up non-system apps and restores them on installation if you let it. The associated passwords with the apps, however, had to be re-entered manually. What is restored is:
Google Calendar settings
Wi-Fi networks & passwords
Home screen wallpapers
Gmail settings
Apps installed through Google Play (backed up on the Play Store app)
Display settings (Brightness & Sleep)
Language & Input settings
Date & Time
Third-party app settings & data (varies by app)

Will this work for the xt1511 variant? I have it unlocked, but i'm having trouble getting a custom recovery on it to begin with, and it's not receiving and OTA to 5.1 which is annoying me.

ZeroAlphawolf said:
Will this work for the xt1511 variant? I have it unlocked, but i'm having trouble getting a custom recovery on it to begin with, and it's not receiving and OTA to 5.1 which is annoying me.
Click to expand...
Click to collapse
It's highly unlikely it will work and I wouldn't recommend trying it.
But if you're determined, make sure one of these works first so you can recover if necessary:
http://motofirmware.center/files/category/45-moto-e-2nd-generation/
Then flash only the main fastboot zip from the op which includes logo, boot, and system; do NOT flash bootloader, radio, or recovery zips.

on boost mobile version xt1526. flashed the main file but could not get data to work and the boost mobile file from the motofirmware page fails to install on twrp

Retail Fastboot from Carrier
Hi, I'd like to know if by getting this fastboot, being Retail and overriding what's currently installed (Carrier's) it would allow me to carrier unlocking it? Also; if I get this; would my updates come directly from Motorola instead of having to be approved and released by my carrier?
I do have a XT1527 that came directly from my carrier.
Thanks in advanced.

carlitosoe said:
Hi, I'd like to know if by getting this fastboot, being Retail and overriding what's currently installed (Carrier's) it would allow me to carrier unlocking it? Also; if I get this; would my updates come directly from Motorola instead of having to be approved and released by my carrier?
I do have a XT1527 that came directly from my carrier.
Thanks in advanced.
Click to expand...
Click to collapse
This fastboot requires an unlocked bootloader, and the carrier versions don't have unlockable bootloaders afaik.
Even if you are able to unlock your bootloader, flashing this fastboot will not remove carrier lock if it is present.
Ota is determined by sim, even on the retail version, afaik.

Works well on xt1524 eu.
So far the best voice quality, and the most stable firmware.

Just a heads up, I will be removing the op and the files soon.

Q9Nap said:
This fastboot requires an unlocked bootloader, and the carrier versions don't have unlockable bootloaders afaik.
Even if you are able to unlock your bootloader, flashing this fastboot will not remove carrier lock if it is present.
Ota is determined by sim, even on the retail version, afaik.
Click to expand...
Click to collapse
At&T/Cricket,verizon doesn't allow bootloader to be unlocked, which is really sad and there should be a law passed that prohibits them from doing that. Us consumers that pay good money for these phones should not have to be locked or prevented from doing what we want with them. I don't understand why it hasn't been illegal yet.
The sprint,Boost, and consumer cellular Models should have unlockable bootloaders and the Moto dev site should provide the codes

Hi. Could anyone point me at a working download link for this stock retail rom? OTA for 5.1 isn't yet available in Spain (xt1524) but i can't seem to find any copy of the ROM around XDA or anywhere else...I Know Q9Nap deleted it, but i hope someone uploaded it somewhere else.
Thanks

voland34 said:
Hi. Could anyone point me at a working download link for this stock retail rom? OTA for 5.1 isn't yet available in Spain (xt1524) but i can't seem to find any copy of the ROM around XDA or anywhere else...I Know Q9Nap deleted it, but i hope someone uploaded it somewhere else.
Thanks
Click to expand...
Click to collapse
Here is a working Link
https://mega.nz/#!c1N1AQCY!s9Gt-RDbMiDbxp3Wv7PPIRAbq5gxzd1xAah1aCMtt6w

UK Nougat update just arrived

Just checked and my Style is offering me Nougat with May security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.

m+a+r+k said:
Just checked and my Style is offering me Nougat with August security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.
Click to expand...
Click to collapse
Woohoo! I think I shall downgrade my reteu-flashed Nougat to retgb 6.0 this weekend in preparation for it then.
If you happen to have an unlocked bootloader, do you mind capturing the OTA via TWRP? The way to do it is the following, if you have downloaded the OTA but not yet installed it:
Install ADB drivers (Windows): https://adb.clockworkmod.com/
Get the ADB command line (Windows): https://forum.xda-developers.com/showthread.php?t=2317790
Download the latest twrp .img for clark: https://dl.twrp.me/clark/twrp-3.1.1-0-clark.img.html
Turn on USB debugging on your phone: https://developer.android.com/studio/run/device.html
Disconnect the phone's USB connector (e.g. to a charger) if connected.
Turn off the phone.
Start the phone into the bootloader by holding down Volume Down as you power up the phone, and then releasing it.
Connect it to a PC or Mac via USB. On Windows, wait for it to be recognized.
On the command line, verify that it is available to fastboot by running the command
Code:
fastboot devices
and verifying that it shows up.
From the ADB/Fastboot command line, run
Code:
fastboot boot \path\to\twrp-3.1.1-0-clark.img
.
Wait for TWRP to start.
Once it is started, from the ADB/Fastboot command line, issue the command
Code:
adb shell find / /data /cache -xdev -name 'Blur_Version*' -print
; you should see at least one file with that name appear.
From the ADB/Fastboot command line, issue the command
Code:
adb pull /path/to/Blur_Version_....zip \path\on\pc\Blur_Version_....zip
Issue
Code:
adb reboot recovery
which should reboot the phone into the stock recovery, assuming your ROM is stock 6.0 including the stock recovery.
Once it is started, issue
Code:
adb sideload \path\on\pc\Blur_Version_....zip
. This will attempt to flash the OTA via adb sideload.
Once you have the OTA, you could put it somewhere useful (e.g. find a way to get it to prazaar's site) for the rest of us!

Well, this gives me hope that the RETUS version may eventually be released. Thanks for the info.

US needs this terribly.

m+a+r+k said:
Just checked and my Style is offering me Nougat with May security update.
I was convinced after all this time we weren't going to get it.
Will backup tomorrow and download.
Click to expand...
Click to collapse
All good. Update was reasonably quick and no problems at all. No settings or software lost.
Very happy.
Shame it is only 7.0 and not final version 7.1.2.

i could do with the Blue and Red boot logo now

Just got August Security update.
Blimey, what's going on? Nothing for over half a year then Nougat and a security update in 2 days!!!

Well, in my bid to switch back to retgb from reteu, I have appeared to hard-brick my phone. One of the OTAs since the sole full firmware available for retgb on the firmware.center site updated the bootloader, and since this phone was previously on the reteu Nougat firmware, the SoC didn't like the bootloader being downgraded (from its point of view), and game over. I have it show up as a Qualcomm HS-USB QDLoader 9008 COM port over USB, and since no service firmware (e.g. programmer.mbn) has been leaked from Motorola for the device (let alone that firmware revision), I guess there's nothing to be done for it.
(Similar failures for certain other models, such as the Moto G4 or G4 plus or the Moto X 2013 or the Moto Z or the Moto G5 Plus or the Moto Z Play or the Moto Z2 Play, can be addressed via "blank-flash" firmware that can be used to flash over the stricken bootloader to at least get fastboot working again, but as far as I can tell, this doesn't exist or is not otherwise available for the Moto X Style, or any of the other 2015 models. I'll still take it to a repair store to see if they can work a miracle via JTAG, but I'm not holding my breath.)
I guess I'll pick up a used LG G5 (which seems to have much less drama when it comes to flashing firmware, too) and eBay this thing for parts.
Moral of the story: If you're bootloader-unlocked and already on the Nougat firmware from another region, don't try to downgrade to the last official retgb and then upgrade again using the official OTAs, or you will end up with a hard brick. (A TWRP restore is likely OK because it doesn't touch the bootloader, and is what I should have done.)

obs3rv said:
Well, in my bid to switch back to retgb from reteu, I have appeared to hard-brick my phone. One of the OTAs since the sole full firmware available for retgb on the firmware.center site updated the bootloader, and since this phone was previously on the reteu Nougat firmware, the SoC didn't like the bootloader being downgraded (from its point of view), and game over. I have it show up as a Qualcomm HS-USB QDLoader 9008 COM port over USB, and since no service firmware (e.g. programmer.mbn) has been leaked from Motorola for the device (let alone that firmware revision), I guess there's nothing to be done for it.
(Similar failures for certain other models, such as the Moto G4 or G4 plus or the Moto X 2013 or the Moto Z or the Moto G5 Plus or the Moto Z Play or the Moto Z2 Play, can be addressed via "blank-flash" firmware that can be used to flash over the stricken bootloader to at least get fastboot working again, but as far as I can tell, this doesn't exist or is not otherwise available for the Moto X Style, or any of the other 2015 models. I'll still take it to a repair store to see if they can work a miracle via JTAG, but I'm not holding my breath.)
I guess I'll pick up a used LG G5 (which seems to have much less drama when it comes to flashing firmware, too) and eBay this thing for parts.
Moral of the story: If you're bootloader-unlocked and already on the Nougat firmware from another region, don't try to downgrade to the last official retgb and then upgrade again using the official OTAs, or you will end up with a hard brick. (A TWRP restore is likely OK because it doesn't touch the bootloader, and is what I should have done.)
Click to expand...
Click to collapse
I tried to flash the latest MM firmware over latest N (August security update) on my XT 1572 (retfr) Style but I get the bootloader preflash verification stuff. It could be done on May but not on August Nougat update. Maybe it has something to do with your experience. Someone else noticed it?

Edvin73 said:
I tried to flash the latest MM firmware over latest N (August security update) on my XT 1572 (retfr) Style but I get the bootloader preflash verification stuff. It could be done on May but not on August Nougat update. Someone else noticed it?
Click to expand...
Click to collapse
Yes. In fastboot, the existing Nougat bootloader is able to protect itself so you get the preflash verification failed error. If you continue to flash the MM firmware, it does boot, and does offer OTAs. One of these OTAs (the one that goes from 24.221.4 to 24.221.5) then flashes the aboot partition from within the OTA update.zip in the stock recovery. At that point, the bootloader is inactive so cannot protect itself from being effectively downgraded. This replacement of the aboot/emmc_appboot is what hard bricked my phone. So be careful!
Probably the better thing to do would be for people with retgb or retfr firmware, and an unlocked bootloader, to upgrade to the retgb/retfr Nougat firmware with August 2017 security patch, then boot (but not flash) twrp using
Code:
fastboot boot /local/path/to/twrp-3.1.1-0-clark.img
, and then create a backup of boot and system, then post it somewhere for others of us who are on the reteu firmware to use. This way we do not meddle with the bootloader but can still receive OTAs. (I captured a TWRP backup of the reteu version in this manner before I bricked my phone by attempting to switch to retgb.)
I have also managed to capture the intermediate OTAs between RETEU-UK-FR_6.0_MPH24.49-18 and 24.221.5 by successively downloading OTAs, starting up the bootloader and using TWRP via fastboot boot to copy them out of /cache on the device via adb pull. As far as I can tell, no one's ever made them available via web before. I have these:
24.49-18 to 24.201.3 (named with 24.11.18)
24.201.3 to 24.221.4 (named with 24.201.3)
24.221.4 to 24.221.8 (named with 24.221.4 -- this hard bricked my phone on flashing the bootloader)
But please be extremely careful with these -- don't use them if you've ever had newer stock firmware versions via fastboot or OTAs via stock recovery (of any region).
@Prazaar, @dzidexx -- any interest in putting these in your archives?

Not that I care, but...
smallmj said:
Well, this gives me hope that the RETUS version may eventually be released. Thanks for the info.
Click to expand...
Click to collapse
There's still hope for the peanut gallery. I heard that Verizon's HTC One (M9) just recently got a software update for Android N. That puts Motorola neck-in-neck with HTC and only about six months behind Samsung.

So Moto Alert has gone ? **** sake I actually used that so my girlfriend knew I was on my way back from biking and could stick my tea on.

About Nokia 7+ Firmware

Well, I got a Nokia 7 Plus prototype (TA-1062), and I'm able to dump emmc from it.
Now I'm working on homebrew firmware - not sure if it can be flashed into retail unit.
I hope @blackpanther0582 could release Retail Android One firmware - even flashing it requires service point authentication.
BTW, I rooted the Nokia 7 Plus prototype easily.

hikari_calyx said:
Well, I got a Nokia 7 Plus prototype (TA-1062), and I'm able to dump emmc from it.
Now I'm working on homebrew firmware - not sure if it can be flashed into retail unit.
I hope @blackpanther0582 could release Retail Android One firmware - even flashing it requires service point authentication.
BTW, I rooted the Nokia 7 Plus prototype easily.
Click to expand...
Click to collapse
I was thinking of buying N7P instead of Xiaomi Redmi Note 5,but I read that Nokia doesn't allow users to unlock the bootloader, so no custom ROMs, no TWRP and no root. That is a big no for me personally.
How did you root your phone? Care to share some info?

_Raziel666 said:
I was thinking of buying N7P instead of Xiaomi Redmi Note 5,but I read that Nokia doesn't allow users to unlock the bootloader, so no custom ROMs, no TWRP and no root. That is a big no for me personally.
How did you root your phone? Care to share some info?
Click to expand...
Click to collapse
Prototype phones already have bootloader unlocked...
What I did are:
1. Enter Qualcomm EDL Mode with an EDL cable, then use QFIL to dump the whole emmc to get image.
2. Dump boot partition.
3. Use Magisk Manager to patch boot.img separately.
4. Flash this boot.img on either fastboot mode or EDL cable.
That's it.
I wonder if a retail phone can achieve these.
NOTE: Nokia 6 TA-1000 with locked bootloader requires an extra procedure to process boot.img in order to root the phone.

hikari_calyx said:
Prototype phones already have bootloader unlocked...
What I did are:
1. Enter Qualcomm EDL Mode with an EDL cable, then use QFIL to dump the whole emmc to get image.
2. Dump boot partition.
3. Use Magisk Manager to patch boot.img separately.
4. Flash this boot.img on either fastboot mode or EDL cable.
That's it.
I wonder if a retail phone can achieve these.
NOTE: Nokia 6 TA-1000 with locked bootloader requires an extra procedure to process boot.img in order to root the phone.
Click to expand...
Click to collapse
I didn't know that prototypes have their bootloader unlocked!
Hopefully, by the time it hits European stores, the Chinese who got it first might have figured something out. Or maybe, as it's part of Android One, it will be obligatory to allow users to unlock the bootloader.

hikari_calyx said:
Well, I got a Nokia 7 Plus prototype (TA-1062), and I'm able to dump emmc from it.
Now I'm working on homebrew firmware - not sure if it can be flashed into retail unit.
I hope @blackpanther0582 could release Retail Android One firmware - even flashing it requires service point authentication.
BTW, I rooted the Nokia 7 Plus prototype easily.
Click to expand...
Click to collapse
I have the firmare will upload it tomorrow. Is there a forum created for Nokia 7+ already ??

Thank you, if root will be avaible I'll definitely consider buying the phone.
What do you think of the phone? Quality of screen, performance, battery...

How were you about to get a prototype device? What about the retail chinese phones? I was thinking about importing them from ebay/aliexpress but im not sure if they'll be able to have their bootloader unlocked, no one has tried so far to my knowledge.

reeved said:
How were you about to get a prototype device? What about the retail chinese phones? I was thinking about importing them from ebay/aliexpress but im not sure if they'll be able to have their bootloader unlocked, no one has tried so far to my knowledge.
Click to expand...
Click to collapse
I still have no idea of if the bootloader on China Variant is unlockable.
But, if you're going to buy Nokia 7+ from China, here's some warning:
1. Only Chinese (both Simplified and Traditional) and English is available on the phone.
2. You can install Play Store manually, but you must told the seller that preserves everything on stock to prevent from tampered system.
3. If the system got damaged, you have to find someone who can provide service support to flash your phone. I don't know if you can flash Android One firmware for global release since I don't have one.

hikari_calyx said:
I still have no idea of if the bootloader on China Variant is unlockable.
But, if you're going to buy Nokia 7+ from China, here's some warning:
1. Only Chinese (both Simplified and Traditional) and English is available on the phone.
2. You can install Play Store manually, but you must told the seller that preserves everything on stock to prevent from tampered system.
3. If the system got damaged, you have to find someone who can provide service support to flash your phone. I don't know if you can flash Android One firmware for global release since I don't have one.
Click to expand...
Click to collapse
Thanks for that info, on point 2 regarding play store does that extend to Google services also? Wifey is holidaying in China and just bought one and thought to buy another for me but I'm holding her off until I can be sure as I rely on Google services a great deal. Also why must the seller be informed, is that a warranty issue or software update issue?
And on point 3, presuming she brings the phone back to New Zealand is there a way I can help the community to explore flashing Android One global release firmware?

maomaoliu-bright said:
Thanks for that info, on point 2 regarding play store does that extend to Google services also? Wifey is holidaying in China and just bought one and thought to buy another for me but I'm holding her off until I can be sure as I rely on Google services a great deal. Also why must the seller be informed, is that a warranty issue or software update issue?
And on point 3, presuming she brings the phone back to New Zealand is there a way I can help the community to explore flashing Android One global release firmware?
Click to expand...
Click to collapse
If you can buy it from China directly, informing seller is not necessary. For example, if you can buy it from Jing Dong or Suning, you needn't to worry about tampered OS, and that means you can receive further updates.
If you buy it from eBay or AliExpress, the system is probably tampered by seller which you can't get further updates.
As for install Play Store, it's really easy - just find Play Store APK from APKPure, APKMirror whatever and install it on the phone, this will allow you to get access to Play Store. Then you can install any other Google Apps on Play Store manually. You needn't to root your phone and install opengapps.
Since Android One firmware hasn't released yet and the bootloader isn't unlockable, you can't flash it right now.

Nokia 7 plus is available on Amazon europe sites like Germany and Italy and others and also ships worldwide and release date showing 12 to 14 or 15 april

hikari_calyx said:
Well, I got a Nokia 7 Plus prototype (TA-1062), and I'm able to dump emmc from it.
Now I'm working on homebrew firmware - not sure if it can be flashed into retail unit.
I hope @blackpanther0582 could release Retail Android One firmware - even flashing it requires service point authentication.
BTW, I rooted the Nokia 7 Plus prototype easily.
Click to expand...
Click to collapse
pls pls pls
Post system image of oreo 8.1
thank you!

Big question here! I am going to europe and want to buy this phone there, the problem is that the model they are selling don't have band 4 (1700/2100) and i need it in my country. Is there a way to fix this? Is a model in europe with band 4? Can i flash the modem with band 4? Thanks a lot!

As the phone should be available, are there any news about the firmware of Europe phones? Is the bootloader unlocked / unlockable?

flo.ei said:
As the phone should be available, are there any news about the firmware of Europe phones? Is the bootloader unlocked / unlockable?
Click to expand...
Click to collapse
According to this post, the official bootloader unlocking from HMD themselves is imminent.

I heard the Chinese Firmware supports navbar gestures where you can disable navbar and use gestures and this isnt available in Global version
That SUCKS! its such a good feature NOKIA give it to all!

varun.gid said:
I heard the Chinese Firmware supports navbar gestures where you can disable navbar and use gestures and this isnt available in Global version
That SUCKS! its such a good feature NOKIA give it to all!
Click to expand...
Click to collapse
Try searching in settings for 'nav'. It will reveal the Navigation key of fingerprint setting.
TA-1046, Android 8.0

hikari_calyx said:
Well, I got a Nokia 7 Plus prototype (TA-1062), and I'm able to dump emmc from it.
Now I'm working on homebrew firmware - not sure if it can be flashed into retail unit.
I hope @blackpanther0582 could release Retail Android One firmware - even flashing it requires service point authentication.
BTW, I rooted the Nokia 7 Plus prototype easily.
Click to expand...
Click to collapse
How you dumped emmc of nokia 7 plus oreo 8.1.0 ?

Does anyone have the build.prop from the Nokia 7 Plus they can post?

hikari_calyx said:
Prototype phones already have bootloader unlocked...
What I did are:
1. Enter Qualcomm EDL Mode with an EDL cable, then use QFIL to dump the whole emmc to get image.
2. Dump boot partition.
3. Use Magisk Manager to patch boot.img separately.
4. Flash this boot.img on either fastboot mode or EDL cable.
That's it.
I wonder if a retail phone can achieve these.
NOTE: Nokia 6 TA-1000 with locked bootloader requires an extra procedure to process boot.img in order to root the phone.
Click to expand...
Click to collapse
Bro can we dump emmc of ta-1046 by using same method
Having unlocked bootloader???

Google Pixel 3 noobie queries

Hi!
I come from the Galaxy S series (S4, S5, S7) phones and I m considering of buying a Google Pixel 3
I can find many decent options, all of which are carrier unlocked
My concern with the Pixel 3 is whether I ll be able to install Android vanilla (without any carrier-related bloatware)
For all of my Samsung's so far, I could easily pick the retail ROM (well not exactly 'vanilla'!) from sammobile and load it with Odin (without breaking the knox)
Can I do something similar in the Pixel 3 or are there any security mechanisms to prevent me? (I m talking about installing original ROM - not custom..)
Bonus question - does any of you know if the Pixel 3 from Verizon and US Cellular have branding [carrier logo(s)] on the device?
Thank you in advance!

Well, you will certainly avoid the Samsung bloatwear. I have a P3 from Google and got my son's P3 through T-mobile. It did not have any additional T-mobile bloat on it, but I don't know about the big V.

Note10.1Dude said:
Well, you will certainly avoid the Samsung bloatwear. I have a P3 from Google and got my son's P3 through T-mobile. It did not have any additional T-mobile bloat on it, but I don't know about the big V.
Click to expand...
Click to collapse
I can find it via Verizon and US Cellular - hopefully none of which have put logos on it..
I have one more - rather embarassing question: do you have to use a Google account in order to use the Pixel 3? For several other Android phones that I know of - it's optional. You can still skip this step and use the phone without having to tie the phone with Google. But can you do that on the P3?
Any more hints on that and my ROM-related queries would be really helpful! Thanks

jstoner said:
I can find it via Verizon and US Cellular - hopefully none of which have put logos on it..
I have one more - rather embarassing question: do you have to use a Google account in order to use the Pixel 3? For several other Android phones that I know of - it's optional. You can still skip this step and use the phone without having to tie the phone with Google. But can you do that on the P3?
Any more hints on that and my ROM-related queries would be really helpful! Thanks
Click to expand...
Click to collapse
Verizon branded Pixel 3s have locked bootloaders, which prevent rooting or custom ROMs (vanilla AOSP would be a custom ROM). According to the flashing instructions at https://developers.google.com/android/images, you also need to unlock the bootloader to flash a google factory image.
I'm not sure if you can skip the google account. If you really want to avoid google services, my recommendation would be to install LineageOS, with no gapps.

dcarvil said:
Verizon branded Pixel 3s have locked bootloaders, which prevent rooting or custom ROMs (vanilla AOSP would be a custom ROM). According to the flashing instructions at https://developers.google.com/android/images, you also need to unlock the bootloader to flash a google factory image.
I'm not sure if you can skip the google account. If you really want to avoid google services, my recommendation would be to install LineageOS, with no gapps.
Click to expand...
Click to collapse
Hmm...if the 3s has that, then the 3 will also have it :/
But I m confused...would I be able to unlock the bootloader?
I can see from this page: https://developers.google.com/android/images#blueline that 'blueline' is that vanilla AOSP version that corresponds to the P3 (right?)
The G account issue is less important. I just don't like 'syncing' stuff (accounts, photos etc). Worse case scenario, I ll create an empty profile, just for the logon

jstoner said:
Hmm...if the 3s has that, then the 3 will also have it :/
But I m confused...would I be able to unlock the bootloader?
I can see from this page: https://developers.google.com/android/images#blueline that 'blueline' is that vanilla AOSP version that corresponds to the P3 (right?)
The G account issue is less important. I just don't like 'syncing' stuff (accounts, photos etc). Worse case scenario, I ll create an empty profile, just for the logon
Click to expand...
Click to collapse
3s is not a model, it is the plural of 3. A Verizon Pixel 3 usually cannot be boot loader unlocked, but if you search this forum, you will find a few special cases where it has been done. One such case is at https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
Vanilla AOSP generall refers to a ROM without any google services. See https://android.stackexchange.com/questions/53171/what-exactly-is-in-aosp for more info. Blueline is the Pixel 3 factory image, which has all the google services. It does not have any added carrier bloatware, but I wouldn't call it a vanilla AOSP.
You can turn off all the syncing stuff, and you may be able to skip the google account part. I just can't definitely say you can skip the google account because I have not tried it.
Another consideration with a locked bootloader is the end support date. Google support for the Pixel 3 ends in October, 4 months from now. There will be no security updates from Google after October. If you have an unlocked bootloader, you can switch to LineageOS and continue to receive security updates. That is what I plan to do.

dcarvil said:
3s is not a model, it is the plural of 3. A Verizon Pixel 3 usually cannot be boot loader unlocked, but if you search this forum, you will find a few special cases where it has been done. One such case is at https://forum.xda-developers.com/t/...branded-pixel-3-how-is-this-possible.4267273/
Vanilla AOSP generall refers to a ROM without any google services. See https://android.stackexchange.com/questions/53171/what-exactly-is-in-aosp for more info. Blueline is the Pixel 3 factory image, which has all the google services. It does not have any added carrier bloatware, but I wouldn't call it a vanilla AOSP.
You can turn off all the syncing stuff, and you may be able to skip the google account part. I just can't definitely say you can skip the google account because I have not tried it.
Another consideration with a locked bootloader is the end support date. Google support for the Pixel 3 ends in October, 4 months from now. There will be no security updates from Google after October. If you have an unlocked bootloader, you can switch to LineageOS and continue to receive security updates. That is what I plan to do.
Click to expand...
Click to collapse
Clear!
I ll check on the resources you ve listed here
If the V-branded P3 is troublesome as it sounds, perhaps I should just go for the US Cellular carrier option. Bootloader may also be locked (but we know for sure that the V is..)
Interestingly, the US Cellular P3 is unlocked to all GSM carriers except Verizon, Boost, Virgin Mobile and Sprint
Is the carrier lock specified in the bootloader?
Btw, thanks for all the help!

jstoner said:
Clear!
I ll check on the resources you ve listed here
If the V-branded P3 is troublesome as it sounds, perhaps I should just go for the US Cellular carrier option. Bootloader may also be locked (but we know for sure that the V is..)
Interestingly, the US Cellular P3 is unlocked to all GSM carriers except Verizon, Boost, Virgin Mobile and Sprint
Is the carrier lock specified in the bootloader?
Btw, thanks for all the help!
Click to expand...
Click to collapse
SIM (carrier) unlock and bootloader unlock are separate, and not related. I have no idea if US Cellular is bootloader unlocked. Google sold a global model, which is the bootloader unlocked version, and the one I have. The IMEI/MEID number of the global variant begins with 990012 (don't know how many digits are significant). If I was buying it, I'd ask the seller to confirm it was bootloader unlocked.
Glad I could help.

dcarvil said:
SIM (carrier) unlock and bootloader unlock are separate, and not related. I have no idea if US Cellular is bootloader unlocked. Google sold a global model, which is the bootloader unlocked version, and the one I have. The IMEI/MEID number of the global variant begins with 990012 (don't know how many digits are significant). If I was buying it, I'd ask the seller to confirm it was bootloader unlocked.
Glad I could help.
Click to expand...
Click to collapse
The two P3 options I m considering (Verizon + US Cellular), both are sealed in their original box. According to that post, if the P3 hasn't ever being turned on, which is probably then when bootloader becomes locked
So I wonder if there is a SIM that comes with the phone already and that I have to remove that prior booting the phone. Not sure what he means with "VZW SIM". Is it a different type of SIM e.g. an eSIM??
I know for fact that these phones are CDMA-locked and only GSM is unlocked (but that's what I need anyways)
Does anyone here have any experience from an US Cellular P3 - is the bootloader locked? (the retailer of the phone doesn't seem to know much on such details..)

jstoner said:
The two P3 options I m considering (Verizon + US Cellular), both are sealed in their original box. According to that post, if the P3 hasn't ever being turned on, which is probably then when bootloader becomes locked
So I wonder if there is a SIM that comes with the phone already and that I have to remove that prior booting the phone. Not sure what he means with "VZW SIM". Is it a different type of SIM e.g. an eSIM??
I know for fact that these phones are CDMA-locked and only GSM is unlocked (but that's what I need anyways)
Does anyone here have any experience from an US Cellular P3 - is the bootloader locked? (the retailer of the phone doesn't seem to know much on such details..)
Click to expand...
Click to collapse
VZW SIM is just a Verizon SIM. It is probably the standard SIM card, not an eSIM. I would remove the SIM prior to booting, just to be safe. According to one of those posts, WiFi had to be connected before they could unlock the bootloader.

dcarvil said:
VZW SIM is just a Verizon SIM. It is probably the standard SIM card, not an eSIM. I would remove the SIM prior to booting, just to be safe. According to one of those posts, WiFi had to be connected before they could unlock the bootloader.
Click to expand...
Click to collapse
I ll find out soon, I ve ordered the P3 (US cellular stock)
Seller claims that it is sealed in original box. If that's really the case, then the carrier can't have put a SIM into it, right? But what about an eSIM? If they have the eSIM pre-programmed, then I can't possibly avoid booting the phone with it..

jstoner said:
I ll find out soon, I ve ordered the P3 (US cellular stock)
Seller claims that it is sealed in original box. If that's really the case, then the carrier can't have put a SIM into it, right? But what about an eSIM? If they have the eSIM pre-programmed, then I can't possibly avoid booting the phone with it..
Click to expand...
Click to collapse
Hmmm I think the way it works is that when the phone is produced, for a specific carrier, and the carrier wants it to have a sim, it's put in at the factory. So, I think, sealed with a sim in it, possible.
I don't think us cellular uses e-sims. Double check that but it doesn't look like one of the carriers that's capable of e-sims.
cheers, good luck. I have a vzw coming today, hoping it's new and can unlock as others have... we'll know soon.

Good news! Just got the phone and ... I ve managed to unlock the bootloader!
Exactly same case as described here. No SIM inserted, connected to WIFI, and in Dev Options, turned OEM unlocking to ON!
Then, on the instructions (link by opensense), I ve used adb and the bootloader is now unlocked! I m really chuffed about it
(btw the US Cellular supplied SIM was attached on the box (outside) with a sticker. Box was sealed.
Now, all is left is for me to pick that 'cleaner' Android option I always wanted!
But which one should it be? It's currently running blueline MP1.0(ROW)
Is there any clearer (official) Android ROM that I should switch to instead?
From G services, I would like to keep the Playstore and Maps...

jstoner said:
Good news! Just got the phone and ... I ve managed to unlock the bootloader!
Exactly same case as described here. No SIM inserted, connected to WIFI, and in Dev Options, turned OEM unlocking to ON!
Then, on the instructions (link by opensense), I ve used adb and the bootloader is now unlocked! I m really chuffed about it
(btw the US Cellular supplied SIM was attached on the box (outside) with a sticker. Box was sealed.
Now, all is left is for me to pick that 'cleaner' Android option I always wanted!
But which one should it be? It's currently running blueline MP1.0(ROW)
Is there any clearer (official) Android ROM that I should switch to instead?
From G services, I would like to keep the Playstore and Maps...
Click to expand...
Click to collapse
Congratulations. You'll have to define what you mean by the term "cleaner (official)" ROM. Blueline is the only official Google ROM for the Pixel 3. Anything else will be a custom ROM. I have no experience with any of the Pixel custom ROMs, so can't offer any advice on those.
You can disable most of the unwanted Google services in the blueline ROM. I'd recommend keeping the backup service, though.
Blueline MP1.0(ROW) is not a version listed at https://developers.google.com/android/images#blueline Go to Settings, About Phone, and tap Android Version. Check the "Android security update" date. Latest is June 5, 2021. I suspect yours is quite old.
If you want to update to the current blueline version, you have 2 options, OTA or flash a new factory image.
For OTA, go to Settings, System, System update, and follow instructions.
To flash a new factory image, follow the instructions at the link above. To prevent wiping your data when flashing, edit the flash-all.bat or flash-all.sh file, and remove the "-w" from the last line.
I you intend to change ROM's, I wouldn't bother updating.
Good luck.

dcarvil said:
Congratulations. You'll have to define what you mean by the term "cleaner (official)" ROM. Blueline is the only official Google ROM for the Pixel 3. Anything else will be a custom ROM. I have no experience with any of the Pixel custom ROMs, so can't offer any advice on those.
You can disable most of the unwanted Google services in the blueline ROM. I'd recommend keeping the backup service, though.
Blueline MP1.0(ROW) is not a version listed at https://developers.google.com/android/images#blueline Go to Settings, About Phone, and tap Android Version. Check the "Android security update" date. Latest is June 5, 2021. I suspect yours is quite old.
If you want to update to the current blueline version, you have 2 options, OTA or flash a new factory image.
For OTA, go to Settings, System, System update, and follow instructions.
To flash a new factory image, follow the instructions at the link above. To prevent wiping your data when flashing, edit the flash-all.bat or flash-all.sh file, and remove the "-w" from the last line.
I you intend to change ROM's, I wouldn't bother updating.
Good luck.
Click to expand...
Click to collapse
I think I ll probably stick with the official one then. My current is PQ1A.181105.017.A1 (which is very old as you guessed)
Which means I can jump to Android 10 or 11. From my experience, latest isn't always the best so I might have to keep reading, see if I should jump to a latest build of 10 instead. My emphasis is on stability/security - not new features...
And I want to ensure that the camera is at its best

jstoner said:
I think I ll probably stick with the official one then. My current is PQ1A.181105.017.A1 (which is very old as you guessed)
Which means I can jump to Android 10 or 11. From my experience, latest isn't always the best so I might have to keep reading, see if I should jump to a latest build of 10 instead. My emphasis is on stability/security - not new features...
And I want to ensure that the camera is at its best
Click to expand...
Click to collapse
If security is a concern, you'll want to go to Android 11. 10 has not been updated since August 2020, when Android 11 came out. Also, I believe there have been camera improvements since August 2020, which would not be in the latest Android 10 build.
I have not seen any reports of stability problems with the June 2021 Android 11 update, which has the latest security patches.
I don't know if you can do an OTA update to Android 11 from Android 9. You might have to go from 9 to 10 to 11. You can flash the Android 11 image without going to 10 first.

I intend to do via flashing (whichever version I decide in the end). Not a fan of OTA

Very strange boot animation in android 11 update

It seems they are sending android 11 to everyone but they changed the boot animation. Now when you boot you see a logo that says edge and then TIM italy. This did not happen in android 10. My moto g 5g is free retail with no brand on the box. I think there is a bug in this update. Is it possible to return to android 10? Also this update changed the intensity of the bars on the screen, now it is more generous but if you see the numeric values of Dbm or ASU these are much lower. I regretted updating so fast and I would like to go back to android 10 until 11 is fixed.

Lol, 11 will never be "fixed".
If the bootloader was updated you're boned.
Apparently on the OTA updates on at least some devices it's not being updated, you can rollback.
The 5th digit from the end of the boot loader version and the firmware are the significant digits. If the boot loader version is the same or less than the firmware, you can rollback. In this case it's a 2.

Not sure that this Samsung rule applies to Motorola updates.

RETIEF said:
Not sure that this Samsung rule applies to Motorola updates.
Click to expand...
Click to collapse
No idea, it may be a Samsung idiosyncrasy.
A very annoying one...

PredatorGreen said:
It seems they are sending android 11 to everyone but they changed the boot animation. Now when you boot you see a logo that says edge and then TIM italy. This did not happen in android 10. My moto g 5g is free retail with no brand on the box. I think there is a bug in this update. Is it possible to return to android 10? Also this update changed the intensity of the bars on the screen, now it is more generous but if you see the numeric values of Dbm or ASU these are much lower. I regretted updating so fast and I would like to go back to android 10 until 11 is fixed.
Click to expand...
Click to collapse
Check the software channel from Settings>Telephone information (or similar), which software channel do you have? If it is timit you are on the tim software channel (and the updates depends on the carrier, but actually seems in line with reteu, the european standar), if you are on reteu this is really strange. I don't know why they miss the boot animation but the firmware is right.

Yes the software channel is timit, but in android 10 it showed the boot animation for reteu channel. And i dont know why now it shows an edge logo animation that has nothing to do with this model. It looks like they put something from another model in the update. Look at the attached photo.

I'm using the euro android 11 XT2113-3_KIEV_RETEU_11_RZK31.Q3-25-15 on a XT2113-2 and everything seems happy as a clam, *except* it would not flash the radio.img. As far as being "boned" if you went to 11 but wished to downgrade.... Has anyone bothered to try a patched vbmeta? I could go up or down on my one action using this route. I think I may just try for the hell of it.
EDIT: downloading 10 now. If it works I'll post my patched vbmeta.
EDIT: Now keep in mind I am doing this from a flash of android 11 xt2113-3 on a xt2113-2 handset... The flash fails on the radio, then next the DSP. It does however downgrade the bootloader no problem. I went ahead and prepatched the boot.img prior to flashing, and it just finished sooooo survey says.......? It worked. Now back in Android 10 XT2113_KIEV_RETUS_10_QZKS30.Q4-40-95-2. Running through the setup now to make sure it dials out etc.
EDIT: Phone dials out, bluetooth and wireless works. Havent seen 5G yet but 4G/LTE is working for sure. So yes, you most assuredly downgrade from 11 if one so chooses. Attached is the vbmeta I used.

PredatorGreen said:
It seems they are sending android 11 to everyone but they changed the boot animation. Now when you boot you see a logo that says edge and then TIM italy. This did not happen in android 10. My moto g 5g is free retail with no brand on the box. I think there is a bug in this update. Is it possible to return to android 10? Also this update changed the intensity of the bars on the screen, now it is more generous but if you see the numeric values of Dbm or ASU these are much lower. I regretted updating so fast and I would like to go back to android 10 until 11 is fixed.
Click to expand...
Click to collapse
You can always just root phone and change the boot animation files. They're in system/media/bootanimation.zip
Just download android 10 firmware get this file from system.img and put it on your phone

the.real.p3y0t3 said:
I'm using the euro android 11 XT2113-3_KIEV_RETEU_11_RZK31.Q3-25-15 on a XT2113-2 and everything seems happy as a clam, *except* it would not flash the radio.img. As far as being "boned" if you went to 11 but wished to downgrade.... Has anyone bothered to try a patched vbmeta? I could go up or down on my one action using this route. I think I may just try for the hell of it.
EDIT: downloading 10 now. If it works I'll post my patched vbmeta.
EDIT: Now keep in mind I am doing this from a flash of android 11 xt2113-3 on a xt2113-2 handset... The flash fails on the radio, then next the DSP. It does however downgrade the bootloader no problem. I went ahead and prepatched the boot.img prior to flashing, and it just finished sooooo survey says.......? It worked. Now back in Android 10 XT2113_KIEV_RETUS_10_QZKS30.Q4-40-95-2. Running through the setup now to make sure it dials out etc.
EDIT: Phone dials out, bluetooth and wireless works. Havent seen 5G yet but 4G/LTE is working for sure. So yes, you most assuredly downgrade from 11 if one so chooses. Attached is the vbmeta I used.
Click to expand...
Click to collapse
Hello and sorry for asking a newbie question here but I don't want this to go sideways...
I have a new XT2113-2 (TM) that is yet to be boot loader unlocked/rooted/etc. I don't want to do that until I am sure. I got this variant of the phone so I could unlock the bootloader, root, TWRP, etc and was afraid the "global" variant -3 might not work with USA 5G. The phone came with Android 11 installed (and has since auto-installed at least one security update). It shows the build as RZKS31.Q3-45-16-3-11 and the baseband ends with Kiev_TMO_CUST. I am using it on ATT (via Red Pocket) since TM service just sucks where I live. And I do get the 5G icon on it now.
But ideally, I want to get this to the original TM Android 10, which I think is shown here as the file XT2113-2_KIEV_TMO_10_QZKS30.Q4-40-95-6_subsidy-TMO_SPR_RSU_QCOM_regulatory-DEFAULT_CFC.xml.zip as I hope it will undo some of the "security" crap Google has added to Android with each successive release.
So I need to be sure of the following:
1. Can I downgrade from 11 to 10?
2. Is there some reason to NOT use the firmware mentioned above? Should I use retail US (RETUS) instead? I am not sure the differences (it would be great if that would permit me to use this phone on Red Pocket Verizon but the IMEI now shows as incompatible on Verizon).
3. Must I unlock the boot loader to downgrade? I know I must to do other stuff and I have the unlock code on hand and ready to put it if needed. If I must unlock the boot loader to downgrade, will I have to re-unlock it afterwards? And, if so, will I have to go through the same process of getting a code or will the code I have now work?
4. How do I flash to do the downgrade? I have the Lenovo Rescue/Smart Assistant installed on my PC and was able to download the stock firmware (I assume it matches what is on there now) and stashed it aside. But is there some other tool needed?
5. Once I achieve downgrade, what is the best way to avoid having the thing auto-update to Android 11?
Thanks for your help with these questions.