Could somebody please guide me on how to root my Pixel XL using magisk???
I'm not trying to be an åsshole, but did you search at all?
I can only give you the broad steps. You need to go to the TWRP thread for the Pixel XL and download both the TWRP zip and boot image. The zip goes on your phone's internal memory after your bootloader is unlocked. You need to get the Pixel XL modified version of Magisk which is located in the Resurrection Remix rom thread for reasons nobody has ever been able to explain. The official version of Magisk will not work on the Pixel XL. The Magisk zip also goes on your phone's internal memory. You put your phone in bootloader mode and attach it to your computer. Using a fastboot command you boot up into the TWRP boot image that is on your computer which creates a temporary TWRP. You use that to flash the TWRP zip and the Magisk zip from the internal memory of your phone. Then you boot once into your rom. After doing that you boot back into the bootloader again, use the fastboot command to flash into the TWRP boot image again, flash the TWRP zip again and then boot back into your Rom. If you don't do this TWRP probably won't stick and you will end up with stock recovery again.
If you don't know about fastboot commands or downloading the proper Android tools to your computer then you need to do some research on the basics of rooting this phone. There's a thread on XDA with instructions on how to root the Pixel XL that isn't great but it should give you the basic information you need if my instructions are too broad to be at all useful.
You want to make sure you are on the June bootloader before rooting. If you aren't up to date it gets more confusing because you might also need to flash an additional boot signature file which isn't necessary if you are on the June bootloader. You also don't want to use the beta version of the modified Magisk file which is currently too unstable for the average user to deal with.
I wish you luck. If something goes wrong you should be able to get back to stock pretty easily by using the flash-all.bat command to flash the full Google stock image. The Pixel XL is more challenging to root than most phones but one positive thing is that it seems to be virtually impossible to hard brick this phone.
Related
I absolutely hate the navigation buttons and the lack of a app drawer so I jumped when I heard I could put a custom Rom on it. So I unlocked the boot loader but couldn't for the life of me get twrp on it so feeling defeated I decided not to mess with it but now the darn thing won't boot it goes to the recovery screen and not any further. So I guess I need help reversing this or completing the twrp install... I don't really care which cuz I just need a working phone. (Preferably with twrp installed so I can put a different Rom on..)
Need a working phone with stock? Extremely easy. Flashing stock has been made very easy.
Just download factory image and follow the instructions here
https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
And since you cannot boot just reach the recovery page, check if you are able to run fastboot command (fastboot devices) and then run the bat file as instructed in the guide above.
This will wipe everything and help you flash stock to your device.
Getting recovery on Robin is easy too. Not sure what went wrong for you. Make sure you have everything in place first.
Download and install Minimal adb/fastboot https://insider.razerzone.com/index...der-flash-custom-recovery-decrypt-root.23775/
Download and install Robin USB Drivers (just in case) https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
Download latest TWRP https://dl.twrp.me/ether/
Download latest factory image https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
If you want to root then get the latest version of Magisk https://forum.xda-developers.com/apps/magisk (v14 worked fine for me)
Download the custom ROM of your choice
After unlocking the bootloader, just flash the recovery file with the fastboot command and select recovery on your device, you should see TWRP in 1-2 minutes.
Watch this video till 7:34 https://www.youtube.com/watch?v=DKyEhn9clNw
Once you have flashed TWRP properly, now you can push magsik, ROM and gapps and flash them one by one to root and install custom ROM of your choice.
Hope it helps.
So I've done a lot of reading and there are multiple threads with steps that aren't exactly clear or contradict each other or are outdated. I just want clarification on what I believe are the steps to flash a custom rom (7.1.2 since I can wait for 8) on a brand new Pixel XL.
Setup phone to the point of enabling adb debugging and oem unlock
Fastboot unlock
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
Should this give me custom ROM, root and twrp that I can boot directly to without a pc again? As long as I do twrp flashing after a ROM each time it'll stick? Also, I keep seeing things for setting a pin before initial twrp boot but without spending 4 days reading I can't find the reason for it. Should I be flashing vendor, bootloader and radio for the latest Nougat release BEFORE unlocking or can I do it through fastboot prior to unlocking?
Coming from Nexus 6P and that was my first run in with the bootloader, radio and vendors so I want to avoid issues for myself. Phone should be here tomorrow and want to get down to business right away lol.
Any and all information is greatly appreciated. If all of this is answered in a centralized area please point me to it and tell me I'm stupid for missing it.
Sent from my SM-N910P using Tapatalk
Found this over in PN thread. Is it accurate? Seems similar to my process.
https://forum.xda-developers.com/showthread.php?p=73846565
wgrant said:
Fastboot boot twrp RC1 img
Flash twrp RC2 zip in twrp
Reboot to installed twrp
Wipe system, data, caches
Flash ROM
Flash twrp again
Reboot to twrp
Flash gapps and root method (magisk working for 7.1.2 or should I be using supersu? Also which versions?)
Flash twrp again??
Boot to ROM then setup and use like normal
https://forum.xda-developers.com/showthread.php?p=73846565
Click to expand...
Click to collapse
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.
noidea24 said:
Assuming the bootloader is already unlocked and disregarding the unlocking instruction, these instructions are dead on accurate. I personally dont use magisk, but maybe another user will chime in. For 7.1.2 id use supersu 2.82.
You dont have to flash twrp again after flashing gapps and supersu, but its a good practice to have.
Click to expand...
Click to collapse
Thank you very much. I'm about to unlock and go nuts on my phone. New phones are so fun to fiddle with!
if you want to use magisk you'll need to flash a custom kernel before you flash magisk. Also you'll need a modified magisk zip. Search around the thread you'll find one, the latest version I found was magisk v13.3.
Edit: Just found out magisk is officially support for pixel on version 14.1 Check out the magisk beta thread.
On my way to installing LineageOS I tried to downgrade Android version 11 -> 10. Unfortunately I used the WRONG INCOMPATIBLE firmware files from google's website (I think for 3 XL), that's why I have a brick now. ''Device is corrupt and no bootup possible.''
Access to Fastboot and STOCK Recovery Mode is possible.
Bootloader is Locked Now (it *was* unlocked before for flashing the firmware)
ADB is not working (since I'm getting stuck on ''google'' symbol when booting up I can't go to Developer Settings)
Factory Preset from Recovery Mode fails: ''can't send spi messages.'' Same Brick occurs.
With No Access to ADB (is it possible to set up from fastboot mode without enabling it in den Developer Options?) I can't try stuff.
And with the bootloader locked no way to flash a new Rom right?
I have NO IDEA what to do next, any IDEAS??
Thank you!!
#brick
Since you can get to recovery you should download the latest ota and sideload it from recovery.
https://developers.google.com/android/images
you should flash the stock image from recovery. Basically unzip it all and just run "flash-all.bat"
41rw4lk said:
Since you can get to recovery you should download the latest ota and sideload it from recovery.
Click to expand...
Click to collapse
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?
dadu1257 said:
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?
Click to expand...
Click to collapse
You need the BL unlocked to flash unsigned/unofficial images, so make sure yours is unlocked. That being said, I'm not sure how solid twrp is for our device, I've never tried it. Twrp was/is a little iffy for android 10 never mind 11. Most around here just use fastboot to do what needs to be done. Most of it is pretty quick and painless, and twrp is not really necessary.
dadu1257 said:
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?
Click to expand...
Click to collapse
I'm pretty sure you would have to downgrade to android 9 (pie) and install a custom kernel to get twrp to install. Unless you want to rock android pie - like I currently am (Bootlegger's 9 - I like my smartbar customizations) - it's best to give up on TWRP and just use fastboot commands for android 10 and up.
If you do decide to downgrade to pie the elementalX kernel (ElementalX-P3a-1.06) works fine with twrp and is available on their site. Temp boot twrp via fastboot, flash kernel, flash twrp zip file, reboot to recovery and flash magisk zip for root (if you want root). But it may be hard to find older pie ROMs out in the wild to flash since devs have dropped support and will be focused on android 10/11.
teemothay said:
I'm pretty sure you would have to downgrade to android 9 (pie) and install a custom kernel to get twrp to install. Unless you want to rock android pie - like I currently am (Bootlegger's 9 - I like my smartbar customizations) - it's best to give up on TWRP and just use fastboot commands for android 10 and up.
If you do decide to downgrade to pie the elementalX kernel (ElementalX-P3a-1.06) works fine with twrp and is available on their site. Temp boot twrp via fastboot, flash kernel, flash twrp zip file, reboot to recovery and flash magisk zip for root (if you want root). But it may be hard to find older pie ROMs out in the wild to flash since devs have dropped support and will be focused on android 10/11.
Click to expand...
Click to collapse
Unlike most of the LineageOS Tutorials out there is used the Custom Recovery from Lineage to install LIneageOS! It was super easy, a few ADB commands and here it is. No Root, no TWRP whatsoever.
Follow wiki lineageos devices website instructions. Here you may also find the recovery data.
Thx guys/girls!
dadu1257 said:
Unlike most of the LineageOS Tutorials out there is used the Custom Recovery from Lineage to install LIneageOS! It was super easy, a few ADB commands and here it is. No Root, no TWRP whatsoever.
Follow wiki lineageos devices website instructions. Here you may also find the recovery data.
Thx guys/girls!
Click to expand...
Click to collapse
Cool. No more soft brick for you :good: Congrats on sorting things out. :highfive:
BUT I still cannot install TWRP Recovery on LineageOS 17. I am getting the same problem as quoted below.
I want to perform Nandroid Backups, any other way to that if TWRP doesn't want me? Maybe with a Magisk Root and some app from F Droid?
?
thanks
dadu1257 said:
Thank you, this worked perfectly fine, since you don't need an unlocked bootloader to flash this system image.
However, I am facing a new problem on my way to installing TWRP Recovery Image...!!
CMD gives me THIS log:
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed
- the device is unlocked (I even relocked it and unlocked it again, didn't work)
- I tried one other older .img for my phone from official twrp.me website, didn't work
Any Ideas?
Click to expand...
Click to collapse
dadu1257 said:
BUT I still cannot install TWRP Recovery on LineageOS 17. I am getting the same problem as quoted below.
I want to perform Nandroid Backups, any other way to that if TWRP doesn't want me? Maybe with a Magisk Root and some app from F Droid?
?
thanks
Click to expand...
Click to collapse
Twrp doesn't work very well on android 10 and above, there is a twrp install guide around here, but not much has come from it. When was the last time anyone actually made and used a nandroid backup? Not that backups aren't important, but that's a little antiquated. Besides, most are really trying to backup data, which is a shared partition on A/B devices. Generally, restoring data on A/B devices causes more problems than anything. Most data backups can be done with an app and/or making a backup of your internal storage. As for more sensitive things like your persist partition and whatnot, you can always use the 'dd' command to back those partitions up.
I should clarify, restoring nand backups of data causes more problems on A/B devices, apps that restore data and settings tend to handle it better.
Now having a different problem
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
When I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed.
I am stuck in Fastboot now.
How can I get out of that?
I used the boot.img from the google firmware android 10 I built Lineage on. Should I use a boot.img from LineageOS .zip? Is there anything like this?
What is dm-verity?
Can I get to my previous unrooted device?
I have a Pixel 3aXL with LineageOS 17
''bootslot: b
enter reason: error boot prepare''
dadu1257 said:
Now having a different problem
I tried to install Magisk following this guide https://magisk.download/root-pixel-3a-3a-xl/
When I try to flash magisk_patched.img in fastboot, it flashes, but reboots to fastboot with "error boot prepare" displayed.
I am stuck in Fastboot now.
How can I get out of that?
I used the boot.img from the google firmware android 10 I built Lineage on. Should I use a boot.img from LineageOS .zip? Is there anything like this?
What is dm-verity?
Can I get to my previous unrooted device?
I have a Pixel 3aXL with LineageOS 17
''bootslot: b
enter reason: error boot prepare''
Click to expand...
Click to collapse
Reflash the boot.img from Los17 to get back to proper boot up, then patch Los17 boot.img and flash that to have root.
41rw4lk said:
Reflash the boot.img from Los17 to get back to proper boot up, then patch Los17 boot.img and flash that to have root.
Click to expand...
Click to collapse
Where is the boot.img from Lineage? There is no such file in the Lineage folder I downloaded.
dadu1257 said:
Where is the boot.img from Lineage? There is no such file in the Lineage folder I downloaded.
Click to expand...
Click to collapse
A lot of devs wil upload the boot.img separately when they upload the rom, so wherever you downloaded Los from check there. If you just have a payload.bin file in your zip, you can always dump it and grab the boot.img there. You could always just reflash Los period to get boot back, then us 'dd' command to backup your own boot.img.
custom recovery for lineageos 17 based on android 10?
teemothay said:
I'm pretty sure you would have to downgrade to android 9 (pie) and install a custom kernel to get twrp to install. Unless you want to rock android pie - like I currently am (Bootlegger's 9 - I like my smartbar customizations) - it's best to give up on TWRP and just use fastboot commands for android 10 and up.
If you do decide to downgrade to pie the elementalX kernel (ElementalX-P3a-1.06) works fine with twrp and is available on their site. Temp boot twrp via fastboot, flash kernel, flash twrp zip file, reboot to recovery and flash magisk zip for root (if you want root). But it may be hard to find older pie ROMs out in the wild to flash since devs have dropped support and will be focused on android 10/11.
Click to expand...
Click to collapse
thanks!
I got Lineage 17 w/ Magisk root running now and want to perform a full NANDroid Backup.
After some research it seems crucial to have a custom recovery like TWRP for that. There is the online nandroid thing - but I would need CWM or anything like this to restore?!
So my question is
a) is there another custom recovery (compatible with Pixel 3a XL w/ lineage 17 based on android 10) I can install and perform Nandroid backup with?
b) any other solution to perform this backup and restore? I heard there are cmd commands for that as well , but I'm a noobie not so sure to do that.
of course there are several apps out there to backup data.. but I don't trust ''any'' app to get root permission. In F Droid I couldn't find what I was looking for.
thank you for help!
How can i root this phone?
Could anybody explain step by step
Muchas gracias.
By the way, how can i do a complete backup ( there's no oficial twrp)
Basically, as any other if you are familiar with (that is recommended method by TJW on his GitHub, Magisk Documentation) with patching the boot.img and flashing
In very short outlines (google for details or search here on XDA, sorry I will not guide anybody by spoon-feeding):
1) Unlock Bootloader, be aware that all Data will be erased
2) Download the zip file for the exact stock firmware you are running (MIUI version and region), Recovery type MIUI installation, unzip and extract boot.img
3) Install Magisk application, open, click on Install Magisk, select Patch method, navigate to your extracted boot.img
4) Copy the patched boot.img from Download folder to PC, run Fastboot and test does it boot correctly (it should, if you extracted from the correct MIUI zip installation file):
fastboot boot <patched boot img>
If it does, permanently flash the root/Magisk by:
fastboot flash boot <patched boot img>
Be aware that by rooting your warranty might be void (you can always, unless you would brick the phone, uninstall Magisk and relock BL)
Be also aware that by rooting, banking and similar apps may stop working and that you would need to search, read and learn how to hide the root - that may become your permanent mouse and cat hobby then
-
Btw, right here on this same XDA subforum for Lisa there are already posts and a thread (I did open a months ago) for how to root.
I'd expect that somebody would search and read before asking
Second, there is an Orange Fox custom recovery for Lisa working on MIUI 13 and you could flash Magisk apk (does not even need to be renamed to zip) from that custom Recovery to install Magisk
However, installing custom Recovery to Lisa (being a device that does not have separate Recovery partition but Recovery is integrated to the Boot partition) is tricky and if you don't correctly follow the guide (you would need to find its thread, read how to install) you could soft brick your phone
Thus, I really recommend patching and flashing the boot.img method instead
I was looking for the solution before asking the question and nothing came up about it, anyway I just did it by sideload.
The Orange fox method gave me a black screen and I had to format the phone twice because there was no way to get it to work.
Regarding the backup, I meant that with the twrp that has been used it was always an option visible in the interface, but with the specific recovery of PixelOs I don't see the option.
Thanks for your answer.
gintony said:
I was looking for the solution before asking the question and nothing came up about it, anyway I just did it by sideload.
The Orange fox method gave me a black screen and I had to format the phone twice because there was no way to get it to work.
Regarding the backup, I meant that with the twrp that has been used it was always an option visible in the interface, but with the specific recovery of PixelOs I don't see the option.
Thanks for your answer.
Click to expand...
Click to collapse
I don't know about that PixelOs recovery (and is it for general usage or only for installing PixelOs
Also, don't know about PixelOs
My answer was about rooting stock MIUI or Xiaomi.eu, both MIUI 13/A12
And the same for using OrangeFox-R11.1_2-Unofficial-lisa - installing and using with MIUI 13
I do have Lisa and I successfully used and still use that OFox, and I'm running the rooted MIUI 13
Hi all,
I have recently shifted from Samsung A52S to Onpelus 9 PRO.
I'm now a bit confused about flashing method....
I mean :
on Samsung devices, you have to use ODIN ( that is a Fastboot replacement tool ) in order to flash the TWRP and then, on TWRP, you can freely flash any new custom ROM or any other img files, by simply press "INSTALL" button instad of ADB sideload commands.
If I well understood, in order to flash this custom ROM, I have to do that through Fastboot commands before and through TWRP ADB sideload commands after......
My question is : may I flash boot.img / vendor_boot.img / dtbo.img and ROM zip directly through TWRP "INSTALL" button instead ???
If not, can someone kindly explain which is the reason why ?
Sorry for this noob question but I'm doing my first step into Oneplus and I don't want to do a mess.....
Many thanks for the help !
I personally been wanting to know why we no longer can simply flash custom roms via TWRP like we use to. I do believe its got to do with the way the A/B partition works however that does not really answers why we can't just flash via TWRP. Unfortunately, I have not been able to find the answer so I am interested too on why we can't simply flash custom roms in TWRP and have to resort in sideloading or via fastboot. I would think flashing via a zip in TWRP will have less user errors compare to using a command line to do your flashing.
Saying that, I have been flashing via fastboot since I got this phone and even though its a longer process, it only takes a few more minutes.
twrp is not even fully adapted for android 12 or 13 (but who needs twrp anymore?)
I prefer to flash via fastbootd
(is less work for me)
best way is the magisk install
ChrisFeiveel84 said:
twrp is not even fully adapted for android 12 or 13 (but who needs twrp anymore?)
Click to expand...
Click to collapse
twrp is still the only way to backup the whole rom
it exist a non official version for 12/13
TWRP is the best tool to recover files when the OS does not boot. Since there is no ROM or kernel out there that recommend or uses TWRP for flashing. There is little reason to use TWRP unless is for file recovery. This is in respective to OP 9.