So, a few times my One has frozen up during install of Kernels and ROMs. I usually get it reboot after multiple endless tries of pushing various combinations of power buttons/volume keys but it can take 30 min or more. Has anybody found somewhat of a consistent method to get the device up and running quickly?
I'm using sk8's cwm and no longer have aroma issues
gunnyman said:
I'm using sk8's cwm and no longer have aroma issues
Click to expand...
Click to collapse
Ok, will give ot a try. Can I just flash CWM over my existing TWRP?
GermanGuy said:
Ok, will give ot a try. Can I just flash CWM over my existing TWRP?
Click to expand...
Click to collapse
absolutely, but be aware that nandroid backups aren't cross compatible, so if you are on a custom rom and you want to restore your stock nandroid, you have to restore it to the phone in twrp then install cwm, then back up again with cwm.
Hold Power and Vol+Down for about 10 seconds (back and home will flash after about 5 seconds) the phone will reboot. Then let go for a second and hold them again to take you back into the bootloader then go back to recovery.
bdoople said:
Hold Power and Vol+Down for about 10 seconds (back and home will flash after about 5 seconds) the phone will reboot. Then let go for a second and hold them again to take you back into the bootloader then go back to recovery.
Click to expand...
Click to collapse
This did not work for me. I know that theoretically it should, but it did not.
Unfortunately, Sk8 CWM Touch did not prevent a lockup I experienced last night in Aroma flashing Renovation ROM and choosing full wipe. Man, I hope they can make Aroma more stable.
GermanGuy said:
Unfortunately, Sk8 CWM Touch did not prevent a lockup I experienced last night in Aroma flashing Renovation ROM and choosing full wipe. Man, I hope they can make Aroma more stable.
Click to expand...
Click to collapse
If you hold the power button down it should start blinking the back and home lights after 5 seconds. After they flash 15 times the phone will shutdown. Doesn't matter if you're in aroma, recovery, hboot... Where ever you are it should do this.
Sent from my HTC One using Tapatalk 2
anit77 said:
If you hold the power button down it should start blinking the back and home lights after 5 seconds. After they flash 15 times the phone will shutdown. Doesn't matter if you're in aroma, recovery, hboot... Where ever you are it should do this.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
The problem is that this expected behavior is inconsistent on the AT&T HTC One. Whether I am on the stock ROM or an International ROM, it will work the first time. After reboot, if I try it again it will not work. After a few tries later on it might work again.
Related
I've been wondering and searching how to boot into recovery on the thunderbolt? Not from rom manager but when the phone is off. When i had my original moto droid all i had to do was turn it off then turn it on while holding x and i was in recovery how do i do that on the thunderbolt?
And if someone would be so kind as to explain what hboot is thanx!!
hboot is htc's bootloader, mainly used for flashing radio's and flashing stock ruu's. From what i know if u boot in to hboot, power + volume down button, then click recovery, it will boot into the recovery.
rickyotten said:
I've been wondering and searching how to boot into recovery on the thunderbolt? Not from rom manager but when the phone is off. When i had my original moto droid all i had to do was turn it off then turn it on while holding x and i was in recovery how do i do that on the thunderbolt?
And if someone would be so kind as to explain what hboot is thanx!!
Click to expand...
Click to collapse
Let's see if I get this right:
hboot is the default bootloader. Press at the same time, and hold, power and volume down to get into the bootloader.
From within the bootloader you can choose to enter recovery.
the_happy_cannibal said:
Let's see if I get this right:
hboot is the default bootloader. Press at the same time, and hold, power and volume down to get into the bootloader.
From within the bootloader you can choose to enter recovery.
Click to expand...
Click to collapse
Yup . Assuming you installed a custom recovery like CWR already tho.
i had to hold both volume up and down buttons
Beastclaw said:
Yup . Assuming you installed a custom recovery like CWR already tho.
Click to expand...
Click to collapse
Is there are way to boot into the default recovery (is there are default recovery?)
Every time I attempt this, it defaults to hboot, looks for a radio zip, tells me there isn't one(because there's not one on the sdcard), and only gives me the option to reboot by pressing power. I briefly see the initial menu, with the options for recovery and such under hboot, but I cannot select them with the volume up or down buttons?
Bateluer said:
Every time I attempt this, it defaults to hboot, looks for a radio zip, tells me there isn't one(because there's not one on the sdcard), and only gives me the option to reboot by pressing power. I briefly see the initial menu, with the options for recovery and such under hboot, but I cannot select them with the volume up or down buttons?
Click to expand...
Click to collapse
are u sure there is no PB...img on ur sd? That's the only reason this would happen.
Spencer_Moore said:
are u sure there is no PB...img on ur sd? That's the only reason this would happen.
Click to expand...
Click to collapse
My mistake, there is. If that radio zip file is there, you cannot move up and down through the menu then? I got a botched ROM here, hangs on the boot animation, no ADB, and no way to read that sdcard outside the phone.
Edit - If I remove the sdcard, I can do a wipe cache&data factory reset, I think? But my ROM files are on the sdcard.
Can you still use cwr without a battery if its plugged in? I know I could on the OG Droid, so if this still works, you can just take the SD card out, go to hboot and select recovery, then put the SD card back in
Sent from my ADR6400L using XDA App
akstyle450 said:
Can you still use cwr without a battery if its plugged in? I know I could on the OG Droid, so if this still works, you can just take the SD card out, go to hboot and select recovery, then put the SD card back in
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
I just attempted this, without the battery, I cannot even get a pulse from the TB. With the battery in and no sdcard, I can get into CWR from hboot. Second I remove the battery from the phone, it powers off. Doing this with it plugged into the wall AC too.
Edit - This is where I'm at right now. If I remove the sdcard, wipe cash&data, I can boot into a mostly broken ROM. Specifically, the keyboard FCs immediately, I can skip past the HTC setup screens, the virtual keyboard will generate another FC. At the end of the setup screens, it'll go to a blank background with no icons and the status bar on top, showing 3G signal strength, time, etc. There's nothing on the screen but that. If I push and hold power, it brings up the Power menu, to shutdown, restart, etc. Any option thoroughly locks the phone and requires a battery pull. After that, it'll get stuck in a boot loop at the boot animation until I get into CWR again and wipe cache/data. And I've left it go for a good 20 minutes, more than enough time to rebuild the dalvik.
I should add that this was slightly, as in totally, self inflicted. :/ I was switching ROMs, rolled back from the GB leak radio to the froyo radio, and was wiping cash&data to move to a froyo ROM; got interrupted by another task, and forget where I was at. Basically, I wiped cache&data without flashing a ROM afterward.
Edit - Had to wait until I got home from work. Install the card in a sled, delete the zip, everything's good now.
Im just stuck at the Thunderbolt wallpaper. I tried removing the sd card, battery and all that crap but still stuck. Any way I can work around this?
Droid_Evo_8 said:
Im just stuck at the Thunderbolt wallpaper. I tried removing the sd card, battery and all that crap but still stuck. Any way I can work around this?
Click to expand...
Click to collapse
Boot into hboot and then into recovery to flash a backup you hopefully made and if not just re-flash your ROM. Happened to me once when I rushed through a new ROM flash and didnt verify the MD5. If you dont have a ROM or a backup saved on your card then you can try to do what the guy above you did and put your card into a reader and put one on there that way.
Power and volume down
THUNDERBOLT
I flashed Joelz ICS beta 1 for my Evo after using his ICS Alpha X prior. When I decided I didn't like the beta 1 and went back to Alpha X, I found that the capacitive buttons became unresponsive about 50% of the time. I used Flash Image GUI to re-flash, then went to TWRP Recovery and flashed it there (wiped everything both times). Now I can press the buttons sometimes, but they only work 50% of the time, and I can't long-press. It also likes to click the bottom of the touchscreen instead of the buttons (like the dock bar in the launcher), even though I'm obvious touching the buttons. Anybody experience this or have any troubleshooting ideas?
Cwebb03 said:
I flashed Joelz ICS beta 1 for my Evo after using his ICS Alpha X prior. When I decided I didn't like the beta 1 and went back to Alpha X, I found that the capacitive buttons became unresponsive about 50% of the time. I used Flash Image GUI to re-flash, then went to TWRP Recovery and flashed it there (wiped everything both times). Now I can press the buttons sometimes, but they only work 50% of the time, and I can't long-press. It also likes to click the bottom of the touchscreen instead of the buttons (like the dock bar in the launcher), even though I'm obvious touching the buttons. Anybody experience this or have any troubleshooting ideas?
Click to expand...
Click to collapse
TWRPhas givin me a few other folks dirty flashes man. 2.0 TWRP. I am using CWM at the moment hasn't failed yet.
I would throw CWM run a stock rom and stock kernel.
Wipe everything. Adb reboot bootloader. Then fastboot flash boot boot.img of the stock kernel. Flash the new stock rom. Should clear ur issue maybe.
reaper24 said:
TWRPhas givin me a few other folks dirty flashes man. 2.0 TWRP. I am using CWM at the moment hasn't failed yet.
I would throw CWM run a stock rom and stock kernel.
Wipe everything. Adb reboot bootloader. Then fastboot flash boot boot.img of the stock kernel. Flash the new stock rom. Should clear ur issue maybe.
Click to expand...
Click to collapse
Thanks for the advice man, I'll try it tomorrow because I have to get up in 7 hours. I feel like I should just PM you instead of posting a thread from now on, you always seem to have the answers
Cwebb03 said:
Thanks for the advice man, I'll try it tomorrow because I have to get up in 7 hours. I feel like I should just PM you instead of posting a thread from now on, you always seem to have the answers
Click to expand...
Click to collapse
Feel free to man. Hope it is just a dirty flash not hardware. I know a dirty kernel flash can due some weird ****.
Here is the recovery I use ...
I just got an Evo 3D and I am trying to flash a custom recovery image. I used htcdev to unlock my phone, then I flashed the latest Clockwork mod recovery image to the phone using fastboot, but when I try to boot into recovery from the bootloader it just reboots and it never takes me into recovery. Ive tried flashing a few different recoveries in the hopes that I just got a bad file but nothing works. Any ideas?
brandenk said:
I just got an Evo 3D and I am trying to flash a custom recovery image. I used htcdev to unlock my phone, then I flashed the latest Clockwork mod recovery image to the phone using fastboot, but when I try to boot into recovery from the bootloader it just reboots and it never takes me into recovery. Ive tried flashing a few different recoveries in the hopes that I just got a bad file but nothing works. Any ideas?
Click to expand...
Click to collapse
Try downloading 4ext from play store, after inatalling it will walk you thru the set up to flash the recovery
Can you get into the bootloader by doing the following:
- Pull out the battery
- Put the battery back in
- Hold the volume down button
- Hold down the power button while still continuing to hold down the volume down button
From there you should go str8 to the bootloader screen rather than the splash screen.
If you get to the bootloader screen, are you able to get into the recovery from the bootloader menu?
Sent from my HTC EVO 3D X515a using xda premium
Yea, do the battery pull, you can also unchecked 'fastboot' in settings, power.
"We're coming from a pure power source."
jura69 said:
Can you get into the bootloader by doing the following:
- Pull out the battery
- Put the battery back in
- Hold the volume down button
- Hold down the power button while still continuing to hold down the volume down button
From there you should go str8 to the bootloader screen rather than the splash screen.
If you get to the bootloader screen, are you able to get into the recovery from the bootloader menu?
Sent from my HTC EVO 3D X515a using xda premium
Click to expand...
Click to collapse
I have tried.....but same with question from brandenk
metalfan78 said:
Yea, do the battery pull, you can also unchecked 'fastboot' in settings, power.
"We're coming from a pure power source."
Click to expand...
Click to collapse
Sent from my HTC EVO 3D X515m using xda premium
So since I posted, I have made it to the next step. I have TWRP recovery installed and working, but for some reason the whole boot.img and kernal flashing doesnt work. After trying for another couple hours trying to install MeanROM I have had no success. Flashing the ROM from recovery works fine, but once it gets to the step of updating the kernal, it just freezes and I had to pull the battery (waiting 10+ minutes). After doing so, I could get past the boot screen, but it would never properly load the ROM, I just got an endless status bar and black screen. I went through this process a couple of times before I decided to restore to my original nandroid backup. Even restoring the backup caused it to hang when it got to restoring boot.img. After waiting another 10 minutes I pulled the battery and rebooted and luckily was able to get into the stock Sense ROM, which is better than nothing, but I really wish I could install a ROM like MeanROM.
brandenk said:
So since I posted, I have made it to the next step. I have TWRP recovery installed and working, but for some reason the whole boot.img and kernal flashing doesnt work. After trying for another couple hours trying to install MeanROM I have had no success. Flashing the ROM from recovery works fine, but once it gets to the step of updating the kernal, it just freezes and I had to pull the battery (waiting 10+ minutes). After doing so, I could get past the boot screen, but it would never properly load the ROM, I just got an endless status bar and black screen. I went through this process a couple of times before I decided to restore to my original nandroid backup. Even restoring the backup caused it to hang when it got to restoring boot.img. After waiting another 10 minutes I pulled the battery and rebooted and luckily was able to get into the stock Sense ROM, which is better than nothing, but I really wish I could install a ROM like MeanROM.
Click to expand...
Click to collapse
Try 4ext Recovery (see my signature). It will flash the kernel properly for S-on users.
It didnt work for me, I am still on the stock ROM so I dont have root access. Is there a way to flash 4ext through fastboot?
EDIT: I got it installed with fastboot, trying it now. Thank you for the suggestion!
EDIT 2: I worked!!! Seriously, thank you again!
brandenk said:
It didnt work for me, I am still on the stock ROM so I dont have root access. Is there a way to flash 4ext through fastboot?
EDIT: I got it installed with fastboot, trying it now. Thank you for the suggestion!
EDIT 2: I worked!!! Seriously, thank you again!
Click to expand...
Click to collapse
Glad I could help. Welcome to the addicting world of flashing a new Rom everyday
Sent from my PG86100
I installed an update without thinking a while back on my phone. It was software version 2.13.651.1 or something, I can't remember. I rooted my phone yesterday using this method:
http://htcevohacks.com/htc-evo-4g-l...tc-evo-4g-lte-unlock-bootloadertwrp-recovery/
I can use ROM Manager to create a backup and flash recoveries. When I flash a version of CM10, it gets stuck on a bootloop. When I hold the power and volume down buttons, I see HBOOT 1.19 and S-ON.
Is there no hope for me to flash roms or is there a way that I can still do it? I've read bad things about having a HBOOT 1.15 or above or something like that. I did not get S-OFF before I updated. Can I no longer get S-OFF? I'm not entirely sure what S-OFF is and what I need it for.
I read somewhere on xda that people who have a HBOOT like mine should try this:
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
I'm going to try that now, let's see how it goes.
If you use fastboot to install kernels you should be good to go after a normal flash through recovery, my phone came s-on and hboot 1.19 and I have no problems flashing roms. Only thing I think we can't do are radios without an official update, don't quote me on that though..
Your not screwed. You won't be able to get s-off at this time, but you can still flash roms. When moving from a sense rom to aosp like cm10, you need to flash the kernel...i use flash gui. I'm guessing that is why you are getting the bootloop.
Sent from my EVO using xda premium
Thank goodness, phew; I thought I was doomed. So if I am to follow #1 on here: http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html, I should be able to flash roms afterwards? Do I need to do this every time I want to flash a new rom?
EDIT: So I believe my phone ran out of battery during the school day stuck in the bootloop. I am charging it right now and the orange light is there. When I hold down the power and volume down buttons, I get nothing. The screen stays black, but the orange light disappears. Then the orange light comes back. Should I just let it charge?
You just need to do it when switching between different type of roms like aosp and sense. If you stick with cm10 you can just flash the rom after the first time.
Sent from my EVO using xda premium
Adding on to my last edit, sometimes when I hold down the power and volume down buttons, the 3 virtual buttons blink and then go out as if rebooting my phone. The screen is always black. Nothing is showing up. Should I be worried or do I just need to be patient and wait for my phone to charge a little?
When the screen turns off let go of the power button for a second then hold it down again while continuing to hold down the volume down button. That should boot you into recovery.
Sent from my EVO using xda premium
gmugrad04 said:
When the screen turns off let go of the power button for a second then hold it down again while continuing to hold down the volume down button. That should boot you into recovery.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
The screen is black no matter what I try. I've tried just pressing the power button to turn the phone on, holding power and volume for recovery, holding power button, nothing is working. The screen remains blank no matter what I do right now. Is it just too low battery right now to do anything?
M-man10 said:
The screen is black no matter what I try. I've tried just pressing the power button to turn the phone on, holding power and volume for recovery, holding power button, nothing is working. The screen remains blank no matter what I do right now. Is it just too low battery right now to do anything?
Click to expand...
Click to collapse
Most likely. Give it some charge and try again.
Sent from my EVO using xda premium
I have no idea why, but CM10 just started working. It was getting stuck in the bootloop for the whole day and even after I had done everything I posted earlier. Just now I tried to RUU and that wasn't working. When it came up with my phone's image version, it was blank. It was saying upgrade from nothing to 2.13.651.1.
I decided to repeat steps from the rooting process I used yesterday: http://htcevohacks.com/htc-evo-4g-l...tc-evo-4g-lte-unlock-bootloadertwrp-recovery/
I did step 25 again and then I did it again, but this time I flashed the stock recovery rom. For some reason unknown to me, CM10 actually loaded through and worked this time. Was something wrong with the other recoveries? I'm just glad it's working.
M-man10 said:
I installed an update without thinking a while back on my phone. It was software version 2.13.651.1 or something, I can't remember. I rooted my phone yesterday using this method:
http://htcevohacks.com/htc-evo-4g-l...tc-evo-4g-lte-unlock-bootloadertwrp-recovery/
I can use ROM Manager to create a backup and flash recoveries. When I flash a version of CM10, it gets stuck on a bootloop. When I hold the power and volume down buttons, I see HBOOT 1.19 and S-ON.
Is there no hope for me to flash roms or is there a way that I can still do it? I've read bad things about having a HBOOT 1.15 or above or something like that. I did not get S-OFF before I updated. Can I no longer get S-OFF? I'm not entirely sure what S-OFF is and what I need it for.
I read somewhere on xda that people who have a HBOOT like mine should try this.:
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
I'm going to try that now, let's see how it goes.
Click to expand...
Click to collapse
Thank You So Much for posting that link! I have been searching everywhere to figure it out how to flash rom to rom. My first rom was Meanrom ICS and I didn't have to do anything extra with that. So when I wanted to flash first to CM10, then JellyBam, I couldn't understand why I kept getting stuck in bootloop. I figured out eventually it was all about boot.img, but couldn't figure out how to do it separately.
thanks again.
please help, what can i do?
is the green- hardware or software related? i dont think i banged it or got hit..
new-to-it said:
please help, what can i do?
is the green- hardware or software related? i dont think i banged it or got hit..
Click to expand...
Click to collapse
I know you will be loosing everything, well unless you have a backup. I would suggest NVflash back to stock with CWM recovery. Then reload the ROM of choice to see or even just boot it into TapUI so see if the problem is Hardware related or UI related. It is tough to say.
i think its hardware, i gave it a nice hard wack and it seems ok...
the thing is i started to save/backup and go back to tap tap. thinking ill use my warrantee,
now it is stuck in a boot mode, turns on, starts to run but only getting to the tap embelm. it does this over and over maybe 6 second intervals..
any ideas??
i cannot get to cwm, and reload gtab or do anything. am i screwed??
new-to-it said:
i think its hardware, i gave it a nice hard wack and it seems ok...
the thing is i started to save/backup and go back to tap tap. thinking ill use my warrantee,
now it is stuck in a boot mode, turns on, starts to run but only getting to the tap embelm. it does this over and over maybe 6 second intervals..
any ideas??
i cannot get to cwm, and reload gtab or do anything. am i screwed??
Click to expand...
Click to collapse
Try NVflashing with the stock 1.1 BL with recovery ver.8 preinstalled, after done power device off by holding down power button. The just boot straight to recovery and do a data wipe factory reset then reboot system. The reason for the boot loop is there is still something on the name that the tnt software doesn't like. After you get it booted up then advice just NVflash 1.1 stock with stock recovery and it should boot right up afterwards. The reason for the 2nd nvflash is to remove any tracef the customs recovery.
Sent from my SGH-T989 using xda app-developers app
ok i think i got it.....
new-to-it said:
ok i think i got it.....
Click to expand...
Click to collapse
Sounds like that you are using the NVflash with Stock recovery. When you hold down volume + and press the power button it is booting into stock recovery hence the triangle symbol. You need to get a fresh NVflash setup that includes CWM recovery and use it.
Sent from The Darkside via Me...