Develop Bugs

Phone keeps rebooting in to recovery

Today i was checking if the kernel which i compiled works or not so i flashed it in philz touch CWM recovery and at after reboot it just kept on flashing LG logo.so i just went back in to recovery and as i didn't have any back up i just flashed the new rom file and after that whenever i try to reboot my phone it goes in to recovery.I tried removing battery and then rebooting but then also it reboots in to recovery.
I had flashed these kernels before and that time also my phone kept flashing LG logo but that time I used TWRP recovery and flashed a new rom sometimes and sometimes just flashed backup and i didn't had any problems,today i flashed CWM and I am running in to this problem .
BTW my phone is E980.
thank you.

yey got it solved.flashed TWRP recovery by madmack and then flashed the rom and it worked.I will never ever touch CWM recovery again.

sukesh1090 said:
yey got it solved.flashed TWRP recovery by madmack and then flashed the rom and it worked.I will never ever touch CWM recovery again.
Click to expand...
Click to collapse
The only one works for me is CWM 6.0.4.4 the problem is any ROM straight from stock f240, GX etc... use aboot.img like CWM 6.0.4.7 so if you use a recovery that not use it this will cauae a boot loop.
I open the zip a delete and done
keep this files on zip anything else delete.
{
"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 am used to the TWRP recovery.I use it in all of my devices,I flashed CWM just to check if my phone goes in to fastboot mode or not and even with CWM my phone won't stay in fastboot mode,so i went back to TWRP.

sukesh1090 said:
I am used to the TWRP recovery.I use it in all of my devices,I flashed CWM just to check if my phone goes in to fastboot mode or not and even with CWM my phone won't stay in fastboot mode,so i went back to TWRP.
Click to expand...
Click to collapse
1. Where did you find the particular TWRP?
2. If you phone was bootlooping into CWM recovery, as mine is doing as well, how did you flash TWRP? Was it already downloaded to phone?

here try this,
TWRP-2.6.1.0-E980-LOKIFIED-E986HACKED.zip
this worked for me.copy it to SD card and then flash this zip in CWM and reboot recovery.it will boot in to TWRP and then factory reset and flash new rom after that you ashould be good to go.

sukesh1090 said:
here try this,
TWRP-2.6.1.0-E980-LOKIFIED-E986HACKED.zip
this worked for me.copy it to SD card and then flash this zip in CWM and reboot recovery.it will boot in to TWRP and then factory reset and flash new rom after that you ashould be good to go.
Click to expand...
Click to collapse
How do I copy it to the SD card? My phone is no longer showing up on the computer when plugged in.

use micro SD card reader or some other phone which can take sd card.

Weird problem while flashing Official Nougat on my op3.

I was on
OOS 3.2.8 with official twrp.
I flashed modified twrp (.28 ) in official twrp .
After that i wiped everything except internal.
Flashed official 4.0 full zip.
Wiped cache & dalvik
Flashed Supersu v79
Flashed official twrp img file in modified twrp (assuming that I will get official twrp after booting to 4.0)
Again wiped cache & dalvik
Clicked on reboot system, msg appeared that No Os Installed sure to reboot?
I rebooted,after that device successful booted but then stucked on this screen---- not moving forward from here.
My recovery is also replaced with Stock Oxygen recovery, I went to Stock recovery > wiped cache & settings data & then again tried to reboot but same problem.
Then I again wiped same things in Stock recovery & tried to install 4.0 from there but Stock recovery showed Install failed.
{
"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"
}
Then i thought nothing can be done from here, so I booted into fastboot mode & tried to flash twrp.
But in pc it showed "can't load recovery "
Now I am confused.
I can't lose internal storage at any cost, so keeping this in mind what can be done to get on official OOS 4.0 with root & twrp.
Help me please.

anonymous77 said:
I was on
OOS 3.2.8 with official twrp.
I flashed modified twrp (.28 ) in official twrp .
After that i wiped everything except internal.
Flashed official 4.0 full zip.
Wiped cache & dalvik
Flashed Supersu v79
Flashed official twrp img file in modified twrp (assuming that I will get official twrp after booting to 4.0)
Again wiped cache & dalvik
Clicked on reboot system, msg appeared that No Os Installed sure to reboot?
I rebooted,after that device successful booted but then stucked on this screen---- not moving forward from here.
My recovery is also replaced with Stock Oxygen recovery, I went to Stock recovery > wiped cache & settings data & then again tried to reboot but same problem.
Then I again wiped same things in Stock recovery & tried to install 4.0 from there but Stock recovery showed Install failed.
Then i thought nothing can be done from here, so I booted into fastboot mode & tried to flash twrp.
But in pc it showed "can't load recovery "
Now I am confused.
I can't lose internal storage at any cost, so keeping this in mind what can be done to get on official OOS 4.0 with root & twrp.
Help me please.
Click to expand...
Click to collapse
Flash modified TWRP 1.28 (That is the only recovery you'll need!)
Try to boot and into TWRP, connect the device to your computer and BACKUP your storage. Once done we can proceed.

The OS is indeed installed, so the screen shot you posted. Was your screen hanged there or were you stuck on the step?

Hello to all. for the problem is the recovery that says that there is no os installed, I resolved not doing wipe system

anonymous77 said:
I was on
OOS 3.2.8 with official twrp.
I flashed modified twrp (.28 ) in official twrp .
After that i wiped everything except internal.
Flashed official 4.0 full zip.
Wiped cache & dalvik
Flashed Supersu v79
Flashed official twrp img file in modified twrp (assuming that I will get official twrp after booting to 4.0)
Again wiped cache & dalvik
Clicked on reboot system, msg appeared that No Os Installed sure to reboot?
I rebooted,after that device successful booted but then stucked on this screen---- not moving forward from here.
My recovery is also replaced with Stock Oxygen recovery, I went to Stock recovery > wiped cache & settings data & then again tried to reboot but same problem.
Then I again wiped same things in Stock recovery & tried to install 4.0 from there but Stock recovery showed Install failed.
Then i thought nothing can be done from here, so I booted into fastboot mode & tried to flash twrp.
But in pc it showed "can't load recovery "
Now I am confused.
I can't lose internal storage at any cost, so keeping this in mind what can be done to get on official OOS 4.0 with root & twrp.
Help me please.
Click to expand...
Click to collapse
Hi,
Your entire partion map is broken now, you don't have any recovery now.
Getting data at this point is somehow boot to ROM. Your hope is to recover the ROM.I think fastboot is working for you.
Try to flash 3.2.8 through oxygen recovery
If it's not working, try below
Proceed with caution(no 100% Guarantee):
1.Download unbrick kit from forum
2.open fastboot and try to flashing only system
3. Dont try storage
4.boot to ROM and recover data
5.do a complete unbrick
6.sideload oxygen 4.0
7.flash twrp28 from fastboot
8. Goto recovery and flash supersu
9.done
Data files for system is there in unbrick kit(oxygen os older version).
Fastboot commands:
flash system system.img

LS.xD said:
Flash modified TWRP 1.28 (That is the only recovery you'll need!)
Try to boot and into TWRP, connect the device to your computer and BACKUP your storage. Once done we can proceed.
Click to expand...
Click to collapse
Yes that's what I thought & tried to flash modified twrp using fastboot but in pc it was showing can't load twrp. I will try that again.
Btw if I can Boot mod twrp then OOS 4.0 can be flashed from it, ?

ansaziz777 said:
Hi,
Your entire partion map is broken now, you don't have any recovery now.
Getting data at this point is somehow boot to ROM. Your hope is to recover the ROM.I think fastboot is working for you.
Try to flash 3.2.8 through oxygen recovery
If it's not working, try below
Proceed with caution(no 100% Guarantee):
1.Download unbrick kit from forum
2.open fastboot and try to flashing only system
3. Dont try storage
4.boot to ROM and recover data
5.do a complete unbrick
6.sideload oxygen 4.0
7.flash twrp28 from fastboot
8. Goto recovery and flash supersu
9.done
Data files for system is there in unbrick kit(oxygen os older version).
Fastboot commands:
flash system system.img
Click to expand...
Click to collapse
I can access oxygen recovery now but can't flash the stock rom from it (3.2.8 & 4.0 both are in my internal storage.

anonymous77 said:
I can access oxygen recovery now but can't flash the stock rom from it (3.2.8 & 4.0 both are in my internal storage.
Click to expand...
Click to collapse
Sideload 3.2.8 and see

anonymous77 said:
I can access oxygen recovery now but can't flash the stock rom from it (3.2.8 & 4.0 both are in my internal storage.
Click to expand...
Click to collapse
What stock recovery you have ? I think you need Ver 2.0 . Ver 1.0 is for MM ROM, and Ver 2.0 is for Nougat one. Find them on the XDA forum

simanicu said:
What stock recovery you have ? I think you need Ver 2.0 . Ver 1.0 is for MM ROM, and Ver 2.0 is for Nougat one. Find them on the XDA forum
Click to expand...
Click to collapse
Searched but couldn't find the v2 stock recovery.

anonymous77 said:
Searched but couldn't find the v2 stock recovery.
Click to expand...
Click to collapse
Go here:
http://oneplusroms.s3.amazonaws.com...694818&Signature=DSUZrSJyV46Dd/JKBmI3Z1Dri5Q=
That should link to the recovery.
It has to be sideloaded through fastboot:
fastboot flash recovery filename.img

@ansaziz777 @LS.xD
Yesterday night I flashed modified twrp using fastboot, after that I tried to clean flash 4.0 again using modified twrp, but same pattern repeated again.
Then I flashed stock recovery (downloaded from google) & then tried to flash 4.0 through stock but again it showed install failed.
Then I again flashed twrp & then took backup of my internal storage & moved 4.0 to desktop.
After that
Fastboot format userdata
Then flashed twrp to transfer internal storage to my phone & this time pc showd can't move this ffile (or similar msg)
Then I flashed oxygen Recovery & then tried to sideload the rom (idk full steps to sideload, didn't find any detailed tutorial on youTube )
Attaching image of the it.
I placed 4.0 zip on desktop & then in stock recovery Clicked on adb and then entered command "adb sideload four.zip" but it failed again
Now I am fuc*ing confused what happened & what to do.
Current status is oxygen Recovery Installed with everything erased.
But even after formatting, phone is in same condition like before.
Someone confirm it that when I l successfully flashed modified twrp & then booted in to it, the version in twrp screen was written as 3.0.2-1 & not 3.0.2-1.28...... Is it normal?
Someone help me please with easiest way.

edit: fail^^

anonymous77 said:
@[email protected]
Yesterday night I flashed modified twrp using fastboot, after that I tried to clean flash 4.0 again using modified twrp, but same pattern repeated again.
Then I flashed stock recovery (downloaded from google) & then tried to flash 4.0 through stock but again it showed install failed.
Then I again flashed twrp & then took backup of my internal storage & moved 4.0 to desktop.
After that
Fastboot format userdata
Then flashed twrp to transfer internal storage to my phone & this time pc showd can't move this ffile (or similar msg)
Then I flashed oxygen Recovery & then tried to sideload the rom (idk full steps to sideload, didn't find any detailed tutorial on youTube )
Attaching image of the it.
I placed 4.0 zip on desktop & then in stock recovery Clicked on adb and then entered command "adb sideload four.zip" but it failed again
Now I am fuc*ing confused what happened & what to do.
Current status is oxygen Recovery Installed with everything erased.
But even after formatting, phone is in same condition like before.
Someone confirm it that when I l successfully flashed modified twrp & then booted in to it, the version in twrp screen was written as 3.0.2-1 & not 3.0.2-1.28...... Is it normal?
Someone help me please with easiest way.






Click to expand...
Click to collapse
Dude, don't worry
First Twrp28 looks 3.0.1-1 only when you boot to it.
2.This issue happens when your partion table got lost(means corrupted, that's why not able to transfer)
best way to recover is
Download unbrick kit from xda
1.power of and press volume up button, then connect to Qualcomm mode
2.recover to 3.2.6
3.then start again

Issue solved.
Booted on 3.2.8

anonymous77 said:
Issue solved.
Booted on 3.2.8
Click to expand...
Click to collapse
Always replay with how u solved it, it may help others.
Sent from my ONEPLUS A3003 using Tapatalk

rkkaranrk said:
Always replay with how u solved it, it may help others.
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
First I used fastboot erase recovery & then flashed stock recovery again but again nothing was happening.
Then formated everything, then flashed modified twrp .
Flashed oos3.2.8 in twrp then flashed modtwrp.img in twrp , after that rebooted in twrp before rebooting system (this is what I did wrong earlier).
After rebooting to twrp , rebooted to system.
Previous error was gone now but now new error came : encryption issue.
Then used tool kit to force decrypt the op3.
After that rebooted to oos3.2.8

Rooting the Pixel XL with Magisk

So I just got a Pixel XL and have unlocked the bootloader, but now I'm trying to root and I'm very confused. I have a few questions:
Should I be using TWRP RC1 or RC2? I'm currently on 3.1.0-0RC2 but I hear RC2 has weird issues with restoring/making Nandroids but I can't tell if that refers to the RC2 of a different build or what... The other issue is the TWRP page for Marlin only lists RC2 for v3.1.0, there is no RC1
Is it possible to get MagiskSU running and installed without a custom kernel - if possible I'd like to stick to the stock kernel
Can I use Magisk Modules or am I stuck in Core Only mode?
Any help would be appreciated, thanks!

CarteNoir said:
So I just got a Pixel XL and have unlocked the bootloader, but now I'm trying to root and I'm very confused. I have a few questions:
Should I be using TWRP RC1 or RC2? I'm currently on 3.1.0-0RC2 but I hear RC2 has weird issues with restoring/making Nandroids but I can't tell if that refers to the RC2 of a different build or what... The other issue is the TWRP page for Marlin only lists RC2 for v3.1.0, there is no RC1
Is it possible to get MagiskSU running and installed without a custom kernel - if possible I'd like to stick to the stock kernel
Can I use Magisk Modules or am I stuck in Core Only mode?
Any help would be appreciated, thanks!
Click to expand...
Click to collapse
Go here and search for Installation Instructions: [Unofficial] Google Pixel family support by goodwin_c
Go here for the latest Magisk/Magisk Manager Pixel/Pixel XL files.

Homeboy76 said:
Go here and search for Installation Instructions: [Unofficial] Google Pixel family support by goodwin_c
Go here for the latest Magisk/Magisk Manager Pixel/Pixel XL files.
Click to expand...
Click to collapse
Hi there, I went to that thread but it has no instructions, just discussion. I had a look for instructions but could only find other threads. I followed what they said (fastboot boot twrp.img => flash twrp.zip => reboot recovery => flash magisk.zip => flash twrp.zip => reboot system) but the root doesn't work (despite all recovery logs saying everything worked properly), and I get this when I open MagiskManager:
{
"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"
}

CarteNoir said:
Hi there, I went to that thread but it has no instructions, just discussion. I had a look for instructions but could only find other threads. I followed what they said (fastboot boot twrp.img => flash twrp.zip => reboot recovery => flash magisk.zip => flash twrp.zip => reboot system) but the root doesn't work (despite all recovery logs saying everything worked properly), and I get this when I open MagiskManager:
Click to expand...
Click to collapse
have you done a 2nd reboot? sometimes that's the charm...

Captain Hindsight said:
have you done a 2nd reboot? sometimes that's the charm...
Click to expand...
Click to collapse
I've done multiple reboots sadly. Still nothing.

@CarteNoir working for me on PA. I always flash magisk last. Twrp is working fine for me. perhaps twrp is flashing over magisk?

tdct12 said:
@CarteNoir working for me on PA. I always flash magisk last. Twrp is working fine for me. perhaps twrp is flashing over magisk?
Click to expand...
Click to collapse
I think that might be the case but I don't know how to stop it. I tried flashing Magisk after TWRP but still no dice. I tried flashing the ElementalX kernel as per the guides and it finally works, but I really don't want to have to use a custom kernel, I'd much rather just stick to the stock kernel. Is there any way I can get this working with the stock kernel?

tdct12 said:
@CarteNoir working for me on PA. I always flash magisk last. Twrp is working fine for me. perhaps twrp is flashing over magisk?
Click to expand...
Click to collapse
TWRP does not flash over magisk, never has and isn't now.
---------- Post added at 07:40 AM ---------- Previous post was at 07:38 AM ----------
CarteNoir said:
I think that might be the case but I don't know how to stop it. I tried flashing Magisk after TWRP but still no dice. I tried flashing the ElementalX kernel as per the guides and it finally works, but I really don't want to have to use a custom kernel, I'd much rather just stick to the stock kernel. Is there any way I can get this working with the stock kernel?
Click to expand...
Click to collapse
So the modified kernel hides your unlocked bootloader status, running the stock kernel means you will fail safetynet and thus negate using magisk to begin with. There is a patched stock kernel you can fastboot that patches the bootloader check but it needs to be fastbooted to the device. Thats if you can get magisk working with it.

pcriz said:
TWRP does not flash over magisk, never has and isn't now.
---------- Post added at 07:40 AM ---------- Previous post was at 07:38 AM ----------
So the modified kernel hides your unlocked bootloader status, running the stock kernel means you will fail safetynet and thus negate using magisk to begin with. There is a patched stock kernel you can fastboot that patches the bootloader check but it needs to be fastbooted to the device. Thats if you can get magisk working with it.
Click to expand...
Click to collapse

pcriz said:
TWRP does not flash over magisk, never has and isn't now.
So the modified kernel hides your unlocked bootloader status, running the stock kernel means you will fail safetynet and thus negate using magisk to begin with. There is a patched stock kernel you can fastboot that patches the bootloader check but it needs to be fastbooted to the device. Thats if you can get magisk working with it.
Click to expand...
Click to collapse
Hey there, took a look at that patched stock kernel but unfortunately couldn't get it to work. I tried following the standard installation steps up until the point where you're supposed to flash the ElementalX kernel, at which point I booted back to bootloader and used fastboot flash kernel to flash the patched stock kernel file, then I returned to recovery to flash TWRP again as per the flow of the instructions, however that didn't work and Magisk still shows as not installed/no root.
I then tried flashing stock images/uninstalling Magisk, then following the standard instructions all the way through, installing the ElementalX kernel along the way. I then rebooted, confirmed Magisk installed and was working correctly, then went back into the bootloader and used fastboot flash kernel to flash the patched stock kernel file. However again on rebooting to system I found that Magisk said no root/not installed.
Is ElementalX doing something other than removing the androidboot.verifiedbootstate flag in regards to making Magisk work? Or is there perhaps anywhere where I can find a TWRP flashable package version of the patched stock kernel?

CarteNoir said:
Hey there, took a look at that patched stock kernel but unfortunately couldn't get it to work. I tried following the standard installation steps up until the point where you're supposed to flash the ElementalX kernel, at which point I booted back to bootloader and used fastboot flash kernel to flash the patched stock kernel file, then I returned to recovery to flash TWRP again as per the flow of the instructions, however that didn't work and Magisk still shows as not installed/no root.
I then tried flashing stock images/uninstalling Magisk, then following the standard instructions all the way through, installing the ElementalX kernel along the way. I then rebooted, confirmed Magisk installed and was working correctly, then went back into the bootloader and used fastboot flash kernel to flash the patched stock kernel file. However again on rebooting to system I found that Magisk said no root/not installed.
Is ElementalX doing something other than removing the androidboot.verifiedbootstate flag in regards to making Magisk work? Or is there perhaps anywhere where I can find a TWRP flashable package version of the patched stock kernel?
Click to expand...
Click to collapse
So I think you would want to fastboot the stock boot.IMG. flash the kernel, then turn around and flash twrp, reboot, install magisk.
If Elemental is doing something more to make this work I don't know what it is, but essentially every custom kernel or kernel that comes packaged with a custom rom does the same thing.

[OP7T][Stock/Magisk v23.0] OxygenOS 11.0.9.1.HD65AA boot.img

OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img
Stock: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g
Magisk v23.0 Patched: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc
Note: DISABLE ALL MAGISK MODULES BEFORE EXECUTING OTA UPGRADE

I have OnePlus7T Indian version. I was on 11.0.9.1 and rooted with Magisk. I have Canary version installed. There was an Update to Magisk which I accidentally by OTA instead of full and now my phone is not booting. It goes into original recovery mode or fastboot only. How can I recover from this? I tried to flash the magisk patched image and it shows as flashed but when I reboot I again reach original recovery / fastboot menu only. Please help!!

jesrani said:
I have OnePlus7T Indian version. I was on 11.0.9.1 and rooted with Magisk. I have Canary version installed. There was an Update to Magisk which I accidentally by OTA instead of full and now my phone is not booting. It goes into original recovery mode or fastboot only. How can I recover from this? I tried to flash the magisk patched image and it shows as flashed but when I reboot I again reach original recovery / fastboot menu only. Please help!!
Click to expand...
Click to collapse
flash original (stock) boot.Img above to unroot

HueyT said:
flash original (stock) boot.Img above to unroot
Click to expand...
Click to collapse
Thanks. Would that work for Indian version also? And would that wipe data?
I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.

jesrani said:
Thanks. Would that work for Indian version also? And would that wipe data?
I was trying many things and when I used Tool All in One to flash TWRP the phone rebooted into the system. Not even sure if TWRP is installed or not but everything is working now and phone is rooted. Not sure how it got resolved. Magisk is updated to latest version.
Click to expand...
Click to collapse
All variants share same boot, data fine

HueyT said:
flash original (stock) boot.Img above to unroot
Click to expand...
Click to collapse
jesrani said:
I have OnePlus7T Indian version. I was on 11.0.9.1 and rooted with Magisk. I have Canary version installed. There was an Update to Magisk which I accidentally by OTA instead of full and now my phone is not booting. It goes into original recovery mode or fastboot only. How can I recover from this? I tried to flash the magisk patched image and it shows as flashed but when I reboot I again reach original recovery / fastboot menu only. Please help!!
Click to expand...
Click to collapse
In such situation always remember, flashing original boot.img may not work best is change the partition. so if you are in a go to b and boot. Use temp TWRP custom recovery to change partition if you cannot change via command line. and once you are able to boot, flash magisk properly on both partition.

This isn't really working for me, I try to flash it with 'fastboot flash boot magisk_patched-23000.img' but it does say this on command but it doesn't boot into root
{
"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"
}
Edit: I have Magisk ver. 25.2

RRRb50 said:
This isn't really working for me, I try to flash it with 'fastboot flash boot magisk_patched-23000.img' but it does say this on command but it doesn't boot into root
View attachment 5716169
Edit: I have Magisk ver. 25.2
Click to expand...
Click to collapse
did you install magisk25 apk?

thexile said:
OnePlus 7T OxygenOS 11.0.9.1.HD65AA Global boot.img
المخزون: https://mega.nz/file/CV9B2I5A#kIjb0ST0XvAn1yJTMi56hdz1asi-d_LH0uaOCcfrA2g
Magisk v23.0 مصححة: https://mega.nz/file/eFcygLwb#U0m48VlQekyhrKAEC3Oc56yfxdbjGmGhiwgndU-Grwc
ملاحظة: قم بتعطيل كافة وحدات MAGISK قبل تنفيذ ترقية OTA
Click to expand...
Click to collapse

I am on OOs 11.0.9.1. my device went into bootloop after i updated some magisk modules.
After spending a number of hours doing various trials and checking Xda threads I managed to get it to boot again but root was lost.
I again read more articles and learnt that I have to flash recovery to both partitions so I used Tool All in one, changed active slots and flashed the magisk patched image from this thread i think on both slots. But i am not sure. I managed to get root but the Magisk manager was not getting installed.
I tried few other things and finally i am now not able to root again. Phone is booting after I flash a recovery but I am not sure if it will boot if restarted or go into loop.
Can anyone explain the proper procedure and sequence to follow for rooting and which files to use.

I installed twrp on partition a and now I am having root. I was not able to install Magisk25.2.apk but was able to install some other version, I think Canary release. So most things seem to work. However when I click Add Systemless Host, nothing seems to be happening. AdAway is not working. How can I get this to work again.
HDFC banking app is also detecting root even though I have installed HideMyApplist and configured DevOptsHide and HideMyApplist in LsPosed. Not sure what is the mistake. Can anyone advice?

Question After flashing TWRP the root is gone

Hello,
After flashing TWRP from advanced options (flash current TWRP) on Xiaomi 12X, Miui 14), it removes the magisk root. When I patch the boot image with magisk again, the root is back but stock recovery is restored. I tried the option to prevent TWRP being replaced by the stock recovery in the advanced options but it did not work. Is there any way to keep BOTH TWRP and root on this device? Thank you.

Wojtek1971 said:
Hello,
After flashing TWRP from advanced options (flash current TWRP) on Xiaomi 12X, Miui 14), it removes the magisk root. When I patch the boot image with magisk again, the root is back but stock recovery is restored. I tried the option to prevent TWRP being replaced by the stock recovery in the advanced options but it did not work. Is there any way to keep BOTH TWRP and root on this device? Thank you.
Click to expand...
Click to collapse
Have you tried with the REC version?
https://forum.xda-developers.com/t/shared-recovery-psyche-twrp-by-skkk.4461461/post-88081701

NOSS8 said:
Have you tried with the REC version?
https://forum.xda-developers.com/t/shared-recovery-psyche-twrp-by-skkk.4461461/post-88081701
Click to expand...
Click to collapse
Does not work, either.

Wojtek1971 said:
Does not work, either.
Click to expand...
Click to collapse
Did you do it like this?
1/root
2/Twrp

NOSS8 said:
Did you do it like this?
1/root
2/Twrp
Click to expand...
Click to collapse
How do I flash TWRP, i.e. what is the actual fastboot command? Also, does it matter which version of TWRP I should flash since there are quite a few of them?

In TWRP go to advanced. There you can choose to install TWRP directly.

Wojtek1971 said:
How do I flash TWRP, i.e. what is the actual fastboot command? Also, does it matter which version of TWRP I should flash since there are quite a few of them?
Click to expand...
Click to collapse
Same method
https://forum.xda-developers.com/t/shared-twrp-by-skkk.4479573/

NOSS8 said:
Same method
https://forum.xda-developers.com/t/shared-twrp-by-skkk.4479573/
Click to expand...
Click to collapse
The cmd fastboot flash recovery_ab twrp.img command fails. After booting to twrp using the fastboot boot twrp.img command and using the option flash current recovery upon rebooting system I'm back in twrp. The only way to get out of the bootloop is to flash magisk patched boot image to both partitions, which restores the stock recovery.

Wojtek1971 said:
The cmd fastboot flash recovery_ab twrp.img command fails. After booting to twrp using the fastboot boot twrp.img command and using the option flash current recovery upon rebooting system I'm back in twrp. The only way to get out of the bootloop is to flash magisk patched boot image to both partitions, which restores the stock recovery.
Click to expand...
Click to collapse
Do you use this rom.V14.0.1.0.TLDEUXM?
What Twrp have you tried (full name)?
Edit:
My bad,No rec version for this device.
After flashing the patched boot did you do that?
{
"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"
}

NOSS8 said:
Do you use this rom.V14.0.1.0.TLDEUXM?
What Twrp have you tried (full name)?
Edit:
My bad,No rec version for this device.
After flashing the patched boot did you do that?
View attachment 5843407​
Click to expand...
Click to collapse
I used this one: [BOOT]3.7.0_12-Mi12X_v7.1_A13-psyche-skkk. I did use the direct install method with magisk. I also tried to install TWRP to recovery ramdisk - it apparently went okay but on rebooting to recovery I'm back to stock one. I also tried flashing orangefox but with the same result . Yes, I'm on the latest miui version.

I've finally worked it out. This is what I did:
1. I rebooted to fastboot
2. In adb I entered "fastboot boot name of the twrp.img
3. Once in twrp I flashed the recovery version of my rom (Miui 14) downloaded from xiaomifirmwareupdater.com
4. I went to advanced options and used install recovery ramdisk
5. In advanced options again I entered "Use magisk to patch boot"
6. I rebooted the system: no bootloop and the root working perfectly.
It is crucial to install twrp first and only then patch the boot from twrp , not the other way round.

P.S.
In this procedure the twrp recovery is not overwritten by stock one.