Stuck in endless flash - Verizon HTC One (M8)

Using TWRP to flash Orion ROM. and it's been about 20 minutes now and it is still flashing there are no buttons to tap to get it to do something....the power button locks the screen while the vol down button gives "e: another threaded action is already running 1 actions starting with timeout".
Anybody know what this means and how do I interrupt it and start the flash over? (I've never seen this before.)

Related

Having problems booting into CWM Recovery from off

I can boot to recovery from the OS. However, I can't boot to recovery via the 3 button combo.
I hold power and both volume buttons and then it keeps "restarting" looping through the AT&T screen. I then release the power button and hold the 2 volume buttons and it always boots to the OS.
What am I doing wrong. I've tried this a bunch now
Thanks,
JOe K.
P.S. I'm trying to reset the battery stats and I'm running Supernova 2.02b
3 button fix
Hi Joe,
I had this problem too. A lot of captivates have 3 button recovery disabled by default. To be able to use 3 button recovery you'll need to flash this 3buttonfix.zip (also fixes download mode) using clockwork mod or the recovery mod of your choice. Reboot you phone then turn it off and try starting recovery with the buttons.
The fix should stay even if you flash new roms, but if you flash to stock you'll need to reinstall the fix.
You are responsible for what you do to your phone, use at your own risk, etc. etc.
Best of luck,
DStan

Cannot boot into recovery!

Hey guys! I just got a One X from AT&T bought on eBay, although I live in Europe.
I managed to unlock the bootloader by changing the CID to 1111111 etc. (how many 1's?) and it worked fine.
I then ran installed ClockworkMod Touch Recovery for the HTC One X through terminal and it was a success.
I rebooted by holding down the power and volume down, and attempted to boot into recovery. I got a white screen with the HTC logo, and red text underneath saying something like "do not use this without HTCs permission" or something of the sort. The phone then turned off.
NOW I'm trying to boot again into the bootloader (I think that's what it's called, but by turning it off and holding the volume down and power key) and it just doesn't work. I've tried a million times, with different variations of holding down the keys. What happens is the light on the touch keys at the bottom flashes a bunch of times, then it boots normally. Everything works on the phone otherwise.
I tried to do it via fastboot/terminal by issuing the command ./fastboot-mac reboot-bootloader but it just says "waiting for device..." even though it's connected.
Anyone had this problem and found a solution?
Recovery
Clockwork recovery is not supported on the evita. Download goo manager and you should be able TWRP from that. And then you can reboot into TWRP.
I think you flashed CWM for the international (Tegra3 quad core) One X. Install TWRP as previous poster recommended.
There is no version of CWM Touch Recovery that is supported for the AT&T One X. You flashed the international version. Fortunately, you can flash TWRP right over it inside Goo Manager.
Be thankful you didn't flash it inside ROM Manager or you could have bricked your phone. I've seen people do it in the past.
ansedve season
Thanks guys, and glad I didn't brick the phone!
I installed Goo Manager and installed OpenRecovery Script, and managed to attempt to go into recovery, but again got the white HTC screen and something about "development purposes only" in red text.
I think I'm really lost on this one, any help would be great, like a link to a tutorial?
in fastboot run this command "fastboot erase cache", then boot into recovery.
DvineLord said:
in fastboot run this command "fastboot erase cache", then boot into recovery.
Click to expand...
Click to collapse
Don't be too concerned with the blah blah in red writing about development version etc. on the boot screen - you get that boot screen when you unlock the bootloader.
mollysue said:
Thanks guys, and glad I didn't brick the phone!
I installed Goo Manager and installed OpenRecovery Script, and managed to attempt to go into recovery, but again got the white HTC screen and something about "development purposes only" in red text.
I think I'm really lost on this one, any help would be great, like a link to a tutorial?
Click to expand...
Click to collapse
What did you do in recovery? Did you flash anything? Does the phone not boot up now?
Thanks guys for all your help. I guess know I technically know what to do to fix things, thanks to you. The only problem that after probably over 100 failed attempts I cannot boot into recovery. I tried all variations of holding the power and volume down button while restarting, rebooting, turning on/off or up/down sideways but it just boots normally every time.
This means I can't use fastboot etc. I guess unlocking the bootloader and voiding the warranty was for nothing
If you know another way to reboot into bootloader other than the hardware buttons method let me know!
Believe it or not, I think you are just performing the button presses incorrectly, if you can't access the bootloader. Bootloader is probably still intact, otherwise the phone would not be working at all.
1) In Settings>Power, make sure "fast boot" is not checked.
2) Then power the phone off fully, but holding the power button until the power menu comes up, and select "Power off". Wait a minute for the phone to power off completely.
3) Hold down the volume down rocker. DO NOT release it until I tell you to later.
4) Press the power button for 3 seconds, then release. DO NOT release the volume down rocker.
5) Once the white bootloader screen shows up, release the volume down rocker.
Alternately, you can do this:
a) With the phone powered on, hold the power button until the capacitive buttons flash (about 5 seconds).
b) The moment the screen goes black, hold down the volume down rocker, (again, DO NOT release it until the bootloader screen comes up) but release the power button.
The timing for this method is a little trickier, if you press the volume down rocker too late, it will boot normally (or safe mode), and too soon, and it just reduces the ringer volume and the phone stays on. But as long as you press and hold volume down the moment the screen goes black, it will work.
---------- Post added at 10:13 AM ---------- Previous post was at 10:11 AM ----------
But also, I would still not recommend trying to boot into recovery until you have installed the TWRP recovery as mentioned previously on this thread, if you have not done so already. There is no CWM Touch Recovery for this phone, so I'm pretty certain you installed in improper recovery on the phone, and recovery will not function at all.
Alternatively, you can go into Goo Manager and select the "Reboot Recovery" option, which should get you into TWRP
Or from command prompt "adb reboot bootloader" so long as you open your prompt from your adb application folder.
Or alternatively skip the middle man: "adb reboot recovery"
I really think your problem lies with your button pressing -- follow instructions on the previous post and you should be home free.
Well I actually eventually managed it! I think the volume button was a bit stuck because it still takes a few tries to boot into bootloader, but eventually I managed it and am in the TWRP menu right now!
I did a little victory dance when it happened. Thanks again!

LG G Pro F350S Can't Boot To Recovery After Lolipop Upgrade

Typical steps to enter recovery mode not working (F350S model)
I have F350S model which I rooted, and accidentally deleted "phone" from the system apps. Was unable to make calls or texts, and I could not find any help to reinstall the deleted "phone" apk (it may not be so simple to "just re-install it", I suppose). My solution was to re-stall a fresh stock ROM (it is 4.4 kitkat),.......BUT....I cannot find any stock ROM online for this phone. So, I decided to use Lollipop upgrade (Future 3.2 ROM).
I installed Lollipop, and everything appeared to be successful. I made phone call and texts, had wifi, and was re-installing my games and social media apps. Then, suddenly, I get an error "Unfortunately, LG IMS has stopped." The error is persistent. I cannot get away from it. I say "OK" and it just comes back. I have no idea what "LG IMS" is, or why it stopped.
I figure I will just re-install the Future 3.2 ROM again and start over. I need to enter recovery mode, and the instructions to do this are one of three possible ways:
1.) Power off, then hold POWER and VOLUME DOWN buttons. When startup logo appears, RELEASE, and then hold POWER and VOLUME DOWN buttons again, and then phone should enter recovery mode. But it does not! It just boots up to the "LG IMS has stopped" error, again,
or 2.) Power off, then hold POWER and VOLUME DOWN buttons. When startup logo appears, release POWER BUTTON ONLY (keep holding VOLUME DOWN button, do not release), then press POWER button again. Phone should enter recovery mode, but it does not! Same as above,
or 3.) Same as above, but after startup logo appears, hold down BOTH VOLUME UP AND DOWN. But...same results. No recovery mode and boots directly to persistent error.
I'm guessing my recovery feature is screwed somehow. How do I fix this? I cannot enter recovery mode using the buttons and directions I have seen for this phone. I've tried a few other variations of button pressing too. No avail. There has to be a solution!!!
Ken B. said:
I have F350S model which I rooted, and accidentally deleted "phone" from the system apps. Was unable to make calls or texts, and I could not find any help to reinstall the deleted "phone" apk (it may not be so simple to "just re-install it", I suppose). My solution was to re-stall a fresh stock ROM (it is 4.4 kitkat),.......BUT....I cannot find any stock ROM online for this phone. So, I decided to use Lollipop upgrade (Future 3.2 ROM).
I installed Lollipop, and everything appeared to be successful. I made phone call and texts, had wifi, and was re-installing my games and social media apps. Then, suddenly, I get an error "Unfortunately, LG IMS has stopped." The error is persistent. I cannot get away from it. I say "OK" and it just comes back. I have no idea what "LG IMS" is, or why it stopped.
I figure I will just re-install the Future 3.2 ROM again and start over. I need to enter recovery mode, and the instructions to do this are one of three possible ways:
1.) Power off, then hold POWER and VOLUME DOWN buttons. When startup logo appears, RELEASE, and then hold POWER and VOLUME DOWN buttons again, and then phone should enter recovery mode. But it does not! It just boots up to the "LG IMS has stopped" error, again,
or 2.) Power off, then hold POWER and VOLUME DOWN buttons. When startup logo appears, release POWER BUTTON ONLY (keep holding VOLUME DOWN button, do not release), then press POWER button again. Phone should enter recovery mode, but it does not! Same as above,
or 3.) Same as above, but after startup logo appears, hold down BOTH VOLUME UP AND DOWN. But...same results. No recovery mode and boots directly to persistent error.
I'm guessing my recovery feature is screwed somehow. How do I fix this? I cannot enter recovery mode using the buttons and directions I have seen for this phone. I've tried a few other variations of button pressing too. No avail. There has to be a solution!!!
Click to expand...
Click to collapse
I think this is the same from F320S from my Wife.
Press and Hold Power and Volume Down When startup logo appears, RELEASE and Press and Hold Power and Volume Up
until the Korean characters Comes and a little longer
letschky said:
I think this is the same from F320S from my Wife.
Press and Hold Power and Volume Down When startup logo appears, RELEASE and Press and Hold Power and Volume Up
until the Korean characters Comes and a little longer
Click to expand...
Click to collapse
Thank for reply, but this button combo no worky, either.
If I hold down ALL THREE BUTTONS, I get a Korean screen, IMEI number with barcode, with 3 options, but I cannot tell what any of it says. I tried all 3 options, and they all just cause the phone to restart. Not sure what they do.
any further information ? I get entering the recovery problem too !
If you are using custom recovery (TWRP or CWM) to enter the recovery press and hold the POWER and VOL UP while your phone is turned off, wait for the Korean characters to appear then release the buttons.

[tips & tricks][emergency button combinations]

My First Post Thread On This Sub-Forum. So Please be Lenient.
A Couple of weeks ago I switched my primary device from Asus Zenfone 2 to Oneplus One 64gb.
A while before that... One of my friends who also owned a One got stuck on the boot logo after flashing an incompatible kernel. As the phone did not have a removable battery.. He had no idea how to go back into TWRP.
I figured that A few (maybe more) of the users would have the same kind of doubts for this device. And hence for them... I've made this simple guide.
SCENARIO 1:
•Phone Freezes,
•goes into SoD (Sleep of Death) ,or
• (practically anything that happens when booted into android but rendering most controls useless),or
• Phone Accidentally booted into fastboot mode without a PC nearby.
Fix it:
These can be easily fixed by forcing a REBOOT on the device.
How:
Press and hold the POWER BUTTON only for about 8-10s.
This will cause a reboot.
This method will work anywhere and everywhere on a one. This can be used to force a reboot in any situation.
SCENARIO 2:
•Phone stuck on boot logo /boot animation after incompatible ROM/Kernel/mod etc flash.
•When causing a Simple reboot won't help. And we need to boot into recovery or fastboot mode.
For this we need to first force a shutdown and then a normal reboot to either recovery or fastboot.
How:
Press and hold down the POWER + VOLUME DOWN Buttons for about 8-10s. The phone will power off.
Then
•For recovery press and hold POWER + VOLUME DOWN for 2-3s
•For fastboot press and hold POWER + VOLUME UP for 2-3s.
And That's it. We've successfully learned how to simulate a battery pull on the One.
NOTE: Please remember that these button combinations are universal. This means they can be used with any ROM or any kernel or even No ROM or no kernel.....lol.
Thanks.
Sent from my A0001 using Tapatalk

Nexus Soft? brick - multirom - no adb/fastboot possible

Hello,
unfortunately I can not report details but today there was an error not finding a /system partition in TWRP recovery. I tried to re-install the lineage-nightly build (01/24/17) which worked before but after that I could not boot the os anymore.
When I reboot I see the Google screen and then the multirom screen for a short while but neither the internal rom nor the others are booting. I can select the menu option to reboot to the bootloader or enter the bootloader by pressing power and volume keys. But I can see the screen for only one second and quickly try to select options without effect before the phone tries to boot again.
The command line program: "adb wait-for-device can not find the device doesn't detect the phone during that time.
Can somebody help?
Thanks
try flashing factory images through fastboot
Sounds like the phone could have the dreaded power button problem.
Thank you very much for your replies.
The problem is that the fastboot mode only shows up for a very short time. I can select the options with the volume keys but when I want to confirm with the power button, the phone already reboots.
I can also enter the multirom menu and select options on the touchscreen but short after it reboots again.
So maybe it really is a hardware issue, although I find the button presses like before.
This means I have to open and clean if not manipulations at the button are helpful.
Next I will try to boot from multirom menu over otg/usb to save stored data.
Is there another way if that fails?
Thanks again
Thank you audit13! That was it, the power button Problem.
I repeated sliding over the power button for several times and was able to get back the correct function.
Open the phone and gently clean around the power button with pure isopropyl alcohol.. After using the alcohol, firmly press and release the power button several times in a row and then try to boot the phone.
Edit: Glad you got it working:good:

Categories

Resources