Related
Pixel 4 "FLAME" March 2020 QQ2A.200305.003 boot.img - Stock and Magisk v20.4 Patched
Hey all, I just updated my wife's P4 to Magisk 20.4 as of yesterday and have had no issues so far on the new version (nor on my P4XL). Here are the stock and recently newly updated Magisk patched (v20.4) boot images. I couldn't direct install the update on either of the phones via Magisk Manager, so I figured I would share these images.
Stock March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757144
Magisk Patched (v20.4) March 2020 boot image: https://www.androidfilehost.com/?fid=4349826312261757143
Remember, these are ONLY for those on QQ2A.200305.003 firmware already. Don't flash if you don't know what you're doing.
Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.
Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.
falawefulwaffle said:
Hey i5lee8bit,
Thanks for posting the p4 OTA boot files. worked perfectly. I have a p4xl as well. How do I extract the boot image from the device? I can not find the new boot image online from google or anything.
Click to expand...
Click to collapse
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
Spookymyo said:
Which method did you use to flash? I've tried it a few different ways and they don't work. I'm thinking on factory resetting and trying again but I don't want to do if I don't have to. I've had no problem rooting my pixel 4 on any of the other updates but for some reason I can't root the March update. It looks like things flash fine but when the phone reboots it gets to a black screen and just stays there. I know it can take a while during app optimization so I let it set over night. Still on a black screen the next morning.
Click to expand...
Click to collapse
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.
i5lee8bit said:
I'm not sure, I just grab them from the factory images (https://developers.google.com/android/images#coral). If it's not there, I wouldn't know. I came from years of HTC devices, but even then we either used TWRP or RUU decryption tool / firmware zips. Not sure if there's a way to extract directly from the device using dd or adb commands, but even then that was done using TWRP. Not sure if there's an alternate method; I'm not the right person to ask either, sorry. Tulsadiver's thread that I linked to for the other guy mentions a boot.img extractor, but I've never used it.
But if the boot file I provided worked perfectly for you, I would assume that means you are using the USA Unlocked model, and it should be available on the developers.google.com link I posted.
From bootloader, just the simple fastboot flash boot name_of_boot_image.img
It sounds like you OTA'd to the March build? And you previously had it Magisk rooted on a prior firmware version? It could be a module not playing nice. Maybe try booting into Magisk Core mode, see Tulsadiver's thread: https://forum.xda-developers.com/pixel-4/how-to/magisk-modules-disabler-booting-magisk-t3991739
Sorry for the delayed responses btw. Quarantine + work + school + new baby = wtf.
Click to expand...
Click to collapse
Thanks for the reply. I ended up getting it to work using the "payload_dumper-win64" method i found in another thread to extract the boot.img from the payload.bin file. Turns out the OTA file was online from google.
To updatePixel 4 xl with "coral-ota-qq2a.200305.003-3b25765d" MAach update OTA software:
- uninstalled Magisk
-updated software
-reinstalled magisk
-patched the boot img from payload.bin
-pushed modified boot to device
-Done
Everything seems to be working well. I got to use python for the first time, so that was kind of fun. I was a flashing machine back around the galaxy s4.
I got root working. Spent so much time trying different things and all I had to do was factory reset my phone. There must have been some file or module interfering with the process. Once I reset my phone the root process went without error. ?*
For me, pwning my new phone was a 7-hour process that required incredible learning capacity. Not everyone is prepared to go through a process like that, and it can easily take multiple days or weeks. This is a guide outlining a version of the exact process that got me to this point. It should be easy for anyone to follow, even people without much technical knowledge. (although, do be careful with the resulting root access)
I started with a GM1915, which is the T-Mobile model. You'd think it would require an unlock key from T-Mobile in order to work, but actually it doesn't. That's what they don't want you to know.
A well-known method for bypassing that requirement is to install an international OS and then upgrade it to a certain developer preview, causing the phone to update the bootloader to a non-crippled version that doesn't require an unlock key. So that's what I did.
However, the process is easier said than done. For someone like me who's done it, it's not too hard, but for a beginner it's intensely confusing. I was a beginner just yesterday and struggled with dumb error messages like "packed image not exist".
The guide is below. Sections starting with "T-MOBILE ONLY" and ending with "END OF T-MOBILE ONLY" are only to be performed on T-Mobile phones with T-Mobile firmware and a locked bootloader. If you have an unlocked bootloader then you can skip those steps.
Make sure you have a Windows machine. The Qualcomm drivers are only available for Windows, the programs are only available for Windows, people on this forum only know Windows. I have a Mac, personally, because Unix is awesome, but unfortunately nobody has thought about us and all the tools are Windows-only. I am just as disappointed as you, trust me. I used a virtual machine, but YMMV, depending on how good your hypervisor's USB passthrough is. You may want to use bare metal if you only have VirtualBox; it's not worth the effort. You will be hot plugging A LOT, and your phone will show up as many different types of USB devices.
You must have fastboot installed, but ADB is not required.
--- T-MOBILE ONLY ---
Install the "L2 drivers" for the phone. You can find them here. Just install as many of them as you can by right-clicking every `.inf` file you find and clicking Install on each one of them. Some of them will have missing files. Some of them won't have a signature. It doesn't matter, as long as you try every one of them, something will work. For me it was the 64-bit driver, in the 64 folder. All the others are 32-bit.
--- END OF T-MOBILE ONLY ---
You should probably plug the phone into your computer now and install the official OnePlus drivers as well. This is so that you can easily access the phone storage, which will become very important soon. Reboot your computer to apply the driver updates.
--- T-MOBILE ONLY ---
Download the "MSM Download Tool" from here (same link as above). Place it in its own folder. This is crucial because you must now download the guacamole-whatever.7z file and extract the .ots file into the same folder as the MSM Download Tool.
MSM Download Tool always looks in its folder for the image and pops up a cryptic error message if it's not found ("packed image not exist"). This is not very widely documented because MSM Download Tool is often distributed in the same folder as the image anyway. That's not the case when you are forced to download them as separate files.
Note that this is the only time you will have to use MSM Download Tool and all other updates can be installed by the phone itself. On international variants you don't have to do this because the bootloader will already be unlockable, which is why this is T-Mobile only.
You need to start downloading three updates. This patched version of international OOS is where you will start, the developer beta will upgrade the bootloader, and the full downgrade will roll you back so you can start updating. Start the downloads now, but you do not have to wait for them to finish yet; it will be a few steps before you have to use them.
Now is about the time to back up any data you want to keep. Everything on your phone will be wiped by the next step, including bootloader unlock status, all your data, the entire operating system and so on.
Now it's time to install international OOS. Place it inside the folder with MSM Download Tool and then start it up. Uncheck the SHA-256 checkbox!
Unplug your USB cable and THEN turn off your phone completely. If the USB cable is plugged in while it's turned off, it will automatically boot into the charging mode which is not what you want. Have your USB cable, and computer mouse, on the ready. You don't want to waste any time, because this may be physically painful: Hold down both volume buttons at the same time for at least 5 seconds, and then plug the USB cable into your phone. Make sure some COM port appears in the tool, then click the "Start" button in MSM Download Tool WHILE STILL HOLDING THEM DOWN. You can only let the volume buttons go AFTER you click "Start", or else the phone will drop out of EDL mode into fastboot.
The process will take a few minutes depending on how fast your USB connection is. Leave the phone plugged in until it is complete. This also gives time to download those two updates, which are together about four gigabytes in size.
Once MSM Download Tool is done flashing, you can reboot the phone and set it up using the setup wizard. Feel free to move fast and enable nothing. You don't need internet, you don't need a correct clock, you don't need accounts or telemetry or anything like that. All data will be wiped again later.
Use your computer to copy the developer preview update to the phone. Don't copy it to the Download folder or anything, copy it into the root (just inside the internal storage). Go to settings > local updates > settings icon in the top right > local update and update to the developer preview.
Once you're in the developer preview, enable OEM unlocking in developer options, reboot into fastboot mode (I do this by also enabling advanced reboot in developer options) and use fastboot oem unlock. Your bootloader is now unlocked! But we're not nearly done yet, there's still lots to do.
After rebooting, since the unlock wiped the phone, you'll have to set it up again. Just breeze through like before, then copy the rollback zip to the phone just like you did for the developer preview.
Go to local update again and use the rollback. This is required in order to go back to a stable OS that can accept OTAs. After this your data will be wiped. This is the real setup wizard. You can set it up with real data; your data will not be wiped again for the rest of this guide.
--- END OF T-MOBILE ONLY ---
If your bootloader is not already unlocked, enable OEM unlocking in developer options and then run `fastboot oem unlock` in Fastboot mode.
Next, you will want to install Magisk. This is a slightly complex process but once it's done your phone will become fully untethered.
First download a tool called Payload Dumper. Extract the entire archive into its own folder. Get an OTA update for your version of OxygenOS (if your phone is T-Mobile, that is the rollback update you just installed; if you aren't following the T-Mobile guide, you may have to download an OTA update from Google), and use WinRAR or similar to extract the `payload.bin` inside into the payload dumper's input folder.
Run the payload dumper. You don't need to run all of it; wait for "boot" to show up in the console window, then wait until something else shows up and then close the window. Inside the output folder there should be a `boot.img`; there may be other img files but the boot is what we're interested in.
Transfer this boot.img to your device and use Magisk Manager to patch it. Transfer the magisk_patched.img to your computer, reboot the phone into fastboot mode and use `fastboot flash boot magisk_patched.img`. Reboot the phone into Android.
If you start Magisk Manager you should see that Magisk is installed. Great. Next step is to install TWRP.
In my experience, flashing TWRP or using `fastboot boot twrp.img` didn't work. You're not clever if you try installing OxygenOS 9.5.4 which adds `fastboot boot` support to the bootloader; it still won't work. In my experience the only correct way to install TWRP on the OnePlus 7 Pro is to use Magisk.
(Someone in the replies below stated that you need to upgrade all the way to OOS 10 in order to boot TWRP using fastboot. This guide details the easier method using Magisk Manager.)
On the phone, go to the TWRP downloads page for the OnePlus 7 Pro, and download the latest installer. Then flash the zip using Magisk.
Crucially, at the end of the installer log it says "you are now unrooted". DO NOT IGNORE THIS MESSAGE! If you reboot now, Magisk will be gone and the stock ROM will immediately overwrite TWRP. You must use Magisk Manager to reinstall Magisk using a "Direct Install". That way, your boot.img will be patched again and your Magisk (and TWRP) will persist across reboots.
Go ahead and try it out. Reboot a few times, sometimes into recovery, sometimes into Android to test Magisk.
We're still not done yet. Wouldn't you love to stay rooted and still be running the latest version of OxygenOS? I sure would. Next I'll describe the process of applying an OTA update while keeping your root and everything. Thanks to A/B you can stay untethered.
Please note that, if you'd like to proceed with the EU version of OxygenOS, you should go grab 9.5.4 before proceeding to the next step, for example from here (MD5 fcec14e2ec053d67c793a27bfdef17d0), and use local update to install it. (note GM21BA instead of GM21AA) The EU version is supposed to have better privacy options and less bloatware, so that's what I personally went with. Converting your OxygenOS from GM21AA to GM21BA has no harmful side effects and should work on any phone. It affects the OTA you'll receive in the next step, and this is possibly the only chance you'll get to switch (or not). So choose wisely.
You can find other versions of OOS in this XDA post.
Remember to turn off all auto-updating in the OxygenOS settings. You don't want your phone suddenly losing Magisk and TWRP after any old reboot. Then you can use the OxygenOS updater to accept an official OTA update. It will recognize you're rooted and install an entire fresh new system to your inactive slot, which is exactly what we want.
There are two steps you need to perform before rebooting. The first is TWRP persistence and the second is Magisk persistence. For TWRP persistence you need to go into Magisk Manager and flash a module called "TWRP A/B retention script". Then for Magisk persistence you need to go install Magisk again, but this time to the inactive slot. You must do TWRP persistence first.
After this you should be good to go back to the update screen and hit reboot. You should still have TWRP and Magisk, but now on the very latest version of OxygenOS. Customize your phone to your heart's content now; it's all yours.
Recommended tweaks:
- install a Magisk module called "Debloater (Terminal Emulator)". Install a terminal emulator like Termux and use `su` to enter a root shell. Then you can run `debloat` and go through the list of apps, removing things you don't want. Certain services need to be watched out for, like PlayAutoInstallConfig (lets your carrier silently install apps without your consent). You can find tidbits online explaining what certain things do, like this pastebin, or this one. Houdini is the kernel driver which is very important.
- enable MagiskHide and hide yourself from Netflix and other DRM-enabled apps. Also hide yourself from Google Play's snet service.
- there is a Magisk module called F-Droid Privileged Extension, it's quite nice.
- use MagiskHide Props Config to set `net.tethering.noprovisioning=true`. This will prevent the carrier from knowing when you are using hotspot features, so they will not immediately cut your connection
- don't install a custom ROM. OxygenOS is high quality and everything you could ever want from a phone honestly. It has all the drivers and stuff for the phone and all of that cool stuff.
Small curiosities:
- SMT download mode is a special flashing mode used by the factory and it can overwrite things like the IMEI. Don't mess with it, you do not know what you're doing.
- Now that you have the software, you can literally just install a Dual SIM tray and have dual SIMs. Your phone is essentially the same as the international OP7P
- Feel free to post if you have any issues or need help with something.
Thank you mate. This will help out a lot of people coming to one plus such as myself. Only wonder I have about it all is the dual sim. I have 2 imei now but obviously both are the same. So I'm trying to figure out how that would work.
TheMadScientist said:
Thank you mate. This will help out a lot of people coming to one plus such as myself. Only wonder I have about it all is the dual sim. I have 2 imei now but obviously both are the same. So I'm trying to figure out how that would work.
Click to expand...
Click to collapse
Yeah, same here. Dual SIM phones are required to have two IMEI numbers since they technically have two transceivers, one for each SIM. Maybe one day someone will post a guide on how to change your IMEI numbers? You could keep one and change the other.
Today I had a little incident with SafetyNet.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had installed the magisk modules Riru and Riru - EdXposed. Big mistake. Uninstalling them didn't fix it. Reinstalling the OS didn't fix it. I thought I was totally ****ed. However, toggling MagiskHide off and back on again and clearing Google Play Services' data seems to have fixed it:
Phew. This SafetyNet guide really helped
EDIT: Also make sure to clear Play Store's data so it re-checks your device for certification.
LoganDark said:
Yeah, same here. Dual SIM phones are required to have two IMEI numbers since they technically have two transceivers, one for each SIM. Maybe one day someone will post a guide on how to change your IMEI numbers? You could keep one and change the other.
Click to expand...
Click to collapse
Unfortunately we can't discuss that on xda.
TheMadScientist said:
Unfortunately we can't discuss that on xda.
Click to expand...
Click to collapse
Software spoofing is allowed. EMS flashing is not.
Riru - EdXposed seems to pass SafetyNet if you use HiddenCore module (and DO NOT BLACKLIST GOOGLE SERVICES or else they will not get patched and they will fail you). I haven't checked to see how deep this goes. Perhaps third party apps which do their own SafetyNet check will see through it. Anyone here with experience?
Edit: BAD ADVICE DO NOT USE HIDDENCORE IT WILL BREAK SAFETYNET EVEN MORE
Well I got to say your guide it's good. But the part where you can only install twrp with magisk I got to say no there. All you have to do is use the roll back package and then update your phone with the first update it allows in system update. That should put you on Oxygen os android 10. Then fastboot will work. Did it myself so I know. Best regards
LokifiedMee said:
Well I got to say your guide it's good. But the part where you can only install twrp with magisk I got to say no there. All you have to do is use the roll back package and then update your phone with the first update it allows in system update. That should put you on Oxygen os android 10. Then fastboot will work. Did it myself so I know. Best regards
Click to expand...
Click to collapse
People seem to have mixed luck regarding using fastboot to boot TWRP. I understand upgrading the bootloader can enable additional fastboot capabilities which is why I tried it myself. It didn't work for me so that's why this guide takes the safer/guaranteed approach.
I did only upgrade to a later version of OOS 9, though. It added `fastboot boot` but trying it softlocked the phone.
Note that in either case, the OnePlus 7 Pro's recovery is stored in the boot partition, and flashing a zip using Magisk is easier than flashing one with TWRP.
I have revised the post to acknowledge the alternative method.
(Also, it's worth mentioning that I know anyone following this guide probably knows how to flash a zip in TWRP. I'm not saying that's too complicated, but the guide details the process I followed specifically. There are many other guides online detailing alternative methods, but they did not work for me, which is why I made this one.)
LoganDark said:
People seem to have mixed luck regarding using fastboot to boot TWRP. I understand upgrading the bootloader can enable additional fastboot capabilities which is why I tried it myself. It didn't work for me so that's why this guide takes the safer/guaranteed approach.
I did only upgrade to a later version of OOS 9, though. It added `fastboot boot` but trying it softlocked the phone.
Note that in either case, the OnePlus 7 Pro's recovery is stored in the boot partition, and flashing a zip using Magisk is easier than flashing one with TWRP.
I have revised the post to acknowledge the alternative method.
(Also, it's worth mentioning that I know anyone following this guide probably knows how to flash a zip in TWRP. I'm not saying that's too complicated, but the guide details the process I followed specifically. There are many other guides online detailing alternative methods, but they did not work for me, which is why I made this one.)
Click to expand...
Click to collapse
No worries mate. Just giving you the heads up. Cheers
I'm unsure how to flash twrp using magisk. I used a friend's machine to flash magisk last night but don't have access now. I'm waiting on asusurion to send mine back. I stayed on the beta and updated to the latest. Would flashing or booting into twrp be possible? Thanks for the guide, btw
Leskanic said:
I'm unsure how to flash twrp using magisk. I used a friend's machine to flash magisk last night but don't have access now. I'm waiting on asusurion to send mine back. I stayed on the beta and updated to the latest. Would flashing or booting into twrp be possible? Thanks for the guide, btw
Click to expand...
Click to collapse
Apologies for the late reply.
Download the "twrp-installer" zip file and use Magisk to flash it.
After that, you have to "direct install" Magisk again.
I guess my question is which option do i use in magisk to flash the twrp installer zip file? Do I use the install module from storage option or in the section where you patch files? Could i just use terminal emulator to boot into twrp then flash twrp and magisk while I'm in twrp? Sorry for my ignorance it's been a couple years since I've had Android with an unlocked bootloader and not having my laptop doesn't help
Leskanic said:
I guess my question is which option do i use in magisk to flash the twrp installer zip file? Do I use the install module from storage option or in the section where you patch files? Could i just use terminal emulator to boot into twrp then flash twrp and magisk while I'm in twrp? Sorry for my ignorance it's been a couple years since I've had Android with an unlocked bootloader and not having my laptop doesn't help
Click to expand...
Click to collapse
The TWRP installer zip is just a Magisk module that you can flash by going to the modules section and tapping "install from storage".
Basically, step 1: go into this section and install the twrp-installer zip this way
Step 2: go here
and direct install Magisk like this
Yes, you are installing Magisk again. That is because the TWRP installer overwrote it, and if you rebooted, you would lose root (and the stock ROM would immediately overwrite TWRP, leaving your device completely stock)
As for flashing both things via TWRP, you would probably flash TWRP first and then Magisk. If you can get the phone to boot into TWRP in the first place, yeah it's probably possible and many others have probably installed their TWRP+Magisk that way.
Thanks i didn't realize the twrp installer zip could be flashed as a module. Sorry it's been a while and I'm trying to get back up to speed
I have a few XPrivacyLua hooks that can be used to change your model number to GM1917 (at least to Java apps). It doesn't have any side effects except peace of mind.
Add these using the XPrivacyLua Pro companion app (you don't need to buy Pro to edit hooks), MAKE SURE to enter GM1917 in the model text box and save, enable them for every app including system apps in XPrivacyLua, and reboot.
Enjoy
LoganDark said:
For me, pwning my new phone was a 7-hour process that required incredible learning capacity. Not everyone is prepared to go through a process like that, and it can easily take multiple days or weeks. This is a guide outlining a version of the exact process that got me to this point. It should be easy for anyone to follow, even people without much technical knowledge. (although, do be careful with the resulting root access)
I started with a GM1915, which is the T-Mobile model. You'd think it would require an unlock key from T-Mobile in order to work, but actually it doesn't. That's what they don't want you to know.
A well-known method for bypassing that requirement is to install an international OS and then upgrade it to a certain developer preview, causing the phone to update the bootloader to a non-crippled version that doesn't require an unlock key. So that's what I did.
However, the process is easier said than done. For someone like me who's done it, it's not too hard, but for a beginner it's intensely confusing. I was a beginner just yesterday and struggled with dumb error messages like "packed image not exist".
The guide is below. Sections starting with "T-MOBILE ONLY" and ending with "END OF T-MOBILE ONLY" are only to be performed on T-Mobile phones with T-Mobile firmware and a locked bootloader. If you have an unlocked bootloader then you can skip those steps.
Make sure you have a Windows machine. The Qualcomm drivers are only available for Windows, the programs are only available for Windows, people on this forum only know Windows. I have a Mac, personally, because Unix is awesome, but unfortunately nobody has thought about us and all the tools are Windows-only. I am just as disappointed as you, trust me. I used a virtual machine, but YMMV, depending on how good your hypervisor's USB passthrough is. You may want to use bare metal if you only have VirtualBox; it's not worth the effort. You will be hot plugging A LOT, and your phone will show up as many different types of USB devices.
You must have fastboot installed, but ADB is not required.
--- T-MOBILE ONLY ---
Install the "L2 drivers" for the phone. You can find them here. Just install as many of them as you can by right-clicking every `.inf` file you find and clicking Install on each one of them. Some of them will have missing files. Some of them won't have a signature. It doesn't matter, as long as you try every one of them, something will work. For me it was the 64-bit driver, in the 64 folder. All the others are 32-bit.
--- END OF T-MOBILE ONLY ---
You should probably plug the phone into your computer now and install the official OnePlus drivers as well. This is so that you can easily access the phone storage, which will become very important soon. Reboot your computer to apply the driver updates.
--- T-MOBILE ONLY ---
Download the "MSM Download Tool" from here (same link as above). Place it in its own folder. This is crucial because you must now download the guacamole-whatever.7z file and extract the .ots file into the same folder as the MSM Download Tool.
MSM Download Tool always looks in its folder for the image and pops up a cryptic error message if it's not found ("packed image not exist"). This is not very widely documented because MSM Download Tool is often distributed in the same folder as the image anyway. That's not the case when you are forced to download them as separate files.
Note that this is the only time you will have to use MSM Download Tool and all other updates can be installed by the phone itself. On international variants you don't have to do this because the bootloader will already be unlockable, which is why this is T-Mobile only.
Start the MSM Downloader tool and make sure that it's open and ready. Uncheck the SHA-256 checkbox!
You need to start downloading two updates. The developer beta will upgrade the bootloader, and the full downgrade will give you a reference boot.img to use for Magisk. Start the downloads now, but you do not have to wait for them to finish yet; it will be a few steps before you have to use them.
Now is about the time to back up any data you want to keep. Everything on your phone will be wiped by the next step, including bootloader unlock status, all your data, the entire operating system and so on.
Unplug your USB cable and THEN turn off your phone completely. If the USB cable is plugged in while it's turned off, it will automatically boot into the charging mode which is not what you want. Have your USB cable, and computer mouse, on the ready. You don't want to waste any time, because this may be physically painful: Hold down both volume buttons at the same time for at least 5 seconds, and then plug the USB cable into your phone. Make sure some COM port appears in the tool, then click the "Start" button in MSM Download Tool WHILE STILL HOLDING THEM DOWN. You can only let the volume buttons go AFTER you click "Start", or else the phone will drop out of MSM mode.
The process will take a few minutes depending on how fast your USB connection is. Leave the phone plugged in until it is complete. This also gives time to download those two updates, which are together about four gigabytes in size.
Once MSM Download Tool is done flashing, you can reboot the phone and set it up using the setup wizard. This one will be overwritten, so feel free to move fast and enable nothing. You don't need internet, you don't need a correct clock, you don't need accounts or telemetry or anything like that. All data will be wiped again later.
Use your computer to copy both updates (developer preview & rollback) to the phone. Don't copy them to the Download folder or anything, copy them into the root. Go to settings > local updates > settings icon in the top right > local update and update to the developer preview.
Once you're in the developer preview, enable OEM unlocking in developer options, reboot into fastboot mode (I do this by also enabling advanced reboot in developer options) and use `fastboot oem unlock`. Your bootloader is now unlocked! But we're not nearly done yet, there's still lots to do.
Go to local update again and use the rollback. This is required in order to go back to a stable OS that can accept OTAs. After this your data will be wiped. This is the real setup wizard. You can set it up with real data; your data will not be wiped again for the rest of this guide.
--- END OF T-MOBILE ONLY ---
If your bootloader is not already unlocked, enable OEM unlocking in developer options and then run `fastboot oem unlock` in Fastboot mode.
Next, you will want to install Magisk. This is a slightly complex process but once it's done your phone will become fully untethered.
First download a tool called Payload Dumper. Extract the entire archive into its own folder. Get an OTA update for your version of OxygenOS (if your phone is T-Mobile, that is the rollback update you just installed; if you aren't following the T-Mobile guide, you may have to download an OTA update from Google), and use WinRAR or similar to extract the `payload.bin` inside into the payload dumper's input folder.
Run the payload dumper. You don't need to run all of it; wait for "boot" to show up in the console window, then wait until something else shows up and then close the window. Inside the output folder there should be a `boot.img`; there may be other img files but the boot is what we're interested in.
Transfer this boot.img to your device and use Magisk Manager to patch it. Transfer the magisk_patched.img to your computer, reboot the phone into fastboot mode and use `fastboot flash boot magisk_patched.img`. Reboot the phone into Android.
If you start Magisk Manager you should see that Magisk is installed. Great. Next step is to install TWRP.
In my experience, flashing TWRP or using `fastboot boot twrp.img` didn't work. You're not clever if you try installing OxygenOS 9.5.4 which adds `fastboot boot` support to the bootloader; it still won't work. In my experience the only correct way to install TWRP on the OnePlus 7 Pro is to use Magisk.
(Someone in the replies below stated that you need to upgrade all the way to OOS 10 in order to boot TWRP using fastboot. This guide details the easier method using Magisk Manager.)
On the phone, go to the TWRP downloads page for the OnePlus 7 Pro, and download the latest installer. Then flash the zip using Magisk.
Crucially, at the end of the installer log it says "you are now unrooted". DO NOT IGNORE THIS MESSAGE! If you reboot now, Magisk will be gone and the stock ROM will immediately overwrite TWRP. You must use Magisk Manager to reinstall Magisk using a "Direct Install". That way, your boot.img will be patched again and your Magisk (and TWRP) will persist across reboots.
Go ahead and try it out. Reboot a few times, sometimes into recovery, sometimes into Android to test Magisk.
We're still not done yet. Wouldn't you love to stay rooted and still be running the latest version of OxygenOS? I sure would. Next I'll describe the process of applying an OTA update while keeping your root and everything. Thanks to A/B you can stay untethered.
Please note that, if you'd like to proceed with the EU version of OxygenOS, you should go grab 9.5.4 before proceeding to the next step, for example from here, and use local update to install it. (note GM27BA instead of GM27AA) The EU version is supposed to have better privacy options and less bloatware, so that's what I personally went with. Converting your OxygenOS from GM27AA to GM27BA has no harmful side effects and should work on any phone. It affects the OTA you'll receive in the next step, and this is possibly the only chance you'll get to switch (or not). So choose wisely.
Remember to turn off all auto-updating in the OxygenOS settings. You don't want your phone suddenly losing Magisk and TWRP after any old reboot. Then you can use the OxygenOS updater to accept an official OTA update. It will recognize you're rooted and install an entire fresh new system to your inactive slot, which is exactly what we want.
There are two steps you need to perform before rebooting. The first is TWRP persistence and the second is Magisk persistence. For TWRP persistence you need to go into Magisk Manager and flash a module called "TWRP A/B retention script". Then for Magisk persistence you need to go install Magisk again, but this time to the inactive slot. You must do TWRP persistence first.
After this you should be good to go back to the update screen and hit reboot. You should still have TWRP and Magisk, but now on the very latest version of OxygenOS. Customize your phone to your heart's content now; it's all yours.
Recommended tweaks:
- install a Magisk module called "Debloater (Terminal Emulator)". Install a terminal emulator like Termux and use `su` to enter a root shell. Then you can run `debloat` and go through the list of apps, removing things you don't want. Certain services need to be watched out for, like PlayAutoInstallConfig (lets your carrier silently install apps without your consent). You can find tidbits online explaining what certain things do, like this pastebin, or this one. Houdini is the kernel driver which is very important.
- enable MagiskHide and hide yourself from Netflix and other DRM-enabled apps. Also hide yourself from Google Play's snet service.
- there is a Magisk module called F-Droid Privileged Extension, it's quite nice.
- use MagiskHide Props Config to set `net.tethering.noprovisioning=true`. This will prevent the carrier from knowing when you are using hotspot features, so they will not immediately cut your connection
- don't install a custom ROM. OxygenOS is high quality and everything you could ever want from a phone honestly. It has all the drivers and stuff for the phone and all of that cool stuff.
Small curiosities:
- SMT download mode is a special flashing mode used by the factory and it can overwrite things like the IMEI. Don't mess with it, you do not know what you're doing.
- Now that you have the software, you can literally just install a Dual SIM tray and have dual SIMs. Your phone is essentially the same as the international OP7P
- Feel free to post if you have any issues or need help with something.
Click to expand...
Click to collapse
It isn't very clear what version of OOS you started on. If I'm running OOS10 on stock this should still (in theory) work right?
r4w0ne said:
It isn't very clear what version of OOS you started on. If I'm running OOS10 on stock this should still (in theory) work right?
Click to expand...
Click to collapse
OOPS, fuck, I missed a step. You have to use MSM Download Tool to clean install this patched OOS before installing the developer preview. I'll update the post ASAP
Edit: Post has been updated
LoganDark said:
OOPS, ****, I missed a step. You have to use MSM Download Tool to clean install this patched OOS before installing the developer preview. I'll update the post ASAP
Click to expand...
Click to collapse
Glad I asked lol.
r4w0ne said:
Glad I asked lol.
Click to expand...
Click to collapse
I actually mentioned installing international OOS in the post but for some reason I didn't link it or provide instructions. Silly me...
Edit: Post has been updated
LoganDark said:
I actually mentioned installing international OOS in the post but for some reason I didn't link it or provide instructions. Silly me...
Edit: Post has been updated
Click to expand...
Click to collapse
New problem, OEM unlocking is greyed out in the options on the developer preview...
EDIT: I'm a retard and didn't follow instructions. Ignore.
I have a Pixel 5 and today I updated from redfin-2110-rq3a.211001.001-factory-23f4cec2 to redfin-2111-sp1a.211105.004-factory-749e8f9f (yes the Aus version).
All went well until I tried to root the device using Magisk - something I've done *many* times. The trouble is that after I flashed the patched boot.img, the device would not boot - it started to for a few seconds and then went back into fastboot mode.
I've tried a few times but always the same result.
And it seems that you cannot rollback to the October release - the flash-all.sh completes OK but the subsequent boot hangs.
BTW: I'm still using the canary channel, is this still necessary?
Help.
Was that an update from A11 to A12? If so you're gonna have to jump through some hoops...
Either way, this is very likely not a Magisk issue, but caused by some new verification stuff in Android 12, so the best place for you to find info/help is going to be in your device's forum.
Upgrade was from the October version, so, to the best of my knowledge, Android 12
Still, you're likely going to find the answer in the Pixel 5 forums...
Hello everyone, i just tried updating to the latest ota on android 13 on a rooted 10 pro using the incremental magisk method and now my phone is bricked. wondering if there is a way to recover without losing data. Phone can boot into fastboot, anything else results in Qualcomm Crashdump mode being displayed on screen. ive connected to a computer and it registers when i type fastboot devices, from that point im pretty much stuck on next steps
I did the same mistake thinking it would work like it would on A12 and ended up sending it in to oneplus to reflash.
In my case I have a NE2215 converted to NE2213, what version are you? Full NE2215?
unsafe8989 said:
In my case I have a NE2215 converted to NE2213, what version are you? Full NE2215?
Click to expand...
Click to collapse
yes full ne2215. quite sad knowing we don't even have proper access to the tools to recover our own phones yet. luckily i kept my op8 for a situation like this.
ltw5ki said:
Hello everyone, i just tried updating to the latest ota on android 13 on a rooted 10 pro using the incremental magisk method and now my phone is bricked. wondering if there is a way to recover without losing data. Phone can boot into fastboot, anything else results in Qualcomm Crashdump mode being displayed on screen. ive connected to a computer and it registers when i type fastboot devices, from that point im pretty much stuck on next steps
Click to expand...
Click to collapse
you are sol. i already told you guys that you'll brick your phone if you use magisk method when updating os versions.
ltw5ki said:
Hello everyone, i just tried updating to the latest ota on android 13 on a rooted 10 pro using the incremental magisk method and now my phone is bricked. wondering if there is a way to recover without losing data. Phone can boot into fastboot, anything else results in Qualcomm Crashdump mode being displayed on screen. ive connected to a computer and it registers when i type fastboot devices, from that point im pretty much stuck on next steps
Click to expand...
Click to collapse
If you did unroot completely you can try to boot into EDL mode, in doing so I managed to flip the boot slot and get mine to boot when I was stuck in crashdump mode.
I updated to C.20 yesterday. The process is to unroot completely with image restore, reboot, then let the the update fully install and reboot. You will update fine but be unrooted. Then you boot a patched boot from bootloader and root directly from Magisk.
Do not forget the reboot after uninstalling Magisk before updating.
I already called op to start the repair process. I am willing to try the edl method in a last ditch effort. Is there a detailed explanation on how to get into edl and the process to flip the boot slot?
ltw5ki said:
I already called op to start the repair process. I am willing to try the edl method in a last ditch effort. Is there a detailed explanation on how to get into edl and the process to flip the boot slot?
Click to expand...
Click to collapse
I'm genuinely not sure how to flip the slot on purpose, it happened to me while I was trying the button combination for EDL mode. I believe you have hold all three buttons (Power, Vol Up&Down) until it restarts, it should vibrate but be a black screen and you can plug the USB in from there to see a port 9008 on the PC. This is very generalized but there are more details all around the forum here.
I will say I believe when it flipped, it booted and I saw the oneplus screen for a split second, the screen sort of glitched, and it immediately rebooted from black screen back to bootloader. I think the switch occurred then.
Also is that from a powered off state or is it possible to do with the phone being on?
Hmmm... I can get into bootloader okay and even launch recovery, but I can't seem to switch the partitions. I contacted support, they can replace the phone, but can't or won't tell me how to switch partitions or load it manually.
Quantumrabbit said:
Hmmm... I can get into bootloader okay and even launch recovery, but I can't seem to switch the partitions. I contacted support, they can replace the phone, but can't or won't tell me how to switch partitions or load it manually.
Click to expand...
Click to collapse
If you can get into bootloader, can you try to fastboot boot a boot image? Does that also lead to a qualcomm crashdump?
Prant said:
If you can get into bootloader, can you try to fastboot boot a boot image? Does that also lead to a qualcomm crashdump?
Click to expand...
Click to collapse
The problem is I don't know if I have any fastbootable images... I have the C19 full zip... would that work to try and fastboot it? Do I fastboot just the C19 bootloader?
I'm not used to being in the situation I'm in right now
Quantumrabbit said:
The problem is I don't know if I have any fastbootable images... I have the C19 full zip... would that work to try and fastboot it? Do I fastboot just the C19 bootloader?
I'm not used to being in the situation I'm in right now
Click to expand...
Click to collapse
Just take a step back and don't do anything rash. Absolutely do not FLASH anything in fastboot, but there are numerous guides around here. You basically want to extract the boot.img from that full upgrade zip's payload.bin file, easiest way being with FastbootEnhance, then use command 'fastboot boot "boot.img"' while you're on bootloader. I'm not sure if this will boot your phone, but it definitely can not damage it as long as you're just booting, so it's worth a shot.
Prant said:
Just take a step back and don't do anything rash. Absolutely do not FLASH anything in fastboot, but there are numerous guides around here. You basically want to extract the boot.img from that full upgrade zip's payload.bin file, easiest way being with FastbootEnhance, then use command 'fastboot boot "boot.img"' while you're on bootloader. I'm not sure if this will boot your phone, but it definitely can not damage it as long as you're just booting, so it's worth a shot.
Click to expand...
Click to collapse
Hey man I'd like to poke at your brain if you don't mind, so I did the same thing as quantumrabbit, didn't reboot after unrooting and got the same issue. My problem was my dumba** tried to follow one of the fastboot guides to try and recover my phone and boy let me tell you I bricked my phone harder then I've ever bricked a phone lol. Anyway I got into contact with OP shipped them the phone, they claim to have repaired it and it should get back to me tomorrow, overall took 2 weeks. I want to avoid doing in this future as root is a must for me, before the 10 Pro I had a 6T. Whenever I was on that device from OOS 9,10 & 11 and custom roms after the update support was over, I was always able to unroot without rebooting, flash the full OTA zip and then install magisk to the next inactive slot. It would work and I would retain root. When I got my 10 Pro, for the first 4 updates that came out for the NE2215 where only incremental. So my method was unroot with no reboot, install the incremental ota, then install root to inactive slot and it worked some how even being incremental updates and without the reboot. Well then, I then converted my NE2215 to a NE2213 using the rollback package, and then update normally until C19 released where I fully unrooted and even factory reset for the OS jump from A12 to A13. C20 came out, and this is where I tried the same stupid method, unroot with no reboot, install full OTA zip, then flash magisk to the inactive slot, this then immediately gave the Qualcomm error people are getting. My question is, is that reboot mandatory and should it always be done, since I never had a issue before hand it slipped my mind. I hope you understand what I'm trying to ask, basically I want to avoid this issue in the future especially with no MSM and OP taking their sweet time to fix my phone, should I always completely unroot and reboot for absolutely any OTA and just manually root again by booting the boot image I'm pretty sure that's a no brainer "yes" to my question but more or less I wanna know what changed from Android 12 where I was able to use the un-recommended method with 4 consecutively updates on NE2215 and about 2 of them on NE2213 after converting. I'd like your insight on why it should be done the correct way and what issues arise etc as you seem knowledgeable. Also the possibilities on how to recover, I saw your solution where you recommend booting a boot image to see if that would work, didn't even cross my mind but I think that would've been the correct approach instead of jumping straight into fastboot flashing like my dumb self did. Thank you!
unsafe8989 said:
Hey man I'd like to poke at your brain if you don't mind, so I did the same thing as quantumrabbit, didn't reboot after unrooting and got the same issue. My problem was my dumba** tried to follow one of the fastboot guides to try and recover my phone and boy let me tell you I bricked my phone harder then I've ever bricked a phone lol. Anyway I got into contact with OP shipped them the phone, they claim to have repaired it and it should get back to me tomorrow, overall took 2 weeks. I want to avoid doing in this future as root is a must for me, before the 10 Pro I had a 6T. Whenever I was on that device from OOS 9,10 & 11 and custom roms after the update support was over, I was always able to unroot without rebooting, flash the full OTA zip and then install magisk to the next inactive slot. It would work and I would retain root. When I got my 10 Pro, for the first 4 updates that came out for the NE2215 where only incremental. So my method was unroot with no reboot, install the incremental ota, then install root to inactive slot and it worked some how even being incremental updates and without the reboot. Well then, I then converted my NE2215 to a NE2213 using the rollback package, and then update normally until C19 released where I fully unrooted and even factory reset for the OS jump from A12 to A13. C20 came out, and this is where I tried the same stupid method, unroot with no reboot, install full OTA zip, then flash magisk to the inactive slot, this then immediately gave the Qualcomm error people are getting. My question is, is that reboot mandatory and should it always be done, since I never had a issue before hand it slipped my mind. I hope you understand what I'm trying to ask, basically I want to avoid this issue in the future especially with no MSM and OP taking their sweet time to fix my phone, should I always completely unroot and reboot for absolutely any OTA and just manually root again by booting the boot image I'm pretty sure that's a no brainer "yes" to my question but more or less I wanna know what changed from Android 12 where I was able to use the un-recommended method with 4 consecutively updates on NE2215 and about 2 of them on NE2213 after converting. I'd like your insight on why it should be done the correct way and what issues arise etc as you seem knowledgeable. Also the possibilities on how to recover, I saw your solution where you recommend booting a boot image to see if that would work, didn't even cross my mind but I think that would've been the correct approach instead of jumping straight into fastboot flashing like my dumb self did. Thank you!
Click to expand...
Click to collapse
your jumping around probably screwed up some partition size. I did not restart for the c20 ota and have no issues.
unsafe8989 said:
Hey man I'd like to poke at your brain if you don't mind, so I did the same thing as quantumrabbit, didn't reboot after unrooting and got the same issue. My problem was my dumba** tried to follow one of the fastboot guides to try and recover my phone and boy let me tell you I bricked my phone harder then I've ever bricked a phone lol. Anyway I got into contact with OP shipped them the phone, they claim to have repaired it and it should get back to me tomorrow, overall took 2 weeks. I want to avoid doing in this future as root is a must for me, before the 10 Pro I had a 6T. Whenever I was on that device from OOS 9,10 & 11 and custom roms after the update support was over, I was always able to unroot without rebooting, flash the full OTA zip and then install magisk to the next inactive slot. It would work and I would retain root. When I got my 10 Pro, for the first 4 updates that came out for the NE2215 where only incremental. So my method was unroot with no reboot, install the incremental ota, then install root to inactive slot and it worked some how even being incremental updates and without the reboot. Well then, I then converted my NE2215 to a NE2213 using the rollback package, and then update normally until C19 released where I fully unrooted and even factory reset for the OS jump from A12 to A13. C20 came out, and this is where I tried the same stupid method, unroot with no reboot, install full OTA zip, then flash magisk to the inactive slot, this then immediately gave the Qualcomm error people are getting. My question is, is that reboot mandatory and should it always be done, since I never had a issue before hand it slipped my mind. I hope you understand what I'm trying to ask, basically I want to avoid this issue in the future especially with no MSM and OP taking their sweet time to fix my phone, should I always completely unroot and reboot for absolutely any OTA and just manually root again by booting the boot image I'm pretty sure that's a no brainer "yes" to my question but more or less I wanna know what changed from Android 12 where I was able to use the un-recommended method with 4 consecutively updates on NE2215 and about 2 of them on NE2213 after converting. I'd like your insight on why it should be done the correct way and what issues arise etc as you seem knowledgeable. Also the possibilities on how to recover, I saw your solution where you recommend booting a boot image to see if that would work, didn't even cross my mind but I think that would've been the correct approach instead of jumping straight into fastboot flashing like my dumb self did. Thank you!
Click to expand...
Click to collapse
Yeah, flashing on this device is a big no go until we get proper recovery tools. 9 times out of 10 you'll make things worse.
While you have people like @g96818 that don't use the full reboot, PC method; when I tried to use that method for C.19, I was the one stuck in qualcomm crash dump last month. When I posted I was informed that with this device, especially since Android 13, doing the incremental systemflash then trying to install magisk to inactive *CAN* leave some weird errors in the system update process.
Either way, for me personally, after that big a scare. I will always update using the full uninstall Magisk with restore images, reboot, flash system update, let it do its thing, then root again using a magisk patched boot image, which is super simple to do. You can use cross region boots, as in 2213 on 2215, done that the past two times. Just remember to never flash, only boot.
Appreciate your guys input, I'll make sure to be extra cautious! Phone comes in today, fingers crossed I successfully update to C20 and root! Lol.
Prant said:
Yeah, flashing on this device is a big no go until we get proper recovery tools. 9 times out of 10 you'll make things worse.
While you have people like @g96818 that don't use the full reboot, PC method; when I tried to use that method for C.19, I was the one stuck in qualcomm crash dump last month. When I posted I was informed that with this device, especially since Android 13, doing the incremental systemflash then trying to install magisk to inactive *CAN* leave some weird errors in the system update process.
Either way, for me personally, after that big a scare. I will always update using the full uninstall Magisk with restore images, reboot, flash system update, let it do its thing, then root again using a magisk patched boot image, which is super simple to do. You can use cross region boots, as in 2213 on 2215, done that the past two times. Just remember to never flash, only boot.
Click to expand...
Click to collapse
One last question, do you remove all your modules first reboot then unroot and reboot?
Prant said:
Yeah, flashing on this device is a big no go until we get proper recovery tools. 9 times out of 10 you'll make things worse.
While you have people like @g96818 that don't use the full reboot, PC method; when I tried to use that method for C.19, I was the one stuck in qualcomm crash dump last month. When I posted I was informed that with this device, especially since Android 13, doing the incremental systemflash then trying to install magisk to inactive *CAN* leave some weird errors in the system update process.
Either way, for me personally, after that big a scare. I will always update using the full uninstall Magisk with restore images, reboot, flash system update, let it do its thing, then root again using a magisk patched boot image, which is super simple to do. You can use cross region boots, as in 2213 on 2215, done that the past two times. Just remember to never flash, only boot.
Click to expand...
Click to collapse
Technically that's on you. I gave a warning that you will brick if you don't fully unroot for c19.
Quantumrabbit said:
The problem is I don't know if I have any fastbootable images... I have the C19 full zip... would that work to try and fastboot it? Do I fastboot just the C19 bootloader?
I'm not used to being in the situation I'm in right now
Click to expand...
Click to collapse
I posted the c20 boots and how to flip the boot so go try it out.
Hey there,
almost a year ago i rooted my device, tried it for a bit and then realized that i cant use my creditcard app without doing some weird stuff.
so i decided to unroot. everything worked. Now after a long time i wanted to do a normal system update to MIUI 13, but everytime i try to start the update using the devices updater,
i get a dialog saying something like "You device supports seamless system updates. Remember to select Slot A when you get prompted by TWRP" (roughly translated, its in german). I dont really understand why my device is still knowing that i user twrp, even after i removed it and reflashed the original fastboot thingy. (im not too familiar with all the rooting stuff)
I tried to flash again to twrp from my computer and install the update that way but that comes with its own problems and i would prefer to use the system updater rather than twrp.
Does any one have an idea why i get the meantioned dialog and how i can get rid of it to let it update normally?
I just realized that the updater is downloading a file called "xiaomi.eu_multi_HMK40Pro_Mi11i_V14 ... .zip". that looks like some unofficial rom to me, is it pulling it from somewhere else rather than the official xiamo servers maybe?
im really lost at this point.
sorry for some broken english here and there
it also says something about my system being encrypted and that i need to enter a password which never happens.
If it's fetching Xiaomi.eu rom that means you changed the rom from stock to the custom made EU version. If you did not, that most likely means that your device was originally the China version and the seller installed the EU version to provide you with the Google/Play Services.
In short: You are not using the official stock rom. Please post screenshots from your About Phone.