I managed to brick my Pixel 2 XL - Google Pixel 2 Questions & Answers

I was following instructions from XDA to root my Pixel 2 XL using Magisk. At one point magisk started compaining that it needed BootBridge-SonyELF.zip in order to continue, so I downloaded it and flashed it, and from that point on my Pixel will not start up. (yeah, I know, I'm an idiot)
During normal boot, it just shoes the G logo for hours. If I try recovery, it shows the TWRP intro screen but will not continue into the TWRP menu.
I tried adb sideload to flash the taimen factory image, but I get an "error: closed" error from the sideload command.
If I run adb devices while in the TWRP intro screen, my device shows up OK, so I guess there is still some hope.
Please help!

norad73 said:
I was following instructions from XDA to root my Pixel 2 XL using Magisk. At one point magisk started compaining that it needed BootBridge-SonyELF.zip in order to continue, so I downloaded it and flashed it, and from that point on my Pixel will not start up. (yeah, I know, I'm an idiot)
During normal boot, it just shoes the G logo for hours. If I try recovery, it shows the TWRP intro screen but will not continue into the TWRP menu.
I tried adb sideload to flash the taimen factory image, but I get an "error: closed" error from the sideload command.
If I run adb devices while in the TWRP intro screen, my device shows up OK, so I guess there is still some hope.
Please help!
Click to expand...
Click to collapse
Fastboot flash stock boot image

Related

LoadImageAndAuth error, can't get into system or TWRP

I installed the Active Edge Magisk Module (from this thread) and after it rebooted it got stuck on the "Android is Updating" screen. I forced a reboot and when I got back into the system I was greeted with an impassable "System UI has stopped" (or something) dialog.
So I decided to just scrap it all and restored from a nandroid I'd made not five minutes prior. Restore successful. Rebooted, aaannnd.
ERROR: LoadImageAndAuth Failed: Load Error
I'm stuck in bootloader, unable to get into either System or TWRP. Attempting either just makes the screen go black for a sec before it spits me right back. The upside is that I can at least see it in adb.
I've found one or two other instances of the error message, but they were trying to flash the update whereas I was just flashing a Magisk module. I don't know if they're related or not.
More importantly, though — how can I fix this? Is Deuce's script my only option or is there a simpler, more painless fix?
I got this error yesterday when I tried to update to the latest January patch. I ran deuce's script to no avail but ultimately I fixed it by fastbooting TWRP and switching slots (in my case from b to a.) If I tried to boot to TWRP from booting to recovery, it always hung on the splash screen, I had to fastboot TWRP.
Sent from my Pixel 2 using Tapatalk
HELP
Hi, I got same problem here, and I have no idea what I can do now. Can you give more detail(like step by step) to show me what you did?
Spikelangelo said:
I got this error yesterday when I tried to update to the latest January patch. I ran deuce's script to no avail but ultimately I fixed it by fastbooting TWRP and switching slots (in my case from b to a.) If I tried to boot to TWRP from booting to recovery, it always hung on the splash screen, I had to fastboot TWRP.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
kongpingzi822 said:
Hi, I got same problem here, and I have no idea what I can do now. Can you give more detail(like step by step) to show me what you did?
Click to expand...
Click to collapse
It was a while ago but basically:
Boot into bootloader
Note which slot you're currently on (b or a)
Use fastboot to switch slots
Reboot bootloader to confirm (should then show opposite slot)
That did it for me
Example: if you are on slot b, enter:
Fastboot --set-active=a
Fastboot reboot-bootloader
It should now show a as active
I forget from there if I just had to reboot and all was good or if I had to reflash the factory image.
I think what ultimately caused it for me was that I was immediately flashing twrp/kernel/magisk after updating without first fully booting android so it could complete the upgrade. I'm not 100% sure though, like I said, it was a while ago.
Sent from my Pixel 2 using Tapatalk
Thanks a lot, I totally bricked my phone and nothing worked , then paid someone to fix all problems. OMG, nightmare

Can't install TWRP?

Maybe it's me not understanding what's new, I've "rooted" quite a few phones going back to the OG Droid - Motorola, Samsung, HTC. Never had any significant issue following directions and getting it done. Maybe things have changed over time. OG Pixel, 128GB, with sailfish-opr3.170623.008 (8.0.0). Auto-update disabled, USB debugging enabled, bootloader unlocked.
Setup: twrp-3.2.1-2-sailfish.img in platform-tools with adb and fastboot (latest versions). twrp-pixel-installer-sailfish-3.2.1-2.zip and Magisk-v16.0.zip at root of "Pixel/Internal Shared Storage". I also extracted a fresh boot.img from a factory image.
Just to make sure I'm starting fresh:
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot --slot other flash boot boot.img
So far so good.
Code:
fastboot boot twrp-3.2.1-2-sailfish.img
TWRP comes up, I give it my PIN, it says decrypt OK, I tell it to install twrp-pixel-installer-sailfish-3.2.1-2.zip. Install seems fine, no errors reported. Back up a couple of levels, and "reboot recovery." It tries, eventually goes to a black screen for a few seconds, then does another reboot to system. No TWRP. Am I wrong in thinking I should be in TWRP at this point?
I can do the above, but flash Magisk-v16.0.zip instead, and I do end up with root, so that works. Just no way to get to TWRP except by fastbooting an external image.
I've also tried installing VerifiedBootSigner-v8.zip after installing twrp.zip, but that fails at the end with an "unable to verify..." or similar message. I'm not sure if that's supposed to be required or not currently, the TWRP install instructions don't mention it, but other guides do.
What am I doing wrong?
All I've ever done was boot to fastboot, adb boot <path-to-twrp>.img, and flash twrp. No need to use the boot signer anymore.
Sent from my Pixel using Tapatalk
Well, I can only guess that twrp-pixel-installer-sailfish-3.2.1-2.zip isn't compatible with the boot image in sailfish-opr3.170623.008.
I installed sailfish-opm1.171019.021-factory-68d3b69a.zip, then the twrp (and Majesk) install worked, just as expected.

Root OOS 10.0.1

Hello, i was on android 10 open beta 2 with root
But while upgrading i ran into some complications and now i am on OOS 10.0.1 but dont have root
I tried to install twrp but after pushing through adb the screen says "fastboot mode" and stays there. And after typing fastboot reboot the phone reboots into home screen
I also tried to patch boot image of oos 10.0.1 but it enters into fastboot loop
Any way i can get root?
What happens when you're in fastboot and boot the twrp file?
Phantom Thief said:
What happens when you're in fastboot and boot the twrp file?
Click to expand...
Click to collapse
The whole screen turns black with the words "fastboot mode" in the center
ViperCDX said:
I tried to install twrp but after pushing through adb the screen says "fastboot mode" and stays there. And after typing fastboot reboot the phone reboots into home screen
Click to expand...
Click to collapse
Your description sounds a bit suspicious, like you aren't doing the right method. Or maybe you are not just using the right (precise) terminology. There is a lot of confusion by folks on how to boot/install TWRP properly on this device, so that is why I am pointing this out, and hope you can clarify more specifically so we can then help you.
You don't need to adb push the TWRP.img file to boot TWRP, and you don't "install" TWRP.img using fastboot either. You should be trying to fastboot boot twrp.img, with that img file on your computer.
You do need the Magisk zip on the phone (and adb push is one way); as well as the TWRP installer zip if you intend to install (not just boot) TWRP to the phone. The TWRP installer zip not completely necessary, if you want to just flash Magisk and achieve root (not have TWRP installed on the phone).
Also, are any error messages showing up on your command prompt on the computer, and if so what does it day exactly?
Might be best if you cut/paste your fastboot commands, or post a screenshot of your PC, so we can see exactly what commands you used, error messages, etc.
redpoint73 said:
Your description sounds a bit suspicious, like you aren't doing the right method. Or maybe you are not just using the right (precise) terminology. There is a lot of confusion by folks on how to boot/install TWRP properly on this device, so that is why I am pointing this out, and hope you can clarify more specifically so we can then help you.
You don't need to adb push the TWRP.img file to boot TWRP, and you don't "install" TWRP.img using fastboot either. You should be trying to fastboot boot twrp.img, with that img file on your computer.
You do need the Magisk zip on the phone (and adb push is one way); as well as the TWRP installer zip if you intend to install (not just boot) TWRP to the phone. The TWRP installer zip not completely necessary, if you want to just flash Magisk and achieve root (not have TWRP installed on the phone).
Also, are any error messages showing up on your command prompt on the computer, and if so what does it day exactly?
Might be best if you cut/paste your fastboot commands, or post a screenshot of your PC, so we can see exactly what commands you used, error messages, etc.
Click to expand...
Click to collapse
ok let me try to be as specific as possible.
First i put the "twrp-3.3.1-4-guacamole.img" file in the adb folder and "twrp-3.3.1-4-guacamole.zip" in the internal storage of my phone
Then i switched off my phone, pressed vol up and vol down and power button to enter fastboot mode
i connected my phone to my pc
opened cmd window in the adb folder
typed "fastboot devices" to check if connected
then "fastboot boot twrp-3.3.1-4-guacamole.img"
on pressing enter , i get the 2 ok messages on cmd window and at that point my phones screen goes completely black with "Fastboot mode" written in the center
And stays there that way
now if i type "fastboot reboot" the phone reboots to the home screen
Hope i made it a bit clear
Sorry cant post screenshots at this moment, i am on vacation and dont have my laptop with me
You're using the wrong twrp image. You have to use the one for android q. Unofficial build of twrp for android q is available on the development section. Get that image, fastboot boot twrp.img and then install magisk 20. You don't need to install the twrp zip. You can just boot the image from fastboot whenever you need a custom recovery.
If you absolutely want the recovery, then you can flash it (remember to get the zip for android q) from magisk and then do direct install of magisk then reboot.
kgs1992 said:
You're using the wrong twrp image. You have to use the one for android q. Unofficial build of twrp for android q is available on the development section. Get that image, fastboot boot twrp.img and then install magisk 20. You don't need to install the twrp zip. You can just boot the image from fastboot whenever you need a custom recovery.
If you absolutely want the recovery, then you can flash it (remember to get the zip for android q) from magisk and then do direct install of magisk then reboot.
Click to expand...
Click to collapse
Oh damn, didnt realise that, so silly of me
Will try the android q version and report back
ViperCDX said:
Oh damn, didnt realise that, so silly of me
Will try the android q version and report back
Click to expand...
Click to collapse
Good catch by the previous user, that you need to use an updated TWRP version.
Unofficial version -70 from the following thread is what you want (if you haven't found it already): https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
redpoint73 said:
Good catch by the previous user, that you need to use an updated TWRP version.
Unofficial version -70 from the following thread is what you want (if you haven't found it already): https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Click to expand...
Click to collapse
Yeah i pushed the .70 version through fastboot then flashed the installer
And now i have twrp
However when i try to flash magisk zip through twrp, the phone enters into fastboot mode and does not enter home screen
I have to fastboot boot image to get out of it
I have tried magisk 20.1,20 and 19.4
Kindly help
Hello guys please help me if you know what is this? What can I do? it's bug in Android 10.0.1 or something wrong that show me every minute this error?Show me in every minute this Don't want communicate with E4:5F:8D:9C:06:1A.Wait your answer,thanks.

Failed root, stuck on unlocked bootloader warning message.

Hi everyone,
I have tried to get root priviledges following a guide from Droidwin.com to flash Magisk throught TWRP. At the very last step, after flashing Magisk 19.3 throught TWRP when I tried to reboot my phone, it gets stuck on the "unlocked bootloader warning message", which is supposed to disappear after a few seconds and move on to the boot animation.
It seems like I can go to the stock recovery, which shows fastboot and wipe actions. At this point, I can acces the fastboot screen, but the device is not listed using the ADB command "adb devices", nothing is find.
I'm wondering, what can I try to restore the phone ? I thank you in advance for any suggestions.
Here are some additionnal informations:
---Device---
Oneplus nord running OxygenOS 10.5.5, european version.
---What I've done to get in this situation---
Unlock bootloader using ADB
Launch an TWRP image file using ADB
"Try" to root using Magisk 19.3 zip throught TWRP
Power off from recovery (using TWRP touch interface), but the guide tells to click reboot at this step ...
Get stuck on the warning message, not having any boot animation.
Try to boot in Fastboot.
Turn the Nord Off and start it with plus minus and Power.
Boot TWRP with "Fastboot boot "TWRP File name.img" and flash magisk 20.4
Thank you @denndenn.
I'm able to launch TWRP using the ADB command "fastboot boot [twrpfile].img". But when TWRP starts, it asks me for my decryption password, I type it, brief lines of code says "unable to read system/apex" before showing the home page of TWRP. Someone knows what this means, and if that can be the cause ?
I've then tried to reflash Magisk 19.3, which lead to the same result. I couldn't figure out how load Magisk 20.4 to my internal storage in order to flash it trought recovery ... Do you know how to flash a file which is not on my phone ?
Search forum....
Msm tool oneplus nord wipes phone but fixes any issues
thibdur said:
Thank you @denndenn.
I'm able to launch TWRP using the ADB command "fastboot boot [twrpfile].img". But when TWRP starts, it asks me for my decryption password, I type it, brief lines of code says "unable to read system/apex" before showing the home page of TWRP. Someone knows what this means, and if that can be the cause ?
I've then tried to reflash Magisk 19.3, which lead to the same result. I couldn't figure out how load Magisk 20.4 to my internal storage in order to flash it trought recovery ... Do you know how to flash a file which is not on my phone ?
Click to expand...
Click to collapse
Plug your phone to your PC while in TWRP, then you can use adb to push files to your phone, for example with adb push magisk.zip /sdcard. Then, flash Magisk in TWRP.
How about flashing stock boot to see if your OPN boots to system again and then simply load Magisk zip to your internal storage and then flash via TWRP?
Thank you a lot for your suggestions !
Here is the solution in my case :
Because fastboot was working, I was able to flash stock oxygen rom, and get every working, but it needs to erase all your data.
You can find a guide on the XDA topic "[ROM][STOCK][FASTBOOT][OPN] Stock Fastboot ROMs for OnePlus Nord". The rom list have the lastest roms version (09/2020), and the process is super automated.
Have a good week-end XDA !

Pixel 4a stuck in fastboot mode

Tried to follow this guide to root my pixel 4a and completed all steps up to 3.4. My phone is now stuck in fastboot mode and I can't get into recovery mode to do a factory reset. Not sure what to do, I'm a little lost. I accidentally used this or this image for Android 10 when I think I should have used this image for Android 11.
Any help would be very appreciated.
Maybe you can use this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
And start on this line in "First Step" section:
Plug the phone into a usb port of your pc.
Then complete all the tasks in "Second Step" section to get your phone at least booting in android 10.
ifixibrick said:
Tried to follow this guide to root my pixel 4a and completed all steps up to 3.4. My phone is now stuck in fastboot mode and I can't get into recovery mode to do a factory reset. Not sure what to do, I'm a little lost. I accidentally used this or this image for Android 10 when I think I should have used this image for Android 11.
Any help would be very appreciated.
Click to expand...
Click to collapse
Run the online flash tool from bootloader screen bro. Make sure you install adb and fastboot tools.
Raj Pandiyan said:
Run the online flash tool from bootloader screen bro. Make sure you install adb and fastboot tools.
Click to expand...
Click to collapse
How do I do that? I seem to be stuck in fastboot mode.
ifixibrick said:
How do I do that? I seem to be stuck in fastboot mode.
Click to expand...
Click to collapse
Is it bricked? Cannot flash stock Android to remove ArcaneOS
I recently purchased a used Pixel 4a, and I now understand why the seller was offering such good price for it and why he refused to respond to me now I have it. This phone has ArcanseOS 10 installed, which has only 3 apps installed... Setting...
forum.xda-developers.com
reboot to recovery, press volume up + power to bring up the recovery settings, turn on sideloading
then adb sideload the factory image.
jawz101 said:
reboot to recovery, press volume up + power to bring up the recovery settings, turn on sideloading
then adb sideload the factory image.
Click to expand...
Click to collapse
Hello. Currently stuck in fastboot mode. Using the volume buttons to select recovery mode and pressing the power button to go into it doesn't take me to recovery mode. The screen briefly goes dark before entering fastboot again. I think the phone is trying to restart but not getting past fastboot mode.
ifixibrick said:
Hello. Currently stuck in fastboot mode. Using the volume buttons to select recovery mode and pressing the power button to go into it doesn't take me to recovery mode. The screen briefly goes dark before entering fastboot again. I think the phone is trying to restart but not getting past fastboot mode.
Click to expand...
Click to collapse
Can you type fastboot reboot recovery and get into recovery mode? You'll see a little Android guy with a red thing if you're in there.
If that doesn't work- it almost sounds as though your recovery partition is deleted or something. You can reflash the recovery from fastboot.
Hey, I had the same problem. I've got it resolved now and wasn't able to find any help on how to resolve it, but this thread is as close as it came, so in the off chance that somebody else comes along, I thought I'd write up the steps I took.
Because it was in fastboot mode, I was able to easily restore my phone to factory settings by running flash factory image script I downloaded here.
My original image was sunfish-rq3a.210605.005-factory-be541467 which I followed the steps with but couldn't get it to work. I got to the Google logo with a status bar that just ran forever. But the flash-all.sh script worked to get the phone booting again.
So what I did to get Magisk to work was to use that same factory image site to download an older version. I used a version that was listed in a different root guide with the idea that maybe the version I tried before wasn't compatible with magisk, but presumably the one from the guide was. So I tried sunfish-rq1a.210105.002, ran the flash-all in fastboot, and confirmed that it booted--it did.
Next I redid 2.2 through 3 and it worked, and the boot completed with Magisk installed. Everything seems to be working fine now.

Categories

Resources