Problems getting rooted (touch not working) - Google Pixel 2 XL Questions & Answers

Hey you!
So I am back using my Pixel 2 XL and I want to root it, but I am having a lot of trouble doing so... Things I have tried:
First time I just tried installing the zip from magisk, after that my phone was stuck in an endless boot loop, nothing to do there...
I have done as this guide says:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
So this is where I am right now:
Flashed the newest factory image "10.0.0 (QQ3A.200605.001, Jun 2020)" by running the "flash-all.bat", booted it up and everything was working.
Downloaded the newest twrp "twrp-3.3.0-0-taimen.img" and loaded it using fastboot.
Installed "twrp-pixel2-installer-taimen-3.3.0-0.zip" and rebooted into recovery.
Wiped userdata, installed AOSiP 10, rebooted into recovery and installed opengapps.
Booted up the rom and checked that everything was working.
Installed Magisk manager and copied over the boot.img file from the factory zip and did the "patch img" thing.
Rebooted into fastboot and did "fastboot flash boot patched_boot.img"
Now I can boot up the rom but... My touchscreen isnt working? power and volume buttons works just fine, twrp has the same problem after I install it with the zip (it works fine when booting it up from fastboot)
I tried installing the stock boot.img but that didnt change anything.
Another thing is that on slot B is the stock rom and on slot A is the AOSiP rom, is this normal? I don't know how the slot thingy works is it just like partitions?? The stock rom on slot B is working just fine.
-Hapse

Update:
I ran the "flash-all.bat" on both slots and booted up twrp using fastboot and installed the magisk zip (not the img) before installing the manager, I then installed the manager once I booted up the rom. So I guess it's stock with root for now...

hapse said:
Hey you!
So I am back using my Pixel 2 XL and I want to root it, but I am having a lot of trouble doing so... Things I have tried:
First time I just tried installing the zip from magisk, after that my phone was stuck in an endless boot loop, nothing to do there...
I have done as this guide says:
https://forum.xda-developers.com/pixel-2-xl/how-to/guide-unlock-flash-root-pixel-2-xl-t3702418
So this is where I am right now:
Flashed the newest factory image "10.0.0 (QQ3A.200605.001, Jun 2020)" by running the "flash-all.bat", booted it up and everything was working.
Downloaded the newest twrp "twrp-3.3.0-0-taimen.img" and loaded it using fastboot.
Installed "twrp-pixel2-installer-taimen-3.3.0-0.zip" and rebooted into recovery.
Wiped userdata, installed AOSiP 10, rebooted into recovery and installed opengapps.
Booted up the rom and checked that everything was working.
Installed Magisk manager and copied over the boot.img file from the factory zip and did the "patch img" thing.
Rebooted into fastboot and did "fastboot flash boot patched_boot.img"
Now I can boot up the rom but... My touchscreen isnt working? power and volume buttons works just fine, twrp has the same problem after I install it with the zip (it works fine when booting it up from fastboot)
I tried installing the stock boot.img but that didnt change anything.
Another thing is that on slot B is the stock rom and on slot A is the AOSiP rom, is this normal? I don't know how the slot thingy works is it just like partitions?? The stock rom on slot B is working just fine.
-Hapse
Click to expand...
Click to collapse
When you are on stock and you flash a custom rom, the custom rom will be flashed to the opposite slot of the stock rom. So yes, it is normal to have stock rom on 1 slot and the custom rom on the other.

Lughnasadh said:
When you are on stock and you flash a custom rom, the custom rom will be flashed to the opposite slot of the stock rom. So yes, it is normal to have stock rom on 1 slot and the custom rom on the other.
Click to expand...
Click to collapse
Ah I see, thank you

Related

Tried flashing Lineage OS but ended up stuck in a boot loop.

I unlocked the bootloader following Motorolas steps. I then flashed the latest version of TWRP avaiable on the development forum and then flashed Lineage OS + the root zip they provide and gapps. I couldn't figure out how to get out of the bootloop so I've since gone back to stock. Any idea what I was missing?
TWRP:
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629
Lineage:
https://forum.xda-developers.com/moto-z-play/development/rom-unofficial-cyanogenmod-14-1-t3495644
Did you read the notices and entries on the Linage last pages of the thread that people are having it fail on the install, the latest release? That would be a clue...
I even tried flashing Pure Nexus but that too was stuck on a loop. I left it for about 10 minutes as it was loading. :/
I did the same thing like you on my first attempt, on my second I was able to install Lineage OS successfully. I'll provide the steps I did.
First attempt steps:
1. Unlocking the bootloader using Motorola website
2. Installing TWRP from the same link in your post.
At that point I tried booting the phone, but the phone was booting to TWRP only, tried wiping, format data from TWRP with no luck.
3. From TWRP flashed Lineage OS zip file and GAPPS nano package (the latest version of TWRP is able to see SD card).
At that point I was able to to boot LOS only after executing "fastboot erase user data". Doing the same from within TWRP was not doing the job. The problem was that after each reboot the phone was getting into bootloop again and "fastboot erase userdata" was necessary.
4. At that point I noticed that TWRP thread starts with warning that you have to install a patcher to disable this "verity" feature of the bootloader may be. And I installed the patcher "Verity_FE_patcher.zip"
The patcher didn't fix the issue and went back to stock Nougat using the guide below:
https://forum.xda-developers.com/moto-z-play/how-to/moto-z-play-reteu-firmware-otas-t3557917
First I tried "flashall.bat" , but it didn't wor.k and I flashed all the files manually using the guide . The phone booted normally and I updated it with one OTA update.
Second attempt steps:
1. I wanted to install the verity patcher before anything else and I boot TWRP 3.1.0.1 without flashing it. It booted normally and I realized that the SD card was formated and the patcher zip file is not there. I reboot the system and the phone got in bootloops again even the TWRP was not installed. I coppied the patcher zip, LOS zip, GAPPS zip on SD card . I tried to boot (without flashing) TWRP again, but for some reason TWRP was not able to boot.
2. I flashed TWRP
3. Booted TWRP and flashed verity patcher.
4. Wiped from TWRP and boot the system
At that point I was able to boot the stock firmware with TWRP installed and I was able to restart the phone normally.
5. Flashed LOS and nano GAPPS
Now everything seems to work properly.
Hope this will help.
Thanks. I'll give this a shot tonight. Our first attempts sound very alike.

Normal boot always ends up in TWRP

Hello everyone,
I have a problem regarding the start-up of my phone. Yesterday I unlocked my bootloader and flashed TWRP (twrp-3.1.1-0-addison.img) with the help of the thread located here.
Everything worked fine, I could boot into TWRP afterwards. I continued by wiping the needed partitions and flashing the newest Lineage OS ZIP alongside with the GApps Nano ZIP.
The problem I face now is that when I reboot in TWRP by selecting the “System” option, I end up again in TWRP (same happens if I shut down the phone and make a normal boot).
However, if I boot to the bootloader and select there the normal “start” option, the phone boots up just fine using the installed ROM.
Any ideas what’s wrong here and how I cloud fix that?
This happens with me, i don't know If its gonna work with you but works for me, i just flash a older twrp image from the same thread you use, ( i install from bootloader, not flashing a img in twrp), then you boot on twrp, and then you install the latest recovery
Note: This works for me, i don't know if its work for you
{Sorry for my poor english, my native language is porruguese }
jst98 said:
This happens with me, i don't know If its gonna work with you but works for me, i just flash a older twrp image from the same thread you use, ( i install from bootloader, not flashing a img in twrp), then you boot on twrp, and then you install the latest recovery
Note: This works for me, i don't know if its work for you
{Sorry for my poor english, my native language is porruguese }
Click to expand...
Click to collapse
Thanks a lot, I will give it a try!
and then you install the latest recovery
Click to expand...
Click to collapse
Do you mean TWRP or a recovery image of the OS?
When i say to intall the latest version is for twrp
Unfortunately, it did not work ....
I flashed twrp-3.0.2-0-addison.img via fastboot, booted to TWRP and installed the newest image with the 'install' option from TWRP.
Phone is still booting to the recovery if I restart ....
_Hope_ said:
Unfortunately, it did not work ....
I flashed twrp-3.0.2-0-addison.img via fastboot, booted to TWRP and installed the newest image with the 'install' option from TWRP.
Phone is still booting to the recovery if I restart ....
Click to expand...
Click to collapse
Aww ! It's just a simple thing. Use this simple command "fastboot oem fb_mode_clear" and it will boot to normal system.
I was also facing this in my previous htc device.
That was tha problem of tge twrp version that i was using.
Try using the different twrp.

[Solved]Can't flash rom+gapps

So i originally had a p2c...blabla
Ota updated to p2a4 or something like that. sf244 ROW
unlocked oem (waited 14days)
flashed twrp.
factory resetted+format system. + data partition is ext4
rom flashed successfully
gapps starts flashing but keeps stuck after just 1% of flashing.. always.
or twrp keeps freezing.
Does anyone have a solution?
Right now i'm back to Stock Rom+Magisk 13.3 .
sm00th4f3 said:
So i originally had a p2c...blabla
Ota updated to p2a4 or something like that. sf244 ROW
unlocked oem (waited 14days)
flashed twrp.
factory resetted+format system. + data partition is ext4
rom flashed successfully
gapps starts flashing but keeps stuck after just 1% of flashing.. always.
or twrp keeps freezing.
Does anyone have a solution?
Right now i'm back to Stock Rom+Magisk 13.3 .
Click to expand...
Click to collapse
If you have backup then Install your stock rom and its every components such as boot, recovery etc....
Or download the fastboot files from the p2 thread and flash it.
Then properly install twrp.
How can i properly install twrp?.. I mean, i think i always installed in correctly...otherwise magisk wouldn't work., right?. Because it does. I need your help. I even got Safetynet Pass and Root Apps like Root Explorer is working Fine.
Only the Flashing of Custom Roms etc fails for me... It's weird.
Okey. I just redid it like 5 Times. And i got a bit farther.. new boot animation shows up. But still blue led after it stops.
I FINALLY found the SolutioN!!! I used this https://androidfilehost.com/?fid=817550096634780916 and did the upgrades per ota. Then adb'd my twrp on my phone. And changed data to ext4. Rebooted. Activated usb debugging again. flashed twrp again(just to be sure), booted into twrp. Formatted system,data,cache,dalvik and then flashed my roms. SUCCESS <3

[SOLVED] HELP! i'm stuck in a boot loop! :(

my flashing history:
i was on audax (oos based nougat rom) with blu spark kernel before, then went to official ob1, then back to audax, then back to stock oos nougat and now i flashed audax and after clean flashing it, it just wont boot up.
when i try to boot up i see the 1+ logo but then it reboots to recovery. i also tried flashing stock nougat again and also flashed stock kernel manually but it also doesnt work.
i always do:
1. wipe system/dalvic/cache/data
2. install ROM
3. wipe dalvik/cache
4. flash magisk (also tried without flashing magisk)
5. reboot
i've been looking on the interwebs all day but nothing worked.. help pls :/
EDIT: problem was blu spark twrp. Maybe installing Oreo ****ed it up. I flashed codeworkx newest twrp universal build and now Im able to boot again!! Btw: I also found that magisk 15.0 prohibits a proper boot up and results in a boot loop. version 15.2, however, does the trick!
when it auto reboot to recovery, formate data
When s**t happens, it is wise to start everything from scratch:
-boot in fastboot mode and flash stock recovery with "fastboot flash recovery recovery.img" (rename recovery.img with your recovery filename), then reboot recovery and select english, advanced, adb sideload;
-flash stock OS with "adb sideload rom.zip" (rename rom.zip with your Oxygen OS filename).
Procedure will require some minute because of the large file size. Remember to save all your data on internal storage first!
I advice you to flash original recovery because often sideloading in TWRP leads to some error.
Your phone will boot again... after that you may reflash TWRP, Magisk etc
I had the same issue. Bootloop and jumb into recovery by itself. You have to flash magisk 15.2 via recovery and will be boot.
redatak said:
I had the same issue. Bootloop and jumb into recovery by itself. You have to flash magisk 15.2 via recovery and will be boot.
Click to expand...
Click to collapse
He says that it occurs even without Magisk... I had a similar trouble once, and the only way to solve it was the procedure I wrote above...
I dont know if you can boot it w/o root
redatak said:
I dont know if you can boot it w/o root
Click to expand...
Click to collapse
Why not? Stock OS is not rooted.
jonsat said:
Why not? Stock OS is not rooted.
Click to expand...
Click to collapse
He said audrax not stock oos
SOLVED! TWRP was the only variable left that I didn't think of. See initial post for solution. thx for help!

TWRP+ Magisk issues. HELP?

Hi! I have a moto z2 play with the Pie stock rom flashed. Bootloader is unlocked but when I try to flash TWRP (used twrp_albus_treble_3.2.2_r23_64) via fastboot after the first system reboot it is always overwritten by default recovery. I tried to boot first to bootloader and than to TWRP, also tried booting the TWRP image and installing TWRP from phone storage, nothing works after system reboot it is always replaced by stock recovery. What am I doing wrong?
I also tried to install Magisk but it wont install, tried flashing through TWRP and also by patching the boot.img than flashing that.
Could use your input!
Thanks!
I have the same problem
I have the same problem
L7noop said:
I have the same problem
Click to expand...
Click to collapse
Did you find a working solution?

Categories

Resources