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.
Related
So i was running Android 10 Nov update rooted WITHOUT TWRP
And i wanted to update to Dec update
So i DLed DEC update factory image took out the -w booted my phone into the bootloader flash-all
It does its thing phone boots up obvi now i dont have root.
I put the bootloader.img onto my phone go into Magisk manager and modify the bootloader then bring it back to the computer.
Boot the phone into bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
phone gets stuck in the G logo with the loading bar
any hints????
after doing some researched i tried it again but this time flashing the patched boot.img to both a and b slots. Still same result
krolla03 said:
So i was running Android 10 Nov update rooted WITHOUT TWRP
And i wanted to update to Dec update
So i DLed DEC update factory image took out the -w booted my phone into the bootloader flash-all
It does its thing phone boots up obvi now i dont have root.
I put the bootloader.img onto my phone go into Magisk manager and modify the bootloader then bring it back to the computer.
Boot the phone into bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
phone gets stuck in the G logo with the loading bar
any hints????
Click to expand...
Click to collapse
krolla03 said:
after doing some researched i tried it again but this time flashing the patched boot.img to both a and b slots. Still same result
Click to expand...
Click to collapse
You stated that you patched the bootloader.img, is that correct?? You need to patch the boot.img, or, was that just a typo on your part?
Did you disable all your magisk modules before you fastbooted the factory image?? If not, then it's very likely that one, or maybe more modules, isn't compatible with the December update. I'll wait for your reply before trying to help solve the problem.
I previously dealt with similar symptoms. You can read about it here -- https://forum.xda-developers.com/showpost.php?p=81102855&postcount=33
Badger50 said:
You stated that you patched the bootloader.img, is that correct?? You need to patch the boot.img, or, was that just a typo on your part?
Did you disable all your magisk modules before you fastbooted the factory image?? If not, then it's very likely that one, or maybe more modules, isn't compatible with the December update. I'll wait for your reply before trying to help solve the problem.
Click to expand...
Click to collapse
OK so stupid me yes i was patching and flashing the bootloader.img not the boot.img.
I just tried flashing the indeed patched boot.img and now im getting the same issue as rustnails. Where it gets stuck at the G logo for a few secs and reboots.
I did not uninstall or disable any of the magisk modulus
how do i do that now that i dont have root?
krolla03 said:
OK so stupid me yes i was patching and flashing the bootloader.img not the boot.img.
I just tried flashing the indeed patched boot.img and now im getting the same issue as rustnails. Where it gets stuck at the G logo for a few secs and reboots.
I did not uninstall or disable any of the magisk modulus
how do i do that now that i dont have root?
Click to expand...
Click to collapse
Fastboot into twrp. Go to advanced, select file manager, go to /data/adb/modules then delete each one of them. Reboot, then go back and fastboot your patched boot.img to regain root :good:
Badger50 said:
Fastboot into twrp. Go to advanced, select file manager, go to /data/adb/modules then delete each one of them. Reboot, then go back and fastboot your patched boot.img to regain root :good:
Click to expand...
Click to collapse
Ok. Before i try that let me just ask this.
Can i just temp boot TWRP to do that
I dont want to install TWRP permanently because ive had mostly trouble with TWRP in the last few android versions.
krolla03 said:
Ok. Before i try that let me just ask this.
Can i just temp boot TWRP to do that
I dont want to install TWRP permanently because ive had mostly trouble with TWRP in the last few android versions.
Click to expand...
Click to collapse
Yep. It'll just be temporary :good:
Badger50 said:
Yep. It'll just be temporary :good:
Click to expand...
Click to collapse
Thanks man. I got it all working again!!!
Hi badger, @Badger50 (Mod Edit: added mention tag)
i have an issue with rooting my device
when I write fastboot flash boot magisk_patched.img I get a message says < waiting for device >
can you please help me to find a solution to my problem?
dark_heroo said:
Hi badger, @Badger50 (Mod Edit: added mention tag)
i have an issue with rooting my device
when I write fastboot flash boot magisk_patched.img I get a message says < waiting for device >
can you please help me to find a solution to my problem?
Click to expand...
Click to collapse
Not sure what your starting point is but:
After installing you fastboot factory image
you can either temporarily or permanently install TWRP (temp TWRP= fastboot twrp.img, install magisk, reboot OR perm TWRP = fastboot twrp.img, install TWRP.zip from witin TWRP)
then you just flash/install magisk in TWRP
In my sig is a link to a detailed step by step guide for all this.
Good luck!
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?
While there is no link for incremental nor full ota, here comes the Batman.
Google Drive with all stuff
Google Drive link
Spoiler: How to flash kernel?
enter fastboot mode
check if exact boot image you downloaded works for you using fastboot boot command (also check if mac adress shows up)
Now you can choose between 2 different installation routes
First routeSecond route
install magisk canary and open it
reboot back to fastboot
install → direct install
fastboot flash boot_a <filename>.img
and then flash to the second slot
fastboot flash boot_b <filename>.img
after installation is done — reboot
fastboot reboot
Spoiler: How to flash recovery?
enter fastboot mode
fastboot flash recovery_a <filename>.img
fastboot flash recovery_b <filename>.img
fastboot reboot recovery
Well done. You are great.
Cheers!
You sure this is for 11.0.2.2.IN11AA?
Because it looks like 11.0.1.1.IN11AA to me, unless I'm doing something wrong (I am new to this).
Cheers
EDIT: Dw, I'm stupid
I had lost root since updating so was looking for a stock boot image for 11.0.2.2 to patch in order to once again restore root by the fastboot method. (It is generally recommended that you patch your own stock boot image.) So, I downloaded your stock boot image which was 98 MB. In the past, stock boot images for the OnePlus 8 Pro have been 16 to 17 MB, so I am wondering if the 98 MB file labeled as stock is actually a stock boot image. Also, both files are exactly the same size so I'm guessing that they are both patched boot images.
vettean said:
I had lost root since updating so was looking for a stock boot image for 11.0.2.2 to patch in order to once again restore root by the fastboot method. (It is generally recommended that you patch your own stock boot image.) So, I downloaded your stock boot image which was 98 MB. In the past, stock boot images for the OnePlus 8 Pro have been 16 to 17 MB, so I am wondering if the 98 MB file labeled as stock is actually a stock boot image. Also, both files are exactly the same size so I'm guessing that they are both patched boot images.
Click to expand...
Click to collapse
To be precise, its boot partition. Yes, boot may size 16mb but partition - not.
And so that's why you you can't say by size which file have patched boot.
more_than_hater said:
To be precise, its boot partition. Yes, boot may size 16mb but partition - not.
And so that's why you you can't say by size which file have patched boot.
Click to expand...
Click to collapse
Thanks for the clarification. After the past couple of updates, in order to get root back I used the Magisk Manager to patch a stock boot image that I found online which was about 16 MB and then installed via fastboot on my PC. Using your 98 MB stock boot image, would I perform the operation the same way by downloading it to my phone and patching it with Magisk Manager before use fastboot?
vettean said:
Thanks for the clarification. After the past couple of updates, in order to get root back I used the Magisk Manager to patch a stock boot image that I found online which was about 16 MB and then installed via fastboot on my PC. Using your 98 MB stock boot image, would I perform the operation the same way by downloading it to my phone and patching it with Magisk Manager before use fastboot?
Click to expand...
Click to collapse
Yes, magisk manager can patch both boot and "boot-in-partition"
more_than_hater said:
While there is no link for incremental nor full ota, here comes the Batman.
Stable stock&patched boot.img
Google Drive link
How to use?
enter fastboot mode
check if exact boot image you downloaded works for you using fastboot boot command (also check if mac adress shows up)
install magisk canary apk and open it
use direct install method
reboot
fin. you are great.
P.S.
I don't recommend to directly flash patched boot.img to boot_a and boot_b partitions, because smth could go wrong. It mostly works for 99,9% times, but it's better to use magisk direct install method.
Click to expand...
Click to collapse
Do you have the link for the 11.0.2.2AA full ota?
Where is the full OTA Update for this??
someone in a different OP8P thread posted this:
OnePlus 8/8 Pro OxygenOS OTA Updates: Download & Installation (Latest: OxygenOS 13 F.15)
Download all OxygenOS OTA software updates for OnePlus 8 and OnePlus 8 Pro, and learn how to manually install them. Latest: OxygenOS 13 F.15 (Android 13) update
www.thecustomdroid.com
more_than_hater said:
While there is no link for incremental nor full ota, here comes the Batman.
Stable stock&patched boot.img
Google Drive link
How to use?
enter fastboot mode
check if exact boot image you downloaded works for you using fastboot boot command (also check if mac adress shows up)
install magisk canary apk and open it
use direct install method
reboot
fin. you are great.
P.S.
I don't recommend to directly flash patched boot.img to boot_a and boot_b partitions, because smth could go wrong. It mostly works for 99,9% times, but it's better to use magisk direct install method.
Click to expand...
Click to collapse
I don't understand how you can have the boot patched for OTA 11.0.2.2AA when the update itself hasn't been released yet !?
spaziomilano said:
I don't understand how you can have the boot patched for OTA 11.0.2.2AA when the update itself hasn't been released yet !?
Click to expand...
Click to collapse
But it has been and pulling a boot img from an install ROM is not that hard.
Link removed - was India version
Agimax said:
But it has been and pulling a boot img from an install ROM is not that hard.
https://otafsg1.h2os.com/patch/amazone2/GLO/OnePlus8ProOxygen/OnePlus8ProOxygen_15.I.32_GLO_0320_2011190124/OnePlus8ProOxygen_15.I.32_OTA_0320_all_2011190124_6f85dfcc1adc2bc.zip
Click to expand...
Click to collapse
So can I use what you sent me to update?
spaziomilano said:
So can I use what you sent me to update?
Click to expand...
Click to collapse
That's just the official OnePlus link to 11.0.2.2AA India full ROM. Up to you, can flash through updater if it's the version you wanted.
Agimax said:
That's just the official OnePlus link to 11.0.2.2AA full ROM. Up to you, can flash through updater if it's the version you wanted.
Click to expand...
Click to collapse
Really appreciate thanks
Agimax said:
That's just the official OnePlus link to 11.0.2.2AA full ROM. Up to you, can flash through updater if it's the version you wanted.
Click to expand...
Click to collapse
Just make the last update but it's DA version not AA...
spaziomilano said:
Just make the last update but it's DA version not AA...
Click to expand...
Click to collapse
Is it a big problem?
Deleted
spaziomilano said:
Is it a big problem?
Click to expand...
Click to collapse
My apologies, I stand corrected -this was the India version. You are right as the AA full ROM version is not yet available. I'll correct my original post.
Agimax said:
My apologies, I stand corrected -this was the India version. You are right as the AA full ROM version is not yet available. I'll correct my original post.
Click to expand...
Click to collapse
Lolll have make the update and now I'm on stable DA instead AA... All work good, I think is not a big problem
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
Hello all,
yesterday I've updated to latest OOS LE2123_11.C.44_1440_202201182111 (Android 12). I was previously on root, so I've updated the phone via full 4GB OTA through the system updater.
Everything was fine until I've tried to root by following these steps:
ATTENTION: if you're a Googler and willing to root the OPO 9 Pro, don't use the steps below, because they lead to a soft-bricked phone! (at least, for me)
Download the full OTA via Oxygen Updater
Extract the boot.img (192MB) via Payload Dumper (and I was confused, because the previous Android 11 boot.img was exactly the half in size)
Let the phone update itself
Throw the boot.img inside Magisk and create a patched boot.img
Flash the pathed boot image via fastboot with "fastboot flash boot Magisk_patched_blabla.img"
The phone was refusing to boot, as it was automatically booting in Fastboot mode.
So I've reflashed the patched IMG file, and the phone switched to Qualcomm Crashdump mode
Then, don't ask me how, I've managed to get it back to fastboot mode. Searched XDA for a clean and tested boot.img, understood that the boot contains 2 slots A/B, set the active boot slot to A, flashed the boot.img downloaded before, and the phone turned back to life.
So...what am I doing wrong? Maybe everything?
What are the correct steps to root the phone?
Thank you in advance
you don't have to flash the magisk_patched.img but instead boot it with : "fastboot boot magisk_patched.img"
Then you can install magisk by it's manager and reboot the phone.
Here is everything explained: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-0-0-0.4252373/
OS Update with install to inactive slot in magisk works too.
nicoilboss said:
you don't have to flash the magisk_patched.img but instead boot it with : "fastboot boot magisk_patched.img"
Then you can install magisk by it's manager and reboot the phone.
Here is everything explained: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-0-0-0.4252373/
Click to expand...
Click to collapse
I follow those steps I can get the boot and install alpha apk after it's install completed to reboot, phone gets bricked and stuck in fastboot.
Wait for the new Magisk, it's going to support Android 12.
https://twitter.com/topjohnwu/with_replies
djsubterrain said:
Wait for the new Magisk, it's going to support Android 12.
https://twitter.com/topjohnwu/with_replies
Click to expand...
Click to collapse
Missed this one...
How come some people is actually running on the rooted OOS C.44 EU? Are they using a particular version of a patched boot.img that's floating underground?
l_mike said:
OS Update with install to inactive slot in magisk works too.
Click to expand...
Click to collapse
I've clickbaited like a moron on the UPDATE/REBOOT button after OTA, and I've missed the opportunity to do it *before* rebooting the phone... then followed the steps I've posted and knocked out of the door...
xmff00 said:
Missed this one...
How come some people is actually running on the rooted OOS C.44 EU? Are they using a particular version of a patched boot.img that's floating underground?
Click to expand...
Click to collapse
Your post doesn't specify which version of magisk you're using, unless I overlooked it. If you're not using alpha already, use alpha. And make sure you also patch the boot.img with alpha and not a different version than you're trying to install. A couple of people have said canary works now (at least for C40), but I can't confirm whether it still works on C44. Stable doesn't work (yet).
terlynn4 said:
Your post doesn't specify which version of magisk you're using, unless I overlooked it. If you're not using alpha already, use alpha. And make sure you also patch the boot.img with alpha and not a different version than you're trying to install. A couple of people have said canary works now (at least for C40), but I can't confirm whether it still works on C44. Stable doesn't work (yet).
Click to expand...
Click to collapse
New stable V24 is released. Works great
nicoilboss said:
you don't have to flash the magisk_patched.img but instead boot it with : "fastboot boot magisk_patched.img"
Then you can install magisk by it's manager and reboot the phone.
Here is everything explained: https://forum.xda-developers.com/t/guide-magisk-unlock-root-keep-root-oos-12-0-0-0.4252373/
Click to expand...
Click to collapse
I've tried to use this method but when I try to flash using the 'fastboot boot magisk_boot.img' I get the error "failed - command boot not recognized"
ADB shows the 'sending' command but then nothing happens other than error mentioned above. I've tried to use both the patched and unpatched images but same error. No idea how to proceed from here