I recently got an HTC One M7(ul) and have been trying to install a custom recovery to install KitKat or Lollipop. So far the only recovery that has worked has been Philz recovery and even then only up to version 6.25.0(All versions after that were 'unified' but don't work). All recoveries appear to install correctly in Fastboot but when booting recovery it hangs on the 'Entering Recovery' screen, flashes a black screen once and returns to 'Entering 'Recovery'. Is this a known problem or am I doing something really weird?
robtherobot101 said:
I recently got an HTC One M7(ul) and have been trying to install a custom recovery to install KitKat or Lollipop. So far the only recovery that has worked has been Philz recovery and even then only up to version 6.25.0(All versions after that were 'unified' but don't work). All recoveries appear to install correctly in Fastboot but when booting recovery it hangs on the 'Entering Recovery' screen, flashes a black screen once and returns to 'Entering 'Recovery'. Is this a known problem or am I doing something really weird?
Click to expand...
Click to collapse
Are you flashing recovery with the correct procedure?
Code:
fastboot flash recovery name-of-recovery.img
fastboot erase cache
fastboot reboot-bootloader
Then select recovery from the bootloader menu it should load fine
Danny201281 said:
Are you flashing recovery with the correct procedure?
Code:
fastboot flash recovery name-of-recovery.img
fastboot erase cache
fastboot reboot-bootloader
Then select recovery from the bootloader menu it should load fine
Click to expand...
Click to collapse
Yeah, I've tried many different versions and methods
robtherobot101 said:
Yeah, I've tried many different versions and methods
Click to expand...
Click to collapse
mmmmm! Try this on http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img :fingers-crossed:
wtf how did you know that would work?
Can I flash KitKat/Lollipop with this recovery?
robtherobot101 said:
Can I flash KitKat/Lollipop with this recovery?
Click to expand...
Click to collapse
Its not the first time I came across this problem here on xda. 2.6.3.3 has always been the most Stable and reliable version. And for some reason works even with this problem.
2.6.3.3 should work fine with kitkat roms but I'm not sure about lollipop. Unfortunately this Is the only recovery that works in this situation and I'm not sure what causes this issue.
The weird thing is in most cases the recovery actually loads normally but the screen stays stuck on the "Entering recovery" screen. While it's stuck like that you can type "adb devices" it should give the normal output showing the device is in fact in recovery. But for now it means your kinda stuck with 2.6.3.3.
Related
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!
So I'm having a hard time here LOL.
I come from a soft brick and after some issues I got my m7_ul back to stock, which is great as it is alive again Now I want to flash a decent ROM, I have thought about ViperOne. However my TWRP 2.7.1.1 seems corrupted, I can't even enter it and I have had a couple of scary moments as the phone won't boot to system. Finally pressing the power button for like 30 seconds did the job and it booted to system. Stock ROM sucks but it is better than a brick haha.
My phone is international m7_ul, my HBOOT is 1.44 and I have Tampered and Unlocked labels, not sure what should I do exactly. Just want the basic strategy to get my custom ROM running and later on I will add a soundmod but that should be easier.
Dani84 said:
So I'm having a hard time here LOL.
I come from a soft brick and after some issues I got my m7_ul back to stock, which is great as it is alive again Now I want to flash a decent ROM, I have thought about ViperOne. However my TWRP 2.7.1.1 seems corrupted, I can't even enter it and I have had a couple of scary moments as the phone won't boot to system. Finally pressing the power button for like 30 seconds did the job and it booted to system. Stock ROM sucks but it is better than a brick haha.
My phone is international m7_ul, my HBOOT is 1.44 and I have Tampered and Unlocked labels, not sure what should I do exactly. Just want the basic strategy to get my custom ROM running and later on I will add a soundmod but that should be easier.
Click to expand...
Click to collapse
If you returned to stock you have re flash custom recovery
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7ul
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Suggest re-download, the re-flash TWRP, flash in fastboot fastboot flash recovery <name of recovery.img> and then fastboot erase cache, this should allow you to enter recovery.
wow that was fast thanks, problem solved, I'm now running TWRP 2.6.3.4
so now I just place the desired ROM flash it, wipe dalvik and cache, and voila, right? will try to find if viperone is compatible with m7ul, I had a problem with ARHD 71.1
Dani84 said:
wow that was fast thanks, problem solved, I'm now running TWRP 2.6.3.4
so now I just place the desired ROM flash it, wipe dalvik and cache, and voila, right? will try to find if viperone is compatible with m7ul, I had a problem with ARHD 71.1
Click to expand...
Click to collapse
They will both work great with your current recovery installed
clsA said:
If you returned to stock you have re flash custom recovery
Click to expand...
Click to collapse
Hello I flashed twrp recovery through twrp manager app which showed an error but after pressing reboot to twrp it did but I got a red triangle error sign his can I fix it?
CostasV23 said:
Hello I flashed twrp recovery through twrp manager app which showed an error but after pressing reboot to twrp it did but I got a red triangle error sign his can I fix it?
Click to expand...
Click to collapse
simply flash twrp using fastboot. Easy, fast and reliable.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
alray said:
simply flash twrp using fastboot. Easy, fast and reliable.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
The thing that did the trick for me was downloading the .img file from the twrp site and flashing with flashify after that it worked . thanks for your time
CostasV23 said:
The thing that did the trick for me was downloading the .img file from the twrp site and flashing with flashify after that it worked . thanks for your time
Click to expand...
Click to collapse
Yep, thats a way to do it, I prefer to use fastboot but if you don't have a computer to work with then its a good alternative. :good:
CostasV23 said:
Hello I flashed twrp recovery through twrp manager app which showed an error but after pressing reboot to twrp it did but I got a red triangle error sign his can I fix it?
Click to expand...
Click to collapse
alray said:
simply flash twrp using fastboot. Easy, fast and reliable.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
wholly smokes this thread is 2 years old how did it come back ? I feel like Ive been resurrected
clsA said:
wholly smokes this thread is 2 years old how did it come back ? I feel like Ive been resurrected
Click to expand...
Click to collapse
That's my bad actually . I was searching how to install a recovery after the red triangle for the s4 mini plus which is a completely different device and it wasn't until later I realised this thread is for the m7 and I couldn't delete it afterwards so my bad yeah
So I have the International HTC One M7, and whenever i flash any recovery except for PhilZ it says successful on fastboot but when i go into recovery from bootloader it shows entering recovery... at top then the screen goes black for 2 seconds and then gets stuck at entering recovery indefinately. I cant use PhilZ mainly due to i keep getting errors (status 0) whenever i flash a rom. Any help ?
Thanks
mrsimpson321 said:
So I have the International HTC One M7, and whenever i flash any recovery except for PhilZ it says successful on fastboot but when i go into recovery from bootloader it shows entering recovery... at top then the screen goes black for 2 seconds and then gets stuck at entering recovery indefinately. I cant use PhilZ mainly due to i keep getting errors (status 0) whenever i flash a rom. Any help ?
Thanks
Click to expand...
Click to collapse
you have to do all the commands
First get TWRP 2.6.3.3
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
If you have a Sprint or Verizon phone you need their custom recovery version
Thanks
clsA said:
you have to do all the commands
First get TWRP 2.6.3.3
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
If you have a Sprint or Verizon phone you need their custom recovery version
Click to expand...
Click to collapse
Thank you so much for your help. This is why i go to XDA first
mrsimpson321 said:
Thank you so much for your help. This is why i go to XDA first
Click to expand...
Click to collapse
What is it in TWRP 2.6.3.3 that not doing what you want?
Why are you changing recovery 3 times in the same day ?
clsA said:
What is it in TWRP 2.6.3.3 that not doing what you want?
Why are you changing recovery 3 times in the same day ?
Click to expand...
Click to collapse
I want to upgrade to InsertCoin but Aroma installer says i need to update to 2.7.1.1 I think
mrsimpson321 said:
I want to upgrade to InsertCoin but Aroma installer says i need to update to 2.7.1.1 I think
Click to expand...
Click to collapse
Pretty strange ...your the first to have a problem with 2.6.3.3 flashing any of the current roms.
Whats the error you get when flashing 2.7.1.1 recovery ?
clsA said:
Pretty strange ...your the first to have a problem with 2.6.3.3 flashing any of the current roms.
Whats the error you get when flashing 2.7.1.1 recovery ?
Click to expand...
Click to collapse
I have the same problem, I can only flash up to TWRP 2.6.3.3 older versions work, but other new versions dont work it keeps saying "entering recovery"... If try to flash Pliz some versions works other versions keep saying entering recovery, I need install multirom but cant install it or another version of TWRP up to 2.6.3.3
I try erasing cache from fastboot but it dont work, my hboot is 1.57 with s-off and unlocked
The same with me except for S-on and flashing 2.7.1.1 (or ANY other recovery) gives me the entering recovery words at the top in a bootloop until i am forced to fastboot 2.6.3.3 with the method above.
ferchorama said:
I'm stuck on the same Warning screen, it is not a bootloop since the phone just seems to freeze but after a minute I get the windows sound as if you conected something via USB, but the warning screen stays, I've let it for hours and I've flashed stock roms. Even when you flash a no warning boot logo.bin the screen shows again even when mfastboot shows as succesful flash. Out of ideas now, please help
Code:
Model XT1068
Click to expand...
Click to collapse
My Phone acts the same.
Any solution hints would be great.
Thanks in Advance
DaNeals
Can you be more specific...?
What did you flash...
Which rom are you coming from...
I dont know which exactly Rom was flashed at last (when this problem first occurs), because i have bought the phone in this condition.
I can boot into fastboot by holding Power+Vol- Button and tried to flash stock Lollipop or KitKat Rom several times. When the phone reboots in the end it still stucks at the "Warning Bootloader Unlocked" screen.
I can also boot into CWM Recovery by "fastboot boot CWM_Touch_Titan_v2.img". If i want to flash a zipped Rom from external sd the process aborts with "Cannot write to" "sdcard/clockworkmod/.last_install path".
DaNeals said:
I dont know which exactly Rom was flashed at last (when this problem first occurs), because i have bought the phone in this condition.
I can boot into fastboot by holding Power+Vol- Button and tried to flash stock Lollipop or KitKat Rom several times. When the phone reboots in the end it still stucks at the "Warning Bootloader Unlocked" screen.
I can also boot into CWM Recovery by "fastboot boot CWM_Touch_Titan_v2.img". If i want to flash a zipped Rom from external sd the process aborts with "Cannot write to" "sdcard/clockworkmod/.last_install path".
Click to expand...
Click to collapse
Have u tried installing TWRP recovery?
C-3PO said:
Have u tried installing TWRP recovery?
Click to expand...
Click to collapse
Yes, i did or better tried it at least.
-> Trying to boot Stock Recovery ends with an Android lying on his back.
-> When i tried to install TWRP OR CWM Recovery the flashing process ends with "Mismatched partition size (recovery)"
-> When i try to boot into TWRP Recovery with the fastboot command "fastboot boot TWRP.img" my phone stuck at the teamwin screen.
The only Recovery i get to run is CWM (with the command "fastboot boot CWM.img")
DaNeals said:
Yes, i did or better tried it at least.
-> Trying to boot Stock Recovery ends with an Android lying on his back.
-> When i tried to install TWRP OR CWM Recovery the flashing process ends with "Mismatched partition size (recovery)"
-> When i try to boot into TWRP Recovery with the fastboot command "fastboot boot TWRP.img" my phone stuck at the teamwin screen.
The only Recovery i get to run is CWM (with the command "fastboot boot CWM.img")
Click to expand...
Click to collapse
"mismatched partition size" is nothing wrong, it is basically just saying, that the TWRP image is smaller than the stock recovery one.
MaddyHD said:
"mismatched partition size" is nothing wrong, it is basically just saying, that the TWRP image is smaller than the stock recovery one.
Click to expand...
Click to collapse
But when the phone reboots into fastboot after this message, it still shows me the Stock Recovery, where i end at the lying Android...
When i click on "choose zip from /sdcard" (internal) in CWM Recovery i can just choose between the folders sdcard/0/ and sdcard/obb/. There is also something wrong and not how it should be, isn't it?
Hello,
I recently flashed the latest TWRP beta for the OxygenOS 4.0.1 on my phone which has an unlocked bootloader. I managed to boot into recovery immediately after flashing the .img through my PC, so that's how I was able to install my SuperSU.
However, since I booted into the OS, anytime I'm trying to enter the TRWP recovery again, I'm stuck in the stock recovery which doesn't let me install anything. So the only way for me to boot into TWRP recovery is using my PC. Can anybody help me to fix that?
Thanks!
What command are you using to install TWRP to your bootpartition?
I think the correct one is something like:
Code:
fastboot flash recovery (file name).img
kwoad said:
What command are you using to install TWRP to your bootpartition?
I think the correct one is something like:
Code:
fastboot flash recovery (file name).img
Click to expand...
Click to collapse
Thanks for your reply! Exactly. And after installing it, I used the command 'fastboot boot TWRP.img", and that brought me into TWRP recovery. But I could only get there this way and still had the stock recovery.
Yuniboy said:
Thanks for your reply! Exactly. And after installing it, I used the command 'fastboot boot TWRP.img", and that brought me into TWRP recovery. But I could only get there this way and still had the stock recovery.
Click to expand...
Click to collapse
did you unlock bootloader first
Yuniboy said:
Thanks for your reply! Exactly. And after installing it, I used the command 'fastboot boot TWRP.img", and that brought me into TWRP recovery. But I could only get there this way and still had the stock recovery.
Click to expand...
Click to collapse
From what I understand, the command 'fastboot boot twrp.img' will boot the specified recovery once, but won't flash it to the device. So it has nothing to do with the recovery that is actually on your device. Perhaps something went wrong when you actually flashed twrp and it wasn't written at all.
xabat said:
did you unlock bootloader first
Click to expand...
Click to collapse
Thanks for both your replies. Yes, I did. An indicator is also that every time I boot up my system it even warns me that the bootloader is unlocked.
freepenguin84 said:
From what I understand, the command 'fastboot boot twrp.img' will boot the specified recovery once, but won't flash it to the device. So it has nothing to do with the recovery that is actually on your device. Perhaps something went wrong when you actually flashed twrp and it wasn't written at all.
Click to expand...
Click to collapse
Well, I flashed the twrp by booting into fastboot mode and then typing 'fastboot flash recovery twrp.img'. I don't know what's wrong there, so maybe you could help me out?
Yuniboy said:
Well, I flashed the twrp by booting into fastboot mode and then typing 'fastboot flash recovery twrp.img'. I don't know what's wrong there, so maybe you could help me out?
Click to expand...
Click to collapse
Unfortunately then I don't know how to help Because that's exactly what I did and I got TWRP running without any problem. If you flash via 'fastboot flash recovery' command will it be on the device after you reboot for the first time?
i remember, once i couldn't boot into recovery either when i used fastboot command. Then I flash recovery using tool below and it worked for me.
https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
freepenguin84 said:
Unfortunately then I don't know how to help Because that's exactly what I did and I got TWRP running without any problem. If you flash via 'fastboot flash recovery' command will it be on the device after you reboot for the first time?
Click to expand...
Click to collapse
Apparently, you were right. I just wiped my device (accidentaly ) and flashed TWRP again, basically did the same steps as before, but now it works. Seems like somehow the installation of TWRP just failed on the first try. Thanks for your help!
xabat said:
i remember, once i couldn't boot into recovery either when i used fastboot command. Then I flash recovery using tool below and it worked for me.
https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
Click to expand...
Click to collapse
Fortunately, it wasn't that bad. So the installation of TWRP failed somehow and I just reinstalled it. Thanks for your help!
kwoad said:
What command are you using to install TWRP to your bootpartition?
I think the correct one is something like:
Code:
fastboot flash recovery (file name).img
Click to expand...
Click to collapse
And For Samsung devices, any method via using ODIN
(Samsung E7/E700H)
freepenguin84 said:
Unfortunately then I don't know how to help Because that's exactly what I did and I got TWRP running without any problem. If you flash via 'fastboot flash recovery' command will it be on the device after you reboot for the first time?
Click to expand...
Click to collapse
Apparently "yes". Source this xda article- https://www.xda-developers.com/how-to-install-twrp/