Related
ok been dealing with this for the past hour no results.. i recently flashed the twrp recovery just to check it out and wanted to flash a rom on it went to do so and now that i reboot phone it stays on the htc start up screen turns off than back on.. only thing working on it is the hboot, no recovery. although occasionally ill see the twrp start up screen than it turns off and goes white htc... any help is appreciated.. thinking i may have to relock and find the stock at&t ruu??:crying:
gabriel1946 said:
ok been dealing with this for the past hour no results.. i recently flashed the twrp recovery just to check it out and wanted to flash a rom on it went to do so and now that i reboot phone it stays on the htc start up screen turns off than back on.. only thing working on it is the hboot, no recovery. although occasionally ill see the twrp start up screen than it turns off and goes white htc... any help is appreciated.. thinking i may have to relock and find the stock at&t ruu??:crying:
Click to expand...
Click to collapse
So you flashed the rom and it wont boot up now? or you flashed the recovery and it wont boot up now.
camo_flage said:
So you flashed the rom and it wont boot up now? or you flashed the recovery and it wont boot up now.
Click to expand...
Click to collapse
the recovery was working i was using jb pacman rom than flashed to i think it was element rom by shadow slayer but once i did that it keeps turning on and off if i try to choose recovery from the hboot it shows the recovery screen for a second than goes to htc screen and turns off and back on
gabriel1946 said:
ok been dealing with this for the past hour no results.. i recently flashed the twrp recovery just to check it out and wanted to flash a rom on it went to do so and now that i reboot phone it stays on the htc start up screen turns off than back on.. only thing working on it is the hboot, no recovery. although occasionally ill see the twrp start up screen than it turns off and goes white htc... any help is appreciated.. thinking i may have to relock and find the stock at&t ruu??:crying:
Click to expand...
Click to collapse
Fastboot erase cache command will fix this problem. Boot to your bootloader select fastboot usb and run that command.
haha im not too good with computers more of a mobile only tech haha can u explain that please?
gabriel1946 said:
haha im not too good with computers more of a mobile only tech haha can u explain that please?
Click to expand...
Click to collapse
I assume you are using windows...? Do you have adb installed/working? If the answer to both of these is yes. Reboot your phone to the bootloader (hboot) select fastboot usb in hboot. Open a cmd Window cd to the dir where adb is located. Then run the command in the above post.
---------- Post added at 06:07 PM ---------- Previous post was at 05:54 PM ----------
gabriel1946 said:
the recovery was working i was using jb pacman rom than flashed to i think it was element rom by shadow slayer but once i did that it keeps turning on and off if i try to choose recovery from the hboot it shows the recovery screen for a second than goes to htc screen and turns off and back on
Click to expand...
Click to collapse
Last time this happened there was a script that was running that corrupted the cache partition. That is why erasing cache fixes it.
esloan said:
I assume you are using windows...? Do you have adb installed/working? If the answer to both of these is yes. Reboot your phone to the bootloader (hboot) select fastboot usb in hboot. Open a cmd Window cd to the dir where adb is located. Then run the command in the above post.
Click to expand...
Click to collapse
adb u mean adbfastbootrecovery? i installed in not sure how to get it working, the command imputing is where im getting lost sorry for my noobness lol appreciate ur help i have my phone on hboot fastboot now connected to my computer ive seen that command imput is shift and right click but i dont get any command window i get normal options.. ive only use command in the run app under start
gabriel1946 said:
adb u mean adbfastbootrecovery? i installed in not sure how to get it working, the command imputing is where im getting lost sorry for my noobness lol appreciate ur help i have my phone on hboot fastboot now connected to my computer ive seen that command imput is shift and right click but i dont get any command window i get normal options.. ive only use command in the run app under start
Click to expand...
Click to collapse
Okay where is your adb file? Ex mine is in a C:/Android. By default if you installed the android SDK the adb files would be in the SDK folders. Any way if you were fast boot flashing a recovery your going to do the same thing just use fastboot erase cache as the command instead of the recovery command. If none of this makes since PM me.
Resolved via PM
After only four day of having this phone i managed to brick it. I would really like to know if its fixable or if i have a really nice paper weight. Im stuck on a boot loop, I was half way through flashing a rom when it suddenly shut off. Now it will not boot up. I can load into the bootlader but when i try to go into recovery it just sends me to fastboot. When i restart the phone i can see the old recovery (TWRP)for just an instant but then the screen goes completely black. If i plug in to my pc, nothing happens my computer detects it but it says y device is damaged nd it cant identify it. PLEASE HELP Am i out of luck?
Ive looked around but i couldnt seem to find anyone with the same problem as me (Sprint Variant)
Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help
There's a Sprint One forum as well, so hopefully you found a ROM on there!
http://forum.xda-developers.com/forumdisplay.php?f=2215
jaythenut said:
Good news it's not bricked i would put this question on the rom thread someonethere sshould be able to help
Click to expand...
Click to collapse
I really hope so because on a college budget i cant afford another phone D:
Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.
wnp_79 said:
Seen this in a couple of other places. Seems certain recoveries are possibly becoming currupted during flashing a new ROM.
What you need to do it get back into fastbboot, and....
fastboot erase recovery
fastboot erase cache
the re-flash your recovery, boot into recovery, full wipe and reflash your ROM.
Click to expand...
Click to collapse
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
i suggest you contact with HTC customservices to repair this problem.
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.
DynamicRam said:
Can you flash recovery in fastboot ?
the safest thing to do is relock and use a matching RUU to get back to stock
Click to expand...
Click to collapse
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
dont give up
Sent from my HTC One
Muquita said:
I cannot. My computer wont recognize it. I re-installed the driver and it Says my device malfunctioned.
Im giving up hope here.
Click to expand...
Click to collapse
Edit: Just got done typing the stuff below and saw you can't connect to your device in fastboot? What do you mean by re-installed driver?
Don’t worry, as long as you can still get into hboot your phone is not completely bricked!
The fastboot commands I referred to need to be carried out on your laptop/pc when you phone is connected in fastboot.
Can I assume that as you have already unlocked bootloader and flashed a custom recovery you are already familiar with this and have your computer set up for fastboot commands?
(Apologies if you already know some of this, best not to skip parts out though!)
I’d start with downloading a fresh version of your chosen recovery, and place it in your fastboot directory ready. I’d also do the same with your ROM.
Like you have already done, boot into fastboot. Connect your phone to your pc, and the red text should change to ‘Fastboot USB’.
Then open up command prompt and get to your fastboot directory. (On Windows 7 you just find that folder in Explorer, hold shift and right-click, then choose ‘Open command window here’.)
To check your pc is talking to your phone, type ‘fastboot devices’. You should get a device serial number back if all is well.
Then type ‘fastboot erase cache’ and hit enter.
Then type ‘fastboot erase recovery’ and hit enter.
Then type ‘fastboot flash recovery [name of recovery].img’ and hit enter.
Then type ‘fastboot reboot recovery’ and hit enter.
Hope fully you should successfully boot into recovery now. Once in recovery, mount USB storage and copy over your fresh ROM. Choose to do a full wipe including cache and dalvik, then reflash your ROM.
Reboot.
Let me know how this goes.
cronus101 said:
Your phone isn't bricked. There are two tools in this forum that can help you. One is made by hasoon2000(I think that's his user name), and the other is jwtool(I think). Use them to help to flash a recovery if you don't know how to use fastboot.
Click to expand...
Click to collapse
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:
Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app
Muquita said:
I used the hasoon2000 to flash TWRP earlier, but my problems is that my pc wont recognize my phone. When i plug it in it and try to re-flash it it cant find it. When i check my devices it shows up as an android device but it says the drivers are damaged. if i could get it to read it i think i should be eable to reflash somethint.
I APPRICIATE ALL THIS HELP. i really am trying to be as specific as possible :fingers-crossed:
Click to expand...
Click to collapse
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html
Muquita said:
When i go back into fastboot my only options are
-Bootloader
-Reboot
-Reboot bootleader
-Power down.
I appriciate the help!
Click to expand...
Click to collapse
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck
wnp_79 said:
I'd say the next step is to re-install your drivers in the SDK. Open up your Android SDK and reinstall them. In Windows Device Manager, find your connected device (probably now with an exclamation mark on it) and right click on it and select 'Update Driver'.
(Assuming you are using Windows 7 here?)
http://developer.android.com/tools/extras/oem-usb.html
Click to expand...
Click to collapse
(Win8 but the procces is identical.) All my drivers are up to date. Still no love.
On the dev forum is a thread that includes all the latest drivers (including an app to remove older drivers.)
Find that thread, download the drivers and bmp and driver removal tool. Remove drivers with tool, install the new drivers, reboot, connect phone and see if 'adb devices' finds anything.
Also make sure you're using the latest adb.
Sent from my HTC One using xda app-developers app
thneed said:
Hey so just a thought and experience I have had with all my HTC phones is when you see that quick glimpse of the TWRP recovery screen then it disappears to an empty black screen......you are sometimes still in a form of recovery but during your Rom flash something (i don't know for sure) changed and it doesn't show the screen only black. So with that long explanation out of the way....have you tried once the screen goes black the
"adb devices "
Mine whenever in this situation would return the output of serial number and recovery so then you can push or sideload the Rom and boot into the system at which point your fastboot drivers will finally be recogniZed.....
Hope this helps a little
Sent from my HTC EVARE_UL using xda app-developers app
Click to expand...
Click to collapse
This actually sounds really similar to my situation.. Would you care to be a little more specific on the procedure? noob here.
Tabtoub said:
when you are in fastboot, connect your phone using the usb cable, and when you see "fastboot" written in red turned into "fastboot usb" or something like this, do the commands below using cmd window of course :
1) fastboot erase recovery
2) fastboot erase cache
3) fastboot flash recovery recoveryname.img
4) fastboot erase cache
Let us know when you fix it
Good Luck
Click to expand...
Click to collapse
My pc will not recognize my phone. The drivers are up to date but when i plug it in it says something malfunctioned ?
Yesterday my Device restart.After Screen don't showing something,but i had vibration response from Home button.
Than Phone reboots again and hangs into bootloop.Tt reboots every 3 seconds.No time to enter in recovery.Also tried to connect with adb to erase cache, but after some hundreds attempts it doesn't work, because no device detected.Also tried to wait until battery is empty.
Same time no AC led is showing, also no physical Buttons are blinking.
Is there any chance to fix it ?
You can boot into the bootloader?
And if you are in fastboot the command is
Code:
fastboot erase cache
and not
Code:
adb erase cache
.
Guich said:
You can boot into the bootloader?
And if you are in fastboot the command is
Code:
fastboot erase cache
and not
Code:
adb erase cache
.
Click to expand...
Click to collapse
no, i cant boot into bootloader, also no recovers because when 3 or 5 seconds passed phone reboots again and again.
Also tried all in one tool.Strange will be that reboots begins automatic after some time on ac.
Really strange...
adb don't recognized the device, right?
Guich said:
Really strange...
adb don't recognized the device, right?
Click to expand...
Click to collapse
yes "waiting for device". or "error device not found".
onkel_neme said:
no, i cant boot into bootloader, also no recovers because when 3 or 5 seconds passed phone reboots again and again.
Also tried all in one tool.Strange will be that reboots begins automatic after some time on ac.
Click to expand...
Click to collapse
had the same issue with my old htc one, after some time on ac it rebootet itself. sent it in for repair, but the issue was still there. then i've updatet the HBOOT and it solved the problem...
herwegan said:
had the same issue with my old htc one, after some time on ac it rebootet itself. sent it in for repair, but the issue was still there. then i've updatet the HBOOT and it solved the problem...
Click to expand...
Click to collapse
How do you update it, when no connect to pc possible ?
onkel_neme said:
How do you update it, when no connect to pc possible ?
Click to expand...
Click to collapse
no idea, sorry. i just wanted to tell you that i experienced this strange issue too, but i was able to boot the device.. so maybe it's useful for you to know that it was caused by the HBOOT.
I'm afraid I may have bricked my phone but good this time.
I had gone through the unlock,flash recovery, etc process a few months ago. Today I downloaded and installed what I think is a rom that was not intended for my phone and everything went south.
I am still able to boot into bootloader, and I can select FASTBOOT and plug the phone in. It switches to FASTBOOT USB, so I type
fastboot erase cache
That seems to work fine so I next type
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.imp
I get sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished.
Swell So I power down and reboot to fastboot, then select recovery. I get a flash of the TWRP screen, then it goes blank and it tries to boot to the OS. Since there isn't one I get stuck at the htc quietly brilliant logo screen. (I'm not feeling particularly brilliant at the moment).
I just flashed openrecovery-twrp-2.6.3.3-m7.img and the same thing happened. I went back to 2.5.0.0-m7 and the same thing.
Am I screwed beyond repair or is there a way to fix this? Perhaps I'm using the wrong recovery image? If so can someone point me to the right one and where I might be able to download it from? I like TWRP a lot but their website is not the best I've ever seen.
dlbarron said:
I'm afraid I may have bricked my phone but good this time.
I had gone through the unlock,flash recovery, etc process a few months ago. Today I downloaded and installed what I think is a rom that was not intended for my phone and everything went south.
I am still able to boot into bootloader, and I can select FASTBOOT and plug the phone in. It switches to FASTBOOT USB, so I type
fastboot erase cache
That seems to work fine so I next type
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.imp
I get sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished.
Swell So I power down and reboot to fastboot, then select recovery. I get a flash of the TWRP screen, then it goes blank and it tries to boot to the OS. Since there isn't one I get stuck at the htc quietly brilliant logo screen. (I'm not feeling particularly brilliant at the moment).
I just flashed openrecovery-twrp-2.6.3.3-m7.img and the same thing happened. I went back to 2.5.0.0-m7 and the same thing.
Am I screwed beyond repair or is there a way to fix this? Perhaps I'm using the wrong recovery image? If so can someone point me to the right one and where I might be able to download it from? I like TWRP a lot but their website is not the best I've ever seen.
Click to expand...
Click to collapse
You could try downloading the dev edition RUU and running it to get your phone to a working stock. After that, you could flash your specific rom to get back to your native stock. There are other options as well.
Try flashing CWM as well and see what happens ...
dlbarron said:
I'm afraid I may have bricked my phone but good this time.
I had gone through the unlock,flash recovery, etc process a few months ago. Today I downloaded and installed what I think is a rom that was not intended for my phone and everything went south.
I am still able to boot into bootloader, and I can select FASTBOOT and plug the phone in. It switches to FASTBOOT USB, so I type
fastboot erase cache
That seems to work fine so I next type
fastboot flash recovery openrecovery-twrp-2.5.0.0-m7.imp
I get sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished.
Swell So I power down and reboot to fastboot, then select recovery. I get a flash of the TWRP screen, then it goes blank and it tries to boot to the OS. Since there isn't one I get stuck at the htc quietly brilliant logo screen. (I'm not feeling particularly brilliant at the moment).
I just flashed openrecovery-twrp-2.6.3.3-m7.img and the same thing happened. I went back to 2.5.0.0-m7 and the same thing.
Am I screwed beyond repair or is there a way to fix this? Perhaps I'm using the wrong recovery image? If so can someone point me to the right one and where I might be able to download it from? I like TWRP a lot but their website is not the best I've ever seen.
Click to expand...
Click to collapse
Seen this happen before, it was because 'fast boot' was selected in Settings.
Settings -> Power -> make sure "fast boot" is unticked. Then power the phone off, then boot to fastboot and flash recovery again.
redbull123 said:
Seen this happen before, it was because 'fast boot' was selected in Settings.
Settings -> Power -> make sure "fast boot" is unticked. Then power the phone off, then boot to fastboot and flash recovery again.
Click to expand...
Click to collapse
I can't get to settings. It hangs at the HTC logo.
v-b-n said:
Try flashing CWM as well and see what happens ...
Click to expand...
Click to collapse
I did try that. It hangs at the "Entering Recovery..." screen.
dlbarron said:
I did try that. It hangs at the "Entering Recovery..." screen.
Click to expand...
Click to collapse
did u "fastboot erase cache" after flashing the recovery?
kibmikey1 said:
You could try downloading the dev edition RUU and running it to get your phone to a working stock. After that, you could flash your specific rom to get back to your native stock. There are other options as well.
Click to expand...
Click to collapse
Is that the right recovery?
Don't I have to be able to boot into recovery to run the RUU? Where can I get it?
What are some of the other options?
nkk71 said:
did u "fastboot erase cache" after flashing the recovery?
Click to expand...
Click to collapse
Yes, I tried erase cache before and after, no difference.
I think you screwed something up in your device's file system, partition table or your bootloader is somehow damaged. As you can run fastboot, I strongly suggest a RUU. To get the right RUU for your phone there are numerous guides such as:
http://forum.xda-developers.com/showthread.php?t=2428276
http://forum.xda-developers.com/showthread.php?t=2158151
xxmorph3u5xx said:
I think you screwed something up in your device's file system, partition table or your bootloader is somehow damaged. As you can run fastboot, I strongly suggest a RUU. To get the right RUU for your phone there are numerous guides such as:
http://forum.xda-developers.com/showthread.php?t=2428276
http://forum.xda-developers.com/showthread.php?t=2158151
Click to expand...
Click to collapse
I think so. I just tried flashing CWM and was able to boot into it. It's showing unable to mount messages.
Looks like I have no choice but to try the RUU. I have been hesitant because I have yet to find a good explanation and good downloads of all the parts I need. Is there something like that available?
all right, this will certainly add to the confusion.
I flashed recovery_m7_att_stock and was able to get into it a little. Then I went back to the bootloader and flashed openrecovery-twrp-2.5.0.0-m7 and actually get into it.
WHAT?
I pushed the CM nightly rom to it and it installed, although there were some errors about not being able to mount some things data and cache. But it did install and I was able to get into CM.
I'm almost afraid to try anything else at this point.
dlbarron said:
I think so. I just tried flashing CWM and was able to boot into it. It's showing unable to mount messages.
Click to expand...
Click to collapse
unable to mount /cache is OK (caused by fastboot erase cache)
unable to mount /data is not ok, could be a corrupt /data partition
nkk71 said:
unable to mount /cache is OK (caused by fastboot erase cache)
unable to mount /data is not ok, could be a corrupt /data partition
Click to expand...
Click to collapse
After rebooting I'm still able to get into TWRP. I've been able to flash a couple of ROMs (very carefully) and I'm no longer seeing any errors about not being able to mount.
Looks like what ever was wrong has been corrected. Now all we have to do is figure out what went wrong and what I did to fix it.
Thanks everyone.
Ok..so here's the situation. I was going to install a new ROM ( my son got a new phone a iphone ) but any ways. As I was in TWRP i did everything we all normally do but the phone died mid flashing GAPPS. when i went to pulg the phone to the charger and restart the phone i see that it started to boot up the it jumped straight to FASTBOOT and it's stuck. I can toggle through fastboot but that is it. when i go to restart it will show the boot animation but then goes to fast boot. it wont go to TWRP nothing. I've combed XDA and found the multi tool but don't think that is working or i might be using it wrong. the computer doesn't recognize the phone. im trying to get this phone back up and going and give to my daughter . any help is greatly appreciated. thank you in advacne.
Here's what I'm talking about just in case someone asks
Try installing a stock factory image from fastboot.
runekock said:
Try installing a stock factory image from fastboot.
Click to expand...
Click to collapse
How...I can't get my computer to recognize the phone... When I plug it in it doesn't read it...I should have the drivers already installed...adb push right.... I'll search for the command to see if it finds the phone
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
runekock said:
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
Click to expand...
Click to collapse
Thanks for the heads up I'll definitely be trying this and I'll give you an update soon