So, has anyone tried the Android 14 developer preview 1? I have and it runs very well on our phone. Would love to hear your impressions.
I tried it briefly on my Pixel 5. Since Magisk does not appear to fully support 14 yet (Zygisk does not work), I ended up going back to TQ1A and am running the developer preview on an Android Virtual Device instead.
Tried it out just now, magisk doesn't detect root at all of a patched boot image, so its a no go as far as a daily use device for me at the moment
TechX1991 said:
Tried it out just now, magisk doesn't detect root at all of a patched boot image, so its a no go as far as a daily use device for me at the moment
Click to expand...
Click to collapse
You have to use the Pixel 7 boot image to patch and flash, like we did for some of the QPR2 Betas.
TechX1991 said:
Tried it out just now, magisk doesn't detect root at all of a patched boot image, so its a no go as far as a daily use device for me at the moment
Click to expand...
Click to collapse
I do not need a rooted devices, so I just used the Developer Preview to check out the new Android 14 release before it is officially released on my Bluejay.
V0latyle said:
I tried it briefly on my Pixel 5. Since Magisk does not appear to fully support 14 yet (Zygisk does not work), I ended up going back to TQ1A and am running the developer preview on an Android Virtual Device instead.
Click to expand...
Click to collapse
Have you tried Canary 25206? Magisk reports "Zygisk: Yes" (with Zygisk enabled in settings) for me on my Pixel 6 Pro running A14 DP1.
Lughnasadh said:
Have you tried Canary 25206? Magisk reports "Zygisk: Yes" (with Zygisk enabled in settings) for me on my Pixel 6 Pro running A14 DP1.
Click to expand...
Click to collapse
If I can figure out how to get Magisk running on an AVD, I'll try that. Tried patching the ramdisk image, that didn't work.
Lughnasadh said:
You have to use the Pixel 7 boot image to patch and flash, like we did for some of the QPR2 Betas.
Click to expand...
Click to collapse
ohhhhh. So just download the pixel 7 beta, extract the boot.img, patch it and flash it?
TechX1991 said:
ohhhhh. So just download the pixel 7 beta, extract the boot.img, patch it and flash it?
Click to expand...
Click to collapse
Yes
Related
Started to download but it is 1am.
Need to sleep
Strange issue.
After installing full OTA, I am not able to use magisk to patch the OTA slot. Option not available in magisk. Only uninstall.
UPDATE: I had a to low DPI resolution, 320dp. That was reason I couldn't see the install button.
If I reboot now, I will loose root.
BTW. I do not use TWRP
Anyway. Rebooted and lost root. Will wait for patched boot image.
Everything else seems to work
UPDATE: Used the beta 1 patched boot image to fastboot -- used magisk to patch -- root is back!
I'm uploading to Google Drive now
Thanks for sharing, downloading
Sent from my ONEPLUS A6003 using Tapatalk
https://otafsg.h2os.com/patch/amazo...us6Oxygen_22_OTA_007_all_1809071908_8f1d8.zip
Official OOS OB 2 link from One Plus
Here is link to my Google Drive download and instructions
https://forum.xda-developers.com/on...droid-pie-oxygenos-beta-t3831803/post77568541
alirey said:
Started to download but it is 1am.
Need to sleep
Strange issue.
After installing full OTA, I am not able to use magisk to patch the OTA slot. Option not available in magisk. Only uninstall.
UPDATE: I had a to low DPI resolution, 320dp. That was reason I couldn't see the install button.
If I reboot now, I will loose root.
BTW. I do not use TWRP
Anyway. Rebooted and lost root. Will wait for patched boot image.
Everything else seems to work
UPDATE: Used the beta 1 patched boot image to fastboot -- used magisk to patch -- root is back!
Click to expand...
Click to collapse
can you explain me exactly how you fixed the root problem? Where is the OOS beta 1 patch boot image, and how would i use magisk to patch it, sry i'm noob
edit: nevermind i figured it out, thanks!
Is t mobile volte working on this build?
fantasy2c said:
Is t mobile volte working on this build?
Click to expand...
Click to collapse
VoLte and VoWifi work fine now on Tmobile USA on OB2.
SMS786 said:
VoLte and VoWifi work fine now on Tmobile USA on OB2.
Click to expand...
Click to collapse
Awesome thank you
alirey said:
Started to download but it is 1am.
Need to sleep
Strange issue.
After installing full OTA, I am not able to use magisk to patch the OTA slot. Option not available in magisk. Only uninstall.
UPDATE: I had a to low DPI resolution, 320dp. That was reason I couldn't see the install button.
If I reboot now, I will loose root.
BTW. I do not use TWRP
Anyway. Rebooted and lost root. Will wait for patched boot image.
Everything else seems to work
UPDATE: Used the beta 1 patched boot image to fastboot -- used magisk to patch -- root is back!
Click to expand...
Click to collapse
You can root without using patched boot image
https://forum.xda-developers.com/oneplus-6/how-to/root-solve-issue-oxgyen-os-beta-1-t3839939
does this happen to you guys too when quick switching between apps? in oos beta 1 and still problem persists in oos beta 2
kewlest22 said:
does this happen to you guys too when quick switching between apps? in oos beta 1 and still problem persists in oos beta 2
Click to expand...
Click to collapse
Yes, this occurs when you use any launcher other than the OnePlus stock launcher.
While it wasn't this broken, in the HydrogenOS beta 2 the quick switch performed notably worse when using a non-stock launcher.
This issue, and issues like it, may effectively end up circumvented in the future when third party launchers start implementing their own recent apps implementations.
Open beta 2 changelog
Moderator Information,
Thread closed, We have an existing thread here: [Official Android Pie Beta] Oxygen OS Open Beta 2 for the OnePlus 6 .
Many thanks,
Stephen
Just Posted
https://developers.google.com/android/images#sunfish
fronto said:
Just Posted
https://developers.google.com/android/images#sunfish
Click to expand...
Click to collapse
I just checked my 4a with the Check for Updates button under settings and Android 11 is there waiting for me to d/l and install.
I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?
Just updated with no issues, but I'm not rooted yet. Only thing I really want is custom accent color (red), so not sure if it's worth rooting.
Sent from my Pixel 4a using XDA Labs
hate to say it but I think at this point that Magisk 20.4 (Manager 7.5.1) cannot root Android 11 on this phone. I have posted this finding on the rooting thread asking if anyone has had success:
https://forum.xda-developers.com/pixel-4a/how-to/guide-unlock-root-pixel-4a-t4153773/page4
I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.
Well I got an email from Google saying that android 11 was waiting for me to download. So I checked updates and it says my device is up to date. So I guess maybe verizon does hold up updates.
moeava said:
I unrooted, applied update, installed Magisk Canary build, patched boot image from downloaded Factory Image, fastboot flash boot... and have successfully rooted my 4a on w/11.
Click to expand...
Click to collapse
where did you find it? nvrmnd https://github.com/topjohnwu/magisk_files/tree/canary
@tcat007 @fronto
For anyone looking to root, you need magisk canary, latest build at time of writing (20424) works fine for me. Took the OTA from 10 to 11 following the magisk OTA update guide here worked like a charm: https://topjohnwu.github.io/Magisk/ota.html
However, somethings seemed to have changed in 11. For audio apps like jdsp and v4a, you'll need to run this in terminal (only needs done once):
Code:
su -c settings put global hidden_api_policy 1
Also note that sbin is gone too (least on pixel 4a) so v4a app install won't work properly (it's being worked on)
fronto said:
I successfully applied the OTA update, then extracted the boot.img from the full image (both versions matching RP1A.200720.011), patched with Magisk, and then flashed it, but now phone wont boot. Just getting the G startup logo for over 10 min now. Has anyone had success with this method? Is there a better way to do it?
Click to expand...
Click to collapse
You need to use latest canary
Stable doesn't yet support 11 afaik
tthalheim said:
You need to use latest canary
Stable doesn't yet support 11 afaik
Click to expand...
Click to collapse
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse
good deal...yeah I figured with the pre-patched boot.img, a lot of people could avoid messing with canary alltogether and just keep normal stable.
Agreed 11 does not seem all that revolutionary. ...but all is working well now with no complaints
Archangel said:
Yeah I dont like that canary Magisk so I used your advice and flashed the patched boot.img and then went back to stable Magisk. I am a little underwhelmed with Android 11 maybe its just me.
Click to expand...
Click to collapse
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk
Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I went back to stable for manager only.
jrkruse said:
If you’re running boot imaged patched with magisk canary then your running magisk canary
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Archangel said:
Yeah brother all I was saying is that I dont like the canary design for Magisk Manager so I wet went back to stable for manager only.
Click to expand...
Click to collapse
Oh ok
Sent from my iPhone using Tapatalk
fronto said:
You only need Canary to create the patched boot file. After it's been flashed, you can run Stable.
Just flash the pre-patched boot file and keep stable:
magisk_patched_sunfish-rp1a.200720.011.img
Click to expand...
Click to collapse
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you
mustbevick said:
Thank you for the upload. Can this be flashed in magisk? I presume no.
Can you clarify the steps? I'm already on android 10 rooted.
1. Uninstall magisk / Restore image
2.. Download install Android 11 / no reboot
3..... ? Then with patched boot.
Thank you
Click to expand...
Click to collapse
Its not flashed in Magisk. Its flashed using fastboot via a computer connection. With that file, you never need to touch Canary manager.
1. uninstall Magisk but you keep Magisk Manager
2. update to Android 11 via OTA or with full image provided you revise the flash-all to not wipe, or just manually issue each command.
3. make sure your 11 is up and running
4. reboot to bootloader, connect PC
5. fastboot flash boot magisk_patched_sunfish-rp1a.200720.011.img
6. reboot and open regular stable Magisk Manager
enjoy
I've rooted my 4a with magisk with the Aug factory image (android 10). I have the both Titanium Pro and Mybackup Pro - Do either of those programs create an image backup similar to the image I create of my PC using a program like Acronis, so that I could just re-install the Android 10 system if I don't like Android 11? If those programs don't do that is there any program that will do that?
Has anyone else noticed x google enrollment then updating message every (re) boot? I must have done something wrong. I got magisk working nicely. Can install itself, modules, ctsProfile is true, whatevs... But nothing else gets a su toast. Not too worried with it this first week or so.. I'll stab again weekend after next.
Sent from my Pixel 4a using Tapatalk
Has anyone updated to Android 12 and successfully rooted again with magisk? It seems from the Pixel 5 thread that there are problems with this..
I have removed root and restored stock boot + updated to Android 12. Have downloaded the factory image and am ready to patch + flash magisk patched boot, but I am reluctant to try after reading the Pixel 5 thread.
Sure, I've done it already.
Check here.
Worked for me too.
I'm starting to think that the 4a 5G and 5 (and presumably all newer models) have this restriction. Not sure why the 4a does not.
a1291762 said:
Worked for me too.
I'm starting to think that the 4a 5G and 5 (and presumably all newer models) have this restriction. Not sure why the 4a does not.
Click to expand...
Click to collapse
I have a Pixel 5 running official Android 12. I upgraded from a magisk rooted Android 11. When I flash the patched boot image in fastboot mode, restarting the device only takes me back to fastboot mode. The only way I can get past fastboot mode into Android 12 is to reflash the stock boot image.
Do I need to disable dmverity, etc.?
Skeetch79 said:
I have a Pixel 5 running official Android 12. I upgraded from a magisk rooted Android 11. When I flash the patched boot image in fastboot mode, restarting the device only takes me back to fastboot mode. The only way I can get past fastboot mode into Android 12 is to reflash the stock boot image.
Do I need to disable dmverity, etc.?
Click to expand...
Click to collapse
I haven't been flowing this thread since it doesn't apply to me but the last thing I saw seemed to suggest upgrading and then trying to figure it out didn't work. Check it out, maybe they got further.
[Closed] Android 12 Update and Root ***Obsolete***
Update 12-16: I am closing this thread as it is no longer relevant. Please refer to this guide.
forum.xda-developers.com
So with the beta QPR2 is known that Pixel 6 and 6 Pro can't be rooted with the magisk method.
m_pastuszek said:
Guys, see https://github.com/topjohnwu/Magisk/issues/6441.
It looks like Google released corrupted boot image.
To make it work, You need to path and flash boot image from Pixel 7.
Pixel 6 -> Pixel 7 boot image.
Pixel 6 Pro -> Pixel 7 Pro boot image.
I don't know what about Pixel 6a.
Click to expand...
Click to collapse
This seems to be the solution. I want to try to flash the Pixel 7 boot image with magisk path, but I'm afraid of brick / bootloop my device, can I do it safe?
Thanks everyone
charly30 said:
So with the beta QPR2 is known that Pixel 6 and 6 Pro can't be rooted with the magisk method.
This seems to be the solution. I want to try to flash the Pixel 7 boot image with magisk path, but I'm afraid of brick / bootloop my device, can I do it safe?
Thanks everyone
Click to expand...
Click to collapse
Dont flash it, just boot it.
fastboot boot "patched boot"
ctfrommn said:
Dont flash it, just boot it.
fastboot boot "patched boot"
Click to expand...
Click to collapse
Unable to root Pixel 6a with either fastboot boot/flash boot.... Also couldn't find a way to keep any custom recovery after flashing stock image to sideload Magisk APK..
Looks like another waiting game?
Esb1809 said:
Looks like another waiting game?
Click to expand...
Click to collapse
No idea.....and why I dont mess with stock
Esb1809 said:
Unable to root Pixel 6a with either fastboot boot/flash boot.... Also couldn't find a way to keep any custom recovery after flashing stock image to sideload Magisk APK..
Looks like another waiting game?
Click to expand...
Click to collapse
You can root using 'fastboot flash boot patchedboot.img'
It seems 6a boot image has issue.
Use pixel 7 pro 's boot image for magisk patching instead of 6a. Also install latest Magisk canary build.
sampathkumar2811 said:
You can root using 'fastboot flash boot patchedboot.img'
It seems 6a boot image has issue.
Use pixel 7 pro 's boot image for magisk patching instead of 6a. Also install latest Magisk canary build.
Click to expand...
Click to collapse
Confirmed; canary w/ 7 Pro boot image works like a charm. Thanks
Can somebody provide me Pixel 7 Pro's magisk patched boot img from the latest QPR2 Beta 1 update?
The one which succesfully roots the Pixel 6 Pro
It seems my device is rooted but Magisk in is showing Installed status as NA
What should be done in this case?
amritpal2489 said:
It seems my device is rooted but Magisk in is showing Installed status as NA
What should be done in this case?
Click to expand...
Click to collapse
You're not rooted yet... You need to actually flash the patched boot image(fastboot flash boot "patched-boot.img") instead of using "fastboot boot". Make sure you're running Magisk Canary also, APK & patched boot below:
Esb1809 said:
You're not rooted yet... You need to actually flash the patched boot image(fastboot flash boot "patched-boot.img") instead of using "fastboot boot". Make sure you're running Magisk Canary also, APK & patched boot below:
Click to expand...
Click to collapse
Thanks a lot
I tried Pixel 6a & 7 boot.img from Android 14 Dev Beta 2 and tried to patch with latest Magisk. However after flashing the patched boot.img from fastboot, phone is still in stock unrooted state.
Anyone has a compatible rooted boot image for Pixel 6a?
d5aqoep said:
I tried Pixel 6a & 7 boot.img from Android 14 Dev Beta 2 and tried to patch with latest Magisk. However after flashing the patched boot.img from fastboot, phone is still in stock unrooted state.
Anyone has a compatible rooted boot image for Pixel 6a?
Click to expand...
Click to collapse
Same problem on Pixel 7 Pro
Think we'll have to wait...
Has anyone tried with the new Magisk 26.0 yet? I just installed the 14 preview, so I'll give it a shot and report back, if not.
Edit: Sucessfully rooted with the 6a boot image from the latest dev preview and Magisk 26001.
Are you patching the init_boot.img or the just the boot.img
kamote_sa_ulap said:
Are you patching the init_boot.img or the just the boot.img
Click to expand...
Click to collapse
The Pixel 6a (or any of the PIxel 6 series devices) doesn't have an init_boot.img.
Oh so I guess for the 7 it should really be the init_boot.img
I tried with the new 14 public beta patching the init boot with Magisk 26 and it's still not rooted.
I wonder if I patch the boot.img instead for the 7, will it brick my phone?
kamote_sa_ulap said:
Oh so I guess for the 7 it should really be the init_boot.img
I tried with the new 14 public beta patching the init boot with Magisk 26 and it's still not rooted.
Click to expand...
Click to collapse
That's because the Pixel 6 series doesn't have an init_boot.img. You are patching an image that your phone doesn't have.
Patching the Pixel 6a boot.img with Stable 26.1 or Canary 26101 should work. It did for me on my Pixel 6 Pro running A14 Beta 1.
Lughnasadh said:
That's because the Pixel 6 series doesn't have an init_boot.img. You are patching an image that your phone doesn't have.
Patching the Pixel 6a boot.img with Stable 26.1 or Canary 26101 should work. It did for me on my Pixel 6 Pro running A14 Beta 1.
Click to expand...
Click to collapse
Im sorry, but im not using a Pixel 6a I'm using a Pixel 7 which have both the init_boot.img and the boot.img
kamote_sa_ulap said:
Im sorry, but im not using a Pixel 6a I'm using a Pixel 7 which have both the init_boot.img and the boot.img
Click to expand...
Click to collapse
Ok. I figured you had a PIxel 6a since this is a Pixel 6a forum and thread.
Lughnasadh said:
Ok. I figured you had a PIxel 6a since this is a Pixel 6a forum and thread.
Click to expand...
Click to collapse
yeah unfortunately, so far this the only thread that talks about rooting a pixel on android 14, nothing on the pixel 7 forum yet. Well it was worth the shot. Thanks.
kamote_sa_ulap said:
yeah unfortunately, so far this the only thread that talks about rooting a pixel on android 14, nothing on the pixel 7 forum yet. Well it was worth the shot. Thanks.
Click to expand...
Click to collapse
Try here. Patching the init_boot.img with Stable 26.1 or Canary 26101 should work for you.
Lughnasadh said:
Try here. Patching the init_boot.img with Stable 26.1 or Canary 26101 should work for you.
Click to expand...
Click to collapse
Alright, i'll try the Canary 26101 since I already tried the Stable 26.1 and it still doesn't work. Hopefully that will do the trick.
kamote_sa_ulap said:
Alright, i'll try the Canary 26101 since I already tried the Stable 26.1 and it still doesn't work. Hopefully that will do the trick.
Click to expand...
Click to collapse
Awesome, was able to root 14 Public Beta on my Pixel 7 using Canary Magisk 26101, Lets see if I can enable 5G now. Thanks man.
Hi, I tried to root pixel 6a and got a hard brick. I can't get into fastboot and I can't power on the device. The screen is black and the pc does not detect it. What I can do?
Has anyone tested the Magisk Beta or Canary channels with the latest Android 14 Beta 2 released on I/O?
k9r4n16 said:
Has anyone tested the Magisk Beta or Canary channels with the latest Android 14 Beta 2 released on I/O?
Click to expand...
Click to collapse
The latest Canary (26101), Beta (26100), and Stable (26100) versions should all be the same at the moment as a new Canary has not been released since the release of 26.1. Canary 26101 is working fine on A14 Beta 2 on my Pixel 6 Pro.
Lughnasadh said:
The latest Canary (26101), Beta (26100), and Stable (26100) versions should all be the same at the moment as a new Canary has not been released since the release of 26.1. Canary 26101 is working fine on A14 Beta 2 on my Pixel 6 Pro.
Click to expand...
Click to collapse
Perfect, I'll give that a shot now then.
Well, I ****ed up.
I forgot that I was on the 14 Beta.
I pushed the boot.img from the latest, stable Android 13 build to be patched by Magisk Manager. Then I rebooted and flashed that. Of course it didn't work, so I re-flashed the original boot.img from the Android 13 build. That of course didn't work either, so I flashed the entire Android 13 package back over, excluding the bootloader and radio images and without wiping the device.
Now it's not doing anything. It doesn't continually boot loop, it doesn't react to a charger (any of the 5 chargers I have, including wireless) and doesn't react to any power combination. I think it's hard bricked.
Is there any hope at all? This is the first time I've ever hard bricked a phone
I have a protection plan on it with T-Mobile, do you think I can get away with using that? The device is fully paid off.
pctv007 said:
Same problem on Pixel 7 Pro
Click to expand...
Click to collapse
I was able to root it with this fastboot boot command and the magisk image