Database Develop

bootloop after update

pls help me
https://forum.xda-developers.com/on...ndroid-8-0-t3728119/post75045144#post75045144
i did everything like write!!
first, updated twrp, than nandroid backup, than i wiped dalvik&cache and than install new ota and magisk, than again wiped and reboot.
now my phone stuck about 20 minute on the red logo with the 2 white circle
what should i do?

maor23 said:
than install new ota and magisk
Click to expand...
Click to collapse
Which OTA, was it the incremental update (<1 GB) or the full zip (>1GB)?
Which version Magisk? 14.6 link the post you linked?
Always post as much specific detail as possible (version numbers, file names, etc.) when asking for help. Otherwise, you waste everyone's time as we have to ask for information you should have provided, in the first place.

redpoint73 said:
Which OTA, was it the incremental update (<1 GB) or the full zip (>1GB)?
Which version Magisk? 14.6 link the post you linked?
Always post as much specific detail as possible (version numbers, file names, etc.) when asking for help. Otherwise, you waste everyone's time as we have to ask for information you should have provided, in the first place.
Click to expand...
Click to collapse
sorry, i was nervous.
i was dm problem so i solved it by help of this post
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
but for your question, i was full zip, and 15.2 zip magisk that was in post

maor23 said:
sorry, i was nervous.
i was dm problem so i solved it by help of this post
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
but for your question, i was full zip, and 15.2 zip magisk that was in post
Click to expand...
Click to collapse
Did you swipe to allow system modification in TWRP? if not, installing the update ahd Magisk should not have tripped dm-verity (prevented the phone from booting to OS).

redpoint73 said:
Did you swipe to allow system modification in TWRP? if not, installing the update ahd Magisk should not have tripped dm-verity (prevented the phone from booting to OS).
Click to expand...
Click to collapse
Flashing Magisk 15.1 will trip dm-verity. 15.2 however is ok.
Sent from my OnePlus3T using XDA Labs

redpoint73 said:
Did you swipe to allow system modification in TWRP? if not, installing the update ahd Magisk should not have tripped dm-verity (prevented the phone from booting to OS).
Click to expand...
Click to collapse
no i didnt, after i install the magisk zip i did cache wipe and than reboot, and the phone stuck on the red logo with 2 white circles about 20 minutes, and than DM

Relock bootloader (with magisk) on the Oneplus 5?

Hello everyone, I've tried to search on the web about this issue since the OTA for Android O is finally out for the Oneplus 5 and couldn't get a satisfying solution. I rooted my OP5 a while ago with Magisk and now that this update is out and tried to install it, It just wouldn´t let me, searching I found that my locked swich to relock the bootloader was because I had to enable it on Magisk, so I opened magisk and couldn´t find that option, and now that I searched on how to enable the "Lock bootloader option" in the Magisk app and found nothing, I'm just out of ideas, so guys, could you help a (noob) brother out with this?
Ps.: If you could attach some screenshots about where to click or what to do, I'll apreciate it a lot (yeah, I'm that stupid when I freak out and don't find how to undo mi mess)

No... Do not lock your bootloader! Since you've been modifying your device that would potentially brick it.
What you're probably looking for is to restore your boot image. That's what Magisk modifies and is the reason why a normal OTA doesn't work. If you have TWRP installed, that would also be an issue.
The easiest way for you to update would be to download the full OTA zip, flash that in TWRP directly followed by the Magisk zip. That way you'll be nice and updated and still rooted.

Didgeridoohan said:
No... Do not lock your bootloader! Since you've been modifying your device that would potentially brick it.
What you're probably looking for is to restore your boot image. That's what Magisk modifies and is the reason why a normal OTA doesn't work. If you have TWRP installed, that would also be an issue.
The easiest way for you to update would be to download the update, flash that in TWRP directly followed by the Magisk zip. That way you'll be nice and updated and still rooted.
Click to expand...
Click to collapse
Allright! I've downloaded the zip with the update, now: do I have to get the latest magisk zip, flash the update and then immediately flash the newest magisk zip?

Fosko Stock said:
Allright! I've downloaded the zip with the update, now: do I have to get the latest magisk zip, flash the update and then immediately flash the newest magisk zip?
Click to expand...
Click to collapse
Yes.

Latest rooted boot image (9.5.11)

Here you can find latest boot image for OnePlus7 Pro rooted with Magisk.
ROM:
OnePlus7ProOxygen_21.E.13_OTA_013_all_1907050211_b8852b6
https://1drv.ms/u/s!AvJju0GuwXqysxoo9LNYN3wla8KX

Why do need the boot.img for root ?
I never used it for root my device.

khalisz said:
Why do need the boot.img for root ?
I never used it for root my device.
Click to expand...
Click to collapse
How old is the last phone you had?

Since Jul 9, 2019.

Cozzeck said:
How old is the last phone you had?
Click to expand...
Click to collapse
Since Jul 9, 2019.

As of OOS 9.5.10 you can boot twrp by fastboot, then sideload twrp into both slots and finally flash magisk which patches the boot.img itself. Thus no need for patched boot.img anymore.

Does this work for the global version??

Patched boot.img is a silly way of rooting... If someone uses the wrong boot.img for their version it will fail to boot. Plus, booting TWRP and flashing the magisk zip is faster and more reliable

alexander1297 said:
Does this work for the global version??
Click to expand...
Click to collapse
The only difference between the global and the EU versions are supposed to be the LTE bands.

lichtblitz said:
As of OOS 9.5.10 you can boot twrp by fastboot, then sideload twrp into both slots and finally flash magisk which patches the boot.img itself. Thus no need for patched boot.img anymore.
Click to expand...
Click to collapse
Sorry for asking but I wanna root mine as soon as it comes. So if you install TWRP and flash with magisk the OTAs won't be broken?

Kengat said:
Sorry for asking but I wanna root mine as soon as it comes. So if you install TWRP and flash with magisk the OTAs won't be broken?
Click to expand...
Click to collapse
I get still offered OTAs by the system. However I prefer to use Oxygen Updater app from Play Store to download it and flash directly in TWRP.

lichtblitz said:
I get still offered OTAs by the system. However I prefer to use Oxygen Updater app from Play Store to download it and flash directly in TWRP.
Click to expand...
Click to collapse
Oh cool. So like "dirty flashing". Will magisk also get killed in the proccess? I'm not sure how A/B partitions work. Do you just install magisk from twrp or do you have to somehow install it on both partitions?

GM all
I seem to have lost my root after I did the update for 9.5.11 this morning
Here is what I did
I did as stated
Download update, Install, DO NOT REBOOT
Went to Magisk, unistalled all modules, then did OTA Install
Rebooted
Went to Magisk installed TWRP, but my phone froze at that point and the screen turned all white and just sat there
So I clicked on the power button and rebooted
Got back into my phone and checked to see if I was still rooted via root checker app and now it says I AM NOT ROOTED
What can I do to fix this I can launch Magisk, but now it says its is not installed on the screen, so I click install, download the ZIP option
It says Select Method, Download ZIP ONLY which I did or Select and Patch a File which I am not sure what file I need to use?
How can I get my root back on the phones
I am on NOW on 9.5.11 GM 1917
Thanks all
Thanks all

dallasnights said:
GM all
I seem to have lost my root after I did the update for 9.5.11 this morning
Here is what I did
I did as stated
Download update, Install, DO NOT REBOOT
Went to Magisk, unistalled all modules, then did OTA Install
Rebooted
Went to Magisk installed TWRP, but my phone froze at that point and the screen turned all white and just sat there
So I clicked on the power button and rebooted
Got back into my phone and checked to see if I was still rooted via root checker app and now it says I AM NOT ROOTED
What can I do to fix this I can launch Magisk, but now it says its is not installed on the screen, so I click install, download the ZIP option
It says Select Method, Download ZIP ONLY which I did or Select and Patch a File which I am not sure what file I need to use?
How can I get my root back on the phones
I am on NOW on 9.5.11 GM 1917
Thanks all
Thanks all
Click to expand...
Click to collapse
Follow the steps on TWRP and rooting on my guide. Look in the Guides & Discussion section of XDA

Flashing this on International breaks the WiFi. Does anyone have the international version?

Hideaki02 said:
Flashing this on International breaks the WiFi. Does anyone have the international version?
Click to expand...
Click to collapse
just flash boot twrp and flash magisk there..

Arden144 said:
Patched boot.img is a silly way of rooting... If someone uses the wrong boot.img for their version it will fail to boot. Plus, booting TWRP and flashing the magisk zip is faster and more reliable
Click to expand...
Click to collapse
If you don't need TWRP, first booting it and flashing the zip takes way longer than "fastboot flash boot boot.img".

Made an OB1 Magisk Patched boot.img

7ProAndroid11MagiskBootImg - Google Drive
drive.google.com
Feel free to download it. All I did was extract the boot.img from the payload.bin, copy the boot.img to an extra phone, patched it with magisk, then uploaded it.
Don't install TWRP yet. The people who are infinitely smarter than I am will make a TWRP that will work for OB1, and that's way above my pay grade. I hope this helps someone.
[Tutorial] How to flash a new boot.img via Fastboot
Hey Guys, since I heard many questions lately concerning flashing a boot.img onto the One S I decided to give you a small tutorial! (which should also work on any other device with bootloadermode) If you have fastboot already installed on your...
forum.xda-developers.com
Here's how to use it.

getting 'unable to parse kernel log' error

peachypickle said:
getting 'unable to parse kernel log' error
Click to expand...
Click to collapse
it worked fine for me.

How install oxygen os open beta 1 android 11 with keep rooted? Any video tutorial?

it's not too bad...
Install the OTA
Go to magisk manager and pick install.
pick install to inactive slot (after OTA)
make sure you don't have any modules enabled that may be incompatible.
reboot
when the 11 TWRP drops, you can install it as a magisk module to gain custom recovery back

Just download magisk 21.4 zip and boot into twrp and flash it. No problems. Way easier. Here is the zip.

spheady said:
Just download magisk 21.4 zip and boot into twrp and flash it. No problems. Way easier. Here is the zip.
Click to expand...
Click to collapse
WOW YOU ARE SMART! Good looking out! This IS way easier. Thank you so much for the heads up!
wait, actually, do some research before you post. there's currently not a functioning TWRP for Android 11 and if you install the update, your TWRP will flash and freeze.

aNGERY said:
WOW YOU ARE SMART! Good looking out! This IS way easier. Thank you so much for the heads up!
wait, actually, do some research before you post. there's currently not a functioning TWRP for Android 11 and if you install the update, your TWRP will flash and freeze.
Click to expand...
Click to collapse
Okay I see. So I have TWRP LOL. I KNOW WHY to.
I have orangfox dual boot .zip from here. Also used TWRP to install the beta 1 on my phone which I run two OSs 96gb each and a extra 32 gb partition for genal stuff. So I flashed from Oxy 10.3.7 in TWRP, beta 1 it's. Than before booting I flashed Orangefox-dualboot-v11-7.zip. Wich installs TWRP and root automatically to both OSs. I recommend to TWRP 1st from 10 and after flashing the ota. Flash a TWRP zip file. Here's a boot.img from mine on the beta side. Be carefull it could have twrp preinstalled in it. I'm new lol but isn't twrp in the boot.img now a days. This one has it if it is. My boot.img it's also got magisk 21.4. totally blew by not having to worries about this thread. One other thing though. It's for a dual boot setup and encryption is off.

spheady said:
Okay I see. So I have TWRP LOL. I KNOW WHY to.
I have orangfox dual boot .zip from here. Also used TWRP to install the beta 1 on my phone which I run two OSs 96gb each and a extra 32 gb partition for genal stuff. So I flashed from Oxy 10.3.7 in TWRP, beta 1 it's. Than before booting I flashed Orangefox-dualboot-v11-7.zip. Wich installs TWRP and root automatically to both OSs. I recommend to TWRP 1st from 10 and after flashing the ota. Flash a TWRP zip file. Here's a boot.img from mine on the beta side. Be carefull it could have twrp preinstalled in it. I'm new lol but isn't twrp in the boot.img now a days. This one has it if it is. My boot.img it's also got magisk 21.4. totally blew by not having to worries about this thread. One other thing though. It's for a dual boot setup and encryption is off.
Click to expand...
Click to collapse
So your saying orangefox recovery will work on OOS open beta 1 even if we don't dual boot?

LokifiedMee said:
So your saying orangefox recovery will work on OOS open beta 1 even if we don't dual boot?
Click to expand...
Click to collapse
Yeah man. Sorry took a minute two get back to you. Flash b1, than OJfox dual twrp.zip do not choose to root it. Boot it up once reboot to twrp and flash 21.4 magisk. Have fun

Crazyinsanejames said:
Yeah man. Sorry took a minute two get back to you. Flash b1, than OJfox dual twrp.zip do not choose to root it. Boot it up once reboot to twrp and flash 21.4 magisk. Have fun
Click to expand...
Click to collapse
Ohh couldn't find Orangefox dual boot's post today so here is the twrp file. It's not really worked on right now and has option to flash magisk on R11 Pass but the copy of magisk is no good on the R11 OS but has magisk. 20.4 option for a Q10 is, when it IDs it. You'll see. The script options. PS orangfox dual booting with three different drives rocks. Also it has a app manager and a magisk mange GUI. Almost forgot beta 10 version 17-19 will not successful y flash this twrp. But any other copy for the phone on xda or OnePlus.com work fine. It's a encryption variety problem. If your password becomes corrupt (only on OS can have password type security on a dual boot setup... I got away with using the same password on both OSs for a minute though. ) in the root partition thiers a directory called Ffiles, with .zip you can flash while TWRped to fix a few things like that. Other than that let me know. Lol I want to mention Evey time you flash an OTA or anything that will alter the work this twrp installs, you need to flash the file afterwards, before rebooting. And reboot after flashing it so everything links up. Of coarse you can select to reboot right back to recovery. Best luck I couldn't find their post on xda so that's why I typed up so much. Lol I'll be funny again I don't know who this stuff on how to downgrade really but thiers a Windows tool that has capibillities err what ever to flash a OTA of 10 in fastboot mode. Anyways no worries. It's called all-in-one flash tool. Works on maney OnePlus phones. Maybe for encrypted data partitions. I run unencrypted stuff I do not like encryption on any electric devices.

aNGERY said:
7ProAndroid11MagiskBootImg - Google Drive
drive.google.com
Feel free to download it. All I did was extract the boot.img from the payload.bin, copy the boot.img to an extra phone, patched it with magisk, then uploaded it.
Click to expand...
Click to collapse
I just want to say thank you. I tried the new magisk update and it didn't work. I could get to recovery and figured I had PB1 for Andoid11 anffd I would flash to gety baclk to working. Of course I lost root, but was able to get it back with magisk_patched_Ei056.img flashed to boot. It works fine. Can hang with root until TWRP gets updated.
VERY APPRECIATED.

Updated Twrp installer, and a link to both encrypted and unencrypted boot.img and vendor.img's. The Twrp was updated around the 29th. The .img files
I just made. Theirs also a system img if you want it All Beta 1 stuff. The new twrp can install magisk21.4 during the process. The boots I'm hoping can load your beta 1 and let you reboot into twrp right after. Gonna use my open drive and test. Later
[Mod Edit] Link and attachment removed - contained malware!

Crazyinsanejames said:
Updated Twrp installer, and a link to both encrypted and unencrypted boot.img and vendor.img's. The Twrp was updated around the 29th. The .img files
I just made. Theirs also a system img if you want it All Beta 1 stuff. The new twrp can install magisk21.4 during the process. The boots I'm hoping can load your beta 1 and let you reboot into twrp right after. Gonna use my open drive and test. Later
[Mod Edit] Link and attachment removed - contained malware!
Click to expand...
Click to collapse
Well found out thevendor.img didnt work lol. Anyways heres cheap trick i found if your not on an OS with twrp
http://Link removed

aNGERY said:
WOW YOU ARE SMART! Good looking out! This IS way easier. Thank you so much for the heads up!
wait, actually, do some research before you post. there's currently not a functioning TWRP for Android 11 and if you install the update, your TWRP will flash and freeze.
Click to expand...
Click to collapse
You should rephrase your comment. TWRP 3.5.0_9.0 works absolutely fine on Android 11. You may have an issue with OOS11, but it is not an Android 11 issue.

SixArmedPriest said:
You should rephrase your comment. TWRP 3.5.0_9.0 works absolutely fine on Android 11. You may have an issue with OOS11, but it is not an Android 11 issue.View attachment 5204173
Click to expand...
Click to collapse
I'm pretty sure it's insinuated that it's pertaining to OOS11. Don't be willfully obtuse.

SixArmedPriest said:
You should rephrase your comment. TWRP 3.5.0_9.0 works absolutely fine on Android 11. You may have an issue with OOS11, but it is not an Android 11 issue.View attachment 5204173
Click to expand...
Click to collapse
Yeah I agree, so do you have the copyypu could link or a link. Sounds cooI didnt know twrp came out with an update finally

Crazyinsanejames said:
Yeah I agree, so do you have the copyypu could link or a link. Sounds cooI didnt know twrp came out with an update finally
Click to expand...
Click to collapse
35090 for Android 11 on the OnePlus 7 pro will not work without decrypting it.

Crazyinsanejames said:
Yeah I agree, so do you have the copyypu could link or a link. Sounds cooI didnt know twrp came out with an update finally
Click to expand...
Click to collapse
actually I take that back.
Download TWRP for guacamole
Download TWRP Open Recovery for guacamole
dl.twrp.me
Here you go, 3.5.0_9-0 is the one release on 12/28. Install it and let us know how you like it!

spheady said:
Lol nice it worked. Lol it also
Ty tried for fun. Think thos thread is for ppl trying to boot a .img file of twrp. Can this flash via fastboot. So twrp to twrp I think ill keep my dual boot Twrp its not so basic.ty
Click to expand...
Click to collapse
You can reboot to recovery from the OS with this twrp installed?

Question Bootloop with patched boot.img

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.