Related
I stumbled across this method while I was trying to flash my Boost Moto G over to Page Plus the traditional way with DFS/CDMA Workshop. I was having some trouble with it and ran into some issues flashing CM11 and bootlooping so I ended up needing to flash back to stock firmware. I decided to give the stock Verizon G firmware a try, hoping it wouldn’t brick my brand new phone, and it works beautifully. Everything works including stock OTA programming so there’s no need to mess around too much with flashing tools (except for one or two easy steps). A big plus to this method is the 3G data settings/keys get programmed properly OTA so you don’t need a donor phone or to pay someone $$ to flash it for you. It’s a little bit of a process but if you can follow the steps properly it’s fairly easy. Note: These are just the steps I took to make this work. Some may not be necessary but follow them anyway if you aren’t 100% sure of what you’re doing.
Edit: I've tested PAC ROM and Pink Kernel after flashing the Verizon firmware and voice and 3g still work and the rom is stable so far so most custom ROMs that work with the boost moto g should be fine to flash.
Disclaimer:
I am not responsible for anything you do. If you brick your phone or it explodes, don’t blame me. This method was tested by me and worked for me but if you choose to follow this guide you do so at your own risk. If you’re not somewhat technically savvy or are very unsure about any of the steps below please have someone else help you or consider paying for a flash.
Edit (3/16): If you end up with a bootloop/brick please try to flash the stock Boost firmware again as this should bring your device back. You can get version 4.3 here and version 4.4.2 here.
Requirements:
Your Phone’s MEID Activated With Page Plus
Unlocked Bootloader (See Motorola Bootloader Unlock Site)
Minimal ADB and Fastboot
DFS Demo
Verizon Stock Firmware Image (Check your "Android version" under Settings -> About Phone)
> Android 4.3
> Android 4.4.2
> Firmware Flashing Guide (Written for version 4.3, see below for an additional step for 4.4.2 and automated scripts that are safer to use)
Motorola USB Drivers
Your Phone’s MSL/SPC Code (From Boost Activation or MSL Reader App)
Edit: For activating your MEID with Page Plus I recommend going through Kitty Wireless. They currently have a promotion going where you'll receive a free "The $12" plan with any new activation or port in and the service is free as well.
Steps:
1) Go to the Boost Mobile website and activate your phone. You can do this without actually paying for the first month. The only reason we do this is to get the MSL/SPC code for your phone that is listed on the last page of the activation process. Make sure you save this code somewhere safe. Now I did the Hands Free Activation on my phone, and I don’t think you really need to, but it can’t hurt so I’d suggest you do it as well.
Edit (3/16): Apparently it's not necessary to OTA activate with Boost before flashing your phone so you can simply install this MSL Reader on your phone to get your SPC code without activating with Boost. Copy the apk to your SD card and then open and install it with a file manager or push it from your PC with "adb install SPCUtility.apk".
2) Unlock your bootloader. Go to Motorola’s bootloader unlocking site and follow their instructions. They tell you to install the Android SDK but it can be a large download so just get the Minimal ADB and Fastboot zip as that’s all you need to complete this process. Make sure you install the Motorola USB drivers as instructed because we’ll need them later on for DFS.
3) Now we need to reset your phone’s SPC to “000000” so Verizon OTA programming will work properly. You’ll need to start your phone in Fastboot mode (power off then hold the volume down and power button together until you boot into a system menu) then select the “BP Tools” option in that menu. This will boot your phone with the diagnostic port needed for DFS enabled. If the drivers fail to install automatically you’ll need to manually install them by going into Device Manager, finding the one with the red X called “Motorola QC Diagnostic Interface”, right-clicking and selecting “Update Driver Software…”, clicking “Browse my computer for driver software” then “Let me pick…”, choose the device type “Ports (COM & LPT)” and click next, then selecting the manufacturer “Motorola” and the driver “Motorola QC Diag Port” from the list. This is the only one we actually need so if there are others with a red X you can leave them as they are. Now, open DFS. Click “Ports” on the top left. Double-click on the port named “Motorola QC Diag Port”. DFS will automatically connect to your phone. Next we need to send the MSL code we got from the Boost activation. Type it into the “SPC” box under the “Ports” button and click the arrow to the left of the box. The log window should show “DEVICE UNLOCKED”. Now go to the “Programming” tab and click “Read” in the SPC section. It’ll show the MSL code you used and you need to change it to “000000” then click “Write”. Finally, click the “Reset” button on the top right and your phone will reboot. Make sure you do this because the changes won’t stick unless you do.
4) The next step is to flash the stock Verizon firmware to your phone. There’s already an excellent guide on that process so just download the Verizon image and follow those instructions.
Edit (3/16): The flashing guide linked here references version 4.3 of the firmware. If you're installing version 4.4.2 following the guide there are additional commands you need to execute. Here are all the commands necessary for 4.4.2:
fastboot flash aboot emmc_appsboot.mbn
This needs to be stickied. Would have gone with a Boost Mobile Moto G if I'd known it was this simple. I'm stuck with a Verizon Moto G.
thanks Heranthius! Super useful info!
Makes me wonder if flashing Verizon firmware is necessary. Or if you could just upload a pageplus /Verizon PRL to your phone and reset your SPC to 000000 and then try the ota programming?
Super interesting! Wish I had the money to buy another to play with!
edit: typos. kinda hate typing on phones at times.
Sent from my XT1031 using Tapatalk
I can say for sure it won't work that way. I tried it that way before I discovered this method. You can get voice and SMS but the way Sprint programs the data settings is completely different from Verizon so you won't get 3G or MMS working properly without manual flashing and a donor phone.
this is exactly what I was going to try out, but you beat me to it I had already changed my SPC to 000000 but my Boost mobile didn't end until yesterday, I was also surprised that no one else had tried this yet either. Thanks for the guide too! Cheers.
Heranthius said:
I can say for sure it won't work that way. I tried it that way before I discovered this method. You can get voice and SMS but the way Sprint programs the data settings is completely different from Verizon so you won't get 3G or MMS working properly without manual flashing and a donor phone.
Click to expand...
Click to collapse
I see. Thanks again for the post! I got mine working the manual way but had tried so many different things. I had no idea how to write a tutorial. Seems like this could be a simple fool proof way for people!
Sent from my XT1031 using Tapatalk
Heranthius said:
I'd also recommend that you also install CWM/TWRP recovery and root your phone because the Verizon firmware has a ton of bloat pre-installed.
Click to expand...
Click to collapse
So, do you have a CM11 Moto G nightly installed to get away from the bloatware? or just the basic moto g android? also, thanks for this. I was wondering if I could get the OTA to do a few things for me. and yet i'm almost thru the manual way.
glad to see all this work and sharing on the moto g to selectel and pageplus
@cedarknoll - No problem, this was my first attempt at writing a guide too. I just wanted to make sure everyone knows there's a really easy way to do this without wasting $35 on a professional flash or spending hours manually flashing. There's definitely a lot of research to do when trying to flash by hand and I know it took me many hours to get my G set up the way I wanted. Even if you have a working manual flash I would still recommend going with the Verizon firmware because it's less of a hack, you can update your PRL and profile OTA if necessary, and most importantly for me the voicemail notifications work as intended so you don't need the Voicemail Notifier apk from Viper's thread.
Sent from my Page Plus Moto G using Tapatalk
I followed this guide to the letter. I got it to activate with talk and text, but no data. Looks like it still needs manual tweaking after the fact - which I will do this weekend.
@Flinkly - Right now I'm just running the stock Verizon rom. All I did was use Rom Toolbox to freeze all of the bloat apps. Like I said in the OP, the first time I flashed CM11 I had a bootlooping issue and I haven't had time yet to try and sort it out. I love this phone though so far and I hope some devs start coming out with Verizon roms soon. The Moto G is amazing for the price and one of the best prepaids available right now I think.
Sent from my Page Plus Moto G using Tapatalk
@micallen - That's odd. When you look in the DFS settings did it write any of the Verizon information under Data and Mobile IP? What version of Android are you on? I did the OTA update to 4.4.2 before flashing my phone. Also, did you do the Boost hands free activation before flashing the Verizon firmware? I read somewhere in another thread that you may need to do that in order to unlock/make writable the NV items for the data settings.
Sent from my Page Plus Moto G using Tapatalk
Heranthius said:
...and most importantly for me the voicemail notifications work as intended so you don't need the Voicemail Notifier apk from Viper's thread.
Click to expand...
Click to collapse
that's some super good info to know!! That apk doesn't seem to work on the moto g anyway. I think most people are using the youmail app as an alternative. Even some of the paid flashers just put you mail on there for people.
Sent from my XT1031 using Tapatalk
Nice job man!
Sent from my XT907 using Tapatalk
Heranthius said:
@micallen - That's odd. When you look in the DFS settings did it write any of the Verizon information under Data and Mobile IP? What version of Android are you on? I did the OTA update to 4.4.2 before flashing my phone. Also, did you do the Boost hands free activation before flashing the Verizon firmware? I read somewhere in another thread that you may need to do that in order to unlock/make writable the NV items for the data settings.
Sent from my Page Plus Moto G using Tapatalk
Click to expand...
Click to collapse
4.2.2
I tweaked the settings (couldn't wait) in DFS and have 3G now. 1.3 down and 1.0 up. Thanks for the guide !
Nice method, I don't have a moto g with me at the moment but I am wondering if only some of the images from verizon package need to be flashed.
Is only:
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
required? the other image seemed more related to just the android system, recovery and booting. I'l be nice if someone that had a boost motog with them could test out which ones are actually required.
@micallen - Awesome, I'm glad it worked for you. You're welcome! Could you post the settings you had to tweak so people trying this method can know what they need to change in DFS? When I flashed my phone I had to tweak the "Primary & Secondary HA Address" and "Min HA & AAA SPI set" boxes on the "Mobile IP" tab.
Sent from my Page Plus Moto G using Tapatalk
@imkey - I think you need to flash the whole system because it's the setup/activation apk of the rom that actually programs the data settings and that's why you need the one from the Verizon firmware in order to OTA program the 3G settings successfully.
Sent from my Page Plus Moto G using Tapatalk
OK I'm a noob at this and this is where I'm stuck any help would be greatly appreciated The next step is to flash the stock Verizon firmware to your phone. There’s already an excellent guide on that process so just download the Verizon image and follow those instructions.
It won't let me open up mfastboot. It just flashes and disappears
I have all the files in falcon_boost_user_4.3_14.10.0Q3.X-84-9_11_release-keys-cid9.xml folder. I just can't figure out how to load the V Firmware on this phone. I'm actually surprised I got this far LOL I have the phone in "fastboot mode" and I'm here in .cmd mode F:\MOTO G\Minimal ADB and Fastboot>
@blueyzfr6 - I'm not near my computer right now but I can try to help from memory. It sounds like you have the Boost firmware downloaded from the "boost" in that folder title. You need to check what version of android you have under settings -> about phone and download the Verizon firmware for that version. It'll either be 4.3 or 4.4.2 and the 4.4.2 one is called "Blur_Version.173.44.20.falcon_cdma.Verizon.en.US" on the download page. Once you get that and extract it there should be a .bat file inside the folder with the firmware title as the file name (I think). Open it in notepad (right click -> edit) and after the line that says "%fastboot% reboot-bootloader" add "pause" on a new line then save it. Double click the bat file to run it. If you get an error that it can't find fastboot.exe there's a sub-folder in there that has fastboot.exe and 2 .DLL files. Copy those into the folder with the .bat file and run it again. Your phone should reboot right away and the console window will say press any key to continue. Wait for the phone to get back into the fastboot menu then press enter. Now it should flash all the image files and when your phone reboots you should have the Verizon firmware and then just perform the activation steps as instructed.
Sent from my Page Plus Moto G using Tapatalk
Thank you so much for this mini-guide. I followed it all and everything seems to work until activating. I did DL the regular verizon firmware, not the Blue one. Don't know what that is for or the difference. I live out of reception, so it's a bit more challenging for me to see what works. I drove to a place with reception, tried to activate it (while showing roaming) and it failed to activate it. I did have the phone already activated on Boost so am not sure if this actually needs to happen. I did submit an ESN change and it went through, though when i checked the ESN verification, it came back "Unknown"
More to come once I try making a phone call and try the internet.
On BL unlocked Verizon Pixel.
I had taken the beta to android O but I decided to return to NHG47L (the May Verizon build) because O was laggy and terrible for my battery life. I did the standard procedure, removing -w from the flash-all.bat file. After it was finished, I left the phone to boot for 10-15 minutes before giving up. I tried rebooting a few times but it still didn't work. Finally I decided to try to return to the April build but I appear to still be having the same issue.
Any help getting my phone back up and running would be greatly appreciated.
FrostedWaffle said:
On BL unlocked Verizon Pixel.
I had taken the beta to android O but I decided to return to NHG47L (the May Verizon build) because O was laggy and terrible for my battery life. I did the standard procedure, removing -w from the flash-all.bat file. After it was finished, I left the phone to boot for 10-15 minutes before giving up. I tried rebooting a few times but it still didn't work. Finally I decided to try to return to the April build but I appear to still be having the same issue.
Any help getting my phone back up and running would be greatly appreciated.
Click to expand...
Click to collapse
I think Verizon images are for those using Verizon sim cards. I have a Verizon pixel without a Verizon sim and received the Google 7.1.2 version. Im not sure if it works like this. If it is like this you maybe need to install the Google factory image.
matiamb said:
I think Verizon images are for those using Verizon sim cards. I have a Verizon pixel without a Verizon sim and received the Google 7.1.2 version. Im not sure if it works like this. If it is like this you maybe need to install the Google factory image.
Click to expand...
Click to collapse
I have a verizon pixel. I ended up just using the android O factory image with the wipe and I'm back up and running again
If you just unsubscribe from the beta, it should prompt you for an update that will downgrade your phone back to 7.1.2
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
Hey all,
I bought a new OnePlus 8 5g T-mobile phone for my wife. She's on the RedPocket annual GMSA/ATT plan. I've stopped the auto OO11 update and I've gone into *#*#4636#*#* and selected "LTE Only" for the connection type (like I did with my old OP6) but it doesn't stick after a reboot.
My real question is:
Since 4G LTE seems to work properly with the T-Mobile stock OS, what are the reasons for converting over to the international version?
Will 4G still work after I update it to OO11.x? I don't mind it having the T-Mobile boot or bloat. I have mostly disabled/uninstalled the apps she doesn't need.
Thanks!!!
The Global version of the ROM can still get OTA updates, and gets them MUCH faster. For example always on display hit global firmware, than hit T-Mobile firmware like 7 months later. Same with Android 11, hitting T-Mobile devices a few months later than global.
T-Mobile also has bloatware that is NON-disable-able, even with adb commands. Unless your rooted, your stuck with it. And some of the package names are cleverly named so you wouldn't assume its anything bad.
You might not care about T-Mobile bloatware, but also remember it has spyware, and even if you don't really "care" about it, every time T-Mobile collects more of your data and pings it back to their servers, thats taking up recources/data on your phone, and by consequence, battery life suffers.
And T-Mobile devices collect A LOT of data, even if your not using them as your mobile provider.
Am I making it sound worse than it is? Probably. Doesn't mean everything I said isn't valid. But yes if you decide to convert to global data will work just fine.
FoxyDrew said:
The Global version of the ROM can still get OTA updates, and gets them MUCH faster. For example always on display hit global firmware, than hit T-Mobile firmware like 7 months later. Same with Android 11, hitting T-Mobile devices a few months later than global.
T-Mobile also has bloatware that is NON-disable-able, even with adb commands. Unless your rooted, your stuck with it. And some of the package names are cleverly named so you wouldn't assume its anything bad.
You might not care about T-Mobile bloatware, but also remember it has spyware. And even if you don't really "care" every time T-Mobile collects more of your data and pings it back to their servers, thats taking up recources/data on your phone, and by consequence, battery life suffers.
And T-Mobile devices collect A LOT of data, even if your not using them as your mobile provider.
Am I making it sound worse than it is? Probably. Doesn't mean everything I said isn't valid. But yes if you decide to convert to global data will work just fine.
Click to expand...
Click to collapse
@FoxyDrew Thank you for the explanation.
Just wondering about this guide: https://forum.xda-developers.com/t/...nternational-with-bootloader-re-lock.4345305/
Do you follow the 1st part, followed by the last update? Is this the best way to install the global version?
Thanks again!!
chuddler said:
@FoxyDrew Thank you for the explanation.
Just wondering about this guide: https://forum.xda-developers.com/t/...nternational-with-bootloader-re-lock.4345305/
Do you follow the 1st part, followed by the last update? Is this the best way to install the global version?
Thanks again!!
Click to expand...
Click to collapse
np man, that guide is very complicated for no reason, converting to global is rather simple, but it's a 3 step process. This all assumes you can unlock your bootloader though.
1.) MSM back to stock T-Mobile Android 10 firmware. Specifically this one. This will re-lock your BL if its unlocked.
2.) Let that boot up, go into settings to enable OEM unlocking, and then unlock the bootloader.
3.) Once the bootloader is unlocked, flash THIS global Android 10 ROM via fastboot. There's a flash-all.bat file to make it simple. Once you've finished this step your essentially done, and on global firmware, you just need to...
4.) Boot the phone up and take the OTA update in settings to Android 11. There will be 2 OTAs to take, one FULL OTA to Android 11, than an incremental one to the latest Android 11 build
Optionally afterwards you can re-lock your bootloader, or keep it unlocked and root if that's what you/she wants.
If you're not familiar with MSM tool, and the drivers it needs, check out this thread.
I would just like to say that I was a late comer to this phone and its been a long time since I've had a decent phone I could BL unlock, root, and tweak to my geek hearts content. The information on this particular forum, is so spread out and contradicting, it was a bit disheartening, but I eventually took my Verizon G7 from the original stock fw
G710VM10f to LOS20 without a single issue, and I'd like to just relay the exact steps I took, just in case some one might find it helpful.
So, starting from 100% stock Verizon fw...
***CREATED BACKUPS***and then:
1. Unlocked Bootlader - I followed the steps exactly, skipping 15-23
2. Crossflashed to g710em30f - LGUP DUAL or any LG UP with Partition DL option is acceptable.
3. Added OrangeFox | LineageOS 20 | MindTheGapps to my SD Card.
4. Rebooted into EDL
5. Used QFIL to flash ofox_metadata.img to boot_a and boot_b
6. Rebooted into OF recovery and did a full format and typed 'YES'.
7. Flashed LineageOS .zip (DO NOT REBOOT)
8. Flashed OrangeFox-R11.0_2.3-Stable-judyln.zip (Reboots to recovery automatically)
9. Flashed MindTheGapps
10. Flashed Magisk (Using OrangeFox built-in method)
11. OrangeFox Menu --> Manage Partitions --> Select Data --> Change FS --> F2FS
12. Reboot
13. PROFIT!
NOTE: I included my rooted boot img file just in case anyone needs it (30G EM FW)
I had to install the Magisk Manager upon completion of setup, but everything else went flawlessly, my service works just fine, all the other weird little issues I've seen people having were absent in my particular experience. So, follow my steps and I would imagine the same would be allowed for others. If there is any questions on specifics, I'd be happy to answer them. Also, its been a while since I've been active here, but hope all is well with everyone and glad to be back.
Good luck!
Sweet!I'm a newbie on the G7 side as well,and have the same Verizon variant!Sad fact,I have AT&T as my carrier and in the states I haven't seen not 1 CFW works with the service due to IMS b.s.!I did manage to switch to the Brightpoint ULM firmware and it works 100%.Good post though!Good to see others are still using the G7!
I'm still running my LG G7 (Verizon, Verizon as the carrier, stock, rooted, debloated, etc) on Android 9.
Nice to see this guide here, just in case I want/need to switch.
You mentioned that your service works fine, which is great to hear:
Some questions:
- Are you on Verizon as a carrier?
- do you have VoLTE working? (I'm assuming 'yes', since you said service is fine.)
I had heard that LineageOS and VoLTE (and anything else that required IMS) was a problem -- has this been fixed? Or, perhaps, was it that your phone was previously activated using the stock ROM?
thanks!
swinokur said:
I'm still running my LG G7 (Verizon, Verizon as the carrier, stock, rooted, debloated, etc) on Android 9.
Nice to see this guide here, just in case I want/need to switch.
You mentioned that your service works fine, which is great to hear:
Some questions:
- Are you on Verizon as a carrier?
- do you have VoLTE working? (I'm assuming 'yes', since you said service is fine.)
I had heard that LineageOS and VoLTE (and anything else that required IMS) was a problem -- has this been fixed? Or, perhaps, was it that your phone was previously activated using the stock ROM?
thanks!
Click to expand...
Click to collapse
I am currently on Verizon, yes, in Michigan if that helps, the service works great, if not better because I opened up a few other bands myself, but I wont be explaining all that here.
As for Volte, as far as I'm aware, Volte will never work on an Android 10+ rom, and that isn't likely to change unfortunately, but I can live without Volte if it means I can run A13 on this bad boy...lol
If you try A13 out. lemme know how it goes and if you thought it was worth it, if you wouldn't mind.
Thanks!
IJoxer said:
I am currently on Verizon, yes, in Michigan if that helps, the service works great, if not better because I opened up a few other bands myself, but I wont be explaining all that here.
As for Volte, as far as I'm aware, Volte will never work on an Android 10+ rom, and that isn't likely to change unfortunately, but I can live without Volte if it means I can run A13 on this bad boy...lol
If you try A13 out. lemme know how it goes and if you thought it was worth it, if you wouldn't mind.
Thanks!
Click to expand...
Click to collapse
I think I'll give it a try later this evening,and see how it goes.I'm thinking VoLTE won't work,but I'm already crossflashed with ULM and IMS is working.I might get lucky?
IJoxer said:
I would just like to say that I was a late comer to this phone and its been a long time since I've had a decent phone I could BL unlock, root, and tweak to my geek hearts content. The information on this particular forum, is so spread out and contradicting, it was a bit disheartening, but I eventually took my Verizon G7 from the original stock fw
G710VM10f to LOS20 without a single issue, and I'd like to just relay the exact steps I took, just in case some one might find it helpful.
So, starting from 100% stock Verizon fw...
***CREATED BACKUPS***and then:
1. Unlocked Bootlader - I followed the steps exactly, skipping 15-23
2. Crossflashed to g710em30f - LGUP DUAL or any LG UP with Partition DL option is acceptable.
3. Added OrangeFox | LineageOS 20 | MindTheGapps to my SD Card.
4. Rebooted into EDL
5. Used QFIL to flash ofox_metadata.img to boot_a and boot_b
6. Rebooted into OF recovery and did a full format and typed 'YES'.
7. Flashed LineageOS .zip (DO NOT REBOOT)
8. Flashed OrangeFox-R11.0_2.3-Stable-judyln.zip (Reboots to recovery automatically)
9. Flashed MindTheGapps
10. Flashed Magisk (Using OrangeFox built-in method)
11. OrangeFox Menu --> Manage Partitions --> Select Data --> Change FS --> F2FS
12. Reboot
13. PROFIT!
NOTE: I included my rooted boot img file just in case anyone needs it (30G EM FW)
I had to install the Magisk Manager upon completion of setup, but everything else went flawlessly, my service works just fine, all the other weird little issues I've seen people having were absent in my particular experience. So, follow my steps and I would imagine the same would be allowed for others. If there is any questions on specifics, I'd be happy to answer them. Also, its been a while since I've been active here, but hope all is well with everyone and glad to be back.
Good luck!
Click to expand...
Click to collapse
I wanted to add the link for the G710em30f firmware is dead in KDZ downloader.Here's an updated link to the firmware if you want to change it or if anyone else is looking for it?
LG G710EM | LG G7 ThinQ | Version: G710EM30f_00_OPEN_EU_OP_1124 | Firmware for Region: NEU from NEU/NORTHERN EUROPE - Lg-firmwares.com
LG G710EM Download the latest version of firmware | OS Version: Android 10 Q | Firmware version: G710EM30f_00_OPEN_EU_OP_1124 | NEU - Fan club LG-firmwares
lg-firmwares.com
Surgemanxx said:
I think I'll give it a try later this evening,and see how it goes.I'm thinking VoLTE won't work,but I'm already crossflashed with ULM and IMS is working.I might get lucky?
Click to expand...
Click to collapse
I'm sure curious to hear if IMS/VoLTE work on this Lineage rom for you!
swinokur said:
I'm sure curious to hear if IMS/VoLTE work on this Lineage rom for you!
Click to expand...
Click to collapse
It doesn't!I have have already tried it myself.Like he stated in his last post,IMS will probably never work on any custom rom.Not as of yet anyway!
Well the thing is, since Verizon turned off all the 3G service at the end of the year, and @IJoxer was saying above that his service is working fine -- sure seems like there's gotta be IMS working somehow? (It is also highly possible that I don't understand all the details about how voice can be made to work in a post 3G world...)
swinokur said:
Well the thing is, since Verizon turned off all the 3G service at the end of the year, and @IJoxer was saying above that his service is working fine -- sure seems like there's gotta be IMS working somehow? (It is also highly possible that I don't understand all the details about how voice can be made to work in a post 3G world...)
Click to expand...
Click to collapse
The Verizon variant is the easiest to cross flash!No partition erasing needed,and I'm using Brightpoint firmware on my Verizon variant and my carrier is AT&T.Everything works except wifi calling,but I didn't care about that anyway!As goes for CFW's,it's a lost cause at the moment in the states unless some magical trick surfaces.