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.
Related
Hello
My Device is running on Stock Android Q BN 11.0.5.0
Recently i installed magisk in my device (keeping OTA).
When i install Magisk Module for Internal audio recording and reboot device it was stucked in bootloop.
Then i flashed stock boot img
After flashing i reboot the device and it is rebooted successfully. But Magisk and Root Access has gone.
Then after i again flash Magisk patched img created by Magisk installer but this time it is again stucked in bootloop.
I tried to flash zip with temporary Twrp but problem is not solved.
Currently i dont have Magisk installed.
Please Help Me to gain root access again
Thank you.
Please reply or DM me https://t.me/adarsh_ad007
1. Reboot to bootloader (fastboot mode) and boot into TWRP (I prefer 3.3.1-5 4pda_edition) in fastboot, go to Advanced -> File Manager -> data -> adb - > modules, and delete all files (directory) belonging to a problematic module
2. Reboot to fastboot and boot into stock boot.img thus checking that it boots;
3. if stock boots, reboot to bootloader and try to boot into magisk_patched.img thus checking that it boots;
4. After that you can make root permanent in MagiskManager, if you wish
thank you bro it diid not work. i tried but not working
Aerobatic said:
1. Reboot to bootloader (fastboot mode) and boot into TWRP (I prefer 3.3.1-5 4pda_edition) in fastboot, go to Advanced -> File Manager -> data -> adb - > modules, and delete all files (directory) belonging to a problematic module
2. Reboot to fastboot and boot into stock boot.img thus checking that it boots;
3. if stock boots, reboot to bootloader and try to boot into magisk_patched.img thus checking that it boots;
4. After that you can make root permanent in MagiskManager, if you wish
Click to expand...
Click to collapse
not working
adarsh.ad007 said:
not working
Click to expand...
Click to collapse
Which step is not working? What is final result? How can you get help if you do not describe anamnesis? No telepathists here, as far as I know.
Aerobatic said:
Which step is not working? What is final result? How can you get help if you do not describe anamnesis? No telepathists here, as far as I know.
Click to expand...
Click to collapse
I did everything what you said but problem is still there.
adarsh.ad007 said:
I did everything what you said but problem is still there.
Click to expand...
Click to collapse
Ohhhhh, why should we torture you to get answers needed to help you?
What does MagiskManager show when you boot to supposedly correct magisk_patched.img?
Can you attach screenshot or describe in detail?
Aerobatic said:
Ohhhhh, why should we torture you to get answers needed to help you?
What does MagiskManager show when you boot to supposedly correct magisk_patched.img?
Can you attach screenshot or describe in detail?
Click to expand...
Click to collapse
Thanks for you support and attention dear.
Actually i flashed PE ROM and then install magisk. Now it works.
And i was booting correct patched img.
I created it via magisk manager myself.
adarsh.ad007 said:
..And i was booting correct patched img. I created it via magisk manager myself.
Click to expand...
Click to collapse
Maybe there was still something that skipped your attention. Pls look at scenario:
- patch stock boot image using MagiskManager with, let us say, Magisk 20.1; boot this patched image, make direct install - root got;
- update Magisk to. e.g., 20.3 installing Magisk-v20.3(20300).zip (root got, everything ok);
- play with new Magisk modules, install wrong version, get bootloop;
- make some otherwise correct steps, like reflashing stock boot;
- finally try to get root with boot image previously patched by Magisk 20.1.
Result: no root, MagiskManager does not accept Magisk 20.1., it expects boot image patched with 20.3
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?
This Guide is intended for OP7 Pro Devices that are already running Android 11 after the May 2021 TMO OTA.
DO NOT flash the provided boot image if your device has not been updated to android 11.
REQUIREMENTS
Before proceeding, you must make sure your GM1915 bootloader has been unlocked, and you have the required tools installed on your PC.
For additional information, please see section 1 of the TMO OP7 Pro Unlock/TWRP Thread
Please Note: TWRP is not compatible with Android 11 on the GM1915 at this time. Do not attempt to install it.
Thanks to @justencase6 for providing a copy of the 11.0.1.2 OTA package.
INSTRUCTIONS
MAKE SURE you flash the correct boot image. Only flash the boot image of the OOS version you are running or you will have boot issues.
Install the latest Magisk Manager on your device if it is not already installed.
Download the patched boot image that matches your current OOS version from below.
Copy the downloaded image to your fastboot directory.
To make things a little easier, you can rename this file to "boot.img"
Reboot your device to the bootloader using the advanced reboot menu or
Code:
adb reboot bootloader
Confirm your device is detected by fastboot :
Code:
fastboot devices
Flash the patched boot image to the boot partition :
Code:
fastboot flash boot_a magisk-patched-OOS-11.0-boot.img
fastboot flash boot_b magisk-patched-OOS-11.0-boot.img
Reboot device :
Code:
fastboot reboot
Your device should now be rooted. Run Magisk Manager and confirm the installation status. You should see the following under "Magisk"
Code:
Installed: 23.0 (23000) A/B: Yes
Ramdisk: Yes SAR: Yes
DOWNLOADS
11.0.1.2
magisk-patched-OOS-11.0.1.2-boot.img
MD5: bad8c767748e49e818d8b5ab698ed6f8
11.0.1.3
magisk_patched-boot-11.0.1.3.img
MD5: 26864b63727bba2c64ac929838d11f08
11.0.1.4
magisk-patched-boot-11.0.1.4.img
MD5: 0e6767c739b9cbf9e99562d01472d9c0
11.0.1.5
Due to problems updating and 11.0.1.5 being an incremental update, this image is not available
11.0.1.6
magisk_patched_boot_11.0.1.6.img
MD5: 765319532315e6a7a442b7bdaf2dfa57
stock_boot_11.0.1.6.img
MD5: eed8d7a8e338400f5b57fea41aae5a73
11.0.1.7
Incremetal Update - No Boot Image Available
11.0.1.8
magisk_patched_boot_11.0.1.8.img
MD5: bb820d2cde0f6dae11fc32d233aecf60
stock_boot_11.0.1.8.img
MD5: ffddf17538204f85ee98e1f805a4e103
I will continue to release these for future OTA's. I don't monitor TMO release dates, I just wait for the OTA notification on my phone so it may take longer for me to find out there is an update.
Feel free to PM me when a new update is pushed out.
weakNPCdotCom said:
This Guide is intended for OP7 Pro Devices that are already running Android 11.0.1.2 after the May 2021 TMO OTA.
DO NOT flash the provided boot image if your device has not been updated to android 11.
REQUIREMENTS
Before proceeding, you must make sure your GM1915 bootloader has been unlocked, and you have the required tools installed on your PC.
For additional information, please see section 1 of the TMO OP7 Pro Unlock/TWRP Thread
Please Note: TWRP is not compatible with Android 11 on the GM1915 at this time. Do not attempt to install it.
Thanks to @justencase6 for providing a copy of the latest OTA package.
INSTRUCTIONS
Install Magisk Manager v23 on your device if it is not already installed.
Copy "magisk-patched-OOS-11.0-boot.img" to your fastboot directory. To make things a little easier, you can rename this file to "boot.img"
Reboot your device to the bootloader using the advanced reboot menu or
Code:
adb reboot bootloader
Confirm your device is detected by fastboot :
Code:
fastboot devices
Flash the patched boot image to the boot partition :
Code:
fastboot flash boot_a magisk-patched-OOS-11.0-boot.img
fastboot flash boot_b magisk-patched-OOS-11.0-boot.img
Reboot device :
Code:
fastboot reboot
Your device should now be rooted. Run Magisk Manager and confirm the installation status. You should see the following under "Magisk"
Code:
Installed: 23.0 (23000) A/B: Yes
Ramdisk: Yes SAR: Yes
DOWNLOADS
magisk-patched-OOS-11.0-boot.img
MD5: bad8c767748e49e818d8b5ab698ed6f8
RELATED THREADS
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
Click to expand...
Click to collapse
Thanks for this very helpful thread. can you please provide me with both stock boot.img and patched boot image for European GM1913 running OS 11.0.1.1 GM21BA ? I have the stock image but won't boot if patched with latest magisk I've been trying for days (Also Tried Canary)
stuntora said:
Thanks for this very helpful thread. can you please provide me with both stock boot.img and patched boot image for European GM1913 running OS 11.0.1.1 GM21BA ? I have the stock image but won't boot if patched with latest magisk I've been trying for days (Also Tried Canary)
Click to expand...
Click to collapse
Im sorry but I only work with T-Mobile devices. I don't have any other firmware on hand and I do not have any way of testing things for other devices. How are you patching the boot image?
weakNPCdotCom said:
Im sorry but I only work with T-Mobile devices. I don't have any other firmware on hand and I do not have any way of testing things for other devices. How are you patching the boot image?
Click to expand...
Click to collapse
extracted the boot.img from payload.bin with python.
patched the extracted img with the latest magisk 23.0
flash the patched img with fastboot to both slots a and b
fastboot reboot aaaaaaaaand voila a nice bootloop
***********
solution
adb reboot bootloader
reflash stock img to slots a and b
fastboot reboot aaaaaaaaand voila a nice phone with no root hahaha
stuntora said:
extracted the boot.img from payload.bin with python.
patched the extracted img with the latest magisk 23.0
flash the patched img with fastboot to both slots a and b
fastboot reboot aaaaaaaaand voila a nice bootloop
***********
solution
adb reboot bootloader
reflash stock img to slots a and b
fastboot reboot aaaaaaaaand voila a nice phone with no root hahaha
Click to expand...
Click to collapse
does the device boot normally if you flash the unmodified boot image that you extracted?
are you using Magisk Manager to patch the boot image?
weakNPCdotCom said:
does the device boot normally if you flash the unmodified boot image that you extracted?
are you using Magisk Manager to patch the boot image?
Click to expand...
Click to collapse
yes, absolutely, the phone boots normally if reflashed with the unmodified boot image. and also yes I use Magisk Manager to select and patch the aforementioned image that can be found in the download folder.
stuntora said:
yes, absolutely, the phone boots normally if reflashed with the unmodified boot image. and also yes I use Magisk Manager to select and patch the aforementioned image that can be found in the download folder.
Click to expand...
Click to collapse
after a little searching, I have found some other people reporting bootloops with magisk that are caused by incompatible modules being installed.
if you had modules installed previously, you can remove them using adb shell.
Code:
adb wait-for-device shell magisk --remove-modules
It's not clear if you need to have magisk on the device first or not, but I would try this method to remove any installed modules, flash the patched boot image again, and see if that helps.
I have had twrp working with 11 from day one they released it for TMO. And I also found that if you have a boot loop you probably need to format,do to keys. Plus a nice lil trick is to disable DM Variety. Also have had root on 11 TMO but haven't been testing in 11 all my testing needs requir lowest firmware posable for exploits.
justencase6 said:
I have had twrp working with 11 from day one they released it for TMO. And I also found that if you have a boot loop you probably need to format,do to keys. Plus a nice lil trick is to disable DM Variety. Also have had root on 11 TMO but haven't been testing in 11 all my testing needs requir lowest firmware posable for exploits.
Click to expand...
Click to collapse
Can you provide a link or some context to help the rest of us get twrp working?
justencase6 said:
I have had twrp working with 11 from day one they released it for TMO. And I also found that if you have a boot loop you probably need to format,do to keys. Plus a nice lil trick is to disable DM Variety. Also have had root on 11 TMO but haven't been testing in 11 all my testing needs requir lowest firmware posable for exploits.
Click to expand...
Click to collapse
yeah, i dont believe you lol. TWRP for OOS 11 was only released for guacamole last week, and it still doesnt work for the GM1915
weakNPCdotCom said:
yeah, i dont believe you lol. TWRP for OOS 11 was only released for guacamole last week, and it still doesnt work for the GM1915
Click to expand...
Click to collapse
So how do u think I pulled the OTA 11 tmobile version, been away for a bit. I'll find the copy I have been using.
A way to get twrp and not loose it, wile in twrp android 10 going to 11.flash the 11 package right after flash the latest twrp check if in A or B then reboot recovery do the same to the other slot.the stock packs have there own recovery this will help maintain twrp.
weakNPCdotCom said:
yeah, i dont believe you lol. TWRP for OOS 11 was only released for guacamole last week, and it still doesnt work for the GM1915
Click to expand...
Click to collapse
If this is not enough prof then message me
11.0.1.3 boot image has been added to OP
justencase6 said:
If this is not enough prof then message me
Click to expand...
Click to collapse
oh, you are decrypted. I would rather not have to do that. also, you are running GM21AA but TMO is GM31CB.
In Nebrassy's repo we are one of a few that aren't supported
{
"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"
}
This is a gm1915, it still has the sim lock on it. I just been able to change from 18831 to 18821. Use *#391# to switch to India.
Also I know how to generate the qr code to decrypt in the *#*#5646#*#* just need imei to generate the code
who can explain me step by step please i did not understand correctly i downloaded the file 11.0.1.3 and i dont know what to do next
weakNPCdotCom said:
This Guide is intended for OP7 Pro Devices that are already running Android 11.0.1.2 or 11.0.1.3 after the May 2021 TMO OTA.
DO NOT flash the provided boot image if your device has not been updated to android 11.
REQUIREMENTS
Before proceeding, you must make sure your GM1915 bootloader has been unlocked, and you have the required tools installed on your PC.
For additional information, please see section 1 of the TMO OP7 Pro Unlock/TWRP Thread
Please Note: TWRP is not compatible with Android 11 on the GM1915 at this time. Do not attempt to install it.
Thanks to @justencase6 for providing a copy of the 11.0.1.2 OTA package.
INSTRUCTIONS
MAKE SURE you flash the correct boot image. Only flash the boot image of the OOS version you are running or you will have boot issues.
Install Magisk Manager v23 on your device if it is not already installed.
If you are on 11.0.1.2, copy "magisk-patched-OOS-11.0.1.2-boot.img" to your fastboot directory.
If you are on 11.0.1.3, copy "magisk_patched-boot-11.0.1.3.img" to your fastboot directory.
To make things a little easier, you can rename this file to "boot.img"
Reboot your device to the bootloader using the advanced reboot menu or
Code:
adb reboot bootloader
Confirm your device is detected by fastboot :
Code:
fastboot devices
Flash the patched boot image to the boot partition :
Code:
fastboot flash boot_a magisk-patched-OOS-11.0-boot.img
fastboot flash boot_b magisk-patched-OOS-11.0-boot.img
Reboot device :
Code:
fastboot reboot
Your device should now be rooted. Run Magisk Manager and confirm the installation status. You should see the following under "Magisk"
Code:
Installed: 23.0 (23000) A/B: Yes
Ramdisk: Yes SAR: Yes
DOWNLOADS
magisk-patched-OOS-11.0.1.2-boot.img
MD5: bad8c767748e49e818d8b5ab698ed6f8
magisk_patched-boot-11.0.1.3.img
MD5: 26864b63727bba2c64ac929838d11f08
RELATED THREADS
T-Mobile OnePlus 7 Pro OOS 11.0.1.2 Stock Firmware (Root Optional)
Click to expand...
Click to collapse
Which fastboot directory are you talking about?
Thank you for this guide.
Can you make an OTA Update patched for Tmobile ? GM1915
Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in fastboot using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco
Marcolo88 said:
Hi, i have a 11T (not the Pro version) and i unlocked it yesterday.
I want root it (like i did with my previous 9T), but it goes into bootloop.
My stock miui version is: 12.5.8.0(RKWEUXM). This are the operation i did:
- installed magisk 23 APK from the git page
- copied the boot image from the image of the same version (i also tried to extract the image from the payload)
- patched with magisk
- flashed in recovery (stock recovery) using fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img
- reboot the phone.
If i flash again the original boot.img, of course bootloop disappear!
I also tried to boot in recovery mode for clean the magisk modules without success (but is a fresh install, i don't think that the restore from xiaomi cloud can copy also the magisk modules).
I don't understand why i'm the only one in the web that have this problem. Someone have idea of what i can try to do?
For now, i want try to keep the original recovery for install the OTA update, but if all doesn't work i'll try the twrp installation (i think with this recovery all problem will go away).
Thank you very much
Marco
Click to expand...
Click to collapse
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.
Belpek said:
In My pro version. I renamed the patched boot.img to just boot.img before i flashed it.
Click to expand...
Click to collapse
And flash it in fastboot not recovery.
Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I flashed too in recovery, i wrote wrong (now i edit my message).
I'll try your suggestion to rename the img, but in the previous Xiaomi i never did it and it worked .
Thank you very much
Belpek said:
And flash it in fastboot not recovery.
Click to expand...
Click to collapse
I tried just now and it doesn't work also with the file renamed
Do you unlock bootloader?
zelenko said:
Do you unlock bootloader?
Click to expand...
Click to collapse
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?
Marcolo88 said:
Yes i unlocked, and if I watch the status, it says unlocked!.
What I can also do?
Click to expand...
Click to collapse
Flash in fastboot...
leobak said:
Flash in fastboot...
Click to expand...
Click to collapse
This i did but it goes into boot loop
you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?
nousernamesorry said:
you need to use the correct boot.img this issue occurs when the boot.img is not correct according to the version of the ROM.
from where are you downloading the patched image?
Click to expand...
Click to collapse
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.
I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.
MocnePifko said:
I know you got it working already but I flashed mine with XiaomiADBFastbootTools.jar and never done that whole "fastboot flash boot_a patched_image.img and, after, fastboot flash boot_b patched_image.img" thingy in ADB. It works no problem every time I do it after an update. I know you can install directly from Magisk after applying an OTA but I prefer this metod. Zygisk will be needet to get root on A12 though and it doesn't have Magisk hide which means I'll never get those banking apps to work anymore thill someone figures out a better method I'll wait with the A12 update. Just my two cents.
Click to expand...
Click to collapse
For me, with zygisk, i can make work all application with root checker (like banking apps).
Marcolo88 said:
With magisk canary it works!
I downloaded the image from here: https://xiaomifirmwareupdater.com/miui/agate/stable/V12.5.8.0.RKWEUXM/
is the correct image.
I don't like the new implementations in canary version, but for now it worked only with this version.
Click to expand...
Click to collapse
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.
louiswong2099 said:
Hi man, I am wondering can I have the download address about that magisk canary build? I've been bootlooping just like you before.
Click to expand...
Click to collapse
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk
Marcolo88 said:
Hi, the canary build is in the same place of the "normal" build in the official git page.
This is the direct link of the APK:
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
The main page is this: https://github.com/topjohnwu/Magisk
Click to expand...
Click to collapse
It worked on my Xiaomi 11T(not pro version) with a magisk-canary-patch, now the bootloop has been gone and really appreciated for your kindness help.
Hi, I've unlocked the bootloader on my new Xiaomi Redmi Note 10 Pro because I like to have apps like adaway and macrodroid which need root access. I've rooted previous phones before but I'm far from an export on it. It's been a while since I have a new phone and had to figure it all out again. Anyway, I've messed up and I hope someone can help me out. I'll try to explain every step I did to make it easier to troubleshoot.
After unlocking, I installed Magisk Manager (the apk file) and got boot.img from a Miui zip. I did not realize I needed to use the EU version of Miui nor did I see that I have "sweet" instead of "mojito" so I got the latest mojito Global rom from here, thinking that would be fine. I let Magisk modify the boot.img and rebooted into fastboot. I flashed the modified boot.img and I also flashed OrangeFox as a recovery. After a reboot the phone got stuck on a fastboot loop so I figured I did something wrong.
After quite some research I came to the conclusion I used the wrong rom (global instead of EEA). So I found the EEA Miui rom and flashed that boot.img using fastboot. I was able to get back into the system. I let Magisk modify the new boot.img and flashed that again with fastboot. This ended up in a fastboot loop again so I flashed the previous boot.img again. At this point I came to the conclusion there was a "mojito" and a "sweet" version and I was trying to flash "mojito" rom on a "sweet" phone. Anyhow I found the "sweet" EEA rom and redid the previous steps. The phone does boot into system now, but wifi isn't working anymore. When I try to toggle it on, it just says "turning on" but it never switches on. I think I messed up some modem driver by flashing the other roms but I can't seem to fix it.
I saw somewhere that I could try to use flash_all.bat which is located in the fastboot roms, but this only gave errors talking about current antirollback version being higher than the package. It didn't matter which version of the package I used, so I gave up on this route quite quickly.
I assumed there was still something wrong with the rom so I went into OrangeFox and wiped everything. If I try to use OrangeFox to install any Miui zip, it fails without any useful message. The only zip I was able to install was OrangeFox itself which I only tried because I was thinking it might was OrangeFox that was f'ed up. I've added a pic of the error. This was with EU firmware from here which I found through the Pixel OS thread.
{
"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"
}
Anyhow, I was hoping flashing a different rom like PixelOS might fix the problem but OrangeFox refused to install any zip apart from it's own.
I hope someone can point me in the right direction because I'm starting to see less and less possible solutions. It's a brand new phone so there is no data on it that I need to save. Also, I was not able to find that V12.5.8.0.RKFEUXM version anywhere. It's either v13 something of V12.5.7.something.
In desperation I decided to download about 10 different versions and try them one by one in OFox. Ranging van V12.5.3.0.RKFEUXM up to the latest and to my surprise, the zip voor V12.5.7.0 actually worked and installed. The phone kept coming back to OFox though, so I wiped everything, did another format, went into fastboot and flashed the boot.img from that zip, did another format and behold, I got into system again and wifi was actually working again!
Anyhow from that point forward I simply installed Magisk again, let it modify the boot.img, flashed the modified boot.img, wiped and formatted in OFox and rebooted. Now I'm finally able to start configuring the phone as I wanted to do hours ago.. Although... I might retry flashing a later version again just to test since I'm not actively using the phone yet.
DeMetaal said:
In desperation I decided to download about 10 different versions and try them one by one in OFox. Ranging van V12.5.3.0.RKFEUXM up to the latest and to my surprise, the zip voor V12.5.7.0 actually worked and installed. The phone kept coming back to OFox though, so I wiped everything, did another format, went into fastboot and flashed the boot.img from that zip, did another format and behold, I got into system again and wifi was actually working again!
Anyhow from that point forward I simply installed Magisk again, let it modify the boot.img, flashed the modified boot.img, wiped and formatted in OFox and rebooted. Now I'm finally able to start configuring the phone as I wanted to do hours ago.. Although... I might retry flashing a later version again just to test since I'm not actively using the phone yet.
Click to expand...
Click to collapse
Use MiFlashTool.
Ok from what I understand is that OP tried to use the boot img from "mojito" on "sweet" and messed up the wifi modem in the process. Some things that I'd like to point out that might've caused the errors are:
1. Using the patched boot.img method to install magisk - normally, and actually stated in magisk installation, this method is only used for devices with no active custom recovery. Since sweet has it's own custom recoveries, simply flashing magisk.apk (renaming it to magisk.zip) in the recovery is enough to install magisk, no need the hassle of downloading, extracting, patching, and flashing a boot.img.
2. The recovery in the screenshot is the old Orange Fox r11.1 which, according to the ss at least and assuming the device isn't using fingerprint spoofing, supports only Android 11 decryption and roms. Also, r11.1 ofox is simply outdated and new ones (Unofficial Ofox 12.1_3 and TWRP 3.7.0_12) are the recommended recoveries to use for flashing A12/A13 roms as it supports decryption for said version of Android.
3. PixelOS requires its own recovery (or the mentioned Unofficial Ofox) because it has signature verification and requires EROFS and F2FS compression supported recoveries hence the reason why it probably failed to be flashed.
4. The anti-rollback error in MiFlash is only for checks and can be simply removed by editing the .bat files referencing the ARB check (check some tutorials is YT for this). ARB is not activated in the device yet therefore going back versions is ok and will not result in bricking. It's just a confusion and possibly Xiaomi is limiting users to downgrade to old versions with possible exploit so maybe that's the reason for the ARB check.
BigChungus321 said:
Ok from what I understand is that OP tried to use the boot img from "mojito" on "sweet" and messed up the wifi modem in the process. Some things that I'd like to point out that might've caused the errors are:
1. Using the patched boot.img method to install magisk - normally, and actually stated in magisk installation, this method is only used for devices with no active custom recovery. Since sweet has it's own custom recoveries, simply flashing magisk.apk (renaming it to magisk.zip) in the recovery is enough to install magisk, no need the hassle of downloading, extracting, patching, and flashing a boot.img.
2. The recovery in the screenshot is the old Orange Fox r11.1 which, according to the ss at least and assuming the device isn't using fingerprint spoofing, supports only Android 11 decryption and roms. Also, r11.1 ofox is simply outdated and new ones (Unofficial Ofox 12.1_3 and TWRP 3.7.0_12) are the recommended recoveries to use for flashing A12/A13 roms as it supports decryption for said version of Android.
3. PixelOS requires its own recovery (or the mentioned Unofficial Ofox) because it has signature verification and requires EROFS and F2FS compression supported recoveries hence the reason why it probably failed to be flashed.
4. The anti-rollback error in MiFlash is only for checks and can be simply removed by editing the .bat files referencing the ARB check (check some tutorials is YT for this). ARB is not activated in the device yet therefore going back versions is ok and will not result in bricking. It's just a confusion and possibly Xiaomi is limiting users to downgrade to old versions with possible exploit so maybe that's the reason for the ARB check.
Click to expand...
Click to collapse
Thanks a lot for this info! I did not know most of what you said so this helps a bunch.
So could me using this older OFox be the reason why I can't update to Miui 13? Because I now have a working Miui 12.5.7 on the phone and it says theres an update for Miui 13 but once thats downloaded and the phone reboots, it boots into OFox but doesn't actually install anything. Also I cant install the downloaded Miui13 zip which is, as far as I can tell, the same as the one the phone tries to download when pressing the update button.
I'll go look into this newer OFox or perhaps TWRP to see if that changes things. I've used TWRP before but switched at some point. I can't remember why.
BigChungus321 said:
Ok from what I understand is that OP tried to use the boot img from "mojito" on "sweet" and messed up the wifi modem in the process. Some things that I'd like to point out that might've caused the errors are:
1. Using the patched boot.img method to install magisk - normally, and actually stated in magisk installation, this method is only used for devices with no active custom recovery. Since sweet has it's own custom recoveries, simply flashing magisk.apk (renaming it to magisk.zip) in the recovery is enough to install magisk, no need the hassle of downloading, extracting, patching, and flashing a boot.img.
2. The recovery in the screenshot is the old Orange Fox r11.1 which, according to the ss at least and assuming the device isn't using fingerprint spoofing, supports only Android 11 decryption and roms. Also, r11.1 ofox is simply outdated and new ones (Unofficial Ofox 12.1_3 and TWRP 3.7.0_12) are the recommended recoveries to use for flashing A12/A13 roms as it supports decryption for said version of Android.
3. PixelOS requires its own recovery (or the mentioned Unofficial Ofox) because it has signature verification and requires EROFS and F2FS compression supported recoveries hence the reason why it probably failed to be flashed.
4. The anti-rollback error in MiFlash is only for checks and can be simply removed by editing the .bat files referencing the ARB check (check some tutorials is YT for this). ARB is not activated in the device yet therefore going back versions is ok and will not result in bricking. It's just a confusion and possibly Xiaomi is limiting users to downgrade to old versions with possible exploit so maybe that's the reason for the ARB check.
Click to expand...
Click to collapse
Thanks mate! Your words might not mean much to you but you helped me out big time!
I installed the latest TWRP because I couldn't find OFox12 for this specific phone. So I used TWRP to install the Miui 13 zip I had previously downloaded and it worked flawlessly. Now I can finally start configuring the phone and start using it. Your message is much appreciated!
https://deac-fra.dl.sourceforge.net/project/orangefox-releases/sweet/OrangeFox-R12.1_3-Unofficial-sweet.zip
Just in case for next time u might wanna brick ur phone.
aLcaTr4z said:
https://deac-fra.dl.sourceforge.net/project/orangefox-releases/sweet/OrangeFox-R12.1_3-Unofficial-sweet.zip
Just in case for next time u might wanna brick ur phone.
Click to expand...
Click to collapse
Haha thanks. TWRP did the job though so I'll probably stick with that for now.