Rooting went fine Flashing rom almost bricked me due to directions?? - Google Pixel 2 XL Questions & Answers

I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Sent from my [device_name] using XDA-Developers Legacy app

androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list out what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol

CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I know it's a typo but condom kernel cracked me up. Does it automatically boot you to safe mode?
Sent from my Pixel 2 XL using XDA Labs

androidddaaron said:
I instslled magisk apk and then booted twrp .img in fastboot as directed and flashed magisk zip from twrp as said too . I Rebooted and was rooted fine . Downloaded Resurrection rom and the guide said to only wipe in twrp flash rom then flash twrp zip again and reboot/profit . The rom splash screen just sat there spitting out little purple pink splatters and never booted so I rebooted into twrp and flashed the twrp zip to make twrp permanent and ended up losing my stock backup from the boot.img twrp and my internal storage . Had taken all night to find the right tool kit to flash firmware back .
What went wrong ? How do you flash rom on this phone I'm no noob but I'm not risking it again .
After you boot twrp and flash magisk are you supposed to flash twrp.zip then make your backups and flash roms? I wasn't sure if it was a long bootup or not gonna boot ever
Click to expand...
Click to collapse
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly

Vinnipinni said:
What?
I never flashed a custom ROM on this device, but it should be fairly easy. Turn off security settings on stock ROM, flash permanent twrp. Wipe system, dalvik/ cache and data and install RR. Boot and wait a few minutes, it sometimes takes some time. I don't know how the gapps situation is, so you might need to flash gapps. Also make sure to make a backup since you will wipe all data. Should be fairly easy of you followed the steps correctly
Click to expand...
Click to collapse
What I' did to flash the rom was separate from rooting procedures . The phone been unlocked for months.
I did both separate times
I fastboot booted twrp.img then I installed magisk zip. I did not permanent flash twrp zip after . I only flashed the perm twrp zip after I wiped and flsahed the RR Rom . So another words I was on twrp temp boot only when I flashed the rom then I flashed twrp zip per the rom Dev instructions . But I can't make sense why you have to flash twrp after you flash a rom install .
I'm assuming it goes like this
Install latest magisk apk.
Fastboot boot twrp .img
Then perm flash twrp .zip
Then flash magisk .zip
Reboot into the O.S and check for root
Reboot into (permanent Twrp) swipe to allow modifications .
wipe stock rom with the swipe only method??
Install Rom of choice and reboot !
Or is it install Rom /flash twrp.zip for a second time then reboot
Sent from my [device_name] using XDA-Developers Legacy app

CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
I want to flash a rom but I'm not understanding how the pixel 2 xl works with twrp vs other devices .
If I reboot without first flashing a kernel then maybe that's the dilemma?
I just don't get why you need to flash permanent twrp .zip after you install Rom If you already had twrp permanent installed to begin with .
I' went over what I did in this thread and what I'm guessing I did wrong. So do I need special kernel for each and every rom listed . I never had to flash a kernel to get a rom to boot on any device and I've been flashing for years with T-Mobile phones on Galaxy devices and unlocked Google based phones.
Sent from my [device_name] using XDA-Developers Legacy app

I don't get why you would need to flash magisk before.
0. Make Backups and turn off security settings. Also make sure you're on the newest OTA
1. Boot into TWRP
2. Do a factory reset in Wipe settings.
3. Flash ROM
4. Flash TWRP of you want, not required but recommended
5. Reboot and set it up
6. Install magisk Manager and reboot to TWRP
7. Flash magisk and reboot
That's it.

CyberpodS2 said:
I see a couple possible problems with your steps. The biggest is not being prepared. Not a shot at you but a fact that comes with a new device. The easiest route at this point would be to list our what exactly you want to have as a finished project. I'm assuming rooted RR with installed TWRP? I ask because if you want to have TWRP installed you should also use a condom kernel that has the touch drivers. I'm not sure if RR had them by default it not. Anyway, confirm what you want and I'm sure one of us will get you pointed in the right direction. You won't find most of us using a tool kit, so you will learn the "right" way... Lol
Click to expand...
Click to collapse
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?

nein7three said:
Hey let me ask you something, I just got the Pixel 2 XL but I always do a lot of research. Something I wasn't prepared for is the touch issue in TWRP. It works fine when initially installed, works fine sometimes after a reboot, but always ends up not working because touch isnt working. You're saying I can install a custom kernel and that should be fixed? I've always rocked Elemental or Franco's but am on rooted stock and since I've never stayed stock before I'm not even sure if I can flash another kernel without changing ROMs. If I can, or even if I have to change ROMs, you're saying that most custom kernels have the touch in TWRP working?
Click to expand...
Click to collapse
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done

Badger50 said:
All the custom kernels fix the twrp touch issue. You can flash them anytime you want on stock rom via twrp. Just disable screen lock(just initially for safety) boot into twrp, flash your kernel then magisk, reboot and done
Click to expand...
Click to collapse
Thanks a lot. Does changing kernels remove magisk?

nein7three said:
Thanks a lot. Does changing kernels remove magisk?
Click to expand...
Click to collapse
Some do, some don't. That's why you flash magisk after the kernel. But that's changing as well :good:

Related

device boots automatically in recovery

Received my zenforce 2 (ZOOA) yesterday and succeeded after various attempts to get bootloader unlocked and TWRP installed.
The problem is my device only boots in TWRP when it's power off and I start it, or if I restart it from TWRP. Besides I tried to install cyanogen and other roms on it, but no matter what it keeps booting into TWRP....
Hoping to get some help
flash stock recovery flash stock rom boot into it do all settings then flash custom recovery again then wipe and then flash your custom rom that happened to me thats how i solved it i also flashed stock droidboot.img
thanx a lot for your answer metty, you saved my phone !
I got to get all done with your instructions, except I reinstalled TWRP img right after installing boot.img and droidboot.im through fastboot
this way I could install custom rom right away
thanx again, really appreciate...
cuberio1 said:
thanx a lot for your answer metty, you saved my phone !
I got to get all done with your instructions, except I reinstalled TWRP img right after installing boot.img and droidboot.im through fastboot
this way I could install custom rom right away
thanx again, really appreciate...
Click to expand...
Click to collapse
no problem man glad i could help and enjoy the wonder that is android and the zenfone btw you should stay on stock rom with audio wizzard for now otherwise audio sounds trash
Thanx your advice.
Had to move to a custom ROM based on stock anyway, as the other ones based on CM gave me freezes and random reboot (even without xposed installed)

Can't install TWRP

I can't get TWRP to install on my phone. I've tried manually fastbooting all three TWRP images that are available from the TWRP website. I tried installing TWRP using the Skipsoft Toolkit. Whatever I do I never get past the TWRP splash screen--no menus ever come up. Since no menus ever come up I can't install the TWRP zip or a custom ROM. I've been trying this for hours and it's driving me crazy. Is there a different procedure to boot into temporary TWRP if you are on the June bootloader? Is there another version of the TWRP image file that I'm missing? Am I supposed to let the TWRP sit there for a really long time? This is driving me completely batty.
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
pcriz said:
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
Click to expand...
Click to collapse
I did. Will give that a try. Thanks.
pcriz said:
Did you downgrade from O?
If that is the case you should flash the stock bootloader and boot.img into both slots on your device and try again
Click to expand...
Click to collapse
That did the trick! Thanks.
jhs39 said:
That did the trick! Thanks.
Click to expand...
Click to collapse
Np
It took way too long but I installed TWRP, flashed DU, installed ElementalEx, rooted with custom Magisk for Pixel and got the phone to pass Safety Net. Everything seems to be working. However, whenever I go into recovery TWRP doesn't seem to be there. I appear to get the stock recovery which I don't understand. I can still boot into temporary TWRP and flash the TWRP zip and flash other zips on my phone but I can't seem to boot directly into TWRP. Is this normal or did I do something wrong somewhere?
jhs39 said:
It took way too long but I installed TWRP, flashed DU, installed ElementalEx, rooted with custom Magisk for Pixel and got the phone to pass Safety Net. Everything seems to be working. However, whenever I go into recovery TWRP doesn't seem to be there. I appear to get the stock recovery which I don't understand. I can still boot into temporary TWRP and flash the TWRP zip and flash other zips on my phone but I can't seem to boot directly into TWRP. Is this normal or did I do something wrong somewhere?
Click to expand...
Click to collapse
If I recall correctly, after flashing any rom you have to flash twrp again before rebooting. Apparently roms flash an img to our recovery partition that looks similar to a modified CWM.
noidea24 said:
If I recall correctly, after flashing any rom you have to flash twrp again before rebooting. Apparently roms flash an img to our recovery partition that looks similar to a modified CWM.
Click to expand...
Click to collapse
I actually did that. Maybe I was supposed to boot into the rom once, then back into recovery to flash TWRP. There are a lot of different flashing instructions for this phone. It's hard to keep it all straight.
jhs39 said:
I actually did that. Maybe I was supposed to boot into the rom once, then back into recovery to flash TWRP. There are a lot of different flashing instructions for this phone. It's hard to keep it all straight.
Click to expand...
Click to collapse
Booting into the rom, going back into temp TWRP and flashing the TWRP zip seems to have worked --TWRP actually stuck this time and I can boot directly into it now. It's a shame Google made the Pixel XL such a headache to flash on.

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.

Flasing a Custom rom boots to recovery

HI,
Every time I flash a custom rom, it doestn't boot. it goes back to TWRP..
The only time it boots is when I flash rom with official twrp. And it boots with few things missing like magisk and other apps. Bluspark and codeworks doesn't boot.
Stock rom downloaded from oneplus also doesn't boot if the recovery is not official TWRP or the stock one..
Is there something I am missing?
Thanks...
Any ideas?
bibekdwa said:
Any ideas?
Click to expand...
Click to collapse
Try wipe data after reboot to recovery
Sent from my ONEPLUS A5010 using Tapatalk
I wiped data.. it boots.. but, without magisk. so had to flash magisk.. then, it doesn't boot..
MsuatafaKhatab said:
Try wipe data after reboot to recovery
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
bibekdwa said:
I wiped data.. it boots.. but, without magisk. so had to flash magisk.. then, it doesn't boot..
Click to expand...
Click to collapse
No problem to flash later
Sent from my ONEPLUS A5010 using Tapatalk
Did you try flashing stock ROM and the Magisk uninstall zip? This removes everything Magisk related. Then boot, only flash Magisk and see if that works for you
Macusercom said:
Did you try flashing stock ROM and the Magisk uninstall zip? This removes everything Magisk related. Then boot, only flash Magisk and see if that works for you
Click to expand...
Click to collapse
I am now back to stock OB1. Whatever custom rom I flash, it has been troublesome.
Last flash was successful, Audax rom. It had nothing missing. I flashed speaker mod, it worked. Then, I tried a custom kernel, blu-spark for nougat. it bootlooped to Qualcomm loader mode..
I have flashed many phones in the past without any problems for 4 years.. but this time it's not working for me..
Is there any 5T specific step that I am missing?
1. Unlock bootloader.
2. Flash Custom recovery. And boot it.
3. Wiped everything including internal storage.
4. Reboot to recovery.
5. Flashed Rom and then magisk and no-verity.
6. Wiped cache ( only sometimes)
7. After this step, the rom doesn't boot. It comes back to recovery using blu_spark and codeworkx... Stock twrp lets it boot but without magisk.
Then, I flashed magisk... It did the same thing, reboots to recovery.
I tried using magisk uninstaller. It didn't work.
Everytime it goes in to loop, I always had to format data because internal storage was not shown. (0mb)
I have never felt this noob...
Correct me if I'm wrong but is the no-verity zip necessary? Doesn't Magisk do that automatically? Just asking as I have stock ROM with Magisk and Xposed and never any issues.
Flash ROM and Gapps and then boot into system. After setting up, flash twrp again and Magisk. No-verity is needed only if you wanna flash certain unencrypted ROMs, in which case formatting data would also be required.
Did you do both fastboot OEM unlock, as well as enabling the option in developer options?
Macusercom said:
Correct me if I'm wrong but is the no-verity zip necessary? Doesn't Magisk do that automatically? Just asking as I have stock ROM with Magisk and Xposed and never any issues.
Click to expand...
Click to collapse
I don't know but without flashing no-verity zip, i haven't been able to boot any of these custom roms for 5t.
Flashing magisk on stock rom has also worked for me, but strangely I can't boot the custom roms on XDA. Liquid rom was successful but I wanted OOS custom roms. So far, I am unsuccessful.
Stock rom with magisk does fulfill my requirements.
But, I am curious about the problem I am having..
bibekdwa said:
I don't know but without flashing no-verity zip, i haven't been able to boot any of these custom roms for 5t.
Flashing magisk on stock rom has also worked for me, but strangely I can't boot the custom roms on XDA. Liquid rom was successful but I wanted OOS custom roms. So far, I am unsuccessful.
Stock rom with magisk does fulfill my requirements.
But, I am curious about the problem I am having..
Click to expand...
Click to collapse
exactly same situation here sir..
so many rom flashes in many htc devices and never ever had those problems
what's the missing point?
sardelisp said:
exactly same situation here sir..
so many rom flashes in many htc devices and never ever had those problems
what's the missing point?
Click to expand...
Click to collapse
I was having same issues so i flashed blu spark twrp and im golden hope this helps
forty9er said:
I was having same issues so i flashed blu spark twrp and im golden hope this helps
Click to expand...
Click to collapse
The only twrp I have tried is blu_spark anyway.

TWRP - Permanent Installation or Temp?

Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks
myk.robinson said:
Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks
Click to expand...
Click to collapse
If you only want to use TWRP when you have a fastboot-ready PC available, there is no need to install it. The reason why that is there is because since TWRP is embedded in the kernel (not flashed to a recovery partition like older devices), it will be overwritten whenever you flash a custom rom that includes a kernel, and I'm fairly certain they all do.
Returning the stock recovery menu is as easy as flashing the stock boot.img. There are no downsides that I know of of having TWRP on your device. And yes, returning to the stock rom and recovery is as easy as fastboot flashing the factory image.
myk.robinson said:
Hello -
My Pixel 2 XL is still running stock but is rooted with Magisk. I have been looking at some custom ROMs. Stock is working fine for me, but the dorm in me REALLY wants to waste time flashing ROMs...
I was looking at the thread for AquariOS and a few others, and they each mention flashing TWRP after installing the ROM.
At present, I have the .img file for TWRP and I boot to it from my computer using fastboot. Is there a reason why ROMs installation instructions have the line to install TWRP? Is there any reason not to just fastboot to it as needed? My concern is how difficult is it to return to the factory recovery mode, and is there any downside to having TWRP on this model instead of the factory. Is it possible to return to the stock ROM and recovery after installing a custom ROM?
Thanks
Click to expand...
Click to collapse
I dont install it anymore.
I run rooted stock and have no need really for a nand backup.
When I need it I just fastboot it and honestly I cant recall the last time I needed to do that.
On other deivces I have it installed for ease of updates for LineageOS.
My Pixel XL 2 swings both ways! I use TWRP on board and Fastboot!
I run stock rooted with flash kernel. I use my Nexus 6p terminal to fastboot boot TWRP on my Pixel when flash kernel pushes an update. I don't really see any reason to run a custom rom on this device as it runs great as is and there is an app for pretty much any custom rom feature you'd want.

Categories

Resources