Hello all I'm having a problem with the OB2 and magisk. It seems to randomly work. The first time i tried to install it it would just get stuck in fastboot mode. And every time i try to install it in Magisk manager I get a unsupported/unknown image with both the official and canary builds. But two of the times I have tried it all worked using the same files i did before. But as soon as I reboot I'm stuck in fastboot mode again. Anybody know what could be causing this?
Did you do a Fresh install or Update from what?
You are Unrooted and it wont install itself via the app. you need to flash a patched boot image via fastboot.
I was just following the guide flashing in the app was just to test. It wouldn't flash in TWRP either which is what all the guides say to do. Thats when it just goes to fastboot mode. I am also coming from the OB1 which i did the exact same thing along with previous pie versions and worked with no problems. Even tried the All in one tool and does the same thing.
If TWRP is working then do a full wipe and install OB2 off a USB with an OTG cable. Flash OB2 and TWRP then reboot back into recovery and Flash Magisk 19.4
The same issue happen with me, i guess i will revert to Android 9
Follow this guide
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
null0seven said:
Follow this guide
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Click to expand...
Click to collapse
Yep followed it and diden't work. But now I have a bricked problem trrying to fix this. Stuck in bootloader/fastboot mode.
Try Fastboot rom by Mauronofrio. You need a working Fastboot
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
If it still not work MSM tool.
null0seven said:
Try Fastboot rom by Mauronofrio. You need a working Fastboot
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
If it still not work MSM tool.
Click to expand...
Click to collapse
OK got it fixed starting from scratch using the How to convert TMobile OP7 to International guide over again. Thanks for your help.
Anybody got ok Google working on the open beta 2
CptKlink said:
Hello all I'm having a problem with the OB2 and magisk. It seems to randomly work. The first time i tried to install it it would just get stuck in fastboot mode. And every time i try to install it in Magisk manager I get a unsupported/unknown image with both the official and canary builds. But two of the times I have tried it all worked using the same files i did before. But as soon as I reboot I'm stuck in fastboot mode again. Anybody know what could be causing this?
Click to expand...
Click to collapse
Did you disable magisk modules
Related
Hey, is there any change i can get my OP6 back working when I did these steps:
fastboot boot twrp.img
and then in twrp i flashed twrp to /boot which obviously wasnt a good idea. now im stuck in twrp bootloop
any ideas how to fix that?
Did you flash magisk zip afterwards? Ut could be the reason for the bootloops. Good luck.
Gr8man001 said:
Did you flash magisk zip afterwards? Ut could be the reason for the bootloops. Good luck.
Click to expand...
Click to collapse
No i didnt, im not even sure now that flashing twrp to boot is right :s
I tried this: https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
but it cant find my device, but thats probably an ADB issue because i can see it in recovery with my ADB version installed.
EDIT: i could resolve it with the restore tool from the linked thread. the problem was the tool wasnt working correctly and i had to reboot the phone (no idea why it wouldnt work the first boot into fastboot)
If you can get back into fastboot then this might work https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.
lgstylus2root said:
Hello fellow A2 Lite owners!
I just got this device today and would LOVE to root 10.0.7.0, However it seems like the only way to go through this is by using a patched boot image which is not viable because none have showed up for 10.0.7.0 yet.
Will there be any other solutions for this? Thank you.
Click to expand...
Click to collapse
I personally feel installing twrp offians twrp and flashing magisk is easyer
rob420p said:
I personally feel installing twrp offians twrp and flashing magisk is easyer
Click to expand...
Click to collapse
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.
lgstylus2root said:
Obviously, It is my preferred way since I used it on a couple of devices including my Redmi Note 4 and Mi Pad.
My concern is not OTA but whether it would somehow break the ROM
Yes, I am aware of Mi Flash, Flashing stock ROMS, and other techniques but it's just that i don't have time for such long endeavors and would like to have a safe-ish way.
However I will try to get twrp running temporarily to install magisk.
Click to expand...
Click to collapse
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.
rob420p said:
No it will not break the ROM I'm running the March update with twrp n magisk the only thing that does not work is backup n restore there is a new twrp 3.3.3.0 but I haven't installed it yet.
Click to expand...
Click to collapse
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Go to the pa ROM page and use that twrp that's offians twrp.the best guild ive seen n is type in customdriod mi a2 lite twrp and that page is the best in my opinion to follow I'll see if I can get a link for the page in a minute
Won't let me simend the link
rob420p,
Please provide links.
rob420p said:
Won't let me simend the link
Click to expand...
Click to collapse
Would you be capable of private messaging me the link?
I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.
lgstylus2root said:
I might have been able to find the link:
ww w.thecustom droid.com /install-twrp-recovery-root-xiaomi-mi-a2-a2-lite
Obviously remove all spaces.
Click to expand...
Click to collapse
I have followed this guide but it would always result in the installed version of TWRP not installing correctly, and the system mentioning "The System has been destroyed, Press power button to shut down"
How can i resolve this?
I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY
marstonpear said:
I just uploaded the boot and patched_boot imgs for 10.0.7.0 (March update) here are the links:
Stock boot.img : https://drive.google.com/open?id=17ukUahutrGCcx38ZXfzMaCCle71M_QuP
Patched boot.img with latest Magisk (07.04.2019 - I suggest patching the stock on your own to root the device) : https://drive.google.com/open?id=1RxFZcwi0utL3qGp9LKDMneBbggNMHmGY
Click to expand...
Click to collapse
I figured out how to do it either way, thank you for your efforts however!
lgstylus2root said:
I figured out how to do it either way, thank you for your efforts however!
Click to expand...
Click to collapse
You can add the links to the main thread so that people can see :good:
Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks
max-damage said:
Hi
Im trying to root V10.0.7.0.PDLMIXM Android on my A2 Lite with Magisk.
After fastboot boot patched_boot.img
Im getting bootloop, phone cannot boot (google lines endless loading).
After restart, goes well but no root.
Please help ! Thanks
Click to expand...
Click to collapse
Search before asking : https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.
max-damage said:
I did search and I followed procedure.
My phone fails to boot on step 10. when I load temporary patched boot.img over fastboot.
Thats my current problem.
I tried to load up downloaded pached boot.img for version V10.0.7.0.PDLMIXM
I also tried to make patched boot.img from original boot.img over phone via Magisk. It doesnt work, bootloop again.
Click to expand...
Click to collapse
I'm stuck with the same problem.
Booting with patched_boot.img (made on my own or downloaded from this forum) make the phone not starting, blocked on white screen.
Have you already solved?
lgstylus2root said:
How did you get TWRP to work? I am using the official image but whenever i boot into the .img, click cancel as instructed, and install the twrp zip, the result is that when i try to boot into recovery it says System has been destroyed (recovery only, normal boot is ok)
Click to expand...
Click to collapse
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....
Winchester316 said:
Only boot twrp not to Flash it...
Boot twrp command » fastboot boot twrp.img
Flash twrp command » fastboot flash recovery twrp.img
I assume you tried "flashing twrp" command, if that's the case it will replace your boot.img to twrp.img that's why it appears the "system has been destroyed" error... Try the "boot twrp command" if you want to access twrp temporarily... Coz right now we cant do(flash full twrp recovery) that as far as I know....
Click to expand...
Click to collapse
I believe we can I have heard reports offains 3.3.3. Twrp can do it I haven't tryed yet.but I did have twrp with root running on the march update but I'm on pa now
Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
Necessary Files:
Install OnePlus 6 Driver
Install Fastboot Drivers
TWRP Image
Magisk 20.1
twrp-3.3.1-x_blu_spark_v9.107_op6
Stock boot image thanks [URL="https://forum.xda-developers.com/member.php?u=6994095" @Akhil701[/URL]
Step 1: [dont do this if you have installed ADB and Fastboot already]
Install Oneplus 6, ADB and Fastboot Drivers from the link above
* Reboot PC after installing
Step 2:
Put
Code:
Stock Boot Image [boot.img]
twrp-3.3.1-x_blu_spark_v9.107_op6.zip and
Magisk-v20.1.zip
on your internal storage
Also Put
Code:
twrp-3.3.1-11-enchilada-Q-mauronofrio.img
on your desktop
Step 3: Reboot device in fastboot/bootloader mode
Step 4: Connect Device to PC Via USB Cable
Step 5: On your desktop Press Shift Right Click then click the [Open Command Prompt Here]
Step 6: on the CMD Windows Type
Code:
fastboot devices
Press enter and see if your device shows up.
Step 7: type in the CMD Window
Code:
fastboot flash boot twrp-3.3.1-11-enchilada-Q-mauronofrio.img
press enter then after that on your phone screen use volume up or down button to reboot to recovery
Step 8:
Once you have the TWRP Screen
flash the stock boot image [boot.img] in boot partition [DO NOT Reboot!]
now go back and flash the Blu_Spark TWRP and then reboot to recovery
Step 9: Rooting
Flash Magisk 20.1.zip then reboot to system.
Thats it! no data will be wiped as long as your bootloader is already unlocked.
thanks to
@Funk Wizard for the initial instruction on how to install twrp and root
@eng.stk for the Blu_Spark TWRP
@mauronofrio for the initial TWRP Image
@Akhil701 for the stock boot.img
@remewer for inspiration to build this guide.
Patched boot.img or why we need the boot image after flashing OOS10 via local update?
Sh0X31 said:
Patched boot.img or why we need the boot image after flashing OOS10 via local update?
Click to expand...
Click to collapse
im not sure about that also. im just hesitant to skip that step. it might break something. thats why i added that step on this guide
Thnx, this was a very easy walkthrough.
Only thing I want to say is that not everyone knows how to flash the 'boot.img' through TWRP. Maybe you can explain that in more detail.
no patched boot.img you need
1. connect your OP6 to PC
2. flash TWRP (from mauronofrio) by fastboot from PC
3. reboot from fastboot to recovery
4. in TWRP flash stock img OOS, don´t reboot
5. in TWRP flash TWRP (blu_spark 9.107)
6- reboot to TWRP to another slot
7. in TWRP flash Magisk 20.1
8. reboot to system
I have noticed this too, probably they have changed somehow the system, even fastboot boot doesn't work anymore....
I had to install magisk via boot.img patching
Functionally on OOS 10.0.1 OP6 ?
So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.
Brisky86 said:
So I was unable to flash the new OTA through twrp running on my rooted OP6.
As such, I opted to install the new OTA through the "local install" option.
That worked great. Settings area all the same. Bootloader still unlocked (I double checked).
Drivers are all installed on my Windows 10 PC.
However, no matter what I attempt to flash from command prompt I always get:
FAILED (remote: unkown command)
Does anyone know of a solution yet?
I have been reinstalling drivers and rebooting my PC with no luck thus far.
Any ideas?
Thanks in advance.
Update:
Whelp now that it is upgraded to Android 10 (and was wiped of all data when I locked and then unlocked the bootloader again) it will not allow me to downgrade back to Andriod 9 through the local upgrade option and since I can not get fastboot to accept any commands I am stuck now in Andriod 10 without the ability to change anything at the moment.
Click to expand...
Click to collapse
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand
magnamentis said:
i knew it while reading but thanks to the screenshot you provided you saved me from sounding "user error" once again and piss of so many who prefer to blame things and others LOL
in short, wrong command, it's fastboot flash boot <image name>
BTW and since i'm already at it, if anyone has a Mac runniing 10.15 "Catalina" and fastboot is working from terminal, i'd like to learn how he/she's done it
just came to my mind to ask here since i have to use windows 10 under parallels desktop to fastboot flash my android stuff at the moment and of course that's just an "Emergency" choice for me, everyone using both platforms will understand
Click to expand...
Click to collapse
Wow. Okay.
This is becoming a comedy of errors on my part.
Oh boy now I am getting Qualcom flashdump messages...
Huh now it is just booting normal but not letting me get into the new recovery flash...
I got it all fixed.
Thank you everyone for your help and patience with my posts.
Does 10.0.1 still have the ability to do screen-off gestures for music? I like 10 but on my wife's 7t, either she didn't turn them on, our it didn't have them so I'm curious if there same thing is happening with this? I also noticed on her 7t, constant data problems when's switching from WiFi to data. Sometimes data won't come back and only a reboot solves. I know it's a bug on OOS 10 on 7t but wondering if it's a device specific bug or an Android 10 bug? Anyone having op6 issues with data not coming back when switching from WiFi?
WIFI problem solved!
Below OOS 10.0.1 back inTWRP
Wipe: cache, system and vendor
Flash OOS 10
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Reboot recovery
Flash OOS 10.0.1
Flash boot img
Flash TWRP
Flash Magisk
Reboot system
Wifi works
After rooting 10.0.1 with magisk 20.1 mobile network is gone. no sim pin, no metwork. after unroot everything is fine
Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail
As above. No wifi, no sound. What's going on?
Coktail said:
Hello Mates,
i updated my rooted oneplus 6 from 10 to 10.01 and after that use this method to root again. But there is a Problem now: My WiFi doesnt work? I cant activate it.
Do anybody know how i can fix that Problem?
Thank you in Advance
Best Regards
Coktail
Click to expand...
Click to collapse
cubic25 said:
As above. No wifi, no sound. What's going on?
Click to expand...
Click to collapse
Look 2 posts up...
ryanallaire said:
Look 2 posts up...
Click to expand...
Click to collapse
Unroot doesn't work for me. Still no wifi and audio.
Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?
dynamode said:
Hi there just incase someone else who had problems [like me]
who is hesitant or looking for a guide on how to install Blu_Spark TWRP and Root the device.
The guide below will work 99.9% of the time. just follow the instructions carefully
@Funk Wizard for the initial instruction on how to install twrp and root
@eng.stk for the Blu_Spark TWRP
@mauronofrio for the initial TWRP Image
@Akhil701 for the stock boot.img
@remewer for inspiration to build this guide.
Click to expand...
Click to collapse
Hello.
I´m on 10.3.0 op6, I followed all the steps and when i finish the step 8 and reboot, i stuck on the recovery message. I repeat all the steps flashing clean rom and always have the same problem.....
Can someone help me? Because i don´t know another way for installing magisc....
Thanks!!!
loggstar said:
Hi guys, sorry to resurrect this thread. I did everything in the correct order using 10.0.3.0 and after step 8 (reboot after flashing blu_spark) my phone gets stuck on blu_spark splash screen without any option to boot into twrp. Normal boot results in bootloop... Any ideas? Do I need to use different versions of twrp.img and .zip?
Click to expand...
Click to collapse
I am in exactly the same position here.
Followed all the steps and am now stuck on the blu_spark boot screen for the past 15 minutes
I have a OnePlus 7 Pro on Android 11, OOS 11.0.0.2. The bootloader is unlocked. The devices runs absolutely fine unrooted. I have been wanting to root for quite some time. I patched the boot.img file of the ROM using latest Magisk Canary (app-debug.apk) from the GitHub repository. When I flash the .img through ADB, it is flashed successfully.
But when I reboot the phone, the phone is stuck on OnePlus' 'Two circling dots animation' (bootloop) and never starts. These are the commands that I enter one-by-one in CMD prompt on my laptop:
adb devices
adb reboot bootloader
fastboot flash boot "D:\Downloads\boot_patched.img"
fastboot reboot
Click to expand...
Click to collapse
So, to get out of this issue, I flash the stock boot image using similar commands. Then the phone boots successfully, but, of course, it is unrooted.
I even tried these commands, still no luck.
fastboot flash boot_a "D:\Downloads\boot_patched.img"
fastboot flash boot_b "D:\Downloads\boot_patched.img"
Click to expand...
Click to collapse
I also tried patching using the stable Magisk release (Magisk v23.0), still nothing.
What am I doing wrong?
iamMG said:
I have a OnePlus 7 Pro on Android 11, OOS 11.0.0.2. The bootloader is unlocked. The devices runs absolutely fine unrooted. I have been wanting to root for quite some time. I patched the boot.img file of the ROM using latest Magisk Canary (app-debug.apk) from the GitHub repository. When I flash the .img through ADB, it is flashed successfully.
But when I reboot the phone, the phone is stuck on OnePlus' 'Two circling dots animation' (bootloop) and never starts. These are the commands that I enter one-by-one in CMD prompt on my laptop:
So, to get out of this issue, I flash the stock boot image using similar commands. Then the phone boots successfully, but, of course, it is unrooted.
I even tried these commands, still no luck.
I also tried patching using the stable Magisk release (Magisk v23.0), still nothing.
What am I doing wrong?
Click to expand...
Click to collapse
I had an issue before, with the Canary APK. Try installing the v23 app and repatch your boot IMG with it. Worth a shot.
I tried, again, with v23. Same bootloop occuring.
Do you perhaps have the magisk app installed, I know of modules causing these sort of bootloop issues.
@soka said:
Do you perhaps have the magisk app installed, I know of modules causing these sort of bootloop issues.
Click to expand...
Click to collapse
Yes, the Magisk app is installed, but I don't have any modules installed. I don't even have root, how will I install a module?
iamMG said:
Yes, the Magisk app is installed, but I don't have any modules installed. I don't even have root, how will I install a module?
Click to expand...
Click to collapse
True, sorry just trying to help you narrow it down.
@soka said:
True, sorry just trying to help you narrow it down.
Click to expand...
Click to collapse
No problem. I just need to know how to fix the issue. Else, I would have to flash OOS 10.
iamMG said:
No problem. I just need to know how to fix the issue. Else, I would have to flash OOS 10.
Click to expand...
Click to collapse
This OnePlus 8T thread https://forum.xda-developers.com/t/...in-eu-us-kb2000-kb2001-kb2003-kb2005.4178675/ says to boot, not flash, the patched boot image. In other words, use fastboot boot "D:\Downloads\boot_patched.img" and then do a direct install in Magisk.
That's the process I used and it worked perfectly.
Note: my phone is an 8T.
BillGoss said:
This OnePlus 8T thread https://forum.xda-developers.com/t/...in-eu-us-kb2000-kb2001-kb2003-kb2005.4178675/ says to boot, not flash, the patched boot image. In other words, use fastboot boot "D:\Downloads\boot_patched.img" and then do a direct install in Magisk.
That's the process I used and it worked perfectly.
Note: my phone is an 8T.
Click to expand...
Click to collapse
Thanks, I will try this method and report back.
Btw, after you booted using this method, for how much time did the boot animation showed up (the two circling white dots around bigger red dot)?
Edit: I tried this method. No luck. The boot animation goes on 5-10 minutes, at which point I reboot into bootloader and flash the stock boot image.
Anyway, I ended up downgrading to OxygenOS 10.3.8.
Starting to give up as well... Never had any issues before (on Android 10) to flash root on O7Pro, but ever since Android 11, I keep having "boot loop" issues. Aka, the boot logo keeps loading and never boots into the OS. Only works again if I re-patch the original boot.img file.
This is starting to get.. VERY, VERY annoying. Why isn't there any proper method of getting this to work?
Not sure which boot.img you using.
But I face similar problem a week ago, and i fix that by using another .img then all fine.
I download from:
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
i'm running oxygen os 11.0.2.1 with root access. i'm running with the latest version of magisk, v.23.0. i haven't had any problems with android 11 and root. my suggestion is to make sure that you're patching the correct boot image. when an update is available, i download the full update, copy the zip to a computer, and then use payload dumper to extract the boot image. that's the boot image i use for patching.
hkdoublecat said:
Not sure which boot.img you using.
But I face similar problem a week ago, and i fix that by using another .img then all fine.
I download from:
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Click to expand...
Click to collapse
I am too afraid to upgrade to OOS 11, only to find out root doesn't work for me. The restore function of this unofficial TWRP version is buggy so can't really depend on it to restore OOS 10.3.8. So, I have decided to stay on the latter until Team Recovery releases a proper update for Android 11.
altwu said:
i'm running oxygen os 11.0.2.1 with root access. i'm running with the latest version of magisk, v.23.0. i haven't had any problems with android 11 and root. my suggestion is to make sure that you're patching the correct boot image. when an update is available, i download the full update, copy the zip to a computer, and then use payload dumper to extract the boot image. that's the boot image i use for patching.
Click to expand...
Click to collapse
Hi i am just wondering if you can upload the patch image and the original boot image of 11.0.2.1GM21AA thanks in advance.
Mangtas_666 said:
Hi i am just wondering if you can upload the patch image and the original boot image of 11.0.2.1GM21AA thanks in advance.
Click to expand...
Click to collapse
attached are the original and magisk patch boot images from my phone running 11.0.2.1 GM21AA.
boot_11021.img is the original boot image that i extracted with payload dumper.
magisk_patched-23000_fQNMs.img is the magisk patched boot image. it was patched with magisk v23.0.
altwu said:
attached are the original and magisk patch boot images from my phone running 11.0.2.1 GM21AA.
boot_11021.img is the original boot image that i extracted with payload dumper.
magisk_patched-23000_fQNMs.img is the magisk patched boot image. it was patched with magisk v23.0.
Click to expand...
Click to collapse
i tried attaching the images to the post but they're not showing up. i tried editing the post to attach the images, but they're still not showing up. sorry.
We received a new 8t and proceeded to do root and unlock on it.
Here is my process and problem.
Unlocked bootloader.
Updated phone to recent version via OTA update.
Downloaded update via Oneplus website.
Extracted payload.bin VIA python.payload dumper.
Moved boot.img to phone and patched it with magisk (select and patch a file)
Moved patched image to PC and ran adb
Fastboot flash boot patched image name.img
rebooted , now its caught in bootloop.
Tried fastboot --set-active=a and it didnt make a difference.
When looking at adb devices it shows the attached phone as unauthorized.
Dont know if this helps
Can get into fastboot
You flashed the OS to the bootloader. Not sure how to help you, man. Maybe try the EDL Tool. That worked for me. Also, always install TWRP and flash magisk zip through TWRP. It's foolproof.
TWRP doesnt work with android 11 or the oneplus 8 as far as I know, last time I looked.
Did a tool and fixed the crashes and bootloop, then followed a youtube video and guide.
Found out I ended up doing a different OS version that didnt match.
eracet said:
TWRP doesnt work with android 11 or the oneplus 8 as far as I know, last time I looked.
Did a tool and fixed the crashes and bootloop, then followed a youtube video and guide.
Found out I ended up doing a different OS version that didnt match.
Click to expand...
Click to collapse
TWRP for the 8T works reasonably well. See https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/