Develop Bugs

Can't get to Recovery mode any more.

Hello,
I've had this phone for about a week and got it configured the way I prefer: S-Off, unlocked Bootloader, SIM unlocked, rooted. I flashed the latest Beanstalk 4.4.4 ROM and life was pretty good.
The only thing was the power on screen had red writing, so I followed this thread: ★ ☆ [MOD] Remove Red Text on Splash Screen | m8 hboots | ALL Variants and it worked! It did remove the red writing, but now I can't boot into Recovery mode.
I tried getting to Recovery mode through HBOOT and also from the OS reboot menu. When the phone tries to get into recovery mode, it stalls at the HTC splash screen and states: "Entering Recovery..." at the top of the screen, but never gets there. I then have to wait for the phone to run out of power, before I can put it on the charger and then be able to boot into the Bootloader or the OS.
So then I found a thread to erase the cache using Minimal ADB and Fastboot: fastboot erase cache
which it did successfully. I then booted to the OS, and now I've lost my cell signal,
I booted back to fastboot and from my computer ran Minimal ADB and Fastboot: fastboot flash recovery twrp.img
which it did successfully. I then tried booting to the Recovery and again I get the HTC start up screen with: "Entering Recovery..." at the top of the screen.
So now I'm waiting for the phone battery to die off a fully charge. Before I do anything else, I would like some of your help with what my next step should be.
Please help!
Thank you.

dubsteps said:
Hello,
I've had this phone for about a week and got it configured the way I prefer: S-Off, unlocked Bootloader, SIM unlocked, rooted. I flashed the latest Beanstalk 4.4.4 ROM and life was pretty good.
The only thing was the power on screen had red writing, so I followed this thread: ★ ☆ [MOD] Remove Red Text on Splash Screen | m8 hboots | ALL Variants and it worked! It did remove the red writing, but now I can't boot into Recovery mode.
I tried getting to Recovery mode through HBOOT and also from the OS reboot menu. When the phone tries to get into recovery mode, it stalls at the HTC splash screen and states: "Entering Recovery..." at the top of the screen, but never gets there. I then have to wait for the phone to run out of power, before I can put it on the charger and then be able to boot into the Bootloader or the OS.
So then I found a thread to erase the cache using Minimal ADB and Fastboot: fastboot erase cache
which it did successfully. I then booted to the OS, and now I've lost my cell signal,
I booted back to fastboot and from my computer ran Minimal ADB and Fastboot: fastboot flash recovery twrp.img
which it did successfully. I then tried booting to the Recovery and again I get the HTC start up screen with: "Entering Recovery..." at the top of the screen.
So now I'm waiting for the phone battery to die off a fully charge. Before I do anything else, I would like some of your help with what my next step should be.
Please help!
Thank you.
Click to expand...
Click to collapse
the "fastboot erase cache" should be done after flashing recovery:
Code:
fastboot flash recovery <name of correct twrp version>.img
fastboot erase cache
no need to wait for it to die out, POWER + VOLUP (possibly under a bright light) should do a forced reboot

nkk71 said:
the "fastboot erase cache" should be done after flashing recovery:
Code:
fastboot flash recovery <name of correct twrp version>.img
fastboot erase cache
no need to wait for it to die out, POWER + VOLUP (possibly under a bright light) should do a forced reboot
Click to expand...
Click to collapse
Thanks so much for the tip on POWER + VOLUP to reboot the phone!
I then booted the OS ok (no cell signal though), rebooted to Fastmode, ran Minimal ADB and Fastboot: flashed the recovery file successfully, and then formatted the cache with the command line text stated.
When booting to Recovery, it's still not going into Recovery mode. Just sitting at the HTC screen with the writing at the top: Entering Recovery...
The phone also seems to be a bit sluggish now - just seems to be taking longer than normal for the parts that still work ok (loading the OS).

dubsteps said:
Thanks so much for the tip on POWER + VOLUP to reboot the phone!
I then booted the OS ok (no cell signal though), rebooted to Fastmode, ran Minimal ADB and Fastboot: flashed the recovery file successfully, and then formatted the cache with the command line text stated.
When booting to Recovery, it's still not going into Recovery mode. Just sitting at the HTC screen with the writing at the top: Entering Recovery...
The phone also seems to be a bit sluggish now - just seems to be taking longer than normal for the parts that still work ok (loading the OS).
Click to expand...
Click to collapse
Not sure which recovery you're trying to flash but you might try a different version.

Magnum_Enforcer said:
Not sure which recovery you're trying to flash but you might try a different version.
Click to expand...
Click to collapse
I flashed TWRP 2.8.0.1 and it worked fine until I decided to try to get rid of the red text on the HTC bootloading screen.

dubsteps said:
Thanks so much for the tip on POWER + VOLUP to reboot the phone!
I then booted the OS ok (no cell signal though), rebooted to Fastmode, ran Minimal ADB and Fastboot: flashed the recovery file successfully, and then formatted the cache with the command line text stated.
When booting to Recovery, it's still not going into Recovery mode. Just sitting at the HTC screen with the writing at the top: Entering Recovery...
The phone also seems to be a bit sluggish now - just seems to be taking longer than normal for the parts that still work ok (loading the OS).
Click to expand...
Click to collapse
have you made sure
1- the recovery is the correct one for your phone
2- the file isnt corrupt (check MD5)
i don't know if this is related to the modded hboot (it shouldnt be) but who knows, i dont like messing with hboot

If all else fails, RUU and start over.

Magnum_Enforcer said:
If all else fails, RUU and start over.
Click to expand...
Click to collapse
Ok, I redownloaded the latest TWRP: 2.8.3.0 for the M8, checked it via MD5. I tried flashing the recovery file and nothing has changed... ( I now notice my phone won't connect to Bluetooth or wifi now)
Seems like all else is failing. I'll have to try RUU now. I'm starting to look around the M8 forum for info on RUU. Got anything threads handy to help me?

dubsteps said:
Ok, I redownloaded the latest TWRP: 2.8.3.0 for the M8, checked it via MD5. I tried flashing the recovery file and nothing has changed... ( I now notice my phone won't connect to Bluetooth or wifi now)
Seems like all else is failing. I'll have to try RUU now. I'm starting to look around the M8 forum for info on RUU. Got anything threads handy to help me?
Click to expand...
Click to collapse
Which carrier are you on?

Magnum_Enforcer said:
Which carrier are you on?
Click to expand...
Click to collapse
Originally the phone was with Rogers Wireless. I had to SIM unlock the phone so I could use it on Bell Mobility.

dubsteps said:
Originally the phone was with Rogers Wireless. I had to SIM unlock the phone so I could use it on Bell Mobility.
Click to expand...
Click to collapse
imho, try reflashing your firmware again (that would include stock hboot)

by removing the red writing you actually installed a custom hboot i think ...revert to your original hboot should fix things for you

nkk71 said:
imho, try reflashing your firmware again (that would include stock hboot)
Click to expand...
Click to collapse
Ok, so I flashed stock recovery and went to HBOOT>RECOVERY -> pressed VOLUP and POWER at red triangle w exclamation point screen.
- Wiped Cache, Factory Reset data (not sure if that is needed, but did it in case)
rebooted and the phone is working again (AND the red text is gone at startup)

dubsteps said:
Ok, so I flashed stock recovery and went to HBOOT>RECOVERY -> pressed VOLUP and POWER at red triangle w exclamation point screen.
- Wiped Cache, Factory Reset data (not sure if that is needed, but did it in case)
rebooted and the phone is working again (AND the red text is gone at startup)
Click to expand...
Click to collapse
nice :good::good:
no reason for custom recovery not to work since you were able to get to stock recovery, i've seen a few rare cases on the m7 where you had to delete the twrp settings file on the sdcard for it to work when going from one version to another (though really a very rarely)

nkk71 said:
nice :good::good:
no reason for custom recovery not to work since you were able to get to stock recovery, i've seen a few rare cases on the m7 where you had to delete the twrp settings file on the sdcard for it to work when going from one version to another (though really a very rarely)
Click to expand...
Click to collapse
Ok, it's definitely the download for the TWRP recovery I had. I'm able to reflash stock recovery and reflash other TWRP downloads (another download of the newest, then maybe 2.7.x.x)
-
OK, I flashed with TWRP 2.8.1.0 and that worked ok. I did MD5 the 2.8.3.0 TWRP, but it just won't work.
Thank you so much nkk71 and everyone who replied to my thread!

dubsteps said:
Hello,
I've had this phone for about a week and got it configured the way I prefer: S-Off, unlocked Bootloader, SIM unlocked, rooted. I flashed the latest Beanstalk 4.4.4 ROM and life was pretty good.
The only thing was the power on screen had red writing, so I followed this thread: ★ ☆ [MOD] Remove Red Text on Splash Screen | m8 hboots | ALL Variants and it worked! It did remove the red writing, but now I can't boot into Recovery mode.
I tried getting to Recovery mode through HBOOT and also from the OS reboot menu. When the phone tries to get into recovery mode, it stalls at the HTC splash screen and states: "Entering Recovery..." at the top of the screen, but never gets there. I then have to wait for the phone to run out of power, before I can put it on the charger and then be able to boot into the Bootloader or the OS.
So then I found a thread to erase the cache using Minimal ADB and Fastboot: fastboot erase cache
which it did successfully. I then booted to the OS, and now I've lost my cell signal,
I booted back to fastboot and from my computer ran Minimal ADB and Fastboot: fastboot flash recovery twrp.img
which it did successfully. I then tried booting to the Recovery and again I get the HTC start up screen with: "Entering Recovery..." at the top of the screen.
So now I'm waiting for the phone battery to die off a fully charge. Before I do anything else, I would like some of your help with what my next step should be.
Please help!
Thank you.
Click to expand...
Click to collapse
Got a similar problem like this one
unlocked bootloader
flashed twrp using the fastboot process of cmd
but i CANT get into RECOVERY MODE
when i click Recovery only a screen flashes saying "Entering recovery" and comes back to the bootloader screen showing HBOOT
PLEASE HELP
A TOTAL NOOB

[Q] Huawei Ascend P6 vibrates on recovery mode

I entered in the world of Android modding just some days ago and I installed B513 for my Ascend P6. Then I tried to install Twrp recovery following this guide (http://forum.xda-developers.com/showthread.php?t=2534420). In a first moment I installed the image on TWRP_R03.1.zip file, but the recovery didn't work (the huawei's logo appeared and nothing happened). Then i tried to install twrp_2_6_3_3_recovery.img. Now i can enter on recovery mode but the phone starts to vibrate when the huawei's logo appear and it won't stop until I restart the phone holding for 10 second on the power button. When i enter in the recovery it appear on the screen but i can't do anything beacause the touch don't work. The same thing happens also for others recovery like the stock one.
What can I do? Do i have to change rom? I'd like to format the phone to factory data but how can i do it if recovery doesn't work?

X38x said:
I entered in the world of Android modding just some days ago and I installed B513 for my Ascend P6. Then I tried to install Twrp recovery following this guide (http://forum.xda-developers.com/showthread.php?t=2534420). In a first moment I installed the image on TWRP_R03.1.zip file, but the recovery didn't work (the huawei's logo appeared and nothing happened). Then i tried to install twrp_2_6_3_3_recovery.img. Now i can enter on recovery mode but the phone starts to vibrate when the huawei's logo appear and it won't stop until I restart the phone holding for 10 second on the power button. When i enter in the recovery it appear on the screen but i can't do anything beacause the touch don't work. The same thing happens also for others recovery like the stock one.
What can I do? Do i have to change rom? I'd like to format the phone to factory data but how can i do it if recovery doesn't work?
Click to expand...
Click to collapse
Since you have B513 on your phone it means that it runs on kitkat, and the recovery version of twrp that you flashed (2.6.3.3) is for jellybean. So i suggest that you flash this version and see if it works.
http://forum.xda-developers.com/showthread.php?t=2709353
Sent from my SM-G850F using xda app-developers app

Thank you very much! It worked

Is my M8 bricked?

Hi XDA-Fellows
1) thanks for all the help of this community so far
2) my problem: I had my HTC One M8 rooted, installed TWRP (I think in the end I had 2.7.8.0 as last version) and Cyanogenmod with a nightly build of around 18. March 2016 installed! THEN the big mistake happened. In advanced developers menu of cyanogenmod I activated the option that was called something like "on update of system also replace recovery software". That obviously was stupid.
Upon rebooting normally TWRP launched and installed the latest nightly. This time I see the white screen with HTC logo on it, red text in bottom, top part of the screen shows "ENTERING RECOVERY", 3 seconds later I see a black screen and every like 2 or 3 seconds it looks like the screen gets powered, it flashes darkgrey shortly (again, looks like it gets powered but instantly shuts off immediately).
This just can be stopped by pressing either P+U or P+D for like 10 seconds. Then again, white screen with HTC logo and ENTERING RECOVERY and the screen switch on/off-loop.
Is my device bricked? What can I do now?
Any help is appreciated.

Hi,
Can you enter to your bootloader ? So maybe you can just reflash it to see if it's going to work..

BelDev said:
Hi,
Can you enter to your bootloader ? So maybe you can just reflash it to see if it's going to work..
Click to expand...
Click to collapse
Yes I can enter bootloader. How should I go on from here on?

Well you just need to download the new TWRP from their web site https://dl.twrp.me/m8/ after that you put your device into bootloader and you plug your phone into your computer and download a toolkit from xda like htc one m8 toolkit and you follow the instructions..

BelDev said:
Well you just need to download the new TWRP from their web site https://dl.twrp.me/m8/ after that you put your device into bootloader and you plug your phone into your computer and download a toolkit from xda like htc one m8 toolkit and you follow the instructions..
Click to expand...
Click to collapse
Thanks. I will give it a try and give feedback.

It worked. I could enter bootloader, switched to FASTBOOT mode, installed ADB Drivers for windows and replaced recovery with latest TWRP! THanks a lot for your help! I thought I could throw away my M8

Well. It worked not completely. I was able to reboot my phone into the Cyanogenmod. But upon entering recovery mode (which I expected now to be TWRP) I get the same result again ... Screen off/on within seconds, repeating endlessly

I think you need to reflash the boot.img and the ROM completely. Because i don't know why do you have a black screen.

I activated root access for apps and tried ROM Manager first! It failed, then I used flashify which worked. Automatically downloaded latest TWRP (3.0.0.1) and flashed it, reboot into recovery. Everything works like a charm again! Thanks again for your help!

Missing Recovery on Android 10

I just noticed after doing a clean install of the C3 factory image using -w that I am unable to boot to the stock recovery. It seems to be missing from my installation. Any ideas why I may be unable to boot to recovery? All I get is a dead Android logo with "No command" or it boots up my system after restarting. I've tried booting from the bootloader numerous times and never seems to work. Is it possible that the stock recovery was never installed? I did no perform a --slot all when installing Android 10 so maybe that's the issue? Any suggestions would be great as I can't seem to find a solution to this in the forums or Google searching. Thanks.

You have to go one step beyond the no recovery screen to see the recovery commands. If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.

Seems I can't even get to the broken Android screen now. In the bootloader if I select boot recovery it just boots my system and never shows the broken Android anymore. Very odd. I'm stumped.

rspkt said:
Seems I can't even get to the broken Android screen now. In the bootloader if I select boot recovery it just boots my system and never shows the broken Android anymore. Very odd. I'm stumped.
Click to expand...
Click to collapse
I am not sure what you are referring to "boot recovery." Are you entering the bootloader in some way other than volume down +power? The option when using the up/down in bootloader is Recovery mode. That will get you to the broken android and no command. At worst though, you can flash boot.img and get your stock recovery/kernel back/unroot.

sliding_billy said:
I am not sure what you are referring to "boot recovery." Are you entering the bootloader in some way other than volume down +power? The option when using the up/down in bootloader is Recovery mode. That will get you to the broken android and no command. At worst though, you can flash boot.img and get your stock recovery/kernel back/unroot.
Click to expand...
Click to collapse
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.

rspkt said:
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
Click to expand...
Click to collapse
I get the same thing where it won't boot to recovery from the bootloader, but goes back to booting to system. It's because I'm rooted. Flash the stock boot image and you'll be fine.

rspkt said:
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
Click to expand...
Click to collapse
OK, that makes better sense. You are pretty clearly in a bootloop. Just confirming the terminology. Flashing stock boot might get you out of the loop, but after rereading your initial message it sounds as if some info is missing. After the flash-all, did it ever get to the setup screen where you enter your gmail account name, etc. Did it get through that to the actual OS, and if so what else did you do that got you into the bootloop? Root attempt?

sliding_billy said:
OK, that makes better sense. You are pretty clearly in a bootloop. Just confirming the terminology. Flashing stock boot might get you out of the loop, but after rereading your initial message it sounds as if some info is missing. After the flash-all, did it ever get to the setup screen where you enter your gmail account name, etc. Did it get through that to the actual OS, and if so what else did you do that got you into the bootloop? Root attempt?
Click to expand...
Click to collapse
Ya my phone setup fine through all the initial setup steps as if it was a new device and the system works perfectly. I did root and install Kirisakura kernel but only after few days of using stock. Just noticed after setting everything up the recovery seems to be missing when I tried to boot into it. I may try and start from scratch again cuz obviously something got broken during the factory image installation using -w.

rspkt said:
Ya my phone setup fine through all the initial setup steps as if it was a new device and the system works perfectly. I did root and install Kirisakura kernel but only after few days of using stock. Just noticed after setting everything up the recovery seems to be missing when I tried to boot into it. I may try and start from scratch again cuz obviously something got broken during the factory image installation using -w.
Click to expand...
Click to collapse
I missed the post by @jd1639 while I was replying. It doesn't sound like anything got messed up as a result of the -w. Because stock recovery is part of boot now, you just need to stay out of there unless you flash boot.img first. Not doing the --slot all wouldn't have any impact unless you install a custom ROM, an OTA or do a manual slot change. Since it was the first time I had done a completely clean wipe in a while when I flashed 10 (after custom ROMs, OTAs, etc), I actually did flash-all (with -w) to both slots. I did a flash-all on B and finished setup, and then booted back to BL, changed slots manually to A and did a second flash-all. Only after that did I start gettin gthe phone ready for daily function. Not sure it helped anything but my OCD, but it was fun to watch the fastbootd thing run a few times. :silly:

jd1639 said:
I get the same thing where it won't boot to recovery from the bootloader, but goes back to booting to system. It's because I'm rooted. Flash the stock boot image and you'll be fine.
Click to expand...
Click to collapse
I never would have assumed having root could cause this issue.

Unlocked bootloader - boot loop after trying to put stock firmware back on

My telephone keeps booting to fastboot after trying to update TWRP.
I am trying to restore the original ROM (apollo_eea_global_images_V12.5.12.0.RJDEUXM_20220208.0000.00_11.0_eea) and I can get the rom installed through fastboot but the phone enters a boot loop cycle. It starts up, vibrates shortly then reboots.
If i press volume up it goes into the original recovery menu. I have tried clearing everything and even entering safe mode but the phone will not boot.
Am i screwed?
Thanks in advance.

I installed the Pixel Experience recovery and side-loaded the zip and at least have a working OS.
I must be doing something wrong with the stock mi10t

Now i sided the miui zip and its working agian. I think i have misunderstood the procedure. I thought you only need to install the rom with flashboot and that was it.