Database Info

Help...Bricked

Hey all -
So I followed instructions very specifically for rooting my Xoom on my Mac, and successfully unlocked the Xoom. As soon as I flashed the rootboot.img I rebooted and cannot get past the Motorola logo. I can get into Android Recovery, Fastboot and RSD protocall support but my Mac does not recognize it when I type in ./adb devices....what shall I do? I already performed Factory Reset but this didn't help.
P.S. When I say I followed instructions carefully, that is not to say this is anyone's fault but my own. I obviously did something wrong, and am realizing now that I flashed a 3.0 img file on my 3.1 Honeycomb...this is probably where I went wrong.
Any help would be greatly, greatly appreciated.
Thanks

I had a similar situation using rootboot, don't worry....download the proper boot.img from tiamat's thread, and flash it via fastboot the same way you did the previous one and reboot. That should fix you right up.
And your Xoom is nowhere near bricked, just a little confused. It will be alright.
Sent from my GT-I9000 using XDA Premium App

ah so quick! thank you thank you thank you. how do i flash it if the device won't show up though?

I had to turn USB debugging on in order for my Mac to recognize the Xoom when i typed in ./adb devices...obviously I can't do that now, so it won't show up. Any way we could talk on AIM or something like that so it's easier to communicate?

bloodmut said:
I had to turn USB debugging on in order for my Mac to recognize the Xoom when i typed in ./adb devices...obviously I can't do that now, so it won't show up. Any way we could talk on AIM or something like that so it's easier to communicate?
Click to expand...
Click to collapse
You said you could get into fastboot, yes? Power the Xoom down with power + volume up, reboot into fastboot with power + volume down, plug in the USB, open a prompt in the same folder as you have the new boot image and use the same command that you did before....should have been something like fastboot flash boot boot.img.
That is what worked for me in much the same situation.
Sent from my GT-I9000 using XDA Premium App

It keeps saying unable to create a plugin over and over and over

Ah ok wait. I needed to shut down Parallels. The command ran, but it said failed in terminal. On the Xoom, it says "Boot command is not allowed on consumer devices, Failed to process command error (0x8)"

bloodmut said:
It keeps saying unable to create a plugin over and over and over
Click to expand...
Click to collapse
Unable to create a plugin....hmmm..that one is new to me.
Still don;t panic. If there is a way to get into Fastboot then there is a way to install a new boot image.
Did you type adb remount to start out?

Just unlocked it again using ./fastboot-mac oem unlock...but when i type ./fastboot-mac boot boot.img it says the boot command is not allowed on consumer devices even though I unlocked it...also could you link the .img i'm supposed to use just so I can be sure lol

and no ./adb devices doesn't show my xoom

Here is the boot image...
http://forum.xda-developers.com/showthread.php?t=978013
and shouldn't the command be:
./fastboot-mac flash boot boot.img

Okie Dokie I'm a damn idiot. Flashed it successfully and am at the welcome screen. Thank you so much for helping me, at least I got some practice in with adb and fastboot commands!

bloodmut said:
Okie Dokie I'm a damn idiot. Flashed it successfully and am at the welcome screen. Thank you so much for helping me, at least I got some practice in with adb and fastboot commands!
Click to expand...
Click to collapse
No worries...I viewed it the same way. Down the line the knowledge you have been getting with this process will serve you well. Anyone can one-click, but doing it this way we learn how and why things work in Android.

Absolutely. One last thing. I only flashed the boot.img and the Wifi says "error" under settings...should I have flashed anything else? I downloaded the stock image files and am considering flashing those and starting from scratch

Ended up flashing stock boot, system, and recovery images and am back to stock with no problems. Again, thank you for your patience and help.

bloodmut said:
Absolutely. One last thing. I only flashed the boot.img and the Wifi says "error" under settings...should I have flashed anything else? I downloaded the stock image files and am considering flashing those and starting from scratch
Click to expand...
Click to collapse
Actually I would go in and flash Tiamat's kernel via CWM. That worked for me in restoring my wifi.
Otherwise you can run the following commands to restore wifi (I think...)
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
adb push cifs.ko /system/lib/modules/cifs.ko
adb push tun.ko /system/lib/modules/tun.ko
adb push scsi_wait_scan.ko /system/lib/modules/scsi_wait_scan.ko
EDIT....OR you can just go back to stock and start again. Good luck.

[Q] ClockWork Mod help needed (has not been answered before, very unique situation)

First off, I am new to this community so I apologize if this is in the wrong place or if I violated other rules.
Hi there, I have been trying to flash Clockwork Mod recovery image onto my lg optimus 2x for hours and hours and it’s not working. I have tried several methods:
1. ROM Manager: during the process of flashing the recovery image, it stops and shows the notification “error while running privileged commands”, a few minutes later, my phone crashes, and on reboot, it gets stuck on the boot loop. I end up having to restore my phone every time (which I’ve done 30+ times of)
*Note: when I activate the recovery menu the phone automatically starts to wipe everything before I gain access to the menu, so every time I go into the recovery menu my phone gets restored.
2. I’ve tried flashing the recovery image from my computer following the procedures of this website android.modaco(dot)com/topic/335479-29-jun-4005-clockworkmod-recovery-for-the-lg-optimus-2x/. Basically, I run the .batch windows installation file, and after it finishes I reboot my phone like it said, and my phone is stuck in a boot loop—help factory reset again.
3. I have tried using flash_image (addictivetips(dot)com/mobile/how-to-install-a-custom-recovery-to-an-android-phone-device/), and everything is working fine as I run the following commands:
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
Until the last line, I get the message “error scanning partition” at the very end, and can’t flash the recovery image.
Fastboot: I have not attempted the fastboot method yet, because upon researching on how to fastboot my phone on google, I found no method for my specific phone, and explanation of required software and steps on a computer was not very clear enough for me to understand. If anyone could explain in detail how to fastboot I would really appreciate it.
I assume flashing CWM on the optimus 2x shouldn’t be this much of a hassle so something must be wrong, I have spent more than 10 hours trying the flash it and restored my phone more than 30 times.
Please help, thankyou.

It seems like you don't have superuser access...did you root your phone before trying to install the recovery?

My phone is rooted and it does for sure have su permissions

U are not alone! I kind of have the same problem with my Samsung. http://forum.xda-developers.com/showthread.php?t=1640523 It's pain in the *** if u ask me! Plz help us!

Don't know if your phone has fastboot or if it's a HTC only thing. But search your devices xda for fastboot.
Get fast boot,usb drivers,
boot to bootloader, connect to pc, on phone turn on fast boot, on pc use fast boot commands :
fastboot flash recovery xyzfile.img
Wait...
Done
Why are SMARTphones soo... Freaking Dumb?
---------- Post added at 10:51 PM ---------- Previous post was at 10:46 PM ----------
Awe cra#p, I just replied to a year old thread by mistake, sorry.
Looking for something similar and landed here, sorry mods.
Why are SMARTphones soo... Freaking Dumb?

[Q] Razr HD Maxx Boot Loop - Need Help

I have a Razr Maxx HD. I am stuck in a bootloop and cannot recovery with factory firmware. The phone was rooted but the bootloader not unlocked. I could use some help. I have tried many of the things that I have seen on online forums but have not had success.
Here is what led to the problem:
1) I rooted my phone. It rebooted fine.
2) I downloaded a modified framework-res.apk and Root Explorer (File Manager) to my phone.
3) Mounted Root Explorer in r/w mode.
4) Copied and overwrote original /system/framework-res.apk with modified file.
5) Phone rebooted and got stuck in loop.
*USB debug mode was on at time of failure.
Here is what I have tried on a Mac:
1) In Android System Recovery <3e>, I tried "Wipe cache partition" and "Wipe data/factory reset." That did not work.
2) I downloaded the Mac Motorola Drivers from their website. I download and installed Android SDK and platform-tools package. I can run ADB in my terminal. However, it only shows the device when in "Recovery/Apply update from ADB " mode. When I perform "adb devices" it shows a serial number and "sideload." I use the "adb sideload" command to transfer the firmware .zip file. It reads the following after it is uploaded:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/framework-res.apk", "bunch of numbers")
Installation aborted.
This was after sideloading the package "Blur_Version.9.1.41.XT926.Verizon.en.US.zip." This was the same file I was modifying earlier. I have tried it with the fireware xml.zip files from sbf.droid-developers.org/vanquish/list.php and only got to line 3 before it aborted.
3) Tried to update from microSD card and got same result.
4) I have the original framework-res.apk file; however I don't know how to push it. I cannot get it to recognize the device in ADB outside of the Recovery from ADB sideload option. All other ADB commands return an "error : closed" reply.
5) As far as Fastboot, it reads AP Flastboot Flash Mode (S), Device is LOCKED. Status Code: 0, Battery OK, USB Connected. I got the device ID and tried the online unlock key generator on Motorola.com but it stated my device was not eligible for unlocking at this time, so it remains locked.
Here is what I have tried on a Windows 7 PC:
1) I downloaded the Windows Motorola Drivers from their website. I download and installed Android SDK and platform-tools package. I can open ADB in cmd line. However, when I perform "adb devices," it does not show a serial number, even in Recovery ADB sideload.
2) I downloaded RSD Lite 5.3.1. Selected one of the extracted sbf.droid-developers.org/vanquish/list.php .xml files. Hit start and nothing happened. "Show Device" did not bring anything up. I am guessing the PC is not detecting the device, but I uploaded the latest Motorola Drivers Package. I even tried the Google USB Driver install in Android SDK.
Can you recommend another course of action or a means of getting one of these methods to work? Please help me unbrick my phone. Thank you in advance for any advice.

..
Boot into the stock recovery by powering off the phone then holding the power button and volume up and down button. Then use the volume keys to select recovery. When it boots you should see andy on his back and a red triangle. This is the stock recovery. Now try adb devices again.

mentose457 said:
..
Boot into the stock recovery by powering off the phone then holding the power button and volume up and down button. Then use the volume keys to select recovery. When it boots you should see andy on his back and a red triangle. This is the stock recovery. Now try adb devices again.
Click to expand...
Click to collapse
It does not work. No devices were listed.
The only time "adb devices" has worked is in "apply update from adb" mode, but here only "adb sideload" command works and other commands return "error : closed". So it does not seem to me to be an issue with my computer sending commands, but my phone allowing them to received?

rmp2737 said:
It does not work. No devices were listed.
The only time "adb devices" has worked is in "apply update from adb" mode, but here only "adb sideload" command works and other commands return "error : closed". So it does not seem to me to be an issue with my computer sending commands, but my phone allowing them to received?
Click to expand...
Click to collapse
Is this the case in both windowz and osx?
Sent from my DROID RAZR HD using Tapatalk 4 Beta
---------- Post added at 05:31 PM ---------- Previous post was at 05:29 PM ----------
I read on xda news that you can create your own update zip to flash in stock recovery. In theory you could have it flash the original framework file. I'll do a bit more digging on that and hey back to you.
Sent from my DROID RAZR HD using Tapatalk 4 Beta
---------- Post added at 06:00 PM ---------- Previous post was at 05:31 PM ----------
I cant find the article bout using a stock update zip. Though you could flash the latest ota update. It would eliminate any chance of you unlocking the bootloader and possibly obtaining root.

mentose457 said:
Is this the case in both windowz and osx?
Click to expand...
Click to collapse
That is only for OSX. I could not even get the adb at all (even in sideload) on Windows. This makes me think it is a driver issue on the Windows computer. It is a work computer and it may be a driver install issue requiring admin access. I will try to fix the driver issue and run RSD Lite again and let you know.
mentose457 said:
I read on xda news that you can create your own update zip to flash in stock recovery. In theory you could have it flash the original framework file. I'll do a bit more digging on that and hey back to you.
Click to expand...
Click to collapse
Thanks. Let me know if you find it.

If you could get your phone to be recognized in adb all of your problems could be solved. You could even unlock your bootloader without being able to get into the os. If I were you id continue to try to get my computer to communicate with my phone.
---------- Post added at 06:08 PM ---------- Previous post was at 06:05 PM ----------
rmp2737 said:
That is only for OSX. I could not even get the adb at all (even in sideload) on Windows. This makes me think it is a driver issue on the Windows computer. It is a work computer and it may be a driver install issue requiring admin access. I will try to fix the driver issue and run RSD Lite again and let you know.
Thanks. Let me know if you find it.
Click to expand...
Click to collapse
is the "apply update from adb" part of the stock recovery? Ive never encountered it.
---------- Post added at 06:09 PM ---------- Previous post was at 06:08 PM ----------
Have you tried to run adb devices while the phone is bootlooping? It may get far enough in the boot process to allow you to use adb.

mentose457 said:
Is the "apply update from adb" part of the stock recovery? Ive never encountered it.
Click to expand...
Click to collapse
Yes, it is part of the stock recovery. I cannot get adb to run at any stage outside of it.
I got fastboot working on the WIndows computer. I had to specify installing the drivers as an Admin. After that, RSD Lite could run. It was able to flash every other file in the package but it failed only on the system.img file.

rmp2737 said:
Yes, it is part of the stock recovery. I cannot get adb to run at any stage outside of it.
I got fastboot working on the WIndows computer. I had to specify installing the drivers as an Admin. After that, RSD Lite could run. It was able to flash every other file in the package but it failed only on the system.img file.
Click to expand...
Click to collapse
Try it again? If all you did was push a botched framework-res.apk to the system folder then you really shouldnt have any problems reverting back with rsd.
mentose457 said:
Have you tried to run adb devices while the phone is bootlooping? It may get far enough in the boot process to allow you to use adb.
Click to expand...
Click to collapse
Have you tried this ^^^
---------- Post added at 07:34 AM ---------- Previous post was at 07:17 AM ----------
What method did you use to fastboot?

mentose457 said:
Try it again? If all you did was push a botched framework-res.apk to the system folder then you really shouldnt have any problems reverting back with rsd.
Click to expand...
Click to collapse
I tried it a few times with RSD Lite different file versions. They did not work. Perhaps the permissions for the folder were not reverted and this is a problem?
I have tried to connect to with ADB during the bootloop and in the recovery mode menu. It did not work.
As for fast boot, I am using the AP Flastboot Flash Mode as part of stock recovery.
Thank you for your help so far. I am lost at this point, since it seems all the typical methods are not working.

I am suspect that performing the factory reset disabled USB Debugging Mode and that is why ADB won't work. If so, I think I am stuck because it's Catch 22. I can't push the files with ADB, I cannot flash the system.img file because it is too big, I cannot flash the system.img file with RSD Lite (for what I can only assume is a permission error), I cannot erase the system.img to clear it before I flash over it because the bootloader is locked, and I can't unlock the bootloader because the exploit requires you to use ADB commands. Unless, I am missing something.

Screwed [Solved]

Hello,
I screwed up while wiping and now my tab only boots to TWRP but wont mount anything.I found a similar case in this forum but Im too unfamilar with ADB/Fastboot to affect a solution.
Is ther a way to partition my tablet from fastboot?
The TF700t is unlocked.
adb and fastboot see the device.
TIA.....

DarkDarwin said:
Hello,
I screwed up while wiping and now my tab only boots to TWRP but wont mount anything.I found a similar case in this forum but Im too unfamilar with ADB/Fastboot to affect a solution.
Is ther a way to partition my tablet from fastboot?
The TF700t is unlocked.
adb and fastboot see the device.
TIA.....
Click to expand...
Click to collapse
What exactly did you wipe, and how did you screw up? To find out more about your situation, boot to your recovery (which version, btw?) and run these commands:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt

_that said:
What exactly did you wipe, and how did you screw up? To find out more about your situation, boot to your recovery (which version, btw?) and run these commands:
Code:
adb shell dmesg > dmesg.txt
adb shell cat /proc/partitions > partitions.txt
Click to expand...
Click to collapse
Im afraid I wiped everything.I think my mistake was wiping in stock recovery instead of TWRP..thus it only boots to TWRP now.
I tried those commands but my machine was hanging like it was waiting for the device so I am going to uninstall and reinstall the windows drivers and ADB/Fastboot and do the commands again ,Ive been at work since this morning so ive got some honey dos then I can start trying it again.
Thanks so much!

When I run the commands as shell I get the ` # <[6n in front of all entries ( I assume thats bc Im booted to recovery not fastboot) and the end result is always "not found" ie: shell not found , adb not found ect....
When I type adb shell sometimes it just hangs, the dmesg command actually writes a file but its an empty file and the terminal just hangs
Im pretty sure if I cant figure out a way to delete this TWRP Im never going to be able to properly use ADB/Fastboot ths never reinstall an OS and decent Recovery..

DarkDarwin said:
When I run the commands as shell I get the ` # <[6n in front of all entries ( I assume thats bc Im booted to recovery not fastboot) and the end result is always "not found" ie: shell not found , adb not found ect....
When I type adb shell sometimes it just hangs, the dmesg command actually writes a file but its an empty file and the terminal just hangs
Im pretty sure if I cant figure out a way to delete this TWRP Im never going to be able to properly use ADB/Fastboot ths never reinstall an OS and decent Recovery..
Click to expand...
Click to collapse
So am I correct in saying that you can get to fastboot ?

lj50036 said:
So am I correct in saying that you can get to fastboot ?
Click to expand...
Click to collapse
well i can run fastboot and adb commands from my pc but the T700t is in recovery (my only boot choice)
but technically yes I can get to fastboot

DarkDarwin said:
well i can run fastboot and adb commands from my pc but the T700t is in recovery (my only boot choice)
but technically yes I can get to fastboot
Click to expand...
Click to collapse
No - can you get the tablet into fastboot mode?
Either by holding Power and Volume down when booting up or, in recovery, issue
Code:
adb reboot-bootloader
What do you get with the command
Code:
adb devices
when in recovery, and if you can get into fastboot mode:
Code:
fastboot devices
Also, you still haven't told us which recovery version you are running.

We had to use _that's bootit.ko to get it out of recovery into fastboot...
Then it was a flash of the stock Asus blob ...
Got him up and running . :good:
@DarkDarwin can you add SOLVED to the thread title ...
Thx Josh

berndblb said:
No - can you get the tablet into fastboot mode?
Either by holding Power and Volume down when booting up or, in recovery, issue
Code:
adb reboot-bootloader
What do you get with the command
Code:
adb devices
when in recovery, and if you can get into fastboot mode:
Code:
fastboot devices
Also, you still haven't told us which recovery version you are running.
Click to expand...
Click to collapse
Thanks for trying to help me yesterday bro!

lj50036 said:
We had to use _that's bootit.ko to get it out of recovery into fastboot...
Then it was a flash of the stock Asus blob ...
Got him up and running . :good:
@DarkDarwin can you add SOLVED to the thread title ...
Thx Josh
Click to expand...
Click to collapse
Any chance we could get a step-bystep on that? Pleeeaaase?

berndblb said:
Any chance we could get a step-bystep on that? Pleeeaaase?
Click to expand...
Click to collapse
Yes, Give me a day or so and I will post it in the Q&A section as its own thread ...
Thx Josh

lj50036 said:
Yes, Give me a day or so and I will post it in the Q&A section as its own thread ...
Thx Josh
Click to expand...
Click to collapse
I went out and got a bigger SD card (64) to try and implement the DATA2SD script.I think I was successful as I now have new folders there named Android and Data that I didn't have before...However,I wonder if I was supposed to wipe anything before I re-flashed the ROM after inserting the formatted , partitioned SD...
I have to admit the I/O issue is extremely aggravating..I cant believe Asus marred an otherwise excellent device like that.

I was sent from this topic: http://forum.xda-developers.com/showthread.php?t=2179759&page=23
To this topic, I also have a similar problem.
Read my comment from last topic:
Ok, when I boot up in android, I can use adb command reboot bootloader to boot in the bootloader.
When i then try fastboot erase system, it's still hangs with waiting for device..
The bootloader is not stuck, i can again boot up android..
it's impossible to open terminal, because the touch is going crazy..
Hmm, i'm trying something else.
I still had 10x tf300 for repair. there are multiple cracked with 5184n version.
I installed the cracked display assembly on this one, then i just can normally use the keyboard.
Will try again in terminal
edit: what command to use in terminal?
Dont forget, i flashed the recovery, but didnt install supersu zip yet..
The strange thing is, when im in the bootloader, i can use fastboot flash recovery command, and write the right recovery.
It's also succesfull (sending recovery OK, writing recovery OK)
But, the transformer hangs in the bootloader after finished (freeze)
When trying to reboot, it's automaticaly going again booting up twrp (enter password)
So it didnt write the recovery, by example if i write twrp 2.7, it still gives me 2.6.3.0 (installed first time)
extra information:
If i'm booted up, and then adb reboot bootloader, then try fastboot commands, they don't work. it keeps saying waiting for devices.., the fastboot commands like flash works for 1 second then the tablet freezes.
Click to expand...
Click to collapse
So, fastboot commands are not working, how to get the bootloader normal again and that it reads fastboot commands?

Look in Device Manager on your PC and check that the Asus ADB interface drivers are there

Wow what a difference DATA2SD and ROM2SD make!

lvrijn said:
I was sent from this topic: http://forum.xda-developers.com/showthread.php?t=2179759&page=23
To this topic, I also have a similar problem.
Read my comment from last topic:
So, fastboot commands are not working, how to get the bootloader normal again and that it reads fastboot commands?
Click to expand...
Click to collapse
Hey there, I may have a solution, I am very busy right now working on a step by step for a few diff unbricking methods...
Yes this sounds like a windows driver issue.... Let me see if I can find some info on this topic ..
Thx Josh

DarkDarwin said:
Look in Device Manager on your PC and check that the Asus ADB interface drivers are there
Click to expand...
Click to collapse
Like I already told, I have flashed dozen of transformers. Adb commands are working (like adb reboot boot loader) it works when booted in android and when in twrp (password). Fastboot commands give waiting for device, but fastboor flash recovery works but the transformer then freezes..
After this problem I already have flashed 3transformers correctly.
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
lj50036 said:
Hey there, I may have a solution, I am very busy right now working on a step by step for a few diff unbricking methods...
Yes this sounds like a windows driver issue.... Let me see if I can find some info on this topic ..
Thx Josh
Click to expand...
Click to collapse
Why would it be a windows driver issue? Other transformers I can flash succesfully adb and fastboot fully working

lvrijn said:
Like I already told, I have flashed dozen of transformers. Adb commands are working (like adb reboot boot loader) it works when booted in android and when in twrp (password). Fastboot commands give waiting for device, but fastboor flash recovery works but the transformer then freezes..
After this problem I already have flashed 3transformers correctly.
---------- Post added at 03:41 PM ---------- Previous post was at 03:37 PM ----------
Why would it be a windows driver issue? Other transformers I can flash succesfully adb and fastboot fully working
Click to expand...
Click to collapse
LOL, looking for help but you know what you got...
WOW

lj50036 said:
LOL, looking for help but you know what you got...
WOW
Click to expand...
Click to collapse
Sorry, I dont understand what you mean. What do you know I got?

lvrijn said:
Sorry, I dont understand what you mean. What do you know I got?
Click to expand...
Click to collapse
Sounds like you know more about this then any of us.
Not all Transformer tablets use the same drivers.
Window is very picky about what driver it will use for what device ...

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!