Hello,
just wanted to ask If you think that in the near future a face unlock patch or Magisk Module for instnce will be revealed. That would be super helpful
No
Related
Hello friends recently i got update about open beta i face bootloop when i instal xposed farmwork due to new security patch can anyone help me to fix it bez no one can use rooted mobile without xposed module so plz fix it as soon as possible and some given a tutorial about that link but it totally fake not working i tried several time
http://forum.xda-developers.com/one...tall-xposed-rooting-op3-beta-7-t3502638/page2
Check the Xposed marshmallow thread, rovo has a test zip floating around in there that some are reporting as working with the November security patch. Read through the last few pages of the thread.
Hello there, I am currently using CyanogenMod 13 with Xposed and Root. Is there a way to apply the September security patch for BlueBorne on this ROM? I really don't want to leave Xposed because of this.
ExpertMC said:
Hello there, I am currently using CyanogenMod 13 with Xposed and Root. Is there a way to apply the September security patch for BlueBorne on this ROM? I really don't want to leave Xposed because of this.
Click to expand...
Click to collapse
Development for Marshmallow is obsolete. You'll have to do it yourself if that's the case. Build cm13 and add in the security patches. Every other developer are working on Android Oreo so I highly doubt that anyone if going to take on such project. As I said, learning to do it yourself is your best bet.
Arju said:
Development for Marshmallow is obsolete. You'll have to do it yourself if that's the case. Build cm13 and add in the security patches. Every other developer are working on Android Oreo so I highly doubt that anyone if going to take on such project. As I said, learning to do it yourself is your best bet.
Click to expand...
Click to collapse
Magisk seems very interesting, is it stable for this device? Is it compatible with non-stock ROMs?
ExpertMC said:
Magisk seems very interesting, is it stable for this device? Is it compatible with non-stock ROMs?
Click to expand...
Click to collapse
Magisk works great for our device. There are also different modules that can be flashed for Magisk as there were for xposed. Magisk is great as it does not trip safetynet and some apps that won't work because they detect root would work when having magisk installed. I suggest you too google "Magisk xda" and go to the subforum and read as much as possible to learn more about it.
Magisk module to fix broken Face Unlock on April and May builds.
https://drive.google.com/open?id=1qtfVb3celjrlT4qQYX_fdfBUCPsp9hbP
Is there a working module for android 12?
Same. Looking for the same module for Android 12.
I have searched every forum in XDA but no success, I want to unlock my Pixel 4 xl bootloader but the OEM unlock grayed out in developer option, please I want to know if there's any way to bypass the protection and unlock bootloader and root my phone, please help, using a non root device is like a prison to me, I am willing to pay if someone can remote unlock it for me, I want to know if it's possible
The same for Google Pixel 4 XL
- https://developers.google.com/android/images
-
https://twitter.com/i/web/status/1559537708959154177
Do not update to the Android 13 your Google Pixel 4 XL if you need to roll back the firmware or root your device.
At least for now
Defencore said:
View attachment 5696081
The same for Google Pixel 4 XL
- https://developers.google.com/android/images
-
https://twitter.com/i/web/status/1559537708959154177
Do not update to the Android 13 your Google Pixel 4 XL if you need to roll back the firmware or root your device.
At least for now
Click to expand...
Click to collapse
Where do you see the new ARB applies to the Pixel 4 XL?
Lughnasadh said:
Where do you see the new ARB applies to the Pixel 4 XL?
Click to expand...
Click to collapse
Sorry, I phrased it wrong. Campaign in the Android 13 for Pixel 4 XL, as well as for Pixel 6 Pro, the ability to unlock OEM was disabled, because of which it is impossible to flash or roll back. Today I updated my Pixel 4 from Android 12 to 13 and it immediately became impossible to unlock the OEM.
Defencore said:
Sorry, I phrased it wrong. Campaign in the Android 13 for Pixel 4 XL, as well as for Pixel 6 Pro, the ability to unlock OEM was disabled, because of which it is impossible to flash or roll back. Today I updated my Pixel 4 from Android 12 to 13 and it immediately became impossible to unlock the OEM.
Click to expand...
Click to collapse
I'm still on 13 beta, please is there a way to go back to my former 12.1
Or am I doomed?
LexPanda said:
I have searched every forum in XDA but no success, I want to unlock my Pixel 4 xl bootloader but the OEM unlock grayed out in developer option, please I want to know if there's any way to bypass the protection and unlock bootloader and root my phone, please help, using a non root device is like a prison to me, I am willing to pay if someone can remote unlock it for me, I want to know if it's possible
Click to expand...
Click to collapse
Did you see my thread ?? I unlocked this device.
Defencore said:
View attachment 5696081
The same for Google Pixel 4 XL
- https://developers.google.com/android/images
-
https://twitter.com/i/web/status/1559537708959154177
Do not update to the Android 13 your Google Pixel 4 XL if you need to roll back the firmware or root your device.
At least for now
Click to expand...
Click to collapse
That's for pixel 6 mate.
Hello guys. I rooted my Pixel 7 almost immediately, and I think I disabled dm-verity and AVB while unlocking my bootloader on Android Flash Tool. How can I check my dm-verity and AVB's actual status? And, most important thing, should I keep them disabled when I'm flashing the upcoming December OTA (I'm not planning to flash any custom kernel in the near future btw), or I can enable them again without losing my data?
BetaPix said:
Hello guys. I rooted my Pixel 7 almost immediately, and I think I disabled dm-verity and AVB while unlocking my bootloader on Android Flash Tool. How can I check my dm-verity and AVB's actual status? And, most important thing, should I keep them disabled when I'm flashing the upcoming December OTA (I'm not planning to flash any custom kernel in the near future btw), or I can enable them again without losing my data?
Click to expand...
Click to collapse
If you don't keep them disabled when updating, just know you will have to wipe when you disable them again, so it's up to you.
How to check if disabled:
[Kernel][04.05.2023][Android 13.0.0 Stable]Kirisakura_Raviantah 1.0.4 for Pixel 7/Pro aka "Pantah"
Kirisakura-Kernel for the Pixel 7/Pro Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Google Pixel 7 Pro aka Cheetah and the Pixel 7 aka Panther, together Pantah. I would appreciate if everybody that flashes the kernel...
forum.xda-developers.com
Release android-13.0.0_r11-panther · capntrips/android_external_avb
Contribute to capntrips/android_external_avb development by creating an account on GitHub.
github.com
Lughnasadh said:
If you don't keep them disabled when updating, just know you will have to wipe when you disable them again, so it's up to you.
How to check if disabled:
[Kernel][04.05.2023][Android 13.0.0 Stable]Kirisakura_Raviantah 1.0.4 for Pixel 7/Pro aka "Pantah"
Kirisakura-Kernel for the Pixel 7/Pro Hello everyone, To keep it short: Here is Kirisakura - Kernel for the Google Pixel 7 Pro aka Cheetah and the Pixel 7 aka Panther, together Pantah. I would appreciate if everybody that flashes the kernel...
forum.xda-developers.com
Release android-13.0.0_r11-panther · capntrips/android_external_avb
Contribute to capntrips/android_external_avb development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Everything I needed Thank you!