Database Users

How to Flash Clockworkmod Recovery 3.0 easily from your phone

I found a really easy way to flash the new recovery. My fastboot didnt seem to have an option for a terminal so I thought of this genius yet n00b way. Here are the steps.
Steps:
1. Install clockworkmod from market.
2. Flash Clockworkmod recovery from Rom Manager.
3. Navigate to clockworkmod/download/koush.tandtgaming.com/recoveries (or where ever your recovery was downloaded to. This can be done in File Manager, Astro, or Androzip.
4. Mine was "recovery-clockwork-2.5.1.3-vision.img". Rename it to "recovery-clockwork-2.5.1.3-visionXXX.img" or something obviously different.
5. Download clockworkmod 3.0 from hereish:
http://forum.xda-developers.com/showthread.php?t=893933
6. Move your recovery.img to clockworkmod/download/koush.tandtgaming.com/recoveries and name it recovery-clockwork-2.5.1.3-vision.img
7. Go into ROM Manager and Flash Clockworkmod recovery, it will say its still 2.5.1.3 when your done. Reboot into recovery and you'll be welcomed by a new orange 3.0
More than likely i could have done it much easier but it just kinda clicked and i didn't wanna bother with fastboot as it feels clunky on the G2.

there's nothing noob about it. that is a bonafide hack. nice!

I tried something like that but I didnt rename it correctly. So nice to know though. Good work.
Sent from my T-Mobile G2 using XDA App

Can u put that in a zip for lazy people like me
Sent from my T-Mobile G2 using XDA App

charlieton said:
there's nothing noob about it. that is a bonafide hack. nice!
Click to expand...
Click to collapse
How is that a hack? LOL

not really a "hack" per se but it tricks ROM manager into flashing a newer clockwork while still thinking it is the same old one. i thought about doing this the other day but never got around to it so great job on this

wineguy13 said:
Can u put that in a zip for lazy people like me
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
You need this is a zip to simply move a file to your SD card? Wow, that IS lazy. lol

I followed the thread but the download take u to a bunch of jumbled code.. is that right?
Sent from my T-Mobile G2 using XDA App

Typo
shadymnms said:
4. Mine was "recovery-cockwork-2.5.1.3-vision.img". Rename it to "recovery-cockwork-2.5.1.3-visionXXX.img" or something obviously different.
Click to expand...
Click to collapse
Nicely done, flashed it via your method.
You may want to correct the typo you have in there as I first tried to copy and paste your file names. It's clockwork, not cockwork.

shadymnms said:
More than likely i could have done it much easier but it just kinda clicked and i didn't wanna bother with fastboot as it feels clunky on the G2.
Click to expand...
Click to collapse
How does it feel clunky? fastboot flash recovery recovery.img is a lot easier than this method.

rp1783 said:
How does it feel clunky? fastboot flash recovery recovery.img is a lot easier than this method.
Click to expand...
Click to collapse
For some reason flashing recovery from fastboot hangs everytime on my phone. This way is good but I did it in terminal. I actually had to flash a cyanogen rom to get the fastboot command, this method would have saved that step.
Sent from my HTC Vision using XDA App

overpower said:
Nicely done, flashed it via your method.
You may want to correct the typo you have in there as I first tried to copy and paste your file names. It's clockwork, not cockwork.
Click to expand...
Click to collapse
Fixed. Thanks lol. I was doing in between flashing villian and was going back and forth. Ahhh... "cockwork", really? Musta slept in too late too.
Sent from my HTC Vision using XDA App

And the downgrade?

fastboot is a lot easier than this IMHO !
You will have fastboot if you have got adb setup on your PC. See the adb guide in this forum for how to setup adb (and fastboot too). It's worth going to the effort, because fastboot will help you with various things in the future. Also you will need the eng hboot.

thank you so much! man now this i can do. i was trying to adb or find terminal in my fastboot.

I'm just starting to install custom ROM tho my DZ, but is this means that ROM Manager will never integrate the new Clockworkmod Recovery?

shadymnms said:
I found a really easy way to flash the new recovery. My fastboot didnt seem to have an option for a terminal so I thought of this genius yet n00b way. Here are the steps.
Steps:
1. Install clockworkmod from market.
2. Flash Clockworkmod recovery from Rom Manager.
3. Navigate to clockworkmod/download/koush.tandtgaming.com/recoveries (or where ever your recovery was downloaded to. This can be done in File Manager, Astro, or Androzip.
4. Mine was "recovery-clockwork-2.5.1.3-vision.img". Rename it to "recovery-clockwork-2.5.1.3-visionXXX.img" or something obviously different.
5. Download clockworkmod 3.0 from hereish:
http://forum.xda-developers.com/showthread.php?t=893933
6. Move your recovery.img to clockworkmod/download/koush.tandtgaming.com/recoveries and name it recovery-clockwork-2.5.1.3-vision.img
7. Go into ROM Manager and Flash Clockworkmod recovery, it will say its still 2.5.1.3 when your done. Reboot into recovery and you'll be welcomed by a new orange 3.0
More than likely i could have done it much easier but it just kinda clicked and i didn't wanna bother with fastboot as it feels clunky on the G2.
Click to expand...
Click to collapse
Thank you kind sir.

Thanks for this simple guide! Before I move forward though, a couple of questions - I need this recovery to flash gingervillain or the CM7 that's being worked on, right? But if I want to revert back to my nandroid backup of cm6.1.1, will I have to flash the old recovery before doing so? Cheers
Sent from my HTC Vision using XDA App

steviewevie said:
fastboot is a lot easier than this IMHO !
You will have fastboot if you have got adb setup on your PC. See the adb guide in this forum for how to setup adb (and fastboot too). It's worth going to the effort, because fastboot will help you with various things in the future. Also you will need the eng hboot.
Click to expand...
Click to collapse
now cmon stevie, i agree its good to have adb and proper sdk w\ drivers installed. But for the super ober noob thats wants shiny pretty new cw3 for whatever reason be it cm7 or just because, even trying to teach the super ober how to cmd and cd to the sdk is a larger challenge than this. Im just saying your a well respected source of info on xda to a lot of super obers and to say this is easier on the big picture, well thats just crazy talk. This is pretty easy for just about anyone.

kalipedia said:
Thanks for this simple guide! Before I move forward though, a couple of questions - I need this recovery to flash gingervillain or the CM7 that's being worked on, right? But if I want to revert back to my nandroid backup of cm6.1.1, will I have to flash the old recovery before doing so? Cheers
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
from what i've read this seems to be the case. i think i'll wait for a stable cm7 release before updating to 3.0

Rooting a 4g

OK so I'm commingle from the epic and I want to root for titanium but I've seen there is different varrent and different ways to root what meatod will work and I have looked and searched before I get the plaza use search I just don't want to brick using wrong root meathod thank you in advance for who ever is willing to help
Sent from my Nexus S 4G using XDA App

+1
Sent from my Nexus S 4G using XDA App

Do you have SDK and working fastboot? That is step one.

Yep
Sent from my Nexus S 4G using XDA App

*note* i did not develop this method entirely i scrapped it together from multiple posts found here on xda. I give credit to those who did the work first. it worked fine for me hopefully it works for you too.
download sdk tools and install
download fastboot drivers and install
both found here
after that, download clockwork recovery
also download superuser files you want eclair/froyo su it works for gingerbread too.
open command prompt and enter the following
Code:
fastboot devices
if it doesn't return your phone in the following line double check that your fastboot drivers are properly installed.
if it does enter the following
Code:
fastboot oem unlock
follow the onscreen prompt on your phone. volume up to "yes" and hit power to confirm
Your phone is now unlocked. next step installing a recovery.
navigate to the folder where the clockwork recovery image is located.
Code:
cd C:\users\#username#\downloads
or wherever the file is on your pc.
then enter the following
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
you now have a proper recovery installed on your phone you may now vol dn to recovery and hit power to confirm
VERY IMPORTANT
in recovery vol dn to "backup and restore" power to confirm
select Backup and hit power again.
you just created a nandroid backup of your phone if you ever mess it up you can restore it back to when it was stock and problem free
In recovery vol dn to "mounts and storage" power to confirm
then choose "Mount USB storage"
copy the SU zip to the root of your phone's storage
then "Unmount"
then "+++++Go Back+++++"
then "install zip from sdcard"
then "choose zip from sdcard"
Choose su-2.3.6.1-ef-signed.zip
then select "Yes - Install su-2.3.6.1-ef-signed.zip"
Reboot your phone and you should now have a stock rooted phone.

Ty Joe I will do this as soon as I get home
Sent from my Nexus S 4G using XDA App

tildog said:
No I have not but did not want to start on anything till I confirmed that the method will not brick I will dl. Sdk. And drivers tonight at work ATM
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
It's really *really* hard (if not damn near impossible) to actually brick a nexus-s. Just so ya know ;D

netarchy said:
It's really *really* hard (if not damn near impossible) to actually brick a nexus-s. Just so ya know ;D
Click to expand...
Click to collapse
That is good to know I had a few scares on my epic I know how to do stuff but on the epic was always a onclick meathod so this looks a little overwhelming in comparison but easyenof otherwise
Sent from my Nexus S 4G using XDA App

tildog said:
That is good to know I had a few scares on my epic I know how to do stuff but on the epic was always a onclick meathod so this looks a little overwhelming in comparison but easyenof otherwise
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Just remember to make a nandroid backup in clockwork after you're done rooting, so you always have a working setup to fall back on if something should go wrong in the future

tildog said:
That is good to know I had a few scares on my epic I know how to do stuff but on the epic was always a onclick meathod so this looks a little overwhelming in comparison but easyenof otherwise
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
i just came from the evo and rooted that phone way before any one click roots where out. Trust me the nexus s is 100 times easier to root than any other phone it's actually pretty quick and easy, i just went into great detail so anyone could be able to follow it hopefully. I think i have seen some 1 click roots for the ns but i never looked into them once i saw how relatively pain free it is to do this way.
i remember having to copy and paste adb commands and spamming them while my phone rebooted. and hopefully... hopefully it would unlock the evo.

just out of curiousity as i wont know until tomorrow, but does gingerbreak work? if so just using the sdk and using adb to push it seems like it would be faster..

shabbypenguin said:
just out of curiousity as i wont know until tomorrow, but does gingerbreak work? if so just using the sdk and using adb to push it seems like it would be faster..
Click to expand...
Click to collapse
Yes there has been success using that. You could i suppose gain root with gingerbreak and then use that to flash clockwork recovery. You would be rooted and able to flash Roms through clockwork. Bootloader would remain locked.

Thanks all. I'll try this later tonight and report back. I've seen a few root methods around here but wanted to make sure it was no different for the ns4g before I actually got into it.
So to confirm one more time Joe's method he posted here should work for the ns4g as well, right?
Sent from my Nexus S 4G using XDA App

matt2053 said:
Yes there has been success using that. You could i suppose gain root with gingerbreak and then use that to flash clockwork recovery. You would be rooted and able to flash Roms through clockwork. Bootloader would remain locked.
Click to expand...
Click to collapse
Yea but its a quick and easy way to root. Until there is more support for the ns4g no real reason to unlock

shabbypenguin said:
Yea but its a quick and easy way to root. Until there is more support for the ns4g no real reason to unlock
Click to expand...
Click to collapse
Yeah for sure, I'm not saying its good or bad. Just pointing out the difference in that method. Some people prefer to keep the bootloader locked anyway. Unlocking it is always one command line away.
Sent from my Nexus S using XDA App

shabbypenguin said:
Yea but its a quick and easy way to root. Until there is more support for the ns4g no real reason to unlock
Click to expand...
Click to collapse
Not totally sure regarding roms, but my latest kernel builds *should* be compatible ;D
(Disclaimer: always nandroid before flashing customs!!)

netarchy said:
Not totally sure regarding roms, but my latest kernel builds *should* be compatible ;D
(Disclaimer: always nandroid before flashing customs!!)
Click to expand...
Click to collapse
cool thanks for the support man

Running into an issue on ns4g. I can unlock and install Clockwork 3.0.0.5 but when I try to Nand backup it says it can't find cache. I've tried to manually mount it but won't do it there either. Any suggestions?

oubravs2b said:
Running into an issue on ns4g. I can unlock and install Clockwork 3.0.0.5 but when I try to Nand backup it says it can't find cache. I've tried to manually mount it but won't do it there either. Any suggestions?
Click to expand...
Click to collapse
Install clockwork 3.0.2.4
Make sure you've renamed the /system/etc/install-recovery.sh script (if you haven't already) as well so clockwork isn't overwritten by the stock recovery.

netarchy said:
Install clockwork 3.0.2.4
Make sure you've renamed the /system/etc/install-recovery.sh script (if you haven't already) as well so clockwork isn't overwritten by the stock recovery.
Click to expand...
Click to collapse
Good to go I think - thanks netarchy!
So for you all that are trying to follow joe's steps, they are correct except the download linked in his post will give you the 3.0.0.4 version of Clockwork and you need the one referenced by netarchy (3.0.2.4). All worked as planned after that.
Rooted and ready to flash netarchy's kernel on ns4g!

Not New to Android, New to Atrix

I've had an Evo for about 9 months....but....
Work basically just gave me an Atrix and laptop dock to mess with, and even encouraged the "development" side of it (aka root it, without saying root it)
I've done a bit of research, and I have a few questions.
Right away I used the "One Click Root" at the top of this forum.
What I want to know is how to enter Clockword Mod Recovory, which I can on the Evo to backup my phone and flash a rom stored on the SD card.
It doesn't seem to have it unlocked that menu though, as I can't access it by holding those buttons down.
That would make my life alot better, as I can start to experiment for the Roms for this phone (currently running Mik2.3? on the Evo, didn't see a ROM for this phone though )
Anyway, thanks for helping out....I'm excited to learn this phone.
Also, the dock is rather new, any cool tricks I could exploit?

(Have you unlocked the bootloader..?)
Flash romracer's recovery, check in the development forum. Or download Rom Manager and install the recovery from there.

Vangelis13 said:
(Have you unlocked the bootloader..?)
Flash romracer's recovery, check in the development forum. Or download Rom Manager and install the recovery from there.
Click to expand...
Click to collapse
Not really sure how to flash in img file.
I really don't remember doing that on the EVO....I can only really do things once I boot into recovery, which I can't seem to figure out on this Phone

Check the noob guide at the top here, all answers are there. First step is to unlock the bootloader.

Vangelis13 said:
Check the noob guide at the top here, all answers are there. First step is to unlock the bootloader.
Click to expand...
Click to collapse
Got it unlocked...
Anyway, what exactly is Deodex? not sure I see that with the Evo...
Also, whats the hotness in roms....can i simply place in a directery and flash like i can with evo and recovery screen?
Well I thought I flashed CWM but it just shows up a android guy with an !
??

drs6222 said:
Got it unlocked...
Anyway, what exactly is Deodex? not sure I see that with the Evo...
Also, whats the hotness in roms....can i simply place in a directery and flash like i can with evo and recovery screen?
Well I thought I flashed CWM but it just shows up a android guy with an !
??
Click to expand...
Click to collapse
when u first turn on the atrix does it say unlocked in the top left corner if it does download and install ether cwm or rom manager drom market and install the cwm from it then install romracers latest revovery from the dev forums
Sent from my MB860 using xda premium

Romracer said:
The system runs /system/etc/install-recovery.sh on boot with the stock rom. On boot it checks the recovery partition for some update and with CWM installed decides to reflash the stock recovery over it. Rename or delete the file and the CWM should stick.
Click to expand...
Click to collapse
after you delete install-recovery.sh you can flash a recovery and have it stick past reboot.

Alcapone263 said:
after you delete install-recovery.sh you can flash a recovery and have it stick past reboot.
Click to expand...
Click to collapse
He shouldn't have to do that. If it's rooted and has an unlocked bootloader he should just be able to download either rom manager from the market and install the recovery that way or he could flash romracer's recovery via fastboot. That's all I really did when I went through this and it worked just fine for me.
On another note, to the thread poster, definitely read the "stuck" threads at the top of each forum and you'll be able to figure everything out without having to ask questions that are already answered. I went through it all and have gotten to the point where I can do a lot of this stuff on my own so I highly recommend doing so.
Sent from my MB860 using xda premium

GeNiO426 said:
He shouldn't have to do that. If it's rooted and has an unlocked bootloader he should just be able to download either rom manager from the market and install the recovery that way or he could flash romracer's recovery via fastboot. That's all I really did when I went through this and it worked just fine for me.
On another note, to the thread poster, definitely read the "stuck" threads at the top of each forum and you'll be able to figure everything out without having to ask questions that are already answered. I went through it all and have gotten to the point where I can do a lot of this stuff on my own so I highly recommend doing so.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
rooted and unlocked bootloader doesn't matter, if he's on the stock ROM and has that file it runs on boot every time. you can install recovery, but it just won't stick since install-recovery.sh runs at boot every time the file is present.

[Q]Can we use ClockworkMod Recovery instead of TWRP?

Just was wondering. I'm more used to what clockworkmod has so I figured it would be easier to install that instead. But I wanted to make sure it was supported before I went ahead and installed it. Anyone know?

Yes. ClockworkMod works just fine on the Kindle Fiya. there is no looking back now.

androidcues said:
Yes. ClockworkMod works just fine on the Kindle Fiya. there is no looking back now.
Click to expand...
Click to collapse
awesome. so i'm ok with installing it straight from rom manager right?
i'm a little paranoid bc a lot of people seem to be posting about bricking their fires.

Unknown. But if you follow the "bricked fire" threads, you'll see that most people find ways to get them back. So I think a lot of folks are at times stuck, but not truly bricked. I think the most common problem, and the one that bit me too - is being stuck in fastboot and therefore having the device not accessible by adb. And they, like me, panic a bit and think they've bricked it. Granted, I'm sure there are ways of truly bricking it, but as long as you're patient, I think KFU and the fastboot command can get you out of most problems.

gadgetman13 said:
Unknown. But if you follow the "bricked fire" threads, you'll see that most people find ways to get them back. So I think a lot of folks are at times stuck, but not truly bricked. I think the most common problem, and the one that bit me too - is being stuck in fastboot and therefore having the device not accessible by adb. And they, like me, panic a bit and think they've bricked it. Granted, I'm sure there are ways of truly bricking it, but as long as you're patient, I think KFU and the fastboot command can get you out of most problems.
Click to expand...
Click to collapse
thanks man, gonna go ahead and do it in a bit. fingers crossed .

Where do you find the CWM files to download?
Sent from my Kindle Fire using Tapatalk

Bmcd37 said:
Where do you find the CWM files to download?
Sent from my Kindle Fire using Tapatalk
Click to expand...
Click to collapse
it installs when you start up rom manager for the first time
EDIT: Woops, just went to install it and it says it's not officially supported yet. Anyone know where to get it?

Looks like there's more to it. Guess I'm gonna be going by this guide to install early CM9:
http://liliputing.com/2011/12/how-to-install-cyanogenmod-7-on-the-amazon-kindle-fire.html

HeliosAI said:
it installs when you start up rom manager for the first time
EDIT: Woops, just went to install it and it says it's not officially supported yet. Anyone know where to get it?
Click to expand...
Click to collapse
I thought CWM required the use of hardware buttons?

HeliosAI said:
Looks like there's more to it. Guess I'm gonna be going by this guide to install early CM9:
http://liliputing.com/2011/12/how-to-install-cyanogenmod-7-on-the-amazon-kindle-fire.html
Click to expand...
Click to collapse
Go to the development section. It says beta but its solid, I did most of the alpha testing for it and doom lord did the port. Is not officially supported by koush. If you know how to use fastboot, you can't fastboot flash recovery.img if u can't figure it out pm me. I'll get u going.
Sent from my Amazon Kindle Fire using xda premium

smirkis said:
Go to the development section. It says beta but its solid, I did most of the alpha testing for it and doom lord did the port. Is not officially supported by koush. If you know how to use fastboot, you can't fastboot flash recovery.img if u can't figure it out pm me. I'll get u going.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Agreed. Doomlord's CWM recovery port is awesome. It's touch based and I've tried most every feature and it seems very solid. I installed it in a much easier fashion than most... I just copied it to my SD area and used the dd command to put a copy into the recovery partition. I did this during normal operation of the Kindle.... No fastboot necessary in using that method. Neall.
.

ndoren said:
Agreed. Doomlord's CWM recovery port is awesome. It's touch based and I've tried most every feature and it seems very solid. I installed it in a much easier fashion than most... I just copied it to my SD area and used the dd command to put a copy into the recovery partition. I did this during normal operation of the Kindle.... No fastboot necessary in using that method. Neall.
.
Click to expand...
Click to collapse
That method is sketch. Fastboot is the proper way to flash a recovery. Any other way you risk trouble. Wear your rubbers and use the fastboot binary.

androidcues said:
That method is sketch. Fastboot is the proper way to flash a recovery. Any other way you risk trouble. Wear your rubbers and use the fastboot binary.
Click to expand...
Click to collapse
its not sketch, just no room for error.
put recovery.img on the root of ur SD card, than open mobile terminal, than type these commands.
su (enter)
dd if=/sdcard/recovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery (enter)
just don't mistype it, all it does is make a copy directly to the /dev folder.
this is how, rom manager actually puts cwm on ur device.
or use this http://forum.xda-developers.com/showthread.php?t=1500935
Sent from my HTC Glacier using xda premium

[RECOVERY] Clockworkmod Recovery TOUCH 5.5.0.4 | everything works except adb (5/15)

I am currently working on porting gweedo's touch recovery to the touchpad. So far I have a working clockworkmod 5.5.0.4 with the cool battery percentage mod but the touch part is not ready yet.
I just wanted to release this as a fully functional recovery (except adb).
1) boot into clockworkmod
2) mounts and storage >> mount /boot
3) adb push uImage.CWMRT5504 /boot/uImage.CWMRT5504
4) reboot and see it in the moboot menu
The touchscreen driver doesnt work but this is a completely working clockworkmod recovery (backups, restore, installing zips, etc.) (except adb)
Thanks
uImage.CWMRT5504 (install file)
LINK: HERE
KNOWN ISSUES:​
- touchscreen doesnt work (yet)
- adb doesnt work in recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Changelog:
- fixed the mount points to be a fully functional recovery. (thanks gdanko)

Pretty cool man!
Sent from my Touchpad using xda premium

good job man
Sent from my SGH-T989 using xda premium

I played around and it works pretty well! No bugs that I could find.
The only feedback I would give is that when you flash ROMs it sucks that the soft touch keys on the screen get in way of a lot of the wording. The horizontal blue line also would strike through words and it looks cruddy.
Any way to change where the message output is placed?

Can't wait to try this out. Keep the work going.

Can someone post mirrors for the downloads. They are both down.

LinuxNewb said:
I played around and it works pretty well! No bugs that I could find.
The only feedback I would give is that when you flash ROMs it sucks that the soft touch keys on the screen get in way of a lot of the wording. The horizontal blue line also would strike through words and it looks cruddy.
Any way to change where the message output is placed?
Click to expand...
Click to collapse
this should be fixed in this beta 14. and also the links are updated to an unlimited bandwidth server.

I hate to be "that guy," but I looked into this before and I don't think you can get the touchscreen working. On the TouchPad, the screen is controlled by a userland-based driver versus a kernel based driver. That's swell, but since CWM is basically only a kernel, it can't load the driver. I'd love to have someone prove me wrong, really. I just couldn't figure out a way to load it on CWM
Also, you're compiling it wrong if it only works temporarily when flashed. I believe that's like "make kernel" (or the equivalent, it's been awhile lol). I can'r remember the correct command, but I might have solved it by compiling CM and then removing the recovery portion? *shrug*
Good luck, though! I meant this to be taken as someone sharing their knowledge to help others, not as a deterrent. Please, continue with this and make an awesome CWM!

I'm not a kernel/recovery dev so I wouldn't even know where to begin looking at this but I know there was a touch based recovery back before CM9 called TeamWin Recovery Project (TWRP). Maybe it might help to look back at how they got it working and see if the same process can be used for CWM?
Here's the link to the original thread with TWRP thread.
http://forum.xda-developers.com/showthread.php?t=1400649
Hope it helps. I would like to see this work. I love the touch based CWM on my GNex.

Is this still in development?

so finally got mounts to work so this is now a fully functional recovery. the only things not working are the touch options and adb. once i get ts_srv to initialize then swipe gestures will finally work. but for now its still at least a good recovery.

So everything in the touch recovery works besides the touch?
Sent from my Galaxy Nexus using XDA

blckngldhwk said:
So everything in the touch recovery works besides the touch?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
LOL not sure if you are trying to be a smart-a** or honestly asking. you must not be asking for reals since the OP answers that question.
its still an updated CWM from the original 5.0.2.6. so its still better than the one from before.

sk8erwitskil said:
LOL not sure if you are trying to be a smart-a** or honestly asking. you must not be asking for reals since the OP answers that question.
its still an updated CWM from the original 5.0.2.6. so its still better than the one from before.
Click to expand...
Click to collapse
Well in the previous post he mentions adb does NOT work in this new version and I'd consider that a critical part of recovery. Any info on progress related to that? Great work.

famewolf said:
Well in the previous post he mentions adb does NOT work in this new version and I'd consider that a critical part of recovery. Any info on progress related to that? Great work.
Click to expand...
Click to collapse
Yes I agree that adb is a critical part. I'll be looking at init.rc to why adb isn't starting. Just haven't had a chance yet.
Sent from my SAMSUNG-SGH-I727 using XDA

you should really edit the main subject line, since no adb and no touch do not equal "FULLY WORKING RECOVERY." Not sure why anyone would bother using it at this point to be honest

sk8erwitskil said:
Yes I agree that adb is a critical part. I'll be looking at init.rc to why adb isn't starting. Just haven't had a chance yet.
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
You may want to search on "Aroma File Manager" (gui file manager you kick off from within recovery by installing the .zip) and see if you can potentially add a direct link to it in recovery...that would be VERY useful addon nobody else currently has as aroma file manager is relatively new.

The aroma touch installers are on most of the roms for my Xperia Arc. I wouldn't say nobody's using them yet as its the latest trend amongst developers. An aroma installer could benefit the touchpad community for those who want to choose what they do and don't want in the rom. But I'm gunna assume for the moment that if a touch recovery won't recognize touch that aroma probably won't work either.

Matt Devo said:
you should really edit the main subject line, since no adb and no touch do not equal "FULLY WORKING RECOVERY." Not sure why anyone would bother using it at this point to be honest
Click to expand...
Click to collapse
Well it is a fully functional recovery. Any recovery aspect you need (backup, restore, install, fix permissions) ALL work. Therefore, it's a working recovery. Touch is an extra and not a requirement to use recovery. So next time you should try thinking before you put down your ignorant ideas.
Sent from my SAMSUNG-SGH-I727 using XDA

sk8erwitskil said:
Well it is a fully functional recovery. Any recovery aspect you need (backup, restore, install, fix permissions) ALL work. Therefore, it's a working recovery. Touch is an extra and not a requirement to use recovery. So next time you should try thinking before you put down your ignorant ideas.
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Yes but you say Fully Working and Touch... well if adb is nonfunctional then its not FULLY functional and if Touch isn't working then its not TOUCH then is it... so yes... the thread should be pulled or the title modified
Sent from my cm_tenderloin using Tapatalk 2