Hi Guys
I'm in mildly troublesome waters and I was hoping that the people here would help me figure my way around a solution.
So about a week or so ago, my AT&T one XL (which is on CM10.1 stable) started behaving weirdly; the screen wouldn't turn on but all the touch functionality would still work as I was able to receive calls by just using my instincts on knowing where what should be. Now at that point, if I pressed different parts of the screen, it would turn on for a few seconds and then the screen would black out again. The buttons do light up.
But as of yesterday, my screen won't turn on no matter where I apply pressure to try to get it to turn on. The screen still works and I can randomly turn on 'Google Now' and and other stuff as long as I know where what is located on the screen.
I called in AT&T as my phone is still in warranty and they are sending a replacement. However, I'm now in a bit of a race-against-time to get my phone back to stock and hopefully even get rid of the *tampered* sign that shows up in fastboot. I was wondering what my options are to get this done at this stage as I'm not even able to tell when I'm in the fastboot mode. I'm worried that if I don't send it back with atleast stock settings then I'm liable to pay a replacement fee of 500$!
Also, does anyone have any experience with sending in a phone that was jailbroken and not running stock but still under warranty?
Any help/information would be great!
Thanks
Angadh
your screens cable is loose or damaged. is your phone s-off? do you recall if u had usb debugging enabled?
I was on 2.20 when I rooted the phone so I'm guessing that implies I didn't s-off. No recollection if I left usb debugging on, but I'd like to tihnk I did!
gadha007 said:
I was on 2.20 when I rooted the phone so I'm guessing that implies I didn't s-off. No recollection if I left usb debugging on, but I'd like to tihnk I did!
Click to expand...
Click to collapse
if usb debugging is on:
use adb to boot to blootloader then relock and ruu to 2.20 you would need to s-off to ruu to 3.18 or to spoof the relocked. tampered should disappear when you ruu.
exad said:
if usb debugging is on:
use adb to boot to blootloader then relock and ruu to 2.20 you would need to s-off to ruu to 3.18 or to spoof the relocked. tampered should disappear when you ruu.
Click to expand...
Click to collapse
Thanks for the info, exad.
So what I tried now was to use the hasoon all in one kit and clicked on the 'Boot into Bootloader' under commands. I got 'error: device not found'. That implies I'm not in USB debugging, right? So do I have any other options from here?
gadha007 said:
Thanks for the info, exad.
So what I tried now was to use the hasoon all in one kit and clicked on the 'Boot into Bootloader' under commands. I got 'error: device not found'. That implies I'm not in USB debugging, right? So do I have any other options from here?
Click to expand...
Click to collapse
yea you can manually boot to fastboot. press and hold power. the capacitive buttons will blink a bunch of times, when they stop blinking let go of power, press and hold volume down.
then you can go on from there.
exad said:
yea you can manually boot to fastboot. press and hold power. the capacitive buttons will blink a bunch of times, when they stop blinking let go of power, press and hold volume down.
then you can go on from there.
Click to expand...
Click to collapse
The phone just seems to boot back up to CM. Ican't tell if I'm doing something in fastboot that makes it go back into CM. Any other ideas? or indicators?
gadha007 said:
The phone just seems to boot back up to CM. Ican't tell if I'm doing something in fastboot that makes it go back into CM. Any other ideas? or indicators?
Click to expand...
Click to collapse
thats all ive got.
exad said:
yea you can manually boot to fastboot. press and hold power. the capacitive buttons will blink a bunch of times, when they stop blinking let go of power, press and hold volume down.
then you can go on from there.
Click to expand...
Click to collapse
Okay. So i was just messing up but after multiple attempts, I finally did it. Thanks for the help. You are awesome!
Related
okay guys so surprisingly i havent seen anything on here about the button combo to get into bootloader on your one x (or recovery)
i think its just volume down and power ? but a lot of the time it just boots up like normal.
anything specific i can do to get it to work better?
also once i re lock my bootloader, there is no way for me to get the phone to boot up normally, like no matter what i do it just reboots into the bootloader what should i do?
(basically im trying to get from clean rom on 1.82.5 base , back to offical stock 1.73.5)
The_Zodiac said:
okay guys so surprisingly i havent seen anything on here about the button combo to get into bootloader on your one x (or recovery)
i think its just volume down and power ? but a lot of the time it just boots up like normal.
anything specific i can do to get it to work better?
also once i re lock my bootloader, there is no way for me to get the phone to boot up normally, like no matter what i do it just reboots into the bootloader what should i do?
(basically im trying to get from clean rom on 1.82.5 base , back to offical stock 1.73.5)
Click to expand...
Click to collapse
You have to hold vol down the entire time until it gets to the bootloader. Also, turn fastboot off.
Or you can always "adb reboot recovery" if you're at a computer
The_Zodiac said:
okay guys so surprisingly i havent seen anything on here about the button combo to get into bootloader on your one x (or recovery)
i think its just volume down and power ? but a lot of the time it just boots up like normal.
anything specific i can do to get it to work better?
also once i re lock my bootloader, there is no way for me to get the phone to boot up normally, like no matter what i do it just reboots into the bootloader what should i do?
(basically im trying to get from clean rom on 1.82.5 base , back to offical stock 1.73.5)
Click to expand...
Click to collapse
I've found that if you lock the bootloader while on a rom that uses an insecure boot.img like cleanrom does you'll see "security warning" on the bootloader screen and the phone won't boot to anything except the bootloader. It's ok though because you can install the ruu from there.
stnguyen09 said:
You have to hold vol down the entire time until it gets to the bootloader. Also, turn fastboot off.
Or you can always "adb reboot recovery" if you're at a computer
Click to expand...
Click to collapse
gunnyman said:
I've found that if you lock the bootloader while on a rom that uses an insecure boot.img like cleanrom does you'll see "security warning" on the bootloader screen and the phone won't boot to anything except the bootloader. It's ok though because you can install the ruu from there.
Click to expand...
Click to collapse
how do you disable fastboot? (or you mean while the phone is running normally in settings?)
i tried running the ruu from the bootloader and it wouldnt work though
is there a different rom i could flash, then be able to lock and flash back to stock 1.7?
The_Zodiac said:
how do you disable fastboot? (or you mean while the phone is running normally in settings?)
i tried running the ruu from the bootloader and it wouldnt work though
is there a different rom i could flash, then be able to lock and flash back to stock 1.7?
Click to expand...
Click to collapse
from the bootloader screen choose fastboot and you should be able to install the RUU
This method of getting into the bootloader always works for me.
It involves counting so read it through first as you need to act quickly:
Hold down the power button untill you see the capacitive buttons start flashing.
After a few seconds they will stop flashing.
Hold the volume down button immediately.
Then hold the power button for around 3 seconds and release it, while still holding the volume up button.
Hold it until you boot into the bootloader screen.
rohan32 said:
This method of getting into the bootloader always works for me.
It involves counting so read it through first as you need to act quickly:
Hold down the power button untill you see the capacitive buttons start flashing.
After a few seconds they will stop flashing.
Hold the volume down button immediately.
Then hold the power button for around 3 seconds and release it, while still holding the volume up button.
Hold it until you boot into the bootloader screen.
Click to expand...
Click to collapse
ill have to give this a shot, at what point do you start holding the volume up button?
Hello, just to start I have read through probably 100 post regarding similar issues but none are working. I have the ATT Htc one x EVITA 3.18 version. I did the super CID unlocked my bootloader through htc dev, flashed twrp recovery, and got a custom rom, gapps etc.. in twrp I wiped all data,system,cache, factory reset. Then flashed my rom and gapps (being kinda new to HTC devices I didn't flash the boot.img from the rom) now my phone after restarting just continues a bootloop (HTC Quietly Brilliant) screen, then powers off repeating this over and over.. I tried holding the volume down with the power button it just loops again, the I tried some other suggestions like holding power and vol down until the flashes stop and releasing power while continuing to hold volume down, again loops, then tried using volume up as well...none of these are working I don't understand what happened and why I can't get into any of these? I did not run any RUU. I tried using adb but of course i cant get into fastboot or anything so the phone is not recognized. If anyone could please help I really do appreciate it. I know this has been all over the threads but I read for the past 3 hours and could not get anything to work.. Thanks in advanced for any help it is much appreciated. :crying:
First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita
timmaaa said:
First of all, don't hold volume up and power, that's bad news. Trying random button combinations is a really bad idea. While it's looping just hold volume and the next time it starts again it should reach the bootloader.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the reply timmaaa... I usually would not try the other button presses just someone else had said that worked for them, but thanks for the advice. I did try what you said and just holding the volume down button, let it bootloop, and keep holding and it just continues to bootloop :/ it stay off for about 20 seconds the same then bootloops, with the htc screen for about 5 seconds the rinse and repeats D**n this thing is annoying. Any other Ideas? Thanks again man appreciate it.
if you are SOFF u can go for RUU?
Sonone said:
if you are SOFF u can go for RUU?
Click to expand...
Click to collapse
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:
sensei_777 said:
No I'm still s-on I didn't try to RUU cus I read it would brick..but seems I'm somewhat bricked anyway:silly:
Click to expand...
Click to collapse
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!
Sonone said:
are you sure you did get the SUPER CID cause if its not then you can RUU your device!
cause if you are not SUPERCID get a matching RUU or a latest version meant for your device!
only if you could somehow manage your phone to get recognized by a PC etc then you could flash boot.img with some toolkit etc and everything would have been fine!
but unless some expert actually figures out your problem dont RUU!
i really wonder whats obstructing the boot loader access!??
please let me know if u can get your device back to normal!
Click to expand...
Click to collapse
I had to change the CID to unlock the bootloader on htc dev, its like 11111 so that is super CID right?
Yea I've tried everything to get to adb since I am familiar with adb but its a no go none of the tool kits or even manual cmd is recognizing the device.. I had a one x just like this before and never had the problem getting into bootloader so I don't really get what is blocking it. Only thing I had done was flash twrp recovery, wiped data/factory reset, system and cache, then flashed the rom as one usually would and gapps, just I had forgot about these phones needing you to flash the boot.img. that is all I did to it. Kinda sucks I just got this thing yesterday from a friend too.
Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita
timmaaa said:
Yes, 11111111 is SuperCID. In any case I probably wouldn't attempt an RUU while the phone is this unstable, could be quite dangerous. It's possible the "adb reboot bootloader" command might work if you catch it at the right time in the boot cycle.
Sent from my Evita
Click to expand...
Click to collapse
Thanks bud, well I can't get it to catch even using super finger speed cmd'ing lol.. oh well.. I'm not gonna try anything else other than the usual ways to get into bootloader until someone else has some idea what might be blocking it from entering. Is there anyway to turn it off? its just restarting over and over with the bootloop. Or does one just let it go dead? I suppose worse case senario sending it for Jtag would fix it right? thanks again to the both of you.
I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita
timmaaa said:
I believe in the command window your can press the down key to give the previous command again, so if you hit down and enter one after the other (spamming it) you might have a chance. I'm really surprised that continually holding volume down during the loop process isn't getting you to bootloader, that's very strange. There's no way to turn it off. But, it usually burns through a fair bit of battery during a boot loop so you could wait for it to die completely, charge it for a couple of hours, and then try the volume down + power combination to get to the bootloader. I hope it works, let us know how you go.
Sent from my Evita
Click to expand...
Click to collapse
Yes well on my laptop its the up key that's what I was doing was spamming, you can hear the connected device sound on then off, but it just doesn't see it. I will let you all know once its working again and what I did or had to do to get it back so that it may possibly help others that run into the same issue. If not I suppose I'll try to get it Jtagged, too nice of a phone to use as a paperweight really
Yeah sorry, I knew it was one of the arrow keys, kinda took a stab in the dark at that one :sly:
Sent from my Evita
Hold down the power button until the phone turns off. You'll see the buttons flash. This simulates a battery pull. Then wait a few secs then hold vol down and press power button for 2 secs while still holding vol down. Wait for bootloader
Sent from my VENOMized HoxL
You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita
timmaaa said:
You should hold volume down while holding power. Holding power alone just initiates a reboot, not a power down, so if you're not holding volume down at the same time when the reboot kicks in it'll just reboot as normal.
Sent from my Evita
Click to expand...
Click to collapse
Nothing is working guys :/ full Battery drain and everything it just keeps looping no matter what I do it will not go in bootloader :crying: thanks for trying to help
If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developers app
exad said:
If you are trying while the phone is plugged into power it will not work.
The method I use is to hold power until the screen shuts off then I let go of power and hold volume down until the bootloader comes up.
Sent from my One Xl using xda app-developer app
Click to expand...
Click to collapse
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.
sensei_777 said:
Yes I don't have power plugged in, I've never had a problem like this. . I also don't even have to turn off the screen everytime it loops it goes off for a good 20 seconds or more. But I did try what you all said too and it seems there is not even an effect at all it just loops
YAY!! I was messing around and held volume up and volume down with power, and it put the phone into some kind of off/sleep mode, then it recognized the device in windows device manager and said device cannot start, so I tried uninstalling the driver and then refreshed to let it reinstall them and during the reinstall i tried running the adb command and it let me back into bootloader! woo! that was lucky.. hopefully this can be helpful to others that get stuck like that. I'm worried now though i have bootloader sitting pretty what should I do first? I'm scared to loop again thanks all.
Click to expand...
Click to collapse
Just flashed the boot.img good to go now thanks for the advice everyone
Hey Guys,
so ive been messing around with this little phone and think i might have managed a hard brick. Any thoughts or advice would be appreciated.
was attempting to relock the bootloader and flashing my local 4.4.2 rom and on the command prompt when i reached flash system.img parsechunk lines, they failed. as it said permission denied.
Tried to continue with no luck. Restarted my phone and now cant get into recovery and no boot, the only screen i see is the white warning bootloader locked screen, get a vibrate and then it turns off again. Any ways to flash without Recovery or Fastboot or am i completely out of luck?
Sorry im new to motorolas, had no problems messing around with my old SGS2
Thanks in advance everybody.
did you try this ?
http://forum.xda-developers.com/showthread.php?t=2542219
the only problem is cant get the phone into fastboot mode. Thanks for the input though!
mackb44 said:
the only problem is cant get the phone into fastboot mode. Thanks for the input though!
Click to expand...
Click to collapse
I've been in a few situations where I thought I had 'bricked' my phone. One way that worked (sometimes) was to long press the POWER button for a very long time(minutes), then release and (sometimes) it would reboot.
The usual way to the fastboot menu is - power off (which yours probably is), then hold vol. down and press power button for 5/10 seconds and release both.
Good luck!
jamsh said:
I've been in a few situations where I thought I had 'bricked' my phone. One way that worked (sometimes) was to long press the POWER button for a very long time(minutes), then release and (sometimes) it would reboot.
The usual way to the fastboot menu is - power off (which yours probably is), then hold vol. down and press power button for 5/10 seconds and release both.
Good luck!
Click to expand...
Click to collapse
Yea tried both options, no luck!
The only screen i can get now is the bootloader unlocked screen or the white charging screen when plugged in. After that the screen will stay on but is completely black.
Success I can get into fastboot now!!!! not sure why i could not before
mackb44 said:
Success I can get into fastboot now!!!! not sure why i could not before
Click to expand...
Click to collapse
yes i had something similar,bootlocker warning and then the screen going dark. i just ended up using fastboot and flashing a stock rom and went from there.
glad your panic is over .
quizmaniac said:
yes i had something similar,bootlocker warning and then the screen going dark. i just ended up using fastboot and flashing a stock rom and went from there.
glad your panic is over .
Click to expand...
Click to collapse
Yea thanks buddy!
just have to wait for it to charge up before it will let me flash using adb, oddly its only showing that it is charging while plugged into usb and not the wall socket
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
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..