Hi everyone, I recently unlocked the bootloader and installed twrp and magisk on my g9 plus (android 11)... But something is not right, even though root is working, I don't have any super user privileges, I tested 5 root uninstallers and I couldn't uninstall any apps from the system, and I can't modify the system files (I use solid explorer). I try downgrade to android 10 and flashing a old magisk, but I had no solution...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
JesusChrist<3 said:
Hi everyone, I recently unlocked the bootloader and installed twrp and magisk on my g9 plus (android 11)... But something is not right, even though root is working, I don't have any super user privileges, I tested 5 root uninstallers and I couldn't uninstall any apps from the system, and I can't modify the system files (I use solid explorer). I try downgrade to android 10 and flashing a old magisk, but I had no solution...View attachment 5401949View attachment 5401951
Click to expand...
Click to collapse
It is not that your device is not rooted, the app is showing you it does. Since A10 it was implemented dynamic partitions, so they are dynamically "mounted" and system remains as read/write only, some ROMs can re-implement that mounting the system where usually it is placed, and some TWRPs also can manage with this, you should try using the file browser in-built in TWRP and delete the apps manually.
Related
Hi all, I decided to create this thread because of a little annoying problem.
1) I followed instructions in the ""[GUIDE] Getting started - Unlock->TWRP->root->OTA updates]"" to install TWRP and ROOT my P20 pro.
Everything was OK until this point.
2) My phone found an update in the OTA checking. It can't be installed because of TWRP so I decided to overwrite the TWRP in the recovery_ramdisk with a recovery_nocheck.img
So then, the update was correctly downloaded, the phone reboots normally, I got a screen with an EMUI installing update successfully but the phone found again and again the same update. I got no error about some updates not installed.
Of course if i don't change TWRP, i got an error message in system that an update was not installed.
Something strange, even if i remove TWRP and replace with emui recovery_nocheck, i am still rooted.
I found the update.zip in root folder \data\update. It can be installed manually with no error in TWRP directly or with HRUpdate but all of these don't change the fact that my phone always found the same update in OTA checking. I even desactivate in root (i found this somewhere that you have to rename the file hwouc.apk) the OTA checking but it doesn't work
Any help please. I don't like the red mark notification in settings.
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just update using TWRP, HuRUpdater and firmware file from Firmware Finder. Trying to use OTA while on Root is like looking for a problem.
Hello all,
Lately I wanted to install rom on my moto x4 and altough I'm a bit noob in the process I was confident I could do it properly (did it in the past with a oneplus one and a sony erickson x10mini )
So I've unlocked my my bootloader and I was ready to boot twrp image with adb to finally be able to install twrp and magisk.
but there is the problem,
normally I should see this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But instead I see this
Honestly I look what was the issue here but my skills as a rom installer are not that great so I got stuck there.
Of course I can still use my phone without any issue but I have no idea on how I can install twrp magisk and later on a rom.
Does anybody have an idea what is the issue here ?
Thank you
Seems like your TWRP version was not able to decrypt data partition.
Boot to system and disable encryption for your phone (Lock screen -> none). Boot to recovery again afterwards. Try flashing your zips.
wkn000 said:
Seems like your TWRP version was not able to decrypt data partition.
Boot to system and disable encryption for your phone (Lock screen -> none). Boot to recovery again afterwards. Try flashing your zips.
Click to expand...
Click to collapse
lol honestly didn't think about that, thanks a lot :highfive:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Before I change rom at thet mark "crypto" have result File, after I change rom it only N/A and safetynet fale must to be use props and module to bypass, last time crypto = File is passing easy and not laging
Someone can give me answer, and hot to install magisk with Crypto = File
Thank you For everyone interesting this thread, hope can fix IT.
"Crypto" just reports what kind of encryption your device uses, it's got nothing directly to do with Magisk (that little piece of info is even removed from the app in the recent Canary releases). If your device isn't encrypted (or if Magisk can't tell if it's encrypted) it'll say N/A...
If you want the device to be encrypted you'll find that setting in your ROM somewhere, not Magisk.
Didgeridoohan said:
"Crypto" just reports what kind of encryption your device uses, it's got nothing directly to do with Magisk (that little piece of info is even removed from the app in the recent Canary releases). If your device isn't encrypted (or if Magisk can't tell if it's encrypted) it'll say N/A...
If you want the device to be encrypted you'll find that setting in your ROM somewhere, not Magisk.
Click to expand...
Click to collapse
Oh I got it thank you so much, Now I can tell don't worry about that.
Has anyone successfully fooled safetynet in an emulator? Maybe it'd be enough to block application's calls to it. Way to do this would be:
1. Somehow boot OEM rom or copy init.rc and build.prop
2. get magisk working using https://github.com/shakalaca/MagiskOnEmulator
3. Trick GMS using some combination of EDXPOSED, https://github.com/microg/RemoteDroidGuard and https://github.com/Felixho19/CuckooWithFrida.
Thoughts?
SafetyNet: Google's tamper detection for Android · Yiannis Kozyrakis ~ blog
thoughts on mobile security
koz.io
mcdoe123 said:
Has anyone successfully fooled safetynet in an emulator? Maybe it'd be enough to block application's calls to it. Way to do this would be:
1. Somehow boot OEM rom or copy init.rc and build.prop
2. get magisk working using https://github.com/shakalaca/MagiskOnEmulator
3. Trick GMS using some combination of EDXPOSED, https://github.com/microg/RemoteDroidGuard and https://github.com/Felixho19/CuckooWithFrida.
Thoughts?
SafetyNet: Google's tamper detection for Android · Yiannis Kozyrakis ~ blog
thoughts on mobile security
koz.io
Click to expand...
Click to collapse
I got root to install stable magisk through this tutorial, however I'm looking for a way to get past safetynet as well.
Android 11 (api 30)
Skin - Pixel_3a_API_30_x86
Windows 10 64bits
In the terminal it even shows the change of props. But it doesn't pass the tests
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Do you have any news?
After flashing Magisk 26.0, I got this error, already reflashed it 3 times in recovery mode. (with app and without)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Device: Xiaomi Redmi 9 4/64.
I had the same, try install direct methods
Spartacus500 said:
I had the same, try install direct methods
Click to expand...
Click to collapse
installation fails on flashing ¯\_(ツ)_/¯
you need to go into the magisk app v26 and click install direct installation right after flashing in recovery
im using a mtk device and magisk patching from app doesnt seem to work at all since mtk locks the currently using slot's bootimg as r/o and reverts changes after reboot.
any workarounds?
sd369888 said:
im using a mtk device and magisk patching from app doesnt seem to work at all since mtk locks the currently using slot's bootimg as r/o and reverts changes after reboot.
any workarounds?
Click to expand...
Click to collapse
it just got corrupted after reboot and i had it revert to miui
I have the same problem on Lenovo Tab 4 after updating to 26.1 from a much older version.
I think I'll just leave it as it is, it seems to work OK, I just can't download new modules.
Same with me, after flashing EvolutionX to my Redmi Note 10S. I also ignored this message because I reflashed it a few times, but nothing changed, still appears.
It works great, so there's nothing to do with that I think.