Question Bootlooping after flashing an old boot.img - Redmi Note 9T

Hello,
About a week ago I updated to MIUI 13 (13.0.2.0.SJEMIXM). My phone (Redmi Note 9T) was rooted and I had a custom recovery (Orange Fox) installed. I flashed the stock recovery and was then able to update. I left the stock recovery on the phone to make it easier to update down the line but did root my phone again.
This morning I was informed that there is a new update (13.0.3.0.SJEMIXM) so I download and installed it. All went well and the phone booted successfully.
I then wanted to have my phone rooted again (magisk) so I just took the boot.img from the previous version (13.0.2.0.SJEMIXM) to be patched since I did not have the factory Rom for the new version (13.0.3.0.SJEMIXM) to retrieve the boot.img file.
I then flashed the patched boot.img via fastboot (fastboot flash boot magisk_pached.img) and my phone started to bootloop.
I also tried flashing the unpatched boot.img but it is still the old one.
I don't know if I did something wrong or if it is just the old boot.img that I need to replace, pls help.
Ps: I have downloaded the OTA update (13.0.3.0.SJEMIXM) but it only contains a boot.img.p file.

Rubz_Mod said:
Hello,
About a week ago I updated to MIUI 13 (13.0.2.0.SJEMIXM). My phone (Redmi Note 9T) was rooted and I had a custom recovery (Orange Fox) installed. I flashed the stock recovery and was then able to update. I left the stock recovery on the phone to make it easier to update down the line but did root my phone again.
This morning I was informed that there is a new update (13.0.3.0.SJEMIXM) so I download and installed it. All went well and the phone booted successfully.
I then wanted to have my phone rooted again (magisk) so I just took the boot.img from the previous version (13.0.2.0.SJEMIXM) to be patched since I did not have the factory Rom for the new version (13.0.3.0.SJEMIXM) to retrieve the boot.img file.
I then flashed the patched boot.img via fastboot (fastboot flash boot magisk_pached.img) and my phone started to bootloop.
I also tried flashing the unpatched boot.img but it is still the old one.
I don't know if I did something wrong or if it is just the old boot.img that I need to replace, pls help.
Ps: I have downloaded the OTA update (13.0.3.0.SJEMIXM) but it only contains a boot.img.p file.
Click to expand...
Click to collapse
Flash the (13.0.3.0.SJEMIXM)boot.img with O.F .
Use Magisk app for rooting the phone.

I fixed the problem.
All I had to do was find new the boot.img and flash it via fastboot.
I then patched the new boot.img file and then I flashed the patched.img via fastboot.
Thanks for your help

Related

Global OTA 9.5.4.0 + TWRP = fail

My phone has unlocked bootloader, TWRP, and is rooted with magisk. Got the OTA for (global) 9.5.4.0 last night - it downloads/de-crypts ok, reboots into TWRP, and then fails to flash. I also tried to flash manually via TWRP by locating the downloaded file, still fails. During the night, it rebooted itself (to try again I suppose), and my alarm didn't go off.
So here I am, late in work, wasting more "work time" to ask you for a possible solution :angel:
Go back to original miui recovery then you can update your miui successfully. After update,reflash twrp and magisk.
jimandy60 said:
Go back to original miui recovery then you can update your miui successfully. After update,reflash twrp and magisk.
Click to expand...
Click to collapse
Sounds easy, but I don't know how to do that. Could you point me in the right direction?
you can't flash an OTA with TWRP
Flash recovery img with fastboot
Code:
fastboot flash recovery recovery.img
then boot your phone
settings->about phone->system update->update
it will get in origin miui recovery and update system automatically
after update finished,reflash twrp and magisk
Thank you very much @jimandy60
With all the respect though, I would prefer downloading the file from a popular location. Is there any way to find this hosted somewhere else, maybe by Xiaomi?
ang3l said:
Thank you very much @jimandy60
With all the respect though, I would prefer downloading the file from a popular location. Is there any way to find this hosted somewhere else, maybe by Xiaomi?
Click to expand...
Click to collapse
maybe try this site?
en.miui.com
Hello!
I got the same problem but instead to come here and ask for help I tried to solve myself. I downloaded the lastest TWRP version and the device was not going into recovering mode. Then I installed again the previous one without results. I downloaded the TWRP app from Play Store and trying to solve I made wipe data, cache and I am not sure but I think also choose wipe system. Now my phone is stuck on the fastboot screen. Does not start. Using ADB I installed back the stck recovery but the problem remains. Somebody can help me please?
reflash the full rom?
download&unzip full rom package,get in fastboot mode and run flash_all.bat
Check out my guide here:
https://forum.xda-developers.com/mi-mix-2/how-to/guide-mi-mix-2-unroot-restore-recovery-t3770690
It has all the steps and files you will need to go from rooted stock MIUI Nougat to rooted stock MIUI Oreo applying the OTA update
colorado_al said:
Check out my guide here:
https://forum.xda-developers.com/mi-mix-2/how-to/guide-mi-mix-2-unroot-restore-recovery-t3770690
It has all the steps and files you will need to go from rooted stock MIUI Nougat to rooted stock MIUI Oreo applying the OTA update
Click to expand...
Click to collapse
Thanks, I'll take a look.

10.0.5 boot.img?

Hey all! I'm trying to root my OnePlus 7t but I'm on 10.0.5 stock and I can't find a patched boot.img, or even a stock one to patch in Magisk. I'm on the global variant. If someone could point me in the right direction, that would be grand. I have already read mostly all the posts...
I have the US version which I think is also the global version. Here's my patched boot.img for 10.0.5
https://drive.google.com/file/d/12tZN5D7dmovIeqsx8sTF-B0z2gxA6LG8/view?usp=sharing
Here's the stock boot for 10.0.5 as well if you screw something up.
https://drive.google.com/file/d/1nS0hqVCyntXHjbTzOH7H8-b29-IlAOIt/view?usp=sharing
Don't ask why the file sizes are so different. It just gets smaller for some reason after patching it in magisk.
I just booted with an older one and flashed the latest magisk
Need 10.0.5 boot.img stock & magisk patched for indian varient
Hey .... Can you help me with the 10.0.5 boot.img , stock & magisk patched for indian varient HD1901 of 7t
ChongoDroid said:
I just booted with an older one and flashed the latest magisk
Click to expand...
Click to collapse
I had tried booting with 10.0.3 while on 10.0.5 , Did not turn out well .
Has anyone on 10.0.5 tried booting w/ the above 10.0.5 patched img ?
Stock and Magisk patched boot.img files for HD1905 7T update version 10.0.5:
dropbox.com/s/887ibs0yorxgs2v/boot.img?dl=0
dropbox.com/s/sxrayyjn562susu/magisk_patched.img?dl=0
SkippRunning said:
Stock and Magisk patched boot.img files for HD1905 7T update version 10.0.5:
dropbox.com/s/887ibs0yorxgs2v/boot.img?dl=0
dropbox.com/s/sxrayyjn562susu/magisk_patched.img?dl=0
Click to expand...
Click to collapse
Do I only need to flash the patched img or both ?
And do they need to be flashed to both A and B slots ?
Thanks for sharing
hightech316 said:
Do I only need to flash the patched img or both ?
And do they need to be flashed to both A and B slots ?
Thanks for sharing
Click to expand...
Click to collapse
I would try fastboot boot before you use fastboot flash just to make sure that the device will boot successfully with the images. You should only need to fastboot boot magisk_patched.img, then open Magisk Manager and install Magisk by choosing the direct install option in the list. You only need the steps I mentioned to have root, and if you flash it to A and B at once you can get stuck in a bootloop. I had that happen at one point from flashing both partitions, and I dont recommend trying it.
SkippRunning said:
I would try fastboot boot before you use fastboot flash just to make sure that the device will boot successfully with the images.
Click to expand...
Click to collapse
Thanks , this can save a headache !
hightech316 said:
Thanks , this can save a headache !
Click to expand...
Click to collapse
Ya, I tried every relevant boot image I could find in the forums, and the device didnt work properly with any of them. The only one that allowed the device to boot successfully caused the wifi and sounds to not work. So I downloaded the full update from OnePlus and extracted it to a folder, then used payload dumper to extract all of the individual images out of the payload.bin file from OnePlus. I copied the boot.img into the phone storage and installed Magisk Manager, then patched the stock boot.img and copied it from the phone to my pc. Then I used fastboot boot magisk_patched.img to make sure the image I made would work. I booted the device and inside Magisk Manager I chose direct install in the list of options and everything went smoothly, and I didnt need to rely on finding images online that would hopefully work.
smokeythebear3 said:
I have the US version which I think is also the global version. Here's my patched boot.img for 10.0.5
https://drive.google.com/file/d/12tZN5D7dmovIeqsx8sTF-B0z2gxA6LG8/view?usp=sharing
Here's the stock boot for 10.0.5 as well if you screw something up.
https://drive.google.com/file/d/1nS0hqVCyntXHjbTzOH7H8-b29-IlAOIt/view?usp=sharing
Don't ask why the file sizes are so different. It just gets smaller for some reason after patching it in magisk.
Click to expand...
Click to collapse
Thanks a bunch for the share. That was the missing piece that I've been looking for. I have the HD1905 variant and I just used Magisk to patch the stock file you provided. After testing, I'm finally rooted. Thanks again.

Magisk boot.img Rog Phone II update WW-17.0240.2007.27 Android 10

Hello,
Boot.img for Rog Phone II patched with Magisk 7.5.1:
update WW-17.0240.2007.27
Patched
Stock boot.img
update WW-17.0230.2004.60
Patched
Stock boot.img
update WW-17.0210.2001.60.
Patched Mirror 1
Patched Mirror 2
Stock boot.img
If you need other version boot.img patched with Magisk just comment or msg me.
Very very thanks
I need it
thank you!
Stuck on bootloop while updating to Android 10
How did you update your phone while keeping magisk? I tried updating via OTA, did not restart and then flashed Magisk 7.5.3 on inactive slot and then rebooted my phone. Now it is stuck on bootloop.
Even the TWRP is gone but the stock recovery shows that the update is installed.
Do you know any way as to how I can fix this?
I have unlocked bootloader so im not using OTA, just downloading updates from Asus site, after update and phone restart you lose magisk, you have to install magisk manager APK, then via fast_boot install patched boot.img.
That's why i uploaded patched boot.img for 17...., u always have to repeat it after updating.
Right now just flash stock ROM
Ushrael said:
I have unlocked bootloader so im not using OTA, just downloading updates from Asus site, after update and phone restart you lose magisk, you have to install magisk manager APK, then via fast_boot install patched boot.img.
That's why i uploaded patched boot.img for 17...., u always have to repeat it after updating.
Right now just flash stock ROM
Click to expand...
Click to collapse
I also have rooted my device. I downloaded the update zip, kept it on internal storage. rebooted my device and when the update notification showed i updated and did not reboot.
Then i went to magisk and installed the magisk to inactive slot and then went onto reboot my device but now i am stuck on a bootloop.
Today only i updated to A10. Can some tell me how to root and install magisk? I will really appreciate your support.
Spawn_Ishan said:
did not reboot.
Click to expand...
Click to collapse
IDK why did u done it, but maybe installing stock boot.img will help u, install stock same as your rom version.
husen4u said:
Today only i updated to A10. Can some tell me how to root and install magisk? I will really appreciate your support.
Click to expand...
Click to collapse
I can't post links, but just type in google Rog phone 2 magisk, even on XDA u have some instructions, just take my patched boot.img if u have version WW-17.0210.2001.60 instead
Ushrael said:
IDK why did u done it, but maybe installing stock boot.img will help u, install stock same as your rom version.
I can't post links, but just type in google Rog phone 2 magisk, even on XDA u have some instructions, just take my patched boot.img if u have version WW-17.0210.2001.60 instead
Click to expand...
Click to collapse
Installing the stock boot image helped me boot my device, but installing magisk causes a bootloop everytime and even if i try to flash twrp, the phone boots only into twrp and not the system.
Also tried using your patched boot image and tried patching a boot image myself from the magisk manager app but still causes bootloop.
---------- Post added at 10:34 PM ---------- Previous post was at 10:13 PM ----------
Ushrael said:
Hello,
If some1 need boot.img for Rog Phone II update WW-17.0210.2001.60.
Patched with Magisk 7.5.1:
Mirror 1
Mirror 2
Stock boot.img
If you need other version boot.img patched with Magisk just comment or msg me.
Click to expand...
Click to collapse
Can i have a boot.img flashed from magisk manager 7.5.3?
Click to expand...
Click to collapse
where did u found 7.5.3? newest is 7.5.1
Do u have WW or CN ROM
Ushrael said:
where did u found 7.5.3? newest is 7.5.1
Do u have WW or CN ROM
Click to expand...
Click to collapse
I have 7.5.1, i confused the manager version.
I have WW Rom.
Stock image booting works just fine, i can even boot twrp but when i flash magisk the system goes in a bootloop.
Spawn_Ishan said:
I have 7.5.1, i confused the manager version.
I have WW Rom.
Stock image booting works just fine, i can even boot twrp but when i flash magisk the system goes in a bootloop.
Click to expand...
Click to collapse
If u are using TWRP just download magisk 20.3.zip file and flash it with twrp. Don't use patched boot.img.
Ushrael said:
If u are using TWRP just download magisk 20.3.zip file and flash it with twrp. Don't use patched boot.img.
Click to expand...
Click to collapse
Tried that first but it causes bootloop, thats when i resorted to patched boot. Dont know why but flashing magsik anyhow causes a bootloop.
Was able to install magisk after i reset my phone.
can i use your bootstock for relock my android 10? is it possible flash by minimal adb and fastboot?
Fresh boot.img for version WW-17.0230.2004.60
I followed this guide: https://forum.xda-developers.com/ro...-check-change-fingerprint-cn-to-t4002279/amp/
And then i did the update to WW-17.0230.2004.60 and lost root.
How I can root again?
Thank you for share!
Spawn_Ishan said:
Installing the stock boot image helped me boot my device, but installing magisk causes a bootloop everytime and even if i try to flash twrp, the phone boots only into twrp and not the system.
Also tried using your patched boot image and tried patching a boot image myself from the magisk manager app but still causes bootloop.
---------- Post added at 10:34 PM ---------- Previous post was at 10:13 PM ----------
Click to expand...
Click to collapse
did you ever find a solution? I want to update from Android 9 but don't want to end up in your situation.
boot.img for update WW-17.0240.2007.27
Thank you ?????
hi friends, can you tell me please, i have WW installed with twrp, what steps have to do if i want update from another zip update? to avoid problems with encryption for example, or problems with boot img because i have root with magisk, thank you

Tried to root

Model BE2013
Build 10.5.2.BE83BA
Tried unsuccessfully to root numerous time, getting stuck on Fastboot Mode.
Then having to restore with MSMdownloadtool.
I have unsuccessfully tried using python to extract the boot.img, so I used the OTA boot.img.
Isn't the OTA boot.img the same as the python extracted version?
Is it easier for me to update to the latest OS 11 then root?
Thanks in advance
ipandroid said:
Model BE2013
Build 10.5.2.BE83BA
Tried unsuccessfully to root numerous time, getting stuck on Fastboot Mode.
Then having to restore with MSMdownloadtool.
I have unsuccessfully tried using python to extract the boot.img, so I used the OTA boot.img.
Isn't the OTA boot.img the same as the python extracted version?
Is it easier for me to update to the latest OS 11 then root?
Thanks in advance
Click to expand...
Click to collapse
Get the OTA download from oneplus website, put the zip on your phones root (Outside the downloads folder) upgrade your phone to OxygenOS 11.0.3 and then extract the boot.img from the OTA and patch it with magisk, rename the newly patched magisk boot img to "boot.img" and flash boot with it.
Worked for me.
Edit: Your phone is most likely on OxygenOS 11.0.2 thus making the 11.0.3 boot.img incompatible.

OOS11.0.3.1 boot.img

hi,
I wanted to patch the boot.img with magisk and downloaded the latest firmware from oneplus. Not reading carefully, the most recent update available for regular download was 11.0.0.2.HD65AA, the phone was on 11.0.3.1GM57BA already though. After flashing the wrong version of boot.img it does not boot well, WiFi doesn't work and boot is slow.
Does anybody have either the stock or a patched boot.img for 11.0.3.1GM57BA for me that I can flash?
best regards
RockNLol
*edit: I was able to download the latest OTA-Update via the app "Oxygen Updater".

Categories

Resources