Database Develop

Nexus One broken power button rooting

Hi,
i have a nexus one with a broken power button, my warranty is out so there is no replacement, i want to root it to be able to install trackball wake s,o i can open the mobile and close it.
when i try to access the bootloader i hold the trackball then i take off the battery 2 to 3 time to switch on, and if i keep holding the trackball it access the bootloader screen.
but i can't choose bootloader because i need to use the power button to do so, i also tried the universal androot, i got a message saying failed! no ~~~fu goo~~~.
my OS version is 2.2.2, build number FRG83G.
please any help.

You can try manual root. I find it easier getting the drivers to install when the phone is in fastboot, but it isn't essential...
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App

If you hold Vol Up + Track Ball and Remove & Insert your battery while your plug in to USB cable you can access Fastboot screen. But you will not be able to select any options because it needs power switch to select options.

many thanks danger-rat, i got a superuser access now on my list
i need one more thing if you please, how can i install cyanogenmod? because as i mentioned before i need trackball wake setting.
best regards,

The quickest way in my opinion is to install ROM manager from the market. You can then choose to install either Clockwork recovery image or Amon_RA. If you choose Clockwork then you can use ROM manager to automate backing up/flashing of new ROMs. Alternatively you can choose Amon_RA recovery, which I personally use. There are only a few differences other than layout but both are excellent recoveries.
Once you've installed a recovery image, you can either download CM7 manually and place it on your SD card or use ROM manager to download it. Depending on your choice of recovery you can use ROM manager to backup then flash or alternatively go into recovery manually and flash CM7 there. To reboot directly to recovery either hook the phone up to a PC and issue the command 'adb reboot recovery' or alternatively install an application like Quickboot which does the exact same thing through a GUI.
You shouldn't really have any problems once you've flash CM7 as it has a reboot to recovery option built in. Good luck
Edit: Oh and always, I repeat always Nandroid! It'll save you any headaches.

thanks man for the guide, it worked wonderfully, but what do Nandroid do?!

omarqa said:
thanks man for the guide, it worked wonderfully, but what do Nandroid do?!
Click to expand...
Click to collapse
It's like imaging software for a PC, it takes a screenshot of your system at that time which can then be restored should anything go awry. I have a couple that I switch between

Bootloop cyanogen
Hi all,
after all your help guys i managed to get my self into trouble again , after i installed cyanogen i found out that the market is not there, and i couldn't add gmail account also, so i recovered the previous one.
i thought I'd reinstalled cyanogen again, so after a couple of failures in installing it "getting an android with and explanation mark over the head", the last one worked but it booted into a boot loop, i keep getting the cyanogen screen again and again.
can i do something with command line such as adb shell
best regards,

I ran into the same problem, it's a little long winded but I found this to work. Also, it seems your recovery is reverting to stock. This is because of files recovery-from-boot.p and install-recovery.sh. After flashing the ROM go to terminal and issue the following commands (Without #) :
# su (Making sure to accept the root privileges prompt)
# mount -o remount,rw /dev/null /system
# mv /system/recovery-from-boot.p /system/recovery-from-boot.p.bak
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# reboot
More info here.
Then flash Amon_RA recovery or Clockwork during fastboot commands from my first link. Rename the image downloaded to recovery and issue the following command during fastboot:
fastboot flash recovery recovery.img
You can then follow the rest of the guide to return to recovery. If you ever end up in a bootloop again just follow the guide in the first link as is and you'll be back in recovery to recover a nandroid backup or flash again.
Also it seems you're missing the Googleapps (Gapps) package for Gingerbread. Flash this after flashing CM7.

omarqa said:
Hi all,
after all your help guys i managed to get my self into trouble again , after i installed cyanogen i found out that the market is not there, and i couldn't add gmail account also, so i recovered the previous one.
i thought I'd reinstalled cyanogen again, so after a couple of failures in installing it "getting an android with and explanation mark over the head", the last one worked but it booted into a boot loop, i keep getting the cyanogen screen again and again.
can i do something with command line such as adb shell
best regards,
Click to expand...
Click to collapse
Did you flash a compatible gapps package (Google apps)? The market and other Google apps are not distributed with Cyanogen ROMs, and have to be flashed separately...
Edit: Sorry, must have overlooked the tail end of the post above...
Sent from my Nexus One using XDA App

how to flash the ROM

omarqa said:
how to flash the ROM
Click to expand...
Click to collapse
There should be an option saying something along the lines of 'Flash zip from SD card'. Simply browse to the zip and flash.

whenever i try to do recovery or anything i keep getting FAILED (remote: signature verify fail) anybody know why i keep getting this???

omarqa said:
whenever i try to do recovery or anything i keep getting FAILED (remote: signature verify fail) anybody know why i keep getting this???
Click to expand...
Click to collapse
Is your device unlocked? It must be unlocked to issue certain fastboot commands.

Which custom recovery do you have installed?
Sent from my Nexus One using XDA App

thanks guys, it got fixed.
so how can i install cyanogenmod, every time i try to install version 6.1.1 i get a android log with exclamation mark over it, any ideas
your help is really appreciated,
edit: i mean by fixed that i restored the original version of the device.

That's the stock recovery (hence my previous question)...
You need to install a custom recovery, and also delete the following two files:
/system/etc/install-recovery.sh
/system/recovery-from-boot.p
(as stated by HD earlier)
Sent from my Nexus One using XDA App

[Q] stuck at bootloader!!

Current device status:
M7-UL
Relocked
S-OFF
CID-11111111
Stock recovery!!
before action or Problem:
Did full wipe through custom recovery TWRP. which cost me to loose everything SDcard including my OS. Now i can't reboot nor i have custom rom.zip----how stupid
Tries:
1. Tried to ADB push custom rom but was not successful cause SDcard mount. tried to unmount but unusful.
2. so i decided to get the orignal firmware 1.29 (before i was 2.17)---please don't ask why
I used mike guide. it work----Thanks mike for the guide
Now i'm back to the old firmware (1.29) with no OS to boot and stock recovery.
I hope the expert here can give me a hand on this and get my HTC one back to life!!
Thanks in advance for you supports

omvingG upon
aburobeen said:
Current device status:
M7-UL
Relocked
S-OFF
CID-11111111
Stock recovery!!
before action or Problem:
Did full wipe through custom recovery TWRP. which cost me to loose everything SDcard including my OS. Now i can't reboot nor i have custom rom.zip----how stupid
Tries:
1. Tried to ADB push custom rom but was not successful cause SDcard mount. tried to unmount but unusful.
2. so i decided to get the orignal firmware 1.29 (before i was 2.17)---please don't ask why
I used mike guide. it work----Thanks mike for the guide
Now i'm back to the old firmware (1.29) with no OS to boot and stock recovery.
I hope the expert here can give me a hand on this and get my HTC one back to life!!
Thanks in advance for you supports
Click to expand...
Click to collapse
Use twrp to sideload the rom. I think you go to Advance tab in TWRP and choose sideload rom and adb I think the command is "adb sideload <name of rom>".
I can't remember fully. I hope someonce can assist you and correct me if I'm wrong.

Rex2369 said:
Use twrp to sideload the rom. I think you go to Advance tab in TWRP and choose sideload rom and adb I think the command is "adb sideload <name of rom>".
I can't remember fully. I hope someonce can assist you and correct me if I'm wrong.
Click to expand...
Click to collapse
Thanks for the replay.
The problem is i'm on stock recovery. I got it back after updating the firmware.
Now i'm relocked and stuck with the stock recovery.
I thinks first i need to unlock and then flash the custom recovery.
But how to do it while i'm in bootloader and with no OS in place!!

When you are in bootloader, click on Fastboot. After you are in Fastboot USB mode (it will show that on the screen), unlock the bootloader using this tutorial:
http://www.redmondpie.com/how-to-unlock-htc-one-bootloader-tutorial/
After you are done with that, you'll need to download TWRP 2.5.0 and place it inside your fastboot folder on your computer, and then open a command prompt window from there (shift + right click and open command prompt window here) and then execute this command:
fastboot flash recovery recovery.img
Of course you replace recovery.img with whatever the name of your recovery is, in that case TWRP 2.5.0's zip file.

TarekElsakka said:
When you are in bootloader, click on Fastboot. After you are in Fastboot USB mode (it will show that on the screen), unlock the bootloader using this tutorial:
http://www.redmondpie.com/how-to-unlock-htc-one-bootloader-tutorial/
After you are done with that, you'll need to download TWRP 2.5.0 and place it inside your fastboot folder on your computer, and then open a command prompt window from there (shift + right click and open command prompt window here) and then execute this command:
fastboot flash recovery recovery.img
Of course you replace recovery.img with whatever the name of your recovery is, in that case TWRP 2.5.0's zip file.
Click to expand...
Click to collapse
Thanks a lot.
it helped
Now how i can get my OS back to business.
Do i need to flash the stock rom or any rom? and how can i flash it!!

So, i think is better flashing a ruu, like the stock european ruu and, via Revone tool, flash a recovery
You're s-offed, you don't need unlock your bootloader

Guich said:
So, i think is better flashing a ruu, like the stock european ruu and, via Revone tool, flash a recovery
You're s-offed, you don't need unlock your bootloader
Click to expand...
Click to collapse
Thanks for the tip.
i'm only a littlle android guy. i hardly manage to get my S-OFF.
would you be so kind to show me on how to do that:angel:

Depends on what you are looking for. Are you trying to revert your device to stock status so you can receive OTA updates? Because that would mean flashing a RUU and relocking the bootloader, as mentioned above. However if you aren't interested in OTA updates (which we don't know when will be available) then go for the easier route, a custom ROM which you flash via TWRP recovery. After you go into TWRP, go to Advanced and choose ADB sideload and then slide to start, then use your computer to adb sideload rom.zip (of course rom.zip will be replaced by whichever ROM you want to sideload).
This is to set up ADB:
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
The proper drivers for your PC to recognize the device in ADB mode are obtained by installing HTC Sync Manager.

TarekElsakka said:
Depends on what you are looking for. Are you trying to revert your device to stock status so you can receive OTA updates? Because that would mean flashing a RUU and relocking the bootloader, as mentioned above. However if you aren't interested in OTA updates (which we don't know when will be available) then go for the easier route, a custom ROM which you flash via TWRP recovery. After you go into TWRP, go to Advanced and choose ADB sideload and then slide to start, then use your computer to adb sideload rom.zip (of course rom.zip will be replaced by whichever ROM you want to sideload).
This is to set up ADB:
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
The proper drivers for your PC to recognize the device in ADB mode are obtained by installing HTC Sync Manager.
Click to expand...
Click to collapse
He can use the adb push command too...

Ah okay. I am new to all of this so I don't have sufficient information, I was just sharing how I got to fix my device when I was in the same situation.

I used adb push zip file as below instruction:
C:\Android>adb devices
List of devices attached
FA35VW927790 recovery
C:\Android>adb push Android_Revolution_HD-One_9.4.zip /data/media/
3100 KB/s (1017950778 bytes in 320.621s)
C:\Android>adb reboot recovery
C:\Android>
I try to look for the zip file but did not find it?? any ideas

Still stuck at this point.
I tried to adb push it many times but still no success
:crying:
Please guys tell me if im doing something wrong or you have a better way of doing it.

aburobeen said:
Still stuck at this point.
I tried to adb push it many times but still no success
:crying:
Please guys tell me if im doing something wrong or you have a better way of doing it.
Click to expand...
Click to collapse
The zip will be there somewhere, I command '/sdcard' instead of '/data/media'.
If you still can't find it just use
adb sideload Android_Revolution_HD-One_9.4.zip
Choose install zip from sideload in recovery and once it's finished transferring it will begin to install automatically so you won't have to look for the zip file
Sent from my HTC One using xda premium

aburobeen said:
I used adb push zip file as below instruction:
C:\Android>adb devices
List of devices attached
FA35VW927790 recovery
C:\Android>adb push Android_Revolution_HD-One_9.4.zip /data/media/
3100 KB/s (1017950778 bytes in 320.621s)
C:\Android>adb reboot recovery
C:\Android>
I try to look for the zip file but did not find it?? any ideas
Click to expand...
Click to collapse
because you wiped your internal storage there is no file structure there, that's why you cant find the zip file.
You'll have to sideload your rom from twrp then boot up your phone which will create the needed directories.
1) update your android sdk. Sideload only works on certain versions of the sdk.
2) Place the rom you would like to flash in the same folder as fastboot and adb.( for you it looks like C:\Android\sdk\platform-tools
3) next from twrp under the advanced tab turn on adb sideload
4) issue the command adb sideload name of rom.zip
good luck

aburobeen said:
Still stuck at this point.
I tried to adb push it many times but still no success
:crying:
Please guys tell me if im doing something wrong or you have a better way of doing it.
Click to expand...
Click to collapse
If you use /sdcard then it will work fine, I had the same issue

Victory at last :laugh:
My experience:
TWRP recovery
1.Tried to adb push /sdcard succeeded on this but failed to flash!!
2. Tried to adb sideload failed.
3. Flashed another recovery CWM.
4. adb sideload file.zip...........success
I don't why TWRP recovery was not responding correctly.
Any way got my phone back to life. and hopefully my experience could help people who made the same foolish mistake!!
Thanks to everybody who contributed to this post.
Cheers all

Maybe you had an earlier version of TWRP which had incompatibility issues with ADB. Anyway I'm glad you got through it. I sure hate being stuck like that as well.
Sent from my HTC One using Tapatalk 4 Beta

aburobeen said:
Victory at last :laugh:
My experience:
TWRP recovery
1.Tried to adb push /sdcard succeeded on this but failed to flash!!
2. Tried to adb sideload failed.
3. Flashed another recovery CWM.
4. adb sideload file.zip...........success
I don't why TWRP recovery was not responding correctly.
Any way got my phone back to life. and hopefully my experience could help people who made the same foolish mistake!!
Thanks to everybody who contributed to this post.
Cheers all
Click to expand...
Click to collapse
What version of CWM did you flash to get sideload working??

Alex740il said:
What version of CWM did you flash to get sideload working??
Click to expand...
Click to collapse
I used the latest CWM Version 6.0.3.2.

question for taking the OTA with root and safestrap?

im wanting to flash the Eclipse 1.0 ROM that is out but im currently still on the initial version that was on the phone at release. i have heard that taking the OTA when rooted can cause boot loops and that i need to OTA fist before flashing Eclipse. what are the steps i need to take in order to safky take the OTA?
also, are titanium backups working so i can load all my apps and data once i get onto eclipse? i thought i saw something about them not working a while back and have not been keeping up with if this has been sorted out?

yamaha83 said:
im wanting to flash the Eclipse 1.0 ROM that is out but im currently still on the initial version that was on the phone at release. i have heard that taking the OTA when rooted can cause boot loops and that i need to OTA fist before flashing Eclipse. what are the steps i need to take in order to safky take the OTA?
also, are titanium backups working so i can load all my apps and data once i get onto eclipse? i thought i saw something about them not working a while back and have not been keeping up with if this has been sorted out?
Click to expand...
Click to collapse
download and install the newest SS that was just released. then go to your stock slot. uninstall SS from the SS app. Then flash stock recovery and system (assuming you didn't flash your baseband as well, if you did then flash the old baseband back on there). then either install pwnmymoto without running, take ota, then check to confirm you have root. OR take ota then root with rockmymoto. then follow instructions to instlal SS on rootzwiki. then follow instructions for the rom.
TIBU works. (not sure for the eclipse rom, just post over there on that thread that question, i haven't run it yet so idk but i would presume that it will since it is based off of the original FW for the phone and not source.) I typically install the apps i had myself from the play store then just reinstall data with TiBu. This is ebcause I have ran into problems installing apps from tibu personally but it was most likely my own error. I never have a problem otherwise, so i just install my own apps. Sometimes google or something does it for me as well so i only instlal a few root apps taht i already saved the apks for so i just move the folder to my phone and install them. Once done with all of that i go and put my data back in with tibu.

jayboyyyy said:
download and install the newest SS that was just released. then go to your stock slot. uninstall SS from the SS app. Then flash stock recovery and system (assuming you didn't flash your baseband as well, if you did then flash the old baseband back on there). then either install pwnmymoto without running, take ota, then check to confirm you have root. OR take ota then root with rockmymoto. then follow instructions to instlal SS on rootzwiki. then follow instructions for the rom.
TIBU works. (not sure for the eclipse rom, just post over there on that thread that question, i haven't run it yet so idk but i would presume that it will since it is based off of the original FW for the phone and not source.) I typically install the apps i had myself from the play store then just reinstall data with TiBu. This is ebcause I have ran into problems installing apps from tibu personally but it was most likely my own error. I never have a problem otherwise, so i just install my own apps. Sometimes google or something does it for me as well so i only instlal a few root apps taht i already saved the apks for so i just move the folder to my phone and install them. Once done with all of that i go and put my data back in with tibu.
Click to expand...
Click to collapse
ok so within the safestrap app i click uninstall recovery, i assume thats what you mean by uninstall safestrap from within the app? after that how do i install the stock recovery and system?

yamaha83 said:
ok so within the safestrap app i click uninstall recovery, i assume thats what you mean by uninstall safestrap from within the app? after that how do i install the stock recovery and system?
Click to expand...
Click to collapse
hmmmm. you go and learn how to use fastboot is how you do it lol. you can also just rsd lite if you don't care about keeping your data. i just posted some general instructions that will help you with fastboot.
http://forum.xda-developers.com/showthread.php?t=2525495&page=6
also , if you don't want to install the sdk tools you can just go download the motofastboot file from here, and run that
http://forum.xda-developers.com/showthread.php?t=2489249

jayboyyyy said:
hmmmm. you go and learn how to use fastboot is how you do it lol. you can also just rsd lite if you don't care about keeping your data. i just posted some general instructions that will help you with fastboot.
http://forum.xda-developers.com/showthread.php?t=2525495&page=6
also , if you don't want to install the sdk tools you can just go download the motofastboot file from here, and run that
http://forum.xda-developers.com/showthread.php?t=2489249
Click to expand...
Click to collapse
i may just use RSDLITE... its been a long time since I had to use fastboot dont really have the time to mess around with it. hmmmmmm

yamaha83 said:
i may just use RSDLITE... its been a long time since I had to use fastboot dont really have the time to mess around with it. hmmmmmm
Click to expand...
Click to collapse
its extremely simple in reality. download that fastboot file from that link. put it in a a folder on your c drive (for instance "fastboot") download the FW for your hone. unzip. put the system and recovery img in the fastboot file you created. then open cmd. type "cd c:/fastboot" THEn plug phone into computer, the reboot phone into fastboot mode with power button and volume down button held for like 3 secs. then run commands in fastboot, fastboot flash recovery recovery.img
fastboot flasht system system.img
fastboot reboot
and your done.
or go use rsd light and remove all of the code from the fastboot commands except for the flash system and flash recovery (the code in the xml file).

jayboyyyy said:
its extremely simple in reality. download that fastboot file from that link. put it in a a folder on your c drive (for instance "fastboot") download the FW for your hone. unzip. put the system and recovery img in the fastboot file you created. then open cmd. type "cd c:/fastboot" THEn plug phone into computer, the reboot phone into fastboot mode with power button and volume down button held for like 3 secs. then run commands in fastboot, fastboot flash recovery recovery.img
fastboot flasht system system.img
fastboot reboot
and your done.
or go use rsd light and remove all of the code from the fastboot commands except for the flash system and flash recovery (the code in the xml file).
Click to expand...
Click to collapse
ah thank you!! that was enough of a refresher to get me going! thanks a lot!

yamaha83 said:
ah thank you!! that was enough of a refresher to get me going! thanks a lot!
Click to expand...
Click to collapse
np. i had to go refresh on my fastboot stuff when i first got the phone because i hadn't touched phone stuff for over a year.

[Q] Stuck in Boot Cycle With Other Problems

Hi All,
First off please forgive how much of a low level noob I am am at this. I didn't create a backup unfortunately. Now we can get to the good stuff. I have unlocked, s-off, and rooted my phone. Loaded a great GPE rom on there and it was working perfectly fine. While looking for a SU for the Rom so that I could delete some wifi bs I found a the HD rom on this site that I would rather use. Soooo I rooted the rom and used cwm to load up the HD 6.1 rom. After the install, when rebooting, it asked me if I wanted to fix the SU permissions and i clicked yes. Now it is stuck in a boot cycle. When I enter fastboot I can enter commands (no adb detection) I can even flash a different recovery on there and the corresponding logo will flash for a second at the end of each boot cycle. Trying to launch reboot or factory reset will put me into another boot cycle. I have tried using fastboot to load directly into recovery but that freezes the phone 2/3 times. Any help would be greatly appreciated so that I can just go back to the GPE rom i was using and stop screwing around with my phone.

XaBuddy said:
Hi All,
First off please forgive how much of a low level noob I am am at this. I didn't create a backup unfortunately. Now we can get to the good stuff. I have unlocked, s-off, and rooted my phone. Loaded a great GPE rom on there and it was working perfectly fine. While looking for a SU for the Rom so that I could delete some wifi bs I found a the HD rom on this site that I would rather use. Soooo I rooted the rom and used cwm to load up the HD 6.1 rom. After the install, when rebooting, it asked me if I wanted to fix the SU permissions and i clicked yes. Now it is stuck in a boot cycle. When I enter fastboot I can enter commands (no adb detection) I can even flash a different recovery on there and the corresponding logo will flash for a second at the end of each boot cycle. Trying to launch reboot or factory reset will put me into another boot cycle. I have tried using fastboot to load directly into recovery but that freezes the phone 2/3 times. Any help would be greatly appreciated so that I can just go back to the GPE rom i was using and stop screwing around with my phone.
Click to expand...
Click to collapse
fastboot erase cache
then flash the recovery again (twrp 2.6.3.3 suggested)
then from recovery wipe and adb push or sideload the rom

I was able to get twrp to work by flashing it again, probably the 7th time, and erased the cache. Now I don't think i want to load the same rom that started this but to go back to the GPE version that I had. Is there a way to get this on the internal sd card through fastboot?

XaBuddy said:
I was able to get twrp to work by flashing it again, probably the 7th time, and erased the cache. Now I don't think i want to load the same rom that started this but to go back to the GPE version that I had. Is there a way to get this on the internal sd card through fastboot?
Click to expand...
Click to collapse
Your options are:
1) adb push
2) sideload from TWRP
3) OTG cable from TWRP
Lots of threads for each of these available in Google

mb_guy said:
Your options are:
1) adb push
2) sideload from TWRP
3) OTG cable from TWRP
Lots of threads for each of these available in Google
Click to expand...
Click to collapse
I was ablt to get adb to recognize the phone however it lists it as a host. I go into the twrp and do the sideload but it opens up the debug message. adb sideload os.zip is the command I'm using as I renamed the file to os.zip so i don't have to type so much. I tried the adb push but it says error:Closed.

mb_guy said:
Your options are:
1) adb push
2) sideload from TWRP
3) OTG cable from TWRP
Lots of threads for each of these available in Google
Click to expand...
Click to collapse
so adb push finally did something but not quite what I wanted this is the message I got
failed to copy '/Users/robertlitz/Downloads/Archive/os.zip' to '/data/media/0/': Is a directory

XaBuddy said:
so adb push finally did something but not quite what I wanted this is the message I got
failed to copy '/Users/robertlitz/Downloads/Archive/os.zip' to '/data/media/0/': Is a directory
Click to expand...
Click to collapse
Try this instead
adb push os.zip /sdcard/os.zip

mb_guy said:
Try this instead
adb push os.zip /sdcard/os.zip
Click to expand...
Click to collapse
It worked!! Thank you so much. I had tried adb push os.zip /sdcard/ a while ago but it didn't take. by typing the zip name after sdcard i assume that "gives" the file an exact location to be placed?

Problem installing Clockworkmod

hi guys! I'm new at this forum, so if i'm doing something wrong about rules and regulation, even if i've read them, correct me please! However, i just bough an At&T Atrix HD with stock 4.1.1 and i wanted to install a CM11; i obtained root privileges and unlocked the bootloader, and when i try to flash the clockwork recovery, apparently everything goes fine in fact i get no errors, but when i turn off the device and try to reboot in recovery it displays the "dead" droid with a red explanation mark. I've read in the cyanogen wiki that some firmwares during the reboot overwrite the custom recovery, is this the case? Which is the command or the procedure to reboot the cell in recovery then?
PS: I flash it through the command line by the PC, i got OSx and i tried with the clockwork posted in cyanogen wiki and the one posted here http://forum.xda-developers.com/showthread.php?t=2421418

Hi, first of all, did you installed the recovery with: fastboot flash recovery recovery.img right??
If you did so, you just need to turn off your phone, hold volume up button and power button and wait until it enters to recovery mode. From there you can flash a new ROM if you have it on your SD card or internal storage.

sliker90 said:
hi guys! I'm new at this forum, so if i'm doing something wrong about rules and regulation, even if i've read them, correct me please! However, i just bough an At&T Atrix HD with stock 4.1.1 and i wanted to install a CM11; i obtained root privileges and unlocked the bootloader, and when i try to flash the clockwork recovery, apparently everything goes fine in fact i get no errors, but when i turn off the device and try to reboot in recovery it displays the "dead" droid with a red explanation mark. I've read in the cyanogen wiki that some firmwares during the reboot overwrite the custom recovery, is this the case? Which is the command or the procedure to reboot the cell in recovery then?
PS: I flash it through the command line by the PC, i got OSx and i tried with the clockwork posted in cyanogen wiki and the one posted here http://forum.xda-developers.com/showthread.php?t=2421418
Click to expand...
Click to collapse
1. You're rooted so go to /system/etc and rename "install-recovery.sh" to "install-recovery.sh.bak"
2. Use Myth Tools to flash recovery (CWM or PhizTouch is included in the tool)
3. Check and Test

thanks to both of you guys!! i've solved with the solution in the second post, just deleting the "install-recovery.sh" script, i was going crazy!! i hope this post will help someone else!
PS: i don't understand why they do not put these solutions in the first posts in important threads like that one i've linked....

devilsking said:
1. You're rooted so go to /system/etc and rename "install-recovery.sh" to "install-recovery.sh.bak"
2. Use Myth Tools to flash recovery (CWM or PhizTouch is included in the tool)
3. Check and Test
Click to expand...
Click to collapse
I thought mythtools removed the .sh file by itself?

jaweinre said:
I thought mythtools removed the .sh file by itself?
Click to expand...
Click to collapse
Nope. You need to do it manually.
I tried to put that function into Myth Tools but it's impossible to do it via adb commands if the kernel is not enabled "insecure".
That's why I put a guide line in Myth Tools to remind user rename that file manually before flashing recovery.

devilsking said:
Nope. You need to do it manually.
I tried to put that function into Myth Tools but it's impossible to do it via adb commands if the kernel is not enabled "insecure".
That's why I put a guide line in Myth Tools to remind user rename that file manually before flashing recovery.
Click to expand...
Click to collapse
Not necessarily. You don't HAVE to rename that file before flashing. The newer CWM's detect that file and will fix it for you. All you gotta do is enter recovery and exit it through the menu, it'll prompt about the file, and say yes to it. Problem solved. It's what I do along with flashing a root zip with every stock flash I do; haven't had a problem yet.
"Enter and exit CWM" is a lot easier to describe than renaming or deleting a file on the /system partition...less error prone too.

skeevydude said:
Not necessarily. You don't HAVE to rename that file before flashing. The newer CWM's detect that file and will fix it for you. All you gotta do is enter recovery and exit it through the menu, it'll prompt about the file, and say yes to it. Problem solved. It's what I do along with flashing a root zip with every stock flash I do; haven't had a problem yet.
"Enter and exit CWM" is a lot easier to describe than renaming or deleting a file on the /system partition...less error prone too.
Click to expand...
Click to collapse
We are 2, never had problems