Netflix is not working since I have android 10, I installed from 0 and Netflix doesn't appear in Google play, and official apk doesn't work for me.
Recently CTS won't pass with Magisk installed (even with Magisk hide). Google must have changed SafetyNet rules, Magisk did not catch up yet. It's not clear if this issue is impacting all Magisk users or only some. I can't pass CTS anymore, Android 9.
_mysiak_ said:
Recently CTS won't pass with Magisk installed (even with Magisk hide). Google must have changed SafetyNet rules, Magisk did not catch up yet. It's not clear if this issue is impacting all Magisk users or only some. I can't pass CTS anymore, Android 9.
Click to expand...
Click to collapse
Likewise on stock android 10 for the past 2 or 3 days. No mods installed as such and failing CTS.
Play store is still showing verified device but I hear some users are getting non verified message which will not allow them install certain apps
How about those who become L3 in the attempt to fix sensors of downgraded to Android 9 and flashed persist partition ?
amnher said:
How about those who become L3 in the attempt to fix sensors of downgraded to Android 9 and flashed persist partition ?
Click to expand...
Click to collapse
Probably out of luck, DRM certificates are gone forever. At least that was the case for Mi A1 phone, but seems to be the same for A3.
_mysiak_ said:
Probably out of luck, DRM certificates are gone forever. At least that was the case for Mi A1 phone, but seems to be the same for A3.
Click to expand...
Click to collapse
Will warranty be a solution? Phone is less than two weeks old
amnher said:
Will warranty be a solution? Phone is less than two weeks old
Click to expand...
Click to collapse
No, you screwed it up. As far as I know, service center can't restore DRM keys even if they wanted to, they are flashed in factory and unique to each phone. The only solution is probably to replace whole motherboard. This was the case with Mi A1 and all Sony phones where unlocking of bootloader removed DRM keys as well. Nevertheless, you can try your luck and contact your service center..
_mysiak_ said:
No, you screwed it up. As far as I know, service center can't restore DRM keys even if they wanted to, they are flashed in factory and unique to each phone. The only solution is probably to replace whole motherboard. This was the case with Mi A1 and all Sony phones where unlocking of bootloader removed DRM keys as well. Nevertheless, you can try your luck and contact your service center..
Click to expand...
Click to collapse
This is worst I really did not expect that in messing with persist image really permanently destroys it and I will not be able to enjoy HD videos of Netflix on my a3. Other than that, what are the disadvantages of loosing L1 (messed up DRM) ?
they pulled back the update maybe that's the reason.
and if your device is bootloader unlocked it's also a reason...
i installed Netflix from apkpure.
amnher said:
This is worst I really did not expect that in messing with persist image really permanently destroys it and I will not be able to enjoy HD videos of Netflix on my a3. Other than that, what are the disadvantages of loosing L1 (messed up DRM) ?
Click to expand...
Click to collapse
Yeah, it's unfortunate, many people are advising to "just flash persist.img and it will solve your issues", but it doesn't seem to help in first place and additionally damages the phone beyond repair. Lesson learned for you I guess, don't trust some random folks on the Internet..
Btw. as far as I know, 720p videos should be still playable on Netflix, it affects only full HD and 4K content (which need L1), which you wouldn't enjoy on 720p screen anyway. On Mi A1 I had only L3 (that was the default DRM level) and I did not notice any usability issues, Netflix, Google play music etc. were working nicely. On the small screen I did not notice that Netflix was playing at lower resolution.
_mysiak_ said:
Yeah, it's unfortunate, many people are advising to "just flash persist.img and it will solve your issues", but it doesn't seem to help in first place and additionally damages the phone beyond repair. Lesson learned for you I guess, don't trust some random folks on the Internet..
Btw. as far as I know, 720p videos should be still playable on Netflix, it affects only full HD and 4K content (which need L1), which you wouldn't enjoy on 720p screen anyway. On Mi A1 I had only L3 (that was the default DRM level) and I did not notice any usability issues, Netflix, Google play music etc. were working nicely. On the small screen I did not notice that Netflix was playing at lower resolution.
Click to expand...
Click to collapse
Im at service center and they do not know what DRM is... but they will flash via testpoint i dunno if it will help
amnher said:
Im at service center and they do not know what DRM is... but they will flash via testpoint i dunno if it will help
Click to expand...
Click to collapse
I'm afraid that not, DRM keys are lost already, they would have to generate/obtain new ones. In each case, let us know how it went..
_mysiak_ said:
I'm afraid that not, DRM keys are lost already, they would have to generate/obtain new ones. In each case, let us know how it went..
Click to expand...
Click to collapse
It came back to 10.3.3.0 which is lower than before when i purchase it. Sadly L3 and they opened a brand new mi a3 and it was L1 so they are surprised. The technicial now is tying to do an ota. Though i doubt it will be fixed
Ps. Failed now they will change the motherboard
Check this out:
forum.xda-developers.com/yureka/themes-apps/fix-device-isnt-compatible-version-t3892194
I dunno it helps, but it worked for me
callmegov said:
Check this out:
forum.xda-developers.com/yureka/themes-apps/fix-device-isnt-compatible-version-t3892194
I dunno it helps, but it worked for me
Click to expand...
Click to collapse
It changes these things in build prop, I doubt that it will help with anything for Netflix and even OP says that it's only to show Netflix in playstore (for phone models which are "unsupported" by Netflix officially, which is not the case for Mi A3).
ro.product.model=Pixel 3 XL
ro.product.brand=google
ro.product.name=crosshatch
ro.product.device=crosshatch
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=Google
ro.product.locale=en-US
Basically, f*ck Netflix and Google. We can't even watch the things, even if we want to pay for it, so f*ck them, I'll just download the movies/shows from somewhere else and put it on my SD card.
[Solved]
Hey guys! Good news
:victory: Got Netflix back to work with unlocked bootloader, current Bliss Rom and Magisk installed. :victory:
I believed that ctsProfile failure was the culprit of not being able to install Netflix from Google Play so I get it to pass thanks to @pkdon123 suggestion and files shared by @rudranshrajput and off course some G search. Here's what I've done (not sure if all steps are needed, I went throught it just once):
Solved ctsProfile with flashing two files through Magisk and rebooting.
Used Magisk Hide to hide it from GP and Google Services Framework. Then run SafetyNet check and ctsProfile passed without any issue.
Clear cache and data from both apps - GP and GSF. Then I had to reboot twice to get GP to work again but finally was able to find and install Netflix from there straight away and everything is working perfectly.
Let me know if it works for you guys. Good luck :fingers-crossed:
Horstorm said:
Hey guys! Good news
:victory: Got Netflix back to work with unlocked bootloader, current Bliss Rom and Magisk installed. :victory:
I believed that ctsProfile failure was the culprit of not being able to install Netflix from Google Play so I get it to pass thanks to @pkdon123 suggestion and files shared by @rudranshrajput and off course some G search. Here's what I've done (not sure if all steps are needed, I went throught it just once):
Solved ctsProfile with flashing two files through Magisk and rebooting.
Used Magisk Hide to hide it from GP and Google Services Framework. Then run SafetyNet check and ctsProfile passed without any issue.
Clear cache and data from both apps - GP and GSF. Then I had to reboot twice to get GP to work again but finally was able to find and install Netflix from there straight away and everything is working perfectly.
Let me know if it works for you guys. Good luck :fingers-crossed:
Click to expand...
Click to collapse
Hiding the full play services causes battery drain.
You only need to hide com.google.android.gms.unstable from play services.
All of this is already mentioned in the magisk documentation.
Also Netflix will still work with rooted device you just need to download it from a different source like apkmirror. It doesn't download from the playstore because play store isn't certified which is why we hide it in magisk.
If people took the time to read the applicable documentation then threads like this wouldn't have to exist
garylawwd said:
Hiding the full play services causes battery drain.
You only need to hide com.google.android.gms.unstable from play services.
All of this is already mentioned in the magisk documentation.
Also Netflix will still work with rooted device you just need to download it from a different source like apkmirror. It doesn't download from the playstore because play store isn't certified which is why we hide it in magisk.
If people took the time to read the applicable documentation then threads like this wouldn't have to exist
Click to expand...
Click to collapse
I was having the same exact problem and I solve this problem by enabling magiskhide and doing exactly what you have said I also tested by downloading the apk from the APK mirror and it was working absolutely fine but my problem was that I wouldn't be able to get Netflix updates from the play store also my device was uncertified and I was trying to make it certified which was easily done by flashing magisk also keep in mind that if you have only unlock the bootloader on stock ROM CTS won't pass and device will be non certified so if you want to stay on your stock ROM you need to lock the bootloader but I would suggest that instead of locking the bootloader you can flash magisk and use magisk hide just as a precaution as if she does anything wrong in future ota you can save yourself easily just by having and unlock bootloader.
garylawwd said:
Hiding the full play services causes battery drain.
You only need to hide com.google.android.gms.unstable from play services.
All of this is already mentioned in the magisk documentation.
Also Netflix will still work with rooted device you just need to download it from a different source like apkmirror. It doesn't download from the playstore because play store isn't certified which is why we hide it in magisk.
If people took the time to read the applicable documentation then threads like this wouldn't have to exist
Click to expand...
Click to collapse
Thanks for a suggestion. I didn't read the Magisk documentation and the truth is that I should but 'ain't nobody got time for that'... I consider myself just as an Android enthusiast and spending time to read all documentation I should to install custom rom and get root access would take enormous amount of precious time. I totally agree that If everyone would read the documentation (also write it responsibly) no such forums would be necessary. On the other hand this is why forums like this (Q&A, Guides,...) exist -> to share the knowledge.
And to the actual problem:
I had no clue that it could be actually connected to Magisk itself due to it worked on same device for several months on different custom roms without any issue. That's why I was looking for an answer in the ROM's thread. After disabling full GP Services I didn't notice higher battery drain, but disabling gms.unstable is sufficient. Installing Netflix from other sources is short-term solution which I off course did but I was looking for a solution that will last.
Off Topic: I've noticed that you're quite active in this forum and seems to have the knowledge. Keep it up and keep the patience. Thank you :good:
Related
Hello,
I fixed my previous issue that caused my phone to unfortunately not boot after Magisk patching kernel instead of ramdisk, but now my problem is a lot weirder and seems even more complex.
I wanted to patch YouTube with Lucky Patcher once again as the patch seemed to be not working now. After the patch has been applied, a communicate was shown saying that it couldn't make some file because blah blah and that firmware got messed up. I didn't care much, but then I wanted to uninstall YouTube's updates and it hung, YT was unavailable and Play Store was showing that it is still uninstalling, so I wanted to reboot. After that my phone started to bootloop. Flashed system.img and ramdisk.img again via fastboot, but didn't fix the issue. Tried using HwOTA to reinstall the whole system and then the party has started. Download recovery showed that it couldn't install the package. I couldn't reboot anyway nor enter eRecovery, so I forced reboot. Since then I can only enter recovery, broken eRecovery and fastboot. Trying to boot system just brings that broken eRecovery too.
Any way to fix that, or am I forced to install stock ROM, lock the bootloader and try sending phone on warranty (if possible, either way to the service)?
I am so pissed off that I'll probably sell the phone if servicing is needed and buy Xiaomi Redmi Note 5 Pro.
Thank you in advance.
SevenUp9 said:
Hello,
I fixed my previous issue that caused my phone to unfortunately not boot after Magisk patching kernel instead of ramdisk, but now my problem is a lot weirder and seems even more complex.
I wanted to patch YouTube with Lucky Patcher once again as the patch seemed to be not working now.
Click to expand...
Click to collapse
Why patch youtube app? To make it adfree?
Fyi, there's this mod app called Youtube Vanced that has black/dark mode and adfree which is awesome.
Edit: you can also install Youtube Vanced along side with the original playstore downloaded youtube.
Well, just to make it black and available to play in the background.
I know there is YouTube Vanced, I used that before, but just for some reason wanted to have original YT app. Not important. Just my weirdness Next time I'll just install Vanced, less problems.
But the thing that simple patching could brick my device... Oh boy. This is really strange.
oh, the irony of your bad luck with lucky patcher
i feel no pain for anyone stealing apps. amazing that the same person stealing apps bricks his phone in the process, and rather than spend time fixing it wants huawei to just replace it.
guys like you are driving up the cost of these devices.
guys like you are also responsible for huawei feeling the need to lock down bootloaders.
WaxysDargle said:
oh, the irony of your bad luck with lucky patcher
i feel no pain for anyone stealing apps. amazing that the same person stealing apps bricks his phone in the process, and rather than spend time fixing it wants huawei to just replace it.
Click to expand...
Click to collapse
No stealing. Simple mod to make YT dark-themed and play in the background, that's all. Believe me or not, some of the songs I listen to on YouTube are not available on Spotify or SoundCloud, and Lucky Patcher had its beggining here, on XDA, right? Same applies to YT Vanced. No need to be pissed.
Huawei may not directly be responsible for the issue, but the fact they are shutting down the bootloader unlocking site, they want to kill modders and that's partially why I don't know how to recover. Modding scene for this phone is growing poorly. Only one custom kernel available that is not bugless... And a few ROMs, mainly because of Treble.
If it's irrecoverable, okay, I'll pay for a repair then, but after that I won't be willing to support Huawei anymore. I expected more care for their more advanced, geeky users...
And no, I want to recover it alone, but I am tired already cause this phone has already caused me problems for over 20 hours (8h debranding and installing Oreo, 12h debricking after Magisk patched kernel instead of ramdisk, and some time for kernel testing, fixing, Magisk stuff). I am just tired and have no idea what to do. And if I wanted to just go for an easy way and send on warranty/to repair, I would do it instead of creating this topic... Repair in a service is mentioned here in case it's irrecoverable. Clear enough.
SevenUp9 said:
No stealing. Simple mod to make YT dark-themed and play in the background, that's all. Believe me or not, some of the songs I listen to on YouTube are not available on Spotify or SoundCloud, and Lucky Patcher had its beggining here, on XDA, right? Same applies to YT Vanced. No need to be pissed.
Huawei may not directly be responsible for the issue, but the fact they are shutting down the bootloader unlocking site, they want to kill modders and that's partially why I don't know how to recover. Modding scene for this phone is growing poorly. Only one custom kernel available that is not bugless... And a few ROMs, mainly because of Treble.
If it's irrecoverable, okay, I'll pay for a repair then, but after that I won't be willing to support Huawei anymore. I expected more care for their more advanced, geeky users...
And no, I want to recover it alone, but I am tired already cause this phone has already caused me problems for over 20 hours (8h debranding and installing Oreo, 12h debricking after Magisk patched kernel instead of ramdisk, and some time for kernel testing, fixing, Magisk stuff). I am just tired and have no idea what to do. And if I wanted to just go for an easy way and send on warranty/to repair, I would do it instead of creating this topic... Repair in a service is mentioned here in case it's irrecoverable. Clear enough.
Click to expand...
Click to collapse
background play is a paid service on youtube. you're stealing.
if you can get to recovery or fastboot, it's not irrecoverable.
you should really consider sticking with stock from now on. no one should feel sorry for you because you bricked your phone and had to work to fix it.
Do I convince anybody to feel sorry that I bricked my device? No.
Do I feel irresponsible for bricking it by my own? No.
Do I reccommend stealing? No.
I just have no money on my own, also previously there was no background play option on YT. Okay, maybe I wanted to crack, but it should be in my bussiness. Thousands of other people do the same, even here.
And yeah, I know it should be recoverable because I can boot into TWRP and fastboot, question is how, because I am already out of my mind. I'm not saying that I am tired to make others feel sorry for me but just to inform I can't handle this on my own atm and need some help.
I am on stock, that is right, not yet needed to flash customs imo as the phone runs just good.
Let's not offtop any longer. I just want to get some possible solutions. Right now I am going to flash all the system files via fastboot or TWRP once again. The problem is that I can't flash anything eRecovery-related.
OK, actually eRecovery and everything related to it such as dload, low-level reset etc. is broken. Even stock recovery, I can't even shutdown or reboot system. It is probably something deeper in whole framework, device is simply not available of doing simple tasks using its own functions. I am afraid it's not what I am able to fix. It's the first time when I have such problem.
I'm going on holiday on Sunday not bringing my PC with me, so I won't be capable of fixing it for around 1,5-2 weeks. But if anyone's got any idea, I am here to listen.
If it is more complex than a fellow mobile user can fix, I'll just leave it for specialists in a service to fix the issue. I hope it's recoverable with any tool just flashing firmware, either way my wallet will be hurt so much, I suppose.
Wait what? Now all the time my phone boots into TWRP from HwOTA, even if I flashed CATUVA21's version.
I mean... Booting after I just power it on, it just boots HwOTA's TWRP like it was eRecovery...
did u flashed the images that is same with your version?
or did u tried flashing kernel before flashing system img?
I had a similar problem when i used HwOTA, remember that HwOTA8 is when you got oreo and HwOTA7 is for nougat. Using the wrong one will boot to twrp if i remember correctly.
summerblaze said:
did u flashed the images that is same with your version?
or did u tried flashing kernel before flashing system img?
Click to expand...
Click to collapse
Yeah, I did both.
Anyway, phone's back from repair shop, quite disappointed that they've charged me for $80 when I could do it for $20 using the same tool they did (DC Phoenix), but whatever. Lesson for me - never ever overuse Lucky Patcher and don't believe that repair shop might be cheap. Also never buy Huawei anymore as it is extremely painful to recover it for nerves and for wallet. I'll be more careful now with this phone, still thinking about selling it and buying Xiaomi Redmi Note 5 or Mi8 because there's a good offer where I can get that phone for ~$380.
I'm going to do last mod to this phone - reflashing OS. The OS I got after the phone's been repaired looks a bit sketchy, because OS version is System 8.0.0.046(07P2) instead of RNE-L21 8.0.0.xxx(C432). Firmware Finder sees no updates for that so I expect OTA isn't working as well. Hope it doesn't get bricked again... Wish me luck.
petanque said:
I had a similar problem when i used HwOTA, remember that HwOTA8 is when you got oreo and HwOTA7 is for nougat. Using the wrong one will boot to twrp if i remember correctly.
Click to expand...
Click to collapse
Yeah I know. I used proper version (HwOTA8), but it flashed TWRP in eRecovery partition which made the phone complete brick because no dload mode. Hope that it doesn't make such mistake now as I'm going to install proper Oreo for EU locale.
Nah. I'll have to beg for a free (or cheap) repair once again because this piece of crap got bricked again. Thank you Huawei for providing so much pain while flashing your devices.
Whatever, a few days ago I realized the issue was way simplier than I expected. Just flashed oeminfo from HwOTA7 instead of 8, as the one in 8 seems broken and the device won't boot up. $80 repair wasn't worth it... Damn.
Hello,
I'm thinking of purchasing a Pocophone after using iPhones for the last 10 years - I've never used an Android device before. I'm really looking for a stock Android experience (I really dislike bloat and vendor customizations in general) and I am a bit confused by all the conflicting information regarding custom roms.
Basically I want to have the Pocophone with the Pixel Experience custom rom with the minimum amount of problems possible. Here's what I've gathered so far:
- I'd need to unlock the bootloader (takes three days) so I can replace it with TWRP.
- I then have to get into TWRP, wipe everything on the device and tell it to install the custom rom .zip file
My questions are:
- I already created my Mi account and downloaded the unlock tool from Xiaomi's website. Do I still need to wait three days after I get the actual phone?
- Do I need to do anything else in this process? I've read some stuff about vendor firmware, disabling encryption, formatting the device after installing the custom rom... is any of this necessary? What else do I need to know?
- If a new version of Pixel Experience is released and I want to update it, what is the process that I have to go through? Can I update/upgrade it without losing my data?
- I've read that some applications, such as Netflix, do not work and/or don't even show up on the play store. Is this true? How can you fix it?
Any and all clarification on this matter would be greatly appreciated.
lixoman100 said:
Hello,
I'm thinking of purchasing a Pocophone after using iPhones for the last 10 years - I've never used an Android device before. I'm really looking for a stock Android experience (I really dislike bloat and vendor customizations in general) and I am a bit confused by all the conflicting information regarding custom roms.
Basically I want to have the Pocophone with the Pixel Experience custom rom with the minimum amount of problems possible. Here's what I've gathered so far:
- I'd need to unlock the bootloader (takes three days) so I can replace it with TWRP.
- I then have to get into TWRP, wipe everything on the device and tell it to install the custom rom .zip file
My questions are:
- I already created my Mi account and downloaded the unlock tool from Xiaomi's website. Do I still need to wait three days after I get the actual phone?
- Do I need to do anything else in this process? I've read some stuff about vendor firmware, disabling encryption, formatting the device after installing the custom rom... is any of this necessary? What else do I need to know?
- If a new version of Pixel Experience is released and I want to update it, what is the process that I have to go through? Can I update/upgrade it without losing my data?
- I've read that some applications, such as Netflix, do not work and/or don't even show up on the play store. Is this true? How can you fix it?
Any and all clarification on this matter would be greatly appreciated.
Click to expand...
Click to collapse
1. Yes. After binding the device with your mi account and apply for the bootloader unlock using the MiFlash tool, you need to wait for 72 hours. It will reflect on MiUnlock tool as well.
2. Just download the latest TWRP from here and flash it (Link: https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-decryption-t3853004) and no need to flash DFE (Disable ForceEncryption). Don't worry about it being unofficial. Even though it's unofficial, it is the best solution for us as of now.
A piece of advice: Never use a decrypted device if you are concerned about the security of your device. Infact, never flash anything suggested by anyone without cross checking the authenticity of the file. You will come across many users suggesting you to flash this and that when the fact is,they are afraid to try on their own and rather want you to be the guinea pig.
3. When a new update comes in, you will get notified automatically. Or there is an option on settings to check for new updates. Just download the update and dirty flash it on TWRP (Dirty flash is flashing without wiping any other partition except /Cache and /Dalvik). However, sometimes when a ROM gets some major changes, you should clean flash it in order to avoid any possible issue. But if it is required, it will be mentioned by the developer (which means you need to be active on XDA to see the developer's note).
4. Netflix doesn't show up only if the Play store (and the device in terms) is "Uncertified", however on PE, play store is already certified as it is using the fingerprint of Pixel 3 in order to pass safetynet. So, don't worry about it. If you still can't see certain apps on Play store after flashing PE, just download them from apkmirror and sideload them. APKmirror is a legit place and doesn't support pirated/cracked or malware apps.
Rowdyy Ronnie said:
1. Yes. After binding the device with your mi account and apply for the bootloader unlock using the MiFlash tool, you need to wait for 72 hours. It will reflect on MiUnlock tool as well.
2. Just download the latest TWRP from here and flash it (Link: https://forum.xda-developers.com/poco-f1/development/recovery-twrp-3-2-3-decryption-t3853004) and no need to flash DFE (Disable ForceEncryption). Don't worry about it being unofficial. Even though it's unofficial, it is the best solution for us as of now.
A piece of advice: Never use a decrypted device if you are concerned about the security of your device. Infact, never flash anything suggested by anyone without cross checking the authenticity of the file. You will come across many users suggesting you to flash this and that when the fact is,they are afraid to try on their own and rather want you to be the guinea pig.
3. When a new update comes in, you will get notified automatically. Or there is an option on settings to check for new updates. Just download the update and dirty flash it on TWRP (Dirty flash is flashing without wiping any other partition except /Cache and /Dalvik). However, sometimes when a ROM gets some major changes, you should clean flash it in order to avoid any possible issue. But if it is required, it will be mentioned by the developer (which means you need to be active on XDA to see the developer's note).
4. Netflix doesn't show up only if the Play store (and the device in terms) is "Uncertified", however on PE, play store is already certified as it is using the fingerprint of Pixel 3 in order to pass safetynet. So, don't worry about it. If you still can't see certain apps on Play store after flashing PE, just download them from apkmirror and sideload them. APKmirror is a legit place and doesn't support pirated/cracked or malware apps.
Click to expand...
Click to collapse
Thank you for all the detailed information. One last question, I've heard of problems of Pocophone not supporting Widevine L3 which caused Netflix (and others) to stream at a lower quality, and I've read somewhere that Xiaomi might be trying to get that problem fixed. Would this problem affect Pixel Experience if I had it installed on the Pocophone? If so, and Xiaomi fixed the issue in an update, would I be able to get the fix without reverting back to the stock rom?
lixoman100 said:
Thank you for all the detailed information. One last question, I've heard of problems of Pocophone not supporting Widevine L3 which caused Netflix (and others) to stream at a lower quality, and I've read somewhere that Xiaomi might be trying to get that problem fixed. Would this problem affect Pixel Experience if I had it installed on the Pocophone? If so, and Xiaomi fixed the issue in an update, would I be able to get the fix without reverting back to the stock rom?
Click to expand...
Click to collapse
To be honest, I still don't believe when Xiaomi says they will make Poco widevine L3 supported. If they do something like this, it will be amazing. But till then, I won't believe them. And 540p is not that bad anyway. If the device had an AMOLED display, you would realize that 540p is actually quite good which doesn't consume lot of data and still gives a pleasurable viewing experience. And if Xiaomi manages to rollout supoort for WV L3, all other custom ROMs need yo depend on Xiaomi if they release the source code. Just like Xiaomi didn't release the source code of their face unlock feature. Hence, custom roms are using Google face unlock which is a disaster.
Rowdyy Ronnie said:
To be honest, I still don't believe when Xiaomi says they will make Poco widevine L3 supported. If they do something like this, it will be amazing. But till then, I won't believe them. And 540p is not that bad anyway. If the device had an AMOLED display, you would realize that 540p is actually quite good which doesn't consume lot of data and still gives a pleasurable viewing experience. And if Xiaomi manages to rollout supoort for WV L3, all other custom ROMs need yo depend on Xiaomi if they release the source code. Just like Xiaomi didn't release the source code of their face unlock feature. Hence, custom roms are using Google face unlock which is a disaster.
Click to expand...
Click to collapse
Thank you again for all the information :good:
Have a nice day.
This bloke on youtube thinks he has it rooted.. maybe fake though..
The fact that the video says that you cannot update Magisk as the bootloader is still locked makes me think it might be legit..
Considering it is all done within the Android OS it is probably safe to try.. you might just have to factory reset if it causes issues.
Another option?
{Mod edit: Link removed}
Looks interesting, this phone would appeal to me more if I could root it.
If the root does work then how could you unroot it or would installing updates get rid of it and you need to root again?
I think root is possible, but until now I have not been able to find out exactly whether the Fastboot is locked or not. it is my first OPPO and so I have no experience with OPPO. even if it's BBK. it's not an OP 8. We can only hope that someone might want to open it here. But from the root on youtube and other websites I would be careful. I also couldn't find any firmware for the flash via MSM tool or download tool ... so at the moment with an unbrick it is not possible to restore it.
__NBH__ said:
Looks interesting, this phone would appeal to me more if I could root it.
If the root does work then how could you unroot it or would installing updates get rid of it and you need to root again?
Click to expand...
Click to collapse
Factory reset should revert if the apps dont have revert option.
I'd like to see them show rooting an X2 Pro, rather than an A5s (CPH1909)
ordered one anyway... first phone without root in 11 years.. i hope i made the right decision.
It depends what you root for I guess. For me I currently root for adaway, viper, substratum themes and to change my font plus I recently run a module for various tweaks.
I used viper for my old wireless earbuds, I recently got new ones which sounds great without viper. Lots of apps now have a dark mode and I hear this phone has a beta mode that can turn other apps dark. Not changing font I can live with and the tweaks module is fun but not essential. Adaway I will miss. But for the first time in a while I'm not so fussed about root. I understand some people like it because you can flash ROMs when the device gets older. I survived for 18 months with a Samsung S8 plus without root so I know I can do it!
I need to decide whether to pre order the phone today or I miss out on the pre order bonus, I like it but don't think I can trade in my 7 pro, I love it a bit too much.
First and foremost adblock though you can do that without root. Second Sony Music magisk module for Android Auto. Third to debloat. 4th for some advanced Tasker tasks. I'm pretty sure I can get workarounds for most
Sage said:
This bloke on youtube thinks he has it rooted.. maybe fake though..
The fact that the video says that you cannot update Magisk as the bootloader is still locked makes me think it might be legit..
Considering it is all done within the Android OS it is probably safe to try.. you might just have to factory reset if it causes issues.
Another option?
{Mod edit: Link removed}
Click to expand...
Click to collapse
I don't see how this can be legit. The video shows a different device and also the rooting tool is for mediatek based devices. The Oppo find x2 pro is based on Qualcomm chipset.
Can anyone confirm if VMOS work this phone? It may be the only way to use root.
Never heard of vmos sounds interesting!
Yeah VMOS is like running VMware or Parellel on Mac. It's easier than rooting an actual android device, but it also gives more battery drain and less intuitive. I have it on my Mate 20 pro, does anyone know if it works on find x2 pro?
Videos been removed. I really wish this phone had working twrp and magisk it'd be literally the ideal phone
I'm just waiting for a oneplus phone with a periscope camera, that will be the one to get as it will be like this phone but with working root.
Yeah miss root. First phone in a decade I have bought without it. Though mostly I use it for adblock though private DNS works very well
Really missing root on this phone. I wish it were available considering the Snapdragon processor
EE
So far, i have been able to Enable USB Debugging and OEM Unlocking, this on the EE Network. Seems there is no TWRP Build Avail for the X2 Pro Yet. And i am unaware of any other way of Flashing the Magisk Zip Safely any other way.
I have also patched the boot IMG with magisk but there is no way to flash the file.
The recovery accepts only ozip files?
bhomie28 said:
I have also patched the boot IMG with magisk but there is no way to flash the file.
The recovery accepts only ozip files?
Click to expand...
Click to collapse
How did you manage to Patch the Boot IMG?
Thanks Man!
I download the OTA ozip file from oppo. Decrypted the ozip, extracted the boot image & patch it with magisk manager:laugh:
Easy going but how I can flash the file:crying:
Hello very friendly helping people!
Im a 10 year iPhone user, but over time i came to hate all the restrictions and so i got myself a K30 Ultra and later today it should finally arrive!
Unfortunately i found out that it doesnt check the Google SafetyNet thingy and i can't use Google Pay with it. That kinda sucks, I never thought about stuff like this on iOS, but I'm confident there is a solution for it.
I found out about rooting my device, but it somehow isn't possible because of the Mediatek chip. But then I also found out that apperenty there IS a way to use the program/thingy that makes the phone pass SafetyNet (Magisk) without the need of a custom ROM.
I'm sorry if im confusing words like rooting im very noobish about all this.
So here are my questions in short form:
1. Can I make Google Pay Work in any way on my Redmi K30 Ultra?
2. Does this also affect my banking apps (I'm using DKB and Kontist) and can this be solved, too?
3. Could you link me some guides how to do it?
4. Is there any danger doing it (like deleting my phone if it doesnt work) and is there a possibility to safe my device on the PC or something like this to be safe?
5. Are their any safety concerns doing "it" (not sure what the solution will be) and should I install an anti virus program on the device? I just read about the cerberus trojan and its kinda scary. I think iOS systems were always pretty safe against those.
6. Anything else i need to know?
Thank you so much! I appreciate it a lot that there is a place where i can go to get help on those things! <3
Google Pay and any other banking apps refuse to work when a rooted Android gets detected by them. BTW: SafetyNet API doesn't purely check whether the device's Android is rooted, as the API is designed to check the overall integrity of device's Android.
jwoegerbauer said:
Google Pay and any other banking apps refuse to work when a rooted Android gets detected by them. BTW: SafetyNet API doesn't purely check whether the device's Android is rooted, as the API is designed to check the overall integrity of device's Android.
Click to expand...
Click to collapse
Hey, thanks for your post!
Are you implying that there is no way around that and its doomed to forever not work on my device?
To clarify things: SafetyNet is run by an app that has implemented this API, it's not run by Android OS itself. Yes, Magisk allows you to lever out this test by manipulating device's fingerprint so you will possibly be able to use Google Pay etc.pp
FYI: Any app not having SafetyNet API implemented easily can check whether Android got rooted / tampered or not. The app simply runs functions like
Code:
isRootNative
isDetectedDevKeys
isDetectedTestKeys
isFoundBusyboxBinary
isFoundDangerousProps
isFoundHooks
isFoundResetprop
isFoundSuBinary
isFoundWrongPathPermission
isFoundXposed
isNotFoundReleaseKeys
isPermissiveSelinux
isSuExists
isMagiskSUExists
isFoundMagisk
isFoundRootCloakingApps
what can't get prevented by Magisk.
jwoegerbauer said:
Yes, Magisk allows you to lever out this test by manipulating device's fingerprint so you will possibly be able to use Google Pay etc.pp
Click to expand...
Click to collapse
Ok, perfect. Would you be able to link me to a guide that shows me how to install Magisk on my device? It has a Mediatek chip so a custom ROM isn't possible (as far as I understand).
Mirardt said:
Ok, perfect. Would you be able to link me to a guide that shows me how to install Magisk on my device? It has a Mediatek chip so a custom ROM isn't possible (as far as I understand).
Click to expand...
Click to collapse
How to install Magisk without a Custom ROM is explained here.
If a Custom ROM like TWRP isn't officially made public for your device then you have to compile TWRP at your own.
This is TWRP and Magisk for the latest firmware on the K30 Ultra. https://mifirm.net/downloadtwrp/166
---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------
Google Pay on a rooted device with Magisk installed /is/ possible, my Galaxy Note 9 with Dr. Ketan's ROM works with Google Pay and I believe it's due to the CTS Profile fix which is available in its ROM Tool app. So there's going to be some way to make it work with the K30 Ultra.
JaboJG said:
This is TWRP and Magisk for the latest firmware on the K30 Ultra. https://mifirm.net/downloadtwrp/166
Click to expand...
Click to collapse
Oh wow how cool is that, that is custom for the K30 ultra
And do I install that with the guide linked above or do I need some certain skill and experience to do that. It says it isn't tested yet. If I do a mirror of my phone before nothing really bad can happen right?
Google Pay on a rooted device with Magisk installed /is/ possible, my Galaxy Note 9 with Dr. Ketan's ROM works with Google Pay and I believe it's due to the CTS Profile fix which is available in its ROM Tool app. So there's going to be some way to make it work with the K30 Ultra.
Click to expand...
Click to collapse
Nice!!!
Yeah the only think that failed SafetyNet Test is the "CTS profile match". But I can't use those roms for my K30 ultra, right, so I just do it with Magisk?
Thanks so much!!
You need to unlock your bootloader with the Mi Unlock tool then flash TWRP over fastboot, and in TWRP make the appropriate backups and flash Magisk. There's many guides and it's relatively straight forward.
K30 Ultra is basically a brand new phone, it's like a month old. It'll be a while but keep an eye on XDA Forums, on the internet, and on YouTube. Somebody will eventually describe or figure out how to fix the CTS Profile.
I think I'm not gonna modify mine and I'll just wear my Apple Watch to use it for contactless payments.
JaboJG said:
You need to unlock your bootloader with the Mi Unlock tool then flash TWRP over fastboot, and in TWRP make the appropriate backups and flash Magisk. There's many guides and it's relatively straight forward.
K30 Ultra is basically a brand new phone, it's like a month old. It'll be a while but keep an eye on XDA Forums, on the internet, and on YouTube. Somebody will eventually describe or figure out how to fix the CTS Profile.
I think I'm not gonna modify mine and I'll just wear my Apple Watch to use it for contactless payments.
Click to expand...
Click to collapse
Alright, so I read 12384 guides and had a very tiny sense of it. The Mi Unlock tool stopped me, though, and now I'll have to wait another 6 days.
As I understood it, my data will be erased, but can be just be restored by MIUI if backed up before. I'm gonna let you know how it worked after I'll do it in about a week.
Probably I won't have to patience to wait. Google Pay is a really nice to have, but neither voLTE, nor voWifi works on my device, so I for sure have do hack that some weird way, because i have no mobile network at all at home and absolutely need voWifi.
Thank you very much for your kind help! <3
No problem at all.
I'm not sure if Wifi-Calling (voWifi) works with my carrier as I've turned it on with the carrier and in the phone, and it doesn't seem to be making calls over wifi. Not a big deal for me though as I've got Unlimited calls with my carrier.
Please let us know if and when you do flash the TWRP as I'd like feedback before flashing it myself.
Do your banking apps refuse to work or is it only google pay that fails due to the safetynet fail?
JaboJG said:
No problem at all.
I'm not sure if Wifi-Calling (voWifi) works with my carrier as I've turned it on with the carrier and in the phone, and it doesn't seem to be making calls over wifi. Not a big deal for me though as I've got Unlimited calls with my carrier.
Please let us know if and when you do flash the TWRP as I'd like feedback before flashing it myself.
Click to expand...
Click to collapse
Yeah, me too, but I have a very bad connection in my flat so I do need voWifi anyway. I will let you know and hope I won't brick my device. But as I understand it, bricking the device just by flashing twrp is very unlikely, right?
MerlijnD said:
Do your banking apps refuse to work or is it only google pay that fails due to the safetynet fail?
Click to expand...
Click to collapse
Only Google Pay, both of my banking apps work perfectly. I couldnt scan the security bar code though, some internal google app wouldn't allow it. So i had to put in both the (very long) idendification and security numbers in manually.
Alright thanks. Another thing im interested in is if Snapchat works when safetynet fails. Did you do any tests regarding that?
MerlijnD said:
Alright thanks. Another thing im interested in is if Snapchat works when safetynet fails. Did you do any tests regarding that?
Click to expand...
Click to collapse
Not using Snapchat, but I just installed it and it starts without problems. Didn't made an account though.
So I'm gonna be able to flash twrp and Magisk in exactly 14 hours and have some questions i would really appreciate an answer to <3
Using this: https://mifirm.net/downloadtwrp/166
1. The thing i want to flash first is twrp and it is the file called "recovery.img" in the downloaded folder, is that correct?
2. Just flashing twrp is "relatively" safe and if I do a backup and the device bricks by installing Magsik after, i can recover it through twrp, correct?
3. Should I not install todays new security update to MIUI or does that not matter at all?
edit: 4. Do I need/want to have "USB debugging", "Install via USB" and "USBebugging (Security Settings)" enabled or just "OEM unlocking"?
Thank you so much! I'm very nervous since i didn't read any experiences of rooting the K30 Ultra before and I'm scared of killing it.
Hey Mirardt, good luck. Let us know how you get on!
1. Yeah, you'll use fastboot to flash the recovery.img for TWRP.
2. Do a full backup with TWRP and you should be safe.
3. Doesn't matter, it's just the September Android security update.
4. Yeah turn on USB Debugging and connect your phone to your computer - it will ask you if you want to allow this computer to debug your phone, choose accept and always (or something similar to those words.) Do this before flashing TWRP.
Mirardt said:
So I'm gonna be able to flash twrp and Magisk in exactly 14 hours and have some questions i would really appreciate an answer to <3
Using this: https://mifirm.net/downloadtwrp/166
1. The thing i want to flash first is twrp and it is the file called "recovery.img" in the downloaded folder, is that correct?
2. Just flashing twrp is "relatively" safe and if I do a backup and the device bricks by installing Magsik after, i can recover it through twrp, correct?
3. Should I not install todays new security update to MIUI or does that not matter at all?
edit: 4. Do I need/want to have "USB debugging", "Install via USB" and "USBebugging (Security Settings)" enabled or just "OEM unlocking"?
Thank you so much! I'm very nervous since i didn't read any experiences of rooting the K30 Ultra before and I'm scared of killing it.
Click to expand...
Click to collapse
JaboJG said:
Hey Mirardt, good luck. Let us know how you get on!
1. Yeah, you'll use fastboot to flash the recovery.img for TWRP.
2. Do a full backup with TWRP and you should be safe.
3. Doesn't matter, it's just the September Android security update.
4. Yeah turn on USB Debugging and connect your phone to your computer - it will ask you if you want to allow this computer to debug your phone, choose accept and always (or something similar to those words.) Do this before flashing TWRP.
Click to expand...
Click to collapse
Hey Jabo, nice, I'm gonna do just that! Just for clarification, I use Mi Unlock Tool first, THEN twrp, then backup, then magisk?
I'll let you know and thanks for the good luck!
edit: so the command would be "fastboot flash recovery recovery.img", right?
I'm VERY sorry for the noobish questions.
I'm going to quickly use this thread to ask how to actually unlock the K30 Ultra Bootloader. I did everything the guides said, but Mi Unlock still doesn't recognize the phone when it's plugged in. Any Advice?
Hey guys (especially JaboJG). quick update: Flashing twrp and Magsik both just worked perfectly. no brick. Thanks for your help!!
The only issue is that it didnt help in passing Google Safety Check. I tried almost everything there is and will post my logs of MagiskHide Props in their thread soon.
Also, now some apps don't work anymore because they detect the root. I hope we will find a fix.
macrett said:
I'm going to quickly use this thread to ask how to actually unlock the K30 Ultra Bootloader. I did everything the guides said, but Mi Unlock still doesn't recognize the phone when it's plugged in. Any Advice?
Click to expand...
Click to collapse
No idea, sorry. It just worked for me.
Hey folks
Xperia XZ1 (Canada) G8343 per topic header.
I recently unlocked my BL following the Sony instructions to run Lineage OS on my phone. Needless to say this has caused some challenges with apps like Google Play, Netflix, and banking apps that need a verified Android device that passes SafetyNet. Magisk has not helped at all, though I confess I am not 100% convinced I have it installed correctly.
Not a huge issue outside of those Apps though.
I have searched high and low for instructions on how to lock the BL again by flashing the phone with stock firmware etc. Seems odd, but also indicates not possible. Thought to check here with the big brains at XDA to see if I have missed anything obvious.
Basically I want to take my phone back to factory state.
Appreciate your help in advance if you can.
Swaziboy said:
Hey folks
Xperia XZ1 (Canada) G8343 per topic header.
I recently unlocked my BL following the Sony instructions to run Lineage OS on my phone. Needless to say this has caused some challenges with apps like Google Play, Netflix, and banking apps that need a verified Android device that passes SafetyNet. Magisk has not helped at all, though I confess I am not 100% convinced I have it installed correctly.
Not a huge issue outside of those Apps though.
I have searched high and low for instructions on how to lock the BL again by flashing the phone with stock firmware etc. Seems odd, but also indicates not possible. Thought to check here with the big brains at XDA to see if I have missed anything obvious.
Basically I want to take my phone back to factory state.
Appreciate your help in advance if you can.
Click to expand...
Click to collapse
Maybe just change your way of thinking and directly think of bypassing safetynet.
jjgvv said:
Maybe just change your way of thinking and directly think of bypassing safetynet.
Click to expand...
Click to collapse
Care to elaborate on that any? From my research bypassing it is increasingly difficult as Google has worked to include more advanced tech in the platform.
Install magisk and activate magisk hide.
Download and install Magisk Hide Props Config module in magisk, use this module to install XZ1 fingerprint.