After 8 years of tinkering with Android phones I have no clue how this happened.
PIXEL 2 (Walleye, non-xl)
Tried getting TWRP and ElementalX working but either one or both weren't doing there thing, though I could at least boot and use my phone normally. Finally ended in a situation where I couldn't boot passed fastboot with an error at the bottom "ERROR: LoadImageAndAuth Failed: Load Error". Found a fix that said to change the active partition. Set it to b and that worked and surprise it loads TWRP...so somehow TWRP was installed, but I can't actually load Android.
Grabbed the latest factory image and manually flashed all the files in the zip-within-the-zip. Everything flashed with no hiccups so I rebooted to bootloader with the intention to then reboot the system, and now this is happening:
TLDR Phone won't turn on. Holding PWR+VolDown SEEMS to do nothing, but it actually flashes a line on the screen like it's trying to load something for a milisecond, then does nothing. Holding PWR+VolUp does nothing. Holding PWR+VolUp+VolDown does the same screen flash followed by the notification LED blinking red 2 or 3 times. Please help!
EDIT: if it matters, the phone is about 50% battery and currently still on judging purely by the fact that it's been warm for about an hour.
sorry for your troubles, i have yet to see this with our phones. Just to get some more information, what happens when you try and charge it? If you plug your phone in to a computer via USB, does it show up in devices? If it shows in devices, can you run platform-tools and see if it shows up via fastboot devices with an ID? If you can connect to fastboot, you could attempt to flash images that way.
djer34 said:
sorry for your troubles, i have yet to see this with our phones. Just to get some more information, what happens when you try and charge it? If you plug your phone in to a computer via USB, does it show up in devices?
Click to expand...
Click to collapse
Nothing happens if I plug into the computer, no sound and not listed in devices. Plugging it in to the charger does nothing except possibly charges it, but I wouldn't know because the screen doesn't seem to be able to turn on for more than a milisecond of a flash.
I had this same problem when I flashed Elemental X kernel over top of the flash kernel and all I did was use the flash-all script that is included with the system image from google. This got me back to my OS where I flashed elemental and magisk. Do you have insurance through your provider?
Related
After flashing a nightly of CM10.2, my phone never booted and instead got stuck in fastboot. My power button has also been broken for months, so it's impossible to navigate the menus in the fastboot ui. When I take my battery out, it automatically boots into fastboot on its own.
Additionally, I found a way to boot into recovery without a power button, but the device is not being recognized as plugged in by my computer.
Any help??? It'd be greatly appreciated, I'm without a phone until I can find a way to fix this.
sinaisinai43 said:
After flashing a nightly of CM10.2, my phone never booted and instead got stuck in fastboot. My power button has also been broken for months, so it's impossible to navigate the menus in the fastboot ui. When I take my battery out, it automatically boots into fastboot on its own.
Additionally, I found a way to boot into recovery without a power button, but the device is not being recognized as plugged in by my computer.
Any help??? It'd be greatly appreciated, I'm without a phone until I can find a way to fix this.
Click to expand...
Click to collapse
I'm having the same exact issue, except with SlimBean 4.3. My phone is stuck in Fastboot (and says "FASTBOOT - NO BOOT OR RECOVERY IMG") and my phone will charge but can't be detected by *any* computer. I've tried three Windows 7 PCs of different makes and an Ubuntu 13.04 box and three different USB cables that all connect my other phone and my tablet fine - none can see it. (It was connecting fine to PC including being seen by ADB prior to this)
My power button is working, but it is also automatically booting into fastboot on its own when I plug it into the computer. Any of the options (besides "Power Off", which performs as advertised) just brings it back to Fastboot.
When I say can't be detected by a computer, I mean there is no USBDeview device listed and there is no 'connect' or 'disconnect' sound on the PC. ADB can't see it.
Yeah, it's strange. Did you find a solution yet, by chance?
sinaisinai43 said:
Yeah, it's strange. Did you find a solution yet, by chance?
Click to expand...
Click to collapse
Nothing yet. Thinking of buying an phone with a busted screen or something and swapping out the internals... I think it's PROBABLY the NAND chip. What I'm suspecting is that because there are several versions of the Nexus S, we might have used the wrong images. I have no idea if this is correct, but it's the only thing I can think of.
My phone's sticker says i9020 on the inside, but D720 (or whatever) when I look up the EIN.
Just hoping somebody sees this and offers a suggestion... I'm getting ready to buy a refurb and put the 'new' body over it so at least I have a functioning, new-ish phone.
This is slightly unfortunate.
Today, my phone decided to say something about the NFC process not working, like it crashed. Over and over. The moment I hit OK, it appeared again. I couldn't even unlock my phone.
I then went to TWRP and went to factory reset, and the problem was still there. Odd. I must have messed up the NFC apk.
I then went to TWRP and tried to wipe the whole phone. I can't remember which button I hit, however it was either wipe or format. I don't think I hit format, but that's all that I can think I did to cause this.
Basically, at this point, I can turn my phone on to either fastboot mode or TWRP, but normal boot gets me stuck at at the 1+ : powered by android screen.
My phone isn't seen by my PC in adb devices or fastboot - presumably because I deleted my OS, and it can't be in USB Debugging if there's no OS to be in the mode? It's either this, or I can't get my PC to see my phone because of a driver issue. If anyone can direct me on the next step of getting my phone working, I'd be greatly appreciative. I have no cares for any data on the phone, I just want it working.
UPDATE : The phone will no longer turn on. Holding any button combo for three seconds makes it buzz. Nothing changes that. It's plugged in using a Nexus 7 charger to an AC outlet.
What did you expect to happen by wiping the whole phone? Stop trying to turn it on, charge it for eight hours, then try booting it into fastboot mode and getting fastboot to work.
Transmitted via Bacon
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Atomschlumpf said:
Hello guys,
so two days ago just when I was heading into work my phone randomly started restarting itself again and again. I had it in my pocket, mobile data and wifi off and nothing really going on when this happened. I was on stock Cyanogen OS with 6.0.1, rooted and with Xposed, but nothing too crazy or experimental.
The phone would boot with a small vibration to the Oneplus logo with the "Powered by Android" writing, stay on that for about 17-18 seconds, then reboot again. No way of going to the recovery with the hardware keys, it would just reboot the same again and again. Since I couldn't really do much, not turn it off and no way of disconnecting the battery, I just had to watch it reboot helplessly until the battery was dead. At home with some hassle I could get it charged again, which basically consisted of charging it while it kept rebooting and cooling it while doing that since it would get really, really hot.
The only option that really works is is getting it into fastboot via the volume up + power button. But in fastboot nothing I did so far changed even the smalles thing about it's behaviour. I tried flashing a new recovery image, letting it boot into the recovery via fastboot (both stock recovery and TWRP), reflashing the complete OS via fastboot again (CM 13 ZNH2KAS3P0), completely wiping it via fastboot and flashing an older ROM (CM11S XNPH44S) but so far nothing has even changed a thing. It keeps booting to the Oneplus logo for about 17-18 seconds before rebooting. The only thing that has changed is with the CM11S ROM the fastboot logo of the android head is now bigger.
I checked the bootloader via fastboot, but it's still unlocked.
So yeah, I'm at my wits end and desperate for any help. At this point I fear it might be a hardware issue and I can trash it, but I'm ready to grasp for straws as I don't really have the money for a new device yet.
Any help is appreciated! Thanks guys!
Click to expand...
Click to collapse
how old is the device?
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Atomschlumpf said:
As far as I know my sister bought it around summer 2014 when it was released, I got it in late 2015
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851
AFAIK,If this toolkit can't fix your device then it's definitely hw issue.
Click to expand...
Click to collapse
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Atomschlumpf said:
Well, the tool won't even recognize my phone, so I guess I'm **** out of luck ¯\_(ツ)_/¯
****ing great....
Click to expand...
Click to collapse
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Mr.Ak said:
Lol,gave up that early?
It needs around 10 tries to get it correctly recognised.
Use XP system with the proper drivers given in the above thread.This tool doesn't work on adb/fastboot,it works on Usb Debugging Port,hence requires different drivers.
Click to expand...
Click to collapse
No, I didn't. I tried the USB Drivers I had already installed, the drivers that came in the package and the QPST Tool suggested in the thread on both my and my girlfriends laptop. But if it doesn't work on ADB/fastboot I probably can't use it anyway since my only two options are having the phone on the fastboot screen or having it constantly reboot....
At this point I'm just really, really frustrated and have sorta accepted it's very likely a hardware issue
I'm with the same problem. In my case, the tool does recognize and shows green after the end but when i try to boot, it only shows the boot logo.
I can enter in fastboot and trying the command "fastboot continue" the brightness goes up, but nothing else
already tried various tools, back to stock, qualcomm , and none worked, so can i throw it out of the window?
Edit: can't enter in recovery, and unlike the op, my phone doesn't reboot (at least i didn't notice it)
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.
So here is what happened, I installed TWRP on my device and completely wiped my phone so I can install bootleggers OS and Gapps on my Pixel 2 Walleye. But I accidentally booted into Boot slot B on twrp and now the only thing the device can boot into is the bootloader mode, recovery and download mode is completely useless, It gives me either operation denied error or Error slot unbootable. The worst part is no computer will recognize my pixel in device manager at all. Mac computer will not detect it either. Ant tips on how to fix this? And again my I have all drivers installed and platform tools are up to date. And devices bootloader is unlocked.
Anything helps!
RomBetaTester said:
So here is what happened, I installed TWRP on my device and completely wiped my phone so I can install bootleggers OS and Gapps on my Pixel 2 Walleye. But I accidentally booted into Boot slot B on twrp and now the only thing the device can boot into is the bootloader mode, recovery and download mode is completely useless, It gives me either operation denied error or Error slot unbootable. The worst part is no computer will recognize my pixel in device manager at all. Mac computer will not detect it either. Ant tips on how to fix this? And again my I have all drivers installed and platform tools are up to date. And devices bootloader is unlocked.
Anything helps!
Click to expand...
Click to collapse
Did you use the same USB cable each time? If yes try different ones, even if it seems to work with other devices. On your PC go to device manager, then view and then hidden devices. Remove anything that has to do with Android. Then try connecting your device. Does an andriod driver show up after you've connected your device?
I have tried 3 different cables. But will try another one
RomBetaTester said:
I have tried 3 different cables. But will try another one
Click to expand...
Click to collapse
Did you go to view, hidden files in device manager and delete all Android drivers? And if you did, did anything show up after connecting your device?
I am having a similar issue after trying to flash the March update. During the script, the System image failed to transfer completely. I tried again using deuce flash all script, and it got a little further (4/5) with the System image but ultimately failed. Things got worse when my computer stopped recognizing the phone. Now I can't even try anything else because there is no communication, similar to OP. I have tried three different computers, three different cables, and have tried deleting Android related drivers in the device manager. No luck, unfortunately. I tried installing USB drivers from Google which also did not help. I welcome any other ideas of what to try next and appreciate any help.
EDIT: I solved the problem by draining the battery completely. In order to drain the battery, I first left the barcode screen on until eventually just the battery image is displayed on-screen when pressing power. Then eventually there will not be enough power to light up the screen at all, but the LED indicator will blink red while holding the power button. Now, I set up my phone such that the power button was held pressed down and left it there until the LED stopped blinking. Now that the power is completely drained, I could successfully get my computer to recognize it! I followed the steps in this post:
https://forum.xda-developers.com/showpost.php?p=78726736&postcount=13
EDIT2: I should also note that the system image didn't flash successfully the first time and I had repeat step 12 which is flashing the update. Luckily it worked the second time!
I had something similar happen. Held down power for about 10 seconds or so until the phone vibrated, then it was recognised by the computer. Then flash stock image
https://forum.xda-developers.com/showpost.php?p=78744315&postcount=31
ricky56789 said:
I had something similar happen. Held down power for about 10 seconds or so until the phone vibrated, then it was recognised by the computer. Then flash stock image
https://forum.xda-developers.com/showpost.php?p=78744315&postcount=31
Click to expand...
Click to collapse
Man you just saved me =)