Hello
Is it possible to install MAGISK 20. 1 on a HUAWEI Mate 9 under EMUI 9. 1. 0. 252 ? Until then, with TWRP we could flash MAGISK, but now, in TWRP it is answered error & installation fails. Solution ?
No
Wysłane z mojego MI 6 przy użyciu Tapatalka
it's stupid :crying: it's a great app, and having your root device allows you to do a lot of things. . . Does this mean that HUAWEI can't be rooted anymore? Topjohnwu should be stimulated
Magisk20 works just fine on Huawei with emui9.1
Read magisk official installation doc.
Patch yourself your recovery_ramdisk.img extracted from UPDATE.APP which is inside your firmware build zip.
Hi,
Sorry Oslo83, it's not working. Following the standard installation mode, when I flash MAGISK 20, by TWRP 3. 2. 1, there are many errors (as many as version 20. 1), then when I reboot, MAGISK is installed but I no longer have a phone connection (no more services). In addition, the phone is unstable and reboots itself.
If I reboot in recovery, Magisk is not installed, Magisk Manager is still installed, and the phone service works. A solution to install MAGISK (on EMUI 9.1.0.252 (C636E7R1P8 patched 04) ?
official magisk installation doc says to:
Patch yourself your recovery_ramdisk.img extracted from UPDATE.APP which is inside your firmware build zip.
Just stop using twrp
Hi Oslo83,
I don't think I have the same MAGISK installation tutorial ; can you put me the link to the MAGISK installation tutorial; sincerly
https://topjohnwu.github.io/Magisk/install.html#huawei
-From your firmware zip file, extact UPDATE.APP file.
-From UPDATE.APP file, extract 9.x's Recovery_ramdisk.img with 'splitupdate' or 'huawei update extractor'.
-Send Recovery_ramdisk.img file to device
-Use MagiskManager to patch Recovery_ramdisk.img file; you will get a
patched_magisk.img
Flash this patched_magisk to 9.x recovery_ramdisk with fastboot.
Once with patched magisk flashed successfully, keep usb plugged on, reboot while holding VolumeUp pressed for more than 3 seconds on BL screen to boot to erecovery, once in erecovery, choose wipe, that shall reboot to recovery mode which has now been replaced by rooted mode since you successfully flashed recovery_ramdisk.
Then once in rooted mode, delete /cache/recovery/command file.
Thanks Oslo83, it's working
Thanks Oslo83, I just want say what I reported.
When I wipe data, my phone always boots direct in Magisk recovery and I can't recharge when he is off, because he turns on when I plug it.
I have install the patched recovery and use the command "fastboot reboot", disconnected the cable pressing VOL UP, the phone booted on Erecovery and I choose to shut down.
And after turned on using power button +VOLUP. I've got Magisk installed and now I can recharge when the phone is turned off. When I turn on normally my system have'nt Magisk and let me choose if I want the Erecovery. When I turn on pressing VOL UP until Huawei logo, I have Magisk on system. Like the tutorial says: https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery
Thanks for this thread
Thanks to oslo83. I have been troubled by the same unstable, reboot problem for a long time. I tried and succeed. Burst into tears. I often hold all the button in the previous trying and it also leads to the system that has the Magisk. As I said, its unstable and reboots itself. But I can boot to a stable system following the steps you've mentioned. I sincerely wants to know the reason. (Forgive my poor English)
oslo83 said:
https://topjohnwu.github.io/Magisk/install.html#huawei
-From your firmware zip file, extact UPDATE.APP file.
-From UPDATE.APP file, extract 9.x's Recovery_ramdisk.img with 'splitupdate' or 'huawei update extractor'.
-Send Recovery_ramdisk.img file to device
-Use MagiskManager to patch Recovery_ramdisk.img file; you will get a
patched_magisk.img
Flash this patched_magisk to 9.x recovery_ramdisk with fastboot.
Once with patched magisk flashed successfully, keep usb plugged on, reboot while holding VolumeUp pressed for more than 3 seconds on BL screen to boot to erecovery, once in erecovery, choose wipe, that shall reboot to recovery mode which has now been replaced by rooted mode since you successfully flashed recovery_ramdisk.
Then once in rooted mode, delete /cache/recovery/command file.
Click to expand...
Click to collapse
Edit: My phone tries to go into the magisk mode but keeps rebooting in magisk mode. Normal mode works fine.
Not sure what's going wrong. I did the same steps as mentioned for my Huawei 6250 device which is running GSI treble image which has root already. Is that inbuilt root a problem?
Related
Hello
I was on B180 (PRA-LX1C432) rooted with magisk
No updates available in settings/update firmware, but connecting to PC HiSuite B194 appeared (which seems to be for Honor 8 lite by the way). It downloaded it, pushed it to phe phone, but when rebooting it goes to twrp... so obviously I'm still on B180
I imagine we have to flash back stock recovery before updating ? And then twrp again, magisk flash, etc ?
Thanks !
About OTA over magisk I found that on P9 forum:
1) unroot by Magisk Uninstaller, find the download link in the post https://forum.xda-developers.com/sho...63&postcount=1
2) flash from TWRP original stock boot img
3) wipe Dalwik and Cache from TWRP
3) flash from fastboot original stock recovery
4) let it make OTA update but select in the System Update settings to use Full (not differential) update - it will not delete your apps and settings
maybe the safest way indeed...
But as I "catch" the full ota, maybe I can use fastboot to flash only system and boot, and the reflash magisk to patch new boot img ?
anyone ?
Nobody updated after root ??
Ok, this is what I did and happened:
- In TWRP, flash magisk uninstaller script: ERROR 1. After reboot magisk was still here. That was a bad start...
- So I opened magisk app, click Uninstall and then Complete Uninstall. After that I made a reboot as asked, and device rebooted twice.
- Then, went to download mode and flashed stock recovery. And reboot.
- Then went to settings/updates/download latest full ota. It downloaded but refused to start the install process claiming to free up more than 900MB... Nothing on my internal sdcard so I had to uninstall some apps... cool !
- Then it reboot and installed the update
- First boot took a while, I still have "this device cannot be trusted" on start, and OEM unlock in settings is grayed and ON, so I think the bootloader is still unlocked
- Theme and wallpapers were reset with the update
For now I don't have flashed back twrp neither magisk .
In the meantime have you flashed TRWP and Migistik ? And again: do you have still to update your signature or something went wrong in installing fw B194.
Lastly: what do you mean by "went to download mode and flashed"...
I have a LLD-L21 C636 with Resurrection Remix OS 7.0.1 Beta 1. It was rootet in the past but some months ago Magisk uninstalled itself while updating. Now I'm trying to recover Magisk since this time. I don't have access to the old patched image anymore, so I did the following:
Download LLD-L21C636E3R1P1B116 (9.1.0.116) from 2019.05.16 with firmware finder.
Extract the RECOVERY_RAMDIS.img file and put it on the phones storage.
Patch it with Magisk Manager while making sure Recovery Mode is ticked in Advances Settings.
Put the resulting file back on the PC and flash it with fastboot.exe flash recovery_ramdisk magisk_patched.img then reboot with fastboot reboot
Reboot to recovery.
But all I get is a bootloop untill it gives up and boots normally.
There might be more things I tried last months but nothing works. Is anyone seeing any obvious error or has any other idea what could be wrong?
How can i root my honor 9 lite
Abhijaat said:
How can i root my honor 9 lite
Click to expand...
Click to collapse
Open bootloader first
So, i updated magisk (version 21? EDIT: manager was set to upda te to beta, but 20.4 also bootloops :/ ). Before rebooting, also installed to inactive slot, cause.... If you can do it after a OTA update, why not doing it normally, right? Bootloop. Have to press both the power button and VOL up for it to turn off. Usually just the long press on power buttton would do the trick.
Oneplus 7T OOS 10.012 EU
SOLUTION for the bootloop:
- Installed TWRP 3.4.0.2
- Because it cannot access data partition nor transfer files via USB, i did adb push -p local-pc-file-here /tmp
- So, i installed OOS 10.0.13 from there and it booted fine, however without magisk even tough i installed it from /tmp as well right after the ROM install without reboot.
- Tried to reinstall magisk from TWRP (had to reinstall it too, as OOS deleted it), but it bootlooped again. So, i'll wait for a boot file with it.
Executing Magisk-uninstaller-20201003.zip on TWRP did NOT work, cause it couldn't mount the necessary partitions.
EDIT: I have no magisk modules, so i don't know why all of this mess :/
If magisk was already installed on the inactive slot before you patched it, the boot image gets corrupted (at least it always does on my 7T). Really shouldn't use the ota patch feature if you're not installing an ota
Allen77777 said:
If magisk was already installed on the inactive slot before you patched it, the boot image gets corrupted (at least it always does on my 7T). Really shouldn't use the ota patch feature if you're not installing an ota
Click to expand...
Click to collapse
Gotcha! All good now. BTW, if anyone needs, there's a patched boot file on 7T's forum for 10.0.13 EU.
I have the same issue with 10.0.13 HD65AA.
First I tried to do the full update like usual with installing Magis 21 into both slots before reboot but then I got stuck on the boot animation.
Tried a lot of things until I found this thread here. Once I got into TWRP I pushed the latest ROM over to the phone and installed it and I could get back into my phone again. But once I tried to install Magisk via TWRP or boot the patched image for 10.0.13 HD65AA from XDA I get stucked in the boot animation again. So I had to once again push the ROM to the phone and install it into the second slot and once again my phone boots again.
So for whatever reason there is an issue with Magisk and both 10.0.13 HD65AA and HD65BA. So at least for me for now no root.
Thank you very much for at least getting into my phone again without losing any data. :good:
Dears, as you may know Magisk v22 has been released recently. It has very confusing installation process (not for all cases). Anyone had a luck installing it with Ramdisk - No result?
Thanks.
anandadavananda said:
Dears, as you may know Magisk v22 has been released recently. It has very confusing installation process (not for all cases). Anyone had a luck installing it with Ramdisk - No result?
Thanks.
Click to expand...
Click to collapse
Extract boot.img from the firmware zip or tgz, patch it (with Recovery option disabled as per default) from Magisk app, and flash the patched img to Boot by Fastboot
That method definitely works since MIUI 10, and for all versions of Magisk (simce v19 or so - at least), and it still works.
No TWRP needed, but one can also have TWRP installed (and flash the patched or original boot img from TWRP instead of by Fastboot)
anandadavananda said:
Dears, as you may know Magisk v22 has been released recently. It has very confusing installation process (not for all cases). Anyone had a luck installing it with Ramdisk - No result?
Thanks.
Click to expand...
Click to collapse
Hello Amanda.
I agree with you that some instructions are confusing, but I managed to install Magisk in my Redmi K20 Pro Premium following these steps:
1) Install TWRP with this procedure: https://twrp.me/xiaomi/xiaomimi9tpro.html
2) Reboot device into recovery to make sure that TWRP prevents the system to overwrite the flashed recovery.
3) Install Magisk in recovery by patching images: https://topjohnwu.github.io/Magisk/install.html#patching-images
4) After installation complete, run `adb reboot` and immediately press and hold Volume Up and Power buttons until the "Mi" flash screen shows up.
5) Immediately release Volume Up and Power buttons after the "Mi" flash screen shows up
I hope you can reproduce this procedure on your phone.
Regards.
Hopefully someone can help me out here:
I'm on Mi 9T (davinici) with xiaomi.eu-cROM 12.1.2 (Stable) and OrangeFox Beta R11.0 Recovery. Bootloader is obviously unlocked.
I followed the guide for Magisk v22.0 and installed the apk first, opened it and it says
"Ramdisk No"
Alright, so I have to patch the recovery.img.
In Orangefox Recovery I open the Terminal and extract recovery.img with
Code:
dd if=/dev/block/bootdevice/by-name/recovery of=/sdcard/recovery.img
Reboot to system and I chose "Install" in Magisk, "Recovery Mode" is already selected, click "Next" and I select the newly created file "recovery.img". Magisk does it's thing and I have "magisk_patched_cOdEy.img" in my Download folder which I pull with adb.
I reboot to fastboot mode and
Code:
fastboot flash recovery magisk_patched_cOdEy.img
which works w/o problems and reboot again.
But when I open Magisk it still says it's not installed.
So, I check the guide under Magisk in Recovery, where it gets really confusing, but from what I got is that I need to start the phone with recovery button combo (Power+VolUp for Mi 9T) pushed and release at splash screen so Magisk is activated. I try this multiple times since it's really hard with the timing (milliseconds too long it kicks me into fastboot mode. idk why).
Can someone figure out what went wrong/what I did wrong? Never had problems with earlier Magisk versions.
Follow up question: There's some warning about going back to stock recovery will brick your phone in installation. Does that include installing OrangeFox again? I'm 95% sure it doesn't, but would be nice to know before I do it.
Some Xiaomi devices have their bootloaders set up so that it will accept an initramfs that was manually added to the boot image. Therefore, on these devices you'll need to patch the boot image even though there's no ramdisk. Try that.
Didgeridoohan said:
Some Xiaomi devices have their bootloaders set up so that it will accept an initramfs that was manually added to the boot image. Therefore, on these devices you'll need to patch the boot image even though there's no ramdisk. Try that.
Click to expand...
Click to collapse
Can I reinstall OrangeFox or TWRP recovery then?
I'll report back, when I tried it.
edit: So this actually works and I was able to enter TWRP recovery again after flashing.
edit 2: Now WiFi is not working anymore. fml.
edit 3: For anyone stumbling over this thread. Nothing worked, I had to do a compelte wipe and then flash Magisk "the old way", by renaming the .apk into a .zip and flashing it in recovery. That did the trick without any probems and I'm rooted now after quite a hassle.
yeah, I stumbled upon it. And I'm having the same/a very similar issue. I was very happy with Magisk up to v22 when the problems began.
I'm still at DerpFest based on Android 9.0 (from 2019 ) and TWRP-3.4.0.0.I had Magisk running since it was 19.4, upgraded it multiple times already. So didn't think much about updating to 22. Then, it said the same: no ramdisk. Pitty. OK, so I went ahead and let Magisk patch the TWRP.img I still got on my phone and flashed the patched TWRP onto recovery. Upon booting, Magisk is there, but no wifi, no sound, no light sensor, ... LTE works, though .
Anyways, I just want to get my old setup back, so I thought, I just flash the original TWRP again. According to the Magisk documentation, if I don't press any button, it should boot to Android without Magisk. Well, it always boots into Android+Magisk disregarding that. If I flash the original TWRP.img back, I always end up in TWRP. So, the order is: boot.img -> magisk-modified-recovery.img -> (boot.img?) -> system. How can I get the behaviour Magisk advertises?
And yes, I tried uninstalling Magisk (via uninstall.zip meythod), which said it would uninstall, but actually didn't. I also flashed different boot images (a backup I had in TWRP, the original boot.img I've found in the DerpFest zip...) to no avail.
So, Immortal68, which of the many wipes one can do did result in the old behaviour? And: now that you have Magisk22, does it say "Ramdisk: yes" again?