I updated to android 10 an hour ago, and placed my phone into the bootloader so I could re-flash TWRP. After I ran the command (fastboot flash boot C:\Users\USER\Downloads\twrp-3.3.1-4-guacamole.img), and tried rebooting, I couldn't leave the bootloader. I've tried using the buttons, trying to push the img to the phone and force it into TWRP, but nothing works. I think I didn't enable USB debugging when I entered the bootloader, but it was enabled before I updated.
It's a known issue, the commands aren't included in the bootloader for q yet. We need to wait for OnePlus to add them. To fix your problem, try fastboot booting the magisk patched boot.img for the 10 beta.
USB Debugging has nothing to do with fastboot.... Just flash stock boot img or a patched with twrp/magisk and boot your phone usually
mercenaryhmster said:
It's a known issue, the commands aren't included in the bootloader for q yet. We need to wait for OnePlus to add them. To fix your problem, try fastboot booting the magisk patched boot.img for the 10 beta.
Click to expand...
Click to collapse
Where do I find the patched boot image?
TheEndernaut said:
Where do I find the patched boot image?
Click to expand...
Click to collapse
If nothing helps, try to reflash with MsmDownloadTool.
TheEndernaut said:
Where do I find the patched boot image?
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Also, once you flashed boot image and booted into Android, Download the twrp INSTALLER and install it via magisk module
From here
https://www.androidfilehost.com/?fid=1899786940962578045
GUGUITOMTG4 said:
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Also, once you flashed boot image and booted into Android, Download the twrp INSTALLER and install it via magisk module
From here
https://www.androidfilehost.com/?fid=1899786940962578045
Click to expand...
Click to collapse
Was able to get past the bootloader, but once I swipe up to load the device, it blacks out
GUGUITOMTG4 said:
https://forum.xda-developers.com/on...isk-patched-boot-image-oneplus-7-pro-t3964345
Also, once you flashed boot image and booted into Android, Download the twrp INSTALLER and install it via magisk module
From here
https://www.androidfilehost.com/?fid=1899786940962578045
Click to expand...
Click to collapse
I can't find the menue in magisk manager where I can install TWRP
TheEndernaut said:
I can't find the menue in magisk manager where I can install TWRP
Click to expand...
Click to collapse
Hamburger (upper left), modules, plus icon (bottom center), browse to twrp installer zip.
TheEndernaut said:
I updated to android 10 an hour ago, and placed my phone into the bootloader so I could re-flash TWRP. After I ran the command (fastboot flash boot C:\Users\USER\Downloads\twrp-3.3.1-4-guacamole.img), and tried rebooting, I couldn't leave the bootloader. I've tried using the buttons, trying to push the img to the phone and force it into TWRP, but nothing works. I think I didn't enable USB debugging when I entered the bootloader, but it was enabled before I updated.
Click to expand...
Click to collapse
First you don't flash the TWRP image.
That image is used as a fastboot boot. It is not to be flashed.
Normally, you would boot with that image and flash the TWRP zip to make it permanent.
Once TWRP is flashed, you need to also flash Magisk.
To get out of the situation you are in, you need a stock boot image to flash.
Once that is done, you can start over.
Read the instructions carefully before flashing images.
johnx818 said:
Hamburger (upper left), modules, plus icon (bottom center), browse to twrp installer zip.
Click to expand...
Click to collapse
There is no modules page
johnx818 said:
Hamburger (upper left), modules, plus icon (bottom center), browse to twrp installer zip.
Click to expand...
Click to collapse
There is no modules menu
tech_head said:
First you don't flash the TWRP image.
That image is used as a fastboot boot. It is not to be flashed.
Normally, you would boot with that image and flash the TWRP zip to make it permanent.
Once TWRP is flashed, you need to also flash Magisk.
To get out of the situation you are in, you need a stock boot image to flash.
Once that is done, you can start over.
Read the instructions carefully before flashing images.
Click to expand...
Click to collapse
Just to clarify then, when I run fastboot flash boot TWRP, I use the zip? If not, what command am I using?!
The command is "fastboot boot recoveryfilaneme.img" using the .img file
TheEndernaut said:
Just to clarify then, when I run fastboot flash boot TWRP, I use the zip? If not, what command am I using?!
Click to expand...
Click to collapse
No, no, no.
TWRP can only be flashed from either TWRP or Magisk.
On this device, you can only boot the image file. You can only flash the zip while running a booted TWRP or from the Magisk Manager.
TheEndernaut said:
Just to clarify then, when I run fastboot flash boot TWRP, I use the zip? If not, what command am I using?!
Click to expand...
Click to collapse
Hope I can explain myself. You are using a command you shouldn't be using: fastboot FLASH boot, you shouldn't flash the image from fastboot, you need to use that image to boot into recovery and then flash recovery itself from INSIDE recovery, then you NEED to flash Magisk from inside recovery too.
The command is: fastboot boot recovery.img
Btw, you can't see the "modules" option in Magisk because I think you flashed stock boot.img. Try flashing Magisk patched boot img and then flash recovery in Magisk as it was said before.
Did you click all the 3 buttons at once?
TheEndernaut said:
After I ran the command (fastboot flash boot C:\Users\USER\Downloads\twrp-3.3.1-4-guacamole.img)
Click to expand...
Click to collapse
This is not a command you will find in any guide for this device (at least not any guide that is correct)!
The command you used, flashed the image to over-write the boot partition, which is essentially the kernel. You no longer have a kernel, so of course the phone cannot properly boot to OS. This is also not the correct way to install TWRP, so therefore you have no TWRP installed on the phone, either.
Proper sequence to install TWRP would have been:
1) fastboot boot TWRP.img
This only "boots" into TWRP, but does not install it. I know the syntax here is confusing. "boot" versus "flash boot" do completely different things. In this case "boot" is the action. In the command you used "flash" is the action, and the "boot" partition is the location.
2) Flash TWRP installer zip
3) Flash Magisk
At this point, the easiest path is probably to do what was suggested in Reply #6 above (flash patched boot image, boot to OS, open Magisk and install TWRP from Magisk).
redpoint73 said:
This is not a command you will find in any guide for this device (at least not any guide that is correct)!
The command you used, flashed the image to over-write the boot partition, which is essentially the kernel. You no longer have a kernel, so of course the phone cannot properly boot to OS. This is also not the correct way to install TWRP, so therefore you have no TWRP installed on the phone, either.
Proper sequence to install TWRP would have been:
1) fastboot boot TWRP.img
This only "boots" into TWRP, but does not install it. I know the syntax here is confusing. "boot" versus "flash boot" do completely different things. In this case "boot" is the action. In the command you used "flash" is the action, and the "boot" partition is the location.
2) Flash TWRP installer zip
3) Flash Magisk
At this point, the easiest path is probably to do what was suggested in Reply #6 above (flash patched boot image, boot to OS, open Magisk and install TWRP from Magisk).
Click to expand...
Click to collapse
How do you install TWRP from Magisk?
blade35 said:
How do you install TWRP from Magisk?
Click to expand...
Click to collapse
Magisk/Modules/+/Select TWRP installer.zip
Related
Helloguys and gals,
I just got a Pixel 3 and wanted to root it. I followed this guide: https://www.youtube.com/watch?v=BgV1xxkcBk8
I installed the latest TWRP recovery (didn't keep it read only, maybe this was a mistake?). After that I installed Magisk which was followed by a bootloop.
To fix the bootloop I used TWRPs fix bootloop fix which worked. But that makes Magisk undone.
So my Questions is how to install Magisk? Do I need to flash the stock image on both slots and start again? Is the guide outdated? If so, which guide should I follow?
Edit: My phone is still on the update from November 2018.
On A/B devices there is no dedicated recovery partition anymore, recovery is contained in the boot partition, so if you install Magisk it's advised not to install TWRP on those devices anymore to avoid both modifying the same image, but instead to always fastboot boot when you need to use TWRP.
These are the steps I follow every time I need to factory reset then root my own Pixel 3 :
Boot to bootloader
Flash stock image on current slot
Flash stock image on other slot
Boot the system, enable Developer options and USB debugging
Fastboot boot TWRP image
Backup Boot partition
Flash Magisk
[optional] Flash custom kernel (check flashing order depending on kernel)
Reboot
bafforosso said:
On A/B devices there is no dedicated recovery partition anymore, recovery is contained in the boot partition, so if you install Magisk it's advised not to install TWRP on those devices anymore to avoid both modifying the same image, but instead to always fastboot boot when you need to use TWRP.
These are the steps I follow every time I need to factory reset then root my own Pixel 3 :
Boot to bootloader
Flash stock image on current slot
Flash stock image on other slot
Boot the system, enable Developer options and USB debugging
Fastboot boot TWRP image
Backup Boot partition
Flash Magisk
[optional] Flash custom kernel (check flashing order depending on kernel)
Reboot
Click to expand...
Click to collapse
Allright, thank you for your explanation! I used the stock image and the flash-all.bat to install the stock image. Will it be enough since you are speaking of two different slots? if not, how can i do both slots?
thx in advance
I run twrp as the devices recovery and have magisk. I would follow the twrp and magisk guides for this device. First boot twrp then use the installer, second reboot, third get to recovery and flash magisk. The boot partition needs to be rebooted before root. It is an initialization thing. Get twrp, reboot, magisk.
Having a similar issue here. I was rooted till the latest OTA happened a few days ago. Trying to re-root in several different ways, but all result in boot loop.
Methods I've tried:
Extracted boot.img from factory image, patched with Magisk Manager, flashed with fastboot
Fastboot boot twrp-3.3.0-0-blueline.img, installed Magisk-v19.3.zip
Fastboot boot twrp-3.3.0-0-blueline.img, installed twrp-pixel3-installer-blueline-3.3.0-0.zip, rebooted recovery, installed Magisk-v19.3.zip
Any ideas?
levibuko said:
Allright, thank you for your explanation! I used the stock image and the flash-all.bat to install the stock image. Will it be enough since you are speaking of two different slots? if not, how can i do both slots?
thx in advance
Click to expand...
Click to collapse
I tinker a lot with my phone so I usually want to have both slots clean flashed when I start back from scratch, not sure that is really necessary, but here are the steps I use for flashing both slots :
Code:
fastboot getvar current-slot
./flash-all.sh
fastboot --set-active=x (x being a or b, the other slot than the one you get with the fastboot getvar command)
./flash-all.sh
Exactly the same issue here, no luck. I'm only able to boot if I flash the stock boot.img. However, no root.
---------- Post added at 08:00 PM ---------- Previous post was at 07:52 PM ----------
tenthousandfeet said:
Having a similar issue here. I was rooted till the latest OTA happened a few days ago. Trying to re-root in several different ways, but all result in boot loop.
Methods I've tried:
Extracted boot.img from factory image, patched with Magisk Manager, flashed with fastboot
Fastboot boot twrp-3.3.0-0-blueline.img, installed Magisk-v19.3.zip
Fastboot boot twrp-3.3.0-0-blueline.img, installed twrp-pixel3-installer-blueline-3.3.0-0.zip, rebooted recovery, installed Magisk-v19.3.zip
Any ideas?
Click to expand...
Click to collapse
Exactly the same issue here, no luck. I'm only able to boot if I flash the stock boot.img. However, no root.
Boot twrp and install it, then reboot to system, then reboot recovery and install magisk. You need to boot system before installing magisk.
wangdaning said:
Boot twrp and install it, then reboot to system, then reboot recovery and install magisk. You need to boot system before installing magisk.
Click to expand...
Click to collapse
Tried that. No success.
Only thing I can think is to install an older magisk then let it update. I originally installed 18 something and have just let it update. I do not use google's factory image though, so cannot really help troubleshoot.
wangdaning said:
Only thing I can think is to install an older magisk then let it update. I originally installed 18 something and have just let it update. I do not use google's factory image though, so cannot really help troubleshoot.
Click to expand...
Click to collapse
I had a similar thought, but no dice. Tried installing Magisk 19.2, which boot looped just like the latest 19.3.
I even went back to 16.7, and though that one didn't boot loop it also didn't show up in the system. Magisk Manager didn't recognize it, anyway.
Though I'm loathe to do a full wipe/reset and then reconfigure all my junk, I may be headed in that direction as I'm running out of other ideas. Perhaps I'll save a backup just before that I can return to if the reset is fruitless.
---------- Post added at 07:53 AM ---------- Previous post was at 07:36 AM ----------
Magisk 18.0 does the same as 16.7 - no bootloop, but no root.
Interestingly, I noticed that the 18.0 and 16.7 zip installers say something about the partition being boot_a, whereas the bootlooping 19.2 and 19.3 zip installers say it's boot_b.
Run the Magisk uninstaller. Flash boot.img to both slots. Do a flash-all (minus the -w). With those things done, you should be essentially at reset state for this problem.
sliding_billy said:
Run the Magisk uninstaller. Flash boot.img to both slots. Do a flash-all (minus the -w). With those things done, you should be essentially at reset state for this problem.
Click to expand...
Click to collapse
Done. Followed that up with a TWRP flash of Magisk 19.2. Then... bootloop! Arg.
tenthousandfeet said:
Done. Followed that up with a TWRP flash of Magisk 19.2. Then... bootloop! Arg.
Click to expand...
Click to collapse
That stinks. Have you tried changing slots in fastboot boot instance of TWRP and then installing Magisk? It sure sounds like your slots are out of sync somehow, and the easiest way to remedy that is to run flash-all with -w in place.
sliding_billy said:
That stinks. Have you tried changing slots in fastboot boot instance of TWRP and then installing Magisk? It sure sounds like your slots are out of sync somehow, and the easiest way to remedy that is to run flash-all with -w in place.
Click to expand...
Click to collapse
I'm not sure if it's related to slots or not, actually. I was thinking that it was, but I've now done a flash-all on both slots (one after the other), then tried my TWRP flash of the Magisk installer again. Results? Bootloop.
I've also tried flashing Magisk Manager's patched_boot.img to both boot_a and boot_b, with the now-familiar outcome.
tenthousandfeet said:
I'm not sure if it's related to slots or not, actually. I was thinking that it was, but I've now done a flash-all on both slots (one after the other), then tried my TWRP flash of the Magisk installer again. Results? Bootloop.
I've also tried flashing Magisk Manager's patched_boot.img to both boot_a and boot_b, with the now-familiar outcome.
Click to expand...
Click to collapse
I hear you about flash-all on both slots, but if you left yourself on the same active slot there could still potentially be an issue. I'll need to think about this some more when I wake. I'd hate to see you do a full reset and end up with the same issue if it is something in the procedural that is causing it. One other thing that shouldn't be a concern, but are you using the proper/current TWRP for the P3 (twrp-3.3.0-0-blueline)? And yet one more thing... try rooting with a patched boot instead of running the installer in TWRP. I can't do the instructions by memory, but they are on here. Check the P3 XL page if they are not readily available on the P3 page.
tenthousandfeet said:
Done. Followed that up with a TWRP flash of Magisk 19.2. Then... bootloop! Arg.
Click to expand...
Click to collapse
Please update when/if you find a solution. We are both in the same boat.
I'll let you know if I get anything working.
sliding_billy said:
I hear you about flash-all on both slots, but if you left yourself on the same active slot there could still potentially be an issue. I'll need to think about this some more when I wake. I'd hate to see you do a full reset and end up with the same issue if it is something in the procedural that is causing it. One other thing that shouldn't be a concern, but are you using the proper/current TWRP for the P3 (twrp-3.3.0-0-blueline)? And yet one more thing... try rooting with a patched boot instead of running the installer in TWRP. I can't do the instructions by memory, but they are on here. Check the P3 XL page if they are not readily available on the P3 page.
Click to expand...
Click to collapse
Here's what I did to get both slots:
Code:
fastboot --set-active=_a
flash-all
fastboot reboot-bootloader
fastboot --set-active=_b
flash-all
fastboot reboot
adb reboot bootloader
fastboot boot twrp-3.3.0-0-blueline.img
Note the TWRP image is the latest - 3.3.0.
I've also tried flashing the Magisk-patched boot, using the following:
Code:
fastboot flash boot patched_boot.img
...and...
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Everything reports success while flashing, but won't boot.
One more thing I could try is an updated ADB/Fastboot. Mine is probably a little dated, though I wouldn't expect that would have any ramifications for flashing with TWRP.
tenthousandfeet said:
Here's what I did to get both slots:
Code:
fastboot --set-active=_a
flash-all
fastboot reboot-bootloader
fastboot --set-active=_b
flash-all
fastboot reboot
adb reboot bootloader
fastboot boot twrp-3.3.0-0-blueline.img
Note the TWRP image is the latest - 3.3.0.
I've also tried flashing the Magisk-patched boot, using the following:
Code:
fastboot flash boot patched_boot.img
...and...
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Everything reports success while flashing, but won't boot.
One more thing I could try is an updated ADB/Fastboot. Mine is probably a little dated, though I wouldn't expect that would have any ramifications for flashing with TWRP.
Click to expand...
Click to collapse
It still looks like your boot slot ended up the one you had tried already (b), since you changes to a and ran flash-all, changed back to b and ran flash-all and rebooted. As for the old platform tools, that could definnitly have an impact on running the fastboot of the patched boot. Other than that, I think a flash-all with the -w is the only approach left.
I'm also in the same boat. I've tried all the various install methods, and done the double "flash-all" on both slots, and no matter what, it ends in a bootloop.
Haven't tried the -w yet so I'll be interested if anyone gives that a go. Until then I'm dying with no root
i am trying to root and install TWRP on my oneplus 7 pro (9.5.11.GMA21AA gm1910) but its always reverting back to stock recovery. i dont know why or what step i am missing or messing up on.
heres what i am doing:
Code:
fastboot boot twrp-3.3.1-70-guacamole-unified-Pie-mauronofrio.img
then in TWRP i am sideloading the TWRP installer via advanced--sideload
Code:
adb sideload twrp-3.3.1-70-guacamole-unified-installer-mauronofrio.zip
then after that i do the magisk20 (also sideload) which is successful.
Code:
adb sideload Magisk-v20.0.zip
then i reboot the system and all is well. magisk works and passes safetynet.
but when i reboot into recovery it goes to the stock recovery and not TWRP.
whats going on? what am i doing wrong?
Boot twrp.img. Phone boots in trwp. Flash twrp.zip & Magisk Latest Stable version in twrp.
null0seven said:
Boot twrp.img. Phone boots in trwp. Flash twrp.zip & Magisk Latest Stable version in twrp.
Click to expand...
Click to collapse
thats exactly what i am doing as i mentioned in my original post.
but when i reboot into recovery it loads STOCK recovery and not TWRP.
cylent said:
thats exactly what i am doing as i mentioned in my original post.
but when i reboot into recovery it loads STOCK recovery and not TWRP.
Click to expand...
Click to collapse
It seems like one partition have the stock recovery
cylent said:
thats exactly what i am doing as i mentioned in my original post.
but when i reboot into recovery it loads STOCK recovery and not TWRP.
Click to expand...
Click to collapse
You say that Magisk works fine. Flash twrp.zip with Magisk > Modules. Reboot to recovery with Magisk. Flash Magisk again.
Another version. Go to Magisk > Downloads and flash TWRP A/B Retention Script.
[Deleted]
The flashing instruction makes no sense to me
Spookybear said:
INSTALLATION:
0. Backup your ROM, your data, your internal storage, and your settings/apps, to an external device
1. Reboot to your custom TWRP-based Recovery
2. The device will automatically reboot into OrangeFox recovery after installation (allow this to happen)
3. Enjoy!
(Note: There is no zip file because this recovery is too big to fit in the ramdisk.
Click to expand...
Click to collapse
Can you please clarify this?
I assume install .IMG to Ramdisk? It will likely come up, so just want to cover all bases.
gorilla p said:
Can you please clarify this?
I assume install .IMG to Ramdisk? It will likely come up, so just want to cover all bases.
Click to expand...
Click to collapse
I tried that...no dice...
Flash to both _a and _b using trwp but recovery does not boot... so back to trwp til some future info...
I flashed via TWRP, via flash .img to ramdisk, rebooted to recovery and nothing.
Stuck at "Bootloader unlocked" screen
Tried to boot via fastboot and it failed.
Was this recovery tested on the OP7 Pro? If so, what ROM was being used and what was the flashing process?
Gungrave223 said:
The flashing instruction makes no sense to me
Click to expand...
Click to collapse
Sorry, fixed the instructions.
avid_droid said:
Yeah directions are honestly the worst I've seen on XDA yet.
Click to expand...
Click to collapse
Sorry, fixed the instructions.
I have a feeling these new instructions aren't going to work either, considering we don't have a recovery partition.
Spookybear said:
Sorry, fixed the instructions.
Click to expand...
Click to collapse
still no dice
HTML:
Writing 'recovery'
FAILED (remote: '(recovery_a)
No such partition'
I guess the command should be
fastboot boot /path to recovery
But again this wont flash recovery permanently AFAIK, everytime we need to boot into recovery we have to flash it via fastboot
insaneparnoid said:
I guess the command should be
fastboot boot /path to recovery
But again this wont flash recovery permanently AFAIK, everytime we need to boot into recovery we have to flash it via fastboot
Click to expand...
Click to collapse
He updated it with fastboot flash, indicating that this is to be installed, however it doesn't appear to work at all at this point.
For me is working , latest OOS beta. Just had to disable vbmeta in order to boot.
we need a flashble zip for this.
is OTG working with OrangeFox ?
otakutw said:
we need a flashble zip for this.
Click to expand...
Click to collapse
Not exactly, try - fastboot flash recovery *drag the image into the cmd then press enter*
Can this recovery be decreased in size so that it can be flashed to the ramdisk?
EDIT: It seems twrp is even bigger than this. Twrp img is 30.7mb while this is 29.4mb. Twrp does flash to the ramdisk. If this could be permanently flashed, it would be perfect. If the size needs to be decreased, certain graphics could be moved to the internal storage to save space on the ramdisk.
Hahaha wow what are you doing here it's like you didn't even test this at all. I'm tried to flash the installer in twrp and it tells me that this recovery is only for guacamole not OnePlus 7 pro. So it does not support custom roms clearly cause I'm on bliss
shadowikr said:
Not exactly, try - fastboot flash recovery *drag the image into the cmd then press enter*
Click to expand...
Click to collapse
There is no recovery partition on modern Android devices. The boot.img ramdisk contains the recovery
Hello.yesterday i tried to root my OnePlus 7 pro.i unlocked the bootloader first and then I have installed the twrp on slot a and slot b.then I have installed magisk,from this moment the WiFi on my phone stopped working.(when I am turning them on the automatically turned off)I tried again to flash stock ROM and twrp but when I install magisk I had the same problem.Then somehow I accidentally bricked the phone and today I have the stock ROM with unlocked bootloader and I need your help to root.
You my friend need to learn how to write clearly xD.
Continuing where you left off this is how you achieve root with Magisk:
1.Boot into the bootloader
2. Using cmd (I assume you installed ADB drivers and fast boot drivers already if not Youtube a guide) use the following command:
fastboot boot <twrp image file here>
once you're in TWRP you can flash the TWRP install ZIP.
Once you're done with that Reboot -> Recovery.
3. Flash Magisk and you're done.
I doubt you're really bricked. Since you have the bootloader unlocked just do the button combo to get into recovery or the bootloader.
Thats the method i did.the real problem is the magisk.are there stable or better magisk versions?
The phone now is stock and unrooted
panagiwtis90 said:
Thats the method i did.the real problem is the magisk.are there stable or better magisk versions?
Click to expand...
Click to collapse
20.3 is the latest version and works perfectly fine on mine
o.o
How is it not stable?
I dont know if i did something wrong.the only difference from HermitDash method is that this comand (fastboot boot <twrp image file here>) not worked for me so i used this
fastboot flash boot_a path-to-twrp.img" and this fastboot flash boot_b path-to-twrp.img"
panagiwtis90 said:
I dont know if i did something wrong.the only difference from HermitDash method is that this comand (fastboot boot <twrp image file here>) not worked for me so i used this
fastboot flash boot_a path-to-twrp.img" and this fastboot flash boot_b path-to-twrp.img"
Click to expand...
Click to collapse
Can you Share a screen capture of your twrp file and your fastboot command
I will try again later and post screenshots
Dont understand.
HermitDash said:
You my friend need to learn how to write clearly xD.
Continuing where you left off this is how you achieve root with Magisk:
1.Boot into the bootloader
2. Using cmd (I assume you installed ADB drivers and fast boot drivers already if not Youtube a guide) use the following command:
fastboot boot <twrp image file here>
once you're in TWRP you can flash the TWRP install ZIP.
Once you're done with that Reboot -> Recovery.
3. Flash Magisk and you're done.
I doubt you're really bricked. Since you have the bootloader unlocked just do the button combo to get into recovery or the bootloader.
Click to expand...
Click to collapse
I dont understand why they say after you boot into twrp from fastboot to reflash twrp.zip file in twrp. I never do and it still works the same. And when you do flash the twrp.zip it says your now unrooted flash magisk. And when you flash magisk it actually then unroots magisk. The best way to root the oneplus 7 pro is using payload extractor and patching the boot.img with magisk. and booting magiskpatched.img then after installing the magisk manager go to modules and flash twrp from there. alot easier.
Can you explain this easier method you said here to try it as i am a noob?
panagiwtis90 said:
Can you explain this easier method you said here to try it as i am a noob?
Click to expand...
Click to collapse
Okay, new to this thread. Where are you at right now? Booting? Which OS, TWRP, Magisk versions?
I am at 10.3 stock rom without root and twrp(just unlocked bootloader)
panagiwtis90 said:
I am at 10.3 stock rom without root and twrp(just unlocked bootloader)
Click to expand...
Click to collapse
I am on the same version what I did was find the patched boot image with magisk for Android 10 flashed it using adb then installed magisk manager and I had root.
https://forum.xda-developers.com/on...atched-boot-image-oneplus-7-pro-t3964345/amp/
panagiwtis90 said:
I am at 10.3 stock rom without root and twrp(just unlocked bootloader)
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
Follow this guide and you won't need to use the patched boot,img file. I've never liked using the patched boot img.
Thank you GeekMcLeod your method worked
amaroney55 said:
I dont understand why they say after you boot into twrp from fastboot to reflash twrp.zip file in twrp. I never do and it still works the same. And when you do flash the twrp.zip it says your now unrooted flash magisk. And when you flash magisk it actually then unroots magisk. The best way to root the oneplus 7 pro is using payload extractor and patching the boot.img with magisk. and booting magiskpatched.img then after installing the magisk manager go to modules and flash twrp from there. alot easier.
Click to expand...
Click to collapse
It's just easier than having to manually extract the boot.img
fastboot boot twrp is just to get twrp up and running then flashing the script actually installs it.
Yes it does say that it'll unroot you but for those that are unrooted already this step doesn't do anything.
After flashing you reboot TWRP so it works fresh post-script.
Then install magisk as usual and reboot to system done.
This is if you want both TWRP and Magisk all done at the same time vs booting the boot.img installing Magisk then installing TWRP where I can have it all done within TWRP which is the usual route people take to get to root.
My comment below in red font:
amaroney55 said:
I dont understand why they say after you boot into twrp from fastboot to reflash twrp.zip file in twrp. I never do and it still works the same.
Fastboot boot twrp just remotely boots a "temporary" (one time) instance of TWRP, but does not install TWRP to the device. Flashing the TWRP installer zip is for installing TWRP on the device. This is optional and a matter of personal preference, and not needed to achieve root. What the installer zip does, is extract the boot.img and injects TWRP, then installs that modified boot.img back to the phone.
And when you do flash the twrp.zip it says your now unrooted flash magisk.
Correct. When the installer zip patches the boot.img to install TWRP (as described above), root is removed.
And when you flash magisk it actually then unroots magisk.
Not correct. Magisk roots the phone. If you flashed Magisk and did not have root, what may be happened, is that you may have flashed Magisk to one slot, then somehow booted to the other (unrooted) slot.
The best way to root the oneplus 7 pro is using payload extractor and patching the boot.img with magisk. and booting magiskpatched.img then after installing the magisk manager go to modules and flash twrp from there. alot easier.
Manually patching the boot.img is certainly a valid way to achieve root, and maybe more reliable. I'd hesitate to say it is "easier".
Also, if you flash TWRP as a Magisk module, you will still need to flash Magisk again to have root. Flashing TWRP by that method will still unroot the phone, same as the other method (as I described above).
Click to expand...
Click to collapse
---------- Post added at 08:56 AM ---------- Previous post was at 08:44 AM ----------
panagiwtis90 said:
I dont know if i did something wrong.the only difference from HermitDash method is that this comand (fastboot boot <twrp image file here>) not worked for me so i used this
fastboot flash boot_a path-to-twrp.img" and this fastboot flash boot_b path-to-twrp.img"
Click to expand...
Click to collapse
You did it wrong. Those two command do completely different things. So the difference in commands is a big one.
As I mentioned above, fastboot boot TWRP.img just remotely boots a temporary (one time) instance of a boot.img that has been patched to include TWRP. Then the correct way to install TWRP to the phone is (from the temporary booted TWRP) flash the TWRP installer zip, which properly extracts your phone's boot.img partition, patches it to install TWRP, then installs the modified boot.img back to the phone.
Fastboot flash boot TWRP.img does something completely different. It flashes the img to the boot partition. "Flash" is the action in this case, and "boot" is the location (not the action). The TWRP img is not meant to be installed to the phone. Don't know for sure, but I highly suspect that boot.img has some differences depending on your 7 Pro model. So when folks incorrectly flash TWRP.img, they are replacing the phone's kernel and breaking WiFi, and sometimes cell network and/or Bluetooth. Again, the correct way to install TWRP is to use the installer zip (as described in the previous paragraph) which properly takes your phones specific boot.img and patches it.
What folks should understand, is that A/B partition devices (like the 7 Pro) do not have a discrete recovery partition. Recovery is part of the boot partition, which also contains the kernel. So by doing "flash boot" you are messing with the kernel in ways you should not, and therefore results like broken WiFi is not surprising.
---------- Post added at 09:06 AM ---------- Previous post was at 08:56 AM ----------
panagiwtis90 said:
Thats the method i did.the real problem is the magisk.are there stable or better magisk versions?
Click to expand...
Click to collapse
Magisk if fine. Your issues are due to pilot error, as I've described above.
Has the full rom been released yet?
arsalturtle891 said:
Has the full rom been released yet?
Click to expand...
Click to collapse
No, at least on Oxygen Updater. Are you on F20 and you want to root?
TheNewHEROBRINE said:
No, at least on Oxygen Updater. Are you on F20 and you want to root?
Click to expand...
Click to collapse
I'm on F18 with root and I want to upgrade to F20. Is there an LE2115_11.F.18 full rom by any chance. I can flash this and then upgrade to F20. I don't mind being without root for the time being
arsalturtle891 said:
I'm on F18 with root and I want to upgrade to F20. Is there an LE2115_11.F.18 full rom by any chance. I can flash this and then upgrade to F20. I don't mind being without root for the time being
Click to expand...
Click to collapse
When you rooted did you do fastboot flash or fastboot boot and then direct install in Magisk app?
I did the following:
Fastboot boot "patchedbootimage".img
Fastboot flash boot_a "patchedbootimage".img
Fastboot flash boot_b "patchedbootimage".img
arsalturtle891 said:
I did the following:
Fastboot boot "patchedbootimage".img
Fastboot flash boot_a "patchedbootimage".img
Fastboot flash boot_b "patchedbootimage".img
Click to expand...
Click to collapse
Then you can't restore your original boot image from Magisk. You should only ever do fastboot boot and then use direct install in Magisk. Unfortunately the latest full rom available for your device is LE2115_11_F.17, so I think your only chance is that someone share a stock F18 boot image so that you can flash it and then update.
arsalturtle891 said:
I did the following:
Fastboot boot "patchedbootimage".img
Fastboot flash boot_a "patchedbootimage".img
Fastboot flash boot_b "patchedbootimage".img
Click to expand...
Click to collapse
First command, you booted the patched boot image. All good. From there, install/open Magisk app and then select direct install option, and Magisk will automatically back up the stock boot and then flash the rooted boot.
Second commands shouldn't have been run.
shadabkiani said:
First command, you booted the patched boot image. All good. From there, install/open Magisk app and then select direct install option, and Magisk will automatically back up the stock boot and then flash the rooted boot.
Second commands shouldn't have been run.
Click to expand...
Click to collapse
Appreciate it!
shadabkiani said:
First command, you booted the patched boot image. All good. From there, install/open Magisk app and then select direct install option, and Magisk will automatically back up the stock boot and then flash the rooted boot.
Second commands shouldn't have been run.
Click to expand...
Click to collapse
I'm not seeing the attachment
Here is the stock unrooted F.18 boot.img. Make sure to extract it first.
So I was able to remove root by first following the same commands I used to root in the first place with the boot image you provided. However, I cannot update to F20 using the system update. It keeps failing
Ok, this time, you have to flash this unrooted boot.img that I provided. NOT just boot it like you do when trying to root. The system will check the flashed boot.img then proceed with OTA.
fastboot flash boot boot.img
Reboot, then try OTA update.
When you have the latest F.20 successfully booted, if you want root, you can get that boot.img through MSM readback feature. Or, I have F.20 boot.img too, and you can ask for that.
shadabkiani said:
Ok, this time, you have to flash this unrooted boot.img that I provided. NOT just boot it like you do when trying to root. The system will check the flashed boot.img then proceed with OTA.
fastboot flash boot boot.img
Reboot, then try OTA update.
When you have the latest F.20 successfully booted, if you want root, you can get that boot.img through MSM readback feature. Or, I have F.20 boot.img too, and you can ask for that.
Click to expand...
Click to collapse
I followed your steps and it still gives an installation error. Just to make sure, I uninstalled magisk through the magist app as well. Further, I did some research on the MSM readback feature. Can you link me to the correct one to use?
arsalturtle891 said:
I followed your steps and it still gives an installation error. Just to make sure, I uninstalled magisk through the magist app as well. Further, I did some research on the MSM readback feature. Can you link me to the correct one to use?
Click to expand...
Click to collapse
The MSM Tool for Global thread is here, but the download link in first post is incomplete. You can download the full tool from here. Make sure to download the correct package. The global one also works for LE2110 (the Chinese model).
So you have flashed my boot.img, and then you are updating from where? Through system update OTA, or from zip file downloaded with Oxygen Updater app?
shadabkiani said:
The MSM Tool for Global thread is here, but the download link in first post is incomplete. You can download the full tool from here. Make sure to download the correct package. The global one also works for LE2110 (the Chinese model).
So you have flashed my boot.img, and then you are updating from where? Through system update OTA, or from zip file downloaded with Oxygen Updater app?
Click to expand...
Click to collapse
I tried both methods and both fail (through system update OTA, and from zip downloaded with oxygen updater app)
I did the following:
fastboot boot "stockboot"
fastboot flash boot "stockboot"
AND I TRIED THIS TOO:
fastboot boot "stockboot"
fastboot flash boot_a "stockboot"
fastboot flash boot_b "stockboot"
arsalturtle891 said:
I tried both methods and both fail (through system update OTA, and from zip downloaded with oxygen updater app)
I did the following:
fastboot boot "stockboot"
fastboot flash boot "stockboot"
AND I TRIED THIS TOO:
fastboot boot "stockboot"
fastboot flash boot_a "stockboot"
fastboot flash boot_b "stockboot"
Click to expand...
Click to collapse
Why do you always "fastboot boot......" and then "fastboot flash boot...."?
Generally, fastboot boot.... will make you phone boot up the given image temporarily (whether it's a boot image or a bootable recovery image). Whereas, fastboot flash boot.... will permanently flash the given image. Normally, you only have to go with one of these methods depending on your task/goal.
Anyway, since you have flashed the stock unrooted boot.img and OTA is still failing, I suggest you just back up your personal data (photos, stuff) to PC or whatever, and then go with the MSM tool method. It will wipe all your data on phone, and revert your phone to OOS11 with locked bootloader. From there, you can take OTA updates all the way upto OOS13 F.20. This seems to be the simpler way to get out of your current predicament.
How to use MSM tool:
1. Download the package according to your device/variant, and extract it.
2. Power off your phone and keep it aside. DO NOT connect your phone to PC for now.
3. Run the MSM tool exe. It will take a couple of minutes to load.
4. Click on Target drop-down menu and choose O2 if you are on Global.
5. Click Start. It will go to Waiting for Device mode.
6. Now on your phone (which should already be powered off), press & hold both the vol+ and vol- buttons (NOT the power button) and connect the data cable from PC to your phone. Your phone's screen will still stay black and it will enter EDL mode.
7. The MSM tool will start flashing as soon as the connection is successful.
Note: You need to have OnePlus device drivers on PC.
I appreciate the support. Can you also provide me with the F20 boot image by any chance.
Sure. Stock unrooted F.20 boot.img attached. Make sure to unzip it.
By the way, if you have MSM tool, you can get your current boot.img from its readback feature. Super simple. Launch MSM tool. Press F8. Select the desired boot image (boot_a or boot_b). Enter the password as: oneplus. Click read. Power off phone, and get it into EDL mode by pressing holding vol- vol+ buttons then connecting data cable from PC. The desired boot.img will be dumped in C: drive.
Also, F.21 has just been released, so you better update to that. I haven't yet as I am currently on crDroid.
Anyway, F.20 boot has been attached.
Hello sir Can I get F.21 boot
vendor boot
dtbo
there're no FULL package out there for Global variant
Just only incremental update
How can I get that Full Image?
Or Should I extract it from India Variant Full Image F.21
will It work normally?