I know they are two different things that one relies on the other to work. I understand that rom devs are usually different people than those working on the recovery program.
You gotta start somewhere...
2.5.x.x recovery in the root thread works enough that you can flash roms with no issues.
I don't know if there's a new version of recovery yet. What I meant by flakiness was the issue that some were having, including me, that the phone would always boot into recovery if it was off and you were trying to charge it.
herbthehammer said:
I don't know if there's a new version of recovery yet. What I meant by flakiness was the issue that some were having, including me, that the phone would always boot into recovery if it was off and you were trying to charge it.
Click to expand...
Click to collapse
That's a known issue with ALL clockwork recoveries and there probably will NEVER be a fix.
This may be the case but since the evo and epic used cwm recovery, the shift is the first phone I've experienced this snafu with. Maybe I was just lucky in the past. And yeah, I'm impatient for it to be fixed. I gotta chill out.
Why are you charging with the phone powered off anyway?
Compusmurf said:
Why are you charging with the phone powered off anyway?
Click to expand...
Click to collapse
because bump charging makes unicorn for reals
Compusmurf said:
Why are you charging with the phone powered off anyway?
Click to expand...
Click to collapse
It charges about 10 times quicker.
cloverdale said:
It charges about 10 times quicker.
Click to expand...
Click to collapse
Definitely
So is this recovery causing all the issues that are happening after root? Like the heating up/lag/low quadrant scores?
I'd like to root just to be able to remove things and use wireless tether, but honestly the phone works fine for me right now.
Recovery
You don't actually need to flash the CWM 3.0 recovery. I too like to charge my phone while it's turned off, and after reading about that bug, I just set up my phone to fastboot boot the CWM from preludedrew. What that does is it loads the new custom recovery, but without over-writing the original. From there you can follow the directions to install the custom ROM.
I'm running Evervolv, and so far it seems to be pretty great. Of course you don't get 4G and the camera is buggy still, but you can take pictures and the wifi actually goes faster now.
Then what's the best rom and recovery out for the shift?
Sent from my HTC Vision using XDA App
Quick question guys, since were on the topic of recovery idk if this is the correct "recovery" or not, I came from the evo so its not much different for me but when I did a nandroid backup for my evo I would select backup/restore and select backup google proprietary system files or something like that, I don't get that option with my shift, I just get backup, is that the same?
Compusmurf said:
That's a known issue with ALL clockwork recoveries and there probably will NEVER be a fix.
Click to expand...
Click to collapse
This is not the case with my EVO 4G. I can charge the phone when it's off without the recovery booting up. This is the case with CWM 3.0/2.6.X.X
Where can I download the recovery for the shift?
Sent from my HTC Vision using XDA App
Related
Hey All,
I have a super big problem >.<
I was trying to get clockworkmod recovery working on my phone and somehow it made me lose root access on CM6 and also I lost I lost my RA Recovery.
What do I do!?!?!
please help
PS: I still have S-On my phone
jvward said:
Hey All,
I have a super big problem >.<
I was trying to get clockworkmod recovery working on my phone and somehow it made me lose root access on CM6 and also I lost I lost my RA Recovery.
What do I do!?!?!
please help
PS: I still have S-On my phone
Click to expand...
Click to collapse
Follow the process to root again
Any Idea why that happened?
Do I need S-Off?
jvward said:
Any Idea why that happened?
Do I need S-Off?
Click to expand...
Click to collapse
i have no idea why that would happen ,, man im sorry , i only left it in cuz i know some people who use is ,
Hey Can I ask what does it offer outside what anons does?
jvward said:
Hey All,
I have a super big problem >.<
I was trying to get clockworkmod recovery working on my phone and somehow it made me lose root access on CM6 and also I lost I lost my RA Recovery.
What do I do!?!?!
please help
PS: I still have S-On my phone
Click to expand...
Click to collapse
I have doen this too, Clockworkmod replaces Amon's, just reflash amons and it will come back.
Thanks,
I got it working again, but just wondering how would I used this recovery manager if I wanted to ?
I dont think it was properly flashing its own recovery image.
Any advice would be appreciated.
Thanks!
jvward said:
Thanks,
I got it working again, but just wondering how would I used this recovery manager if I wanted to ?
I dont think it was properly flashing its own recovery image.
Any advice would be appreciated.
Thanks!
Click to expand...
Click to collapse
Don't use CLOCKWORK recovery unless you want a nice looking brick.
t2noob said:
Don't use CLOCKWORK recovery unless you want a nice looking brick.
Click to expand...
Click to collapse
Using Clockwork turns my phone into an Iphone 4?
Jking, does it bring anything to the plate that anons does not? and if so does anyone know if there is a way to manually flash the recovery image from them onto the phone, because if I use it, it just make my phone sit at the skate board screen?
jvward said:
Using Clockwork turns my phone into an Iphone 4?
Jking, does it bring anything to the plate that anons does not? and if so does anyone know if there is a way to manually flash the recovery image from them onto the phone, because if I use it, it just make my phone sit at the skate board screen?
Click to expand...
Click to collapse
It does have some pretty nice features, but it could cause a brick in the future.
I used it about a month before i had any problems with it.
I wasn't able to flash or restore any nands i had made, it would just spit out error after error. I even tried flashing the ROOT rom and that didn't help either. then when i tried rebooting it just never turned on again and I had to get the phone replaced. On other phones it works great, but on the eris its no good.
I would suggest stay with RA unless you're willing to risk your phone and money.
Cool,
I was just interested in the update rom feature for the Eris, but oh well if its that dangerous >.<
Thanks!
Quick question T2noob, I just noticed your post on the blog for clockwork recovery where you ever able to get past this error.
"The recovery for for the eris 1.8.1.1 isn't working, I tried to reboot into recovery but it never boots, it just stays at the android skateboard screen. If you need anything, testing, info on the phone, ect you can email me at XXXXXXXX"
Yea You need to flash RA then Clockwork thats how he had me fix it, but like i said don't use Clockwork recovery just take a look at this thread im not the only one
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=687272
I find it really odd that so many people have trouble with clockwork. Been using it to flash ROMs for months with no issues. Hopefully don't have any in the future!
i've used clockwork mod for 3 weeks now without any problems. also have rom manager installed, same author. i absolutely love both apps. i came from a v3 leak and couldn't get amon recovery to load on my phone, this worked like a charm first time. also i read in the forums that amons recovery is no longer supported by the author unlike clockwork mod which the author updates frequently.
t2noob said:
Yea You need to flash RA then Clockwork thats how he had me fix it, but like i said don't use Clockwork recovery just take a look at this thread im not the only one
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=687272
Click to expand...
Click to collapse
that thread you linked too only has you and the op posting in it. in fact i read that thread before i installed it and thought to myself that 2 people aren't enough to convince me it causes any more problems than amon's. personally i only used clockwork because that is what i could get loaded on my phone and have loved it since. also its been updated like 4 times since May when that link was started. so if it bricks my phone so what it just a phone and everythings backed up in triplicate anyways. be a nice excuse to get me a new toy.
I also believe the op's problem is that he used rom manager to flash amons recovery. now its my understanding that doing that removes clockwork mod recovery and replaces it with amon's. so he actually had a problem with amon's recovery and not clockwork mod recovery. i think the problems occur when people use rom manager to falsh a different recovery instead of clockwork mod which it is made to work with. just my ramblings here.
kzoodroid said:
that thread you linked too only has you and the op posting in it. in fact i read that thread before i installed it and thought to myself that 2 people aren't enough to convince me it causes any more problems than amon's. personally i only used clockwork because that is what i could get loaded on my phone and have loved it since. also its been updated like 4 times since May when that link was started. so if it bricks my phone so what it just a phone and everythings backed up in triplicate anyways. be a nice excuse to get me a new toy.
I also believe the op's problem is that he used rom manager to flash amons recovery. now its my understanding that doing that removes clockwork mod recovery and replaces it with amon's. so he actually had a problem with amon's recovery and not clockwork mod recovery. i think the problems occur when people use rom manager to falsh a different recovery instead of clockwork mod which it is made to work with. just my ramblings here.
Click to expand...
Click to collapse
take it as a grain of salt, if you come into the irc there are devs there that had this happen to them and can tell you what exactly happens. And I used ClockWork for about a month before i got the brick so...do as you like with this information.
well there are a lot of people running clockwork mod without problems. i went to the cyanogen forums looking for who was running cm6, like the op, and there are just as many people using clockwork as amon's. and there were a few reports of nandroid recovery failures using amon's in cm6 as the reason why they switched to clockwork.
kzoodroid said:
well there are a lot of people running clockwork mod without problems. i went to the cyanogen forums looking for who was running cm6, like the op, and there are just as many people using clockwork as amon's. and there were a few reports of nandroid recovery failures using amon's in cm6 as the reason why they switched to clockwork.
Click to expand...
Click to collapse
I heard that clock work is a great recovery on other devices, but on the eris it's not good the irc devs also worked with the guy who makes the recovery email him if you like he will tell you he had gotten complaints about on the eris. And there isn't an official cm6 for the eris so the people you talked to were running it for other devices. Like I said a grain of salt.
Sent from my Eris using XDA App
Well I would like to test it out but the recovery image it drops over anons does not seem to work anyone have any moderately detailed instructions on to how to get it to work?
Sent from my Eris using Tapatalk
Now and again I like to power down and make sure I have a full charge. I tried this y-day and when I powered down, then plugged into my charger, the phone auto booted into Clockwork Recovery. Is this normal?
Same thing happens to my phone as well. No idea as of why..
Sent from my HTC Glacier using XDA App
It's a known bug with Clockwork at this point. So far no one has figured it out.
I myself did a nandroid backup and re-flashed the stock recovery so I could do a couple full charges. I'm not messing with my phone until I get Clockwork back, just in case.
Any update on this? ROM Manager updated this morning but the version number on recovery appears to be the same. Haven't reflashed or tested yet.
Phateless said:
Any update on this? ROM Manager updated this morning but the version number on recovery appears to be the same. Haven't reflashed or tested yet.
Click to expand...
Click to collapse
From what I gathered, Koush doesn't foresee a fix for this bug. Check out his tweets. He says the G2 and MT4G report usb charging differently in recovery and probably won't be fixed. Sad. It's the only thing keeping me from flashing CW recovery.
Swyped on my rooted MyTouch4G
XfooYen said:
From what I gathered, Koush doesn't foresee a fix for this bug. Check out his tweets. He says the G2 and MT4G report usb charging differently in recovery and probably won't be fixed. Sad. It's the only thing keeping me from flashing CW recovery.
Click to expand...
Click to collapse
Have you heard anything more about this? It's really pissing me off that my phone doesnt shut off... grrr
Ya'll need to check this:
http://forum.xda-developers.com/showpost.php?p=10230011&postcount=13
Can any give me a link to the newest cw recovery?
Sent from my HTC Vision using Tapatalk
fliint said:
Can any give me a link to the newest cw recovery?
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
http://mrcellphoneunlocker.com/recovery.img
Download it from the RomManager.
Thanks
Sent from my HTC Vision using Tapatalk
its not on the rom manager, (yet)
gnunixguy said:
Download it from the RomManager.
Click to expand...
Click to collapse
Rom manager doesn't list 3.0, only 2.5.1.4 as being the latest
ROMmanager is 3.0.0.2 the recovery has not changed since november 10.
There's nothing wrong with cwm. Maybe one will come with GB.
vision
Does this recovery fix the "off issue" what's new in it?
PlatinumMOTO said:
Does this recovery fix the "off issue" what's new in it?
Click to expand...
Click to collapse
Support for ext4 file systems, that GB uses. If you're using any Android 2.2 based ROM, stay with CWM 2.5.1.3.
Sent from my HTC Desire Z using XDA App
AllWin said:
Support for ext4 file systems, that GB uses. If you're using any Android 2.2 based ROM, stay with CWM 2.5.1.4.
Sent from my HTC Desire Z using XDA App
Click to expand...
Click to collapse
For latest mine says 2.5.1.3
omarsalmin said:
For latest mine says 2.5.1.3
Click to expand...
Click to collapse
Sorry, that was a typo. Fixed.
i see what you mean... and i just installed 3.0.0 and its my color - orange
-- this is just for the gingerbread build by RHCP I am crazy because I am flashing gingerbread to my phone right now. i think ive gone insane.
androidcues said:
i see what you mean... and i just installed 3.0.0 and its my color - orange
-- this is just for the gingerbread build by RHCP I am crazy because I am flashing gingerbread to my phone right now. i think ive gone insane.
Click to expand...
Click to collapse
let us know the results? did your g2 survive?
can anyone let us know if any problems have been discovered with this so far?
warsng said:
let us know the results? did your g2 survive?
Click to expand...
Click to collapse
Yes it did --- I kinda jumped into it and did not really heed Cyanogen's big fat warnings... (reckless flashing) and I couldnt get gapps to flash -- the stuff from rhcp's CM7 thread -- but I got gingerbread going -- then I got distracted all night...woke up this morning trying to make the phone shape up for work -- that was a #fail and the battery seems horrible (then again by no means was it a proper battery test) -- so I decided to restore and that involved new drivers..(for some reason my SDK at work couldnt find the phone so I had to reinstall a fresh SDK (which i named gbSDK)... then found the current recovery at mybrainhurts.com and erased 3.0.0 and fastbooted the froyo recovery back in and restored. easy pie --
gingerbread is a whole 'nother game -- i just hope theres a way to go back and forth between froyo and GB (and eclair/cupcake/donut) without having to fastboot erase and fastboot flash relevant recoveries.
I am sure folks want to know if the new one fixes the "off" mode...and the answer is - i dont know. I didnt check. i kind of hope not because its a feature rather than a bug. theres no quick way to get to recovery when the phone is off. (on to fboot then to hboot then to recovery is too much work)
Is it even worth it to upgrade at this point in time? I'm a bit worried as it seems to be working pretty damn good with what I'm doing now. No partitions on my SD card because I don't care to put apps on it (it's not the fastest class card anyway).
androidcues said:
Yes it did --- I kinda jumped into it and did not really heed Cyanogen's big fat warnings... (reckless flashing) and I couldnt get gapps to flash -- the stuff from rhcp's CM7 thread -- but I got gingerbread going -- then I got distracted all night...woke up this morning trying to make the phone shape up for work -- that was a #fail and the battery seems horrible (then again by no means was it a proper battery test) -- so I decided to restore and that involved new drivers..(for some reason my SDK at work couldnt find the phone so I had to reinstall a fresh SDK (which i named gbSDK)... then found the current recovery at mybrainhurts.com and erased 3.0.0 and fastbooted the froyo recovery back in and restored. easy pie --
gingerbread is a whole 'nother game -- i just hope theres a way to go back and forth between froyo and GB (and eclair/cupcake/donut) without having to fastboot erase and fastboot flash relevant recoveries.
I am sure folks want to know if the new one fixes the "off" mode...and the answer is - i dont know. I didnt check. i kind of hope not because its a feature rather than a bug. theres no quick way to get to recovery when the phone is off. (on to fboot then to hboot then to recovery is too much work)
Click to expand...
Click to collapse
what exactly happened when you flashed the gapps?
at least it didn't fry your g2. i think i might give it a go once i hear a few more success stories. my main worry atm is the ext4 issue. i guess i could just wait until rc1 i guess.
by 'off mode', are you referring to s-off?
warsng said:
what exactly happened when you flashed the gapps?
at least it didn't fry your g2. i think i might give it a go once i hear a few more success stories. my main worry atm is the ext4 issue. i guess i could just wait until rc1 i guess.
by 'off mode', are you referring to s-off?
Click to expand...
Click to collapse
I read the rhcp cm7 thread and i needed to unmount system before flashing the gapps. Thats why gapps failed because i didnt read!
By Off i meant how cw doesnt let the phone turn off when charging... i hope cw 3.0 lets us keep that feature.
Ill probably give it another go this weekend...it works its just if you wanna go back to froyo you need to replace recoveries manually..not a big deal but frankly gingerbread isnt all that more exciting than froyo. I feel i have what i need.in Froyo..the gb keyboard...the gb market... and thats fine with me.
vision
androidcues said:
I read the rhcp cm7 thread and i needed to unmount system before flashing the gapps. Thats why gapps failed because i didnt read!
By Off i meant how cw doesnt let the phone turn off when charging... i hope cw 3.0 lets us keep that feature.
Ill probably give it another go this weekend...it works its just if you wanna go back to froyo you need to replace recoveries manually..not a big deal but frankly gingerbread isnt all that more exciting than froyo. I feel i have what i need.in Froyo..the gb keyboard...the gb market... and thats fine with me.
vision
Click to expand...
Click to collapse
appreciate the info , thanks.
Erase Recovery option
Call me naïve, but if people are making full-blown builds with an image recovery and everything from the CM gingerbread source (which includes the Clockwork Mod recovery 3.0.0 image if I'm reading the source properly), could you just go into ROM Manager, go into Settings, and check the "Erase Recovery" option to allow it to erase the recovery between flashes?
I would test this myself, but I need to go home and make myself fresh builds of CM7 and CM6.2 to try swapping/flashing back and forth between. I can report back once I get around to it later this afternoon.
If I understand that option correctly, applying a full flash of these alpha builds of CM7 should write the new recovery image (v3.0.0.0), and if you need to switch back to CM6, you should be able to just reflash a full build of 6.1.1/6.2 back and it will restore the older recovery image (v2.5.1.8 according to the latest froyo version).
EDIT: Negate that thought. Not sure how you would go about forcing the recovery image flash while in recovery. I got to research this a little more...
Now available for the Evo Shift, go try it out and let us know what ya think about it!
If it aint broke, don't fix it.
VICODAN said:
If it aint broke, don't fix it.
Click to expand...
Click to collapse
I don't care I would still like a ICS touch recovery for the shift that works with rom manager.
I saw this a couple of days ago. I wouldn't mind getting it.
Sent from my PG06100 using Tapatalk
Been using it on the EVO. It's good, but not quite as responsive as TWRP was. It's basically just an enlarged CWM that's touchable, not quite designed for touch yet. On the otherhand its still nice and can't wait to see future progressions with it
Sent from my EVO 4G
notsointeresting said:
Been using it on the EVO. It's good, but not quite as responsive as TWRP was. It's basically just an enlarged CWM that's touchable, not quite designed for touch yet. On the otherhand its still nice and can't wait to see future progressions with it
Sent from my EVO 4G
Click to expand...
Click to collapse
Yeah according to koush's twitter he just "hacked" touch into cwm recovery so I'm sure he'll work on it more. Twrp is a nice recovery and koush is a really good recovery developer so I'm sure he'll make it better if possible. It's funny after finding out about twrp 2.0 being in development before it was even released I asked koush if it was possible to have touch in cwm. Now we're getting it lol.
notsointeresting said:
Been using it on the EVO. It's good, but not quite as responsive as TWRP was. It's basically just an enlarged CWM that's touchable, not quite designed for touch yet. On the otherhand its still nice and can't wait to see future progressions with it
Sent from my EVO 4G
Click to expand...
Click to collapse
Using it on my NS4G and honestly I like it better than TWRP. Everything being larger is reassuring, in TWRP I was always nervous because there was such a small area to select. With the items being so close in TWRP I always wanted my volume keys to work so I could make fine maneuvers and in CWM Touch they do. So you can use it just like regular CWM or with touch. Nice if you mess up your touch screen. And of course it also works with ROM Manager. I downloaded it from the site but I may actually donate the $2 for it too.
Touch recovery has just become available on my SHIFT!!! CHECKIN' IT OUT NOW, VERY COOL!
Let Me Put My Shift In U
letmeputdatipin said:
Touch recovery has just become available on my SHIFT!!! CHECKIN' IT OUT NOW, VERY COOL!
Let Me Put My Shift In U
Click to expand...
Click to collapse
I know I tested it for him last night but it's not stable. I wouldn't purchase it quite yet. Download it from the site and test it out. It will boot into recovery for about 5-10 secs format your cache then reboot to system/rom. Strange bug. It would be nice if someone else could confirm this.
sparksco said:
I know I tested it for him last night but it's not stable. I wouldn't purchase it quite yet. Download it from the site and test it out. It will boot into recovery for about 5-10 secs format your cache then reboot to system/rom. Strange bug. It would be nice if someone else could confirm this.
Click to expand...
Click to collapse
I just flashed it through fastboot and haven't seen that issue. I'm actually in the process of making a backup
Edit: Weird thing.. made a backup and rebooted, everything was gone. It brought my ROM completely back to barebones.. even gapps were gone. Restoring with Touch now to see what happens.
Sent from my Android powered Tenderloin
crump84 said:
I just flashed it through fastboot and haven't seen that issue. I'm actually in the process of making a backup
Edit: Weird thing.. made a backup and rebooted, everything was gone. It brought my ROM completely back to barebones.. even gapps were gone. Restoring with Touch now to see what happens.
Sent from my Android powered Tenderloin
Click to expand...
Click to collapse
Hmm, well I did fastboot erase recovery before flashing, not sure if that has anything to do with it. What recovery did you flash this on top of, just the previous cwm recovery? You can also report bugs to him on irc freenode #koush
sparksco said:
Hmm, well I did fastboot erase recovery before flashing, not sure if that has anything to do with it. What recovery did you flash this on top of, just the previous cwm recovery? You can also report bugs to him on irc freenode #koush
Click to expand...
Click to collapse
Yeah I was coming from the previous version of cwm. I just did a restore and everything is fine. Ill probably mess with it a little later when I have some free time.
Sent from my Android powered Tenderloin
I'm not at my pc to try fastboot again but I did flash the previous cwm recovery and it works fine. Then I flashed the new touch recovery with the flash_image command in terminal emulator and I'm getting the same results as before. This is really annoying me because I would like to get this recovery working and I don't know WTH is going wrong here. Maybe it's the new firmware update? I doubt it. Anyways hope to here from more people that try this out.
Edit: when I get a chance later I'll flash with fastboot without running the fastboot erase recovery command and see how it goes.
I must have got lucky... I used joey krim's GUI Flash App and flashed it over the top of the prior clockwork mod recovery... I'll spend a little time tonight trying to replicate...
Sent from my PG06100 using Tapatalk
Well just used the touch recovery to flash my first ROM and had no issues. Maybe my first experience was fluke.
Anyway, liking this recovery so far.
I'm gonna be using GUI flash like Drob since its just easier for me
question for the pro's, if I understand all this I just rename the recovery-clockwork-touch-5.8.1.6-speedy.img to PG06100.img , boot into fastboot and flash ?
jrny99 said:
question for the pro's, if I understand all this I just rename the recovery-clockwork-touch-5.8.1.6-speedy.img to PG06100.img , boot into fastboot and flash ?
Click to expand...
Click to collapse
I'm nit sure about that (although I feel it should be .zip but probably wrong), but you could use Flash Image GUI from the Market or use fastboot from your PC. You'd just stick the .img file in the same folder as fastboot, cd there and type "fastboot flash recovery whateveryounamedit.img". Personally I like Flash Image, works well for flashing kernels too.
jrny99 said:
question for the pro's, if I understand all this I just rename the recovery-clockwork-touch-5.8.1.6-speedy.img to PG06100.img , boot into fastboot and flash ?
Click to expand...
Click to collapse
Yeah, just to reiterate what J-Ice already said... don't rename the img, just flash through fastboot.
I can confirm this is not working for at least one other person on the latest firmware update via twitter messaging...I've tried GUI, fastboot, flash_image, all same results.
Due to koush for releasing a wonderful tool to the android community i threw in the current cwm into the builder and it came out with a new and shiny version!
Known Issues
Don't boot into recovery using rom manager, as is it will boot u into older version.. but if u delete the recovery-update.zip in the clockworkmod folder it will boot into the new recovery but with an error
The background images for the recovery are huge x_X
Recovery: recovery-clockwork-5.8.4.3-desirec.img
md5sum: db3e9d93c7f1f52a427b7f6ca427cabf
mine, just in case!
Do you have an Eris that you're testing this on? I was under the impression that CWM and ROM Manager didn't play nicely with the Eris. What's your experience been?
KarateExplosion6 said:
Do you have an Eris that you're testing this on? I was under the impression that CWM and ROM Manager didn't play nicely with the Eris. What's your experience been?
Click to expand...
Click to collapse
ya, I have an Eris.. I think that was long time ago which has been solved before even the latest official cwm..
I left the Eris long ago but keep it around as a pmp, since my trackball doesnt scroll and the mic is busted.. when I started using it again I couldn't flash anything new because I was on amonRA.. so I took the plunge and used cwm and I haven't ran into a single issue.. there, that's my Eris history xP right now I have it on cm7.2 stable
Sent from my Galaxy Nexus using Tapatalk 2
swordrune10 said:
ya, I have an Eris.. I think that was long time ago which has been solved before even the latest official cwm..
I left the Eris long ago but keep it around as a pmp, since my trackball doesnt scroll and the mic is busted.. when I started using it again I couldn't flash anything new because I was on amonRA.. so I took the plunge and used cwm and I haven't ran into a single issue.. there, that's my Eris history xP right now I have it on cm7.2 stable
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Fantastic! I was actually looking for someone running CM7.2 Stable. My brother is using my Eris and I've had him on xtrSense forever. I'd like to flash him up to Gingerbread. What do you think of the stable release?
KarateExplosion6 said:
Fantastic! I was actually looking for someone running CM7.2 Stable. My brother is using my Eris and I've had him on xtrSense forever. I'd like to flash him up to Gingerbread. What do you think of the stable release?
Click to expand...
Click to collapse
the only thing I have to say since I barely use the thing is that I have installed is a 32gb sdcard and before on 7.1 it sometimes didn't finish the boot cycle because every so often it gets stuck at checking sdcard.. now its more likely to boot completely.. don't get me wrong, it still sometimes gets stuck on boot... again fault is because of the 32gb sdcard.. and me having to have lots of music...
Sent from my Galaxy Nexus using Tapatalk 2
swordrune10 said:
the only thing I have to say since I barely use the thing is that I have installed is a 32gb sdcard and before on 7.1 it sometimes didn't finish the boot cycle because every so often it gets stuck at checking sdcard.. now its more likely to boot completely.. don't get me wrong, it still sometimes gets stuck on boot... again fault is because of the 32gb sdcard.. and me having to have lots of music...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Shouldn't matter to my brother. He doesn't even use an SD card!!
KarateExplosion6 said:
Shouldn't matter to my brother. He doesn't even use an SD card!!
Click to expand...
Click to collapse
x_X before I switched I used cm5 (unofficial) on Eris, it was good.. gingerbread is ok on it.. but ics on a better phone is a lot better
Sent from my Galaxy Nexus using Tapatalk 2
swordrune10 said:
Due to koush for releasing a wonderful tool to the android community i threw in the current cwm into the builder and it came out with a new and shiny version!
Known Issues
Don't boot into recovery using rom manager, as is it will boot u into older version.. but if u delete the recovery-update.zip in the clockworkmod folder it will boot into the new recovery but with an error
The background images for the recovery are huge x_X
Recovery: recovery-clockwork-5.8.4.3-desirec.img
md5sum: db3e9d93c7f1f52a427b7f6ca427cabf
Click to expand...
Click to collapse
How does the tool work? I want to get this to work on my htc hero gsm
jordfaz said:
How does the tool work? I want to get this to work on my htc hero gsm
Click to expand...
Click to collapse
what u do is u go to the site and insert a recovery ( even stock ) for ur device and it builds it for ur based on cwm.. fortunately ( or unforunately, if u wanted to do it urself ) there was already one done for the hero =] .... yes that means i looked through a good amount of them just to see what people were building x.x
swordrune10 said:
ya, I have an Eris.. I think that was long time ago which has been solved before even the latest official cwm..
Click to expand...
Click to collapse
There are lots of posts on this site (and on others), many relatively recent, from people with Erises that cannot boot that almost all started with a person who was running with ClockworkMod as their recovery image; none that I know of from people who started with Amon_RA. Scary Alien made a trackball-optional version of Amon_RA (with Amon_RA's permission) for the Eris which works with the hardware keys as well as the trackball. See http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
So, be careful with Clockwork Recovery.
doogald said:
There are lots of posts on this site (and on others), many relatively recent, from people with Erises that cannot boot that almost all started with a person who was running with ClockworkMod as their recovery image; none that I know of from people who started with Amon_RA. Scary Alien made a trackball-optional version of Amon_RA (with Amon_RA's permission) for the Eris which works with the hardware keys as well as the trackball. See http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html
So, be careful with Clockwork Recovery.
Click to expand...
Click to collapse
I seriously think the issues have been resolved.. the way koush works on them brings what he did before to the next recovery he makes.. if that issue was still around there would be a lot of phones not booting..
Sent from my Galaxy Nexus using Tapatalk 2
swordrune10 said:
I seriously think the issues have been resolved.. the way koush works on them brings what he did before to the next recovery he makes.. if that issue was still around there would be a lot of phones not booting..
Click to expand...
Click to collapse
There was just an issue a week or two ago. http://forum.xda-developers.com/showthread.php?t=1702130
That's pretty typical - for some reason, these phones end up with bad blocks in some partitions (usually system.img, cache.img) that are difficult to resolve.
Note that you can install ROM Manager on a CM ROM and hit "install recovery". This installs an update.zip file in the root of the SD card. From Amon_RA you can flash the update.zip and it will start Clockwork. That method seems to be safe and is the way that I flash, Nandroid, etc., on the Eris.
Again, this seems to be an Eris issue with Clockwork as the default recovery. If it works for you, that's fine, but I would try to get on the 1.49.2000 S-OFF bootloader so that you can use fastboot as a recovery tool if you are not on that bootloader already.
doogald said:
There was just an issue a week or two ago. http://forum.xda-developers.com/showthread.php?t=1702130
That's pretty typical - for some reason, these phones end up with bad blocks in some partitions (usually system.img, cache.img) that are difficult to resolve.
Note that you can install ROM Manager on a CM ROM and hit "install recovery". This installs an update.zip file in the root of the SD card. From Amon_RA you can flash the update.zip and it will start Clockwork. That method seems to be safe and is the way that I flash, Nandroid, etc., on the Eris.
Again, this seems to be an Eris issue with Clockwork as the default recovery. If it works for you, that's fine, but I would try to get on the 1.49.2000 S-OFF bootloader so that you can use fastboot as a recovery tool if you are not on that bootloader already.
Click to expand...
Click to collapse
Yeah, that's how I always thought was the safest way to do it--running CWM from ROM Manager.
Yep, been using ROM Manager, and CWM through update.zip via Amon RA for a year and a half now without any issues. I don't think I'd ever be tempted to flash CWM over Amon RA; I'd rather have the best of both worlds without wondering if I'm taking any additional risk.
well.. I understand everyone's opinion and its cool.. I tried working on making a recovery.zip that just restarted the recovery not overwrite it, but it just wouldn't do it =/
Sent from my Galaxy Nexus using Tapatalk 2