Database Info

[Q] [HELP] SuperSU installed by don't have root access

Hello,
So I messed up a bit... I have absolutely no idea what to do, I have SuperSU and TWRP installed on my OPO but I don't seem to have root access...
What should I do? (I'll be happy to provide any extra needed information)
EDIT: THANKS FOR THE HELP THIS IS WORKING
(I'll be happy to provide anyone with help)

oscarbo said:
Hello,
So I messed up a bit... I have absolutely no idea what to do, I have SuperSU and TWRP installed on my OPO but I don't seem to have root access...
What should I do? (I'll be happy to provide any extra needed information)
Click to expand...
Click to collapse
did you update the binaries in supersu?

Doo Doo said:
did you update the binaries in supersu?
Click to expand...
Click to collapse
Well I updated to 44R hoping that I could try again with a fresh install.

oscarbo said:
Well I updated to 44R hoping that I could try again with a fresh install.
Click to expand...
Click to collapse
Install latest Su , then in SU settings remove " Respect CM Root Settings " reboot

Cholerabob said:
Install latest Su , then in SU settings remove " Respect CM Root Settings " reboot
Click to expand...
Click to collapse
Is that the UPDATE-SuperSU-v1.99r3 ?
Also, do you think I can put TWRP and Root it again using the toolkit? (Or any other way that won't wipe my phone)

oscarbo said:
Is that the UPDATE-SuperSU-v1.99r3 ?
Also, do you think I can put TWRP and Root it again using the toolkit? (Or any other way that won't wipe my phone)
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=eu.chainfire.supersu&hl=en
Rooting wont erase anything. Drop the toolkit learn to do it manually, it will save you a lot of headaches. Copy the su file to your phone, reboot into TWRP recovery, install from zip, find and install superSU file. If root does not stick, look into SU settings and remove " Respect CM Root Settings " and reboot to system.

Mate 9 L29C185B181 camera not working after decrypting data.

Hello guys, I seriously need help please.
I decrypted my data. Everything is working perfectly with the exception of the Huawei camera.
1.The icon has change to android green icon
2.It flashes when u open
3 . 3rd party camera app like camera 360 which I just Install from playstore also not working, only showing me black screen.
Will be glad if someone can restore my camera back:crying:.
Am on firmware L29C185B181 please.

golastic said:
Hello guys, I seriously need help please.
I decrypted my data. Everything is working perfectly with the exception of the Huawei camera.
1.The icon has change to android green icon
2.It flashes when u open
3 . 3rd party camera app like camera 360 which I just Install from playstore also not working, only showing me black screen.
Will be glad if someone can restore my camera back:crying:.
Am on firmware L29C185B181 please.
Click to expand...
Click to collapse
Did you flash some other models boot image?

ante0 said:
Did you flash some other models boot image?
Click to expand...
Click to collapse
Everything I flashed was extracted from my firmware version... update_data_full_public.zip and update_full_hw_meafnaf.zip.

golastic said:
Everything I flashed was extracted from my firmware version... update_data_full_public.zip and update_full_hw_meafnaf.zip.
Click to expand...
Click to collapse
Camera is not part of those zips so that can't be it. Could you backup your current boot image in twrp and send to me?

Maybe Flash public and hw in twrp to fix the camera?

ante0 said:
Camera is not part of those zips so that can't be it. Could you backup your current boot image in twrp and send to me?
Click to expand...
Click to collapse
Sure Sir.....
https://mega.nz/#!8JNX3CwZ!PjSDO9c4mNWh5_ddKANmLNqLPRo7hyk_of5lAZThPUU (from partitions backup apk)
https://mega.nz/#F!BZ0XRb6Z!Y8QkOaw6K8dtuzuysgImNA (from twrp)

You can revert to stock anytime using this tool https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108/page74

golastic said:
Sure Sir.....
https://mega.nz/#!8JNX3CwZ!PjSDO9c4mNWh5_ddKANmLNqLPRo7hyk_of5lAZThPUU
Click to expand...
Click to collapse
Something is up with your boot images, none can be unpacked.
Try flashing https://mega.nz/#!lhVTmbqQ!gIf4Tu4JC3pdzz-T7OAxi4wr3PQySkqdTgclkOkEU2E
Then re-root without rebooting.
Which root are you using by the way?

ante0 said:
Something is up with your boot images, none can be unpacked.
Try flashing https://mega.nz/#!lhVTmbqQ!gIf4Tu4JC3pdzz-T7OAxi4wr3PQySkqdTgclkOkEU2E
Then re-root without rebooting.
Which root are you using by the way?
Click to expand...
Click to collapse
Magisk 13.3 alongside superuser-r310-beta.zip

golastic said:
Magisk 13.3 alongside superuser-r310-beta.zip
Click to expand...
Click to collapse
Ah. Phh is probably why it won't unpack then.
I'm not sure then. If re-flashing B181 hw and public doesn't fix it, it's probably the boot image (seeing as regular camera apps don't work either something is up with the drivers).
I'd try with SuperSU/phh too or update to b182+ if possible and flash regular magisk 13.3, without phh.

ante0 said:
Ah. Phh is probably why it won't unpack then.
I'm not sure then. If re-flashing B181 hw and public doesn't fix it, it's probably the boot image (seeing as regular camera apps don't work either something is up with the drivers).
I'd try with SuperSU/phh too or update to b182+ if possible and flash regular magisk 13.3, without phh.
Click to expand...
Click to collapse
Thx sir but huawei firmware finder is only tell me current firmware to be C185B181.
Will be glad to link me to me 182 .
Thx

golastic said:
Thx sir but huawei firmware finder is only tell me current firmware to be C185B181.
Will be glad to link me to me 182 .
Thx
Click to expand...
Click to collapse
Correct. Latest is 181. I guess you could try installing Magisk, it will reboot instantly in twrp if it can't mount image as loop. 182+ is only because most firmware got loop support in 182. (First) B182 for C432 was released 12th of April and yours was released 24th of April, so it might work.
Or rebrand to C636.

golastic said:
Thx sir but huawei firmware finder is only tell me current firmware to be C185B181.
Will be glad to link me to me 182 .
Thx
Click to expand...
Click to collapse
New build for C185: B184.
It says BC185, but checking VERSION.mbn in update.zip confirms it's for C185:
MHA-L29C185B184
There was actually a B182 too for C185, released as BC185 too.
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=MHA-L29BC185&firmware_page=0

ante0 said:
New build for C185: B184.
It says BC185, but checking VERSION.mbn in update.zip confirms it's for C185:
MHA-L29C185B184
There was actually a B182 too for C185, released as BC185 too.
http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=MHA-L29BC185&firmware_page=0
Click to expand...
Click to collapse
Can Install the firmware through Huawei finder apk and will it restore my camera please. I love my phone but without the camera working is makes my headache.
Have tried all u ask me by restoring stock boot loader and flashing superSu but the camera is still not working. It flashing :crying::crying::crying::crying:

golastic said:
Can Install the firmware through Huawei finder apk and will it restore my camera please. I love my phone but without the camera working is makes my headache.
Have tried all u ask me by restoring stock boot loader and flashing superSu but the camera is still not working. It flashing :crying::crying::crying::crying:
Click to expand...
Click to collapse
Before updating, have you tried restoring boot without rooting and see if that fixes camera?
Try this one, I removed verity and replaced fileencryption with encryptable so it doesn't encrypt your /data again.
https://mega.nz/#!lhE2zLSR!ngNY3bXKMS_eKizjmfnKHbFgVSVnp94dgCXnxuL_G_0
If it doesn't do anything, continue below.
Currently, https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Other ways are Firmware Finder or OTA, but both those require your IMEI to be approved for the update.
And Funky Huawei, which you need to pay for.
It will wipe /data when/if you decrypt again so make sure to make a backup of /data first, or backup apps with Titanium Backup or which backup app you use.
Basically download the Base zip, MHA zip and Windows or linux zip from https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Extract all to the same folder (hwota) and merge if it asks.
Then download:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v91627/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...hw_meafnaf/update_full_MHA-L29_hw_meafnaf.zip
http://update.hicloud.com:8180/TDS/...27/f1/full/public/update_data_full_public.zip
Put all in the "update" folder in the hwota folder you extracted before.
Rename update_full_MHA-L29_hw_meafnaf.zip to update_all_hw.zip
Rename update_data_full_public.zip to update_data_public.zip
Put phone in fastboot mode (download mode) and run update.bat (windows) or update.sh (linux)
Pick "Same brand update" when it asks, and "Script update directory".
When it's done your bootloader will be locked again so you need to unlock it if you want to root again.
You will be able to install regular Magisk 13.3 now without superuser (phh)

ante0 said:
Before updating, have you tried restoring boot without rooting and see if that fixes camera?
Try this one, I removed verity and replaced fileencryption with encryptable so it doesn't encrypt your /data again.
https://mega.nz/#!lhE2zLSR!ngNY3bXKMS_eKizjmfnKHbFgVSVnp94dgCXnxuL_G_0
If it doesn't do anything, continue below.
Currently, https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Other ways are Firmware Finder or OTA, but both those require your IMEI to be approved for the update.
And Funky Huawei, which you need to pay for.
It will wipe /data when/if you decrypt again so make sure to make a backup of /data first, or backup apps with Titanium Backup or which backup app you use.
Basically download the Base zip, MHA zip and Windows or linux zip from https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Extract all to the same folder (hwota) and merge if it asks.
Then download:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v91627/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...hw_meafnaf/update_full_MHA-L29_hw_meafnaf.zip
http://update.hicloud.com:8180/TDS/...27/f1/full/public/update_data_full_public.zip
Put all in the "update" folder in the hwota folder you extracted before.
Rename update_full_MHA-L29_hw_meafnaf.zip to update_all_hw.zip
Rename update_data_full_public.zip to update_data_public.zip
Put phone in fastboot mode (download mode) and run update.bat (windows) or update.sh (linux)
Pick "Same brand update" when it asks, and "Script update directory".
When it's done your bootloader will be locked again so you need to unlock it if you want to root again.
You will be able to install regular Magisk 13.3 now without superuser (phh)
Click to expand...
Click to collapse
Resolved the camera issue by following the last steps by flashing the 3 zip files......have unlocked bootloader and installed twrp 3.1.0.1 and trying to install magisk 13.3 but it always stuck at huawei logo.
Have also tried rooting but it seems only SuperSU2.82EMUI5noverityEnforcing works and do i need to follow the steps of formatting data to get it decyrpted?
Currently on MHA-L29C185B182 at the moment.
Thx @ante0 for your kind gesture.Appreciated

golastic said:
Resolved the camera issue by following the last steps by flashing the 3 zip files......have unlocked bootloader and installed twrp 3.1.0.1 and trying to install magisk 13.3 but it always stuck at huawei logo.
Have also tried rooting but it seems only SuperSU2.82EMUI5noverityEnforcing works and do i need to follow the steps of formatting data to get it decyrpted?
Currently on MHA-L29C185B182 at the moment.
Thx @ante0 for your kind gesture.Appreciated
Click to expand...
Click to collapse
My bad.
If you're using official Magisk 13.3, that's why it's not booting. Since your data partition is encrypted, and Magisk removes the encryption flag, it tries to boot without decrypting. So it ends in a boot loop.
Use this: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE (this one just doesn't force remove encryption)
Or decrypt first, then flash HW and Public and official Magisk 13.3.
But yes, to decrypt you need to format data.

ante0 said:
My bad.
If you're using official Magisk 13.3, that's why it's not booting. Since your data partition is encrypted, and Magisk removes the encryption flag, it tries to boot without decrypting. So it ends in a boot loop.
Use this: https://mega.nz/#!I4FQzbyA!gBZelHmD3lGGwzGISUXkf7GQTUAq5i785d_qPHQOaVE (this one just doesn't force remove encryption)
Or decrypt first, then flash HW and Public and official Magisk 13.3.
But yes, to decrypt you need to format data.
Click to expand...
Click to collapse
Is there another way of flashing the 3 zip files without running through pc cuz i dont know whats happening. Am done with with everything working with Magisk and data encrypted but what i have realised this around is my development option is not working along with debugging mode. Also am not able to install apk aside from playstore....Due to that adb in command prompt is not working cuz debugging mode is disables.
In fastboot mode am only able to check device status and reboot device.Id you send a commnd to flash an image it response failed....

golastic said:
Is there another way of flashing the 3 zip files without running through pc cuz i dont know whats happening. Am done with with everything working with Magisk and data encrypted but what i have realised this around is my development option is not working along with debugging mode. Also am not able to install apk aside from playstore....Due to that adb in command prompt is not working cuz debugging mode is disables.
In fastboot mode am only able to check device status and reboot device.Id you send a commnd to flash an image it response failed....
Click to expand...
Click to collapse
If you can't get in to dev options, wipe dalvik/art & cache in twrp, it could fix playstore as well.
If you can't enable adb, try enable disable a few times and remove USB cable between. I always have to do that the first time.
You can actually do everything from twrp to install firmware. But you'd have to check the hwota.sh file for commands... There are a few you must execute.
And is camera working now again?

ante0 said:
Before updating, have you tried restoring boot without rooting and see if that fixes camera?
Try this one, I removed verity and replaced fileencryption with encryptable so it doesn't encrypt your /data again.
https://mega.nz/#!lhE2zLSR!ngNY3bXKMS_eKizjmfnKHbFgVSVnp94dgCXnxuL_G_0
If it doesn't do anything, continue below.
Currently, https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Other ways are Firmware Finder or OTA, but both those require your IMEI to be approved for the update.
And Funky Huawei, which you need to pay for.
It will wipe /data when/if you decrypt again so make sure to make a backup of /data first, or backup apps with Titanium Backup or which backup app you use.
Basically download the Base zip, MHA zip and Windows or linux zip from https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Extract all to the same folder (hwota) and merge if it asks.
Then download:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1366/g104/v91627/f1/full/update.zip
http://update.hicloud.com:8180/TDS/...hw_meafnaf/update_full_MHA-L29_hw_meafnaf.zip
http://update.hicloud.com:8180/TDS/...27/f1/full/public/update_data_full_public.zip
Put all in the "update" folder in the hwota folder you extracted before.
Rename update_full_MHA-L29_hw_meafnaf.zip to update_all_hw.zip
Rename update_data_full_public.zip to update_data_public.zip
Put phone in fastboot mode (download mode) and run update.bat (windows) or update.sh (linux)
Pick "Same brand update" when it asks, and "Script update directory".
When it's done your bootloader will be locked again so you need to unlock it if you want to root again.
You will be able to install regular Magisk 13.3 now without superuser (phh)
Click to expand...
Click to collapse
ante0 said:
If you can't get in to dev options, wipe dalvik/art & cache in twrp, it could fix playstore as well.
If you can't enable adb, try enable disable a few times and remove USB cable between. I always have to do that the first time.
You can actually do everything from twrp to install firmware. But you'd have to check the hwota.sh file for commands... There are a few you must execute.
And is camera working now again?
Click to expand...
Click to collapse
Yes Camera is working good and it looks like they have added a new feature in the camera app for b182 called MOVING PICTURE which add sound whiles you capture.I use to love that when i was using S5.
Now after careful observation about the instruction u gave me,am able to install B182 ,have decyrpted data ,have magisk 13.3 running without any issue.
I jux wanna say thanks so much for your patience with me...Much appreciated:good::good::good::good::good:
BTW which of the models will u recommend if want to rebrand?:

Is root available on EMUI9. 1?

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

Can't modify system even after root

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.

[Help] - Can't R/W on Root Explorer after root by Magisk

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