Search This thread

m0han

Senior Member
Apr 30, 2012
5,570
2,681
I have tested with incognito mode in chrome. But there is no issue I have seen.
Maybe(?) something still remains to be fixed. I rebooted and tested again. Incognito mode screenshot 'no go' in Chrome. Works with Kiwi.
 

Attachments

  • SS_20230325_093906.jpg
    SS_20230325_093906.jpg
    60.8 KB · Views: 60
  • SS_20230325_094601.jpg
    SS_20230325_094601.jpg
    147.8 KB · Views: 59

m0han

Senior Member
Apr 30, 2012
5,570
2,681
I see the thread title has been edited to reflect the latest version v7.0. I also see there is a v7.0 stable(?) build attached to the OP (md5: a2afab13f46a890a88b44825c9439543) apart from the v7.0beta (md5: 576c48e37a207b6ebc6ef15552877b08) that was given in an earlier post for testing. It would be good for all users if @mehedihjoy makes announcements of such changes so that more and more people can test the beta as well as the stable builds.
 

m0han

Senior Member
Apr 30, 2012
5,570
2,681
I have tested with incognito mode in chrome. But there is no issue I have seen.
You probably tested with your v7.0 stable release. I did now and Incognito mode screenshot works in Chrome. Several reboots later, the bootloop issue seems to be fixed for good - for me, at least. Thank you for the fixes.

Edit: Screenshots working in GPay too. 👍
 

Attachments

  • SS_20230325_113128.jpg
    SS_20230325_113128.jpg
    339.5 KB · Views: 42
Last edited:
  • Like
Reactions: mehedihjoy
Mar 3, 2021
5
0
Hi, I tried the latest v7.0 (sorry for late feedback).. after several reboots the phone booted and is working fine for manual reboot. Screenshots and all working fine. However, I'm still unable to login to Xiaomi Account and Revoke authorization of system apps.

Device: Redmi Note 11T 5G (evergo)
Android: 12 (MIUI 13.0.6.0)
 

Attachments

  • Screenshot_2023-03-25-15-57-12-423_com.android.settings.jpg
    Screenshot_2023-03-25-15-57-12-423_com.android.settings.jpg
    281.5 KB · Views: 42

mehedihjoy

Member
Aug 24, 2022
31
48
Hi, I tried the latest v7.0 (sorry for late feedback).. after several reboots the phone booted and is working fine for manual reboot. Screenshots and all working fine. However, I'm still unable to login to Xiaomi Account and Revoke authorization of system apps.

Device: Redmi Note 11T 5G (evergo)
Android: 12 (MIUI 13.0.6.0)
But I have no problem like this.
Device : Redmi Note 7 Pro(violet)
OS : MIUI 14 based on Android 13
 

Attachments

  • Screenshot_2023-03-25-18-49-34-561_com.xiaomi.account.jpg
    Screenshot_2023-03-25-18-49-34-561_com.xiaomi.account.jpg
    204.6 KB · Views: 48
Last edited:

Kh007i

New member
Jan 25, 2019
2
0
First of all, great work.
I've installed V6.0 and it's breaking Xiaomi's Find Device on MIUI 14 (xiaomi.eu) with Android 13.
Here's the report summary:
Code:
java.lang.RuntimeException: An error occurred while executing doInBackground()
    at android.os.AsyncTask$4.done(Unknown Source:27)
    at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:381)
    at java.util.concurrent.FutureTask.setException(FutureTask.java:250)
    at java.util.concurrent.FutureTask.run(FutureTask.java:269)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
    at java.lang.Thread.run(Thread.java:1012)
Caused by: java.util.NoSuchElementException
    at android.os.HwBinder.getService(Native Method)
    at android.os.HwBinder.getService(Unknown Source:1)
    at vendor.xiaomi.hardware.mtdservice.V1_2.StaticMTservice.getService(Unknown Source:4)
    at com.miui.cloudservice.alipay.provision.support.KeyStoreServiceV30.widevineGetVersion(Unknown Source:0)
    at com.miui.cloudservice.alipay.provision.v.isAvailable(Unknown Source:6)
    at com.miui.cloudservice.alipay.provision.a.a(Unknown Source:858)
    at com.miui.cloudservice.alipay.provision.v.a(Unknown Source:12)
    at com.miui.cloudservice.alipay.provision.x.b(Unknown Source:24)
    at com.miui.cloudservice.alipay.provision.x.a(Unknown Source:83)
    at com.miui.cloudservice.alipay.provision.w.a(Unknown Source:8)
    at com.miui.cloudservice.alipay.provision.w.doInBackground(Unknown Source:2)
    at android.os.AsyncTask$3.call(Unknown Source:20)
    at java.util.concurrent.FutureTask.run(FutureTask.java:264)
    ... 3 more
I've tried V7.0 and Find device still broken
 

Listy2021

Senior Member
Jan 28, 2012
549
322
Do you flash the uninstaller through Magisk or TWRP in recovery? I've disabled the module through Magisk in normal boot due to it causing a bootloop the other day and now want it gone from my phone

@mehedihjoy
 

skr1p7k1dd

Member
Dec 4, 2017
12
2
Does NOT work on Oneplus 8 Pro on Android 12. It puts the phone into a bad state and apps are crashing left and right. Luckily I could safely remove it and go back to normal.
 
  • Like
Reactions: CyberstormFox

Top Liked Posts

  • There are no posts matching your filters.
  • 30
    For so long everyone is looking for Disable Flag Secure Magisk Module. But can't find it anywhere. Earlier Xposed Module was released. This is the first time I brought the Disable Flag Secure Magisk Module. By flashing it you can take screenshot from locked profile of Facebook. You can also take screenshots from apps/pages where taking screenshots is prohibited. No LsPosed/Xposed required for this. So flash and enjoy.😁

    #requirements:
    * android 8+
    * deodexed rom

    #all_changelogs:
    * included apktool 7.0
    * removed zipsigner, keycheck
    * added support for Samsung devices
    * added support for DRM-Protected content(like- Netflix, Amazon Prime, Disney+ etc)
    * fixed problems with DRM-Protected content
    * fixed bootloop problem successfully

    For any kind of help-
    My Facebook Profile: Md Mehedi Hasan
    6
    Hi, this module is based on my Dynamic Installer, I don't require you to attach credits for the installer because it's free to use, but yeah when the patching logic was taken directly from other projects (General Samsung Patcher), and the only thing that really annoying is that in the print my BlassGO username was abbreviated to "BG" (I consider it disrespectful)

    Mainly waited for a fix to the final problem mentioned

    And just as a recommendation, it would be ideal to update the installer base, since that is a very old version and with flaws
    3
    Fyiuh finally found it tested working on ppui Android 12
    3
    In my internal storage there isn't any unistaller.
    It has been removed. Because it doesn't need.
    3
    Now use this version[3.0] and final release.
    All bugs have been fixed.
    Don't Use Old Version.
    Flash & Enjoy😁
    For Any Help:-
    My Facebook Profile : Mehedi H Joy

    View attachment 5711693View attachment 5711695
    Pixel 6 Pro on A13, working great!