Related
Let me start off by saying that I just got this phone and decided to install a custom recovery and rom on it. As I do with all my phones that allow me to do so. I got the phone with android 4.4.4 on it, rooted it with Kingroot, and proceeded to use the XZDualrecovery tool to install TWRP. After that was all done, I downloaded the Z5 Expierience Rom, and I'm going to take a long shot here and say that I must have majorly missed something. Because after flashing that Rom in TWRP, my phone will do next to nothing. All went fine with the install of the ROM itself. Wiped Dalvik/Cache before restart.
If i hold down the power button I get a single vibration and then the phone does nothing (Does not even turn on backlight). If I plug the phone into my computer the phone will start a sequence of Red (LED), Green (LED), Vibrate. It does this aobut once every second. I can access Fastboot if I hold the volume + button, the LED then goes solid blue and the phone stops the LED - Vibration sequence. The only problem I have, as far as just not being able to Flashtool it back to life is, not being able to get the phone to go into Flashmode. No matter what I do, the phone will not let me get it into Flashmode. Im sure there is a good reason for this, I am just not sure what it is.
I've been flashing Roms and Recoveries since G1 days. I'm usually pretty decent at figuring this kind of thing out, but this thing has got me puzzled. I clearly went terribly wrong somewhere here, hopefully someone who knows this phone much better than I can point me in the right direction and hopefully get my less than 10 hour phone working again.
P.S. - If the phone is plugged into the wallcharger is does something similar to when it is plugged into my computer, but instead of a Sequence of Red - Green - Vibrate, I just get a steady red blink folled by a vibration. The phone will continue to do so until unplugged from the charger.
All help is very appreaciated!
I'm having the same issue. Anyone with the fix would be appreciated
Not sure what to try at this point!
I've been looking non-stop in my free time for a fix for this thing, and no matter what I do I keep getting the same results. Not really sure where to go from here, I have tried Flashtool, Emma, and PC Compainion out of desperaity. I tried all three options on teo seperate computers (One Windows 10 and the other Windows 7.) I have also tried multiple cables. No matter what I do all this thing will do is blink at me and vibrate. Is this thing hard bricked? I read its close to impossible to hard brick one of these phones. I'm wiling to accept that I have if that is the case. Just would like an opinion from someone who has some knowledge with these.
Same here, someone plz help.
If is only a change of batery or the phone is dead completly, an the stop trying to revive it.
Thanks .
Nick1801 said:
Let me start off by saying that I just got this phone and decided to install a custom recovery and rom on it. As I do with all my phones that allow me to do so. I got the phone with android 4.4.4 on it, rooted it with Kingroot, and proceeded to use the XZDualrecovery tool to install TWRP. After that was all done, I downloaded the Z5 Expierience Rom, and I'm going to take a long shot here and say that I must have majorly missed something. Because after flashing that Rom in TWRP, my phone will do next to nothing. All went fine with the install of the ROM itself. Wiped Dalvik/Cache before restart.
If i hold down the power button I get a single vibration and then the phone does nothing (Does not even turn on backlight). If I plug the phone into my computer the phone will start a sequence of Red (LED), Green (LED), Vibrate. It does this aobut once every second. I can access Fastboot if I hold the volume + button, the LED then goes solid blue and the phone stops the LED - Vibration sequence. The only problem I have, as far as just not being able to Flashtool it back to life is, not being able to get the phone to go into Flashmode. No matter what I do, the phone will not let me get it into Flashmode. Im sure there is a good reason for this, I am just not sure what it is.
I've been flashing Roms and Recoveries since G1 days. I'm usually pretty decent at figuring this kind of thing out, but this thing has got me puzzled. I clearly went terribly wrong somewhere here, hopefully someone who knows this phone much better than I can point me in the right direction and hopefully get my less than 10 hour phone working again.
P.S. - If the phone is plugged into the wallcharger is does something similar to when it is plugged into my computer, but instead of a Sequence of Red - Green - Vibrate, I just get a steady red blink folled by a vibration. The phone will continue to do so until unplugged from the charger.
All help is very appreaciated![/QUOTE
!st question is did you flash the correct rom for your device?
If you can go to recovery, then try to flash another rom,
Or use adb/fastboot to try and flash recovery img and use fastboot to reboot recovery.
Alternatively you may have to flash a kernel relevant to your rom.
Click to expand...
Click to collapse
Try this and see if it helps.........
If your phone is unbranded, i.e. not locked to a carrier, download a any generic(customized) firmware for your device through Xperifirm and flash it through Flashtool. It will wipe all your data (excluding your microSD, of course) but you don't have any other choice. This is most probably unbrick it...... So, try it and all the best.:good:
EDIT: If you've tried it, then go for this. Luckily you've fastboot still working, right? So, go to fastboot mode and flash a recovery image through it. It may take a lot of time but if recovery works, you can install a stock based rom for your device and then go back to stock firmware through Xperifirm and Flashtool.....
The phone is a Verizon model. I've tried to unlock the bootloader using command prompt following the sony instructions, after recieving my unlock key. I am able to connect to the phone and all of the fastboot commands work until I try and run the one to actually unlock the bootlaoder. That says the it is "not allowed." I think that is because I never enabled OEM Unlocking in the developers menu though. Not sure if there is a stock kernel I should try an flash through fastboot. Or if there is a stock recovery file that is flashbable through fastboot with a locked bootloader. The phone is definetley working in fastboot and somehow still knows how to charge. Im pretty sure at this point the problem is that the phone has a custom rom on it but the bootloader is still locked. I cannot unlock the bootloader because I can't get in Android to enable the proper options. Have also tried Flashtool for unlock the bootloader, along with extracting kernel sins from a stock 4.4.4 and a stock 5.0.1 FTF and trying to flash them. Since the begining I have still seen no change in the phone behavior.
Nick1801 said:
The phone is a Verizon model. I've tried to unlock the bootloader using command prompt following the sony instructions, after recieving my unlock key. I am able to connect to the phone and all of the fastboot commands work until I try and run the one to actually unlock the bootlaoder. That says the it is "not allowed." I think that is because I never enabled OEM Unlocking in the developers menu though. Not sure if there is a stock kernel I should try an flash through fastboot. Or if there is a stock recovery file that is flashbable through fastboot with a locked bootloader. The phone is definetley working in fastboot and somehow still knows how to charge. Im pretty sure at this point the problem is that the phone has a custom rom on it but the bootloader is still locked. I cannot unlock the bootloader because I can't get in Android to enable the proper options. Have also tried Flashtool for unlock the bootloader, along with extracting kernel sins from a stock 4.4.4 and a stock 5.0.1 FTF and trying to flash them. Since the begining I have still seen no change in the phone behavior.
Click to expand...
Click to collapse
dude I'm from the Verizon side yea like you have an bootloader status unlock no so your not going to change that and you can only flash Verizon z3v stuff you are really lucky if you can still get to fastboot after doing this. Use flashtool and flash a Verizon ROM from the z3v section only and pray it works.
Hello,
So my mom owns a Xperia Z3, and each time she would turn it on, the System UI would keep crashing. I didn't know why, but I thought I would boot into recovery and clear the cache/dalvik and see if that fixes anything. I'm not sure if it would, but I'm putting that investigation on hold for now because I noticed a bigger problem - I can't even boot into recovery or the bootloader!
So here is what I did: I enabled USB debugging, connected the phone to my PC, accepted the RSA fingerprint and opened up to command prompt. Ensuring the device was there, I typed `adb devices` and it was successful. Then, I typed `adb reboot bootloader`. The phone just gave me a black screen. After about a minute I decided to turn the phone off, and so I did, and it rebooted into the ROM. Then, when the device restarted and it connected to the PC, I went through the steps to ensure the device was connected and I typed `adb reboot recovery`. The device simply rebooted into the ROM. I looked at a few articles on how to start either recovery or the bootloader using key combinations, but it was of no use.
I have never really messed with a Sony phone before; I use a Nexus 5X and the most I did was install LineageOS. Pardon my ignorance if I am missing something that only Sony phones have, but to my understanding, the partitions should be identical to that of my phone (the names, of course, not the images)
I appreciate anyone who takes the time to help me (and therefore my mom) with this issue.
Have you solve your problem?
Have the same problem ... any solutions?
I know this is old but for the Z3 (or at least my D6633) the bootloader (aka fastboot) mode is indicated by a blue notification light, if you have that, you should be able to use
Code:
fastboot devices
and see your phone. I still couldn't boot into any recovery mode, stock or custom, and would appreciate any help with the matter.
Hi guys. So I have been going through xda and Google for hours and hours trying solutions, to no avail. I almost never post on forums for help because I can usually find the solution. Not this time. This is my last resort next to throwing my phone out a window or praying for death's sweet release.
The facts: I have a rooted Xperia Z3v. I tried to upgrade TWRP in order to follow some directions on upgrading to Nougat. I flashed TWRP from 2.8.X.X to 3.X.X.X. I rebooted and it never made it to the Sony logo. Now, if I plug the phone in to either a wall socket or PC it vibrates, endlessly at three second intervals, each time with red LED. If I try to enter flash mode, then its the same but with a brief green led after the red. I can enter fastboot (the only way to stop it vibrating while plugged in) and my PC sees it, including Flashtool, but since my bootloader is locked permanently, I can't really do much with it.
When plugged into the wall-charger, I noticed that the charger's LED changes from "Active" to "Inactive" with every vibration. I'm pretty sure I'm in a reboot loop. The screen is totally dead and there's no logo, but every three seconds it kills it self and comes back.
I have tried everything I could think of.
What I have:
I have the stock firmware ready to go
I have TWRP backups on SD card and PC
I have Flashtool
I think my drivers are good, but not 100% sure
I can fastboot
I'm at my wit's end and losing hope.
Please, I'm open to any suggestions at all.
There is a chance to save your phone 50% this trick might work for your phone sort of .
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or atleast take a rest for what the heck is going on with your phone
4.If none of the solutions work disscuss with me i am happy to help
Same thing here. Flashed wrong ROM via TWRP.
As a result, immediate loop (repetitive vibration, led blinking red) when connected via USB. No recovery access. Only fastboot access (blue led).
Locked bootloader.
Flashtool:
- tried flashing kernel.sin extracted from a stock ftf - no good (locked bootloader, unlocking requires flashboot which is not accessible).
- tried flashing system.sin extracted from a stock ftf - no good, flashtool says
INFO - Flashing selected system
and immediately after that
INFO - Please check the log before rebooting into system
So it clearly doesn't do anything. Any other approaches to try?
Tech core said:
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
Click to expand...
Click to collapse
Flashmode does not work, it starts cycling immediately.
Tech core said:
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
Click to expand...
Click to collapse
Yes, certainly.
Tech core said:
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or at least take a rest for what the heck is going on with your phone
Click to expand...
Click to collapse
Can't flash anything, so can't try it.
Tech core said:
There is a chance to save your phone 50% this trick might work for your phone sort of .
First i need some answers
1.If you go to flash mode the phone vibrates right is it detectable by your pc at that time.
2.did you Try hard reset not by the vol button press but the very sophisticated button under the sim tray.
3.https://forum.xda-developers.com/z3/development/nougat-7-1-1-android-source-project-t3532346
try this I know this is not for your phone but you will be able to actually boot your phone or atleast take a rest for what the heck is going on with your phone
4.If none of the solutions work disscuss with me i am happy to help
Click to expand...
Click to collapse
I bought an M4 Aqua to keep me going for now as they're cheap. The E2306 is unrootable with 6.0.1 and I don't want to downgrade to Loli so no possibility to butt**** this one. If s300pmu1 and you figure it out, I'll do the same to mine.
TheControlled said:
I bought an M4 Aqua to keep me going for now as they're cheap. The E2306 is unrootable with 6.0.1 and I don't want to downgrade to Loli so no possibility to butt**** this one. If s300pmu1 and you figure it out, I'll do the same to mine.
Click to expand...
Click to collapse
I didnt get your comment brief it to me
Background: Rooted phone with SuperSU and TWRP. I am very unknowledgeable when it comes to everything programming wise.
Yesterday SuperSU got an update. I installed it like I have before, and rebooted. My phone got stuck in a boot loop, in that it would go past the Sony screen and into the animation, but then reboot. I still had access to TWRP, so I tried doing some reading and attempted to flash a new ftf onto my phone using Flashtool. It didn't work, and now my phone was stuck at the screen that says Sony and Xperia. Next I tried using fastboot to flash boot.img and system.img onto my phone. It worked and my phone booted into a very generic looking OS. However next I tried flashing an updated tft onto it - This caused it to not boot at all, and instead get stuck on a screen that shows only Sony. I was able to use fastboot to push a TWRP image onto my phone, so now I can (occasionally) enter TWRP. However, despite pushing version 3.0.2.0 onto it, it says it has version 2.7.2 installed, meaning I cannot install image files from within the recovery. I cannot enter fastboot either, as when I try to it just gets stuck on the Sony screen again. I'm currently charging the phone, as I believe this might be the issue, but if anything has any idea what I should do, please help. I've read about flashing a system.sin file, however when I can't actually get fastboot working, no solutions seem tenable to me.
Like I said, I'm pretty much illiterate in this area, so don't go too fast on me please.
One more thing I should mention, when plugged in my phone will enter the Sony screen and get quite hot, even if I turn it off by holding in the power and volume up buttons, so I'm fearing it's not even charging.
You need to hold power on and volume up buttons together until phone completely turns off.
Get a firmware and put it in flashtool firmware folder ("C:\Users\XXXYOURNAMEXXX\.flashTool\firmwares") use a sony usb cable and hold the volume down before and whilst inserting the cable when prompted on flashtool.
avi312singh said:
You need to hold power on and volume up buttons together until phone completely turns off.
Get a firmware and put it in flashtool firmware folder ("C:\Users\XXXYOURNAMEXXX\.flashTool\firmwares") use a sony usb cable and hold the volume down before and whilst inserting the cable when prompted on flashtool.
Click to expand...
Click to collapse
I did that, trying to flash a new firmware to try and fix the boot loop is what made the problem worse. After I tried that the phone wouldn't go past the Sony screen.
EDIT: I think I'm making progress. I had made the mistake of downloading firmware for Xperia Z3 compact. After getting the correct firmware, the phone has now booted and is showing the android robot as during a firmware update.
Thought I'd add that I got my phone working again. Turns out I had been trying to put a Z3 compact firmware onto it. found the right firmware, flashed it with flashtool and it's working just fine now. Might be a good idea to keep the thread open for others who are doing the same mistake?
Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!
stanelie said:
Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!
Click to expand...
Click to collapse
happened to my walleye too , and managed to bring it back to life . check this thread for a possible solution. https://forum.xda-developers.com/pixel-2/help/december-factory-image-to-broken-t3875213
Thanks!
I missed that thread while researching this issue.
I will try these things when I get back from work next week.
Thanks again!
stanelie said:
Thanks!
I missed that thread while researching this issue.
I will try these things when I get back from work next week.
Thanks again!
Click to expand...
Click to collapse
Just as a reference for anyone else who needs the fix and can't be bothered opening another thread.
SOLUTION: At the menu where it is stuck and saying device fail etc, plug in your usb cable to the mobile, press and hold the POWER button for 10 seconds, it will now recognise your phone under fastboot.
Once that is cleared, it's pretty much straightforward flashing latest pixel 2 image via fastboot and problem solved.
sidenote: Issue came with anyone who tried to flash december security updates and above as of what I heard.
I will try that, thanks.
So, several things :
Holding down the power button had no effect other than restarting the boot menu, but Fastboot never became available.
Opening up the phone and disconnecting the battery and reconnecting it made Fastboot available again. This would be in line with other users that let the phone battery discharge completely before regaining fastboot access.
Sidenote : opening up this phone is not for the faint of heart. I managed to damage something on the motherboard doing so (probably a static electricity discharge), the screen ended up displaying gibberish. I was able to salvage my phone by replacing the motherboard. I had ordered a replacement motherboard when I thought all was lost with no fastboot, and I had it on hand. Expensive little sucker...
stanelie said:
Hello.
I did something wrong while trying to flash TWRP on my pixel 2, I am now stuck at the bootloader, and I cannot boot System or Recovery. While at the bootloader screen, it says Device State : unlocked. If I try to get to download mode, it says "ERROR: Operation Denied". If I try to go into recovery, it says "ERROR: Slot Unbootable: Load Error". If I try "Start", I get the same error message.
Also, adb or fastboot don't seem to be able to "see" the pixel connected to the computer. I believe my cables are good since I was able to flash Magisk and reflash the whole system with them before bricking it.
Can anyone help?
Thanks!
Click to expand...
Click to collapse
Same thing happened to me except I never even tried to root. Just pulled the phone out of my pocket, and the little Android dude was belly up. It's showing device locked - and although I had it in Dev. mode from weeks back (thought USB Debugging was enabled) it fails to respond to adb commands, boot-loader mode, etc.
...Looks like Google laid an egg with this one.
Pixel 2 - "ERROR: Slot Unbootable: Load Error"
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
ashokabs said:
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
I don't even know how to thank you. I almost had a heart attack watching my Pixel bricked. Thanks man!
Save my day! I just keep pressing power button and fastboot response finally!
Can this be done if the device is locked?
_Kalyan said:
I don't even know how to thank you. I almost had a heart attack watching my Pixel bricked. Thanks man!
Click to expand...
Click to collapse
Does ur bootloader locked or unlocked?
---------- Post added at 11:36 AM ---------- Previous post was at 11:36 AM ----------
ashokabs said:
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
Works on bootloader state locked or not?
SoKa1993 said:
Does ur bootloader locked or unlocked?
---------- Post added at 11:36 AM ---------- Previous post was at 11:36 AM ----------
Works on bootloader state locked or not?
Click to expand...
Click to collapse
If the boot loader is locked look for a script for unlocking the bootloader from recovery or bootloader state. I did find it but cannot remember. My bootloader was unlocked so I did not have to use it.
ashokabs said:
Pixel 2 - "ERROR: Slot Unbootable: Load Error"
If you get the above error you will find that you cannot boot into recovery and the phone stays in the bootloader screen each time you try to start the phone. If your bootloader is unlocked you might be able to recover your phone to flash a stock image and revive. My problem started when I tried to restore a nandroid backup after trying out Android Q beta 1. I got the error mentioned above.
Most of the people recommended that I get a replacement from Google support as they had tried everything but it didn't work. Well right here in XDA Pixel 2 forum there is a solution waiting to be used. I am reproducing it from the post titled
"December factory image seems to have broken fastboot enumeration"
Quote
A possible way to resurrect a bricked Pixel 2...
Hey guys, I have just been able to get mine alive. The device started to be recognized (USB/fastboot) after about 10 unsuccessful attempts to start the system: "Start", from bootloader.
So what exactly happened and what I did:
1. Bricked a Pixel 2.
2. It started into bootloader and showed the "slot unbootable" error.
3. The device was not recognized by any of my machines at all, lsusb did not show anything new in the system, and, respectively, fastboot did not see the device.
4. The default option in the bootloader is "Start" if I remember correctly. So I just pressed the power button and did not release it until I noticed a vibration. It were about 10 unsuccessful attempts of system loading before that vibration.
5. Right after that vibration I connected a generic (NONAME) USB-C <-> USB-A cable to both the device and my Linux machine, and fortunately the device was recognized by the system and fastboot was able to detect the device correctly. So I flashed the a factory image, and it went just fine.
Unquote
Let me confirm that this works. I kept the power button down while the phone was connected via USB to the PC for at least 5 mins. During several reboots suddenly I got a beep from the PC which indicated that ADB was working. I flashed a stock image and voila the pixel 2 is back in operation.
Hope this helps several other people who might have this problem.
Click to expand...
Click to collapse
I have same problem. I use Pixel 2 and Fedora. My question is, what i exactly should do? I mean the steps. I didn't get that beep from my laptop. But I got the vibration when I hold the power button when it's not connected to USB. Please Help me.
Sorry my english isn't that good.