Develop Bugs

Boot hang, TWRP Recovery unresponsive

Coming to you all with hat in hand.
Not sure what steps to take next.
Unlocked bootloader and all the rest of the steps here:
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
Symptom is a never ending booting "G".
I reboot and can choose recovery but the twrp screen in unresponsive. As in, I get the slider but cannot slide it.
I'm not sure what that means.
I do see the device and its listed as 'recovery' in adb.
I did see the issue of using old platform tools too late. :crying:
How bleak is my outlook?
Thank you for any help.

When you booted the twrp.img did you have the newest one and then install the newest twrp installer.zip?

Short version... Extract the boot.img from the system image file and install that to both partitions through fastboot (going to have to do some reading on how to do that, and you might learn a bit in the process). System should boot normally then with stock recovery. Now, you can use the current version of the twrp.img to root without even needing to permanently install it. Before you even do that though, spend some time getting to know your device and the current versions and options that are out there. That web page you pointed to was just a primer and was published when the device first came out. Their have been some small changes.

@edmodumb - What billy said^^. From your adb folder you can fastboot flash boot.img, then fastboot boot twrp.img right afterwards to get TWRP back (and the phone will boot System as well).

pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?

motrac said:
pixel 3xl unlocked bootloader - installed twrp.img via fastboot- installed twrp.zip in recovery-installed magisk 17.3 via
recovery
phone booted up , no problem then i went to magisk app and installed magisk installed by direct patch and rebooted,
now struck in booloop.
if i boot into recovery twrp is unresponsive even if i reinstall with fastboot.
i tried to install factory image but still stuck in bootloop????
i tried to flash boot.img to the a and b partions with fastboot but no sure if i'm doing it right?
Click to expand...
Click to collapse
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch

Homeboy76 said:
Flash the boot image to both slots #6 in the guide or flash the factory image #4 in the guide to return to stock. then do #7 in the guide to root. Done! Do not flash the patched_boot.img.
[Guide] Pixel 3 XL Android 9.0 (Pie) Unlock/Root/Install Images/Kernels/Recovery + November 2018 Security Patch
Click to expand...
Click to collapse
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"

motrac said:
i flashed factory and it installs but at the end i get this:
"Erase successful, but not automatically formatting. File system type raw not supported."
is that ok or is it an error?
phone still doesn't boot.
when i flash boot file i get:
"FAILED (remote: Failed to write to partition Not Found)"
Click to expand...
Click to collapse
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help

Yikes ! I am not the expert, but . . . . it really sounds like 'rma' time to me...
.
If you do things on a low battery, it'll corrupt stuff. Is this thing fully charged up ?
.

motrac said:
reflashed factory after updating fastboot and it boots now, good learning lesson for me. thanks for the help
Click to expand...
Click to collapse

Homeboy76 said:
Click to expand...
Click to collapse
@motrac @Homeboy76
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot

jcrompton said:
@[email protected]
Woah sounds like my problem is similar --- I can't boot into anything but a dark screen except for bootloader.
I saw the "updated fastboot"
I tried flashing the boot.img and then the factory image
but no luck --- just blackscreen when I try to do anything other than bootloader
I had some errors when flashing factory image -- see screeen shot
Click to expand...
Click to collapse
Is "updated fastboot" r28.0.1?

Homeboy76 said:
Is "updated fastboot" r28.0.1?
Click to expand...
Click to collapse
Yes.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
Yes.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Still can't boot my device -- just no luck after updating fastboot
PLEASE .. any help would be appreciated!!
This is another place where I was trying to solve the issue - sorry for doubling up
https://forum.xda-developers.com/showpost.php?p=78276952&postcount=258

Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!

I did a backup on twrp and then it wouldn't boot ugh off to try it all again LOL

edmodumb said:
Resurrecting. Had to set aside for a while, sorry.
@sliding_billy & @v12xke , thank you for the responses. Out of around six phones, this is the first time I've had issues rooting/flashing images. That's thanks to XDA.
After your responses and some more learning (this time paying more attention to post dates), I have the phone back up on its feet.
Off to re-root, wish me luck.
Thank you very much!
Click to expand...
Click to collapse
Best of luck!

OnePlus 7T 10.3.0 for Indian HD1901, included with patched boot img

This is the new update 10.3.0, for indian 7Ts HD1901, i got this zip from device update itself
OTA rom - https://drive.google.com/open?id=14eM8AzKKeht6i_zHw8lvSaRoknN90PPk
you need payload dumper to open and extract payload.bin to get .imgs of roms
patched boot image - https://www.androidfilehost.com/?fid=4349826312261679634
use this guide to root your 7T using above img - https://forum.xda-developers.com/oneplus-7t/how-to/guide-how-to-root-oneplus-7t-twrp-t3979307

this is same as the new 10.0.7 for the global/eu versions

Can you please share original boot image from 10.0.7??? payload dumper gives me error.

sagardakua said:
Can you please share original boot image from 10.0.7??? payload dumper gives me error.
Click to expand...
Click to collapse
here it is https://drive.google.com/open?id=1eagdkkAMeaav2AtBI9b7b3m6_LQ-vLH6
this is for indian hd1901, so dont complain to me if you flash this on some another model and get error

I am on the indian variant. Used the above img file and flashed via fastboot. The phone booted fine. Went to Magisk and direct installed it. I hit reboot and i get stuck at the bootloader screen. Any help?

sathya said:
I am on the indian variant. Used the above img file and flashed via fastboot. The phone booted fine. Went to Magisk and direct installed it. I hit reboot and i get stuck at the bootloader screen. Any help?
Click to expand...
Click to collapse
as in fastboot screen or bootloader unlocked screen?
also you dont flash, you boot the image
"fastboot boot patched.img"
maybe try flashing the stock img to restore and try again "fastboot flash boot boot.img" (or do i proper restore via fastboot if that doesnt work, there's a guide here for that)

levai_spencer said:
as in fastboot screen or bootloader unlocked screen?
also you dont flash, you boot the image
"fastboot boot patched.img"
maybe try flashing the stock img to restore and try again "fastboot flash boot boot.img" (or do i proper restore via fastboot if that doesnt work, there's a guide here for that)
Click to expand...
Click to collapse
Sorry, my bad. I used the boot command to boot the img but i am getting stuck at the bootloader post i install magisk. Here is what i did.
Entered Fastboot mode
Through ADB, i used "fastboot boot magisk_patched.img
The phone booted fine
Opened Magisk as i was already rooted before
Clicked on Install
Selected "Direct Install"
Rebooted my phone
Stuck at the bootloader warning screen
Unless i load the image again via fastboot, it wont let me in. Hence i am not able to root

sathya said:
Sorry, my bad. I used the boot command to boot the img but i am getting stuck at the bootloader post i install magisk
Click to expand...
Click to collapse
are you booting or flashing? its a 2 different things...

levai_spencer said:
are you booting or flashing? its a 2 different things...
Click to expand...
Click to collapse
My apologies, i used the wrong term. I edited my post and explained what i am exactly doing above. I am booting not flashing.

sathya said:
My apologies, i used the wrong term. I edited my post and explained what i am exactly doing above. I am booting not flashing.
Click to expand...
Click to collapse
its a well known magisk bug, i also faced such situation hence i asked,
you can either try to flash stock img using
"fastboot flash boot boot.img"
or follow this guide to restore
https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
i was able to fix using above guide
(backup before you continue to be safe)
I'll update the patched boot img just in case

levai_spencer said:
i also faced such situation hence i asked,
you can either try to flash stock img using
"fastboot flash boot boot.img"
or follow this guide to restore
https://forum.xda-developers.com/oneplus-7t/how-to/rom-stock-fastboot-roms-oneplus-7t-t3979213
i was able to fix using above guide
(backup before you continue to be safe)
Click to expand...
Click to collapse
If i boot the original image, i wont be able to root my phone right?
Should i again boot the image you have shared?

sathya said:
If i boot the original image, i wont be able to root my phone right?
Should i again boot the image you have shared?
Click to expand...
Click to collapse
yes, booting stock boot img will remove root, once you fix the problem, you can follow same root guide and patched img to root the phone again

sathya said:
If i boot the original image, i wont be able to root my phone right?
Should i again boot the image you have shared?
Click to expand...
Click to collapse
also, make sure to use same 10.3.0 files to restore your phone using the restore guide i gave (assuming you updated to 10.3.0)

Ok, i followed the procedure. That didnt work. I wiped completely and used your image. As soon as i install magisk, i get stuck in bootloader warning screen. I guess there is no way out to root this new indian firmware.

sathya said:
Ok, i followed the procedure. That didnt work. I wiped completely and used your image. As soon as i install magisk, i get stuck in bootloader warning screen. I guess there is no way out to root this new indian firmware.
Click to expand...
Click to collapse
did you try restore using the guide i gave? i used this guide to fix bootloader stuck
you'll need to download the ota file linked, extract zip, use payload dumper to get imgs, and flash all imgs according to the guide
you can also create your own magisk patched image, thats how i got mine and my 7T is rooted on 10.3.0

okay you can do this if flashing my patched img is causing issues
if you have an old 10.0.6 patched img, use that to get root
i got this one from xda, i was able to also root using that

Ok. I tried pretty much everything. But i am just getting stuck at the bootloader warning screen.
I tried the old 10.0.6 but it doesnt get out of fastboot

sathya said:
Ok. I tried pretty much everything. But i am just getting stuck at the bootloader warning screen.
I tried the old 10.0.6 but it doesnt get out of fastboot
Click to expand...
Click to collapse
did u try to wipe data/internal in recovery?

December firmware update!

Does anyone know where i can find the newest security December 1, 2019 update for the g7 play? i've searched online and cannot find it anywhere. My phone keeps reminding me of a failed update so i went looking for the new one. Do i re-flash the phone to stock and update it that way before re-rooting it or wait until someone post the newest update in the mirrors repository? What do you guys suggest?

dominoeflux said:
Does anyone know where i can find the newest security December 1, 2019 update for the g7 play? i've searched online and cannot find it anywhere. My phone keeps reminding me of a failed update so i went looking for the new one. Do i re-flash the phone to stock and update it that way before re-rooting it or wait until someone post the newest update in the mirrors repository? What do you guys suggest?
Click to expand...
Click to collapse
https://support.motorola.com/us/en/Solution/MS147329
Oct 2019 seems to be the latest:
https://www.theandroidsoul.com/spri...lay-moto-g6-play-with-october-security-patch/
Normally you go back to stock, patch and then re-root.
What model do you have?
I cannot get root on my XT1952-4.

mtmtumbo said:
https://support.motorola.com/us/en/Solution/MS147329
Normally you go back to stock, patch and then re-root.
What model do you have?
I cannot get root on my XT1952-4.
Click to expand...
Click to collapse
I have the same model with boost mobile...do you need help rooting it? I just followed the instructions for the boot.img magisk patch but when you patch it make sure you select beta in magisk and in advanced settings make sure all are checked especially recovery mode before you patch and lastly when you reboot, reboot to recovery every time or the root will not stick...that's something no one mentioned when i was trying to root mine. I had to research the problem of why the root wasn't sticking. When you reboot to recovery it will stay on a blank screen and then vibrate, that's normal. It does that before it boots up. Once it's booted, check to make sure you have root by opening the magisk app, you should see both green check marks and thanks for you help with how to update.

dominoeflux said:
I have the same model with boost mobile...do you need help rooting it? I just followed the instructions for the boot.img magisk patch but when you patch it make sure you select beta in magisk and in advanced settings make sure all are checked especially recovery mode before you patch and lastly when you reboot, reboot to recovery every time or the root will not stick...that's something no one mentioned when i was trying to root mine. I had to research the problem of why the root wasn't sticking. When you reboot to recovery it will stay on a blank screen and then vibrate, that's normal. It does that before it boots up. Once it's booted, check to make sure you have root by opening the magisk app, you should see both green check marks and thanks for you help with how to update.
Click to expand...
Click to collapse
thanks, I followed the instructions as well to patch boot.img and use fastboot with magisk_patched.img, but when I rebooted, I only got the xxxxxx-xxxxxx-xxxxxxx-xxxxxxx-xxxxxx code and then no vibration and nothing else - seems stuck and just looping at this point
what do you mean select beta in magisk?
what version of apk did you create the patched img from? 7.4.0?
and yes, i made sure i checked all the advanced options (including recovery) before creating the patched img file

mtmtumbo said:
thanks, I followed the instructions as well to patch boot.img and use fastboot with magisk_patched.img, but when I rebooted, I only got the xxxxxx-xxxxxx-xxxxxxx-xxxxxxx-xxxxxx code and then no vibration and nothing else - seems stuck and just looping at this point
what do you mean select beta in magisk?
what version of apk did you create the patched img from? 7.4.0?
and yes, i made sure i checked all the advanced options (including recovery) before creating the patched img file
Click to expand...
Click to collapse
when you go in the magisk manager, select the three lines at the top left and go to settings/update channel and select beta....if you don't you will loop. i used the latest magisk version which is 7.4.0 so yes you're using the correct one. your suppose to see those codes it's normal, if the phone does not vibrate, then that means that it didn't work.

dominoeflux said:
when you go in the magisk manager, select the three lines at the top left and go to settings/update channel and select beta....if you don't you will loop. i used the latest magisk version which is 7.4.0 so yes you're using the correct one. your suppose to see those codes it's normal, if the phone does not vibrate, then that means that it didn't work.
Click to expand...
Click to collapse
Thanks, I enabled beta in magisk and tried it again and it still did not vibrate after showing the codes - just rebooting in a loop as before.
What size is your magisk_patched.img and boot.img files?
Here are mine:
33,554,432 boot.img
18,103,592 magisk_patched.img
You can see after the patching that the size of the boot image drops almost in half - is that normal?
I transfer these files using adb push and pull as I heard MTP transfers could corrupt the files.
Anyhow, since we're on the same build, can you post up your boot and patched img somewhere so I can try them?

mtmtumbo said:
Thanks, I enabled beta in magisk and tried it again and it still did not vibrate after showing the codes - just rebooting in a loop as before.
What size is your magisk_patched.img and boot.img files?
Here are mine:
33,554,432 boot.img
18,103,592 magisk_patched.img
You can see after the patching that the size of the boot image drops almost in half - is that normal?
I transfer these files using adb push and pull as I heard MTP transfers could corrupt the files.
Anyhow, since we're on the same build, can you post up your boot and patched img somewhere so I can try them?
Click to expand...
Click to collapse
Did you repatch the stock boot.img before flashing again? The magisk patch is different if not on beta and the magisk recovery is not selected, that's why it's probably still not working.
also make sure that you're patching the correct boot.img from your stock firmware that you're on, it creates problems if you're not. I can't upload my .imgs for some reason and you're correct it didn't vibrate the first time i was successful, but after i have to reboot the phone i would reboot to recovery so when the phone boots the root sticks, that's when it will vibrate.

@mtmtumbo I apologize I haven't been on here in a couple of days, any update on rooting your g7 play?

dominoeflux said:
Did you repatch the stock boot.img before flashing again? The magisk patch is different if not on beta and the magisk recovery is not selected, that's why it's probably still not working.
also make sure that you're patching the correct boot.img from your stock firmware that you're on, it creates problems if you're not. I can't upload my .imgs for some reason and you're correct it didn't vibrate the first time i was successful, but after i have to reboot the phone i would reboot to recovery so when the phone boots the root sticks, that's when it will vibrate.
Click to expand...
Click to collapse
happy new year all
yes i re-patched the stock boot.img before flashing, magisk was on beta and yes the third option in advanced for recovery was selected before i patched the boot.img
after i saw the codes and it was looping, i rebooted the phone to recovery but no difference
i'm also having a problem flashing twrp without just using fastboot boot twrp.img - flashing it with fastboot flash doesn't work (using dtbo.img first to avoid the black screen)
btw you can use mega.nz to upload your img's - give it a shot and post the URL here
if it matters, this is the ROM I'm using:
XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC

mtmtumbo said:
happy new year all
yes i re-patched the stock boot.img before flashing, magisk was on beta and yes the third option in advanced for recovery was selected before i patched the boot.img
after i saw the codes and it was looping, i rebooted the phone to recovery but no difference
i'm also having a problem flashing twrp without just using fastboot boot twrp.img - flashing it with fastboot flash doesn't work (using dtbo.img first to avoid the black screen)
btw you can use mega.nz to upload your img's - give it a shot and post the URL here
if it matters, this is the ROM I'm using:
XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse
Happy New Year man.....i believe i figured out why you're still boot looping, did you reboot back into the bootloader after you flashed the patched.img?
edit: when your doing twrp, you have to boot into it before installing it to the ramdisk. there's a how to in this forum here: https://forum.xda-developers.com/g7-play/how-to/how-to-successfully-install-twrp-g7-play-t3979701
the GSI's don't work for me so i'm waiting for a legit custom build before installing twrp again

Update 134-7
XT1952-2
ATTMX
https://mirrors.lolinet.com/firmwar...USMXLA_regulatory-XT1952-2-MEXICO_CFC.xml.zip
OpenMX
https://mirrors.lolinet.com/firmwar...EFAULT_regulatory-XT1952-2-MEXICO_CFC.xml.zip
RETAR
https://mirrors.lolinet.com/firmwar...ULT_regulatory-XT1952-2-ARGENTINA_CFC.xml.zip

[OP7T][Stock/Magisk] OxygenOS 11.0.2.1.HD65AA boot.img

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

Question le2125_11_c.61 OOS12 root

My phone updated to le2125_11_c.61 and I can't find a suitable boot.img to flash magisk. The OTA update has a partial boot image so that fails. Does anyone have a copy of the boot.img for this version, or is there another method I should use?

rustyshakelford2 said:
My phone updated to le2125_11_c.61 and I can't find a suitable boot.img to flash magisk. The OTA update has a partial boot image so that fails. Does anyone have a copy of the boot.img for this version, or is there another method I should use?
Click to expand...
Click to collapse
Just use the C.48 patched image, boot (don't flash), and then direct install Magisk. Should work. If it doesn't, no harm done since you didn't flash it.

EtherealRemnant said:
Just use the C.48 patched image, boot (don't flash), and then direct install Magisk. Should work. If it doesn't, no harm done since you didn't flash it.
Click to expand...
Click to collapse
That was a nice thought, but unfortunately it didn't work. The phone hangs when booting both the magisk'd and regular C.48 image.
I did fastboot boot boot.img. Is that correct? I'm a bit out of practice.

rustyshakelford2 said:
That was a nice thought, but unfortunately it didn't work. The phone hangs when booting both the magisk'd and regular C.48 image.
I did fastboot boot boot.img. Is that correct? I'm a bit out of practice.
Click to expand...
Click to collapse
Yeah that's correct. Bummer that it didn't work. Give me a few to download and patch it.

rustyshakelford2 said:
That was a nice thought, but unfortunately it didn't work. The phone hangs when booting both the magisk'd and regular C.48 image.
I did fastboot boot boot.img. Is that correct? I'm a bit out of practice.
Click to expand...
Click to collapse
Well unfortunately I have downloaded two different python scripts trying to patch the full OTA with the incremental OTA and they are both failing so I guess we will have to wait for someone else to do it because I don't have the expertise to fix this.

As long as your bootloader is unlocked, You could try booting (again not flashing) into TWRP and then try sideloading Magisk (after renaming .apk to .zip) ?

djsubterrain said:
As long as your bootloader is unlocked, You could try booting (again not flashing) into TWRP and then try sideloading Magisk (after renaming .apk to .zip) ?
Click to expand...
Click to collapse
You can't boot into TWRP because it doesn't work on OOS12. It crash dumps.
Someone who is rooted needs to install the OTA and pull the image unless there is a tool I haven't come across that works better for incremental OTA extraction.

The incremental C.61 OTA (downloaded thru Oxygen Updater) ins't getting installed.
The oxygen updater app isn't listing the file and the About device Local Install is throwing Verification failed.
Any idea to fix this ?
LE2121
Thanks

observingi said:
The incremental C.61 OTA (downloaded thru Oxygen Updater) ins't getting installed.
The oxygen updater app isn't listing the file and the About device Local Install is throwing Verification failed.
Any idea to fix this ?
LE2121
Thanks
Click to expand...
Click to collapse
I am also facing the same problem..

rustyshakelford2 said:
My phone updated to le2125_11_c.61 and I can't find a suitable boot.img to flash magisk. The OTA update has a partial boot image so that fails. Does anyone have a copy of the boot.img for this version, or is there another method I should use?
Click to expand...
Click to collapse
Try using the MSM tool for your device, press F8, then select boot_a or boot_b depending on what slot you're in. To check your slot, reboot to fastboot and issue the command fastboot getvar current-slot.
You should be able to then patch the boot.img and flash it normally.

razercortex said:
Try using the MSM tool for your device, press F8, then select boot_a or boot_b depending on what slot you're in. To check your slot, reboot to fastboot and issue the command fastboot getvar current-slot.
You should be able to then patch the boot.img and flash it normally.
Click to expand...
Click to collapse
Getting this phone to actually boot into MSM mode is a nightmare. I either end up in fastboot or it boots up normally. I got it to show up exactly once, but it timed out and booted up before I got the readback going.

rustyshakelford2 said:
Getting this phone to actually boot into MSM mode is a nightmare. I either end up in fastboot or it boots up normally. I got it to show up exactly once, but it timed out and booted up before I got the readback going.
Click to expand...
Click to collapse
Enable USB debugging in settings, then type adb reboot edl.

razercortex said:
Enable USB debugging in settings, then type adb reboot edl.
Click to expand...
Click to collapse
I got it! I managed to readback boot_b using the password "oneplus". I can't seem to find where it saved the file though.

It's in C:\ aka your root drive

razercortex said:
Try using the MSM tool for your device, press F8, then select boot_a or boot_b depending on what slot you're in. To check your slot, reboot to fastboot and issue the command fastboot getvar current-slot.
You should be able to then patch the boot.img and flash it normally.
Click to expand...
Click to collapse
That's a cool trick. I didn't know about that one.

Successfully rooted! Huge thanks to razercortex and others in this thread who helped.
Here is a download of both the unmodified and magisk patched boot.img for e2125_11_c.61 global.
https://www.dropbox.com/s/bpoe31lt022rigj/e2125_11_c.61%20global%20boot.img.zip?dl=1
I booted the patched image via fastboot and then did a magisk direct install. After updating the safetynet fix module and running props I am passing safeteynet. I had to restore props to defaults and then apply the android 11 fingerprint for this phone, otherwise it would fail CTS.

rustyshakelford2 said:
Successfully rooted! Huge thanks to razercortex and others in this thread who helped.
Here is a download of both the unmodified and magisk patched boot.img for e2125_11_c.61 global.
https://www.dropbox.com/s/bpoe31lt022rigj/e2125_11_c.61%20global%20boot.img.zip?dl=1
I booted the patched image via fastboot and then did a magisk direct install. After updating the safetynet fix module and running props I am passing safeteynet. I had to restore props to defaults and then apply the android 11 fingerprint for this phone, otherwise it would fail CTS.
Click to expand...
Click to collapse
Can you please share the steps to get the boot.img
I have to get it from LE2121

gulshanstrider said:
Can you please share the steps to get the boot.img
I have to get it from LE2121
Click to expand...
Click to collapse
You should be able to just boot (don't flash) the 2125 rooted image they posted and then use Magisk to direct install.

EtherealRemnant said:
You should be able to just boot (don't flash) the 2125 rooted image they posted and then use Magisk to direct install.
Click to expand...
Click to collapse
I have an LE2125 on 11_C.61 and when I fastboot the posted patched boot.img file I get Magisk Installed: N/A in Magisk Manager. I even patched the posted boot.img myself in Magisk and get Magisk Installed: N/A when fastbooting that patched boot.img. Any ideas?

TornSack said:
I have an LE2125 on 11_C.61 and when I fastboot the posted patched boot.img file I get Magisk Installed: N/A in Magisk Manager. I even patched the posted boot.img myself in Magisk and get Magisk Installed: N/A when fastbooting that patched boot.img. Any ideas?
Click to expand...
Click to collapse
Did you go to try to direct install? I haven't actually tried C.61 yet, I've got stuff to do this weekend and can't have my phone in an experimental state when I'm trying to call and Uber to get around, so I can't test it myself.