Just upgraded magisk to 11 this morning from inside the app and it has been stuck rebooting the past ten minutes. Can anyone help?
can still get into Twrp though if that helps figure out solutions.
I have similar problem, on a OnePlus 3 with a CM13 based Rom.
After the update from 10.2 to 11 the start of Android never finished.
Temporary solution (until I have more time to produce a real bug report or someone else finds the problem) uninstalled Magisk via Uninstaller zip in TWRP and reinstalled Magisk 10.2 there.
Same problem for me on Pure Nexus when installing v11. Stuck on boot screen.
Had to flash Magisk Uninstaller, and re-flash Magisk 11 through TWRP. Seems to work, until I installed ViperFX (through Magisk) and it asked me to reboot - now I'm back in a boot loop.
Going to roll back to Magisk 10.2 until something gets fixed.
Flash the uninstaller script in TWRP and try again. And even if it seems to be bootlooping, let it sit. Mine stayed on boot animation for a good 5-10 minutes the first boot up on v11. If it still seems to be looping, try flashing a clean boot image and start over.
Nexus 6, Pure Nexus 01/21.
Okay, so I finally got it to boot doing the following:
1) Factory Reset
3) Format System
2) Reflash Rom, GApps
3) Boot into Rom
4) Reboot, flash Magisk
5) Boot back into Rom
I think the issue is if you are coming from 10.2 (or earlier) you need to remove SU before flashing magisk. Magisk has SU built in (though should work with SuperSU or phh's for now) but I think there is some issue when upgrading. Maybe try flashing your preferred SU package after you reboot into the rom after Magisk is installed.
---------- Post added at 03:20 PM ---------- Previous post was at 03:16 PM ----------
Didgeridoohan said:
Flash the uninstaller script in TWRP and try again. And even if it seems to be bootlooping, let it sit. Mine stayed on boot animation for a good 5-10 minutes the first boot up on v11. If it still seems to be looping, try flashing a clean boot image and start over.
Nexus 6, Pure Nexus 01/21.
Click to expand...
Click to collapse
Hehe, well, I only just found out about that before I nuked my phone.
OK for me the boot problem was fixed by restoring the boot partition from a backup without Magisk installed and the flashing version 11.
So the problem is mostly cased by something in the boot partition.
If you don't have a backup of the boot partition. Flashing the boot image of the ROM or the hole ROM should fix this.
At lest for me no need to reset everything.
Did a full unroot of supersu, told it to restore the backed up boot image, booted immediately into recovery, flashed magisk and magisksu stuck no problem. I like this all in one solution v11 brings.
It's viper4android now causing the bootloop... I flashed clean with magisk 11.1
lutanica said:
It's viper4android now causing the bootloop... I flashed clean with magisk 11.1
Click to expand...
Click to collapse
agreed. this seems to be unresolved right?
steveo17 said:
agreed. this seems to be unresolved right?
Click to expand...
Click to collapse
Still unresolved yes..
I fixed my bootloop problems doing the following:
1. Booted into recovery (TWRP)
2. Decrypted my data partition
3. Connected the phone to my PC
4. `adb shell`
5. rm -rf /data/magisk /data/magisk.img /data/stock_boot* /data/su/
6. Installed Magisk v11.1 by sideloading the zip
7. Rebooted
Proof:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
steveo17 said:
agreed. this seems to be unresolved right?
Click to expand...
Click to collapse
denvit said:
I fixed my bootloop problems doing the following:
1. Booted into recovery (TWRP)
2. Decrypted my data partition
3. Connected the phone to my PC
4. `adb shell`
5. rm -rf /data/magisk /data/magisk.img /data/stock_boot* /data/su/
6. Installed Magisk v11.1 by sideloading the zip
7. Rebooted
Proof:
Click to expand...
Click to collapse
And you've Viper4android installed and it's functioning?
I only heard about Magisk and its rooting abilities yesterday. So far I have always used SuperSU, but now I'd like to migrate. Now and again I'd like to use my banking app, and it's not allowed on rooted phones. I've tried rootcloak before, but for some reason I can't remember, didn't really work. So I would love it if this solution did.
However, when I install suhide required, it bootloops. So I reflash the whole system, bootloop remains. Only when I flash rm-suhide it does actually boot. But now I have to remove SuperSU and flash root again using the magisk.zip. When I do, it bootloops. Go figure.
I'm on the angler February update N4F26O.
Haven't tried the adb shell solution yet, but just about everything else.
denvit said:
I fixed my bootloop problems doing the following:
1. Booted into recovery (TWRP)
2. Decrypted my data partition
3. Connected the phone to my PC
4. `adb shell`
5. rm -rf /data/magisk /data/magisk.img /data/stock_boot* /data/su/
6. Installed Magisk v11.1 by sideloading the zip
7. Rebooted
Click to expand...
Click to collapse
Verified working with an extra step: after you reboot, remove SuperSU if you have it (app drawer, drag to uninstall). This seems to default the SU method to the MagiskSU, which allows it to pass safety net as well. Before I uninstalled SuperSU, I was getting safetynet fail CTS mismatches.
Also, after doing the quoted method, it did take a little longer than usual booting, give it 5 min at least.
Lastly, Viper4Arise doesn't work (driver won't load), probably because of something related to the new magisk, or because it preferred SuperSU.
Thanks
2hdq said:
I only heard about Magisk and its rooting abilities yesterday. So far I have always used SuperSU, but now I'd like to migrate. Now and again I'd like to use my banking app, and it's not allowed on rooted phones. I've tried rootcloak before, but for some reason I can't remember, didn't really work. So I would love it if this solution did.
However, when I install suhide required, it bootloops. So I reflash the whole system, bootloop remains. Only when I flash rm-suhide it does actually boot. But now I have to remove SuperSU and flash root again using the magisk.zip. When I do, it bootloops. Go figure.
I'm on the angler February update N4F26O.
Haven't tried the adb shell solution yet, but just about everything else.
Click to expand...
Click to collapse
Firstly unroot the SuperSU, flash the latest Magisk zip file v11.1. You don't need the suhide as the latest version of Magisk already has the necessary files to root your device. Hope this helped you
At the risk of sounding dumb, I couldn't figure out how to decrypt my data partition. I don't know if what I did made any actual difference but I did a nandroid of my data, rebooted twrp, restored data, entered the adb command, then installed magisk. Reboot to system, all set!
Hope this helps someone out.
Sent from my Nexus 6P using Tapatalk
I'm getting a constant boot loop (stuck at boot animation) each time I try to install magisk on my Oneplus 3. with OOS 4.0, it worked fine on MM but no go since updating to nougat.
Edit:Fixed it! I hadn't ran the uninstaller first. Once I did this it worked fine. Doh!
Hi on my lg g5 (with fulmics custom rom Android 7.0) magisk 11.1 crashes settings app, any solutions? I could revert back to 10.2?
Related
This morning, waking up I recieved the notification that a new magisk manager is available. I installed it as usual, except this time my device suddenly was not rooted anymore.
Si I press the install magisk button that pops up, it flashes magisk, and BAM. Phone restarts, and boot loop.
The phone's a OP5, android 7.1.1, and I had to do a factory reset twice before it would boot. Even using the magisk uninstaller did yield no results.
How come the phone suddenly got unrooted? Can I safely root it again now? Why wouldn't the first factory reset get it out of boot loop?
How can I prevent data loss in the future? Help?
Update 1 - Fun fact: After my two factory resets (what it took to reboot, since the uninstaller wouldn't flash right, fml.) and setting the phone up right now, my phone IS rooted with magisk 17.
So the flashing of magisk v17 worked. It just ****ed my phone so hard it needed a wipe to comprehend the immense power of the Magisk! (Yes, this is a slightly salty hyperbole, fix your updates!)
Update 2 - TimMayle managed to run the uninstaller and re-flashing magisk v17 on TWRP, try this if you have the issue. (While the uninstaller wouldn't work for me, that might be a device specific issue.)
TimMayle said:
Hello,
I was on Magisk 16 and probably Manager 5.8.3.
Magisk 17 wouldn't flash from Magisk Manager. So I did flahs it in TWRP.
Then I was in bootloop.
In TWRPm I flashed magisk uninstaller to remove it completely and installed Magisk 17.
Bootloop Gone !
Tim
Click to expand...
Click to collapse
Update 3 - Thanks void74 for another potential procedure that might fix your issues.
void74 said:
I faced this problem too this morning.
I have a Redmi Note 5 with AOSiP ROM, I don't know if it's the right way to do it, but I solved the bootloop problem this way:
- volume up and then boot to TWRP
- copied magisk uninstall to phone memory
- installed magisk uninstall
- rebooted in fastboot/bootloader mode
- flashed original boot.img extracted from stock image zip file ("fastboot flash boot boot.img")
- rebooted to TWRP
- installed magisk 17.0 zip file
- rebooted to system, all OK!
Only problem is that I lost previous magisk configuration, but it's a snap to reconfigure it!
I hope I have saved some lives.
Click to expand...
Click to collapse
Update 4 - Thank you Shampinger for giving ups a Linux-specific variation on the steps to follow.
Shampinger said:
Same issue here on Redmi Note 5 global (whyred). Thanks to this thread I could fix it.
Steps (on Linux):
1. boot into fastboot (vol down + power)
2. from folder with your twrp zip run:
Code:
sudo fastboot boot twrp-x.x.x-x-whyred.img
there might be an easier way to boot into recovery without having to use the zip on your computer that I don't know about
3. copy Magisk uninstaller and Magisk v17 to phone (if not already there)
4. flash uninstaller zip
5. go back and flash Magisk v17 zip
6. reboot
Click to expand...
Click to collapse
Update 5 - While a fixed version is being perfected, Mangraviti summed up what you should do:
Mangraviti said:
Here is what to do, if you HAVE NOT installed the new version:
1) Do not update via Magisk Manager.
2) Do not update via TWRP using the zip you can download via Magisk Manager.
3) Uninstall Magisk using Magisk uninstaller (ZIP).
4) Boot to Android.
5) Reboot to TWRP
6) Install V17 ZIP via TWRP and boot to Android.
If you HAVE INSTALLED and got a bootloop:
1) Download the uninstaller ZIP.
2) Enter TWRP during the bootloop.
3) Uninstall using the uninstaller ZIP.
4) Boot to Android.
5) Download V17.
6) Reboot to TWRP and flash the V17.
7) Boot to Android it it should be working.
Click to expand...
Click to collapse
Update 6 - If you have Wi-Fi issues after update v17, you can attempt what TAJ_Rocks has found out:
TAJ_Rocks said:
Found fix for dead wifi
Delete this p2p supplicant.conf supplicant made wifi a c#nt:laugh:
Reboot after deleting
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
+1.
Exactly the same issue. The phone lost root and is now stuck in bootloop. How to recover? Any hopes of saving the data?
Please throw some light....
Same issue here... bootloop after update. I wish I didn't update.
Oreo 8 on Huawei Nexus 6p.
Same here on HTC U11 with Lineage 15.1
Feels bad man.
How do I fix?
I fixed bootloop by uninstalling magisk with magisk uninstaller. After that I installed v16
Is this when updating from Magisk v16.0, Manager v5.8.3? What happens if you uninstall and install v17.0 clean?
Same here (bootloop) after update from 16 to 17. I used unnistaller but ended in fastboot after reboot :laugh:
Had to install rom and v17 to work.
Redmi Note 5 Pro MIUI 9.6.4.0 Global
Same thing on s7 with Android 7.0 , now I'm resetting the device.
Fun fact: After my two factory resets (what it took to reboot, since the uninstaller wouldn't flash right, fml.) and setting the phone up right now, my phone IS rooted with magisk 17.
So the flashing of magisk v17 worked. It just ****ed my phone so hard it needed a wipe to comprehend the immense power of the Magisk! (Yes, this is a slightly salty hyperbole, fix your updates!)
Mi Note 3, MIUI 9 Xiaomi eu.
I upgraded Magisk Manager and now my phone is unrooted. Fortunately I came here to read what's wrong, so I didn't flash Magisk 17.
But now I am unrooted.
What can I do?
ZioArturone said:
Mi Note 3, MIUI 9 Xiaomi eu.
I upgraded Magisk Manager and now my phone is unrooted. Fortunately I came here to read what's wrong, so I didn't flash Magisk 17.
But now I am unrooted.
What can I do?
Click to expand...
Click to collapse
Okay, so this is guesswork at best, but if you don't wish to flash v17, what I would suggest is uninstalling the latest magisk manager, and going to your magisk folder to install the .apk of the version before.
See if you're still unrooted, then if you are, find magisk v16 either in your magisk folder, or from a download link, and flash that back on for the time being.
Didgeridoohan said:
Is this when updating from Magisk v16.0, Manager v5.8.3? What happens if you uninstall and install v17.0 clean?
Click to expand...
Click to collapse
Hello,
I was on Magisk 16 and probably Manager 5.8.3. (Xperia Z3C on OmniRom).
Magisk 17 wouldn't flash from Magisk Manager. So I did flahs it in TWRP.
Then I was in bootloop.
In TWRPm I flashed magisk uninstaller to remove it completely and installed Magisk 17.
Bootloop Gone !
Tim
Didgeridoohan said:
Is this when updating from Magisk v16.0, Manager v5.8.3? What happens if you uninstall and install v17.0 clean?
Click to expand...
Click to collapse
Yes. That's exactly what I did. OK. So I now ran magisk uninstaller, booted fine. Then installed clean v17.0 and it works now - no bootloop. Many thanks!
I am having the same problem with magisk manager 5.8.3 + v16 zip. After upgrading to v5.9.0(138) all my previous setting all gone. Plus i can install v17 zip at all.
This is on HTC U11+ with android v8.0
Same for me had bootloop on android 7.1.2 i was on magisk 16.0 stable. I got notification before an hour. I upadted the apk and it showed magisk not installed. So i downloaded the zip and flashed 17.0 stable zip and had bootloop. So i just cleaned cache and dalvik now phone is started and root and magsik working. But now wifi is unable to switch on
Also got a bootloop on my Samsung Galaxy S4 jfltexx running Resurrection Remix v5.8.5 (Android 7.1.2). Fortunately I took a TWRP backup before this upgrade and was able to restore it.
But I'm also without root due to Magisk Manager not offering any option other than to install Magisk-v17.0(17000).zip
Some say use the uninstaller or uninstaller.zip but where can I find this? Magisk Manager says "Magisk is not installed" and there's no uninstall-like option to be found.
ZioArturone said:
Mi Note 3, MIUI 9 Xiaomi eu.
I upgraded Magisk Manager and now my phone is unrooted. Fortunately I came here to read what's wrong, so I didn't flash Magisk 17.
But now I am unrooted.
What can I do?
Click to expand...
Click to collapse
I'm in the same situation with a s6. After another device (s7) has a bootloop I don't think that i flash the v17 from the manager
gkmac said:
Also got a bootloop on my Samsung Galaxy S4 jfltexx. Fortunately I took a TWRP backup before this upgrade and was able to restore it.
But I'm also without root due to Magisk Manager not offering any option other than to install Magisk-v17.0(17000).zip
Some say use the uninstaller or uninstaller.zip but where can I find this? Magisk Manager says "Magisk is not installed" and there's no uninstall-like option to be found.
Click to expand...
Click to collapse
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
In "Downloads" you have "Latest uninstaller" go to recovery and flash the zip, that should uninstall magisk.
Dacraun said:
Okay, so this is guesswork at best, but if you don't wish to flash v17, what I would suggest is uninstalling the latest magisk manager, and going to your magisk folder to install the .apk of the version before.
See if you're still unrooted, then if you are, find magisk v16 either in your magisk folder, or from a download link, and flash that back on for the time being.
Click to expand...
Click to collapse
Uninstalled latest MM, installed previous version, then I installed magisk 16.0 via twrp.
It didn't work, I am unrooted.
This update ****ed up all...
ZioArturone said:
Uninstalled latest MM, installed previous version, then I installed magisk 16.0 via twrp.
It didn't work, I am unrooted.
This update ****ed up all...
Click to expand...
Click to collapse
Check the first post, I quoted someone flashing the uninstaller and flashing v17 again and it worked. Maybe that'll work for you?
I do suggest doing a total backup in twrp first though. Just in case.
Hello everyone this a little guide for rooting your Galaxy S9 and S9+ (EXYNOS) with Magisk Official
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quote:
READ THIS BEFORE ROOTING DEVICE
- In any case i'm not reponsable of the beginning of the 3rd World War if you find a way to build a time machine with this guide ! So keep your plans of the time machine in a secure place.
- Any of below said method to root will trip knox and void warranty forever.
- Root process needs wipe data so make backup of important data (including Internal Device storage) before proceed.
- As of now you will lose Samsung Pay and Secure folder forever if you root once, even unrooting won't help. (hope in future we can get it working on tripped knox device). Also you may not able to run some banking apps, you can use Magisk Hide
- OTA likely won't work once you root device.
- To unroot device completely, simply flash Samsung stock firmware, Remember, Unrooting won't revokes warranty nor you will be able to use Secure folder/Samsung Pay. Once rooted, these feature gone for you unless some magic happen in future and may find a way to use it.
Click to expand...
Click to collapse
Magisk hide 17.1 isn't working SafetyNet Fail
Take a look at the pictures at the end of this thread.
If your coming from my another thread about the Magisk 16.3 modified
1.Do a /data backup in TWRP
2.Wipe with TWRP
3.Use odin to update to the latest firmware from samsung
4.Root with this guide and restore.
Click to expand...
Click to collapse
How to proceed
1.Enable Developer Option (settings - about phone - Software information - Tap 7 times on build number to activate developer option in settings menu)
2.Enable OEM Unlock from developer option (if you don't have this option it means that your S9 is incompatible)
3.Download TWRP for S9 or S9+
4.Switch Off device
5.Press Vol down + Bixby + Power to reboot to download mode, press volume up when asked to continue to download mode
6.Download Odin and open it, Disable 'Auto reboot' from option menu of Odin
7.Select TWRP (tar image) with AP tab of Odin and Start
8.Once Successfully flashed, you will see 'Passed' in Odin tab
9.Disconnect device and hold Vol down + power till screen goes off, Now immediately press Vol Up + Bixby + Power to reboot to TWRP
10.Select to allow modification
11.From TWRP, Select WIPE menu - Then FORMAT DATA - You need to type 'yes' to perform wipe. WARNING : This will erase all data including Int SD storage from device
12.Once format device completes, go back and select REBOOT' Menu and then - 'RECOVERY', This will reboot to TWRP again
13.Flash no-verity-opt-encrypt-samsung-1.0 and then Magisk (you can also flash a kernel or xposed)
14.Once flash successfully finish, Reboot to System
14.1 Sometimes the manager doesn't install, you need to just install the manager with the link.
15.Open settings - Developer option - Look for OEM Unlock option. It will automaticaly change to unticked after some reboot don't panic! at the disco it's normal.
16.MAKE A BACKUP IN CASE OF BOOTLOADER RELOCK.
Enjoy ! You have your Galaxy S9 or S9+ watched by the organisation rooted.
Q&A:
Hey F10, why my magisk app isn't appearing or crashing when i lunch it ?
You have to delete the related folders of magisk at this path: /data/app
Hello dev, my phone is bootlooping after the flash help me plz.
You missed the dm-verity flash, just flash it.
Hi i tried to flash a kernel and i lost the root. I don't have any backup what should i do ?
Some kernel when flashing re enable the encryption of the / partition so the only way to go back is the backup. Without that you good to wipe and reflash magisk (and loosing all your data).
Does the magisk 17.2 (Beta) works on my Snine ?
Ya it's works.
Links:
Magisk 17.1 official:
[url]https://androidfilehost.com/?fid=962187416754474353[/URL]
Magisk Manager:
https://github.com/topjohnwu/Magisk/releases/download/manager-v5.9.1/MagiskManager-v5.9.1.apk
Xposed Oreo S9:
[url]https://forum.xda-developers.com/showthread.php?t=3034811[/URL]
Twrp S9:
[url]https://twrp.me/samsung/samsunggalaxys9.html[/URL]
Twrp S9+:
[url]https://twrp.me/samsung/samsunggalaxys9plus.html[/URL]
After doing this pc wont recognized phone any idea why?
yehuda2525 said:
After doing this pc wont recognized phone any idea why?
Click to expand...
Click to collapse
Check your driver.
update magisk manager
hi , i have already root my device thanks to you but with 16.3 modified version . so to update it do i need to install the 17.1 directly or i need to uninstalle it and install the new one ? thanx for the help:good:
edit : i did all this but nothing workes .
when i install it directly , after the reboot i found magisk but it crash.
i have uninstall it and reinstall but now there is no icon of it ?
ponthere said:
hi , i have already root my device thanks to you but with 16.3 modified version . so to update it do i need to install the 17.1 directly or i need to uninstalle it and install the new one ? thanx for the help:good:
edit : i did all this but nothing workes .
when i install it directly , after the reboot i found magisk but it crash.
i have uninstall it and reinstall but now there is no icon of it ?
Click to expand...
Click to collapse
Sometimes the manager disappear, you just need to reinstall it.
https://github.com/topjohnwu/Magisk/releases/download/manager-v5.9.1/MagiskManager-v5.9.1.apk
I did it but installation fail !!
Is it possible to install Magisk without TWRP on the S9+ ?
When I try to patch the boot image I get "Repackaging boot image.... ! Installation fail" The Magisk log file everything seems to work then it ends with " Cleaning up.... ! Installation failed" . I can probably patch the boot.img of the S9+ with my S7 Edge. Any idea if this would work?
yahavrave said:
Is it possible to install Magisk without TWRP on the S9+ ?
When I try to patch the boot image I get "Repackaging boot image.... ! Installation fail" The Magisk log file everything seems to work then it ends with " Cleaning up.... ! Installation failed" . I can probably patch the boot.img of the S9+ with my S7 Edge. Any idea if this would work?
Click to expand...
Click to collapse
Update with latest firmware from Samsung.
Not sure what you mean @frauchgu10. I have the latest OTA installed.
yahavrave said:
Not sure what you mean @frauchgu10. I have the latest OTA installed.
Click to expand...
Click to collapse
I don't know why but maybe this version is incompatible with this method. I will maybe do some test about that.
Maybe.. But do you think it wil work if I patched the latest boot image (for the S9+) on another phone (S7 Edge). What will happen if I try to flash it via Odin ?
Everything went smooth! Recovery installed, and rooted.
Thanks!
frauchgu10 said:
I don't know why but maybe this version is incompatible with this method. I will maybe do some test about that.
Click to expand...
Click to collapse
hi there,
im unable to root after the august 1 security patch running stock rom G965FXXU2BRGA_G965FOXM2BRG8_ILO on galaxy s9+
my phone lags then freezes permanently after flashing magisk and booting up . i haven't experienced this before the update
any ideas?
im thinking the update probably broke "No Verify Encrypt" because magisk is unable to keep dm-verity enabled .
i discovered this when opening magisk manager,the checkbox for preserve dm verity is not checked,and when i do enabled it it does nothing.tried restarting too
i tried various methods including issuing "echo KEEPVERITY=true>>/data/.magisk" command in recovery terminal after flashing magisk with no success ( i even tried flashing different magisk version ,latest version then the one before it and another one..etc) tried supersu too . i tried everything in "Magisk and MagiskHide Installation and Troubleshooting guide " documented in Magisk Troubleshoot Wiki (Didgeridoohan!)
my steps to rooting is the following :
enabling OEM unlock if not enabled
flashing twrp 3.2.3.0 star2lte
formating data then rebooting to recovery
Installing No Verify Encrypt 6.0 star zip file then rebooting to recovery again
installing rmm state bypass v2
flashing magisk ( tried different versions,customs ones too ,supersu)
rebooting to system
(gathered from various tutorials from highonandriod or other places)
What features are gone if i rooted my phone other than secure folder and samsung pay?
When rooted you can't update via OTA. Some games can detect root like pokemon go so you can not play these games without doing some tricks.
frauchgu10 said:
When rooted you can't update via OTA. Some games can detect root like pokemon go so you can not play these games without doing some tricks.
Click to expand...
Click to collapse
Okay, any others than that?
frauchgu10 said:
When rooted you can't update via OTA. Some games can detect root like pokemon go so you can not play these games without doing some tricks.
Click to expand...
Click to collapse
could you help me with my problem?
im having trouble with my device rooting,after the first boot my device freezes up and wont respond.
it seems that samsung patched some of the vulnerabilities used by the bypasses to achieve root,
after the august update. the device is unable to sustain the NO Verity OPT encrypt , the device seems to re-encrypt it self after the first boot
thanks alot man
mrwan74 said:
could you help me with my problem?
im having trouble with my device rooting,after the first boot my device freezes up and wont respond.
it seems that samsung patched some of the vulnerabilities used by the bypasses to achieve root,
after the august update. the device is unable to sustain the NO Verity OPT encrypt , the device seems to re-encrypt it self after the first boot
thanks alot man
Click to expand...
Click to collapse
I see Samsung reinforced the security I'm trying to do something about that. If you want a stable rom I suggest you to install the soldier9312 rom:
https://forum.xda-developers.com/ga...fd-n-stock-rom-soldier9312-1-0-t3771346/page1
frauchgu10 said:
I see Samsung reinforced the security I'm trying to do something about that. If you want a stable rom I suggest you to install the soldier9312 rom:
https://forum.xda-developers.com/ga...fd-n-stock-rom-soldier9312-1-0-t3771346/page1
Click to expand...
Click to collapse
okay thanks alot man i appreciate it
@frauchgu10
i came upon some new information that maybe would be helpful
ashyx ,a recognized contributor to the xda community said ,and i quote the following :
"Since Oreo Dm-verity flags are no longer in the Ramdisk. The flags are dtb based.
If the dtb isnt patched or dm-verity disabled in the kernel source then rooting will likely cause a boot loop.
Same goes for disabling forced encryption, the flags are no longer in the Ramdisk fstab, but usually located in the Vendor partition.
Magisk attempts to hex patch the kernel, but when Samsung update the firmware the hex patch offsets change and patching fails."
i hope this helps man
I truly appreciate everyone’s efforts and commitments Thank you for taking time out of your personal time to this :good::good::good::good:
Hello guys, i just got home from the OnePlus popup event in Amsterdam. And i just finished rooting the OnePlus 6T.
Requirements: ADB/Fastboot
First unlock your bootloader if you haven't already done it, there are many tutorials on the internet.
Download Blu_Sparks OP6 TWRP 9.86(.img and .zip) or newer.
Then boot into bootloader and do: fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
When you're in TWRP go to Advanced>Adb sideload and start it.
Then do: adb sideload twrp-3.2.3-x_blu_spark_v9.86_op6.zip
After that installs, reboot recovery. Then go to advanced>adb sideload and start it again
Then do: adb sideload Magisk-v17.3.zip
after that finished just reboot back to oos and you're rooted!
Blu Spark twrp: https://forum.xda-developers.com/devdb/project/?id=27466#downloads
Magisk: https://github.com/topjohnwu/Magisk/releases
I'm the first rooted earopean OP6T consumer ever.
If you need any help ask me on my telegram group: https://t.me/xOP6T
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
..
mingo_mgx said:
Hello guys, i just got home from the OnePlus popup event in Amsterdam. And i just finished rooting the OnePlus 6T.
Requirements: ADB/Fastboot
First unlock your bootloader if you haven't already done it, there are many tutorials on the internet.
Download Blu_Sparks OP6 TWRP 9.86(.img and .zip) or newer.
Then boot into bootloader and do: fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
When you're in TWRP go to Advanced>Adb sideload and start it.
Then do: adb sideload twrp-3.2.3-x_blu_spark_v9.86_op6.zip
After that installs, reboot recovery. Then go to advanced>adb sideload and start it again
Then do: adb sideload Magisk-v17.3.zip
after that finished just reboot back to oos and you're rooted!
Blu Spark twrp: https://forum.xda-developers.com/devdb/project/?id=27466#downloads
Magisk: https://github.com/topjohnwu/Magisk/releases
I'm the first rooted OP6T user ever.
Click to expand...
Click to collapse
Can i ask you a little help to make a dedicated and better twrp?
mingo_mgx said:
Hello guys, i just got home from the OnePlus popup event in Amsterdam. And i just finished rooting the OnePlus 6T.
Requirements: ADB/Fastboot
First unlock your bootloader if you haven't already done it, there are many tutorials on the internet.
Download Blu_Sparks OP6 TWRP 9.86(.img and .zip) or newer.
Then boot into bootloader and do: fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
When you're in TWRP go to Advanced>Adb sideload and start it.
Then do: adb sideload twrp-3.2.3-x_blu_spark_v9.86_op6.zip
After that installs, reboot recovery. Then go to advanced>adb sideload and start it again
Then do: adb sideload Magisk-v17.3.zip
after that finished just reboot back to oos and you're rooted!
Blu Spark twrp: https://forum.xda-developers.com/devdb/project/?id=27466#downloads
Magisk: https://github.com/topjohnwu/Magisk/releases
I'm the first rooted OP6T user ever.[/QUOTE
Is it possible..
After boot the twrp> flash twrp zip> boot on twrp> flash magisk> boot to OOS..?
Click to expand...
Click to collapse
you can also ROOT OP6T with the magiskmanager to patch the boot.img
Can we skip the second install (adb sideload twrp zip) to just sideload Magisk and keep stock recovery for now
Can confirm, this works on my 6T also.
Striatum_bdr said:
Can we skip the second install (adb sideload twrp zip) to just sideload Magisk and keep stock recovery for now
Click to expand...
Click to collapse
Auto answering, it works without flashing for good twrp, just adb sideload Magisk zip once you've booted into temporary twrp img
Don't forget to install Magiskmanager apk then.
Will evidently need to be repeated at each OOS update if boot is replaced
What's the correct procedure when an OOS OTA is released?
Are we safe to install and then just reflash TWRP and Magisk?
Striatum_bdr said:
Auto answering, it works without flashing for good twrp, just adb sideload Magisk zip once you've booted into temporary twrp img
Don't forget to install Magiskmanager apk then.
Will evidently need to be repeated at each OOS update if boot is replaced
Click to expand...
Click to collapse
Why need the magisk zip to be sideloaded..
Can not be just flashed through the temporary twrp?
iaTa said:
What's the correct procedure when an OOS OTA is released?
Are we safe to install and then just reflash TWRP and Magisk?
Click to expand...
Click to collapse
You need to keep stock recovery to be able to use OTA, To use TWRP you'll have to download the whole oos ROM, flash it and then you need to reflash TWRP and magisk as there is no separate recovery partition on op6 /6t
---------- Post added at 04:47 PM ---------- Previous post was at 04:45 PM ----------
cultofluna said:
Why need the magisk zip to be sideloaded..
Can not be just flashed through the temporary twrp?
Click to expand...
Click to collapse
Because it's temporary you have to use sideload, as TWRP is present only in ram, and it seems that the op6 version have difficulties to decrypt op6t data partition if I understood correctly. And because I didn't want to flash for good TWRP on the phone to keep stock recovery.
cultofluna said:
Why need the magisk zip to be sideloaded..
Can not be just flashed through the temporary twrp?
Click to expand...
Click to collapse
Well when we boot the op6 twrp on our op6t's it doesnt ask to decrypt, so everything is in jibberish.
iaTa said:
What's the correct procedure when an OOS OTA is released?
Are we safe to install and then just reflash TWRP and Magisk?
Click to expand...
Click to collapse
When you get an OTA update it will download the full rom so it will be around 1,5gb. Just install it when you recieve it, and after that do the steps again to get root again.
mingo_mgx said:
I'm the first rooted OP6T user ever.
Click to expand...
Click to collapse
Doubt it.
feimummy said:
you can also ROOT OP6T with the magiskmanager to patch the boot.img
Click to expand...
Click to collapse
can u please elaborate sir ??
freakzapster said:
can u please elaborate sir ??
Click to expand...
Click to collapse
It's not very easy as you need to extract boot.img from the full oos zip(or extract it from your phone with fastboot), patch the boot img, then fastboot flash it back. Far more simple to to it as explained. And you need a computer anyway.
And with the new slot A/B architecture you need anyway a computer each time you flash a ROM, as you need to reinstall TWRP each time, due to the lack of recovery partition here (it's been 'replaced' by vendor partition necessary for Treble compatibility) .
@mingo_mgx: I have done a post here
Thanks for sharing the info :good:
ABotelho23 said:
Doubt it.
Click to expand...
Click to collapse
Yes he is, he was one of the few getting a Oneplus 6T on the 31st of October, and if there's no Guide to root yet, most of the users won't bother with unlocking BL
I had rooted my 6T and was installing midnight core magisk module. After flashing it in magisk i rebooted the phone and now im stuck in bootloop. I tried sideloading Magisk Uninstaller, But it gives me some error. Tried sideloading magisk, but still stuck in bootloop. Any suggestions?
So over in the LG V20 forum a lot of people are finding out that installing Magisk 20.2 throws the phone into Fastboot mode.
https://forum.xda-developers.com/v20/help/direct-installing-magisk-update-wiped-t4028705
https://forum.xda-developers.com/v20/how-to/warning-dont-upgrade-version-magisk-20-2-t4028577
Seems the only fix is to revert back to Magisk 20.1 after flashing the stock boot image.
omega552003 said:
So over in the LG V20 forum a lot of people are finding out that installing Magisk 20.2 throws the phone into Fastboot mode.
https://forum.xda-developers.com/v20/help/direct-installing-magisk-update-wiped-t4028705
https://forum.xda-developers.com/v20/how-to/warning-dont-upgrade-version-magisk-20-2-t4028577
Seems the only fix is to revert back to Magisk 20.1 after flashing the stock boot image.
Click to expand...
Click to collapse
I have the same in LG G6.
It only kills boot.img, the system cannot boot and the smartphone remains in fastboot mode.
If you have TWRP recovery and you use Magisk or other boot.img modification tools, you should always have a backup with the latest boot.img
After restoring boot.img from a backup (before upgrading Magisk), you will not have to install any earlier working Magisk.
LG-H870 V30a
Doing the same thing on my Razer Phone 2. Magisk 20.1 working fine.
This is exactly what happened to me. I lost all my data trying to figure out what is going on. Now flashing Stock Root Oreo. Damn it.
BeardKing said:
Doing the same thing on my Razer Phone 2. Magisk 20.1 working fine.
Click to expand...
Click to collapse
You running arter97's kernel?
I just upgraded on my G5, but didnt reboot yet. Can I flash 20.1 and be good?
omega552003 said:
So over in the LG V20 forum a lot of people are finding out that installing Magisk 20.2 throws the phone into Fastboot mode.
...
Seems the only fix is to revert back to Magisk 20.1 after flashing the stock boot image.
Click to expand...
Click to collapse
slavomes said:
I have the same in LG G6.
It only kills boot.img, the system cannot boot and the smartphone remains in fastboot mode.
If you have TWRP recovery and you use Magisk or other boot.img modification tools, you should always have a backup with the latest boot.img
After restoring boot.img from a backup (before upgrading Magisk), you will not have to install any earlier working Magisk.
LG-H870 V30a
Click to expand...
Click to collapse
totalnoob34 said:
I just upgraded on my G5, but didnt reboot yet. Can I flash 20.1 and be good?
Click to expand...
Click to collapse
I had this happen with my G5 and 20.1 today. Had to boot into TWRP with the hardware buttons and restore the boot partition from my latest TWRP backup to bring the phone back to life.
jdc said:
I had this happen with my G5 and 20.1 today. Had to boot into TWRP with the hardware buttons and restore the boot partition from my latest TWRP backup to bring the phone back to life.
Click to expand...
Click to collapse
I don't have a twrp backup, though. Was it an image file? I think magisk creates one automatically.
Sent from my LG-H850 using XDA Labs
totalnoob34 said:
I don't have a twrp backup, though. Was it an image file? I think magisk creates one automatically.
Sent from my LG-H850 using XDA Labs
Click to expand...
Click to collapse
Check this.
Someone wrote about this backup files. I have 3 folder with different files, so you have to know which is latest backup.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LG-H870 V30a
Let's try to figure out why things aren't working... If you're willing to help, take a look here:
https://forum.xda-developers.com/ap...v1-universal-systemless-t3432382/post81394545
slavomes said:
Check this.
Someone wrote about this backup files. I have 3 folder with different files, so you have to know which is latest backup.View attachment 4918541View attachment 4918543
LG-H870 V30a
Click to expand...
Click to collapse
It is easy. Just check the date and time files are created. Then identify the file that has a time stamp close to the time you updated Magisk to 20.2. That particular file is the right backup.
Confirm the problem. I own an Lg G3 D855 with the v30o. Fortunately i messed up things one day before trying to fix the fail of safetynet. A module caused my phone bootloop so i manually removed the module with the TWRP from the /data dir. So when i got the update 20.2 my phone had the same issue, my mind directly went to Magisk and installed the 20.1 via TWRP and everything's fine again.
I've installed Magisk 20.1 via Orange Fox Recovery. Still hanging in fastboot. (Official TWRP can't mount /data.)
Any suggestions? LG G6.
Cloonix said:
I've installed Magisk 20.1 via Orange Fox Recovery. Still hanging in fastboot. (Official TWRP can't mount /data.)
Any suggestions? LG G6.
Click to expand...
Click to collapse
G6 here, same issue. I dirty flashed my ROM and Magisk 19.3 and am back in business.
Nothing special about 19.3, it was just the version I happened to have a zip handy.
Latest magisk 20.3 canary (20202) working fine on lg g5 android 9 and 10.
Sent from my LG G5 using XDA Labs
20.3 and still the same issue. Reverted again to 20.1 (LG G3)
leopseft said:
20.3 and still the same issue. Reverted again to 20.1 (LG G3)
Click to expand...
Click to collapse
The problem that this thread is about, for the G5, G6, V20, etc, has been confirmed to be fixed with Magisk v20.3.
So, you might have a different issue and need to figure out what that is and provide details about it.
Didgeridoohan said:
The problem that this thread is about, for the G5, G6, V20, etc, has been confirmed to be fixed with Magisk v20.3.
So, you might have a different issue and need to figure out what that is and provide details about it.
Click to expand...
Click to collapse
It sure works on my G6
omega552003 said:
So over in the LG V20 forum a lot of people are finding out that installing Magisk 20.2 throws the phone into Fastboot mode.
https://forum.xda-developers.com/v20/help/direct-installing-magisk-update-wiped-t4028705
https://forum.xda-developers.com/v20/how-to/warning-dont-upgrade-version-magisk-20-2-t4028577
Seems the only fix is to revert back to Magisk 20.1 after flashing the stock boot image.
Click to expand...
Click to collapse
how . pleas tell are we to flash a stock boot image when computer fastboot is not recognised by phone fastboot?
computer see's and id's phone. phone does not see computer.
fast boot is the onlything working on the phone. perioud.
Just curious if anyone has any insight as to whether I can use the Magisk app to patch the newest boot.img (12.5.1.0 global / Android 11 / mi9t pro) and whether it will go smoothly if I install it via fastboot flash boot patchedmagiskhere.img?
I just updated the device using the clean_all mode on MiFlash and everything looks to be working fine;
No TWRP or custom recovery installed
Bootloader in unlocked state
As the update is so new I just wanted to check if anyone had any experience before I go ahead. There's also the old method of flashing magisk as a .zip via TWRP which is now 'depreciated'. As the device says 'Ramdisk NO' it implies Magisk may need to be used in 'recovery mode' (i.e. patched recovery.img and vol+power on every boot) but it worked just fine in MIUI11 so I don't think that's right.
Update: If you've come here looking to find out how to do this then I added instructions in this post.
Can't find answers so I might try fastboot boot patched_magisk.img later today. In theory this'll let me test a patched boot.img instead of going in blind with fastboot flash boot patched_magisk.img so that the boot.img isn't flashed, just booted. If it works I assume I can probably just select Direct Install in Magisk.
droident said:
Can't find answers so I might try fastboot boot patched_magisk.img later today. In theory this'll let me test a patched boot.img instead of going in blind with fastboot flash boot patched_magisk.img so that the boot.img isn't flashed, just booted. If it works I assume I can probably just select Direct Install in Magisk.
Click to expand...
Click to collapse
Hey let me know if you find a solution for this.
I upgarded to this version via TWRP last night. Tried flashing Magisk via TWRP and it kept boot looping into TWRP.
Had to re-flash the rom again in order to boot into the system.
I tried patching the stock recovery image but couldn't get the system to boot into Magisk mode. Tried the Volume Up + Power and let go on splash screen combo but it kept going to stock recovery.
Any help would be appreciated. I'll go crazy having to use the phone without root.
Update: I tried what you mentioned. Manually booting patched boot image. No luck. After showing the MIUI logo for a long time it goes back to recovery. I guess it's basically the same as flashing via TWRP.
shajman said:
Hey let me know if you find a solution for this.
I upgarded to this version via TWRP last night. Tried flashing Magisk via TWRP and it kept boot looping into TWRP.
Had to re-flash the rom again in order to boot into the system.
I tried patching the stock recovery image but couldn't get the system to boot into Magisk mode. Tried the Volume Up + Power and let go on splash screen combo but it kept going to stock recovery.
Any help would be appreciated. I'll go crazy having to use the phone without root.
Click to expand...
Click to collapse
For Xiaomi, always patch BOOT img, not Recovery.
Do not tick Recovery option and flash to Boot partition.
Guides can be found elswhere
Important that you patch the boot img corresponding to your CURRENTLY using stock firmware (if you upgraded, you have to extract and patch its boot.img, not some older or from different Global vs Chinna or else)
zgfg said:
For Xiaomi, always patch BOOT img, not Recovery.
Do not tick Recovery option and flash to Boot partition.
Guides can be found elswhere
Important that you patch the boot img corresponding to your CURRENTLY using stock formware (if you upgraded, you have to extract and patch its boot.img, not some older or from different Global vs Chinna or else)
Click to expand...
Click to collapse
This is what I have always done (patching boot). However it does not seem to be working with v12.5.1.0
I've just tried the Canary build of Magisk as well and no luck. The MIUI splash screen stays on for a while and then it goes to Recovery.
This never happened with any of the previous ROMS (Android 10)
Not sure if I'm doing something wrong.
shajman said:
This is what I have always done (patching boot). However it does not seem to be working with v12.5.1.0
I've just tried the Canary build of Magisk as well and no luck. The MIUI splash screen stays on for a while and then it goes to Recovery.
This never happened with any of the previous ROMS (Android 10)
Not sure if I'm doing something wrong.
Click to expand...
Click to collapse
You may have modules installed and enabled, that do no more work with the new firmware
If you didn't wipe/format Data, modules are still in: /data/adb/modules
(updating firmware does not affect there)
Use TWRP, go to that folder and add an empty file named: disable
(exactly as that), to each subfolder (each subfolder corresponds to one module, you may recignize them by folder names)
Then reboot with the patched boot.img
Later, manage your modules (enable, uninstall, update) from Magisk app (once you successfully boot to Magisk)
zgfg said:
You may have modules installed and enabled, that do no more work with the new firmware
If you didn't wipe/format Data, modules are still in: /data/adb/modules
(updating firmware does not affect there)
Use TWRP, go to that folder and add an empty file named: disable
(exactly as that), to each subfolder (each subfolder corresponds to one module, you may recignize them by folder names)
Then reboot with the patched boot.img
Later, manage your modules (enable, uninstall, update) from Magisk app (once you successfully boot to Magisk)
Click to expand...
Click to collapse
You Sir are an absolute LIFE SAVER!!!!!!!
Thank you!
I also patched magisk just fine . Thanks guys for sharing your experiences; it kinda reassured me it'd probably work - I was thinking booting a patched magisk boot.img might be safer so I did that first and it booted as expected. So I just returned to fastboot and flashed it properly. Installed a few modules (the essentials; ACC, Energized, Busybox), rebooted, we're all good ^_^
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I think it's already been explained above me but for anyone who hasn't figured it out yet:
Find the recovery zip or fastboot files you updated with (if you don't have them still then go here but use the *exact* region and version - if your device isn't raphael then don't use these), open with 7zip/winrar/whatever and copy the boot.img from them to any folder on your phone. Open Magisk Manager, browse for where you copied it to and patch it; recovery mode box unticked. Then look for Magisk_patched_xxx.img (xxx part being whatever Magisk called it) in your /Downloads folder on your phone. Copy it back to your PC, fire up Tiny ADB & Fastboot.
Do a test-run with fastboot boot Magisk_patched_xxx.img first. If it boots up fine and Magisk shows as working, commit the changes by returning to fastboot with adb reboot fastboot and then the command fastboot flash boot Magisk_patched_xxx.img. Then power it up.
If the temporary boot test-run didn't work, obviously don't execute the flash boot command; power-cycling the phone will get it unstuck.
I should probably note I don't have TWRP (using stock recovery) and I don't know how that factors into this. This was done the day after a clean_all fastboot flash; read previous posts if you've used Magisk previously and updated with your data intact.
I would like to add here to use the boot.img patch method. Flashing magisk as a zip through the recovery will cause a bootloop.
Tested this on my Mi 9T Pro (12.5.1 global) with system encryption enabled.
FPSUsername said:
I would like to add here to use the boot.img patch method. Flashing magisk as a zip through the recovery will cause a bootloop.
Tested this on my Mi 9T Pro (12.5.1 global) with system encryption enabled.
Click to expand...
Click to collapse
I was tempted to do the same because it's the conventional way of installing Magisk and it's how it's always been installed.
That and mucking with something called boot.img sounds like a one-way trip to brick-street. I.e. boot.img makes me think bootloader or in other words, bad news. Although from what I've heard it turns out you can completely screw up the boot.img and you should still have access fastboot and recovery modes. But I didn't run into any problems flashing a new boot.img so I didn't find out .
droident said:
I was tempted to do the same because it's the conventional way of installing Magisk and it's how it's always been installed.
That and mucking with something called boot.img sounds like a one-way trip to brick-street. I.e. boot.img makes me think bootloader or in other words, bad news. Although from what I've heard it turns out you can completely screw up the boot.img and you should still have access fastboot and recovery modes. But I didn't run into any problems flashing a new boot.img so I didn't find out .
Click to expand...
Click to collapse
Men, patching the images is nothing new or exotic.
If you ever read Magisk guide from TJW (the aurhor of Magisk) you would well know that the method has been described there for many years (I personally used the method back since 2018 on other phones)
Besides, it has many practical advantages - if anything goes wrong you just flash the original (unpatched) image
Or, when Magisk updates (unfortunately, it does no more and who knows would it ever again, at least from the established channels like Stable or Canary), if there is a problem with the new Magisk - you just flash your previous version of img that was patched with the working version of Magisk and you are back in business
And there is also nothing impractical here - if you have proper TWRP (you do have for this phone) you don't need to flash the patched img from fastboot but simply from TWRP
You can also use TWRP backup boot.emmc.win instead of extracted boot.img - simply give boot.emmc.win to Magisk for patching (you don't need to rename it) and then flash it
So, guys, did the patched boot image worked for you? for me it did not boot up... :/
HValenti said:
So, guys, did the patched boot image worked for you? for me it did not boot up... :/
Click to expand...
Click to collapse
Of course it does work. But read carefully above. If you just upgraded without Factory reset, and if you had Magisk before, some modules (that remained installed to /data) may cause you the bootloop
And/or, you have to patch exactly the boot.img corresponding to your current firmware, not some from an older A10, etc
In such case, how do you remove the magisk modules after the update? Without root, there is no access to modules.
HValenti said:
In such case, how do you remove the magisk modules after the update? Without root, there is no access to modules.
Click to expand...
Click to collapse
Why don't you read the previous messages in this thread - post #6
Or see:
zgfg said:
Yes, it was asked/answered several times but let it be answered again
Besides adb, there are two other ways of disabling (or even uninstalling) the remained modules
You have to flash your patched boot.img, then
a) Reboott to Android Safe mode, then reboot again to 'normal' mode.
All modules will be disabled but also you will have to re-enable Magisk Hide again
b) Use TWRP (if appropriate for your device), Advanced, File Manager, go to /data/adb/modules and to each folder (foder = module, you can recognize modules by folder names or by reading the textual file module.prop you will find inside) put a file that must be named: disable (exactly as that)
Click to expand...
Click to collapse
Or simoly read the Magisk Wiki, available from Magisk Github (linked from Magisk app):
Module Issues:Magisk and MagiskHide Installation and Troubleshooting guide
www.didgeridoohan.com
zgfg said:
For Xiaomi, always patch BOOT img, not Recovery.
Do not tick Recovery option and flash to Boot partition.
Guides can be found elswhere
Important that you patch the boot img corresponding to your CURRENTLY using stock firmware (if you upgraded, you have to extract and patch its boot.img, not some older or from different Global vs Chinna or else)
Click to expand...
Click to collapse
My Ramdisk says "no" should I still patch boot.img?
not sure how to delete. It does work
Vanmanman said:
My Ramdisk says "no" should I still patch boot.img?
not sure how to delete. It does work
Click to expand...
Click to collapse
It says for everybode on MUII No for Ramdisk but it was discussed snd written everywhere and zillion times that Xiaomi users have to patch boot img
Can I somehow extract boot.img from phone without custom recovery and root?
Rejerf said:
Can I somehow extract boot.img from phone without custom recovery and root?
Click to expand...
Click to collapse
Download the full OTA for your phone, and from it, you can extract the boot.img.
Link for the OTA download and instructions on how to do it is provided here: https://forum.xda-developers.com/t/...-5-1-0-edit-yes-it-does.4299669/post-85271375
Please does someone upgraded succefully from 12.0.5.0 to 12.5.1.0 with root and without wiping data ?
If yes, how did you flashed the 12.5 ROM because TWRP recovery does no support MIUI 12.5 A11 encryption, so I guess flashing it from TWRP is not recomanded.
I am quite afraid to be forced to wipe everything and preserve root is mandatory for me so I did not tried to upgrade for now.
Thank you in advance.