I recently flashed TWRP on my Moto e4 plus US model successfully, and afterwards I flashed Magisk to obtain root, which worked. But then I had to restore from a backup because wifi was disabled for some reason. After restoring it I went to flash Magisk again, and now it's giving me mount system errors. Any suggestions?
Related
I have a honor 8, I did install lineage but something happened and got into bootloop and did use my twrp backup that installed stock system without my apps etc. I do have a kernel that gives me root access (SuperSU) tried to uninstall with the in app root remove but it failed when I did check stock boot.img. so I extracted the boot, vendor och system from update.app and installed it with twrp, but the boot.img gave me a bootloop so I used my SuperSU boot.img and it boot. Did try to force update with a dload folder but it didn't work only came to 5% and did try like 10 different versions. After that did I download flashify and flashed stock recovery.img but couldn't boot up to it it whent to erecovery. Did also try to boot into bootloader but it just booted up to twrp (did installed it again). How can i get back to completely stock? And does I have a bootloader? Also have a decrypted the /data partition for the custome rom
I've tried magisk and i get "update process ended with erorr 1".
I also tried flasing SuperSu and it was sucessfull, but still not rooted.
use latest magisk zip
thgm21 said:
I've tried magisk and i get "update process ended with erorr 1".
I also tried flasing SuperSu and it was sucessfull, but still not rooted.
Click to expand...
Click to collapse
It occurs because rooting your ROM requires to mount Vendor. But the recovery you're using is unable to mount Vendor. So it produces error 1.
To solve it you need to flash another twrp recovery capable of mounting vendor.
Try twrp recovery by xdoge. It'll work.
A while ago, I had TWRP and magisk working. I decided to try and install xposed from the magisk repository, which ended in a bootloop, so I restored the phone using eRecovery.
After this, I installed TWRP and attempted to install magisk again, which led to a bootloop once again - this happens every time I install magisk.
I have tried using uninmod, which just displays no modules to uninstall when I use it in the terminal, and I have tried mounting magisk.img to a folder, but this just contains "lost+found" and no modules.
It would be a great help if someone could offer some advice on how to fix this, because I hope to flash EMUI 9.
So i had a hickup with updating magisk to v20.3.
The result was that after a reboot the device got stuck in fastboot mode.
I went to TWRP 3.3.0 recovery and backed up all offered partitions before then attempting to re-flash magisk.
Didn't work out.
Then i heard that if you extract the boot.img from the stock firmware and flash it with fastboot you can get back to a working state where you can install Magisk again.
So i thought.
Now after booting i am greeted by the miui first install wizard and the whole set of apps seems to be gone as well as my settings.
IIRC i only removed the dalvik cache which shouldn't affect this state.
Where in the procedure is the mistake and can i get the old pre-broken update state back? I am afraid something has been lost in the process
selemine said:
So i had a hickup with updating magisk to v20.3.
The result was that after a reboot the device got stuck in fastboot mode.
I went to TWRP 3.3.0 recovery and backed up all offered partitions before then attempting to re-flash magisk.
Didn't work out.
Then i heard that if you extract the boot.img from the stock firmware and flash it with fastboot you can get back to a working state where you can install Magisk again.
So i thought.
Now after booting i am greeted by the miui first install wizard and the whole set of apps seems to be gone as well as my settings.
IIRC i only removed the dalvik cache which shouldn't affect this state.
Where in the procedure is the mistake and can i get the old pre-broken update state back? I am afraid something has been lost in the process
Click to expand...
Click to collapse
Just install the latest stock rom then install recovery and restore all the backed up partitions.
Now install magisk and reboot.
If that doesn't work (u get into fastboot again) then just flash the boot.img file via fastboot and then reboot.
if i restore the backed up partitions and install magisk over it i get back to the non-booting , stuck in fastboot version. So something is wrong in the state of denmark.
selemine said:
if i restore the backed up partitions and install magisk over it i get back to the non-booting , stuck in fastboot version. So something is wrong in the state of denmark.
Click to expand...
Click to collapse
I looked at the /data backup from twrp and it is only 3mb, unless stuff got moved to /system or so, it seems to be gone forever.
Hell , i wil never update magisk again.
selemine said:
I looked at the /data backup from twrp and it is only 3mb, unless stuff got moved to /system or so, it seems to be gone forever.
Hell , i wil never update magisk again.
Click to expand...
Click to collapse
Don't install magisk with the rom, just restore the data, flash the stock boot.img file and then reboot.
After boot uninstall the magisk manager app and reboot to recovery and then flash magisk again.
Hi,
I have successfully flashed magisk_patched_boot.img and TWRP but when I enter in TWRP using adb reboot recovery then it asks for the password and whichever I enter password it says Unable to decrypt data. Can anyone please help how can I flash SuperSu in TWRP which says this error?
Firstly, why don't you just use magisk, using SuperSu seems dumb, since, it can't offer systemless customisations, I recommend you to restore your phone to the original state, lock the bootloader of you unlocked it, and, patch the boot image of the device and flash it using so flash tools... Also, using sp flash tools you can keep your bootloader locked and still be able to use magisk and other customisations, also, I need a nvram partition backup, since, I fully erased my device age now my imei is gone, just take a backup of the nvram and send it to me, I will edit the info for my device and flash it myself...