My essential phone shows up as "pixel XL" in settings for device. I believe this is from using the Google framework magisk module. I have removed the module but it remains the same. This has caused me to not be able to receive OTA updates or use the stock camera app because it believes it's a different phone. Does anyone know how to fix this without flashing back to stock? I have already tried a build.prop editor but there was nothing there regarding the word pixel to change.
bschmidy10 said:
My essential phone shows up as "pixel XL" in settings for device. I believe this is from using the Google framework magisk module. I have removed the module but it remains the same. This has caused me to not be able to receive OTA updates or use the stock camera app because it believes it's a different phone. Does anyone know how to fix this without flashing back to stock? I have already tried a build.prop editor but there was nothing there regarding the word pixel to change.
Click to expand...
Click to collapse
Flash back to stock
Yeah. I got a Google security alert saying a pixel accessed my account. Changes PW just to be sure.
Sent from my PH-1 using XDA Labs
bschmidy10 said:
My essential phone shows up as "pixel XL" in settings for device. I believe this is from using the Google framework magisk module. I have removed the module but it remains the same. This has caused me to not be able to receive OTA updates or use the stock camera app because it believes it's a different phone. Does anyone know how to fix this without flashing back to stock? I have already tried a build.prop editor but there was nothing there regarding the word pixel to change.
Click to expand...
Click to collapse
I wonder what it reports to carrier ... would it mean we can get volte if carrier has approved Pixel XL? (he thinks without looking into volte at all)
sorry not much help to you though
It's pretty strange. Same thing happened to my one plus 3 but I was running a custom rom so I didn't care at all. I'm 90% sure it's from the Google framework magisk module. I have never owned an actual pixel but for instance in my Google play music authorized devices section it lists 4 PIXEL XL phones lol. They are all from my location upon my security checkup and like I said my phone thinks that's what it is so I don't have a concern about being hacked. Only thing I'm confused about is why did removing the module not resolve the issue... Or how did they do it in the first place so I can make a module to turn it back into an essential phone lol. Only thing I found from searching was a deprecated GitHub repo for the module.
I'll probably just give in and wipe everything and go back to stock. Been wanting to avoid that because of the convoluted process of flashing and rooting with A/B partitions. I read somewhere there was a new method to maintain TWRP now though? Does anyone know anything about that? Appreciate the input (even if it wasn't much help lol)
I'm not running the framework module.
But I did install the pixel sound effects.
Sent from my PH-1 using XDA Labs
Related
Rooted the phone on first day, then came across DNS66 app to block ads without root, based on what I was seeing, OOS is even providing agressive doze, so I was in a point to be able to use phone without greenify, so no root needed anymore. However when unrooted device, locked bootloader, the DM-VERITY error will not go away.
Tried a lot of methods available in XDA, nothing worked.
Here's what you do, flash the stock recovery from official downloads, the nougat version, then lock the bootloader, and sideload the entire ROM after wiping internal data from recovery. And it was gone.
I absolutely love OxygenOS. Since COS messed up, and I saw earlier releases of OOS for my OPO, I never thought they would come this far with great ROM development so fast. It's a great thing. This phone is unreal. There is no match for the value for money it is. Sure it would satisfy me more if it was a 2k display (spec wise), but this display is absolutely gorgeous. Perfect saturation level for my preference. It will be fun to see OOS get better. For the first time since I've become an advanced user, I'm using a phone without root permission, without sacrificing much for the stuff I need/use.
Sent from my ONEPLUS A3003 using XDA-Developers Legacy app
When I try sideload from official recovery "adb devices" either doesn't show my device at all or its says it's offline. Didn't you have this problem?
devlamania said:
Rooted the phone on first day, then came across DNS66 app to block ads without root, based on what I was seeing, OOS is even providing agressive doze, so I was in a point to be able to use phone without greenify, so no root needed anymore. However when unrooted device, locked bootloader, the DM-VERITY error will not go away.
Tried a lot of methods available in XDA, nothing worked.
Here's what you do, flash the stock recovery from official downloads, the nougat version, then lock the bootloader, and sideload the entire ROM after wiping internal data from recovery. And it was gone.
I absolutely love OxygenOS. Since COS messed up, and I saw earlier releases of OOS for my OPO, I never thought they would come this far with great ROM development so fast. It's a great thing. This phone is unreal. There is no match for the value for money it is. Sure it would satisfy me more if it was a 2k display (spec wise), but this display is absolutely gorgeous. Perfect saturation level for my preference. It will be fun to see OOS get better. For the first time since I've become an advanced user, I'm using a phone without root permission, without sacrificing much for the stuff I need/use.
Click to expand...
Click to collapse
Just to correct you a bit it's not an error, but a warning. Phone operates normal
But thanks for the insight. Will look at DNS66
devlamania said:
Rooted the phone on first day, then came across DNS66 app to block ads without root, based on what I was seeing, OOS is even providing agressive doze, so I was in a point to be able to use phone without greenify, so no root needed anymore. However when unrooted device, locked bootloader, the DM-VERITY error will not go away.
Tried a lot of methods available in XDA, nothing worked.
Here's what you do, flash the stock recovery from official downloads, the nougat version, then lock the bootloader, and sideload the entire ROM after wiping internal data from recovery. And it was gone.
I absolutely love OxygenOS. Since COS messed up, and I saw earlier releases of OOS for my OPO, I never thought they would come this far with great ROM development so fast. It's a great thing. This phone is unreal. There is no match for the value for money it is. Sure it would satisfy me more if it was a 2k display (spec wise), but this display is absolutely gorgeous. Perfect saturation level for my preference. It will be fun to see OOS get better. For the first time since I've become an advanced user, I'm using a phone without root permission, without sacrificing much for the stuff I need/use.
Sent from my ONEPLUS A3003 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I just got my phone a couple days ago. Rooted and custom recovery and when I flashed 4.0.2, I had the dm-verity issue, but I just officially fixed it today by flashing this zip file.
https://forum.xda-developers.com/showpost.php?p=70393513&postcount=72
If your question is... I am on 4.0.1 or 4.0.2 and this bootloader is for 3.5.4, will this work for me??
Simple answer... yes.
Works perfectly for me on 4.0.2
Also I haven't heard of the app you mentioned, but I am using AdGuard Pro, and it works great for me so far.
Also using the following apps.
CCleaner - I Run this every so often to cleanup app cache
ForceDoze
Hibernation Manager (I've used Greenify and it works great, but it needs Xposed to work). SInce Xposed is not yet available for Nougat I found this app to be a good alternative to Greenify and doesn't require root either.
L Speed
LeanDroid
V 2.0 said:
Just to correct you a bit it's not an error, but a warning. Phone operates normal
But thanks for the insight. Will look at DNS66
Click to expand...
Click to collapse
Yep, thanks for the correction, that's a warning, but it annoyed the sh** out of me.
DNS66 you can find in f-droid. It creates a VPN and blocks all requests to ad servers. Pretty straightforward but awesome. Since adaway hosts are also included, plus a lot more, it blocks a lot of ads unless it's being fed by main application server.
Sent from my ONEPLUS A3003 using XDA-Developers Legacy app
m0d hipp¥ said:
I just got my phone a couple days ago. Rooted and custom recovery and when I flashed 4.0.2, I had the dm-verity issue, but I just officially fixed it today by flashing this zip file.
https://forum.xda-developers.com/showpost.php?p=70393513&postcount=72
If your question is... I am on 4.0.1 or 4.0.2 and this bootloader is for 3.5.4, will this work for me??
Simple answer... yes.
Works perfectly for me on 4.0.2
Also I haven't heard of the app you mentioned, but I am using AdGuard Pro, and it works great for me so far.
Also using the following apps.
CCleaner - I Run this every so often to cleanup app cache
ForceDoze
Hibernation Manager (I've used Greenify and it works great, but it needs Xposed to work). SInce Xposed is not yet available for Nougat I found this app to be a good alternative to Greenify and doesn't require root either.
L Speed
LeanDroid
Click to expand...
Click to collapse
I'm running at almost 8.5 hours SOT based on average since I went total unrooted stock yesterday. That is abnormally good !!
That too, without anything from the list you mentioned. I "was" using Greenify pro version, but now I'm not, yes I clean up cache always, using All-In-One Toolbox Pro.
Which suggests, OOS 4.0.2 doesn't actually need anything from outside apart from the functionalities it's providing in-built.
So I recently upgraded to the latest 7.1.2 factory images, TWRP, full pixel mod, Magisk 12.0.
After upgrading I installed L Speed and that's about all the tweaking I've done.
Full pixel mod didn't seem to be causing this issue for anyone else, I usually l speed to no avail.
What would cause this?
I ask because when I search for the Amazon app it offers me Amazon for tablets instead. It also says Apple music isn't available for my device.
GatorsUF said:
So I recently upgraded to the latest 7.1.2 factory images, TWRP, full pixel mod, Magisk 12.0.
After upgrading I installed L Speed and that's about all the tweaking I've done.
Full pixel mod didn't seem to be causing this issue for anyone else, I usually l speed to no avail.
What would cause this?
I ask because when I search for the Amazon app it offers me Amazon for tablets instead. It also says Apple music isn't available for my device.
Click to expand...
Click to collapse
Did you access playstore before installing your apps/mods? As you only installed a few things, I suggest you revert to full stock.
Try stock, then install one app, try again, and so on. Until it breaks apps install and/or recognize your device as a tablet.
Sorry I don't know what's causing g your issue...
Good luck...
Just bought this phone from someone off swappa. I put all my apps on it, but while doing the setup I found that the Camera app and the Essential Resources app show updates available on Google Play. However, when I try to install them, I get 505 errors for both. 150 other apps installed just fine, but I can't install these 2 essential apps. Weird thing is, I checked the most recent version of the camera app available on the play store (0.1.067) and compared it to the one on my phone and it's the same version! Yet it says update on the play store. I looked for 'essential resources" under apps on my phone and I can't even find it at all.
Is it possible that the guy who sold me the phone modified the software somehow and that's what is causing the problems I am having? I want to update the essential resources app so that more apps can use the full screen.
Lastly, I tried to enter recovery by holding the power+volume down button when I start the phone. The menu comes up and I select recovery and all I get is a "no command" error along with the android with an exclamation point. Is there another key sequence I need to press at that point to get into recovery? I'm trying to clear the cache.
xphyle1971 said:
Just bought this phone from someone off swappa. I put all my apps on it, but while doing the setup I found that the Camera app and the Essential Resources app show updates available on Google Play. However, when I try to install them, I get 505 errors for both. 150 other apps installed just fine, but I can't install these 2 essential apps. Weird thing is, I checked the most recent version of the camera app available on the play store (0.1.067) and compared it to the one on my phone and it's the same version! Yet it says update on the play store. I looked for 'essential resources" under apps on my phone and I can't even find it at all.
Is it possible that the guy who sold me the phone modified the software somehow and that's what is causing the problems I am having? I want to update the essential resources app so that more apps can use the full screen.
Lastly, I tried to enter recovery by holding the power+volume down button when I start the phone. The menu comes up and I select recovery and all I get is a "no command" error along with the android with an exclamation point. Is there another key sequence I need to press at that point to get into recovery? I'm trying to clear the cache.
Click to expand...
Click to collapse
Just clear cache and data on play store application and see if that resolve your problem.
Sent from my HTC_U-3u using XDA-Developers Legacy app
Did that. No dice. Also removed my Google account and readded it. Still doesn't work. I installed the whitelist editor and used the adb commands to enable it. I hope whatever the previous owned did doesn't prevent me from receiving OTA updates.
xphyle1971 said:
Did that. No dice. Also removed my Google account and readded it. Still doesn't work. I installed the whitelist editor and used the adb commands to enable it. I hope whatever the previous owned did doesn't prevent me from receiving OTA updates.
Click to expand...
Click to collapse
The best suggestion with this phone is to do a factory reset, and set up the phone as new. Don't install anything from a back up or another device.
I believe I found the reason. I bought this phone off Swappa. It appears it's running a test build of the software somehow. NMI75B test-keys. I believe this is the reason the apps don't update. I have no idea why the phone updated to this build OTA, but I've seen a few other threads here and on Reddit where others have this build also.
xphyle1971 said:
I believe I found the reason. I bought this phone off Swappa. It appears it's running a test build of the software somehow. NMI75B test-keys. I believe this is the reason the apps don't update. I have no idea why the phone updated to this build OTA, but I've seen a few other threads here and on Reddit where others have this build also.
Click to expand...
Click to collapse
Has nothing to do with your build
https://drfone.wondershare.com/android-issue/error-505.html
I suspect it has to do with the playstore
Sent from my PH-1 using Tapatalk
jasonevil said:
Has nothing to do with your build
https://drfone.wondershare.com/android-issue/error-505.html
I suspect it has to do with the playstore
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Respectfully, I think you're wrong. I downloaded and have updated 150+ non-system apps to this phone without issue. Only 3 system apps won't download and update without giving me 505 errors. The 3 apps are Camera, Essential Services, and Essential Resources. I believe that the test build of the firmware I am using is the culprit. All 3 are system apps. In addition, I've already tried all 505 error remedies to try and fix the problem and they don't work for these 3 apps.
Hey Folks!
Hope someone can help me out here. I've read a whole bunch of forums and have tried a number of potential solutions to no avail. I have Magisk 15.2 installed and am running Lineage OS 14.2. Multiple apps confirm I pass Safetynet and I can successfully add a card to Android Pay. However, when I try to pay at a terminal, nothing happens. I have tried multiple terminals with no success. Nfc is enabled and android beam works.
Thanks!!!
Try enabling Core Only Mode in Magisk settings, try disabling systemless BusyBox, or try uninstalling your version of Magisk and trying the latest beta. SafetyNet is a nightmare to keep up with. Every time it updates, Magisk gets broken and we have to wait for a new update. Unfortunately, the only real solution is to stop using SafetyNet-dependent apps or keep a locked bootloader/unrooted phone. Or perhaps have one phone for custom ROM stuff and another one for SafetyNet stuff. :/ This is why I'm so vocal about ROMs passing SafetyNet. Hopefully you'll find a fix.
Hey there. Thanks! My phone already passes safety net, though, so I don't think that's the issue... That's what's so bizarre about it! Would you still recommend taking those steps with Magisk Manager?
lastconfederate2 said:
Hey there. Thanks! My phone already passes safety net, though, so I don't think that's the issue... That's what's so bizarre about it! Would you still recommend taking those steps with Magisk Manager?
Click to expand...
Click to collapse
You don't get an error message or anything? Sorry, I missed that. Not sure what the issue is, then. I assume by the other apps, you mean legit apps that actually check for SafetyNet, like downloads in Netflix, a game like Fire Emblem Heroes or a banking app like RBS. If you're able to use those apps or use all of the features perfectly, the issue might just be Android Pay, which probably now detects Magisk(?). Anyway, unless you're actually able to use an app that uses SafetyNet, those SafetyNet checkers don't count for much.
Correct. No error messages, Netflix and others work fine, successfully registered a card in Android Pay, it just doesn't do anything at payment terminals.
lastconfederate2 said:
Correct. No error messages, Netflix and others work fine, successfully registered a card in Android Pay, it just doesn't do anything at payment terminals.
Click to expand...
Click to collapse
I am experiencing the same issue but with Omni 7.1 and Magisk 15.2.
Card was added but giving "Card read error" at payment terminal.
If changing the settings or flashing a beta build doesn't get it to work, then I'm not sure what will. If you're able to, backup your existing ROM and factory reset it. If your Pro3 variant has an official LeEco ROM that passes SafetyNet natively, flash that and lock the bootloader and set up Android Pay to see if it works. Can't offer much else to help you, sorry.
Might be nothing to do with your problem, but i noticed when using nfc to add contacts with other nfc phones etc, that this phone has its nfc chip at the bottom/middle of the phone (it was a while ago, hope I've not remembered incorrectly). Until i realised this i had problems getting it to work.
Edit.. my memory is so bad in now thinking it was the very very top of the phone. Try both.
Thanks for your help, everyone. I discovered today that if I initiate the transaction while my screen is locked, it will actually start the process. I can then unlock the screen and re-tap and it will successfully complete about 75% of the time.
Nothing still happens if i tap the terminal with screen unlocked.
Not perfect, but it works for now!
lastconfederate2 said:
Thanks for your help, everyone. I discovered today that if I initiate the transaction while my screen is locked, it will actually start the process. I can then unlock the screen and re-tap and it will successfully complete about 75% of the time.
Nothing still happens if i tap the terminal with screen unlocked.
Not perfect, but it works for now!
Click to expand...
Click to collapse
Are you still able to get it to work like this? What was the last update you installed? I am trying to do some research to figure out why this happens on many different devices with different roms and such. Most seem to have the ability to get Pay to work and load cards into it, but using at stores and tapping the terminals does nothing(currently my issue).
So what is you setup as of now? Magisk ver, universal safetynet fix(if you're using that) ver, OS ver/date, and what security patch?
If you can provide those things it would be helpful.
Thank you.
Yes, that is still how it works, though I've found over time that it works more like 25% of the time. The last LOS update I have installed is February 10th. I'm using Magisk 15.3, running Android 7.1.2, and last security patch is 1/05/18.
Thanks!
Any luck with this?. Havent tried lock screen pay yet, but unlocked it doesn't work.
LOS 15.1- GTi9506
wkwk said:
Any luck with this?. Havent tried lock screen pay yet, but unlocked it doesn't work.
LOS 15.1- GTi9506
Click to expand...
Click to collapse
Google switched the API last week and rebranded Android Pay as Google pay
https://www.xda-developers.com/google-pay-android-pay-google-wallet/
Have you tried installing Google Pay?
https://play.google.com/store/apps/details?id=com.google.android.apps.walletnfcrel&hl=en
tsongming said:
Google switched the API last week and rebranded Android Pay as Google pay
https://www.xda-developers.com/google-pay-android-pay-google-wallet/
Have you tried installing Google Pay?
https://play.google.com/store/apps/details?id=com.google.android.apps.walletnfcrel&hl=en
Click to expand...
Click to collapse
Yes same issue.
Interestingly, upgrading to official LOS 15.1 this week completely resolved the issue. Google Pay works great unlocked, now.
lastconfederate2 said:
Interestingly, upgrading to official LOS 15.1 this week completely resolved the issue. Google Pay works great unlocked, now.
Click to expand...
Click to collapse
It will probably work in Lineage 14.1 once its been updated for the newer api.
Has anyone gotten latest version of PoGo working on latest Oreo with ElementalX? I've never played but my friends keep asking me to join so I figured what the heck..
Slight problem... Device Not Compatible??
I had magisk and xposed, but I tried disabling, and even fully uninstalling xposed (and all additional xposed modules), and adding PoGo to the MagiskHide options, with no luck.
It still says that my device is not compatible...I would assume that's due to the rooting?
Or is it because I'm using ElementalX kernel?
I read somewhere that there's a (not pokemon go-specific) bypass sort of thing involving SatefyNet, but you have to install Magisk *before* going through initial phone setup, but any guide I've ever read about flashing/rooting ph-1 says to go through setup and then install magisk. I tried to find the post that talks about it but I can't find it right now. Anyway, I would imagine there's some kind of checksum against system and if magisk has been added after the fact, the checksum wont match? I really have no idea, just a guess.
I haven't seen any other posts specifically mentioning Essential being incompatible, so maybe it's just me.
I was originally thinking it was because of root or magisk remnants(?), but maybe it's the non-stock kernel.
If anyone could help, I'd really appreciate it.
I feel silly asking such a noob question, I've just never play PoGo...or any Pokemon...ever.
extra info:
I have successfully created an account using their google auth option.
I get through the first Professor Willow part, then character selection.
Usually part way through character selection, I get the error in the attached image.
Its not on any one specific section, however, it can/has occur at any point during the loading.
I've cleared cache and data a hundred times because it seems to get further each time if I do a fresh data wipe and start over -- I know the next step already so I can get through faster maybe lol
--update--
I finally got through character selection and made it to the first chance to catch pokemon. I hit a squirtle and it was trying to break free, and then that error popped up.
Haven't been able to get back in far enough again to see if it actually added to my PokeDex or not.
Sorry for the late reply, but you have to hide root detection under magisk.
For Pokemon go to work, go to Magisk > MagiskHide > then search for Pokemon go and select it then reboot.