Database Info

[Q] Transformer TF101G unable to boot to recovery.

Hi all,
This may sound like an old problem but believe me, it's not. Let me explain.
I've rooted my Transformer TF101G (B90) last year sometime on 3.2.1. This works fine with no issues. I've flashed ClockworkMod after installing ROM Manager. This worked fine, I can boot normally, I can boot to recovery, no problem.
With the latest update available from ASUS via the web, I decided to to allow the annoying icon complaining about upgrading to download and run the upgrade. After downloading the update the Pad rebooted so if to install the new update. This landed me on the CWM with an error message that stated the verification (or something failed). After this, the Transformer wouldn't boot directly to Android, but ended up booting to the recovery partition every time. I had to use the fastboot option to "cold boot" into Android.
This was annoying, so I googled and found the solution on this forum to fix the issue with 5.5.0.4 that kept rebooting to recovery. This solved that problem and I was still able to boot to recovery whenever required.
I decided to update CWM to version 5.8.2.1 via ROM Manager. This seemed to work via ROM Manager, but restarting the transformer and going to recovery showed version 5.5.0.4 still. So I went back to ROM Manager and it showed that it was upgraded to 5.8.2.1. I decided to update this to ClockworkMod Touch by purchasing it via Google market to support the guys that do development on it. This claimed to install also. "Reboot into Recovery" from ROM Manager still showed version 5.5.0.4.
I was now very confused.
So I decided to downgrade CWM from the 5.8.2.1 version it stated was installed to version 5.8.1.9. This worked according to ROM Manager, but rebooting into recovery still showed 5.5.0.4. I mean, WTF!
In the meanwhile the freeken update icon on the task tray still complained about updating Android. I allowed it again to try and update. At the point it rebooted it left me stuck on the "EEE Pad" screen.
Booting up with Vol - and Power takes me to the screen that gives you an option to press Vol + to boot to RCK. Doing so the Pad freezes at "Booting Recovery Kernel Image". My PC then detects USB ADB interface but any adb commands respond with "error: device offline" or "error: device not found".
Booting up with Vol + and Power leaves the screen blank. My PC then detects an USB APX interface. Using "fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img" only responds with "waiting for device".
The only way to boot my tablet at the moment is to use the "cold boot" option.
I would like to think I've tried everything out there and would appreciated anybody that could point me to maybe something else I could try.
PS: In ROM Manager I get "An error occurred while attempting to run privileged commands" when I use the "Fix Permissions" option.

PeekNPoke said:
PS: In ROM Manager I get "An error occurred while attempting to run privileged commands" when I use the "Fix Permissions" option.
Click to expand...
Click to collapse
Fixed the privileged error by installing Busybox, but still unable to boot to recovery even when reinstalling CWM with the "Erase Recovery" option ticked.

PeekNPoke said:
Fixed the privileged error by installing Busybox, but still unable to boot to recovery even when reinstalling CWM with the "Erase Recovery" option ticked.
Click to expand...
Click to collapse
I had the same problem. It seems the 5.5.0.4 or whatever recovery has borked the transformer. First, I was just in a recovery loop and when I followed how to get out of it, I have no recovery at all now it seems. I need to find a recovery.img and fastboot to manually install it but I can't find a recovery.img that is current.

dragon_76 said:
I had the same problem. It seems the 5.5.0.4 or whatever recovery has borked the transformer. First, I was just in a recovery loop and when I followed how to get out of it, I have no recovery at all now it seems. I need to find a recovery.img and fastboot to manually install it but I can't find a recovery.img that is current.
Click to expand...
Click to collapse
I can't get fastboot to work either. I though I might reinstall ClockworkMod via
fastboot.exe -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img
but it never connects.
Is there no tool that could be used from the adb shell that could re-flash ClockworkMod or even the original recovery (if that is available somewhere)?

PeekNPoke said:
I can't get fastboot to work either. I though I might reinstall ClockworkMod via
fastboot.exe -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img
but it never connects.
Is there no tool that could be used from the adb shell that could re-flash ClockworkMod or even the original recovery (if that is available somewhere)?
Click to expand...
Click to collapse
Same problem here(tf101g): tried to update to ics.... stuck on cwm 5.5.0.4
Resolved problem using: echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Now i can't access to cwm, even if i update to the last cwm touch....paying...any idea?

recovery
Sorry for my bad english,
I think I have the solution
First invites you down the driver and the nvflsh see appendix are the drivers are too large as a single file
2 go into the apx and the modern transformer connected to the PC
Third drivers instalation
4 instalation nvflasch
then you have a new recovery
This worked for me
ps I have a B60

mmarco80 said:
Same problem here(tf101g): tried to update to ics.... stuck on cwm 5.5.0.4
Resolved problem using: echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Now i can't access to cwm, even if i update to the last cwm touch....paying...any idea?
Click to expand...
Click to collapse
I've solved The problem whit the gnufabio toolsto install recovery. Then Used "reboot to recovery"
Now i've manually installed official ics ....work fine!

Thomas Cardif said:
Sorry for my bad english,
I think I have the solution
First invites you down the driver and the nvflsh see appendix are the drivers are too large as a single file
2 go into the apx and the modern transformer connected to the PC
Third drivers instalation
4 instalation nvflasch
then you have a new recovery
This worked for me
ps I have a B60
Click to expand...
Click to collapse
I tried this combined with the instructions on android.modaco.com/topic/335416-nvflash-setup-instructions-drivers-links-active because I'd never used nvflash before.
I managed to boot my TF101 in APX-mode, but as soon as I do any nvflash-command (e.g. nvflash --sync) the connection to the TF is lost:
C:\Program Files (x86)\nvflash>nvflash --sync
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Click to expand...
Click to collapse
After that I have to reboot the TF and shut it down again to be able to go into APX-mode again.
What do I miss? Mine is a B80.

hans_zelf said:
What do I miss? Mine is a B80.
Click to expand...
Click to collapse
You can't use nvflash with a B80

baseballfanz said:
You can't use nvflash with a B80
Click to expand...
Click to collapse
Oops. Fastbook doesn't seem to work either. Any ideas?

Yeah, I can't get fastboot to work either. I still have root access on the device. Is it not possible to flash the recovery from to root prompt on the device?

I tried using ADB. That way I actually can access the device and copy the recovery.img to the device using:
adb push recovery.img /data/local/recovery.img
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock2 /system
# cd /system
# cat /data/local/recovery.img > recovery.img
# flash_image recovery recovery.img
Click to expand...
Click to collapse
Works out until the last step. Then I get a message sh: flash_image: not found. Am I missing some files I have to flash first or have I forgotten something else?

Success!
Finally I succeeded!
Flashed recovery using Gnufabio's RecoveryInstaller. (After that the TF101 rebooted itself but still got stuck at the splashscreen. Did a cold Linux-boot).
Opened an ADB-session:
C:\Program Files\...\platform-tools>adb shell
/ # su
/ # echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes transferred in 0.039 secs (128 bytes/sec)​/ # exit
Click to expand...
Click to collapse
Finally, using ROM-manager I downgraded to CWM 5.5.0.4.
After that I was able to boot into recovery, but not from ROM-manager. I had to hold Vol- but at least I have a working recovery and was able to upgrade to ICS.
I'm not sure if the first step was really necessary but this is how I did it.

Hey hans_zelf,
Wow, I'm glad you got it going. I'll give it a go aswell and give feedback here. By the way, where did you get the recovery.img file you originally tried to flash?

Not really sure. I did a search within the forum and found several img's and zips.
But in the end I didn't need it because both RecoveryInstaller and ROM-manager download their own.

Ok,
I did the following:
adb shell
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
exit
Used ROM Manager v5.0.0.6, selected "Erase Recovery" in the settings menu, then flashed ClockworkMod 5.5.0.4, and powered down.
I then tried to start with Vol + and Power, just a blank screen but the 0955:7820 usb driver loaded. Then I used Vol - and Power, it booted to the Eee screen with the blue progress bar, after this is booted normally to the OS.
I powered it down again, and this time booted with Vol - and Power. Got to the screen that says use Vol + to load Recovery. I did that, and Bobs-Your-Uncle !!!!! IT WORKS !!!
Thanks hans_zelf, I'd still be stuck if it wasn't for you !
PS: I think the trick might have been to flash the 5.5.0.4 back, I'm not sure, and I'm not trying this again

You're welcome, but all I really did was combine some very helpfull tips from this forum
In the meantime I flashed my recovery to repacked Touch CWM v5.8.1.8 by Roach2010. Works like a charm. Not only touch support but also keyboard!

Thanks hans_zelf & PeekNPoke. Got my tf101 back into recovery mode from following what you guys said. I had this problem because I upgraded CWM in Rom Manager. Is that what happened to you guys? If so I think this should be stickied because if was a easy mistake and this is the only thread I could find that helped get my recovery back. Thanks again

Yep. Mine was also barked after I upgraded CWM from ROM-Manager.

mike0122 said:
Thanks hans_zelf & PeekNPoke. Got my tf101 back into recovery mode from following what you guys said. I had this problem because I upgraded CWM in Rom Manager. Is that what happened to you guys? If so I think this should be stickied because if was a easy mistake and this is the only thread I could find that helped get my recovery back. Thanks again
Click to expand...
Click to collapse
me too, i've solved whit gnufabio recovery

Asus TF 201 - Does not want to enter recovery mode

Hi,
I have a problem with my Asus TF 201.
I was trying to flash the Jelly Bean 4.1.1 CM 10 on my Asus TF210.
I have the device rooted and i used the goomanager to flash the rom...
Install OpenRecoveryScript. It downloads TWRP-2.2.0-tf201.blob and I get "Recovery has been installed!" Trying to boot into recovery (manually - Goo Manager -> Reboot Recovery does nothing) I get the Android belly up with the red triangle with exclamation point in the middle. Also, when I tried to install CM10 from Goo Manager, I got a similar message, but then it just sat there.
i'm not sure where i'm doing wrong that it's not entering recovery mode.
i used the rom manager to flash the CWM 5.8.3.4....
appreciate someone can help me..
TQ

Reflash the recovery and boot into recovery mode manually.

TWRP v2.2.2.0 Problem using internal storage (sdcard0)
Theonew said:
Reflash the recovery and boot into recovery mode manually.
Click to expand...
Click to collapse
I seem to experience the following problem. After succesfully downoading a cm10 nightly using the latest goo manager, I reboot into recovery. But instead of automatically updating, I get stuck in "Please type your password". After clicking the Cancel button I can not see the downloaded cm10 zip file anywere. However I am able to flash successfully from my external sdcard, which is great by the way!... What should I do to correct my obviously internal sdcard problem?

Dear All,
I have 2 big problems with my TF201.
First - It cannot enter the recovery mode neither from ADB via the command:
adb reboot recovery
nor via the "hold volume down and power for 3 seconds, let go of power only, then press volume up when prompted on screen"
The result that I get every time is Android lying down with a red asterisk.
Second – ADB recognizes the TF201 correctly but I cannot say the same for FASTBOOT.
When I execute the command:
adb devices
I get the following result:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C2OKAS026360 device
But when I try FASTBOOT as follows:
fastboot devices
or
fastboot -i 0x0b05 erase cache
for example, I get:
< waiting for device >
And that is forever.
Please, help me figure out what is wrong with my TF201.
Thank you in advance.

Same problem
Hi Dear All
I also have the same problem please help me.

Exactly the same issue
..... did anyone every get around to fixing this? Its' driving me crackers!

Bricked :(

All im getting is the TWRP menu, even after holding the vol down & power. Wont get to the rck screen. Any ideas?

spooky71 said:
All im getting is the TWRP menu, even after holding the vol down & power. Wont get to the rck screen. Any ideas?
Click to expand...
Click to collapse
What happened?
This is a common result if you flash a non-4.2 twrp on a 4.2 bootloader, which will cause a fastboot flash brick.
You will need adb drivers installed on pc, then while in recovery connect your tab to pc, open a command prompt and cd to you android-sdk/platform-tools folder and type
Code:
adb devices
if adb is setup correctly you will get a response with your devices s/n. If this is ok then type
Code:
adb reboot-bootloader
which will reboot your tab to the bootloader screen.

The problem is that whenever I boot up, all i get is the TWRP menu, not letting the pc see the pad. On device manager I get Transformer under other devices. Ive downloaded the drivers, but its not installing them. When I run adb reboot-bootloader, I get device not found.

Have a look here, scroll down and follow on from the where you see the device manager image - this worked for me to get adb working from recovery.
So did this happen after you flashed twrp 2.4.4.0-4.2? or did you flash another twrp or cwm?
Heading out now for a few hours but will be back later

pjc21 said:
Have a look here, scroll down and follow on from the where you see the device manager image - this worked for me to get adb working from recovery.
So did this happen after you flashed twrp 2.4.4.0-4.2? or did you flash another twrp or cwm?
Heading out now for a few hours but will be back later
Click to expand...
Click to collapse
Still nothing. Whats killing me is that it cant detect different sd cards.

Have NO Recovery

Hi all !
Two weeks ago I somehow lost my recovery...
I had CWM 6.0.2.1 and decided to flash compatible TWRP zip 2.6.3.0 and switch recovery. I think i forgot to wipe something. It did flash it, but not successfully. When I tried to enter the recovery it stucked in "searching RCK" and didn't enter the costume recovery. I rebooted it and it get stucked on the ASUS screen. So now I have 2 options:
(The tablet is off)
1. Turning on- holding POWER- stucked on ASUS boot screen.
2. Holding POWER+VOL DOWN- enters RCK. from here I have two options, again:
2a. Enter recovey- press VOL UP - doesn't eter recovery; stucked at "searching RCK".
2b. press nothing- I have two options:
2b.a. cold boot - boots normally to the ROM (CM10)
2b.a. wipe data - haven't tried it, but i belive it will wipe my data XD
I've tried PERI and 1ClickTransformerRoot - no results...
In my opinion, the main problem is that the tablet can't reboot normally...
I need your help, I'll apritiate it a lot !
Sent from my SL101 using xda app-developers app

Wipe data won't wipe data as it relies on stock recovery.
Here is what I would do:
Download the TWRP you want to use.
Unzip so you have the TWRP.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ [b]su[/b]
# [b]dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4[/b]
# [b]reboot[/b]
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery.

frederuco said:
Wipe data won't wipe data as it relies on stock recovery.
Here is what I would do:
Download the TWRP you want to use.
Unzip so you have the TWRP.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ [B]su[/B]
# [B]dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4[/B]
# [B]reboot[/B]
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery.
Click to expand...
Click to collapse
I would add to first do this when booted to the ROM from either terminal or through adb shell:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3
And reboot normally. This will clear a flag or something that's causing the boot loop and allow normal reboots. Then do as Frederuco says above.

sidneyk said:
I would add to first do this when booted to the ROM from either terminal or through adb shell:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3
And reboot normally. This will clear a flag or something that's causing the boot loop and allow normal reboots. Then do as Frederuco says above.
Click to expand...
Click to collapse
Thanks a lot ! It now boots normally !
frederuco said:
Download the TWRP you want to use.
Unzip so you have the TWRP.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ [b]su[/b]
# [b]dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4[/b]
# [b]reboot[/b]
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery.
Click to expand...
Click to collapse
I've tried it before and now - didn't worked for me...
Can I try a similar method with CWM ? :fingers-crossed:
Btw. you two are great !

You can do the same with a CWM blob file.
Also, if you have a TF101 (non 3G) you can boot to APX and install using NVFlash (EasyFlasher).
See here for details on how to use EasyFlasher: http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
DK5 said:
Btw. you two are great !
Click to expand...
Click to collapse
Yeah, we know!

DK5 said:
Btw. you two are great !
Click to expand...
Click to collapse
Should understatements really be allowed? :laugh:

@DK5: I had the same problem. Thanks @ the two specialists for helping!
Slider boots up normally now, but sadly I can't enter recovery.
Have you get recovery back?

FIXED
Goggle81 said:
@DK5: I had the same problem. Thanks @ the two specialists for helping!
Slider boots up normally now, but sadly I can't enter recovery.
Have you get recovery back?
Click to expand...
Click to collapse
I did what frederuco suggested, just with CWM:
http://forum.xda-developers.com/showthread.php?t=1855686&highlight=cwm
frederuco said:
Download the CWM you want to use.
Unzip so you have the CWM.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ [b]su[/b]
# [b]dd if=/sdcard/CWM.blob of=/dev/block/mmcblk0p4[/b]
# [b]reboot[/b]
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery.
Click to expand...
Click to collapse
And my slider booted normally :victory:
Good luck mate ! I hope it will work for you :fingers-crossed:

Didn't work for me. Will check it again.
Thanks mate!
Edit: sadly I didn't find the time to do it until know.
Thanks at all! Got recovery back. Now I will flash 4.4.2

I was trying to root and install KatKiss on my Asus SL101.
Somehow i messed it up.
I managed to root it, installed twrp but couldnt get into recovery.
Somehow i installed CWM too and when i hit format it stucked.
Now i can enter recovery CWM but it says it cant mount the sd card where i put the Katkiss, the apps and the SL101 compatibility pack.
I cant go back into the original rom cause it just says asus and the cyrcle goes on and on.
I could use some advice on how and where to enter those lines as i am not very familiar with android
ty

Mirabeau78 said:
I was trying to root and install KatKiss on my Asus SL101.
Somehow i messed it up.
I managed to root it, installed twrp but couldnt get into recovery.
Somehow i installed CWM too and when i hit format it stucked.
Now i can enter recovery CWM but it says it cant mount the sd card where i put the Katkiss, the apps and the SL101 compatibility pack.
I cant go back into the original rom cause it just says asus and the cyrcle goes on and on.
I could use some advice on how and where to enter those lines as i am not very familiar with android
ty
Click to expand...
Click to collapse
Have you tried cold boot?
Read through the OP in order to cold boot into ROM:
2. Holding POWER+VOL DOWN- enters RCK. from here I have two options, again:
2a. Enter recovey- press VOL UP - doesn't eter recovery; stucked at "searching RCK".
2b. press nothing
2b.a. cold boot - boots normally to the ROM
Click to expand...
Click to collapse
If it worked, download Android Terminal Emulator and type in:
Code:
su
dd if=/dev/zero of=/dev/block/mmcblk0p3
And reboot normally. This will clear a flag or something that's causing the boot loop and allow normal reboots.
Download the TWRP you want to use.
Unzip so you have the TWRP.blob and put it in the /sdcard/ directory.
Then run the following in a terminal:
Code:
$ su
# dd if=/sdcard/TWRP.blob of=/dev/block/mmcblk0p4
# reboot
Wait for it to fully reboot (should see an Eee Pad with progress indicator on boot)
Once it is booted, reboot to recovery and install KatKiss :highfive:
Big TNX to @frederuco and @sidneyk , if it woks thank them before you thank me, it is their instructions above

2. Holding POWER+VOL DOWN- enters RCK. from here I have two options, again:
2a. Enter recovey- press VOL UP - doesn't eter recovery; stucked at "searching RCK".
2b. press nothing
2b.a. cold boot - boots normally to the ROM
in my case
2a. it does enter recovery cwm, but cant format and it doesnt see the sd card - cant mount it.
2b. press nothing
2b.a cold boot - doesnt boot normally. it stays on the asus logo page and the bubbles rotates
therefore i dont know where could i install that terminal

is my situation helpless? (

Mirabeau78 said:
is my situation helpless? (
Click to expand...
Click to collapse
While in recovery, are you able to connect to a PC and get adb access from a CMD prompt if in Windows or a terminal if in linux?
Sent from my SM-N900T using XDA Premium HD app

i have windows and i tried using 1click and it cant find the device. old adb base or something even if is completly updated

I too am having this same problem. I had one of the Cyanogenmod nightlies installed, I wanted to upgrade to katkiss so I tried to install TWRP. I installed it using the TWRP app. I thought I installed it successfully, but I didn't. I got stuck at the boot loader. After cold booting android, and installing Rom Manager, I find out that both CWM and TWRP are installed some how? I tried the easyflasher method, but every time I try to install the APX drivers, Windows 8.1 gives me an error about a corrupted hash. I also tried Frederuco's method, and that didn't work either. I'm just stuck between a rock and a hard place right now. AND I JUST GOT THIS TABLET TWO F***ING DAYS AGO!!!!

Jeretista said:
I too am having this same problem. I had one of the Cyanogenmod nightlies installed, I wanted to upgrade to katkiss so I tried to install TWRP. I installed it using the TWRP app. I thought I installed it successfully, but I didn't. I got stuck at the boot loader. After cold booting android, and installing Rom Manager, I find out that both CWM and TWRP are installed some how? I tried the easyflasher method, but every time I try to install the APX drivers, Windows 8.1 gives me an error about a corrupted hash. I also tried Frederuco's method, and that didn't work either. I'm just stuck between a rock and a hard place right now. AND I JUST GOT THIS TABLET TWO F***ING DAYS AGO!!!!
Click to expand...
Click to collapse
Rommanager = not good for Asus tf101. Also, you don't need any app for installing twrp. If you have a working, up to date recovery, you should be able to flash the twrp zip directly from recovery. I recommend my builds of twrp, of course.
Sent from my Transformer TF101 using XDA Premium HD app

NM: Got it to work with easy flasher. Forgot to do a step while installing apex drivers.

Jeretista said:
NM: Got it to work with easy flasher. Forgot to do a step while installing apex drivers.
Click to expand...
Click to collapse
Congratulations. Way to stick with it!

Htc 820 rebooting ONLY into recovery and black screen

Hello i tried to flash twrp recovery on my htc 820u but i think it didn't install. Phone was still working correctly until i tried to do a factory reset. Now it will just boot into recovery every time and i have only a black screen. the phone vibrates when i touch the screen but i cannot switch it off. when i reboot it just goes back to recovery.
Can anyone suggest something please? Is there a way to prevent the phone from booting into recovery?
PS: I'm on lollipop 5.0

Vivacity said:
Hello i tried to flash twrp recovery on my htc 820u but i think it didn't install. Phone was still working correctly until i tried to do a factory reset. Now it will just boot into recovery every time and i have only a black screen. the phone vibrates when i touch the screen but i cannot switch it off. when i reboot it just goes back to recovery.
Can anyone suggest something please? Is there a way to prevent the phone from booting into recovery?
PS: I'm on lollipop 5.0
Click to expand...
Click to collapse
You must not duplicate the post in different forum for the same topic.
Anyway, do it as follow:
1. Connect your device to the PC once it is booted into twrp recovery
2. Copy your Lollipop recovery to the device over adb: adb push recovery.img /external_sd/recovery.img
3. Run: adb shell
4. Run in shell: dd if=/external_sd/recovery.img of=/dev/block/mmcblk0p44
5. Run in shell: reboot
If the device reboots into stock recovery, press and hold vol up + vol down + power until the display goes black. Release the vol up button immediately (while still holding other buttons). Device will reboot into fastboot. Select reboot from the menu.
Hope you are back to business.

tomal said:
You must not duplicate the post in different forum for the same topic.
Anyway, do it as follow:
1. Connect your device to the PC once it is booted into twrp recovery
2. Copy your Lollipop recovery to the device over adb: adb push recovery.img /external_sd/recovery.img
3. Run: adb shell
4. Run in shell: dd if=/external_sd/recovery.img of=/dev/block/mmcblk0p44
5. Run in shell: reboot
If the device reboots into stock recovery, press and hold vol up + vol down + power until the display goes black. Release the vol up button immediately (while still holding other buttons). Device will reboot into fastboot. Select reboot from the menu.
Hope you are back to business.
Click to expand...
Click to collapse
thank you so much. that is much appreciated. hope if anyone else encounters this type of problem this will be able to help them.

tomal said:
You must not duplicate the post in different forum for the same topic.
Anyway, do it as follow:
1. Connect your device to the PC once it is booted into twrp recovery
2. Copy your Lollipop recovery to the device over adb: adb push recovery.img /external_sd/recovery.img
3. Run: adb shell
4. Run in shell: dd if=/external_sd/recovery.img of=/dev/block/mmcblk0p44
5. Run in shell: reboot
If the device reboots into stock recovery, press and hold vol up + vol down + power until the display goes black. Release the vol up button immediately (while still holding other buttons). Device will reboot into fastboot. Select reboot from the menu.
Hope you are back to business.
Click to expand...
Click to collapse
By any chance would you happen to know why the twrp shows black screen? it is still functionnal, would it be because of incompatibility with lollipop? and any way to fix it?
PS: it worked fine on kitkat.

Vivacity said:
By any chance would you happen to know why the twrp shows black screen? it is still functionnal, would it be because of incompatibility with lollipop? and any way to fix it?
PS: it worked fine on kitkat.
Click to expand...
Click to collapse
It goes in sleeping mode, you can disable this in settings=> screen=> enable/disable screen timeout (all in twrp)
---------- Post added at 03:22 PM ---------- Previous post was at 03:09 PM ----------
tomal said:
You must not duplicate the post in different forum for the same topic.
Anyway, do it as follow:
1. Connect your device to the PC once it is booted into twrp recovery
2. Copy your Lollipop recovery to the device over adb: adb push recovery.img /external_sd/recovery.img
3. Run: adb shell
4. Run in shell: dd if=/external_sd/recovery.img of=/dev/block/mmcblk0p44
5. Run in shell: reboot
If the device reboots into stock recovery, press and hold vol up + vol down + power until the display goes black. Release the vol up button immediately (while still holding other buttons). Device will reboot into fastboot. Select reboot from the menu.
Hope you are back to business.
Click to expand...
Click to collapse
What can I do when (for step 2) I do not have a recovery? Can I use one not coming from this Phone?
I did encounter the same "reboot to recovery bug" but I got it from updating the SU Binary.
Hope you can help me.

Hi guys, same problem here, with twrp apparently functioning but nothing displays on screen. Also, impossible to boot the device properly.
Tried the whole adb procedure mentioned above, did nothing as far as I can tell. Trying to reboot from fastboot leads to the HTC green boot logo, but no further... What should I try now ? Is it possible to inject a stock rom from HTC and where can I get it ?
Thanks in advance for your help.

thank you this helped me too

moonwise said:
Hi guys, same problem here, with twrp apparently functioning but nothing displays on screen. Also, impossible to boot the device properly.
Tried the whole adb procedure mentioned above, did nothing as far as I can tell. Trying to reboot from fastboot leads to the HTC green boot logo, but no further... What should I try now ? Is it possible to inject a stock rom from HTC and where can I get it ?
Thanks in advance for your help.
Click to expand...
Click to collapse
Same here! Please help!