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
Related
Latest update is out on the developer page of Google.
Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?
chaco81 said:
Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?
Click to expand...
Click to collapse
?
I did not have to use a "patched" boot image thirty days ago . . . Normal old boot image did the trick.
.
You have to boot twrp but what do we gain by loading the twrp zip ? . nandroid backups ?
chaco81 said:
Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?
Click to expand...
Click to collapse
Have no idea haven't even tried. Didn't know where to get started since I haven't seen anyone say anything about rooting with the January patch.
Rooting is the same as it always has been. Boot to TWRP and install the Magisk zip from TWRP.
The update is good, I see no new features but I noticed big improvements in performances and RAM management
chaco81 said:
Thanks, do you know if booting to TWRP and flashing Magisk v18 will root?
Or do we have to do patched boot.img like in Dec?
Click to expand...
Click to collapse
Just have to put twrp on and flash through that all good and tested even with swift installer for themes
TonikJDK said:
Rooting is the same as it always has been. Boot to TWRP and install the Magisk zip from TWRP.
Click to expand...
Click to collapse
OK, yes, Magisk v18 worked fine by flashing it on TWRP
Link to download?
Sent from my Pixel 3 XL using Tapatalk
chakra said:
Link to download?
Click to expand...
Click to collapse
January 2019 Update (for Pixel 3 XL aka "crosshatch"):
Factory Image -- https://dl.google.com/dl/android/aosp/crosshatch-pq1a.190105.004-factory-7165155c.zip
Full OTA Image -- https://dl.google.com/dl/android/aosp/crosshatch-ota-pq1a.190105.004-5f23d043.zip
Can you flash via TWRP?
virtyx said:
Can you flash via TWRP?
Click to expand...
Click to collapse
Installing OTA via TWRP (I assume you are referring to than and not the Magisk flash) has never worked on the Pixel 3 or 3XL. Sideload the OTA or flash-all with the -w removed.
Just came across this bit of vague information but thought some might be interested. Apologies if it's old info, but seems to indicate the upcoming Feb 2019 update.
Feb 19 Various bug fixes as well as support for Optus VoWIFI + EVS codec activation.
Security updates for Android 9.0
Status: Complete
Click to expand...
Click to collapse
https://yescrowd.optus.com.au/t5/Blog/Android-Software-Updates-07-01-2019/ba-p/522497
sliding_billy said:
Installing OTA via TWRP (I assume you are referring to than and not the Magisk flash) has never worked on the Pixel 3 or 3XL. Sideload the OTA or flash-all with the -w removed.
Click to expand...
Click to collapse
Never side loaded an OTA before. Does it wip TWRP and root? I'd assume so but just checking.
Fire Hound 8.1
Shaftamle said:
Never side loaded an OTA before. Does it wip TWRP and root? I'd assume so but just checking.
Fire Hound 8.1
Click to expand...
Click to collapse
It does. Effectively, it does the same thing as the factory image without the -w. It just loads les files. I have been doing the factory image way for years on the OG Pixel XL and now the 3XL. I have done a sideload once just to see the process as well as an OG TWRP sideload once (when it was working) for the same reason. The factory method is the easiest and most reliable IMO. You just need to remember to remove the -w, LOL.
anyone have any idea why i can get twrp to install but when i install any version of magisk it boots to the g with a line under it for a few minutes then it just reboots to twrp
DrUnkeN_TiGeR said:
anyone have any idea why i can get twrp to install but when i install any version of magisk it boots to the g with a line under it for a few minutes then it just reboots to twrp
Click to expand...
Click to collapse
Could be a few things. Make sure you have the current fastboot/adb files, flash boot.img to both slots, make sure you have the most recent TWRP and stable Magisk files, verify all of your downloads and start over.
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
1. Unlock bootloader via MI Flash Tool
2. Install ADB and Fastboot Drivers
3. Downloader Latest Platform Tools
4. Open command prompt window in platform tools folder
5. Take phone to fastboot mode (Adb reboot bootloader)
6. Flash the given boot image (Fastboot flash boot boot.img)
7. Flash the given vbmeta (Fastboot flash vbmeta vbmeta.img)
8. Reboot (Fastboot reboot)
9. Download, install and open latest magisk manager in phone. It will reboot phone.
10. Done. You have root now. Verify via root checker.
Credits: @Tigrouzen
is there any bug or issue with miui rom after root? and how to install twrp or any other custom recovery?
ji-r47 said:
is there any bug or issue with miui rom after root? and how to install twrp or any other custom recovery?
Click to expand...
Click to collapse
Some games will start to crash, and some apps wont work because they will detect root and close down. You can flash stock boot and vbmeta image to unroot and they will work.
Unofficial TWRP (compiled by @Tigrouzen) is attached. Flash in fastboot mode and then flash vbmeta from above.
ahsan.ey.ca said:
Some games will start to crash, and some apps wont work because they will detect root and close down. You can flash stock boot and vbmeta image to unroot and they will work.
Unofficial TWRP (compiled by @Tigrouzen) is attached. Flash in fastboot mode and then flash vbmeta from above.
Click to expand...
Click to collapse
Thank you very much
ahsan.ey.ca said:
Some games will start to crash, and some apps wont work because they will detect root and close down. You can flash stock boot and vbmeta image to unroot and they will work.
Unofficial TWRP (compiled by @Tigrouzen) is attached. Flash in fastboot mode and then flash vbmeta from above.
Click to expand...
Click to collapse
Do you have source code for it?
VD171 said:
Do you have source code for it?
Click to expand...
Click to collapse
Not my work, ask @Tigrouzen .
It's working. I don't have to install any ROM to root the phone. Thanks.
This can be done with any version of ROM? I have India version 12.0.9
@sakeyo i dont think region is important for this process, the only diference is the bloatware inside the rom,
if it doesnt works, you can just flash back the stock boot.img and vbmeta.img
or if you want, you can change the ROM to Global
I used XiaomiToolv2 https://www.xiaomitool.com/V2/
It works perfectly on my device. Thanks!
Hi Sakeyo. Please tell me what version of Magisk did you use?
Thanks in advance
asia559571 said:
Hi Sakeyo. Please tell me what version of Magisk did you use?
Thanks in advance
Click to expand...
Click to collapse
Im using the latest magisk version, it works flawlessly
its the version 23
yoshijulas said:
Im using the latest magisk version, it works flawlessly
its the version 23
Click to expand...
Click to collapse
Thank You yoshijulas for your reply and Kind Regards
asia559571 said:
Hi Sakeyo. Please tell me what version of Magisk did you use?
Thanks in advance
Click to expand...
Click to collapse
Hello. I am currently not rooted. I removed Magisk and closed the bootloader. But when I was rooted I always used the latest versions of Magisk.
sakeyo said:
Hello. I am currently not rooted. I removed Magisk and closed the bootloader. But when I was rooted I always used the latest versions of Magisk.
Click to expand...
Click to collapse
To be honest, I only wanted root for the sake of having ViPER4Android. I tried the rootless version, but it failed on my phone... got stuck in a boot loop. I'm using Black Player Ex, the equalizer in tandem with the Mi Sound Enhancer works like a charm. One thing I noticed, is that the sound level on the Global Rom is very low compared to the Chinese version, so I'm sticking to the Chinese Rom. If You come across ViPER that can be installed on our device without the need for root, Please let me know. It's a shame that Xiaomi wouldn't/don't have ViPER pre-installed as a system app?
Best Regards
ahsan.ey.ca said:
Some games will start to crash, and some apps wont work because they will detect root and close down. You can flash stock boot and vbmeta image to unroot and they will work.
Unofficial TWRP (compiled by @Tigrouzen) is attached. Flash in fastboot mode and then flash vbmeta from above.
Click to expand...
Click to collapse
@ahsan.ey.ca I know you just need boot.img and vbmeta.img to get root, but when you installed recovery.img did you get the frozen screen where you can't swipe to unlock twrp?
I'm paranoid, will this boot and vbmeta work on any MiUI version?
Reyproject said:
I'm paranoid, will this boot and vbmeta work on any MiUI version?
Click to expand...
Click to collapse
Not sure.
Probably boot can works.
But the vbmeta certainly works on any version.
Where can I find the boot.img for flashing recovery?
criza said:
Where can I find the boot.img for flashing recovery?
Click to expand...
Click to collapse
Try here:
[IMG][ROOT][PATCHED] Magisk Patched Boot: ROOTED Images Partitions for DANDELION (Redmi 9A / Redmi 9AT)
Magisk Patched BOOT.IMG for DANDELION ROOT / PREROOT ROOTED / PREROOTED Works with: - Xiaomi Redmi 9A - Xiaomi Redmi 9AT Does NOT work with: - Xiaomi Redmi 10A Firmware Versions: - (Engineering) 246 - (Engineering) 440 - (Indonesia)...
forum.xda-developers.com
Hello everyone.
I was wondering if anyone has found a work around to get a custom recovery to work on the oos 11 beta one for op7p gm1917.
I've tried msm tool and have working TWRP untill I install ops 11.
Once I install the beta 1 and TWRP booting to recovery is stuck in a flashing TWRP logo. Only way to recover from this is to flash stock boot image.
I do have root as I patched the stock boot.img with magisk 8.0.4 then flashed the boot image with fastboot.
If anyone could help me get this TWRP up and running I would definitely appreciate it.
Thank you...
mrhodes19904 said:
If anyone could help me get this TWRP up and running I would definitely appreciate it.
Thank you...
Click to expand...
Click to collapse
TWRP is not available for Android 11 yet, so you will have to wait.
nabril15 said:
TWRP is not available for Android 11 yet, so you will have to wait.
Click to expand...
Click to collapse
At least I have root that's all that matters
pcould you please put the modified boot here?
RicoMartins said:
pcould you please put the modified boot here?
Click to expand...
Click to collapse
magisk.img
Shared with Dropbox
www.dropbox.com
Thanks, buddy.
You guys can flash a zip of twrp like orangefox dual boot. Right after the ota in twrp. With a pen drive to get twrp in OS11. No need to actually use a dualboot its just a really nice build I use it.
Anyone tried this method? https://www.droidwin.com/update-oneplus-to-android-11-oxygenos-11-via-twrp-without-losing-root/
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