Hello I believe my HTC one is bricked. I was changing my ROM, I have done it before but its been awhile so I did it wrong and bricked it. This is what I know.
When putting in the new ROM it showed an error and I realized I forgot to clear the data and cache. So I went back into my recovery to clear the cache and I did a factory reset.
Then it started to boot loop. It would boot to my boot screen, turn off, then boot up to my recovery, show the recovery's logo screen for a very short period then turn off and go back to the HTC boot screen.
I held down the power button and volume down and managed to get to my boot loader from there I did another factory reset because I thought it would go back to stock.
I attempted an RUU to no avail.
All of that got me to where I am now. I can boot to to my boot loader and recovery. I have full access of my teamwin recovery and my boot loader. My recovery says I have no OS every time I reboot. I am not in USB debugging mode and only have access to fastboot from my computer.
I really think I just need a nuclear option to set it back to. %100 stock using only fastboot. My last resort is going into the att store and play dumb.
xeas said:
Hello I believe my HTC one is bricked. I was changing my ROM, I have done it before but its been awhile so I did it wrong and bricked it. This is what I know.
When putting in the new ROM it showed an error and I realized I forgot to clear the data and cache. So I went back into my recovery to clear the cache and I did a factory reset.
Then it started to boot loop. It would boot to my boot screen, turn off, then boot up to my recovery, show the recovery's logo screen for a very short period then turn off and go back to the HTC boot screen.
I held down the power button and volume down and managed to get to my boot loader from there I did another factory reset because I thought it would go back to stock.
I attempted an RUU to no avail.
All of that got me to where I am now. I can boot to to my boot loader and recovery. I have full access of my teamwin recovery and my boot loader. My recovery says I have no OS every time I reboot. I am not in USB debugging mode and only have access to fastboot from my computer.
I really think I just need a nuclear option to set it back to. %100 stock using only fastboot. My last resort is going into the att store and play dumb.
Click to expand...
Click to collapse
you can boot to recovery
choose advanced/sideload
then from your pc put the rom you want to push to the phone in the adb/fastboot folder
then
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
clsA said:
you can boot to recovery
choose advanced/sideload
then from your pc put the rom you want to push to the phone in the adb/fastboot folder
then
adb devices
(verify you phone are detect)
adb sideload name_of_the_rom_file.zip
(Wait the file is transfered to phone and recovery flash)
Click to expand...
Click to collapse
Fixed. I went into the att store and a nice gentleman told me what he did. He relocked the boatloader and ran the HTC ruu
xeas said:
Fixed. I went into the att store and a nice gentleman told me what he did. He relocked the boatloader and ran the HTC ruu
Click to expand...
Click to collapse
very good
i have the same problem but my phone is not being recognized everytime i pull up a linux terminal.
i flashed the android revolution 41 rom and after instalation i accidentally skipped the last step and got stuck in the loop
i am getting the same logo and the clockworkmod 6.0.3.4 screen for a few seconds the phone restarts and gets stuck at the htc logo.
i know some have had problems with their htc one on windows 8 so i went and made my pc ubuntu, same thing.
thanks in advance for the help
qibz said:
i have the same problem but my phone is not being recognized everytime i pull up a linux terminal.
i flashed the android revolution 41 rom and after instalation i accidentally skipped the last step and got stuck in the loop
i am getting the same logo and the clockworkmod 6.0.3.4 screen for a few seconds the phone restarts and gets stuck at the htc logo.
i know some have had problems with their htc one on windows 8 so i went and made my pc ubuntu, same thing.
thanks in advance for the help
Click to expand...
Click to collapse
Welcome to XDA
posting your problem with all the needed information in a new thread would help.
when making your post be sure and include
whats on the bootloader screen
and a copy/paste of the results from fastboot getvar all
most likely your not s-off or your not on the correct version of TWRP
also in your new post add @clsA so i get the notification that you posted
Related
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
unomillionaire said:
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
Click to expand...
Click to collapse
You should reflash your recovery to TWRP using fastboot. Then boot into recovery using fastboot. From there you should be able to do a complete wipe and flash a ROM. It is outlined in the thread you linked OP and second post. Feel free to come into the d3rp q+a thread in my sig if you need more help.
It worked thanks you
unomillionaire said:
Okay about a month ago I root my gf evo 3d , she has hboot 1.5 so I followed the steps on this thread http://forum.xda-developers.com/showthread.php?t=1239821.
Everything has been working fine up until about a week ago , her phone started running hot and the battery would drain really quick with barely any usage. So my plan was to do a factory restart and full wipe and reinstall the rom fresh but when I tried to get into recovery the phone just shuts off , then goes to the boot screen then after the boot screen the phone just restarts itself. I even tried to do a factory reset from the phones menu options and the same things happens. The ways I tried getting into recovery are by using the shutdown menu options (hold power , reboot , recovery) , I've also tried rom manager and last I tried getting to recovery from bootloader and nothing seems to work.
I am completely lost PLEASE! HELP!
Click to expand...
Click to collapse
unomillionaire said:
It worked thanks you
Click to expand...
Click to collapse
As a heads up to some of the inner workings.
All the methods you listed are correct methods of booting into the recovery. ROM Manager selecting boot recovery, booting into the bootloader and selecting recovery and also adb shell, reboot recovery.
The boot order goes: bootloader -> kernel -> recovery. Once you see the HTC screen or whatever custom splash screen is loaded, you know the device is now booting the kernel. At this point, if the device hangs on the splash screen or reboots again to the splash screen, something is wrong with the kernel "recovery" itself.
If you get this rebooting to splash screen or hanging on splash screen two or three times in a row, that should be sufficient to know, you have correctly booted the device into recovery mode and the next step is to reflash the recovery, essentially reloading it.
We can speculate on how/why the recovery became corrupt on your device, but in the end, these things sometimes just happen to no intentional fault of the user.
Hopefully this doesn't happen again, but if it does, hopefully this extra information will help prevent a bit of frustration the next time around!
joeykrim said:
As a heads up to some of the inner workings.
All the methods you listed are correct methods of booting into the recovery. ROM Manager selecting boot recovery, booting into the bootloader and selecting recovery and also adb shell, reboot recovery.
The boot order goes: bootloader -> kernel -> recovery. Once you see the HTC screen or whatever custom splash screen is loaded, you know the device is now booting the kernel. At this point, if the device hangs on the splash screen or reboots again to the splash screen, something is wrong with the kernel "recovery" itself.
If you get this rebooting to splash screen or hanging on splash screen two or three times in a row, that should be sufficient to know, you have correctly booted the device into recovery mode and the next step is to reflash the recovery, essentially reloading it.
We can speculate on how/why the recovery became corrupt on your device, but in the end, these things sometimes just happen to no intentional fault of the user.
Hopefully this doesn't happen again, but if it does, hopefully this extra information will help prevent a bit of frustration the next time around!
Click to expand...
Click to collapse
So you mean, stuck at the splash screen(HTC with white screen) and reboot again and again is because of the recovery destroyed? My phone stuck at the splash screen for about 10 seconds and then reboot again and again. I have tried to flash many recovery images, includeing twrp 1.0.3, twrp 1.1.1, cwm-1.0.4, cwm-1.0.5, cwm-5.0.2, all failed to boot up into recovery:-(
Thanks in advance!
so yesterday i powered down my phone completely to put a screen protector on it. when i turned it back on i noticed i do not get the red lettering anymore at start up. i am unlocked and rooted with regaw. i booted into the bootloader this morning it shows version 1.12 and says fastboot under that. i had the options to reboot, reboot bootloader and power off i beleive. ... what happened to the option for recovery??? i also updated to TWRP 2.2
p.s. fastboot is turned off in android.
edit: i can boot into recovery from android, but since it is not showing in the bootloader what do i do if i need to get into it from there??
Edit 2: I can boot into recovery from cold boot, but when I try from a warm boot it says fast boot...anyone have any ideas?
That's how it is on this phone. Mine does that too.
ok i was alittle worried at first!
I've had my Optimus G rooted for a while now, and I had recently updated to Cyanogenmod 11 M3 and after a few weeks of good use, my phone crashed for no reason. There was a green screen that said Kernel Crash, demigod fail or something and some other stuff. Told me to press up to do this, down to do this, power to do this…. Anyways the phone wouldn't boot up after that. It was stuck on the LG logo. I could only get it into fast boot and download mode but from fast boot there was no way to get to recovery or regular boot. I found the TeenyBins post and tried to fix it using both of the .bins they had but at 85% the phone tried to boot up and was stuck on the LG logo again. Then I found the stock .bins and tried to flash them over, yet I got the same result. I've tried everything I can think to do, if anyone has any suggestions, please please help.
Teenybins don't have an OS. Did you try to get into recovery after flashing them? Doing a hard reset after stock bins may get it to boot, but internal storage will be wiped. For future reference in the demigod screen the buttons are backwards.
After flashing Teenybin I can boot into fast boot, but from there when I select recovery it goes back to the logo. Same thing happens if I select the other options. It's the google logo, not the LG logo, because the Teenybin I most recently tried was the alternate file
bowshermatthew said:
After flashing Teenybin I can boot into fast boot, but from there when I select recovery it goes back to the logo. Same thing happens if I select the other options. It's the google logo, not the LG logo, because the Teenybin I most recently tried was the alternate file
Click to expand...
Click to collapse
If you are already in fastboot, download any recovery (CWM or TWRP) extract it, rename it to recovery.img from the zip and then go to the folder where you have adb and fastboot bins and type:
fastboot flash recovery recovery.img
from there you'll be able to access recovery.
Thank you for the help, I was going to try that last night after reading your post but I took it to the AT&T store and they said they would replace it for free (warranty). I appreciate the quick response time.
i had my amaze repaired (power IC, bad data cable caused it to not charge or even boot up or go in bootloader). Now within 30 seconds off booting up it used to restart. and i cant get into the recovery( shows logo and powers off when going into recovery from bootloader). i cleared the cache from bootloader and its now stuck at boot animation( not boot logo) and wont boot completely. before clearing cache after logo it used to show 4ext recovery boot screen then screen off, now it just shows logo and screen off. really need help i got this phone fixed after 1 year. im s-off and running any 4.4.4 rom (dont remember which rom, i think pacman rom)
so basically i can get into bootloader and use fastboot commands (no adb, authorized device). cant do anything else on the phone. is there a way to fix the phone?
Arsalanzahoor said:
i had my amaze repaired (power IC, bad data cable caused it to not charge or even boot up or go in bootloader). Now within 30 seconds off booting up it used to restart. and i cant get into the recovery( shows logo and powers off when going into recovery from bootloader). i cleared the cache from bootloader and its now stuck at boot animation( not boot logo) and wont boot completely. before clearing cache after logo it used to show 4ext recovery boot screen then screen off, now it just shows logo and screen off. really need help i got this phone fixed after 1 year. im s-off and running any 4.4.4 rom (dont remember which rom, i think pacman rom)
so basically i can get into bootloader and use fastboot commands (no adb, authorized device). cant do anything else on the phone. is there a way to fix the phone?
Click to expand...
Click to collapse
reflashed recovery for the 4th time and it worked. it said the cache partition is corrupt. formatted it. phone works now. updating apps caused system ui stopped working error. going to flash other roms.
Arsalanzahoor said:
reflashed recovery for the 4th time and it worked. it said the cache partition is corrupt. formatted it. phone works now. updating apps caused system ui stopped working error. going to flash other roms.
Click to expand...
Click to collapse
Glad you got your phone working--your persistence paid off.
Be sure to make a backup before flashing other ROM's.
Hi guys,
I think I made a huge mistake Any help appreciated...
I was following the Magisk and TWRP guides to try and root my phone. I thought it was all going well, but then when trying to flash TWRP, it didn't let me flash it to recovery, it said 'no partisan'. I found on a forum post to try the command 'fastboot getvar current-slot' (this returned a) then 'fastpool flash_a twrp.img'.
I tried this but then TWRP got stuck on the loading screen. I then realised that I couldn't boot into my Android version anymore as I'd flashed TWRP directly onto the boot partition! So I went about trying to flash my stock Android version back onto the phone... I then did this:
'fastboot boot_a boot.img' I stupidly then rebooted. I now am stuck with a perpetually spinning Google loading boot image. I can't launch into recovery mode as I have none, and when holding the power button and volume up it shows an info screen saying "PRESS POWER BUTTON TO PAUSE" and then it goes to the perpetual loading screen again.
I also can't do any more fast booting because adb cannot connect anymore...
Am I completely doomed?
silkt said:
Hi guys,
I think I made a huge mistake Any help appreciated...
I was following the Magisk and TWRP guides to try and root my phone. I thought it was all going well, but then when trying to flash TWRP, it didn't let me flash it to recovery, it said 'no partisan'. I found on a forum post to try the command 'fastboot getvar current-slot' (this returned a) then 'fastpool flash_a twrp.img'.
I tried this but then TWRP got stuck on the loading screen. I then realised that I couldn't boot into my Android version anymore as I'd flashed TWRP directly onto the boot partition! So I went about trying to flash my stock Android version back onto the phone... I then did this:
'fastboot boot_a boot.img' I stupidly then rebooted. I now am stuck with a perpetually spinning Google loading boot image. I can't launch into recovery mode as I have none, and when holding the power button and volume up it shows an info screen saying "PRESS POWER BUTTON TO PAUSE" and then it goes to the perpetual loading screen again.
I also can't do any more fast booting because adb cannot connect anymore...
Am I completely doomed?
Click to expand...
Click to collapse
I ended up eventually un-bricking my phone by booting into safe mode and re-connecting the ADB. I then successfully ran 'flash-all.'