Develop Bugs

[Q] One x touch screen fail

Searched many places for my problem but cannot find it specifically and this forum seems to be more clued up than most so here goes.
One x screen started to occasionally freeze on unlock screen (volume buttons worked also the volume pop up came on so screen itself not frozen just couldnt touch input i presume) but would fix with either a full power down or a few presses of the top button. Over the course of a day or two this has progressed to virtually always freezing and finally to where i couldnt unfreeze it even after powering down.
Did a factory reset which did give me access to my phone again but still the problem persists.
From my research it could possibly be some sort of cache problem. Also noticed after factory reset with no apps or data installed, apart from the preinstalled ones, am using 4.7 gb of internal memory with only htc sense running. this seems excessive to me but never checked it before so not sure if this is about right. If not then the cache theory could be right.
So can anyone help me please.

bump

thebarran said:
Searched many places for my problem but cannot find it specifically and this forum seems to be more clued up than most so here goes.
One x screen started to occasionally freeze on unlock screen (volume buttons worked also the volume pop up came on so screen itself not frozen just couldnt touch input i presume) but would fix with either a full power down or a few presses of the top button. Over the course of a day or two this has progressed to virtually always freezing and finally to where i couldnt unfreeze it even after powering down.
Did a factory reset which did give me access to my phone again but still the problem persists.
From my research it could possibly be some sort of cache problem. Also noticed after factory reset with no apps or data installed, apart from the preinstalled ones, am using 4.7 gb of internal memory with only htc sense running. this seems excessive to me but never checked it before so not sure if this is about right. If not then the cache theory could be right.
So can anyone help me please.
Click to expand...
Click to collapse
Did you try RUU?

Not rooted my phone so was hoping to find a fix without rooting in case i have to send it back.

thebarran said:
Not rooted my phone so was hoping to find a fix without rooting in case i have to send it back.
Click to expand...
Click to collapse
Try following this:
http://forum.xda-developers.com/showthread.php?t=1859714
No need to root / unlock bootloader
EDIT: follow option 2

following option 2 but stuck.
Make sure that USB debugging is enabled (Settings/Developer options). In order to determine which ruu file you require, boot your device into bootloader mode (Power off and then restart device by holding Power and Volume Down button together). Connect to pc via USB and check that device shows FASTBOOT USB on screen. Enter the following command in command prompt:
fastboot getvar version-main
But when i enter that in Command prompt i get fastboot is not recognised command etc using windows 8. Any help
Note: my phone is locked

thebarran said:
following option 2 but stuck.
Make sure that USB debugging is enabled (Settings/Developer options). In order to determine which ruu file you require, boot your device into bootloader mode (Power off and then restart device by holding Power and Volume Down button together). Connect to pc via USB and check that device shows FASTBOOT USB on screen. Enter the following command in command prompt:
fastboot getvar version-main
But when i enter that in Command prompt i get fastboot is not recognised command etc using windows 8. Any help
Note: my phone is locked
Click to expand...
Click to collapse
Can you try running fastboot on a different OS? Windows XP/7, Ubuntu? Something else?
EDIT: BTW, are you sure you are running the fastboot command from the fastboot folder?

davidk-il said:
EDIT: BTW, are you sure you are running the fastboot command from the fastboot folder?
Click to expand...
Click to collapse
not doing this what do you mean?

thebarran said:
not doing this what do you mean?
Click to expand...
Click to collapse
Navigate on your PC to the fastboot folder lets say "c:\fastboot".
Shift+right click on any blank place and choose open command window here(or something like that my OS is not in english now).
Try using fastboot commands .

ah nice works, thanks. stay with me in case i get stuck again.

thebarran said:
ah nice works, thanks. stay with me in case i get stuck again.
Click to expand...
Click to collapse
Sorry,
Gotta get some sleep =)
If after running RUU nothing changes take the phone to service.

more problems
Ran and installed the ruu but got an
error[152]:image update error
The ROM update utility cannot update your android phone.
Please get the correct ROM update utility and try again
But i have the correct version already 3.14.401.31 it just wont install and now my phone is stuck on a black screen with htc in centre and nothing else.

Did you run the ruu.exe as a administrator ?
Right click the ruu exe and select that.....and put the phone in the bootloader/fastboot usb mode

Mr Hofs said:
Did you run the ruu.exe as a administrator ?
Right click the ruu exe and select that.....and put the phone in the bootloader/fastboot usb mode
Click to expand...
Click to collapse
tried it in admin mode still no good and cant get to any other screen on my phone now other than the black screen with htc in the middle

thebarran said:
tried it in admin mode still no good and cant get to any other screen on my phone now other than the black screen with htc in the middle
Click to expand...
Click to collapse
Phone for sure in fastboot usb mode?

davidk-il said:
Phone for sure in fastboot usb mode?
Click to expand...
Click to collapse
it was when i first did it biut cannot check no more

Hold the power button and the volume - button together until it reboots and boots into the bootloader, hook the usb cable and you should see "fastboot usb" in red text. At that point you run the ruu with administrator rights

Mr Hofs said:
Hold the power button and the volume - button together until it reboots and boots into the bootloader, hook the usb cable and you should see "fastboot usb" in red text. At that point you run the ruu with administrator rights
Click to expand...
Click to collapse
i cannot. all that happens now is that it powers down and comes back to the black htc screen. cannot get to boot screen anymore.

thebarran said:
i cannot. all that happens now is that it powers down and comes back to the black htc screen. cannot get to boot screen anymore.
Click to expand...
Click to collapse
Try shutting of the phone, powering on when holding power button+volume down for about 8s.
You will get a hboot, choose fastboot connect usb cable and try ruu with admin permissions

finally did get to hboot screen by letting the phone shutdown itself but couldnt ruu as battery power to low so i powered down and recharged battery but back to square one where i cannot get to boot screen just constant black htc screen and cant power down again.
So ill let my battery run down again to power off completely open boot screen then stay on that til i power up enough to try ruu again.
Il let you know what happens when this is done later.

PC won't recognize phone in fastboot mode

Tried to flash Carbon rom. Fastboot flashed boot.img then when I tried to flash rom in recovery it failed. So when I tried to go back to fastboot mode and flash another boot.img to restore a nandroid my phone isn't being recognized. Interestingly, when I go back into recovery my phone is recognized. But I need to install the boot.img first but can't d/t phone not being recognized.
Any help out there? Where's Mr. Hofs when I need him? lol

Used the original cable ?
Not used a usb hub ?
Try it on another windows pc ?

Mr Hofs said:
Used the original cable ?
Not used a usb hub ?
Try it on another windows pc ?
Click to expand...
Click to collapse
Ha! There you are.
Yes, original cable. What you mean by a usb hub? And don't have another PC...

scott62185 said:
Ha! There you are.
Yes, original cable. What you mean by a usb hub? And don't have another PC...
Click to expand...
Click to collapse
Yep hi mate
I mean using a direct usb 2.0 port on the pc ....
Otherwise reboot everything ! And can you erase cache first ?
Fastboot erase cache
What's the exact error ? Waiting for device ......

Mr Hofs said:
Yep hi mate
I mean using a direct usb 2.0 port on the pc ....
Click to expand...
Click to collapse
Okay, I'll try it in a usb port on the back of my computer.

It says, "device driver was not successfully installed" even though it was before I started this whole process.
Also, when I put it into recovery and plug it in, the charging light still does not come on...

scott62185 said:
It says, "device driver was not successfully installed" even though it was before I started this whole process.
Also, when I put it into recovery and plug it in, the charging light still does not come on...
Click to expand...
Click to collapse
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.

Mr Hofs said:
Keep the phone connected and reboot the recovery , the led should come on then.
Keep the phone connected in the bootloader and reboot the pc.
Click to expand...
Click to collapse
Okay, I'll try that. be right back

Didn't work...

Weird .....
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?

Mr Hofs said:
Weird .....
When the phone is in the bootloader is it recognized as fastboot usb (in red text) and what does the device manager in windows say about a android phone ?
Click to expand...
Click to collapse
I had it so fastboot was in blue text...is that wrong?
Okay, changed it so the fastboot is in red text (duh! lol). Tried the whole process and carbon rom still aborted (didn't flash). But at least I was able to apparently flash the boot.img via fastboot. Unfortunately, I still don't see the charging light while in recovery, and I need to leave to go take care of something. I did see it once when it was plugged in on the bootscreen...

scott62185 said:
I had it so fastboot was in blue text...is that wrong?
Click to expand...
Click to collapse
Well there is a text that says "fastboot" and as soon as you connect it to the pc it should turn into "fastboot usb"
What does this command give back
Fastboot devices

Mr Hofs said:
Well there is a text that says "fastboot" and as soon as you connect it to the pc it should turn into "fastboot usb"
What does this command give back
Fastboot devices
Click to expand...
Click to collapse
Should I leave it plugged in w/ the boot screen since that has the charging light on?

It should be in the bootloader where it says
All bootloader info
Here it should say "fastboot usb"
Hboot
Reboot
******* (can't recall)
Power down
Then perform the command
Fastboot devices

Mr Hofs said:
It should be in the bootloader where it says
All bootloader info
Here it should say "fastboot usb"
Hboot
Reboot
******* (can't recall)
Power down
Then perform the command
Fastboot devices
Click to expand...
Click to collapse
So, I had to leave the house and now I'm out and about. I left it plugged in with the splash screen as that enabled the charging light. I hope that was the right decision. I'll check back in tonight when I get home. Thanks!
Sent from my Nexus 4 using xda premium

scott62185 said:
So, I had to leave the house and now I'm out and about. I left it plugged in with the splash screen as that enabled the charging light. I hope that was the right decision. I'll check back in tonight when I get home. Thanks!
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
the device won't charge if it is in the bootloader

So, I'm able to get fastboot mode working (flashed boot.img) BUT whenever I try to flash a rom (I've tried Carbon and Slim), it says "installation aborted" [assert failed: getprop ("ro bootloader")]
Any ideas on what's going wrong? Do you guys have advice on which other rom to try and flash?
My hboot is 1.23, by the way.

scott62185 said:
So, I'm able to get fastboot mode working (flashed boot.img) BUT whenever I try to flash a rom (I've tried Carbon and Slim), it says "installation aborted" [assert failed: getprop ("ro bootloader")]
Any ideas on what's going wrong? Do you guys have advice on which other rom to try and flash?
My hboot is 1.23, by the way.
Click to expand...
Click to collapse
Okay, now it's completely dead. I guess I didn't figure it out in time. Do I have any recourse?

Yeh the hboot is to low, we get it charging. Leave it on the charger while the phone is off. We will pick it up on gtalk

Mr Hofs said:
Yeh the hboot is to low, we get it charging. Leave it on the charger while the phone is off. We will pick it up on gtalk
Click to expand...
Click to collapse
Okay, I plugged it back in. But can it charge if it's already dead?

[Q] HTC Desire HD Bricked bootloader not loading and cannot connect to pc need help

Good day!
After searching everywhere in the web and using different methods, I decided to create an account and ask you guys how to solve my problem
Basically, I have a HTC Desire HD phone, this is unlocked, rooted and using cm-Jellytime_42_R11 ROM. I decided to change ROM and go back to Android Revolution. What I did first was I deleted a couple of folders in my clockwork folder, I deleted both backup to free space. Afterwards, I was trying to connect my phone to my laptop but to no avail (it only charged) then I decided to just boot into recovery. After a couple of tries trying to access and going to bootloader/recovery mode it just wont push through. So I decided to normal boot, then the phone won't boot anymore. It just hanged in the Jellytime loading screen.
Note: I removed the battery a couple of too many times since I was trying to boot into recovery.
Thanks in advance to anyone who can help me with this problem

I didn't understand very well.
Can you now go to Hboot screen volume (-) + power button?
And where you get now stucked when you just power on phone?

Gussta said:
I didn't understand very well.
Can you now go to Hboot screen volume (-) + power button?
And where you get now stucked when you just power on phone?
Click to expand...
Click to collapse
no, i couldnt go to Hboot while holding down volume - and power.
The phone gets stucked in the Jellytime loading screen. It just stops. help me please

What does it do when you try to go to hboot? Is it detected in fastboot? Is it detected in adb when you try to boot normally?

bananagranola said:
What does it do when you try to go to hboot? Is it detected in fastboot? Is it detected in adb when you try to boot normally?
Click to expand...
Click to collapse
it does nothing. It just cant go to hboot. it wont normal boot too. so stuck.

richardrip10 said:
it does nothing. It just cant go to hboot. it wont normal boot too. so stuck.
Click to expand...
Click to collapse
WHen it getts stuck in the roms boot animation, connect usb to the phone and try
Code:
adb devices
Most devices show up via adb during the boot animation.
If the device shows up there, enter
Code:
adb reboot bootloader
then go here and download 4ext recovery.
extract the .img file from the zip. Rename it to recovery.img and place it in your adb directory and enter this whiles in fastboot
Code:
fastboot devices
to make sure your device shows up
then
Code:
fastboot flash recovery recovery.img
after it has successfully flashed reboot to recovery ad try and flash the rom u want.
hope i helped. Click on the thanks buttton.
You can ask if you still have problems.

computer doesn't recognize android. laptop doesnt even make sound that a device has been connected. I checked the device manager but to no avail. but the phone is charging.

richardrip10 said:
computer doesn't recognize android. laptop doesnt even make sound that a device has been connected. I checked the device manager but to no avail. but the phone is charging.
Click to expand...
Click to collapse
What recovery were you using before this happened?

mickeyasamoah said:
What recovery were you using before this happened?
Click to expand...
Click to collapse
cwm sir.

richardrip10 said:
cwm sir.
Click to expand...
Click to collapse
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.

mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
sorry, it still didn't work. Is this a bricked phone?

mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
btw, my computer really cant detect my phone. It doesnt make any sound when it is connected through USB. but other devices can be detected by my computer. I tried inserting the usb into a 2.0 and 3.0 usb.

mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
hey bro, I actually made it work. problem is when im flashing the recovery, it shows Failed<remote: not allowed>
what should I do?

mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
no worries now brother! was able to fix my phone now! THANK YOU SO MUCH! :good::good::good:

richardrip10 said:
no worries now brother! was able to fix my phone now! THANK YOU SO MUCH! :good::good::good:
Click to expand...
Click to collapse
Okay Brother.. Guess you should post how you fixed it in the OP so that others with the same problem can look it up.

mickeyasamoah said:
Okay Brother.. Guess you should post how you fixed it in the OP so that others with the same problem can look it up.
Click to expand...
Click to collapse
Ok, so basically, the problem why i can't do the power button + vol (-) is that my volume buttons are broken. (sad) Second, the reason why my computer wasn't detecting my phone is that my phone's charging slot is dirty and I had to clean it with a needle to remove the dust, at the same time, the cable I was using was broken. When I was able to clean the slot and change cables, I then followed the steps by mickeyasamoah (thanks bro) with the adb procedures. Although it failed when it was in the flash recovery line (dunno why), I just proceeded into flashing a new ROM and voila, it worked.

richardrip10 said:
Ok, so basically, the problem why i can't do the power button + vol (-) is that my volume buttons are broken. (sad) Second, the reason why my computer wasn't detecting my phone is that my phone's charging slot is dirty and I had to clean it with a needle to remove the dust, at the same time, the cable I was using was broken. When I was able to clean the slot and change cables, I then followed the steps by mickeyasamoah (thanks bro) with the adb procedures. Although it failed when it was in the flash recovery line (dunno why), I just proceeded into flashing a new ROM and voila, it worked.
Click to expand...
Click to collapse
I am happy i was able to help.
Instead of saying thanks only, you could actually hit the thanks button.
Have a nice day.

[Q] Using Nexus Root Toolkit without USB Debugging enabled

I have a 2013 Nexus 7 wifi tablet, bootloader locked, with USB debugging disabled. It decided mid-activity that all it would like to do in life is display the "Google" image on the boot up screen.
I can access the bootloader so I tried doing the standard wipe in recovery mode but that did not work.
Investigated Wugfresh's Nexus Root Toolkit. Drivers (Windows 7) are installed but under Step 4 of the Full Driver Configuration guide it is unable to find the device as an ADB device, even though the device does show up on my Device Manager (but only as bootloader interface, not ADB). Tried to use the unlock feature anyway but on the tablet it just gets stuck on the "unlock bootloader" screen after trying to run the unlock tool (choosing "yes" by pressing the up volume button to scroll to the yes option, followed by the power button to select it).
My questions based on this are simple:
1) Can I unlock this device without having USB debugging enabled? If so, how?
2) Can I restore to factory stock settings without having USB debugging enabled (and not using recovery mode on the device itself, as that does not work)? If so, how?
All of the tools I have seen thus far require that USB debugging be enabled on the device. Since I can't actually boot up the device, there is no way to make this happen. I don't really care about any of the data on the device, I just want it to function again to avoid buying a new one.

Stop using a toolkit. Your device will never be recognized by adb when booted into the bootloader.
Unlocking the bootloader is simple if you have the Windows drivers set up correctly. Open command prompt with admin privileges, type 'fastboot oem unlock' and done. This is why I hate toolkits.

nhizzat said:
Stop using a toolkit. Your device will never be recognized by adb when booted into the bootloader.
Unlocking the bootloader is simple if you have the Windows drivers set up correctly. Open command prompt with admin privileges, type 'fastboot oem unlock' and done. This is why I hate toolkits.
Click to expand...
Click to collapse
I believe this also requires that USB Debugging be enabled. I would paste links but the forum prevents me from doing so since I just signed up.
If I am incorrect in thinking that USB Debugging must be enabled for this to work, then please let me know. All I really need is clear instructions on how to hard reset the device without USB debugging enabled. Unlocking just seems to be a prerequisite for that in most of the tutorials I have found so far.

You can flash the device back to stock with wugs without adb. There should be an option you pick under the factory restore button that says "soft bricked" which tells wugs that it needs to go straight fastboot mode instead of trying to restart the tablet with adb.

skrypj said:
You can flash the device back to stock with wugs without adb. There should be an option you pick under the factory restore button that says "soft bricked" which tells wugs that it needs to go straight fastboot mode instead of trying to restart the tablet with adb.
Click to expand...
Click to collapse
Thanks for your reply. I have tried this option without the ADB (but with my computer recognizing the device). Since it did not work I expect the device is well and truly screwed (the recovery mode factory reset also does not work on the tablet itself).

Bugnerd said:
Thanks for your reply. I have tried this option without the ADB (but with my computer recognizing the device). Since it did not work I expect the device is well and truly screwed (the recovery mode factory reset also does not work on the tablet itself).
Click to expand...
Click to collapse
Couple of things:
1. You may also have a driver issue, I was playing with this the other day on both my Nexus 5 and Nexus 7. My nexus 5 worked fine, but later that day when i tried my nexus 7 I had troubles with my PC recognizing the N7 in fastboot mode. It would be fine in ADB and would reboot, but then the computer would freak out when it saw the fastboot device. Sometimes it would kinda work, sometimes the N7 would freeze on the bootloader screen or fail to flash during the process. It even locked my PC at one point. I completely uninstalled(per the Step 1 instructions in Wug's) all Android associated drivers(Samsung, LG, Asus, whatever. Kill them all) on the PC and reinstalled and it solved the issues. It sounds like maybe your PC is failing to flash properly like mine was.
2. Not sure if you tried this yet but; go to Options Menu>Flash Stock Tab>Check "Enable 'Force Flash Mode' . . . " Then try to flash stock + unroot again with the soft-bricked option selected. This basically makes Wug's ignore the check process at the beginning of the flash. I had to do this for both my N5 and N7.
Keep in mind, you will lose EVERYTHING on your N7 if you unroot and flash, including your internal storage.

Yeah, it does not seem to want to do the unroot + flash even with the override of checks. It seems unlocking is really a prerequisite for that tool (according to the text that appears as it proceeds), and unlocking appears to require the USB debugging. If it really can be unlocked without that, then it is not cooperating and just getting stuck on the unlocking screen. I expect it is now a very expensive paperweight.
All of this nonsense just over a year since I bought it, of course.

Try it with another computer, another USB cable...

I'm in the same boat, can't get it to unlock so it's essentially dead now
I've tried original and a G3 usb cord and nothing, front and rear USB ports, just will not unlock, almost to the point of sending it on and paying to get it fixed if possible , will try another computer first

Can you boot manually into fasboot mode and do flashing full stock firmware for ur device..
Bcoz I thinks you don't need usb debugging when on fastboot mode..
if you want to use toolkit, you must setup all driver for ur device first using the toolkit.. but you must do it when ur device is full "working", not when It's just stuck on google image... that's ur main problem now ...
you should try install the driver again on new "fresh" pc ....
Good luck bro... :fingers-crossed:

Did you try to manually unlock it? Boot to the boot loader screen(down volume+power) and the fastboot unlock it using the cmd in windows?

Az-one786 said:
Can you boot manually into fasboot mode and do flashing full stock firmware for ur device..
Bcoz I thinks you don't need usb debugging when on fastboot mode..
if you want to use toolkit, you must setup all driver for ur device first using the toolkit.. but you must do it when ur device is full "working", not when It's just stuck on google image... that's ur main problem now ...
you should try install the driver again on new "fresh" pc ....
Good luck bro... :fingers-crossed:
Click to expand...
Click to collapse
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
I can try the drivers again on another PC, but I have a feeling that won't fix anything.

skrypj said:
Did you try to manually unlock it? Boot to the boot loader screen(down volume+power) and the fastboot unlock it using the cmd in windows?
Click to expand...
Click to collapse
I looked into this a week or so ago and I think I determined that it would also require the USB debugging to be on (at least from the tutorials). Do you have any recommendations of tutorials on this process? Screwing around with this stuff is not really my bag.

Bugnerd said:
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
I can try the drivers again on another PC, but I have a feeling that won't fix anything.
Click to expand...
Click to collapse
Ok.., Your have no choice by now, you'll need to find a working driver for your PC to get recognize your tablet when on fastboot mode..
I've got this issues before when I want to update my tab using toolkit...
My PC can recognized my tab as adb devices, but when it's reboot to check fastboot status it fail to detect my device is on fastboot mode..
But maybe I'm so lucky that day, Moboginie notification has pop-up and it's has searching and found the driver and fix it itself ...
Then i try again and this time it's has no problem at all till now... I still can access my storage using Moboginie but until now window explorer still fail to recognized my N7...
It's so weird isn't it ...

Try Moborobo

Bugnerd said:
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
Click to expand...
Click to collapse
After the recovery screen with "sick" Andy, did it automatically begin to reboot? If not, you know that it's very tricky with the power+vol up button (sometimes I think it's power+both volume buttons that works) to access that screen in recovery (the one past sick Andy). Sometimes I've tried five or six times. I have twrp so I can't check it out right now.
As far as adb/fastboot drivers set up to run any commands, I thought they were required. I'm not certain about USB debugging. It seems you've tried with your device in fastboot and running Cmd (fastboot oem unlock) from your fast boot directory. Do you get a device code when you enter [fastboot devices] while in that directory? If not, your N7 will not accept fastboot commands.
Sent from my Nexus 7 using Tapatalk

[Q] Phone stuck in bootloop, can't flashboot anything. Suggestions?

Ahh my phone has had quite the past week on this CM12 Android 5.0 ROM...
I was just listening to music and checking social media on my phone when bam, it turns off.
I held the power button and it didn't turn on the first few times.
Then finally, it boots, but it won't get past the splash screen.
It's stuck in a bootloop and I can't get into the recovery. I can't factory reset it either.
I tried to go to fastboot and flash the recovery again, but my computer doesn't recognize my phone.
I have adb, fastboot, and all of the correct drivers installed and it won't do anything.
I tried flashing with "fastboot flash recovery twrp.img" but it just said "<waiting for device>" even though my phone was connected and in fastboot mode.
I don't know what to do. I can't boot it, I can't get into recovery, I can't factory reset it, and I can't fastboot anything.
What should I do? Please I am open to ANY suggestions at this point. I can't deal with this constantly not having a phone crap.
Thanks, it'll be much appreciated.
Extra Info:
Device manager lists my phone as this: "Unknown USB Device (Device Failed Enumeration)"
Every time I go into fastboot, my computer displays this message: "USB device not recognized. The last USB device you connected to this computer malfunctioned, and Windows does not recognize it"

SyrStorm said:
Ahh my phone has had quite the past week on this CM12 Android 5.0 ROM...
I was just listening to music and checking social media on my phone when bam, it turns off.
I held the power button and it didn't turn on the first few times.
Then finally, it boots, but it won't get past the splash screen.
It's stuck in a bootloop and I can't get into the recovery. I can't factory reset it either.
I tried to go to fastboot and flash the recovery again, but my computer doesn't recognize my phone.
I have adb, fastboot, and all of the correct drivers installed and it won't do anything.
I tried flashing with "fastboot flash recovery twrp.img" but it just said "<waiting for device>" even though my phone was connected and in fastboot mode.
I don't know what to do. I can't boot it, I can't get into recovery, I can't factory reset it, and I can't fastboot anything.
What should I do? Please I am open to ANY suggestions at this point. I can't deal with this constantly not having a phone crap.
Thanks, it'll be much appreciated.
Extra Info:
Device manager lists my phone as this: "Unknown USB Device (Device Failed Enumeration)"
Every time I go into fastboot, my computer displays this message: "USB device not recognized. The last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
Click to expand...
Click to collapse
Make sure you aren't connected via usb to your computer when you attempt to force a reboot. It should be vol up and power until it reboots and then switch to vol down to enter hboot.

dottat said:
Make sure you aren't connected via usb to your computer when you attempt to force a reboot. It should be vol up and power until it reboots and then switch to vol down to enter hboot.
Click to expand...
Click to collapse
I can get into hboot and all that just fine. The phone won't boot, and I can't get into recovery is my problem. Oh and the fact that the computer doesn't recognize my phone in fastboot

Update: I just whipped out a really old computer running Windows XP and I installed the platform-tools and HTC One drivers on it. I hooked the phone up to the computer, and the drivers worked. I flashed TWRP and it flashed successfully according to fastboot, but it won't go into recovery still. What should I do now? I know I can RUU somehow (I'm not really sure how though), but I want to try and avoid that, if possible. Any suggestions? Thanks people!
EDIT: NVM it actually booted! What a success! This stuff is crazy!