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.
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.
Im hoping someone can help me or possibly direct me to a youtube video to achieve what im looking to achieve
I struggled with, but finally managed to upgrade my device to stock 7.0, but rooted with magisk. When i tried to install xposed it forced a bootloop, so i restored a backup i had just made prior, and all has been well. I had wanted to install and use "Root cloak" as, at least so far thats been working on my 8.0 device (also Samsung, also stock but rooted but with SU method in that case, i couldnt get SU alone to work on my 7.0, for whatever reason)
I left it alone, but I'm noticing more and more that apps Id like to use come up saying "device is incompatible", which at first i thought it was weird as the play store itself allowed the install... but then upon some basic looking around, it seems that the apps have a way of detecting root, even through "magisk hide" - the feature directly included in magisk manager.
currently when i try to test for safetynet directly in the magisk manager, it doesnt actually properly test at all, no pass or fail, it just said unable
the rather peculiar part is that some of these apps arent all even banking apps, theyre for games. I cant figure out why gaming apps have issues with root access, especially when these apps themselves dont have root access, but thats kind of an aside
Any simplified help anyone can offer would be great! i am slightly familiar with editing the build prop, but i wouldnt know which values to change or even if that method is still effective. i used to use that on a quite older device (captivate glide) to spoof which version of android i was on in order to download app updates (which did work just fine, so why my older version wasnt supported is beyond me, lol)
thank you in advance for any help you can offer!
hey there,
i was using custom roms back in the day with my oppo find 7, so android 7ish. Back than maintaining custom roms was a major pain in .... because, at least for me, i needed to full flash every time there was an update and most roms were kind of buggy as well.
Since my 9t is being annoying lately (EU 12.0.5) with shutting down apps way to often/fast, forgetting logins, making backups everywhere, switching back to light mode, no idea how to do a proper cleanup without deleting half my app settings etc. I was wondering what the state of the custom rom is nowadays.
I was thinking about getting something smaller, but since the pixel 5 is out of sale, the zenfone 8 missing wireless charge and no real alternative and all of them are more than 600 bucks, so i dont want to get a new phone tbh, prices are out of this world imho. Also iam quit pleased with the device itself, i.e. battery, performance, everyday stuff
so basically here is what i want to know:
How are updates handled in Pixelexperience or lineage?
how hard/easy is installation?
is google pay working?
is there a relyable way to make a full backup of my phone to go back to as is now?
did anybody experience the mentioned issues and maybe has a solution?
bonus qquestions
is there any major improvement in upcomming MIUI Versions(12.1, 12.5) and a roadmap of rollout?
what does SOT mean?
thanks in advance
for updates you may have to re flash the newer rom.
2. installation is easy given you know how to do it.
3. google pay is working fine.
4. twrp is the way, but believe me you won't aspire to go back.
5. I am running pixel experience rom on MI A2 device, the device is working great.
*/learn from youtube properly how to flash recovery, install rom for your device */
best of luck
I'm on Xiaomi.eu Stable (did use Weeklies for 6 months) - daily driver / business phone
If you like MIUI, you have A11, MIUI 12.5, debloated, all stable
You only flash ROM from TWRP (of course, first time, when switching to, Format Data is mandatory).
Later they have like OTA mechanism (Updater downloads ROM in zip, reboots to TWRP and upgrades)
not sure if i really like miui or not, thats why i was eyeing pixel/zenfone, i was pretty happy with my Mi A1 before the 9t
wouldnt a twrp backup break my safety net? if i remember correctly i need to unlock/root
suraj123 said:
2. installation is easy given you know how to do it.
Click to expand...
Click to collapse
well i knew it, but it has been ages
Abudinka said:
not sure if i really like miui or not, thats why i was eyeing pixel/zenfone, i was pretty happy with my Mi A1 before the 9t
wouldnt a twrp backup break my safety net? if i remember correctly i need to unlock/root
well i knew it, but it has been ages
Click to expand...
Click to collapse
For flashing any other ROM you need to unlock Bootloader - and that breaks Safety Net, not TWRP folder or so
However, Xiaomi.eu has built-in patch to pass SafetyNet with no need for Magisk, any Magisk module, anything
I.e., you switch to Xiaomi.eu (with Bootloader unlocked), no need to install Magisk and any of the modules like USNF, MHPC, etc) and you have SafetyNet, Device Certified in Google Play.
Also Widevine L1 and Netflix really plays in FullHD, HDR-10
And if you need Magisk for something else, you just enable MagiskHide and you still have SafetyNet etc.
No troubles here with SafetyNet
how much free space do i need for a twrp backup? most likely half of the internal space i guess.
so basically for every other rom besides xiami.eu i need to worry about safety net with magisk or similar?
I have TWRP Nandroid backup of 15 GB, but most of that is Data.
You don't need the backup for installing/updating the ROM.
That's only for your comfort
But I put it to PC and delete from the phone (if really needed, TWRP can also connect to PC and you can copy it back to phone before restoring)
I never needed to restore
And one more but very important thing
TWRP (backup) has NOTHING with SafetyNet. SafetyNet DOES NOT look do you have TWRP folder, or do you have Magisk app/mngr (I'm not talking about thevMagisk core/service but apk)
Unfortunately, there are too many unknowledgeable people writing that and similar nonsense elswhere
Problem is (and that's the reason why it might look 'similar' from the end user's point of view) that various banking apps, ganes and so, use VARIOUS methods and in some cases even speculative GUESSES trying to find if your device is SAFE for their apps and businesses (whatever that means for somebody), or is your phone 'rooted' (also in the very loose sense)
Those methods and guesses may include:
- Testing SafetyNet (framework provided by Google, partly in Google Play Services and partly on Google servers).
Fornally, when Bootloader is unlocked and/or with custom ROM (not certified with Google) or rooted (stock) ROM , you *should* fail SafetyNet - but there are methods to trick Google and still to pass SafetyNet.
Actually, to flash any such nod (custom ROM or recovery, or root, you first need to unlock Bootloader - and that's the first thing that SafetyNet looks for, but on some phones and ROMs it is possible to fool even the Google's SafetyNet)
That's the reason why thosre apps combine various other methods trying to find (or just to guess) if your phone is 'safe' or not
Some use sofisticated methods looking for su in the path or modified init.rc, or bypass Magisk Hide acting as isolated processes - that way finding the gllitches in MagiskHide making them possible to detect Magisk
But some use very PRIMITIVE guesses:
- If they find TWRP folder, they 'conclude' you 'must' be having TWRP, hence your Bootloader 'must' have been unlocked and you might have been flashed the root or custom ROM, hence they simply declare your phone as 'unsafe' or "rooted'.
But you could take 100% stock and not-modded phone and just create there a folder named TWRP on Internal memory - and your phone will fail their 'safety' pass (but not the Google's SafetyNet)
- Similarly, some just look if they find that the com.topjohbwu.magisk package installed (being Magisk apk, but that is not Magisk as core/service).
Again, you can take 100% stock, not-modded phone and just install there the Magisk apk (maybe, because you wantef to use its built-in SafetyNet checker), and those apps will declare your phone was 'rooted' - which is again total nonsense
On the other side, that is all about statistics. There will be let's say 0.001% of people who do have TWRP folder but not custom TWRP recovery and similarly 0.005% people who do have Magisk app but no Magisk
On the other side, 90% of people who do have custom Recovery will also have TWRP folder and 60% of people with Magisk service/core will also have Magisk app (formerly mngr) - the rest 40% of Magisk users will have hided/obfuscated/repackaged Magisk app (therefore, it cannot be found under the com.tophohnwu.magisk package name)
Hence those apps (and their developers, or better to say those who paid those developers to implemen that GUESSES) can take them rights to declare the phones with TWRP foldersor Magisk app installed as 'unsafe'
Those 1-5 users out of 100000, who by incidence do have TWRP folder (but no custom recovery) or Magisk app (but no Magisk) - bad luck, who cares about them
On the other side, that guesses (since they didn't come up with anything more sofisticated) will make them possible to catch 500 users with TWRP or Magisk, who tricked the Google's SafetyNet (but didn't even think about that primitive possibilities to 'catch' them)
thanks for the explanation, i most likely have a look this evening. Still, most app data will be lost when switching to pixel experience i assume
Abudinka said:
thanks for the explanation, i most likely have a look this evening. Still, most app data will be lost when switching to pixel experience i assume
Click to expand...
Click to collapse
Please find and read instructions for switching to the (custom) ROM - they can be found elswhere
An important and a MUST step is Formatting Data (that also formats Internal memory). Hence not 'most' but ALL user spps, their settings, your data like photos, contacts, Wifi passwords and everything will be wiped
Read and learn about what and how can be backed up. Good luck
im fully aware, that switching to another rom needs a full wipe and therefore loss of all data if not backup'ed.
I was more hoping one could provid a link and/or recommend something convienent.
And one more point. You must first unlock Bootloader - find where/how, apply for and you will need to wait 7 days
Unlocking bootloader performs Factory reset. However, at that time you are still on MIUI and you can use Xiaomi Cloud to backup and restore upon Factory resetting
(Once you unlock Bootloader, you can make Nandroid backups in TWRP but you cannot restore to custom ROM what you backed-up from MIUI, or vice versa
Once you switch to your custom ROM (and potentially root), you can use some apps for backing up and restore - but avoid the old and outdated Titanium
Hence I don't really see a point in TWRP backups, only just-in-case, for restoring the last working point in case of (soft) brick cases
zgfg said:
(Once you unlock Bootloader, you can make Nandroid backups in TWRP but you cannot restore to custom ROM what you backed-up from MIUI, or vice versa
Click to expand...
Click to collapse
Thanks alot again for the detailed explanation. This was the detail i was looking for. so basically its impossible to avoid losing app settings which are not saved in cloud and assigned to an app account.
The hint about miui backup/xiaomi cloud comes in handy as well. Also regarding the delayed bootload unlock, if it really takes up to 30 days (as stated on the pixelexperience install guide), maybe the Sony event on 26th brought something interessting
Abudinka said:
Thanks alot again for the detailed explanation. This was the detail i was looking for. so basically its impossible to avoid losing app settings which are not saved in cloud and assigned to an app account.
The hint about miui backup/xiaomi cloud comes in handy as well. Also regarding the delayed bootload unlock, if it really takes up to 30 days (as stated on the pixelexperience install guide), maybe the Sony event on 26th brought something interessting
Click to expand...
Click to collapse
It usually takes (and not from recently) exactly 168 hours = 7 days, no more or less.
There are also threads here on XDA about
Unless Xiaomi just recently changed the policy, but that could also depend on models
SOT = screen on time
Hey,
I come to you with a peculiar set of bugs? Problems?
I got a pretty fresh 12G Ram Nothing Phone (1) here. I tried rooting it pretty much immediately with help of the forum post here, but the OTA updater failed afterwards, so I let magisk uninstall itself, flashed a clean full European update and then ran the OTA updater al the way up to 1.1.4, using the phone for 2 days no problems now.
Today I ran into a problem I have never seen before: Netflix on the app store is listed as not compatible with my device. All other streaming apps work. In fact pretty much all other apps I previously used do work (acutally KWGT also showed as incompatible, but the apk from another page worked).
Now all my banking apps still work and they are super sensitive to any changes (except GPay of course, since the bootloader is still unlocked), but I still ran a safety net check, which passed, however the apps I used for testing did still show a cts profile mismatch. How can this be? Is there anything I could do to fix it? Could this cause for whatever reason just a ban on netflix in the store?
Im kind of lost here. Id like to try everything before I have to do a full reset, as that would mean a lot of trouble.
Edit: Well nvm Im idiot. So apparently just having the bootloader unlocked causes a CTS profile mismatch and Netflix does get removed from the appstore for that. Never encountered this on my rooted to death Mix 3 before, which is why I made the assumption that it is weird. Delete this thread if you want
Still any good fix available rn? The Netflix apk alone doesnt seem to work and root is not available yet on 1.1.4 afaik.
Leolele99 said:
Hey,
I come to you with a peculiar set of bugs? Problems?
I got a pretty fresh 12G Ram Nothing Phone (1) here. I tried rooting it pretty much immediately with help of the forum post here, but the OTA updater failed afterwards, so I let magisk uninstall itself, flashed a clean full European update and then ran the OTA updater al the way up to 1.1.4, using the phone for 2 days no problems now.
Today I ran into a problem I have never seen before: Netflix on the app store is listed as not compatible with my device. All other streaming apps work. In fact pretty much all other apps I previously used do work (acutally KWGT also showed as incompatible, but the apk from another page worked).
Now all my banking apps still work and they are super sensitive to any changes (except GPay of course, since the bootloader is still unlocked), but I still ran a safety net check, which passed, however the apps I used for testing did still show a cts profile mismatch. How can this be? Is there anything I could do to fix it? Could this cause for whatever reason just a ban on netflix in the store?
Im kind of lost here. Id like to try everything before I have to do a full reset, as that would mean a lot of trouble.
Edit: Well nvm Im idiot. So apparently just having the bootloader unlocked causes a CTS profile mismatch and Netflix does get removed from the appstore for that. Never encountered this on my rooted to death Mix 3 before, which is why I made the assumption that it is weird. Delete this thread if you want
Still any good fix available rn? The Netflix apk alone doesnt seem to work and root is not available yet on 1.1.4 afaik.
Click to expand...
Click to collapse
You added playstore and play services to the denylist and installed safetynet fix i guess?