Android pay - Xperia Z5 Premium Q&A, Help & Troubleshooting

I just got my phone and I try toinstall android pay it come out said not compatible with system?anyone know how to make it work?my phone unroot and bl still lock

no one know!?

[deleted]

That is bull****! Thanks for that information.waiting for google or someone can fix it,i don't want unlock bl yet

[deleted]

If someone does confirm with build.prop changes please post... Hopefully there's something that can be done that may not require unlock bl and root

The answer from google doesn't make sense as the Z5 and Z5C have had reports on reddit of people using Android Pay.

[deleted]

I would be willing to bet it has to do something with the screen. We know Sony is using the official 6.0 API for targeting 4K screens - maybe something in there messes with Android Pay and the upgrade to 6.0 will fix it? I doubt google is white listing devices. And we know custom dpi settings messup Android pay...

jonshipman said:
I would be willing to bet it has to do something with the screen. We know Sony is using the official 6.0 API for targeting 4K screens - maybe something in there messes with Android Pay and the upgrade to 6.0 will fix it? I doubt google is white listing devices. And we know custom dpi settings messup Android pay...
Click to expand...
Click to collapse
Grumble, my first attempt to reply here failed due to forum maintenance that lost the post.
Google is indeed whitelisting devices:
http://developer.android.com/training/safetynet/index.html
SNet will trigger on any rooted device, or when certain modifications to /system are detected (Xposed merely being installed on a device will trip SNet for example). Also, the device attestation data can be sent to a remote server for validation - all evidence indicates that Android Pay uses this as an Xposed module that patches local "failure" results does not fix Android Pay.
HOWEVER: Any device that has passed CTS (and more specifically ANY device that has been approved for Google Mobile Services, aka GMS, aka gapps licensing) should pass SafetyNet checks. SNet fails on the Z5P when it shouldn't. It has nothing to do with international devices as SNet is supposed to be usable by international app developers, it's not a US-only thing.
An unmodified (but bootloader unlocked) Z3 (D6603 specifically, so international unlocked version) does pass SNet checks. However Android Pay is stuch a steaming POS now that even on a device that passes SNet checks it's unreliable/inconvenient as hell. https://plus.google.com/+MattFlaming/posts/N9Gg9HKdmXu - My experiences mirror his except with even MORE pin-checks-on-tap with around a 50% failure rate even after putting in my PIN (AGAIN?) and re-tapping. Which is why I haven't been motivated at all to pitch in and help with the Xposed module that is trying to disable SafetyNet. (It right now only patches the local response, and as I said above, that fails with Pay. For it to work, it needs to fake attestation data, and doing that on a device that's triggering false positives on "modification" when running stock is... problematic.)

The Z5P doesn't pass CTS:
http://imgur.com/UsUjbEQ
Edit: I wrote Sony support (and made a stink on Reddit) but hopefully it's just a human error somewhere if the Z5/Z5C both pass.

My hope is that Marshmallow will clear this up and that's probably what Sony is waiting for as well. Other than that, this phone is [email protected] one of the best I have used in some time and I have had all the new Samsung garbage from this year as well as the Axon, OnePlus Two, etc. Sony makes great phones and it sucks that they market so poorly in the States. I mean if you have a PS4, why would you consider another phone? oh wait, that's right... because no carrier sales them...

jonshipman said:
The Z5P doesn't pass CTS:
http://imgur.com/UsUjbEQ
Edit: I wrote Sony support (and made a stink on Reddit) but hopefully it's just a human error somewhere if the Z5/Z5C both pass.
Click to expand...
Click to collapse
There's no way this would've been allowed to ship with GMS if CTS had never passed.
Also your screenshot doesn't prove that the device doesn't pass CTS, just that SafetyNet is tripping. To prove it doesn't pass CTS, you'd actually have to RUN the CTS suite.
It's a ****up on Google's part - there have been numerous cases of known-confirmed CTS-passing devices that fail SafetyNet checks.
Funny thing is, it's done for security reasons, but security update releases are frequently the most likely to fail SafetyNet. (See CyanogenOS Stagefright updates for the OnePlus One - As much as I dislike Cyngn, I know they don't ship non-CTS-certified releases on production CyanogenOS devices.)

http://talk.sonymobile.com/t5/Xperi...um-failing-SafetyNet-checks/m-p/1071057#M4913
My request was forwarded internally if that's any consolation.

Strange issue this, bad QA? or what?

|Night| said:
Strange issue this, bad QA? or what?
Click to expand...
Click to collapse
There are other cases of SafetyNet false-positiving... Such as all Stagefright security updates for the OnePlus One.
It's bad QA on Google's part.

mahst68 said:
If someone does confirm with build.prop changes please post... Hopefully there's something that can be done that may not require unlock bl and root
Click to expand...
Click to collapse
Could you please post your file "build.prop" ... I'd changed mine, and now I'm completed lost in a mess!!!

Related

What Is Lost by Staying with FireOS instead of Switching to CM?

There is an XDA thread entitled What Is Lost by Moving to CM from FireOS. This thread is the opposite: What is Lost by Staying with FireOS instead of Switching to CM?
Now, obviously, there is a difference in UI, which involves a substantial amount of individual preference. Some people like FireOS, others like CM.
But what concrete things are unavailable that a typical Android user may want?
For example, as of this posting, it appears that Amazon Underground will not (ironically) work on the Amazon Fire Phone.
Which common apps will still not work reliably with FireOS?
Anything else?
That depends. Do you mean to side load Google Play services and the Play Store?
I think FireOS (with root, Google Framework etc) you would keep all Amazon stuff.. on CM, you would lose everything related to the Amazon framework stuff. I personally just stay on root for now.
DePingus said:
That depends. Do you mean to side load Google Play services and the Play Store?
Click to expand...
Click to collapse
From everything I'm reading here on XDA, there does not seem to be a reliable way to get it work (and stay working)... or has someone found a way?
rockpaperlizard said:
From everything I'm reading here on XDA, there does not seem to be a reliable way to get it work (and stay working)... or has someone found a way?
Click to expand...
Click to collapse
I've had Google services running OK since I installed several months ago. I'm sticking with rooted stock with a third party launcher. IMO this combination works fine and I've pretty much zero annoyances with it.
The threads for the roms are pretty clear on the bugs: lots of camera issues, no mute, no nfc, Play service crashes. Some people are also reporting call drops and wifi issues on certain channels. If you read through the thread you'll notice a few people end up switching back to stock FireOS.
My phone updated to 4.6.4 when I got it so Google Play Services won't work (unless I downgrade to 4.6.3, but I don't want to start flashing stuff just yet). Right now I'm using a combination of F-Droid and apkmirror to sideload apps like FireFox and alternate launchers. I've gone through the pre-installed apps and disabled some of the Fire OS crap like Quick Start, AT&T app, Facebook and Twitter connect, Telemetry junk, etc. Some apps like Silk Browser will not stay disabled (because it does an update and I haven't figured out how to stop it from auto-updating).
Right now I'm REALLY missing Google Inbox.
DePingus said:
Some apps [...] will not stay disabled because it does an update
Click to expand...
Click to collapse
Disable the following apps:
• Amazon Device Client Platform
• DCP Platform Contracts
• System Update(s) - yes, there are 2 apps with that description, disable BOTH
This will stop all updates: app updates and OS related OTA updates.
ratbags said:
I've had Google services running OK since I installed several months ago. I'm sticking with rooted stock with a third party launcher. IMO this combination works fine and I've pretty much zero annoyances with it.
Click to expand...
Click to collapse
DePingus said:
,,,,My phone updated to 4.6.4 when I got it so Google Play Services won't work (unless I downgrade to 4.6.3, but I don't want to start flashing stuff just yet). Right now I'm using a combination of F-Droid and apkmirror to sideload apps like FireFox and alternate launchers.
Click to expand...
Click to collapse
This is the part that confuses me... some people say Google Play store is working fine on FireOS and others say it won't work. Can you explain why the different reports? Does it all come down to downgrading to FireOS 4.6.3 and sticking with that version? If so, isn't Stagefright an issue?
rockpaperlizard said:
Can you explain why the different reports? Does it all come down to downgrading to FireOS 4.6.3 and sticking with that version? If so, isn't Stagefright an issue?
Click to expand...
Click to collapse
Bottom line: Google Play Store & services...
• ...work well on the "GSM unlocked" OS versions - 35.4.6.1 (461013820) and 35.4.6.3 (463001620).
• ...doomed on the "AT&T" OS versions - 32.4.6.1 (461013320) and 32.4.6.4 (464000420)
• GER version of the OS was problematic as well, tested it myself in the beginning (just as another example)
Using the latest US "GSM unlocked" 4.6.3 (463001620) is the best option, all known Stagefright vulnerabilities are patched in this one*.
And yes, all OS versions can be installed on all devices, netlock is ofc. not affected, multi language support is available.
Using the AT&T verson is a lost cause, because you have to use a work around, e.g. blocking updates of the Play services or uninstalling Play services updates everytime they update.
It's a dead end, because (some) apps will demand a newer version of the Play services, so all the effort is not worth it.
*A little bit of history: Stagefright Patch Round 1: 4.6.3 (463001420) / Stagefright Patch Round 2: 4.6.3 (463001620)
rockpaperlizard said:
This is the part that confuses me... some people say Google Play store is working fine on FireOS and others say it won't work. Can you explain why the different reports? Does it all come down to downgrading to FireOS 4.6.3 and sticking with that version? If so, isn't Stagefright an issue?
Click to expand...
Click to collapse
I blocked updates after 461 as I anticipated problems. Stage fright isn't much of an issue because I use a third party SMS app and block auto retrieval of MMS messages. Then again, I never send or receive MMS.
Bingo Bronson said:
Bottom line: Google Play Store & services...
• ...work well on the "GSM unlocked" OS versions - 35.4.6.1 (461013820) and 35.4.6.3 (463001620).
• ...doomed on the "AT&T" OS versions - 32.4.6.1 (461013320) and 32.4.6.4 (464000420)
• GER version of the OS was problematic as well, tested it myself in the beginning (just as another example)
Using the latest US "GSM unlocked" 4.6.3 (463001620) is the best option, all known Stagefright vulnerabilities are patched in this one*.
And yes, all OS versions can be installed on all devices, netlock is ofc. not affected, multi language support is available.
Using the AT&T verson is a lost cause, because you have to use a work around, e.g. blocking updates of the Play services or uninstalling Play services updates everytime they update.
It's a dead end, because (some) apps will demand a newer version of the Play services, so all the effort is not worth it.
*A little bit of history: Stagefright Patch Round 1: 4.6.3 (463001420) / Stagefright Patch Round 2: 4.6.3 (463001620)
Click to expand...
Click to collapse
WOW! That is great info! THANK YOU! :good: That should be part of a FAQ (or a FAQ on its own).
Questions:
If you buy an AT&T Fire Phone, and it includes the unlock code, will you still have the problems since it still is the AT&T ROM?
When buying a phone, besides asking the seller to turn it on and tell you the version of the ROM (which they may not do if it is new in the box), how do you know if it is a GSM unlocked version or the AT&T version?
Does the GSM unlocked version of FireOS only auto-update to new GSM unlocked versions, or has Amazon merged everything into one FireOS version at this point?
rockpaperlizard said:
If you buy an AT&T Fire Phone, and it includes the unlock code, will you still have the problems since it still is the AT&T ROM?
Click to expand...
Click to collapse
Yes, the unlock only changes some information stored in a chip, eeprom maybe, who knows...
Problems are caused by the ROM, so the best thing to do is:
Receive new phone, boot it up, don't register anything and don't connect to WiFi, check the installed version, if AT&T:
Power off the device, sideload the 4.6.3 image via ADB recovery (there's a link in my sig. "Fire Phone stock recovery: factory images")
When buying a phone, besides asking the seller to turn it on and tell you the version of the ROM (which they may not do if it is new in the box), how do you know if it is a GSM unlocked version or the AT&T version?
Click to expand...
Click to collapse
Fortunately, the seller doesn't need to boot it up, on the box is a sticker with basic info like: storage size, OS version, IMEI, UPC... so as long as the seller is honest, it should be clear which version is actually on the device.
Does the GSM unlocked version of FireOS only auto-update to new GSM unlocked versions, or has Amazon merged everything into one FireOS version at this point?
Click to expand...
Click to collapse
Each version is independent and it will stay that way, wouldn't make much sense for them to change it and I guess there are some agreements they made with AT&T which have to be met...
Bingo Bronson said:
...
Fortunately, the seller doesn't need to boot it up, on the box is a sticker with basic info like: storage size, OS version, IMEI, UPC... so as long as the seller is honest, it should be clear which version is actually on the device.
...
Click to expand...
Click to collapse
Thanks for all the super helpful info! :good:
Do the outside of the boxes indicate sufficient version info to tell if it is AT&T or not?
rockpaperlizard said:
Do the outside of the boxes indicate sufficient version info to tell if it is AT&T or not?
Click to expand...
Click to collapse
Well, it does read the short version number, like "OS V 3.6.0" but the seller knows ofc. that he bought (e.g.) a pallet full of AT&T devices because it has to be declared on the paperwork.
edit: A 2nd sticker on the other side of the box states: "the device can only be used with a SIM card from T-Mobile" (dark grey font on black background, neat ^^)
I guess they will have a sticker like this in the U.S. for the AT&T variants as well, so that's another good indicator to know "what's in the f***ing box !?!"
The two biggest sellers (regarding Fire Phone) on Ebay (US site of ebay, fer sure) sell the remaining "AT&T UNLOCKED (+ PRIME)".
Bingo Bronson said:
• ...work well on the "GSM unlocked" OS versions - 35.4.6.1 (461013820) and 35.4.6.3 (463001620).
Click to expand...
Click to collapse
Forgive me if I missed in this thread... Which versions of the Play Service and Play Store are you referring to?
FWIW, I am running 4.6.4 with Player Services 7.8.99 and Play Store removed. I get "XXX relies on on Google Play services which is not supported on your device" complaints from some apps, but most things continue to work anyway. That is most non-Google apss - Hangouts and YouTube are problematic.
jwernerny said:
Which versions of the Play Services and Play Store are you referring to?
Click to expand...
Click to collapse
No version in particular. (All versions I were referring to are Fire OS version numbers)
On the GSM unlocked version, I never had trouble with any version of Play Store & Services, so I just used the latest at that time (updates were also without issues).
I am running 4.6.4 with Play Services 7.8.99 and Play Store removed [...] complaints from some apps, but most things continue to work anyway [...] Hangouts and YouTube are problematic.
Click to expand...
Click to collapse
Well, as long as it's working for you and all your favorite apps keep working properly, you don't need to switch. Livin' on the edge!
Speaking of YouTube, if you like to download videos / audio from there:
SnapTube (Received more updates lately, still beta, supports multiple media sites, can download audio only on YT as well)
NewPipe (Very lightweight, watch or download videos, just released this week, still new & buggy = be gentle ^^)
So If you have an ATT phone there is no way to get the software off the unlocked version on it?
I have the ATT and if I need to I will buy an "factory unlocked for learning rooting and installing mods as It has been a couple of three years since I have done this.
I hope the fire phone mod project succeeds and I think it will be great when the bugs get worked out. I enjoy following this but I bought the unlocked ATT because I needed a new smart phone and for $115 with a year of prime...
Ask me about my warranty service from Amazon!!!!!!!! Horror story but thats another forum!!
RandB fan said:
So If you have an ATT phone there is no way to get the software off the unlocked version on it?
[...] but I bought the unlocked ATT because I needed a new smart phone and for $115 with a year of prime...
Click to expand...
Click to collapse
Don't worry, there is no "AT&T phone" only an AT&T OS variant.
All Fire Phones are the same, regarding hardware, netlock is no biggie since you already received an unlock code.
You can install the 4.6.3 version on your device, since it is the preferred version when it comes to Google Play Store & services.
Maybe you could explain that process for all of us ATTers? links?
So I don't screw things up...
Hey guys... could you clarify things up a bit so I do things correctly. My case is this:
I've ordered a brand new in box Fire Phone off Ebay that should be arriving in a couple of days, and I know for sure (as it's clearly stated by the seller) that this is the AT&T version. According to the seller they don't open the box, they just provide you the unlock code and you do the whole unlock and activation yourself.
The main reason I ordered this phone is to give it to my kid as his first smartphone but at the same time enjoy the year of Amazon Prime service, since I've been a Prime subscriber for a good 3 years now and I'm up for renewal in November. So essentially my goal is to renew my Prime subscription and give my son a decent Android phone for $35 at the same time.
Based on what I've read I'd be planning initially to keep FireOS to make it stable for him. He also has a Nexus 7 Tablet where he does most of his gaming and school stuff, so I think we can live with FireOS to keep it stable as a phone but still I'd like to install Google Playstore to have access to Google's apps, so I'd guess I'll have to replace the AT&T Rom the Unlocked-GSM FireOS ROM as described by Bingo.
What should be the recommended path for my case?... I don't want to compromise the initial activation so I get the Prime-year with no issues, after that I could play with all the Roms, roots and sideloads that are necessary (and have fun in the process). My concern is that I'd suppose that once I go through the initial activation process for the phone with my Amazon account most probably it will try to update to the latest OS version right?... since these is just a Rom I'd suppose that there should not be issues to let it update and then do the whole safetrap/rooting and sideload the GSM Unlocked Rom?... or should I take a different approach.?
Thanks, George

Gooligan ?

Hey guys, what's your take on "Gooligan" vulnerability?
I, myself find it a bit strange Google hasn't took it public, and gave us a formal statement.
Also, being rooted, I have some doubts about Android's vulnerability and security
Scutariu said:
Hey guys, what's your take on "Gooligan" vulnerability?
I, myself find it a bit strange Google hasn't took it public, and gave us a formal statement.
Also, being rooted, I have some doubts about Android's vulnerability and security
Click to expand...
Click to collapse
Apparently not applicable for Android 6, 7 ...
Sent from quite brutal hTc 10 ..
jauhien said:
Apparently not applicable for Android 6, 7 ...
Sent from quite brutal hTc 10 ..
Click to expand...
Click to collapse
Ooh, haven't seen anything on the web about this one.
Any sources?
Scutariu said:
Ooh, haven't seen anything on the web about this one.
Any sources?
Click to expand...
Click to collapse
Once installed, it uses a process known as rooting to gain highly privileged system access to devices running version 4 (Ice Cream Sandwich, Jelly Bean, and KitKat) and version 5 (Lollipop) of Google's Android operating system.
Click to expand...
Click to collapse
From here: http://arstechnica.com/security/2016/11/1-million-android-accounts-compromised-by-android-malware-called-gooligan/
In my opinion, this just goes to show how a unified Android update system is greatly needed. The relatively few of us that manage to stay up to date are protected from the majority of Android exploits but that still leaves 74% of android users vulnerable.
The article did note that Google said there was no evidence that data was accessed from compromised accounts. They are also using their 'Verify Apps' function to check for infected APK's prior to installation. I think Gooligan itself isn't much of a problem aside from highlighting the issue of keeping Android up to date on devices.
The user has to:
- Enable install from unknown sources
- Install questionable apps from third-party sources
The user who does this knows the risks. Their phone told them so.

Security-wise, what are my options?

Hey,
I'm 100% new to doing any sort of custom stuff with my Android devices, so please forgive my dumb questions.
I've known for a while now that my Nexus 7 was vulnerable since it stopped receiving security updates in August 2016, but I wasn't terribly concerned at the time since I use it so casually. With this recent WPA2 news, though, I'm kinda anxious.
Is there any way at all to make my device secure? Google doesn't give a **** so I know there's no chance in hell it gets an official patch, so I assume I have to go with a custom ROM, but I have no idea where to start.
If I went with a custom version, will I still be able to use the apps I own? Will I still be able to use stuff like Chrome and Drive as well? Also, if I'm using a custom ROM, is there actually any guarantee that it is actually secure? How do I ensure it receives security updates in an unofficial setting?
tl;dr version: Just hoping for a way to use my Android device mostly in the same way I already do, but with actual security updates going forward, since Google are a-holes.
Be aware that some apps will refuse to run on a rooted device. You also won't be able to use Google Pay.
You can mitigate the security issue somewhat by using a VPN service; all your communications will be encrypted, so a MITM attack should fail unless they can also decrypt your communications stream.
I use PrivateInternetAccess myself; one of their app's features is the ability to bypass VPN for selected apps, so for example I can run Pokemon Go (which won't run on VPN) and avoid running video streams through VPN (I don't really care if they can see me watching Hill Street Blues on Hulu and I'd rather avoid the performance hit). YMMV and I'd recommend doing your own research, and VPN isn't a magic bullet. But it makes the WPA2 problem less urgent without a lot of work and without having to root your device.
Mind you, I'm saying all this while perusing the forums to discover what custom ROMs are available for my Nexus 7, as I'm considering rooting it.
---------- Post added at 07:49 PM ---------- Previous post was at 07:36 PM ----------
To address a different part of your question, aside from the "some things won't run rooted" issue I already mentioned, the rest of your apps should run fine. You'll want to install some version of Open GApps to get Google functionality. That's probably covered in the instructions for the custom ROM.
Two favorites are LineageOS, which has a lot of neat features added, and AOSP, which is the bare Google Android experience with neither bells nor whistles.
Keep in mind that if you don't like what you get, you can always change. So if LineageOS isn't for you, you can try AOSP, or something else if you find it. I'm assuming that somebody has the base ROM available; it should even be possible to put the stock ROM back and unroot the device. Know that I'm speaking from inexperience, sorta... I haven't done this with a Nexus yet, but I've done it lots of times with a Galaxy S4. So I'm not really an authority but I figured I could get you started in the right direction, at least. Just remember to back up everything on your device before you start.
Really, really be sure you back up before you start.
I'm having this conundrum as well. I currently use MM on my Nexus 7 2013 due to better idle time and more reliable WiFi. It seems like there is no way to fix this vulnerability without moving to Nougat.
Lineage OS is a good rom to start with. It receives security updates OTA, and it doesn't come with root binaries, so most apps should work.
anzianzi said:
Lineage OS is a good rom to start with. It receives security updates OTA, and it doesn't come with root binaries, so most apps should work.
Click to expand...
Click to collapse
+1

Viper4Android without root possible?

I was able to eq/tune the bluetooth audio in my car perfectly using V4A on my last bunch of LG phones that were rooted. I just bought the Pixel 2 XL from Verizon knowing that the bootloader had been locked (WTF Google, why do you allow carriers to do that? - isn't the whole idea of Google phones that they are unadulterated Android?) because it appeared to be the best phone for my other music endeavors (Audio Evolution Mobile multi-track recording).
I saw some mention that it will run if SELinux is in permissive mode. Is there a way to do that manually after each reboot and then enable V4A?
Thanks
dsteinschneider said:
I was able to eq/tune the bluetooth audio in my car perfectly using V4A on my last bunch of LG phones that were rooted. I just bought the Pixel 2 XL from Verizon knowing that the bootloader had been locked (WTF Google, why do you allow carriers to do that? - isn't the whole idea of Google phones that they are unadulterated Android?) because it appeared to be the best phone for my other music endeavors (Audio Evolution Mobile multi-track recording).
I saw some mention that it will run if SELinux is in permissive mode. Is there a way to do that manually after each reboot and then enable V4A?
Thanks
Click to expand...
Click to collapse
The short answer is no. I know you can change selinux with adb, however, V4A needs root to function properly. I definitely agree with you though on the Verizon/Google thing. I'm a Big Red user as well, but haven't purchased a device directly from them in 4 years for the reason you stated. And, unfortunately, it'll likely only get worse! ?
dsteinschneider said:
WTF Google, why do you allow carriers to do that [lock the bootloader]? - isn't the whole idea of Google phones that they are unadulterated Android?
Click to expand...
Click to collapse
Just to touch on this, the bootloader has nothing to do with Android itself. The P2XL is still "unadulterated" Android. The Verizon units have the locked bootloader because that was the price Google had to pay in order to get the phone in the Verizon store. AT&T wouldn't have been much better, and the other two carriers aren't large enough to think about.
This "unadulterated" complaint isn't new. The Nexus 6 encountered this in 2014, because models sold in the AT&T store were carrier locked, though the bootloader was unlockable.
Badger50 said:
The short answer is no. I know you can change selinux with adb, however, V4A needs root to function properly. I definitely agree with you though on the Verizon/Google thing. I'm a Big Red user as well, but haven't purchased a device directly from them in 4 years for the reason you stated. And, unfortunately, it'll likely only get worse!
Click to expand...
Click to collapse
Thanks, good tip on buying from Google next time. I bought this one from Verizon because they knocked $300 off the price and there are 3 other Android users in the family I can pass this one to.
The Pixel 2 XL sound over bluetooth to my car's Pioneer DEH-80PRS is quite good. The highs are clear without harshness, the frequency response is flat. I'm also getting plenty of gain using the supplied dongle with Shure e5c IEM's.
Strephon Alkhalikoi said:
Just to touch on this, the bootloader has nothing to do with Android itself. The P2XL is still "unadulterated" Android. The Verizon units have the locked bootloader because that was the price Google had to pay in order to get the phone in the Verizon store. AT&T wouldn't have been much better, and the other two carriers aren't large enough to think about.
This "unadulterated" complaint isn't new. The Nexus 6 encountered this in 2014, because models sold in the AT&T store were carrier locked, though the bootloader was unlockable.
Click to expand...
Click to collapse
As a long suffering Samsung and LG bloatware eradicator I'm grateful that I was able to eliminate the 3 or 4 VZW additions in a few minutes. No NFL running in the background - reminds me of the Simpsons episode where Bart claims he is being controlled by MLB until their satellite crashes in the backyard
I use Nova Launcher (although the launcher that came with the Pixel 2 XL seemed OK) so I'm able to tweak the behavior mostly how I want it. I originally started flashing ROMs to get around VZW restrictions placed on the phones. Especially for GPS when I was on Windows phones.
ViPER4Android
You can run Viper4Android without root. However, you need a rooted device to install it.
To install Viper4Android, follow these steps;
1. Download Busybox on your android device.
2. After downloading install Busybox. It will ask permission for root, simply grant the permission. Busybox will be installed on your device.
3. Now, Download ViPER4Android and then (more)
dsteinschneider said:
As a long suffering Samsung and LG bloatware eradicator I'm grateful that I was able to eliminate the 3 or 4 VZW additions in a few minutes....
I use Nova Launcher (although the launcher that came with the Pixel 2 XL seemed OK) so I'm able to tweak the behavior mostly how I want it....
Click to expand...
Click to collapse
Having an unlocked model I genuinely forget that Verizon models install a few apps. The good news is that, as you found out, they're removable.
The P2XL is the first device I own to not have a custom ROM on it, though it is rooted. I, like virtually everyone else who has been here for years, would root Android to add features that were missing. Android 8.1 was the first version of Android to have sufficient features to make a custom ROM unnecessary. There are things I would like to see in a stock ROM such as a reboot menu with the option to reboot into recovery or the bootloader, but those are minor things which apps can compensate for. Like you, I use Nova, not just for its customization features but also because I disable the stock launcher in order to remove the horizontal recents screen.
AbdulMajid11 said:
You can run Viper4Android without root. However, you need a rooted device to install it.
To install Viper4Android, follow these steps;
1. Download Busybox on your android device.
2. After downloading install Busybox. It will ask permission for root, simply grant the permission. Busybox will be installed on your device.
3. Now, Download ViPER4Android and then (more)
Click to expand...
Click to collapse
Hi Abdul,
I'm looking for clarification. Do the above instructions mean that just by installing Busybox on my VZW Pixel 2 XL which I believe to be "unrootable" that it will temporarily be rooted?
Thanks
Strephon Alkhalikoi said:
Having an unlocked model I genuinely forget that Verizon models install a few apps. The good news is that, as you found out, they're removable.
The P2XL is the first device I own to not have a custom ROM on it, though it is rooted. I, like virtually everyone else who has been here for years, would root Android to add features that were missing. Android 8.1 was the first version of Android to have sufficient features to make a custom ROM unnecessary. There are things I would like to see in a stock ROM such as a reboot menu with the option to reboot into recovery or the bootloader, but those are minor things which apps can compensate for. Like you, I use Nova, not just for its customization features but also because I disable the stock launcher in order to remove the horizontal recents screen.
Click to expand...
Click to collapse
Agreed. It would be great to be able to root my VZW Pixel 2 XL for things like being able to access the Google Play Music playlist database directly (to backup) but other than small things like that I'm very satisfied with Android 8.1.
bunu dene harika bir uygulama https://play.google.com/store/apps/details?id=com.jazibkhan.equalizer
bunu da dene https://play.google.com/store/apps/details?id=com.pittvandewitt.wavelet
Mod Edit: English Translation Below
try this great app https://play.google.com/store/apps/details?id=com.jazibkhan.equalizer
try this too https://play.google.com/store/apps/details?id=com.pittvandewitt.wavelet

[SHARE] OCEAN_PPOS29.114_134_7_4_cid50 Latest Stock Build for XT-1955-5 Retus

They have released another stock rom update but it is nowhere to be found on net so i downloaded it and will share its not as large as the previous when zipped it is labeled as OCEAN_PPOS29.114_134_7_4_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip and is not on the lolinet files list yet. I had to unroot and wipe and relock bootloader to take the ota, going to reunlock and root etc but figured id share since if you have the file you should be able to update thru magisk without all the trouble i had to go through :/ anywhay here is a link for those that want to not install thru magisk without having to unroot etc. Of course you need to click uninstall recovery mode before you install the ota also have auto ota disabled in your dev settings first or you can wipe the device to stock and install the files manually in the zip file up to you make sure your on A when you install, I had to do it twice but got it working also if you use viper and camera is crashing setenforce 0 in adb shell will fix that for you now viper and camera works if this helps you i am a broke son of a gun disabled veteran and going thru hell with usps right now any donations are helpful and will go to help feed 3 kids. It is not necessary and I Never ask for donations but it really is that bad I am going to have to go thru a legal battle for fraud against the USPS etc. They have been stealing funds set aside for disabled veterans and I caught them and they will stop at nothing to get me outta there but regardless i'm whistle blowing on their fraudulent activities in hopes someone actually serves them the justice they deserve they have made up a lie that i threathened to kill them which is complete horse crap but it is what it is they have ZERO evidence they tried last year when i discovered other crimes and they just keep piling up and they will hopefully if justice is served be arrested and spend time in federal penitentiary and I will be filing lawsuits etc. Thru the VA but until then I am broke no money not sure how im gonna feed my kids etc. Freaking out but I am ex infantry and I always defeat my enemies and they will be defeated with hard evidence and facts I never made violent threats as they claim its the only thing they can say to get me out of the office immediately because inspection service is crooked as hell too and half of em are on the cartels payroll to let dope slide right thru the postal system. Its so much worse than you could ever imagine how deep down the rabbit hole this whole thing goes anyway this is not the place for it all. I am just trying to help out like minded folks who like to mess with their devices and get what they can out of them. The latest firmware is available here Only use if you have XT1955-5 RETUS otherwise you could have issues that is a moto g7 power retail USA.
Google Drive link https://drive.google.com/file/d/1iGrvr7uj7MtuPAak-PoWKu756Ojd425l/view?usp=sharing
BTC: 3ERLgRUQtStPjKeieJpDs2p8nvjbr6nU1E
BCH: qrmh7vdhqt5yqw47zafw6c9fgnezr5gk854v88a7wh
ETH: 0x997e251635Fd289F1107BB817e8814285Bf0ec0f
Paypal Donation send to [email protected]
toxinburn said:
They have released another stock rom update but it is nowhere to be found on net so i downloaded it and will share its not as large as the previous when zipped it is labeled as OCEAN_PPOS29.114_134_7_4_cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml.zip and is not on the lolinet files list yet. I had to unroot and wipe and relock bootloader to take the ota, going to reunlock and root etc but figured id share since if you have the file you should be able to update thru magisk without all the trouble i had to go through :/ anywhay here is a link for those that want to not install thru magisk without having to unroot etc. Of course you need to click uninstall recovery mode before you install the ota also have auto ota disabled in your dev settings first or you can wipe the device to stock and install the files manually in the zip file up to you make sure your on A when you install, I had to do it twice but got it working also if you use viper and camera is crashing setenforce 0 in adb shell will fix that for you now viper and camera works if this helps you i am a broke son of a gun disabled veteran and going thru hell with usps right now any donations are helpful and will go to help feed 3 kids. It is not necessary and I Never ask for donations but it really is that bad I am going to have to go thru a legal battle for fraud against the USPS etc. They have been stealing funds set aside for disabled veterans and I caught them and they will stop at nothing to get me outta there but regardless i'm whistle blowing on their fraudulent activities in hopes someone actually serves them the justice they deserve they have made up a lie that i threathened to kill them which is complete horse crap but it is what it is they have ZERO evidence they tried last year when i discovered other crimes and they just keep piling up and they will hopefully if justice is served be arrested and spend time in federal penitentiary and I will be filing lawsuits etc. Thru the VA but until then I am broke no money not sure how im gonna feed my kids etc. Freaking out but I am ex infantry and I always defeat my enemies and they will be defeated with hard evidence and facts I never made violent threats as they claim its the only thing they can say to get me out of the office immediately because inspection service is crooked as hell too and half of em are on the cartels payroll to let dope slide right thru the postal system. Its so much worse than you could ever imagine how deep down the rabbit hole this whole thing goes anyway this is not the place for it all. I am just trying to help out like minded folks who like to mess with their devices and get what they can out of them. The latest firmware is available here Only use if you have XT1955-5 RETUS otherwise you could have issues that is a moto g7 power retail USA.
Google Drive link https://drive.google.com/file/d/1iGrvr7uj7MtuPAak-PoWKu756Ojd425l/view?usp=sharing
BTC: 3ERLgRUQtStPjKeieJpDs2p8nvjbr6nU1E
BCH: qrmh7vdhqt5yqw47zafw6c9fgnezr5gk854v88a7wh
ETH: 0x997e251635Fd289F1107BB817e8814285Bf0ec0f
Paypal Donation send to [email protected]
Click to expand...
Click to collapse
I forgot to mention if you have viper 4 Android and camera is not functional setenforce 0 and camera will work i have tried it over and over and it does work although i cannot tell that v4a is really processing i may retry installing it through magisk instead and seeing if that solves it but who knows their are various sound fixes for it to make it work with youtube and spotify etc. but it interferes with the camera driver i have discovered that setenforce to 0 will make camera work again. Reboot you will need to redo the command or use a init.d script or app that swaps it off for you.
toxinburn said:
I forgot to mention if you have viper 4 Android and camera is not functional setenforce 0 and camera will work i have tried it over and over and it does work although i cannot tell that v4a is really processing i may retry installing it through magisk instead and seeing if that solves it but who knows their are various sound fixes for it to make it work with youtube and spotify etc. but it interferes with the camera driver i have discovered that setenforce to 0 will make camera work again. Reboot you will need to redo the command or use a init.d script or app that swaps it off for you.
Click to expand...
Click to collapse
Will this work on ocean power phone Moto g7? It's my first a b device and my daily driver
roadkill42 said:
Will this work on ocean power phone Moto g7? It's my first a b device and my daily driver
Click to expand...
Click to collapse
You have to check if your phone is a XT1955-5, as there are other variants like XT1955-2 in which this will probably not be perfect and might cause problems.
The RETUS part is not mandatory, as this file is [ cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC ] which should work for any phone, but be careful if you have one of the subsidized US versions that don't allow bootloader unlocking.
As always, you have to do your own research, measure the risks, know the basics and don't blame anyone here of your dead phone, burnt house or lost job because of alarms not ringing.
DanAlucard said:
You have to check if your phone is a XT1955-5, as there are other variants like XT1955-2 in which this will probably not be perfect and might cause problems.
The RETUS part is not mandatory, as this file is [ cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC ] which should work for any phone, but be careful if you have one of the subsidized US versions that don't allow bootloader unlocking.
As always, you have to do your own research, measure the risks, know the basics and don't blame anyone here of your dead phone, burnt house or lost job because of alarms not ringing.
Click to expand...
Click to collapse
Thanks it from cusumer celliuar and from what I read it can be bootloader unlocked how do I tell what cid I am .Thanks in advance
---------- Post added at 08:13 AM ---------- Previous post was at 07:29 AM ----------
[/COLOR]
DanAlucard said:
You have to check if your phone is a XT1955-5, as there are other variants like XT1955-2 in which this will probably not be perfect and might cause problems.
The RETUS part is not mandatory, as this file is [ cid50_subsidy_DEFAULT_regulatory_DEFAULT_CFC ] which should work for any phone, but be careful if you have one of the subsidized US versions that don't allow bootloader unlocking.
As always, you have to do your own research, measure the risks, know the basics and don't blame anyone here of your dead phone, burnt house or lost job because of alarms not ringing.
Click to expand...
Click to collapse
+1! Many people have bricked that didn't read and understand on these G7 Power device(s). (I'm one who did ??) I have a metro 1955-5 and I'll be staying on the RETUS_Ocean_PPOS29.114_7_1_cid50 firmware until someone either creates a new blank flash or one is brought to us that works because I've read more than one report of bricks staying bricks because the latest firmware isn't compatible with the current blank flash we have available. I haven't seen any changes in development stating we have to be on a more recent firmware in order for a rom to work and we have a few stable roms available that work as good as stock does on my device. To me the people to watch close are Electimon, Rondeau79 , Bernie nix , SyberHexen , Geofferey , whoda711 , and Dark98 . If they make a post about something, they know what they're talking about and I always trust what they say because they've already all contributed to G7 Power device(s) in some way or another and to do that you have to know what you're doing otherwise it would be impossible. Reading their threads and understanding what they have done is extremely helpful. Anything I don't understand I Google search and make sure that I do. Searching here on xda and Google searching one can get a good grasp on understanding things and not have to worry anymore about the whole bricking your phone deal. But to me there's no reason to update because everything is still compatible that we have in our forums and the devs all make security patches when they drop a new build of a rom. Also just because you are a few months out of date on a security patch doesn't mean you're going to get hacked and you are no longer safe. Maybe a year or more but a few months and we're all still in the okay zone as far as that goes. From what I've read it's firmware that's older than most of us will still have this device that becomes extremely vulnerable to viruses and whatnot.. Many people freak out on the whole security patch being out of date and the people who sell us the phones use that as a way to push you to buy a new device. Unless there's a new warning that's legit about something I believe security patch wise I'm good even if I am 6-7 months behind. However when I know my phone isn't current on my "about phone" information my OCD kicks in and I feel like I MUST be updated to the bleeding edge release of whatever it is. Hahahahaha! ?? I also use canary magisk always. ?
I hope everyone is staying safe during this whole Corona virus situation. I'm staying my butt at home and eating my food slow and cutting back so I don't have to go around others as much. Anything helps because it is person to person transmitted. It's me and my two cats which are my favorite two other living things to be around so I'm good. ?? Stay safe out there.
Sent from my Mi MIX 2 using XDA Labs
Actually I wish i could find the command it did work for me, but I couldnt tell you for the life of me what i typed in i was inebriated lol but it went to edl mode then worked i remember being on the bootloader screen with red letters typed somethin in and it went to black screen then the quick flash started working i also hear it works better on usb 2.0 from some people.
roadkill42 said:
Will this work on ocean power phone Moto g7? It's my first a b device and my daily driver
Click to expand...
Click to collapse
I downloaded a set enforce switch app from play store that can turn it on or off with a tap while enforcing is off my camera works while it is on my camera does not, so i have to choose viper 4 android or camera sucks but true. I am on latest firmware for RETUS -5

Categories

Resources