Hello, i am currently on pure nexus with the April update on tmobile (pixel xl). I have a few questions I'm hoping someone could answer before diving in. Which factory image do i use, 7.1.2 May N2G47T? I would like to be able to take ota updates after I'm done, i take it that this would now be possible then? Also, do i need to relock my bootloader to take ota updates. Thanks
Sent from my Pixel XL using Tapatalk
jreink01 said:
Hello, i am currently on pure nexus with the April update on tmobile (pixel xl). I have a few questions I'm hoping someone could answer before diving in. Which factory image do i use, 7.1.2 May N2G47T? I would like to be able to take ota updates after I'm done, i take it that this would now be possible then? Also, do i need to relock my bootloader to take ota updates. Thanks
Click to expand...
Click to collapse
No, that is the image for Deutsce Telekom. You want N2G47K. They are labeled on the full image page.
You do not need to relock to get ota's
TonikJDK said:
No, that is the image for Deutsce Telekom. You want N2G47K. They are labeled on the full image page.
You do not need to relock to get ota's
Click to expand...
Click to collapse
Ok, but that is April's image, is there a May image i can use?
Sent from my Pixel XL using Tapatalk
Hey there buddy,
Google's website for Factory and OTA includes images/releases from certain carriers. I live in Canada for example so version 7.1.0(I think?) has a release for my specific carrier, so whenever I factory reset, I use that one then relock my bootloader directly after. This leads me to receiving proper OTA everytime.
Other than finding your own carrier image, your best bet is using the standard build flash.
Always be careful with flashing and tinkering and best of luck! =]
jreink01 said:
Ok, but that is April's image, is there a May image i can use?
Click to expand...
Click to collapse
Sorry, dunno what I was typing there.
N2G47O
TonikJDK said:
Sorry, dunno what I was typing there.
N2G47O
Click to expand...
Click to collapse
Just to confirm, the update you mentioned, n2g47o will work with tmobile?
Sent from my Pixel XL using Tapatalk
jreink01 said:
Just to confirm, the update you mentioned, n2g47o will work with tmobile?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Yes. There are three. Verizon, Dutch Telecom and everyone else. Tmobile is in the everyone else category so you are good with that one.
TonikJDK said:
Yes. There are three. Verizon, Dutch Telecom and everyone else. Tmobile is in the everyone else category so you are good with that one.
Click to expand...
Click to collapse
I myself am with Tmobile as well and still on N2G47E, April's Build.
I didn't upgrade to May's build because I read there was an issue with TWRPRC1/RC2 or SU with the bootloader on May
I was wondering if this issue has been solved? Is there another zip I need to flash as well?
So far I have been sticking with Stock Rom, but I root with SU and use elemental X kernal with TWRP. thanks!
Related
Good morning,
I have an XT1028 running on Verizon Prepaid; I've had it on continuous service for over a year now through VZW. Prior to updating it past 4.4.2, I unlocked my bootloader via SunShine and recently updated to the CDMA build of CM12.1 by Meticulus.
I'd love the option to take advantage of some Lollipop-based kernels like Attacked, but they appear to require the Lollipop bootloader to function correctly. Is it possible for me to update my bootloader and retain my unlock for an XT1028? Or, alternatively, given that my phone has been on VZW for a year, if my phone were re-locked by a bootloader update, has anyone had any luck or experience receiving a bootloader unlock directly through Verizon? I've heard anecdotes of Verizon's policy of unlocking after six months or one year, but never actually found anything where XT1028 users have successfully done this.
Thanks!
From what I've heard and experienced, upgrading bootloader will not relock it in the process - held true for my own RAZR M. The problem is whether you have the 5.0 bootloader files / OTA at hand...
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
From what I've heard and experienced, upgrading bootloader will not relock it in the process - held true for my own RAZR M. The problem is whether you have the 5.0 bootloader files / OTA at hand...
Click to expand...
Click to collapse
Thanks for the quick reply. As far as I am aware, there is a flashable zip to update a CDMA bootloader to lollipop 41.19, although it is designed for Boost so it requires reflashing the radio to get it to work for Verizon. I may give it a shot after a bit more research, as the only thing left before I'm fully satisfied with 5.1 is potentially a more battery-efficient kernel.
a_gert said:
Thanks for the quick reply. As far as I am aware, there is a flashable zip to update a CDMA bootloader to lollipop 41.19, although it is designed for Boost so it requires reflashing the radio to get it to work for Verizon. I may give it a shot after a bit more research, as the only thing left before I'm fully satisfied with 5.1 is potentially a more battery-efficient kernel.
Click to expand...
Click to collapse
I have the flashable zip and have the 5.0 BL on my own Boost G. It's hard to say whether the Boost one is compatible with Verizon's, because the BL upgrade process touches 5 partitions, and there is a possibility that one of them may be different between the 2 variants.
You should give it a shot. I have no desktop or I would
a_gert said:
Thanks for the quick reply. As far as I am aware, there is a flashable zip to update a CDMA bootloader to lollipop 41.19, although it is designed for Boost so it requires reflashing the radio to get it to work for Verizon. I may give it a shot after a bit more research, as the only thing left before I'm fully satisfied with 5.1 is potentially a more battery-efficient kernel.
Click to expand...
Click to collapse
I've heard of people using the Brazil ota on the Asia retail. I'm really curious whether or not the boost its will work on Verizon. I don't care about the radio, I use it for WiFi. I hear they are the same exact phones tho. Let us know if you the
sweetmyke said:
I've heard of people using the Brazil ota on the Asia retail. I'm really curious whether or not the boost its will work on Verizon. I don't care about the radio, I use it for WiFi. I hear they are the same exact phones tho. Let us know if you the
Click to expand...
Click to collapse
I went ahead and upgraded my bootloader to 41.19 using an updated flashable zip from SuperR here: http://androidforums.com/threads/cdma-get-ready-for-otas.897474/page-21
It is derived from a Boost update and changes the partitions without overwriting the existing radio, so I got the LP bootloader and retained my 4.4.4 VZW radio. Worked perfectly for me!
Thanks for the response but...
a_gert said:
I went ahead and upgraded my bootloader to 41.19 using an updated flashable zip from SuperR here: http://androidforums.com/threads/cdma-get-ready-for-otas.897474/page-21
It is derived from a Boost update and changes the partitions without overwriting the existing radio, so I got the LP bootloader and retained my 4.4.4 VZW radio. Worked perfectly for me!
Click to expand...
Click to collapse
My bootloader can't be unlocked and I wanted to use the boost ota with stock recovery on Verizon 4.4.4 and only care if wifi works., and like I said Asia retail flashed Brazil's ota. What do you think. I have the link to the boost its soak of you wanna try for me since you can always flash back....please
sweetmyke said:
My bootloader can't be unlocked and I wanted to use the boost ota with stock recovery on Verizon 4.4.4 and only care if wifi works., and like I said Asia retail flashed Brazil's ota. What do you think. I have the link to the boost its soak of you wanna try for me since you can always flash back....please
Click to expand...
Click to collapse
Even if it works for him it might not work for you since the stock recovery has a much harsher signature verification.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
AndyYan said:
Even if it works for him it might not work for you since the stock recovery has a much harsher signature verification.
Sent from Google Nexus 4 @ CM12.1
[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
Click to expand...
Click to collapse
I'm wondering what the downside, other than the obvious(creating a paperweight), would be on flashing the Boost software on a XT1028 on 4.4.4. Would it just fail and remain the same, or if not could one back out by flashing the Verizon 4.4.4 firmware.
http://androidforums.com/threads/cdma-get-ready-for-otas.897474/page-21
I have a spare XT1028 and I'm tempted.
sweetmyke said:
I've heard of people using the Brazil ota on the Asia retail. I'm really curious whether or not the boost its will work on Verizon. I don't care about the radio, I use it for WiFi. I hear they are the same exact phones tho. Let us know if you the
Click to expand...
Click to collapse
10amla said:
I'm wondering what the downside, other than the obvious(creating a paperweight), would be on flashing the Boost software on a XT1028 on 4.4.4. Would it just fail and remain the same, or if not could one back out by flashing the Verizon 4.4.4 firmware.
http://androidforums.com/threads/cdma-get-ready-for-otas.897474/page-21
I have a spare XT1028 and I'm tempted.
Click to expand...
Click to collapse
Like Andy says, signature verification on stock recovery is a lot tighter, so I'm inclined to guess that it would fail out of the gate.
a_gert said:
Like Andy says, signature verification on stock recovery is a lot tighter, so I'm inclined to guess that it would fail out of the gate.
Click to expand...
Click to collapse
That'd be my guess as well, I'm just trying to ascertain the probability of creating a paperweight(a nice one though). If it fails on the outset, the probability is low.
Bout to be in the same boat
10amla said:
I'm wondering what the downside, other than the obvious(creating a paperweight), would be on flashing the Boost software on a XT1028 on 4.4.4. Would it just fail and remain the same, or if not could one back out by flashing the Verizon 4.4.4 firmware.
http://androidforums.com/threads/cdma-get-ready-for-otas.897474/page-21
I have a spare XT1028 and I'm tempted.
Click to expand...
Click to collapse
I'm getting a LG l90 from my girl sometime next week. I still wanted this as my main but I will most likely try it
sweetmyke said:
I'm getting a LG l90 from my girl sometime next week. I still wanted this as my main but I will most likely try it
Click to expand...
Click to collapse
I'm using them as mini-tablets(WiFi only, so the radio is not important), I got 2 of them at Best Buy for $40 each. One is in the kitchen and is a home automation switch/ip camera. I've not deployed the 2nd one, so I could try it on that one.
10amla said:
I'm using them as mini-tablets(WiFi only, so the radio is not important), I got 2 of them at Best Buy for $40 each. One is in the kitchen and is a home automation switch/ip camera. I've not deployed the 2nd one, so I could try it on that one.
Click to expand...
Click to collapse
It won't let me post the link .,..I'll try to pm it
sweetmyke said:
It won't let me post the link .,..I'll try to pm it
Click to expand...
Click to collapse
Thanks, I've been reading the thread over at Android Forums. It's downloaded and copied to the phone, but not installed.
Did you put it on the root of your SD. You need stock recovery
10amla said:
Thanks, I've been reading the thread over at Android Forums. It's downloaded and copied to the phone, but not installed.
Click to expand...
Click to collapse
So you can get it on the SD but it won't let you install?
sweetmyke said:
So you can get it on the SD but it won't let you install?
Click to expand...
Click to collapse
No, I just copied it over to the phone. I've been re-reading the Android Forums thread to make sure I'm not missing anything. These phones are my first non-Samsung devices(I don't count the ol' Vizio), and the Moto world's a bit different. I want to reduce the chance of making any unforced errors.
I understand ....better safe than sorry
10amla said:
No, I just copied it over to the phone. I've been re-reading the Android Forums thread to make sure I'm not missing anything. These phones are my first non-Samsung devices(I don't count the ol' Vizio), and the Moto world's a bit different. I want to reduce the chance of making any unforced errors.
Click to expand...
Click to collapse
It's an ota so I'm sure you put it on the root of your SD card go to stock recovery and hit install update and from my understanding it will just turn your phone into a boost Mobile. I won't be able to try for another week or two unless you can confirm. I know for sure they pit the Brazil ota on the Asia one with stock recovery.
sweetmyke said:
It's an ota so I'm sure you put it on the root of your SD card go to stock recovery and hit install update and from my understanding it will just turn your phone into a boost Mobile. I won't be able to try for another week or two unless you can confirm. I know for sure they pit the Brazil ota on the Asia one with stock recovery.
Click to expand...
Click to collapse
What's holding me back right how is determining if there's a pathway back in case something goes badly. I see three outcomes(ordered good to bad): everything works and I'm on Boost mobile, it refuses to do anything, and it messes up. I want to be prepared for the last possibility. I seen horror stories about downgrading, and I want to minimize that possibility.
Added the Moto G into my sig. Hey, Mowned, no wearbles?
10amla said:
What's holding me back right how is determining if there's a pathway back in case something goes badly. I see three outcomes(ordered good to bad): everything works and I'm on Boost mobile, it refuses to do anything, and it messes up. I want to be prepared for the last possibility. I seen horror stories about downgrading, and I want to minimize that possibility.
Added the Moto G into my sig. Hey, Mowned, no wearbles?
Click to expand...
Click to collapse
And... It's option 2. It fails on verifying the package and aborts. No harm, no foul. So we wait for a few weeks/months(I've heard as late as August) for Verizon to come out with their OTA.
Can I upgrade with an unlocked bootloader and have no problems with the OTA updates?
I would be safe and sideload OTA's or flash the images using fastboot
Alright thanks can I just use Google updates or do I need Verizon images?
Still need VZW updates.
Sent from my Pixel using Tapatalk
quangtran1 said:
Still need VZW updates.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
where can I find the latest software to sideload for the verizon pixel?
drocny87 said:
where can I find the latest software to sideload for the verizon pixel?
Click to expand...
Click to collapse
https://developers.google.com/android/images
I just received a notification in my status bar for an update. The thing is, I've already applied the January update earlier this month. Anybody else getting this? Just curious why my phone thinks it needs to update...? I'm bootloader unlocked, twrp installed, Magisk 15.3 rooted and have the latest Flash kernel installed.
Yup. I just got the same thing. Any idea what it is?
JAYNO20 said:
Yup. I just got the same thing. Any idea what it is?
Click to expand...
Click to collapse
Nope. Hopefully someone smarter than me can chime in lol
jascolli said:
Nope. Hopefully someone smarter than me can chime in lol
Click to expand...
Click to collapse
Did you buy yours from Verizon?
I've got the notification too. Verizon model. Maybe this is the bootloader unlock fix!
JRJ442 said:
Did you buy yours from Verizon?
Click to expand...
Click to collapse
No from the Google store.
jascolli said:
No from the Google store.
Click to expand...
Click to collapse
I bought mine from Verizon and got it today too. I flashed stock back to take the OTA but it failed a few times. I was thinking it was a patched bootloader since they didn't do that with the January update. But apparently not if yours is from Google. There were some random lockscreen touch issues reported. It could possibly be a fix for that.
Sure hope it's not to lock the bootloader. My Verizon pixel 2 comes tomorrow and I want to unlock and root. I doubt it's preloaded already. Can anyone confirm you can unlock the bootloader with the new update?
I don't think it has anything to do with Verizon. I'm on T-mobile and got the 2nd update today as well.
rukawa2k said:
I don't think it has anything to do with Verizon. I'm on T-mobile and got the 2nd update today as well.
Click to expand...
Click to collapse
Verizon doesn't push the updates. It is linked to your IMEI and pushed by Google.
Just got notified myself... Google phone on Verizon
Got it installed, new build number OPM2.171019.016. Maybe a bug fix release. I'm at work or I'd check it out more. It installed just fine though on non-Verizon Pixel 2.
just got the notification and thought I was going crazy since I just sideloaded jan 5th update yestreday
My wife's phone got it, however mine has not. Both are Google play store phone, on Verizon.
i don't see anything on google's website for sideloads.
It's probably for Spectre/meltdown patches/fixes.
Sent from my walleye using XDA Labs
dobbs3x said:
It's probably for Spectre/meltdown patches/fixes.
Click to expand...
Click to collapse
I thought that initially as well. Went out and seen those issues were addressed already...at least according to BigRed
https://www.verizonwireless.com/support/google-pixel-update/
https://www.verizonwireless.com/support/google-pixel-2-update/
mikeprius said:
i don't see anything on google's website for sideloads.
Click to expand...
Click to collapse
I know. I've been keeping an eye out too.
b00ster23 said:
I thought that initially as well. Went out and seen those issues were addressed already...at least according to BigRed
https://www.verizonwireless.com/support/google-pixel-update/
https://www.verizonwireless.com/support/google-pixel-2-update/
Click to expand...
Click to collapse
Ya but these could be fixes to the last one. They rushed it out so probably some fixes.
Sent from my walleye using XDA Labs
FYI.....
https://9to5google.com/2018/01/18/google-pixel-2-receiving-new-out-of-cycle-android-8-1-ota-update/
Hey guys,
Shouldn't we receive today the update for may?
*spamming "check for updates" button*
first Monday of the month.
Jucacarvalho1987 said:
Hey guys,
Shouldn't we receive today the update for may?
Click to expand...
Click to collapse
Yeah, I'm kinda wondering that myself. Normally I start seeing screenshots all over the place. Nothing yet. I guess I lucked out getting my April update on the 4th, which was super weird since I NEVER get them right on the 5th.
live
https://developers.google.com/android/ota
Whats the difference between the OPM2.171019.029.B1 and the OPM4.171019.016.B1 build?
DeanNexus said:
Whats the difference between the OPM2.171019.029.B1 and the OPM4.171019.016.B1 build?
Click to expand...
Click to collapse
.029 is actually listed on Verizon's site, but they've had unified builds in the past, so I don't know that it's Verizon specific.
https://www.verizonwireless.com/support/google-pixel-2-update/
Twrp and magisk still work.
Sent from my Pixel 2 using Tapatalk
DeanNexus said:
Whats the difference between the OPM2.171019.029.B1 and the OPM4.171019.016.B1 build?
Click to expand...
Click to collapse
https://source.android.com/security/bulletin/pixel/2018-05-01
I'm in the UK and just had .029 pushed to my phone.
I just got it via OTA. No more multi-touch bug
munchy_cool said:
https://source.android.com/security/bulletin/pixel/2018-05-01
Click to expand...
Click to collapse
I could not find anything that explained the difference there. I'm on an unlocked Verizon P2 and need to make absolutely sure I flash the correct update, so I don't screw things up and lose root and twrp.
OPM2.171019.029.B1 is for normal builds, OPM4.171019.016.B1 is for Telus and Koodo
DuckRuckus said:
I could not find anything that explained the difference there. I'm on an unlocked Verizon P2 and need to make absolutely sure I flash the correct update, so I don't screw things up and lose root and twrp.
Click to expand...
Click to collapse
you will loose root and twrp if you flash factory image.
munchy_cool said:
you will loose root and twrp if you flash factory image.
Click to expand...
Click to collapse
I apologize...I meant the ability to root and install twrp
Hi, received via OTA.
dethknite said:
OPM2.171019.029.B1 is for normal builds, OPM4.171019.016.B1 is for Telus and Koodo
Click to expand...
Click to collapse
Actually, I'm not so sure about that anymore, since it clearly says that OPM4.171019.016.B1 is for "Fi Carriers". How do we know "Fi Carriers" doesn't simply mean anyone on Project Fi? In Dec 2017, OPM2 was "Telus Only" and then in Jan 2018 it was "Verizon".
Mike10705 said:
Actually, I'm not so sure about that anymore, since it clearly says that OPM4.171019.016.B1 is for "Fi Carriers". How do we know "Fi Carriers" doesn't simply mean anyone on Project Fi? In Dec 2017, OPM2 was "Telus Only" and then in Jan 2018 it was "Verizon".
Click to expand...
Click to collapse
It didn't clarify that earlier today, so that's where this all started.
Right and in the US, Project Fi is T-Mobile/Sprint/and US Cellular with network switching. So do we just close our eyes and pick one? I mean who knows at this point. I sideloaded to OPM4 from last month's OPM2 because I'm on Fi and I dont notice much of a difference in coverage. Then there is a guy on Reddit, on Telus, who said he was on OPM4 last month and was OTA flashed to OPM2.
OPM4 is all canadian Fi stuff (Volte+wifi) https://mobilesyrup.com/2018/02/23/koodo-telus-offer-carrier-services-integrated-google-assistant...
OPM2 is all others... I am US on Project Fi and running OPM2 fine. The build is essentially the same with those carrier specific changes.
Is it time to start guessing what the URL on https://s3.amazonaws.com/oneplussupport/ will be?
My best guess was https://s3.amazonaws.com/oneplussupport/OP7P/guacamole_21.O.07_190512.rar but no luck.
Edit: Found the EU one! https://s3.amazonaws.com/oneplussupport/OP7Pro/guacamole_21_E.08_190515.rar
OnePlus is definitely using this as the root directory: https://s3.amazonaws.com/oneplussupport/OP7Pro/
Does this mean we can unlock the T-Mobile variant with this?
Exathi said:
Does this mean we can unlock the T-Mobile variant with this?
Click to expand...
Click to collapse
Yes, this program will literally transform the T-Mobile variant into the international version you can buy from OnePlus directly. There is literally no difference between the two, you get the same OTAs as international version just as if you bought it from OnePlus
Holy hell. I found it.
https://s3.amazonaws.com/oneplussupport/OP7Pro/guacamole_21_E.08_190515.rar
LLStarks said:
Holy hell. I found it.
https://s3.amazonaws.com/oneplussupport/OP7Pro/guacamole_21_E.08_190515.rar
Click to expand...
Click to collapse
Woot time to unlock this thing
LLStarks said:
Holy hell. I found it.
https://s3.amazonaws.com/oneplussupport/OP7Pro/guacamole_21_E.08_190515.rar
Click to expand...
Click to collapse
Has a password, though.
But now we know the filename. This one is apparently for 9.5.4 on the EU model (GM1913). Can't find one for the other builds. Maybe it works for US/Global/India.
Vanhoud said:
Yes, this program will literally transform the T-Mobile variant into the international version you can buy from OnePlus directly. There is literally no difference between the two, you get the same OTAs as international version just as if you bought it from OnePlus
Click to expand...
Click to collapse
I believe the 6t tmobile version after the conversion could get over the air update. U have to.inject the updates manually. Quote me if im wrong but that was one of thw reason why i didnt convert my 6t.
eduardmc said:
I believe the 6t tmobile version after the conversion could get over the air update. U have to.inject the updates manually. Quote me if im wrong but that was one of thw reason why i didnt convert my 6t.
Click to expand...
Click to collapse
Not true. OTAs worked fine after full conversion.
LLStarks said:
But now we know the filename. This one is apparently for 9.5.4 on the EU model (GM1913). Can't find one for the other builds. Maybe it works for US/Global/India.
Click to expand...
Click to collapse
I'm going to try on my T-Mobile version hope everything goes well
engMTW said:
Not true. OTAs worked fine after full conversion.
Click to expand...
Click to collapse
U should have no issues with OTA, the tool turns ur phone back to as it was in the box, it relock bootloader, u roots and stock recovery, now there are some out there that could be modded to not delete userdata and no relock bootloader which means no incremental OTAs
twinnfamous said:
I'm going to try on my T-Mobile version hope everything goes well
Click to expand...
Click to collapse
So anyone know the password? Lol
Exathi said:
So anyone know the password? Lol
Click to expand...
Click to collapse
Nope just realized I downloaded for nothing.
would this remove sim lock?
Nekromantik said:
would this remove sim lock?
Click to expand...
Click to collapse
No but we can at least unlock the bootloader on the T-Mobile version
Permanent SIM unlock can probably be done with fastboot commands after a bootloader unlock.
I should have the US (OnePlus Store, not T-Mobile) MSMdownloadtool tomorrow, with the password. Stay tuned on that front.
Exathi said:
No but we can at least unlock the bootloader on the T-Mobile version
Click to expand...
Click to collapse
Thats only thing I want.
I wont have the tMobile one im in the UK and getting 5G variant and it might be sim locked but want to unlock bootloader and not wait 6 months before they give me unlock code.
I just called OP for the literally the 10th time today.
I told them I don't care about my warranty.. I just want the msm tool and unlock. Bin generator. They said that their technical support team is working on it. They also said they will be sending me an email with either the link for the MSM tool either today or tomorrow.
I doubt they will just give a token generator out but once we Hve our hands on the msm tool. We can sort some things out.