edit....... all sorted
Has anyone had success in rooting this phone on android 10, ive tryed with magisk by patching the boot .img.lz4 but always fails on unable to repack boot image....
Please help...
how did u root your phone i m also on q?
Related
Hi, i have Huawei y9 2018 oreo 8... i tried to flash xposed framework beta 3 sdk 26 but i got bootloop after restart... I tried to fix it with Uninstaller xposed but it doesn't work so i flashed the boot.img with the recovery and this worked ... But I lost the magisk... I try to flash it again with the recovery but every time I try it i get bootloop again and i flash the boot again to fix it... Guys can you help me to find the problem? I wanna flash magisk again without get bootloop.
https://www.didgeridoohan.com/magis...agisk_functionality_bootloop_loss_of_root_etc
Possibly could need to patch boot only and flash patched img with fastboot.
But I have return question for you
.I have not found link to TWRP for y9. Would you share link to recovery you are found to use.
Didgeridoohan said:
https://www.didgeridoohan.com/magis...agisk_functionality_bootloop_loss_of_root_etc
Click to expand...
Click to collapse
How did he get twrp ? And how did he unlock the bootloader ? Plz i need help rooting this devise and there is no bootloader codes on huawei's website? If some can help plz
I am trying to fix a boot loop problem after installing a problematic Magisk Module, and I am stuck. After multiple efforts to try to undo the problem in Android 11, I believe I need to downgrade first to then boot into Magisk Core-Only mode to uninstall the module. The problem is I can't downgrade. I have tried to install the latest build for Pixel 4 XL on both Android 11 DP4 and 11 Beta, and I always get a boot loop. I used flash-all and Android Flash Tool and still get a bootloop. I switch the active partition and flash Android 10 there, nothing. Can anyone help?
Btw, if I flash Android 11 Beta (or the latest Android 11 build), it works.
Did you remember to wipe the data and factory reset?
normally i just update my phone and install the latest magisk, but now rooting just makes the phone bootloop, miui ver 20.6.4 and the previous weeks update did the same. dose anyone else have the issue? perhaps rooting method changed?
xdarkmario said:
normally i just update my phone and install the latest magisk, but now rooting just makes the phone bootloop, miui ver 20.6.4 and the previous weeks update did the same. dose anyone else have the issue? perhaps rooting method changed?
Click to expand...
Click to collapse
I don't think that there is some changes in rooting method because I followed :
1.Unlock bootloader
2.Flashed TWRP
3.Flashed magisk
4.Configured magisk app after normal boot
And confirmed, my device is rooted !!
Got it to work. But I had to manually patch my boot image myself and then fully uninstall magisk then flash modded boot img.
Hello all. first post here as i only recently found this great site. So ive been wanting a rooted phoje for a long time now as i iswd to jailbreak my uphone back when i used apple and hadnt learned of Androida greatness. I got a pixel 5a and i love it! Its different and i just love it. Maybe more than my s21ultra even. Anyways I updated to android 12 beta and then tried to root my device. I've never done this before so i tried to learn as much as possible. Anyways I followed the magisk tutorials and unlocked my boot loader and downloaded the boot.IMG for Android 12 and patched the image then did the fastboot and adb stuff only to end up with my phone not working. Clearly I did something wrong. It originally said on the fastboot menu failed to load or verify boot image. And was stuck on that menu. Tried to recover reboot and it stayed the same. Somehow I got it to restart then it was in a bootloop going to google to the unlocked bootloader warning screen over and over. I got frustrated and left it. It died and put it on the charger and it was in rescue or recovery mode saying no command. I got it into recovery menu and tried to factory reset and now it boot to the white google screen. I wanna flash it back to android 11 that it came with so I can eventually try and root it again as that seems much more successful then Android 12. ANy help is very appreciated and I am a SUPER noob at this and don't know about any of it so please keep that in mind when replying. Thanks
You needed to disable verification and dm-verity when flashing the android 12 beta.. You're stuck at fastboot now because of this..
The solution is to use the Google flashing tool, and re-flash android 11 w/ wiping the data selected.. You can try without having wipe data selected, up to you.
P.S. while I recommend you stay on Android 11 if you want a less buggy rooted phone, follow guide #1 on this thread here if you wanna use android 12 beta w/ Magisk:
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com
bobpiesz said:
You needed to disable verification and dm-verity when flashing the android 12 beta.. You're stuck at fastboot now because of this..
The solution is to use the Google flashing tool, and re-flash android 11 w/ wiping the data selected.. You can try without having wipe data selected, up to you.
P.S. while I recommend you stay on Android 11 if you want a less buggy rooted phone, follow guide #1 on this thread here if you wanna use android 12 beta w/ Magisk:
[Guide] Flash Magisk on Android 12
Trying to root the Pixel 5 running Android 12 by flashing a magisk-patched boot image results in the phone only booting to fastboot mode ("failed to load/verify boot images") Some users have reported that booting (instead of flashing) the patched...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for the help I really appreciate it! I'm gonna give it an attempt right now.
I am facing the same type of problems for so long now.
Seems Magisk breaks booting when on the 12 S bootloaders :c even with disable-verity and disable verification in any step of the process
Disabling verity and verification is no longer required with Magisk 23016.
Follow my guide here, use the Factory Image method.
I have just updated the ROG 3 from Android 11 to Android 12 Version WW-31.0210.0210.230 succesfully. Unfortunately I lost root and TWRP even after I flashed the TWRP_Flash_tpposite_Slot-CPTBv2.zip . I have installed the latest TWRP twrp-3.6.2_12-0-I003D.img succesfully (thanks Captain_Throwback for the file). and tried to root with Magisk. It succesfully flashed in TWRP, but the boot took endless. After many tries, I have used the stock boot in the Magisk app 25.1(25100) to patch it. Even flashing the patched version I could't have a succesfull boot. Anyone has a clue what I am doing wrong?