I was trying to get dolby atmos on awakenOS, the device is unlocked and was rooted.
I was trying to get a magisk module going for the dolby atmos. As instructed I flashed the magisk 26.0 and all was good but as soon as I flashed the miui core module the device started bootlooping.
To try to fix that I reflashed the boot.img and vendor.boot for the awakenos to reflash the rom and to get the device back . but as soon as I reached the part of adb rebooting to sideload, I reached the sideload but after dragging the rom zip it always says cannot read anymore. Every time I manually boot into recovery I still find the device in sideload. adb commands such as adb reboot and reboot to recovery seem to be doing nothing to the device anymore
Hidden_Iye said:
I was trying to get dolby atmos on awakenOS, the device is unlocked and was rooted.
I was trying to get a magisk module going for the dolby atmos. As instructed I flashed the magisk 26.0 and all was good but as soon as I flashed the miui core module the device started bootlooping.
To try to fix that I reflashed the boot.img and vendor.boot for the awakenos to reflash the rom and to get the device back . but as soon as I reached the part of adb rebooting to sideload, I reached the sideload but after dragging the rom zip it always says cannot read anymore. Every time I manually boot into recovery I still find the device in sideload. adb commands such as adb reboot and reboot to recovery seem to be doing nothing to the device anymore
Click to expand...
Click to collapse
Hello.
The Modules work perfect for me. You need to unbrick your device now by going back to MIUI. Are you able to go to Fastboot Mode?
nabulsi08 said:
Hello.
The Modules work perfect for me. You need to unbrick your device now by going back to MIUI. Are you able to go to Fastboot Mode?
Click to expand...
Click to collapse
Yeah I've tried to reflash the boot.img and the vendor from awakenos devs. And was also successful in flashing the rom but the device still bootloops
Hidden_Iye said:
Yeah I've tried to reflash the boot.img and the vendor from awakenos devs. And was also successful in flashing the rom but the device still bootloops
Click to expand...
Click to collapse
If you are able to go to Fastboot Mode, do the Following things: Download the official Mi Flash Tool and the latest MIUI Version. Flash the extracted ROM and choose the option "Clean all". Your device needs to be back on MIUI to be unbroken safely. You may find a way to unbrick it without flashing MIUI but what I said is what I recommend.
nabulsi08 said:
If you are able to go to Fastboot Mode, do the Following things: Download the official Mi Flash Tool and the latest MIUI Version. Flash the extracted ROM and choose the option "Clean all". Your device needs to be back on MIUI to be unbroken safely. You may find a way to unbrick it without flashing MIUI but what I said is what I recommend.
Click to expand...
Click to collapse
Thank you it worked! I'm back on MIUI and will be going back to AwakenOS. btw so for now is there no other way of getting Dolby on AwakenOS?
Thank you for your time, you guys make this place better with all the help you share.
Hidden_Iye said:
Thank you it worked! I'm back on MIUI and will be going back to AwakenOS. btw so for now is there no other way of getting Dolby on AwakenOS?
Thank you for your time, you guys make this place better with all the help you share.
Click to expand...
Click to collapse
Sure, no problem! I don't know why it didn't work for you. For me it works perfectly fine. I even attached some pictures in the Awaken OS Thread. I can provide the Dolby Atmos of Motorola if you want which I've tried on some devices but not on this one so I cannot say that it will work. I'm not responsible for any bricks too.
I'm still waiting for unlock, but I would like to try if Viper Atmos will deliver the similar effect
Which is reverse engineering on Dolby Atmos I guess?
Related
I got Redmi note 5 (china/AI) version with oreo out of the box and all good but i wanted to get rid of chinese bloatware and stuff. so i installed global official rom which turned out to be for indian Redmi note 5 pro and now i cant use camera. So I am trying to go back or install beta version or install twrp for this (https://forum.xda-developers.com/re...dmi-note-5-china-ai-to-leaked-global-t3782175) but i cant even install twrp. followed the methods still cant. any tips or guidance plz. my bootloader is unlocked.
tried installing twrp through XiaoMiTool, "device unautorized"
tried through Cmd, all worked and after reboot it was supposed to go to twrp automatically but it didnt and got boot up, i went to recovery manually but still stock recovery.
Now what to do ? need global rom for chinese variant which is in .tgz file so that MiTool can flash it. or tell me a way to flash roms in zip format.
Downloaded official roms from http://en.miui.com/download-342.html#513 both roms were in zip file. both roms didnt install the way described in Flashing guide (update app, search downloaded_rom and flash)
MiTool didnt flash them
MiFlash didnt install them.
Did you execute this command - fastboot boot twrp.img right after this command - fastboot flash recovery twrp.img? You need to boot to twrp first before you reboot. If even after reboot twrp gets replaced by stock recovery, then you need to repeat the fastboot process again and then flash lazyflasher in twrp.
Ghoul159 said:
Did you execute this command - fastboot boot twrp.img right after this command - fastboot flash recovery twrp.img? You need to boot to twrp first before you reboot. If even after reboot twrp gets replaced by stock recovery, then you need to repeat the fastboot process again and then flash lazyflasher in twrp.
Click to expand...
Click to collapse
BRO!!!!! LOVE YOU MAN
thank you so much, turns out i missed that exact command which you mentioned. i've been stuck on this all day man... hahaha thanks. could barely play 1 game of dota through out this day. thanks. tell me if there's a way to give thumbs up or some kind of upvote ?
junioreinstein said:
BRO!!!!! LOVE YOU MAN
thank you so much, turns out i missed that exact command which you mentioned. i've been stuck on this all day man... hahaha thanks. could barely play 1 game of dota through out this day. thanks. tell me if there's a way to give thumbs up or some kind of upvote ?
Click to expand...
Click to collapse
You're welcome bro. I didn't do much. You might've missed this basic step when dealing twrp with miui roms. It's a slight effort. Anyway, enjoy this beast.
Ghoul159 said:
You're welcome bro. I didn't do much. You might've missed this basic step when dealing twrp with miui roms. It's a slight effort. Anyway, enjoy this beast.
Click to expand...
Click to collapse
nah it was enough help, accurately what i needed. Thanks again. Take Care.
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
try to flash stock boot.img and recovery.img
sonn3 said:
try to flash stock boot.img and recovery.img
Click to expand...
Click to collapse
Same issue. So how would we go about flashing properly?
Search for recovery.img and boot.img in stock rom and flash in fastboot mode.
mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
Did you select close avb 2.0 in twrp and factory reset?
mikachu182 said:
hello,
my device is bootlooping after i tried flashing magisk and twrp. How can i fix this?
Click to expand...
Click to collapse
We would need further details on which device (region) which MIUI version (number, android, region) you were on when you attempted to install Magisk. Of course we assume here you had unlocked your bootloader first, otherwise any attempt to flash anything will result in bootloop.
Many have successfully rooted on Android 9 regardless of MIUI version.
Complication often comes with Chineses devices from what I read, Global not so much so if you are on Global device consider yourself lucky
Easiest root is probably to flash LR team TWRP If you can still access fastboot mode (voloume - + power) version 09.24 or 11.04 if you are on Android 9 or version 12.10 if you are on Android 10. Note that you probably have more chances of success being on Android 9.
And use the root feature from WITHIN that TWRP to install root on your device.
You have a complete guide of the steps to reproduce here:
Guide
I have tested on Android 9, EEA device, EEA rom MIUI 11.0.2.0 and it works without an issue if you follow the guide provided above.
If you still want to manually flash Magisk from any other recovery, make sure to use version 19.04 which seems to have the higher odds of success (update afterward from Manager).
Also as mentioned by @wang1chung do not forget to close avb 2.0.
Myself I also had RM Force encrypt option used (just in case) even if not mentionned in the thread.
But unlike what was suggested in those threads I did not wipe data.
That said since I do not want to have TWRP to stick for now, I actually want it to automatically be replaced by stock recovery all went fine for me, and Magisk is there.
And when I need TWRP for something I just flash it again and do my stuff.
Hope this helps.
Good luck!
Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?
allxdadev said:
Same problem here. Luckly fastboot was still working (vol down + power after Redmi logo gets off). Then, I've downloaded stock ROM, and tryied manually execute fastboot commands, without success. Then, I've found a .bat file inside the root folder of the stock ROM .tar.gz archive, then executed the .bat file. Phone is working back. So, whats the catch about install Magisk? Any tips?
Click to expand...
Click to collapse
Personally I used the hassle-free method pressing the button to root directly from within the LR-TWRP (09.24, or 11.04 on Android 9 MIUI), swiped, then pressed that other provided button to close AVB 2.0, swiped and it worked on first attempt.
Of course TWRP got replaced on first reboot by system recovery, but I dont care as I do not want it to stick on my device. I just flash it again when I need it.
Magisk stayed, updated it from Manager (well manager updated first to that new ugly theme.... yurk!), then Magisk updated, no problem.
Note that I am on EU Phone running EEA MIUI 11.0.2.0. You might get a different outcome with other devices/roms.
Side note, LR-TWRP 09.24 installs Magisk 19.04 which has been reported numerous time to work on most Android 9 MIUI regional versions. LR-TWRP 11.04 howevers installs Magisk 20.0 fyi.
Hope this helps,
Regards,
regarding the thread title, i had the same problem. right when i was about to retart everything all over from 0, i was glad i was able to just go into twrp and just unroot. rebooted and it started as if nothing hsppended. now i jjust gotta find which module made me bootloop.
try this n give us the result
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me
Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.
Hello Good day everyone, please help this idiot who just bricked his phone for no reason at all:crying:
I accidentally wipe my system or should i say im just flat out an idiot for wiping everything without any backup. i have installed twrp and i unlock the bootloader already because i wanted to install miui in my mi a2 lite phone but ended up wiping everything and now im stuck in twrp mode. i still can do fastboot and open my phone in twrp mode but thats all NO OS. How can i save my phone back to normal. please help me. THANK YOU ALL!!!
If you can get to fastboot, use the stock rom flash script. See the stock rom thread in the guides forum.
If you've got windows, miflash may be easier to use. I think it takes the same stock rom file.
a1291762 said:
If you can get to fastboot, use the stock rom flash script. See the stock rom thread in the guides forum.
If you've got windows, miflash may be easier to use. I think it takes the same stock rom file.
Click to expand...
Click to collapse
Just make sure you download a fastboot rom which has all partitions.
When I wanted to remove all traces of root from my phone last week, i noticed that many of the more recent images only have /system or just a few partitions.
I ended up installing one of the earliest Pie images (V10.0.2.0.PDLMIFJ if i recall correctly) and then doing all the OTA's until I was at V11.0.9.0.QDLMIXM or something.
Fix
idiotAce said:
Hello Good day everyone, please help this idiot who just bricked his phone for no reason at all:crying:
I accidentally wipe my system or should i say im just flat out an idiot for wiping everything without any backup. i have installed twrp and i unlock the bootloader already because i wanted to install miui in my mi a2 lite phone but ended up wiping everything and now im stuck in twrp mode. i still can do fastboot and open my phone in twrp mode but thats all NO OS. How can i save my phone back to normal. please help me. THANK YOU ALL!!!
Click to expand...
Click to collapse
It happened to me like a week ago and i was able to fix it just yesterday. cuz i am new at this root stuff. But i was able to do it at th e end. You need to install stock rom, miflash. Also download flashable stock rom. Because i installed like 5 stock roms. But they were not flashable so it did not work. Extract the stock rom that you downloaded. Then open miflash. Now go into fastboot mode and plug your phone to your pc. Now locate the folder where flashable files are and then click flash. It should say Success. If not that means it did not work.But it should work so yeah. That is it.
guys my phone boots into fastboot only, no twrp no recovery, any way to fix it?
drshnitzelbauer said:
guys my phone boots into fastboot only, no twrp no recovery, any way to fix it?
Click to expand...
Click to collapse
fastboot oem edl
then launch miflash tool
sushi689 said:
fastboot oem edl
then launch miflash tool
Click to expand...
Click to collapse
it just saved my life and my phone idk how it worked but i fixed it. thanks a lot!!!!!!!!!!!!
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://file5.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
My computer is down so:
THANKS A MILLION!!!!!!!!!!!!!
YOU'RE SO AWESOME!!!!!!!!!!!!
Orion9k0 said:
Is this for root? I'm on 11.0.1.1 and rooted, now I see the OTA for 11.0.2.1, is there a way I can update while keeping root?
Click to expand...
Click to collapse
If you are not using TWRP, follow this guide: https://forum.xda-developers.com/t/guide-how-to-root-oneplus-7t-without-twrp.3979307/
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
posiblyLopsided said:
didnt work. i got stuck on the booting animation. ive heard this is an issue and have experienced this personally with the past 3 updates. i downloaded the patched image to my pc. ive got all the drivers installed and everything. i go into fastboot mode and use this command
Code:
fastboot boot magisk_patched.img
this then boots to the booting animation which it gets stuck on
Click to expand...
Click to collapse
Did you switch back the default OTA active slot after flashing both?
nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
i did not flash i only booted. i have tried flashing in the past with android 11 and had the same result of eternal loading. but that was a while ago and it is possible i did smth wrong.
nagi_007pk said:
Did you switch back the default OTA active slot after flashing both?
Click to expand...
Click to collapse
Did you remove or at the very least disable all Magisk modules before OTA updating?
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
kurskoo40 said:
Try this: If you need help you can always just post a quote here
adb reboot bootloader
fastboot boot "your magisk.img"
Let your phone boot (happens automatically)
adb reboot bootloader
fastboot flash boot "your magisk.img"
Click to expand...
Click to collapse
the issue is that when i do fastboot boot magisk.img it gets stuck on the boot animation. i have to hold the power button and volume up to force it to power off then i can boot it back to the normal version
posiblyLopsided said:
i dont believe i had any enabled in the last update because i havnt had root since android 10 but maybe when i initially updated months ago to android 11 i may have.
Click to expand...
Click to collapse
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
thexile said:
Ensure the folder /data/adb/modules is empty. In other words, delete all your Magisk modules and try again.
Click to expand...
Click to collapse
how would i do that? can i use my phone file manager or do i need to use adb?
posiblyLopsided said:
how would i do that? can i use my phone file manager or do i need to use adb?
Click to expand...
Click to collapse
Since you have no root access currently, you have to do so via adb in recovery mode with adb enabled.
thexile said:
Since you no root access currently, you have to do so via adb in recovery mode with adb enabled.
Click to expand...
Click to collapse
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
posiblyLopsided said:
im camping over the weekend so i will try this on monday and get back to you if it works or not. i assume now its prob good practice to disable magisk modules when updating so i will do that from now on.
Click to expand...
Click to collapse
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
yeah looks like i learned the hard way too. also i didnt realise they released twrp for oneplus 7t. id heard that it just didnt work with android 11 but maybe im wrong. ill try it out anyways. if the twrp works that would be amazing. also thanks for all the help.
thexile said:
OnePlus 7T OxygenOS 11.0.2.1.HD65AA Global boot.img
Stock: https://srv-file9.gofile.io/download/9552fcfe-db22-44ef-81a6-5dd49b7e2c6b/boot.img
Magisk v23.0 Patched: https://srv-store6.gofile.io/download/bb88a9cb-e642-4888-b73e-76265a34a6cf/magisk_patched-23000.img
Click to expand...
Click to collapse
Thanks. This worked fine. I just used local install from update, backed out without rebooting, installed magisk app and did the first reboot into bootloader, then wrote magisk modded boot image to boot a/b. It was a dirty update over the prior version.
thexile said:
Yes, at the very least disable all Magisk modules before OTA update. I learnt this hard way. One particular module that I know of which will cause bootloop after OTA is SmaliPatcher.
Anyway, I found a simpler method which bypass the manual patching of stock recovery.img (I couldn't get it to work on OOS11 anyway).
Use this version of TWRP and fastboot boot into it. You should then boot into TWRP (without overwriting your stock recovery) and use TWRP file manager to delete all Magisk modules.
Click to expand...
Click to collapse
i have successfully rooted after useing twrp to remove those magisk modules.
Hi, I really need EU version of boot.img, could you please help me?
I've even looked for the full 11.0.2.1.HD65BA but with no luck.
So basically can't find anywhere both the boot.img and the full stock rom, any advice?
Thank you