My One won't boot and it also won't boot into recovery. I can get it into Hboot, though. I have tried reflashing a recovery and that has not worked. It happened after installing ARHD 7.1. Any help in appreciated at how to fix this.
fastboot erase cache
hello00 said:
fastboot erase cache
Click to expand...
Click to collapse
That did it. Thanks!
Related
For those who flashed the 1.29 RUU and are boot looping and a wipe isn't fixing it:
Go into the recovery.
Go to wipe.
Go to advanced.
Tell it to reformat your cache partition.
I've only tested it on one phone but it may be that the RUU is corrupting the cache partition before failing and thus leaving you with a boot looping phone.
Or, since you're already in fastboot...
Code:
fastboot erase cache
CNexus said:
Or, since you're already in fastboot...
Code:
fastboot erase cache
Click to expand...
Click to collapse
Yep, if you have access to a computer, you can also do that as well.
I used the CM app and Windows to unlock, and root my ATT One. I've tried several times to use Flashify to flash TWRP./ It will load and get me to the TWRP main menu, but it freezes and I have to hold volume down and power to get to recovery to reboot. Am I stuck with CWM?
Did you do
fastboot erase cache
?
BenPope said:
Did you do
fastboot erase cache
?
Click to expand...
Click to collapse
sorry, no I didn't. I'll give that a try.
Hi folks,
I have a problem. I tried to flash SinlessRom GE Kitkat 5.1. It flashed allright, but then I got in a boot loop. It boots, but when the set up starts, and I see the screen where to choose the language, then device boots again (and it becomes a bootloop).
I interrupted the boot loop using Vol-down and power, but my recovery wasn't working. When I chose recovery, it didn't entered recovery but booted again.
Then I tried to flash a new recovery, but now I doesn't enter a new bootloop, but get's stuck at the white HTC Screen with in pink "entering recovery..."
I tried to erase cache in fastboot modus, but it didn't help.
Do you guys can help me? Any suggestions?
wybren said:
Hi folks,
I have a problem. I tried to flash SinlessRom GE Kitkat 5.1. It flashed allright, but then I got in a boot loop. It boots, but when the set up starts, and I see the screen where to choose the language, then device boots again (and it becomes a bootloop).
I interrupted the boot loop using Vol-down and power, but my recovery wasn't working. When I chose recovery, it didn't entered recovery but booted again.
Then I tried to flash a new recovery, but now I doesn't enter a new bootloop, but get's stuck at the white HTC Screen with in pink "entering recovery..."
I tried to erase cache in fastboot modus, but it didn't help.
Do you guys can help me? Any suggestions?
Click to expand...
Click to collapse
try erasing the userdata using fastboot. I has a similar problem earlier this week and I remember using that command. Sometime when I enter recovery it just goes to normal boot (randomly), not sure if thats your problem but try entering recovery multiple times. If not...
fastboot erase userdata
fastboot erase cache
fastboot flash recovery recovery.img
wybren said:
Hi folks,
I have a problem. I tried to flash SinlessRom GE Kitkat 5.1. It flashed allright, but then I got in a boot loop. It boots, but when the set up starts, and I see the screen where to choose the language, then device boots again (and it becomes a bootloop).
I interrupted the boot loop using Vol-down and power, but my recovery wasn't working. When I chose recovery, it didn't entered recovery but booted again.
Then I tried to flash a new recovery, but now I doesn't enter a new bootloop, but get's stuck at the white HTC Screen with in pink "entering recovery..."
I tried to erase cache in fastboot modus, but it didn't help.
Do you guys can help me? Any suggestions?
Click to expand...
Click to collapse
khhhhris said:
try erasing the userdata using fastboot. I has a similar problem earlier this week and I remember using that command. Sometime when I enter recovery it just goes to normal boot (randomly), not sure if thats your problem but try entering recovery multiple times. If not...
fastboot erase userdata
fastboot erase cache
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
1- are you s-on or s-off, 4.4 is not compatible (at least for now) with S-On devices!
2- you need to "fastboot erase cache" after flashing recovery; personally i do it before and after, but the important part is after
3- why are you recommending "fastboot erase userdata", just wondering.
nkk71 said:
1- are you s-on or s-off, 4.4 is not compatible (at least for now) with S-On devices!
2- you need to "fastboot erase cache" after flashing recovery; personally i do it before and after, but the important part is after
3- why are you recommending "fastboot erase userdata", just wondering.
Click to expand...
Click to collapse
+1, s-off is required. I only recommend erasing userdata because I had a very similar issue, erasing userdata and a fresh recovery seemed to do the trick after no luck with simply flashing a new recovery and wiping cache Just going off past experience.
khhhhris said:
+1, s-off is required. I only recommend erasing userdata because I had a very similar issue, erasing userdata and a fresh recovery seemed to do the trick after no luck with simply flashing a new recovery and wiping cache Just going off past experience.
Click to expand...
Click to collapse
good to know, was "fastboot erase userdate" successfully? what kind of output did you get?
nkk71 said:
good to know, was "fastboot erase userdate" successfully? what kind of output did you get?
Click to expand...
Click to collapse
Thanks all for the response.
This did the trick:
erase cache
flash twrp recovery (first I tried cwm)
erase cache
Then I managed to enter twrp recovery and flash a new rom.
Don't know why, but I'm happy again
Thanks for the help.
Cool.. hit the users's thanks button!
Now my SU is giving me trouble, it doesn't work or the su exe file is missing. No problem, I'll reflash the zip.
I still have the stock recovery, so I:
fastboot boot recovery.img
but when I do that , it appears to succeed, but hangs the phone on the fastboot screen.
So I can't boot or flash a custom recovery.
Tried goomanager, that didn't work either.
Any help appreciated in getting su working again, and/or installing a custom recovery and/or ROM.
Thanks!
bilybob said:
Now my SU is giving me trouble, it doesn't work or the su exe file is missing. No problem, I'll reflash the zip.
fastboot boot recovery.img
Thanks!
Click to expand...
Click to collapse
that only worked with hboot 1.44, you're going to have to flash it.
I tried flashing - that didn't work either. I did:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
Same problem. Are you certain this should work?
Thanks
bilybob said:
I tried flashing - that didn't work either. I did:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
Same problem. Are you certain this should work?
Thanks
Click to expand...
Click to collapse
try erasing cache.
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
That seems to have worked.
Not sure if it was the cache erase or I believe I was missing the recovery from:
fastboot flash recovery recovery.img
I just had:
fastboot flash recovery.img
Anyway, I have re-flashed the SU pkg and all appears good now.
Thanks very much for the help from each of you.
khandelwalsiddharth said:
try erasing cache.
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
Click to expand...
Click to collapse
If I am not mistaken and read it wrong, SuperSu needs to be updated with the OTA 4.3 read this link http://www.androidpolice.com/2013/0...persu-update-to-v1-43-to-fix-the-100-cpu-bug/
Hey guys,
I've got a big problem with my recovery. But first things first: I got my One (M7) about two or three weeks ago, flashed TWRP 2.8.3.0 and rooted via flashing the SuperSU.zip.
Yesterday I finally had time to install CM11. So I wanted to enter the recovery, first via the Power-Off menu (have a XPosed Module that added a shortcut for it) then via the bootloader and then via ADB. The "Entering-Recovery..."-Screen appears, then disappears for 2 seconds and then reappers and the phone is stuck with it, nothing happens, TWRP doesn't start.
So I tried to reflash the recovery via ADB but it doesn't help.
Does anyone have an idea about how I get my recovery working again?
Greetings from germany
Edit: If it helps: I'm on stock rom with S-On on HBOOT 1.57
fastboot erase cache
Already tried that after installing TWRP. Shall I do that before installing?
Edit: I tried fastboot erase cache now pre- and past-flashing TWRP 2.8.4.0.... nothing's changed
NotoriusBB said:
Already tried that after installing TWRP. Shall I do that before installing?
Edit: I tried fastboot erase cache now pre- and past-flashing TWRP 2.8.4.0.... nothing's changed
Click to expand...
Click to collapse
Are you following these steps:
In bootloader/FASTBOOT USB:
Code:
fastboot flash recovery openrecovery-twrp-2.8.3.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Have you tried other version?
I believe you must use 2.8.0.0 and above for CM11.
NotoriusBB said:
Already tried that after installing TWRP. Shall I do that before installing?
Edit: I tried fastboot erase cache now pre- and past-flashing TWRP 2.8.4.0.... nothing's changed
Click to expand...
Click to collapse
majmoz said:
Are you following these steps:
In bootloader/FASTBOOT USB:
Code:
fastboot flash recovery openrecovery-twrp-2.8.3.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Have you tried other version?
I believe you must use 2.8.0.0 and above for CM11.
Click to expand...
Click to collapse
When your recovery will not load like this the easy way to fix it is to reflash the current firmware on the phone again
this writes the stock recovery back to the phone and most times TWRP will work again after this
majmoz said:
Are you following these steps:
In bootloader/FASTBOOT USB:
Code:
fastboot flash recovery openrecovery-twrp-2.8.3.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
Have you tried other version?
I believe you must use 2.8.0.0 and above for CM11.
Click to expand...
Click to collapse
Yes
Yes
I don't think so
clsA said:
When your recovery will not load like this the easy way to fix it is to reflash the current firmware on the phone again
this writes the stock recovery back to the phone and most times TWRP will work again after this
Click to expand...
Click to collapse
Yep, I already worked it out yesterday by flashing the stock recovery first via fastboot and then TWRP again.
But thanks anyway to everyone for contributing and trying to help
NotoriusBB said:
Yes
Yes
I don't think so
Click to expand...
Click to collapse
what is your "fastboot getvar all" ?
NotoriusBB said:
Already tried that after installing TWRP. Shall I do that before installing?
Edit: I tried fastboot erase cache now pre- and past-flashing TWRP 2.8.4.0.... nothing's changed
Click to expand...
Click to collapse
Try here
http://forum.xda-developers.com/showthread.php?t=2739126
yatindroid said:
Try here
http://forum.xda-developers.com/showthread.php?t=2739126
Click to expand...
Click to collapse
Thanks, I will take a look at it since I still only can install TWRP 2.6.3.3 and enter it, other versions won't start and 2.6.3.3 gives me an error every time I want to install a custom rom -.-
Edit: Doesn't work