Database Info

Need help with my Transformer and don't know where else to look.

So I have my TF101, updated to the ICS release when it came out, rooted of course.
Since then it was kind of unstable. When not using the device it would appear to power off, but pressing the power button for about 10 seconds would bring it back up.
I noticed the recovery was not available after the update, but paid it no mind for that time.
Then out of nowhere the device screen will not turn on. After long pressing the power button a click noise can be heard, it's supposed to be the camera. Since it wasn't responding, I though it was bricked.
Then connecting it to the PC will let me access all the files on the device, something very weird.
I have tried various combinations of things after a very long and tedious search, nothing seems to work.
Here are the symptoms:
-The device is turned on, but no backlight or sound.
-When long pressing the power button click sound is heard.
-When connected to the PC via usb the files on the device can be accessed.
-ADB is accessible and the device can be rebooted via it.
-After rebooting the device via the power button or ADB usb comes up almost immediately, I don't think this happens when booting normally.
So basically, is the device bricked? Why can I access files from it? How can I push a working recovery for the TF101? Is it possible to flash a ROM from ADB?
I know these are a lot of questions, but I tried, and failed. Haven't found a case like this online, and my ADB experience is limited to adb shell and reboot
Thanks in advance for the help!

Hi Cronoadvan,
looks like your screen is dead, if you check q&A you see that more people have the same thing lately.
Is your device SBK1? so, are you able to use nvflash?

Cronoadvan said:
So I have my TF101, updated to the ICS release when it came out, rooted of course.
Since then it was kind of unstable. When not using the device it would appear to power off, but pressing the power button for about 10 seconds would bring it back up.
I noticed the recovery was not available after the update, but paid it no mind for that time.
Then out of nowhere the device screen will not turn on. After long pressing the power button a click noise can be heard, it's supposed to be the camera. Since it wasn't responding, I though it was bricked.
Then connecting it to the PC will let me access all the files on the device, something very weird.
I have tried various combinations of things after a very long and tedious search, nothing seems to work.
Here are the symptoms:
-The device is turned on, but no backlight or sound.
-When long pressing the power button click sound is heard.
-When connected to the PC via usb the files on the device can be accessed.
-ADB is accessible and the device can be rebooted via it.
-After rebooting the device via the power button or ADB usb comes up almost immediately, I don't think this happens when booting normally.
So basically, is the device bricked? Why can I access files from it? How can I push a working recovery for the TF101? Is it possible to flash a ROM from ADB?
I know these are a lot of questions, but I tried, and failed. Haven't found a case like this online, and my ADB experience is limited to adb shell and reboot
Thanks in advance for the help!
Click to expand...
Click to collapse
Since no ASUS logo is displayed, it is likely a hardware problem. Maybe you can try to bring it into recovery mode by pressing power + vol down button.

nlheiz said:
Hi Cronoadvan,
looks like your screen is dead, if you check q&A you see that more people have the same thing lately.
Is your device SBK1? so, are you able to use nvflash?
Click to expand...
Click to collapse
I am not sure, how do I check that? nvflash, at least the version I'm trying to use, won't run on win764? It's rather confusing.
tingtan said:
Since no ASUS logo is displayed, it is likely a hardware problem. Maybe you can try to bring it into recovery mode by pressing power + vol down button.
Click to expand...
Click to collapse
The screen does not light up at all, and USB is accessible after around 4 secs of long pressing power and hearing the click noise(camera?) which is not normal since no device boots so fast. This tablet never did anyway, taking from 20 to 30 secs.
After USB is available I can adb shell from windows but that's pretty much it, I don't know what to do afterwards.

Cronoadvan said:
I am not sure, how do I check that? nvflash, at least the version I'm trying to use, won't run on win764? It's rather confusing.
Click to expand...
Click to collapse
Check your serial number. If its below B70 you got SBK1.

Goatshocker said:
Check your serial number. If its below B70 you got SBK1.
Click to expand...
Click to collapse
Yes it is, it's B50. Is that a bad thing?

Cronoadvan said:
Yes it is, it's B50. Is that a bad thing?
Click to expand...
Click to collapse
Hi Cronoadvan,
thats not bad, this means that you could use nvflash to put a new image on your TF if you want to to make sure that it is working. If you use this forum:
http://forum.xda-developers.com/showthread.php?t=1558170
then it wil be stock again, and if needed you can then send your TF back for repair.
If you look and search in development you will find some ways how to use nvflash. like this one
http://forum.xda-developers.com/showthread.php?p=22465766
Hope this helps.....

nlheiz said:
Hi Cronoadvan,
thats not bad, this means that you could use nvflash to put a new image on your TF if you want to to make sure that it is working. If you use this forum:
http://forum.xda-developers.com/showthread.php?t=1558170
then it wil be stock again, and if needed you can then send your TF back for repair.
If you look and search in development you will find some ways how to use nvflash. like this one
http://forum.xda-developers.com/showthread.php?p=22465766
Hope this helps.....
Click to expand...
Click to collapse
Thank you so much! That was my last resort and sadly was clueless on how to do that too!
Hopefully it's just some kind of weird software coma, but now even if it's a hardware problem there is still hope!
Thank you very much good Sir, may life repay you thrice as much

Your welcome......please read the apx and nvflash option really well. It is rather straightforward but you have to install the apx drivers correct and use power and volume + (together) to enter apx mode. Voor drivers maybe you can use this forum below:
http://forum.xda-developers.com/showthread.php?t=1185104
it had an option for installing apx drivers for win 7 64 bit.
Hope your screen will work again, and if not you can send it back without warrant loss...
good luck!!!!!

nexus s power button not working

im stuck in the loading animation of ICS right now and my phone wont start, since my power button is broken i cant boot into recovery to wipe cache... is there some way i can boot into recovery console without the power button? can i used odin to start into recovery console?
please help!

if your phone is off the only way to connect it to your pc is booting it(bootloader or normally).. so power button is the only way. I was using android sdk and the toolkit but I hope there is a program for this situation even if I don't think so
instead if you can start your phone in bootloader mode but when you boot it loops in the starting animation means there is something wrong with your rom/kernel and you have to flash something new (you can do it in fastboot mode using one of the two programs I've mentioned before)
However I've not understand the situation fully... if your power button is broken how can you be in the loading animation??? :/

serafo said:
if your phone is off the only way to connect it to your pc is booting it(bootloader or normally).. so power button is the only way. I was using android sdk and the toolkit but I hope there is a program for this situation even if I don't think so
instead if you can start your phone in bootloader mode but when you boot it loops in the starting animation means there is something wrong with your rom/kernel and you have to flash something new (you can do it in fastboot mode using one of the two programs I've mentioned before)
However I've not understand the situation fully... if your power button is broken how can you be in the loading animation??? :/
Click to expand...
Click to collapse
i can restart the phone by putting a USB or power cord into the phone, i cant turn it on with the power button.. because of that is why i cant get to recovery console, but i can get into the bootloader screen, but none of my buttons work there... also i got a jig USB, so i can get into download mode, but im missing the files to use ODIN to re-image the phone...

WolfShooterX said:
i can restart the phone by putting a USB or power cord into the phone, i cant turn it on with the power button.. because of that is why i cant get to recovery console, but i can get into the bootloader screen, but none of my buttons work there... also i got a jig USB, so i can get into download mode, but im missing the files to use ODIN to re-image the phone...
Click to expand...
Click to collapse
I'm not familiar with odin but if you can boot your phone in fastboot mode I think you can flash every file or make a wipe from your pc like with sdk for example.. you have just to search for the commands.. sorry if I can't be helpful

Did you explore the idea of repairing your power button ? Seems like a good solution

petenatas said:
Did you explore the idea of repairing your power button ? Seems like a good solution
Click to expand...
Click to collapse
lol, yeah... but want to boot it at least.... which i did with Odin :victory:
now, does anyone know where i can get the files to root a nexus s with odin?

WolfShooterX said:
lol, yeah... but want to boot it at least.... which i did with Odin :victory:
now, does anyone know where i can get the files to root a nexus s with odin?
Click to expand...
Click to collapse
I have never used Odin with Nexus S, never needed that. As you are able to boot, you may look at the following thread to get the script for rooting your phone.
http://forum.xda-developers.com/showthread.php?t=1544940
Remember, this process will unlock the boot loader if it is locked and unlocking boot loader will delete all files, even from the internal SD card. So you may consider having a complete backup on your computer.

I make a little trick to fix this case. I disassembled my phone for get motherboard with button in my hands. After it I "played" with power button: push, sway from side to side and kick it by finder nail. After all assembled phone and now the power button works fine.

Nexus S boot problem

Here's the problem..my Nexus S power button isn't working, so I was using other hardware keys to shut down, turn on and such. Now I got into a problem. I installed chainfire3d drivers and now the phone won't boot and since my power button is broken, I can't access recovery. I can get into fastboot but the volume up/volume down buttons won't work so I can't select the option "RECOVERY" plus my PC doesn't recognize that my phone is in fastboot (I'm using Windows 8, 64bit.)
Can someone help me with this, if it's possible? How do I get into recovery?
Thank you in advance.

SlashSpeed said:
Here's the problem..my Nexus S power button isn't working, so I was using other hardware keys to shut down, turn on and such. Now I got into a problem. I installed chainfire3d drivers and now the phone won't boot and since my power button is broken, I can't access recovery. I can get into fastboot but the volume up/volume down buttons won't work so I can't select the option "RECOVERY" plus my PC doesn't recognize that my phone is in fastboot (I'm using Windows 8, 64bit.)
Can someone help me with this, if it's possible? How do I get into recovery?
Thank you in advance.
Click to expand...
Click to collapse
There might be several solutions to your problem. According to what youve written it seems that the powerbutton is stuck in the "ON" position, right? Meaning that the phone turns on when you insert the battery. It would also mean that in bootloader you cant select anything because the powerbutton is "pressed". Sadly if this is the case, having properly working drivers wouldnt help since phone wont be detected until the powerbutton is in the "OFF" position.
Case 1: powerbutton in "ON" position
Solution 1: Send your phone to repair. Sadly you will have to pay for that since your warranty is void (unlocking the bootloader voids the warranty as far as i know". Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Solution 2: Since your warranty is void, do it yourself. NS disassembly is quite easy and theres nothing to be afraid of. In this case theres just some dust so once you také it appart and clean the powerbutton it should work again. Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Case 2: powerbutton in "OFF" position
There are plenty of tutorials around here on getting drivers to work. General advice would be reinstall the drivers, try different ports, try to do it from other computer.
Hope this helps, good luck

cahir_cz said:
There might be several solutions to your problem. According to what youve written it seems that the powerbutton is stuck in the "ON" position, right? Meaning that the phone turns on when you insert the battery. It would also mean that in bootloader you cant select anything because the powerbutton is "pressed". Sadly if this is the case, having properly working drivers wouldnt help since phone wont be detected until the powerbutton is in the "OFF" position.
Case 1: powerbutton in "ON" position
Solution 1: Send your phone to repair. Sadly you will have to pay for that since your warranty is void (unlocking the bootloader voids the warranty as far as i know". Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Solution 2: Since your warranty is void, do it yourself. NS disassembly is quite easy and theres nothing to be afraid of. In this case theres just some dust so once you také it appart and clean the powerbutton it should work again. Having the button unstuck would allow you to choose recovery with volume buttons and accept with power.
Case 2: powerbutton in "OFF" position
There are plenty of tutorials around here on getting drivers to work. General advice would be reinstall the drivers, try different ports, try to do it from other computer.
Hope this helps, good luck
Click to expand...
Click to collapse
Hey, thanks for the help, much appreciated. I'll try to open the case and clean the power button if possible and see if it's gonna work then.
On the other note, after 3 hours of searching I finally found the right solution. When on the Google screen, Windows recognized the phone as "Nexus". I clicked on it in device manager and installed Android ADB interface driver (which I downloaded via SDK manager). Windows then recognized the device in cmd via adb and I could reboot into recovery with the command "adb reboot recovery".
What a relief! :victory:

SlashSpeed said:
Hey, thanks for the help, much appreciated. I'll try to open the case and clean the power button if possible and see if it's gonna work then.
On the other note, after 3 hours of searching I finally found the right solution. When on the Google screen, Windows recognized the phone as "Nexus". I clicked on it in device manager and installed Android ADB interface driver (which I downloaded via SDK manager). Windows then recognized the device in cmd via adb and I could reboot into recovery with the command "adb reboot recovery".
What a relief! :victory:
Click to expand...
Click to collapse
Congratulations Never knew you can use adb while booting Good luck with the cleaning

Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..

SlashSpeed said:
Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..
Click to expand...
Click to collapse
well get in to fastboot menu and original flash firmware
should i take u step by step? or u have some idea of fastboot?

uxmanz said:
well get in to fastboot menu and original flash firmware
should i take u step by step? or u have some idea of fastboot?
Click to expand...
Click to collapse
I can get into the fastboot menu, but I can't use the volume up/down buttons and I don't think that my computer recognizes the device in fastboot at all, because of the broken power button. If you could help me somehow, then I would really be in your debt.

SlashSpeed said:
Well I'm just..brilliant to say the least. After I fixed everything I tried to install the Chainfire3D driver again, this time with no EGL and well, same thing happened, no boot. Stuck on Google screen, just that this time, Windows recognizes the device as "google file-cd gadget usb device" not as "Nexus" or "ADB interface". Damn it...
Edit: Well, I'm clueless now...any help would be appreciated..
Click to expand...
Click to collapse
Asking for it aren't you?
Chainfire isn't compatible with Jellybean. Seriously.
Google-file CD Gadget USB Device is what becomes detected as "Nexus" later in the boot process. Have you tired detecting devices with adb devices?

polobunny said:
Asking for it aren't you?
Chainfire isn't compatible with Jellybean. Seriously.
Google-file CD Gadget USB Device is what becomes detected as "Nexus" later in the boot process. Have you tired detecting devices with adb devices?
Click to expand...
Click to collapse
Yeah...learned it the hard way..I'm too stubborn sometimes. Chainfire3D actually worked on CM10 on the Optimus Black, seems like here it wasn't the case..
Anyway, about that, yeah, I did and it doesn't detect it. Can I somehow turn the CD gadget USB device back into Nexus, like it was before or?

SlashSpeed said:
Yeah...learned it the hard way..I'm too stubborn sometimes. Chainfire3D actually worked on CM10 on the Optimus Black, seems like here it wasn't the case..
Anyway, about that, yeah, I did and it doesn't detect it. Can I somehow turn the CD gadget USB device back into Nexus, like it was before or?
Click to expand...
Click to collapse
I believe you could always enter download mode and ODIN back to stock in the worst case scenario.

polobunny said:
I believe you could always enter download mode and ODIN back to stock in the worst case scenario.
Click to expand...
Click to collapse
I tried that, but nothing happened, I couldn't enter download mod, probably because the power button is broken and it's probably on "ON".

SlashSpeed said:
I tried that, but nothing happened, I couldn't enter download mod, probably because the power button is broken and it's probably on "ON".
Click to expand...
Click to collapse
If you can enter bootloader mode you can enter download mode.

polobunny said:
If you can enter bootloader mode you can enter download mode.
Click to expand...
Click to collapse
I can enter download mode by holding down Volume Up and Volume Down together right? It doesn't work sadly..

SlashSpeed said:
I can enter download mode by holding down Volume Up and Volume Down together right? It doesn't work sadly..
Click to expand...
Click to collapse
Make sure your phone is connected to your PC. Then hold VOL down and press power if I recall correctly. It might be both volume keys together that you hold, but either way you need to make sure you phone is connected to your computer.

polobunny said:
Make sure your phone is connected to your PC. Then hold VOL down and press power if I recall correctly. It might be both volume keys together that you hold, but either way you need to make sure you phone is connected to your computer.
Click to expand...
Click to collapse
Tried both, with just volume down and volume down + up and nothing. My phone was connected to the PC. I can only enter the bootloader..

SlashSpeed said:
Tried both, with just volume down and volume down + up and nothing. My phone was connected to the PC. I can only enter the bootloader..
Click to expand...
Click to collapse
If you hold the middle of the volume key while connecting the USB cable (not pressing power) do you see anything?

polobunny said:
If you hold the middle of the volume key while connecting the USB cable (not pressing power) do you see anything?
Click to expand...
Click to collapse
I can't do that, because as soon as I plug in the battery the phone turns on..but yeah, I tried what you said and nothing.

SlashSpeed said:
I can't do that, because as soon as I plug in the battery the phone turns on..but yeah, I tried what you said and nothing.
Click to expand...
Click to collapse
Ah obviously. I'm out of idea here, someone else might chime in. Other than making the power button work, you might have thrown yourself into a real problem this time.

polobunny said:
Ah obviously. I'm out of idea here, someone else might chime in. Other than making the power button work, you might have thrown yourself into a real problem this time.
Click to expand...
Click to collapse
If nothing else helps, I guess I'll just send it to a repair center for the power button. I wanted to do that anyway and I sadly I have a real reason.. :/
Polobunny, I appreciate your efforts though.
Edit: Took my phone to a repair center, screw it.

Damn, wont' even load fastboot!

OK I'm stumped.
I was sick of the OTA updates bugging me so I set about flashing to 4.4.2 on my XT1034. All went along fine till I got to the part where I had to flash system with sparsechunk. It kept giving me a permissions error. I wasn't sure what to do so I decided to try rebooting, clearly that was not the answer. Now my phone shows the unlocked boot loader screen for a few seconds and goes to a black screen. I can tell the screen is on, it's just that the screen itself is showing all black. My computer recognizes that something in there and installs the drivers for the ADB interface and USB composite, but not the MTP device. All commands to adb or fastboot just says waiting for device.
Anyone have any idea?
Edit: Not sure if it makes a difference, but I was on stock 4.3, trying to go to 4.4.2 or in firmware terms...
from Blur_Version.14.14.16.falcon_umts.AWSRetail.en.US
to Blur_Version.172.44.4.falcon_umts.AWSRetail.en.US

If your phone even does not start in fastboot mode then i would say you are pretty much fu***d.

Fastboot Cable?
I just had a thought. I have a fastboot cable from my Droid Razr XT912. I wonder if that might force it into fastboot mode?
I'll have to wait till I get home to try it but I'll update it I make any progress.

Hold power button until phone turns off. Turn phone on while holding volume down.

tapman said:
I have a fastboot cable from my Droid Razr XT912.
Click to expand...
Click to collapse
You have a fastboot cable :fingers-crossed::laugh:
Thats really great!
No my friend, your USB cable will not help you to access fastboot mode.
The first way to access Fastboot is to press Volume Down + Power when the phone is switched off.
The second way to access Fastboot is to boot the phone into Android and then
Code:
adb reboot bootloader
But as you have no operating system on your phone there is only option one for you.
So your fastboot cable will not help you. Try several times to get in fastboot with option one.

lost101 said:
Hold power button until phone turns off. Turn phone on while holding volume down.
Click to expand...
Click to collapse
No luck. When I power it off it just power's itself back on a few seconds later whether I and holding the power button or not and regardless of if it's plugged in or not. I've tried the following combinations:
power off then hold volume down while it powers itself on
power off then power back on while holding volume down
hold power and volume down till it reboots
All have the same result, reboot, unlocked bootloader screen, blank, windows detects new hardware and tries to install drivers but fails on the MTP

So also if there is no cable connected it switches on itself?
Actually when it comes to the bootloader screen you missed already the fastboot entrance point.
Give it some more tries.

mokkami said:
So also if there is no cable connected it switches on itself?
Actually when it comes to the bootloader screen you missed already the fastboot entrance point.
Give it some more tries.
Click to expand...
Click to collapse
Correct. I'll keep trying :/
Edit: Sweet Jebus it worked! I'm back into fastboot
Thank you so very much!
Could be a coincidence but after taking off my case(otterbox defender) and trying again it worked. Maybe the membrane was causing me to press both volume buttons? Weird but I'll take it.

Glad to hear. Yeah i had also an Otterbox for my HHTC HD2 and i had also this problem.
Now you can go on to restore your Moto G

mokkami said:
Glad to hear. Yeah i had also an Otterbox for my HHTC HD2 and i had also this problem.
Now you can go on to restore your Moto G
Click to expand...
Click to collapse
Yup back up and running now, no idea why I was getting those permission errors. *shrug*
Thanks again

[Q] HTC one m8 hardbricked can't access any thing

I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!

piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
if your phone boots into a black screen its not hardbricked, hardbricked means it wont turn on at all and you have no indicators

piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
Does ADB recognize the device?

piisceiss said:
I bricked my htc one m8. Dont even know how, all i had was cyanogenmod 11 installed and it and my phone just boots into black screen after initial splash screen. I can get the charging indicator to show at low or full battery and i get vibration feedback when i hard reboot. I cant get into recovery or bootloader and my computer doesn't recognize it. What do!!
Click to expand...
Click to collapse
Unplug your phone and hold volume up and power for 30
seconds. Do not have it plugged in while doing this.

Bierce22 said:
if your phone boots into a black screen its not hardbricked, hardbricked means it wont turn on at all and you have no indicators
Click to expand...
Click to collapse
Ok so thats good to know

DizDroid said:
Does ADB recognize the device?
Click to expand...
Click to collapse
No but i could be doing aomething wrong. Ill give it another go

piisceiss said:
No but i could be doing aomething wrong. Ill give it another go
Click to expand...
Click to collapse
You may need to uncheck usb debugging in developer options then reboot and go in and check usb debugging again then try adb tools using adb devices and see if it works then. Some m8's can be a real pain that way you just need to keep trying.

M9guy said:
You may need to uncheck usb debugging in developer options then reboot and go in and check usb debugging again then try adb tools using adb devices and see if it works then. Some m8's can be a real pain that way you just need to keep trying.
Click to expand...
Click to collapse
I cant boot into the os, it only goes to a black screen. It still vibrates though when i try doing any form of reset

piisceiss said:
I cant boot into the os, it only goes to a black screen. It still vibrates though when i try doing any form of reset
Click to expand...
Click to collapse
I would run the newest ruu that dottat has posted in the android development section for this phone, put it on your sd card using your computer, then put it back in your phone and boot to fastboot and let it pick it up and hit I believe it is yes and it will restore your phone. You are on 4.4.4 right ? If you are having problems getting to fastboot hold power and volume up until you see the lights change and or it vibrate then quickly switch to power and volume down and it should take you to fastboot, it may take you multiple tries to get it there. This sounds like the screen of death issues people have had on viperone which the fix for that so far has been to reverse the 4g handoff fix as most people that have the sod they had used the 4g handoff fix but if you cant get past the black screen then you cant do the fix for that. Have you tried leaving your phone sit for a while to see if it comes out of it ? Also most people only had that issue in weak signal areas so a good signal area could get your screen working again if you had done the 4g handoff fix. If you did some have said that the change can stick even through a ruu, but I cannot verify that either way.

Can I say I'm having an almost same problem.
I wiped my phone in prep of loading a new rom.
RUU the firmware for 4.4.4
Loaded twrp
and then it rebooted to the htc screen.
Now I can't get past that screen. I can hard reboot but it only comes back to that screen. and if I try to access it through the computer it can't load the driver so that I can sideload.
Help please

rcbarrieault said:
Can I say I'm having an almost same problem.
I wiped my phone in prep of loading a new rom.
RUU the firmware for 4.4.4
Loaded twrp
and then it rebooted to the htc screen.
Now I can't get past that screen. I can hard reboot but it only comes back to that screen. and if I try to access it through the computer it can't load the driver so that I can sideload.
Help please
Click to expand...
Click to collapse
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.

It took about an hour of trying. But I did it. Plus I had to do a few other things to get things remounted.

rcbarrieault said:
It took about an hour of trying. But I did it. Plus I had to do a few other things to get things remounted.
Click to expand...
Click to collapse
I will have to try this. What other things did you do?

Once I was back in recovery I reformatted before rebooting and then from recovery I installed the rom.

dottat said:
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
Click to expand...
Click to collapse
I did this and we're all fixed, thank you for all the replies

dottat said:
it's tricky to get it back to hboot... but you can with practice. Hold power a both volume buttons until you think it finally has rebooted. Switch to only holding vol down to enter hboot. Timing and practice makes perfect.
Click to expand...
Click to collapse
I agree with Dottat, faced the same issue when trying to flash ARHD 22.1 on my Verizon M8. I think I sprayed some **** in my pants with that loud fart .
After trying several times I got the trick and could get into Hboot. The issue I think was I was holding Power + Volume up & down for more than required time and it Rebooted. We need to Switch Off the device by Holding Power + Volume UP & Down button for about 8-10 secs and then just remove the finger from Volume UP button. It takes you to Hboot mode..