Related
So, when I updated from OOS 9 to 10 I forgot to remove magisk and it's modules and completely forgot about it.
When I finished the update I noticed all the emojis where gone and from other posts here I found that it was because of a problem with the reserve partition that could be solved flashing a magisk module. Well, to my surprise, when I tried flashing magisk again on OOS 10 I always got stuck on a bootloop, I tried everything, removing the old modules that where still installed, using different twrp versions, using bluspark kernel, flashing a patched img through adb... But I always got a bootlop after installing magisk.
Since I couldn't get magisk on and was getting frustrated I decided to wait for the next OTA to see if it might fix it, but now that I tried installing it, I get stuck at 89% installation and don't know what to do. It's probably because of the reserve partition where the emoji should be, but since I can't use magisk idk how to fix it.
Is there another way to fix the reserve partition? Maybe a patch through twrp? Will a clean install of some sort help me or will it also get stuck at installation and brick my device?
Any help is welcome!
EDIT: Since noone replied I tried to fix it myself by trying to flash magisk a couple of times again (which gave me bootlops as expected), so I ended up flashing an OOS 5.1 downgrade build (which factory resets your phone so back up your stuff) and updating all the way to 10.3.1 through OTA updates. This fixed both my emoji and stuck update problem, so If you have similar problems and have not had any luck with other solutions I suggest you to downgrade like I did. If you back everything up on the cloud you should be back up and running in under an hour.
How did you flash the downgrade rom since your system updater is stuck?
Go twrp recovery, look for .Ota, flash the downloaded update zip and reboot.(Must be patient for step 2 to complete)
If can't find .Ota, go to File manager app, click storage below, click 3 dot on top right coner, settings, turn Show hidden file switch on
[UPDATE/KEEP ROOT GUIDE] OCT 2020 (RP1A.201005.004) "CORAL" Magisk/Stock Boot Images
PLEASE NOTE: I STILL HAVE NOT UPDATED TO ANDROID 11 YET, SO PLEASE FLASH AT YOUR OWN RISK AS ASSISTANCE FROM ME WILL BE VERY LIMITED. PLEASE BE KIND TO ONE ANOTHER AND HELP EACH OTHER OUT! AND SORRY FOR THE LATE POST. JUST GOT BACK FROM A LONG WEDDING WEEKEND, AND THE 8-HOUR DRIVE (EACH WAY) WITH A 9 MONTH OLD BABY WAS... QUITE AN ADVENTURE.
PLEASE DROP A THANKS IF YOU STILL FIND THESE GUIDES HELPFUL! :good:
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
ALL FILES BELOW ARE FOR "RP1A.201005.004, Oct 2020"!
Magisk Canary v21.0 Patched Boot Image: https://www.androidfilehost.com/?fid=10763459528675557936
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=10763459528675557937
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=10763459528675557938
[SAFETYNET INFO]: Again, I'm not updating myself yet, so I'm not sure about this. I will update this info as others report back. On Android 10, using the MagiskHide Props Config module (or an alternate module created by Displax, though I prefer Didgeridoohan's module) and choosing option 2 - Force BASIC key attestation would force BASIC HW attestation and allow SafetyNet to pass again. This works perfectly for me, and I even run additional mods including EdXposed. I'm not sure if this works on Android 11, and I won't be able to confirm myself for a while. If anybody tries it, please let me know and I'll update this section. The module and info on using it can be found here: https://forum.xda-developers.com/ap...just search for it in the Magisk Manager app.
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RP1A.200720.009, Sep 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rp1a.200720.009-factory-dtbo.img: https://www.androidfilehost.com/?fid=8889791610682933260
coral-rp1a.200720.009-factory-boot.img: https://www.androidfilehost.com/?fid=8889791610682933258
October 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rp1a.201005.004-5e85d0f7.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-rp1a.200720.009-factory-boot.img
3. fastboot flash dtbo coral-rp1a.200720.009-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rp1a.201005.004-5e85d0f7.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rp1a.201005.004-magisk_patched-21.0.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
I just want to reemphasize once again - I have not yet updated to Android 11, so I haven't been able to personally test any of these newer builds. Any feedback would be appreciated. And of course, be kind to one another and help each other out if you have any issues!
Finally, I need to mention again that the Magisk v21.0 boot image I created for the Oct. 2020 build came out to 64mb (and not the usual 30~something mb), which makes me feel a little wary. I would really appreciate feedback if my pre-patched boot image works. (edit: I just tested with patching my current Aug. 2020 boot image with Magisk v21.0 and it also came out to 64mb and successfully flashed perfectly fine, so hopefully my pre-patched Oct. 2020 image should also be fine.)
Thanks!
i5lee8bit said:
I just want to reemphasize once again - I have not yet updated to Android 11, so I haven't been able to personally test any of these newer builds. Any feedback would be appreciated. And of course, be kind to one another and help each other out if you have any issues!
Finally, I need to mention again that the Magisk v21.0 boot image I created for the Oct. 2020 build came out to 64mb (and not the usual 30~something mb), which makes me feel a little wary. I would really appreciate feedback if my pre-patched boot image works. (edit: I just tested with patching my current Aug. 2020 boot image with Magisk v21.0 and it also came out to 64mb and successfully flashed perfectly fine, so hopefully my pre-patched Oct. 2020 image should also be fine.)
Thanks!
Click to expand...
Click to collapse
It is safe to update to Android 11 and do a clean install by wiping data (so keep the "-w" in the flash-all.bat file), let the phone reboot into Android 11, setup phone and let it install your previous apps, etc.
Afterwards, install MM 8.01, change settings to beta build, patch boot image AND REBOOT THE PHONE. After rebooting, copy the magisk_patched image file to your adb (it should be 64 MB in size) folder. Proceed with using flashing the patched boot image.
I just updated to October's factory image a few minutes ago and success.
bb709394 said:
It is safe to update to Android 11 and do a clean install by wiping data (so keep the "-w" in the flash-all.bat file), let the phone reboot into Android 11, setup phone and let it install your previous apps, etc.
Afterwards, install MM 8.01, change settings to beta build, patch boot image AND REBOOT THE PHONE. After rebooting, copy the magisk_patched image file to your adb (it should be 64 MB in size) folder. Proceed with using flashing the patched boot image.
I just updated to October's factory image a few minutes ago and success.
Click to expand...
Click to collapse
I'm actually holding off because I'm waiting for a few mods to be compatible with 11, particularly GravityBox. Also, the purpose of my guides are to update without the need to wipe data / flash full clean factory image / seamlessly update with absolutely no additional setup. I know people say it's not so bad these days to set up from scratch, but for me it's still definitely a "ain't nobody got time fo dat" situation. =)
Thanks anyway though.
i5lee8bit said:
I just want to reemphasize once again - I have not yet updated to Android 11, so I haven't been able to personally test any of these newer builds. Any feedback would be appreciated. And of course, be kind to one another and help each other out if you have any issues!
Finally, I need to mention again that the Magisk v21.0 boot image I created for the Oct. 2020 build came out to 64mb (and not the usual 30~something mb), which makes me feel a little wary. I would really appreciate feedback if my pre-patched boot image works. (edit: I just tested with patching my current Aug. 2020 boot image with Magisk v21.0 and it also came out to 64mb and successfully flashed perfectly fine, so hopefully my pre-patched Oct. 2020 image should also be fine.)
Thanks!
Click to expand...
Click to collapse
I didn't use your file. What I do is download the full firmware, remove -w and flash, then boot into TWRP and flash the Magisk zip. For some reason this October Update, it wouldn't decrypt my data when booting into TWRP so I patched the boot.img myself. I wanted to let you know that mine also came out to 64mb and after I flashed it to the boot partition, it worked perfectly. So I can "sorta" confirm that it should work.
i5lee8bit said:
I'm actually holding off because I'm waiting for a few mods to be compatible with 11, particularly GravityBox. Also, the purpose of my guides are to update without the need to wipe data / flash full clean factory image / seamlessly update with absolutely no additional setup. I know people say it's not so bad these days to set up from scratch, but for me it's still definitely a "ain't nobody got time fo dat" situation. =)
Thanks anyway though.
Click to expand...
Click to collapse
Seamless update is worth so much. Setting up a phone when its your daily driver is just so much work. No banking pin app will work, you have to set up messangers again, alot of apps will barely work (even with backup services like swift backup or titan) and some apps can't even be backuped at all and will create errors when loading backups.
@i5lee8bit, I just followed your tutorial to successfully upgrade the October patch with the files you provided. Everything is okay. Thanks a lot for your enthusiastic sharing.
WorldOfJohnboy said:
I didn't use your file. What I do is download the full firmware, remove -w and flash, then boot into TWRP and flash the Magisk zip. For some reason this October Update, it wouldn't decrypt my data when booting into TWRP so I patched the boot.img myself. I wanted to let you know that mine also came out to 64mb and after I flashed it to the boot partition, it worked perfectly. So I can "sorta" confirm that it should work.
Click to expand...
Click to collapse
I still haven't bothered with TWRP since the HTC U12+ days, and I actually found that I prefer it that way. Pretty sure TWRP needs to be updated for each (or at least most) monthly update btw. But thanks for the info, looks like 64mb is now the normal way Magisk outputs the patched boot image.
Morgrain said:
Seamless update is worth so much. Setting up a phone when its your daily driver is just so much work. No banking pin app will work, you have to set up messangers again, alot of apps will barely work (even with backup services like swift backup or titan) and some apps can't even be backuped at all and will create errors when loading backups.
Click to expand...
Click to collapse
Yeah, I only backup/restore certain apps (data or apps not on app store) when switching phones because there are always those little glitchy problems and what not if relying on TiBu / Swift too much. I'll use the built in backup/restore for certain apps (like Nova), but other than that when doing a clean install, while Android has better built in features to make it easier to migrate compared to a few years ago, it is still a major PITA.
blue2018 said:
@i5lee8bit, I just followed your tutorial to successfully upgrade the October patch with the files you provided. Everything is okay. Thanks a lot for your enthusiastic sharing.
Click to expand...
Click to collapse
Thanks for the info! Just updated the OP so there isn't a huge scary caution, lol. I figured it would be fine when I tested with August patched with v21.0 and still came out to 64mb, but thanks for the confirmation.
Silly Question Maybe
guys its been a while so pls have patience with my ignorance. I have Xfinity Pixel 4xl and need to use it on T-mobile. Under Developer options,. OEM Unlocking is greyed out and it does not allow me to modify. Am i screwed ?
I tried updating and I can't figure out why it is not working...
Upon boot, I am still on Sept patch with root.
Then eventually it tells me that an update is available to be installed and to reboot to finish.
When I reboot, it says that there was an error.
Magisk no longer has "install after OTA" option. Anyone have any ideas?
xclaim494 said:
guys its been a while so pls have patience with my ignorance. I have Xfinity Pixel 4xl and need to use it on T-mobile. Under Developer options,. OEM Unlocking is greyed out and it does not allow me to modify. Am i screwed ?
Click to expand...
Click to collapse
Sorry about the late response, but maybe this info might help (it's a post I made on slickdeals.net regarding b/l unlocking the P4 series): https://slickdeals.net/f/14385296-x...e-399-free-shipping?p=140865899#post140865899
Also important to note, there is a difference between SIM unlocking (so you can use with T-Mobile) and oem/BL unlocking (so you can modify / root the phone).
tl;dr on my slickdeals post: SIM unlock status controls the oem (bootloader) unlock toggle status. Verizon is known to be the only variant where they fully prevent BL unlocking. XMo is an MVNO off of Verizon. Nobody has reported yet whether it can be done on XMo variants even after SIM unlocking. So you might be screwed.
smithilberry said:
I tried updating and I can't figure out why it is not working...
Upon boot, I am still on Sept patch with root.
Then eventually it tells me that an update is available to be installed and to reboot to finish.
When I reboot, it says that there was an error.
Magisk no longer has "install after OTA" option. Anyone have any ideas?
Click to expand...
Click to collapse
Did you follow the OP / 2nd post exactly? And made sure you're sideloading the correct, Oct 2020 ota zip? Should work fine with the given instructions and links. Make sure you downloaded (or just redownload) all the correct files.
Tbh it sounds like you're just reinstalling the Sept update and boot files.
The November update is out. Anyone here already got the new files?
Morgrain said:
The November update is out. Anyone here already got the new files?
Click to expand...
Click to collapse
I do... not sure if there's a separate thread as this is for the October update.
Side note, I apparently can no longer BOOT to TWRP to flash the Magisk Zip as even the TWRP Coral Beta doesn't decrypt Android 11. So, looks like I'm stuck manually patching the Boot and flashing via bootloader.
All of the similar threads just end after a few replies (I think because people didn't have unlocked bootloaders) so I thought I'd try to ask again. I have a T-Mo OP8 (IN2017) on 10.5.22IN55CB. I already have the bootloader unlocked. But all of the root methods I can find need a payload.bin from the stock firmware, and I can't seem to find that. Is there another method or a source for branded firmware? I wasn't sure if I could do it by just booting the TWRP found on this board without flashing the recovery.
TIA.
SilverZero said:
All of the similar threads just end after a few replies (I think because people didn't have unlocked bootloaders) so I thought I'd try to ask again. I have a T-Mo OP8 (IN2017) on 10.5.22IN55CB. I already have the bootloader unlocked. But all of the root methods I can find need a payload.bin from the stock firmware, and I can't seem to find that. Is there another method or a source for branded firmware? I wasn't sure if I could do it by just booting the TWRP found on this board without flashing the recovery.
TIA.
Click to expand...
Click to collapse
I booted into TWRP and took a backup of the device. I then transferred the backup to my local PC and took the boot file from the backup, renaming the extension to .img. I then put this boot image on my device and downloaded magisk manager and set magisk manager to install magisk by patching a file. Once completed, I downloaded the patched file to my PC and booted to fastboot. While in fastboot, I flashed the magisk_patched boot image to both boot slots (boot_a, and boot_b). Upon rebooting, I had root. One thing, as soon as you have root, I recommend taking an image of your persist file (for fingerprint) to prevent any issues if the persist partition gets corrupted on your device. Search the forum for instructions on how to do this.
Cheers,
B.D.
You literally don't have to do anything special. Boot TWRP, flash Magisk zip in TWRP, reboot. Done.
stompysan said:
You literally don't have to do anything special. Boot TWRP, flash Magisk zip in TWRP, reboot. Done.
Click to expand...
Click to collapse
Works great. Thanks!
BostonDan said:
I booted into TWRP and took a backup of the device. I then transferred the backup to my local PC and took the boot file from the backup, renaming the extension to .img. I then put this boot image on my device and downloaded magisk manager and set magisk manager to install magisk by patching a file. Once completed, I downloaded the patched file to my PC and booted to fastboot. While in fastboot, I flashed the magisk_patched boot image to both boot slots (boot_a, and boot_b). Upon rebooting, I had root. One thing, as soon as you have root, I recommend taking an image of your persist file (for fingerprint) to prevent any issues if the persist partition gets corrupted on your device. Search the forum for instructions on how to do this.
Cheers,
B.D.
Click to expand...
Click to collapse
Post below yours worked for me but I appreciate the advice on backups and what to watch for. I haven't installed TWRP yet, just booted it and installed.
SilverZero said:
Works great. Thanks!
Click to expand...
Click to collapse
I should state one thing that I didn't in my original post. Booting TWRP and flashing that way ONLY works if you are still running Android 10. Since you have a T-Mobile variant, I knew this was a non-issue (we STILL don't have official A11). For those running Android 11, you do have to patch the boot image and flash it like stated above. Also note that this will likely change if we get TWRP on A11. Once we have that working, flashing Magisk from it should work fine.
stompysan said:
I should state one thing that I didn't in my original post. Booting TWRP and flashing that way ONLY works if you are still running Android 10. Since you have a T-Mobile variant, I knew this was a non-issue (we STILL don't have official A11). For those running Android 11, you do have to patch the boot image and flash it like stated above. Also note that this will likely change if we get TWRP on A11. Once we have that working, flashing Magisk from it should work fine.
Click to expand...
Click to collapse
Following up on this just in case you know anything new. My IN2017 just updated to A11 without any action on my part, and I lost root. Is there a TWRP or patched boot img that you know of for us on TMo now?
There is no working twrp for us on Android 11. I also haven't seen a patched boot image of 11.0.1.3.IN55CB around yet. I have that firmware extracted on my laptop so I could grab the boot image and patch it for you, but I won't be able to do that until later tomorrow. If no one else has it out or if you don't find it before I can get to it, I'll post it up.
Edit: Here's the patched boot image: Magisk Patched Boot IMG TMO 11.0.1.3
Hey,
Yesterday i received the official global version of Ogygen OS 11 (OnePlus7Oxygen_14.E.35_OTA_0350_all_2103221233) for my Oneplus 7 which made me happy and i installed it on my current TWRP and root Ogygen OS 10. Afterwards my root and TWRP was gone. I read many threads now about that TWRP is not available currently for Android 11. So i was stuck with extracting the boot.img from the stock zip file and patching it with the latest canary Magisk (66e30a77 (22006)). The patch is successful.
After i flashed the boot.img to boot_a and boot_b via fastboot the phone restarted but there was still no root. (Magisk still showed that its not installed and superuser rights for Magisk also weren't granted->notification during start).
After trying and validating that i used the latest version of everything and also did a factory reset and tried the same handling again, i tried to use the latest beta Oxygen OS11 stock image for flashing the boot.img (same handling as before). After flashing i gained superuser rights and magisk was installed but no bluetooth and WIFI was working so there was an issue (is clear because it was not the same stock zip).
So does anyone of you might have already an solution for this?
Rgds,
Matthias
matthi383 said:
Hey,
Yesterday i received the official global version of Ogygen OS 11 (OnePlus7Oxygen_14.E.35_OTA_0350_all_2103221233) for my Oneplus 7 which made me happy and i installed it on my current TWRP and root Ogygen OS 10. Afterwards my root and TWRP was gone. I read many threads now about that TWRP is not available currently for Android 11. So i was stuck with extracting the boot.img from the stock zip file and patching it with the latest canary Magisk (66e30a77 (22006)). The patch is successful.
After i flashed the boot.img to boot_a and boot_b via fastboot the phone restarted but there was still no root. (Magisk still showed that its not installed and superuser rights for Magisk also weren't granted->notification during start).
After trying and validating that i used the latest version of everything and also did a factory reset and tried the same handling again, i tried to use the latest beta Oxygen OS11 stock image for flashing the boot.img (same handling as before). After flashing i gained superuser rights and magisk was installed but no bluetooth and WIFI was working so there was an issue (is clear because it was not the same stock zip).
So does anyone of you might have already an solution for this?
Rgds,
Matthias
Click to expand...
Click to collapse
Hello,
Did you see this thread right below yours?
Android 11 OB4
Just installed OB4, anybody got a boot.img file or magisk patched boot image file? Also any news on TWRP for Android 11? Thanks in anticipation OK I was just lazy hoping somebody Elese did the work. Ended up using my OB2 patched boot image file...
forum.xda-developers.com
Magisk canary can also cause a lot of issues. I'm using 22.0.
Hey thank you! I already saw this and tried it out before to get TWRP working as in the Oxygen OS 11 Beta but this TWRP version does not work with the official OOS11 for the Oneplus 7. It's strange that on Open Beta it works and now its not working.
Watching this thread because I'm stuck too. I either need locked bootloader or unlocked with Magisk
Does anyone already has a solution to this one?
I got the OTA today for 11.0.0.2, rooted fine with Magisk 22.1. Check out my guide:
https://forum.xda-developers.com/t/...m1900-android-11-oos-stable-11-0-0-2.4253743/
WareDat said:
I got the OTA today for 11.0.0.2, rooted fine with Magisk 22.1. Check out my guide:
https://forum.xda-developers.com/t/...m1900-android-11-oos-stable-11-0-0-2.4253743/
Click to expand...
Click to collapse
I wish someone would upload the fastboot ROM
Thank you man it worked ! i hope others are seeing also your intructions and files so they can use them and have root back again
Hi all,
I tried to root my new oneplus 8t but stupidly enough i downloaded and used a wrong stock boot image (i need EU but used global).
Now my phone is stuck in bootloop, can someone assist please?
Or maybe someone can share with me a working patched file for EU (as i can't do that as my phone is not responsive anymore).
I tried to do so with magisk app.
Thanks in advance!
saharb14 said:
Hi all,
I tried to root my new oneplus 8t but stupidly enough i downloaded and used a wrong stock boot image (i need EU but used global).
Now my phone is stuck in bootloop, can someone assist please?
Or maybe someone can share with me a working patched file for EU (as i can't do that as my phone is not responsive anymore).
I tried to do so with magisk app.
Thanks in advance!
Click to expand...
Click to collapse
full flash is the only way
Refer this thread
sabeehp said:
full flash is the only way
Refer this thread
Click to expand...
Click to collapse
Thanks, but MSM doesn't recognize my phone, is there a way to make it work and recognize my phone?
saharb14 said:
Hi all,
I tried to root my new oneplus 8t but stupidly enough i downloaded and used a wrong stock boot image (i need EU but used global).
Now my phone is stuck in bootloop, can someone assist please?
Or maybe someone can share with me a working patched file for EU (as i can't do that as my phone is not responsive anymore).
I tried to do so with magisk app.
Thanks in advance!
Click to expand...
Click to collapse
Have your tried flashing the correct boot image? If all you did was flash the incorrect boot image then that should fix the problem.
BillGoss said:
Have your tried flashing the correct boot image? If all you did was flash the incorrect boot image then that should fix the problem.
Click to expand...
Click to collapse
In order to flash the correct one, i need to transfer it to the device and use magisk.
The problem is that the device stuck in boot loop so i can't do that.
That's why i asked if someone has already patched Europe version to share with me or any other option for me to fix it
Here is a collection of stock boot images (if you don't trust them, just extract it using a payload dumper from the ota zip that can be found in other threads)
OnePlus 8T Stock Boot Image Collection and Installation Guide
Download the stock boot image of all OxygenOS versions for the OnePlus 8T. Also learn how to flash a boot image on OnePlus 8T using Fastboot and TWRP.
www.thecustomdroid.com
Either flash or just boot the stock image in flashboot.
Copy stock image to phone and patch with magisk
Copy patched stock image to PC
Flash patched boot image in fastboot
saharb14 said:
Thanks, but MSM doesn't recognize my phone, is there a way to make it work and recognize my phone?
Click to expand...
Click to collapse
press volume down+volume up button then connect it to pc. it will detect as qualcomm qd loader (u need qualcomm driver)
saharb14 said:
Thanks, but MSM doesn't recognize my phone, is there a way to make it work and recognize my phone?
Click to expand...
Click to collapse
The thread referenced previously is the solution.
There is no other tool or method that will resolve your issue.
If you follow the instructions correctly it will work.
If you are confused on the instruction I suggest searching youtube and you will find many videos that will walk you through the process.