Database Info

RUU Error 171 Stuck on waiting for boot loader

As the title says, RUU attempts booting my phone but it never comes back on. Even selecting restart boot loader in fastboot or a command it doesn't power itself back on. I have read through other forums and nothing has worked for me yet.
EDIT: I should probably clarify fastboot usb WORKS. Ruu must see my phone considering it detects the ROM version and turns the phone off in attempt to reboot. Anything that I do that requires a reboot doesn't work. I have tried unlocking the bootloader again, everything is fine until it comes to rebooting then I must turn the phone on myself and nothing changes...... IT DOESN'T REBOOT ITSELF therefore seemingly nothing wants to work. And the HTC boot screen is gone??
More background information: http://forum.xda-developers.com/showthread.php?p=39046436#post39046436

What we're your steps exactly? Did you relock your bootloader

a box of kittens said:
What we're your steps exactly? Did you relock your bootloader
Click to expand...
Click to collapse
Yes I did through fast boot with the oem lock command. I've tried installing RUU with a Windows 7 laptop (has HTC sync software) and Windows 8 desktop (basic drivers). Both failed, tried using Windows XP/Vista in compatibility modes and running as an admin with the same results.

Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.

iElvis said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
Click to expand...
Click to collapse
No luck. And I believe it does see the phone in the beginning of the installation. It makes it reboot to the boot loader and that's where it loses the connection. The phone just isn't booting itself back up. I appreciate the reply, if you have anymore ideas please let me know.

Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?

iElvis said:
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
Click to expand...
Click to collapse
Re-downloaded RUU and still no go. And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.

Does anybody else have some more ideas?

Okkoto said:
And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Click to expand...
Click to collapse
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.

redpoint73 said:
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
Click to expand...
Click to collapse
Fastboot does see it but adb does not. And what I mean by rebooting the phone in my last post is RUU attempts rebooting it from the boot loader which does turn the phone off but it stays turned off. I've used other commands to reboot the phone from the fastboot screen and those too turn off the phone then again it doesn't come back on like a reboot should do.

I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.

Okkoto said:
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Click to expand...
Click to collapse
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.

DvineLord said:
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
Click to expand...
Click to collapse
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.

i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.

Okkoto said:
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
Click to expand...
Click to collapse
when you say it shows connected through fastboot what do you mean?
how are you getting the device into fastboot - through recovery??
oh, and what was on your device before you tried loading the RUU?

kkm68 said:
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Click to expand...
Click to collapse
Yes this + if you're on a usb3 port try usb2. Also make sure you're using the cable that came with the phone as I understand other cables may cause issues like this. Also, avoid using a hub or usb extension.

Solution to error 171
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!

diegoyabishh said:
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
Click to expand...
Click to collapse
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.

jondon156 said:
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
Click to expand...
Click to collapse
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita

Heisenberg said:
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Click to expand...
Click to collapse
hi all..
facing same problem with HTC Desire 816 n 4g... have anyone got any solution??
plz pass it..
thank you

Problem after unlocking bootloader - Bricked?

Hey guys, how are you?
Well, I wished to root my Moto G, so I (tryed?) to unlock the bootloader. Alright, done it, but then I ran into some trouble...
After the booting up, everything started forceclosing and since then, when I try to boot it, I get a black screen after the Motorola logo.
Now, I am really really worried about my phone. I got it a month ago. I'm so afraid I really f****d up my phone right now that my hands are shaking.
I'm new to Android, so sorry if the solution is pretty obvious. And if it's not, could explain it very carefully to me? I don't know what to do.
My best wishes to you, guys.

I'm assuming you used superboot if so that would happen.
The logo sort of blured out right just press volume down and power and it would work
Or did this happen when you were just trying to unlock bootloader?

TomGlass1 said:
I'm assuming you used superboot if so that would happen.
The logo sort of blured out right just press volume down and power and it would work
Or did this happen when you were just trying to unlock bootloader?
Click to expand...
Click to collapse
Yeah, that happenned when I was trying to unlcok bootloader.
And well, my computer now doesn't even recognizes my phone.
EDIT: It appears as "Fastboot falcon S" in the Device Manager. Tried installing some drivers I found in the Internet, but it didn't work.

Explain exactly what happened please. Was the unlock successful and did you just bootup normally after or did u do anything else in fastboot mode? Why are you trying to install fastboot drivers again, as you already wouldve had them to unlock the bootloader. Did you try installing recovery or some root img from fastboot? You said its forceclosing, but it isnt starting at all now?
Some things you can do right now (if your bootloader is unlocked) is to flash a recovery (twrp,cwm) through fastboot and if you think most system files (or settings) are beyond repair, flash your firmware version though fastboot. Will point you to the guides for them, but post more info if you want help.

hemanthmahesh said:
Explain exactly what happened please. Was the unlock successful and did you just bootup normally after or did u do anything else in fastboot mode? Why are you trying to install fastboot drivers again, as you already wouldve had them to unlock the bootloader. Did you try installing recovery or some root img from fastboot? You said its forceclosing, but it isnt starting at all now?
Some things you can do right now (if your bootloader is unlocked) is to flash a recovery (twrp,cwm) through fastboot and if you think most system files (or settings) are beyond repair, flash your firmware version though fastboot. Will point you to the guides for them, but post more info if you want help.
Click to expand...
Click to collapse
Alright, just after I unlocked, when I was booting, I got a message saying that "xxxx has stopped working/failed to initialize/something like that". And then, when I rebooted, I got the usual message of the "bootlocker has been unlocked". After that, the Motorola logo started animating, but then I just got a black screen. I can't turn it off and the battery just got depleted (I'm charging right now).
When I try to connect it in my computer, the PC recognizes it as "MTP Device" or "Fastboot falcon S" when fastbooted. I can't install any drivers and the Motorola Device Manager doesn't recognizes it either.
Well, if there is some missing information, just ask me. I tried to describe my problem the best I could. Anyway, sorry for my bad English and thanks in advance for any effort trying to discover what's wrong.

Motorola Device Manager isn't helpful in this state as it doesn't handle things in fastboot. You already have all the required drivers (fastboot falcon S is the right driver afaik, falcon being motog codename) for flashing your stock firmware.
1. First, you can try the "Factory" option in bootloader (the third one, use volume down to move selector, volume up to select), though this might not really work for major issues.
2. When in fastboot mode, use "fastboot getvar all" to get the firmware details if you already didn't know about it.
3. Otherwise if yours is a standard gsm (non dualsim/non cdma), just download Blur_Version.174.44.9.falcon_umts.Retail.en.GB (UK stock for gsm, 4.4.2)
Download the mfastboot files to use rather than fastboot for flashing. You might need to modify your commands a bit for various firmwares.
http://forum.xda-developers.com/showthread.php?p=47820707 (refer this thread for flashing your stock firmware)
All the firmwares are in either of the links below (all around 400mb):
http://sbf.droid-developers.org/phone.php?device=14
(or)
http://www.filefactory.com/folder/c6cdedc45a775d27
I still don't get why many ppl are getting these errors after unlocking, very bad unlock method of moto if so ( I didnt get any such issues though).

When I use the "fastboot getvar all" command, it says "waiting for device". The phone is already connected, but the Moto G doesn't recognizes it's connected either.
I'm getting more and more afraid I really hardbricked it.

http://www.mymotocast.com/download/MDM?platform=windows
Tried installing these drivers? Your fastboot doesn't seem to be setup properly. How did you unlock without a working fastboot driver? You are trying that command in bootloader mode right?

Already installed it from the start. The message I got is always this:
"There aren't any updates for your device at the moment
Current Version: N/A"
My fastboot: Doesn't matter the operation I do, I always get this <waiting for device> and the phone is already connected into the computer. And the phone doesn't recognizes it is connected too.
And greeeeat news: my phone now doesn't charges either. I get stuck on a screen with a battery logo and 0%, when connected to the charger. Still, I still can access the fastboot mode. Well, am I lucky or not?

I'm pretty confused with this. How exactly did you unlock without a working fastboot (no waiting for device issue)? Did you change your pc drivers after unlock or trying this from a different pc? When you say "phone doesn't recognizes it is connected" you mean it says "Connect USB data cable" below "Device is UNLOCKED"? If so, maybe try another usb port cause it should normally say "Transfer Mode: USB Connected" regardless of proper drivers.
Your phone will chrarge no matter what though, no worry about that. It needs to say "Battery OK (Charging)" when connected to PC
No, as long as you have working your device isn't technically bricked in any sense. Don't worry, get that fastboot working again and anything can be fixed.
Also you didnt say whether or not you tried that "Factory" option in bootloader!

hemanthmahesh said:
I'm pretty confused with this. How exactly did you unlock without a working fastboot (no waiting for device issue)? Did you change your pc drivers after unlock or trying this from a different pc? When you say "phone doesn't recognizes it is connected" you mean it says "Connect USB data cable" below "Device is UNLOCKED"? If so, maybe try another usb port cause it should normally say "Transfer Mode: USB Connected" regardless of proper drivers.
Your phone will chrarge no matter what though, no worry about that. It needs to say "Battery OK (Charging)" when connected to PC
No, as long as you have working your device isn't technically bricked in any sense. Don't worry, get that fastboot working again and anything can be fixed.
Also you didnt say whether or not you tried that "Factory" option in bootloader!
Click to expand...
Click to collapse
OMG. I tried that "Factory" option before but it didn't work. Now I tried a second time and it worked. Thanks a lot! Really :laugh:
Anyway, now my phone is back again and rooted. Thanks for the help, guys!

Thaiane said:
Already installed it from the start. The message I got is always this:
"There aren't any updates for your device at the moment
Current Version: N/A"
My fastboot: Doesn't matter the operation I do, I always get this <waiting for device> and the phone is already connected into the computer. And the phone doesn't recognizes it is connected too.
And greeeeat news: my phone now doesn't charges either. I get stuck on a screen with a battery logo and 0%, when connected to the charger. Still, I still can access the fastboot mode. Well, am I lucky or not?
Click to expand...
Click to collapse
Guys the problem occurs due to corruption of /data folder. Even I had the same issue.
What you can do is
1. Connect your phone to PC in fastboot mode.
2. In fastboot, enter the command "adb erase userdata" and "adb erase cache" without quotes and reboot you phone. It will work for most of the devices, if it doesn't I have some other workaround too.

help
forgotter said:
Guys the problem occurs due to corruption of /data folder. Even I had the same issue.
What you can do is
1. Connect your phone to PC in fastboot mode.
2. In fastboot, enter the command "adb erase userdata" and "adb erase cache" without quotes and reboot you phone. It will work for most of the devices, if it doesn't I have some other workaround too.
Click to expand...
Click to collapse
I have the same problem. my phone stuck in blank screen after Unlock Bootloader. and then I try to do "adb erase userdata" and "adb erase cache". but my phone has no chenge, still stuck in.
I attach log when enter command adb above.
I'm sorry before. I can't spech English well

jidurrr said:
I have the same problem. my phone stuck in blank screen after Unlock Bootloader. and then I try to do "adb erase userdata" and "adb erase cache". but my phone has no chenge, still stuck in.
I attach log when enter command adb above.
I'm sorry before. I can't spech English well
Click to expand...
Click to collapse
The log you have posted contains only the help commands of adb and not the actual commands you gave.
Give a try to factory reset from fastboot mode on your phone. And do you a custom recovery installed in your phone?

forgotter said:
The log you have posted contains only the help commands of adb and not the actual commands you gave.
Give a try to factory reset from fastboot mode on your phone. And do you a custom recovery installed in your phone?
Click to expand...
Click to collapse
I've tried factory reset for several times, but no change as well.
yes, I get a CWM in my phone. and then, what have I do?

jidurrr said:
I've tried factory reset for several times, but no change as well.
yes, I get a CWM in my phone. and then, what have I do?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2704207
Go to the above forum.
Sorry for late reply was busy with studies.

I had flash stock firmware
through PC

[Q] Hard-Bricked, no boot. Failed during flash

OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?

gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
+1

gtgeek said:
OK,
I was trying to flash a new ROM and had some issues where it would continously reboot so, after some reading it seemed like I needed a new version of TWRP, so I updated it. That didn't help.
I decided to reflash the stock rom on the device but after doing that, it wouldn't boot past the ASUS boot screen. So I tried again (via fastboot), same result. So I tried again and this time fastboot crashed in the middle of the load and now the tablet won't boot or anything.
It seems like the tablet still has power because windows makes a funky sound when you plug it in.
I saw this post but pressing the tiny button with a paperclip doesn't do anything.
Edit:
Windows can tell I plugged something in but says there is an error and doesn't recognize it anymore. Therefore, I don't have adb or fastboot access.
Edit: I installed the naked drivers and got it to recognize the device as an apx. I then pointed it to the normal driver and is recognizes it as an adb device but I can't connect via adb.
Edit: Nevermind, it came unplugged and when I plugged it in again windows didn't recognize it.
Where in the crap do I go from here?
Click to expand...
Click to collapse
So will the tablet not boot into the bootloader ?
Thx Josh

lj50036 said:
So will the tablet not boot into the bootloader ?
Thx Josh
Click to expand...
Click to collapse
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.

gtgeek said:
Nothing, just the black screen.
I only know something is going on when I connect it to a pc I can here it connect/disconnect when I hold the power button or press the reset button. Also checked the hdmi output on another screen to make sure that wasn't the problem....it wasn't.
Click to expand...
Click to collapse
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh

lj50036 said:
I see....
If you dont have your nvflash blobs, its a brick ...
Sorry for the bad news ....
Thx Josh
Click to expand...
Click to collapse
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?

gtgeek said:
That was the conclusion I was coming to.
Now, for a nerdier question. If I had physical access to the processor, could I program it directly using it's programming ports?
Click to expand...
Click to collapse
Nope there is just no way...
The chip is locked down ... :crying:
There is lots of info out there but its just info ...
No one to date has come back from where you are ....
Thx Josh

[Q] Nexus 5 Mysterious Stuck on boot animation

Hi Everyone!
Really new to xda so I'm not sure if this is the right place to post this at (sorry). I have a nexus 5 that after I (purposely) rebooted, is now just stuck on the boot animation, (it was not updating to 5.1.0 or 5.0.1). I tried leaving it on but it just kept spinning until the phone died. I can access fastboot, and recovery, have tried wiping cache, and factory resetting multiple times. Nothing has happened. I have gotten adb and fastboot on my mac, and downloaded a factory image from google to try and reflash, but ./adb devices doesn't show anything, even though the phone is connected in fastboot mode. (On the google website it says drivers shouldn't be an issue?). My nexus 5 is running stock, was unlocked before but now still unrooted, its the US version and I have tried connecting to the computer with multiple micro-usb cables (including the one included in the box). What should I do? Or how do I get my nexus 5 to show in ./adb devices?
I'm stumped, any help would be greatly appreciated , thanks!

hanssw said:
Hi Everyone!
Really new to xda so I'm not sure if this is the right place to post this at (sorry). I have a nexus 5 that after I (purposely) rebooted, is now just stuck on the boot animation, (it was not updating to 5.1.0 or 5.0.1). I tried leaving it on but it just kept spinning until the phone died. I can access fastboot, and recovery, have tried wiping cache, and factory resetting multiple times. Nothing has happened. I have gotten adb and fastboot on my mac, and downloaded a factory image from google to try and reflash, but ./adb devices doesn't show anything, even though the phone is connected in fastboot mode. (On the google website it says drivers shouldn't be an issue?). My nexus 5 is running stock, was unlocked before but now still unrooted, its the US version and I have tried connecting to the computer with multiple micro-usb cables (including the one included in the box). What should I do? Or how do I get my nexus 5 to show in ./adb devices?
I'm stumped, any help would be greatly appreciated , thanks!
Click to expand...
Click to collapse
As long as you're able to charge the phone still while it's off you'll have some options.
When you do factory reset, does it complete the process and reboot on its own??
Just saw this thread. You might want to try it out.
http://forum.xda-developers.com/showthread.php?t=2957801
Sent from my 1+1

Mojar7070 said:
As long as you're able to charge the phone still while it's off you'll have some options.
When you do factory reset, does it complete the process and reboot on its own??
Just saw this thread. You might want to try it out.
http://forum.xda-developers.com/showthread.php?t=2957801
Sent from my 1+1
Click to expand...
Click to collapse
Yes it does does complete it, I reset it from recovery, so it completes and when it restarts its still stuck on the loop again for another hour. I'm downloading the file, hopefully it works
EDIT: Already completed the flash using the tool, but the first boot didn't work, reformatting again after the flash.
EDIT 2: Reboot doesn't work after the reformat after the flash.

hanssw said:
Yes it does does complete it, I reset it from recovery, so it completes and when it restarts its still stuck on the loop again for another hour. I'm downloading the file, hopefully it works
EDIT: Already completed the flash using the tool, but the first boot didn't work, reformatting again after the flash.
EDIT 2: Reboot doesn't work after the reformat after the flash.
Click to expand...
Click to collapse
Have you tried flashing through fastboot?? I'll be honest I'm not to knowledgeable on fastboot, maybe someone else would like to chime in for that.
I've used wug fresh nexus tools but you'll need the phone to boot up properly to get into developer settings to turn on USB debugging.
Sorry if I can't help any further.
Sent from my 1+1

Nexus 5 boot stuck
Bro just try to write the following Command in cmd in the platform devices folder
'fastboot devices' instead adb devices. copy the stock image to the Platform-tools folder and just flash it via fastboot commands. mine was stuck in boot animation and did the same

Pixel 3 Brick issue.

So I unlocked the bootloader no problem. TWRP no problem, then something happened with the magisk flash. Phone tried to boot, as normal, then it went to recovery, then to a boot loop. I can get it to the fastboot screen, but ADB won't recognize the phone, I have chased around different USB drivers for two hours, thrown every command at it that I can think of, but nothing is working. Any suggestions? I literally picked the phone up (bought off of swappa locally), drove home and bricked it lol.
edit: The phone is recognized by my computer, just not ADB.

jerseymk2 said:
So I unlocked the bootloader no problem. TWRP no problem, then something happened with the magisk flash. Phone tried to boot, as normal, then it went to recovery, then to a boot loop. I can get it to the fastboot screen, but ADB won't recognize the phone, I have chased around different USB drivers for two hours, thrown every command at it that I can think of, but nothing is working. Any suggestions? I literally picked the phone up (bought off of swappa locally), drove home and bricked it lol.
edit: The phone is recognized by my computer, just not ADB.
Click to expand...
Click to collapse
So you put the phone in fastboot mode and ADB won't recognize the phone? That is normal, ADB works when the phone is booted normally. In fastboot mode you only use fastboot commands.
Fastboot devices

Just need to "fastboot flash boot boot.img" with the stock boot.img.

jsauder2 said:
Just need to "fastboot flash boot boot.img" with the stock boot.img.
Click to expand...
Click to collapse
Sorry I work for the railroad and was away for the last few day. I am aware of that, the issue I was facing was that the phone was not communicating with the laptop when I booted fastboot. I was able to get it this morning after about what felt like 900 attempts. I knew what needed to be done, I was having severe connectivity issues, I played the game of switching cables, switching usb ports etc... finally it had connectivity. Thank you again for your help though.