Related
First things first, if you flashed a previous version of Clockwork Recovery using Odin, FLASH BACK TO A STOCK KERNEL. (There's another link in the forum to do this, I can't find it at the moment)
This recovery is *very* safe to use. It does NOT flash your kernel; it is a completely uninvasive recovery method.
How it works: The recovery is packaged as an update.zip that you run from STOCK recovery. The update.zip unpacks Clockwork Recovery onto the ramdisk and restarts recovery. When you reboot, it reverts back to the original, unmodified, stock recovery. So, you will need to keep the recovery on the root of your SD card as an update.zip, and apply the zip every time you want to start Clockwork.
HOWEVER, if you use ROM Manager, all of the recovery installation and management are done for you!
Installation instructions:
Download ROM Manager from the Market.
Flash Recovery.
Choose Galaxy S i9000 as your phone.
Accept the Superuser prompt.
Use ROM Manager to create a Backup.
On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
Watch the backup go!
That's it! This is completely painless and safe! There is no need for Odin anymore to replace the recovery or flash updates!
If you appreciate my work, please buy the Premium version of ROM Manager!
If you can't seem to get ROM Manager off the market, you can get it from my homepage:
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html
Just installed! Working great!
Installed with ROM manager. Works like a charm! Thanx alot Koush!
works fine
works like a charm
Installed, everything working without problems.
To install roms with clockwork we need roms in *.zip format? Where to get them?
Sent from my GT-I9000 using Tapatalk
Just got my phone
will try it after charging ]
YOU ARE THE MAN
thank you and thanks all Xda devs and members
hmm ... I know this might sound stupid but, acually GSG is my first android phone, though I know how to flash roms with odin and how to apply update.zip and all that but what is the difference between this and ClockworkMod Recovery ?? and does it use the same components as odin ? (I mean CODE, CSC, MODEM and Pit) ?
Stickied. Closing the other one. Not sure why you would start a new thread instead of modifying the old one though...
Thanks Koush your the man. Coming from a htc magic I hate this odin bull
Hmm... did every step and in the first reboot, after using rom manager to create a backup, it was supposed to go to the cloclworkmod recovery screen as mentioned, but instead it goes to the regular recovery screen.
Bug? I'm using the JM1 FW
EDIT: After rebooting my phone and trying to open ROM Manager again, I have some sort of "Recovery Failure" screen with 3 options:
- Recovery mode is broken.
- ROM Manager doesn't reboot.
- Other.
?
Arkymedes said:
Hmm... did every step and in the first reboot, after using rom manager to create a backup, it was supposed to go to the cloclworkmod recovery screen as mentioned, but instead it goes to the regular recovery screen.
Bug? I'm using the JM1 FW
Click to expand...
Click to collapse
Do you already have an update.zip on your internal sdcard? If yes, rename it, and then should boot just fine!
kalpik said:
Do you already have an update.zip on your internal sdcard? If yes, rename it, and then should boot just fine!
Click to expand...
Click to collapse
Ahhh... I guess I'm not very used to this "Internal SD Card" thing... there was the update.zip I used to root the phone there and I only checked my regular External SD.
Everything is fine now, sorry for bothering.
Arkymedes said:
Hmm... did every step and in the first reboot, after using rom manager to create a backup, it was supposed to go to the cloclworkmod recovery screen as mentioned, but instead it goes to the regular recovery screen.
Bug? I'm using the JM1 FW
EDIT: After rebooting my phone and trying to open ROM Manager again, I have some sort of "Recovery Failure" screen with 3 options:
- Recovery mode is broken.
- ROM Manager doesn't reboot.
- Other.
?
Click to expand...
Click to collapse
I had the same issue. Must have been the update.zip, but I didnt remove it, just pressed the other option, went into manual recovery mode, rebooted went into rom manager and backed up my files. Worked a charm
Does this mean there will be no more work on a permanent recovery solution?
I have the Korean version M110S - and it does not have the standard recovery (it is crippled - no apply:update.zip). Is there and abd command to "apply update.zip" ?
May I ask if this work for me using mimocan ext4 fix on the backup/restore?
This may sound stupid, but I'm kinda new to Android modding (SGS is my first droid, moving here from WiMo on SE-X1) and.... What is Clockwork?
So if I ever needed to send this phone in for warranty purposes, I could just flash the backup of my stock ROM in and I should be good to go?
does this method works for captivate and vibrant???
edit: just install/ captivate and vibrant option available.
Rithina said:
May I ask if this work for me using mimocan ext4 fix on the backup/restore?
Click to expand...
Click to collapse
Worked for me with mimocan ext4 fix
Hi
I root my HTC EVO about 2 weeks ago. When Unrevok ask me to install the custom recovery I answer yes (CWM V4.0.1.4). Everything went great. After that I download the Rom Manager App to manage my backups.
On the Rom Manager App when I press on "Backup Current Rom" I get this prompt "You must have ClockworkMod Recovery installed before continuing!. Install the recovery though Rom Manager First".
It is safe to install the ClockworkMod Recovery even do I have CWM V4.0.1.4 ?
Thanks in advance.
Yes, rom manager will just re-flash it to the latest version.
Do yourself a favor and get Amon Ra and dump ROM Manager
HipKat said:
Do yourself a favor and get Amon Ra and dump ROM Manager
Click to expand...
Click to collapse
+1
10chara
Active_Matrix said:
+1
10chara
Click to expand...
Click to collapse
+2
10char
Sent From My Pocket
Amon-Ra vs. CWM
Is it really that much better? I kinda like the ROM manager that came with my CM7 Rom, and I know that prefers CWM.
Or do yourself a bigger favor and install twrp.
Journeyman83 said:
Is it really that much better? I kinda like the ROM manager that came with my CM7 Rom, and I know that prefers CWM.
Click to expand...
Click to collapse
ROM Manager has a history of not being as efficient as it promises and making mistakes in backups. It also will not do a correct wipe of your system before flashing a new ROM, which creates problems, potentially, with FC's, etc...
atyoung said:
Or do yourself a bigger favor and install twrp.
Click to expand...
Click to collapse
TWRP is not there yet. They lack the wipe boot feature which will screw up alot of ROM installs. Ra Recovery is still the way to go, plus all ROMS that have issues flashing in CWM have issues in TWRP. Once TeamWin fixes the major issues with TWRP then it will be the recovery to use. Presently it is still flawed.
If I have ROM manager can I just download and flash RA Recovery over that without having to flash the PC36IMG.zip? I'm new to this so I just want to make sure I'm doing this right.
LandOfLinkin said:
If I have ROM manager can I just download and flash RA Recovery over that without having to flash the PC36IMG.zip? I'm new to this so I just want to make sure I'm doing this right.
Click to expand...
Click to collapse
If you have the android sdk installed on your system just boot to your bootloader and select fastboot. Then place the file in .img format in your android-sdk-windows\tools directory then rename the file to something shorter, I usually go with amonra.img. then navigate to that directory with cmd. Then type fastboot flash recover amonra.img this will flash the new recovery. However if you don't have the sdk installed then you will need the pc36img.zip format place it on the root if your sdcard and reboot the phone while holding power+vol up. The bootloader should detect the file and ask if you wish to apply the update. Press vol up to accept the update, and it will flash the new recovery. Now once you do this you will need to make all new backups because any backup made with CWM will not work with ra recovery.
Sent from my PC36100 using Tapatalk
Thanks for the help. I actually downloaded Android terminal emulator and flashed it from the SD card. You guys are just too darn helpful!
Sent from my PC36100 using XDA Premium App
Thanks guys for the help.
Clockwork android app + link2sd + googleplay failure
I buyed the app but cant install the 42kb premium key :-/
please help
I am having an issue with cwm. when I go into rom manager i was able to succesfully flash it to my phone. Now when i reboot into recovery I get the android guy with a red exclamation point. sometimes I can get in but I cant reboot my phone from the menu and have to do a battery pull. I am able to flash .zip's and update the bootanimation for example if i get in. When I reboot from rom manager I get some error message that is stopped working before it reboots and again sometimes it works sometimes it doesnt.
should I push the recovery through the sdk again?
Yes, you should. I read that sometimes CWM won't stick if applied through ROM Manager.
There is a file on the nexus s and i believe the Gnex as well that will rewrite the stock recovery after a reboot. unless you change this file you have to flash the recovery every time you want to go into it. use a file manager and search for install-recovery i believe its install-recovery.sh and rename it to install-recovery.sh.bak ( or wtv ) may solve it.
I just did a quick search in root explorer and found a file called "install-recovery.sh"
it should be in the root folder/etc/install-recovery.sh
and i just tried going into CWM and got the same thing as the OP. I am going to rename the "Install-recovery.sh" file like Goat_For_sale suggested, then reinstall CWM and see what happens after a few reboots.
Standby.
*final* edit
So here is what I did.
1.renamed "install-recovery.sh" to "install-recovery.sh.bak" (located in the "etc" folder of the root) I used root explorer. Make sure you mount as writeable or else you cant change the file name.
2. rebooted phone as normal. went into Rom Manager and reinstalled CWM.
3. turned phone off, and booted into recovery and boom! CWM came up nicely.
Glad I found this thread, or I would have been annoyed when I go to flash a rom tonight and couldnt figure out why I wasnt able to get into CWM.
Good luck OP.
I hope you were able to resolve this issue. I was having the exact same issue and i followed the instructions in this thread and it corrected it and i havent had a problem since.
http://forum.xda-developers.com/showthread.php?t=1392336
Now cwm seems to be working but when I hit to boot into recovery from rom manger it says that something has stopped working unexpectally but it seems to boot into recovery just fine.
If you follow the steps on the link that i posted, and make sure that you follow the step of deleting the file with Root Manager once you have moutned as RW then that should get you working. If you are still having issues with I would be happy to walk you through the process tonight over google talk once i get off of work.
Thanks Angelino I will try that today. I just havent deleted that file yet. Now since im rooted and already flashed cwm, i should just go into root manager delete the file and then do the fastboot and flash the recovery again?
TSanborn79 said:
Thanks Angelino I will try that today. I just havent deleted that file yet. Now since im rooted and already flashed cwm, i should just go into root manager delete the file and then do the fastboot and flash the recovery again?
Click to expand...
Click to collapse
dude try my method, it was super easy, and doesnt require deleting anything, just renaming that file.
threepio said:
dude try my method, it was super easy, and doesnt require deleting anything, just renaming that file.
Click to expand...
Click to collapse
I did try your method but it only partially works. I still get an error when trying to boot from rom manager.
It actually says superuser has stop working. Finally was able to read it.
I am having issues with my gnex and recovery. I am rooted and can run clockwork when I boot from the app. However when I run root explorer i can find any of the recovery files to delete or rename. They arent showing up in system or etc but when i restart my phone stock recovery is still there... ideas?
TSanborn79 said:
I did try your method but it only partially works. I still get an error when trying to boot from rom manager.
Click to expand...
Click to collapse
wierd. I havent had a problem yet. Hope u get it figured out.
ok you need to have clockworkmod installed...
Code:
fastboot flash recovery recovery.img
(insecure boot.img)
unzip boot.img.zip, boot to bootloader and
Code:
fastboot flash boot boot.img
or flash JRN84D-insecure-boot.zip from recovery
-put the CWM-SuperSU-v0.92-mod.zip on your sd and flash
done. :good:
if you have problems...
flash Koush's Jellybean repack (IMM76I OR IMM30D) http://d-h.st/Gkh
If recovery isn't sticking for you, delete recovery-from-boot.p in /system
I can do this for the other superuser as well...this is chainfire's super su
Thanks. May I clarify if I have to do both to get root or either one?
mcdull said:
Thanks. May I clarify if I have to do both to get root or either one?
Click to expand...
Click to collapse
the boot image is insecure...not necessarily needed
Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.
mcdull said:
Oic.. thanks alot.
Is there any chance to pack the insecure kernel into cwm package as well?
I have no access to computer that allow me to apply fastboot flash. I am sure a lot of ppl will be in the same situation. Thanks alot.
Click to expand...
Click to collapse
sure, give me a minute
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
bootloader mode -> reflash clockwork recovery using fastboot.
pablo1215 said:
Okay I installed the jellybean rom from rom manager but I lost clockwork recovery, anyone got any suggestions?
Click to expand...
Click to collapse
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img
Thanks guys appreciate the tip.
not working
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.
krishmasand said:
Just flashed the two .zips. SuperSU is installed, but it says that the binary needs to be updated. When it tries to update it fails, and no root apps work.
Click to expand...
Click to collapse
reboot, then open supersu and then update
Worked like a charm, I've got clockwork back after a little adb action and now I'm restoring some apps with titanium. Can't wait to see the development on this. Just think I almost sold this phone and bought a Galaxy S3 today, may wait a week or so now.
Thanks guys you are amazing!!!
Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update
tramane said:
Flashed both zips in cwm
Super su app is there but needs to update binary
It fails on update
Click to expand...
Click to collapse
ok your the second guy...first hasn't responded back. did you reboot and try again?
which "jellybean" version are you on? koush's on rom manager seems to be the best (no wifi issues for one)
ogdobber said:
fastboot a new one in...new one will stick
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.
other superuser
still doesn't work, do you think you can try the other SuperUser app? D:
Enhanced said:
Is there a reason why my CWM won't stick? I fastboot a new one in and right after, I can access CWM from the bootloader menu if I don't boot into the OS yet. However, once I do boot into the OS and use ADB to reboot into recovery, it goes back to the Android with the red triangle.
What am I doing wrong? I'm usually pretty good with this stuff.
Click to expand...
Click to collapse
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM
[please delete]
IINexusII said:
You'll need to delete that recovery from boot.p file otherwise it'll keep deleting CWM
Click to expand...
Click to collapse
I knew common sense told me that I would need to delete the /system/recovery-from-boot.p file, but it wasn't posted here so I didn't bother.
Thanks.
Here is the official ClockworkMod Recovery 6.0.4.7 non-touch images and touch images for the Nexus 10 enjoy :cyclops:!
Credit goes to Koush for releasing the official ClockworkMod Recovery images
These are safe to flash via fastboot.
Non-Touch
http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.4.7-manta.img
Touch
http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.7-manta.img
These can be flashed via fastboot using the following commands:
Code:
fastboot flash recovery /path/to/.img
fastboot reboot
Once again enjoy :victory:!
Note: To get the recovery to stick on reboot when Clockworkmod Recovery asks you if you want rename flash-recovery.sh or similar say "Yes", this will allow you to keep Clockworkmod Recovery installed permanently (Unless you flash a different recovery image) when you reboot your phone.
These reboot randomly as well. I've been trying to get TWRP to work, but TWRP is doing the same thing. Nothing in dmesg or last_kmsg to help either. :/
Also sdcard mount does not work nor anything reading from sdcard... only thing working is adb sideload.
Dees_Troy said:
These reboot randomly as well. I've been trying to get TWRP to work, but TWRP is doing the same thing. Nothing in dmesg or last_kmsg to help either. :/
Click to expand...
Click to collapse
zedomax said:
Also sdcard mount does not work nor anything reading from sdcard... only thing working is adb sideload.
Click to expand...
Click to collapse
Ok that is really bizare, both CWMR and TWRP are not working right and encountering similar issues regarding random reboots and mount issues. Whats odd is other people are experiencing random reboots during regular use even when not in recovery. I'm starting to believe that something Google might have to put out at fix for software wise may be needed.
So I take it no more "booting" the temporary ones posted before for the Nexus 4/Nexus 10? We can go ahead and "flash" these ones right?
zedomax said:
Also sdcard mount does not work nor anything reading from sdcard... only thing working is adb sideload.
Click to expand...
Click to collapse
i cant even get the sideload to work to get SU installed. Its driving me crazy. I keep trying it over and over again with the same result. As soon as i go over to recovery it unmounts from the computer then the sideload command fails due to computer losing connection with it. "Device not found"
Tried both CWM versions now .5 and .6
Not my first time around the block with rooting :-/
Used heimdall suite to flash my GS2.. any way to get it to push the .zip file for SU over to the phone? Push the recovery img then push the .zip maybe?
So I never even ended up trying to sideload anything, I just flashed the official recovery, then went immediately to recovery from fastboot, and once there I just flashed the SU zip and now I have root. Of course, CWMR doesn't work (i.e. if I use Quick Boot to boot to recovery it just takes me to the stock recovery, and if I try to go to recovery from fastboot manually, I just get the dead android w/red triangle).
Jayrod1980 said:
Finally got it... helped to just get the supersu on the root of the device. I used the fastboot commands to get to cwm touch and then I quickly installed it through the interface. I couldn't sideload. The device won't recognize adb when I'm in fastboot mode at all. I don't know what I was doing wrong in that instance, but using cwm briefly let me install supersu. Thanks for your help! Surprising this is so buggy considering it's a nexus... and it's not the nexus that's excluded from AOSP. Go figure!
Click to expand...
Click to collapse
I had to do it this way in order to get root. Finally.. been working on this for like 5ish hours now.. what a pain. Hopefully there will be an easier route for everyone else and a CWM that does not reboot in 20ish seconds soon. Good luck to everyone that goes this route.. it takes a lot of trial and error
snunez said:
Hopefully there will be an easier route for everyone else and a CWM that does not reboot in 20ish seconds soon.
Click to expand...
Click to collapse
I'm sure there will be, probably by the end of the weekend, if not sooner
I took apart CWM touch 6.0.1.6 and fixed reboot after 20 sec
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
damien667 said:
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
Click to expand...
Click to collapse
Great work! If you could post the unpacked version I'd appreciate it. I was trying to build a fixed version without success and would like to compare.
So,
Am I right in thinking...
cd to the adb tools folder where the sdk is saved.
I need to unlock the boot loader via fastboot oem.
Then copy your file to the same directory on my Mac
Then type in the command line you suggested with the correct filename?
After that I will be rooted
Swype'd at pace from my Galaxy S2
Here's my working tree
The-Kevster said:
Great work! If you could post the unpacked version I'd appreciate it. I was trying to build a fixed version without success and would like to compare.
Click to expand...
Click to collapse
I used this tool to unpack and re-pack the image: https://github.com/huaixzk/unpackbootimg.git
Attached is my current working tree as a tar.gz
Edit: the tool in that git repo is missing a step to gunzip | cpio the ramdisk... I made a shell script to do that for me when unpacking and repacking
Edit2: I added the wrapper scripts I made for posterity
damien667 said:
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
Click to expand...
Click to collapse
Wow! It worked perfectly... You are a genius. No more random reboots in recovery! Thank you. I have one question... Are you able to do the same for TWRP for the Nexus 10, if possible?
Underworld79 said:
Wow! It worked perfectly... You are a genius. No more random reboots in recovery! Thank you. I have one question... Are you able to do the same for TWRP for the Nexus 10, if possible?
Click to expand...
Click to collapse
I could probably do it to TWRP as well (later today, it's sleep time for me)... however, I don't know where the latest nexus 10 recovery image is from them (considering it's not in this forum).
so can I permanently flash this now instead of fastboot?
damien667 said:
I took the stock recovery.img from https://developers.google.com/android/nexus/images#mantarayjop40c, unpacked it, copied over the recovery binary from cwm touch 6.0.1.6 and resource files into the ramdisk... repacked it, and voila... no more reboots!
I'm sure Koush will eventually figure out what's going on with his automatic build system... my manually made recovery seems to work ok.
Please have at it (and feel free to thank me and report bugs), and if you want a tgz of my "unpacked" recovery I'll upload as well. You can also just unpack my uploaded file and see where the differences are yourself.
I've done recovery mods in the past for the G1, G2, and Gnexus when stuff like this happens when a device first comes out and recoveries have bugs in them.
Just "fastboot flash recovery $file.img" to try it out. I've got it running on my nexus 10 already and it hasn't rebooted (I succesfully installed CWM-SuperSU-v0.98.zip from http://forum.xda-developers.com/showthread.php?t=1538053 )
Click to expand...
Click to collapse
Well I just flashed your version of the recovery, and after doing "fastboot-mac reboot" and rebooting, I tried rebooting to recovery via adb, and unfortunately it brought me back to the dead android red triangle screen. In fact, I can't even get to CWMR at all. Anyone else??
And to be clear, I have successfully rooted, so at this point I'm just trying to get a functioning version of CWMR on the tablet, if possible.
Did you try holding power and pressing Vol+ when booting recovery? That's how you enter stock recovery.
Randomwalker said:
Did you try holding power and pressing Vol+ when booting recovery? That's how you enter stock recovery.
Click to expand...
Click to collapse
Yeah I know that, but I'm not trying to enter stock recovery, I'm trying to enter the custom recovery (which is the supposed "stable" one by damien) which I've installed. And it only let me access CWMR immediately after flashing it. However anytime afterwards I simply cannot access it again:
1) tried "adb reboot recovery" and it brings me to the dead android w/red triangle
2) tried getting to recovery via the Quick Boot app, and the same thing happens
3) tried getting to recovery via the normal holding buttons down to get to bootloader, then going to recovery manually from there, and a no-go as well.
In the end, all that happens is I have to toggle the buttons once I get to the dead android screen, and the menu for the stock recovery appears, which allows me to reboot. But as for CWMR, it is nowhere to be found. WTF.
Did you reboot after installing CWM? If so, did you remove install.sh, that will restore the stock recovery?