on my Poco F2 Pro and I was able to install TWRP correctly as well as Magisk canary
Only, the root does not seem complete and the modification of build.prop to 0755 via TWRP is not possible.
So I end up with a rooted device but half.
Ex: AdAway only works with a rooted device works perfectly.
but Root Explorer.apk encounters an error message when switching to R / W which indicates:
"Warning: the modification of the permissions was not successful. Please note that some file systems (SD card for example) do not allow changes to the permissions"
I have the same problem
Since Android 10 it's not possible. You can use Magisk modules (i.e. MagiskHide Props).
https://forum.xda-developers.com/pixel/help/mount-rw-android-10-magisk-20-4-t4081043/post82266003
Related
I assume here you have custom recovery like twrp and Magisk (Required only in Method 2) Installed in your device, I have made it simple, crsipy and concise so that noob can get rescued from bootloop
Note : This guide is helpful only of bootloop is caused by Xposed modules, Magisk modules, System or User App.
[emoji637]?*?**?*?*?*?*?*?***
1)Reboot to Recovery
2)Go to Recovery File Manager and Browse to /data/app/
3)Find there package name of xposed module,user app causing bootloop like package name of famous xposed module Xposed Edge is "com. Jozien.xposededge"(just remind app name and you will get it) and swipe to deleter that folder
4)You are done, just reboot your device
*[emoji638]?*?***?*?*?*?*?*?**
(Recommend For Xposed Users and Systemless Mods)
1)Download Magisk Manager For Recovery by @VR25 From Magisk Respo.
2)Flash via Magisk or Recovery (works even after you are stuck in bootloop)
3) Now Go to Recovery Terminal
4)Type the fallowing Command
"/data/media/mm" without quotes
5)Type "a" without quotes to enable or disable magisk module)
6)Now type keyword (first two, three letters matching with magisk module and enter to disable it
7)Enter Again to Complete Procedure
Suppose An xposed module is causing bootloop (Assuming you have Ed Xposed Framework Installed)
Just type Ed or Xposed keyword to disable This module and other module similarly and you are done
Uraniam9 said:
I assume here you have custom recovery like twrp and Magisk (Required only in Method 2) Installed in your device, I have made it simple, crsipy and concise so that noob can get rescued from bootloop
Note : This guide is helpful only of bootloop is caused by Xposed modules, Magisk modules, System or User App.
Here are the steps to get out from a Bootloop
*METHOD 1*
1)Reboot to Recovery
2)Go to Recovery File Manager and Broswe to /data/app/
3)Find there package name of xposed module,user app causing bootloop like package name of famous xposed module Xposed Edge is "com. Jozien.xposededge"(just remind app name and you will get it) and swipe to deleter that folder
4)You are done, just reboot your device
* METHOD 2*
Recommend For Xposed Users
1)Download Magisk Manager For Recovery by @VR25 From Magisk Respo.
2)Flash via Magisk or Recovery (works even after you are stuck in bootloop)
3) Now Go to Recovery Terminal
4)Type the fallowing Command
"/data/media/mm" without quotes
5)Type "a" without quotes to enable or disable magisk module)
6)Now type keyword (first two, three letters matching with magisk module and enter to disable it
Suppose An xposed module is causing bootloop (Assuming you have Ed Xposed Framework Installed)
Just type Ed or Xposed keyword to disable This module and other module similarly and you are done
Click to expand...
Click to collapse
You may add that you need to enter twice = to do what Ctrl+C as said in the app. In the last step
Added
Thanks. I just included this thread in my signature
Thank you so very much, Mr. uraniam9. You just saved me a hell lot of work restoring my phone. God bless you.
I just can't make Edxposed work, system hangs on the Samsung animated logo. Device is SM-J730G/DS running stock official with Magisk 20.3 and latest TWRP for my device. I'm getting this problem flashing both sandhook or that other one I forgot it's name.
My device is Poco F2 Pro with xiaomi.eu android 11 rom.
I have flashed Magisk 21.4. But when open Root Explorer, I can't mount r/w on /root.
My install steps is:
Flash Magisk after flash rom.
Open Magisk, install, selcet and patch a file
fastboot flash boot patched.img
In Magisk, RE have been granted root. But it is not real root because I can't edit system app.
Is there anything wrong?
BTW, when I flash MIUI Global rom + Pixel Experience or Fluid rom, I can get real root.
Hello.
History.
1. I install lineage recovery
2. I install the lineage.
3. I reinstall stock (Android 11), I didn't like lineage.
4. I want to root and install Magisk.
5. I install recovery TWRP, to get the boot.img
6. I couldn't get the boot.img
7. I use the boot .img of the stock rom I installed to get the patched boot.img.
8. First start root works fine.
9. I try to make a magisk App proxy to hide it.
10. I install Youtube Vanced, I give it root permissions.
11. Reboot and bootloop.
I've tried several stock roms but none of them work, sometimes I try the simple rom, then I patch the boot with magisk because that's how I've seen in other forums that it works but it doesn't work either.
The only room that has served me has been Grapheneos, it installs has bootloop but in the end it starts, but it has no sound and no sensor, gyroscope, light etc...
I think it may be the persist.img is corrupt.
Could someone share a persist.img file that is good to install and try or any other ideas of what else I could try.
Interesting console bugs.
01-19 12:10:43.195 1115 16869 W adsprpcd: vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:883: Warning: apps_std_fopen_with_env failed with 0xd for /mnt/vendor/persist/sensors/registry/registry (Permission denied)
01-19 12:10:43.195 1115 16869 E adsprpcd: vendor/qcom/proprietary/adsprpc/src/apps_std_imp.c:1236::Error: 201: 0 == (nOpenErr = apps_std_fopen_with_env(ADSP_LIBRARY_PATH, ";", name, "r", &ps))
audio_hw_primary: out_write: sound card is not active/SSR state
The solution was like this:
1. I installed grapheneOS, which was the only OS that allowed me to start the phone.
2. I rooted with Magisk
3. Checking the log there was a persistent error and it was permissions
/mnt/vendor/persist/sensors/registry/registry (Permission denied)
4. Enter the shell with the console, (using root) and tried to change the permissions on the mnt folder to the vendor folder, but it did not allow it.
5. Create a new vendor folder with correct permissions and move all files to the new folder.
6. reboot and everything was working fine.
I hope it helps someone else.
Note: very important after making the changes in the folder run the 'sync' command
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Liquidform said:
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Click to expand...
Click to collapse
You could use DFE (If you want unencrypted data) or use magisk module for recovery. to remove unwanted magisk modules
Liquidform said:
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Click to expand...
Click to collapse
There is magisk module which check on start of the phone if any module makes a bootlop and disable it. Magisk Bootloop saver on github
Liquidform said:
Is there any ways to remove Magisk Modules through Custom Recovery on android 12?
Incase we installed a Module that can cause bootloop
As you guys know since android 12
No Custom Recovery was able to decrypt data encryption yet, so we're unable to access the folder that contains Magisk Modules
Click to expand...
Click to collapse
Power phone off completely. Power on and when MIUI logo shows on screen hold volume down button until phone boots, this will disable all magisk modules you have installed. It's called magisk safe mode. You can now enter magisk app and enable modules one by one until you find the culprit.
Sidenote: I upgraded from xiaomi.eu 12.0.6 to 13.0.3 using fastboot. TWRP was unable to decrypt when I booted to recovery to install magisk after update. I rebooted back to MIUI and disabled pin and fingerprint. Rebooted back to TWRP and was able to access data and install magisk from the downloads folder. So try disabling screen lock and see if TWRP is working then.
Well orangefox has magisk manager built in, so modules can be removed with a swipe
you can navigate to data/adb/modules folder in twrp file manager without decryption needed and delete module folder.
worked for me on android 12.
I got stuck at Xiaomi logo after installing some module. The storage is encrypted on Android 12, decryption in recovery is not possible at the moment. So using OrangeFox or deleting /data/... is not possible.
The only solution that worked for me was accessing the safe mode and running this command from adb shell.
magisk --remove-modules
Hello y'all, i want to root my phone, i followed several tutorials and installed image file of twrp v 3.2.3 , lazyflasher.zip and magisk.zip . Tried flshing the twrp image file through fastboot, but it is unable to decrypt my data and is asking for a password, installed a later version of twrp v 3.4.0 and tried the same, it was able to decrypt , Now i succesfully entered TWRP and then i first installed the image file but i was not able to install the ladyflasher.zip(error 1 cannot unpack zip file) so i avoided the lazyflasher step and directly tried installing magisk and it said successful, but when my phone rebooted there was no magisk app and my phone is not rooted! Tried with different versions of magisk like v 16 and v 23 , still no effect. Also instead of magisk zip file i installed supersu zip file and still the result is same ( No supersu app on phone and thus not rooted)!
Reflash Stock ROM to get rid off of all mods you applied so far, then retry.
Issue Solved! Thanks for your tip @xXx yYy , but i solved it! Basically the absence of magisk app is not a problem, i manually installed the magisk manager and basically upgraded the magisk version(I flashed v 16 through twrp, magisk manager required v 23 and above) so i clicked install within the app and boom! root access is granted, crazy but anyways it did work , so issue solved