Related
How would i install Android p/9/pie on my pixel since the bootloader is unlocked and rooted? Is there a guide i can follow? Would i use the factory image or the OTA file? Any help would be appreciated. Thank you in advance.
subvapor said:
How would i install Android p/9/pie on my pixel since the bootloader is unlocked and rooted? Is there a guide i can follow? Would i use the factory image or the OTA file? Any help would be appreciated. Thank you in advance.
Click to expand...
Click to collapse
Flash like every other factory image and all should be good.
phaino00 said:
Flash like every other factory image and all should be good.
Click to expand...
Click to collapse
Is it do able without a computer my laptop quit on me? If its not I'll have to wait till I'm around my moms house to do it. Ive only ever flash custom roms before so im not sure if it can be done with TWRP. Thanks for the help.
You need to use the fastboot tools, so you need your PC.
phaino00 said:
Flash like every other factory image and all should be good.
Click to expand...
Click to collapse
phaino00 said:
You need to use the fastboot tools, so you need your PC.
Click to expand...
Click to collapse
Okay thanks for the help.
Whats the difference between the files?
9.0.0 (PPR1.180610.009, Aug 2018)
9.0.0 (PPR1.180610.010, Aug 2018, Telus)
The Telus one is for people who have Telus for cell service. If you don't have Telus use the 009 if you have telus use 010. Google tends to do this from time to time.
phaino00 said:
Flash like every other factory image and all should be good.
Click to expand...
Click to collapse
Does this apply if you have custom recovery (TWRP) and modified boot.img (Magisk)?
I fastboot flashed the 9.0 files on top of the July 8.1 version without a data wipe. I had to reinstall TWRP and Magisk using the same install procedure I used on 8.1. Even though root was successfully working on Magisk 16 I had to install beta version 16.7 for the SafetyNet check to work properly.
Sent from my SHT-AL09 using Tapatalk
Butch1326 said:
I fastboot flashed the 9.0 files on top of the July 8.1 version without a data wipe. I had to reinstall TWRP and Magisk using the same install procedure I used on 8.1. Even though root was successfully working on Magisk 16 I had to install beta version 16.7 for the SafetyNet check to work properly.
Click to expand...
Click to collapse
How long did it take to boot after installing Magisk? I let my phone sit at the white boot screen for about 30 minutes before I had to reflash Pie again.
SkinnyT said:
How long did it take to boot after installing Magisk? I let my phone sit at the white boot screen for about 30 minutes before I had to reflash Pie again.
Click to expand...
Click to collapse
Not the exact same problem as yours, but I found that I wasn't able to boot into the OS after flashing Magisk 16.7. It would get to the animated "G" loading screen, but then reboot automatically and go into TWRP. Currently reflashing the stock (without wipe) and trying again.
Try installing the Magisk Uninstaller, then rebooting into system. If that doesn't work, you can use fastboot to install the boot.img file taken from the full factory image. If you already have it ready to go, it's faster than a full reinstall of the OS.
SkinnyT said:
How long did it take to boot after installing Magisk? I let my phone sit at the white boot screen for about 30 minutes before I had to reflash Pie again.
Click to expand...
Click to collapse
For me it did not take long for the Pixel to start after boot. Maybe a minute or two. It did take 5-10 minutes to run the Pie update.
Maybe it was because I originally installed Magisk 16 before going to version 16.7.
I agree with post-mortem's suggestion. It will be easier for you to reinstall Magisk before reinstalling the OS.
I've been starting out by flashing the factory image with adb. Then once it boots I can fastboot the twrp.img and get twrp into the recovery slot with no issues. I didn't get a chance today, but tomorrow I'll try with Magisk again.
post-mortem said:
Try installing the Magisk Uninstaller, then rebooting into system. If that doesn't work, you can use fastboot to install the boot.img file taken from the full factory image. If you already have it ready to go, it's faster than a full reinstall of the OS.
Click to expand...
Click to collapse
I did end up doing that, though I don't know if this itself solved my problem. I'll explain more below
daver68 said:
Not the exact same problem as yours, but I found that I wasn't able to boot into the OS after flashing Magisk 16.7. It would get to the animated "G" loading screen, but then reboot automatically and go into TWRP. Currently reflashing the stock (without wipe) and trying again.
Click to expand...
Click to collapse
I ended up fixing my problem. After posting this, I repeated my exact steps a few more times to make sure I wasn't doing something wrong.
1. boot into bootloader
2. fastboot factory image (without -w)
3. boot into stock Pie
4. fastboot boot twrp 3.2.2.0 image
5. install twrp 3.2.2.0 zip
6. reboot into recovery
7. flash Magisk 16.7
8. reboot into Pie
These steps didn't work, and I would always get into a bootloop that takes me straight to recovery
What I ended up doing that fixed my problem was the following
1. boot into bootloader
2. fastboot factory image (without -w)
3. boot into stock Pie
4. fastboot boot twrp 3.2.2.0 image
5. install twrp 3.2.2.0 zip
6. reboot into recovery
7. flash Magisk uninstaller
8. reboot recovery
9. flash Magisk 16.6
10. set boot partition to B
11. reboot into rooted Pie
Specifically, I used the Magisk Uninstaller, used an "older" version of Magisk (16.6, not the later 16.7), and I also changed my boot partition from A to B after flashing Magisk. This worked for me, and until I know specifically why, I'm going to just re-use this procedure on the next factory image update.
Hopefully this can help someone else having the same problem!
I am unlocked + rooted with Magisk. I want to stay that way.
Last time I upgraded from OOS 9.0.1 > 9.0.2 via UI, the upgrade wiped everything and I needed to start from scratch (as if I just got a new phone). Is there a way to make the upgrade seamless without losing everything? I want to upgrade to 9.0.3
https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232
Post #3 has the instructions you need
Long story short you need to flash the update via TWRP.
unknown00 said:
I am unlocked + rooted with Magisk. I want to stay that way.
Last time I upgraded from OOS 9.0.1 > 9.0.2 via UI, the upgrade wiped everything and I needed to start from scratch (as if I just got a new phone). Is there a way to make the upgrade seamless without losing everything? I want to upgrade to 9.0.3
Click to expand...
Click to collapse
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system
tabletalker7 said:
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system
Click to expand...
Click to collapse
Just to confirm that this is how I have upgraded to 9.0.3 without problems days ago.
For 4. I have used blue spark twrp
Sent from my ONEPLUS A6003 using Tapatalk
RASTAVIPER said:
Just to confirm that this is how I have upgraded to 9.0.3 without problems days ago.
For 4. I have used blue spark twrp
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
tabletalker7 said:
1. Download full ROM
2. Reboot to recovery
3. Flash full ROM
4. Flash TWRP
5. Reboot to recovery
6. Flash magisk
7. Reboot to system
Click to expand...
Click to collapse
2 questions - why can't I do #6 after #3? Can I?
Also, do I need to do #4 since I have it already installed?
unknown00 said:
2 questions - why can't I do #6 after #3? Can I?
Also, do I need to do #4 since I have it already installed?
Click to expand...
Click to collapse
You can't do either thing you want to do there because of the added fun of the OnePlus 6 having A/B partitioning. With A/B partitioning there is no recovery partition, and recovery is now a part of boot. You need to flash TWRP again because the update will overwrite TWRP with stock recovery. And you have to wait til after the reboot to recovery to install magisk so it gets the partitioning right.
Like above.
Flashing ROM Will also flash stock recovery so after ROM you need to flash twrp again,if you reboot without it it's lost.
Also why magisk isn't flashed right away is because: when you choose to reboot to twrp after the twrp flash it Will change slot, this way you Will get magisk on the correct slot.
All this can be done from the OS.
Install the ROM upgrade as usual,don't reboot.
Open magisk app
Search for a module a/b twrp (you Will only find one module) and install it.ndont reboot just yet.
Go to main screen of magisk
Press install, install, install to inactive slot (after OTA). After this install you can reboot.
Both works, I find the twrp way to be more convenient
I don't about stable i am on open beta 10 i root every beta without twrp using patch boot image i got update every time around 1.5 GB because i am rooted after update i just lose root everything same before update phone not wipe anything
I upgraded vom 9.0.1 to 9.0.3 by
- Downloading the full 9.0.3
- Copy them to the sdcard root directory
- Update via settings / manual update - DO NOT REBOOT
- Reinstall Magisk into inactive slot with Magisk Manager
- Reboot
Works. But Magisk 18 MagiskHide does not work properly on my OP6, so I had to downgrade to Magisk 17.2.
- Download latest TWRP BluSpark .img, Magisk 18 uninstaller, Magisk 17.2
- Copy uninstaller and Magisk 17.2 to sdcard root
- Reboot into Fastboot
- Boot into TWRP by fastboot boot <name of TWRP BluSpark .img file)
- flash uninstaller
- flash Magisk 17.2
- Clear Dalvik cache
- Reboot and setup Magisk (settings in Magisk manager regarding Hide and root permissions were lost).
- Uninstall duplicate Magisk Manager 6.1.x (not compatible with Magisk 17.2).
akxak said:
I upgraded vom 9.0.1 to 9.0.3 by
- Downloading the full 9.0.3
- Copy them to the sdcard root directory
- Update via settings / manual update - DO NOT REBOOT
- Reinstall Magisk into inactive slot with Magisk Manager
- Reboot
Works. But Magisk 18 MagiskHide does not work properly on my OP6, so I had to downgrade to Magisk 17.2.
- Download latest TWRP BluSpark .img, Magisk 18 uninstaller, Magisk 17.2
- Copy uninstaller and Magisk 17.2 to sdcard root
- Reboot into Fastboot
- Boot into TWRP by fastboot boot <name of TWRP BluSpark .img file)
- flash uninstaller
- flash Magisk 17.2
- Clear Dalvik cache
- Reboot and setup Magisk (settings in Magisk manager regarding Hide and root permissions were lost).
- Uninstall duplicate Magisk Manager 6.1.x (not compatible with Magisk 17.2).
Click to expand...
Click to collapse
No need to reinstall TWRP in the first method?
unknown00 said:
No need to reinstall TWRP in the first method?
Click to expand...
Click to collapse
I do not have TWRP installed, it is basically not necessary as OOS can be updated with the settings/manual update tool and Magisk can be reinstalled via Magisk manager.
I had to use TWRP solely to downgrade to Magisk 17.2 from Magisk 18 as this cannot be done with Magisk Manager. But for that purpose, it's enough to temporarly make TWRP available via fastboot boot command without permanently installing it.
If you have TWRP and want to keep it, that easy process doesn't work to upgrade the OS.
unknown00 said:
No need to reinstall TWRP in the first method?
Click to expand...
Click to collapse
If you wanna keep TWRP you do the way I described few posts up.....
tabletalker7 said:
You can't do either thing you want to do there because of the added fun of the OnePlus 6 having A/B partitioning. With A/B partitioning there is no recovery partition, and recovery is now a part of boot. You need to flash TWRP again because the update will overwrite TWRP with stock recovery. And you have to wait til after the reboot to recovery to install magisk so it gets the partitioning right.
Click to expand...
Click to collapse
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.
thejase said:
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.
Click to expand...
Click to collapse
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.
tabletalker7 said:
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.
Click to expand...
Click to collapse
I guess I'll just try this upcoming weekend to install magisk via the manager inside Android. I'll try to remember to report back. Thanks for the help.
thejase said:
So magisk installs to the opposite partition you're currently booting from? Only reason I ask is because previously, I missed the second reboot before installing magisk and the phone wouldn't boot (long boot logo and eventual automatic restart to recovery). Ultimately, I just permanently installed twrp and was going to wait till the weekend to try root again in case there were issues. I'm currently booting from slot A. How do I install magisk now in recovery? Should I be in slot A or B in recovery for install? Or can I now just do it from magisk manager? Thanks for the info.
Click to expand...
Click to collapse
tabletalker7 said:
I am not entirely sure if it does or not, but again the A/B partitioning puts things in the boot partition instead of the partitions you are used to. Installing TWRP changes the boot partition, so you need to reload that boot partition before installing magisk will work right.
Click to expand...
Click to collapse
thejase said:
I guess I'll just try this upcoming weekend to install magisk via the manager inside Android. I'll try to remember to report back. Thanks for the help.
Click to expand...
Click to collapse
As promised, I'm writing back with my findings. I believe some enabled module in magisk was the issue. What I did was uninstall magisk 18 with the latest uninstaller. Thinking it was V18 itself that was the problem, I then proceeded to install v17.3 on both slots (reboot to recovery in betweene). This worked and booted! It started to occur to me that I had not disabled any of my modules before installation of the rom/magisk. This is a big mistake as a lot of magisk modules are still using old formatting and cause new installations to fail if left enabled. Since an uninstall also disables all modules, I believe using 17.3 was not necessarily the solution but rather either disabling modules before an install, or uninstalling whatever version magisk was installed to begin with (which essentially disables/uninstalls those modules anyway). After installing 17.3 and getting it to boot, I just updated via magisk manager to v18 with no issues to speak of! Now comes the part where I need to remember all the installed modules I had and test them one by one.
For uninstallation of modules in twrp, you can use https://forum.xda-developers.com/apps/magisk/module-tool-magisk-manager-recovery-mode-t3693165 Or https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
I hope this helps someone!
Like the title says, I can´t boot to recovery (Oneplus one). If I try to boot to recovery, I´m ending in the Qualcomm CrashDump Mode.
I have a Oneplus 7 Pro with Stable 10.0 BA FW.
Rooted with Magisk (Patched Boot.img) Is this causing the problem?
After pressing Vol+ and powerbutton, the devices boots normally.
Thanks in advance.
RealDanyo said:
Like the title says, I can´t boot to recovery (Oneplus one). If I try to boot to recovery, I´m ending in the Qualcomm CrashDump Mode.
I have a Oneplus 7 Pro with Stable 10.0 BA FW.
Rooted with Magisk (Patched Boot.img) Is this causing the problem?
After pressing Vol+ and powerbutton, the devices boot normally.
Thanks in advance.
Click to expand...
Click to collapse
I had the same issue this morning when trying to update to 10.0.1. Just boot to bootloader and boot twrp then install 10.
I think is the magisk update (magisk 20.0) that causes this, because it's happening to me in the beta 3 and before I updated magisk it was working fine with the beta 2
ItsTecnoDavid said:
I think is the magisk update (magisk 20.0) that causes this, because it's happening to me in the beta 3 and before I updated magisk it was working fine with the beta 2
Click to expand...
Click to collapse
I have no issues with magisk or twrp.
It might be the way you are installing ota or rom.
Might be model specific not sure as I don't know what model you are on. Mine is GM1915.
I'm talking about the official recovery
GM21AA, exactly the same situation (from 10 stable to 10.0.1 and magisk from 19.4 beta to 20) and the stock recovery bump into Qualcomm Crashdump problem here, system bootup normal as well as bootloader.
Troubleshooting:
1. Local update twice, install magisk at inactive slot OTA before reboot, for Android 10's A/B partitions machinasm , try let magisk patch both boot.img. Same...
2. Local update and reboot, lost root but stock recovery work, Fastboot boot twrp.img (latest, not flash, cause I don't need the permanent twrp)->twrp install magisk, reboot system, then, again, same problem.
Todo:
Magisk manager or twrp uninstall magisk, but if it's fail maybe ended up to bootloop, scary.
May try to install back old 19.4 magisk.zip via twrp, it's working in 10.0.0
Anyone with the same problem have any idea?
Thats the exact same error I ran into.
But as mentioned earlier, I never had TWRP on my OP7P. I flashed the patched boot.img via adb and I´m still on 10.0 BA Firmware.
I thought TWRP dosn´t work on Android Q (I´m coming from an Pixel3 and there it won´t work) So maybe I will give TWRP a try tomorrow. Are there different versions or is the official one the best?
RealDanyo said:
Thats the exact same error I ran into.
But as mentioned erlier, I never had TWRP on my OP7P. I flashed the patched boot.img via adb and I´m still on 10.0 BA Firmware.
I thought TWRP dosn´t work on Android Q (I´m coming from an Pixel3 and there it won´t work) So maybe I will give TWRP a try tomorrow. Are there different versions or is the official one the best?
Click to expand...
Click to collapse
The recovery here is the one to use.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Be sure to read through
So thanks erveryone who helped.
I now have TWRP running as recovery. So there is no need for official recovery. (and no Qualcomm CrashDump Mode)
Had this happen to me earlier this week. Just ended up using the MSM tool and restoring shipping firmware. You can look for the unbricking thread here for more info on that.
Yea, this just happened to me. Updated Magisk, Updated to 10.0.1 from 10.0. Booted fine.
Re-installed a few magisk modules (didn't just re check the modules, but reinstalled each)
Now OS won't boot, and recovery goes to Crash Dump. Would be ok if OS wouldn't bootloop and I could get to OS.
Oh, and my ADB now is an unauthorized device while its in bootloop mode
EDIT:
phew. Tried to hold volume up+dn rather than up or dn, got into bootloader. Able to fastboot boot TWRP and then delete problematic RIRU magisk modules. All is well in the world now...
I don't get it why it have to be so hard.
I'm constantly soft bricking/ bootlooping this phone when trying to do simple things such flashing magisk and twrp. I remember it being so much easier with my Poco F1, never got close to bricking it.
Now every little mistake ends with a bricked phone and 5 hours on the internet trying to understand why
WillyRy said:
Yea, this just happened to me. Updated Magisk, Updated to 10.0.1 from 10.0. Booted fine.
Re-installed a few magisk modules (didn't just re check the modules, but reinstalled each)
Now OS won't boot, and recovery goes to Crash Dump. Would be ok if OS wouldn't bootloop and I could get to OS.
Oh, and my ADB now is an unauthorized device while its in bootloop mode
EDIT:
phew. Tried to hold volume up+dn rather than up or dn, got into bootloader. Able to fastboot boot TWRP and then delete problematic RIRU magisk modules. All is well in the world now...
Click to expand...
Click to collapse
Same issue here and no TWRP installed.
I did ADB REBOOT FASTBOOT and was able to install the twrp image by FASTBOOT BOOT twrp-3.3.1-70-guacamole-unified-Q-mauronofrio.img
Going to try and remove Magisk and see if I can salvage my data and then re-install Magisk afterwards.
Ok...got back into the system by flashing the Magisk Uninstaller in TWRP that is here: https://magiskroot.net/md/Magisk_Manager_for_Recovery_Mode_(mm)-2019.4.4.zip
Went to advanced in TWRP, then to terminal, then typed mm.
Typed in C for Core only to load into system without Magisk. Deleted my Magisk modules that may have interfered with it (I had an older version of No Limit that I should have updated prior. After removing and rebooting back into system, all is fine now.
JLine05 said:
Same issue here and no TWRP installed.
I did ADB REBOOT FASTBOOT and was able to install the twrp image by FASTBOOT BOOT twrp-3.3.1-70-guacamole-unified-Q-mauronofrio.img
Going to try and remove Magisk and see if I can salvage my data and then re-install Magisk afterwards.
Ok...got back into the system by flashing the Magisk Uninstaller in TWRP that is here: https://magiskroot.net/md/Magisk_Manager_for_Recovery_Mode_(mm)-2019.4.4.zip
Went to advanced in TWRP, then to terminal, then typed mm.
Typed in C for Core only to load into system without Magisk. Deleted my Magisk modules that may have interfered with it (I had an older version of No Limit that I should have updated prior. After removing and rebooting back into system, all is fine now.
Click to expand...
Click to collapse
Yea man, things are hinkey this update.
My big problem was i had twrp but it got wiped i guess (could no longer access) and couldn't access adb nor fastboot. But finally got into bootloader (cmd fastboot) so was able to fix.
Easier solution than installing Magisk uninstaller (presuming one has twrp installed, which would be the case if able to flash Magisk uninstaller) is go to TWRP>advanced>file manager and navigate data/adb/modules and delete from there
DO you guys know if there is an updated magisk being developed or what is the way to fix it? Uninstall magisk via TWRP (since I can temporarily install and get into TWRP using the all in one tool by the TWRP developer). Then install TWRP and then Install Magisk ?
I have same problem
How to fix it and bring back stock recovery?
wawanRedblack said:
I have same problem
How to fix it and bring back stock recovery?
Click to expand...
Click to collapse
Can you boot OS?
Can you get to bootloader?
WillyRy said:
Can you boot OS?
Can you get to bootloader?
Click to expand...
Click to collapse
Yes i can boot os and bootloader is ok
EDIT: After a few reboots, TWRP stopped working.. now if I try to enter recovery, I get into fastboot instead. But I can still boot the system fine and I still have Magisk. Sorry.. looks like TWRP on this version is still a no-go for now..
I leave the guide here to keep the discussion open, though.. and after the steps some more info on what exactly worked for me..
Hi all, the following steps worked for me (not really, see edit above), but as usual please proceed at your own risk, backup everything before, and be prepared to reinstall everything from scratch if something goes wrong. I am not responsible of anything that happens to your devices when following this guide.
Prerequisites:
- OnePlus 6 (might work also for 6t, but it's untested)
- Oxygen OS 9 open beta 25 (Might work also with the stable version, but again, untested)
- Enable the "advanced reboot" option in developer options.
- latest blu_spark TWRP installed (3.3.1 v9.101)
- if you have Magisk, make sure it's version 20.0 or later (previous versions don't support Android 10)
- if you have Magisk modules, it's highly recommended to disable or uninstall them before proceeding, as some of them might not be compatible with Android 10 and eventually cause a bootloop.
- A computer that is able to run fastboot commands and that you can connect your phone to.
Now, the steps:
- Reboot into TWRP, open the "reboot" menu and take a note of your current active slot (can be a or b)
- Go back to Oxygen OS and install Android 10 open beta 1 through system updates. At the end of the installation, DO NOT PRESS "REBOOT".
- Press the power button and from the advanced reboot menu, reboot into bootloader.
- Connect the phone to the pc.
- If your active slot, noted in the first step, was "a", type "fastboot --set-active=a" . If it was "b", use the same command but replace the final letter with "b".
- On the phone, use the volume buttons to select "recovery mode", and press the power button to confirm.
- You should now be into TWRP: install TWRP again using its installation zip file, DO NOT REBOOT.
- Go to the reboot menu, and change the active slot to the other one (depending on your currently active one).
- Still in TWRP, reboot to recovery.. you should land in TWRP again.
- If you had Magisk, or if you want it, flash it.
- Reboot to system.
If everything goes well, you should now be on Oxygen OS 10 open beta 1, with TWRP installed!
Note: the current version of TWRP does not support flashing the new OnePlus open betas, so when a new open beta is released and you want to update, you will have to go through this process again (until a new compatible TWRP is released).
EDIT 2: Just to give some more information in case someone else wants to try, here's what I did AFTER the steps below:
- Rebooted into OOS open beta 1, just to check that it was booting.. worked.
- Rebooted into TWRP and did a complete wipe, including the internal storage (I wanted a clean install of OB1)
- Rebooted into OOS and did the phone setup (Google account, ecc) including setting up a lockscreen pattern, but no figerprints yet.
- Rebooted again into TWRP to install Magisk, and everything worked, TWRP also asked for my pattern and decrypted data correctly
- After that I didn't reboot anymore for a while, and completed the setup with apps, fingerprints, etc.. and also installed a magisk module (quickswitch), but without using recovery.
- The next time I tried to reboot into recovery, I wasn't able anymore.. I was getting into fastboot instead, but the system can still boot just fine.
cc_rock said:
Hi all, the following steps worked for me, but as usual please proceed at your own risk, backup everything before, and be prepared to reinstall everything from scratch if something goes wrong. I am not responsible of anything that happens to your devices when following this guide.
Prerequisites:
- OnePlus 6 (might work also for 6t, but it's untested)
- Oxygen OS 9 open beta 25 (Might work also with the stable version, but again, untested)
- Enable the "advanced reboot" option in developer options.
- latest blu_spark TWRP installed (3.3.1 v9.101)
- if you have Magisk, make sure it's version 20.0 or later (previous versions don't support Android 10)
- if you have Magisk modules, it's highly recommended to disable or uninstall them before proceeding, as some of them might not be compatible with Android 10 and eventually cause a bootloop.
- A computer that is able to run fastboot commands and that you can connect your phone to.
Now, the steps:
- Reboot into TWRP, open the "reboot" menu and take a note of your current active slot (can be a or b)
- Go back to Oxygen OS and install Android 10 open beta 1 through system updates. At the end of the installation, DO NOT PRESS "REBOOT".
- Press the power button and from the advanced reboot menu, reboot into bootloader.
- Connect the phone to the pc.
- If your active slot, noted in the first step, was "a", type "fastboot --set-active=a" . If it was "b", use the same command but replace the final letter with "b".
- On the phone, use the volume buttons to select "recovery mode", and press the power button to confirm.
- You should now be into TWRP: install TWRP again using its installation zip file, DO NOT REBOOT.
- Go to the reboot menu, and change the active slot to the other one (depending on your currently active one).
- Still in TWRP, reboot to recovery.. you should land in TWRP again.
- If you had Magisk, or if you want it, flash it.
- Reboot to system.
If everything goes well, you should now be on Oxygen OS 10 open beta 1, with TWRP installed!
Note: the current version of TWRP does not support flashing the new OnePlus open betas, so when a new open beta is released and you want to update, you will have to go through this process again (until a new compatible TWRP is released).
Click to expand...
Click to collapse
Anyone tried?
This sounds plausible. Nice!
Question though, how much working functionality remains? Can TWRP be used to install zips, clear cache, do factory reset, install magisk stuff, etc..? Are these still compatible with android 10? Have you tried to do something with it?
kyljys said:
This sounds plausible. Nice!
Question though, how much working functionality remains? Can TWRP be used to install zips, clear cache, do factory reset, install magisk stuff, etc..? Are these still compatible with android 10? Have you tried to do something with it?
Click to expand...
Click to collapse
Hi, first of all, see the edit above.. looks like my TWRP stopped working now.. but it was working for a while.
Initially I was able to flash TWRP itself, and then flash Magisk (which still works) .. not sure exactly when TWRP stopped working.
I bet it stopped working after magisk install. It does the same fir the stock recovery also. No recovery, goes to bootloader.
Oh.. So that means we either have twrp and no root... Or root and no recovery... Choose whatever one wants... Hehe.. Thnx op for the efforts though
cc_rock said:
Hi, first of all, see the edit above.. looks like my TWRP stopped working now.. but it was working for a while.
Initially I was able to flash TWRP itself, and then flash Magisk (which still works) .. not sure exactly when TWRP stopped working.
Click to expand...
Click to collapse
One thing to try would be installing magisk 19.4 from twrp. In canary thread there's a discussion on this very problem with other oneplus devices with A10 and magisk 20.1 that the recovery disappears. Magisk 19.4 did have some fixes regarding Android 10, maybe worth a shot?
Though we could wait the next version of magisk as this problem seems to be under investigation.
I'm able to to keep twrp with magisk 19.3
[email protected] said:
I'm able to to keep twrp with magisk 19.3
Click to expand...
Click to collapse
Ive also managed to do this after a fair bit of fiddling. A quick guide below as im off to bed.
1) you need to be rooted
2) Flash twrp installer in magisk manager (twrp-3.3.1-x_blu_spark_v9.101_op6.zip)
3) reboot to bootloader
3) fastboot flash boot boothybridbeta2.img ( https://drive.google.com/open?id=1JCltKatjRUk1XdEibAme8MnDJxMkzhwE ) boot image is from [ROM][PORT][10.0.0] OnePlus7 Open Beta 3 Port for OnePlus 6 [12.10.19]
4) fastboot reboot
5) reboot to recovery via adb
6) run magisk uninstaller.zip
7) flash stock boot.img in twrp
8) flash twrp installer.zip
9) reboot recovery (to see if it works)
10) reboot phone and choose boot to recovery from phone system again to test it works
11) install magisk v19.3 installer zip in twrp
12) reboot
Hey, after installing android 11 on my Oneplus 6 I have servere issues on getting root back.
Both methods I used result in a stuck boot.
Method 1: fastboot boot twrp, then install magisk.zip (tried with both 21.4 (last with a zip) and the renamed 23.0 (from apk to zip)
Method 2: Extracted boot.img from my OTA update, then patched with magisk 23.0.
Flashed the new boot.img -with fastboot -with twrp both result in a stuck boot.
Suprisingly flashing the extracted boot.img from the OTA boots fine, but that image is without magisk
Update: I have extracted the boot.img directly from the phone, patched it and it still doesn't work
I've also tried fastboot boot twrp with a variety of versions of twrp after upgrading to 11.1.1.1 but with no success.
If someone could recommend a verified way to root a op6 with 11.1.1.1 I'd appreciate it
Thratchen said:
I've also tried fastboot boot twrp with a variety of versions of twrp after upgrading to 11.1.1.1 but with no success.
If someone could recommend a verified way to root a op6 with 11.1.1.1 I'd appreciate it
Click to expand...
Click to collapse
twrp actually works, but after flashing magisk or flashing a magisk boot.img it breaks. I have a working version here
Ping me if you get magisk working
I can confirm the TWRP-3.5.2-enchilada-Nebrassy-2.img run on my OP6 without any issue and allowed my to install the latest magisk, giving me a fully functioning root for my 11.1.1.1 ROM. Thanks for the help
To remember!
Thratchen said:
I can confirm the TWRP-3.5.2-enchilada-Nebrassy-2.img run on my OP6 without any issue and allowed my to install the latest magisk, giving me a fully functioning root for my 11.1.1.1 ROM. Thanks for the help
Click to expand...
Click to collapse
Which installation method of magisk did you use?
How long did you wait after first boot?
I downloaded the full 11.1.1.1 ROM as I was upgrading from a previous rooted 10.3.x version. I placed this file in the phones root directory and use the "local upgrade" feature.
When that completed I rebooted the phone a few times just to make sure everything was working as expected. I usually waited 1-2 minutes before rebooting every time.
Next I placed the latest magisk version file into the root of the phone rebooted into the bootloader and performed fastboot boot TWRP-3.5.2-enchilada-Nebrassy-2.img which booted into the TWRP as expected. Then I installed the magisk.zip and rebooted the phone into a nice newly rooted magisk environment. Tbh I didn't wait anymore 10-20 seconds to reboot after installing magisk while in TWRP.
I hope that's helpful for you
Thratchen said:
I downloaded the full 11.1.1.1 ROM as I was upgrading from a previous rooted 10.3.x version. I placed this file in the phones root directory and use the "local upgrade" feature.
When that completed I rebooted the phone a few times just to make sure everything was working as expected. I usually waited 1-2 minutes before rebooting every time.
Next I placed the latest magisk version file into the root of the phone rebooted into the bootloader and performed fastboot boot TWRP-3.5.2-enchilada-Nebrassy-2.img which booted into the TWRP as expected. Then I installed the magisk.zip and rebooted the phone into a nice newly rooted magisk environment. Tbh I didn't wait anymore 10-20 seconds to reboot after installing magisk while in TWRP.
I hope that's helpful for you
Click to expand...
Click to collapse
Thanks for the reply, as a last question: Which magisk version did you use (could you link i?t). I assume you took the magisk v23 apk and renamed it to .zip? or what did you do?
Yes. I used the latest canary build of magisk and simply renamed it to magisk.zip
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Thratchen said:
Yes. I used the latest canary build of magisk and simply renamed it to magisk.zip
https://raw.githubusercontent.com/topjohnwu/magisk-files/canary/app-debug.apk
Click to expand...
Click to collapse
Hmm, I perfectly copied your instructions and still get a bootloop. Even reflashed 11.1.1.1 again. Might be time for a reset
Do you actually get a bootloop or it just gets stuck in the unlocked bootloader warning screen?
Mine hangs there for several minutes before booting, I reflashed several times because of it but all I had to do is wait.
vkass said:
Do you actually get a bootloop or it just gets stuck in the unlocked bootloader warning screen?
Mine hangs there for several minutes before booting, I reflashed several times because of it but all I had to do is wait.
Click to expand...
Click to collapse
I leave the "bootloader unlocked" screen and the rotating "circle" animation plays. I even can connect via adb logcat to see the boot logs (but I do not understand them, though they clearly loop)
is there a zip version of TWRP-3.5.2-enchilada-Nebrassy-2 available that I can flash or can i flash the standard twrp latest zip after booting in to the nebrassy recovery so that it is permanant recovery?
Also can I flash the latest 23 relase of magisk or does it have to be the canary?
I was able to successfully boot in to the nebrassy recovery but i don't want to get in to a permanent bootloop if the standard twrp zip will break things after flashing or the stable relase of magisk will get me in to a bootloop
Thanks @UraniumDonut !
tacohell said:
is there a zip version of TWRP-3.5.2-enchilada-Nebrassy-2 available that I can flash or can i flash the standard twrp lat est zip after booting in to the nebrassy recovery so that it is permanant recovery?
Also can I flash the latest 23 relase of magisk or does it have to be the canary?
I was able to successfully boot in to the nebrassy recovery but i don't want to get in to a permanent bootloop if the standard twrp zip will break things after flashing or the stable relase of magisk will get me in to a bootloop
Thanks @UraniumDonut !
Click to expand...
Click to collapse
The twrp image should have a button in twrp called "install current twrp to recovery" or similar. With magisk I cannot help you as I have bootloops with every version of magisk , but @Thratchen had success with the canary version (I didn't)
UraniumDonut said:
I leave the "bootloader unlocked" screen and the rotating "circle" animation plays. I even can connect via adb logcat to see the boot logs (but I do not understand them, though they clearly loop)
Click to expand...
Click to collapse
Try to flash the full update zip with twrp, it will flash to both partitions, then try to flash latest magisk renamed apk in twrp.
vkass said:
Try to flash the full update zip with twrp, it will flash to both partitions, then try to flash latest magisk renamed apk in twrp.
Click to expand...
Click to collapse
Thanks, I’ll try. A few questions:
Wipe dalvik after flash?
Boot into system or instant flash magisk?
Wipe dalvik after magisk?
Which magisk?(canary or 23.0)?
Thanks!
UraniumDonut said:
The twrp image should have a button in twrp called "install current twrp to recovery" or similar. With magisk I cannot help you as I have bootloops with every version of magisk , but @Thratchen had success with the canary version (I didn't)
Click to expand...
Click to collapse
Thhank @UraniumDonut - that worked - I have never before used that method and honestly didn't even know about it. I use the official documented twrp way which is to first fastboot in to twrp and then install the zip file which has to be located on the phone file system. This method seems a lot easier!
As to magisk, I usually flash that from twrp using the zip file method and never have had any issues. But with all the issues surrounding oos 11 I am playing it safe as I don't want to get in to a boot loop. Will do some more research before I try something. But thanks to you I have made 1 step forward progress!
UraniumDonut said:
Thanks, I’ll try. A few questions:
Wipe dalvik after flash?
Boot into system or instant flash magisk?
Wipe dalvik after magisk?
Which magisk?(canary or 23.0)?
Thanks!
Click to expand...
Click to collapse
I wiped
No need to boot first
Wiping once is enough
I'm using 23
I did not install twrp at all, just booted it, flashed Ota and magisk and reboot.
vkass said:
I wiped
No need to boot first
Wiping once is enough
I'm using 23
I did not install twrp at all, just booted it, flashed Ota and magisk and reboot.
Click to expand...
Click to collapse
I'm out of ideas. I followed your guide exactly.
Flashed 11.1.1.1 OTA.zip
The log said "installing to inactive slot _b, reboot recovery to flash more zips"
I wiped dalvik,
I rebooted into recovery slot b (I didnt boot into system)
I installed magisk 23.0 APK renamed to zip. It installed into slot b.
I did not wipe dalvik.
I rebooted into system.
I still get a stuck boot (OnePlus circles rotating)
Bonus: after "fastboot flash boot stock_boot.img" it boots fine (but no root)
I never installed TWRP, just "fastboot boot TWRP"
I understand nothing
Just for reference here
UraniumDonut said:
I'm out of ideas. I followed your guide exactly.
Flashed 11.1.1.1 OTA.zip
The log said "installing to inactive slot _b, reboot recovery to flash more zips"
I wiped dalvik,
I rebooted into recovery slot b (I didnt boot into system)
I installed magisk 23.0 APK renamed to zip. It installed into slot b.
I did not wipe dalvik.
I rebooted into system.
I still get a stuck boot (OnePlus circles rotating)
Bonus: after "fastboot flash boot stock_boot.img" it boots fine (but no root)
I never installed TWRP, just "fastboot boot TWRP"
I understand nothing
Click to expand...
Click to collapse
I posted detailed steps if you want to give this a try @UraniumDonut: https://forum.xda-developers.com/t/how-to-root-op6-11-1-1-1.4344269/#post-85765879