Related
For those of you who want to root your OnePlus 6, here is the easiest root method even a 10-year old can follow that works on all Windows, Mac, and Linux. Now, before I begin, you will have to unlock the bootloader. If you have not unlocked your bootloader or don’t know what that is, please follow How to Unlock Bootloader on OnePlus 6 first!
Here's a full step-by-step video tutorial:
First, I want to thank those who made root tutorials but I found an easier way to root that does not involve switching any slots, took me a quite awhile to figure this out but well worth the effort. You only have to flash TWRP image to boot, then with TWRP flash boot.img, TWRP installer, and Magisk with this tutorial. You can do it easily on all Windows, Mac, Linux, or even Chromebook(just install Chrome ADB on Chrome Web store)
Special thanks to magnamentis, his method didn't work for me as I lost my Wifi but after few hours of tinkering, found you can just reflash boot.img then the TWRP installer zip file he provided, and voila! Flawless root everytime, I've tested this about 10 times now, thanks again for the post here:
https://forum.xda-developers.com/showpost.php?p=76687704&postcount=212
Step 1. Once you have unlocked your bootloader, make sure to SIGN IN as if you do not sign into your phone, you will end up in a nasty bootloop.
Step 2. Check your Android version in Settings->About Phone just in case you are reading this in the future when Android 9.0 comes out but this tutorial is future-proof and will work on future Android versions so long as you use the correct boot image file.
Step 3. Power off your phone and hold down Volume Up and Power buttons for about 3 seconds until you enter the Fastboot mode. When doing this, make sure your USB cable is disconnected otherwise you may enter another special mode for unbricking. If you mess up and get into that special mode, simply reboot your device by holding down Volume Down and Power buttons for about 20 seconds.
Step 4. Once in fastboot mode, connect a USB cable from your OnePlus 6 to your computer. You can use Windows, Mac, or Linux. For my video tutorial, I will be using Windows 10 but you can go ahead and use the substitute code for Mac or Linux as most of the steps are nearly identical.
Step 5. You will need to download:
NOTE: All the download links are at the BOTTOM OF THE PAGE, wait 5 secs and click on "CLICK HERE TO DOWNLOAD", don't click on the ads!!!
Download fastboot.zip:
https://download.highonandroid.com/file/Tools/fastboot.zip
Android USB Drivers for Windows:
https://download.highonandroid.com/file/Drivers/UniversalAdbDriverSetup.msi
Download Magisk:
https://download.highonandroid.com/file/Tools/Magisk/Magisk-v16.4.zip
Download TWRP image:
https://download.highonandroid.com/file/TWRP/OnePlus6/twrp-3.2.1-oneplus6.img
Download TWRP installer zip:
https://download.highonandroid.com/file/TWRP/OnePlus6/twrp-installer-oneplus6-3.2.1.zip
Download and boot.img for OnePlus 6T Android 8.1:
https://download.highonandroid.com/file/TWRP/OnePlus6/boot/8.1/boot.img
Step 6. If you have followed my bootloader unlock tutorial and installed drivers for Windows, you can skip that step. If not, you can go head and run the Android USB Driver program and install drivers. For Mac or Linux, no drivers are needed!
Step 7. Unzip fastboot.zip and move over the TWRP image file you downloaded earlier to the fastboot folder.
Step 8. Open a command prompt for Windows by typing “cmd” in the search bar. For Mac or Linux, open a terminal, if you don’t know how, please Google it.
Step 9. Type the following.
For Windows:
cd Downloads
cd fastboot
fastboot flash boot twrp twrp-3.2.1-oneplus6.img
For Mac:
cd Downloads
cd fastboot
chmod 755 *
./fastboot-mac flash boot twrp twrp-3.2.1-oneplus6.img
Note: CHMOD command basically changes file permissions so you can run the files.
For Linux:
cd Downloads
cd fastboot
chmod 755 *
sudo ./fastboot-linux flash boot twrp twrp-3.2.1-oneplus6.img
Note: CHMOD command basically changes file permissions so you can run the files.
This will flash the TWRP image to your boot partition. Normally, we can simply boot TWRP image but since we don’t have official TWRP recovery(as of writing this), you will have to flash TWRP image to the boot partition, which allows us to boot TWRP recovery.
Step 10. Choose “Recovery” using the Volume keys and hit Power button to enter TWRP recovery.
Step 11. Recovery will probably be in Chinese, hit the “Read Only” button, top button on left middle.
Step 12. You can change the language back to English by hitting the second box from bottom right then hit the globe icon on top right.
Step 13. Go back to your computer and copy over the TWRP install zip file, Magisk zip file, and boot.img file.
Step 14. You don’t need the USB cable connected anymore. Go ahead and install the boot.img file using the image option in Install menu. This will flash back your regular boot image to the boot partition.
Step 15. Next, install the TWRP install zip and Magisk zip file. This will give you permanent TWRP recovery and full root.
Step 16. Reboot and you should see everything working including WiFi, 4G LTE, yadayadayada. Open Magisk Manager app and find you have full root with SafetyNet pass also so you can hide root.
Verify you have full root by installing Titanium Backup app(free app) on the Play Store, you should see a Superuser request window.
That’s it! Enjoy folks!
OnePlus 6T? How is this supposed to be easier? You have sixteen steps here. The other method from wuxianlin is very simple I did it in five minutes with no issues at all including WiFi still working. And how can you say you don't have to switch slots. It is required to flag TWRP to both a and b for it to work properly. You don't even mention that in this tutorial.
se7ensde said:
OnePlus 6T? How is this supposed to be easier? You have sixteen steps here. The other method from wuxianlin is very simple I did it in five minutes with no issues at all including WiFi still working. And how can you say you don't have to switch slots. It is required to flag TWRP to both a and b for it to work properly. You don't even mention that in this tutorial.
Click to expand...
Click to collapse
I got lost trying to do that root method, I was following this one here:
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
But yeah you don't have to switch slots for my root tutorial, which can cause havoc if you flash to the wrong one. If you don't believe me just watch the video. It doesn't hurt to have multiple root methods so long as they work. But my Wifi kept dying everytime I used the slot switch method until I found this way to do it.
I am only trying to make a tutorial that even a kid follow but I've broken down a few steps into maybe 10+ steps, probably helpful for noobs who are trying to root. If you are advanced XDA user, great job though, took me a few hours myself to get a flawless root method. Believe me, I love shortcuts and any method that works the first time out but sucks if people don't explain every little detail as not everyone is an expert. I've been rooting phones for awhile now and it was not easy task with OP6.
Can i use this method over patched boot image? I now rooted from https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440 this guide…i wonder
galza said:
Can i use this method over patched boot image? I now rooted from https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440 this guide…i wonder
Click to expand...
Click to collapse
Yes, since this root method flashes a stock boot image after installing TWRP, you can follow it fine. But make a backup of everything just in case.
Basically, this root method, you flash TWRP to boot partition, then flash stock boot image in TWRP, flash TWRP installer for permanent TWRP, then flash Magisk, and reboot. It's actually just 4 steps, I had to make it much longer for noobs because they will mess up.
zedomax said:
Yes, since this root method flashes a stock boot image after installing TWRP, you can follow it fine. But make a backup of everything just in case.
Basically, this root method, you flash TWRP to boot partition, then flash stock boot image in TWRP, flash TWRP installer for permanent TWRP, then flash Magisk, and reboot. It's actually just 4 steps, I had to make it much longer for noobs because they will mess up.
Click to expand...
Click to collapse
I didn't have to switch slots to root at all and I used the very first method to gain root that was posted here on op6 forums.
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440
se7ensde said:
I didn't have to switch slots to root at all and I used the very first method to gain root that was posted here on op6 forums.
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440
Click to expand...
Click to collapse
Yes, that root method is great but it does not give you TWRP recovery, meaning you can't install custom ROMs with it. But if you need TWRP recovery, you will need to install TWRP recovery thru one of the tutorials here.
zedomax said:
Yes, that root method is great but it does not give you TWRP recovery, meaning you can't install custom ROMs with it. But if you need TWRP recovery, you will need to install TWRP recovery thru one of the tutorials here.
Click to expand...
Click to collapse
The current method of installing TWRP is not noob friendly. Nor is yours in fact after reading yours or seems not complicated than it needs to be. You also need to give credit to the creators of our TWRP and there guides.
galza said:
Can i use this method over patched boot image? I now rooted from https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440 this guide…i wonder
Click to expand...
Click to collapse
Did it work for you?
Thanks @zedomax!! Never hurts to have different methods, opinions, or guides! Jeep rockin! #neversettle
@zedomax Thank you for these amazing tutorials. I watched both your videos. In that you mentioned that OnePlus ota updates are twrp compatible but then if I root will I have to unroot the phone or flash the stock rom first then install that ota update and then root again or there's some other method to install OTA on a rooted device?
Aashay said:
@zedomax Thank you for these amazing tutorials. I watched both your videos. In that you mentioned that OnePlus ota updates are twrp compatible but then if I root will I have to unroot the phone or flash the stock rom first then install that ota update and then root again or there's some other method to install OTA on a rooted device?
Click to expand...
Click to collapse
You can accept OTA, but you will have to reflash Magisk.img. Most OTAs do not overwrite boot.img I think unless they are major updates(like to Android P 9.0 when available). So, just flash OTA and if you lose root, reboot into TWRP and flash Magisk.
HI, thanks for the guide but my phone just blocked at recovery launch. Ho can i do?
Same
Edit: It's ok, probably a bug
Thank you zedomax for taking the time to create this guide. I'm gonna try it!
I assume this will work for both A6000 and A6003 right?
Hi Admin,
I lost my Wifi as soon as i rooted my device, please help?
Prabhjeet Bagga said:
Hi Admin,
I lost my Wifi as soon as i rooted my device, please help?
Click to expand...
Click to collapse
Me too. How can this be fixed?
I think I bricked my phone.
This is what I did:
- Bought OnePlus 6 (I think it was A6000)
- Installed OTA, so I was on Android 8.1.0 and OOS 5.1.8
- Followed this tutorial, which broke wifi
- I followed mixtapes02's advice on the video and reflashed OOS 5.1.8
- Now I cannot boot into Android anymore, I can only get to TWRP
EDIT: I managed to install OOS 5.1.5 successfully
aximili said:
I think I bricked my phone.
This is what I did:
- Bought OnePlus 6 (I think it was A6000)
- Installed OTA, so I was on Android 8.1.0 and OOS 5.1.8
- Followed this tutorial, which broke wifi
- I followed mixtapes02's advice on the video and reflashed OOS 5.1.8
- Now I cannot boot into Android anymore, I can only get to TWRP
EDIT: I managed to install OOS 5.1.5 successfully
Click to expand...
Click to collapse
I had the same issues and went through the same process. Took a whole day to get it back to stock.
I am sorry to ask such a noob question, but i am very confused by the command you say to use in Step 9:
>fastboot flash boot twrp twrp-3.2.1-oneplus6.img
what is the meaning of the first "twrp" in that command?
shouldn't it be simply:
fastboot flash boot twrp-3.2.1-oneplus6.img
Thank you in advance for the explanation
Magisk on G7 Play XT1952-4 Installed Succesfully
(Just a heads up. I have never posted to XDA before but have lurked on here for years. I don't have enough posts to post it in the Dev section. So I apologize if my post format is bad. But I will do my best. Hopefully I am not reporting old news, I've been waiting a few months to finally get Magisk to work on this phone.)
I do not take responsibility if you brick your phone doing this. So do it at your own risk.
Google Drive folder link with all files at the bottom of this post with screenshots as well
Install:
Firmware used during this is PPY29.105_160 (Firmware included in GDrive folder)
BOOTLOADER HAS TO BE UNLOCKED ON YOUR PHONE
I suggest you to backup and factory reset your phone before doing this.
If you're already on this firmware, then I have placed both the stock boot.img and the magisk_patched.img separate as well so you don't have to unzip the full firmware. I haven't tried this with other models of this phone or firmwares. Upgrade to this firmware if on an older version. Multiple ways to do so I'm sure you can figure it out
Copy the boot.img to your phones storage
Install Magisk Manager 7.3.4 aka 239 (APK in GDrive folder). Make sure all 3 options are checked in advanced settings in Magisk. Click install on Magisk and patch the file and locate it on your phone.
Place the patched.img in your ADB folder. Reboot into fastboot. I used CMD in Windows so I ran the following "fastboot flash boot magisk_patched.img"
Toggle up to Boot Recovery
Please Note. When I did the following. For some reason I was unable to get to the stock recovery after doing this. If I remove modules and reboot the phone Magisk is "not installed" however if you reboot the phone and go into Fastboot mode and then select the option of boot to recovery, it boots the phone normal with magisk enabled??? :confused. Eh at this point I'm just glad to have Magisk installed on this phone finally lol. I'm sure you can find the answer in the Magisk in Recovery section here
Magisk should be installed now after booting up. Check Magisk Manager to verify.
Notes:
I tried to install one module just to verify it wasn't a fluke and I was able to do so successfully
Once again I apologize if this post is unorganized or anything. Running on little sleep
I will do my best to answer any questions you might have from my experience when I am able to.
GOOGLE DRIVE FOLDER LINK
Nice work OP. Well written guide. Clear and concise.
i need some help i tried this method and ended up loosing baseband idk what i did wrong i have a retail varient , tried flashing stock rom multiple times do we have a persist.img to get the phone booting again ? twrp wont even boot i get the failed to many links error to see if wiping the phone that way would make it boot i flashed to both banks i have the XT195-4 varian
Use rsd lite to flash full rom it will reset your phone then enable usb debugging so you can reboot to fastboot then follow the instructions
Linuxassassin said:
Use rsd lite to flash full rom it will reset your phone then enable usb debugging so you can reboot to fastboot then follow the instructions
Click to expand...
Click to collapse
Thank you I managed to create a flash.bat with revived the phone I can confirm working on retail varient firmware 138
Ok this is a bit odd. Managed to get magisk installed. Rebooted and magisk is no longer installed. Figured I would have to reboot recovery again. Now whenever I go to boot recovery in the bootloader it just falls back to the bootloader.
The recovery option in magisk will not stick either it seems
Edit: Not sure what happened. I reflashed the stock firmware for my device, went through the steps again, and now magisk seems to have stuck. I do have to boot to recovery, but that was to be expected according to the documentation.
Oh Viper4Android, how I have missed thee
Edit 2: It appears the reboot to recovery option in magisk is what is breaking my install. As long as I do not try to reboot to recovery from anything outside of the bootloader, magisk sticks. Not sure what the cause for this is, but for now it is best to stay away from those options in Magisk
Edit 3: Not sure what the issue is, but after some tinkering, and a reboot, booting recovery to get magisk loaded does not work. Reboot to recovery takes me straight to the bootloader. If I click start the phone boots without magisk, and if I hold the button combo I get the stock recovery, but magisk appears to be gone
Please help
I flash wrong boot so I reflashed the entire firmware then patched the boot.img of the firmware I just flashed, all ok.
I flashed the patched boot image and toggled volume key to recovery but have no options there, so have to start phone by holding power button.
When phone boots up magisk is not installed. This is killing me so close yet...
P.s I omitted erase user data and erase DDR and phone is exactly as I left it ?
moochermick said:
Please help
I flash wrong boot so I reflashed the entire firmware then patched the boot.img of the firmware I just flashed, all ok.
I flashed the patched boot image and toggled volume key to recovery but have no options there, so have to start phone by holding power button.
When phone boots up magisk is not installed. This is killing me so close yet...
P.s I omitted erase user data and erase DDR and phone is exactly as I left it
Click to expand...
Click to collapse
your missing a step , what worked for me , since i updated my phone manually and now im on slot_a flash both banks with the magisk_patched.img and you wont have that problem , if your on slot_b flash slot_a as well , and it should work , fastboot getvar all to see what slot is bootable
@thenatti
Thanks I will give that ago.
thenatti said:
your missing a step , what worked for me , since i updated my phone manually and now im on slot_a flash both banks with the magisk_patched.img and you wont have that problem , if your on slot_b flash slot_a as well , and it should work , fastboot getvar all to see what slot is bootable
Click to expand...
Click to collapse
I have flashed the patched boot to both banks and still magisk not installed, what's all this talk about booting from recovery, I can't do anything from recovery except hold the power button to restart the phone.
Any further suggestions?
Ok here's what worked...
Reflashed all firmware and restarted phone,
Flashed patched boot.img and in fastboot on pc "fastboot continue" phone rebooted.
Back into fastboot on phone and selected "recovery" phone rebooted and Magisk installed.???
Many many thanks to op and everyone involved.
Can anyone make a video with installation of Magisk on this device, PLEASE!! Will be more easy..
I am thinking my original problem is with Magisk itself. For some reason I randomly lose root after a restart, and booting recovery just goes straight back to the bootloader. It hasnt happened to me again, but it happened twice yesterday.
I am usually good a bug tracking, but I have been unable to narrow this down to a specific thing.
Anyway.... today things are working great.
moochermick said:
Ok here's what worked...
Reflashed all firmware and restarted phone,
Flashed patched boot.img and in fastboot on pc "fastboot continue" phone rebooted.
Back into fastboot on phone and selected "recovery" phone rebooted and Magisk installed.
Many many thanks to op and everyone involved.
Click to expand...
Click to collapse
Can you bring me your steps for install Magisk on your device with variant that you have, please?
I would suggest for people having trouble with getting magisk installed
A few things to note
No will need to boot into fastboot then use volume keys to
Select recovery option Everytime you boot or you won't be rooted
Stay on the beta of magisk cause stable is not ready for our device
If you brick use rsd lite with latest firmware
Thats on https://mirrors.lolinet.com/firmware/moto/channel/official/
How to boot in fastboot is volume up and power key
When you flash firmware via rsd lite it will factory reset your phone
Then after that setup your phone but don't connect to WiFi or do
Just enable developer options
USB debugging
Plug phone into PC
If you don't have the us varient of the phone get the firmware for your phone
transfer the boot.img from your firmware to your phone
install magisk manager from the original post
Then follow the instructions to install magisk
ALSO MAKE SURE YOUR BOOTLOADER IS UNLOCKED
Or you will brick your phone
Hope that helps
I have had a successful install pretty stable been running great for I think 3days now
Mods I installed
Viper4android
Energized
Edxposed needs riru core to work
Gravitybox for pie requires edxposed
Anyone have the boot.img for firmware
PPYS29.105-134-2
---------- Post added at 10:50 PM ---------- Previous post was at 10:44 PM ----------
Linuxassassin said:
I have had a successful install pretty stable been running great for I think 3days now
Mods I installed
Viper4android
Energized
Edxposed needs riru core to work
Gravitybox for pie requires edxposed
Click to expand...
Click to collapse
How you could flash the modules?
thx
Linuxassassin said:
I would suggest for people having trouble with getting magisk installed
A few things to note
No will need to boot into fastboot then use volume keys to
Select recovery option Everytime you boot or you won't be rooted
Stay on the beta of magisk cause stable is not ready for our device
If you brick use rsd lite with latest firmware
Thats on
How to boot in fastboot is volume up and power key
When you flash firmware via rsd lite it will factory reset your phone
Bro thank you so much rsd lite unbricked my device!
Then after that setup your phone but don't connect to WiFi or do
Just enable developer options
USB debugging
Plug phone into PC
If you don't have the us varient of the phone get the firmware for your phone
transfer the boot.img from your firmware to your phone
install magisk manager from the original post
Then follow the instructions to install magisk
ALSO MAKE SURE YOUR BOOTLOADER IS UNLOCKED
Or you will brick your phone
Hope that helps
Click to expand...
Click to collapse
Bro thank you so much rsd lite unbricked my device!
Fdraco10 said:
Anyone have the boot.img for firmware
PPYS29.105-134-2
---------- Post added at 10:50 PM ---------- Previous post was at 10:44 PM ----------
How you could flash the modules?
Click to expand...
Click to collapse
You search riru core in modules
Install that reboot to recovery
Flash edxposed
Funfact gsi won't flash on a phone till we get unofficial twrp
So I use gravitybox for pie hence my power menu
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
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: twitter dot com /topjohnwu/status/1272136975022084097?s=19 (until I figure out how to stop new XDA from forcing the URL to embed a giant twitter posting in the middle of the post...)
ALL FILES BELOW ARE FOR "RQ2A.210405.005, Apr 2021"!
Magisk v22.0 Patched Boot Image: https://www.androidfilehost.com/?fid=2188818919693776322
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=2188818919693776321
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=2188818919693776320
----------------------------------------------
-------------UPDATE PROCESS BELOW-------------
----------------------------------------------
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 (RQ2A.210305.006, Mar 2021)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rq2a.210305.006-factory-dtbo.img: https://www.androidfilehost.com/?fid=17248734326145746585
coral-rq2a.210305.006-factory-boot.img: https://www.androidfilehost.com/?fid=17248734326145746583
April 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq2a.210405.005-0d148a1d.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-rq2a.210305.006-factory-boot.img
3. fastboot flash dtbo coral-rq2a.210305.006-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-rq2a.210405.005-0d148a1d.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-rq2a.210405.005-magisk_patched-22.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.
-------------------------------------------------
-------------------TROUBLESHOOTING-------------------
-------------------------------------------------
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
Since Magisk v21.x, Core Only mode has been replaced by using Android's built-in Safe Mode. Booting into Safe Mode should essentially boot you back into your system but with all modules disabled (as well as Magisk Hide). Keep in mind that even after you reboot, modules will remain disabled, unless you re-enable them first. Also remember to re-enable Magisk Hide if you had it enabled before.
Please see @Didgeridoohan's guide for more details: https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Core_Only_Mode
It's also worth mentioning, his guide is extremely well-made and contains a lot of useful information that could benefit all Magisk users and modders. I highly recommend looking through it anyway!
@i5lee8bit - thanks, worked fine on my Pixel 4 XL. However, during the OTA process my console showed me following error message:
Code:
C:\Unified_Android_ToolKit\platform-tools_r30.0.4-windows\platform-tools> adb sideload C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip
serving: 'C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip' (~94%) adb: failed to read command: No error
The device itself showed something across the lines of exit error code 0.
Everything seems to be running ok so far. Do I have to worry about the OTA stopping to transfer at 94%?
niko26 said:
Code:
C:\Unified_Android_ToolKit\platform-tools_r30.0.4-windows\platform-tools> adb sideload C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip
serving: 'C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip' (~94%) adb: failed to read command: No error
The device itself showed something across the lines of exit error code 0.
Everything seems to be running ok so far. Do I have to worry about the OTA stopping to transfer at 94%?
Click to expand...
Click to collapse
Maybe you should update your platform tools to the latest version: it's v31.0.0 as of February 2021. Your log says you're running 30.0.4.
Hi. This first time happens to me when I reboot the phone the Root is gone and have to flash the magisk_patched again!! Please is there any suggestion on how I keep Root after reboot?
DinarQ8 said:
Hi. This first time happens to me when I reboot the phone the Root is gone and have to flash the magisk_patched again!! Please is there any suggestion on how I keep Root after reboot?
Click to expand...
Click to collapse
You'll have to re-root after each update. The method used to keep root when updating via OTA was removed from Magisk b/c it was causing problems on Pixels.
niko26 said:
@i5lee8bit - thanks, worked fine on my Pixel 4 XL. However, during the OTA process my console showed me following error message:
Code:
C:\Unified_Android_ToolKit\platform-tools_r30.0.4-windows\platform-tools> adb sideload C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip
serving: 'C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip' (~94%) adb: failed to read command: No error
The device itself showed something across the lines of exit error code 0.
Everything seems to be running ok so far. Do I have to worry about the OTA stopping to transfer at 94%?
Click to expand...
Click to collapse
Like @Ghisy already said, definitely start with trying newest platform tools. I've had that error come up before but experienced no problems.. weird thing is it happened to my wife's Pixel 4, but not my Pixel 4 XL when I did the updates right after another. So used the same platform tools, PC, etc. Another thing to consider that may help you feel better is that some custom ROMs actually expect that to happen when installing their ROM as a sideload OTA, so could indeed be nothing to worry about.
If it really really worries you, you could always flash the full factory image with "-w" removed from the script file, and either replace the boot.img with the Magisk patched one (rename it first), or flash it separately later. But for now if everything is working normally and it indicates you're on April 2021, I wouldn't worry about it.
DinarQ8 said:
Hi. This first time happens to me when I reboot the phone the Root is gone and have to flash the magisk_patched again!! Please is there any suggestion on how I keep Root after reboot?
Click to expand...
Click to collapse
What @Lughnasadh said is certainly true; is this what you mean? Or the way I read your question, are you losing root between reboot despite flashing the Magisk patched boot image? Are you sure you flashed it? Are you doing fastboot flash boot (file.img) or doing fastboot boot (file.img)? Make sure you're actually flashing it, not just booting to it. If all else fails, try doing a complete uninstall of Magisk and then start over (hopefully won't be necessary). I've never heard of anyone having the problem you're having though, and it sounds more like you're fastboot booting to the Magisk patched image, and not actually fastboot flashing it...
i5lee8bit said:
Like @Ghisy already said, definitely start with trying newest platform tools. I've had that error come up before but experienced no problems.. weird thing is it happened to my wife's Pixel 4, but not my Pixel 4 XL when I did the updates right after another. So used the same platform tools, PC, etc. Another thing to consider that may help you feel better is that some custom ROMs actually expect that to happen when installing their ROM as a sideload OTA, so could indeed be nothing to worry about.
If it really really worries you, you could always flash the full factory image with "-w" removed from the script file, and either replace the boot.img with the Magisk patched one (rename it first), or flash it separately later. But for now if everything is working normally and it indicates you're on April 2021, I wouldn't worry about it.
What @Lughnasadh said is certainly true; is this what you mean? Or the way I read your question, are you losing root between reboot despite flashing the Magisk patched boot image? Are you sure you flashed it? Are you doing fastboot flash boot (file.img) or doing fastboot boot (file.img)? Make sure you're actually flashing it, not just booting to it. If all else fails, try doing a complete uninstall of Magisk and then start over (hopefully won't be necessary). I've never heard of anyone having the problem you're having though, and it sounds more like you're fastboot booting to the Magisk patched image, and not actually fastboot flashing it...
Click to expand...
Click to collapse
Ohhh yes thanks to remember me i forgot to write FLASH i was only boot without flash. Thanks for all
im having an issue with getting root back. i followed the instructions and when its time to reboot to the system, i get the splash screen but it reboots back to the bootloader or itll reboot twice and send me to the OS but without Magisk. ive done the factory image thing and still the same thing. i need help
@i5lee8bit Good stuff as usual, updated fine over here! Thanks!
Does anyone know the update process for Magisk now that everything is unified? I used to update manager then patch the boot image again. Is it still the same process from Magisk 22 to 22.1 (today's update)?
Ghisy said:
@i5lee8bit Good stuff as usual, updated fine over here! Thanks!
Does anyone know the update process for Magisk now that everything is unified? I used to update manager then patch the boot image again. Is it still the same process from Magisk 22 to 22.1 (today's update)?
Click to expand...
Click to collapse
If you are already rooted on Magisk 22.0, you should be able to just update the app to 22.1 and then do the direct install method to update root (I just did this and everything was fine using Beta channel). If you were unrooted and installing root for the first time (rather than updating), patching the boot image would be the way to go.
@Lughnasadh Yeah, I'm already rooted on v22. Just did the app update then direct install and it worked fine! I've been in the rooting game since the HTC Desire but the latest changes with Magisk confused me for a minute there!
Thanks
bluizzo said:
im having an issue with getting root back. i followed the instructions and when its time to reboot to the system, i get the splash screen but it reboots back to the bootloader or itll reboot twice and send me to the OS but without Magisk. ive done the factory image thing and still the same thing. i need help
Click to expand...
Click to collapse
Hey sorry, had a really busy week and haven't been on XDA in a few days. Did you get this resolved yet?
My first thought was you were probably bootlooping due to a Magisk (or Xposed) module that doesn't agree with the new firmware. Because that could cause a bootloop, kicking you back to bootloader and eventually forcing a safe mode boot, disabling all Magisk modules and MagiskHide... only problem with this is that afterwards, you should still have root, though with all modules and MagiskHide disabled (I'm more attuned to believe this was actually your case, not that you were "losing root" per se. When it boots back up, are you able to go into Magisk Manager and toggle your modules? Also, what does it say on the manager's home page under "Magisk" and "App" sections? (the parts titled "Installed"). You'll also want to make sure you're running / have installed Manager v22.0 (if flashing the Magisk patched image I provided in the OP; you can always update Magisk / Magisk Manager to v22.1 afterwards).
Sounds like you already tried flashing the 04-2021 full factory image too? Which would eliminate the possibility you maybe flashed the wrong boot / dtbo / or OTA files. If all else fails:
Re-flash full factory image (remove the -w flag in the script file - it sounds like you already did this so I'm assuming you know why) and it should boot unrooted - but you should be able to use the phone.
Make sure Magisk Manager version is 22.0 (i.e. same version as patched in the OP, though 22.1 would work fine too), and if not, grab it from topjohnwu's github and install it.
Reboot to bootloader and flash the Magisk patched boot image in OP (fastboot flash boot coral-rq2a.210405.005-magisk_patched-22.0.img).
Boot the phone. Hopefully you're done.
But if it bootloops, boot it in safe mode (this will disable all your modules as well as MagiskHide). Reboot again.
Open Magisk Manager and all modules should be disabled... time to test for the culprit!
Remember to re-enable MagiskHide, if you had it enabled before. It does not automatically re-enable like it did back in the pre-Magisk 21.0 days. Wow, this post ended up being a lot longer than I expected, and you might not even need the help anymore, lol (though I hope you did get it resolved sooner than later). But at least I can link to this as reference for future guides. Best of luck to you.
Lughnasadh said:
If you are already rooted on Magisk 22.0, you should be able to just update the app to 22.1 and then do the direct install method to update root (I just did this and everything was fine using Beta channel). If you were unrooted and installing root for the first time (rather than updating), patching the boot image would be the way to go.
Click to expand...
Click to collapse
Exactly as @Lughnasadh said, this is what I do too (except I'm using stable channel). Direct Install used to give me problems, but that was almost a year ago (a bit after I first got the phone last March), but it hasn't given me any problems since. Even in the very unlikely chance it did cause problems, you could always re-flash the patched boot image in the OP and then patch the stock boot image yourself using Magisk Manager and flash it.
i5lee8bit said:
Hey sorry, had a really busy week and haven't been on XDA in a few days. Did you get this resolved yet?
My first thought was you were probably bootlooping due to a Magisk (or Xposed) module that doesn't agree with the new firmware. Because that could cause a bootloop, kicking you back to bootloader and eventually forcing a safe mode boot, disabling all Magisk modules and MagiskHide... only problem with this is that afterwards, you should still have root, though with all modules and MagiskHide disabled (I'm more attuned to believe this was actually your case, not that you were "losing root" per se. When it boots back up, are you able to go into Magisk Manager and toggle your modules? Also, what does it say on the manager's home page under "Magisk" and "App" sections? (the parts titled "Installed"). You'll also want to make sure you're running / have installed Manager v22.0 (if flashing the Magisk patched image I provided in the OP; you can always update Magisk / Magisk Manager to v22.1 afterwards).
Sounds like you already tried flashing the 04-2021 full factory image too? Which would eliminate the possibility you maybe flashed the wrong boot / dtbo / or OTA files. If all else fails:
Re-flash full factory image (remove the -w flag in the script file - it sounds like you already did this so I'm assuming you know why) and it should boot unrooted - but you should be able to use the phone.
Make sure Magisk Manager version is 22.0 (i.e. same version as patched in the OP, though 22.1 would work fine too), and if not, grab it from topjohnwu's github and install it.
Reboot to bootloader and flash the Magisk patched boot image in OP (fastboot flash boot coral-rq2a.210405.005-magisk_patched-22.0.img).
Boot the phone. Hopefully you're done.
But if it bootloops, boot it in safe mode (this will disable all your modules as well as MagiskHide). Reboot again.
Open Magisk Manager and all modules should be disabled... time to test for the culprit!
Remember to re-enable MagiskHide, if you had it enabled before. It does not automatically re-enable like it did back in the pre-Magisk 21.0 days. Wow, this post ended up being a lot longer than I expected, and you might not even need the help anymore, lol (though I hope you did get it resolved sooner than later). But at least I can link to this as reference for future guides. Best of luck to you.
Exactly as @Lughnasadh said, this is what I do too (except I'm using stable channel). Direct Install used to give me problems, but that was almost a year ago (a bit after I first got the phone last March), but it hasn't given me any problems since. Even in the very unlikely chance it did cause problems, you could always re-flash the patched boot image in the OP and then patch the stock boot image yourself using Magisk Manager and flash it.
Click to expand...
Click to collapse
Nah, you're good fam. I ended up accidentally flashing the factory img and I'm back with root. Thank you for your help and the guides
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/