Dear All,
I am using the Pixel 5 with Android 13 Build No: TQ1A.230105.001 and I rooted by flashed the image from Magisk app through ADB.
I checked and the phone said ROOTED and I cant grant access to apps but when I change font by any app, it isn't work and I copy in Root Explorer, I can't change the button "MOUNT R/W".
What can I do now? Should I re-root or flash again???
Thank you and waiting for your help.
Some new versions of android restrict it, and you have to do so through recovery.
Arealhooman said:
Some new versions of android restrict it, and you have to do so through recovery.
Click to expand...
Click to collapse
can I install TWRP on Andoird 13???
dpn025 said:
can I install TWRP on Andoird 13???
Click to expand...
Click to collapse
Yes. You Amy be able to set your system to rw through stock recovery, take a look if you can mount it.
Arealhooman said:
Yes. You Amy be able to set your system to rw through stock recovery, take a look if you can mount it.
Click to expand...
Click to collapse
please help me, I can't understand it.
do you have atock recovery? Or TWRP?
Arealhooman said:
do you have atock recovery? Or TWRP?
Click to expand...
Click to collapse
I'm still stock recovery.
Boot into stock recovery. Take a photo for me. If you can’, just tell me if there’s a option that starts with “mount” and what does it say?
From Android 10 and above, the system has changed to one Super Partition. This means that the system cannot be mounted as R/W as it's Read-only by nature.
There is a tool Universal SystemRW that supposedly converts the Read-only to R/W. I haven't tried it personally but it looks very promising.
swangjang said:
From Android 10 and above, the system has changed to one Super Partition. This means that the system cannot be mounted as R/W as it's Read-only by nature.
There is a tool Universal SystemRW that supposedly converts the Read-only to R/W. I haven't tried it personally but it looks very promising.
Click to expand...
Click to collapse
No, TWRP can mount too. And stock recovery for some devices
Root explorer is screwed up for some pixel ROMs including lineage so I don't know about stock. It will crash when trying to read many files, specifically text files you should normally be able to read or edit. It's working on the latest pixel experience ROM but crashed on two other roms I was trying
dpn025 said:
please help me, I can't understand it.
Click to expand...
Click to collapse
use material file manager. It's the only one that seems to be working right now
Related
Hello,
I rooted my device and installed AdAway,
Everytime I reboot I lose the blocking functionality.
How do I fix that?
Thanks
EDIT: https://forum.xda-developers.com/mate-9/help/ro-rooted-mate9-t3564231
bel3atar said:
Hello,
I rooted my device and installed AdAway,
Everytime I reboot I lose the blocking functionality.
How do I fix that?
Thanks
EDIT: https://forum.xda-developers.com/mate-9/help/ro-rooted-mate9-t3564231
Click to expand...
Click to collapse
If you used PHH to root, open the zip, open config.txt in a text editor, change "verity" to "noverity". Save and flash again.
You might need to flash back your stock boot image before flashing.
Edit: That link you posted there is full of misinformation.
Keeping system RO is best. It's not read-only/read-write that's causing it to roll back hosts.
I did that, but the flash fails with error 1.
I can't even install the original superuser-r310-beta.zip
bel3atar said:
I did that, but the flash fails with error 1.
I can't even install the original superuser-r310-beta.zip
Click to expand...
Click to collapse
Did you restore your stock boot image first?
Post your full build if you don't have it.
MHA/LON-LxxCxxxBxxx
ante0 said:
did you restore your stock boot image first?
Post your full build if you don't have it.
Mha/lon-lxxcxxxbxxx
Click to expand...
Click to collapse
mha-l29c432b182
bel3atar said:
mha-l29c432b182
Click to expand...
Click to collapse
https://mega.nz/#!VhlkmQbJ!sgq55_e6cf78VwxmKvUHD7f23aJnnWUwdOehft2Lpdk
Flash In TWRP to Boot partition, then flash your superuser zip with "noverity" in config.txt
ante0 said:
https://mega.nz/#!VhlkmQbJ!sgq55_e6cf78VwxmKvUHD7f23aJnnWUwdOehft2Lpdk
Flash In TWRP to Boot partition, then flash your superuser zip with "noverity" in config.txt
Click to expand...
Click to collapse
Solved, thank you =)
One more question: Will I still get OTA updates or will I have to apply them manually?
bel3atar said:
Solved, thank you =)
One more question: Will I still get OTA updates or will I have to apply them manually?
Click to expand...
Click to collapse
If you don't modify anything in /system, /product or /vendor you should still get OTA.
For example: installing Busybox modifies /system. Viper4Android modifies /vendor and /system.
If you need Busybox you should consider switching to Magiskv12. Its busybox is systemless (Doesn't modify anything).
And with Magisk you can use Android Pay and PokemonGO (and other apps that use SafetyNet).
MagiskHide is a little buggy on Mate 9, and other Huawei devices that use Nougat. If you enable it, fingerprint and pin will break after you reboot. If you just enable, run Android Pay, and disable after you will be fine.
I just installed the latest Android 10 for Pixel/Sailfish. I have use Magisk to root using the Boot Image Patching, as TWRP doesn't works yet for Android 10/Sailfish. I have enabled systemless host in Magisk and rebooted.
Now I have installed the latest version of FX File manager. When I goto root (granted root) within FX, I click mount R/W, it said that the folder is read-only. I had the same issue with EX file explorer.
I mainly want to edit a few files in /etc/permissions/ and move a few apps to system apps
What can I do to get the mount R/W to work? These are my normal steps on Android 9 to get this to work, I am unsure if I am missing anything
From my limited understanding and a few brief trawls of Google you can't write to system on 10 as you could in 9 or lower. Probably a job for a magisk module/terminal and edit it in a systemless way so to speak.
You can fastboot boot twrp 3.3.1-0, decryption works, it may show mounting errors but it does work, been using it to flash magisk and ROMs on my sailfish without problem.
junglism93 said:
From my limited understanding and a few brief trawls of Google you can't write to system on 10 as you could in 9 or lower. Probably a job for a magisk module/terminal and edit it in a systemless way so to speak.
You can fastboot boot twrp 3.3.1-0, decryption works, it may show mounting errors but it does work, been using it to flash magisk and ROMs on my sailfish without problem.
Click to expand...
Click to collapse
This is what I suspect also. I do know 10 is quite new.
I have been able to flash Magisk no issues. Root access is fine (adblock, titanium backup works). HOwever, I can't seem to mount r/w using a file explorer. I suspect this has to do with the way Google have upgraded its security, but I'm not fully sure.
pennywaltz said:
I just installed the latest Android 10 for Pixel/Sailfish. I have use Magisk to root using the Boot Image Patching, as TWRP doesn't works yet for Android 10/Sailfish. I have enabled systemless host in Magisk and rebooted.
Now I have installed the latest version of FX File manager. When I goto root (granted root) within FX, I click mount R/W, it said that the folder is read-only. I had the same issue with EX file explorer.
I mainly want to edit a few files in /etc/permissions/ and move a few apps to system apps
What can I do to get the mount R/W to work? These are my normal steps on Android 9 to get this to work, I am unsure if I am missing anything
Click to expand...
Click to collapse
You can't do anything. As you've been told before, the system partition can't be edited by the user on Android 10. Whether it is because of security or something else I don't know, but it's not possible at the moment.
Here is the explanation:
https://www.xda-developers.com/android-q-storage-access-framework-scoped-storage/
There are some workarounds detailed in this article but I haven't been able to get them to work.
Hi all,
I have a Huawei Mate 9 (MHA-L09C432) with EMUI 9.1 on it and an unlocked booloader with Magisk installed.
Because I want to modify root settings I would like to have full root access...
Is there a method now to get full root access with EMUI 9.1?
Thank you for your answers in advance!
htcdesire-hd said:
Hi all,
I have a Huawei Mate 9 (MHA-L09C432) with EMUI 9.1 on it and an unlocked booloader with Magisk installed.
Because I want to modify root settings I would like to have full root access...
Is there a method now to get full root access with EMUI 9.1?
Thank you for your answers in advance!
Click to expand...
Click to collapse
You have Magisk and that's the root. 'Classic/full root' is no more possible because of EROFS. Only systemless root functionality provided by Magisk
zgfg said:
You have Magisk and that's the root. 'Classic/full root' is no more possible because of EROFS. Only systemless root functionality provided by Magisk
Click to expand...
Click to collapse
Ok thats bad, hoped that there is a solution now...
Is that EMUI related or will no future Android phone have "real" root?
But a SW downgrade would bring back real root?
htcdesire-hd said:
Ok thats bad, hoped that there is a solution now...
Is that EMUI related or will no future Android phone have "real" root?
But a SW downgrade would bring back real root?
Click to expand...
Click to collapse
EROFS means read-only file system, developed by Huawei, used in EMUI 9.1 and 10.
Google is pushing that system must not be changed, and it is similarly enforced in other phones with Android 10.
Read discussions in Magisk and Magisk Canary threads on XDA, even better topjohnwu's (developer of Magisk) blog on Reddit, to understand in which direction (systemless) it goes and why.
By HiSuite you should be able to downgrade from EMUI 9.1 to 9.0 (prior to EROFS)
zgfg said:
EROFS means read-only file system, developed by Huawei, used in EMUI 9.1 and 10.
Google is pushing that system must not be changed, and it is similarly enforced in other phones with Android 10.
Read discussions in Magisk and Magisk Canary threads on XDA, even better topjohnwu's (developer of Magisk) blog on Reddit, to understand in which direction (systemless) it goes and why.
By HiSuite you should be able to downgrade from EMUI 9.1 to 9.0 (prior to EROFS)
Click to expand...
Click to collapse
Ok thanks for the explanation. Doesn't sound good for me... But maybe there will be a solution like reformatting in future I hope to get "real" root!
Thanks for the tip, I will do so.
Good I will do that!
htcdesire-hd said:
Ok thanks for the explanation. Doesn't sound good for me... But maybe there will be a solution like reformatting in future I hope to get "real" root!
Thanks for the tip, I will do so.
Good I will do that!
Click to expand...
Click to collapse
It's unlikely that you'd be able to change the partition types back to ext4 - one of the other things to note about EROFS is that at least some of the contents are compressed, and as a result the system partition is smaller than it was with ext4. It's likely the same is true of all of the other partitions though I haven't checked. But in any case, there likely isn't enough physical space to store a repacked EMUI 9.1 image set in the new partitions.
irony_delerium said:
It's unlikely that you'd be able to change the partition types back to ext4 - one of the other things to note about EROFS is that at least some of the contents are compressed, and as a result the system partition is smaller than it was with ext4. It's likely the same is true of all of the other partitions though I haven't checked. But in any case, there likely isn't enough physical space to store a repacked EMUI 9.1 image set in the new partitions.
Click to expand...
Click to collapse
Ok I understand...
I saw that you can unpack the EROFS partition in a virtual environment, remove or modify system files and repack it...
But that's to complicated for my purpose...
irony_delerium said:
It's unlikely that you'd be able to change the partition types back to ext4 - one of the other things to note about EROFS is that at least some of the contents are compressed, and as a result the system partition is smaller than it was with ext4. It's likely the same is true of all of the other partitions though I haven't checked. But in any case, there likely isn't enough physical space to store a repacked EMUI 9.1 image set in the new partitions.
Click to expand...
Click to collapse
I tried to downgrade but it failed (probably because I have a Magisk patched recovery).
So I tried to install the stock recovery but I can't boot into Fastboot... (I shut down my phone, hold down volume and plugged in USB ... also rebooting to fastbood via ADB did not work -> always booting to system).
What can I do about that? Factory reset? Or is this a known issue with EMUI 9.1?
htcdesire-hd said:
I tried to downgrade but it failed (probably because I have a Magisk patched recovery).
So I tried to install the stock recovery but I can't boot into Fastboot... (I shut down my phone, hold down volume and plugged in USB ... also rebooting to fastbood via ADB did not work -> always booting to system).
What can I do about that? Factory reset? Or is this a known issue with EMUI 9.1?
Click to expand...
Click to collapse
Let it boot to system and use Magisk manager to uninstall it. The 9.1 fastboot doesn't pay attention to the button state if it thinks it should be booting into recovery, and that flag persists as long as stock recovery hasn't booted.
irony_delerium said:
Let it boot to system and use Magisk manager to uninstall it. The 9.1 fastboot doesn't pay attention to the button state if it thinks it should be booting into recovery, and that flag persists as long as stock recovery hasn't booted.
Click to expand...
Click to collapse
Unfortunatelly Magisk says "stock backup does not exist" when I try to uninstall ...
htcdesire-hd said:
Unfortunatelly Magisk says "stock backup does not exist" when I try to uninstall ...
Click to expand...
Click to collapse
Then instead, take your stock recovery image, and from a PC:
adb push recovery_ramdisk.img /sdcard/recovery_ramdisk.img
adb shell
su
dd if=/sdcard/recovery_ramdisk.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
irony_delerium said:
Then instead, take your stock recovery image, and from a PC:
adb push recovery_ramdisk.img /sdcard/recovery_ramdisk.img
adb shell
su
dd if=/sdcard/recovery_ramdisk.img of=/dev/block/bootdevice/by-name/recovery_ramdisk
Click to expand...
Click to collapse
Thank you very much, that worked!
I was not able to do that via ADB but I used the Android App "Termius" which has a local terminal.
Now I was able to remove Magisk, downgrade and root my phone again decently!
One last question: how can I prevent update notifications now?
htcdesire-hd said:
One last question: how can I prevent update notifications now?
Click to expand...
Click to collapse
Code:
adb shell pm disable-user com.huawei.android.hwouc
For that, even root is not required.
And you can always re-enable System Update by:
Code:
adb shell pm enable
com.huawei.android.hwouc
zgfg said:
Code:
adb shell pm disable-user com.huawei.android.hwouc
For that, even root is not required.
And you can always re-enable System Update by:
Code:
adb shell pm enable
com.huawei.android.hwouc
Click to expand...
Click to collapse
Thank you very much, that worked!
htcdesire-hd said:
Thank you very much, that worked!
I was not able to do that via ADB but I used the Android App "Termius" which has a local terminal.
Now I was able to remove Magisk, downgrade and root my phone again decently!
Click to expand...
Click to collapse
Apparently, you had root still working (if I correctly understand your long story).
In that case you could have also flashed stock Recovery by EMUI Flasher apk from post #1 at:
https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
zgfg said:
Apparently, you had root still working (if I correctly understand your long story).
In that case you could have also flashed stock Recovery by EMUI Flasher apk from post #1 at:
https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171
Click to expand...
Click to collapse
Thank you for the tip!
zgfg said:
Code:
adb shell pm disable-user com.huawei.android.hwouc
For that, even root is not required.
And you can always re-enable System Update by:
Code:
adb shell pm enable
com.huawei.android.hwouc
Click to expand...
Click to collapse
I have one problem after setting up my phone again completely:
I can't connect to WIFI hotspots anymore... It tries to connect but ends in "connection timed out"...
What could cause this problem?
I restored my WIFI connections via Titanium Backup, could that cause a problem?
htcdesire-hd said:
I have one problem after setting up my phone again completely:
I can't connect to WIFI hotspots anymore... It tries to connect but ends in "connection timed out"...
What could cause this problem?
I restored my WIFI connections via Titanium Backup, could that cause a problem?
Click to expand...
Click to collapse
I would not restore by Titanium (specially if changing a firmware) but lby the stock Backup app (or HiSite, it's PC counterpart).
It can also backup/restore WiFi connections and with that I even successfully transfered my WiFi passwords from P9 Oreo to Mate 9 Pie
(You can select which parts you want to restore and if there are incompatible settings, it will not offer that part for restoring to the new Huawei device/firmware)
zgfg said:
I would not restore by Titanium (specially if changing a firmware) but lby the stock Backup app (or HiSite, it's PC counterpart).
It can also backup/restore WiFi connections and with that I even successfully transfered my WiFi passwords from P9 Oreo to Mate 9 Pie
(You can select which parts you want to restore and if there are incompatible settings, it will not offer that part for restoring to the new Huawei device/firmware)
Click to expand...
Click to collapse
I didn't make a backup with HiSuite...
But I solved the problem by resetting the network settings:
Settings -> System -> Reset -> Reset Network Settings
Hello people,
I have unlocked my phone yesterday and installed Magisk and root explorer.
I would like to replace the files in /system/fonts to change the default fonts. I tried to flash a twrp zip with new fonts and also manually tried to replace the fonts. But the system cannot be mounted as r/w in root explorer even after granting root permissions and flashing twrp zip does nothing. Is there any way to overcome this issue to mount system as r/w?
I mean what is the point of rooting if we cannot modify system!
Thanks!
Normal ... This is a new Android 10 restriction ... The system partition can no longer be mounted for writing, even with root!
On my old Redmi Note 4 (Rom Havoc Android 10), I had managed to change the fonts by copying the file from TWRP.
Many modifications are starting to be systemlessly. Like viper4android and others. The worst is not being able to flash system/vendor images in recovery.
wopr33 said:
Normal ... This is a new Android 10 restriction ... The system partition can no longer be mounted for writing, even with root!
On my old Redmi Note 4 (Rom Havoc Android 10), I had managed to change the fonts by copying the file from TWRP.
Click to expand...
Click to collapse
Thanks for the information. I tried to copy file in TWRP but it is giving an error. Could you please let me know how you have done it?
I don't know how TWRP works for the Poco X3, but for the Redmi Note 4 I copied the file using the built-in explorer, with no errors.
I think you need to activate the system partition in R/W in TWRP.
htcmusic said:
Thanks for the information. I tried to copy file in TWRP but it is giving an error. Could you please let me know how you have done it?
Click to expand...
Click to collapse
Sadly nothing will work for you rn. As far as i know, all devices launching with Android 10 use "dynamic partitions" wherein all partitions are inside Super.img and /system, /vendor, /product no longer writeable (Read only).
IMHO you're better off learning how to make a Magisk module yourself. Look at this guide from topjohnwu: https://topjohnwu.github.io/Magisk/guides.html
Slim K said:
Sadly nothing will work for you rn. As far as i know, all devices launching with Android 10 use "dynamic partitions" wherein all partitions are inside Super.img and /system, /vendor, /product no longer writeable (Read only).
IMHO you're better off learning how to make a Magisk module yourself. Look at this guide from topjohnwu: https://topjohnwu.github.io/Magisk/guides.html
Click to expand...
Click to collapse
Thank you for the info.
I finally was able to change the font using magisk modules as mentioned here: https://github.com/nongthaihoang/custom_font_installer
htcmusic said:
Thank you for the info.
I finally was able to change the font using magisk modules as mentioned here: https://github.com/nongthaihoang/custom_font_installer
Click to expand...
Click to collapse
I am very interested (to replace emojis).
I looked at the Magisk module page, it talks about flashing the ZIP, so I need TWRP ? For the moment, I didn't install it.
wopr33 said:
I am very interested (to replace emojis).
I looked at the Magisk module page, it talks about flashing the ZIP, so I need TWRP ?
Click to expand...
Click to collapse
You don't need twrp to install a Magisk module. You can do that through the Magisk Manager just as easily.
wopr33 said:
I am very interested (to replace emojis).
I looked at the Magisk module page, it talks about flashing the ZIP, so I need TWRP ? For the moment, I didn't install it.
Click to expand...
Click to collapse
I just installed the magisk module with custom fonts in internal storage as mentioned in the github page. It was magical, I was trying to replace the fonts for the whole day and it didn't work. Somehow this magisk module does the job.
Android 10 has this messed up file system that does not allow any writing of the system files. While I have root neither Root Explorer or any other third party apk can force it over. I also cannot install any application with Root Explorer. What's the good of root if we can't actually mod our own system files?
Also, since debloating everything and removing google everything, I can't use instacart anymore. It says I need Google Play Services. This NEVER was an issue on my Moto G7 Power.
At the very least is there a tool where I can unpack Super.Sparsechunk files and then repack them so I can flash them as stock via fastboot. All I want to do is delete the stock ringtones on this phone and replace them with my own .ogg files (as I've done on every Moto I've ever had). Thanks.
You have to root it before using R/W
One Ace is easy to root though
Unlock bootloader and patch boot.img with Magisk app, and flash it
mingkee said:
You have to root it before using R/W
One Ace is easy to root though
Unlock bootloader and patch boot.img with Magisk app, and flash it
Click to expand...
Click to collapse
I did all that. It still will not go to R/W. This seems to be an Android 10 issue.
Here you go my friend. Enjoy!
lebigmac said:
Here you go my friend. Enjoy!
Click to expand...
Click to collapse
Your method as of now is not working.
It's working fine on my Xiaomi (which is A slot only device) but you are right. The current version is not as universal yet as I'd like it to be. There seems to be an lpmake error at the very end of the script for those with A/B slot device.
Don't worry I am working very hard on identifying and fixing the error.
Soon your system shall be RW!