Develop Bugs

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

h815_usu twrp bootloop problem

i unlock my device using usu mode and using with custom roms. one day i installed ressurection remix 7.01 and supersu after some use i decide to only factory reset for clean start on twrp. after this my device stucked on twrp loop. no matter how try other options and roms booting only twrp.(tried offical latest 3.6.0)
i can use bootloader and download mode and tried unlock again with usu mode but no luck.
here my salt options can i do anything or my device gone forever? device model was H815TR
{
"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"
}

theartanis said:
i unlock my device using usu mode and using with custom roms. one day i installed ressurection remix 7.01 and supersu after some use i decide to only factory reset for clean start on twrp. after this my device stucked on twrp loop. no matter how try other options and roms booting only twrp.(tried offical latest 3.6.0)
i can use bootloader and download mode and tried unlock again with usu mode but no luck.
here my salt options can i do anything or my device gone forever? device model was H815TR
View attachment 5490901
Click to expand...
Click to collapse
Boot to fastboot and exec
fastboot format userdata
Then boot

steadfasterX said:
Boot to fastboot and exec
fastboot format userdata
Then boot
Click to expand...
Click to collapse
booted on twrp and nothing in device. twrp says rom successfully flashed after rebooting device is empity. so twrp wiping auto everything after reboot?

theartanis said:
booted on twrp and nothing in device. twrp says rom successfully flashed after rebooting device is empity. so twrp wiping auto everything after reboot?
Click to expand...
Click to collapse
I told you that you should boot Android after that command and not TWRP. So does Android boot now or not?

i retry and booting to only twrp

theartanis said:
i retry and booting to only twrp
Click to expand...
Click to collapse
Please flash the latest Preview(!) TWRP and not the official one. The official one is only valid for Oreo and does not contain the latest fixes

now i tried with twrp 3.5.2_9 preview-275 same thing happens

theartanis said:
now i tried with twrp 3.5.2_9 preview-275 same thing happens
Click to expand...
Click to collapse
Choose wipe -> advanced format userdata snd reboot.
If that does not fix it doe the above fastboot command again and try to boot

no luck i think main problem is twrp says everytime rom flashing succesfully but device is empity nothing installed

theartanis said:
no luck i think main problem is twrp says everytime rom flashing succesfully but device is empity nothing installed
Click to expand...
Click to collapse
What ROM do you flash? Pls flash a UsU rom.
Also after flashing get the recovery log. See my signature how

i flashing your lineageos 14.1_usu rom
https://bpa.st/IOQA > This log is after flashing rom without reboot system
https://bpa.st/AJQQ > this is after reboot

theartanis said:
i flashing your lineageos 14.1_usu rom
https://bpa.st/IOQA > This log is after flashing rom without reboot system
https://bpa.st/AJQQ > this is after reboot
Click to expand...
Click to collapse
Hm ok all went fine but when flash a nougat based ROM use the nougat(!) preview TWRP . Not sure if that helps but if you wanna use such an old ROM it might be needed anyways.

wow at last 14.1 lineage os booted after installed with N twrp-3.4.0-PREVIEW-230 but it have a error failed to mount /firmware (no such device) after wipe or install its not important right?

theartanis said:
wow at last 14.1 lineage os booted after installed with N twrp-3.4.0-PREVIEW-230 but it have a error failed to mount /firmware (no such device) after wipe or install its not important right?
Click to expand...
Click to collapse
I guess with "it" you meant TWRP has that issue ? As long as you stay on on UsU roms it shouldn't be an issue

thank you for everything now i using your last version of twrp and installed android 9.0 rom

General LE2123_11.C.61 Update in Germany

LE2123_11.C.61_ 1610_202206141855
Finally made it to my device in Hamburg
{
"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"
}

My device is showing the update too, but I did not install yet. How did you maintain root after upgrading?

I am wondering the same. The normal way doesn't work for me. Magisk tells me there is not stock backup.

If anyone knows how to update with root let us know,seems like even using the oxygen updater isn't working too

Deinstall magisk and restore original boot image, update (download incremental via oxygen updater) via oneplus updater app (you'll find it via Google, don't use the integrated updater) and install magisk to inactive slot and reboot. That's it, worked for me

If you have a rooted device and want to keep root you should install it via that local updater apk.
That c61 file you guys have downloaded, is this incremental or full?

I would like the patched boot img for this ROM....
Oxygen 61......
Please

Anonymouze said:
Deinstall magisk and restore original boot image, update (download incremental via oxygen updater) via oneplus updater app (you'll find it via Google, don't use the integrated updater) and install magisk to inactive slot and reboot. That's it, worked for me
Click to expand...
Click to collapse
Unfortunately, that is not working for me. I am getting installation error. I wonder if it could be because the local update app version?

Might be a reason but I don't think so , I attached the version I've used. Do you restore the boot image when deinstalling magisk?

Anonymouze said:
Might be a reason but I don't think so , I attached the version I've used. Do you restore the boot image when deinstalling magisk?
Click to expand...
Click to collapse
Hi, thanks for providing the app. Yes, I restore images, but still get installation error.. I have this issue since c48. I think it's because it is incremental update and my bootloader is unlocked, but I see some people manage to install it. I was hoping OP will releace full zip this time, but it seems I have ti wait.

My bootloader is also unlocked. Do you have oos12 already installed on your inactive boot slot? If not that might be a problem when flashing incremental updates

Anonymouze said:
My bootloader is also unlocked. Do you have oos12 already installed on your inactive boot slot? If not that might be a problem when flashing incremental updates
Click to expand...
Click to collapse
I am on OOS12 c47, but I am not sure what I have on the inactive slot. I had an issue and I had to reset the device after thet I tried c48, but it was the same.

I'm sure there is a way to change/switch the active/inactive slot with adb or fastboot. If so you can check what's going on on the inactive slot

Anonymouze said:
I'm sure there is a way to change/switch the active/inactive slot with adb or fastboot. If so you can check what's going on on the inactive slot
Click to expand...
Click to collapse
Thanks, I will check

I managed to get root on c61...after having updated from 48.
It wasn't straight forward. I couldn't do it the usual way of uninstalling Magisk...and then updating....and then installing Magisk to another slot. So.... This is what I did do.
In Magisk. Uninstall Magisk. Complete Uninstall.
Get into fastboot.
Flash the boot.img file from the pinned post about rooting.
Reboot and update as normal.
Now...go to the rooting post...and root again.

I updated from C47 with this method:
I first updated magisk to 25.1 and downloaded the module universal safteynet fix 2.3.1
I disabled all modules in magisk and did a reboot
In magisk manager I uninstalled magisk and restored the boot image
I installed the C61 update in system settings (no oxygen updater or local update)
After installing I did NOT reboot but reinstalled magisk to inactive slot. Then I did a reboot
After the reboot I reactivated my modules

rumaroma said:
I updated from C47 with this method:
I first updated magisk to 25.1 and downloaded the module universal safteynet fix 2.3.1
I disabled all modules in magisk and did a reboot
In magisk manager I uninstalled magisk and restored the boot image
I installed the C61 update in system settings (no oxygen updater or local update)
After installing I did NOT reboot but reinstalled magisk to inactive slot. Then I did a reboot
After the reboot I reactivated my modules
Click to expand...
Click to collapse
I couldn't restore my boot image. I had used the Alpha version ....which doesn't backup the boot image. So I had to do it the way I did. Your way is the usual way on a\b phones.

Hi guys!
Can I get boot.img for C61???? Please

rumaroma said:
I updated from C47 with this method:
I first updated magisk to 25.1 and downloaded the module universal safteynet fix 2.3.1
I disabled all modules in magisk and did a reboot
In magisk manager I uninstalled magisk and restored the boot image
I installed the C61 update in system settings (no oxygen updater or local update)
After installing I did NOT reboot but reinstalled magisk to inactive slot. Then I did a reboot
After the reboot I reactivated my modules
Click to expand...
Click to collapse
Unfortunately for me, nothing worked. I am also on c47. I tried complete magisk uninstall, re-flashed the full c47 zip (which worked via local update), manually restored boot images on both slots, when tried to update to c48 had the same issue even after factory reset. I am still getting installation problem. Maybe will be waiting for full zip, try to relock the bootloader or just switch to custom ROM

sshriss said:
Unfortunately for me, nothing worked. I am also on c47. I tried complete magisk uninstall, re-flashed the full c47 zip (which worked via local update), manually restored boot images on both slots, when tried to update to c48 had the same issue even after factory reset. I am still getting installation problem. Maybe will be waiting for full zip, try to relock the bootloader or just switch to custom ROM
Click to expand...
Click to collapse
Finally OP released C62 as full zip and I flashed it without issues. I have no major complains. All seem to be working as before.

[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.