Develop Bugs

[Q] Is the Verizon Galaxy Nexus Still Worth It?

Is the Galaxy Nexus still worth it on Verizon half a year after launch? I'm looking to get a phone, and yes it has to be Verizon, and this is really the only appealing one. Don't feel like playing the waiting game.

Yes if you want AOSP android and are willing to deal with potential issues.

m0b1l3 said:
I'm looking to get a phone, and yes it has to be Verizon, and this is really the only appealing one.
Click to expand...
Click to collapse
So... you answered your own question.

joshnichols189 said:
Yes if you want AOSP android and are willing to deal with potential issues.
Click to expand...
Click to collapse
Damn I just ordered mine.. what issues.. ?
Sent from my LG Revolution using Tapatalk 2

mursepaolo said:
Damn I just ordered mine.. what issues.. ?
Click to expand...
Click to collapse
Just read the forums. People complain about anything and everything. There actually are real issues with signal, call quality and software hiccups... although they effect people differently.
Just use your device. Don't go looking for issues.

Okay, but do you think Verizon's gonna get the s3? Honestly though, I don't really like it. I don't even know if they're gonna change the processor for LTE. Is there a better phone on Verizon?

m0b1l3 said:
Okay, but do you think Verizon's gonna get the s3?
Click to expand...
Click to collapse
Nobody knows.
Honestly though, I don't really like it. I don't even know if they're gonna change the processor for LTE.
Click to expand...
Click to collapse
Okay... then you don't care.
Is there a better phone on Verizon?
Click to expand...
Click to collapse
Completely subjective. Go try them all and do your research then decide. How can I know what you want?

Yes, Verizon along with the other two big carriers as well as US Cellular is getting the S3.
Problems with the Nexus:
1. battery life is terrible. buy the extended battery from VZW, makes a world of difference.
2. Can't transfer data off the phone via usb.

jgarozzo said:
2. Can't transfer data off the phone via usb.
Click to expand...
Click to collapse
Uh. Yes you can. Plug it in, open Windows Explorer (or Android File Transfer on OSX) and transfer files.

jgarozzo said:
2. Can't transfer data off the phone via usb.
Click to expand...
Click to collapse
Can't tell if serious..

Yes, the Verizon Nexus is worth it. Its easily still the best Verizon phone available right now (unless you want the Razor Maxx's battery life).
Like all current smart phones, it's not perfect, but I've found that the latest 4.0.4 update has cleared up most of my software problems. (Been running a leaked build for about a month now, though I switched to stock yesterday so I could get the official OTA update - which came through a couple hours ago).
Only complaints for me right now are hardware related: so-so camera, screen banding, and status bar burn in on the screen (this may or may not be a hardware failure, as some other phones I've seen don't have the issue, but then others have it MUCH worse as well).
I should also note that I live in Phoenix and have great LTE coverage, so I can't comment on any of the network issues that some people have reported.
Ultimately, I would say pick it up and try it out for a while. If it doesn't work for you take it back and wait for another phone to come out.
Sent from my Galaxy Nexus

I'm having the same dilemma as well, although I have begun leaning heavily to the Gnex simply because after going to the store and checking out the Razr Maxx, it just looked terribly ugly to me.
The sad part is a major deciding factor for me leaning towards the gnex was that I assumed it had an unlocked bootloader (ITS A NEXUS). Now that I know it is not unlocked, I am back on the fence. I know it can be easily unlocked, but that voids the warranty (if they can tell...), do you guys really think VZW would decline a return or exchange based on the bootloader?

juntistik said:
The sad part is a major deciding factor for me leaning towards the gnex was that I assumed it had an unlocked bootloader (ITS A NEXUS). Now that I know it is not unlocked, I am back on the fence. I know it can be easily unlocked, but that voids the warranty (if they can tell...), do you guys really think VZW would decline a return or exchange based on the bootloader?
Click to expand...
Click to collapse
Sigh... You realize that having a phone ship with an unlocked bootloader would be a HUGE security problem? Giving full access to the hardware without any user intervention, how is that a good idea?
People need to seriously understand the difference between a locked bootloader (which ALL phones should have by stock) and an encrypted bootloader, which is one that is locked, and not easily unlockable (requires an exploit to unlock).
Just because its locked by default, doesn't mean it can't be unlocked. It literally takes 1 command line prompt: "fastboot oem unlock" to unlock that bootloader and do whatever you want with the device. It can also be easily relocked with just 1 more command prompt as well. Verizon cannot tell you've unlocked once you've locked again, and as long as you're not stupid enough to return a non-stock phone, they will never deny you a warranty claim.
Read up on the subject before you start pulling out these stupid, baseless complaints. I'm tired of hearing people complain about locked vs unlocked bootloaders when they clearly have no idea what it actually means or offers them.

martonikaj said:
Sigh... You realize that having a phone ship with an unlocked bootloader would be a HUGE security problem? Giving full access to the hardware without any user intervention, how is that a good idea?
People need to seriously understand the difference between a locked bootloader (which ALL phones should have by stock) and an encrypted bootloader, which is one that is locked, and not easily unlockable (requires an exploit to unlock).
Just because its locked by default, doesn't mean it can't be unlocked. It literally takes 1 command line prompt: "fastboot oem unlock" to unlock that bootloader and do whatever you want with the device. It can also be easily relocked with just 1 more command prompt as well. Verizon cannot tell you've unlocked once you've locked again, and as long as you're not stupid enough to return a non-stock phone, they will never deny you a warranty claim.
Read up on the subject before you start pulling out these stupid, baseless complaints. I'm tired of hearing people complain about locked vs unlocked bootloaders when they clearly have no idea what it actually means or offers them.
Click to expand...
Click to collapse
^This
This is the way all Nexus phones have been. You should be grateful Samsung lets you re-lock the bootloaders in case you have any issues. The HTC Nexus One was a permanent unlock.

Gnex is you want Android
iP4 if you want iOS
Those are pretty much the best phones on VZW at the moment.

You shouldn't worry too much about the locked boot loader on the Nexus. It's REALLY easy to unlock/re-lock the phone as needed.
If you're not comfortable doing it manually you can always download a tool to take care of the process for you.
For example: I just used the WugFresh Galaxy Nexus tool to return my phone to it's stock software, with a locked boot loader, so that I could try out the ota 4.0.4 update for a while. As far as anyone else can tell it's always run the stock version of Android and hasn't been fiddled with.
It's also good to remember that unlocking the boot loader on the Nexus doesn't require you to download some b.s. tool like HTC is using, and there's no official record of you playing with your phone.
Sent from my Galaxy Nexus

tell them your having problems with service, continuous dropped calls, get out of your contract. find an area that gets terrible verizon service, tell them your moving there. they will allow you out. they go grab t-mobile

I've had mine for a couple days and love it!! LTE is awesome, AOKP is awesome and the size is the best!!! Def a good phone still to look at.
Sent from my Verizon Samsung Galaxy Nexus

Apparently the s3 is about to come out on Verizon? Do you think I should still go with the GNex? I absolutely hate the design of the s3, and I'm not thinking the quad cor is gonna stay. 2 GB ram however.

Drop Verizon and get the gsm version
Sent from my HTC sensation 4g using Tapatalk

I have a Google store pixel running on the Verizon build, and it seems hard to fix.

I'll try to keep it short, but;
I bought a Google edition Pixel XL from swappa because I saw a really good deal on it and couldn't pass it up. Though even though it's a google bought phone (I checked the IMEI and unlocked the bootloader with no problems, so it basically has to be), I'm on the Verizon build of NDE63X instead of NDE63V, which is the "regular" build. I'm not sure if this could pose any problems in the future, but I thought I'd try to get on the regular build in case.
I tried sideloading the normal OTA image, but it denied by saying it was out of date as compared the build I'm on now? It was downloaded straight from the Google developers page, so that doesn't seem to make sense to me. Eventually I toyed around and ended up flashing the phone with the google edition of the OTA, and everything seemed to be in order. All of this was a pretty long and painstaking process because I've known barely anything about the intricacies of Android before like 2 days ago and have just been learning it all from scratch. However, when I finally was in the V build over the X build, I saw my phone had an update; I went ahead and installed it just thinking that it was standard and maybe the OTA I flashed in was lacking the November security patch or something. When this update went through, it put me back on the X build. Needless to say I was a little frustrated, I kinda felt like I just wasted a royally large amount of time.
So I guess that leaves the question of; why/how exactly did this happen? Is it an issue?
My bootloader is unlocked now after that whole fiasco; should I relock it? Is it any kind of significant security issue? I've heard that relocking the bootloader can brick the phone entirely, and lord knows I don't want that.
If I keep the bootloader unlocked, what exactly can I do with it? I know it allows to install custom kernals/roms, but I'm not exactly sure what that's like or what it's exactly capable of. I know, this is a very general question that I could google. But I'd also just like to hear people's inputs about it.
Will my phone get regular updates with the bootloader unlocked, or would it unable/cause some kind of error?
Thanks in advance for any replies! Like I said, I'm still really new to this whole thing, so if you could kind of explain answers and/or instructions in kind of a black-and-white way that would help me a lot. All of this is kind of intimidating, but it's also been a lot of fun, I like learning about it all.

@cam30era
This is what I did, I actually had it on the V build, for all of about 20 minutes. Then it pushed an update through and the update changed it back to the X. I'm not sure if I screwed something up along the way or exactly how it happened, but it seemed like a kind of unique thing.

Actually, if you'd like to downgrade, make sure your bootloader is unlocked. Flash the boot image from the factory image zip. After that you can sideload the V ota.
Sent from my Pixel XL

So what exactly is your problem with the build that you have other than being the "Verizon" version? The phone isn't going to function any different and there are probably little to no differences in the software other than a letter on the build number.
Sent from my Pixel XL

Odds are that the radio is the only difference. There were different radios for the Nexus 6 between VZW and GSM, but the firmware was basically identical there too. I really don't get why everyone is hell-bent on the VZW firmware being different or no good with the Pixel but they weren't with past devices.
Sent from my Pixel XL

That would only affect models sourced from Verizon...
Sent from my Pixel XL

imnuts said:
Odds are that the radio is the only difference. There were different radios for the Nexus 6 between VZW and GSM, but the firmware was basically identical there too. I really don't get why everyone is hell-bent on the VZW firmware being different or no good with the Pixel but they weren't with past devices.
Sent from my Pixel XL
Click to expand...
Click to collapse
Agreed. AS long as you keep your bootloader unlocked you can flash what you want. If you see something amiss flash another version.
Flashing the verizon firmware on a Non verizon phone should be fine. @imnuts said, same questions and answers with the Nexus 6. I flashed all sorts of builds just to see how they would perform... IN the end there were all the same.

bricked pixel xl after july security update

Hey all,
I recently had to get my pixel replaced from Google and they sent me a refurbished one about a week ago. I updated to the July security update yesterday and over night my battery drained from 43% to 3% when I woke up. Took a shower and came back 15 mins later to find my pixel completely dead and wouldn't take a charge or anything. Weird thing is, my computer will find it in fastboot, but won't let me flash anything because it isn't the correct device even though I downloaded the factory images for the Verizon pixel XL, which I have. I'm just curious if anyone else experienced something like this after the update or if I got a bad refurb. Either way it's on its way back to Google now. I'm just curious before updating my broken phone to the new update

I'm not sure what you mean by it wasn't the correct device. If you were able to unlock the bootloader then Google didn't send you a Verizon Pixel XL which might be why you couldn't flash the Verizon image on your phone.

jhs39 said:
I'm not sure what you mean by it wasn't the correct device. If you were able to unlock the bootloader then Google didn't send you a Verizon Pixel XL which might be why you couldn't flash the Verizon image on your phone.
Click to expand...
Click to collapse
You can flash any of the pixel XL images to a pixel XL device. Whether it is Google or Verizon version makes no difference. Mines Verizon version running the T-Mobile build.

toknitup420 said:
You can flash any of the pixel XL images to a pixel XL device. Whether it is Google or Verizon version makes no difference. Mines Verizon version running the T-Mobile build.
Click to expand...
Click to collapse
I didn't know that. I thought maybe the build had to be the same variant that was originally shipped with the phone. Wonder what was meant by wasn't the correct device then?

jhs39 said:
I didn't know that. I thought maybe the build had to be the same variant that was originally shipped with the phone. Wonder what was meant by wasn't the correct device then?
Click to expand...
Click to collapse
I don't think his device was actually in the bootloader. Which could explain the incorrect device issue. I think he was in some Qualcomm mode. Which you need manufacturer tools to fix from there.

PIXEL 2 XL QUESTIONS ~ Bootloader, Black Smudge, Etc.

After unlocking the Bootloader on my Pixel 2 XL (Android 8.1 DP1) my Play Store Device Certification as "Uncertified", is that normal??
Also, I've seen thread about the screen's Blue shifts and comparing build date but has anyone compared the Black smudge effect?
My RMAed Pixel2 XL (Build date 10/18) has it really bad. Is everyone experiencing this? Is it just part of the POLED Tech?
Lastly, has Android 8.1 DP1 been buggy for anyone? It's constantly crashing the Google app and sometimes doesn't register taps on my screen (across all apps different locations)
I've Factory resetted twice this week.
Thanks!

I unlocked my Pixel and this shows whenever I turn my phone on/off. I've never owned a Pixel or Nexus, is this normal?

rank78 said:
I unlocked my Pixel and this shows whenever I turn my phone on/off. I've never owned a Pixel or Nexus, is this normal?
Click to expand...
Click to collapse
Yes, that is normal. You need not worry.

Also, it cannot be removed. It will always show if you have an unlocked bl

You'll need to get used to that message...

Lawlrus said:
Also, it cannot be removed. It will always show if you have an unlocked bl
Click to expand...
Click to collapse
galaxys said:
You'll need to get used to that message...
Click to expand...
Click to collapse
Dammit, it's annoying as hell. Thanks guys.

OnePlus 7t using verizon- bootloader unlock question

Hi.
Just had high level verizon tech fix my cdma-less on my account and I have this great working phone that says T-Mobile on the init boot screen but is actually running Verizon.
Regarding unlocking the bootloader, (why do I always have to do this? I think I have a sickness... I just... cant... help it....) why would the standard fastboot unlock not work? I was thinking of trying it when I get home just to see what happens. I already have the dev/OEM unlock selected. Plus the phone says it is already unlocked for any service. Most posts are tmobile posts relying on a 7 day wait from tmobile to get a code/something... I am thinking that would not apply to me for better or worse.
I really just need root for a complete blackout theme and pull off a few bloatware tmobile apps. But it runs so good now, as is, that it really isnt imperative.

Oh, I see. I need an unlock token. bummer

Well yes and no about the token. I have a HD1907 working very nicely on verizon, but I'm on the global firmware and did not have to wait a week for the token.
Edit: My first oneplus phone and I'm not sure I get exactly why a lot do not like 7t but I'm really digging and loving the phone.

jmkarnai01 said:
Well yes and no about the token. I have a HD1907 working very nicely on verizon, but I'm on the global firmware and did not have to wait a week for the token.
Edit: My first oneplus phone and I'm not sure I get exactly why a lot do not like 7t but I'm really digging and loving the phone.
Click to expand...
Click to collapse
I put in a request for the token and will wait a week. I see how it can be done as you mentioned. I am thinking I will be cool with just magisk modding the boot img and getting root that way. Keeping everything else as is. I really dig the oneplus ui.
After having a bunch of other phones throughout the years, I can say that this oneplus is just very nice. I have no complaints, just compliments. If this is how oneplus devices are then I was missing out before! *except the strange wait time for unlocking the bootloader via-oneplus*

https://forum.xda-developers.com/oneplus-7t/how-to/t-mobile-7t-conversion-to-international-t4153943
This is what you need

aer0zer0 said:
https://forum.xda-developers.com/oneplus-7t/how-to/t-mobile-7t-conversion-to-international-t4153943
This is what you need
Click to expand...
Click to collapse
Thanks. I will try this tonight.
** I am now rooted.
I feel blessed to have such a fast and smooth phone. A mix of substratum themes helped blackout my phone.

canezila said:
Hi.
Just had high level verizon tech fix my cdma-less on my account and I have this great working phone that says T-Mobile on the init boot screen but is actually running Verizon.
Regarding unlocking the bootloader, (why do I always have to do this? I think I have a sickness... I just... cant... help it....) why would the standard fastboot unlock not work? I was thinking of trying it when I get home just to see what happens. I already have the dev/OEM unlock selected. Plus the phone says it is already unlocked for any service. Most posts are tmobile posts relying on a 7 day wait from tmobile to get a code/something... I am thinking that would not apply to me for better or worse.
I really just need root for a complete blackout theme and pull off a few bloatware tmobile apps. But it runs so good now, as is, that it really isnt imperative.
Click to expand...
Click to collapse
Got any tips for getting them to activate cdma-less? Everytime I've tried they just say they don't have the option and just resort to my device not being compatible.

ammmze said:
Got any tips for getting them to activate cdma-less? Everytime I've tried they just say they don't have the option and just resort to my device not being compatible.
Click to expand...
Click to collapse
Threatening to change to TMobile or similar

canezila said:
Hi.
Just had high level verizon tech fix my cdma-less on my account and I have this great working phone that says T-Mobile on the init boot screen but is actually running Verizon.
Regarding unlocking the bootloader, (why do I always have to do this? I think I have a sickness... I just... cant... help it....) why would the standard fastboot unlock not work? I was thinking of trying it when I get home just to see what happens. I already have the dev/OEM unlock selected. Plus the phone says it is already unlocked for any service. Most posts are tmobile posts relying on a 7 day wait from tmobile to get a code/something... I am thinking that would not apply to me for better or worse.
I really just need root for a complete blackout theme and pull off a few bloatware tmobile apps. But it runs so good now, as is, that it really isnt imperative.
Click to expand...
Click to collapse
Hello, I just purchased a 7T that I am planning to use on Visible (Verizon network) I was looking through the forum and saw your post. Did you initially have a problem running the 7T on the Verizon network? I s that the reason you had the tech working to fix your CDMA account? I'm trying to decide if I want to go through the hastle or just switch to another provider where I can just use the phone.

hermdresh said:
Hello, I just purchased a 7T that I am planning to use on Visible (Verizon network) I was looking through the forum and saw your post. Did you initially have a problem running the 7T on the Verizon network? I s that the reason you had the tech working to fix your CDMA account? I'm trying to decide if I want to go through the hastle or just switch to another provider where I can just use the phone.
Click to expand...
Click to collapse
Mostly to fix sms/mms