rooting and twrp and custom roms - Google Pixel XL Questions & Answers

Hi so I just got this device from a friend. It is completely up to date running pie and Nov security.
I am coming from Nexus 6p. So a/b partitions are new to me.
So is the root process the same as it was for 6p?.
First unlock the bootloader. Then install latest twrp with fastboot
Then flash magisk.
Then after that install custom roms, kernels, ect?
Or is the a/b partition thing make things different?

mojorisin7178 said:
Hi so I just got this device from a friend. It is completely up to date running pie and Nov security.
I am coming from Nexus 6p. So a/b partitions are new to me.
So is the root process the same as it was for 6p?.
First unlock the bootloader. Then install latest twrp with fastboot
Then flash magisk.
Then after that install custom roms, kernels, ect?
Or is the a/b partition thing make things different?
Click to expand...
Click to collapse
Go here: [Guide] Pixel XL Android 9.0.0 (Pie) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + October 2018 Security Patch
Do #7 or #8 to Root/Reroot.
If you want to install a Custom ROM see Custom ROM section.

You pretty much got it. You can't flash twrp from bootloader no more. Out have to "fastboot boot twrp.img" which will get you temporarily into twrp, and if you want a permanent install you can flash the installer while in twrp

noidea24 said:
You pretty much got it. You can't flash twrp from bootloader no more. Out have to "fastboot boot twrp.img" which will get you temporarily into twrp, and if you want a permanent install you can flash the installer while in twrp
Click to expand...
Click to collapse
What? Please explain how you flashed twrp from the bootloader?

Go-to twrp website, and then tbe section for our phone "marlin". You'll see a twrp installer .zip file, and another twrp .img file.
Download the latest of the installer zip and the twrp img.
Commands will be
"Fastboot boot (filename).img"
Then when in twrp, go-to advanced, adb sideload and run the command "adb sideload (filename).zip"

Tell us how ya got Nov security when it has not been released for the Pixel....lol

noidea24 said:
You pretty much got it. You can't flash twrp from bootloader no more. Out have to "fastboot boot twrp.img" which will get you temporarily into twrp, and if you want a permanent install you can flash the installer while in twrp
Click to expand...
Click to collapse
homeboy76 said:
What? Please explain how you flashed twrp from the bootloader?
Click to expand...
Click to collapse
noidea24 said:
Go-to twrp website, and then tbe section for our phone "marlin". You'll see a twrp installer .zip file, and another twrp .img file.
Download the latest of the installer zip and the twrp img.
Commands will be
"Fastboot boot (filename).img"
Then when in twrp, go-to advanced, adb sideload and run the command "adb sideload (filename).zip"
Click to expand...
Click to collapse
Wasn't expecting an answer to the question, because I always flash twrp from bootloader/fastboot mode. Do you still sideload twrp.zip to install twrp, instead of flashings it with twrp

crackerjack1957 said:
Tell us how ya got Nov security when it has not been released for the Pixel....lol
Click to expand...
Click to collapse
Sorry my bad I am on October security not November. My 6p is on November and I just got this phone so I just got confused for a second.

You can just transfer the zip to your phone, and after booting the twrp.IMG you will be able to install it like a normal zip.

Related

HELP - TWRP on OnePlus 3 running the Open Beta 9 (Nougat ROM)

Here's the deal. I unlocked the bootloader of my OnePlus 3, flashed TWRP Recovery with "Tool All In One" through my pc. Then I was able to root my phone, I did it and then, flashed the Open Beta 9 through TWRP.
Now the problem I have now is that I'm unable to flash TWRP from my computer and I don't know why. It doesn't display any error or anything else. But when I boot into recovery mode, it is not TWRP, it's the stock one. Help me out. I want root and Xposed lol!
fastboot flash recovery TWRP.img
into recovery Vol Plus and Power
flash SU
beta9 is Nougat so xposed is not working yet.
takumintchan said:
fastboot flash recovery TWRP.img
into recovery Vol Plus and Power
flash SU
beta9 is Nougat so xposed is not working yet.
Click to expand...
Click to collapse
Yeah but, how to flash the recovery? What program or whatever I need to flash it?
Drkrs616 said:
Yeah but, how to flash the recovery? What program or whatever I need to flash it?
Click to expand...
Click to collapse
You need adb and Fastboot.
http://forum.xda-developers.com/showthread.php?t=2588979&page=95
On The Fastboot PATH
Same directory, Put twrp.img
Shift and Right Mouse.Open cmd and type
fastboot flash recovery "twrp file name.img"
You can get TWRP.
I recommend TWRP .28
After you can flash any Rom and Kernel , SU etc...
You need modified TWRP Recovery to Run Open Beta 9, official TWRP won't work
Here's the link for Modified TWRP
http://forum.xda-developers.com/devdb/project/dl/?id=21835
Thank you guys so much, I successfully flashed TWRP on my phone. First time, it didn't want to boot but when I rebooted it id did
... Well, update: Booted into system and when y tried to boot into recovery, this time unplugged from the pc, booted with stock recovery -_-
... Update of the update haha: I downloaded the root zip and then I flashed the TWRP, Installed root zip and made a backup of the whole system and now, the TWRP recovery is installed permanently. Thank you if you guys followed my thread.

Twrp and flashing a Rom

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.

Pixel 2 XL Root [Going Mad About]

Hi everyone,
I'm going mad about Pixel 2 XL Root. I'm Trying to use Magisk v18 on latest Android versione but I'm not able to root the device.
Everytime I try to flash Magisk the screen stays loading Google Icon in loop forever and ever. I've tried every guide on the web whitout success.
Anyone can help me?
[Edit]
Theese are the steps i take
-flash recovery twrp (ok)
-reboot to recovery (ok)
-flash magisk v18 (loop)
megamarini said:
Hi everyone,
I'm going mad about Pixel 2 XL Root. I'm Trying to use Magisk v18 on latest Android versione but I'm not able to root the device.
Everytime I try to flash Magisk the screen stays loading Google Icon in loop forever and ever. I've tried every guide on the web whitout success.
Anyone can help me?
Click to expand...
Click to collapse
All the usual preemptive steps are complete, correct? You OEM unlocked it and all that?
djcrystals said:
All the usual preemptive steps are complete, correct? You OEM unlocked it and all that?
Click to expand...
Click to collapse
Sure mate, I have rooted every smartphone owned since Xperia X8 and this is a very strange behaviour for me.
megamarini said:
Sure mate, I have rooted every smartphone owned since Xperia X8 and this is a very strange behaviour for me.
Click to expand...
Click to collapse
Don't feel too bad my friend, the P2XL is a quirky little bugger to say the least. I had a heck of a time rooting 9.0 after I updated from 8.1, then outa the blue, it worked. Here's a few steps to try.
1. Fastboot twrp, then flash magisk, try to boot.
2. Fastboot twrp, flash twrp.zip, boot up, then go back to twrp and flash magisk. If no go, do the same steps, except after you flash magisk, flash the magisk uninstaller zip, then flash magisk again.
3. Fastboot into twrp, flash twrp.zip, custom kernel.zip, then magisk.zip. if no go, then try the magisk uninstaller.zip method again.
4. Stick with it, be patient, sooner or latter you'll find the right combo. Also, it seems easier to root using a custom kernel, if your willing to try it :good:
Badger50 said:
Don't feel too bad my friend, the P2XL is a quirky little bugger to say the least. I had a heck of a time rooting 9.0 after I updated from 8.1, then outa the blue, it worked. Here's a few steps to try.
1. Fastboot twrp, then flash magisk, try to boot.
2. Fastboot twrp, flash twrp.zip, boot up, then go back to twrp and flash magisk. If no go, do the same steps, except after you flash magisk, flash the magisk uninstaller zip, then flash magisk again.
3. Fastboot into twrp, flash twrp.zip, custom kernel.zip, then magisk.zip. if no go, then try the magisk uninstaller.zip method again.
4. Stick with it, be patient, sooner or latter you'll find the right combo. Also, it seems easier to root using a custom kernel, if your willing to try it :good:
Click to expand...
Click to collapse
Thank You mate, when I'll get home I'll try to follow yor steps and I'll let you know. Any suggestion about kernel on stock firmware? ElementalX it's ok?
Had the SAME problem yesterday:
Fastbooted TWRP
Flashed TWRP
Flashed Magisk
---> STUCK
Flashed TWRP
Flashed Magisk
---> BOOTED UP
Sui77 said:
Had the SAME problem yesterday:
Fastbooted TWRP
Flashed TWRP
Flashed Magisk
---> STUCK
Flashed TWRP
Flashed Magisk
---> BOOTED UP
Click to expand...
Click to collapse
Tryed everything but nothing works..
megamarini said:
Tryed everything but nothing works..
Click to expand...
Click to collapse
Maybe give the guide linked in my sig a shot.
If that doesn't help, try the following:
-once you've permanently installed TWRP, try rebooting to recovery after each additional step BEFORE rebooting to system:
install cust kernel, reboot to recovery, reboot to system
install magisk, reboot to recovery, reboot to system
if that doesn't work, try doing a mass install after TWRP is permanently installed:
in the same flash, install cust kernel and magisk, reboot to system
These have helped other users who have had odd issues with their set ups, but in the end, Pixel 2 XL is a fickle beast
Best of luck!
Az Biker said:
Maybe give the guide linked in my sig a shot.
If that doesn't help, try the following:
-once you've permanently installed TWRP, try rebooting to recovery after each additional step BEFORE rebooting to system:
install cust kernel, reboot to recovery, reboot to system
install magisk, reboot to recovery, reboot to system
if that doesn't work, try doing a mass install after TWRP is permanently installed:
in the same flash, install cust kernel and magisk, reboot to system
These have helped other users who have had odd issues with their set ups, but in the end, Pixel 2 XL is a fickle beast
Best of luck!
Click to expand...
Click to collapse
SOLVED
The only way (for me) to root my Pixel 2 XL is follow theese steps:
Rooting with Magisk
NOTE #4: This section assumes you are not going to install TWRP. If you are, skip to the next section and just flash the latest Magisk zip after installing TWRP.
Download the Magisk zip from the official thread and install the manager from the zip.
Grab a boot image to patch (either the one from the latest factory image or a custom kernel one) and push it to your device:
Code:
adb push <path_to_file> /sdcard/Download
Open Magisk Manager and click the Install button.
Click "Install" at the first prompt then choose "Patch Boot Image File". A file manager will pop up.
Select the boot image you want to patch and let Magisk Manager patch it.
Pull it off your device:
Code:
adb pull /sdcard/MagiskManager/patched_boot.img
Reboot into the bootloader:
Code:
adb reboot bootloader
Flash the boot image and reboot.
Code:
fastboot flash boot patched_boot.img
fastboot reboot
Open Magisk Manager and you should be rooted!
Source: XDA Post
Thank you so much to everyone who tried to help me!

Rooting issues

I have a Pixel 3 XL and I was following this Guide to root it.
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
When I get to part 2-10 (The part to install Magisk) my phone wont boot into the OS. Instead I end up back at TWRP. If I reinstall TWRP from my download folder or restore a back up I can get back into the OS. I still have TWRP installed but no root. I know I'm doing something wrong but I'm not sure. Like I've said TWRP is install but not Magisk.
What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?
ktmom said:
What Android version; Pie or Q, stock or custom? What Magisk version? Are you booting to TWRP (fastboot boot twrp.img) or did you flash twrp to the device?
Click to expand...
Click to collapse
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.
ktmom said:
Try clean fastboot flashing the stock boot.img back onto the phone. You can get it from the fastboot factory img. Then just boot TWRP to flash the Magisk zip. The Magisk zip will need to be on the device for the booted TWRP to find it just like if you were running TWRP installed on the device.
An alternative is to use Magisk manager to patch the stock boot.img and then fastboot flash that patched img to the device.
Click to expand...
Click to collapse
I tried the easiest method first, which was installing the Magik app and flashing the zip, I got the following error,
Device platform: arm64-v8a
copying image to cache
Unpacking boot image
! Unsupported/Unkown image format
! Installation failed
I'll try flashing the stock image, but should I flash twrp again after the image? I've done this before in the past because some phones require it as part of the rooting instructions. Does this order sound right, flash stock image, reboot, flash twrp reboot, then Magisk?
Potatochip400 said:
I did this from a blank slate. Pie, stock, the newest version if Magisk 19.3. I flashed twrp to my device.
Click to expand...
Click to collapse
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Just tried the beta version (19.4) and I'm stuck in a standard bootloop. I'll try and get it into recovery.
No worries, I forgot to mention that I restored a back up
Eudeferrer said:
You must use the latest magisk 19.4.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Surely not on Pie. I'm using 19.3 on the last Pie.
ktmom said:
Surely not on Pie. I'm using 19.3 on the last Pie.
Click to expand...
Click to collapse
I'm on pie, but your first suggestion was the fix. I had to flash the factory img before doing everything else. I just had to put a little more time a side and not be lazy.

Pixel 3a XL soft #BRICK - please help

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!

Categories

Resources