Woke up this morning and phone stuck on animation screen. I can boot into bootloader and select recovery but TWRP does not load. It only just cycles through the boot animation. I tried re-flashing TWRP with fastboot and it said it was successful but will still not boot recovery. It just cycles through the boot animation screen.
Any ideas? Any way to save photos? I can only use fastboot and not adb I assume.
This is a XT1254
Raistlen0 said:
Woke up this morning and phone stuck on animation screen. I can boot into bootloader and select recovery but TWRP does not load. It only just cycles through the boot animation. I tried re-flashing TWRP with fastboot and it said it was successful but will still not boot recovery. It just cycles through the boot animation screen.
Any ideas? Any way to save photos? I can only use fastboot and not adb I assume.
Click to expand...
Click to collapse
Try booting from TWRP loaded on your PC.
fastboot boot TWRP.img (where "TWRP" is whatever you have named your copy of TWRP in your ADB folder).
You can actually boot to TWRP this way without even installing TWRP. Think of it as "temporary" TWRP. I've done it to make a copy of an stock firmware image where stock recovery is still installed.
Thanks. Looks like phone got wet somehow. After dryng out it will boot into recovery but it says no OS present and shows the SD card empty except for a twrp folder. Guess i will have to reimage ROM and see what happens.
same issue, where you using LOS 7 ?
Was running LOS 7, and suddenly one day was stuck on bootloop.
TWRP loaded once tried to reflash LOS with the existuing files in the user download, but after reboot then no TWRP
Further attempts to install TWRP with no sucees, also noyticed cache fs was not posible to mount/clear, attempted to clear the other fs and now none loads
The suggested hardbrick solution from https://forum.xda-developers.com/moto-maxx/general/tuto-unbrick-xt1225-100-t3483623 fails when loading any version of gpt
C:\MAXX-Unbrick Kit2\2.Unbrick>mfastboot.exe flash partition gpt6s1.bin
< waiting for device >
sending 'partition' (32 KB)...
OKAY [ 0.235s]
writing 'partition'...
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.626s
Click to expand...
Click to collapse
From what I read i need to flash the same gpt but no idea how to get it.
Also fastboot commands seems to work but not the adb nor the RSD lite
Raistlen0 said:
Any ideas? Any way to save photos? I can only use fastboot and not adb I assume.
This is a XT1254
Click to expand...
Click to collapse
Go to https://photos.google.com/. Your photos may already by there. In some countries like U.S. all your photos are automatically backed up if you give the app permission. I set it to back up when I'm on my home wi-fi network. I also have automatic picture back up with Dropbox and Amazon Prime photos.
You can also choose which folders the apps pull photos from -- not just the "camera" folders, but even Download, WhatsApp, and others if you wish.
Raistlen0 said:
Thanks. Looks like phone got wet somehow. After dryng out it will boot into recovery but it says no OS present and shows the SD card empty except for a twrp folder. Guess i will have to reimage ROM and see what happens.
Click to expand...
Click to collapse
Were you able to reimage it, for mine it was not possible, I kept focused on the corrupted got.bin, but then looked it even further, and seems eMMC corruption.
Any gas that I wrote on it got damaged, even the bootlogo is corrupted now ( showing only half of it, replacing it completes but still showing old image) it is a shame as camera/screen worked great, but without adding, there is not really much that can be done.
If your target is to recover the data, by all means do not try to reimage it, boot into recovery and try mounting the data partition, once done you can either transfer your files using ADB, or by mounting a thumb drive with an org adapter and copy them from terminal emulator on the TWRP
Related
Hey guys, love all the work that goes on in this forum.
I've run into a bit of a problem. My mate gave me his phone to try and fix after he interrupted a factory reset. It's stuck in a bootloop.
It's a RAZR HD and was originally from Telstra (Aus).
I've managed to unlock the bootloader, but quickly after that everything has gone to hell.
When I turn the phone on, it gives the bootloader is unlocked message. Then the android installation guy comes up and after about 5 seconds of trying to install the phone bootloops.
I am able to enter the Android System Recovery (3e) and have done factory reset/wipe data and wipe cache options, however does not change anything. When I press reboot system, the bootloop continues as if I did nothing. I have tried installing a ROM from an SD card however it fails at the Verifying Package stage. I am unable to adb push anything as usb debugging wasn't turned on.
I am able to enter into fastboot and can see my device however cannot flash any images from there for some reason using the fastboot commands (it comes up with a <bootloader> variable not supported! error: cannot load '[name of image file]'
I was able to use RSD Lite to flash the official Telstra ROM to the phone, however at the very end of the installation when it rebooted, it just went into the bootloop again.
Any help would be muchly appreciated.
Thanks guys!
Anyone?
I was able to get adb sideload to work (I had the wrong path name to the zip file) but still no luck...
piCARSO said:
Anyone?
I was able to get adb sideload to work (I had the wrong path name to the zip file) but still no luck...
Click to expand...
Click to collapse
try mfastboot and flash the partition table first, if that fails, there is no hope of saving the device. if it passes, flash the rest of the files, including the wipe command.
bweN diorD said:
try mfastboot and flash the partition table first, if that fails, there is no hope of saving the device. if it passes, flash the rest of the files, including the wipe command.
Click to expand...
Click to collapse
Thanks for the reply. When you say flash the partition table first, would that be the partition_signed file (aka mfastboot flash partition partition_signed)?
piCARSO said:
Thanks for the reply. When you say flash the partition table first, would that be the partition_signed file (aka mfastboot flash partition partition_signed)?
Click to expand...
Click to collapse
yes, thats correct.
Good day, its my first thread here, so I'm sorry for my english and terminology.
My Photon Q had CM-13-Nightly installed, bootloader unlocked and Clockwork recovery installed. Everything was working fine, till few days ago. Phone was left unused with drained battery, so I charged it and powerd on. After that, all app started to crash one after another. I was trying to do factory reset from recovery, erase everything from bootloader menu or using bootloader commands (bootloader erase data, bootloader -w) but nothing worked. I still have my system, with same apps, wallpaper etc and apps still crash. Are these all symptoms of damaged partition or internal storage? Will be thankful for any help
Erasing in bootloader/fastboot mode can be dangerous... be careful.
I would just factory reset and reinstall the ROM. Don't use ClockworkMod for recovery tho, use TWRP. CWM hasn't had updates in a long time (and frankly I'm surprised it was able to flash the latest CM).
I have tried to change recovery, but it was also impossible. I also tried to wipe data / factory reset, after that flashed new Rom but nothing changed. Still all my apps and settings remains. There is one more thing to add, that I can copy file from device when connected to my laptop, but cannot delete anything. Anyway, how to change recovery? Phone doesn't keep any changes for example adb debugging in developer options. CWM update is turned off, but cannot change recovery
greedo85 said:
I have tried to change recovery, but it was also impossible. I also tried to wipe data / factory reset, after that flashed new Rom but nothing changed. Still all my apps and settings remains. There is one more thing to add, that I can copy file from device when connected to my laptop, but cannot delete anything. Anyway, how to change recovery? Phone doesn't keep any changes for example adb debugging in developer options. CWM update is turned off, but cannot change recovery
Click to expand...
Click to collapse
Boot to fastboot/bootloader mode, 'fastboot flash recovery twrp.img' assuming twrp.img is in the location you are running fastboot flash from...
How did you flash CWM recovery in the first place?
I have bought this phone with Cyanogen Recovery and Custom ROM flashed already. I tried what You posted, it shows that TWRP is flashed, but when I enter recovery again, I still have Cyanogen. I tried with 3 different versions of TWRP downloaded for Photon Q... I also don't know what does it mean "(bootloader) Variable not supported!"
HTML:
C:\fastboot>fastboot flash recovery twrp-2.3.0.0-asanti_c.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6702 KB)...
OKAY [ 0.512s]
writing 'recovery'...
OKAY [ 1.786s]
finished. total time: 2.298s
arrrghhh said:
Boot to fastboot/bootloader mode, 'fastboot flash recovery twrp.img' assuming twrp.img is in the location you are running fastboot flash from...
How did you flash CWM recovery in the first place?
Click to expand...
Click to collapse
greedo85 said:
I have bought this phone with Cyanogen Recovery and Custom ROM flashed already. I tried what You posted, it shows that TWRP is flashed, but when I enter recovery again, I still have Cyanogen. I tried with 3 different versions of TWRP downloaded for Photon Q... I also don't know what does it mean "(bootloader) Variable not supported!"
Click to expand...
Click to collapse
I think you can safely ignore the bootloader message.
As for flashing TWRP, did you boot TWRP immediately after flashing, or did you boot Android?
I believe you need to make sure you boot TWRP immediately after flashing, otherwise CM Recovery will blow it out.
After flashing TWRP hold power until the device shuts off, release, and now hold power + vol down to enter recovery. Please use the latest version of TWRP from kabaldan, or the latest official TWRP.
I did exactly as You have posted. Still Cyanogen :/ I got recovery from here: https://dl.twrp.me/asanti/twrp-3.0.2-0-asanti_c.img.html , its the newest I think
greedo85 said:
I did exactly as You have posted. Still Cyanogen :/ I got recovery from here: https://dl.twrp.me/asanti/twrp-3.0.2-0-asanti_c.img.html , its the newest I think
Click to expand...
Click to collapse
Sorry it's power + vol UP (according to my own guide...)
3. Hit power - device turns off. Hold vol up + power, then release power when the screen comes on - continue holding vol up. When you see the moto logo dim a bit, release vol up. You should now be in TWRP!
Did that - Cyanogen again :/ Have any idea why is that happening? Internal memory broke down?
greedo85 said:
Did that - Cyanogen again :/ Have any idea why is that happening? Internal memory broke down?
Click to expand...
Click to collapse
I'm not sure why people have issues with this... I always thought it was how they 'completed' the flashing process. I don't recall being able to reproduce the condition.
Perhaps boot Android then boot TWRP? Or try to reboot directly to recovery from the fastboot cli? Try something different... or just fastboot boot the TWRP image? There is a problem in the process, I'm just not sure 'where' since I don't have the phone in front of me.
Already done that, before I started this thread... Nothing works. I have tried multiple combination, such as reboot to this (I don't know how to name it, B&W menu with APfastboot, recovery etc), boot system first than recovery, boot directly to recovery after flashing new one etc. Are there any fastboot commands, that I could use to forcefully erase recovery or data? You sure that it's not physical damage of internal memory?
greedo85 said:
Already done that, before I started this thread... Nothing works. I have tried multiple combination, such as reboot to this (I don't know how to name it, B&W menu with APfastboot, recovery etc), boot system first than recovery, boot directly to recovery after flashing new one etc. Are there any fastboot commands, that I could use to forcefully erase recovery or data? You sure that it's not physical damage of internal memory?
Click to expand...
Click to collapse
IIRC this device will let you 'fastboot boot' images directly - I think I suggested this - have you tried it?
I'll dig around and see what else I can find from the TWRP thread. I was pretty sure it had to do with the process, but I could be mistaken.
Edit - I'll flash CM Recovery on my old Q and see if I can recreate this as well. It's always bothered me...
How would I boot images directly? From where?
greedo85 said:
How would I boot images directly? From where?
Click to expand...
Click to collapse
Just like you fastboot flash them, but 'fastboot boot <imagefilename>"...
arrrghhh said:
Just like you fastboot flash them, but 'fastboot boot <imagefilename>"...
Click to expand...
Click to collapse
Did You mean this? Why is Command restricted?
Code:
C:\fastboot>fastboot boot twrp-3.0.2-0-asanti_c.img
downloading 'boot.img'...
OKAY [ 0.674s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.770s
greedo85 said:
Did You mean this? Why is Command restricted?
Code:
C:\fastboot>fastboot boot twrp-3.0.2-0-asanti_c.img
downloading 'boot.img'...
OKAY [ 0.674s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 0.770s
Click to expand...
Click to collapse
I guess they only allow fastboot booting kernels... at least I used to do that on this device.
So I just flashed CM Recovery no problem. Going to flash back TWRP.
Is there anything I can do now to put this phone back to work?
greedo85 said:
Is there anything I can do now to put this phone back to work?
Click to expand...
Click to collapse
I'm... kind of at a loss. Make sure you have the latest TWRP. I just downloaded the latest CM Recovery, fastboot flash recovery <cmrecimg> and it rebooted to Android on its own. I reboot to recovery, CM Recovery is installed. All good.
I reboot to bootloader mode, grab the latest official TWRP, fastboot flash recovery <twrpimg>, this time when I unplugged it was still in fastboot mode. So I hit the power button, phone turns off. Then I hold power + vol up until I see the screen turn on. Continue to hold vol up, but release power. Then when the screen dims (or when recovery starts if you can't tell) release vol up.
Maybe that'll help you? Good luck.
Did exactly the same procedure as You described. Still Cyanogen. I can even record it and send here...
Could You please send me a link where I can find another TWRP ( You mentioned some developer few posts above, I guess), differend that I have found?
greedo85 said:
Did exactly the same procedure as You described. Still Cyanogen. I can even record it and send here...
Could You please send me a link where I can find another TWRP ( You mentioned some developer few posts above, I guess), differend that I have found?
Click to expand...
Click to collapse
Dunno why it would make any difference at this point, but have at it.
so im having a issue attemping to root my verizion variant google pixel. ive been successful in getting the device a unlocked boot loader but now the issue i am running into in the recovery. Secondly when i go to reboot the phone after flashing the recovery as failed the loading screen goes on for hours with no change. This is what im running currently.\
C:\adb>fastboot flash recovery twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (9434 KB)...
OKAY [ 0.330s]
writing 'recovery'...
(bootloader) Flashing active slot "_b"
FAILED (remote: partition [recovery] doesn't exist)
finished. total time: 0.435s
That is what i get as a responce. any help would be a great help. Those that can assist me in the matter im willing to sent some BTC your way. Thanks in advance. ive also tried to go the boot-to-root method and i get the same effect of the phone being stuck at the loading screen.
Why are you not reading in the other section where this is posted. Mods, roms, etc. It is known that recovery partition is gone, it's part of boot. There is TWRP alpha2 thread that works on Pixel and instructions. SuperSU 2.78 SR4 works as well.
I suggest you do reading first to understand how the new partitions work before you start moding. Pixel has 2 system, 2 boot partitions.
milan187 said:
Why are you not reading in the other section where this is posted. Mods, roms, etc. It is known that recovery partition is gone, it's part of boot. There is TWRP alpha2 thread that works on Pixel and instructions. SuperSU 2.78 SR4 works as well.
I suggest you do reading first to understand how the new partitions work before you start moding. Pixel has 2 system, 2 boot partitions.
Click to expand...
Click to collapse
is there any link that you can reference? thanks in advance.
http://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/page10
First thing you're doing wrong is flashing the boot image you're supposed to be booting the boot image.
jayfried said:
http://forum.xda-developers.com/pixel/development/twrp-alpha1-pixel-devices-t3500314/page10
First thing you're doing wrong is flashing the boot image you're supposed to be booting the boot image.
Click to expand...
Click to collapse
i have isolated what i think is the root of the issue.
First, i can't do a normal boot up on the phone is stays at the google load screen with the four dots that shift left and right.
Second i try and use adb push and i can't get the files on the phone and I'm stuck in fast boot. (adb devices shows nothing and fast boot devices shows the phone)
my theory is that i need the zip on the phone and it would have what it needs to run.
Any help on the matter would be of great help.
There are 2 files for twrp, an image file which you put with your adb and fastboot tools and a zip file that goes on your phone which you can put on there one you fastboot "BOOT" the image file. fastboot boot of the twrp.img file will boot the phone to recover but it doesn't install the recovery you have to at this point install the zip file which can be put on the phone as it's file system should be mounted and installed From twrp. As you are not able to boot the phone right now I recommend starting over with a fresh install of Google factory image.
This is the first thing you should do if you haven't already: http://forum.xda-developers.com/showthread.php?t=2588979&page=93
Make sure to install it system wide so you can run the adb and fastboot from any directory on your computer. Then this:
https://developers.google.com/android/images
1.Download and unzip the correct file which would probably be in NDE63V
2. Put phone in bootloader mode and run the flash all batch file, boot it and set up phone
3. Put the zip files on the phone for twrp and root and enable USB debug
4. Back to bootloader and fastboot boot the twrp image
5. Once booted in twrp install the zip for twrp and reboot to recovery from the reboot tab
6. Once back in the recover which is now installed install the zip for root then reboot system and rejoice
---------- Post added at 09:14 PM ---------- Previous post was at 08:56 PM ----------
Sorry for all the edits
jstorms1991 said:
i have isolated what i think is the root of the issue.
First, i can't do a normal boot up on the phone is stays at the google load screen with the four dots that shift left and right.
Second i try and use adb push and i can't get the files on the phone and I'm stuck in fast boot. (adb devices shows nothing and fast boot devices shows the phone)
my theory is that i need the zip on the phone and it would have what it needs to run.
Any help on the matter would be of great help.
Click to expand...
Click to collapse
Did you enable adb debugging? Honestly, just following the instructions works great. No theories needed.
Use flashall from Google of you are stuck to go back to stock, then start over.
Also look here, it's from XL but applies.
Do your research before messing around.
https://r.tapatalk.com/shareLink?ur...share_tid=3494478&share_fid=3793&share_type=t
[GUIDE] Restore to stock after soft bricking. Then install TWRP, Root & Custom Kernel
I would REALLY appreciate help if possible. I'm trying to recover my honeymoon pictures from a Pixel that freezes as soon as it boots.
It has the locked, original bootloader, but debugging is enabled. Sailfish Oreo 8.1.0/OPM1.171019.012/4470837 installed.
I thought after enabling debug that I could adb shell or adb pull files in recovery mode, but I can't figure out how (assuming it's possible). I can boot into "no command" recovery, and get into the Android Recovery menu with "Apply update from ADB", "Mount /system", etc. I've even upgraded the OS with adb sideload successfully...
But booting into Android, it freezes almost always on the "G" loading screen...but rarely, it will display the clock and notifications and immediately freeze. Even more rarely (like once in a thousand boots), it will give me maybe 10 seconds before it freezes. The last time it did this, I had just enough time to enable dev options, enable debugging, and "always enable with this computer"...then it froze.
What are my options or the most likely way to recover my files? Is there anything I can do from recovery, or if I get another 10 seconds in Android, is there anything I should try?
Fastboot boot into twrp and then using adb pull grab your entire pictures directory.
Also booting into twrp and doing a factory wipe should fix the bootloop I had this happen this morning
KittyRgnarok said:
Fastboot boot into twrp and then using adb pull grab your entire pictures directory.
Also booting into twrp and doing a factory wipe should fix the bootloop I had this happen this morning
Click to expand...
Click to collapse
Thanks for the suggestion! I'll try this tonight, but I worry it won't work since my bootloader is the original and locked. If I understand correctly:
- you need an unlocked bootloader to do "fastboot boot"
- you have to factory reset and wipe all your files to unlock the bootloader
Is that not true?
Yes, it looks like I can't "fastboot boot" because it's not unlocked. Everything I've found says unlocking should wipe my device.
Is there any way to boot an img or get to adb shell/pull without wiping it?
Code:
>>> fastboot boot twrp-3.2.1-0-sailfish.img
downloading 'boot.img'...
OKAY [ 0.868s]
booting...
(bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote failure)
finished. total time: 0.967s
Oh yeah I forgot about that. Uhhhhh no I think ur boned sorry
are you sure you did not have google photos automatically backing up your photos?
mruno said:
are you sure you did not have google photos automatically backing up your photos?
Click to expand...
Click to collapse
Yes, I'm sure. I was away from any connection on my honeymoon and it crashed right before coming home.
If your phone is under warranty still you can likely RMA it to get a phone that isn't bootstuck but as far as the data I think it's pretty safe to say you can't access it unless you have already disabled forced full disk encryption prior(which I'm not even sure is safe to do on these devices).
Hi,
I am incredibly new to this and I think I might have managed to destroy this google pixel I just bought. I had attempted to root the phone using magisk after unlocking the bootloader and installing TWRP though I had a little bit of trouble, I was following instructions here https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/. I managed to unlock the bootloader but after signing in to the phone again and attempting to install TWRP to get magisk It wouldn't let me access most of my downloads on the phone because TWRP was asking for a password for my user. I tried the passcode I had set but I didn't work I tried rebooting the phone and removing the lock but many apps on the phone once I booted it back no longer worked, specifically settings which is how I was planning on removing the password. I also tried using adb commands to wipe the lock but nothing really seemed to be working so I found a factory reset setting on TWRP and now I have been stuck at the google reset screen for about 5 hours now. Any help is appreciated.
Thanks
ajg32 said:
Hi,
I am incredibly new to this and I think I might have managed to destroy this google pixel I just bought. I had attempted to root the phone using magisk after unlocking the bootloader and installing TWRP though I had a little bit of trouble, I was following instructions here https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/. I managed to unlock the bootloader but after signing in to the phone again and attempting to install TWRP to get magisk It wouldn't let me access most of my downloads on the phone because TWRP was asking for a password for my user. I tried the passcode I had set but I didn't work I tried rebooting the phone and removing the lock but many apps on the phone once I booted it back no longer worked, specifically settings which is how I was planning on removing the password. I also tried using adb commands to wipe the lock but nothing really seemed to be working so I found a factory reset setting on TWRP and now I have been stuck at the google reset screen for about 5 hours now. Any help is appreciated.
Thanks
Click to expand...
Click to collapse
What do you mean by "remove the lock" and "wipe the lock"? If you relocked the bootloader, your recovery options are limited. Can you access the phone with adb and/or fastboot? If the bootloader is still unlocked, flash a stock factory image available at https://developers.google.com/android/images. Instructions for flashing are at that URL.
If your bootloader is now locked, can you get to fastboot? If not, I don't know of anything you can do. If you can get to fastboot, you can try to sideload a full OTA image from https://developers.google.com/android/ota. Instructions are at that URL.
If you can recover, forget rooting with TWRP - those instructions are outdated. Just install the Magisk app, and use it to patch boot.img, then flash the patched boot.img. If you need TWRP for other purposes, do not install it, just boot it with "fastboot boot twrp.img".
Never lock the bootloader unless you have a completely stock device. Even then, you risk bricking the phone.
dcarvil said:
What do you mean by "remove the lock" and "wipe the lock"? If you relocked the bootloader, your recovery options are limited. Can you access the phone with adb and/or fastboot? If the bootloader is still unlocked, flash a stock factory image available at https://developers.google.com/android/images. Instructions for flashing are at that URL.
If your bootloader is now locked, can you get to fastboot? If not, I don't know of anything you can do. If you can get to fastboot, you can try to sideload a full OTA image from https://developers.google.com/android/ota. Instructions are at that URL.
If you can recover, forget rooting with TWRP - those instructions are outdated. Just install the Magisk app, and use it to patch boot.img, then flash the patched boot.img. If you need TWRP for other purposes, do not install it, just boot it with "fastboot boot twrp.img".
Never lock the bootloader unless you have a completely stock device. Even then, you risk bricking the phone.
Click to expand...
Click to collapse
Sorry for the lack of clarity. The bootloader was still unlocked I was simply trying to access files in the TWRP menu but I had to enter the pin I put on the phone. When I mentioned that I was trying to remove the lock it was so that I could use the file manager to install through the TWRP menu. I believe the bootloader is still unlocked but I simply cannot really communicate with the phone. It is on, but its suck on a google logo with a loading bar. Aside from adb commands which don't seem to be working as the phone is not being detected Is there any sort of combination of clicking the power button or something similar that may shake the phone out of the resetting loop?
ajg32 said:
Sorry for the lack of clarity. The bootloader was still unlocked I was simply trying to access files in the TWRP menu but I had to enter the pin I put on the phone. When I mentioned that I was trying to remove the lock it was so that I could use the file manager to install through the TWRP menu. I believe the bootloader is still unlocked but I simply cannot really communicate with the phone. It is on, but its suck on a google logo with a loading bar. Aside from adb commands which don't seem to be working as the phone is not being detected Is there any sort of combination of clicking the power button or something similar that may shake the phone out of the resetting loop?
Click to expand...
Click to collapse
Try these instructions - https://www.hardreset.info/devices/google/google-pixel-3/fastboot-mode/
If you can get to fastboot mode, flash a stock image from the URL in my previous post.
If that does not work, google "plxel 3 recovery mode" or "pixel 3 fastboot mode" to try to find something that works. If you can get to fastboot mode, you have a good chance of recovering the phone. Don't try to do anything with TWRP.
dcarvil said:
Try these instructions - https://www.hardreset.info/devices/google/google-pixel-3/fastboot-mode/
If you can get to fastboot mode, flash a stock image from the URL in my previous post.
If that does not work, google "plxel 3 recovery mode" or "pixel 3 fastboot mode" to try to find something that works. If you can get to fastboot mode, you have a good chance of recovering the phone. Don't try to do anything with TWRP.
Click to expand...
Click to collapse
Thank you very much for all the help, I managed to restore the phone pre-TWRP mess. You mentioned rooting by only installing magisk. Would that method be similar to the one described here https://www.rootdroids.com/guides/how-to-root-google-pixel-3-with-magisk-without-twrp/?
ajg32 said:
Thank you very much for all the help, I managed to restore the phone pre-TWRP mess. You mentioned rooting by only installing magisk. Would that method be similar to the one described here https://www.rootdroids.com/guides/how-to-root-google-pixel-3-with-magisk-without-twrp/?
Click to expand...
Click to collapse
Yes, that is the method. Those instructions don't really tell you how to get boot.img though. Unzip the factory image you downloaded. Inside that zip is another zip. Unzip that second zip and boot.img will be extracted.
dcarvil said:
Yes, that is the method. Those instructions don't really tell you how to get boot.img though. Unzip the factory image you downloaded. Inside that zip is another zip. Unzip that second zip and boot.img will be extracted.
Click to expand...
Click to collapse
I believe I got the correct boot.img although now when I try to flash boot the patched img file I get an error. Specifically,
Warning: skip copying boot_a image avb footer (boot_a partition size: 67108864, boot_a image size: 100663296).
Sending 'boot_a' (98304 KB) OKAY [ 2.286s]
Writing 'boot_a' (bootloader) Image missing cmdline or OS version
FAILED (remote: 'Failed to write to partition Bad Buffer Size')
fastboot: error: Command failed
Looking it up it seems like the most common fix is to boot from TWRP
ajg32 said:
I believe I got the correct boot.img although now when I try to flash boot the patched img file I get an error. Specifically,
Warning: skip copying boot_a image avb footer (boot_a partition size: 67108864, boot_a image size: 100663296).
Sending 'boot_a' (98304 KB) OKAY [ 2.286s]
Writing 'boot_a' (bootloader) Image missing cmdline or OS version
FAILED (remote: 'Failed to write to partition Bad Buffer Size')
fastboot: error: Command failed
Looking it up it seems like the most common fix is to boot from TWRP
Click to expand...
Click to collapse
"boot_a image size: 100663296" is the wrong size. How are you transferring boot.img and the patched image between your phone and PC? You should be using adb push/pull. If you did use adb push/pull, I'd need to see all the commands you used, and a directory listing of all the files to see if I can spot something wrong. Also, what version of Magisk?
You could try renaming magisk.apk to magisk.zip and installing the zip with TWRP, but I don't know if that method still works on the Pixel 3. I've never tried that method. Make sure you just boot TWRP (fastboot boot twrp.img), and do not install TWRP. If that breaks things, at least you know how to recover now.