Related
Here is one thing you should know before proceeding: Android 10 has new fastbootd and the latest Android Platform Tool is required to get fastbootd support.
Download your version https://developer.android.com/studio/releases/platform-tools
Tested on -7 RETUS and it worked after few trial and error
You must unlock bootloader first (and your phone is wiped during process)
Extract boot.img from full ROM and patch with Magisk Manager, and copy the patched boot.img back to host computer
Now here are the steps:
Enter bootloader (power the phone off, press and hold volume down while power your phone back on, and you should see bootloader screen
Now connect your One Hyper to host computer and enter
Code:
fastboot reboot fastboot
You will see something looks like stock recovery but it has fastbootd on the top.
From there, you can flash patched boot.img as you used to.
Reboot when it's done
CTSProfile and BasicIntegrity false, any ideas?
Space_Dog said:
CTSProfile and BasicIntegrity false, any ideas?
Click to expand...
Click to collapse
It's probably the version. I have same situation
mingkee said:
Here is one thing you should know before proceeding: Android 10 has new fastbootd and the latest Android Platform Tool is required to get fastbootd support.
Download your version https://developer.android.com/studio/releases/platform-tools
Tested on -7 RETUS and it worked after few trial and error
You must unlock bootloader first (and your phone is wiped during process)
Extract boot.img from full ROM and patch with Magisk Manager, and copy the patched boot.img back to host computer
Now here are the steps:
Enter bootloader (power the phone off, press and hold volume down while power your phone back on, and you should see bootloader screen
Now connect your One Hyper to host computer and enter
Code:
fastboot reboot fastboot
You will see something looks like stock recovery but it has fastbootd on the top.
From there, you can flash patched boot.img as you used to.
Reboot when it's done
Click to expand...
Click to collapse
What is this FastbootD? Something new on Android 10, cause the Pixel 4 has it too...
AndroidManager2020 said:
What is this FastbootD? Something new on Android 10, cause the Pixel 4 has it too...
Click to expand...
Click to collapse
It's Android 10 way to flash boot, recovery, dtbo, vbmeta, and super
The interface is more like stock recovery with fastbootd on the top
mingkee said:
It's Android 10 way to flash boot, recovery, dtbo, vbmeta, and super
The interface is more like stock recovery with fastbootd on the top
Click to expand...
Click to collapse
I totally understand the concept but what different between regular fastboot, mfastboot, and fastbootD?
mingkee said:
Here is one thing you should know before proceeding: Android 10 has new fastbootd and the latest Android Platform Tool is required to get fastbootd support.
Download your version https://developer.android.com/studio/releases/platform-tools
Tested on -7 RETUS and it worked after few trial and error
You must unlock bootloader first (and your phone is wiped during process)
Extract boot.img from full ROM and patch with Magisk Manager, and copy the patched boot.img back to host computer
Now here are the steps:
Enter bootloader (power the phone off, press and hold volume down while power your phone back on, and you should see bootloader screen
Now connect your One Hyper to host computer and enter
Code:
fastboot reboot fastboot
You will see something looks like stock recovery but it has fastbootd on the top.
From there, you can flash patched boot.img as you used to.
Reboot when it's done
Click to expand...
Click to collapse
For the retail channel on my device, should be LARET which had (2) Builds, the latest being (XT2027-1_DEF_RETLA_10_QPFS30.103-12-5-2_subsidy-DEFAULT_regulatory-XT2027-1-SUTEL-DS_CFC.xml.zip) i'll change to RETAIL after i receie the device. I am worried about getting OTAs later then Brazil/LA Channels.. There are NO RETAIL Firmware Packages for the Retail Channel Device. I guess ill have to see what model it is, Purchased from Amazon, which is where I got my G8+ for a CHEAP $205.83 and as soon as i went to reorder a replacement, price jumped $75, like amazon knew i was going to reorder the same device. Then i came across the one hyper and for a few $$$$ more, specs and chipset are better, same exact specs as the Zoom and the Hyper ran me $314 and the Zoon is like $394.00 I Just need something new to keep me busy until the Edge+ is released....and currently also a Pixel 4 XL (Trying to trade for a LG V60 thinq with the Dual Screen. ) Pixel is 1 month old, 1.5 months at the most, OEM Box, OEM accessories ONLY EVER USED, a couple cases.
Been a Android user since 2010, never had an LG Android. Wait, i had the V40/V50 for under 12 hrs and hated it. it felt cheap and clunky.... But i feel in love with this V60. And i also have (2) Moto G7 aka River. My Moto Def should be here tuesday hopefully. See how quick i can brick this one Moto G8+ was bricked on day one but i pulled out of it using a brand new Levovo Upgrade Tool!
Magisk install
I cannot find on XDA if we can or cannot install Magisk on the XT2027-1 ( One Hyper )
I found a few other sites on the internet that say it can be installed
BUT I tend to err on the side of caution.
I do not want to nuke this phone.
Is this a possibility to install Magisk or not?
I use Viper4 Android and a few other apps like blockada and such
Finally, IF Magsik is installed, I cannot get OTA updates, correct?
Can I uninstall Magisk, update OTA, then reinstall Magisk?
Thank you all
jharkness316 said:
I cannot find on XDA if we can or cannot install Magisk on the XT2027-1 ( One Hyper )
I found a few other sites on the internet that say it can be installed
BUT I tend to err on the side of caution.
I do not want to nuke this phone.
Is this a possibility to install Magisk or not?
I use Viper4 Android and a few other apps like blockada and such
Finally, IF Magsik is installed, I cannot get OTA updates, correct?
Can I uninstall Magisk, update OTA, then reinstall Magisk?
Thank you all
Click to expand...
Click to collapse
Have run into issues......... Damn Windows update restarted computer in middle of night before I was to finish rooting.
I can get into bootloader and when I try to flash I am stuck in bootloop
I get the following errors:
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
Sending 'vbmeta_a' (4 KB) OKAY [ 0.016s]
Writing 'vbmeta_a' (bootloader) WARNING: vbmeta_a anti rollback downgrade, 0 vs 5
OKAY [ 0.000s]
Finished. Total time: 0.016s
Ideas on how to fix? This was flashing back the ORIGINAL stock rom
---------- Post added at 07:57 AM ---------- Previous post was at 07:11 AM ----------
FIXED Rescue and Smart Assistant from Lenovo fixed it
Got it fixed thanks to Rescue and Search program from Motorola
Would like to know since TWRP is not working with the One Hyper, is there a way that I can make a master rom backup via ADB or FASTBOOTD?
If so, can someone make a batch file or list all the things to backup this rom?
I would greatly appreciate it. Thank you
I have my Magisk installed on my Hyper and all is working well. I just got Moto trying to download and update a patch (assuming Google security update). It could not update obviously.
My question is how can I UNinstall magisk , all the modules, and then update my Hyper?
Now if I uninstall magisk I will lose root, correct?
This is the rom I am currently using........DEF_RETAIL_QPFS30.103-47-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC
jharkness316 said:
I have my Magisk installed on my Hyper and all is working well. I just got Moto trying to download and update a patch (assuming Google security update). It could not update obviously.
My question is how can I UNinstall magisk , all the modules, and then update my Hyper?
Now if I uninstall magisk I will lose root, correct?
This is the rom I am currently using........DEF_RETAIL_QPFS30.103-47-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC
Click to expand...
Click to collapse
in order to take updates you would need to restore the stock boot image with fastboot or magisk, and then update your device, then take the new boot image from the downloaded update and patch with magisk and then flash it to regain magisk root, you do not need to uninstall magisk or the modules but you will need to restore stock boot partitions to allow the device to not error out during the install process. This is how it has been in the past for magisk official guides can be found on magisk website here: https://topjohnwu.github.io/Magisk/ota.html
[deleted]
Hi Everyone
I was rooting My op7 pro after updating to open beta android 11. While i was booting twrp it shows Fastboot Mode screen And stuck on that
Hope i ll find possible solution from the community
Regards
ali_hamza
I went through something similar. I'm reading that TWRP does not support Android 11 yet, so I think we have to do without it for now.
Steps I took:
Disconnect any USB
Hold down vol up, vol down, and power until screen goes black
Do this again until you actually get to normal fastboot mode
Connect to your PC
On your PC if you haven't already, download and install adb/fastboot tools, python, and the payload dumper tool - see Extract Android OTA Payload.bin File using Payload Dumper Tool (thecustomdroid.com)
On your PC, download the ROM zip of the Android 11 beta for OnePlus 7 Pro from the OnePlus forums
Open the Zip and extract the payload.bin file
Follow the instructions above to extract boot.img from payload
Open an admin command prompt and cd to a folder where you have adb/fastboot and this boot.img file
To make sure your phone is properly connected to your PC with correct drivers etc, run fastboot devices
Run fastboot flash boot boot.img
Run fastboot reboot
This got me back into an unrooted Android 11 system. My recovery is messed. I think there's a way to directly patch the boot.img file with Magisk and flash that. Will need to work on getting TWRP back if/when someone figures that out (or when it is supported)
Once you're unrooted and running on the Android 11 beta:
connect to your PC
tell Android to go into file transfer mode
take boot.img file from above instructions and copy it to the root of your phone storage
open the Magisk Manager app, click to install Magisk, and then choose Patch boot image
resulting patched boot image file will be saved to your phone's Downloads folder
back on the PC, pull this patched boot img file back onto your PC and into your fastboot folder
reboot phone into fastboot mode (using volup+voldn+power)
Run fastboot flash boot magisk_patched_?????.img (your file will have a unique name)
Run fastboot reboot
Now you're rooted.
benjaminries said:
I went through something similar. I'm reading that TWRP does not support Android 11 yet, so I think we have to do without it for now.
Steps I took:
Disconnect any USB
Hold down vol up, vol down, and power until screen goes black
Do this again until you actually get to normal fastboot mode
Connect to your PC
On your PC if you haven't already, download and install adb/fastboot tools, python, and the payload dumper tool - see Extract Android OTA Payload.bin File using Payload Dumper Tool (thecustomdroid.com)
On your PC, download the ROM zip of the Android 11 beta for OnePlus 7 Pro from the OnePlus forums
Open the Zip and extract the payload.bin file
Follow the instructions above to extract boot.img from payload
Open an admin command prompt and cd to a folder where you have adb/fastboot and this boot.img file
To make sure your phone is properly connected to your PC with correct drivers etc, run fastboot devices
Run fastboot flash boot boot.img
Run fastboot reboot
This got me back into an unrooted Android 11 system. My recovery is messed. I think there's a way to directly patch the boot.img file with Magisk and flash that. Will need to work on getting TWRP back if/when someone figures that out (or when it is supported)
Once you're unrooted and running on the Android 11 beta:
connect to your PC
tell Android to go into file transfer mode
take boot.img file from above instructions and copy it to the root of your phone storage
open the Magisk Manager app, click to install Magisk, and then choose Patch boot image
resulting patched boot image file will be saved to your phone's Downloads folder
back on the PC, pull this patched boot img file back onto your PC and into your fastboot folder
reboot phone into fastboot mode (using volup+voldn+power)
Run fastboot flash boot magisk_patched_?????.img (your file will have a unique name)
Run fastboot reboot
Now you're rooted.
Click to expand...
Click to collapse
You should just be able to run direct install after you boot to A11 with the patched boot image.
Some of us will have followed a standard Oxygen OS beta update flash cycle of:
Download the beta update
Reboot to recovery (TWRP)
Flash update, wipe dalvik
Flash TWRP installer to patch new boot image
Reboot to recovery (from recovery, to get A/B slot switched)
Flash Magisk to patch boot image for root
Reboot to system
I bricked at step 5 because TWRP installer didn't play nice with the new Android 11 boot image. Even when I flashed the latest unofficial TWRP from fastboot, the best I could get was a TWRP that couldn't decrypt filesystem... and after that, a bootloop that just flashed the TWRP load screen briefly every second, between black screens.
I'm super appreciative of OnePlus for having such a reliable way to get back to fastboot no matter what. I take it that when I extracted the OP stock boot image from beta and flashed it in fastboot, I also overwrote TWRP with stock recovery? It no longer seems like recovery is a separate partition to be flashed - nothing from the payload file seemed to be it.
calripkenturner said:
You should just be able to run direct install after you boot to A11 with the patched boot image.
Click to expand...
Click to collapse
Wait... you don't mean "direct install" of TWRP, do you? Is there a version that supports Android 11 filesystem decryption? Wouldn't that also get rid of root? What is it that you think should be directly installed after successful boot of Android 11 with Magisk patched boot image?
benjaminries said:
Wait... you don't mean "direct install" of TWRP, do you? Is there a version that supports Android 11 filesystem decryption? Wouldn't that also get rid of root? What is it that you think should be directly installed after successful boot of Android 11 with Magisk patched boot image?
Click to expand...
Click to collapse
No, direct install of magisk. Check the twrp thread in the rom and development section. There is already a patched boot image and instructions on rooting. Twrp isnt working yet as far as I know.
calripkenturner said:
No, direct install of magisk. Check the twrp thread in the rom and development section. There is already a patched boot image and instructions on rooting. Twrp isnt working yet as far as I know.
Click to expand...
Click to collapse
Got it. Yeah my Magisk Manager was still installed from previous beta, but it took away the "direct install" option when I lost root from flashing the unpatched boot.img. Personally I would always rather patch my own boot.img file than rely on something from a filesharing service, especially when trying to get out of brick...
But I can see how until proper TWRP support comes, we can just use Magisk to patch alternate boot slot before rebooting but immediately after flashing the latest OOS beta using the regular system update process. Hindsight...
benjaminries said:
Some of us will have followed a standard Oxygen OS beta update flash cycle of:
Download the beta update
Reboot to recovery (TWRP)
Flash update, wipe dalvik
Flash TWRP installer to patch new boot image
Reboot to recovery (from recovery, to get A/B slot switched)
Flash Magisk to patch boot image for root
Reboot to system
I bricked at step 5 because TWRP installer didn't play nice with the new Android 11 boot image. Even when I flashed the latest unofficial TWRP from fastboot, the best I could get was a TWRP that couldn't decrypt filesystem... and after that, a bootloop that just flashed the TWRP load screen briefly every second, between black screens.
I'm super appreciative of OnePlus for having such a reliable way to get back to fastboot no matter what. I take it that when I extracted the OP stock boot image from beta and flashed it in fastboot, I also overwrote TWRP with stock recovery? It no longer seems like recovery is a separate partition to be flashed - nothing from the payload file seemed to be it.
Click to expand...
Click to collapse
need to use orangfox recovery
esi2121 said:
need to use orangfox recovery
Click to expand...
Click to collapse
Hard to find documentation suggesting OrangeFox works with Android 11 filesystem encryption or OOS 11 beta specifically. Does it?
benjaminries said:
Hard to find documentation suggesting OrangeFox works with Android 11 filesystem encryption or OOS 11 beta specifically. Does it?
Click to expand...
Click to collapse
Check the orangefox ,it's only recovery support a11 for now
esi2121 said:
Check the orangefox ,it's only recovery support a11 for now
Click to expand...
Click to collapse
Yeah I did, and I could not find any evidence that it supports the new Android 11 filesystem encryption.
Changelog suggests much of the core functionality is ported from TWRP - that OrangeFox is more or less a fork with extra functions and a better interface.
The reason users of both TWRP and OrangeFox have been able to use custom Android 11 ROMs is that those roms are kind of a Frankenstein - they're based on Android 10 AOSP with Project Treble packages from Android 11. OOS 11 beta seems to have different partition architecture?
I think we need to wait until somebody reports their actual experience with OOS 11 beta on a custom recovery.
Yesterday i download and tried to flash Pitch Black Recovery Project but results were same.
I think there should be some changes regarding A11 in any recovery so the best is that we should wait for their( Devs) further response
benjaminries said:
Yeah I did, and I could not find any evidence that it supports the new Android 11 filesystem encryption.
Changelog suggests much of the core functionality is ported from TWRP - that OrangeFox is more or less a fork with extra functions and a better interface.
The reason users of both TWRP and OrangeFox have been able to use custom Android 11 ROMs is that those roms are kind of a Frankenstein - they're based on Android 10 AOSP with Project Treble packages from Android 11. OOS 11 beta seems to have different partition architecture?
I think we need to wait until somebody reports their actual experience with OOS 11 beta on a custom recovery.
Click to expand...
Click to collapse
yup thats it , but in orangefox git said official support A11
esi2121 said:
yup thats it , but in orangefox git said official support A11
Click to expand...
Click to collapse
Check out this (now locked) thread though: it seems like there's no working port of OrangeFox for guacamole that supports OOS11 yet... lots of people bricking and boot-looping on the hope that there might have been!
[UNOFFICIAL] [RECOVERY] [OnePlus 7 Pro] OrangeFox Recovery Project [R10.1] | XDA Developers Forums (xda-developers.com)
I have a OnePlus 7 Pro on Android 11, OOS 11.0.0.2. The bootloader is unlocked. The devices runs absolutely fine unrooted. I have been wanting to root for quite some time. I patched the boot.img file of the ROM using latest Magisk Canary (app-debug.apk) from the GitHub repository. When I flash the .img through ADB, it is flashed successfully.
But when I reboot the phone, the phone is stuck on OnePlus' 'Two circling dots animation' (bootloop) and never starts. These are the commands that I enter one-by-one in CMD prompt on my laptop:
adb devices
adb reboot bootloader
fastboot flash boot "D:\Downloads\boot_patched.img"
fastboot reboot
Click to expand...
Click to collapse
So, to get out of this issue, I flash the stock boot image using similar commands. Then the phone boots successfully, but, of course, it is unrooted.
I even tried these commands, still no luck.
fastboot flash boot_a "D:\Downloads\boot_patched.img"
fastboot flash boot_b "D:\Downloads\boot_patched.img"
Click to expand...
Click to collapse
I also tried patching using the stable Magisk release (Magisk v23.0), still nothing.
What am I doing wrong?
iamMG said:
I have a OnePlus 7 Pro on Android 11, OOS 11.0.0.2. The bootloader is unlocked. The devices runs absolutely fine unrooted. I have been wanting to root for quite some time. I patched the boot.img file of the ROM using latest Magisk Canary (app-debug.apk) from the GitHub repository. When I flash the .img through ADB, it is flashed successfully.
But when I reboot the phone, the phone is stuck on OnePlus' 'Two circling dots animation' (bootloop) and never starts. These are the commands that I enter one-by-one in CMD prompt on my laptop:
So, to get out of this issue, I flash the stock boot image using similar commands. Then the phone boots successfully, but, of course, it is unrooted.
I even tried these commands, still no luck.
I also tried patching using the stable Magisk release (Magisk v23.0), still nothing.
What am I doing wrong?
Click to expand...
Click to collapse
I had an issue before, with the Canary APK. Try installing the v23 app and repatch your boot IMG with it. Worth a shot.
I tried, again, with v23. Same bootloop occuring.
Do you perhaps have the magisk app installed, I know of modules causing these sort of bootloop issues.
@soka said:
Do you perhaps have the magisk app installed, I know of modules causing these sort of bootloop issues.
Click to expand...
Click to collapse
Yes, the Magisk app is installed, but I don't have any modules installed. I don't even have root, how will I install a module?
iamMG said:
Yes, the Magisk app is installed, but I don't have any modules installed. I don't even have root, how will I install a module?
Click to expand...
Click to collapse
True, sorry just trying to help you narrow it down.
@soka said:
True, sorry just trying to help you narrow it down.
Click to expand...
Click to collapse
No problem. I just need to know how to fix the issue. Else, I would have to flash OOS 10.
iamMG said:
No problem. I just need to know how to fix the issue. Else, I would have to flash OOS 10.
Click to expand...
Click to collapse
This OnePlus 8T thread https://forum.xda-developers.com/t/...in-eu-us-kb2000-kb2001-kb2003-kb2005.4178675/ says to boot, not flash, the patched boot image. In other words, use fastboot boot "D:\Downloads\boot_patched.img" and then do a direct install in Magisk.
That's the process I used and it worked perfectly.
Note: my phone is an 8T.
BillGoss said:
This OnePlus 8T thread https://forum.xda-developers.com/t/...in-eu-us-kb2000-kb2001-kb2003-kb2005.4178675/ says to boot, not flash, the patched boot image. In other words, use fastboot boot "D:\Downloads\boot_patched.img" and then do a direct install in Magisk.
That's the process I used and it worked perfectly.
Note: my phone is an 8T.
Click to expand...
Click to collapse
Thanks, I will try this method and report back.
Btw, after you booted using this method, for how much time did the boot animation showed up (the two circling white dots around bigger red dot)?
Edit: I tried this method. No luck. The boot animation goes on 5-10 minutes, at which point I reboot into bootloader and flash the stock boot image.
Anyway, I ended up downgrading to OxygenOS 10.3.8.
Starting to give up as well... Never had any issues before (on Android 10) to flash root on O7Pro, but ever since Android 11, I keep having "boot loop" issues. Aka, the boot logo keeps loading and never boots into the OS. Only works again if I re-patch the original boot.img file.
This is starting to get.. VERY, VERY annoying. Why isn't there any proper method of getting this to work?
Not sure which boot.img you using.
But I face similar problem a week ago, and i fix that by using another .img then all fine.
I download from:
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
i'm running oxygen os 11.0.2.1 with root access. i'm running with the latest version of magisk, v.23.0. i haven't had any problems with android 11 and root. my suggestion is to make sure that you're patching the correct boot image. when an update is available, i download the full update, copy the zip to a computer, and then use payload dumper to extract the boot image. that's the boot image i use for patching.
hkdoublecat said:
Not sure which boot.img you using.
But I face similar problem a week ago, and i fix that by using another .img then all fine.
I download from:
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Click to expand...
Click to collapse
I am too afraid to upgrade to OOS 11, only to find out root doesn't work for me. The restore function of this unofficial TWRP version is buggy so can't really depend on it to restore OOS 10.3.8. So, I have decided to stay on the latter until Team Recovery releases a proper update for Android 11.
altwu said:
i'm running oxygen os 11.0.2.1 with root access. i'm running with the latest version of magisk, v.23.0. i haven't had any problems with android 11 and root. my suggestion is to make sure that you're patching the correct boot image. when an update is available, i download the full update, copy the zip to a computer, and then use payload dumper to extract the boot image. that's the boot image i use for patching.
Click to expand...
Click to collapse
Hi i am just wondering if you can upload the patch image and the original boot image of 11.0.2.1GM21AA thanks in advance.
Mangtas_666 said:
Hi i am just wondering if you can upload the patch image and the original boot image of 11.0.2.1GM21AA thanks in advance.
Click to expand...
Click to collapse
attached are the original and magisk patch boot images from my phone running 11.0.2.1 GM21AA.
boot_11021.img is the original boot image that i extracted with payload dumper.
magisk_patched-23000_fQNMs.img is the magisk patched boot image. it was patched with magisk v23.0.
altwu said:
attached are the original and magisk patch boot images from my phone running 11.0.2.1 GM21AA.
boot_11021.img is the original boot image that i extracted with payload dumper.
magisk_patched-23000_fQNMs.img is the magisk patched boot image. it was patched with magisk v23.0.
Click to expand...
Click to collapse
i tried attaching the images to the post but they're not showing up. i tried editing the post to attach the images, but they're still not showing up. sorry.
We received a new 8t and proceeded to do root and unlock on it.
Here is my process and problem.
Unlocked bootloader.
Updated phone to recent version via OTA update.
Downloaded update via Oneplus website.
Extracted payload.bin VIA python.payload dumper.
Moved boot.img to phone and patched it with magisk (select and patch a file)
Moved patched image to PC and ran adb
Fastboot flash boot patched image name.img
rebooted , now its caught in bootloop.
Tried fastboot --set-active=a and it didnt make a difference.
When looking at adb devices it shows the attached phone as unauthorized.
Dont know if this helps
Can get into fastboot
You flashed the OS to the bootloader. Not sure how to help you, man. Maybe try the EDL Tool. That worked for me. Also, always install TWRP and flash magisk zip through TWRP. It's foolproof.
TWRP doesnt work with android 11 or the oneplus 8 as far as I know, last time I looked.
Did a tool and fixed the crashes and bootloop, then followed a youtube video and guide.
Found out I ended up doing a different OS version that didnt match.
eracet said:
TWRP doesnt work with android 11 or the oneplus 8 as far as I know, last time I looked.
Did a tool and fixed the crashes and bootloop, then followed a youtube video and guide.
Found out I ended up doing a different OS version that didnt match.
Click to expand...
Click to collapse
TWRP for the 8T works reasonably well. See https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
Hello! I'm sorry I am pretty confused right now, I installed the November OTA update after uninstalling all Magisk modules, but forgot to disable Magisk Hide. Here are the steps I've taken to try to get root back on my phone:
1. Went to Google's website
2. Downloaded the Factory image for this version of update
3. Extracted the boot.img file and patched it with Magisk 25.2 (25200) (33)
4. Sent back to computer, and opened adb
4. Used "adb reboot bootloader"
5. Tried both "fastboot boot (the patched img)", and "fastboot flash boot (the patched img)"
I got the message
Sending 'boot_a' (65536 KB) OKAY [ 0.412s]
Writing 'boot_a' OKAY [ 0.090s]
Finished. Total time: 0.506s
None of these options seemed to work after the phone restarted however, I tried using the hidden Magisk and it told me to reinstall the app, so I deleted it and reinstalled it from the Magisk github. However, it's still showing "Installed N/A" in Magisk. I'm not sure what to do, may I please have some help haha-
My steps taken on installing the OTA update:
1. Removed Magisk modules (but forgot to turn off Magisk hide!)
2. Tried clicking Uninstall in Magisk and "Restore Image" but was hit with the error ""stock image does not exist."
3. Flashed original boot.img file using FKM (Franco Kernel Manager)
4. Used Direct Install in Magisk and rebooted phone
5. Still had error "stock image does not exist."
6. Downloaded the OTA image from Google
7. Changed the name to OTA.zip and placed into platform-tools
8. Connected phone and opened ADB
9. "adb fastboot recovery"
10. "adb sideload OTA.zip"
11. confirmed that the update worked in phone settings
btw, these are some additional information about my phone
Pixel 7 Pro, updating from Android 13 October Update to Android 13 November Update
To root the Pixel 7 series you need to patch the init_boot.img, not the boot.img.
fastboot flash init_boot <nameofpatchedinit_boot.img>
Lughnasadh said:
To root the Pixel 7 series you need to patch the init_boot.img, not the boot.img.
fastboot flash init_boot <nameofpatchedinit_boot.img>
Click to expand...
Click to collapse
Ohhh thank you so much! Nothing else changes right? and it wont reset my phone or anything right
jorvind said:
Ohhh thank you so much! Nothing else changes right? and it wont reset my phone or anything right
Click to expand...
Click to collapse
That's the only difference from earlier Pixels when rooting. It won't reset your phone.
If you want to use a custom kernel you will have to disable verity and verification, which will cause you to wipe your phone if doing it for the first time.
Lughnasadh said:
That's the only difference from earlier Pixels when rooting. It won't reset your phone.
If you want to use a custom kernel you will have to disable verity and verification, which will cause you to wipe your phone if doing it for the first time.
Click to expand...
Click to collapse
Ohh thank you so much! I just did it, confirmed it worked! D