I just managed to (after spending 2 days figuring this out) get TWRP recovery in my old Xperia Z2 that had android version 6.0.1 Marshmallow. Currently running TWRP 3.0.2-0 (idk if it matters), bootloader is also unlocked. Was installed with SuperUs, and cleaned from it completely. But it never gave me the option to restore back to boot img.
I've been browsing the forum, trying so many solutions but nothing has worked yet. Any help would be appreciated ASAP. And I cant currently access the logs, BUT I have manually written down what the log is and I have no idea what to make of it.
I looked at BootBridge but the explanation is confusing me. So I flash Magisk through another service or whatever to make it able to get flashed? I dont have any other img's or anything to replace the boot partition with, so I got no clue what to do.
* Magisk v17.1 Installer
********************
- Mounting /system, /vendor
- Found boot/ramdisk image: /dev/block/mmcblk0p14
- Device platform: arm
- Constructing environment
- Unpacking boot image
- Sony ELF32 Format detected
- Please use BootBridge from @AdrianDC to flash Magisk
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/MAGISK/Magisk-v17.1(1700).zip'
Updating partition details...
...done
Edit: I dont have a img backup of the old rom, unfortunately
Alright, a break made me realize how it works. But the bad news is that my phone is now in the boot loop haha. If anyone have additional information on how this all works, that would be appreciated
Another update, now I could uninstall and reinstall magisk in TWRP without failure, but I still get stuck in boot loop so it doesnt work obviously
Another Edit: If I do manage to factory reset the phone back to its original software, is it possible to do a better setup this time and create a good backup? Since SuperUs didnt allow me to backpedal to an earlier state
Alright managed to restore and once again flash my phone so that I can use TWRP, but im still locked by BootBridge looping my phone in bootup, when trying to install magisk v17.1
flash stock ROM
abkdmn said:
flash stock ROM
Click to expand...
Click to collapse
Managed to get it to work! Made a custom ROM from a stock version after it being patched to disable RIC. Now the only problems I have, is to get Magisk working correctly so that I can get away and pass SafetyNet
Have unlocked your bootloader?, If yes then ave you tried boot bridge by adrianDC to flash magisk successfully ?
Leave some additional information like : your ROM version, twrp version, phone model.
If you want to restart to new in order to use a custom ROM or Stock ROM with magisk and bypassing safety net leave details about those ROMs and files which you are going to use.
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.
I use a Huawei Enjoy 7 Plus (CMCC, model TRT-TL10A) with EMUI 5.1.3 (Android 7.0). I got my phone unlocked, flashed (a modded version of) TWRP 3.1.1, and then Magisk v23.0 at first. However, my phone bootlooped. Switching to Canary (23001) doesn't help either, probably because its changelog shows that it has no difference to the existing Magisk v23.
So I wanted to open an issue about this on the Magisk GitHub repo. However, it asked me to provide dmesg data, but I have no idea on how to do such a thing when my phone is unable to start up.
Please tell me how to do this. If there is any workaround with the bootloop issue, please let me know. Thanks.
MightyPandora8 said:
I use a Huawei Enjoy 7 Plus (CMCC, model TRT-TL10A) with EMUI 5.1.3 (Android 7.0). I got my phone unlocked, flashed (a modded version of) TWRP 3.1.1, and then Magisk v23.0 at first. However, my phone bootlooped. Switching to Canary (23001) doesn't help either, probably because its changelog shows that it has no difference to the existing Magisk v23.
So I wanted to open an issue about this on the Magisk GitHub repo. However, it asked me to provide dmesg data, but I have no idea on how to do such a thing when my phone is unable to start up.
Please tell me how to do this. If there is any workaround with the bootloop issue, please let me know. Thanks.
Click to expand...
Click to collapse
Don't know how to pull it. But to fix your situation. Flash the stock boot img via fastboot. Remove magisk app. Install canary then repatch your boot img via magisk then flash the patched boot.img through twrp or fastboot
I would try to gain root before flashing twrp. Then you know where the issue lies
Prerequisites:
Bootloader unlocked
TWRP
Bootloader unlock guide : https://forum.xda-developers.com/t/guide-bootloader-unlock-on-rui-2-0-based-on-android-11-r.4286451/
TWRP : https://forum.xda-developers.com/t/twrp-recovery-unofficial-for-realme-x7-max-rmx3031.4336503/
Download this version of Magisk Manager "Magisk Alpha (706a4922-alpha)" from file attached below because stable version is causing bootloop, for now
Steps :
To Root Your Phone Install above mentioned version of magisk manager
Pull your boot.img from recovery
adb pull /dev/block/by-name/boot boot.img
check boot image in directory you extracted your adb zip
Patch your pulled boot.img from apk given below
Flash it via Twrp in Boot Partition
Now u successfully rooted your device
Troubleshooting:
One issue I personally faced was driver problem (Fastboot Device Not detecting) which I was easily able to fix with the help of this video : https://cutt.ly/wEEit33
use this only if you are also facing this issue
Sources : here
Sir can i flash the magisk alpha from twrp by converting the apk into .zip then flash it directly from twrp.??
Aditya8520 said:
Sir can i flash the magisk alpha from twrp by converting the apk into .zip then flash it directly from twrp.??
Click to expand...
Click to collapse
NO, that's not how it works
Always getting bootloop. Tried multiple magisk versions, multiple ways to extract boot.img, but always getting only to white "realme" logo. Im on A18 btw
borkakoz said:
Always getting bootloop. Tried multiple magisk versions, multiple ways to extract boot.img, but always getting only to white "realme" logo. Im on A18 btw
Click to expand...
Click to collapse
Read carefully, I have metioned in post "Download this version of Magisk Manager "Magisk Alpha (706a4922-alpha)" from file attached below because stable version is causing bootloop, for now"
Harsh raj sah said:
Read carefully, I have metioned in post "Download this version of Magisk Manager "Magisk Alpha (706a4922-alpha)" from file attached below because stable version is causing bootloop, for now"
Click to expand...
Click to collapse
As I mentioned in my reply, I tried multiple versions of Magisk, and version from post too. Is there any other way to get that patched boot img?
I also noticed that flashing process is almost instant. It takes only like a split second. Can it be the issue?
it's not stable at all
are there any other options?
i had arranged all the things fix all the issue and make an article of root realme x7 max. all the command is provided here even downloads file
HELLO THERE
Here's a list of all working roms, twrps, kernels and more for MediaPad T5.
If you want a guide of how to install, go to this post.
Report issues to T5 Support group from here
I'm making a MEGA folder with all specific (needed to work) and non-specific zips, kernels and twrps
N-S --> CAN USE NON-SPECIFIC ZIPS (may not work)
S --> NEEDS SPECIFIC ZIPS TO WORK ( can use non-specific compatible too)
PR --> Pre Rooted ROM
PRX --> Pre Rooted but doesn't work
UR --> Un Rooted ROM
U --> Untested ROMs (may work but I've not tested it yet)
M --> MODDED FOR T5 COMPATIBILITY
Modded roms are tested and proved to work. All the roms in the list are
compatibles, but newer versions may cause some installation errors.
Join the telegram group if you have any issue and I'll take a look as fast as I can.
PRX - LineageOS by @DarkJoker360 N-S
LeaOS by @AltairFR S U
PR - CrDroid by @Hami_Do N-S M
I tried the following roms on AGS2-W09
Did not boot:
lineage-18.1-20220224-UNOFFICIAL-iceows-pra
crdrom-v313+211013-arm64-avZ
crDroid_v7.10_11-WAS-21092021
Too large to install:
crdrom-v315+220202-iceows-pra
Works:
lineage-18.1-20211106-UNOFFICIAL-prague
CryptLoad said:
I tried the following roms on AGS2-W09
Did not boot:
lineage-18.1-20220224-UNOFFICIAL-iceows-pra
crdrom-v313+211013-arm64-avZ
crDroid_v7.10_11-WAS-21092021
Too large to install:
crdrom-v315+220202-iceows-pra
Works:
lineage-18.1-20211106-UNOFFICIAL-prague
Click to expand...
Click to collapse
crdroid should work. Go to the telegram grou chat to get the modded version until I release it. crdrom is about to get fixed. Lineage too.
crDroid_v7.10_11-WAS-21092021 does work
same for:
lineage-18.1-20220523-UNOFFICIAL-prague
LeaOS-20220616-UNOFFICIAL-iceows-pra.img (uploaded 1 day ago)
It took me more than a day to figure this out but if you have flashed Magisk in one of these custom ROMs then you need to restore the original KERNEL.img and RAMDISK.img form your stock firmware, otherwise everything will boot loop (even if you restore the initial custom ROM you have flashed first time). This is mostly because Magisk modifies the boot.img to apply the root patch.
As a side note here: you can install magisk.zip through TWRP immediately after reflashing your starting/initial custom ROM to be able to boot as before.
To do this I have used HuaweiFirmwareFinder (website + proxy app) to download update.app and then extracted the imgs with HuaweiUpdateExtractor and then used fastboot to flash the images.
It is useful if you have remembered your previous stock version as there can be conflicts with other images (like erecovery or recovery_ramdisk) if they have different versions.
Also I have never used TWRP to do the inital flashings, just fastboot because I see many threads here with people bricking their tablets.
denzelcris said:
crDroid_v7.10_11-WAS-21092021 does work
same for:
lineage-18.1-20220523-UNOFFICIAL-prague
LeaOS-20220616-UNOFFICIAL-iceows-pra.img (uploaded 1 day ago)
It took me more than a day to figure this out but if you have flashed Magisk in one of these custom ROMs then you need to restore the original KERNEL.img and RAMDISK.img form your stock firmware, otherwise everything will boot loop (even if you restore the initial custom ROM you have flashed first time). This is mostly because Magisk modifies the boot.img to apply the root patch.
As a side note here: you can install magisk.zip through TWRP immediately after reflashing your starting/initial custom ROM to be able to boot as before.
To do this I have used HuaweiFirmwareFinder (website + proxy app) to download update.app and then extracted the imgs with HuaweiUpdateExtractor and then used fastboot to flash the images.
It is useful if you have remembered your previous stock version as there can be conflicts with other images (like erecovery or recovery_ramdisk) if they have different versions.
Also I have never used TWRP to do the inital flashings, just fastboot because I see many threads here with people bricking their tablets.
Click to expand...
Click to collapse
This makes sense as flashing the boot also flashes the KERNEL and RAMDISK (correct me if I'm wrong). But do you know if you should do the same if you flash the system? I'm trying to flash a GSI but my device goes to a boot loop after flashing the system.
crDroid is working...just dont forget to unpack the x.z-file
Hi, anyone can help me?. I'm trying to install leaos on my Huawei Mediapad T5 (i'm not new on this), but everytime i reboot It when It finish installing, It keeps rebooting when It has to show the first configuration screen.
Nevermind, i finally got It to work