Hello, I got my pixel 3 XL two days ago and I flashed my device with the Google flash tool (web browser) and now I'm seeing widevine security level L3, therefore I can't watch Netflix video's on HD. Any way to fix this? I have never used any room or kernel stuff, locked the bootloader after flashing and disabled developer mode.
Only google can fix it, they have to either exchange device or switch mainboard. Has the same problem and only exchanging phone helped
Related
Hey guys,
Although I have lurked here for years, I never joined (part of me too scared to and part of me did not have anything helpful to say haha).
But I come for help to I think the place that has all answers android related.
We run a retail store - and a customer recently purchased a large order of Motorola Moto Gs (boost mobile) from us - long story short he was having an issue with one of the phones (upgrading the firmware) and returned it to us. Due to our partnership with our distributor instead of trying to return it to them - we put up back on sale and it was sold very quickly! (yey)
But here is the thing, the original owner did some modding to them (they were meant to be used for wifi only) - he unlocked the phone and I guess he "flashed it via FastBoot commands" based on our communication.
He told us that to get warranty back we will need to restore it.
After time researching we found "firmware restore lock and more 4.4.3" on these forums. With help of guides and youtube videos we were able to get things up and running - installed motorola drivers on the computer, and then ran "restore us_retail_xt1032..." everything seemed to be fine - but things to get bit weird after as well.
Although this eliminated the warning about the phone being unlocked, now it causes the phone to restart (randomly) - although it seems to be fixed now. In addition, the wifi switch does not seem to want to come on (grayed out). Also, when we try turning on bluetooth - it seems to be turning on and then turning off after a few seconds (is that normal for it to do that? - if it is please ignore it).
Our biggest thing is getting wifi fixed for our future customer. Now please, when explaining how to fix this - please try to be as simple as possible (as if you were explaining this to your non-technology progressive family member).
Thank you for all the help!! :good::fingers-crossed:
bump.
The Pixel 4a is the first phone in 10 years I didn't root because of the hardware check, but nevertheless Google Pay doesn't work for me on this phone. I had no single problem on my OnePlus 6 with Magisk. Is there a known bug? Does anybody know if usb debugging enabled is a problem for Google Pay? It's very frustrating to go back to the plastic card to pay.
Did you unlock bootloader? That'd cause it to fail the check even if not rooted.
fleischbanane said:
The Pixel 4a is the first phone in 10 years I didn't root because of the hardware check, but nevertheless Google Pay doesn't work for me on this phone. I had no single problem on my OnePlus 6 with Magisk. Is there a known bug? Does anybody know if usb debugging enabled is a problem for Google Pay? It's very frustrating to go back to the plastic card to pay.
Click to expand...
Click to collapse
USB debugging enabled kills some streaming services; wouldn't be surprised if Google Pay is sensitive to this
No, I didn't unlock the bootloader. I think this triggers the Google checks.
The only thing I did was enabling the developer options in order to give Tasker and some other apps special permissions.
I have a 4a on Android 10 with developer options enabled. I've used GPay once, and it worked ok for me.
woody1 said:
I have a 4a on Android 10 with developer options enabled. I've used GPay once, and it worked ok for me.
Click to expand...
Click to collapse
Thanks a lot, so I have to check my card. As mentioned before it worked last week on my OnePlus 6, so it's really strange.
Will try another card next time.
Not sure if it helps but sometimes I have run into an issue with using magnet mounts on the back of my phone case with pay terminals.
It's very frustrating. I tried three different cards and looked up the NFC location which is very different to my OnePlus 6. Under the fingerprint scanner instead of in the camera module. I really don't want to factory reset because I already set up all banking apps.
Thank you all for your help.
Edit: I found on Reddit, that there seems to be s a problem with Tasker, so I uninstalled it and also disabled the developer options. Will see if this works for me.
To be clear, is Google Pay telling you your device is ineligible / incompatible etc and refusing to let you set up a card? Or is the issue that it simply doesn't work at a payment terminal?
If doesn't work at the terminal. The app tells me everything is fine. I also tested the NFC chip with a German ID card. The phone can read all information stored in the ID.
Ok. That clarifies things a bit. If Google Pay isn't complaining about device eligibility then that's not what your issue is.
It's still not impossible that it's a hardware problem. Maybe it still works correctly for reading other unpowered devices like an ID card, but doesn't work for being read by payment terminals.
I'm not alone. :highfive:
The process in the video is the exact same I see every time I try it: https://9to5google.com/2020/10/26/some-pixel-5-owners-cant-make-nfc-payments-with-google-pay/
Luckily I didn't try a factory reset. :fingers-crossed:
Google Pay Not working
I have the exact same problem but this also happens on Oneplus Nord and Pixle 4a i have both devices and i get the same error on both devices .
Google pay works on
S10 Android 10
realmme 6 pro
Realme x50 5g
Fossil gen 5 Wear os Watch
pixel 3axl Android 11 beta
Will not work on
Pixel 4a Android 11
Oneplus Nord Android 10
have uninstalled the app and reinstalled
Cleared cache
Cleared storage
Cleared play services
removed account
removed card
re added card
re added account
reset device one plus nord only
none of the above methods worked for me
also i can connect my watch to the phone not working and the app on watch will work for making a contactless payment
the Nfc is working on my phone i have tested it with other NFC device and it works as intended
Called the bank No blocks on my card and it is setup correctly
Called google asked a million times the same question over and over and talking with support at the moment
so sorry i cant solve the issue but just thought id let you know what i have been doing
Also tried on different card machine get the same error all the time
Version 2.119.338332786 solved all my issues!
https://www.apkmirror.com/apk/google-inc/google-pay/google-pay-2-119-338332786-release/
Hi all, snagged an Xperia 1 out of electronics recycling at my job, charged it up and saw that it hadn't been reset and still had a pin lock on it. My dumb self decided to reset it via sony's software companion which updated the software (which nullified certain other bypass methods) and activated the frp. I want to be able to use this thing casually since its still a pretty good device, is there any way to get past it?
Quote100 said:
Hi all, snagged an Xperia 1 out of electronics recycling at my job, charged it up and saw that it hadn't been reset and still had a pin lock on it. My dumb self decided to reset it via sony's software companion which updated the software (which nullified certain other bypass methods) and activated the frp. I want to be able to use this thing casually since its still a pretty good device, is there any way to get past it?
Click to expand...
Click to collapse
Usually bypassing FRP is best shown in a video, because of the steps necessary to complete the process.
Search youtube for the model you have, most likely there are several videos that will work.
sd_shadow said:
Usually bypassing FRP is best shown in a video, because of the steps necessary to complete the process.
Search youtube for the model you have, most likely there are several videos that will work.
Click to expand...
Click to collapse
I've seen the hardreset video on it but whenever I get to the step of installing the apk files it just doesn't work at all. package installer just repeatedly stops
Hello,
I have one OP8T 11.0.8.12 i want to downgrade. Is that possible?
THe problem is i have a Google account lock on it and i cannot use it.. So i try on youtube how to do but in this version is missing th Oneplus Switch. SO i was thinking if we can downgrade to get this app.
You have a phone.
You wish to downgrade the phone to a previous version, but you are unable to access the phone because it is locked.
Locked using an account you do not have control over.
Unless you add a little more detail, what you are describing is the sort of situation one would be in if they were in possession of a stolen phone.
Is there any solution for the bypass of the Google account?
Hi all,
It's been a while since I've really done anything outside of business as usual with my Pixel phones. I haven't needed to root since my Nexus 6P days and every nexus previous to that. So for the most part, all my Pixels, I've been on stock OS and generally fine bc I got out of the custom ROM scene. Starting with my Pixel 5, I stopped unlocking the bootloader as well. Now on the 7 Pro and I am curious if there's a way to reflash the stock OS without data loss given all the progress that's been made in the community as well as the availability of the Pixel Repair Tool directly from Google. This latest March 2023 update has been a little funky and I've had some weird glitches going on. I don't want to go through the whole process of setting the phone up completely again given I have several apps for work that are annoying to set back up. Are there any options or am I stuck just waiting until April to see if the next update straightens it out?
I did search the forums before asking and honestly without reading through 100's of pages of posts, I couldn't find anything related to locked bootloader. I do have the Google unlocked phone from the Google store though so I have the ability to unlock, just chose not to at the beginning.
Thanks!
You should be able to just use Google's Android Flash Tool, and uncheck the wipe option (YMMV). Although if you have glitches a clean flash with the tool seems best.
jrg67 said:
Hi all,
It's been a while since I've really done anything outside of business as usual with my Pixel phones. I haven't needed to root since my Nexus 6P days and every nexus previous to that. So for the most part, all my Pixels, I've been on stock OS and generally fine bc I got out of the custom ROM scene. Starting with my Pixel 5, I stopped unlocking the bootloader as well. Now on the 7 Pro and I am curious if there's a way to reflash the stock OS without data loss given all the progress that's been made in the community as well as the availability of the Pixel Repair Tool directly from Google. This latest March 2023 update has been a little funky and I've had some weird glitches going on. I don't want to go through the whole process of setting the phone up completely again given I have several apps for work that are annoying to set back up. Are there any options or am I stuck just waiting until April to see if the next update straightens it out?
I did search the forums before asking and honestly without reading through 100's of pages of posts, I couldn't find anything related to locked bootloader. I do have the Google unlocked phone from the Google store though so I have the ability to unlock, just chose not to at the beginning.
Thanks!
Click to expand...
Click to collapse
If you reinstall the factory system image, all you will accomplish is adding a bit more wear to the flash memory it is stored on.
jrg67 said:
Hi all,
It's been a while since I've really done anything outside of business as usual with my Pixel phones. I haven't needed to root since my Nexus 6P days and every nexus previous to that. So for the most part, all my Pixels, I've been on stock OS and generally fine bc I got out of the custom ROM scene. Starting with my Pixel 5, I stopped unlocking the bootloader as well. Now on the 7 Pro and I am curious if there's a way to reflash the stock OS without data loss given all the progress that's been made in the community as well as the availability of the Pixel Repair Tool directly from Google. This latest March 2023 update has been a little funky and I've had some weird glitches going on. I don't want to go through the whole process of setting the phone up completely again given I have several apps for work that are annoying to set back up. Are there any options or am I stuck just waiting until April to see if the next update straightens it out?
I did search the forums before asking and honestly without reading through 100's of pages of posts, I couldn't find anything related to locked bootloader. I do have the Google unlocked phone from the Google store though so I have the ability to unlock, just chose not to at the beginning.
Thanks!
Click to expand...
Click to collapse
You can sideload the full OTA with a locked bootloader but I don't think it will help your situation.
I'm wondering if reinstalling the OS would help because it seems like something got corrupted but not enough to make a huge difference. Just some slow animations, having to gesture back 2 times in the Google messages app to exit (first swipe on conversation list just reloads that screen and second swipe actually exits), I don't know, just some other minor little annoyances that I can't fully remember at this point. Wasn't doing any of this prior to this update. I have to think it's not my data on the phone given the nature of these little glitches.
I think all those in this thread may be forgetting that in order to unlock the bootloader, one is required to wipe the device right after -- which goes against the title "without wipe"...
Even if OP was able to just flash the system partition or use Android Flash Tool, OP would need to have an unlocked bootloader. Although, what I know about Android Flash Tool is that, as long as "OEM unlocking" is ticked, it can automatically unlock the bootloader, but I can't confirm it requires the wipe (but since that's SOP, i imagine it's still required).
You don't need to be rooted to flash partitions, but the ability to flash means you'd have to wipe.
Sideloading OTA does not require OEM unlocking, unlocked bootloader, or root; for what it's worth -- dunno if OTA does anything like a Full Factory flash-all that dirty flashes over all (other than internalsd and app) partitions and therefore having a better chance at resetting/re-initializing what's needed to stabilize glitches or bugs....