Develop Bugs

[Q] PLEASE HELP!! Kindle Fire stuck at yellow triangle.

I tried to root my girlfriend's kindle today, and I did everything right, up until I had to install twrp with the kfu. She pulled the usb out before it could install, and now im stuck at the yellow triangle. Ive been able to get my computer to recognize it as "kindle" under device manager, but Im lost as to what to do next. Ive tried to update the drivers but it wont install. I REALLY WOULD APPRECIATE ANY HELP!!!

Try booting into recovery, if that doesn't work then try getting the kindle fire utility to get stock update.zip (#4 in run). If that doesn't work then I have no idea.
Sent from my Kindle Fire

Im not sure how to boot into recovery, wen I turn the kindle on, its on the yellow triangle. I press power and nothing happens but i dont think twrp was ever installed. nd I tried that too, it just hangs after waiting on device

King_Me said:
Im not sure how to boot into recovery, wen I turn the kindle on, its on the yellow triangle. I press power and nothing happens but i dont think twrp was ever installed. nd I tried that too, it just hangs after waiting on device
Click to expand...
Click to collapse
To get into recovery (or at least try), on the screen with the yellow triangle hold the power button until it turns orange (the button, not the triangle) then the screen should do a small flash and go back to the yellow triangle, after 5-10 sec it should say on the screen "teamwin" and then slide up to TWRP if you installed recovery. From there, you can mount usb storage from recovery and get a rom on it to flash (I prefer CM9) and then when it boots into CM9 it will be rooted.

I figured it out. lol. Thanks man. I had to install the drivers that came with the kfu. I forgot that part. *face palm*

King_Me said:
I figured it out. lol. Thanks man. I had to install the drivers that came with the kfu. I forgot that part. *face palm*
Click to expand...
Click to collapse
Lol well that's good.
Sent from my SGH-T989 with CM7

colorblind
BiteBlaze said:
To get into recovery (or at least try), on the screen with the yellow triangle hold the power button until it turns orange (the button, not the triangle) then the screen should do a small flash and go back to the yellow triangle, after 5-10 sec it should say on the screen "teamwin" and then slide up to TWRP if you installed recovery. From there, you can mount usb storage from recovery and get a rom on it to flash (I prefer CM9) and then when it boots into CM9 it will be rooted.
Click to expand...
Click to collapse
I'm there too but (gulp) colorblind, it might turn orange but I don't see it. I am stuck at triangle not being recognised by computer.

http://forum.xda-developers.com/showthread.php?t=1552547
would also read post #2 about drivers
if you got the drivers right, some more information would be helpful
what is your problem ? - what exactly have you done/tried ?

b63 said:
http://forum.xda-developers.com/showthread.php?t=1552547
would also read post #2 about drivers
if you got the drivers right, some more information would be helpful
what is your problem ? - what exactly have you done/tried ?
Click to expand...
Click to collapse
Hi, I have a similar (maybe the same) problem: my KF has blocked the yellow triangle.
This happened after that I tried for the second time to apply the "Install permanet root with superuser" from the Kindle Fire Utility 0.9.5.
The first time everything went fine except the subsequent installation of Extras returning error at the following lines:
tools\adb push apps\system\vending.apk /system/app
tools\adb push apps\system\GoogleCalendarSyncAdapter.apk /system/app
tools\adb push apps\system\GoogleContactsSyncAdapter.apk /system/app
The error was: permission denied.
So, I tought that somenting wen wrong in the previous installation and I tried again.
This time something went really wrong: the KF is in the state I told: yellow triangle.
I tried to turn off and on again but it is in the same state.
I tried to push the button waiting for the TWRP to get up, but nothing happened.
I tried to connect with PC, but the KF is not visible.
What can I do? Does somebody have any hint?
Thank you.

Problems rooting, no idea what happened, can sometimes get into TWRP.

I have rooted an evo 4g, a droid x, and 2 galaxy nexus' and i've never had this much trouble. I installed AOKP and gapps via TWRP and sometimes the device just wont boot. I hit the power button and it flashes green and does nothing. Sometimes if i plug it into my PC and hit the power button the option to hit power to bring up recovery comes up, and I just sit there not knowing where to go next. What should I do? KFU says it's boot status is 4000 and just hangs at activated fastboot.
edit - didnt realize this version of twrp allowed usb mounting, all is good.

Hi friend. These ics rom use kernel 3.0.. If you shut down, hold the power button for 30 seconds until it fully power down... After you see the screen completely dark, then press the power button again, it will turn on. At least that my experience from the first time use ics on kindle fire. Hope that help.

well, theres a new problem now. I turn it on and it just shows the kindle fire splash with an android above it. if I plug it in, it turns on instantly. KFU isnt reading it as anything but windows sees it as android adb interface. doing adb reboot fastboot says device not found. adb devices shows no devices.
I bought up KFU and installed firefirefire though that interface, then switched to cmd prompt and manually used fastboot flash recovery twrp.img after cd'ing android platform tools and putting that latest twrp downloaded from their site in that folder (platform tools)
this happened when using fastboot flash recovery twrp.img in command prompt. It was in this screen while flashing. I did this because KFU wasnt flashing the latest version.
So yup...
edit - this is now fixed. Back to my original problem however.
I install AOKP and Gapps, but after the recovery ! screen it just blacks out. no boot animation or anything. I can get back into recovery and flash back to stock, but, ya know. I want AOKP. What's going on? Yes I am wiping everything.

Sorry wish I could help but this is way over my head....I hope someone else with knowledge will come along and help you...Good Luck!

a few people in the AOKP forums have the same issue, say to just wait forever or keep rebooting....I dunno bout that. I'm not seeing any progress.

patass said:
a few people in the AOKP forums have the same issue, say to just wait forever or keep rebooting....I dunno bout that. I'm not seeing any progress.
Click to expand...
Click to collapse
You need to start by reading this:
http://forum.xda-developers.com/showpost.php?p=23747567

Actually it was just the official aokp rom. Other roms are flashing fine. Dunno what's up with that.
Sent from my Galaxy Nexus using xda premium

[Q] Nexus 7 hangs at "Google", can't enter Recovery

My 2013 Nexus 7 (all stock) hangs at the "Google" screen and won't go further.
If I enter the bootloader and select "Enter Recovery", the screen clears and it goes to the "Google" screen and goes no further. The dead Android with the red triangle/arrow never appears.
Can't connect to it via adb (device doesn't show up) and fastboot just says "Waiting for device..."
Is there anything I can do to recover?
Thanks.

thisisjjd said:
My 2013 Nexus 7 (all stock) hangs at the "Google" screen and won't go further.
If I enter the bootloader and select "Enter Recovery", the screen clears and it goes to the "Google" screen and goes no further. The dead Android with the red triangle/arrow never appears.
Can't connect to it via adb (device doesn't show up) and fastboot just says "Waiting for device..."
Is there anything I can do to recover?
Thanks.
Click to expand...
Click to collapse
Are you completely stock? Were you attempting to flash anything? Does this only happen when you try to boot into Recovery, or when you try to do normal boot too?

Same thing happen to me, about an hour ago i try to turn on my stock nexus 7 2013, it got stuck on the boot animation, after 10 minutes i turn it off by holding the power button, then wait a minute try to tun it on again and i wont pass the Google logo.
i use it this morning as usual and turn in off like every day i don't know what causes this boot loop.
Any help will be appreciated.

charesa39 said:
Are you completely stock? Were you attempting to flash anything? Does this only happen when you try to boot into Recovery, or when you try to do normal boot too?
Click to expand...
Click to collapse
Yup, completely stock. I had the bootloader unlocked but I hadn't ever flashed anything.
It started like this: The screen was dark and the LED notification light was blinking indicating some sort of message. I pressed the power button and nothing happened. I waited a bit and pressed power a few more times. Nothing. (LED kept blinking.)
I finally decided I had to force a reboot, so I held the power button down for the 5 seconds (or whatever) required. The "Google" logo appeared, then the colorful animated logo appeared. After a few seconds of that, the "Google" logo appeared again and hung.
Subsequent attempts to normal boot hung at the "Google" logo.
Attempts to enter recovery hang at the Google logo.

thisisjjd said:
Yup, completely stock. I had the bootloader unlocked but I hadn't ever flashed anything.
It started like this: The screen was dark and the LED notification light was blinking indicating some sort of message. I pressed the power button and nothing happened. I waited a bit and pressed power a few more times. Nothing. (LED kept blinking.)
I finally decided I had to force a reboot, so I held the power button down for the 5 seconds (or whatever) required. The "Google" logo appeared, then the colorful animated logo appeared. After a few seconds of that, the "Google" logo appeared again and hung.
Subsequent attempts to normal boot hung at the "Google" logo.
Attempts to enter recovery hang at the Google logo.
Click to expand...
Click to collapse
Hmm. That's odd. It sounds like the only thing to do would be to flash the factory image. Luckily, you're bootloader is already unlocked, so you shouldn't use any of your userdata. Follow post #2 from this thread: http://forum.xda-developers.com/showthread.php?t=2382051. Pay particular attention to what you need to modify to make sure you don't wipe your userdata.

charesa39 said:
Hmm. That's odd. It sounds like the only thing to do would be to flash the factory image. Luckily, you're bootloader is already unlocked, so you shouldn't use any of your userdata. Follow post #2 from this thread: http://forum.xda-developers.com/showthread.php?t=2382051.
Click to expand...
Click to collapse
I'm not sure how to do that because when it is sitting in the bootloader or after I've selected Recovery and it hangs at the Google logo, fastboot just prints "waiting for device" as if the boot process hasn't gotten to the part where it is willing to participate in the fastboot protocol.
Or am I not understanding something?

thisisjjd said:
I'm not sure how to do that because when it is sitting in the bootloader or after I've selected Recovery and it hangs at the Google logo, fastboot just prints "waiting for device" as if the boot process hasn't gotten to the part where it is willing to participate in the fastboot protocol.
Or am I not understanding something?
Click to expand...
Click to collapse
Well, fastboot is for when the your device is sitting at the bootloader menu. You may be getting it confused with adb, which is when you are completely booted into the OS. So, boot into the bootloader, plug the tablet into the computer, and open the cmd terminal in your platform-tools folder and type "fastboot devices". You should see your device. I'm assuming you already have the drivers since you already unlocked your bootloader.

charesa39 said:
Well, fastboot is for when the your device is sitting at the bootloader menu. You may be getting it confused with adb, which is when you are completely booted into the OS. So, boot into the bootloader, plug the tablet into the computer, and open the cmd terminal in your platform-tools folder and type "fastboot devices". You should see your device. I'm assuming you already have the drivers since you already unlocked your bootloader.
Click to expand...
Click to collapse
I thought I had tried that, but thank you, I'll try again. I appreciate your advice.

Indeed, "fastboot devices" worked at the bootloader. But now I have new problems:
Although I had unlocked the bootloader, the bootloader now reports "lock status: locked" and the unlock icon that had been there during the Google boot screen the day before is now gone. Resigned to lose my userdata, I tried "fastboot oem unlock".
The screen went to the "Unlock bootloader?" screen. I select "Yes" and press the power button. The command line says:
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
and then hangs there. I've tried it twice and waited about an hour each time with no progress beyond this. The screen remains on the "Unlock bootloader?" screen during this time. I wonder if this is another manifestation of the hang when normal booting and when going to the Recovery screen.
Suggestions? Thanks for your help.

thisisjjd said:
Indeed, "fastboot devices" worked at the bootloader. But now I have new problems:
Although I had unlocked the bootloader, the bootloader now reports "lock status: locked" and the unlock icon that had been there during the Google boot screen the day before is now gone. Resigned to lose my userdata, I tried "fastboot oem unlock".
The screen went to the "Unlock bootloader?" screen. I select "Yes" and press the power button. The command line says:
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
and then hangs there. I've tried it twice and waited about an hour each time with no progress beyond this. The screen remains on the "Unlock bootloader?" screen during this time. I wonder if this is another manifestation of the hang when normal booting and when going to the Recovery screen.
Suggestions? Thanks for your help.
Click to expand...
Click to collapse
Hmm. Unfortunately, this is issue seems beyond my knowledge. That's odd that yesterday it was showing unlocked, and today it randomly is locked. If all you did was unlock the bootloader using fastboot, it should still be locked. Did you use a toolkit to unlock before, or did you do it manually with "fastboot oem unlock"?

charesa39 said:
That's odd that yesterday it was showing unlocked, and today it randomly is locked.
Click to expand...
Click to collapse
By "yesterday", I mean before the tablet hung and I had to force reboot it when this problem started.
charsea39 said:
If all you did was unlock the bootloader using fastboot, it should still be locked. Did you use a toolkit to unlock before, or did you do it manually with "fastboot oem unlock"?
Click to expand...
Click to collapse
I unlocked the bootloader originally when I first got the tablet back in July using "fastboot oem unlock". Now, when I try to unlock the bootloader it hangs while the cmd line says "erasing userdata".
I'd still like some help if anyone has any ideas.

hector333 said:
Same thing happen to me, about an hour ago i try to turn on my stock nexus 7 2013, it got stuck on the boot animation, after 10 minutes i turn it off by holding the power button, then wait a minute try to tun it on again and i wont pass the Google logo.
i use it this morning as usual and turn in off like every day i don't know what causes this boot loop.
Any help will be appreciated.
Click to expand...
Click to collapse
thisisjjd said:
By "yesterday", I mean before the tablet hung and I had to force reboot it when this problem started.I unlocked the bootloader originally when I first got the tablet back in July using "fastboot oem unlock". Now, when I try to unlock the bootloader it hangs while the cmd line says "erasing userdata".
I'd still like some help if anyone has any ideas.
Click to expand...
Click to collapse
Can you boot into stock recovery? Without flashing a stock rom or the system image the only thing I can think of would be to do a factory reset. It sucks but it is sometimes necessary. If you are stuck in a boot loop long press the power button to force a reboot, as soon as the screen turns off press the volume down button that will get you to the bootloader. Or if the device is off press and hold both the power button and volume down button to get to the bootloader. Choose recovery with the volume button then press the power button. You should see android laying down with exclamation mark. Press and hold the power button and while holding the power button press and release the volume up button. Stock recovery! Use the volume button to select "wipe data/factory reset" then press power button. If that doesn't take care of it download the factory image and extract, if running 4.4.2 wifi version you should see ;
bootloader-flo-flo-04.02.img
flash-all.bat
flash-all.sh
flash-base.sh
image-razor-kot49h.zip
if you double click the "flash-all.bat" with the device already at the bootloader that will flash the complete image including userdata which wipes the device. You can also open flash-all.bat with notepad and remove -w from the script and it should not flash the userdata.img. Or... you could extract all of the images from the "image-razor-kot49h.zip" and flash them seperately with fastboot, whatever images you try to flash need to be in the same folder as fastboot.exe (platform-tools) so you do have multiple options as long as there is no hardware issue that is causing the reboot. Hope this helps!

wantabe said:
Can you boot into stock recovery? Without flashing a stock rom or the system image the only thing I can think of would be to do a factory reset. It sucks but it is sometimes necessary.
Click to expand...
Click to collapse
Thanks, but sadly this doesn't help me. I'm perfectly happy to do a factory reset at this point, but selecting "Recovery mode" from the bootloader just hangs again at the "Google" logo.
I attempted flashing stock images, but even though my tablet was absolutely unlocked before this happened, "fastboot flash ..." now says "Bootloader is locked." It feels as if whatever damaged the system software also damaged the storage where locked/unlocked is stored.
I feel as if there is nothing to do at this point other than contact Asus about hardware service. Sigh.

thisisjjd said:
Thanks, but sadly this doesn't help me. I'm perfectly happy to do a factory reset at this point, but selecting "Recovery mode" from the bootloader just hangs again at the "Google" logo.
I attempted flashing stock images, but even though my tablet was absolutely unlocked before this happened, "fastboot flash ..." now says "Bootloader is locked." It feels as if whatever damaged the system software also damaged the storage where locked/unlocked is stored.
I feel as if there is nothing to do at this point other than contact Asus about hardware service. Sigh.
Click to expand...
Click to collapse
Sorry to hear that! I don't remember ever hearing being able to get into the bootloader but not into recovery from there. Your probably right about having to do doing an RMA. If it's any consolation I had a good experience with ASUS when I had to RMA my 1st gen N7 32GB after the speakers went bad.

I'm glad to hear you had a good experience with ASUS support. I have an RMA and am sending it to them. Thanks for your help.

I am having the same exact problem as the OP. Stuck at the Google logo. However, I never unlocked the bootlocker since I bought it (Nexus 7 2013 32GB) back in June 2013.
When I try to go into Recovery, I also get sent back to the screen with the Google logo. It will not enter Recovery so I can Factory Reset.
Is this pretty much going to be an RMA to ASUS. I purchased at Best Buy. Think there's any chance they will exchange?

mnunez611 said:
I am having the same exact problem as the OP. Stuck at the Google logo. However, I never unlocked the bootlocker since I bought it (Nexus 7 2013 32GB) back in June 2013.
When I try to go into Recovery, I also get sent back to the screen with the Google logo. It will not enter Recovery so I can Factory Reset.
Is this pretty much going to be an RMA to ASUS. I purchased at Best Buy. Think there's any chance they will exchange?
Click to expand...
Click to collapse
I would say definitely RMA it. With you having a stock tablet it's not worth risking messing something up trying to fix your tablet and then maybe you can't RMA. I would start with Best Buy and them what their warranty period is. If it is within their stories warranty then take it to them. If not then call ASUS.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

Help me
Hello Guys I am stuck in a very annoying situation at the moment which is that my nexus 7 has become inaccessiblhttp://forum.xda-developers.com/images/smilies/eek.gife. This is how it happened
one day I tried to play the android game NOVA 3 on my Nexus 7 on the highest graphical setting so I went and researched how to do this. I was pointed towards some kind of app called 'ChainFire 3D', Once I pressed the install button inside this app the Nexus 7 switched off and the next time I tried to turn it on I got the X logo of death (boot loop). I then tried to enter recovery and I got the annoying 'no command' errohttp://forum.xda-developers.com/images/smilies/crying.gifr. I cant seem to remember how I rooted this thing but I do have access to the fastboot stuff ONLY (inside cmd).
if there is anyone who has any idea how to go about fixing such an issue without wiping everything on my nexus could they please get back to me ASAP.http://forum.xda-developers.com/images/smilies/fingers-crossed.gif
thanks in advance

I have the exact same issue as the OP. Can't get to recovery cause the Google logo hangs there. I can fastboot but the N7 is locked since it was not rooted. Using fast boot and Wugs I get the same thing where it just hangs on erasing userdata for hours. Wondering if any fix has been discovered for this since the OP issue was months ago.

Use fastboot OEM unlock command to unlock the boot loader then re flash stock.
Sent from my Nexus 7

Did I ruin my phone?

Was trying to switch from TWRP to CWM (having trouble with TWRP installing CM nightlies). I installed the latest CWM via fastboot. Seemed to load OK, but when I tried to start up the recovery, it just rebooted after showing 'Entering Recovery...' in pink at the top.
Now I'm really stuck. No matter what I do, the phone starts up, shows Entering Recovery at the top, and then shuts down. I cannot enter the bootloader. I cannot start up the phone into the ROM (which is a TikTak ROM that was working fine). Basically, I'm unable to do anything.
When the phone is plugged in, no orange charge light comes on. Vol Down + Power doesn't work. Vol Up + Power doesn't work. Either way, the phone tries to enter recovery, then shuts down.
Is there anything else I can try? Is this phone bricked?

What was the fastboot command you did? It sounds like you flashed to the wrong partition, or flashed an m7 recovery instead of an m7wlv
Sent from my HTC6500LVWBLU using XDA Free mobile app

Uzephi said:
What was the fastboot command you did? It sounds like you flashed to the wrong partition, or flashed an m7 recovery instead of an m7wlv
Sent from my HTC6500LVWBLU using XDA Free mobile app
Click to expand...
Click to collapse
fastboot flash recovery <cwm.zip> (whatever it was called)
Same way I did it for TWRP which worked perfectly.
Really need a solution here, if there is one. Currently planning on just letting the battery drain and starting again...

mobilemedic20 said:
fastboot flash recovery <cwm.zip> (whatever it was called)
Same way I did it for TWRP which worked perfectly.
Really need a solution here, if there is one. Currently planning on just letting the battery drain and starting again...
Click to expand...
Click to collapse
If you can't get a charge light while it is off, DO NOT let it die! It will not charge while dead. When it is booting, can you do adb or fastboot commands from your PC? If so, try:
ADB/fastboot reboot bootloader
Sent from my HTC6500LVWBLU using XDA Free mobile app

Usually, the command: fastboot erase cache
Will resolve such issues, though it doesn't always work, depends on what's causing the actual issue.
But that is what I would suggest trying from fastboot.

Problem is I can NOT get into the boot loader at all, unless i'm missing something. Start phone, tries to load recovery, shuts off. That's it. Is there a way to get the bootloader to open? I seem to have no options.

mobilemedic20 said:
Problem is I can NOT get into the boot loader at all, unless i'm missing something. Start phone, tries to load recovery, shuts off. That's it. Is there a way to get the bootloader to open? I seem to have no options.
Click to expand...
Click to collapse
With device powered off,
Power + volume down
Even if partially powered on, trying to load recovery,....
Same process, hold volume down and power until it boots to hboot.

santod040 said:
With device powered off,
Power + volume down
Even if partially powered on, trying to load recovery,....
Same process, hold volume down and power until it boots to hboot.
Click to expand...
Click to collapse
Tried it man, vol down + power as much as you want. It starts, tries to enter recovery (for about 3 seconds) then goes dead. The thing is, even with the screen off and I plug it into the computer, the computer recognizes the phone a little... It says 'driver not recognized' (even though they're installed). So maybe it's actually partially on in the background, and locked up? That's why I'm hoping the battery running down will fix it.
I'm literally dusting off my old galaxy nexus to get that loaded up, because I need my phone. I'm worried the One is bricked.
***Edit / update - when I plug the phone in 'off' (not responsive) mode, and try fastboot anything, it hangs saying 'waiting for device'. Whatever that means.

mobilemedic20 said:
Tried it man, vol down + power as much as you want. It starts, tries to enter recovery (for about 3 seconds) then goes dead. The thing is, even with the screen off and I plug it into the computer, the computer recognizes the phone a little... It says 'driver not recognized' (even though they're installed). So maybe it's actually partially on in the background, and locked up? That's why I'm hoping the battery running down will fix it.
I'm literally dusting off my old galaxy nexus to get that loaded up, because I need my phone. I'm worried the One is bricked.
***Edit / update - when I plug the phone in 'off' (not responsive) mode, and try fastboot anything, it hangs saying 'waiting for device'. Whatever that means.
Click to expand...
Click to collapse
You are holding down on both the volume down and the power button for as long as your fingers can stand to?
It's not a quick press of both, but a steady hold down of both buttons, even if it tries to do the recovery loading , keep holding both down.
Make sure you are pressing them both FIRMly and for at least 30 seconds or more.
If you are already trying that, then disregard.
But the way it's behaving, it doesn't sound like you are.
If so, again, disregard, just making sure you are attempting one of the only possible methods you have, correctly.
As it won't do what it's supposed to if you do not continue to hold them down, even if that entering recovery screen comes up, you need to continue holding them down.

santod040 said:
You are holding down on both the volume down and the power button for as long as your fingers can stand to?
It's not a quick press of both, but a steady hold down of both buttons, even if it tries to do the recovery loading , keep holding both down.
Make sure you are pressing them both FIRMly and for at least 30 seconds or more.
If you are already trying that, then disregard.
But the way it's behaving, it doesn't sound like you are.
If so, again, disregard, just making sure you are attempting one of the only possible methods you have, correctly.
As it won't do what it's supposed to if you do not continue to hold them down, even if that entering recovery screen comes up, you need to continue holding them down.
Click to expand...
Click to collapse
Yes, that's what I've been doing - and if I hold it down for a longer time, the phone will just cycle through. Off, "Entering recovery", off, "entering recovery", etc every 10 seconds or so. It's clearly not working.

mobilemedic20 said:
Yes, that's what I've been doing - and if I hold it down for a longer time, the phone will just cycle through. Off, "Entering recovery", off, "entering recovery", etc every 10 seconds or so. It's clearly not working.
Click to expand...
Click to collapse
Well that's too bad. Sorry to hear you're having these issues.
I noticed in your first post in this thread, you said you did this:
fastboot flash recovery cwm.zip
Was the file actually a zip?
It should have been a .img file.
Just trying to figure out what happened, as it could help in finding a resolution.
As it stands right now, there is nothing really to go off of.

Anyone, still trying to recover my phone... Here's where I'm at. I figured out that while the phone is off, if I plug it in, I can access ADB via the computer's cmd prompt, but no fastboot (says 'waiting for device'). If I use ADB to reboot the bootloader or recovery, I get the same problem - phone resets, tries to enter recovery for 2 seconds, then back off again.
Can I somehow use ADB to get the phone working again?

mobilemedic20 said:
Anyone, still trying to recover my phone... Here's where I'm at. I figured out that while the phone is off, if I plug it in, I can access ADB via the computer's cmd prompt, but no fastboot (says 'waiting for device'). If I use ADB to reboot the bootloader or recovery, I get the same problem - phone resets, tries to enter recovery for 2 seconds, then back off again.
Can I somehow use ADB to get the phone working again?
Click to expand...
Click to collapse
If you borked your boot loader where you can't access it, there isn't much we can do to help. If the phone can't boot to the boot loader, we can't do anything to help. I think the only thing you can do is send it in for JTAG.
Sent from my One using XDA Free mobile app

Uzephi said:
If you borked your boot loader where you can't access it, there isn't much we can do to help. If the phone can't boot to the boot loader, we can't do anything to help. I think the only thing you can do is send it in for JTAG.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
'Send it in for JTAG'... sorry, what does this mean?
I'm also going to try bringing it to Verizon and claiming ignorance to see if I can get a warranty replacement. What's the downside, right?

adb shell
dd if=/sdcard/LOCATIONOFHBOOT/HBOOT.img of=/dev/block/nameofblock
should work, but i have no clue what the hboot block name is and that this way is really risky. Maybe a dev can chime in and help.
http://forum.xda-developers.com/showthread.php?t=2320271
maybe pm this guy for help?

synisterwolf said:
adb shell
dd if=/sdcard/LOCATIONOFHBOOT/HBOOT.img of=/dev/block/nameofblock
should work, but i have no clue what the hboot block name is and that this way is really risky. Maybe a dev can chime in and help.
http://forum.xda-developers.com/showthread.php?t=2320271
maybe pm this guy for help?
Click to expand...
Click to collapse
Appreciate the suggestion but have no idea how to proceed with this. Read that link, even more clueless.

Download mode freezing

When I try to use fastboot to boot into custom recovery (twrp-3.0.2-7-pme-DEBUG.img), fastboot says "booting..." then hangs. HTC 10 hangs in download mode until I have to hold all buttons to hard reboot. This also happened when trying to flash cache for magisk autoroot method (before test twrp for HTC 10 nougat released).
Could this be an adb driver issue?

adamjmacdonald said:
When I try to use fastboot to boot into custom recovery (twrp-3.0.2-7-pme-DEBUG.img), fastboot says "booting..." then hangs. HTC 10 hangs in download mode until I have to hold all buttons to hard reboot. This also happened when trying to flash cache for magisk autoroot method (before test twrp for HTC 10 nougat released).
Could this be an adb driver issue?
Click to expand...
Click to collapse
Hang on, when you get into download mode you can navigate right? With the volume keys, I mean.
Also, do fastboot devices
I assume it'll show up as you're giving it a command, but it's not doing it properly.
Why not just navigate to recovery manually? Go into download mode.
Reboot to bootloader.
Reboot to recovery.
Pretty simple, really. If you're hanging on that screen, you may have an issue. Try to reflash the TWRP for N FW.
Since you said it happened before...it may be? Try another computer, if you can. If all else fails, run an RUU (last resort option).

Ariac Konrel said:
Hang on, when you get into download mode you can navigate right? With the volume keys, I mean.
Also, do fastboot devices
I assume it'll show up as you're giving it a command, but it's not doing it properly.
Why not just navigate to recovery manually? Go into download mode.
Reboot to bootloader.
Reboot to recovery.
Pretty simple, really. If you're hanging on that screen, you may have an issue. Try to reflash the TWRP for N FW.
Since you said it happened before...it may be? Try another computer, if you can. If all else fails, run an RUU (last resort option).
Click to expand...
Click to collapse
I RUU'd and retried and it worked. Hate to give a "no root cause" solution but, as you said, if all else fails...

adamjmacdonald said:
I RUU'd and retried and it worked. Hate to give a "no root cause" solution but, as you said, if all else fails...
Click to expand...
Click to collapse
Could have been that something went wrong to damage the FW, thus RUU.
We'll leave it at that.
Glad it got sorted though!