Related
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Edit: CHECK THE COMMENTS FOR SOLUTION
AlexCoetzee said:
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Click to expand...
Click to collapse
Try downloading the stock image and installing that from fastboot. If you are on a Verizon one and on 7.1.1 you are out of luck for root if you bootloader isn't unlocked.
AlexCoetzee said:
I stupidly tried to use Chainfires root method on my pixel by flashing boot-to-root.img. I am now stuck in a bootloop and I have no idea how to fix it. I can get into the fastboot page I think it is called by holding the volume down and power buttom. How can I fix this? Sorry if it is a dumb question. I tried using adb but don't know how it works and I get the error 'error: device '(null)' not found' when trying to do 'adb reboot bootloader'.
I really appreciate if anyone can help me. I am freaking out :laugh:
Click to expand...
Click to collapse
Ok, stop freaking, this is very fixable. Assuming you have the Google version, or the Verizon version unlocked.
Short answer, we are going to get it into fastboot mode and we are going to flash you back to stock and probably save your data.
First, we need to make sure you have the correct version of Fastboot/ADB. It must be from GOOGLE.
https://developer.android.com/studio/releases/platform-tools.html
Unzip that onto a spot on your desktop.
Then go here and download the latest image for the Pixel. I am assuming you are in the US, get 7.1.1 (NOF26V, Feb 2017) for the Pixel.
https://developers.google.com/android/images#sailfish
Unzip that into a the Platform folder you made above with the fastboot tools. When you are all done it should look like the picture below. The highlighted items are the items that came from the Factory Image you extracted in step two. Everything else is from the platform tools.
Now RIGHT click 'flash-all.bat' and edit it. Near the end...look for the -w and take it out and save it. Removing that is what is going to save your data.
Power down your phone, restart it in bootloader mode. Power and Vol Down. Connect it to your computer and then double click 'flash-all.bat'.
That will take you back to stock unlocked and all your data and settings will be there.
Get past that and let us know. Then we will get you properly rooted. Yea, you used the wrong root process.
I love you <3
Thank you so much. I stupidly was trying to flash a file that wasn't an image file! I really appreciate your help man I don't know what I'd do if it wasn't for you.
AlexCoetzee said:
Thank you so much. I stupidly was trying to flash a file that wasn't an image file! I really appreciate your help man I don't know what I'd do if it wasn't for you.
Click to expand...
Click to collapse
You are most welcome. Do you need help rooting now?
TonikJDK said:
You are most welcome. Do you need help rooting now?
Click to expand...
Click to collapse
No thank you! I figured that out pretty quickly with TWRP and I am happily rooted now Quite a different process after jailbreaking iOS for 8 years. Thanks for your help!
Misterxtc said:
Try downloading the stock image and installing that from fastboot. If you are on a Verizon one and on 7.1.1 you are out of luck for root if you bootloader isn't unlocked.
Click to expand...
Click to collapse
Glad to see you are still out there @Misterxtc
Seems like you've been a mainstay almost everywhere I've been and I've relied on your threads and guides for a long time.
Tulsadiver said:
Glad to see you are still out there @Misterxtc
Seems like you've been a mainstay almost everywhere I've been and I've relied on your threads and guides for a long time.
Click to expand...
Click to collapse
Good to see you here too. It feels great to be free of TouchWiz!!
Misterxtc said:
Good to see you here too. It feels great to be free of TouchWiz!!
Click to expand...
Click to collapse
And how. I'm done with Samsung.
Thanks for the straightforward instructions!
---------- Post added at 11:45 AM ---------- Previous post was at 11:38 AM ----------
TonikJDK said:
You are most welcome. Do you need help rooting now?
Click to expand...
Click to collapse
Do you have a link to rooting with TWRP? I've found several rooting posts but most talk about rooting via fastboot.
Thanks!
stpbby said:
Thanks for the straightforward instructions!
---------- Post added at 11:45 AM ---------- Previous post was at 11:38 AM ----------
Do you have a link to rooting with TWRP? I've found several rooting posts but most talk about rooting via fastboot.
Thanks!
Click to expand...
Click to collapse
No link handy, but here is how I do it. And yes, it is via fastboot, only way I know of at this point.
Download 2.7.9 SR3 SuperUser and copy it to your phone.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Download TWRP RC1 and copy it to your fastboot folder.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.
fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.
That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.
Thanks! That worked.
I need help with unlocking bootloader and rooting phone
TonikJDK said:
No link handy, but here is how I do it. And yes, it is via fastboot, only way I know of at this point.
Download 2.7.9 SR3 SuperUser and copy it to your phone.
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Download TWRP RC1 and copy it to your fastboot folder.
https://forum.xda-developers.com/pixel-xl/development/twrp-alpha1-pixel-devices-t3500312
Using other versions than above will bootloop you. Reboot the phone into bootloader mode. Power and Vol down.
fastboot BOOT twrpFilename.img Where twrpfilename.img is the name of the TWRP file you just downloaded. Note is says boot in the command, not flash.
That will boot the phone into TWRP. Select Install and install the SU zip you copied to the phone above. And reboot the phone, done.
Click to expand...
Click to collapse
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
gandhi98 said:
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
Click to expand...
Click to collapse
If your on Verizon, no, you can't unlock the bootloader
gandhi98 said:
I have completed the steps that you listed however the phone did not do a thing. Is it not possible to unlock the bootloader on 7.1.2? Am I doing something wrong? I can elaborate more if you need.
Click to expand...
Click to collapse
If it is a Verizon phone, no you can't unlock it. If it is a Google phone to unlock...below is a decent link on how to. Except use the ADB Fastboot tools I link to in the third post of this thread.
https://android.gadgethacks.com/how-to/unlock-bootloader-your-google-pixel-pixel-xl-0174627/
And be aware, when you unlock it...it will wipe all the data on your phone.
My pixel (stock, not rooted) is boot looping after the May OTA updates. Google support says to take it back to the store as it's still under warranty. Would the above fix work for my phone? Is it worth it, or should I just get a new one? This is already my second pixel as the first one died abruptly after 3 months.
moeREM said:
My pixel (stock, not rooted) is boot looping after the May OTA updates. Google support says to take it back to the store as it's still under warranty. Would the above fix work for my phone? Is it worth it, or should I just get a new one? This is already my second pixel as the first one died abruptly after 3 months.
Click to expand...
Click to collapse
Is the bootloader unlocked? If so I would certainly try flashing stock first. It can't hurt, and moments ago my Nexus 6 that I keep for backup was doing the same thing after the OTA. I just reflashed stock and it is fine now.
TonikJDK said:
Is the bootloader unlocked? If so I would certainly try flashing stock first. It can't hurt, and moments ago my Nexus 6 that I keep for backup was doing the same thing after the OTA. I just reflashed stock and it is fine now.
Click to expand...
Click to collapse
I think so, but am not 100% sure. Was bought unlocked from a retail shop. (Sorry, am a bit of a newb!)
So please let me understand
I am on 7.1.2 april (N2G47E), and if I want to update to may N2G47O the steps are:
- sideload ota
- flash new bootloader from may factory image
- twrp RC1 and supersu 2.79 sr3
Does this work or do I have to make something different?
TENN3R said:
So please let me understand
I am on 7.1.2 april (N2G47E), and if I want to update to may N2G47O the steps are:
- sideload ota
- flash new bootloader from may factory image
- twrp RC1 and supersu 2.79 sr3
Does this work or do I have to make something different?
Click to expand...
Click to collapse
I'm having bootloops at the initial white google logo screen with SR3-SuperSU-v2.79-SR3-20170114223742.zip flash method on 7.1.2-May
Re: https://theunlockr.com/2017/02/01/root-google-pixel-pixel-xl/2/
In case anyone of u ever needs to flash stock boot.img's to restore things,
The twrp telegram group kindly provided me with those backups, i just sorted them and made them available for download...
Currently I have all patches after 4.88 base so may to october security patch...
You can find all stock images here:
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
and Magisk(v17.2) prerooted patched myself here:
https://cloud.vault81.de/s/AeHiE5HR2qonb3N
Mirror: (All Images)
https://mega.nz/#F!QQp1jQQZ!k5ejlU2NJyic0HusCa_IAQ
Nice job, i have been waiting for this for a long time. Thank you so much ??.
Trissi said:
In case anyone of u ever needs to flash stock boot.img's to restore things,
The twrp telegram group kindly provided me with those backups, i just sorted them and made them available for download...
You can find all stock images here:
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
Magisk Prepatched Images will be added later...
Click to expand...
Click to collapse
Thanks sir
Greatttttt
Thank you for the img files. Unfortunately i have a problem. When i try to boot the October image with fastboot on A slot where my phone is updated to the october patch - it stucks on android logo. When i switch to B slot which is September patched and use the september img u provided - again the same thing. Any idea?
Mo4o293 said:
Thank you for the img files. Unfortunately i have a problem. When i try to boot the October image with fastboot on A slot where my phone is updated to the october patch - it stucks on android logo. When i switch to B slot which is September patched and use the september img u provided - again the same thing. Any idea?
Click to expand...
Click to collapse
Thats weird... what model do you have? , I thought they work on all Models...
On my device (TA-1012)[Single sim 128gb/6gb], I have exactly the same patches on a and b and both work like a charm with their specific images... Just redownloaded and tested it again...
To narrow down your problem further:
Did you flash anything else? Is your device booting normally when just rebooting? Root? Twrp?
Mo4o293 said:
Thank you for the img files. Unfortunately i have a problem. When i try to boot the October image with fastboot on A slot where my phone is updated to the october patch - it stucks on android logo. When i switch to B slot which is September patched and use the september img u provided - again the same thing. Any idea?
Click to expand...
Click to collapse
If you have another model and some time leftover I would greatly appreciate if you(and everyone else reading this with Another model):
1. could reflash the 4.88 Stock Image
2. Turn off automatic update
3.follow this Upgrade guide over and over again
https://forum.xda-developers.com/no...root-nokia-8-ability-to-t3848390/post77751877
4. Afterwards send me the stock_boot_(randomstuff).gz Magisk generates as Backups in the folder /data or (only viewable with root explorer) AND a screensho of the file creation dates so I know which is which...
I would then upload them and add them to the thread to help others with your model...
No worry's if you don't have time...
Trissi said:
Thats weird... what model do you have? , I thought they work on all Models...
On my device (TA-1012)[Single sim 128gb/6gb], I have exactly the same patches on a and b and both work like a charm with their specific images... Just redownloaded and tested it again...
To narrow down your problem further:
Did you flash anything else? Is your device booting normally when just rebooting? Root? Twrp?
Click to expand...
Click to collapse
Thanks for the replay! My device is TA-1012 [4/64]. I haven't flashed anything. I neither have TWRP or root. When rebooting it is showing the warning that my bootloader is unlocked (offical method). But i noticed something strange. Maybe you will laugh at me :laugh: but the thing is when i boot the phone and the warning pops up it says to press the power button to continue but that doesn't work. I have to wait to boot itself. In the other hand when i boot the stock images you provided the power button works and when i press it, the warning disappears and the android logo pops up. I dont know if this was helpful in some way but i wanted to mention it. Also i will post the backed up img soon that you wanted up there.
Ok so i came up with another idea. I forgot to mention that all these steps i did on Linux so i have Windows also and switched to see if the things are the same. When i enter in cmd, adb recognizes the device without problem. When i write adb reboot bootloader everything is fine. BUT when i write fastboot devices when my phone is in download mode , nothing happens. When i try something like fastboot reboot or fastboot boot xyz.img it says <Waiting for device>. I tried adb and fastboot installer but again nothing. I cannot find nokia drivers, but in OST LA there are 3, i installed them and again nothing. So what should i do?
Edit: It worked when i downloaded new version of adb and fastboot CLI but again - booting the oct img even in Windows cmd makes the phone stuck on android logo
Mo4o293 said:
Thanks for the replay! My device is TA-1012 [4/64]. I haven't flashed anything. I neither have TWRP or root. When rebooting it is showing the warning that my bootloader is unlocked (offical method). But i noticed something strange. Maybe you will laugh at me :laugh: but the thing is when i boot the phone and the warning pops up it says to press the power button to continue but that doesn't work. I have to wait to boot itself. In the other hand when i boot the stock images you provided the power button works and when i press it, the warning disappears and the android logo pops up. I dont know if this was helpful in some way but i wanted to mention it. Also i will post the backed up img soon that you wanted up there.
Click to expand...
Click to collapse
The Power Button stuff is exactly the same for me... Don't think thats the issue...
Really weird, would love to debug further but really have not much other ideas...
Did you try newest fastboot/adb binaries on windows too?
Do you have access to another pc to try it on?
Switched out cables/ports used?
Trissi said:
The Power Button stuff is exactly the same for me... Don't think thats the issue...
Really weird, would love to debug further but really have not much other ideas...
Did you try newest fastboot/adb binaries on windows too?
Do you have access to another pc to try it on?
Switched out cables/ports used?
Click to expand...
Click to collapse
I've switched ports, tried another pc even with different OS (win7). Downloaded the newest adb and fastboot binaries from Android Developers site - nothing. Also i ran a test in fastboot and its says:
bootloader unlocked: true
critical unlocked: false. But i dont think critical is necessary, isnt it?
Mo4o293 said:
I've switched ports, tried another pc even with different OS (win7). Downloaded the newest adb and fastboot binaries from Android Developers site - nothing. Also i ran a test in fastboot and its says:
bootloader unlocked: true
critical unlocked: false. But i dont think critical is necessary, isnt it?
Click to expand...
Click to collapse
If critical was never unlocked it can't have been modified(I think)
Really outta ideas here sorry mate...
Have you tryed booting the prerooted imgs?
Trissi said:
If critical was never unlocked it can't have been modified(I think)
Really outta ideas here sorry mate...
Have you tryed booting the prerooted imgs?
Click to expand...
Click to collapse
Yep the same thing
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
I think i should try to flash the stock firmware provided in the forum i think it was the June one. Maybe that will make my device able to flash your images
I have similar issues. I have ta-1012 4/64. When it was of september patch, no september image worked (modified or not), it stucks at "android powered" logo. This is the volatile booting which is performed by "fastboot boot" command.
I use a linux desktop. I tried the latest fastboot executable which came with android-studio and also the one on archlinux android-tools package. (they are a bit different) Results are same.
Now it has october patch. No success with october boot images, too
---------- Post added at 21:59 ---------- Previous post was at 21:53 ----------
Mo4o293 said:
Yep the same thing
---------- Post added at 06:41 PM ---------- Previous post was at 06:39 PM ----------
I think i should try to flash the stock firmware provided in the forum i think it was the June one. Maybe that will make my device able to flash your images
Click to expand...
Click to collapse
I think you should wait for TWRP.
Dr. Slump said:
I have similar issues. I have ta-1012 4/64. When it was of september patch, no september image worked (modified or not), it stucks at "android powered" logo. This is the volatile booting which is performed by "fastboot boot" command.
I use a linux desktop. I tried the latest fastboot executable which came with android-studio and also the one on archlinux android-tools package. (they are a bit different) Results are same.
Now it has october patch. No success with october boot images, too
---------- Post added at 21:59 ---------- Previous post was at 21:53 ----------
I think you should wait for TWRP.
Click to expand...
Click to collapse
Yep. We are the black sheeps. Anyway i will definitely wait for TWRP because the other things are risky and thats my daily driver. BTW Im on Manjaro which is based on Arch.
Mo4o293 said:
think i should try to flash the stock firmware provided in the forum i think it was the June one. Maybe that will make my device able to flash your images
.
Click to expand...
Click to collapse
If you do happen to do that please remember this if you have Time....
If you have another model and some time leftover I would greatly appreciate if you(and everyone else reading this with Another model):
1. could reflash the 4.88 Stock Image
2. Turn off automatic update
3.follow this Upgrade guide over and over again
https://forum.xda-developers.com/no...root-nokia-8-ability-to-t3848390/post77751877
4. Afterwards send me the stock_boot_(randomstuff).gz Magisk generates as Backups in the folder /data or (only viewable with root explorer) AND a screensho of the file creation dates so I know which is which...
Click to expand...
Click to collapse
Trissi said:
In case anyone of u ever needs to flash stock boot.img's to restore things,
The twrp telegram group kindly provided me with those backups, i just sorted them and made them available for download...
Currently I have all patches after 4.88 base so may to october security patch...
You can find all stock images here:
https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
and Magisk(v17.2) prerooted patched myself here:
https://cloud.vault81.de/s/AeHiE5HR2qonb3N
Click to expand...
Click to collapse
You can download it on GoogleDrive? links do not open
Anatoly64RUS said:
You can download it on GoogleDrive? links do not open
Click to expand...
Click to collapse
Problem seems on your side
Anatoly64RUS said:
You can download it on GoogleDrive? links do not open
Click to expand...
Click to collapse
Works fine for me too...
I have A pretty restrictive https configuration on that server...
Do you use A massively outdated browser? If Not it should work...
Trissi said:
Works fine for me too...
I have A pretty restrictive https configuration on that server...
Do you use A massively outdated browser? If Not it should work...
Click to expand...
Click to collapse
Browsers are all updated, I'm just from Russia, so a big request to anyone is easy, upload to google drive
Edit: Update!
See My Guide: [Guide] Pixel 3 XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + September 2018 Security Patch
Doubtful being that the article's date is from May...
jrac86 said:
Doubtful being that the article's date is from May...
Click to expand...
Click to collapse
Edit: OP updated!
Fake News...
It's a feature of Magisk. You install Magisk manager and it will save a patched version of your boot.img that you can pull and flash in fastboot mode.
Sent from my Pixel 2 XL using Tapatalk
bxlegend said:
It's a feature of Magisk. You install Magisk manager and it will save a patched version of your boot.img that you can pull and flash in fastboot mode.
Click to expand...
Click to collapse
Some think the link is "clickbait."
I thought if you installed MM only, you could patch a boot.img with MM. Are you saying that when you install MM it does it without intervention?
Last time I did it you had to get a boot image, transfer it to the device, MM can then patch it, you transfer it back to a PC, flash in fastboot.
Pretty sure we need to wait for a few things, twrp for the Pixel 3, and Google to release the images.
the phone is starting to get to hands on people
it's not like samsung where we can make twrp and root without the device
we need to get images and do testing too
kachaffeous said:
Pretty sure we need to wait for a few things, twrp for the Pixel 3, and Google to release the images.
Click to expand...
Click to collapse
Edit: OP updated
TheUndertaker21 said:
the phone is starting to get to hands on people
it's not like samsung where we can make twrp and root without the device
we need to get images and do testing too
Click to expand...
Click to collapse
Edit: OP updated.
I'm curious what the new Titan security chip will do for rooting and custom rooms. Sounds like something that if done right it can be flashed, but it could present a roadblock depending on how it was implemented.
Images are up.
Sent from my taimen using XDA Labs
---------- Post added at 08:01 PM ---------- Previous post was at 07:12 PM ----------
Current boot patch doesn't work. John will have his phone today.
https://twitter.com/topjohnwu/status/1052993970303889418
Sent from my taimen using XDA Labs
I found this out the hard way
Thought I bricked my phone; black screen. Finally after holding down the power button for a second it said boot incompatible or something in the bootloader. There was a new message I hadn't seen before on a Pixel bootloader. (It also says "button combo" in that message area if you use the buttons to get to bootloader.)
Current boot patch doesn't work.
Click to expand...
Click to collapse
No luck here. I patched the boot img with magisk and it fails to boot. @topjohnwu Please save us. I'll test if needed. I flashed back to stock boot and am good to go.
Factory images are up
Thanks for giving it a try,,,was hoping it would work but I doubted it. Hopefully Magisk can be updated for root! If not, this is going back,,,not enough of a worthy upgrade esp if root is not possible.
northmendo said:
No luck here. I patched the boot img with magisk and it fails to boot. @topjohnwu Please save us. I'll test if needed. I flashed back to stock boot and am good to go.
Click to expand...
Click to collapse
I think I can still cancel my order but I''m hopeful it wont come to that.
Archangel said:
Thanks for giving it a try,,,was hoping it would work but I doubted it. Hopefully Magisk can be updated for root! If not, this is going back,,,not enough of a worthy upgrade esp if root is not possible.
Click to expand...
Click to collapse
Root will come. Give it time
Same tried patching boot.img, fails to boot. Reflashing stock boot.img fixes it. Never really looked at the sizes before, but the patched_boot.img is roughly half the size of the stock boot.img
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.
Android 11 has been released. Anyone upgraded yet on a rooted device?
Subscribing for root results.
I will try later in a bit and let you know the results.
I need food and drink and the files. Note anyone from India - Please dont download the A11 Files as it isnt for your device.
fkofilee said:
I will try later in a bit and let you know the results.
I need food and drink and the files. Note anyone from India - Please dont download the A11 Files as it isnt for your device.
Click to expand...
Click to collapse
I'm curious to know too!
We gots Root!
So far so good root is working
XMayhem2099 said:
So far so good root is working
Click to expand...
Click to collapse
how did you root? same steps as before with the monthly Android 10 releases? which Magisk are you using?
dimm0k said:
how did you root? same steps as before with the monthly Android 10 releases? which Magisk are you using?
Click to expand...
Click to collapse
I'm guessing, take the OTA, install magisk to inactive slot, reboot and done?
antiochasylum said:
I'm guessing, take the OTA, install magisk to inactive slot, reboot and done?
Click to expand...
Click to collapse
oops, I was hoping to do it via full image rather than OTA
dimm0k said:
oops, I was hoping to do it via full image rather than OTA
Click to expand...
Click to collapse
Probably better to do that lol. My ota is sitting at 1.72gb so it would seem to be a full image.
Did the 1st flash... Didnt boot - Unlocked BL - Looks like nothing flashed to Partition A / Boot A.
Flashing again now ^^
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Do you use the canary build of Magisk or the stable release?
Anyone got a replacement for overscan?
matekaneve said:
Do you use the canary build of Magisk or the stable release?
Click to expand...
Click to collapse
Canary
Well after redownloading the Core Files and updating ADB - Looks like we are alive...
Checking root now.
gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Not working here either, we need to wait for Magisk update, most probably.
gettinwicked said:
I can't get it to root. I do a fastboot flash boot magisk_patched.img and it fails every time. Anyone had any luck rooting this way?
Click to expand...
Click to collapse
Yes, successfully rooted this way. I didn't play around with any of the betas so this was my first time to just dirty flash right over 10. I patched my own boot.img like usual and transferred it over to my adb folder before flashing. Since you're using MM Canary already, I don't know what to tell you. Maybe your patched boot.img is corrupt? Did you flash the full image or OTA? Next step for me (after creating a new patched boot.img) would be to clean flash the full image. Best of luck.
do you have a link to the canary apk?
I tried going to the canary page, but the download link is dead. TIA
v12xke said:
Yes, successfully rooted this way. I didn't play around with any of the betas so this was my first time to just dirty flash right over 10. I patched my own boot.img like usual and transferred it over to my adb folder before flashing. Since you're using MM Canary already, I don't know what to tell you. Maybe your patched boot.img is corrupt?
Click to expand...
Click to collapse
Further down the page youll see it
https://github.com/topjohnwu/Magisk
---------- Post added at 20:29 ---------- Previous post was at 20:27 ----------
Also to add - Magisk Canary outputted a 4MB Boot Image which was wrong - Correctly patched it should be 32.55 MB roughly.
Make sure you pay attention that the boot.img has been patched properly.
I had trouble rooting but eventually got it to work. I deleted all previous boot images and patched images from phone and pc. Reinstalled platform tools. Grabbed fresh boot img from the factory image, patched it then flashed it. And we're in biz