I have the htc Flyer and i flyer dextersjb rom after flashing it i flashde the boot.img from my computer manualy(Cause i have the bootloader unlockde) after i booted it passed through the splash screen sawed the boot animation for 3 seconds and it rebooted. Again it was in splash screen boot animation for 3 sec and rebooted itself and agai again agian. i tried in recovery got threw the splash screen saw the recovery for 3 secs and just like when it was 'Booting" please help. I have left is fastboot mode at least then it is not rebooting. Help pleaseeee
Is your device s-on [top of the bootloader]? If so, that's supposed to prevent flashing of kernels, as far as i understand, and it seems that is your problem. Try reflashng the stock kernel. Otherwise, maybe you forgot to do a factory reset from recovery if you're changing roms.
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!
Interesting thing happened today which has basically put my phone in a death spiral state. The battery died and after charging it a while I went to power it back on and found it in a boot loop state. I can get into the bootloader, but from there if I select recovery it reboots and the white bar on the right side of the screen fails to fill up, then the phone reboots. I've tried flashing two different versions of TWRP from the bootloader and it still exhibits the same issue.
HBOOT 1.12.1111
RADIO 1.12.11.1210
S-OFF
I was running CM10.1 without much issue until the power issue.
Any thoughts?
Thanks to Zanzibar for helping me work through this on IRC. Eventually the steps outlined here: http://forum.xda-developers.com/showthread.php?t=2338391&highlight=boot+loop did the trick.
fastboot erase cache
fastboot reboot
The device started booting but hung on the CM logo for far too long. I hard rebooted and installed an updated version of TWRP and then wiped and flashed the ROM over again. More updates to follow.
Well the device worked for the night but when I rebooted it this morning it immediately began the boot loop situation again. I RUU'd once and it got stuck in another boot loop. I got it to boot after hard powering down and it loaded the factory ROM. I rebooted back to the bootloader and flashed TWRP 2.5.0.0 and tried to reboot. Another boot loop. Hard power cycling didn't solve it either, so I pushed the RUU for a second time. Now the device refuses to boot into anything other than the boot loader -- the initial issue from this post -- and no amount of hard power cycling makes a difference.
The phone is currently showing as LOCKED in the boot loader so I dropped it off at the Sprint store to see if they could find anything physically wrong etc. More updates as they are discovered in the hopes that if someone else ever experiences this, they have something to reference.
Thanks for posting. Did you solve the problem? I think I'm having something similar.
Phone got hung up during a super wipe and i held the power button down and turned it off. It felt stupid while I was doing it, but I waited a good 30 minutes and really felt like I didnt have a choice. I can get into my bootloader but not recovery. Keeps rebooting to splash screen. Tried to fastboot flash the recovery image but i get failed remote: not allowed. not sure what else to do. If anyone has any ideas, I would be greatful.
s-off
hboot-2.09.0000
openrecovery-twrp-2.6.3.0-jewel-selinux.img
Nevermind. I dont know what happened. I left it on the splash screen for a while and the boot animation for the rom started. It never did boot, so i went back into bootloader, tried to fastboot flash the recoverery image again - failed. Tried recovery again and it started. Restored my backup - and my phone is back from the dead once again.
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
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.