TWRP official app when searching for device doesn't have my device listed and TWRP manager can't detect Twrp does anyone know why this might be?
Also I'm having trouble backing up using twrp it fails with the error code 255? I've tried to unmount data change the time but still fails.
TWRP is not officially released for Mate 9, it's unofficial build/s.
And that error just mean you're encrypted, like Mate 9 is by default.
To remove encryption you'll have to Format - Format Data (This wipes everything including internal sdcard), after this you will have to flash SuperSU 2.82 SR3+, Magisk v14 (14.3+ doesn't remove encryption flag so it won't work without modifying Magisk source) or modify your boot image manually.
And then download and flash Public + HW zip for your firmware from http://pro-teammt.ru/firmware-database/
Dear all,
I'm in quite a dilemma. I have an FRD-L09 with the following environment:
Oreo Firmware (FRD-L09C432B521)
Unlocked FRD and Bootloader
TWRP 3.2.1 from 7to.cn (the one which can mount /system writable) (this one: https://forum.xda-developers.com/ho...p-ish-twrp-3-2-1-honor-9-running-gsi-t3818442)
I did not go the "Fix DataEncryption" way because, to me, it's pretty convenient that nobody is able to access /data even with TWRP, so if the phone gets stolen, my data is protected
I installed Magisk 17.1 and Magisk Manager which worked perfectly fine.
Then I downloaded and installed the corresponding Xposed Module for Magisk (apparently system-less, so Xposed-Uninstaller.zip doesn't work). This resulted in a boot loop.
I'm not able to suppress Xposed loading with the usual "press a device button many times in a row".
If I uninstall Magisk (i.e. flash stock recovery.img extracted from update.app), the system boots up normally, so it's Magisk+Xposed that causes the boot loop
BUT: Now I'm unable to remove the Xposed module from /data/magisk.img because 1. of course I can't access /data from a booted system without root and 2. I can't access /data from TWRP because I want to leave it protected.
Also, the "Fix DataEncryption" option apparently wipes the /data partition which I'd really like to avoid.
With other TWRP releases, I cannot access /data even after entering my lockscreen PIN or the "default_password" as decryption password, so I'm pretty certain that the encryption key is derived by other means - I think I remember reading that it's stored somewhere in hardware, which is also why, for Custom ROMs, encryption on Honor 8 is always an issue.
So does anyone have any clue how I can either access /data from TWRP while keeping it encrypted, or delete magisk.img via any other way?
I'll be happy about any hint!
EdRoxter said:
Dear all,
I'm in quite a dilemma. I have an FRD-L09 with the following environment:
Oreo Firmware (FRD-L09C432B521)
Unlocked FRD and Bootloader
TWRP 3.2.1 from 7to.cn (the one which can mount /system writable) (this one: https://forum.xda-developers.com/ho...-ish-twrp-3-2-1-honor-9-running-gsi-t3818442)
I did not go the "Fix DataEncryption" way because, to me, it's pretty convenient that nobody is able to access /data even with TWRP, so if the phone gets stolen, my data is protected
I installed Magisk 17.1 and Magisk Manager which worked perfectly fine.
Then I downloaded and installed the corresponding Xposed Module for Magisk (apparently system-less, so Xposed-Uninstaller.zip doesn't work). This resulted in a boot loop.
I'm not able to suppress Xposed loading with the usual "press a device button many times in a row".
If I uninstall Magisk (i.e. flash stock recovery.img extracted from update.app), the system boots up normally, so it's Magisk+Xposed that causes the boot loop
BUT: Now I'm unable to remove the Xposed module from /data/magisk.img because 1. of course I can't access /data from a booted system without root and 2. I can't access /data from TWRP because I want to leave it protected.
Also, the "Fix DataEncryption" option apparently wipes the /data partition which I'd really like to avoid.
With other TWRP releases, I cannot access /data even after entering my lockscreen PIN or the "default_password" as decryption password, so I'm pretty certain that the encryption key is derived by other means - I think I remember reading that it's stored somewhere in hardware, which is also why, for Custom ROMs, encryption on Honor 8 is always an issue.
So does anyone have any clue how I can either access /data from TWRP while keeping it encrypted, or delete magisk.img via any other way?
I'll be happy about any hint!
Click to expand...
Click to collapse
Re-install EMUI 8 with eRecovery.
ThePS4Gamer said:
Re-install EMUI 8 with eRecovery.
Click to expand...
Click to collapse
Yeah, I really hoped I could do something without wiping my /data partition, but I guess I'll have to back up my data and do a factory reset and start over...
PS: eRecovery only offers EMUI 5 on the Honor 8 - EMUI 8 is only installable via HiSuite.
EdRoxter said:
Yeah, I really hoped I could do something without wiping my /data partition, but I guess I'll have to back up my data and do a factory reset and start over...
PS: eRecovery only offers EMUI 5 on the Honor 8 - EMUI 8 is only installable via HiSuite.
Click to expand...
Click to collapse
Solution is simple.
Requirement:
TWRP(which Twrp? honor view 10's. Research how to install)
Solution:
-install magisk pached boot img to ramdisk and twrp to recovery_ramdisk
-boot in Twrp
-then navigate to Advance->Terminal
-write below command:
touch /cache/.disable_magisk && chmod 0777 /cache/.disable_magisk && sync && reboot
Behind the scene: It will enable magisk core only mode, then uninstall malfunctioning modules from magisk manager and disable core only mode, reboot and mtv enjoy
spica1234 said:
touch /cache/.disable_magisk && chmod 0777 /cache/.disable_magisk && sync && reboot
Behind the scene: It will enable magisk core only mode, then uninstall malfunctioning modules from magisk manager and disable core only mode, reboot and mtv enjoy
Click to expand...
Click to collapse
Thank you so much! This was exactly was I was looking for, but googling for "disable Magisk boot" and the like didn't bring up any results other than a bunch of tutorials on how to remove Magisk modules from TWRP with uninmod, which obviously didn't work for me because I couldn't mount /data from TWRP.
So.. where do I start..
After I rooted my phone with magisk and twrp -------------------->(I had a qualcomm crashdump crash when I tried to boot from the twrp .img and I found a way around it)
I tried installing some magisk modules.(first time installing a magisk module ever)
2-3 modules later I noticed that some modules should have an app installed after reboot but I didnt saw any new app despite of having no errors in the terminal while installing.
I tried:
--Installing newer beta magisk version (17.2)
--Reinstalling the module
--Complete factory reset with the unbrick tool (msmdownloadtool) and all over again.
--Installing bluspark recovery (and then all over again)
--Installing bluspark kenel (and then all over again)
--Changing data filesystem partition to F2FS (but OOS didnt like it and bootloop)
--Installing the .zip modules from twrp (didnt work) (probably cause of encryption but if I find a new module I want to install I dont want to factory reset every time)
--Installing xXx No limits magisk rom
And I am here to ask for help because I really do not know what to do.
Thank you :/
ps.I am new to this forum so do not take it for granted to know even some basic stuff
First do NOT use f2fs it's junk. Use Google for more information on that file system
Upon installation of magisk system update detects device has been rooted or modified and cant be updated, upon uninstallation still the same but upon flashing stock rom it comes back to normal i need solutions cos systemless su isnt being detected but magisk is being detected
simple001 said:
Upon installation of magisk system update detects device has been rooted or modified and cant be updated, upon uninstallation still the same but upon flashing stock rom it comes back to normal i need solutions cos systemless su isnt being detected but magisk is being detected
Click to expand...
Click to collapse
Your system update requires an unmodified system partition. Magisk modifies system partition, that is why the update detects it.
On the other hand, systemless su does not modify system, hence the name "systemless", that is why the update doesn't detect it.
You won't be able to apply the update while the system partition is modified. Remove Magisk completely, then apply the update, after the update is finished, then root the device again and re-install Magisk.
Sent from my SM-S767VL using Tapatalk
hey i want to install a custom rom (gsi) so i hope some people can help me out
main info: i have a ulefone note 9p with mediatek 6762 (runs with mediatek 6765 android scatter) and android 10.
this twrp is a twrp 3.4.0. built for ulefone note 9p i downloaded from here:
unofficial twrp 3.4.0 Root Ulefone Note 9P - unofficial twrp
download unofficial twrp 3.3.1 root Ulefone Note 9P, user who own Ulefone Note 9P can root it by following the below instructions
unofficialtwrp.com
after going to the painful procedure of unlocking bootloader flashing stock and twrp modified rom + rooting the device
i stuck at the procedure to install a gsi image via twrp.
i already know that the device must be unrooted and i have already gained some experiences in flashing the rom
even after a few softbricks, so i will try installing this image with a stock rom and twrp after i received the help i need.
i use a sd card because twrp always disappears when i transfer a file via my phone and i land on stock recovery.
this problem solves when i root my phone via magisk. as i heard flashing gsi's dont work in a heavy modified state (like with magisk),
so a sd card solved this problem to run files on recovery mode without file transfer and rooting.
the problem i have is the following: i followed some instructions saying to wipe some data first in advanced wipe
- also the system partition which is not available. after that tried to install the image directly. as it finds the rom from my sd card i have to select the partition type to flash image
i only have boot recovery and super available but i need the system partition. i looked in the internet further (the painful process) and it gave me some hints going to mount.
there it finds the system partition but when i set a checkmark on it nothing changes, so this hint didn't helped me.
what should i do now? i'm stuck in some dead end and i don't know what to do it seems like this is the only way for me to get it work.
please help.
i think i found something. since my phone is rooted i also tried to delete system apps which also don't work. i tried many system app removers but it always give error. i think the problem lies in permissions that are not given to this phone. how can i get full access to \ system to gain full permission rights? i also have busybox installed btw
You've to mount the /system partition as RW in order to access this storage location.
Example code:
Code:
adb devices
adb shell "su -c 'mount -t auto -o rw,remount /system'"