Related
Hi,
please poste here if you receive the 4.04 ICS update for yakjuxw
Please only reply if you actually received the update!
yes got it this morning, not noticed anything different with it
Yakjuxw? Nothing here..
Sent from my Galaxy Nexus using Tapatalk
alan_g said:
yes got it this morning, not noticed anything different with it
Click to expand...
Click to collapse
Are you sure you have a yakjuxw version?
alan_g said:
yes got it this morning, not noticed anything different with it
Click to expand...
Click to collapse
can you look for the url for us in the logs?
Had this version.. but I converted to yakju ... didn't think updates from Samsung would be this close to Google's Release
-Google Galaxy Nexus
My phone was yakjuxw but I converted to yakju and never looked back. It is child's play to convert and you get direct and fast update support directly from Google. Go for it.
larryvand said:
My phone was yakjuxw but I converted to yakju and never looked back. It is child's play to convert and you get direct and fast update support directly from Google. Go for it.
Click to expand...
Click to collapse
True, true. But warranty is through Vodafone where I got it from and it'll be void if I reflash it. I already sent it twice back. First time it had the motherboard replaced because of a boot loop and now it's there for unexplained battery drain, 40% overnight with everything but the phone disabled.
I just got a yakjuxw nexus yesterday, and immediately fastboot flashed to yakju, 4.0.4. First time, it boot looped, but a second attempt went just fine. I figured this was the easiest way to make sure I got updates from Google in a timely manner.
Method for quicker OTA update
I got the update OTA (UK).
I used this method to get it quicker. Took about 6 attempts, but i didn't bother rebooting.
Should work, some redditors said it took anywhere from 2-20 attempts :/
http ://www.reddit.com/r/GalaxyNexus/comments/rq0qh/ysk_how_to_get_the_404_ota_quicker/
(delete the gap after "http", can't post links yet!)
wingzero2085 said:
I just got a yakjuxw nexus yesterday, and immediately fastboot flashed to yakju, 4.0.4. First time, it boot looped, but a second attempt went just fine. I figured this was the easiest way to make sure I got updates from Google in a timely manner.
Click to expand...
Click to collapse
In which country did you get it?
I'm hoping to see a Danish dictionary in the update and I thought the xw was a European build, but it looks like its all over the world.
purekillforce said:
I got the update OTA (UK).
I used this method to get it quicker. Took about 6 attempts, but i didn't bother rebooting.
Should work, some redditors said it took anywhere from 2-20 attempts :/
http ://www.reddit.com/r/GalaxyNexus/comments/rq0qh/ysk_how_to_get_the_404_ota_quicker/
(delete the gap after "http", can't post links yet!)
Click to expand...
Click to collapse
You have a yakjuxw version?
purekillforce said:
I got the update OTA (UK).
I used this method to get it quicker. Took about 6 attempts, but i didn't bother rebooting.
Should work, some redditors said it took anywhere from 2-20 attempts :/
http ://www.reddit.com/r/GalaxyNexus/comments/rq0qh/ysk_how_to_get_the_404_ota_quicker/
(delete the gap after "http", can't post links yet!)
Click to expand...
Click to collapse
And you are sure you have yakjuxw?
yakjuxw only.
I think peoples should read properly that OP stated yakjuxw only, not yakju or converted.
Toxvaerd said:
In which country did you get it?
I'm hoping to see a Danish dictionary in the update and I thought the xw was a European build, but it looks like its all over the world.
Click to expand...
Click to collapse
My phone is an unlocked European model, but I'm in the US on AT&T. Note that I converted my yakjuxw build to the plain Google yakju. I'm not even sure why anyone wouldn't do this (aside from being afraid of bricking your phone )-- it wasn't that difficult to do using the Gnex toolkit offered in the development section here.
The worst part for me was getting my Win7 64 bit PC to recognize my phone in fastboot mode and actually install the driver. Once I did that, I was good to go (ok, maybe except the boot loop, but I've flashed the hell out of a Viewsonic G-Tablet before, so boot looping wasn't anything I haven't seen already).
wingzero2085 said:
My phone is an unlocked European model, but I'm in the US on AT&T. Note that I converted my yakjuxw build to the plain Google yakju. I'm not even sure why anyone wouldn't do this (aside from being afraid of bricking your phone )-- it wasn't that difficult to do using the Gnex toolkit offered in the development section here.
The worst part for me was getting my Win7 64 bit PC to recognize my phone in fastboot mode and actually install the driver. Once I did that, I was good to go (ok, maybe except the boot loop, but I've flashed the hell out of a Viewsonic G-Tablet before, so boot looping wasn't anything I haven't seen already).
Click to expand...
Click to collapse
Thanks for your input, but I'm not going to convert my phone. This kind of discussion is so OT.
wingzero2085 said:
I'm not even sure why anyone wouldn't do this (aside from being afraid of bricking your phone )
Click to expand...
Click to collapse
I've already got my phone set up the way I want to and I don't want to lose three months worth of texts and such to wipe my phone for yakju
Is it so hard to read the topic title?
ONLY POST IF YOU RECEIVED THE UPDATE FOR THE yakjuxw version!
dendirk said:
Is it so hard to read the topic title?
ONLY POST IF YOU RECEIVED THE UPDATE FOR THE yakjuxw version!
Click to expand...
Click to collapse
Did you receive it?
Because...you know...you posted
Don't go there man. Keep it on topic. This thread is here so we know when an update for your Nexus is spottet.
Keep it on topic so the important information doesn't drown in useless comments like that.
Hey there,
So I just got my GSM Galaxy Nexus in the mail today and found a couple things to be a bit odd. You see, my package came with 2 Galaxy Nexuses (or nexi?) and my brother's phone seemed completely normal. It had Android 4.0.4 which he instantly got an update for Jellybean. My phone on the other hand was a bit off, as stated previously. My Galaxy Nexus shipped with Android 4.0.1, when i went to the "about phone" tab, there was no option to even check for a system update, my lock screen doesn't work (security settings are on slide yet the power button just wakes my screen and no sliding to unlock required), I have no market or google play store, I can't add a Gmail account under the "accounts and sync" tab, and my home button wasn't working (factory resetting fixed this).
I'm honestly just stuck on what to do about this device. I've factory reset this device 5 times already and nothing else has worked except for fixing the home button which wasn't working on my initial boot up.
Is there any solution to this Nexus or do I just have a defective one?
U can get rif of lock screen in the setting>security>screen lock<none
Sent from my Galaxy Nexus using xda premium
In Settings - About Phone, what is your Build Number? Also your brother's?
Any why couldn't you have picked your brother's phone out of the box?
netbuzz said:
In Settings - About Phone, what is your Build Number? Also your brother's?
Any why couldn't you have picked your brother's phone out of the box?
Click to expand...
Click to collapse
Build Number: full_maguro-eng 4.0.1 ICL23D 347 test-keys
And why couldn't I have picked my brother's? Haha I don't know!
They sent you a phone with an early engineering build. This can be easily fixed by flashing the stock Google image.
Here's a guide with all the info you need. http://forum.xda-developers.com/showthread.php?t=1626895
If you are in the US flash the takju build. Elsewhere the yakju build.
I'll hang out here for a while. If you have any questions reply here and I'll help!
Sent from my Nexus 7 using xda premium
airkenada said:
U can get rif of lock screen in the setting>security>screen lock<none
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The problem is that my settings are set to slide yet my phone is acting as if it's set to none
El Daddy said:
They sent you a phone with an early engineering build. This can be easily fixed by flashing the stock Google image.
Here's a guide with all the info you need. http://forum.xda-developers.com/showthread.php?t=1626895
If you are in the US flash the takju build. Elsewhere the yakju build.
I'll hang out here for a while. If you have any questions reply here and I'll help!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Does this void any warranty?
BrokeEven said:
Does this void any warranty?
Click to expand...
Click to collapse
You won't have a problem with warranty if you are running a stock build.
http://www.blogcdn.com/www.engadget.com/media/2011/11/nexnex20111117103746mat400mat400.jpg
Can you compare whether your phone and your brother's have some of these apps? I'm betting its your phone.....
maschiosoosai said:
Can you compare whether your phone and your brother's have some of these apps? I'm betting its your phone.....
Click to expand...
Click to collapse
Ha yeah! The not-so-normal apps that I have on my phone include "Angry GPS", "Dev Tools", and "SUB PBA Test". I checked with my Brother's Nexus running JB and he's got none of those. I called into Google's hotline for Nexus support and was able to get in touch with one of the supervisors. I was told that the device I received was a Developer's Model and that it was the "strangest thing ever".
El Daddy said:
You won't have a problem with warranty if you are running a stock build.
Click to expand...
Click to collapse
So, the instructions involve unlocking my bootloader (a task I know very little about!). To be honest, I don't have much experience with the mobile development. The only thing I've done in terms of tweaking with phones is following the instruction with the ace hack kit to root my phone (which seemed a lot more simplier than these instruction) and flashing custom ROMs.
To further my previous question, since the instructions say unlock the bootloader, does that invalidate my phone's warranty if I were to return anytime within its warranty period with an unlocked bootloader running stock android? (Would they even check/realize?)
And lastly, how safe is this procedure (returning the stock?) Is there a chance to brick my device?
BrokeEven said:
So, the instructions involve unlocking my bootloader (a task I know very little about!). To be honest, I don't have much experience with the mobile development. The only thing I've done in terms of tweaking with phones is following the instruction with the ace hack kit to root my phone (which seemed a lot more simplier than these instruction) and flashing custom ROMs.
To further my previous question, since the instructions say unlock the bootloader, does that invalidate my phone's warranty if I were to return anytime within its warranty period with an unlocked bootloader running stock android? (Would they even check/realize?)
And lastly, how safe is this procedure (returning the stock?) Is there a chance to brick my device?
Click to expand...
Click to collapse
You need to unlock your bootloader to flash the images. You can always relock your bootloader if you wish. You won't have an issue with the warranty.
Flashing the images the way I provided is a good way to learn the basics and will be beneficial in the future. It's very easy to learn. Just follow the link step by step. Flashing with fastboot is the safest way to do things and there is a very small chance of you bricking your phone.
Also what did google tell you to do when you called them?
Development Tools
maschiosoosai said:
Can you compare whether your phone and your brother's have some of these apps? I'm betting its your phone.....
Click to expand...
Click to collapse
I just got another Nexus from Play Store.
It's in developer mode, without Google apps and filled with a bunch of testing tools, like AngryGPS and Screen Test, the same menu in this image from maschiosoosa.
I tried to call Google Support and they give me two options.. One is doing exactly what everybody does.. Flash a stock Google image (but they said: "it's a very difficult way" lol) or the second, they will call Samsung for a replacement.
It's not a defective device, but it's kind of getting a Windows 8 Consumer Preview. A thing that it's not finished yet. Shame on Goole. lol
I'll flash of course.. It seems the bootloader is unlocked and its probably easy to do the flash thing.
Hey BrokeEven, if you got your device from Play Store you can ask for a replacement (if you are not sure of the flash image).
And probably your bootloader is already unlocked (at least if you received this same dev tool device).
El Daddy said:
You need to unlock your bootloader to flash the images. You can always relock your bootloader if you wish. You won't have an issue with the warranty.
Flashing the images the way I provided is a good way to learn the basics and will be beneficial in the future. It's very easy to learn. Just follow the link step by step.
Also what did google tell you to do when you called them?
Click to expand...
Click to collapse
Thank you, I'm gonna give it a shot!
When I called Google and talked to one of the supervisors, he was almost excited to hear about such an "interesting" story and said, "It looked like you may have gotten a rooted or developers model" and "If i got a dev model, I'd just keep it haha - but that's just me" I proceeded to ask him about whether or not it'd be a safe idea to keep the phone and do my own tweaking and such. He responded by telling me that even if i was to safely flash back to stock, it'd be "hard to prove" to Google or Samsung that I hadn't tampered with it. He was a cool guy
So let's say I did in fact get a rooted model by mistake, is there any way I'd be able to figure out if the bootloader is locked or not (even though rooted doesn't necessarily mean it has an unlocked bootloader)?
BrokeEven said:
Thank you, I'm gonna give it a shot!
When I called Google and talked to one of the supervisors, he was almost excited to hear about such an "interesting" story and said, "It looked like you may have gotten a rooted or developers model" and "If i got a dev model, I'd just keep it haha - but that's just me" I proceeded to ask him about whether or not it'd be a safe idea to keep the phone and do my own tweaking and such. He responded by telling me that even if i was to safely flash back to stock, it'd be "hard to prove" to Google or Samsung that I hadn't tampered with it. He was a cool guy
So let's say I did in fact get a rooted model by mistake, is there any way I'd be able to figure out if the bootloader is locked or not (even though rooted doesn't necessarily mean it has an unlocked bootloader)?
Click to expand...
Click to collapse
Yep... The same case... The guys on Google are very funny. lol
Reboot your device and check if theres a unlocked locker at the bottom of the Google logo screen.
BrokeEven said:
Thank you, I'm gonna give it a shot!
When I called Google and talked to one of the supervisors, he was almost excited to hear about such an "interesting" story and said, "It looked like you may have gotten a rooted or developers model" and "If i got a dev model, I'd just keep it haha - but that's just me" I proceeded to ask him about whether or not it'd be a safe idea to keep the phone and do my own tweaking and such. He responded by telling me that even if i was to safely flash back to stock, it'd be "hard to prove" to Google or Samsung that I hadn't tampered with it. He was a cool guy
So let's say I did in fact get a rooted model by mistake, is there any way I'd be able to figure out if the bootloader is locked or not (even though rooted doesn't necessarily mean it has an unlocked bootloader)?
Click to expand...
Click to collapse
Reboot the phone, when it's rebooting (showing google logo) if there's unlocked sign (lock that is unlocked) under the google logo, then it's unlocked Nexus. If you only see Google logo, then it's just locked Nexus
I don't know whether this is a curse or a blessing... I remembered when i ordered this phone I said "meh, I'm not gonna bother with rooting and flashing ROMs. I'll just stick to stock. And so Google sends me a Nexus with an unlocked bootloader and now force me to flash back to stock (or root) in order to get my phone fully functional
One pic is my unlocked bootloader, the other is a picture of my ALL the apps on my phone
Cool so you are already unlocked. Just download the images and flash away!
Sent from my Nexus 7 using xda premium
El Daddy said:
Cool so you are already unlocked. Just download the images and flash away!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Just one question and this may be a simple one...
It's step 8 under subsection C. What does it mean to open the command prompt in the same directory? And sorry in advance! I need you to be very simple in explaining this to me. To my knowledge, I thought you just open the command prompt. How do you open the command prompt in the same directory?
BrokeEven said:
Just one question and this may be a simple one...
It's step 8 under subsection C. What does it mean to open the command prompt in the same directory? And sorry in advance! I need you to be very simple in explaining this to me. To my knowledge, I thought you just open the command prompt. How do you open the command prompt in the same directory?
Click to expand...
Click to collapse
On windows just hold down shift while you right click in the folder. You will see open command prompt here or similar.
Sent from my Nexus 7 using Tapatalk 2
Basically, after reading several posts where users of Galaxy Nexus devices ordered via Google Play Store reported 'fastboot oem unlock' did NOT wipe their personal data (as it should, this is an important security feature), I'm curious if this is a widespread phenomenon. Do all Play Store Nexus devices display this behavior? Is it a bug for a specific batch of devices? Did Google remove the security feature on purpose?
For those of you owning a Play Store Nexus and unlocked the bootloader via fastboot oem unlock, I have a few questions:
1) after you issued the fastboot oem unlock command, did you need to confirm this action on the phone and did this look like the picture attached to this post?
2) was your personal data untouched after the unlock?
3) what version of the bootloader where you running at the time of the unlock?
Thanks in advance.
this thread might be useful to read over.
http://forum.xda-developers.com/showthread.php?t=1650830
Zepius said:
this thread might be useful to read over.
http://forum.xda-developers.com/showthread.php?t=1650830
Click to expand...
Click to collapse
Thanks. And I thought I searched before posting...
Petrovski80 said:
Thanks. And I thought I searched before posting...
Click to expand...
Click to collapse
And we can't find the cause btw.
Mach3.2 said:
And we can't find the cause btw.
Click to expand...
Click to collapse
Yeah I just finished reading the thread. Too bad, despite everybody's efforts in that thread. I've modified my bootloader info post with this new (for me) info btw.
I purchased my Galaxy Nexus from a high street store here in England and the OEM unlock command also did not wipe data. It was running 4.0.4 out of the box if that makes any difference.
Sent from my Galaxy Nexus
Hi everyone, in our Italian n5x community some of us are getting troubles from lg assistance... bootloaders are locked and it seems it's not allowed to unlock it anymore, wich obviously means people is not allowed anymore to unlock, root and so on...
Why is that possible? Is there any way to bypass this kind of "security lock" ?
Sent from my Nexus 6P using XDA-Developers mobile app
andreak said:
Hi everyone, in our Italian n5x community some of us are getting troubles from lg assistance... bootloaders are locked and it seems it's not allowed to unlock it anymore, wich obviously means people is not allowed anymore to unlock, root and so on...
Why is that possible? Is there any way to bypass this kind of "security lock" ?
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Try flashing the H791 TOT file someone here created:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
It has the RPM partitions specified in the GPT partition table but it doesn't have any contents flashed onto it. Hopefully that would be enough.
Did this help anything? I am having the same problems here ...
Hey, got the same problem here. Posted about this even before I saw this post; gonna try this and inform you about it as I get home.
Alright, tried to flash the .tot file but I sadly got nothing. Worse, I got a hardbrick apparently: my N5x stays still on the Google screen, and "No RPMB" is still there.
However, flashing an ota makes my device work again, but still "No RPMB". And obviously, it doesn't let me unlock bootloader for a longer time than a reboot.
Well that's sad to read. Thx for trying anyway. Seems like a(nother) rma is the only solution then? ...
Grammat said:
Well that's sad to read. Thx for trying anyway. Seems like a(nother) rma is the only solution then? ...
Click to expand...
Click to collapse
Afraid so. Just sent my N5x to LG Remember to specify that rpmb is causing problems. At least, that's what I did, hopefully it will get the work done. Let's see in 20ish days...
Nothing fixed that rpmb status....shame on lg
Sent from my Nexus 6P using XDA-Developers mobile app
andreak said:
Nothing fixed that rpmb status....shame on lg
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
1. What is rpmb?
2. EU law says unlocking the bootloader, rooting an/or flashing custom software is no reason to waver warranty by the manufacturer unless he can prove that that was the cause of the defect.
Link: http://forum.xda-developers.com/showthread.php?t=1998801
Just received my Nexus 5X back from LG UK following an RMA (bootloop issue, motherboard replaced). I now have the "NO RPMB" issue too.
Just spoke to LG who were less than useless, stating that I'm "not allowed" to unlock as it would void the warranty... waiting for a call back from someone technical!
So frustrating...
Somebody with the same issue posted how he got root despite having his bootloader locked:
http://forum.xda-developers.com/showpost.php?p=68836703&postcount=7
So maybe at least we can get our root back!
Hi.
Im also having trouble with "no rpmb" after return from RMA (new mainboard).
Is there any possibility to make my Nexus great again?
Thanks!
KnieveI
KnieveI said:
Hi.
Im also having trouble with "no rpmb" after return from RMA (new mainboard).
Is there any possibility to make my Nexus great again?
Thanks!
KnieveI
Click to expand...
Click to collapse
Unfortunately, the only way I got this resolved was by escalating a complaint with LG and getting the device replaced by them.
darkness_sam said:
Unfortunately, the only way I got this resolved was by escalating a complaint with LG and getting the device replaced by them.
Click to expand...
Click to collapse
Ok , thanks.
In my country we are supposed to get it fixed at the local dealer , not by LG.
Had a hard time getting the mainboard changed the first time, as they claimed the reboot issue was software related and not under any kind of warranty.
Do you know why they do this? Are my phone broken in any way or is this only a problem regarding unlocking the bootloader?
Thanks
KnieveI
Hey there! I found a solution to get root access, here's my post on Reddit about it:
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
Hope this helps!
Linkoh said:
Afraid so. Just sent my N5x to LG Remember to specify that rpmb is causing problems. At least, that's what I did, hopefully it will get the work done. Let's see in 20ish days...[/QU
How did this end up for you ?
Click to expand...
Click to collapse
Received my refurb N5X, looks like it was refurbished/updated only a very short time ago- it was running 7.1.2 out of the sealed box and it had RPMB
negusp said:
Received my refurb N5X, looks like it was refurbished/updated only a very short time ago- it was running 7.1.2 out of the sealed box and it had RPMB
Click to expand...
Click to collapse
You've asked specifically for a device with RPMB ?
Is there any chance to get one with RPMB by saying DRM-content like Netflix are not playable on the phone ? I've seen on Reddit* some people have their phone replaced for this issue, but got a phone with bad battery.
* Can't post link because I'm a new user, so this is the link with spaces on domaine name : https:// www . reddit . com /r/nexus5x/comments/5lr7iz/rant_nonunlockable_bootloader_no_rpmb_after/dby1w9o/
I Purchased the Pixel XL Directly from the google store.
It arrived in the mail just a few days ago
it is unrooted
I have not unlocked the bootloader
I am the 1st owner who set it up.
it is totally unaltered except I installed some basic apps like anyone would when they get a new phone.
when I try to add a debit card on the Pixel XL in the Android Pay app, it gives me the error message:
"Android Pay Can't be Used. Google is unable to verify that your device or the software running on it is Android compatible"
This is extremely frustrating, and this is very dissapointing to me, that a brand new Pixel XL, out of the box, after being setup cannot perform such a basic task as adding a debit card, especially since the O.S. is unaltered. and the bootloader has never been tinkered with and it is not rooted.
I called Google customer service but all they can tell me is that the error message is not supposed to come up unless the device is rooted. However my Device is NOT rooted, so what gives? nobody knows anything.
I come here as my last resort..... Will anyone please help me troubleshoot this. I would be most appreciative if anyone could help me troubleshoot this. Please & Thanks.
slickromeo said:
I Purchased the Pixel XL Directly from the google store.
It arrived in the mail just a few days ago
it is unrooted
I have not unlocked the bootloader
I am the 1st owner who set it up.
it is totally unaltered except I installed some basic apps like anyone would when they get a new phone.
when I try to add a debit card on the Pixel XL in the Android Pay app, it gives me the error message:
"Android Pay Can't be Used. Google is unable to verify that your device or the software running on it is Android compatible"
This is extremely frustrating, and this is very dissapointing to me, that a brand new Pixel XL, out of the box, after being setup cannot perform such a basic task as adding a debit card, especially since the O.S. is unaltered. and the bootloader has never been tinkered with and it is not rooted.
I called Google customer service but all they can tell me is that the error message is not supposed to come up unless the device is rooted. However my Device is NOT rooted, so what gives? nobody knows anything.
I come here as my last resort..... Will anyone please help me troubleshoot this. I would be most appreciative if anyone could help me troubleshoot this. Please & Thanks.
Click to expand...
Click to collapse
I didn't have this problem when I was on stock as a Verizon purchased Pixel XL owner.
However,
I am having the same problem since I rooted and unlocked the phone. I am running Verizon Pixel XL, Elements Kernel Version .7, TWRP Alpha 1.
Any help for the OP and myself would be greatly appreciated.
slickromeo said:
I Purchased the Pixel XL Directly from the google store.
It arrived in the mail just a few days ago
it is unrooted
I have not unlocked the bootloader
I am the 1st owner who set it up.
it is totally unaltered except I installed some basic apps like anyone would when they get a new phone.
when I try to add a debit card on the Pixel XL in the Android Pay app, it gives me the error message:
"Android Pay Can't be Used. Google is unable to verify that your device or the software running on it is Android compatible"
This is extremely frustrating, and this is very dissapointing to me, that a brand new Pixel XL, out of the box, after being setup cannot perform such a basic task as adding a debit card, especially since the O.S. is unaltered. and the bootloader has never been tinkered with and it is not rooted.
I called Google customer service but all they can tell me is that the error message is not supposed to come up unless the device is rooted. However my Device is NOT rooted, so what gives? nobody knows anything.
I come here as my last resort..... Will anyone please help me troubleshoot this. I would be most appreciative if anyone could help me troubleshoot this. Please & Thanks.
Click to expand...
Click to collapse
Honestly, try a factory reset.
---------- Post added at 09:40 PM ---------- Previous post was at 09:38 PM ----------
fsuagentsmith said:
I didn't have this problem when I was on stock as a Verizon purchased Pixel XL owner.
However,
I am having the same problem since I rooted and unlocked the phone. I am running Verizon Pixel XL, Elements Kernel Version .7, TWRP Alpha 1.
Any help for the OP and myself would be greatly appreciated.
Click to expand...
Click to collapse
It's not going to work for you because SafetyNet sees you have an unlocked bootloader and non stock software.
Did u install all the Updates you got?
slickromeo said:
I Purchased the Pixel XL Directly from the google store.
It arrived in the mail just a few days ago
it is unrooted
I have not unlocked the bootloader
I am the 1st owner who set it up.
it is totally unaltered except I installed some basic apps like anyone would when they get a new phone.
when I try to add a debit card on the Pixel XL in the Android Pay app, it gives me the error message:
"Android Pay Can't be Used. Google is unable to verify that your device or the software running on it is Android compatible"
This is extremely frustrating, and this is very dissapointing to me, that a brand new Pixel XL, out of the box, after being setup cannot perform such a basic task as adding a debit card, especially since the O.S. is unaltered. and the bootloader has never been tinkered with and it is not rooted.
I called Google customer service but all they can tell me is that the error message is not supposed to come up unless the device is rooted. However my Device is NOT rooted, so what gives? nobody knows anything.
I come here as my last resort..... Will anyone please help me troubleshoot this. I would be most appreciative if anyone could help me troubleshoot this. Please & Thanks.
Click to expand...
Click to collapse
Edited duh missed bought from google part lol.
I would take screenshots showing bootloader is locked and tell google you have proof. Say if they dont want to fix this issue your going to file a chargeback with your credit card company that will change their tune right there.
I installed the OTA update for the November security updates (see attached image)
So you think the November security update messed it up??
I am seriously considering a factory data reset but I'd like to see if anyone has any other alternatives first that I might try
If you temp disable root, does it work then?
Anyone try Magisk, or is that not advisable with the pixel?
Thanks
fsuagentsmith said:
I didn't have this problem when I was on stock as a Verizon purchased Pixel XL owner.
However,
I am having the same problem since I rooted and unlocked the phone. I am running Verizon Pixel XL, Elements Kernel Version .7, TWRP Alpha 1.
Any help for the OP and myself would be greatly appreciated.
Click to expand...
Click to collapse
I spoke to Google Customer service again, i once again repeatedly told them that I have never been rooted, the bootloader had never been tinkered with......... They finally escalated me and asked me to submit a bug report. So i'm following the bug report steps now........ However I am still very frustrated and just want this to work........ If anyone else has any other troubleshooting steps for me, please share with me. I have multiple google accounts on my phone just in case that makes any difference, but I dont think it should make a difference.
death2all110 said:
Honestly, try a factory reset.
---------- Post added at 09:40 PM ---------- Previous post was at 09:38 PM ----------
It's not going to work for you because SafetyNet sees you have an unlocked bootloader and non stock software.
Click to expand...
Click to collapse
I figured that was the cause, looks like a work around will have to be developed.
slickromeo said:
I spoke to Google Customer service again, i once again repeatedly told them that I have never been rooted, the bootloader had never been tinkered with......... They finally escalated me and asked me to submit a bug report. So i'm following the bug report steps now........ However I am still very frustrated and just want this to work........ If anyone else has any other troubleshooting steps for me, please share with me. I have multiple google accounts on my phone just in case that makes any difference, but I dont think it should make a difference.
Click to expand...
Click to collapse
Did you try a factory reset?
I haven't tried a factory reset because I was hoping to resolve the issue without needing to factory reset.... I already submitted the bug report to Google, how long do you think it'll take them to respond with a solution for me? Or do you think a factory reset is worth it just to save the time and the wait....?
death2all110 said:
Did you try a factory reset?
Click to expand...
Click to collapse
I gave up the waiting game and Finally decided to do a Factory Data Reset to see if that would fix it....
It did not work. I get the exact same error message from a fresh factory reset.... the only apps that updated were the ones that always update after a factory reset.... This time i made sure to only add 1 of my google accounts when setting up the device.... After the stock apps all updated themselves, and play services updated itself. I still got the same error message......... on a freshly reset unmodified, unrooted, stock Pixel XL with a bootloader that has never been tinkered with !!!
I am majorly dissapointed !
I'm issuing a $20 Cash REWARD payable through Paypal or Google Wallet to whichever person helps me troubleshoot this to my satisfaction (I'll be satisfied when I get the app to work the way it's supposed to work i.e. I can add a debit card)
Does anyone have any further ideas of things that I should do ?????
or is my only remedy, to sit and wait for Google's Bug report to make the rounds and they get back to me :crying:
I'm continuing to research and I stumbled upon someone else with my issue https://www.reddit.com/r/Nexus6P/comments/41sl7x/android_pay_cannot_be_used_google_is_unable_to/
However, they changed the DPI, and I did not.... so it still doesn't explain why this is happening to me.
I installed one of the apps one of the commentators suggested to check compatibility with SafetyNet
so I installed this one https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
and when I installed it and run the app, the SafetyNet check app tells me an error (See Screenshot)
Which leads me to another question.......... How in the world is it possible for SafetyNet error for AndroidPay in a fully stock, unaltered, unmodified, unrooted (bootloader never unlocked) Pixel XL ?????
Have you booted into the bootloader menu just to check the bootloader isn't unlocked for some reason?
Sent from my Pixel XL using Tapatalk
DaveHTC200 said:
Have you booted into the bootloader menu just to check the bootloader isn't unlocked for some reason?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
When I shut down my phone
and press and hold PWR+VOLDOWN until it boots up
here is the text I see:
BL: 8996-012001-1608281716
Baseband: 8996-012511-1610221116
Product/Variant: marlin-US-PVT
Serial Number: HT6AE0201507
CPU: MSM8996SG-AB 0X10001
UFS: 128GB Toshiba
DRAM: 4096MB Hynix LPDDR4
Boot-slot: b
Console: DISABLED
Device is LOCKED
so, I assume that were it says "Device is LOCKED" that means the bootloader is locked, am I right?
I clicked Restart Bootloader to see if that would solve anything............
slickromeo said:
When I shut down my phone
and press and hold PWR+VOLDOWN until it boots up
here is the text I see:
BL: 8996-012001-1608281716
Baseband: 8996-012511-1610221116
Product/Variant: marlin-US-PVT
Serial Number: HT6AE0201507
CPU: MSM8996SG-AB 0X10001
UFS: 128GB Toshiba
DRAM: 4096MB Hynix LPDDR4
Boot-slot: b
Console: DISABLED
Device is LOCKED
so, I assume that were it says "Device is LOCKED" that means the bootloader is locked, am I right?
Click to expand...
Click to collapse
That's correct!! OK so it's not the bootloader that's causing it! Do you have a figure in the display settings under the "display size"? Or just small etc
Sent from my Pixel XL using Tapatalk
DaveHTC200 said:
That's correct!! OK so it's not the bootloader that's causing it! Do you have a figure in the display settings under the "display size"? Or just small etc
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
inside android settings, in the Display menu, i find a setting called "Display size" and it is set to 'Default'
I should mention I clicked "Restart Bootloader" previously when you told me to boot directly to the bootloader, just to see if that did anything. and I just wanted to confirm with you that It did not affect anything, I am still getting the same error.
slickromeo said:
I should mention I clicked "Restart Bootloader" previously when you told me to boot directly to the bootloader, just to see if that did anything. and I just wanted to confirm with you that It did not affect anything, I am still getting the same error.
Click to expand...
Click to collapse
That won't make a difference, you can't unlock it direct from the phone.
Have you tried to clear data and force close the android pay app?
Sent from my Pixel XL using Tapatalk