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.
Hey everyone! I'm sort of new to the whole custom recovery thing and while I know that there is a whole post concerning TWRP and Pixel 2XL, I would love if someone could take the time to explain, and maybe help me get it working on my phone.
BTW the reason I want to get a custom recovery is so I can flash a custom rom as Pixel OS just isn't cutting it for me anymore.
Here's what I know:
I am currently on an unlocked phone that is rooted on android 10. I heard that android 10 totally screwed up TWRP and makes it impossible to install after updating. Is that true? If so, is it possible for me to factory reset my phone to android 9 and then install TWRP after the fact? Or, have I totally screwed myself by updating to android 10? I know that I could just ask these questions on the other thread but it confuses me a lot and it would help if I could just get some clear answers.
TWRP works fine on Android 10. I would update to the latest update of Android(which is the August update for right now). Then copy any files( TWRP.zip and what ever Rom.zip) to your phone. Boot into bootloader and run the fastboot commands to boot into TWRP. Wipe data on your phone within TWRP and then proceed to flash the rim followed by TWRP.
Make sure you add the installer zip to the flashing queue when flashing a ROM or you'll get stock recovery again.
Hi, I got myself an used Motorola Moto G7 play (XT1952-1) with Android 10 Stock update (Build QPYS30.52-22-8-9) and just can't successfully install TWRP on it. What I did:
- Bootloader unlocked
- TWRP temporary loaded with fastboot (fastboot boot twrp.img)
- In TWRP 'Iinstall' selected the matching TWRP .zip and it said it was installed in both slots a and b.
But then, when I select 'restart to bootloader' and try to launch recovery, I get a bootloop (black screen with (N/A) in the top left corner. The OS as such still starts normally. So I guess the main problem here is the bootloop when trying to launch recovery...?
I tried installing over booted TWRP with unmodified boot.img and with Magisk patched boot.img, same result. The G7 play does not have a separate revovery partition, recovery is included in the boot.img
I used the TWRP files (EU) and instructions from here:
Motorola Moto G7 Play
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
My stock firmware is XT1952-1_CHANNEL_RETEU_10_QPYS30.52-22-8-9_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip from here:
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
Am I missing something? I've now searched for days (most info is outdated, taken from other places/Motorola phones with just 'G7 play' added, or is ambiguous); so can anyone *PLEASE* help me? Does anyone have a G7 play of the same type with Android 10 Stock who has successfully installed TWRP and was able to access the Recovery afterward without being stuck in a loop?
I also can't create a TWRP backup with a fastboot booted TWRP because system (and internal SD too) seems to be encrypted, and I don't seem to be able to deactivate this in the phone. Is this normal? Some places say that TWRP can decrypt when it's installed permanently...
Or could anybody patch the boot.img in above Firmware and add TWRP for me so I can just flash the boot.img?
Thanks in advance... please reply noob-friendly.
Still need a patched boot.img? Attached you'll find a boot.img with TWRP installed. I followed your links to get boot.img + twrp.img.
NO MAGISK INSTALLED!!!Please patch before flashing if Magisk is already installed.
I put a log of the repack command into the zip that is showing the checksums of the boot header. Just to have a proof.
WoKoschekk said:
Still need a patched boot.img? Attached you'll find a boot.img with TWRP installed.
Click to expand...
Click to collapse
Thanks for trying to help, but this boot.img behaves exactly like the one I made by following the installation instructions on the TWRP website. I flashed it, restarted bootloader, then tried to go into recovery, and it bootloops (black screen with N/A in the top left corner).
But what I need is a boot.img with a WORKING TWRP recovery (that can actually be launched when recovery is selected...
Any idea why this won't work, why TWRP won't start?
@Alonso_Quixana Try the attached one. It's a boot.img patched with twrp + recovery_dtbo. The recovery_dtbo is part of the twrp.img but TWRP's installer.zip doesn't take it into account while repacking the patched boot.img. Maybe (hopefully!) that's the reason why you're able to boot TWRP but not to install it permanently.
Please try also - in any case! - the patched installer.zip that comes with a recovery_dtbo.
Sadly, you can't flash TWRP on stock ROM, in case you did sucessfully, ROM will not boot and that can cause SIM and VoLTE issues, i did flash it on mine and now VoLTE doesn't work on my phone, you can only boot it in case you want to flash an custom ROM, flash it then reboot into recovery to install GApps on the Custom Recovery that the ROM does install, but since all of the ROMs are arm64, i don't recommend it since you will have constant app restarting when changing from one app to another app
chuy19312 said:
Sadly, you can't flash TWRP on stock ROM, in case you did sucessfully, ROM will not boot and that can cause SIM and VoLTE issues, i did flash it on mine and now VoLTE doesn't work on my phone, you can only boot it in case you want to flash an custom ROM, flash it then reboot into recovery to install GApps on the Custom Recovery that the ROM does install, but since all of the ROMs are arm64, i don't recommend it since you will have constant app restarting when changing from one app to another app
Click to expand...
Click to collapse
Thanks for replying...
I've seen so-called tutorials on Youtube where someone actually succeeded in installing TWRP on his Moto G7 play (but did not mention which Android version was on the phone), and the TWRP developers too claim that their version for Moto G7 play would work, it even got an official update for Android 10 (alas they never reply to direct e-mails, those snooty guys)... some on XDA even said the flashing of a 'dirty port' worked for them. Were they all mistaken? Or did it work on Android 9? Are all XDA threads and internet posts / Youtube videos misleading / lying?
Are you REALLY sure that there is no way to install TWRP on a Moto G7 play (to be able to create a working backup of the encrypted data partition)? A 'full restorable backup of everything' is what I need...
I'm not sure about Android 10 Stock Rom, but it seems to be a 32bit system on a 64bit Kernel?
Alonso_Quixana said:
I'm not sure about Android 10 Stock Rom, but it seems to be a 32bit system on a 64bit Kernel?
Click to expand...
Click to collapse
It's a 32bit system on a 64bit CPU (Snapdragon 632). That's not unusual for Motorola devices. Open a terminal app and execute uname -a.
Alonso_Quixana said:
Thanks for replying...
I've seen so-called tutorials on Youtube where someone actually succeeded in installing TWRP on his Moto G7 play (but did not mention which Android version was on the phone), and the TWRP developers too claim that their version for Moto G7 play would work, it even got an official update for Android 10 (alas they never reply to direct e-mails, those snooty guys)... some on XDA even said the flashing of a 'dirty port' worked for them. Were they all mistaken? Or did it work on Android 9? Are all XDA threads and internet posts / Youtube videos misleading / lying?
Are you REALLY sure that there is no way to install TWRP on a Moto G7 play (to be able to create a working backup of the encrypted data partition)? A 'full restorable backup of everything' is what I need...
I'm not sure about Android 10 Stock Rom, but it seems to be a 32bit system on a 64bit Kernel?
Click to expand...
Click to collapse
I think it only works on certain Moto G7 Play variations or even only on Android 9, also, another way to install TWRP is installing an Custom ROM then flashing an flashable zip of TWRP_11 by SyberHexen on Custom ROM's Recovery
Link to TWRP_11 Flashable Zip
channel-twrp-installer-3.6.2_11.0_RC-1.0.zip | by SyberHexen for Moto G7 Play
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
In my case, flashing TWRP, even by following some tutorials made my MetroPCS Moto G7 Play to stop booting and also, VoLTE stopped working, fortunately, i had an EFS backup to restore my IMEI
Android 10 Stock Rom is an Arm (32 bits) ROM, every Custom ROM i tested are Arm64, but i don't recommend any of them since you will get constant app rebooting and notification problems since this is an 2 GB RAM device
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.
Hi everyone,
I'm writing this blog post to ask for some help from the XDA community. I have a Samsung A22 SM-A225F and I want to install a custom ROM on it, preferably an Android 12 GSI. However, I'm having some trouble getting it to boot properly.
I'm following the directions on this blog post which claims to have successfully installed Android 12 GSI on the same device. The steps I'm following are as follows:
Use Odin tool to flash the stock verified ROMs on my phone to start from zero.
Flash the (magisk patched.tar) file on AP
Boot to Android and set it up then install Magisk app to check for root (I'm doing this because it doesn't work otherwise)
Flash TWRP and run multidisabler then boot again to check if everything is working.
Finally flash the system.img, I'm not sure about vbmeta so I'm skipping it.
But I keep getting a bootloop no matter what I try, I've tried wiping cache and everything.
Weirdly enough I have flashed stock Android like two days ago except that it actually booted to set up but it didn't detect the network and kept mini rebooting from time to time.
I've tried the steps in that blog for Android 11 to flash crDroid but that also didn't work, I've also tried flashing crDroid even when following the steps for Android 12. Still no success.
I'm wondering if anyone has any idea what I'm doing wrong or what I can do to fix this issue. I've read some other guides on how to install custom ROMs and GSIs on Samsung devices without TWRP but they seem too complicated for me.
If anyone can help me out or point me in the right direction, I would really appreciate it. Thanks in advance! and i'll gladly provide any information required when i have time as it's currenlty night time
what twrp u using also where u flashing it using fastboot or from TWRP ?
i recommend u using fastboot to flash GSI