bricked my phone - Google Pixel XL Questions & Answers

Hi I have a pixel xl that I bricked. Ill give you a quick history of what I did. I had this phone rooted with magisk and on LOS and it is my backup phone that I play with. I had to send my pixel 4 xl in for a warranty exchange. So I had to use my pixel xl for a few days and I decided to return it to stock and lock the bootloader. So I did that but magisk seems to have persisted through the process of returning to stock and the phone worked fine I just got the message that the device has a different operating system installed and I still had root. Anyway I now have the pixel 5 and I was playing with my pixel and it just started boot looping and the phone gets really hot. It could just be that the hardware crapped out.
So I was able to unlock the bootloader and use fastboot to boot twrp and mount the system and I copied the twrp installer over and tried installing it. It did not work and I think i wiped out all recoveries because now when I try to boot recovery it just goes to boot the system like there is nothing there at all. Oh and I tried booting back to twrp and wiping everything. So that's where I'm at now and not sure what to try next. Do I use fastboot to boot into twrp and download the last ota file and sideload it? I'm open to any suggestions that anyone might have.

Related

bootloop issue?

Hi,
I think I have the bootloop issue. I was running purenexus marshamellow.
At first, I couldn't get past boot after many attempts,phone kept going dark. I wasn't even able to boot into bootloader. So, I removed the sim card to put in a backup phone. The next day I went to work on the phone to see what was wrong with it. Amazingly it booted up. So I connected to adb and downloaded all my personal media (adb pull). At that point I have never read about the bootloop issue, phone has been solid for a while and I don't keep up with the news. So then I decided to do a clean flash of purenexus. I noticed Nougate is available and decided to go with that.
For the most part, I can boot into bootloader without any problems now. So I flashed, the bootloader, the vendor image and radio. I went to reboot into TWRP and I got the bootloop issue. So I decided to flash the latest TWRP. Then I was able to boot into TWRP. I was able to wipe the cache/data. However, when I went to install purenexus, it would freeze and reboot. At that point I realized something is wrong and I came here. I read about the bootloop issue. So now I am wondering if I have that issue? I'm pretty certain I do, except that I can reliably boot into the bootloader. TWRP and android itself will cause reboots, but not the bootloader.
So should I send in the phone to get replaced? Or is there anything else I should try?
Also, I am halfway done towards installing purenexus, is there a way for me install in the bootloader without having to go into twrp?

New to Pixel xl (experienced rooter)

Hey guys!
I am trying to root my pixel. I have unlocked bootloader, booted device and checked usb debugging and set a pin for password. once i get to booting twrp to the pixel xl, it gets stuck, waited 5 mins or so and twrp wont boot. i have tried command prompt and Chainfires .img to try and get twrp to boot so i can flash recovery. It always get stuck at twrp screen. Phone hasnt been rooted yet . im on build NKG47L 7.1.2. Any ideas? Am i missing something??? phone bought from google...
You'll have to fastboot twrp, then install twrp... with twrp... yea.
I've been running into the same issue, and I'm on developer preview 3
Sent from my Pixel XL using XDA-Developers Legacy app
I ran into the exact same problem but it might not be for the same reason as you. I was on Android O and downgraded to Nougat. Someone suggested that I run the flash-all.bat command and flash the stock image separately to both partitions A & B. Not really understanding the partitions I don't know why that worked but right after I did it I was able to boot into fastboot TWRP immediately --and this was after hours of trying anything and everything I could think of with nothing working.
---------- Post added at 07:11 AM ---------- Previous post was at 07:10 AM ----------
madnik said:
I've been running into the same issue, and I'm on developer preview 3
Click to expand...
Click to collapse
Are you talking about Android O? I don't think TWRP works on Android O yet.
lamf2939 said:
Hey guys!
I am trying to root my pixel. I have unlocked bootloader, booted device and checked usb debugging and set a pin for password. once i get to booting twrp to the pixel xl, it gets stuck, waited 5 mins or so and twrp wont boot. i have tried command prompt and Chainfires .img to try and get twrp to boot so i can flash recovery. It always get stuck at twrp screen. Phone hasnt been rooted yet . im on build NKG47L 7.1.2. Any ideas? Am i missing something??? phone bought from google...
Click to expand...
Click to collapse
Which TWRP image are you trying to boot. I use aphla2 and it always boots right in. Maybe try a diff version to see if it works for you.
lamf2939 said:
Hey guys!
I am trying to root my pixel. I have unlocked bootloader, booted device and checked usb debugging and set a pin for password. once i get to booting twrp to the pixel xl, it gets stuck, waited 5 mins or so and twrp wont boot. i have tried command prompt and Chainfires .img to try and get twrp to boot so i can flash recovery. It always get stuck at twrp screen. Phone hasnt been rooted yet . im on build NKG47L 7.1.2. Any ideas? Am i missing something??? phone bought from google...
Click to expand...
Click to collapse
Same thing here, but i solved with update adb/fastboot at last version.
lamf2939 said:
Hey guys!
I am trying to root my pixel. I have unlocked bootloader, booted device and checked usb debugging and set a pin for password. once i get to booting twrp to the pixel xl, it gets stuck, waited 5 mins or so and twrp wont boot. i have tried command prompt and Chainfires .img to try and get twrp to boot so i can flash recovery. It always get stuck at twrp screen. Phone hasnt been rooted yet . im on build NKG47L 7.1.2. Any ideas? Am i missing something??? phone bought from google...
Click to expand...
Click to collapse
I have 7.1.2 nkg47b flashed to both slots, newest platform tools from google, issue command: fastboot boot twrp-3.0.2-0-RC1-fastboot-marlin.img and it goes right in to twrp. then from temporary twrp image, I install the twrp RC1 zip for the permanent recovery. works great for me. So, maybe make sure both slots are the same, new updated adb/fastboot tools, RC1 works better that RC2 for me, do temporary by flashing the img file, then permanent install with the zip file.
lamf2939 said:
Hey guys!
I am trying to root my pixel. I have unlocked bootloader, booted device and checked usb debugging and set a pin for password. once i get to booting twrp to the pixel xl, it gets stuck, waited 5 mins or so and twrp wont boot. i have tried command prompt and Chainfires .img to try and get twrp to boot so i can flash recovery. It always get stuck at twrp screen. Phone hasnt been rooted yet . im on build NKG47L 7.1.2. Any ideas? Am i missing something??? phone bought from google...
Click to expand...
Click to collapse
I had a similar issue the other day for no apparent reason - was getting stuck on TWRP splash screen. I switched from boot slot B to slot A and it worked after that.

various issues with google variant

I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
I haven't installed a custom ROM on my P2XL, so I'm running rooted stock. Anyway, for rooted stock, this is what I did.
Entered bootloader mode.
Booted into recovery using the command "fastboot boot recovery.img", where "recovery.img" is the TWRP recovery iteslf. In my case, I renamed it "taimen.img".
Flashed the TWRP installer zip needed for the P2XL (Required if intending to replace the stock recovery).
Rebooted into recovery.
Flashed a custom kernel (Recommended - resolves touch issues in TWRP).
Flashed Magisk.
6. Rebooted.
If installing a custom ROM, flash it prior to the custom kernel. Slots only matter if running stock. Random reboots and app crashes are not signs of a hardware issue.
stevew84 said:
I've had Google phones for years now, including previous Pixel, but I just got an XL 2 yesterday and I'm regretting it.
It's Google unlocked and running June's latest image. I've experienced various app crashing on stock, and random reboots.
Then there's the rooting and flashing. I unlocked the bootloader and installed the most recent, twrp (the one verified to work on xda for roms) but can't flash anything.
My twrp either hangs on the twrp start screen, or when it does load, the touch screen doesn't work. When I can get it going, every rom I flash gives me an error on the second step. I'm flashing on slot B by the way, that's what boots up when I boot to twrp.
Lastly, I am unlocked both for flashing and flashing_critical thru adb, so I'm at a loss and seriously confused.
When I FIRST unlocked everything, I was able to flash Nitrogen rom but I got stuck at the rom splash screen.
Tldr:
-What is the Correct install method/sequence for roms?
-do the slots matter?
-is random reboots and app crashing on stock a sign of a hardware issue?
Click to expand...
Click to collapse
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
I agree. I got it used tho which is an issue.
Badger50 said:
Ya know my friend, after our conversation yesterday, and your questions in the nitrogen thread, and now random reboots and app crashes, I think it's time to consider a factory reset. You shouldn't be having those problems on a stock setup. If that's not successful, then I would definitely consider an RMA. Just my 2 cents worth :good:
Click to expand...
Click to collapse
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
stevew84 said:
Just so you know, I got the rom to flash finally, but it's stuck at the rom splash screen during first boot. I'm going to leave it and hope it eventually boots up.
Click to expand...
Click to collapse
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Ok cool thanks. I relocked bootloader last night and went back to stock. Unlocked it all this morning from my work computer and different unlock app. So here's hoping.
Badger50 said:
If it doesn't after 5 minutes, do a hard restart with the power button. If that doesn't work, then reboot to twrp and flash the rom and twrp installer zip again.
Click to expand...
Click to collapse
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
stevew84 said:
I finally got everything to work. My vendor image is a mismatch but I could just flash junes and be done with it, right?
Click to expand...
Click to collapse
What did you do to get it to work? You could just flash the June vendor.img to both slots. If you keep getting a vendor mismatch, probably nothing to worry about according to the Dev of nitrogen.
Different machine, cable and unlocking tool.
But I went to bone stock with locked bootloader, then flashed the newest twrp with the newest all in one tool. Was on slot A so wiped everything and flashed rom plus twrp again. I rebooted system to slot B, but then it just hung at the rom splash screen.
So I did it all over on slot A, ignored the "no os installed" message and booted anyway. Then it fired up. Rebooting into twrp from there took me to B, which is where I need to be for an image file or root.
So yea, thanks for the help.
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
MatthewRobinson said:
I'm having this issue also. I tried flashing nitrogen, it hung. I tried to go back with factory reset Img and nothing happens in adb. Flashed the may img and it wouldn't boot all the way up. Now I'm stuck in bootloader trying to figure this all out. Seems like nothing in doing is working. I can get recovery to boot, but no files inside so idk. Tried to sideloadb nitrogen, but it said adb out of date for device when sdk is fully updated.
Click to expand...
Click to collapse
You didn't mention the out of date message in your other post, but uninstall SDK and then download the stand-alone adb/fastboot binaries from May of this year. Dump that in a folder (eg. c:\adb) and put that folder in your path statement. Manually flash the full factory image without modifying flash-all.bat. Post your screeen if you have any errors. :good:
stevew84 said:
I agree. I got it used tho which is an issue.
Click to expand...
Click to collapse
Google knows the date the phone was purchased based on imei number and honors their warranty by date, not owner. Unless it was blacklisted.
smartymcfly said:
Google knows the date the phone was purchased based on imei number and honors their warranty based on that.
Click to expand...
Click to collapse
Thanks. I might try to take advantage.

pixel xl stuck in bootloop after trying to install twrp!

Someone please help me, im really worried i bricked my new phone. I just got this phone about two weeks ago.
So i unlocked my bootloader a few days ago and now since its the weekend i decided i would try to do some more modding with my phone. Well i followed all instructions to the T and now im stuck in a bootloop and not able to access recovery mode. Im worried that when it does run out of battery, which is going to take forever. That as soon as i give it power it will go back into the bootloop. Someone please give me some advice on how to alleviate this issue.
Did you relock the bootloader ?
no i didnt. i was able to get the phone to turn off by holding the power button down for a longtime. so i got it figured out. still would like to install twrp but now im kinda freaked out lol.
Get the SDK tools, download twrp for marlin and the zip, boot to bootloader, fastboot twrp, move the installer zip to the phone, flash it like normal in twrp
Oh yeah good point. Do not flash TWRP in fastboot, you have to fastboot boot into TWRP. And flash TWRP from within itself (TWRP recovery)
okay yeah ive been having a hell of a time trying to get twrp installed i just cant get it going. how do you fastboot twrp?
Go to this thread: [Guide] Pixel XL Android 8.1.0 (OREO) Unlock/Lock Bootloader + Install Stock Images/Custom kernels/TWRP Recovery/Systemless ROOT + June Security Patch
Do #4 then #7.
I've had some boothangs - not loops, but I'm wondering if it might be related to disabling the rapid charge? I keep seeing this repeated in the logcat when it's frozen"
06-27 09:31:54.937 695 695 W /system/bin/thermalserviced: Waited one second for [email protected]::IThermal/default. Waiting another...
06-27 09:31:55.512 1156 1156 W zygote64: Waited one second for [email protected]::IThermal/default. Waiting another...
Click to expand...
Click to collapse
The mentioning of the thermal makes me think of a possible relationship to heat and rapid charging... but I'm no engineer.
I encountered this problem after messing with my hosts file and thought I would post my solution even though this was for the pixel 2 just in case anyone else is searching for the same problem. To get it to boot again I flashed the factory boot image in fastboot. I then patched the factory boot image with magisk manager and manually flashed this in fastboot. The phone then booted up fine. This still happens occasionally on reboot when I make changes, but repeating the process gets it to boot up again.

not booting into twrp via phone controls

I bought a used Pixel XL in canada for my dad. Unlocking bootloader, flashing twrp and root were super simple. But when I purchased another Canadian Pixel XL for my mum. I was a little puzzled. Bootloader is successfully unlocked. And successfully flashed twrp 3.2.3 and was able to navigate through it. But when the phone boots to system and then I try to boot into recovery. It tries to and the phone just restarts to system. Another strange thing is that I have slot a and b in twrp 3.2.3 whereas my dad's phone doesn't have the slots since it launched with nougat. Mum's pixel is currently on 8.0 out of the box.
It can boot into twrp via computer. But when I try rebooting into twrp via twrp it just restarts the phone to system
The phone also shows as aosp on msm8669 when connected to my pc. Googled it and says Verizon. But it was bought in Canada best buy...
I can definitely return the phone after relocking the bootloader but just wondering if there's a fix for this.
Edit. Updated to pie via ota and twrp boots with no issues

Categories

Resources