Related
I have a Google edition pixel and have been trying to root it. I have unlocked the bootloader, installed twrp, flash supersu, then flash verifiedboot. Once the phone boots up i check to see if it has root access with root check app, and it still does not. I follwed these instructions https://forum.xda-developers.com/pixel/how-to/guide-root-android-o-dev-preview-1-pixel-t3591548
Used Supersu sr3
champstar said:
I have a Google edition pixel and have been trying to root it. I have unlocked the bootloader, installed twrp, flash supersu, then flash verifiedboot. Once the phone boots up i check to see if it has root access with root check app, and it still does not. I follwed these instructions https://forum.xda-developers.com/pixel/how-to/guide-root-android-o-dev-preview-1-pixel-t3591548
Used Supersu sr3
Click to expand...
Click to collapse
Hi,
You have to look here for 8.0 : https://forum.xda-developers.com/pixel/how-to/guide-root-android-o-dev-preview-1-pixel-t3591548
Read the OP again, it should say boot Twrp and not flash, because there is no flashable Twrp for O yet.
Sent from my Google Pixel using XDA Labs
Sgace said:
Hi,
You have to look here for 8.0 : https://forum.xda-developers.com/pixel/how-to/guide-root-android-o-dev-preview-1-pixel-t3591548
Read the OP again, it should say boot Twrp and not flash, because there is no flashable Twrp for O yet.
Sent from my Google Pixel using XDA Labs
Click to expand...
Click to collapse
That is exactly what I did. Still root did not work. Should I try a different supersu zip?
champstar said:
That is exactly what I did. Still root did not work. Should I try a different supersu zip?
Click to expand...
Click to collapse
Supersu zip mentioned should be the latest and working.
Maybe ask in that thread.
Sent from my Google Pixel using XDA Labs
Tried this with the latest Supersu SR4 and still not working. I'm on Android 8.0 August 5,2017 security patch.
Maybe they fixed the exploit? I'm not sure why I can't get it rooted.
champstar said:
Tried this with the latest Supersu SR4 and still not working. I'm on Android 8.0 August 5,2017 security patch.
Maybe they fixed the exploit? I'm not sure why I can't get it rooted.
Click to expand...
Click to collapse
What messages does it say in twrp, as you flash SuperSU? ... if you've already flashed SuperSU, the script could be restoring the backup boot.IMG, which could be your problem...
When I bump into that, personally; I just download the factory image, then edit the flash-all.sh script and remove the -w flag (which tells the script to not wipe the device), I save the script then execute it...
It flashes the image and I end up with an unaltered boot.IMG and system, then I flash SuperSU after....
I'm on the Sept 5 image using SuperSU sr3 ... SuperSU works like a charm.
After plenty of tiral and error I have finally rooted the phone.
For some reason this tutorial was the only one to work for me.
http://www.teamandroid.com/2017/08/23/root-google-pixel-xl-android-80-oreo-software-update/2/
Hope this can help someone in the future.
THANKS!
champstar said:
After plenty of tiral and error I have finally rooted the phone.
For some reason this tutorial was the only one to work for me.
http://www.teamandroid.com/2017/08/23/root-google-pixel-xl-android-80-oreo-software-update/2/
Hope this can help someone in the future.
Click to expand...
Click to collapse
Im an htc u11+ user, the device is largely underrated thus very few resources available.
However, i was having the exact same issues you were, flashing your supersu zip worked for me after various frustrating attempts using other versions of superSU
Thanks a lot
Mod was already available for the Pixel2.
If you don't know what Edge Sense Plus is, you can check it here: https://forum.xda-developers.com/pixel-2/themes/root-custom-active-edge-actions-edge-t3732368
Just curious but do we know it can be rooted?
krabman said:
Just curious but do we know it can be rooted?
Click to expand...
Click to collapse
@topjohnwu will take care about that.
Sent from my HTC U11 using Tapatalk
Will get pixel 3xl by November 8 9. I am willing to test it for you.
ill have mine by 18th or 19th ill help out if still needed.
Mine is supposed to arrive today. I am hoping that root will be as simple as unlocking the bootloader, patching stock boot.img and flashing. I suspect that it'll be a while before we have a custom recovery though.
j to the 4n said:
@topjohnwu will take care about that.
Sent from my HTC U11 using Tapatalk
Click to expand...
Click to collapse
Sent from my Pixel 2 XL using Tapatalk
WisdomWolf said:
Mine is supposed to arrive today. I am hoping that root will be as simple as unlocking the bootloader, patching stock boot.img and flashing. I suspect that it'll be a while before we have a custom recovery though.
Click to expand...
Click to collapse
Doing this would be extremely unwise without a copy of the stock boot image. I would advise you to wait till the factory images come out. Which should be soon. If you bootloop, highly likely, you will have a unusable phone until the factory images get posted.
Well considering that I would need a copy of the stock boot.img to accomplish this process it seems like we are in arguegreement. [emoji6]
Sent from my Pixel 2 XL using Tapatalk
Has anyone unlocked the bootloader? That's all I care about (for now). Is it the same process as the Pixel 2 XL? I'm just curious if anything has changed with Titan being a part of the hardware now.
WisdomWolf said:
Well considering that I would need a copy of the stock boot.img to accomplish this process it seems like we are in arguegreement. [emoji6]
Click to expand...
Click to collapse
Your phone comes with a boot image.
You can patch the boot image with Magisk Manager. Which saves a copy of the patched boot image on your device. Then it needs too be transferred to a PC to be flashed in fastboot. My advice is still relevant. As soon as I have factory images, I will try and root.
I have mine. I'm willing to test whatever/whenever it's safe to do so.
I did enable the "OEM Unlocking" in the developer settings. It didn't come with a USB-C to USB -A cable, so I cannot connect it to a PC anyway.
I have phone in hand.
I would love to test, once the root situation has been figured out. Links to how to get phone rooted appreciated (I'm already aware of how to root it via Magisk (once factory image or standalone boot.img is released), and how to root via TWRP (once TWRP is released)).
Golf c said:
Your phone comes with a boot image.
Click to expand...
Click to collapse
Where is the standalone boot image? Did not come with my phone (no boot.img other than the boot.img that is in slots A and B).
lensgrabber said:
Has anyone unlocked the bootloader? That's all I care about (for now). Is it the same process as the Pixel 2 XL? I'm just curious if anything has changed with Titan being a part of the hardware now.
Click to expand...
Click to collapse
I just unlocked mine. It's the unlocked version, not the VZW version though. Same commands as the XL 2.
sd_matto said:
I have phone in hand.
I would love to test, once the root situation has been figured out. Links to how to get phone rooted appreciated (I'm already aware of how to root it via Magisk (once factory image or standalone boot.img is released), and how to root via TWRP (once TWRP is released)).
Where is the standalone boot image? Did not come with my phone (no boot.img other than the boot.img that is in slots A and B).
Click to expand...
Click to collapse
There is no "standalone" boot image yet. It comes with factory image. Which should be out soon. The boot image is in your device. You can patch the boot image with Magisk Manager or sideload the Magisk zip. I would not do either of those until you have the factory image. If you bootloop, your device will be useless without factory images
mattj949 said:
I just unlocked mine. It's the unlocked version, not the VZW version though. Same commands as the XL 2.
Click to expand...
Click to collapse
Did you use the "unlock_critical" version of the command or just "unlock"?
Golf c said:
You can patch the boot image with Magisk Manager.
Click to expand...
Click to collapse
To which boot image are you referring:
1. The boot image in the factory image (I know how to do this), or
2. The boot image already in the device (I would love to learn how to do this)?
sd_matto said:
To which boot image are you referring:
1. The boot image in the factory image (I know how to do this), or
2. The boot image already in the device (I would love to learn how to do this)?
Click to expand...
Click to collapse
No 2 the boot image in the device. Unlock bootloader.
Download Magisk Manager apk. Im about ready to unlock mine right now. In Magisk Manager select patch boot image file. It will save a copy to your device. Transfer to PC.
Fastboot flash boot image. You will bootloop im sure. AVB has changed with crosshatch.
DO NOT attempt this without factory image.
I will be doing this when factory image comes out.
nirenshah said:
Did you use the "unlock_critical" version of the command or just "unlock"?
Click to expand...
Click to collapse
Just "unlock" the other one is not valid for this one. Sorry, I should have mentioned that!
My apologies gentlemen. You do need a separate copy of the the boot image from the factory image to patch in Magisk Manager. Sorry for the wrong info. Actually it makes sense doesn't it.
Golf c said:
Your phone comes with a boot image.
You can patch the boot image with Magisk Manager. Which saves a copy of the patched boot image on your device. Then it needs too be transferred to a PC to be flashed in fastboot. My advice is still relevant. As soon as I have factory images, I will try and root.
Click to expand...
Click to collapse
I got my Pixel 3XL last night. Excited to get things going on the Pixel 3XL, coming from a Nexus 6P.
I was sad that the factory image isn't immediately available on google's site for this phone, and I don't want to brick it trying to install Magisk without a factory image to fall back onto.
In any case, woot, woot! Phone looks great and I'm going to transfer over my line today.
Cheers,
B.D.
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Maj3sty said:
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
Click to expand...
Click to collapse
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Voodoojonny said:
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Click to expand...
Click to collapse
I tried it and doesnt work. It seems the module changed any files in system(via root).
wenna.speedy said:
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
Click to expand...
Click to collapse
Nice try, but looks like you are not the only person with the same issue! I'm using Jetaudio and I have great sound with my JBL (Bluetooth) & Sennheiser wired headsets. I'm pass!!!
Mi A2 Lite using Tapatalk
lbsilva said:
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Click to expand...
Click to collapse
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Voodoojonny said:
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Click to expand...
Click to collapse
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
You can try install twrp and mount internal storage. I dont know if exists new version with working mounting.
hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you try using MiFlashTool?
hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
Hmm, as told above, then your only option is a backup with twrp. If you can't decrypt data with twrp (after you installed it - not booting) you can try to boot to slot b - that sometimes help. Just select under reboot in twrp or type "fastboot set_active b"...
wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
There is no wipe required, I just got caught in the loop as well.
Two things you need:
-TRWP installed
-Uninmod installed (magisk module remover)
1. If you are stuck in the loop, boot into fastboot,
- connect your pc and run ADB & fastboot cmd, run the command fastboot boot recovery.img(or your TRWP image) and run TRWP
2. Download Uninmod zip, transfer to phone. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
- Use TWRP to install Uninmod,
- remove the Notchkiller mod
- credits to veez21
3. find this file overlays.list and delete it from /data/resource-cache/overlays.list https://github.com/Magisk-Modules-Repo/NotchBarKiller/issues/3
- credits to MatChung
Reboot and there was like a minute of delay on same boot screen, but then it should boot fine.
If you are not stuck in the loop but just installed the module:
-remove the module in magisk
-find the file and delete it.
TLDR: remove the Notchbarkiller mod and remove overlays.list file. Reboot!
Hope it works. It did for me. Poco F1
I flashed this madule last night and found that it break calls. Could not make and receive phone calls. Huawei P20 Pro with EMUI 8.1 running.
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
D1stRU3T0R said:
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
Click to expand...
Click to collapse
Written in the first post...
wenna.speedy said:
Written in the first post...
Click to expand...
Click to collapse
I know...
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
SnoopDoggyStyleDogg said:
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
Click to expand...
Click to collapse
UPDATE: This thread is a false alarm as I managed to install the module on the March update and the only crash I get is from google play services with no bootloop and everything working. Maybe the OP has another phone and except that a module that is on the Mi A2 Lite thread should work on any phone or he's done something wrong. I will attach some screenshots to confirm that the module is indeed working and OP's post is a false alarm for stock A2 Lite ROMs (No custom ROM and not other phones)
NOTE: As you can see in the YouTube screenshot there's no black back on the left side of the screen as it should be without the module installed
Has anyone received an OTA notification yet?
OTA doesn't get released until the 5th or 6th of the month I believe.
artiemon said:
Has anyone received an OTA notification yet?
Click to expand...
Click to collapse
Yes I got the OTA on both the Pixel 3 and the 3a
I'm new to the pixel how do i update to the latest while rooted also no twrp
Sent from my Pixel 3a XL using Tapatalk
What I do is get the whole update,,,not the OTA but the whole fastboot update. Then unzip it fully into a folder and put that into my min fastboot folder. Find the flash-all windows batch file and right click it with notepad +, take out the -w save and close. Then fastboot the update which will update and keep all your data. Then you will have to go in and reroot with Magisk and do the whole boot.img again.
Texus91501 said:
I'm new to the pixel how do i update to the latest while rooted also no twrp
Sent from my Pixel 3a XL using Tapatalk
Click to expand...
Click to collapse
Just received the ota about an hour ago already downloaded and installed.
I'm not seeing an OTA yet but when it does pop up I'm going to try doing the magisk OTA method, don't see why it wouldn't work.
I got it also, I had to manually check for the update though.
Sent from my Pixel 3a XL using Tapatalk
Got tired of waiting so I decided to sideload; that would be when things went sideways. Did the usual but got an error during the flash about a corrupt file and the phone went into softbrick. Had to do a clean flash to get out of it. No idea what that was about but I have to allow as to how I'm not going to be testing the Magisk OTA method for the June update.
I still haven't gotten a notification about it. Manual checks also saying nothing available. Strange. Debating if I want to just do a sideload instead of waiting in case I'm in the weird never-gets-an-update crew.
krabman said:
Got tired of waiting so I decided to sideload; that would be when things went sideways. Did the usual but got an error during the flash about a corrupt file and the phone went into softbrick. Had to do a clean flash to get out of it. No idea what that was about but I have to allow as to how I'm not going to be testing the Magisk OTA method for the June update.
Click to expand...
Click to collapse
ApeironTsuka said:
I still haven't gotten a notification about it. Manual checks also saying nothing available. Strange. Debating if I want to just do a sideload instead of waiting in case I'm in the weird never-gets-an-update crew.
Click to expand...
Click to collapse
I did little different. Went the fastboot route. After removing the "-w" from the flash-all.bat script. Had no problems at all. Just had to reroot and flash the new ex kernal .zip file via the flash tool in EXKM.
All Good
Sent from my Pixel 3a XL using XDA-Developers Legacy app
Anyone else having issues with installing Magisk on this security update?
I just updated via flash-all.bat, rebooted, installed Magisk to June's boot.img, flashed, rebooted & now can't boot without re-flashing the original boot.img (on either slot).
No problem here.
You have to copy boot image from factory images (unzip the image.zip file) it's there to phone. Then use Magisk to PATCH that boot image. Copy it to computer then flash with fastboot flash boot.
There also thread on rooting read that too
Sent from my Pixel 3a XL using XDA-Developers Legacy app
shadyshadow said:
No problem here.
You have to copy boot image from factory images (unzip the image.zip file) it's there to phone. Then use Magisk to PATCH that boot image. Copy it to computer then flash with fastboot flash boot.
Click to expand...
Click to collapse
Yeah, I've done that multiple times & still the same issue.
What size is the patched boot file you got from Magisk? June's boot.img is 68mb & the patched file that Magisk outputs is only 26mb, so I'm not sure that's right
Ok my June boot.img is 64mb ..after patching it is 26.96mb
Sent from my Pixel 3a XL using XDA-Developers Legacy app
---------- Post added at 11:43 AM ---------- Previous post was at 11:41 AM ----------
DanielF50 said:
Yeah, I've done that multiple times & still the same issue.
What size is the patched boot file you got from Magisk? June's boot.img is 68mb & the patched file that Magisk outputs is only 26mb, so I'm not sure that's right
Click to expand...
Click to collapse
Ok my June boot.img is 64mb ..after patching it is 26.96mb
Sent from my Pixel 3a XL using XDA-Developers Legacy app
DanielF50 said:
Yeah, I've done that multiple times & still the same issue.
What size is the patched boot file you got from Magisk? June's boot.img is 68mb & the patched file that Magisk outputs is only 26mb, so I'm not sure that's right
Click to expand...
Click to collapse
I had the same issue. Using Magisk canary 19.4 works patching the boot.img. Also the patched image does get trimmed to 26
MB.
Sent from my Pixel 3a XL using Tapatalk
shadyshadow said:
Ok my June boot.img is 64mb ..after patching it is 26.96mb
Click to expand...
Click to collapse
Thanks!
vandyman said:
I had the same issue. Using Magisk canary 19.4 works patching the boot.img. Also the patched image does get trimmed to 26
MB.
Click to expand...
Click to collapse
Thanks dude - unfortunately this still didn't work for me either so I ended up wiping the whole device & re-flashing the June update, which worked (with 19.4), so gotta spend a couple of hours setting it up again
DanielF50 said:
shadyshadow said:
[/COLOR]Ok my June boot.img is 64mb ..after patching it is 26.96mb
Thanks!
vandyman said:
I had the same issue. Using Magisk canary 19.4 works patching the boot.img. Also the patched image does get trimmed to 26
MB.
Thanks dude - unfortunately this still didn't work for me either so I ended up wiping the whole device & re-flashing the June update, which worked (with 19.4), so gotta spend a couple of hours setting it up again
Click to expand...
Click to collapse
The only thing I can add is that I'm patching with Magisk 19.3 latest stable.
Sent from my Pixel 3a XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Texus91501 said:
I'm new to the pixel how do i update to the latest while rooted also no twrp
Sent from my Pixel 3a XL using Tapatalk
Click to expand...
Click to collapse
If you installed Magisk normally (using the app to modify the stock boot.img and then moving the modified img to your computer to flash it in fastboot mode, then these directions will work. However, If you used the modified boot.img that is being passed around on the forum, these directions will not work because Magisk doesn't have the stock boot.img to use in step 1.
- Magisk: Click “Uninstall” → “restore images” → NO REBOOT
- Download and install OTA → NO REBOOT
- Clear all apps from recents
- Magisk: Click “Install” → “Install to second/inactive slot (After OTA)”
- Reboot
Anyone noticed that the Pixel Imprint name has changed to Nexus Imprint in the June update?
Got my XL today and noticed the change after I updated.
Not amazingly interesting but thought I'd mention it.
I am starting this thread for us users and experiences while using Android Q. What works, what doesn't. I am not a dev. I am a user. Not here to bash anyone if something doesn't work. @topjohnwu just got root released for this last night.
So one thing I found which I am sure will fixed soon is
SD MAID not working.
Afwall is working.
Systemui tuner working
Button mapper working
I am sure as we go on and they will all work great. But like I said this is just a post what you found thread. If something does work, post it. If something doesn't, post it. Even if someone needs something like an apk. Ask and shall receive. This is a time of helping each other. Not flaming and bashing. Thank you to everyone that has read this and thank you to all the great devs out there and thank you to us users that can exchange information peacefully.
Is it still not possible to write to /system?
w0rdie said:
Is it still not possible to write to /system?
Click to expand...
Click to collapse
Same here. I would think the File Explorer devs would have to update to support Q?
Quickswitch is not working, back button did not work for me with it installed
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
I am using a custom kernel so I didn't try to root the stock boot image. But it seems other people are rooting the stock boot image. I would hope they can help you. If I get around to it, I will try and root the stock boot image to see if it works. Someone should be able to help. Custom kernel roots just fine
kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
Make sure you are flashing the patched boot image to both slots.
Sent from my Pixel 3 XL
Eudeferrer said:
Make sure you are flashing the patched boot image to both slots.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
I ran fastboot flash boot_b magisk_patched.img
then
fastboot flash boot_a magisk_patched.img
Same issue still bootloops.
Thanks.
Kevin
so im guessing custom kernels are a no no?
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
kevdog98 said:
I ran fastboot flash boot_b magisk_patched.img
then
fastboot flash boot_a magisk_patched.img
Same issue still bootloops.
Thanks.
Kevin
Click to expand...
Click to collapse
I ran into the same issue... it started bootlooping, so I flashed dp4 from scratch and then skipped setup, grabbed the boot.img from the dp4 folder on pc, put it on my phone, installed the newest app.release from canary builds and patched it..... rebooted to bootloader and flashed the boot.img in both slots and rebooted .. it worked
i42o said:
so im guessing custom kernels are a no no?
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
I ran into the same issue... it started bootlooping, so I flashed dp4 from scratch and then skipped setup, grabbed the boot.img from the dp4 folder on pc, put it on my phone, installed the newest app.release from canary builds and patched it..... rebooted to bootloader and flashed the boot.img in both slots and rebooted .. it worked
Click to expand...
Click to collapse
Custom kernel. Singular is a go. That's what I'm running. I didn't have to flash both slots. That doesn't make sense at all. I am going to get my lazy ass off the veranda and flash the rooted boot image.
Edit: I have Pie in my inactive slot and QBeta 4 in my active slot. If that makes any sense to you guys?
What's the problem? Flashed to active slot only.
Your doing something wrong if you can't root the stock boot image
When I originally rooted Q I did it ota patch inactive slot. Bootlooped. I just went to factory recovery and wiped data. Has worked ever since. I believe mine was looping to modules not being compatible with Q yet. Also if you grab the Q image and pull the boot image. You can patch it that way too. With Q, it is finicky with apps because of isolated storage. Which is weird because zarchiver still sees all files but amaze only sees root directory. Files app I noticed is saying some files I have are folders and not disk images. Zarchiver says it right still. Fastboot -w to manually remove all data too. Sometimes Titan m drive can cause weird things that is why I go to stock recovery and wipe it that way, wipes the Titan m drive too.
Did anybody already try to flash ainur sound mod and can report if it's working? For me the main reason to unlock bootloader again and start root procedure on Q...
kevdog98 said:
I can't get the root to work on my pixel 3 XL. After patching the boot.img through fastboot all I get is bootloops and the an error saying can not boot with boot.img on the fastboot recovery screen. If I re-flash the factory boot.img through fastboot I can boot just fine again.
Anyone else experience this?
Click to expand...
Click to collapse
Same problem here. Already posted the issue at the Magisk thread.
alex1301 said:
Same problem here. Already posted the issue at the Magisk thread.
Click to expand...
Click to collapse
Very strange. Are you guys on the MM Canary channel?
Magisk Manager 228
Magisk Canary 19304
Golf c said:
Very strange. Are you guys on the MM Canary channel?
Magisk Manager 228
Magisk Canary 19304
Click to expand...
Click to collapse
Yeah, updated everyhting before getting started.
alex1301 said:
Yeah, updated everyhting before getting started.
Click to expand...
Click to collapse
Do you have any modules for magisk on your phone? Almost none work at the moment. They are working to get them up and running. Also old data can cause bootloops. Did you leave the Preserve AVB unchecked? If you have Q up and running, check that you are getting the latest magisk zip when patching too.
S8rooted&tooted said:
Do you have any modules for magisk on your phone? Almost none work at the moment. They are working to get them up and running. Also old data can cause bootloops. Did you leave the Preserve AVB unchecked? If you have Q up and running, check that you are getting the latest magisk zip when patching too.
Click to expand...
Click to collapse
Nothing left. My Pixel had never any modules activated or anything else. What is preserve AVB?
Used the latest files.
alex1301 said:
Nothing left. My Pixel had never any modules activated or anything else. What is preserve AVB?
Used the latest files.
Click to expand...
Click to collapse
Click on advanced settings. And make sure when you did patch it, it wasn't checked. It should not be now with 10. With pie it is. Q will not work with it checked. It will double check system to the other partition. And the slot with magisk doesn't match the untouched slot.